# Patent

## Title
Method and apparatus for mapping 3GPP service primitives to media independent handover event services

## Abstract

A Third Generation Partnership Project (3GPP) media independent handover (MIH) service access point (SAP) is configured to provide MIH event services, (e.g., IEEE 802.21 event services), by mapping service primitives to the MIH event services. The service primitives may be 3GPP service primitives which originate from at least one of a radio resources (RR) layer, a logical link control (LLC) layer, a general packet radio service (GPRS) mobility management (GMM) layer, a session management (SM) layer, a non-access stratum (NAS), an access stratum (AS) and an evolved universal terrestrial radio access (E-UTRA)/evolved core network (E-CORE) system. The event services may include a link parameter change event service, a link up event service, a link going down event service, a link down event service, a handover complete event service and a link detected event service.

## Background
CROSS REFERENCE TO RELATED APPLICATION
This application is a continuation of U.S. patent application Ser. No. 11/554,392, filed on Oct. 30, 2006, which claims the benefit of U.S. Provisional Ser. No. Application No. 60/733,703, filed on Nov. 4, 2005, each of which is incorporated by reference as if fully set forth herein.


FIELD OF INVENTION
The present invention relates to wireless communication systems. More particularly, the present invention relates to mapping of Third Generation Partnership Project (3GPP) service primitives to media independent handover (MIH) event services as defined within the IEEE 802.21 standard.
BACKGROUND
The IEEE 802.21 standard relates to mechanisms and procedures that aid in the execution and management of inter-system handovers. Under the IEEE 802.21 standard, three main services can be accessed by mobility management (MM) applications in order to aid in the management of handover operations and system discovery and system selection. These three services include an event service, an information service and a command service, which are delivered to prospective users using a common uniform interface, regardless of the underlying access technologies supporting the communication towards the core network.
A method which supports the delivery of event services is needed to determine when an event is to be triggered based on the prevailing characteristics of the underlying technology. The underlying technology could be supported by the 3GPP specification, 3GPP2 and wireless local area networks (WLANs), (e.g., IEEE 802.11 or IEEE 802.16), and the like.
Currently, there are no procedures or functionality to generate triggers toward upper layers, based on information provided by the 3GPP underlying layers. The IEEE 802.21 specification outlines triggers that should be sent to upper layers. However, the IEEE 802.21 specification does not describe how events are triggered when the underlying physical resources are based on 3GPP technology. Therefore a method capable generating these triggers is required.
SUMMARY
The present invention is related to a 3GPP-MIH service access point (SAP) which is configured to provide MIH event services, (e.g., IEEE 802.21 event services), by mapping service primitives to the MIH event services. The service primitives may be 3GPP service primitives which originate from at least one of a radio resources (RR) layer, a logical link control (LLC) layer, a general packet radio service (GPRS) mobility management (GMM) layer, a session management (SM) layer, a non-access stratum (NAS), an access stratum (AS) and an evolved universal terrestrial radio access (E-UTRA)/evolved core network (E-CORE) system. The event services may include a link parameter change event service, a link up event service, a link going down event service, a link down event service, a handover complete event service and a link detected event service.
The present invention uses existing service primitives already defined within 3GPP in order to trigger events that can be used for the determination of handover operations. These service primitives are mapped onto concrete IEEE 802.21 events as defined in IEEE 802.21, as a means to optimize inter-system handover operations.
The present invention provides a method to trigger MIH events, using existing 3GPP radio resource management (RRM), MM and session management (SM) service primitives. The concept of service primitives mapping is extended using mobility management procedures and concepts introduced within both long term evolution (LTE) and system architecture evolution (SAE) within the 3GPP specifications.
The present invention may be applicable to IEEE 802 standards including WLAN baseline air interface standards such as IEEE 802.11 baseline, IEEE 802.11a orthogonal frequency division multiplex (OFDM) 5 GHz WLAN, IEEE 802.11b high rate direct sequence spread spectrum (HR-DSSS) 2.4 GHz WLAN, IEEE 802.11g OFDM 2.4 GHz WLAN, IEEE 802.11j OFDM 10 MHz option WLAN, IEEE 802.11n high-throughput WLAN, and IEEE 802.16 broadband wireless access systems. The WLAN standards supplement to extend operation for particular scenarios such as IEEE 802.21 MIH.
The present invention is also applicable to cellular standards, such as 3GPP or 3GPP2, and other standardized or proprietary wireless technologies similar to IEEE 802 WLANs, examples notably include 802.15 Bluetooth, and HIPERLAN/2.



