KR20090003332A - Mobility middleware architecture for multiple radio access technology apparatus - Google Patents

Abstract

A multiple radio access technology (RAT) apparatus with mobility middleware provides a user with access to various RAT networks, such as a frequency division duplex (FDD) network and a wireless local area network (WLAN). In one embodiment, the apparatus is a dual mode FDD/WLAN converged wireless communication handset which includes a terminal equipment (TE) module having mobility middleware, an applications and protocols processor and a terminal interface (TI). The dual mode FDD/WLAN converged wireless communication handset further includes a user services identity module (USIM), a mobile termination (MT) module and a protocol stack which interface with the mobility middleware via a plurality of links. In another embodiment, the multi-RAT apparatus is terminal equipment which includes a mobility middleware core module, a mobility middleware communication module, a driver and an insertably removable wireless communication device for providing a multiple radio transport medium to applications running in the terminal equipment.

Description

MOBILITY MIDDLEWARE ARCHITECTURE FOR MULTIPLE RADIO ACCESS TECHNOLOGY APPARATUS

TECHNICAL FIELD The present invention relates to a terminal equipment architecture, and more particularly, to mobility middleware for managing multiple radio access technologies (RATs) in terminal equipment.

Convergence is the term used for emerging trends in the telecommunications and internet industries to integrate the functions of many different types of devices into one unit and includes the convergence of networks, terminal devices, and services. In the context of wireless communications, convergence devices are radio access technology (e.g., IEEE 802.11, 3 Generation Partnership Project (3GPP), a code division multiple access (CDMA), Bluetooth ^®, etc.), or wired access technology (e. G. , IEEE 802.3) has the ability to support multiple access technologies to communicate with different networks.

One of the most difficult challenges associated with converged devices is maintaining mobility between heterogeneous networks. Some standards groups, such as IEEE 802.21, or the Internet Engineering Task Force for Layer 3 (L3) Mobility (IETF) Mobile Internet Protocol (IP), which provide link layer intelligence to support mobility, address various parts of the mobility problem. Doing.

Currently, the current high-end market, where PDA and smartphone platforms dominate, primarily uses a dual-processor (one for modem, one for applications) architecture platform.

In 3GPP handsets, such as dual-mode universal mobile communication system (UMTS) frequency division duplex (FDD) / Wireless Local Area Network (WLAN) handsets, mobile termination (MT) modules are used to perform wireless transmissions and related functions. The (TE) module includes end-to-end applications, and the User Service Identity Module (USIM) contains data and procedures that clearly and securely identify the handset.

Although current standards such as IETF Mobile IP or IEEE 802.21 specify messaging to enable mobility, they do not provide any implementation solution. In addition, some coordination is required between these mobility entities. However, this tuning was not handled by any standard group.

It is also desirable to provide a mobility middleware architecture when the application processor and the RAT network are not on the same platform.

The present invention relates to a multi-RAT device with mobility middleware that provides a user with access to various RAT networks, such as FDD networks and WLANs. In one embodiment, the device is a dual mode FDD / WLAN converged wireless communication handset comprising a mobility middleware, an application and protocol processor, and a TE module having a terminal interface (TI). The dual mode FDD / WLAN converged wireless communication handset further includes a USIM, MT module, and protocol stack that interfaces with mobility middleware over a plurality of links. In yet another embodiment, a multi-wireless access technology device is a removable wireless communication device for providing a plurality of wireless transport media to mobility middleware core modules, mobility middleware communication modules, drivers, and applications running on a terminal device. Terminal equipment that includes the device.

The removable wireless communication device can be an FDD / Wireless Broadband (WiMAX) personal computer (PC) card. Mobility middleware includes a set of functions such as network detection, network selection, inter-network handover, parallel attach, measurement, multi-access quality of service (QoS), security, and power control.

There are provided multiple RAT devices with mobility middleware that provide users with access to various RAT networks.

As referred to herein, the term “wireless transmit / receive unit (WTRU)” may operate in a user equipment (UE), mobile station, fixed or mobile subscriber unit, pager, cellular telephone, PDA, computer, laptop or wireless environment. Other types of user devices include, but are not limited to.

The present invention introduces a cross-layer function called mobility middleware, which refers to a set of functions that enable seamless mobility within heterogeneous networks and support multiple services. These functions may include network detection, network selection, inter-network handover, parallel attach (when the device is connected to multiple access technologies simultaneously), measurement, multi-access QoS, security, and power control.

Mobility middleware does not lie at any particular protocol layer. Mobility middleware provides interlayer interaction. Interaction with applications and access layers is through an application program interface (API).

1 is a high level diagram of a 3GPP dual mode FDD / WLAN converged wireless communication handset 100 of a cell phone that includes mobility middleware functionality configured in accordance with the present invention. The 3GPP dual mode FDD / WLAN converged wireless communication handset 100 includes a mobile termination (MT) module 105, a terminal equipment (TE) module 110, and a user service identity module (USIM) 115. TE module 110 includes mobility middleware 120. Depending on the implementation, the MT module 105, TE module 110, and user service identity module (USIM) 115 may be merged on the same or separate chips or processors. The MT module 105 may include a UMTS FDD chip 125. In addition, the 3GPP dual mode FDD / WLAN converged wireless communication handset 100 may include a WLAN chip 130. Although the UMTS FDD (i.e., cellular) and WLAN are shown as chips 125 and chip 130, respectively, as an implementation thereof in FIG. 1, the 3GPP dual mode FDD / WLAN converged wireless communication handset 100 is many different types. Access technology (eg, IEEE 802.15, Digital Video Broadcasting-Handheld (DVB-H), etc.). Mobility middleware 120 integrates applications with multiple access networks.

Mobility middleware 120 enables end user applications to run seamlessly as the middleware coordinates handovers between the various technologies. For example, a user of the 3GPP dual mode FDD / WLAN converged wireless communication handset 100 will not witness any interruption of streaming video during the handover between the cellular network and the WLAN. Mobility middleware 120 coordinates and controls mobility. For example, mobility middleware 120 may determine that the WLAN air interface is degrading and may initiate a cellular stack in preparation for handover. Mobility middleware 120 may then trigger mobile IP to change the network path.

