7. 	Service access points (SAPs) and primitives
7.1 	Introduction
The MIH Function uses the following SAPs for interfacing with other entities.
7.1.1 	Media-dependent SAPs
1)		MIH_LINK_SAP: Abstract media-dependent interface of MIHF with the lower layers of the media-specific protocol stacks. The MIH_LINK_SAP maps to the following technology specific SAPs:
a)			MLME_SAP
a)			: The MIHF uses this SAP for interfacing with the link layer of IEEE 802.11 networks. The MIH_LINK_SAP defines additional primitives that map to MLME_SAP. These primitives are recommended as enhancements to IEEE 802.11 link layer SAPs.
a)			 MLME_SAP is defined by IEEE 802.11 and it may include, but is not limited to primitives related to: 
—				System configuration
—				Link state change notifications/triggers
—				MIH frame transport through control or management frames
b)			C_SAP, M_SAP: The MIHF uses these SAPs for interfacing with the Control and Management planes of the IEEE 802.16 network. 

C_SAP is defined by IEEE 802.16g and it may include, but is not limited to primitives related to: 
—				Handovers (e.g., notification of HO request from mobile station (MS))
—				Idle mode mobility management (e.g., Mobile entering idle mode)
—				Subscriber and session management (e.g., Mobile requesting session setup)
—				Radio resource management
—				Authentication, Authorization, and Accounting (AAA) server signaling (e.g., EAP payloads)
—				Media Independent Function Services
			The primitives defined as part of C_SAP are described in Table B, “C_SAP primitives,” on page 167.

M_SAP is defined by IEEE 802.16g and it may include, but is not limited to primitives related to: 
—				System configuration
—				Monitoring Statistics
—				Notifications Triggers
—				Multi-mode interface management
c)			MIH_3GLINK_SAP: This SAP defines the interface between the MIHF and the different protocol elements of the 3G system. 

3GPP and 3GPP2 service primitives for GSM, UMTS, LAC, PPP and LTE system architecture evolution (SAE) may be used to access IEEE 802.21 services. This is done by establishing a relationship between the 3GPP/3GPP2 primitives and IEEE 802.21 primitives.

Table L-3 lists this mapping. Note that a 3GPP primitive group may be mapped to more than one IEEE 802.21 primitive. For example, the “SMGREG-PDP-MODIFY” primitive is mapped to the Link_Up primitive and it could also indicate the successful completion of handover and is hence also mapped to the MIH_Handover_Complete primitive.
d)			LSAP: defined in the IEEE 802.2 standard, provides the interface between the MIHF and the Logical Link Control sublayer in IEEE 802.3 and IEEE 802.11 networks. This SAP is used for local MIH exchanges between the MIHF and the lower layers of the IEEE 802.3 interface (as the IEEE 802.3 instantiation of the MIH_LINK_SAP) and for the L2 transport of MIH messages across IEEE 802.3 and IEEE 802.11access links. When MIH messages are exchanged over 802.11 access links using LSAP, the message are carried in 802.11 data frames.
e)			CS_SAP: defined in the IEEE 802.16 standard, provides the interface between the MIHF and the service-specific Convergence Sublayer in IEEE 802.16 networks. This SAP is used for the L2 transport of MIH messages through data frames across IEEE 802.16 access links.
2)		MIH_NET_SAP: Abstract media-dependent interface of MIHF which provides transport services over the data plane on the local node, supporting the exchange of MIH information and messages with the remote MIHF.
7.1.2 	Media-independent SAPs
1)		MIH_SAP
1)		: This SAP defines the media-independent interface between the MIHF and MIH Users.
2)		
2)		MIH_NMS_SAP
2)		: This SAP defines the media-independent interface between the MIHF and the Network Management System.
7.2 	SAPs
The SAPs are defined as a set of primitives. Taken together, the primitives define the services. Within the definition of each primitive there is a table of allowable parameters. Each parameter is defined using abstract data types. These types indicate the semantic value of that parameter. The parameters defined within the clause for a particular primitive are produced or consumed by that primitive. Several of the abstract data types are used in multiple primitive definitions. In each abstract data type definition, the various names applied to this type are listed. 
Most of the primitives have corresponding MIH protocol messages. In those messages, there are TLV encoded parameters that implement the primitive parameter abstract data types within the protocol. The definition of the full binary encoding for each of these instantiations is in Annex C.
7.2.1 	Media-dependent SAPs
7.2.1.1 	MIH_LINK_SAP
The primitives defined as part of the MIH_LINK_SAP are described in  Table 10 and their mapping to specific link technology primitives are listed in Tables L-1-L-3.
Table 10—	MIH_LINK_SAP primitives	
Primitives	Service category	Description	
Link_Event_Subscribe	Command	Subscribe for event notifications	
Link_Event_Unsubscribe	Command	Unsubscribe from event notifications	
Link_Configure_Thresholds	Command	Configure link thresholds for Link events	
Link_Up	Event	L2 connectivity is established 	
Link_Down	Event	L2 connectivity is lost	
Link_Going_Down	Event	L2 connectivity loss is imminent	
Link_Event_Rollback	Event	Predicted event has not occurred and hence event indication must be rolled back.	
Link_Detected	Event	A new link is detected	
Link_Parameters_Report	Event	Link parameters have crossed specified thresholds	
Link_PDU_Transmit_Status	Event	Indicate transmission status of a PDU	
Link_Handover_Imminent	Event	L2 handover is imminent	
Link_Handover_Complete	Event	L2 handover has been completed	
Link_Capability_Discover	Command	Query and discover the list of supported link layer events and link layer commands.	
Link_Get_Parameters	Command	Request parameters of air interface	
Link_Action	Command	Request actions on a link layer connection	
.

7.2.1.2 	MIH_NET_SAP
The following primitives are defined for MIH_NET_SAP.
Table 11—	MIH_NET_SAP primitives	
Primitive	Service
category	Description	
MIH_TP_Data	Network Communication	This primitive is used for transfer of data	

7.2.2 	Media-independent SAPs
7.2.2.1 	MIH_SAP
The primitives defined as part of MIH_SAP are described in  Table 12.
Table 12—	MIH_SAP primitives	
Primitives	Service category	Description	
MIH_Capability_Discover	Service 
Management	Discover list of Events and Commands supported by MIHF.	
MIH_Register	Service 
Management	Register with a remote MIHF.	
MIH_DeRegister	Service 
Management	Deregister with a remote MIHF.	
MIH_Event_Subscribe	Service 
Management	Subscribe for MIH event notifications	
MIH_Event_Unsubscribe	Service 
Management	Unsubscribe from MIH event notifications	
MIH_Link_Up	Event	L2 connection has been established	
MIH_Link_Down	Event	L2 connectivity is lost	
MIH_Link_Going_Down	Event	L2 connectivity is predicted to go down	
MIH_Link_Detected	Event	A new link is detected	
MIH_Link_Parameters_Report	Event	Link parameters have crossed specified threshold	
MIH_Link_Event_Rollback	Event	Predicted event has not occurred and hence event indication must be rolled back	
MIH_Link_PDU_Transmit_Status	Event	Indicate transmission status of a PDU	
MIH_Link_Handover_Imminent	Event	L2 handover is imminent	
MIH_Link_Handover_Complete	Event	L2 handover has been completed	
MIH_Get_Link_Parameters	Command	Get the status of link	
MIH_Configure_Link	Command	Configure link parameters and parameter thresholds	
MIH_Scan	Command	Scan the network	
MIH_Net_HO_Candidate_Query	Command	Initiate handover	
MIH_MN_HO_Candidate_Query	Command	Initiate MN query request for candidate network	
MIH_N2N_HO_Query_Resources	Command	Prepare for handover and query available resources	
MIH_Net_HO_Commit	Command	Network has committed to handover	
MIH_MN_HO_Commit	Command	Mobile node has committed to handover	
MIH_MN_HO_Complete	Command	Initiate MN handover complete notification	
MIH_N2N_HO_Complete	Command	Handover has been completed	
MIH_Get_Information	Information	Request to get information from repository	

MIH command primitives defined in MIH_SAP may indicate its destination as either the local MIHF or a remote peer MIHF. For the remote case, the local MIHF will first process the primitive to create an MIH message and then forward the message to the destination peer MIHF for execution. 
7.2.2.2 	MIH_NMS_SAP
The primitives defined as part of MIH_NMS_SAP are described in  Table 13.
Table 13—	MIH_NMS_SAP primitives	
Primitives	Service Category	Description	
MIH_NMS_Initialize	Network Management		This primitive brings the MIHF to the initial state in the state transition.	
MIH_NMS_Get_State	Network Management		Get state information of the MIHF indicating working status.	
MIH_NMS_Reset	Network Management		During operation resets the MIHF parameters and brings it into the initial state.	

7.3 	MIH_LINK_SAP primitives
7.3.1 	Link_Event_Subscribe
7.3.1.1 	
7.3.1.1 	Link_Event_Subscribe.request
7.3.1.1.1 	Function
This primitive is used by MIHF (the subscriber) to subscribe an interest in one or more events from a specific link layer technology. The response indicates which of the requested events were successfully subscribed to. Events that were not successfully subscribed to will not be delivered to the subscriber.
7.3.1.1.2 	Semantics of service primitive
Link_Event_Subscribe.request
			 	(
				RequestedLinkEventList
				)
Parameter:
Name	Type	Description	
Requested Link Event List	LINK_EVENT_LIST	List of link layer events that the subscriber would like to receive indications for.	

7.3.1.1.3 	When generated
This primitive is generated by a subscriber such as the MIHF that is seeking to receive event indications from different link layer technology.
7.3.1.1.4 	Effect on receipt
The recipient responds immediately with Link_Event_Subscribe.confirm primitive.
7.3.1.2 	
7.3.1.2 	Link_Event_Subscribe.confirm
7.3.1.2.1 	Function
This primitive returns the result of the subscription request.
7.3.1.2.2 	Semantics of service primitive
Link_Event_Subscribe.confirm
			 	(
				ResponseLinkEventList,
				Status
				)
Parameters:
Name	Type	Description	
Response Link Event List	LINK_EVENT_LIST	List of link layer events along with their subscription status.	
Status			STATUS	Status of operation. Code 3 (Authorization Failure) is not applicable.	

7.3.1.2.3 	
7.3.1.2.3 	When generated
This primitive is generated in response to a Link_Event_Subscribe.request primitive.
7.3.1.2.4 	Effect on receipt
The recipient may examine the ResponseLinkEventList and learn about the subscription status of different events. If Status does not indicate “Success”, the recipient shall ignore the returned ResponseLinkEventList and perform appropriate error handling.
7.3.2 	Link_Event_Unsubscribe
7.3.2.1 	Link_Event_Unsubscribe.request
7.3.2.1.1 	Function
This primitive is used by the MIHF (the subscriber) to unsubscribe from a set of previously subscribed link layer events.
7.3.2.1.2 	Semantics of service primitive
Link_Event_Unsubscribe.request
			 	(
				RequestedLinkEventList
				)
Parameter:
Name	Type	Description	
Requested Link Event List	LINK_EVENT_LIST	List of link layer events for which indications need to be unsubscribed from the Event Source	

7.3.2.1.3 	When generated
This primitive is generated by a subscriber such as the MIHF that is seeking to unsubscribe from an already subscribed set of events.
7.3.2.1.4 	Effect on receipt
The recipient responds immediately with Link_Event_Unsubscribe.confirm primitive.
7.3.2.2 	Link_Event_Unsubscribe.confirm
7.3.2.2.1 	Function
This primitive returns the result of the request to unsubscribe from receiving link layer event notifications.
7.3.2.2.2 	Semantics of service primitive
Link_Event_Unsubscribe.confirm
			 	(
				ResponseLinkEventList,
				Status
				)
Parameters:
Name	Type	Description	
Response Link Event List	LINK_EVENT_LIST	List of link layer events along with their unsubscription status.	
Status			STATUS	Status of operation. Code 3 (Authorization Failure) is not applicable.	

7.3.2.2.3 	When generated
This primitive is generated in response to a Link_Event_Unsubscribe.request primitive.
7.3.2.2.4 	Effect on receipt
The recipient may examine the ResponseLinkEventList and learn about the unsubscription status of different events. If Status does not indicate “Success”, the recipient shall ignore the returned ResponseLinkeventList and perform appropriate error handling.
7.3.3 	Link_Configure_Thresholds
7.3.3.1 	Link_Configure_Thresholds.request
7.3.3.1.1 	Function
This primitive is used by the MIHF to configure thresholds for the Link_Parameters_Report indication.
7.3.3.1.2 	Semantics of service primitive
Link_Configure_Thresholds.request
			 	(
				 LinkConfigureParameterList
				)
Parameter:
Name	Type	Description	
Link Configure Parameter List	LIST(LINK_CONFIG_PARAM)	A list of Link Configure Parameter. 	

7.3.3.1.3 	When generated
This primitive is generated by an MIHF that may need to set threshold values for different link parameters.
7.3.3.1.4 	Effect on receipt
The recipient responds immediately with Link_Configure_Threshold.confirm primitive.
7.3.3.2 	Link_Configure_Thresholds.confirm
7.3.3.2.1 	Function
This primitive is sent in response to the Link_Configure_Threshold.request primitive. This primitive specifies the status of threshold configuration operation.
7.3.3.2.2 	Semantics of service primitive
Link_Configure_Thresholds.confirm (
				LinkConfigureStatusList,
				Status
				)
Parameters:
Name	Type	Description	
Link Configure Status List	LIST(LINK_CONFIG_STATUS)	A list of Link Configure Status.	
Status			STATUS	Status of operation. Code 3 (Authorization Failure) is not applicable.	

7.3.3.2.3 	When generated
This primitive is generated in response to the Link_Configure_Thresholds.request operation
7.3.3.2.4 	Effect on receipt
The recipient prepares to receive Link_Parameters_Report indications on successful execution of this primitive. However, if Status does not indicate “Success”, the recipient shall ignore any other returned values and, instead, shall perform appropriate error handling.
7.3.4 	
7.3.4 	Link_Up.indication
7.3.4.1 	Function
This notification is delivered when a layer 2 connection is established on the specified link interface. All layer 2 activities in establishing the link connectivity are expected to be completed at this point of time.
7.3.4.2 	Semantics of service primitive
Link_Up.indication 			(
			LinkIdentifier,
			MacOldAccessRouter,
			MacNewAccessRouter,
			IPRenewalFlag,
			Mobility Management Support
			)
Parameters:
Name	Type	Description	

Link Identifier	LINK_TUPLE_ID	Identifier of the link associated with the event	

MAC Old Access Router	
MAC_ADDRESS	
(Optional) MAC Address of old Access Router	

MAC New Access Router	
MAC_ADDRESS	(Optional) MAC Address of new Access Router	

IP Renewal Flag	IP_RENEWAL_FLAG	
(Optional) 
Indicates whether the MN shall change IP Address in the new PoA

Mobility Management Support	IP_MOBILITY_MGMT	
(Optional) 
Indicates the type of Mobility Management Protocol supported by the new PoA 	

7.3.4.3 	When generated
This notification is generated when a layer 2 connection is established for the specified link interface.
7.3.4.4 	Effect on receipt
The MIHF normally passes this link notification to the MIH User(s) which has subscribed for this notification in an MIH_Link_Up event. The MIH User(s) may take different actions on this notification.
7.3.5 	Link_Down.indication
7.3.5.1 	Function
This notification is delivered when a layer 2 connection is broken on the specified link and no more packets may be sent on the specified link
7.3.5.2 	Semantics of service primitive
Link_Down.indication 			(
			LinkIdentifier,
			MacOldAccessRouter,
			ReasonCode
			)
Parameters
:
Name	Type	Description	

Link Identifier	LINK_TUPLE_ID	Identifier of the link associated with the event	

Mac Old Access Router	MAC_ADDRESS	(Optional) MAC Address of old Access Router	

Reason Code	LINK_DOWN_REASON	
Reason why the link went down.	

