TWI339541B - Architecture for multiple radio access technology apparatus - Google Patents

Description

1339541 IX. Description of the invention: [Technical field to which the invention pertains] The present invention relates to a terminal device architecture. In particular, the present invention relates to mobile mediation software that manages multiple radio access technologies (RATs) within a terminal device.

In the telecommunications and Internet industries, "integration, is a term used to denote the emerging trend of incorporating the functionality of many different types of devices into a single unit. It encompasses the integration of networks, end devices, and services. In the communication ring, the 'integrated device usually has the ability to support multiple access technologies that communicate with different networks', such as wireless access technology (for example, IEEE 8〇21, 3rd Generation Partnership Project (3GPP), and separate storage Take (cdma) tooth®, etc.) or wired access technology (such as Ethernet leg E 802.3). Set the U to 5' with the _ the largest hard class on the network to maintain mobility. Standard 丨 j species

Yuanzhizhi J provides the link layer intelligence to assist in the shifting. The personal digital assistant (pDA) market is mainly used by the dual-processor system for data machines and the other for applications. More wood structure (a / wireless area network (two ^ UMTS) frequency division duplex (_ (MT) module is used in the j machine, mobile terminal D..., line transmission and related functions, terminal set 6 1339541 The standby module contains the end-to-end application, and the user service identification module (brain M) contains the data and programs of the mobile phone explicitly and securely. 0 to 1 Qing mobile IP or IEEE 8〇2.2] In terms of standards, although these standards stipulate (4) the implementation of (four) sexual message delivery processing, Lu is that they do not provide any implementation. In addition, there is some coordination between these mobile entities. However, there is no standard group In addition, if it is possible to provide a mobile mediation software that is not in the same platform as the Rat network, then the present invention relates to a multi-device with mobile mediation software. The subscriber provides access to *the same RAT network, such as FDD, Weekly and WLAN. In one embodiment, the calendar integrates a wireless communication handset that includes a mobile processor and a terminal Interface (5) 丄 group. By, the road and the fish integrated wireless communication mobile phone also contains the _, _ _ group is used for the operation of the terminal in the terminal 人 ΐ = = & 栌, s, The utility model comprises a mobile mediation software core module, a rights communication module, a driver and an insertable removable wireless communication device. The pluggable removable wireless communication device can be a fdd/wireless broadband 7 1339541 (WiMAX) personal computer (PC) card. The mediation software includes a set of functions including network detection, network selection, inter-network handover, parallel connection, measurement, multiple access quality of service (QoS), security, and power control. The term "wireless transmit/receive unit (WTRU)" includes but is not limited to user equipment (UE), mobile stations, fixed or mobile subscriber units, pagers, cellular telephones, personal digital assistants (PDAs), computers, notebook computers. Or any other user equipment that can operate in a wireless environment. The present invention proposes a cross-layer function called mobile mediation software, which refers to a group of different networks. Internally seamlessly mobile and support for multiple services including network detection, network selection, internet switching, parallel connectivity (when the device is connected to multiple access technologies simultaneously), measurement, multiple storage Take QoS, security, and power control. The mobile mediation software is not in any specific protocol layer, and the mobile mediation software provides cross-layer interaction. This interaction with the application and access layer is via the application. Interface (API) is completed. Figure 1 shows a schematic view of a 3GPP dual mode FDD/WLAN integrated wireless communication handset 100 in a cellular telephone incorporating the mobile mediation software functionality configured in accordance with the present invention. The 3GPP dual mode FDD/WLAN integrated wireless communication handset 100 includes a mobile terminal (MT) module 105, a terminal equipment (TE) module 110, and a subscriber service identification module (USIM) 115. The TE module 110 includes a mobile mediation software 120. Depending on the implementation, the MT module 105, the TE module 110, and the USIM 115 can be combined on a wafer or processor that is the same or separate 8 1339541. The MT module 105 can include a UMTS FDD wafer 125. In addition, the 3GPP dual mode FDD/WLAN integrated wireless communication handset 100 can also include a WLAN chip 130. As an example, although the UMTS FDD (ie, cellular network) and the WLAN are respectively represented by the wafers 125 and 130 in FIG. 1, the 3GPP dual-mode FDD/WLAN integrated wireless communication mobile phone can also support a large number of Other types of access technologies (eg, IEEE 802.15, Handheld Digital Video Broadcasting (DVB-Η), etc.). The mobile mediation software 120 integrates applications and multiple access networks. Since the mobile mediation software 120 coordinates handovers across different technologies, the mobile mediation software enables end-user applications to run seamlessly. For example, when switching between a cellular network and a WLAN, users of the 3GPP dual-mode FDD/WLAN integrated wireless communication handset 00 will not be aware of any interruptions in the streaming video. Mobile mediation software 120 coordinates and controls mobility. For example, the mobile mediation software 120 can determine that the WLAN wireless interface is degrading and can initiate the cellular stack for handover in advance. The mobile mediation software 120 can then trigger the mobile IP to change the network path. Figure 2 shows the architecture of a 3GPP dual mode FDD/WLAN integrated wireless communication handset configured in accordance with the present invention. The handset 2() includes a TE module 205, a USIM 210, an MT module 215, and an IEEE 802.11 protocol stack 220. The TE module 205 includes a mobile mediation software 225, an application and protocol processor 230, and a terminal interface (TI). The TE module 2〇5, the USIM 210, the MT module 215, and the IEEE 802.1 1 protocol stack 22〇9 1339541 can be used as needed and on the same or separate wafer or processor U and the protocol processor 230 to perform user end use. End user application 231. The end user application 231 can include voice delivery (I) via Ip, video, and the like. Further, the 'application and protocol processor 23G further includes a Session Initiation Protocol (SIP) client 232, an IP protocol suite 233, a mobile IP client 234, and an IEEE 820.21 interface that is connected to the mobile mediation software 225 via the link 28〇4. 235. As defined by the 3GPP standard, it is still said that the 21st includes the Authentication and Secret Recording (AKA) Bee Apo Pure Group 245 and the Extensible Authentication Protocol (EAP) AKA WLAN Security Module 25〇. The security modules 245 and 25 exchange the associated security information with the mobile mediation software 225 via the link 2806. The MT module 215 includes a 3GPP FDD non-access stratum (NAS) 255 and a 3GPP FDD access stratum (As) 265. NAS 255 includes 3Gpp Functional 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) 26〇. RABM 26〇 controls all types of radio access bearers (rABs). The NAS 255 further includes an alert command set interpreter (ATC) 26, an ATC Advanced Technology Attachment (ΑΤΑ) 262, an IP repeater 263, and a bit stream repeater 264. ΑΤΑ 262 ensures that the ATC commands are exchanged between the UI module 205 and the UI module 215. 3GPP H)D AS 265 includes 3GPP L1/L2/L3 functions such as FDD Physical Layer (PHY) 266, FDD Media Access Control Layer (MAC) 267, FDD Radio Link Control (RLC) 268, Packet Data Compression Protocol A 1339541 (PDCP) unit 269, a Broadcast and Multicast Control (BMC) unit 270, and a Radio Resource Control (RRC) 271. The IP repeater 263 exchanges IP packets/RABs with the PDCP unit 269. The bitstream repeater 264 exchanges with the FDD RLC 268 those IP/free packet/bitstream RABs (e.g., voice material, video telephony material, etc.). NAS 255 and AS 265 all include an IEEE 802.21 interface 235 that communicates with mobile mediation software 225 via links 2803 and 2802, respectively. The IEEE 802.1 1 protocol stack 220 includes a logical link control (LLC) layer 22, an IEEE 802.11 MAC layer 122, an IEEE 802.11 PHY Zhan 123, and a Session Management Entity (SME) 224, all of which are via the IEEE 802.21 interface 235 and links. 2801 is connected to the mobile mediation software 225 interface. As shown in FIG. 2, the function of the mobile mediation software 225 is to interact with other different entities within the 3GPP dual mode FDD/WLAN integrated wireless communication handset 100 via links 2801~2806. In addition, as previously described, the IEEE 802.21 interface 235 is included in the block 230 of the TE module 205, the 3GPP FDDNAS 255 and 3GPP FDD AS 265 of the MT module 215, and the IEEE 802.21 protocol stack 220. Mobile mediation software 225 involves a set of functions that enable seamless movement within different networks and support multiple services. One of these features is the network detection feature, which allows the terminal to recognize the characteristics of the surrounding network. Another of these functions is the network selection function, which can select the most suitable access network for users based on the characteristics of QoS, system operator, user profile, application needs, etc. in many re-existing 11 1339541 network. road. Another of these features is the inter-network handover feature for seamlessly switching from the previous network to the newly selected network. The purpose of this feature is to provide service continuity to the user. And this feature can interact with other mobile features such as Mobile IP. Another of these features is the Parallel Connection feature, which enables devices to simultaneously connect to multiple access technologies to meet specific QoS applications. For example, voice calls can be processed via a cellular system, while file transfers are processed via WLAN. This parallel connection function interacts with the switching management and the IP layer for context transfer. Another feature of this is the measurement function, which collects measurements received from different AT networks and provides inputs to other mobile mediation software functions such as network selection, power management, and more. Another feature of this is the Multiple Access QoS feature, which ensures that the QoS needs of the application are handled by the selected network. Another of these features is the security feature, which handles the security operations required to provide relevant security via AT and improve inter-network handover. For example, the security feature can authenticate the user in advance to reduce the handover delay. Another function of this is the power control function, which coordinates the power control function of each access technology to increase the battery life of the device. The mobile mediation software 225 supports IEEE 802.21 messaging (e.g., information, events, and commands) directly between the network 240 and the network via the link 28〇5b via the link 2801 and the IEEE 802.1 1 12 1339541. The method uses Mobile IP as a "vehicle for transmitting a positive 02.21 message between the mobile terminal and the network, thereby minimizing the need to change existing functions at both ends. Mobile mediation software 225 via chain The way 2806 interacts with the existing security functions 245 and 250 in the handset 200 to address security issues during the handover process. When switching between the UMTS and the WLAN network, security must be ensured. Therefore, the mobile agent Software 225 requires input from UMTS security components (such as AKA bee security module 245) and wlan security components (such as WLAN ΑΚΑ WLAN security module 25〇) to ensure this consistency. Existing AT commands from ΑΤΑ 262 It can be used to communicate commands to/from the mobile mediation software 225 via links 28〇5& and 2805b. Mobile mediation software 225 via link 2804 and IEEE 802.21 mediation, 235 and applications such as SIP client 232 Interaction with service-enabled agreements For example, applications may have certain requirements. Mobile media software 225% can map such qos requirements to Suitable network. ^ Mobile mediation software 225 interacts with IEEE 802.11 via link 2801 and interacts with 220 to facilitate the handover process. Since 3〇ρρ dual & FDD/WLAN integrated wireless communication handsets 2 from UMTS The area covered by the network moves to the area covered by the IEEE 802.11 network, so the handover from FDD to IEE 211 will be performed at this time. In the process of switching 14 1339541, the mobile mediation software 225 can request the IEEE 802.11 protocol stack 220 to start. The associated program required to establish the link 280. The present invention is directed to a mobile architecture in which the application processor is not on the same platform as the RAT network. The architecture is split between the PC and the pluggable removable wireless communication device. The architecture introduces some complexity and imposes additional requirements on mobile mediation software. A mobile mediation architecture for such devices will be introduced here, where, for example, the device can be a specific dual mode FDD/ WiMAX device. Figure 3 shows the features of the mobile mediation software 225, wherein the mobile mediation software includes a mobile entity 305 and a service entity 310, and The mobile vehicle body includes functions that allow seamless movement within different networks and support multiple services. The mobile entity 305 includes a relatively independent smart decision generation portion (ie, mobile strategy 315) and an interface portion (ie, mobile enablement). The service entity 310 also includes a relatively independent smart decision generation portion (ie, the service policy 325) and an interface portion (ie, the service enabler 330). The service enabler 33 is defined in accordance with the Open Mobile Alliance (OMA) or 3GPP protocols and programs. The modular design of the architecture enables the mobile mediation software 225 to support a growing number of different end-user applications 335 and rat. For example, if WiMAX is added to the device as a new RAT, a WiMAX-enabled interface will be added to the mobile enabler 320, while the rest of the mobile mediation remains unchanged. The mobile "software 225 is in the transport stack 340 (e.g., 3GPP, Global System of Mobiles (GSM), WLAN, Long Term Project Evolution). Typically, there is a type of interaction with the mobile mediation software 225. One type of application is an end-user application (eg, two-pig transmission (v〇ΙΡ), instant messaging, etc.) Another = is a five-layer protocol (such as mobile port or SIP). These applications are for the two-sigma service intermediary. Software function control for coordination. For example, terminal

=3Γ to use the service and mobile application programming interface (ΑΠ) in a coordinated manner via the open ΑΡΙ345. The good intermediary software 225 is not in any particular protocol layer. Instead, the migration (4) provides cross-layer interaction, and the interactions at the seam end: application 335 and the transfer stack 34G are performed via open ^ APIs 345 and 350, respectively. Figure 4 shows the detailed structure of the mobile strategy 315 and = = = 320 in the mobile entity 3〇5. Mobile policy 315 is a smart entity,

ς = Re-access (4) questions are processed, and the mobility of the columns is raised, and the strategy and wisdom are provided. It is said that RAT-() coordination is provided. The entity is coupled to the subscription interface via a mobile enabler 32 to monitor and control the underlying access technology stack. In addition, the mobile policy 315 also controls the open API secret terminal. The mobile policy 315 includes the ability to enable seamless support and support for multiple services within different networks, including: ") Network Detection 352, which allows the terminal to identify the characteristics of the surrounding network. The network selection function 354 can select one of the plurality of access networks that is most suitable for the user according to (10), the system operator, the user profile, the application requirement, and the like; 3) the inter-network switching function 356 The function of the 16 1339541 无缝 seamless switch from the previous network to the newly selected network (the purpose is to provide services for users, this function interacts with other mobile functions such as mobile IP), 4) Parallel connection function 358, which can help the device to connect to multiple RATs, is more suitable for Q〇s applications (for example, voice can be processed via cellular communication' and file transfer is via wl). The parallel connection function interacts with the handover (H〇) management and IP layer for context transfer; 5) measures Wei, the function "those measurements received from 3 RAT" and provides input for other mobile mediation software functions, Such as network selection, power management, etc.; 6) multiple access Q〇S function, which ensures that the needs of the application are handled by the selected network; 7) security function 364, which provides relevant security for the RAT Improve the security operations required for inter-network handover (eg, the security function can authenticate the user in advance to reduce handover delay); and 8) power control function 366' power control for each access technology The functions are coordinated to increase the battery life of the device. It should be noted that the mobile policy function does not replace the existing mobile functions in each radin. For example, the inter-network handover handles the problem involving multiple access switching, and its Will interact with the switching function of each access technology. The mobile enabler 320 is a thin, functional layer connected to different rAT interfaces. By using an open API, it can allow the mobile device 32〇 enable collecting statistical information from the RAT and transmits a command to the RAT. In addition, it organizes and normalizes the information received from different RATs and provides a control/information trigger interface to the mobile policy entity 315, thereby allowing control of the rat 17. The mobile enabler 320 receives and processes the measurements from the transport stack 34 (see Figure 3) and forwards the processed information to the mobile policy entity 315. In addition, it also sends commands and requests from the mobile policy entity 21 to the end user application 335 (see Figure 3). The mobility enable provides a thin layer for 320 to isolate the mobile policy 315 from any particular access network, thereby modularizing the design and facilitating expansion to different RATs. Figure 5 shows an example of a service entity 310. Service enabler 330 is a set of software functions and standardized, which enables third-party application developers to define and build mobile device applications independently of the underlying transport technology. A typical example of such allowed technologies is Drm. 505, instant messaging 510, and presence service 515. Using these examples separately in a typical implementation, the end user application opener can develop an application that allows DRM protected content to be sent via the instant messaging device only when certain rendering conditions are in place. The service enabler 33 allows the end user application to make action calls and queries for the enabled functions in a standardized manner ' thus theoretically allowing the development of an unlimited number of applications, all of which are supported by a supported transmission technique Operates in a transparent manner. The service policy 325 is a smart entity' that handles service related issues and provides policies for the coordination of different applications supported by the service enabler 330. Another embodiment according to Fig. 6 is directed to a variety of transmission mechanisms known as 1339541. The application typically sends and receives data unchanged. Details regarding the transmission are hidden by the mobile mediation software 700. The mobile mediation software 700 provides a unified and consistent interface for applications in the terminal device 600'. Mobile mediation software 700 can determine which wireless technology to initiate and use for data transmission. The mobile mediation software 700 is implemented entirely in the terminal device 600', which allows for higher computing power, memory, and power, thereby enabling the mobile mediation software to support more features, functions, and policies. The mobile mediation software 700 communicates with the protocol software elements (e.g., UMTS 705 and WiMAX 710) residing on the pluggable decibelable wireless communication device 605' via the USB link. The commands and responses between the mobile mediation software 700 and the contract software are transmitted over the USB link. The communications driver 715 receives the USB traffic and will then route the mobile media commands and responses to and from the agreed software components. Figure 8 shows an additional dual mode FDD/WiMAX PC card architecture in accordance with the present invention. In FIG. 8, the mobile mediation software communication module 800A resides on the terminal device 600', and the mobile mediation software core module 800B resides in the pluggable removable wireless communication device 605 between the communication driver 715 and the UMTS 705 and the WiMAX 710. A unified and consistent interface is provided for applications in the mobile mediation software core module 800B for the terminal device 600. The mobile mediation software core module 800B determines the wireless technology to be initiated and used for data transfer. The mobile mediation software communication module 800A supports sending and receiving higher level messages such as IP messages. The mobile mediation software core module 800B is implemented on the pluggable removable 20 1339541 wireless communication device 605" which enables the terminal device 600 to perform access faster and react to link level events, thereby improving handover effectiveness. The mobile mediation software core module 800B communicates via an API call or via a call to an AT command to a contracted software component (eg, UMTS 405 and WiMAX 410) residing on the pluggable removable wireless communication device 〇5". The commands and responses between the software communication device 800A and the protocol software are transmitted over the USB link. The communication driver 715 receives the USB traffic and then routes those to and via the mobile mediation software core module 8〇〇b. Mobile mediation software commands and responses from the agreed software component. Figure 9 is a functional block diagram depicting the mobile mediation software in the terminal device 600' architecture in accordance with Figure 7. In this scenario, assume the operation on the terminal device 600. The system (OS) is a Microsoft (MS) Windows OS, and the interface between the terminal device 600' and the pluggable removable wireless communication device 605 is USB. As shown in FIG. 9, in the terminal device 600', the mobile agent The software is implemented as two modules: a mobile mediation software communication module 800A and a mobile mediation software core module 800B, which is a network driver interface. An extension of the NDIS wide area network (NDISWAN) mini-drive 905. The end user application in the terminal device 600' may include voice over IP (VoIP), video, etc. The terminal device 600, further including a session initiation protocol (SIP) client 920, Internet Protocol (IP) protocol suite 930, and Mobile IP (MIP) client 935. As previously described with reference to Figure 4, mobile mediation softwares 800A and 800B communicate via an API, such as 21 1339541 communication device 605" to manage. The WAN command from the terminal device 600" is transmitted to the pluggable removable wireless communication device 605" via the USB link and is intercepted by the mobile mediation software core module 800B. The mobile mediation software core module 800B can then determine how to distribute the commands and data. In addition, the mobile mediation software core module 800B also performs management functions such as monitoring link status, selecting links and preparing them for future handovers, and at the time of actual handover, the mobile mediation software core module • 800B will This switch will be performed. In order to continue the data session, the mobile mediation software communication module 800A in the terminal device 600" needs to initiate other high-level protocols, such as MIP and SIP programs. Once the command from the mobile mediation software core module 500B is received, the mobile mediation software communication module Such a program is initiated by group 800A. The mobile mediation software communication module 800A interacts with a high level agreement residing in the terminal device 600" to provide efficient communication.

In the structure of Figure 10, the mobile mediation software core module resides on the MT side. This will allow link-level activities to be used quickly. This allows them to respond quickly to such events and trigger an action. Since the core module is implemented on the MT platform and is connected to the TE interface using a standard USB/WAN interface, its impact on the PC side is small. In addition, it is more likely and should be able to implement simple connections and configurations.

The mobile mediation software core 800B can perform important tasks such as network detection and network selection, and the mobile mediation software communication module 800A performs those that need to implement message exchange on the IP and call the application interface on other control stacks (API). ) function. The mobile mediation software core module 800B 24 1339541 and the mobile mediation software communication module 800A exchange messages via independent interfaces. The mobile mediation software core module 800B acts as the primary mobile mediation software function, whereby multiple services are supported by implementing control functions and 链路8〇2·21 link events and services. For the mobile mediation software core module 800Β, one service it can provide includes network detection that allows the terminal to recognize the characteristics of the surrounding network.