BRIEF DESCRIPTION OF THE DRAWINGS
A more detailed understanding of the invention may be had from the following description of a preferred embodiment, given by way of example and to be understood in conjunction with the accompanying drawings wherein:
FIG. 1 shows an 3GPP-MIH SAP which maps 3GPP service primitives, received from various 3GPP entities, to MIH event services in accordance with the present invention;
FIG. 2 is an exemplary block diagram of the MIH-GPP SAP of FIG. 1;
FIG. 3 is an example of mapping a 3GPP service primitive to an MIH event service when a page is received by an RR layer;
FIG. 4 is an example of mapping a 3GPP service primitive to an MIH event service when data supporting a specific quality of service (QoS) is received by the RR layer;
FIG. 5 is an example of mapping a 3GPP service primitive to an MIH event service when a peer LLC layer is established;
FIG. 6 is an example of mapping a 3GPP service primitive to an MIH event service when a peer LLC layer is released;
FIG. 7 is an example of mapping a 3GPP service primitive to an MIH event service when an LLC layer unrecoverable error occurs;
FIG. 8 is an example of mapping a 3GPP service primitive to an MIH event service when a GMM layer indicates that a station is attached;
FIG. 9 is an example of mapping a 3GPP service primitive to an MIH event service when a GMM layer indicates that a station is detached;
FIG. 10 is an example of mapping a 3GPP service primitive to an MIH event service when an SM layer indicates that a data session is active;
FIG. 11 is an example of mapping a 3GPP service primitive to an MIH event service when an SM layer indicates that a data session is deactivated;
FIG. 12 is an example of mapping a 3GPP service primitive to an MIH event service when an SM layer indicates that a data session is modified;
FIG. 13 is an example of mapping a 3GPP service primitive to an MIH event service when an SM layer indicates that a data session is terminated due to an unrecoverable error;
FIG. 14 is an example of mapping a 3GPP service primitive to an MIH event service when an SM layer indicates that a packet data protocol (PDP) context is active;
FIG. 15 is an example of mapping a 3GPP service primitive to an MIH event service when an SM layer indicates that a PDP context is modified;
FIG. 16 is an example of mapping a 3GPP service primitive to an MIH event service when an SM layer indicates that a PDP context is deactivated;
FIG. 17 is an example of mapping a 3GPP service primitive to an MIH event service when an NAS indicates that a station is attached;
FIG. 18 is an example of mapping a 3GPP service primitive to an MIH event service when an NAS indicates that a station is detached;
FIG. 19 is an example of mapping a 3GPP service primitive to an MIH event service when an NAS indicates that a PDP context is active;
FIG. 20 is an example of mapping a 3GPP service primitive to an MIH event service when an NAS indicates that a PDP context is modified;
FIG. 21 is an example of mapping a 3GPP service primitive to an MIH event service when an NAS indicates that a PDP context is deactivated;
FIG. 22 is an example of mapping a 3GPP service primitive to an MIH event service when an NAS indicates that a radio access bearer (RAB) is activated for data transfer;
FIG. 23 is an example of mapping a 3GPP service primitive to an MIH event service when an NAS indicates that a RAB is deactivated for data transfer;
FIG. 24 is an example of mapping a 3GPP service primitive to an MIH event service when an NAS indicates that a RAB is modified for data transfer;
FIG. 25 is an example of mapping a 3GPP service primitive to an MIH event service when an NAS indicates that a RAB data transfer error has occurred;
FIG. 26 is an example of mapping a 3GPP service primitive to an MIH event service when an AS indicates that a RAB has been activated;
FIG. 27 is an example of mapping a 3GPP service primitive to an MIH event service when an AS indicates that a RAB has been released;
FIG. 28 is an example of mapping a 3GPP service primitive to an MIH event service when an AS failure occurs;
FIG. 29 is an example of mapping a 3GPP service primitive to an MIH event service when an AS broadcasts information regarding a geographic area;
FIG. 30 is an example of mapping a 3GPP service primitive to an MIH event service when an AS provides notification of paging for a particular user or terminal;
FIG. 31 is an example of mapping a 3GPP service primitive to an MIH event service when an AS provides a notification for all users;
FIG. 32 is an example of mapping a 3GPP service primitive to an MIH event service when an AS provides notification information for one or more users;
FIG. 33 is an example of mapping a 3GPP service primitive to an MIH event service when an AS indicates a user equipment (UE) initiated connection establishment;
FIG. 34 is an example of mapping a 3GPP service primitive to an MIH event service when an AS indicates a network initiated connection release;
FIG. 35 is an example of mapping a 3GPP service primitive to an MIH event service when an AS indicates a network initiated RAB establishment;
FIG. 36 is an example of mapping a 3GPP service primitive to an MIH event service when an AS indicates a network initiated RAB release;
FIG. 37 is an example of mapping a 3GPP service primitive to an MIH event service when an AS indicates the potential for an aborted connection unless streamlining is performed;
FIG. 38 is an example of mapping a 3GPP service primitive to an MIH event service when an AS indicates location information provided by a network for a specific UE;
FIG. 39 is an example of mapping a 3GPP service primitive to an MIH event service when an AS indicates a connection loss;
FIG. 40 is an example of mapping a 3GPP service primitive to an MIH event service when an E-UTRA/E-CORE system indicates that the location of a UE is now known by a network;
FIG. 41 is an example of mapping a 3GPP service primitive to an MIH event service when an E-UTRA/E-CORE system indicates that the location of a UE is known to a network but no transport channel is established; and
FIG. 42 is an example of mapping a 3GPP service primitive to an MIH event service when an E-UTRA/E-CORE system indicates that radio resources have been established and that a UE is able to perform uplink (UL) and downlink (DL) transport of a protocol data unit (PDU).



DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
The present invention is based on the use existing and new, (e.g., LTE and SAE), primitives within 3GPP that can be mapped onto IEEE 802.21 events as defined by the IEEE 802.21 specification.
A primitive is an abstract representation of functions such as an information function, an event or a command.
An MIH event service classifies, filters and reports changes within the link layer characteristics, (i.e., maximum offered throughput, supported bandwidth, or the like), the link status, (i.e., an indicator of whether the link is operational or not), and the link quality, (e.g., low signal strength). Event services may also indicate changes in the state and transmission behavior of the physical, data link and logical link layers. Furthermore, event services are used to indicate an operation state as a result of a management action.
FIG. 1 is a mapping model for 3GPP layer primitives, where a 3GPP-MIH service access point (SAP) 100 maps 3GPP service primitives to MIH event services according to IEEE 802.xx standards.
As shown in FIG. 1, a radio resources (RR) layer 105, an LLC layer 110, a general packet radio service (GPRS) mobility management (GMM) layer 115, and a session management (SM) layer 120 associated with a global system for mobile communications (GSM)/enhanced data rates for GSM evolution (EDGE) radio access network (GERAN) 125 send 3GPP service primitives 160 to the 3GPP-MIH SAP 100. Furthermore, the non-access stratum (NAS) 130 and the access stratum (AS) 135 of a universal mobile telecommunications system (UMTS) services 140 send 3GPP service primitives 160 to the SAP 100. An LTE system 145 sends 3GPP service primitives 160 via an evolved universal terrestrial radio access (E-UTRA) and evolved core network (E-CORE) layers 155 to the SAP 100. The SAP outputs MIH event services 170 in response to receiving the 3GPP service primitives 160.
FIG. 2 is an exemplary block diagram of the 3GPP-MIH SAP 100 of FIG. 1. The 3GPP-MIH SAP 100 includes a processor 205 and a 3GPP to MIH mapping database 210. When the SAP 100 receives a 3GPP service primitive 160, the processor 205 in the SAP 100 interprets, (i.e., identifies), the 3GPP service primitive 160 in terms of functional capabilities and potential parameters. The processor 205 then queries the mapping database 210 based on such functional capabilities and parameters to obtain and output the MIH event services 170.
Table 1 identifies specific 3GPP service primitives for each of the layers of the GERAN 125 shown in FIG. 1. According to the present invention, the 3GPP service primitives generated by the GERAN 125 via the RR layer 105, the LLC layer 110, the GMM layer 115 and the SM layer 120 are mapped to MIH event services, (e.g., IEEE 802.21 events), as shown in Table 1 below.










TABLE 1






3GPP Service

MIH Event Service


3GPP
Primitive
3GPP Service
(e.g., IEEE 802.21


Layer
Descriptions
Primitive
Event)







RR
Page received by RR layer
GMRR-PAGE
Link Parameter Change



Successful reception of data
GRR-DATA
Link Parameter Change



supporting specific QoS