7.3.5.3 	When generated
This notification is generated when layer 2 connectivity is lost. Layer 2 connectivity may be lost explicitly in cases where the mobile node may initiate disassociate type procedures. In other cases the mobile node may infer loss of link connectivity due to successive time-outs for acknowledgements of retransmitted packets along with loss of reception of broadcast frames.
7.3.5.4 	Effect on receipt
The MIHF normally passes this link notification to the MIH User(s) which has subscribed for this notification in an MIH_Link_Down event. The MIH User(s) may take different actions on this notification. The handover policy may eliminate this link from list of active links for routing connections and may consider handing over any potential active connections to other more suitable links.
7.3.6 	
7.3.6 	Link_Going_Down.indication
7.3.6.1 	Function
This notification is delivered when a Layer 2 connection is expected (predicted) to go down (Link_Down) within a certain time interval. Link_Going_Down event may be the indication to initiate handover procedures. Different applications may have different requirements with respect to the time interval required to anticipate in advance a Link_Going_Down and make adequate a priori preparation to handover a connection depending on application class. Hence MIH Users such as a L3 mobility protocol may actually configure the time interval in which a Link_Going_Down event may be delivered.
7.3.6.2 	Semantics of service primitive
Link_Going_Down.indication 				(
				LinkIdentifier,
				TimeInterval,
				ConfidenceLevel,
				LinkGoingDownReason,
				UniqueEventIdentifier
				)
Parameters
:
Name	Type	Description	

Link Identifier	LINK_TUPLE_ID	Identifier of the link associated with the event.	

Time Interval	UNSIGNED_INT(2)	
Time Interval (in milliseconds) in which the link is expected to go down. The link connectivity is expected to be available at least for the time specified.	

Confidence Level	PERCENTAGE	
The confidence level (%) for link to go down within the specified time interval	
Link Going Down Reason	LINK_GOING_DOWN_REASON	The reason why the link is going to be down.	

Unique Event Identifier	UNSIGNED_INT(2)	
Used to uniquely identify the event. To be used in case of event rollback	

7.3.6.3 	When generated
A Link_Going_Down event implies that a Link_Down is imminent within a certain time interval. If Link_Down is NOT received within specified time interval then actions due to previous Link_Going_Down may be rejected. 
A 100% confidence would indicate certainty that the link is definitely going down within the specified time interval. For example a BS that may have decided to shut down for administrative reasons may send down a Link_Going_Down trigger with 100% confidence level. Predictions based on changes in link parameters such as signal strength values would have a lower confidence level. Different links would use implementation specific methods to predict future loss in link connectivity.
7.3.6.4 	Effect on receipt
The MIHF receives this event from the link layer. The MIHF then passes this notification to the MIH User(s) which have subscribed for this notification. MIH User(s) may take different actions on this notification. MIH Users may prepare to initiate handovers based on the confidence level reported as part of the event.
7.3.7 	
7.3.7 	Link_Event_Rollback.indication
7.3.7.1 	Function
Link_Event_Rollback is used in conjunction with Link_Going_Down. In case of Link_Going_Down if the link is no longer expected to go down in the specified time interval, then a Link_Event_Rollback message is sent to the Event destination. The destination should disregard or rollback the changes associated with the event identifier in such cases.
7.3.7.2 	Semantics of service primitive
Link_Event_Rollback.indication 				(
				LinkIdentifier,
				UniqueEventIdentifier
				)
Parameters:
Name	Type	Description	

Link Identifier	LINK_TUPLE_ID	Identifier of the link associated with the event	

Unique Event Identifier	UNSIGNED_INT(2)	Used to identify the event which needs to be rolled back	

7.3.7.3 	When generated
This notification is generated when a predictive event expected to occur within a certain time interval is no longer expected to occur before the expiry of the indicated time interval.
7.3.7.4 	Effect on receipt
The MIHF receives this event from the link layer. The MIHF then passes this notification to the MIH User(s) which have subscribed for this notification. The MIH User(s) may reevaluate the link under consideration by retrieving other link quality related parameters. Any handover procedures that may have already been initiated may need to be rescinded.
7.3.8 	
7.3.8 	Link_Detected.indication
7.3.8.1 	Function
Link_Detected indicates that a new type of link has been detected for use.
 This may imply that the mobile node is in the coverage area and may listen to a beacon, or that the mobile node may have received a response to a probe. Link_Detected does not guarantee that the mobile node would be able to establish connectivity with the detected link, but just that the mobile node may attempt to gain connectivity. MIH Users and the MIHF itself may evaluate additional properties of the link before attempting to establish a L2 connection with the link.
7.3.8.2 	Semantics of service primitive
Link_Detected.indication 			(
			LinkIdentifier,
			MIHCapability
			)
Parameters
Name	Type	Description	

Link Identifier	LINK_TUPLE_ID	Identifier of the link associated with the event	
MIH Capability	LINK_MIH_CAPABILITY_FLAG	
Used to indicate which MIH capabilities are supported on this link.	
:
7.3.8.3 	When generated
This notification is generated when a new link is detected. The detection may be based on a beacon or response to a probe.
7.3.8.4 	Effect on receipt
The MIHF receives this event from the link layer. The MIHF then passes this notification to the MIH User(s) which have subscribed for this notification. The MIH User(s), including the MIHF itself, may discover additional properties of the link before selecting it for establishing connectivity.
7.3.9 	Link_Parameters_Report.indication
7.3.9.1 	Function
Link_Parameters_Report indicates changes in link parameters that have crossed specified threshold levels. This may include link layer parameters such as Speed of the link, QoS, SNR or BER. The threshold level for each such parameter may have to be configured through a separate command to the link layer.
7.3.9.2 	Semantics of service primitive
Link_Parameters_Report.indication	(
				LinkIdentifier,
				LinkParametersReportList
				)
Parameters
Name	Type	Description	

Link Identifier	LINK_TUPLE_ID	Identifier of the link associated with the event	
Link Parameters Report List	
LIST(LINK_PARAM_REPORT)	A list of Link Parameter Report.	
:
The set of link layer parameters that could trigger this event is specified in  7.3.3.
7.3.9.3 	When generated
This notification is generated either at a predefined regular interval determined by a user configurable timer or when a specified parameter of the currently active interface crosses a configured threshold.
7.3.9.4 	Effect on receipt
The MIHF receives this event from the link layer. The MIHF then passes this notification to the MIH User(s) which have subscribed for this notification. The MIH User(s) may take different actions on this notification. If parameters related to link quality cross a certain threshold then that link may need to be evaluated for handing over current connections. The MIHF may collectively evaluate different parameters and give appropriate indications to higher layers regarding suitability of different links.
7.3.10 	
7.3.10 	Link_PDU_Transmit_Status.indication
7.3.10.1 	Function
Link_PDU_Transmit_Status indicates the transmission status of a higher layer PDU. A success status indicates that a higher layer PDU has been successfully delivered from the ARQ module of the link layer in the current node to the ARQ module in the link layer in the peer node. A higher layer intermediate buffer management entity could use this indication to flush higher layer packets stored in any intermediate buffers. A failure status indicates that at least one segment belonging to a higher layer PDU was not delivered successfully from the ARQ module of the link layer in the current node to the ARQ module in the link layer in the peer node.
7.3.10.2 	Semantics of service primitive
Link_PDU_Transmit_Status.indication 					(
					LinkIdentifier,
					PacketIdentifier,
					TransmissionStatus
					)
Parameters
:
Name	Type	Description	

Link Identifier	LINK_TUPLE_ID	Identifier of the link associated with the event	

Packet Identifier	
UNSIGNED_INT(2)	
Identifier for higher layer PDU on which this notification is generated.	
Transmission Status	Boolean	Status of the transmitted packet.
True: Success
False: Failure	

7.3.10.3 	When generated
A success notification is generated when a higher layer PDU is successfully transmitted over the link. A failure notification is generated when any link layer segment corresponding to a higher layer PDU was not transmitted successfully.
7.3.10.4 	Effect on receipt
The MIHF receives this event from the link layer. The MIHF then passes this notification to the MIH User(s) which have subscribed for this notification. The MIH User(s) may take different actions on this notification. A higher layer intermediate buffer management entity in MIH could use the success indication to flush higher layer packets stored in any intermediate buffers and a failure indication to retransmit higher layer packets stored in any intermediate buffers, especially if there are changes in the access network during handovers.
7.3.11 	Link_Handover_Imminent.indication
7.3.11.1 	Function 
Link_Handover_Imminent is generated when a native link layer handover or switching decision has been made and its execution is imminent (as opposed to Link_Going_Down which only indicates that a link is losing connectivity due to a change in a certain link condition such as signal strength, but does not guarantee that an autonomous link switch-over has been decided by the link layer). It contains information about the new point of attachment of the mobile node (the LinkIdentifier parameter contains information about the new PoA). It also contains information about any application specific data that might be useful for the application running on the mobile node. Link_Handover_Imminent may be used by MIH Users (e.g., transport) to initiate handover specific adaptation and as an enabler for initiating effective make-before-break handovers thereby reducing packet loss due to link layer handovers. This is a link layer event that exists for intra-technology handovers defined in many media types (e.g., cellular, IEEE 802.16e). 
7.3.11.2 	Semantics of service primitive
Link_Handover_Imminent.indication 					(
					LinkIdentifier,
					MacAccessRouter
					)
Parameters
:
Name	Type	Description	

Link Identifier	LINK_TUPLE_ID	Identifier of the link associated with the event	

Mac Access Router	MAC_ADDRESS 	
(Optional) MAC Address of new Access Router	

7.3.11.3 	When generated 
Depending on whether it is the Mobile node or the Network, it is generated when a native link layer handover or switching decision has been made and its execution is imminent.
7.3.11.4 	Effect on receipt 
The MIHF receives this event from the link layer. The MIHF then passes this notification to the MIH User(s) which have subscribed for this notification. The MIH User(s) may take necessary actions to minimize the effect of the pending native link layer handover or switching on user data transfer. For example, to cover the handover period (when packets cannot be transferred), the network may proactively start sending the additional data as soon as it has received indication about the event and should expect a request from the MN specifying how much data it needs to cover the handover period. This event may also be used as an indication to start buffering packets.
7.3.12 	
7.3.12 	Link_Handover_Complete.indication
7.3.12.1 	Function
Link_Handover_Complete event is generated whenever a native link layer handover/switching has just been completed (as opposed to Link_Up which only indicates that a link has been brought up for L2 connectivity, but does not indicate that a native link handover/switch-over has just been completed by the link layer). Notifying the upper layer of this event may improve transport, session and application layer responsiveness to autonomous link changes. They may better adapt their data flows by resuming flows upon receiving this indication. The upper layer may also use this event to check whether its IP configuration needs to be updated. This is a link layer event that exists for intra-technology handovers defined in many media types (e.g., cellular, IEEE 802.16e). This event is applicable for the mobile node only and is valid only for intra-technology handovers. 
7.3.12.2 	Semantics of service primitive
Link_Handover_Complete.indication 					(
					LinkIdentifier,
					MacAccessRouter
					)
Parameters
:
Name	Type	Description	

Link Identifier	LINK_TUPLE_ID	Identifier of the link associated with the event	

Mac Access Router	MAC_ADDRESS 	
(Optional) MAC Address of new Access Router	

7.3.12.3 	When generated
This is generated whenever a L2 link layer handover or switching has just been completed.
7.3.12.4 	Effect on receipt 
The MIHF receives this event from the link layer. The MIHF then passes this notification to the MIH User(s) which have subscribed for this notification. Upon reception of this event, an upper layer (e.g., transport) may stop any handover adaptation that it has engaged to cope with the just completed native link layer handover/switching and resume normal data transfer. This event may also be used as an indication that a re-verification of the IP parameter should be considered.
7.3.13 	
7.3.13 	
7.3.13 	Link_Capability_Discover
7.3.13.1 	
7.3.13.1 	
7.3.13.1 	Link_Capability_Discover.request
7.3.13.1.1 	Function
This primitive is used by the MIHF to query and discover the list of supported link layer events and link layer commands.
7.3.13.1.2 	Semantics of service primitive
No primitive parameters exist for this primitive.
Link_Capability_Discover.request
			 	(				
				)
7.3.13.1.3 	
7.3.13.1.3 	When generated
This primitive is generated by the MIHF when it needs to receive link layer event notifications and learn about which link layer commands the low layer can support.
7.3.13.1.4 	Effect on receipt
The recipient responds immediately with Link_Capability_Discover.confirm primitive.
7.3.13.2 	
7.3.13.2 	Link_Capability_Discover.confirm
7.3.13.2.1 	Function
This primitive returns the result of the query to discover link layer capability.
7.3.13.2.2 	Semantics of service primitive
Link_Capability_Discover.confirm
			 	(				
				SupportedLinkEventList,
				SupportedLinkCommandList,
				Status
				)
Parameters:
Name	Type	Description	
Supported Link Event List	LINK_EVENT_LIST	List of link layer events supported by the link layer.	
Supported Link Command List	LINK_COMMAND_LIST	List of link layer commands supported by the link layer.	
Status			STATUS	Status of operation. Code 3 (Authorization Failure) is not applicable.	

7.3.13.2.3 	When generated
This primitive is generated in response to a Link_Capability_Discover.request primitive.
7.3.13.2.4 	Effect on receipt
The recipient may examine the returned event and command list and learn about link layer capability. However, if Status does not indicate “Success”, the recipient shall ignore any other returned values and, instead, shall perform appropriate error handling.
7.3.14 	Link_Get_Parameters
7.3.14.1 	Link_Get_Parameters.request
7.3.14.1.1 	Function
This primitive is used by the MIHF to obtain the current value of a set of link parameters of a specific link.
7.3.14.1.2 	Semantics of service primitive
Link_Get_Parameters.request 				(
				LinkParametersRequest
				)
Parameter:
Name	Type	Description	
Link Parameters Request	LIST(LINK_PARAM_TYPE)	A list of link parameters for which status is requested. 	

7.3.14.1.3 	When generated
This primitive is generated by the MIHF to obtain the current value of a set of link parameters from a link.
7.3.14.1.4 	Effect on receipt
The recipient link shall respond with Link_Get_Parameters.confirm primitive.
7.3.14.2 	Link_Get_Parameters.confirm
7.3.14.2.1 	Function
This primitive is sent in response to the Link_Get_Parameters.request primitive. This primitive provides current value of the requested link parameters. (Note, how the value is measured or calculated by the link is not specified by this standard).
7.3.14.2.2 	Semantics of service primitive
Link_Get_Parameters.confirm 				(
				LinkParametersStatusList,
				Status
				)
Parameters:
Name	Type	Description	
Link Parameters Status List	LIST(LINK_PARAM)	A list of measurable link parameters and their current value.	
Status			STATUS	Status of operation. Code 3 (Authorization Failure) is not applicable.	

7.3.14.2.3 	When generated
This primitive is generated in response to the Link_Get_Parameters.request operation.
7.3.14.2.4 	Effect on receipt
The recipient may pass the link parameter values received to the MIH Users. However, if Status does not indicate “Success”, the recipient shall ignore any other returned values and, instead, shall perform appropriate error handling.
7.3.15 	Link_Action
7.3.15.1 	Link_Action.request
7.3.15.1.1 	Function
This primitive is used by the MIHF to request actions on a link layer connection to enable optimal handling of link layer resources for the purpose of handovers. The link layer connection can be ordered, e.g. to shut down, to remain active, to perform a scan, or to come up active and remain in stand-by mode. The command execution delay time can also be specified for cases where the link layer technology under consideration supports the action.
7.3.15.1.2 	Semantics of Service Primitive
Link_Action.request 			(
			 LinkIdentifier
			 LinkAction
			 ExecutionDelay
			)
Parameters:
Name	Type	Description	
Link Identifier	LINK_TUPLE_ID	Identifier of present link	
Link Actions	LINK_ACTIONS	Specifies the suggested action on link.	
Execution Delay	UNSIGNED_INT(2)	Time (in ms) elapsed before action needs to be taken, if ExecutionDelay is 0 then the action is expected to be taken on receipt of this command.	

7.3.15.1.3 	When generated
The MIHF generates this primitive upon request from the MIH User to perform an action on a pre-defined link layer connection.
7.3.15.1.4 	Effect on receipt
Upon receipt of this primitive, the link layer technology supporting the current link layer connections performs the action specified by the Link Actions parameter in accordance with the procedures specified by the relevant standards organization and at the time specified by the Execution Delay parameter.
7.3.15.2 	Link_Action.confirm
7.3.15.2.1 	Function
This primitive is used by link layer technologies to provide an indication of the result of actions executed on the current link layer connection.
7.3.15.2.2 	Semantics of Service Primitive
Link_Action.confirm 			(
			ScanResponseSet,
			LinkActionResult
			Status
			)