2 illustrates an architecture of a 3GPP dual mode FDD / WLAN converged wireless communication handset 200 constructed in accordance with the present invention. Handset 200 includes TE module 205, USIM 210, MT module 215, and IEEE 802.11 protocol stack 220.

TE module 205 includes mobility middleware 225, application and protocol processor 230, and terminal interface TI, 240. TE module 205, USIM 210, MT module 215 and IEEE 802.11 protocol stack 220 may be integrated on the same or separate chips or processors, if desired. The application and protocol processor 230 executes an end user application 231 corresponding to the application that the user ultimately uses. End user application 231 may include VoIP, video, and the like. The application and protocol processor 230 is an IEEE 802.21 interface that interfaces with the mobility middleware 225 via session initiation protocol (SIP) client 232, IP suite 233, mobile IP client 234, and link 280 ₄ . 235).

As defined in the 3GPP standard, USIM 210 includes an Authentication and Key Agreement (AKA) cellular security module 245 and an extensible authentication protocol (EAP) AKA WLAN security module 250. Security modules 245 and 250 exchange associated security information with mobility middleware 225 via link 280 ₆ .

The MT module 215 includes a 3GPP FDD No Access Layer (NAS) 255 and a 3GPP FDD Access Layer (AS) 265. NAS 255 includes 3GPP function mobile network (MN, 256), call control (CC, 257), session manager (SM, 258), general packet radio service (GPRS) mobility manager (GMM, 259) and radio access bearer. Manager (RABM) 260. The RABM 260 handles all types of radio access bearers (RABs). NAS 255 further includes ATTC (ATtention Command Set Interpreter) 261, ATC Advanced Technology Attachment (ATA) 262, IP Relay 263, and Bit Stream Relay 264. ATA 262 ensures that ATC commands are exchanged between TE module 205 and MT module 215.

The 3GPP FDD AS 265 includes an FDD physical layer (PHY) 266, an FDD medium access control layer (MAC) 267, an FDD radio link control (RLC) 268, a packet data compression protocol (PDCP) unit 269, and a broadband 3GPP L1 / L2 / L3 functions such as Cast and Multicast Control (BMC) units and Radio Resource Control (RRC) 271. The IP relay 263 exchanges an IP packet / RAB with the PDCP unit 269. The bit stream relay 264 exchanges a non-IP based packet / bit stream RAB (eg, voice data, video telephony data, etc.) with the FDD RLC 268.

Both NAS 255 and AS 265 include an IEEE 802.21 interface 235 for communicating with mobility middleware 225 over links 280 ₁ and 280 ₂ , respectively.

IEEE 802.11 protocol stack 220 includes a logical link control (LLC) layer 221, an IEEE 802.11 MAC layer 122, an IEEE 802.11 PHY layer 123, and a session management entity (SME) 224, all of which Interfaces with mobility middleware 225 via IEEE 802.21 interface 235 and link 280 ₁ .

2, the function of the mobility middleware 225 is linked (280 ₁ - 280 ₆₎ interacts with various entities and the other in the 3GPP dual mode FDD / WLAN converged wireless handset 100 via . As mentioned above, the IEEE 802.21 interface 235 is connected to the block 230 of the TE module 205, to the 3GPP FDD NAS 255 and the 3GPP FDD AS 265 of the MT module 215, and to the IEEE 802.21. Merged into the protocol stack 220.

Mobility middleware 225 refers to a set of functions that enable seamless mobility and support multiple services within heterogeneous networks.

One such function is a network detection function that allows a terminal to identify the characteristics of the surrounding networks.

Another function is, within many access networks, a network selection function that selects the access network that best suits the subscriber's needs based on QoS, system operator, user profile, application requirements, and the like.

Yet another function is an inter-network handover function that performs seamless handover from the old network to the newly selected network. The purpose is to provide service continuity to the user. This feature interacts with other mobility features such as mobile IP.

Yet another function is a parallel attach function that allows a device to simultaneously access multiple access technologies to satisfy a particular QoS application. For example, voice calls can be handled via a cellular system, while file transfers are handled via a WLAN. The parallel attach function interacts with the handover management and the IP layer for context transfer.

Yet another function is a measurement function that collects measurements received from various AT networks and provides input to other mobility middleware functions such as network selection, power management, and the like.

Yet another function is a multi-access QoS function that ensures that the QoS requirements for the application are addressed by the selected network.

Yet another function is a security function that handles the security operations required to provide relevant security across the AT and improves handover between networks. For example, the security function may pre-authenticate the user to reduce handover delay.

Yet another function is a power control function that coordinates the power control function of each access technology to improve the battery life of the device.

IEEE 802.21 primitives (eg, information, event) for medium independent handover (MIH) services regarding the interaction of mobility middleware 225 with IEEE 802.11 protocol stack 220 over link 280 ₁ . And IEEE 802.11 standardization work on the IEEE 802.11 MAC layer 222 and the IEEE 802.11 PHY layer 223 to support instructions. IEEE 802.21 primitives can be merged within existing or new IEEE 802.11 primitives.

The interaction of the mobility middleware 225 with the 3GPP FDD NAS 255 over the link 280 ₃ is directly between the IEEE 802.21 primitives (ie, information, events, commands) and some existing NAS (SM and GMM) primitives. Depends on the mapping There is no change required by SM 258 and GMM 259 for mobility middleware 125 to work with 3GPP FDD NAS 155.

For the interaction of mobility middleware 255 with 3GPP Access Stratum (AS) 265 over link 280 ₂ , there is a mapping between the IEEE 802.21 primitives and the primitives of FDD Radio Resource Control (RRC) 271. . There is no change required by RRC 271 for mobility middleware 225 to operate with 3GPP FDD AS 265.

Interaction of the mobility middleware 225 with the mobile IP client 234 via the link 2804 ₄ includes two aspects. In one aspect, IEEE 802.21 may trigger mobile IP client 234 to accelerate handover. For example, when an IEEE 802.21 "MIH link down" event occurs, mobility middleware 225 forwards an event trigger to the mobile IP client, so that TI 240 registers with an external agent and sends a care of address (CoA). Acquire and trigger to send a "binding update". This can reduce the delay in the mobile IP handover procedure.

Yet another aspect is an ongoing process to support the transmission of IEEE 802.21 messages (eg, information, events and commands) between the TI 240 and the network side, over IP via link 2280 _5b . IETF mobile IP standardization activity. This method uses mobile IP as a "transport means" to transport IEEE 802.21 messages between the mobile terminal and the network side, thereby minimizing the need for changes to existing functions on both sides.

Mobility middleware 225, interacts with existing security functions (245 and 250) in the handset (200) via a link _{(280. 6)} In order to solve the security problem of the hand-over while. When handover occurs between UMTS and WLAN network, security consistency must be ensured. Thus, to ensure this consistency, inputs from the UMTS security portion (eg, AKA cellular security 245) and WLAN security portion (eg, EAP-AKA WLAN security 250) are transferred to mobility middleware 225. Is required by).