LLC
Peer LLC layer is
LL-ESTABLISH
Link Up/Link Parameter



established

Change



Peer LLC layer is released
LL-RELEASE
Link Going Down/Link





Parameter Change



LLC Layer unrecoverable
LL-STATUS
Link Down



error


GMM
Station is attached
GMMREG-ATTACH
Link Parameter Change



Station is detached
GMMREG-DETACH
Link Parameter Change


SM
Data session active
SMSM-ACTIVE
Link Up/Link Parameter





Change



Data session is deactivated
SMSM-DEACTIVATE
Link Down/Link Parameter





Change



Data session modified
SMSM-MODIFY
Link Parameter Change



Data session terminated due
SMSM-STATUS
Link Down



to unrecoverable error



PDP Context is active
SMREG-PDP-ACTIVATE
Link Up/Link Parameter





Change/Handover Complete



PDP Context is modified
SMREG-PDP-MODIFY
Link up/Link Parameter





Change/Handover Complete



PDP Context is deactivated
SMREG-PDP-DEACTIVATE
Link Going Down/Link





Down









FIG. 3 is an example of mapping a 3GPP service primitive to an MIH event service when a page is received by the RR layer 105. As indicated by Table 1 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link parameter change event service in response to receiving a 3GPP service primitive from the RR layer 105 that indicates that a page was received by the RR layer 105. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 or the like.
FIG. 4 is an example of mapping a 3GPP service primitive to an MIH event service when data supporting a specific QoS is received by the RR layer 105. As indicated by Table 1 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link parameter change event service in response to receiving a 3GPP service primitive from the RR layer 105 that indicates that data supporting a specific QoS is received by the RR layer 105. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 or the like.
FIG. 5 is an example of mapping a 3GPP service primitive to an MIH event service when a peer LLC layer is established, as indicated by the LLC layer 110. As indicated by Table 1 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link up event service or a link parameter change event service in response to receiving a 3GPP service primitive from the LLC layer 110 that indicates that a peer LLC layer has been established. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 6 is an example of mapping a 3GPP service primitive to an MIH event service when a peer LLC layer 110 is released, as indicated by the LLC layer 110. As indicated by Table 1 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link going down event service or a link parameter change event service in response to receiving a 3GPP service primitive from the LLC layer 110 that indicates that a peer LLC layer has been released. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 7 is an example of mapping a 3GPP service primitive to an MIH event service when an LLC layer unrecoverable error occurs, as indicated by the LLC layer 110. As indicated by Table 1 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link down event service in response to receiving a 3GPP service primitive from the LLC layer 110 that indicates that an LLC layer unrecoverable error has occurred. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 8 is an example of mapping a 3GPP service primitive to an MIH event service when the GMM layer 115 indicates that a station is attached. As indicated by Table 1 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link parameter change event service in response to receiving a 3GPP service primitive from the GMM layer 115 that indicates that a station is attached. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 9 is an example of mapping a 3GPP service primitive to an MIH event service when the GMM layer 115 indicates that a station is detached. As indicated by Table 1 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link parameter change event service in response to receiving a 3GPP service primitive from the GMM layer 115 that indicates that a station is detached. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 10 is an example of mapping a 3GPP service primitive to an MIH event service when the SM layer 120 indicates that a data session is active. As indicated by Table 1 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link up event service or a link parameter change event service in response to receiving a 3GPP service primitive from the SM layer 120 that indicates that a data session is active. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 11 is an example of mapping a 3GPP service primitive to an MIH event service when the SM layer 120 indicates that a data session is deactivated. As indicated by Table 1 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link down event service or a link parameter change event service in response to receiving a 3GPP service primitive from the SM layer 120 that indicates that a data session is deactivated. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 12 is an example of mapping a 3GPP service primitive to an MIH event service when the SM layer 120 indicates that a data session is modified. As indicated by Table 1 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link parameter change event service in response to receiving a 3GPP service primitive from the SM layer 120 that indicates that a data session has been modified. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 13 is an example of mapping a 3GPP service primitive to an MIH event service when the SM layer 120 indicates that a data session is terminated due to an unrecoverable error. As indicated by Table 1 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link down event service in response to receiving a 3GPP service primitive from the SM layer 120 that indicates that a data session has been terminated due to an unrecoverable error. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 14 is an example of mapping a 3GPP service primitive to an MIH event service when the SM layer 120 indicates that a PDP context is active. As indicated by Table 1 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link up event service, a link parameter change event service or a handover complete event service in response to receiving a 3GPP service primitive from the SM layer 120 that indicates that a PDP context is active. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 15 is an example of mapping a 3GPP service primitive to an MIH event service when the SM layer 120 indicates that a PDP context is modified. As indicated by Table 1 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link up event service, a link parameter change event service or a handover complete event service in response to receiving a 3GPP service primitive from the SM layer 120 that indicates that a PDP context has been modified. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 16 is an example of mapping a 3GPP service primitive to an MIH event service when the SM layer 120 indicates that a PDP context is deactivated. As indicated by Table 1 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link going down event service or a link down event service in response to receiving a 3GPP service primitive from the SM layer 120 that indicates that a PDP context has been deactivated. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
Table 2 identifies specific 3GPP service primitives for each of the layers of the UMTS 140 and the LTE system 145 shown in FIG. 1. According to the present invention, the 3GPP service primitives generated by the UMTS 140 via the NAS 130 and the AS 135, as well as the 3GPP service primitives generated by the LTE via the E-UTRA/E-CORE system 150, are mapped to MIH event services, (e.g., IEEE 802.21 events), as shown in Table 2 below.