Another service provided by the mobile mediation software core module 800 is network selection. The service selects the access network that best meets the user's requirements based on QoS, system operator, user profile, application needs, and so on within many re-access networks.

Another service that the mobile mediation software core module 8〇〇b can provide also includes inter-network handover. This function performs a seamless transition from the previous network to the newly selected network. Its purpose is to provide service continuity to users. And this feature interacts with other mobile features such as Mobile IP. "There are fewer spears in the move" software core module 8〇〇b can provide additional services including

^Sub-Q〇s °Hai Green Insurance is selected by the selected network to handle the QoS needs of the application. Another service that the mobile mediation soft axis module 8_ can provide includes a parallel connection service. The service can initiate simultaneous connection with multiple networks to satisfy the qgS application. For example, a voice call can be processed via a cellular system' while file transfer is via a WLAN. This parallel connection function interacts with the switching layer (4) and the IP layer of the context transfer. 25 1339541 Another service that the mobile mediation software core module 800B can provide includes power management. The service coordinates the power control function of each access technology to increase the battery life of the device. Another service that the mobile mediation software core module 800B can provide also includes measurement services. The service collects measurements received from different ATs and provides input to other mobile mediation software functions, such as network selection, power management, and the like. • Another service that mobile mediation software core module 800B can provide also includes security. This service handles the security operations required to provide relevant security via AT and improve inter-network handover. For example, the security feature can authenticate users in advance to reduce handover delays. Another service that mobile mediation software core module 800B can provide also includes routing functionality. The mobile mediation software core module 800B routes control messages and data between the control application in the terminal device 600 and the communication protocol stack of the WiMAX 710 that can be plugged into the removable wireless communication device 605. • Mobile mediation software communication module 800A can provide MIH messaging. This function will accept the MIH message sent from the mobile mediation software core module 800B via the IP to the MIH server. The mobile mediation software communication module 800A will then call the appropriate API and will send it in the IP stack available to the computing platform of the terminal device 600. Alternatively, the mobile mediation communication module 800A should be able to receive MIH messages from the MIH server via IP and send this message to the mobile mediation software core module 800B. The mobile mediation software communication module 800A provides support for interaction between the mobile mediation software core module 26 1339541 800B and other control protocols. This function will provide services for the mobile mediation software core module 800B, such as calling the MIP, the sip on the sip, etc. when the mobile mediation software core module 800B makes a request. The mobile mediation software communication module 8A can perform logical processing' to support API calls and complete the process. The mobile mediation software interacts with the IEEE 802.16 management entity to help implement the handover process. Upon switching from FDD to IEEE 802 16, the mobile mediation software can request the 802.16 management entity to initiate the associated procedure to establish an 802.16 link. In addition, direct mapping between IEEE 802.21 primitives (information, events, commands) and certain NAS (SM and GMM) primitives already exists. For SMs and GMMs used in private mediation software, they can work with FDD NAS without any changes. Similar to the FFD NAS, the above mapping is also provided between the IEEE 802, 21 primitive and the FDD RRC primitive. For RRC for mobile mediation, it works with FDD AS without modification. The interaction between mobile mediation software and mobile IP is divided into two aspects. One aspect is that IEEE 802.21 can trigger a mobile ip to speed up the handover. For example, in the event of an 802.21 MIH Keyway Disconnect event, the mobile mediation software can forward the event trigger to the mobile IP client in the mobile terminal, thereby triggering the mobile terminal to register with the foreign agent, obtaining the temporary address (care 〇f address) and send update (binding update), which can reduce the delay in the mobile IP handover process. On the other hand, there is an ongoing IETF mobile ip standard activity, so that 27, 54i support terminal and network IEEE 802.21 messaging C information, events, and commands between IPs. This method uses Mobile IP as a "vehicle" for communicating IEEE 802.21 messages between the mobile terminal and the network. This minimizes the need to change existing functionality at both ends.