Existing AT commands from ATA 262 may be used to carry commands to / from mobility middleware 225 via links 280 _5a and 280 _5b .

Mobility middleware 225 interacts with application and service enabling protocols, such as SIP client 232 and IEEE 802.21 interface 235 via link 280 ₄ . For example, an application may have certain QoS requirements. Mobility middleware 225 may map QoS requirements to the most appropriate network.

Mobility middleware 225 interacts with IEEE 802.11 protocol stack 220 via link 280 ₁ to facilitate handover procedures. When the handover from FDD to IEEE 802.11 is imminent due to the 3GPP dual mode FDD / WLAN converged wireless communication handset 200 moving from the area covered by the UMTS FDD network to the area covered by the IEEE 802.11 network, During over, the mobility middleware 225 may request the IEEE 802.11 protocol stack 220 to initiate the association procedure needed to establish the link 280.

The present invention relates to a mobility architecture when the application processor and the RAT network are not on the same platform. This architecture, which is divided into a PC and a removable wireless communication device, introduces some complexity and imposes additional requirements on mobility middleware. An example is the mobility middleware architecture for such devices, including certain dual mode FDD / WiMAX devices.

FIG. 3 illustrates features of mobility middleware 225 including service entity 310 and mobility entity 305 that includes functionality to enable seamless mobility and support multiple services within heterogeneous networks. The mobility entity 305 includes a relatively independent intelligent decision unit (ie, mobility policy 315) and an interface unit (ie, mobility enabler 320). The service entity 310 also includes a relatively independent intelligent decision unit (ie, service policy 325) and an interface unit (ie, service enabler 330). The service enabler 330 is defined according to the Open Mobility Alliance (OMA) or 3GPP protocol and procedure.

The modular design of the architecture allows the mobility middleware 225 to support an increasing number of different end user applications 335, and RATs. For example, if WiMAX is added to the device as a new RAT, the interface for supporting WiMAX in the Mobility Enabler 320 is added, while the rest of the mobility middleware is maintained.

Mobility middleware 225 sits on top of transport stack 340 (eg, 3GPP, Global System for Mobile communications (GSM), WLAN, Long-Term Evolution (LTE), etc.). There are generally two types of applications that interact with mobility middleware 225. One type of application is an end user application (eg, VoIP, instant messaging, etc.), and the other type of application is a higher layer protocol (eg, mobile IP or SIP). These applications have coordinated control of mobility and service middleware functions. For example, end user application 335 may use services and mobility application programming interfaces (APIs) in a coordinated manner through open APIs 345.

Mobility middleware 225 does not lie at any particular protocol layer. Instead, mobility middleware provides inter-layer interactions, and interactions with end user application 335 and transport stack 340 are performed through open APIs 345 and 350, respectively.

4 illustrates a detailed configuration of the mobility policy 315 and the mobility enabler 320 of the mobility entity 305. Mobility policy 315 is an intelligent entity that deals with multi-access mobility issues and provides policy and intelligence for quality of service (QoS) and heterogeneous mobility between RATs. It interfaces with the access layers through the mobility enabler 320 to monitor and control the underlying access technology stack. Mobility policy 315 uses open APIs for end user application control.

Mobility policy 315 includes a set of functions that enable seamless mobility and support multiple services within heterogeneous networks. These functions include: 1) a network detection function 352 that allows the terminal to identify features of the surrounding networks; 2) a network selection function 354 that selects one of the many access networks that best suits the subscriber's needs, based on QoS, system operator, user profile, application requirements, etc .; 3) Inter-network handover function 356, which performs seamless handover from the old network to the newly selected network (the purpose is to provide service continuity to the user; this function is interoperable with other mobility functions such as mobile IP). Function); 4) Parallel attach function 358 (e.g., voice calls are handled via cellular, while file transfers occur via WLAN, which facilitates the device to access multiple RATs simultaneously to satisfy QoS applications). do). This parallel attach function interacts with the handoff (HO) management and the IP layer for context transfer; 5) a measurement function that collects measurements received from various RATs and provides input for other mobility middleware functions such as network selection, power management, etc .; 6) a multi-access QoS function to ensure that QoS requirements for the application are addressed by the selected network; 7) a security function 364 that provides the relevant security across the RAT and handles the security actions needed to improve inter-network handover (eg, the security function may pre-authenticate users to reduce handover delay). have); And 8) a power control function that coordinates the power control function of each access technology to improve the battery life of the device.

It should be noted that the mobility policy function does not replace the existing mobility function in each RAT. For example, inter-network handovers address issues related to multi-access handovers and interact with the handover functionality for each access technology.