TABLE 2






3GPP Service

MIH Event Service


3GPP
Primitive
3GPP Service
(e.g., IEEE 802.21


Layer
Descriptions
Primitive
Event)







NAS
Station is attached
GMMREG-
Link Parameter




ATTACH
Change



Station is detached
GMMREG-
Link Parameter




DETACH
Change



PDP Context is
SMREG-PDP-
Link Up/Handover



active
ACTIVATE
Complete/Link





Parameter Change



PDP Context is
SMREG-PDP-
Link Parameter



modified
MODIFY
Change/Link Up



PDP Context is
SMREG-PDP-
Link Down/Link



deactivated
DEACTIVATE
Parameter Change



Radio Access Bearer
RABMSM-
Link Up/Link



is activated for data
ACTIVATE
Parameter Change/



transfer

Handover Complete



Radio Access Bearer
RABMSM-
Link Down/Link



is deactivated for
DEACTIVATE
Link Parameter



data transfer

Change



Radio Access Bearer
RABMSM-MODIFY
Link Parameter



is modified for data

Change/Link Up/



transfer

Handover Complete



Radio Access Bearer
RABMSM-STATUS
Link Down



data transfer error


AS
Radio Access Bearer
RABMAS-RAB-
Link Up/Handover



has been activated
ESTABLISH
Complete



Radio Access Bearer
RABMAS-RAB-
Link Down



has been released
RELEASE



AS failure
RABMAS-STATUS
Link Down



Indication



Information
Information
Link Parameter



regarding
Broadcast
Change



geographical area.



Notification of
Paging Request
Link Parameter



paging for particular

Change



user or terminal



Notification
Notification
Link Parameter



information for all
Broadcast
Change



users



Notification
Notification
Link Parameter



information for a
Indication
Change



specific or for many



user



UE initiated
Connection
Link Up



connection
Establishment



establishment



Network initiated
Infrastructure Side
Link Down



connection release
Initiated




Connection Release



Network initiated
Infrastructure Side
Link Up/Link



Radio Access Bearer
Initiated Radio
Detected



Establishment
Access Bearer




Establishment



Network initiated
Infrastructure Side
Link Down



Radio Access Bearer
Initiated Radio



Release
Access Bearer




Release



Indication that the
Streamlining
Link Going Down



connection may be
Required Indication



aborted unless



streamlining is done



Location information
UE location
Link Parameter



provided by the
information
Change



network for a specific



UE



Connection loss
Connection loss
Link Down



indications
indication


E-
The location of the
LTE-detached
Link Parameter


UTRAN/E-
UE is now known by

Change


CORE
the network



The UE is known to
LTE-idle
Link Parameter



the network but no

Change/Link Down



transport channel is



established



Radio resources have
LTE-Active
Link Up/Link



been established and

Handover Complete



the UE is able to



perform UL and DL



transport of PDU