Mobile mediation software interacts with applications and service enablement protocols such as SIP. For example, an application may have a certain q〇S requirement. Mobile mediation software can map this QoS requirement to the most appropriate network. Read the mobile shimware to interact with existing security features in the mobile terminal to resolve security issues in the handover process. In the existing security functions, there is no need to change. Existing AT commands can be used to pass commands to and from the mobile mediation software. The mobile mediation software communication module 800A interacts with the Ip protocol stack to communicate via IP and purely Xinjiang messages. On the moving towel

The heart module 8_ and the mobile mediation software communication module _A will be built between the second == _ medium server to send Xinjiang $ ^ to ask for help through the IP, English poetry, heart. The mobile mediation software communication module δΟΟΑ will send two = t responses. In the mobile mediation software communication module _ 中 in the recording body image (four) coffee is forwarded to the mobile interaction: body communication module 8 〇〇Α and ΜΙΡ and SIP stack to carry out the threat of 8 (10) exchange, 〇 丨; 丨 software communication The module 800 sends a request to activate the MIP or SIP interaction, or the mobile mediation software module 800A can also initiate MIP or sip interaction independently. The present invention can be implemented in any type of wireless communication network as needed. For example, the present invention can be implemented in any type of IEEE 802 type system, WiMAX 'LTE, or any other type of wireless communication system. In addition, the present invention can also be implemented as a multi-layer application in a software or in an integrated circuit, which can be an exclusive integrated circuit (ASIC), a plurality of integrated circuits, and a logic programmable gate array (LPGA). , a combination of multiple LPGAs, knife elements or slab circuits, LPGAs, and discrete components. The present invention is applicable to future system architectures, mediation software, and applications. The present invention can be implemented in a WTRU and is suitable for Wideband Coded Multiple Access (WCDMA), Time Division Duplex (TDD) (High Chip Rate, Low Chip Rate), Time Division Synchronous Code Division Multiple Access (TDS_CDMA) ) and FDD empty mediation. In addition, the present invention is also applicable to the long-term project evolution (LTE) of the next-generation UMTS technology. Example 1 · A wireless communication handset comprising: (a) a terminal device (TE) module M, including: mobile mediation software, application software and protocol processors, and a terminal interface (11); (b) user services Identification module (usim). (c) mobile terminal (MT) module; and (d) coordinating the stacking of mobile media software with USIM, application software and protocol processors, protocol stacking, and MT mode via complex links Group interface connection. 29 1339541 2. The wireless communication handset of embodiment 1, wherein the protocol stack (d) is an IEEE 802.11 protocol stack, comprising: (dl) a logical link control (LLC) layer; (d2) IEEE 802.11 media access control (MAC) layer; (d3) IEEE 802.11 entity (PHY) layer; (d4) Session Management Entity (SME); and (d5) at least one IEEE 802.21 interface, wherein the mobile mediation software establishes at least one link via the interface To connect with the stacking interface. 3. The wireless communication handset of any one of embodiments 1 and 2, wherein the MT module (c) comprises: (cl) a third generation partner project (3GPP) frequency division including at least one IEEE 802.21 interface Duplex (FDD) Non-Access Stratum (NAS); and (c2) 3GPP FDD Access Layer (AS) including at least one IEEE 802.21 interface, where the mobile mediation software is connected to the 3GPP FDD NAS and 3GPP FDD via a complex link AS interface connection. 4. The wireless communication handset of embodiment 3, wherein the 3GPP FDD NAS further comprises: (i) a 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) Alert Command Set Interpreter (ATC); (vii) ATC Advanced Technology Annex (ATA); 30 1339541 (viii) Internet Protocol (IP) repeater; and, (ix) bitstream repeater. 5. The wireless communication handset of any of embodiments 3 and 4 wherein the ATC command is exchanged between the TE module and the MT module via TI and ATC. 6. The wireless communication handset of any one of embodiments 3 to 5, wherein the 3GPP FDD AS comprises: • (i) an FDD physical layer (PHY); (ii) an FDD medium access control layer (MAC); (iii) FDD Radio Link Control (RLC); (iv) Packet Data Compression Protocol (PDCP) unit; (v) Broadcast and Multicast Control (BMC) unit; and (vi) Radio Resource Control (RRC) unit. The wireless communication handset of any one of embodiments 1 to 6, wherein the mobile mediation software comprises a mobile entity and a service entity. The wireless communication handset of any of embodiments 1-7, wherein the mobile entity comprises at least one mobility policy and at least one mobility enabler. 9. The wireless communication handset of embodiment 8 wherein the mobility policy performs a network detection function. 10. The wireless communication handset of embodiment 8 wherein the mobility policy performs a network selection function. 11. The wireless communication handset of embodiment 8 wherein the mobility policy performs an inter-access point handover function. 31 1339541 12. The wireless communication handset of embodiment 8 (4), wherein the mobility policy performs a parallel connection function. !3. The wireless communication 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 device of embodiment 8, wherein the mobile policy performs a security function. 16. The wireless overnight handset of embodiment 8 wherein the mobility policy enforces power control functionality. The wireless communication handset of any of embodiments 1 to 16, wherein the service entity comprises at least one service policy and at least one service enabler. 18. The wireless communication handset of any of embodiments 8-17, wherein the mobile enabler is connected to a different radio access technology (RAT) interface via an open application interface (Apj) to collect Organize and standardize statistical or other information received from the RAT network and transmit commands to the RAT network and provide a control/information trigger interface to the mobile policy to control the RAT network. The wireless communication device of any one of embodiments 1 to 18 wherein the mobile mediation software is connected to the third party application software and the transport stack interface via at least the "open application" (4). 2〇. A terminal device, comprising: a mobile mediation software core module; 32 1339541 a mobile mediation software communication module communicating with a mobile mediation software core module; a first driver for communicating with a mobile mediation software core module And an insertable removable wireless communication device in communication with the first driver for providing multiple wireless transmission media to the application software running in the terminal device. 21. The terminal device of embodiment 20, wherein the first driver is a Network φ Driver Interface Specification (NDIS) Wide Area Network (NIDSWAN) mini-埠 drive. The terminal device of any one of embodiments 20 and 21, wherein the pluggable wireless communication device further comprises: a second driver in communication with the first driver; and a universal movement electrically coupled to the second driver Telecommunications system (UMTS); and a protocol stack electrically coupled to the second driver. The terminal device of embodiment 22, wherein the protocol stack is an IEEE 802.16 protocol stack, the protocol stack comprising: (i) an IEEE 802.16 medium access control (MAC) layer; (ii) IEEE 802.16 Entity (PHY) layer; and (iii) Session Management Entity (SME). The terminal device according to any one of embodiments 22 and 23, wherein the UMTS comprises: (i) a third generation partnership project (3GPP) frequency division duplex (FDD) non-access stratum (NAS); And 33