Mobility enabler 320 is a layer of "thin" functions that interface with different RATs. The open API is used to allow the mobility enabler 320 to collect statistics from the RAT or send a command to the RATs. It also consolidates, normalizes, and provides the control information trigger interface to the mobility policy entity 315 the information received from the different RATs, allowing for control of the RAT.

The mobility enabler 320 receives and processes measurements from the transport stack 340 (see FIG. 3) and forwards the processed information to the mobility policy entity 315. In addition, commands and requests may be sent from the mobility policy entity 210 to the end user application 335 (see FIG. 3).

Mobility enabler 320 provides a thin layer to separate mobility policy 315 from any particular access network, thereby modularizing the design and easily expanding for different RATs.

5 is an example of a service entity 310. The service enabler 330 is a set of software functions that is a standardized API that allows third party application developers to define and build mobile device applications independently of the underlying transport technology. Typical examples of these enabling techniques are DRM 505, instant messaging 510, and presence 515. Using these examples alone in a typical implementation, an end user application developer can develop an application that allows DRM-protected content to be transmitted through an instant messaging facility only when certain presence conditions are appropriate. The service enabler 330 allows the end user application to form and call action calls in a standardized manner to allow the development of a theoretically infinite number of applications that operate in a manner transparent to the supporting transport technology. Allow to query about the bling function.

Service policy 325 is an intelligent entity that addresses service related issues and provides a policy for the coordination of different applications supported by the service enabler 330.

According to another embodiment shown in FIG. 6, the present invention includes a removable wireless communication device 605 that provides functionality similar to that of the MT module 105 and WLAN chip 130 shown in FIG. 1. Terminal equipment architecture 600. The removable wireless communication device 605 may take the form of an FDD / WiMAX PC card. The FDD / WiMAX PC Card allows the terminal device architecture 600 to connect to a wireless network for use with a variety of applications such as web browsing, email, file transfer, and the like.

The above-described removable radio communication device 605 may support a plurality of radio access technologies (RATs). Mobility middleware will allow seamless service continuity for users running applications from their portable computing devices such as PCs, notebooks, PDAs and the like.

In one embodiment of the invention shown in FIG. 7, mobility middleware 700 is present only in terminal device 600 ′. 7 shows a removable wireless communication device 605 'having a dual mode FDD / WiMAX PC card architecture in accordance with the present invention. Although FIG. 7 illustrates only the UMTS module 705, the WiMAX module 710, and the communication module 715 as part of a removable wireless communication device 605 ′ as an implementation, a fusion type removable wireless communication device may be a plurality of devices. Different access technologies (eg, IEEE 802.15, Digital Video Broadcasting-Handheld (DVB-H), etc.) can be supported.

The removable wireless communication device 605 'provides a plurality of wireless transport media to applications in the terminal equipment 600'. In FIG. 7, only UMTS 705 and WiMAX 710 are shown by way of example. The UMTS 705 and WiMAX 710 consist of protocol software and a modem. These components can be any standard compatible implementation. Applications in terminal equipment 600 'do not know the underlying various transport mechanisms. Applications typically send and receive data without any change. Details about the transport are hidden by the mobility middleware 700. Mobility middleware 700 provides a uniform and consistent interface to applications within terminal equipment 600 '. Mobility middleware 700 determines which radios will be activated and used for data transmission. Mobility middleware 700 is fully implemented within terminal equipment 600 '. This terminal device 600 'enables greater mobility, memory, and power to enable the mobility middleware 700 to support more features, functions, and policies. Mobility middleware 700 communicates with protocol software components (eg, UMTS 705 and WiMAX 710) residing on a removable wireless communication device 605 ′ via a USB link. Commands and responses between the mobility middleware 700 and the protocol software are carried over the USB link. The communication driver 715 receives the USB traffic and then routes commands and responses between the mobility middleware and the protocol software components.

8 illustrates an alternative dual mode FDD / WiMAX PC card architecture in accordance with the present invention. In FIG. 8, mobility middleware communication module 800A resides on terminal equipment 600 ′, and mobility middleware core module 800B communicates with communication driver 715 and UMTS 705 on removable wireless communication device 605 ″. ) And WiMAX 710.

Mobility middleware core module 800B provides a uniform and consistent interface to applications within terminal equipment 60 ". Mobility middleware core module 800B determines which radios will be activated and used for data transmission. The middleware communication module 800A supports the sending and receiving of higher layer messages, such as IP messages, and the mobility middleware core module 800B provides handover by allowing terminal equipment 600 "to access and react to link level events faster. It is implemented within a removable wireless communication device 605 "that improves efficiency. The mobility middleware core module 800B is present on the removable wireless communication device 605" via an API call or by invoking an AT command. Communicating with protocol software components (eg, UMTS 405 and WiMAX 410). Commands and responses between the mobility middleware communication device 800A and the protocol software are carried over the USB link. The communication driver 715 receives the USB traffic and then routes commands and responses between the mobility middleware and the protocol software components via the mobility middleware core module 800B.

9 is a functional block diagram illustrating mobility middleware in terminal equipment 600 'in accordance with the architecture of FIG. In this scenario, the operating system (OS) on the terminal device 600 'is a MicroSoft (MS) Windows OS and the interface between the terminal device 600' and the removable wireless communication device 605 'is USB.

As shown in FIG. 9, mobility middleware is implemented in terminal equipment 600 ′ as two modules. The two modules are the mobility middleware communication module 700A and the mobility middleware core module 800B corresponding to an extension of the Network Driver Interface Specification Wide Area Network (NDISWAN) miniport driver 905. End user applications in terminal equipment 600 'may include VoIP, video, and the like. Terminal equipment 600 ′ further includes a Session Initiation Protocol (SIP) client 920, an Internet Protocol (IP) suite 930, and a mobile IP (MIP) client 935. As described above with reference to FIG. 4, mobility middleware 800A and 800B communicate via an API such as the IEEE 802.21 API.