Parameters:
Name	Type	Description	
Scan Response Sets	LIST	(Optional) A list of discovered links and related information.	
Link Action Result	LINK_AC_RESULT_CODE	Specifies the succeeded link actions.	
Status	STATUS	Status of operation. Code 3 (Authorization Failure) is not applicable.	

7.3.15.2.3 	When generated
The link layer technology generates this primitive to communicate the result of the actions executed on the link layer connection.
7.3.15.2.4 	Effect on receipt
Upon receipt of this primitive, the MIHF determines the relevant MIH command that needs to be used to provide an indication or confirmation to the MIH User of the actions performed on the current link layer connection. If a Scan action was issued by the associated Link_Action.request, the optional ScanResponseSet field shall be included in the Link_Action.confirm response.
7.4 	MIH_SAP primitives
The primitives defined as part of MIH_SAP are described in the following subclauses.
7.4.1 	MIH_Capability_Discover
7.4.1.1 	MIH_Capability_Discover.request
7.4.1.1.1 	Function
This primitive is used by an MIH User to discover the capabilities of the local MIHF or a remote MIHF. When invoking this primitive to discover the capabilities of a remote MIHF, the MIH User can optionally piggyback the capability information of its local MIHF so that the two MIHFs can mutually discover each other’s capabilities with a single invocation of this primitive.
7.4.1.1.2 	Semantics of service primitive
MIH_Capability_Discover.request
			 	(
				DestinationIdentifier,
				SupportedMihEventList,
				SupportedMihCommandList,
				SupportedIsQueryTypeList,
				SupportedTransportList
				)
Parameters:

Name	
Type	
Description	
Destination Identifier	MIHF_ID	This identifies the local MIHF or a remote MIHF which will be the destination of this request. 	
Supported MIH Event List	MIH_EVENT_LIST	(Optional) List of supported events on MIHF.	
Supported MIH Command List	MIH_COMMAND_LIST	(Optional) List of supported commands on MIHF.	
Supported IS Query Type List	MIH_IS_QUERY_TYPE_LIST	(Optional) List of supported MIIS query types.	
Supported Transport List 	MIH_TRANSPORT_LIST	(Optional) List of supported transport types. 	

7.4.1.1.3 	
7.4.1.1.3 	When generated
This primitive is generated by an MIH User to discover the capabilities of the local MIHF or a remote MIHF. In the case of remote discovery, this primitive may contain the SupportedMihEventList, SupportedMihCommandList, SupportedIsQueryTypeList, and SupportedTransportList parameters to enable mutual discovery of each other’s capabilities.
7.4.1.1.4 	Effect on receipt
If the destination of the request is the local MIHF itself, the local MIHF shall respond with MIH_Capability_Discover.confirm. If the destination of the request is a remote MIHF, the local MIHF shall generate and send a corresponding MIH_Capability_Discover request message to the remote MIHF if it does not have the capability information of the remote MIHF.
7.4.1.2 	MIH_Capability_Discover.indication
7.4.1.2.1 	Function 
This primitive is used by an MIHF to notify an MIH User on the receipt of an MIH_Capability_Discover request message from a peer MIHF.
7.4.1.2.2 	Semantics of Service primitive 
MIH_Capability_Discover.indication (
				SourceIdentifier,
				SupportedMihEventList,
				SupportedMihCommandList,
				SupportedIsQueryTypeList,
				SupportedTransportList
				)
Parameters:

Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which is a remote MIHF.	
Supported MIH Event List	MIH_EVENT_LIST	(Optional) List of supported events on MIHF. 	
Supported MIH Command List	MIH_COMMAND_LIST	(Optional) List of supported commands on MIHF.	
Supported IS Query Type List	MIH_IS_QUERY_TYPE_LIST	(Optional) List of supported MIIS query types. 	
Supported Transport List 	MIH_TRANSPORT_LIST	(Optional) List of supported transport types. 	

7.4.1.2.3 	When generated 
This primitive is used by an MIHF to notify an MIH User when an MIH_Capability_Discover request message is received.
7.4.1.2.4 	Effect on receipt
The MIH User may respond with an MIH_Capability_Discover.response primitive.
7.4.1.3 	MIH_Capability_Discover.response
This primitive is used by an MIH User to convey the supported MIH capabilities to the MIH User which invoked the MIH_Capability_Discover request.
7.4.1.3.1 	Semantics of Service primitive 
MIH_Capability_Discover.response(
				DestinationIdentifier,
				SupportedMihEventList,
				SupportedMihCommandList,
				SupportedIsQueryTypeList,
				SupportedTransportList,
				Status
				) 
Parameters:

Name	Type	Description	
Destination Identifier	MIHF_ID	This identifies the remote MIHF which will be the destination of this response. 	
Supported MIH Event List	MIH_EVENT_LIST	List of supported events on MIHF. 	
Supported MIH Command List	MIH_COMMAND_LIST	List of supported commands on MIHF. 	
Supported IS Query Type List	MIH_IS_QUERY_TYPE_LIST	(Optional) List of supported MIIS query types.	
Supported Transport List	MIH_TRANSPORT_LIST	(Optional) List of supported transport types. 	
Status			STATUS	Status of operation.	