FIG. 17 is an example of mapping a 3GPP service primitive to an MIH event service when the NAS 130 indicates that a station is attached. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link parameter change event service in response to receiving a 3GPP service primitive from the NAS 130 that indicates that a station is attached. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 18 is an example of mapping a 3GPP service primitive to an MIH event service when the NAS 130 indicates that a station is detached. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link parameter change event service in response to receiving a 3GPP service primitive from the NAS 130 that indicates that a station is detached. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 19 is an example of mapping a 3GPP service primitive to an MIH event service when the NAS 130 indicates that a PDP context is active. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link up event service, a handover complete event service or a link parameter change event service in response to receiving a 3GPP service primitive from the NAS 130 that indicates that a PDP context is active. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 20 is an example of mapping a 3GPP service primitive to an MIH event service when the NAS 130 indicates that a PDP context is modified. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link parameter change event service or a link up event service in response to receiving a 3GPP service primitive from the NAS 130 that indicates that a PDP context is modified. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 21 is an example of mapping a 3GPP service primitive to an MIH event service when the NAS 130 indicates that a PDP context is deactivated. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link down event service or a link parameter change event service in response to receiving a 3GPP service primitive from the NAS 130 that indicates that a PDP context is deactivated. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 22 is an example of mapping a 3GPP service primitive to an MIH event service when the NAS 130 indicates that a RAB is activated for data transfer. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link up event service, a link parameter change event service or a handover complete event service in response to receiving a 3GPP service primitive from the NAS 130 that indicates that a RAB is activated for data transfer. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 23 is an example of mapping a 3GPP service primitive to an MIH event service when the NAS 130 indicates that a RAB is deactivated for data transfer. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link down event service or a link parameter change event service in response to receiving a 3GPP service primitive from the NAS 130 that indicates that a RAB is deactivated for data transfer. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 24 is an example of mapping a 3GPP service primitive to an MIH event service when the NAS 130 indicates that a RAB is modified for data transfer. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link parameter change event service, a link up event service or a handover complete event service in response to receiving a 3GPP service primitive from the NAS 130 that indicates that a RAB is modified for data transfer. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 25 is an example of mapping a 3GPP service primitive to an MIH event service when the NAS 130 indicates that a RAB data transfer error has occurred. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link down event service in response to receiving a 3GPP service primitive from the NAS 130 that indicates that a RAB data transfer error has occurred. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 26 is an example of mapping a 3GPP service primitive to an MIH event service when the AS 135 indicates that a RAB has been activated. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link up event service or a handover complete event service in response to receiving a 3GPP service primitive from the NAS 130 that indicates that a RAB has been activated. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 27 is an example of mapping a 3GPP service primitive to an MIH event service when the AS 135 indicates that a RAB has been released. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link down event service in response to receiving a 3GPP service primitive from the AS 135 that indicates that a RAB has been released. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 28 is an example of mapping a 3GPP service primitive to an MIH event service when a failure of the AS 135 occurs. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link down event service in response to receiving a 3GPP service primitive from the AS 135 that indicates that AS 135 has failed. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 29 is an example of mapping a 3GPP service primitive to an MIH event service when the AS 135 broadcasts information regarding a geographic area. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link parameter change event service in response to receiving a 3GPP service primitive from the AS 135 that includes information regarding a geographic area. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 30 is an example of mapping a 3GPP service primitive to an MIH event service when the AS 135 provides notification of paging for a particular user or terminal. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link parameter change event service in response to receiving a 3GPP service primitive from the AS 135 that provides notification of paging for a particular user or terminal. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 31 is an example of mapping a 3GPP service primitive to an MIH event service when the AS 135 provides a notification for all users. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link parameter change event service in response to receiving a 3GPP service primitive from the AS 135 that provides notification information for all users. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 32 is an example of mapping a 3GPP service primitive to an MIH event service when the AS 135 provides notification information for one or more users. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link parameter change event service in response to receiving a 3GPP service primitive from the AS 135 that provides a notification for one or more users. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 33 is an example of mapping a 3GPP service primitive to an MIH event service when the AS 135 indicates a UE initiated connection establishment. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link up event service in response to receiving a 3GPP service primitive from the AS 135 that indicates a UE initiated connection establishment. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 34 is an example of mapping a 3GPP service primitive to an MIH event service when the AS 135 indicates a network initiated connection release. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link down event service in response to receiving a 3GPP service primitive from the AS 135 that indicates an infrastructure side, (i.e., network), initiated connection release. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 35 is an example of mapping a 3GPP service primitive to an MIH event service when the AS 135 indicates a network initiated RAB establishment. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link up event service or a link detected event service in response to receiving a 3GPP service primitive from the AS 135 that indicates an infrastructure side, (i.e., network), initiated RAB establishment. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 36 is an example of mapping a 3GPP service primitive to an MIH event service when the AS 135 indicates a network initiated RAB release. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link down event service in response to receiving a 3GPP service primitive from the AS 135 that indicates an infrastructure side, (i.e., network), initiated RAB release. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 37 is an example of mapping a 3GPP service primitive to an MIH event service when the AS 135 indicates the potential for an aborted connection unless streamlining is performed. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link going down event service in response to receiving a 3GPP service primitive from the AS 135 that indicates the potential for an aborted connection unless streamlining is performed. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 38 is an example of mapping a 3GPP service primitive to an MIH event service when the AS 135 indicates location information provided by a network for a specific UE. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link parameter change event service in response to receiving a 3GPP service primitive from the AS 135 that indicates location information provided by a network for a specific UE. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 39 is an example of mapping a 3GPP service primitive to an MIH event service when the AS 135 indicates a connection loss. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link down event service in response to receiving a 3GPP service primitive from the AS 135 that indicates a connection loss. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 40 is an example of mapping a 3GPP service primitive to an MIH event service when the E-UTRA/E-CORE system 150 indicates that the location of a UE is now known by a network. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link parameter change event service in response to receiving a 3GPP service primitive from the E-UTRA/E-CORE system 150 that indicates that the location of a UE is now known by a network. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 41 is an example of mapping a 3GPP service primitive to an MIH event service when the E-UTRA/E-CORE system 150 indicates that the location of a UE is known to a network but no transport channel is established. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link parameter change event service or a link down event service in response to receiving a 3GPP service primitive from the E-UTRA/E-CORE system 150 that indicates that the location of a UE is known to a network but no transport channel is established. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
FIG. 42 is an example of mapping a 3GPP service primitive to an MIH event service when the E-UTRA/E-CORE system 150 indicates that radio resources have been established and that a UE is able to perform UL and DL transport of a PDU. As indicated by Table 2 above, the processor 205 in the SAP 100 illustrated in FIG. 2 outputs a link up event service or a link handover complete event service in response to receiving a 3GPP service primitive from the E-UTRA/E-CORE system 150 that indicates that radio resources have been established and that a UE is able to perform UL and DL transport of a PDU. This MIH event service may be applicable to any type of standard, such as IEEE 802.21 and the like.
It should be noted that the specific mapping of a 3GPP service primitive to an MIH event service, (e.g., an IEEE 802.21 event), may change. In particular, primitives for SAE and LTE currently remain undefined. However, the present invention demonstrates how mapping service primitives to event services may easily be adapted or used to provide triggers.
Although the features and elements of the present invention are described in the preferred embodiments in particular combinations, each feature or element can be used alone (without the other features and elements of the preferred embodiments) or in various combinations with or without other features and elements of the present invention.