The detachable wireless communication device 605 ′ includes a USIM 910, a UMTS 705, a WiMAX 710, and a communication driver 715. The UMTS 705 includes a 3GPP FDD NAS 915 and a 3GPP FDD AS 920. WiMAX 710 includes an IEEE 802.16 protocol stack. As defined in the 3GPP standard, the USIM 910 includes an Authentication and Key Agreement (AKA) cellular security module and an Extensible Authentification Protocol (EAP) AKA WLAN security module. The security module exchanges associated security information with the mobility middleware core module 800B via a USB link. NAS 915 includes GSM CC / SM 940, ATC Advanced Attachment (ATA) 945, and IP relay.

Both NAS 915 and AS 920 have a standard set of APIs. Mobility middleware 800 communicates by calling these standard APIs. In addition to the standard API, mobility middleware 800 uses AT commands to communicate with NAS 915. API calls or AT commands are carried by a communication link (eg, a USB link) between the terminal equipment 600 'and the removable wireless communication device 605'.

The WiMAX IEEE 802.16 protocol stack 710 includes an IEEE 802.11 MAC layer 955, an IEEE 802.11 PHY layer 960, and a session management entity (SME) 965, all of which make standard API calls over a USB link. It interfaces with the mobility middleware 800B.

The mobility middleware 800 may set a specific RAT as a default when the terminal equipment 600 'is initialized. The signal strength is then continuously monitored by sending standard API commands. When mobility middleware 800 receives a measurement report, it may optionally send the report to the network or locally analyze the report. Depending on signal strength and the defined handover algorithm, mobility middleware 800 may prepare another RAT for potential handover. If the handover is imminent, another RAT is initiated and the session is transferred to the new link. Mobility middleware 800 is responsible for initiating all signaling necessary to maintain the session. Mobility middleware 800 may use API calls, AT commands, or other defined interfaces to initiate a procedure. In this configuration, mobility middleware core module 800B resides in terminal equipment 600 '. Mobility middleware core module 800B will have access to improved computing power, memory, more power, and the like. Thus, mobility middleware core module 800B can implement more complex handover policies, and analysis of local measurement reports on the client side, so that complex functions can be implemented and decisions can be made locally to improve performance. To help.

FIG. 10 is a functional block diagram illustrating mobility middleware in a removable wireless communication device 600 ", in accordance with the architecture of FIG. 8. As shown in FIG. 10, the mobility middleware core module 800B is removable wireless. Implemented within the communication device 605 ", the mobility middleware communication module 800A resides in the terminal equipment 600". This option has the advantage of being close to the link level protocol stack. Therefore, it is faster for link level events. Can respond.

The mobility middleware core module 800B accepts network related commands and data from the terminal device 600 ". Thus, the terminal device 600" does not see any changes, and in order to set up / tear down the link and send and receive data. Use the normal WAN interface. Terminal equipment 600 "and removable wireless communication device 605" are connected via a USB link. This USB link is managed by a driver in each of the terminal equipment 600 "and the removable wireless communications device 605". WAN commands from terminal equipment 600 "are carried to a removable wireless communication device 605" via a USB link, and intercepted by mobility middleware core module 800B. The mobility middleware core module 800B then determines how to distribute the instructions and data. In addition, the mobility middleware core module 800B performs management functions such as link state monitoring, link selection, and preparation for future handoffs. In the case of actual handoff, the mobility middleware core module 800B The handoff is executed.

In order to continue the data session, other higher level protocols, such as MIP and SIP procedures, need to be initiated by the mobility middleware communication module 800A in the terminal equipment 600 ". Instructions from the mobility middleware core module 500B Upon receipt, the mobility middleware communication module 800A initiates such a procedure.The mobility middleware communication module 800A interacts with the higher level protocols present in the terminal equipment 600 "to provide efficient communication. .

In the configuration of FIG. 10, the mobility middleware core module is present on the MT side. This will have very quick access to link level activity. Thus, you can quickly react to these events to trigger an action. Since the core module is implemented on the MT platform and interfaces with TE using a standard USB / WAN interface, the impact on the PC side is smaller. This will be more portable and easier to connect and configure.

Mobility middleware core module 800B performs important tasks such as network detection, network selection, etc., while mobility middleware communication module 800A provides functionality that requires the exchange of messages over IP and application program interfaces on other control stacks. Start API). The mobility middleware core module 800B and the mobility middleware communication module 800A exchange messages through separate interfaces.

Mobility middleware core module 800B serves as the main mobility middleware function. As such, multiple services are supported by implementing control functions and IEEE 802.21 link events and services. One service that can be supported by the mobility middleware core module 800B includes network detection, which allows the terminal to identify characteristics of the surrounding networks.

Another service provided by the mobility middleware core module 800B is network selection. Within many access networks, this service selects the network that best suits the subscriber's needs based on characteristics such as QoS, system operator, user profile, application requirements, and the like.

Yet another service provided by the mobility middleware core module 800B includes an inter-network handover. This function performs seamless handover from the old network to the newly selected network. The purpose is to provide service continuity to the user. This feature interacts with other mobility features such as mobile IP.

Yet another service provided by the mobility middleware core module 800B includes multi-access QoS. This service ensures that the QoS requirements for the application are addressed by the selected network.

Yet another service provided by the mobility middleware core module 800B includes a parallel attach service that initiates simultaneous connection of a plurality of AT networks to satisfy QoS applications. For example, voice calls can be handled over a cellular network, while file transfers occur over a WLAN. This parallel attachment service interacts with the handover management and the IP layer for context transfer.

Yet another service provided by mobility middleware core module 800B includes power management. This service coordinates the power control capabilities of each access technology to improve the battery life of the device.

Yet another service provided by the mobility middleware core module 800B includes a measurement service. This service collects measurements received from various ATs and provides input for other mobility middleware functions such as network selection, power management, and the like.

Yet another service provided by the mobility middleware core module 800B includes security. This service handles the security actions required to provide relevant security across ATs and to improve handover between networks. For example, this can pre-authenticate users to reduce handover delay.