[Editor’s note: Contribution #55 should SupportedLinks, LinkMACs, MBBHandoverSupport be included in .response message also?]
7.4.1.3.2 	When generated 
This primitive is generated by an MIH User as a response to a received MIH_Capability_Discover.indication primitive.
7.4.1.3.3 	Effect on receipt
Upon receiving this primitive, the MIHF generates and sends the corresponding MIH_Capability_Discover response message to the destination MIHF.
7.4.1.4 	MIH_Capability_Discover.confirm
7.4.1.4.1 	Function
This primitive is used by the MIHF to convey the supported MIH capabilities about Event Service, Command Service, and Information Service to the MIH User which invoked the MIH_Capability_Discover.request.
7.4.1.4.2 	Semantics of service primitive
MIH_Capability_Discover.confirm
			 	(
				
Source
Identifier,
				SupportedLinks,
				LinkMACs,
				SupportedMihEventList,
				SupportedMihCommandList,
				SupportedIsQueryTypeList,
				SupportedTransportList,
				MBBHandoverSupport,
				Status
				)

Parameters:

Name	
Type	
Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which can be either the local MIHF or a remote MIHF.	
Supported Links	LIST(NETWORK_TYPE)	A list of supported network types.	
Link MACs	LIST(NETWORK_TYPE_ANDMAC)	A list of network type and MAC address pair.	
Supported MIH Event List	LIST(NETWORK_TYPE_AND_EVENTS)	(Optional) List of network type and supported events pair.	
Supported MIH Command List	MIH_COMMAND_LIST	List of supported commands on MIHF.	
Supported IS Query Type List	MIH_IS_QUERY_TYPE_LIST	(Optional) List of supported MIIS query types. 	
Supported Transport List	MIH_TRANSPORT_LIST	(Optional) List of supported transport types.	
MBB Handover Support	LIST(MBB_HANDOVER_SUPPORT)	This is used to indicate if a make before break handover is supported. It is assumed that a break before make handover is supported by default.	
Status			STATUS	Status of operation.	

7.4.1.4.3 	
7.4.1.4.3 	When generated
This primitive is invoked by a local MIHF to convey the results of a previous MIH_Capability_Discover.request primitive from an MIH User.
7.4.1.4.4 	Effect on receipt
Upon reception of this primitive the receiving entity becomes aware of the supported MIH capabilities. However, if Status does not indicate “Success”, the recipient shall ignore any other returned values and, instead, shall perform appropriate error handling.
7.4.2 	MIH_Register 
7.4.2.1 	MIH_Register.request
7.4.2.1.1 	Function
This primitive is used by an MIH User to register the local MIHF with remote MIHF.
7.4.2.1.2 	Semantics of service primitive
MIH_Register.request			(
			DestinationIdentifier, 
			RequestCode
			)
Parameters:
Name	Type	Description	
Destination Identifier	MIHF_ID	This identifies a remote MIHF which will be the destination of this request. 	
Request Code	REG_REQUEST_CODE	Registration request code

[Editor’s note: Re-registration scope to be defined.]	

7.4.2.1.3 	When generated
This primitive is invoked by the MIH User when it needs to register the local MIHF with a remote MIHF.
7.4.2.1.4 	Effect on receipt
On receipt, the local MIHF shall send an MIH_Register request message to the destination MIHF.
7.4.2.2 	MIH_Register.indication
7.4.2.2.1 	Function
This primitive is used by an MIHF to notify an MIH User that an MIH_Register request message has been received.
7.4.2.2.2 	Semantics of service primitive
MIH_Register.indication			(
			SourceIdentifier, 
			RequestCode
			)
Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which is a remote MIHF.	
Request Code	REG_REQUEST_CODE	Registration request code.

[Editor’s note: Re-registration scope to be defined.]	

7.4.2.2.3 	When generated
This primitive is generated by the remote MIHF when an MIH_Register request message is received.
7.4.2.2.4 	Effect on receipt
The remote MIH User will perform necessary actions to process the registration request and respond with an MIH_Register.response.
7.4.2.3 	MIH_Register.response
7.4.2.3.1 	Function
This primitive is used by an MIH User to send the processing status of a received registration request.
7.4.2.3.2 	Semantics of service primitive
MIH_Register.response			(
			Destination Identifier,
			ValidTimeInterval,
			Status
			)
Parameters:
Name	Type	Description	
Destination Identifier	MIHF ID	This identifies a remote MIHF which will be the destination of this response. 	
Valid Time Interval	UNSIGNED_INT(4)	Time interval in seconds during which the registration is valid.
When the MIH_Register.response does not indicates success, this value shall be set to 0.	
Status			STATUS	Status of operation.	

7.4.2.3.3 	When generated
This primitive is invoked by the MIH User to report back the result after completing the processing of a registration request.
7.4.2.3.4 	Effect on receipt
Upon receipt, the local MIHF shall send an MIH_Register response message to the destination MIHF.
7.4.2.4 	MIH_Register.confirm
7.4.2.4.1 	Function
This primitive is used by the local MIHF to convey the result of a registration request to an MIH User.
7.4.2.4.2 	Semantics of service primitive
MIH_Register.confirm			(
			SourceIdentifier,
			ValidTimeInterval,
			Status
			)
Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which is a remote MIHF.	
Valid Time Interval	UNSIGNED_INT(4)	Time interval in seconds during which the registration is valid.	
Status			STATUS	Status of operation.	

7.4.2.4.3 	When generated
This primitive is used by an MIHF to notify an MIH User the result of an MIH registration request.
7.4.2.4.4 	Effect on receipt
Upon receipt, the MIH User can determine the result of the registration request.
7.4.3 	MIH_DeRegister
7.4.3.1 	MIH_DeRegister.request
7.4.3.1.1 	Function
This primitive is used by an MIH User to deregister the local MIHF with peer MIHF.
7.4.3.1.2 	Semantics of service primitive
MIH_DeRegister.request			(
			DestinationIdentifier 
			)
Parameter:
Name	Type	Description	
Destination Identifier	MIHF_ID	This identifies a remote MIHF which will be the destination of this request. 	

7.4.3.1.3 	When generated
This primitive is invoked by the MIH User when it needs to terminate an existing MIH registration with a remote MIHF.
7.4.3.1.4 	Effect on receipt
Upon receipt, the local MIHF shall generate and send an MIH_DeRegister request message to the destination MIHF.
7.4.3.2 	MIH_DeRegister.indication
7.4.3.2.1 	Function
This primitive is used by an MIHF to notify an MIH User that an MIH_DeRegister request message has been received.
7.4.3.2.2 	Semantics of service primitive
MIH_DeRegister.indication			(
			SourceIdentifier 
			)
Parameter:
Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which is a remote MIHF.	

7.4.3.2.3 	When generated
This primitive is generated by an MIHF when an MIH_DeRegister request message is received.
7.4.3.2.4 	Effect on receipt
The MIH User will perform necessary actions to process the deregistration request and respond with an MIH_DeRegister.response.
7.4.3.3 	MIH_DeRegister.response 
7.4.3.3.1 	Function
This primitive is invoked by a remote MIH User to respond the processing status of a received deregistration request.
7.4.3.3.2 	Semantics of service primitive
MIH_DeRegister.response			(
			DestinationIdentifier,
			Status
			)
Parameters:
Name	Type	Description	
Destination Identifier	MIHF_ID	This identifies a remote MIHF which will be the destination of this response. 	
Status			STATUS	Status of operation. Code 2 (Reject) shall not be used.	

7.4.3.3.3 	When generated
This primitive is invoked by the MIH User to report back the result after completing the processing of a deregistration request from a remote MIH User.
7.4.3.3.4 	Effect on receipt
Upon receipt, the local MIHF shall send an MIH_DeRegister response message to the destination MIHF.
7.4.3.4 	MIH_DeRegister.confirm
7.4.3.4.1 	Function
This primitive is used by the local MIHF to convey the result of a deregistration request to the local MIH User.
7.4.3.4.2 	Semantics of service primitive
MIH_DeRegister.confirm			(
			SourceIdentifier,
			Status
			)
Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which is a remote MIHF.	
Status			STATUS	Status of operation. Code 2 (Rejected) shall not be used.	

7.4.3.4.3 	When generated
This primitive is used by an MIHF to notify the local MIH User the status of MIH deregistration request.
7.4.3.4.4 	Effect on receipt
Upon receipt, the MIH User can determine the status of the deregistration request.
7.4.4 	MIH_Event_Subscribe
7.4.4.1 	MIH_Event_Subscribe.request
7.4.4.1.1 	Function
This primitive is used by an MIH User (the subscriber) to subscribe an interest in one or more MIH event types from the local or a remote MIHF. 
7.4.4.1.2 	Semantics of service primitive
MIH_Event_Subscribe.request			 	(
				DestinationIdentifier,
				LinkIdentifier,
				RequestedMihEventList
				)

Parameters:

Name	Type	Description	
Destination Identifier	MIHF_ID	This identifies the local MIHF or a remote MIHF which will be the destination of this request. 	
Link Identifier	LINK_TUPLE_ID	Identifier of the link for event subscription. For local event subscription, PoA MAC Address in the Link Identifier need not be present if the link type lacks such a value. 	
Requested MIH Event List	MIH_EVENT_LIST	List of MIH events that the endpoint would like to receive indications for, from the Event Source.	

7.4.4.1.3 	When generated
This primitive is invoked by an MIH User when it wants to receive indications on a set of specific MIH events from the local MIHF or a remote MIHF.
7.4.4.1.4 	Effect on receipt
If the destination of the request is the local MIHF itself, the local MIHF shall respond immediately with an MIH_Event_Subscribe.confirm primitive. If the destination of the request is a remote MIHF, the local MIHF shall generate and send an MIH_Event_Subscribe request message to the remote MIHF.
7.4.4.2 	MIH_Event_Subscribe.confirm
7.4.4.2.1 	Function
This primitive returns the result of an MIH event subscription request.
7.4.4.2.2 	Semantics of service primitive
MIH_Event_Subscribe.confirm			 	(
				SourceIdentifier
				LinkIdentifier,
				ResponseMihEventList,
				Status
				)

Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which can be either the local MIHF or a remote MIHF.	
Link Identifier	LINK_TUPLE_ID	Identifier of the link for event subscription.	
Response MIH Event List	MIH_EVENT_LIST	List of MIH events.	
Status			STATUS	Status of operation.	

7.4.4.2.3 	When generated
This primitive is generated by the local MIHF at the completion of processing an MIH_Event_Subscribe.request primitive from a local MIH User or in response to the receiving of an MIH_Event_Subscribe response message from a peer MIHF.
7.4.4.2.4 	Effect on receipt
The recipient MIH User may examine the returned event list and learn about the subscription status of different events. However, if Status does not indicate “Success”, the recipient shall ignore any other returned values and, instead, shall perform appropriate error handling.
7.4.5 	MIH_Event_Unsubscribe
7.4.5.1 	MIH_Event_Unsubscribe.request
7.4.5.1.1 	Function
This primitive is used by an MIH User (the subscriber) to unsubscribe from a set of previous subscribed MIH events.
7.4.5.1.2 	Semantics of service primitive
MIH_Event_Unsubscribe.request			 	(
				DestinationIdentifier,
				LinkIdentifier,
				RequestedMihEventList
				)

Parameters:

Name	Type	Description	
Destination Identifier	MIHF_ID	This identifies the local MIHF or a remote MIHF which will be the destination of this request. 	
Link Identifier	LINK_TUPLE_ID	Identifier of the link for event unsubscription. For local event unsubscription, PoA MAC Address in the Link Identifier need not be present if the link type lacks such a value.	
Requested MIH Event List	MIH_EVENT_LIST	List of MIH events for which indications need to be deregistered from the Event Source.	

7.4.5.1.3 	When generated
This primitive is invoked by an MIH User (subscriber) that is seeking to unsubscribe from an already subscribed set of events from the local MIHF or a remote MIHF.
7.4.5.1.4 	Effect on receipt
If the destination of the request is the local MIHF itself, the local MIHF shall respond immediately with MIH_Event_Unsubscribe.confirm primitive. If the destination of the request is a remote MIHF, the local MIHF shall generate and send an MIH_Event_Unsubscribe request message to the remote MIHF.
7.4.5.2 	MIH_Event_Unsubscribe.confirm
7.4.5.2.1 	Function
This primitive returns the result of an MIH event unsubscription request.
7.4.5.2.2 	Semantics of service primitive
MIH_Event_Unsubscribe.confirm			 	(
				SourceIdentifier,
				LinkIdentifier,
				ResponseMihEventList,
				Status
				)

Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which can be either the local MIHF or a remote MIHF.	
Link Identifier	LINK_TUPLE_ID	Identifier of the link for event unsubscription.	
Response MIH Event List	MIH_EVENT_LIST	List of MIH events along with their unsubscription status.	
Status			STATUS	Status of operation.	

7.4.5.2.3 	When generated
This primitive is generated by the local MIHF at the completion of processing an MIH_Event_Unsubscribe.request primitive from a local MIH User or in response to the receiving of an MIH_Event_Unsubscribe response message from a peer MIHF.
7.4.5.2.4 	Effect on receipt
The recipient MIH User may examine the returned event list and learn about the unsubscription status of different events. However, if Status does not indicate “Success”, the recipient shall ignore any other returned values and, instead, shall perform appropriate error handling.
7.4.6 	MIH_Link_Up
7.4.6.1 	MIH_Link_Up.indication
7.4.6.1.1 	Function
The MIH_Link_Up.indication is sent to local MIHF users to notify them of a local event, or is the result of the receipt of an MIH_Link_Up indication message to indicate to the remote MIHF users, who have subscribed to this remote event.
7.4.6.1.2 	Semantics of the service primitive
MIH_Link_Up.indication 			(
			SourceIdentifier,
			LinkIdentifier,
			MacOldAccessRouter,
			MacNewAccessRouter,
			IPRenewalFlag,
			Mobility Management Support
			)
Parameters:

Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which can be either the local MIHF or a remote MIHF.	

Link Identifier	LINK_TUPLE_ID	Identifier of the link associated with the event	

MAC Old Access Router	
MAC_ADDRESS	
(Optional) MAC Address of old Access Router	

MAC New Access Router	
MAC_ADDRESS	(Optional) MAC Address of new Access Router	

IP Renewal Flag	IP_RENEWAL_FLAG	
(Optional) 
Indicates whether the MN shall change IP Address in the new PoA

Mobility Management Support	IP_MOBILITY_MGMT	
(Optional) 
Indicates the type of Mobility Management Protocol supported by the new PoA 	

7.4.6.1.3 	When generated
The MIH_Link_Up.indication is sent to local MIHF users to notify them of a local event (i.e., Link_Up.indication), or is the result of the receipt of an MIH_Link_Up indication message to indicate to the remote MIHF users, who have subscribed to this remote event, that a remote link up event occurred.
7.4.6.1.4 	Effect on receipt
MIH User dependant.
7.4.7 	MIH_Link_Down
7.4.7.1 	MIH_Link_Down.indication
7.4.7.1.1 	Function
The MIH_Link_Down.indication is sent to local MIHF users to notify them of a local event, or is the result of the receipt of an MIH_Link_Down indication message to indicate to the remote MIHF users, who have subscribed to this remote event.
7.4.7.1.2 	Semantics of the service primitive
MIH_Link_Down.indication 			(
			SourceIdentifier,
			LinkIdentifier,
			MacOldAccessRouter,
			ReasonCode
			)
Parameters
:
Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which can be either the local MIHF or a remote MIHF.	

Link Identifier	LINK_TUPLE_ID	Identifier of the link associated with the event	

Mac Old Access Router	
MAC_ADDRESS	
(Optional) MAC Address of old Access Router	

Reason Code	LINK_DOWN_REASON	
Reason why the link went down.	

7.4.7.1.3 	When generated
The MIH_Link_Down.indication is sent to local MIHF users to notify them of a local event (i.e., Link_Down.indication), or is the result of the receipt of an MIH_Link_Down indication message to indicate to the remote MIHF users, who have subscribed to this remote event, that a remote link_down event occurred.
7.4.7.1.4 	Effect on receipt
MIH User dependant.
7.4.8 	MIH_Link_Going_Down
7.4.8.1 	MIH_Link_Going_Down.indication
7.4.8.1.1 	Function
The MIH_Link_Going_Down.indication is sent to local MIHF users to notify them of a local event, or is the result of the receipt of an MIH_Link_Going_Down indication message to indicate to the remote MIHF users, who have subscribed to this remote event.
7.4.8.1.2 	Semantics of the service primitive
MIH_Link_Going_Down.indication 				(
				SourceIdentifier,
				LinkIdentifier,
				TimeInterval,
				ConfidenceLevel,
				LinkGoingDownReason,
				UniqueEventIdentifier
				)
Parameters
:
Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which can be either the local MIHF or a remote MIHF.	

Link Identifier	LINK_TUPLE_ID	Identifier of the link associated with the event.	

Time Interval	UNSIGNED_INT(2)	
Time Interval (in milliseconds) in which the link is expected to go down. The link connectivity is expected to be available at least for the time specified.	

Confidence Level	PERCENTAGE	
The confidence level (%) for link to go down within the specified time interval	
Link Going Down Reason	LINK_GOING_DOWN_REASON	The reason why the link is going to be down.	

Unique Event Identifier	UNSIGNED_INT(2)	
Used to uniquely identify the event. To be used in case of event rollback	

7.4.8.1.3 	When generated
The MIH_Link_Going_Down.indication is sent to local MIHF users to notify them of a local event (i.e., Link_Going_Down.indication), or is the result of the receipt of an MIH_Link_Going_Down indication message to indicate to the remote MIHF users, who have subscribed to this remote event, that a remote link_going_down event occurred.
7.4.8.1.4 	Effect on receipt
MIH User dependant.
7.4.9 	MIH_Link_Detected
7.4.9.1 	MIH_Link_Detected.indication
7.4.9.1.1 	Function
The MIH_Link_Detected.indication is sent to local MIHF users to notify them of a local event, or is the result of the receipt of an MIH_Link_Detected indication message to indicate to the remote MIHF users, who have subscribed to this remote event.
7.4.9.1.2 	Semantics of the service primitive
MIH_Link_Detected.indication 			(
			SourceIdentifier,
			LinkIdentifier,
			MIHCapability
			)
Parameters
Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which can be either the local MIHF or a remote MIHF.	

Link Identifier	LINK_TUPLE_ID	Identifier of the link associated with the event	
MIH Capability	LINK_MIH_CAPABILITY_FLAG	
Used to indicate which MIH capabilities are supported on this link.	
:
7.4.9.1.3 	When generated
The MIH_Link_Detected.indication is sent to local MIHF users to notify them of a local event (i.e., Link_Detected.indication), or is the result of the receipt of an MIH_Link_Detected indication message to indicate to the remote MIHF users, who have subscribed to this remote event, that a remote link_detected event occurred.
7.4.9.1.4 	Effect on receipt
MIH User dependant.
7.4.10 	MIH_Link_Parameters_Report
7.4.10.1 	MIH_Link_Parameters_Report.indication
7.4.10.1.1 	Function
MIH_Link_Parameters_Report indication is sent by the local MIHF to a local MIH User to report the status of a set of parameters of a local or remote link. 
The event may be local or remote.
7.4.10.1.2 	Semantics of service primitive
MIH_Link_Parameters_Report.indication 					(
					SourceIdentifier,
					LinkIdentifier,
					LinkParametersStatusList
					)
Parameters
Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which can be either the local MIHF or a remote MIHF.	

Link Identifier	LINK_TUPLE_ID	Identifier of the link associated with the event	
Link Parameters Status List	LIST(LINK_PARAM_REPORT)	A list of Link Parameter Status.	
:

7.4.10.1.3 	When generated
This notification is generated by the local MIHF either:
—		at a predefined regular interval determined by a user configurable timer;
—		when a specified parameter of a currently active local interface crosses a configured threshold. In such a case, the local MIHF mostly likely will first receive a Link_Parameters_Report.indication from the local link layer; or
—		when an MIH_Link_Parameter_Report indication message is received from a remote MIHF.
7.4.10.1.4 	Effect on receipt
Upper layer entities may take different actions upon receipt of this indication. For example, a mobility management entity locally or remotely located from the event origination link may take these events into account in its decision algorithm.
7.4.11 	MIH_Link_Event_Rollback
7.4.11.1 	MIH_Link_Event_Rollback.indication
7.4.11.1.1 	Function
The MIH_Link_Event_Rollback.indication is sent to local MIHF users to notify them of a local event.
7.4.11.1.2 	Semantics of the service primitive
MIH_Link_Event_Rollback.indication 				(
				SourceIdentifier,
				LinkIdentifier,
				UniqueEventIdentifier
				)
Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which can be either the local MIHF or a remote MIHF.	

Link Identifier	LINK_TUPLE_ID	Identifier of the link associated with the event.	

Unique Event Identifier	UNSIGNED_INT(2)	Used to identify the event which needs to be rolled back.	

7.4.11.1.3 	When generated
The MIH_Link_Event_Rollback.indication is sent to local MIHF users to notify them of a local event (i.e., Link_Event_Rollback.indication), or is the result of the receipt of an MIH_Link_Event_Rollback indication message to indicate to the remote MIHF users, who have subscribed to this remote event, that a remote link_event_rollback event occurred.
7.4.11.1.4 	Effect on receipt
MIH User dependant.
7.4.12 	MIH_Link_PDU_Transmit_Status
7.4.12.1 	MIH_Link_PDU_Transmit_Status.indication
7.4.12.1.1 	Function
The MIH_Link_PDU_Transmit_Status.indication is sent to local MIHF users to notify them of a local event.
7.4.12.1.2 	Semantics of the service primitive
MIH_Link_PDU_Transmit_Status.indication	(
				SourceIdentifier,
				LinkIdentifier,
				PacketIdentifier,
				TransmissionStatus
				)
Parameters
Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the local MIHF where this event occurred.	

Link Identifier	LINK_TUPLE_ID	Identifier of the link associated with the event	
Packet Identifier	
UNSIGNED_INT(2)	
Identifier for higher layer PDU on which this notification is generated.	
Transmission Status	Boolean	Status of the transmitted packet.
True: Success
False: Failure	
:
7.4.12.1.3 	When generated
The MIH_Link_PDU_Transmit_Status.indication is sent to local MIHF users to notify them of a local event (i.e., Link_PDU_Transmit_Status.indication).
7.4.12.1.4 	Effect on receipt
MIH User dependant.
7.4.13 	MIH_Link_Handover_Imminent
7.4.13.1 	MIH_Link_Handover_Imminent.indication
MIH_Link_Handover_Imminent is issued by the MIHF to report that a link switch is about to occur. The event notified may be either an intra-technology or inter-technology link switch. In the event of an intra-technology link switch, this indication directly corresponds to the link layer event Link_Handover_Imminent defined in  7.3.11.
7.4.13.1.1 	Function

This primitive is issued by the MIHF to report the imminent occurrence of either an intra-technology or inter-technology link handover to MIH Users. This MIH event may be local or remote.
7.4.13.1.2 	Semantics of service primitive
MIH_Link_Handover_Imminent.indication 					(
					SourceIdentifier,
					Old Link Identifier,
					New Link Identifier,
					HandoverType,
					MacOldAccessRouter,
					MacNewAccessRouter
					)
Parameters
Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which can be either the local MIHF or a remote MIHF.	
Old 
Link Identifier	LINK_TUPLE_ID	Identifier of the old link	
New 
Link Identifier	LINK_TUPLE_ID	Identifier of the new link	
Handover Type	HANDOVER_TYPE	Indicates whether intra-technology or inter-technology handover:	
Mac Old Access Router	MAC_ADDRESS	(Optional) MAC Address of old Access Router	
Mac New Access Router	MAC_ADDRESS	(Optional) MAC Address of new Access Router	
:
7.4.13.1.3 	When generated

This notification is generated by the MIHF when a link layer inter- or intra-technology handover is about to occur. In the case of an intra-technology handover, the event could be triggered by the reception of a Link_Handover_Imminent.indication from a link.
7.4.13.1.4 	Effect on receipt
Upper layer entities may take different actions on this notification. 
7.4.14 	MIH_Link_Handover_Complete
7.4.14.1 	MIH_Link_Handover_Complete.indication
MIH_Link_Handover_Complete is issued by the MIHF to report the successful completion of a link handover to MIH Users. The event notified may be either an intra-technology or inter-technology link handover. The link handover may be a result of either the execution of an MIH_MN_HO_Commit or MIH_Net_HO_Commit command previously issued by an MIH User or by a Link_Handover_Complete indication from the link layer.
7.4.14.1.1 	Function

This primitive is issued by the MIHF to report the completion of a link handover to MIH Users. This event may notify MIH Users of a successful intra-technology or inter-technology handover. This MIH event may be local or remote.
7.4.14.1.2 	Semantics of service primitive
MIH_Link_Handover_Complete.indication 					(
					SourceIdentifier,
					OldLinkIdentifier,
					NewLinkIdentifier,
					MacOldAccessRouter,
					MacNewAccessRouter
					)
Parameters
Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which can be either the local MIHF or a remote MIHF.	
Old 
Link Identifier	LINK_TUPLE_ID	Identifier of the old link	
New Link Identifier	LINK_TUPLE_ID	Identifier of the new link	
Mac Old Access Router	MAC_ADDRESS	(Optional) MAC Address of old Access Router	
Mac New Access Router	MAC_ADDRESS	(Optional) MAC Address of new Access Router	
:
7.4.14.1.3 	When generated

This notification is generated by the MIHF when a link layer inter- or intra-technology handover is completed. In the case of an intra-technology handover, the event could be triggered by the reception of a Link_Handover_Complete.indication from a link. In the case of an inter-technology handover, the event could be triggered by the successful execution of an MIH_MN_HO_Commit or MIH_Net_HO_Commit primitive issued earlier by an MIH User.
7.4.14.1.4 	Effect on receipt
Upper layer entities may take different actions on this notification. An MIH User may make use of this notification to configure other layers (IP, Mobile IP) for various upper layer handovers (e.g., L3 Handovers) that are needed. Transport layers (e.g., TCP) may also make use of this primitive to fine tune their flow control and flow congestion mechanisms.
7.4.15 	MIH_Get_Link_Parameters
An MIH_Get_Link_Parameters command is issued by upper layer entities to discover and monitor the status of the currently connected and potentially available links. The destination of an MIH_Get_Link_Parameters command may be local or remote. For example, an MIH_Get_Link_Parameters issued by a local upper layer may help the policy function that resides out of the MIH to make optimal handover decisions for different applications when multiple links are available in a mobile node, while a remotely initiated MIH_Get_Link_Parameters from the network side may enable the network to collect the status information on multiple links in a mobile node through the currently connected link.
7.4.15.1 	
7.4.15.1 	MIH_Get_Link_Parameters.request
7.4.15.1.1 	
7.4.15.1.1 	Function
This primitive is invoked by an MIH User to discover the status of the currently connected and potentially available links.
7.4.15.1.2 	
7.4.15.1.2 	Semantics of the service primitive
MIH_Get_Link_Parameters.request 			(
			DestinationIdentifier,
			DeviceStatesRequest,
			LinkIdentifierList,
			GetStatusRequestSet
			)

Parameters:

Name	
Type	Description	
Destination Identifier	MIHF_ID	This identifies the local MIHF or a remote MIHF which will be the destination of this request. 	
Device States Request	DEVICE_STATES_REQ	(Optional) List of device states being requested.	
Link Identifier List	LIST(LINK_ID)	List of link identifiers for which status is requested. If the list is empty, return the status of all available links.	
Get Status Request Set	LINK_STATUS_REQ	Indicate which link status(es) is being requested. 	

7.4.15.1.3 	
7.4.15.1.3 	When generated
This primitive is invoked by an MIH User when it wants to request the status information of a set of local or remote links. 
7.4.15.1.4 	Effect of receipt
If the destination of the request is the local MIHF itself, the local MIHF shall get the requested information on the status of the specified local links and respond with an MIH_Get_Link_Parameters.confirm. If the destination of the request is a remote MIHF, the local MIHF shall generate and send an MIH_Get_Link_Parameters request message to the remote MIHF.
7.4.15.2 	MIH_Get_Link_Parameters.confirm
7.4.15.2.1 	
7.4.15.2.1 	Function
This primitive is issued by an MIHF to report the requested status of a set of specific local or remote links in response to an MIH_Get_Link_Parameters request from a local or remote MIH User. 
7.4.15.2.2 	
7.4.15.2.2 	Semantics of the service primitive
MIH_Get_Link_Parameters.confirm 			(
			Source
Identifier,
			DeviceStatesResponseList,
			GetStatusResponseList,
			Status
			)

Parameters:

Name	
Type	
Description	
Source Identifier	MIHF ID	This identifies the invoker of this primitive which can be either the local MIHF or a remote MIHF.	
Device States Response List	DEVICE_STATES_RSP	(Optional) List of device states responses.	
Get Status Response List	LIST(LINK_STATUS_RSP)	List of Status Responses.	
Status			STATUS	Status of operation.	

7.4.15.2.3 	When generated
This primitive returns the results of an MIH_Get_Link_Parameters request to the requesting MIH User. 
7.4.15.2.4 	Effect of receipt
Upon receipt of the link status information, the MIH User makes appropriate decisions and takes suitable actions. However, if Status does not indicate “Success”, the recipient shall ignore any other returned values and, instead, shall perform appropriate error handling.
7.4.16 	MIH_Configure_Link
The MIH_Configure_Link may be issued by an upper layer entity to control the behavior of lower layers, for example, to set some feature of the driver of a specific link. When the MIHF receives MIH_Configure_Link, it issues the Link_Configure_Thresholds commands to the corresponding link.
7.4.16.1 	MIH_Configure_Link.request
7.4.16.1.1 	Function
This primitive is issued by an MIH User to control the behavior of a lower layer link. 
7.4.16.1.2 	
7.4.16.1.2 	Semantics of the service primitive
MIH_Configure_Link.request 			(
			DestinationIdentifier,
			LinkIdentifier,
			OperationMode,
			ConfigurationRequestList
			)

Parameters:
Name	Type	Description	
Destination Identifier	MIHF_ID	This identifies the local MIHF or a remote MIHF which will be the destination of this request. 	
Link Identifier	LINK_TUPLE_ID	Identifier of the link to be configured.	
Operation Mode	OPERATION_MODE	(Optional) Operation mode.	
Configuration Request List	LIST(LINK_CONFIG_PARAM)	List of Configuration Requests.	

7.4.16.1.3 	.When generated
This primitive is invoked by an MIH User when it attempts to control the behavior of a local or remote lower layer link, for example, set some features in the driver.
7.4.16.1.4 	Effect of receipt
If the destination of the request is the local MIHF itself, the local MIHF shall issue a Link_Configure_Thresholds request to the lower layer link to set the thresholds for the link according to the specified configuration parameters. 
If the destination of the request is a remote MIHF, the local MIHF shall generate and send an MIH_Configure_Link request message to the remote MIHF. Upon the receipt of the message, the remote MIHF shall then issue a Link_Configure_Thresholds request to the lower layer link to set the thresholds for the link according to the specified configuration parameters.
7.4.16.2 	MIH_Configure_Link.confirm
7.4.16.2.1 	
7.4.16.2.1 	Function
This primitive is issued by an MIHF to report the result of an MIH_Configure_Link request. 
7.4.16.2.2 	Semantics of the service primitive
MIH_Configure_Link.confirm (
			Source
Identifier,
			LinkIdentifier,
			OperationModeStatus,
			ConfigurationResponseList,
			Status
			)

Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which can be either the local MIHF or a remote MIHF.	
Link Identifier	LINK_TUPLE_ID	Identifier of the link configured.	
Operation Mode Status	OPERATION_MODE_STATUS	(Optional) Operation mode.	
Configuration Response List	LIST(LINK_CONFIG_STATUS)	List of the configuration status for each requested link.	
Status			STATUS	Status of operation.	

7.4.16.2.3 	When generated
This primitive returns the result of an MIH_Configure_Link request to the requesting MIH User.
7.4.16.2.4 	
7.4.16.2.4 	Effect of receipt
Upon receipt of the result, the MIH User makes appropriate evaluations and takes any suitable actions. However, if Status does not indicate “Success”, the recipient shall ignore any other returned values and, instead, shall perform appropriate error handling. 
7.4.17 	
7.4.17 	MIH_Scan
An upper layer entity can use an MIH_Scan command to discover available PoAs in its neighborhood. An MIH_Scan command may trigger the issuance of a link scan command at the destination MIHF. The link scan command is defined in the related SDO and beyond the scope of this standard. If the current active link is to be scanned, it is most likely that the on-going user data traffic will be interrupted. MIH_Scan performs a single scan request and does not scan continuously until a PoA is discovered.
7.4.17.1 	MIH_Scan.request
7.4.17.1.1 	
7.4.17.1.1 	Function
This primitive is invoked by an MIH User to request an MIHF to survey of available PoAs in its current neighborhood.
7.4.17.1.2 	Semantics of the service primitive
MIH_Scan.request (
		DestinationIdentifier,
		ScanLinkIdentifier
		)

Parameters:
Name	Type	Description	
Destination Identifier	MIHF_ID	This identifies the local MIHF or a remote MIHF which will be the destination of this request. 	
Scan Link Identifier	LINK_ID	Identifier of the link to be scanned.	

7.4.17.1.3 	When generated
This primitive is invoked by an MIH User when it wants to request an MIHF to perform a survey of available PoAs in its current neighborhood. 
7.4.17.1.4 	
7.4.17.1.4 	Effect of receipt
If the destination of the request is the local MIHF itself, the local MIHF shall issue the corresponding Link Scan command to the specified link. The Link Scan command is defined in the relevant SDO. If the destination of the request is a remote MIHF, the local MIHF shall generate and send an MIH_Scan request message to the remote MIHF.
7.4.17.2 	MIH_Scan.confirm
7.4.17.2.1 	
7.4.17.2.1 	Function
This primitive is issued by an MIHF to report the result of an MIH_Scan request. 
7.4.17.2.2 	
7.4.17.2.2 	Semantics of the service primitive
MIH_Scan.confirm 			(
			Source
Identifier,
			ScanLinkIdentifier,
			ScanResponseSet,
			Status
			)
Parameters:
Name	Type	Description	
Source Identifier	MIHF ID	This identifies the invoker of this primitive which can be either the local MIHF or a remote MIHF.	
Scan Link Identifier	LINK ID	Identifier of the link scanned.	
Scan Response Set	LIST(LINK_SCAN_RSPRSP)	A list of discovered PoAs and related information.	
Status			STATUS	Status of operation.	

7.4.17.2.3 	
7.4.17.2.3 	When generated
This primitive returns the result of an MIH_Scan.request to the requesting MIH User. 
7.4.17.2.4 	Effect of receipt
The MIH User can act on the scan result accordingly.
7.4.18 	
7.4.18 	MIH_Net_HO_Candidate_Query
7.4.18.1 	MIH_Net_HO_Candidate_Query.request
7.4.18.1.1 	Function
This primitive is invoked by an MIH User to communicate with a peer MIH User about its intent of handover initiation.
7.4.18.1.2 	Semantics of service primitive
MIH_Net_HO_Candidate_Query.request
 				(
			DestinationIdentifier,
			SuggestedNewLinkList,
			QueryResourceList
			)
Parameters:

Name	
Type	
Description	
Destination Identifier	MIHF_ID	This identifies a remote MIHF which will be the destination of this request. 	

Suggested New Link List	LIST(LINK_POA_LIST)	
A list of PoAs for each link, suggesting the new access networks to which handover initiation should be considered. The access networks towards the top of the list are more preferable than those towards the bottom of the list.	
Query Resource List	QUERY_RESOURCE_LIST	List of resources to be queried at the new candidate network. (Editor’s note: need input)	

7.4.18.1.3 	When generated
This primitive is invoked by an MIH User to communicate with a remote MIH User about its intent of handover initiation. Serving PoS requests MN to provide information about resources required to initiate a handover by setting the QueryResourceFlag parameter. [Editor’s note: sentence out of date: QueryResourceFlag now?]
7.4.18.1.4 	Effect on receipt
Upon receipt of this primitive by the local MIHF, it shall generate and send an MIH_Net_HO_Candidate_Query request message to the remote MIHF identified by the Destination Identifier. On the remote MIHF, the MIHF must forward the request as an indication to the MIH User.
7.4.18.2 	MIH_Net_HO_Candidate_Query.indication
7.4.18.2.1 	Function
This primitive is generated by an MIHF to indicate to an MIH User that an MIH_Net_HO_Candidate_Query request message is received from a remote MIHF. 
7.4.18.2.2 	Semantics of service primitive
MIH_Net_HO_Candidate_Query.indication (
			SourceIdentifier,
			SuggestedNewLinkList,
			QueryResourceList
			)
Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which is a remote MIHF.	

Suggested New Link List	LIST(LINK_POA_LIST)	
A list of PoAs for each link, suggesting the new access networks to which handover initiation should be considered. The access networks towards the top of the list are more preferable than those towards the bottom of the list.	
Query Resource List	QUERY_RESOURCE_LIST	TBD	

7.4.18.2.3 	When generated
This primitive is generated by an MIHF on receiving an MIH_Net_HO_Candidate_Query request message from a peer MIHF.
7.4.18.2.4 	Effect on receipt
An MIH User receiving this indication should invoke an MIH_Net_HO_Candidate_Query.response primitive towards the remote MIHF indicated by the Source Identifier in the request message.
7.4.18.3 	MIH_Net_HO_Candidate_Query.response
7.4.18.3.1 	Function
This primitive is used by the MIHF on an MN to respond to an MIH_Net_HO_Candidate_Query request message from a remote MIHF in the network.
7.4.18.3.2 	Semantics of service primitive
MIH_Net_HO_Candidate_Query.response
 				(
				DestinationIdentifier,
				CurrentLinkIdentifier,
				PreferredLinkList,
				RequestedResourceSet,
				HandoverStatus,
				Status
				)
Parameters:

Name	
Type	
Description	
Destination Identifier	MIHF_ID	This identifies a remote MIHF which will be the destination of this response. 	

Current Link Identifier	LINK_TUPLE_ID	
This identifies the current link over which the command needs to be sent. 	

Preferred Link List	LIST(LINK_POA_LIST)	A list of PoAs for each link, suggesting the new access networks and PoAs to which handover initiation should be considered. This may be different than the networks that were suggested in the handover request. The list is sorted from most preferred first to least preferred last.	
Requested Resource Set	LINK_RESOURCE_SET	Requested resources needed by the mobile terminal. (Editor’s note: need definition)	
Handover Status	HANDOVER_STATUS	
Lists the reason for aborting/declining the handover request.	
Status			STATUS	Status of operation.	

7.4.18.3.3 	When generated
The remote MIH User invokes this primitive in response to an MIH_Net_HO_Candidate_Query.indication from its MIHF.
7.4.18.3.4 	Effect on receipt
The MIHF shall send an MIH_Net_HO_Candidate_Query response message to the peer MIHF as indicated in the Destination Identifier.
7.4.18.4 	MIH_Net_HO_Candidate_Query.confirm
7.4.18.4.1 	Function
This primitive is generated by the MIHF to confirm that an MIH_Net_HO_Candidate_Query response message is received from a peer MIHF.
7.4.18.4.2 	Semantics of service primitive
MIH_Net_HO_Candidate_Query.confirm (
					SourceIdentifier,
					CurrentLinkIdentifier,
					PreferredLinkList,
					RequestedResourceSet,
					HandoverStatus,
					Status
					)
Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	Shall contain the MIHF ID of the mobile node that sent the MIH_Net_HO_Candidate_Query response message.	
Current Link Identifier	LINK_TUPLE_ID	This identifies the current link over which the command needs to be sent. 	

Preferred Link List	LIST(LINK_POA_LIST)	A list of PoAs, suggesting the new access networks to which handover initiation should be considered. This may be different than the networks that were suggested in the handover request. The list is sorted from most preferred first to least preferred last.	
Requested Resource Set	LINK_RESOURCE_SET	Requested resources needed by the mobile terminal.	
Handover Status	HANDOVER_STATUS	
Lists the reason for aborting/declining the handover request.	
Status			STATUS	Status of operation.	

7.4.18.4.3 	When generated
This primitive is generated by the MIHF on receiving an MIH_Net_HO_Candidate_Query response message from a peer MIHF.
7.4.18.4.4 	Effect on receipt
On receiving the primitive the entity which originally initiated the handover request may decide to carry out the handover or abort it based on the primitive. However, if Status does not indicate “Success”, the recipient shall ignore any other returned values and, instead, shall perform appropriate error handling.
7.4.19 	
7.4.19 	MIH_MN_HO_Candidate_Query
7.4.19.1 	MIH_MN_HO_Candidate_Query.request
7.4.19.1.1 	Function
This primitive is used by MIH Users on a mobile node to inform MIHF to perform candidates query for a possible handover initiation and query if the QoS resources and/or IP address configuration method of the ongoing data sessions can be supported in the candidate networks. This primitive also includes the current IP configuration server address (e.g., DHCP server, FA IP address, AR IP address) when the current IP configuration method is included.
7.4.19.1.2 	Semantics of service primitive
MIH_MN_HO_Candidate_Query.request (
				DestinationIdentifier,
				CurrentLinkIdentifier,
				CandidateLinkList,
				QueryResourceList,
				IPConfigurationMethod,
				DHCPServerAddress,
				FAAddress,
				AccessRouterAddress
				)
Parameters:
Name	Type	Description	
Destination Identifier	MIHF_ID	Shall contain the MIHF ID of node that sent the MIH_MN_HO_Candidate_Query request message. 	
Current Link Identifier	LINK_TUPLE_ID	This identifies the current link over which the request needs to be sent. 	
Candidate Link List	LIST(LINK_POA_LIST)	
A list of PoAs, identifying candidate networks to which handover needs to be initiated. The list is sorted from most preferred first to least preferred last.	
Query Resource List	QUERY_RESOURCE_LIST	List of resources to be queried at candidate networks.	
IP Configuration Method	IP_CONFIG_METHODS	Current IP configuration method.	
DHCP Server Address	IP_ADDRESS	IP address of current DHCP Server. It is only included when mobile node is using dynamic address configuration	
FA Address	IP_ADDRESS	IP address of current Foreign Agent. It is only included when mobile node is using Mobile IPv4	
Access Router Address	IP_ADDRESS	IP address of current Access Router. It is only included when mobile node is using IPv6 	

7.4.19.1.3 	When generated
This primitive is generated by an upper layer entity such as a Handover Policy engine, L3 Mobility protocol like MIP, Application or some other entity in the mobile node that may want to query other candidate networks for a possible handover. MN uses the QueryResourceList parameter to notify the Serving PoS of the resource list which it is interested in checking at the candidate networks as part of this query. MN's upper layer entity generates this primitive when it wants to query IP address related information from the candidate networks before handover.
7.4.19.1.4 	Effect on receipt
Upon receipt of this primitive by the local MIHF, it shall generate and send an MIH_MN_HO_Candidate_Query request message to the remote MIHF identified by the Destination Identifier.
7.4.19.2 	MIH_MN_HO_Candidate_Query.indication
7.4.19.2.1 	Function
This primitive is used by MIHF to indicate the receipt of MIH_MN_HO_Candidate_Query request message from a mobile node to the registered MIH-Users. 
7.4.19.2.2 	Semantics of service primitive
MIH_MN_HO_Candidate_Query.indication (
				SourceIdentifier,
				CurrentLinkIdentifier,
				CandidateLinkList,
				QueryResourceList,
				IPConfigurationMethod,
				DHCPServerAddress,
				FAAddress,
				AccessRouterAddress
				)

Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which is a remote MIHF.	
Current Link Identifier	LINK_TUPLE_ID	This identifies the current link over which the request needs to be sent. 	
Candidate Link List	LIST(LINK_POA_LIST)	
A list of PoAs, identifying candidate networks to which handover needs to be initiated. The list is sorted from most preferred first to least preferred last.	
Query Resource List	QUERY_RESOURCE_LIST	List of resources to be queried at candidate networks. 	
IP Configuration Method	IP_CONFIG_METHODS	Current IP configuration method.	
DHCP Server Address	IP_ADDRESS	IP address of current DHCP Server. It is only included when mobile node is using dynamic address configuration	
FA Address	IP_ADDRESS	IP address of current Foreign Agent. It is only included when mobile node is using Mobile IPv4	
Access Router Address	IP_ADDRESS	IP address of current Access Router. It is only included when mobile node is using IPv6 	

7.4.19.2.3 	When generated
This primitive is generated by MIHF on receiving MIH_MN_HO_Candidate_Query request message from a peer MIHF in a mobile node.
7.4.19.2.4 	Effect on receipt
The MIH User receiving this primitive may generate an MIH_N2N_HO_Query_Resources.request primitive to exchange MIH_N2N_HO_Query_Resources messages with MIHF in one or more candidate networks under consideration before sending a corresponding MIH_MN_HO_Candidate_Query response message.
7.4.19.3 	MIH_MN_HO_Candidate_Query.response
7.4.19.3.1 	Function
This primitive is used by MIH Users to inform MIHF of the result of the candidate query request.
7.4.19.3.2 	Semantics of service primitive
MIH_MN_HO_Candidate_Query.response (
				DestinationIdentifier,
				CurrentLinkIdentifier,
				PreferredCandidateLinkList,
				AvailableResourceSet,
				IPConfigurationMethod,
				DHCPServerAddress,
				FAAddress,
				AccessRouterAddress,
				IPAddressInformationStatus,
				Status
				)
Parameters:
Name	Type	Description	
Destination Identifier	MIHF_ID	Shall contain the MIHF ID of the node that sent the MIH_MN_HO_Candidate_Query response message. 	
Current Link Identifier	LINK_TUPLE_ID. 	This identifies the current link over which the command needs to be sent.	
Preferred Candidate Link List	LIST(LINK_POA_LIST)	
A list of PoAs, identifying candidate networks to which handover needs to be initiated. The list is sorted from most preferred first to least preferred last.	
Available Resource Set	LIST(LINK_RESOURCE_SET)	A list of available resource for each link.	
IP Configuration Method	IP_CONFIG_METHODS	Current IP configuration method.	
DHCP Server Address	IP_ADDRESS	(Optional) IP address of candidate DHCP Server. It is only included when dynamic address configuration is supported	
FA Address	IP_ADDRESS	(Optional) IP address of candidate Foreign Agent. It is only included Mobile IPv4 is supported	
Access Router Address	IP_ADDRESS	(Optional) IP address of candidate Access Router. It is only included IPv6 Stateless configuration is supported	
IP Address Information Status	IP_CONFIG_STATUS	The result of IP configuration.	
Status			STATUS	Status of operation.	

7.4.19.3.3 	When generated
The MIH User responds with this primitive in response to an earlier MIH_MN_HO_Candidate_Query.request command from a peer MIHF entity in mobile node after the exchange of MIH_N2N_HO_Query_Resources messages with the MIHF in the candidate networks.
7.4.19.3.4 	Effect on receipt
On receiving the response the entity which originally initiated the candidate query request decides the suitability of the candidates based on the list, available resources, and the IP address related information on each network. 
7.4.19.4 	MIH_MN_HO_Candidate_Query.confirm
7.4.19.4.1 	Function
This primitive is used by MIHF to inform MIH Users of the receipt of candidate query and IP address related information response. 
7.4.19.4.2 	Semantics of service primitive
MIH_MN_HO_Candidate_Query.confirm (
				SourceIdentifier,
				CurrentLinkIdentifier,
				PreferredCandidateLinkList,
				AvailableResourceSet,
				IPConfigurationMethod,
				DHCPServerAddress,
				FAAddress,
				AccessRouterAddress,
				IP Address Information Status,
				Status
				)
Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	This identifies the invoker of this primitive which is a remote MIHF.	
Current Link Identifier	LINK_TUPLE_ID. 	This identifies the current link over which the command needs to be sent.	
Preferred Candidate Link List	LIST(LINK_POA_LIST)	
A list of PoAs, identifying candidate networks to which handover needs to be initiated. The list is sorted from most preferred first to least preferred last.	
Available Resource Set	LIST(LINK_RESOURCE_SET)	A list of available resources for each link.	
IP Configuration Method	IP_CONFIG_METHODS	IP configuration Method on PreferredCandidatePoA List	
DHCP Server Address	IP_ADDRESS	(Optional) IP address of candidate DHCP Server. It is only included when dynamic address configuration is supported	
FA Address	IP_ADDRESS	(Optional) IP address of candidate Foreign Agent. It is only included Mobile IPv4 is supported	
Access Router Address	IP_ADDRESS	(Optional) IP address of candidate Access Router. It is only included IPv6 Stateless configuration is supported	
IP Address Information Status	IP_CONFIG_STATUS	The result of IP configuration.	
Status			STATUS	Status of operation.	

7.4.19.4.3 	When generated
This primitive is generated by MIHF on receiving MIH_MN_HO_Candidate_Query response message from a peer MIHF in the network.
7.4.19.4.4 	Effect on receipt
On receiving the primitive the MIH User entity which originally initiated the candidate query request may decide to choose the candidate network for handover or abort it based on the information in the primitive. This primitive triggers MIH User to initiate the process to get IP address to be used in the target depending on the received candidate query response. 
7.4.20 	MIH_N2N_HO_Query_Resources
7.4.20.1 	MIH_N2N_HO_Query_Resources.request
7.4.20.1.1 	Function
This primitive is used by an MIHF on the serving network to communicate with its peer MIHF on the candidate network. This is used to prepare the new link resource for impending handover and query the available link resource and IP address related information of the candidate network.
7.4.20.1.2 	Semantics of service primitive
MIH_N2N_HO_Query_Resources.request
 				(
				DestinationIdentifier,
				QueryResourceList,
				IPConfigurationMethod,
				DHCPServerAddress,
				FAAddress,
				AccessRouterAddress
				)
Parameters:

Name	
Type	
Description	
Destination Identifier	MIHF_ID	This identifies a remote MIHF which will be the destination of this request. 	

Query Resource List	QUERY_RESOURCE_LIST	
List of resources to be queried at the new candidate network.	
IP Configuration Method	IP_CONFIG_METHODS	Current IP configuration method.	
DHCP Server Address	IP_ADDRESS	(Optional) IP address of current DHCP Server. It is only included when mobile node is using dynamic address configuration	
FA Address	IP_ADDRESS	(Optional) IP address of current Foreign Agent. It is only included when mobile node is using Mobile IPv4	
Access Router Address	IP_ADDRESS	(Optional) IP address of current Access Router. It is only included when mobile node is using IPv6 	

7.4.20.1.3 	
7.4.20.1.3 	When generated
This primitive is generated after receiving the MIH_Net_HO_Candidate_Query request message from the MIHF on the mobile node in the case of mobile-initiated handover. In the case of network-initiated handover, this primitive is generated after receiving the MIH_Net_HO_Candidate_Query.response message from the mobile node.
7.4.20.1.4 	Effect on receipt
This peer MIHF on the candidate network identifies the link resource usage and prepares resources for the impending handover. 
A corresponding indication (MIH_N2N_HO_Query_Resources.indication) may be triggered to send to all subscribed MIH User entities in the local stack. The associated parameters for the generated indication are the same as those used in the command request.
7.4.20.2 	MIH_N2N_HO_Query_Resources.indication
7.4.20.2.1 	Function
The MIHF on the candidate network indicates that an MIH_N2N_HO_Query_Resources request message is received from a remote MIHF on the serving network so that the upper layer entity can identify the link resource usage, prepare resources, and provide IP address related information for the impending handover.
7.4.20.2.2 	Semantics of service primitive
MIH_N2N_HO_Query_Resources.indication (
					SourceIdentifier,
					QueryResourceList,
					IPConfigurationMethod,
					DHCPServerAddress,
					FAAddress,
					AccessRouterAddress
					)
Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	Shall contain the MIHF ID of node that sent the MIH_N2N_HO_Candidate_Query request message.	
Query Resource List	QUERY_RESOURCE_LIST	List of resources to be queried at the new candidate network.	
IP Configuration Method	IP_CONFIG_METHODS	Current IP configuration method.	
DHCP Server Address	IP_ADDRESS	(Optional) IP address of current DHCP Server. It is only included when mobile node is using dynamic address configuration	
FA Address	IP_ADDRESS	(Optional) IP address of current Foreign Agent. It is only included when mobile node is using Mobile IPv4	
Access Router Address	IP_ADDRESS	(Optional) IP address of current Access Router. It is only included when mobile node is using IPv6 	

7.4.20.2.3 	When generated
This primitive is generated by MIHF when the MIHF on the candidate network receives MIH_N2N_HO_Query_Resources request message from a peer MIHF on the serving network.
7.4.20.2.4 	Effect on receipt
The MIH User on the candidate network identifies the link resource usage and prepares resources for the impending handover. It also replies with MIH_N2N_HO_Query_Resources.response primitive.

7.4.20.3 	MIH_N2N_HO_Query_Resources.response
7.4.20.3.1 	Function
This primitive is used by an MIHF on the candidate network to communicate with its peer MIHF on the serving network which sent out an MIH_N2N_HO_Query_Resources request. This is used to respond with the result of any resource preparation for the impending handover and to notify the MIHF on the serving network of the link resource status of the candidate network. It is also used to provide IP address related information of the candidate networks.
7.4.20.3.2 	Semantics of service primitive
MIH_N2N_HO_Query_Resources.response
 				(
				DestinationIdentifier,
				ResourceStatus,
				AvailableResourceSet,
				IPConfigurationMethod,
				DHCPServerAddress,
				FAAddress,
				AccessRouterAddress,
				IPAddressInformationStatus,
				Status
				)
Parameters:

Name	Type	
Description	
Destination Identifier	MIHF_ID	Shall contain the MIHF ID of the node that sent the MIH_N2N_HO_Query_Resources response message.	

Resource Status	LINK_RESOURCE_STATUS	
Specifies whether requested resources are available or not at the new PoA.	
Available Resource Set	LIST(LINK_RESOURCE_SET)	A list of available resources for each link.
[Editor’s note: need better def]	
IP Configuration Method	IP_CONFIG_METHODS	Current IP configuration method.	
DHCP Server Address	IP_ADDRESS	(Optional) IP address of candidate DHCP Server. It is only included when dynamic address configuration is supported.	
FA Address	IP_ADDRESS	(Optional) IP address of candidate Foreign Agent. It is only included Mobile IPv4 is supported.	
Access Router Address	IP_ADDRESS	(Optional) IP address of candidate Access Router. It is only included IPv6 Stateless configuration is supported.	
IP Address Information Status	IP_CONFIG_STATUS	The result of IP configuration.	
Status			STATUS	Status of operation.	

7.4.20.3.3 	
7.4.20.3.3 	When generated
The MIHF on the candidate network responds with this primitive in response to an MIH_N2N_HO_Query_Resources request from a peer MIHF entity on the serving network.
7.4.20.3.4 	Effect on receipt
After receiving the response, the MIHF on the serving network may send MIH_Net_HO_Candidate_Query response to the mobile node.
7.4.20.4 	MIH_N2N_HO_Query_Resources.confirm
7.4.20.4.1 	Function
This primitive is generated by the MIHF on the serving network to respond with the result of any resource preparation for the impending handover and to notify the link resource status of the candidate network. It also carries IP address related information on the candidate networks to MIH Users on the serving network.
7.4.20.4.2 	Semantics of service primitive
MIH_N2N_HO_Query_Resources.confirm (
				SourceIdentifier,
				ResourceStatus,
				AvailableResourceSet,
				IPConfigurationMethod,
				DHCPServerAddress,
				FAAddress,
				AccessRouterAddress,
				IPAddressInformationStatus,
				Status
				)
Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	Shall contain the MIHF ID of the node that sent the MIH_N2N_HO_Candidate_Query response message.	
ResourceStatus	LINK_RESOURCE_STATUS	Specifies whether requested resources are available or not at the new PoA.	
Available Resource Set	LIST(LINK_RESOURCE_SET)	A list of available resource for each link.
[Editor’s note: need better def]	
IP Configuration Method	IP_CONFIG_METHODS	IP configuration Method on PreferredCandidatePoA List	
DHCP Server Address	IP_ADDRESS	(Optional) IP address of candidate DHCP Server. It is only included when dynamic address configuration is supported	
FA Address	IP_ADDRESS	(Optional) IP address of candidate Foreign Agent. It is only included Mobile IPv4 is supported	
Access Router Address	IP_ADDRESS	(Optional) IP address of candidate Access Router. It is only included IPv6 Stateless configuration is supported	
IP Address Information Status	IP_CONFIG_STATUS	The result of IP configuration.	
Status			STATUS	Status of operation.	

7.4.20.4.3 	When generated
This primitive is generated by the MIHF when the MIHF on the serving network receives an MIH_N2N_HO_Query_Resources.response message from a peer MIHF on the candidate network.
7.4.20.4.4 	Effect on receipt
After receiving this primitive, the upper layer entity on the serving network may send an MIH_Net_HO_Candidate_Query.response primitive to the MIHF in case it was indicated with MIH_Net_HO_Candidate_Query.indication primitive before. However, if Status does not indicate “Success”, the recipient shall ignore any other returned values and, instead, shall perform appropriate error handling.
7.4.21 	MIH_Net_HO_Commit
7.4.21.1 	MIH_Net_HO_Commit.request
7.4.21.1.1 	Function
This primitive is used by a peer MIHF to communicate with the remote MIHF on the network. The primitive is used to request the peer MIHF the commitment to perform link handover actions based on selected choices for a candidate network and PoA. 
7.4.21.1.2 	Semantics of service primitive
MIH_Net_HO_Commit.request
 				(
				DestinationIdentifier,
				LinkActionSetList,
				)

Parameters:

Name	
Type	
Description	
Destination Identifier	MIHF_ID	Shall contain the MIHF ID of the node that sent the MIH_Net_HO_Commit request message.	
Link Action Set List	LIST(LINK_ACTION_REQ)	A list of handover actions for the links.	

7.4.21.1.3 	When generated
The MIH User generates this primitive to order specific handover actions on one or more links.
7.4.21.1.4 	Effect on receipt
Upon receipt of the MIH_Net_HO_Commit.request, the MIHF issues one or more specific link action commands to instruct the relevant link layer technologies to perform the specified actions on the link or links, identified by the Link Identifier(s). The actions that need to be performed are signalled through the Link Action parameters. It is up to the MIHF to either wait for the Execution Time period before issuing the Link Action for immediate execution (i.e., with an Execution Time of zero value), or issue the Link Action immediately with the same Execution Time parameter and leave the future execution responsibility to the specific link layer technology. 
A corresponding indication (MIH_Net_HO_Commit.indication) may be triggered to send to all subscribed MIH User entities in the local stack. The associated parameters for the generated indication are the same as those used in the command request.
7.4.21.2 	MIH_Net_HO_Commit.indication
7.4.21.2.1 	Function
This primitive is generated by an MIHF to indicate that an MIH_Net_HO_Commit request message has been received from a peer MIHF. 
7.4.21.2.2 	Semantics of service primitive
MIH_Net_HO_Commit.indication (
				SourceIdentifier,
				LinkActionSetList
				)
Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	Shall contain the MIHF ID of the node that sent the MIH_Net_HO_Commit request message.	
Link Action Set List	LIST(LINK_ACTION_REQ)	A list of handover actions for the links.	

7.4.21.2.3 	When generated
This primitive is generated by an MIHF on receiving an MIH_Net_HO_Commit request message from a peer MIHF.
7.4.21.2.4 	Effect on receipt
The MIH User receiving this primitive replies with an MIH_Net_HO_Commit.response primitive.
7.4.21.3 	MIH_Net_HO_Commit.response
7.4.21.3.1 	Function
This primitive is used by an MIHF to communicate with a peer MIHF from which an MIH_Net_HO_Commit request message is received. The primitive is used to communicate the response of a handover commit request.
7.4.21.3.2 	Semantics of service primitive
MIH_Net_HO_Commit.response 	(
				DestinationIdentifier,
				LinkActionResultList,
				Status
				)

Parameters:

Name	
Type	
Description	
Destination Identifier	MIHF_ID	Shall contain the MIHF ID of the node that sent the MIH_Net_HO_Commit response message.	
Link Action Result List	LIST(LINK_ACTION_RSP)	A list of link actions result.	
Status			STATUS	Status of operation.	

7.4.21.3.3 	When generated
This primitive is generated in response to an MIH_Net_HO_Commit.request primitive.
7.4.21.3.4 	Effect on receipt
Upon receipt, the old Serving PoS is informed about the status of the previously issued command request so that it can react accordingly. For instance, it may start forwarding any pending or remaining packets to the new Target PoS. The MN recipient may initiate a handover process and begin the setting up of the new layer 2 connection. Similarly, the network recipient may determine that the handover procedure is in progress to the intended network.
7.4.21.4 	MIH_Net_HO_Commit.confirm
7.4.21.4.1 	Function
This primitive is generated by the MIHF to confirm that an MIH_Net_HO_Commit response message is received from a peer MIHF.
7.4.21.4.2 	Semantics of service primitive
MIH_Net_HO_Commit.confirm (
				SourceIdentifier,
				LinkActionResultList,
				Status
				)

Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	Shall contain the MIHF ID of the node that sent the MIH_Net_HO_Commit response message.	
Link Action Result List	LIST(LINK_ACTION_RSP)	A list of link actions result.	
Status			STATUS	Status of operation.	

7.4.21.4.3 	When generated
This primitive is generated by the MIHF on receiving an MIH_Net_HO_Commit response message from a peer MIHF.
7.4.21.4.4 	Effect on receipt
Upon receipt, the old serving PoS is informed about the status of the previously issued command request so that it can react accordingly. For instance, it may start forwarding any pending or remaining packets to the new target PoS. The MN recipient may initiate a handover process and begin the setting up of the new layer 2 connection. The network recipient may determine that the handover procedure is in progress to the intended network. However, if Status does not indicate “Success”, the recipient shall ignore any other returned values and, instead, shall perform appropriate error handling.
7.4.22 	MIH_MN_HO_Commit
7.4.22.1 	MIH_MN_HO_Commit.request
7.4.22.1.1 	Function
This primitive is used by MIH Users on a mobile node to inform MIHF to commit the handover to a specific target network. MIHF may forward the message remotely to the peer MIHF in the network. The MN may, instead, continue the handover procedure utilizing IP mobility protocols after activating target L2 links natively.
7.4.22.1.2 	Semantics of service primitive
MIH_MN_HO_Commit.request (
				DestinationIdentifier,
				CurrentLinkIdentifier,
				TargetLinkIdentifier,
				TargetPoA,
				OldLinkActions
				)
Parameters:

Name	Type	Description	
Destination Identifier	MIHF_ID	This identifies a remote MIHF which will be the destination of this request. 	
Current Link Identifier	LINK_TUPLE_ID	This identifies the current link over which the command needs to be sent.	
Target Link Identifier	LINK_TUPLE_ID	This is the identifier target network to which handover needs to be initiated	
Target PoA	MAC_ADDRESS	This is the Target Point of Attachment List (AP/BS). [Editor’s note: need better def]	
Old Link Actions	LINK_ACTIONS	Specifies the suggested action on link during handover. 	

7.4.22.1.3 	When generated
This primitive may be generated when a mobile node decides to perform a handover based on suggested choices for a candidate network and PoA.
7.4.22.1.4 	Effect on receipt
Upon receipt of this primitive by the local MIHF, it shall generate and send an MIH_MN_HO_Commit request message to the remote MIHF identified by the Destination Identifier.
7.4.22.2 	MIH_MN_HO_Commit.indication
7.4.22.2.1 	Function
This primitive is used by MIHF to inform MIH Users locally that MIH_MN_HO_Commit request is received. 
7.4.22.2.2 	Semantics of service primitive
MIH_MN_HO_Commit.indication (
				SourceIdentifier,
				CurrentLinkIdentifier,
				TargetLinkIdentifier,
				TargetPoA,
				OldLinkActions
				)
Parameters:

Name	Type	Description	
Source Identifier	MIHF_ID	Shall contain the MIHF ID of the node that sent the MIH_MN_HO_Commit request message.	
Current Link Identifier	LINK_TUPLE_ID	This identifies the current link over which the command needs to be sent.	
Target Link Identifier	LINK_TUPLE_ID	This is the identifier target network to which handover needs to be initiated.	
Target PoA	MAC_ADDRESS	This is the Target Point of Attachment List (AP/BS). [Editor’s note: need better def]	
Old Link Actions	LINK_ACTIONS	Specifies the suggested action on link during
handover. 	

7.4.22.2.3 	When generated
This primitive may be generated when MIH_MN_HO_Commit request is received. 
7.4.22.2.4 	Effect on receipt
The recipient may identify that the mobile node may have started handover to the selected target network. A corresponding response (MIH_Net_HO_Commit.response) maybe triggered to acknowledge the receipt.
7.4.22.3 	MIH_MN_HO_Commit.response
7.4.22.3.1 	Function
This primitive is used by MIH Users to send a response to MIH_MN_HO_Commit request. 
7.4.22.3.2 	Semantics of service primitive
MIH_MN_HO_Commit.response (
				DestinationIdentifier,
				CurrentLinkIdentifier,
				Status
				)
Parameters:
Name	Type	Description	
Destination Identifier	MIHF_ID	This identifies a remote MIHF which will be the destination of this response. 	
Current Link Identifier	LINK_TUPLE_ID	This identifies the current link over which the command needs to be sent.	
Status			STATUS	Status of operation.	

7.4.22.3.3 	When generated
This primitive may be generated when MIH_MN_HO_Commit request is received. 
7.4.22.3.4 	Effect on receipt
MN may now proceed with the next step in handover after taking any local link actions. A corresponding confirm is generated to the MIH Users.
7.4.22.4 	MIH_MN_HO_Commit.confirm
7.4.22.4.1 	Function
This primitive is used by MIHF to inform MIH Users locally that MIH_MN_HO_Commit response is received. 
7.4.22.4.2 	Semantics of service primitive
MIH_MN_HO_Commit.confirm (
				SourceIdentifier,
				CurrentLinkIdentifier,
				Status
				)
Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	Shall contain the MIHF ID of the node that sent the MIH_MN_HO_Commit response message.	
Current Link Identifier	LINK_TUPLE_ID 	This identifies the current link over which the command needs to be sent. 	
Status			STATUS	Status of operation.	

7.4.22.4.3 	When generated
This primitive may be generated when MIH_MN_HO_Commit response is received. 
7.4.22.4.4 	Effect on receipt
MN may now proceed with the next step in handover.
7.4.23 	MIH_MN_HO_Complete
7.4.23.1 	MIH_MN_HO_Complete.request
7.4.23.1.1 	Function
This primitive may be optionally used by MIH Users to indicate the completion of MIH level handover aiding procedure. 
7.4.23.1.2 	Semantics of service primitive
MIH_MN_HO_Complete.request (
				DestinationIdentifier,
				LinkIdentifier,
				HandoverResult
				)
Parameters:
Name	Type	Description	
Destination Identifier	MIHF_ID	This identifies a remote MIHF which will be the destination of this request. 	
Link Identifier	LINK_TUPLE_ID	This identifies the current link over which the command needs to be sent. 	
Handover Result	HANDOVER_RESULT	Handover result.	

7.4.23.1.3 	When generated
This primitive may be generated when MIH level handover procedure is complete.
7.4.23.1.4 	Effect on receipt
Upon receipt of this primitive by the local MIHF, it shall generate and send an MIH_MN_HO_Complete request message to the remote MIHF identified by the Destination Identifier.
7.4.23.2 	MIH_MN_HO_Complete.indication
7.4.23.2.1 	Function
This primitive is used by MIHF to inform MIH Users locally that MIH_MN_HO_Complete request is received. 
7.4.23.2.2 	Semantics of service primitive
MIH_MN_HO_Complete.indication (
				SourceIdentifier,
				LinkIdentifier,
				HandoverResult
				)
Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	Shall contain the MIHF ID of the node that sent the MIH_MN_HO_Complete request message.	
Link Identifier	LINK_TUPLE_ID	This identifies the current link over which the command needs to be sent. 	
Handover Result	HANDOVER_RESULT	Handover result.	

7.4.23.2.3 	When generated
This primitive may be generated when an MIH_MN_HO_Commit request message is received.
7.4.23.2.4 	Effect on receipt
This indicates the completion of the MIH level mobile initiated handover. A corresponding response is generated.
7.4.23.3 	MIH_MN_HO_Complete.response
7.4.23.3.1 	Function
This primitive is used by MIH Users to send a response to MIH_MN_HO_Complete request. 
7.4.23.3.2 	Semantics of service primitive
MIH_MN_HO_Complete.response (
				DestinationIdentifier,
				CurrentLinkIdentifier,
				Status
				)
Parameters:
Name	Type	Description	
Destination Identifier	MIHF_ID	Shall contain the MIHF ID of the node that sent the MIH_MN_HO_Complete response message.	
Current Link Identifier	LINK_TUPLE_ID	This identifies the current link over which the command needs to be sent. 	
Status			STATUS	Status of operation.	

7.4.23.3.3 	When generated
This primitive may be generated when MIH_MN_HO_Complete request is received.
7.4.23.3.4 	Effect on receipt
This indicates the completion of the MIH level handover aiding procedure.
7.4.23.4 	MIH_MN_HO_Complete.confirm
7.4.23.4.1 	Function
This primitive is used by MIHF to inform MIH Users locally that an MIH_MN_HO_Complete response message is received. 
7.4.23.4.2 	Semantics of service primitive
MIH_MN_HO_Complete.confirm (
				SourceIdentifier,
				CurrentLinkIdentifier,
				Status
				)
Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	Shall contain the MIHF ID of the node that sent the MIH_MN_HO_Complete response message.	
Current Link Identifier	LINK_TUPLE_ID	This identifies the current link over which the command needs to be sent. 	
Status			STATUS	Status of operation.	

7.4.23.4.3 	When generated
This primitive may be generated when MIH_MN_HO_Commit response message is received.
7.4.23.4.4 	Effect on receipt
This indicates the completion of the MIH level handover aiding procedure.
7.4.24 	MIH_N2N_HO_Complete
7.4.24.1 	MIH_N2N_HO_Complete.request
7.4.24.1.1 	Function
This primitive is used by an MIH User in the network to communicate with a peer network MIH entity about the completion of handover operation.
7.4.24.1.2 	Semantics of service primitive
MIH_N2N_HO_Complete.request
 	(
				DestinationIdentifier,
				CurrentLinkIdentifier,
				HandoverResult
				)

Parameters:

Name	
Type	
Description	
Destination Identifier	MIHF_ID	Shall contain the MIHF ID of the node that sent the MIH_N2N_HO_Complete request message. 	
Current Link Identifier	LINK_TUPLE_ID	
This identifies the current link over which the command needs to be sent. This parameter is included only for the case where the accompanying MIH_N2N_HO_Complete request message is transferred between the mobile node and the Serving PoS.	
Handover Result	HANDOVER_RESULT	Handover result.	

7.4.24.1.3 	When generated
The MIH User invokes this primitive when handover operations to the new network PoA have been completed.
7.4.24.1.4 	Effect on receipt
Upon receipt of this primitive by the local MIHF, it shall generate and send an MIH_N2N_HO_Complete request message to the remote MIHF identified by the Destination Identifier.
7.4.24.2 	MIH_N2N_HO_Complete.indication
7.4.24.2.1 	Function
This primitive is generated by the MIHF to indicate the status of the handover operation.
7.4.24.2.2 	Semantics of service primitive
MIH_N2N_HO_Complete.indication(
SourceIdentifier,
CurrentLinkIdentifier,
HandoverResult
)
Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	Shall contain the MIHF ID of the node that sent the MIH_N2N_HO_Complete request message.	
Current Link Identifier	LINK_TUPLE_ID	
This identifies the current link over which the command needs to be sent. This parameter is included only for the case where the accompanying MIH_N2N_HO_Complete request message is transferred between the mobile node and the Serving PoS.	
Handover Result	HANDOVER_RESULT	Handover result.	

7.4.24.2.3 	When generated
This primitive is generated by the MIHF on receiving an MIH_N2N_HO_Complete request message from a peer MIHF.
7.4.24.2.4 	Effect on receipt
The MIH User receiving this primitive replies with an MIH_N2N_HO_Complete.response primitive.
7.4.24.3 	MIH_N2N_HO_Complete.response
7.4.24.3.1 	Function
This primitive is used to send a response to a handover complete request.
7.4.24.3.2 	Semantics of service primitive
MIH_N2N_HO_Complete.response (
				DestinationIdentifier,
				CurrentLinkIdentifier,
				ResourceStatus,
				Status
				)

Parameters:

Name	
Type	
Description	
Destination Identifier	MIHF_ID	Shall contain the MIHF ID of the node that sent the MIH_N2N_HO_Complete response message. 	
Current Link Identifier	LINK_TUPLE_ID	
This identifies the current link over which the command needs to be sent. This parameter is included only for the case where the accompanying MIH_N2N_HO_Complete response message is transferred between the mobile node and the Serving PoS. 	
Resource Status	LINK_RESOURCE_RETENTION_STATUS	Status of resource.	
Status			STATUS	Status of operation.	

7.4.24.3.3 	When generated
The MIHF responds with this primitive after processing the handover complete request.
7.4.24.3.4 	Effect on receipt
Upon receipt, the MN MIHF may determine that the handover complete request was processed successfully. Upon receipt, the MIHF in the new network may forward this message to the MN.
7.4.24.4 	MIH_N2N_HO_Complete.confirm
7.4.24.4.1 	Function
This primitive is generated by the MIHF to confirm that an MIH_N2N_HO_Complete response message is received from a peer MIHF.
7.4.24.4.2 	Semantics of service primitive
MIH_N2N_HO_Complete.confirm 	(
				SourceIdentifier,
				CurrentLinkIdentifier,
				ResourceStatus,
				Status
				)
Parameters:
Name	Type	Description	
Source Identifier	MIHF_ID	Shall contain the MIHF ID of the node that sent the MIH_N2N_HO_Complete response message.	
Current Link Identifier	LINK_TUPLE_ID	
This identifies the current link over which the command needs to be sent. This parameter is included only for the case where the accompanying MIH_N2N_HO_Complete response message is transferred between the mobile node and the Serving PoS. 	
Resource Status	LINK_RESOURCE_RETENTION_STATUS	Status of resource	
Status			STATUS	Status of operation.	

7.4.24.4.3 	When generated
This primitive is generated by MIHF on receiving MIH_N2N_HO_Complete response message from a peer MIHF.
7.4.24.4.4 	Effect on receipt
Upon receipt, the MN upper layer entity may determine that the handover complete request was processed successfully. Upon receipt, the MIHF in the new network may forward this message to the MN. However, if Status does not indicate “Success”, the recipient shall ignore any other returned values and, instead, shall perform appropriate error handling.
7.4.25 	MIH_Get_Information
7.4.25.1 	MIH_Get_Information.request 
7.4.25.1.1 	Function
This primitive is used by an MIH User to request information from an MIH information server. The information query may be related to a specific interface, attributes to the network interface, as well as the entire network capability. The service primitive has the flexibility to query either a specific data within a network interface or extended schema of a given network. 
7.4.25.1.2 	
7.4.25.1.2 	Semantics of service primitive
MIH_Get_Information.request
 				(
				DestinationIdentifier,
				InfoQueryBinaryDataList,
				InfoQueryRDFDataList,
				InfoQueryRDFSchemaURL,
				InfoQueryRDFSchemaList,
				MaxResponseSize
			 	)
Parameters:

Name	
Type	Description	
Destination Identifier	MIHF_ID	The local MIHF or a remote MIHF which will be the destination of this request. 	

Info Query Binary Data List	LIST(INFO_QUERY_BINARY_DATA)	A list of binary queries	

Info Query RDF Data List	LIST(INFO_QUERY_RDF_DATA)	A list of RDF queries	

Info Query RDF Schema URL	NULL	An RDF Schema URL query.	

Info Query RDF Schema List	LIST(INFO_QUERY_RDF_SCHEMA)	A list of RDF schema queries	
Max Response Size	UNSIGNED_INT(2)	(Optional) This field specifies the maximum size of InfoQueryParameters in MIH_Get_Information response primitive in octets. If this field is not specified, the maximum size is set to 65,535. The actual maximum size forced by the IS server may be smaller than that specified by the IS client. 	

7.4.25.1.3 	When generated
This primitive is generated by an MIH User that is seeking to retrieve information.
7.4.25.1.4 	Effect on receipt
The recipient will forward the query in an MIH message to the designated MIIS server. The MIIS server tries to interpret the query request and retrieve the specified information. 
7.4.25.2 	MIH_Get_Information.indication
7.4.25.2.1 	Function
This primitive is generated by the MIHF to indicate that an MIH_Get_Information Request message is received from a peer MIHF.
7.4.25.2.2 	Semantics of service primitive
MIH_Get_Information.indication (
				SourceIdentifier,
				InfoQueryBinaryDataList,
				InfoQueryRDFDataList,
				InfoQueryRDFSchemaURL,
				InfoQueryRDFSchemaList,
				MaxResponseSize
			 	)
Parameters:

Name	
Type	Description	
Source Identifier	MIHF_ID	Shall contain the MIHF ID of the node that invoked MIH_GET_Information.request.	

Info Query Binary Data List	LIST(INFO_QUERY_BINARY_DATA)	A list of binary queries	

Info Query RDF Data List	LIST(INFO_QUERY_RDF_DATA)	A list of RDF queries	

Info Query RDF Schema URL	NULL	An RDF Schema URL query.	

Info Query RDF Schema List	LIST(INFO_QUERY_RDF_SCHEMA)	A list of RDF schema queries	
Max Response Size	UNSIGNED_INT(2)	(Optional) This field specifies the maximum size of InfoQueryParameters in MIH_Get_Information response primitive in octets. If this field is not specified, the maximum size is set to 65,535. The actual maximum size forced by the IS server may be smaller than that specified by the IS client. 	

7.4.25.2.3 	When generated
This primitive is generated by the MIHF on receiving an MIH_Get_Information request message from a peer MIHF.
7.4.25.2.4 	Effect on receipt
The recipient tries to interpret the query request and retrieve the specified information. Once the information is retrieved, the recipient replies with the MIH_Get_Information.response primitive.
7.4.25.3 	MIH_Get_Information.response
7.4.25.3.1 	Function
This primitive is used by an MIH User to respond to an MIH_GET_Information.indication primitive.
7.4.25.3.2 	Semantics of service primitive
MIH_Get_Information.response
 (
				DestinationIdentifier,
				InfoResponseBinaryDataList,
				InfoResponseRDFDataList,
				InfoResponseRDFSchemaURL,
				InfoResponseRDFSchemaList,
				Status
			 	)
Parameters:

Name	
Type	Description	
Destination Identifier	MIHF_ID	The local MIHF or a remote MIHF which will be the destination of this response. 	

Info Response Binary Data List	LIST(INFO_RSP_BINARY_DATA)	A list of binary query responses.	

Info Response RDF Data List	LIST(INFO_RSP_RDF_DATA)	A list of RDF query responses	

Info Response RDF Schema URL	LIST(INFO_RSP_RDF_URL)	A list of RDF Schema URL.	

Info Response RDF Schema List	LIST(INFO_RSP_RDF_SCHEMA)	A list of RDF schema query responses.	
Status	STATUS	Status of operation.
The response lists contains meaningful data if and only if the status is ‘0’	

7.4.25.3.3 	When generated
This primitive is generated by an MIH User in response to an received MIH_Get_Information request.
7.4.25.3.4 	Effect on receipt
The MIH User that requested the information tries to interpret the InfoQueryResponse and take suitable action. However, if Status does not indicate “Success”, the recipient shall ignore any other returned values and, instead, shall perform appropriate error handling.
7.4.25.4 	MIH_Get_Information.confirm
7.4.25.4.1 	Function
This primitive is generated by the MIH to respond to an MIH_GET_Information.request primitive.
7.4.25.4.2 	Semantics of service primitive
MIH_Get_Information.confirm 				(
				SourceIdentifier,
				InfoResponseBinaryDataList,
				InfoResponseRDFDataList,
				InfoResponseyRDFSchemaURL,
				InfoResponseRDFSchemaList,
				Status
			 	)
Parameters:

Name	
Type	Description	
Source Identifier	MIHF_ID	Shall contain the MIHF ID of the node that invoked MIH_GET_Information.response.	

Info Response Binary Data List	LIST(INFO_RSP_BINARY_DATA)	A list of binary query responses.	

Info Response RDF Data List	LIST(INFO_RSP_RDF_DATA)	A list of RDF query responses	

Info Response RDF Schema URL	LIST(INFO_RSP_RDF_URL)	A list of RDF Schema URL.	

Info Response RDF Schema List	LIST(INFO_RSP_RDF_SCHEMA)	A list of RDF schema query responses.	
Status	STATUS	Status of operation.
The response lists contains meaningful data if and only if the status is ‘0’	

7.4.25.4.3 	When generated
This primitive is generated by the MIHF on receiving an MIH_Get_Information Response message from a peer MIHF.
7.4.25.4.4 	Effect on receipt
The MIH User that requested the information tries to interpret the InfoQueryResponse and takes suitable action. However, if Status does not indicate “Success”, the recipient shall ignore any other returned values and, instead, shall perform appropriate error handling.
7.5 	MIH-3GLINK-SAP primitives
Primitives are a conceptual representation of functions that are invoked across protocol layers. MIH-3GLINK-SAP primitives are part of a larger set of primitives that run from the MIHF to the relevant link layer technology across a conceptual SAP referred to as MIH-LINK-SAP. This is depicted in Table L-3.
7.6 	MIH_NET_SAP primitives
7.6.1 	MIH_TP_Data
The primitives associated with data transfers are as follows:
- MIH_TP_Data.request
- MIH_TP_Data.indication
- MIH_TP_Data.confirm
The MIHF uses the MIH_TP_Data.request primitive to request that an MIH PDU be transported. The transport service provider uses the MIH_TP_Data.indication primitive to indicate the arrival of an MIH PDU. MIH_TP_Data.response and MIH_TP_Data.confirm primitives are used to acknowledge the receipt of the MIH PDU only when the sending MIHF requested the MIH PDU be sent reliably.
7.6.1.1 	MIH_TP_Data.request
7.6.1.1.1 	Function
This primitive is the request for transfer of an MIH PDU.
7.6.1.1.2 	Semantics
MIH_TP_Data.request 			(
			TransportType,
			SourceAddress,
			DestinationAddress,
			ReliableDeliveryFlag,
			MIHProtocolPDU
		 	)

Parameters:

Name	Type	Description	
Transport Type	TRANSPORT_TYPE	Identifies the protocol layer specific transport option	
Source Address	TRANSPORT_ADDRESS	Protocol layer specific Transport Address of entity which has the Source MIHF	
Destination Address	TRANSPORT_ADDRESS	Protocol layer specific Transport Address of entity which has the Destination MIHF	
Reliable Delivery Flag	BOOLEAN	Indicate that the data shall be sent reliably and an error is generated if delivery fails.
True: Reliable delivery is required.
False: Reliable delivery is not required.	
MIH Protocol PDU	OCTECT_STRING	MIH Protocol PDU to be transferred	

7.6.1.1.3 	When generated
This primitive is used to request that an MIH PDU be transported to a remote MIHF.
7.6.1.1.4 	Effect on receipt
The receipt of this primitive causes the selected transport service provider to attempt to transport the MIH PDU.
7.6.1.2 	MIH_TP_Data.indication
7.6.1.2.1 	Function
This primitive is the indication for transfer of an MIH PDU.
7.6.1.2.2 	Semantics
MIH_TP_Data.indication 			(
			TransportType,
			SourceAddress,
			DestinationAddress,
			ReliableDeliveryFlag,
			MIHProtocolPDU
			)

Parameters:
Name	Type	Description	
Transport Type	TRANSPORT_TYPE	Identifies the protocol layer specific transport option	
Source Address	TRANSPORT_ADDRESS	Protocol layer specific Transport Address of entity which has the Source MIHF	
Destination Address	TRANSPORT_ADDRESS	Protocol layer specific Transport Address of entity which has the Destination MIHF	
Reliable Delivery Flag	BOOLEAN	Indicate that the data shall be sent reliably and an error generated if delivery fails.
True: Reliable delivery is required.
False: Reliable delivery is not required.	
MIH Protocol PDU	OCTECT_STRING	MIH Protocol PDU received.	

7.6.1.2.3 	When generated
This primitive is used by the transport service provider to indicate that an MIH PDU has been received from a remote MIHF.
7.6.1.2.4 	Effect on receipt
The receipt of this primitive causes the MIHF to receive the MIH PDU that was transported. If the Reliable Delivery Flag is set to TRUE, the MIHF shall respond with an MIH_TP_Data.response primitive.
7.6.1.3 	MIH_TP_Data.confirm
7.6.1.3.1 	Function
This primitive is used to confirm an acknowledged transfer.
7.6.1.3.2 	Semantics
MIH_TP_Data.confirm 			(
			TransportType,
			SourceAddress,
			DestinationAddress,
			Status
		 	)
Parameters:

Name	Type	Description	
Transport Type	TRANSPORT_TYPE	Identifies the protocol layer specific transport option.	
Source Address	TRANSPORT_ ADDRESS	Protocol layer specific Transport Address of entity which has the Source MIHF	
Destination Address	TRANSPORT_ADDRESS	Protocol layer specific Transport Address of entity which has the Destination MIHF	
Status			STATUS	Status of operation.	

7.6.1.3.3 	When generated
This primitive is passed from the transport service provider to the MIHF to confirm that a request to transfer an MIH PDU succeeded. 
7.6.1.3.4 	Effect on receipt
Upon receipt of this primitive, the receiving MIHF may stop its retransmission timer for the corresponding request. When the MIHF does not receive this primitive for a pre-defined time after transmitting an MIH_TP_Data.request with ReliableDeliveryFlag set to TRUE, the MIHF may try to retransmit the MIH_TP_Data.request.
7.7 	MIH_NMS_SAP primitives
MIH_NMS_SAP provides primitives for NMS to monitor and configure the MIHF. 
7.7.1 	MIH_NMS_Initialize
The following primitives are used to initialize the MIHF:
—		MIH_NMS_Initialize.request
—		MIH_NMS_Initialize.confirm
NMS sends the MIH_NMS_Initialize.request to set the MIHF to the initial working state. The MIHF responds with the MIH_NMS_Initialize.confirm primitive.
7.7.1.1 	MIH_NMS_Initialize.request
7.7.1.1.1 	Function
This primitive is used by NMS to initialize MIHF.
7.7.1.1.2 	Semantics
This primitive contains no parameters.
MIH_NMS_Initialize.request 				(
				)
7.7.1.1.3 	When generated
This primitive is generated by the NMS when it needs to initialize the MIHF.
7.7.1.1.4 	Effect on receipt
MIHF executes initialization.
7.7.1.2 	MIH_NMS_Initialize.confirm
7.7.1.2.1 	Function
This primitive returns the result of the MIHF initialization.
7.7.1.2.2 	Semantics
MIH_NMS_Initialize.confirm   				(
				Status
				)
Parameter:

Name	Type	Description	
Status			STATUS	Result of MIHF initialization.	

7.7.1.2.3 	When generated
This primitive is generated by the MIHF when the MIHF has processed an MIH_NMS_Initialize.request from the NMS.
7.7.1.2.4 	Effect on receipt
NMS may confirm whether the MIHF works or not. 
7.7.2 	MIH_NMS_Get_State
The primitives associated with retrieval of MIHF state information are as follows:
—		MIH_NMS_Get_State.request
—		MIH_NMS_Get_State.confirm
NMS uses the MIH_NMS_Get_State.request primitive to get the state information from the MIHF. The MIHF uses the MIH_NMS_Get_State.confirm primitive to send the state information to the NMS. 
The state information may include information as follows:
[Editor’s note: this is the definition for NMS_STATE_REQ and NMS_STATE_RSP]
—		Link level state information
•  	Subscribed link layer events
•  	Link Configuration Thresholds (Link Parameter Type, Initiate Action Threshold, Rollback Action Threshold, Execute Action Threshold)
•  	Link status (Up/Going Down/Down)
•  	Link Handover status (Imminent/Complete)
•  	Link Capability (Supported MIES/MICS List)
•  	Link Parameters (RSSI, NDR, C/I, BER, PER, Link Data Rate)
—		Upper layer specific information 
•  	MIH Capability (Supported MIES/MICS/MIIS List)
•  	MIH Status (Device Info, Operation Mode, Link ID, Channel ID, Battery Level, Link QoS Parameter List)
•  	MIH Handover status
—		Transport specific information
•  	Connectivity of data transfer session (Connect/Disconnect)
7.7.2.1 	MIH_NMS_Get_State.request
7.7.2.1.1 	Function
This primitive is used by the NMS to get the state information.
7.7.2.1.2 	Semantics
MIH_NMS_Get_State.request   				(
				StateInformationRequestList
				)
Parameter:

Name	Type	Description	
State Information Request List	LIST(NMS_STATE_REQ)	List of the state information to be queried	

7.7.2.1.3 	When generated
This primitive is generated by the NMS when it needs to get the state information from the MIHF.
7.7.2.1.4 	Effect on receipt
The MIHF collects the requested information.
7.7.2.2 	MIH_NMS_Get_State.confirm
7.7.2.2.1 	Function
This primitive returns the state information to the NMS.
7.7.2.2.2 	Semantics
MIH_NMS_Get_State.confirm 				(
				StateInformationResponseList,
				Status
				)
Parameters:

Name	Type	Description	
State Information Response List	LIST(NMS_STATE_RSPRSP)	A list of a pair of {state information; state information value}.	
Status			STATUS	Status of operation.	

7.7.2.2.3 	When generated
This primitive is generated by the MIHF when the MIHF receives an MIH_NMS_Get_State.request from the NMS.
7.7.2.2.4 	Effect on receipt
The NMS may manage the MIHF based on the state information.
7.7.3 	MIH_NMS_Reset
The following primitives are used to reset the MIHF:
—		MIH_NMS_Reset.request
—		MIH_NMS_Reset.confirm
The NMS sends the MIH_NMS_Reset.request to set the MIHF to the initial working state. The MIHF responds with the MIH_NMS_Reset.confirm primitive.
7.7.3.1 	MIH_NMS_Reset.request
7.7.3.1.1 	Function
This primitive is used by the NMS to reset the MIHF.
7.7.3.1.2 	Semantics
This primitive has no parameters.
MIH_NMS_Reset.request ()
7.7.3.1.3 	When generated
This primitive is generated by the NMS when it needs to reset the MIHF.
7.7.3.1.4 	Effect on receipt
The MIHF resets and enters initial state. 
7.7.3.2 	MIH_NMS_Reset.confirm
7.7.3.2.1 	Function
This primitive returns the result of resetting the MIHF.
7.7.3.2.2 	Semantics
MIH_NMS_Reset.confirm (
			 Status
			)
Parameter:

Name	Type	Description	
Status			STATUS	Status of operation.	

7.7.3.2.3 	When Generated
This primitive is generated by the MIHF when the MIHF has processed an MIH_NMS_Reset.request from the NMS.
7.7.3.2.4 	Effect on receipt
The NMS may confirm whether the MIHF has been reset or not and whether it is operational.