Oi) 3GPP FDD Access Stratum (AS). ★ The bias-input wireless communication device is a frequency division duplex (FDD) benefit line video PC (PC) card. ... deep 26 · a kind of terminal equipment, including: mobile intermediary software communication module; = dynamic intermediary software communication module to pass (four) first-driver; and human first driver to communicate the pluggable extraction two 'for the terminal The application software running in the device provides multiple media transmissions, wherein the pluggable removable wireless communication device includes a flash drive and a mobile media core module, and the module is powered by the first actuator and the first The driver and the mobile mediation software communication module perform 2<7. The terminal device as described in Embodiment 26, wherein the first driver is a network driver interface specification (10) IS) a wide area network (face swan) fan" The terminal device of any one of embodiments 26 and 27, wherein the pluggable wireless communication device further comprises: a universal mobile telecommunication system (UMTS) electrically coupled to the mobile mediation core module; and The mobile mediation software core module is a stack of protocols. The terminal device of embodiment 28, wherein the pluggable-type, the line-pass L device further comprises a user service identification module (USIM) that communicates with the mobile mediation software core module and the umts. The terminal device according to any one of embodiments 26 to 29, wherein the pluggable wireless communication device is a frequency division duplex (FDD) wireless _ broadband personal computer (PC) card. The terminal device according to any one of embodiments 28 to 30, wherein the UMTS comprises: (i) a third generation partnership project (3GPP) frequency division duplex (FDD) non-access layer (NAS); And • (ii) 3GPP FDD Access Layer (AS). The terminal device of any one of embodiments 28 to 31, wherein the protocol stack is an IEEE 802.16 protocol stack, the protocol stack comprising: (i) an IEEE 802.16 medium access control (MAC) layer; (ii) IEEE 802.16 entity (PHY) layer; and (iii) Session Management Entity (SME). Although the features and elements of the present invention are described in a particular combination in the preferred embodiments, each feature or element can be used alone or in the absence of the other features and elements of the preferred embodiment. It is not used in various situations in combination with other features and elements of the invention. The method or flow chart provided by the present invention can be implemented in a computer program, software or firmware executed by a general purpose computer or processor, wherein the computer program, software or firmware is tangibly embodied in a computer readable storage medium. Examples of computer readable storage media include read only memory (ROM), random access memory (RAM), scratchpad, cache memory, semiconductor memory device, internal hard disk, and removable disk. Magnetic media, magneto-optical media, and optical 35 1339541 media such as CD-ROM discs and digital versatile discs (DVDs). Suitable processors, for example, include: general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), multiple microprocessors, one or more microprocessors associated with a DSP core, Controller, microcontroller, dedicated integrated circuit (ASIC), field programmable gate array (FPGA) circuit, any integrated circuit and/or state machine. The processor associated with the software can 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. The WTRU may be used in conjunction with modules implemented in hardware and/or software, such as cameras, camera modules, video phones, speaker phones, vibration devices, speakers, microphones, television transceivers, hands-free headsets, keyboards, Bluetooth® Module, frequency modulation (FM) wireless unit, liquid crystal display (LCD) display unit, organic light emitting diode (OLED) display unit, digital music player, media player, video game player module, internet browser and / or any wireless local area network (WLAN) module. 36 1339541 [Brief Description of the Drawings] The present invention will be understood in more detail from the following description of the specific embodiments, which are provided by way of example : Figure 1 shows a schematic view of a 3GPP dual-mode FDD/WLAN integrated wireless communication handset incorporating the functionality of the mobile mediation software configured in accordance with the present invention, • Figure 2 shows the 3GPP dual-mode FDD in Figure 1 / WLAN integrated wireless communication handset more detailed view; Figure 3 is an exemplary block diagram of a mobile mediation software architecture in accordance with one embodiment of the present invention; Figures 4 and 5 show the mobile mediation software architecture in Figure 3 Detailed block diagram; FIG. 6 shows a terminal device architecture with a pluggable removable wireless communication device in accordance with another embodiment of the present invention; • FIG. 7 shows a pluggable removable wireless communication device in accordance with the present invention; Figure 8 is a diagram showing an insertable removable wireless communication device in accordance with an alternative embodiment of the present invention; Figure 9 is a diagram showing the insertable pumping in accordance with the structure of Figure 7. Wireless communication apparatus in a mobile middleware functional block diagram; FIG. 10 is described in terms of the insertably removable wireless communication device architecture of FIG. 8 in a mobile middleware functional block diagram. 37 1339541