Yet another service provided by the mobility middleware core module 800B is a routing function. Mobility middleware core module 800B routes control messages and data between control applications in terminal equipment 600 and between communication protocol stacks in WiMAX 710 of removable wireless communication device 605.

Mobility middleware communication module 800A will provide MIH messaging. This function will accept MIH messages to be sent over IP from the mobility middleware core module 800B to the MIH server. The mobility middleware communication module 800A will then call the appropriate API to send messages over the IP stack available in the computing platform of the terminal device 600. On the other hand, mobility middleware communication module 800A should be able to receive MIH messages from the MIH server via IP and send them to mobility middleware core module 800B.

Mobility middleware communication module 800A supports mobility middleware core module 800B to interact with other control protocols. This function should provide services to mobility middleware core module 00B, such as launching APIs on MIP, SIP, upon request such as mobility middleware core module 800B. The mobility middleware communication module 800A may implement logic to support API calls and complete transactions.

Mobility middleware interacts with IEEE 802.16 management entities to facilitate handover procedures. When handover from FDD to IEEE 802.16 is imminent, the mobility middleware may request an 802.16 management entity to initiate an association procedure to establish an 802.16 link.

Direct mapping between IEEE 802.21 primitives (information, events, commands), some NAS, (SM and GMM), primitives already exists. No change is required on SM and GMM for mobility middleware to work with FDD NAS.

Similar to an FDD NAS, the above mapping is also provided between the IEEE 802.21 primitives and the FDD RRC primitives. No change is required on RRC for mobility middleware to work with FDD AS.

There are two aspects of mobility middleware's interaction with mobile IP. One aspect is that IEEE 802.21 can trigger mobile IP to accelerate handover. For example, if an 802.21 "MIH link down" event occurs, the mobility middleware may forward the event trigger to the mobile IP client in the mobile terminal. This triggers the mobile terminal to register with an external agent, obtain a care of address (CoA), and send a "binding update". This will reduce the delay in the mobile IP handover procedure.

Another aspect is that there is an ongoing IETF mobile IP standardization activity to support the transport of IEEE 802.21 messages (information, events, commands) between the terminal and the network via IP. This method minimizes the need for changes to existing functions on both sides by using mobile IP as a "transport means" to carry IEEE 802.21 messages between the mobile terminal and the network side.

Mobility middleware interacts with application and service enabling protocols, such as SIP. For example, an application may have certain QoS requirements. Mobility shimware will be able to map QoS requirements to the most appropriate network. Mobility shimware interacts with existing security features within mobile terminals to solve security problems during handover. No change in current security features is expected.

Existing AT commands can be used to transport commands to / from mobility middleware.

The mobility middleware communication module 800A interacts with the IP protocol stack to send and receive MIH messages over IP. A "message exchange" interface is established between the mobility middleware core module 800B and the mobility middleware communication module 800A. The mobility middleware core module 800B sends a request to the mobility middleware communication module 800A to send MIH messages to the MIH server via IP. Mobility middleware communication module 800A sends IP messages and waits for a response. After the mobility middleware communication module 800A receives a response from the MIH server, the response is forwarded to the mobility middleware core module 800B.

Mobility middleware communication module 800A interacts with MIP and SIP stacks. The mobility middleware core module 800B sends a request to the mobility middleware communication module 800A on the "message exchange" interface to initiate a MIP or SIP interaction, or the mobility middleware communication module 800A performs a MIP or SIP interaction. It may be started independently.

The invention may be implemented in any type of wireless communication system, if desired. By way of example, the present invention may be implemented in any type of IEEE 802 type system, WiMAX, LTE or other type of wireless communication system. The present invention is directed to a Logical Programmable Gate Array (LPGA), multiple LPGAs, or discrete components, or integrated circuit (s), as a software multilayer application, or on an integrated circuit such as an application specific integrated circuit (ASIC), multiple integrated circuits. And LPGA (s) and individual component (s). The invention applies to future system architectures, middleware, and applications.

The present invention may be implemented in a WTRU and includes Wideband Code Division Multiple Access (WCDMA), Time Division Duplex (TDD), (high chip rate, low chip rate), Time Division Synchronous-Code Division Multiple Access (TDS-CDMA), and Applicable to FDD air interface. The present invention is also applicable to Long Term Evolution (LTE), which is the next generation of UMTS technology.

Embodiment

1. A wireless communication handset,

(a) a terminal equipment (TE) module comprising mobility middleware, an application and protocol processor, and a terminal interface (TI);

(b) a User Service Identity Module (USIM);

(c) a mobile termination (MT) module; And

(d) a protocol stack, wherein the mobility middleware interfaces over the plurality of links with the USIM, the application and protocol processor, the protocol stack, and the MT module.

2. The method of embodiment 1, wherein the protocol stack d is

(d1) logical link control (LLC) layers;

(d2) an IEEE 802.11 media access control (LLC) layer;

(d3) an IEEE 802.11 physical (PHY) layer;

(d4) session management entity (SME); And

(d5) at least an IEEE 802.21 interface, wherein said mobility middleware establishes at least one link for interfacing with said protocol stack via said at least IEEE 802.11 interface.

An IEEE 802.11 protocol stack comprising: a wireless communication handset.

3. The embodiments 1 and 2, wherein the MT module (c),

(c1) Third Generation Partnership Project (3GPP) Frequency Division Duplex (FDD) Non-Access Stratum (NAS) including at least one IEEE 802.21 interface;

(c2) 3GPP FDD Access Stratum (3GPP) including at least one IEEE 802.21 interface, wherein said mobility middleware interfaces with said 3GPP FDD NAS and 3GPP FDD AS over a plurality of links.

4. The system of embodiment 3, wherein the 3GPP FDD NAS is:

(i) 3GPP functional mobile network (MN);

(ii) a call control (CC) unit;

(iii) a session manager (SM);