## Claims

1. A method for use in a wireless communications device, the method comprising:
communicating, at the wireless communications device, wireless data using universal mobile telecommunications system (UMTS) technology;
receiving, at the wireless communications device, a 3GPP radio access bearer has been activated (RABMAS-RAB-ESTABLISH) primitive;
generating, at the wireless communications device, a Media Independent Handover (MIH) handover complete event based on the RABMAS-RAB-ESTABLISH primitive; and
providing, at the wireless communications device, the MIH handover complete event to an upper layer.

2. The method of claim 1, further comprising:
receiving a 3GPP radio access bearer is modified for data transfer (RABMSM-MODIFY) primitive;
generating an MIH handover complete event based on the RABMSM-MODIFY primitive; and
providing the MIH handover complete event based on the RABMSM-MODIFY primitive to an upper layer.

3. The method of claim 1, further comprising:
receiving a 3GPP radio access bearer is modified for data transfer (RABMSM-MODIFY) primitive;
generating an MIH link parameter change event based on the RABMSM-MODIFY primitive; and
providing the MIH link parameter change event to an upper layer.

4. The method of claim 1, further comprising:
receiving a Third Generation Partnership Project (3GPP) radio access bearer is activated for data transfer (RABMSM-ACTIVATE) primitive;
generating an MIH link up event based on the RABMSM-ACTIVATE primitive; and
providing the MIH link up event to an upper layer.

5. The method of claim 1, further comprising:
receiving a 3GPP radio access bearer is deactivated for data transfer (RABMSM-DEACTIVATE) primitive;
generating an MIH link down event based on the RABMSM-DEACTIVATE primitive; and
providing the MIH link down event to an upper layer.