[Main component symbol description] 200 mobile phone 280! ~ 2806 link 305 mobile entity 310 1 business entity 600 Ί 500, 600" terminal device 605', 605" wireless communication device 3GPP third generation partner project WLAN wireless local area network AKA Authentication and Key Distribution API Application Programming Interface ΑΤΑ Southern Technology Attachment ATC Alert Command Set Interpreter BMC Broadcast and Multicast Control WiMAX Wireless Broadband C Control cc Call Control ΕΑΡ Extended Authentication Protocol FDD Crossover Duplex GMM Mobile Manager GSM Global System for Mobile Communications IP Internet Protocol L-Layer LLC Logical Link Control LIE Long-Term Project Evolution MAC Media Access Control Layer MIH Media Independent Switching NDISWAN Network Driver Interface Specification Wide Area Network MIP Mobile EP MN Mobile Network OMA Open Mobile Alliance OS Operating System PC Personal Computer PDA Personal Digital Assistant PDCP Packet Data Compression Agreement PHY Entity QoS Quality of Service RABM Radio Access Bearer Manager RL Wireless Link RR Radio Resource SIP Session Initiation Protocol SM Session Manager SME Session Management Entity UMTS Universal Mobile Telecommunications system USIM User Service Spike Identification Module VoIP Voice Transfer 38