(iv) General Packet Radio Service (GPRS) Mobility Manager (GMM);

(v) Radio Access Bearer Manager (RABM);

(vi) AttenTion Command set interpreter;

(vii) ATC Advanced Technology Attachment (ATC ATA);

(viii) internet protocol (IP) relay; And

(ix) further comprising a bit stream relay.

5. The wireless communications handset of embodiments 3 and 4, wherein ATC commands are exchanged between the TE module and the MT module via the TI and the ATC ATA.

6. The method of any of embodiments 3-5, wherein the 3GPP FDD AS is:

(i) an FDD physical layer (PHY);

(ii) an FDD medium access control layer (MAC);

(iii) FDD radio link control (RLC);

(iv) a packet data compression protocol (PDCP) unit;

(v) broadcast and multicast control (BMC) units; And

(vi) a wireless communication handset, comprising a radio resource control (RRC) unit.

7. The wireless communication handset of any of embodiments 1-6, wherein the mobility middleware includes a mobility entity and a service entity.

8. The wireless communications handset of any of embodiments 1-7, wherein the mobility entity includes at least one mobility policy and at least one mobility enabler.

9. The wireless communications handset of embodiment 8, wherein the mobility policy is to perform a network detection function.

10. The wireless communication handset of embodiment 8, wherein the mobility policy performs a network selection function.

11. The wireless communications handset of embodiment 8, wherein the mobility policy is to perform an inter-network handover function.

12. The wireless communication handset of embodiment 8, wherein the mobility policy performs a parallel attach function.

13. The wireless communications handset of embodiment 8, wherein the mobility policy performs a measurement function.

14. The wireless communication handset of embodiment 8, wherein the mobility policy performs a quality of service (QoS) function.

15. The wireless communication handset of embodiment 8, wherein the mobility policy is to perform a security function.

16. The wireless communication handset of embodiment 8, wherein the mobility policy performs a power control function.

17. The wireless communication handset of any of embodiments 1-16, wherein the service entity includes at least one service policy and at least one service enabler.

18. The method of any of embodiments 8-17, wherein the mobility enabler is further configured to collect instructions, aggregate, and normalize statistics or other information received from radio access technology (RAT) networks. Wireless communication handset, interfacing with different RATs via an open application program interface (API) to provide the control / information trigger interface to the mobility policy for controlling the RAT networks for transmission to RAT networks. .

19. The wireless communication handset of any of embodiments 1-18, wherein the mobility middleware interfaces with third party applications and transport stacks through at least one open application program interface.

20. In terminal equipment,

Mobility middleware core modules;

A mobility middleware communication module in communication with the mobility middleware core module;

A first driver in communication with the mobility middleware core module; And

And a removable wireless communication device in communication with the first driver to provide a plurality of wireless transport media to applications running within the terminal equipment.

21. The terminal equipment of embodiment 20, wherein the first driver is a Network Driver Interface Specification Wide Area Network (NDISWAN) miniport driver.

22. The apparatus of embodiment 20 or 21, wherein the removable wireless communication device comprises:

A second driver in communication with the first driver;

A Universal Mobile Telecommunication System (UMTS) electrically coupled to the second driver; And

And a protocol stack electrically coupled to the second driver.

23. The system of embodiment 22, wherein the protocol stack is

(i) an IEEE 802.16 Media Access Control (MAC) layer;

(ii) an IEEE 802.16 physical (PHY) layer; And

(iii) Session Management Entity (SME)

Is an IEEE 802.16 protocol stack comprising a, terminal equipment.

24. The method of embodiment 22 or 23, wherein the UMTS is

(i) Third Generation Partnership Project (3GPP) Frequency Division Duplex (FDD) Non-Access Stratum (NAS);

(ii) terminal equipment comprising 3GPP FDD Access Stratum (AS).

25. The terminal equipment of any of embodiments 20-24, wherein the removable wireless communication device is a frequency division duplex (FDD) wireless broadband personal computer (PC) card.

26. For terminal equipment,

Mobility middleware communication module;

A first driver in communication with the mobility middleware communication module;

A removable wireless communication device in communication with the first driver for providing a plurality of wireless transport media for applications running in the terminal equipment, comprising: (i) a second driver; (ii) a removable middle communication device comprising a mobility middleware core module in communication with the mobility middleware communication module via the second driver and the first driver.

Terminal equipment comprising a.

27. The terminal equipment of embodiment 26, wherein the first driver is an NDISWAN miniport driver.

28. The device of embodiment 26 or 27, wherein the removable wireless communication device comprises:

A UMTS electrically coupled to the mobility middleware core module;

And a protocol stack electrically coupled to the mobility middleware core module.

29. The terminal equipment of embodiment 28, wherein the removable wireless communication device further comprises a mobility middleware core module and a user service identity module (USIM) in communication with the UMTS.

30. The terminal equipment of any of embodiments 26-29, wherein the removable wireless communication device is a frequency division duplex (FDD) wireless broadband personal computer (PC) card.

31. The method of any of embodiments 28-30, wherein the UMTS is

(i) 3GPP FDD NAS (Non-Access Stratum); And

(ii) terminal equipment comprising 3GPP FDD Access Stratum (AS).

32. The method of any of embodiments 28-31, wherein the protocol stack is

(i) an IEEE 802.16 Media Access Control (MAC) layer;

(ii) an IEEE 802.16 physical (PHY) layer; And

(iii) Session Management Entity (SME)

Is an IEEE 802.16 protocol stack comprising a, terminal equipment.

Although the features and elements of the present invention have been described with reference to specific embodiments in particular combinations, each feature and element may be used alone or in the absence of other features and elements of the preferred embodiments, or other features and elements of the present invention. Can be used in various combinations with or without them. The methods or flowcharts provided herein may be implemented in computer programs, software, or firmware specifically embodied in computer readable storage media for execution by a general purpose computer or processor. Examples of computer readable storage media include read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and CD- Optical media such as ROM disks and DVDs.