6. The method of claim 1, further comprising:
receiving a 3GPP radio access bearer data transfer error (RABMSM-STATUS) primitive;
generating an MIH link down event to an upper layer in response to the RABMSM-STATUS primitive; and
providing the MIH link down event to an upper layer.

7. An Media Independent Handover (MIH)-capable wireless communications device, the wireless communications device comprising:
a circuit configured to communicate wireless data using universal mobile telecommunications system (UMTS) technology;
a circuit configured to receive a 3GPP radio access bearer has been activated (RABMAS-RAB-ESTABLISH) primitive;
a circuit configured to generate an MIH handover complete event based on the RABMAS-RAB-ESTABLISH primitive; and
a circuit configured to provide the MIH handover complete event to an upper layer.

8. The wireless communications device of claim 7, further comprising:
a circuit configured to receive a 3GPP radio access bearer is modified for data transfer (RABMSM-MODIFY) primitive;
a circuit configured to generate an MIH handover complete event based on the RABMSM-MODIFY primitive; and
a circuit configured to provide the MIH handover complete event based on the based on the RABMSM-MODIFY primitive to an upper layer.

9. The wireless communications device of claim 7, further comprising:
a circuit configured to receive a 3GPP radio access bearer is modified for data transfer (RABMSM-MODIFY) primitive;
a circuit configured to generate an MIH link parameter change event based on the RABMSM-MODIFY primitive; and
a circuit configured to provide the MIH link parameter change event to an upper layer.

10. The wireless communications device of claim 7, further comprising:
a circuit configured to receive a Third Generation Partnership Project (3GPP) radio access bearer is activated for data transfer (RABMSM-ACTIVATE) primitive;
a circuit configured to generate an MIH link up event based on the RABMSM-ACTIVATE primitive; and
a circuit configured to provide the MIH link up event to an upper layer.

11. The wireless communications device of claim 7, further comprising:
a circuit configured to receive a 3GPP radio access bearer is deactivated for data transfer (RABMSM-DEACTIVATE) primitive;
a circuit configured to generate an MIH link down event based on the RABMSM-DEACTIVATE primitive; and
a circuit configured to provide the MIH link down event to an upper layer.

12. The wireless communications device of claim 7, further comprising:
a circuit configured to receive a 3GPP radio access bearer data transfer error (RABMSM-STATUS) primitive;
a circuit configured to generate an MIH link down event to an upper layer in response to the RABMSM-STATUS primitive; and
a circuit configured to provide the MIH link down event to an upper layer.

13. A method for use in a wireless communications device, the method comprising:
communicating, at the wireless communications device, wireless data using universal mobile telecommunications system (UMTS) technology;
receiving, at the wireless communications device, a 3GPP radio access bearer is modified for data transfer (RABMSM-MODIFY) primitive;
generating, at the wireless communications device, a Media Independent Handover (MIH) handover complete event based on the RABMSM-MODIFY primitive; and
providing, at the wireless communications device, the MIH handover complete event based on the based on the RABMSM-MODIFY primitive to an upper layer.

14. The method of claim 13, further comprising:
receiving a 3GPP radio access bearer has been activated (RABMAS-RAB-ESTABLISH) primitive;
generating an MIH handover complete event based on the RABMAS-RAB-ESTABLISH primitive; and
providing the MIH handover complete event to an upper layer.

15. The method of claim 13, further comprising:
receiving a 3GPP radio access bearer is modified for data transfer (RABMSM-MODIFY) primitive;
generating an MIH link parameter change event based on the RABMSM-MODIFY primitive; and
providing the MIH link parameter change event to an upper layer.

16. The method of claim 13, further comprising:
receiving a Third Generation Partnership Project (3GPP) radio access bearer is activated for data transfer (RABMSM-ACTIVATE) primitive;
generating an MIH link up event based on the RABMSM-ACTIVATE primitive; and
providing the MIH link up event to an upper layer.

17. The method of claim 13, further comprising:
receiving a 3GPP radio access bearer is deactivated for data transfer (RABMSM-DEACTIVATE) primitive;
generating an MIH link down event based on the RABMSM-DEACTIVATE primitive; and
providing the MIH link down event to an upper layer.

18. The method of claim 13, further comprising:
receiving a 3GPP radio access bearer data transfer error (RABMSM-STATUS) primitive;
generating an MIH link down event to an upper layer in response to the RABMSM-STATUS primitive; and
providing the MIH link down event to an upper layer.