Claims (1)

竹年丨1(10) Japan Ten, the scope of application for patents: 1 · A wireless communication mobile phone, comprising: a terminal equipment (TE) module, the module includes - an application and protocol processor, and - a terminal interface (5); a user a service identification module (USIM); a mobile terminal (MT) module; and a protocol stacking of the mobile media software via the complex M, the lie and the mosquito (4), the stack is called the interface interface . In 2. Patent application (4) 1 Yunlai wireless communication mobile phone, wherein the agreement stack is - IEEE8G2.il protocol stack, including:, a logical link control (LLC) layer; an IEEE 802.11 media access control (MAC) layer An IEEE 802.il entity (ΡΗγ) layer; a session management entity (SME); and at least an IEEE8G2.21 interface, the mobile mediation software is configured to establish at least a link via the interface, and stack with the protocol Interface connection. 3. The wireless communication handset of claim 1, wherein the UI module comprises: a second generation partner project (3GPP) frequency division duplex (FDD) non-access layer (NAS), including at least An IEEE 8 〇 2 21 interface; and a 3GPP FDD access layer (AS) including at least one IEEE 8 〇 2 21 interface, wherein the mobile mediation software is via the complex link with the 3 〇ρρ FDD NAS and the 3GPP FDD AS interface connection. 1339541 4 - The wireless communication handset of claim 3, wherein the 3GPP FDD NAS further comprises: a 3GPP functional mobile network (MN) a call control (CC) unit; a session manager (SM); A General Packet Radio Service (GPRS) Mobility Manager (GMM); a Radio Access Bearer Manager (RABM); an Alert Command Set Interpreter (ATC); an ATC Southern Technology Attachment (ΑΤΑ), an Internet Road Protocol (IP) repeater; and a one-way stream repeater. 5. The wireless communication handset of claim 3, wherein the ATC command is exchanged between the TE module and the MT module via the TI and the ATC. 6. The wireless communication handset of claim 3, wherein the 3GPP FDD AS comprises: an FDD physical layer (PHY); an FDD medium access control layer (MAC); an FDD radio link control (RLC) a packet data compression protocol (PDCP) unit; a broadcast and multicast control (BMC) unit; and a radio resource control (RRC) unit. The wireless communication handset of claim 1, wherein the mobile intermediary software comprises a mobile entity and a service entity. 41. The wireless communication handset of claim 7, wherein the mobile entity comprises at least a mobility policy and at least a mobility enabler. For example, in the wireless communication mobile phone described in claim 8, wherein the mobile policy enforcement-network detection function. The wireless communication handset of claim 8, wherein the mobile workstation performs a network selection function. 11. The wireless communication handset of claim 8, wherein the H' mobile policy enforcement-access point switching function. 12. The wireless communication handset of claim 8, wherein the mobile policy performs a parallel connection function. ^ 13 · A wireless communication handset as described in claim 8 of the patent application, wherein the 5 Hai mobile strategy performs a measurement function. The wireless communication handset of claim 8, wherein the mobile policy performs a quality of service (Q〇s) function. 2. A wireless communication handset as described in claim 8 of the patent application, wherein the mobile strategy performs a security function. The wireless communication handset of claim 8, wherein the mobility policy performs a power control function. The wireless communication handset of claim 7, wherein the service entity comprises at least a service policy and at least a service enabler. 18. The wireless communication handset of claim 8, wherein the mobile enabler is connected to the K set, (4) and # via an open application interface (Αρι) and a different wireless access technology (UAT) interface. Normalize statistics or other information received from the RAT network, and: 42 1339541 RAT network transmits commands and provides a control/information trigger interface to the mobile policy to control the RAT network. The wireless communication handset of claim 1, wherein the mobile mediation software is coupled to the third party application and the transport stack interface via at least one open application interface. 20. A terminal device, comprising: a mobile A-media software core module; a mobile mediation software communication module, which communicates with the mobile mediation software core module; a first driver, and the mobile mediation software core The module is in communication; and an insertable removable wireless communication device is in communication with the first driver for providing multiple wireless transmission media to an application running in the terminal device. 21. The terminal device of claim 20, wherein the first drive is a Network Drive Interface Specification (NDIS) Wide Area Network (NIDSWAN) mini-drive. 22. The terminal device of claim 20, wherein the pluggable removable wireless communication device further comprises: a second driver in communication with the first driver; a universal mobile telecommunications system (UMTS), It is electrically coupled to the second driver; and a protocol stack electrically coupled to the second driver. The terminal device of claim 22, wherein the 43 1339541 protocol stack is an IEEE 802.16 protocol stack, the protocol stack comprising: an IEEE 802.16 medium access control (MAC) layer; an IEEE 802.16 entity ( PHY) layer; and a Session Management Entity (SME). 24. The terminal device of claim 22, wherein the UMTS comprises: a third generation partnership project (3GPP) frequency division duplex (FDD) non-access stratum (NAS); and a 3GPP FDD Take the layer (AS). The terminal device of claim 20, wherein the pluggable removable wireless communication device is a frequency division duplex (FDD) wireless broadband personal computer (PC) card. a terminal device comprising: a mobile mediation software communication module; a first driver communicating with the mobile mediation software communication module; and a pluggable removable wireless communication device coupled to the first driver Communicating for providing a multi-wireless transmission medium to an application running in the terminal device, wherein the pluggable removable wireless communication device comprises: a second driver and a mobile mediation software core module, The second driver and the first driver communicate with the mobile mediation software communication module. The terminal device of claim 26, wherein the first driver is a network driver interface specification (NDIS) wide area network 44 1339541 • - (NDISWAN) mini port driver. 28. The terminal device of claim 26, wherein the pluggable removable wireless communication device further comprises: a universal mobile telecommunications system (UMTS) electrically coupled to the mobile mediation core module; and a A protocol stack that is electrically coupled to the mobile mediation core module. The terminal device of claim 28, wherein the pluggable removable wireless communication device further comprises a user service identification module (USIM) in communication with the mobile mediation software core module and the UMTS. The terminal device of claim 26, wherein the pluggable removable wireless communication device is a frequency division duplex (FDD) wireless broadband personal computer (PC) card. 31. The terminal device of claim 28, wherein the UMTS comprises: a third generation partner project (3GPP) frequency division duplex (FDD) non-access stratum (NAS); and a 3GPP FDD access Layer (AS). 32. The terminal device of claim 28, wherein the protocol stack is an IEEE 802.16 protocol stack. The protocol stack includes: an IEEE 802.16 medium access control (MAC) layer; an IEEE 802.16 entity (PHY) Layer; and a session management entity (SME). 45