Suitable processors include, for example, general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), multiple microprocessors, one or more microprocessors in conjunction with DSP cores, controllers, microcontrollers, application specific integrated circuits (ASICs). Field programmable gate array (FPGA) circuits, any other type of integrated circuit (IC) and / or state machine.

The processor in conjunction with the software may be used to implement a radio frequency transceiver for use in a wireless transmit / receive unit (WTRU), user equipment, terminal, base station, wireless network controller, or any host computer. WTRUs include cameras, video camera modules, video phones, speakerphones, vibrators, speakers, microphones, television transceivers, handsfree headsets, keyboards, Bluetooth ^® modules, frequency modulated (FM) radio units, LCD display units, organic light emitting diodes (OLEDs). Can be used in conjunction with modules, implemented in hardware and / or software, such as display units, digital music players, media players, video game player modules, internet browsers, and / or any wireless local area network (WLAN) modules. .

A more detailed understanding of the invention can be obtained from the following description of the preferred embodiment given by way of example in conjunction with the accompanying drawings.

1 is a high level diagram of a 3GPP dual mode FDD / WLAN converged wireless communication handset with mobility middleware functionality configured in accordance with the present invention.

FIG. 2 is a more detailed view of the 3GPP dual mode FDD / WLAN converged wireless communication handset of FIG. 1.

3 is an exemplary block diagram of a mobility middleware architecture according to one embodiment of the invention.

4 and 5 are detailed block diagrams of the mobility middleware architecture of FIG.

6 illustrates a terminal equipment architecture having a removable wireless communication device in accordance with another embodiment of the present invention.

7 illustrates a removable wireless communication device in accordance with the present invention.

8 illustrates a removable wireless communication device according to an alternative embodiment of the present invention.

9 is a functional block diagram illustrating mobility middleware in a removable wireless communication device in accordance with the architecture of FIG.

10 is a functional block diagram illustrating mobility middleware in a removable wireless communication device in accordance with the architecture of FIG.

Claims (15)

A wireless communication handset, A terminal equipment (TE) comprising a mobility middleware, an application and protocol processor comprising a first IEEE 802.21 interface, and a terminal interface (TI); User service identity module (USIM); A NAS mobile termination (MT) module comprising a 3GPP FDD NAS comprising a second IEEE 802.21 interface and a 3GPP FDD AS comprising a third IEEE 802.21 interface; And Protocol stack containing a fourth IEEE 802.21 interface Wherein the mobility middleware interfaces over the plurality of links with the USIM, the application and protocol processor, the protocol stack, and the first, second, third, and fourth IEEE 802.21 interfaces. . The method of claim 1, wherein the IEEE 802.11 protocol stack (d), Logical link control (LLC) layer; An IEEE 802.11 media access control (LLC) layer; An IEEE 802.11 physical (PHY) layer; And Session Management Entity (SME) The wireless communication handset further comprising. The method of claim 1, wherein the 3GPP FDD NAS, 3GPP function mobile network (MN); Call control (CC) units; Session manager (SM); General Packet Radio Service (GPRS) Mobility Manager (GMM); Radio access bearer manager (RABM); AttenTion Command set interpreter (ATC); ATC Advanced Technology Attachment (ATC ATA); Internet Protocol (IP) Relay; And Bit stream relay The wireless communication handset further comprising. 4. The handset of claim 3, wherein an ATC command is exchanged between the TE module and the MT module via the TI and the ATC ATA. The method of claim 1, wherein the 3GPP FDD AS, FDD physical layer (PHY); An FDD medium access control layer (MAC); FDD radio link control (RLC); A packet data compression protocol (PDCP) unit; Broadcast and multicast control (BMC) units; And And a radio resource control (RRC) unit. In terminal equipment, Mobility middleware core modules; A mobility middleware communication module in communication with the mobility middleware core module; A first driver in communication with the mobility middleware core module; And A removable wireless communication device in communication with the first driver for providing a plurality of wireless transport media to applications running in the terminal equipment, comprising: a second driver communicating with the first driver, the second driver communicating with the second driver; And a protocol stack electrically coupled to the second driver, and electrically coupled UMTS. Terminal equipment comprising a. 7. The terminal equipment of claim 6, wherein the first driver is a Network Driver Interface Specification Wide Area Network (NDISWAN) miniport driver. The method of claim 6, wherein the protocol stack, An IEEE 802.16 medium access control (MAC) layer; An IEEE 802.16 physical (PHY) layer; And Session Management Entity (SME) Is an IEEE 802.16 protocol stack comprising a, terminal equipment. The method of claim 6, wherein the UMTS, Third Generation Partnership Project (3GPP) Frequency Division Duplex (FDD) Non-Access Stratum (NAS); 3GPP FDD Access Stratum To include, terminal equipment. In terminal equipment, Mobility middleware communication module; A first driver in communication with the mobility middleware communication module; A removable wireless communication device in communication with the first driver for providing a plurality of wireless transport media for applications running in the terminal equipment, comprising: (i) a second driver; (ii) a removable middle communication device comprising a mobility middleware core module in communication with the mobility middleware communication module via the second driver and the first driver. Terminal equipment comprising a. 11. The terminal equipment of claim 10, wherein the first driver is an NDISWAN miniport driver. The method of claim 10, wherein the removable wireless communication device, A UMTS electrically coupled to the mobility middleware core module; A protocol stack electrically coupled to the mobility middleware core module To further include, terminal equipment. 13. The terminal equipment of claim 12, wherein the removable wireless communication device further comprises a mobility middleware core module and a user service identity module (USIM) in communication with the UMTS. The method of claim 12, wherein the UMTS 3GPP FDD NAS; And Terminal equipment, including 3GPP FDD AS. The method of claim 12, wherein the protocol stack, An IEEE 802.16 medium access control (MAC) layer; An IEEE 802.16 physical (PHY) layer; And Session Management Entity (SME) Is an IEEE 802.16 protocol stack comprising a, terminal equipment.

Images