Patent Abstract:
A multiple wireless access technology capable (WAT-capable) wireless transmit receive unit (WTRU) includes a registration message generator configured to generate a registration message indicating that the WTRU is configured to communicate using an IEEE 802.11x technology. The WTRU also includes a transmitter configured to send the registration message via an IEEE 802.11x WLAN to a cellular network during registration with the cellular network, and a receiver configured to receive services from the cellular network via the WLAN. The registration message further indicates that the WTRU is configured to receive Short Message Service (SMS) messages from the cellular network via the WLAN. The WTRU receiver receives services that include Short Message Service (SMS) messages.

Full Description:
CROSS REFERENCE TO RELATED APPLICATIONS 
     This application is a continuation of U.S. patent application Ser. No. 10/880,696, filed on Jun. 30, 2004, which claims the benefit of U.S. Provisional Application No. 60/515,479 filed on Oct. 29, 2003, which are incorporated by reference as if fully set forth herein. 
    
    
     FIELD OF INVENTION 
     The present invention relates to wireless communication systems. More particularly, the present invention relates to delivery of services to multi-technology capable wireless transmit/receive units. 
     BACKGROUND 
     Although the meanings of the following acronyms are well understood by skilled artisans, the following list is deemed to assist in a better understanding of the invention: 
     3GPP third generation partnership project 
     AAA authentication, authorization, and accounting 
     AP access point 
     CCF charging control function 
     CSCF call state control function 
     EIR equipment identity register 
     GGSN gateway GPRS support node 
     GMSC gateway MSC 
     GPRS general packet radio system 
     GSM global system for mobile communication 
     HLR home location register 
     HSS home subscriber server 
     IP internet protocol 
     IWMSC interworking MSC for SMS 
     MMS multi-media services 
     MS mobile station 
     MSC mobile switching station 
     PDG packet data gateway 
     PHY physical layer 
     PDA personal digital assistant 
     SC service center 
     SIM subscriber identity module 
     SMS short messaging service 
     TCP transmission control protocol 
     UMTS universal mobile telecommunications system 
     VoIP voice over internet protocol 
     WAG wireless application gateway 
     WAT wireless access technology 
     WLAN wireless local area network 
     WTRU wireless transmit/receive unit 
     The trend in the wireless industry is to increasingly support wireless transmit/receive units (WTRUs) that support multiple Wireless Access Technologies (WATs) in heterogeneous networks. Network interworking introduces the possibility of several WATs (e.g., several different types of wireless local area networks) such 802.11a, 802.11b, 802.11g, etc. being connected to a cellular type network (e.g., a Universal Mobile Telecommunications System (UMTS) network). Further, using subscriber identity module (SIM) technology, users may switch their 802.11b card to an 802.11a card, for example, or any other type of multi-mode card using their SIM to access the network while the network is not totally aware of the WAT supported at the WTRU level. Additionally, users may use their 802.11 cards, for example, in different types of WTRUs, such as when they obtain a new laptop or personal digital assistant (PDA), for example. 
     In light of the above, it is desirable to efficiently handle various types of wireless services across multiple WATs for WTRUs that may operate in cellular and WLAN type networks. 
     SUMMARY 
     The present invention is a method and system for efficiently handling various types of wireless services across multiple wireless access technologies for WTRUs that may operate in different types of networks. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  is a WTRU logical block diagram embodying the principles of the present invention. 
         FIG. 2  is a block diagram of steps involved in performing a registration-based operation wherein a capability report is provided in accordance with present invention. 
         FIG. 2A  is a timeline illustration of the procedure illustrated in  FIG. 2 . 
         FIG. 3  is a block diagram of steps involved in performing a network-solicited operation wherein a capability report is provided in accordance with the present invention. 
         FIG. 3A  is a timeline illustration of the procedure illustrated in  FIG. 3 . 
     
    
    
     DETAILED DESCRIPTION 
     Hereafter, a WTRU includes, but is not limited to, a user equipment, mobile station, fixed or mobile subscriber unit, pager, PDA or any other type of device capable of operating in a wireless environment. When referred to hereafter, a base station includes but is not limited to a Node B, site controller, access point (AP) or any other type of interfacing device in a wireless environment. 
       FIG. 1  is a simplified logical block diagram of the layers provided in a WTRU  12 , it being understood that a similar layered structure is provided in the network. The objective is to convey the capabilities of the WTRU to the network so that the network can tailor the services provided to the WTRU in accordance with the WTRU&#39;s capabilities. As an example, devices such as a PDA, a laptop equipped with a wireless communication card and a cell phone may all be capable of communicating with a WLAN, but each device has different capabilities. A laptop typically has a larger memory and greater processing power than both a PDA and a cell phone. Different laptops may have different capabilities; one laptop being able to conduct video conferencing while another laptop being unable to support such services. 
     Referring to  FIG. 2 , a process for WTRU registration that includes the generation and transmittal of a capability report as shown, by combining notification of services supported by the WTRU with a registration process, the network is then able to tailor the services provided to the WTRU communicating with the network. Each time a multi-WATs WTRU, also referred to as a multi-technology WTRU (i.e., a WTRU capable of operating in more than one type of wireless network), successfully registers for service with an authentication, authorization and accounting (AAA) server  16  of a 3GPP network  14  through WLAN access network  22 , a WLAN application capability report is sent to the 3GPP network  14  and preferably to the home subscriber server (HSS)  18 . 
     With reference to  FIG. 1 , initially, the WTRU operating system  15 , at step ( 1 ), directs the registry application  13  to register the WTRU with the network, for example, the WTRU registers with the 3GPP network through a WLAN. At step ( 2 ), the registry application generates and sends a capability report based on either information from the operating system  15  or applications module  17  of the WTRU to include WLAN applications that interact with the 3GPP network, such as short message service (SMS) and voice over IP (VoIP), as well as any other currently supported applications. Drivers, such as a 3GPP driver  19   a  and WLAN device driver  19   b , as well as other drivers  19   c , support the services obtained from the network. The layers  13 ,  17 ,  15  and associated drivers are also provided in the network to support registry, receipt and storage of the capability report and, subsequent thereto, to provide the services identified in the capability report obtained from the WTRU. 
     The WLAN capability report is preferably a list of all supported air interface (PHY) capabilities currently supported by the WTRU  12  (e.g., 802.11a, 802.11b, 802.11x, 802.16, 802.20, UMTS-FDD, UMTS-TDD, TDSCDMA, GPRS, CDMA2000, or any other type of wireless network). 
     The WLAN capability report preferably also includes a list of all supported applications/services currently supported by the WTRU (e.g., web browsing, email, SMS, VoIP, or any other type of wireless service). The list of supported services can be associated with certain PHY capabilities (e.g., 802.11b card with MMS service capabilities). The list may also indicate third generation (3G) interworking such as 3GPP and/or 3GPP2 (e.g., GPRS/802.11 dual-mode cards supporting GPRS based SMS services) and/or other services developed in the future for existing or future networks. Optionally, the lists can identify the type and capacity of equipment of the WTRU, i.e. whether the WTRU is a cell phone, lap top computer, etc. with memory and processing speed capacities. The information regarding the device capability may be stored in the device drivers illustrated in  FIG. 1 . 
     The SMS message is preferably sent from a 3GPP network to a WTRU on an 802.11 network that is displayed to a user. The lists described above are preferably standardized. 
     The WLAN capability report is generated by a “thin” application program for generating the capability report. The “thin” application program can be on top of the operating system (e.g., like a Windows® program) and, being “thin,” does not require thousands of lines of code, but requires only several hundred lines of code. For example, the “thin” program is provided in the WLAN/3GPP application registry (AR)  13  in the WTRU  12  shown in  FIG. 1 , wherein the network registry queries the WTRU&#39;s operating system  15  or the applications module  17 , to determine the list of relevant applications. 
     As illustrated in  FIG. 2 , the capability report is preferably sent encrypted from the end user WTRU (currently on a WLAN) through WLAN access network  22  to the 3GPP AAA server  16 , which forwards the report to the 3GPP HSS/HLR  18 / 20 . The report is preferably sent encrypted via transmission control protocol/internet protocol (TCP/IP) from the WTRU  12  on the WLAN to the 3GPP AAA server  16 , at step ( 2 ), and the 3GPP AAA server  16  then preferably forwards the report to the HSS  18  as part of the WLAN registration process, at step ( 3 ). The HSS/HLR  18 / 20  sends an acknowledgement (ACK) to the AAA  16 , at step ( 4 ) which sends an ACK to WTRU  12  through WLAN network  22 , at step ( 5 ). 
     Thereafter, whenever the HSS/HLR  18 / 20  is queried for the location and capability of the user, a relevant check is made to determine if the user&#39;s WTRU supports that capability in the WLAN network. 
     Referring to the top portion of  FIG. 2 , WLAN access network  22  communicates with 3GPP AAA server  16  through a Wr/Wb interface. HSS  18  and HLR  20  communicate with 3GPP AAA server  16  through interfaces Wx and D′/Gr′, respectively. 
     As indicated in parentheses in  FIG. 2 , the system components and steps involved in performing a registration based operation are preferably: 
     1. WTRU  12  generates WLAN application capability report. 
     2. WTRU  12  transmits report via WLAN  22  to 3GPP AAA  16 . 
     3. 3GPP AAA  16  forwards report to HSS/HLR  18 / 20 . 
     4. HSS/HLR  18 / 20  acknowledges the report to AAA  16 . 
     5. 3GPP  14  acknowledges the report to the WTRU  12  via WLAN  22 . 
     Thereafter, any 3GPP node that attempts to deliver service to the WTRU in the WLAN network will check if the WTRU supports the service in WLAN mode. 
     The timing of these steps is shown and described in greater detail in  FIG. 2A , wherein a capability report is created at step S 1 , the WTRU  12  generating a WLAN application capability report and, at step S 2 , transmitting the report to the 3GPP AAA server  16  through WLAN  22  (shown in  FIG. 2 ). The 3GPP AAA  16 , at step S 3 , forwards the report to HSS  18  and HSS  18 , at step S 4 , stores the report and, at step S 5 , acknowledges the report, sending an acknowledgement (ACK) to AAA  16 . AAA Server  16 , at step S 6 , sends an ACK to WTRU  12  through WLAN access network  22 . Then, any 3GPP node that delivers service to the WTRU  12  in the WLAN network can first determine if the WTRU supports the service when operating in WLAN mode, by accessing HSS  18 . 
     Referring now to  FIG. 3 , the system components are the same as those shown in  FIG. 2 . The preferred steps involved in performing a network-solicited capability operation, as indicated in parentheses in  FIG. 3 , can be summarized as follows: 
     1. SMS message is sent from SC  24 . 
     2. GMSC  26  queries HSS  18  about WTRU  12  location. 
     3. HSS  18  returns PDG/WAG  28  address. 
     4. GMSC  26  forwards SMS to PDG/WAG  28 . 
     5. PDG/WAG  28  queries the WTRU  12  via WLAN  22  about SMS capabilities. 
     6. WTRU  12  lists all service capabilities and reports to PDG/WAG  28 . 
     If successful, PDG/WAG  28  delivers SMS to WTRU  12  through WLAN  22 . 
     Timing of these steps is shown in  FIG. 3A  wherein a capability report has not previously been provided. In this embodiment, a short message system (SMS) message is sent from service center (SC)  24  to a gateway Mobile Switching Center (MSC) or an interworking MSC for SMS (GMSC/IWSMC)  26 , at step S 1 , and responsive thereto, GMSC/IWSMC  26 , at step S 2 , queries HSS  18  about the WTRU location. The HSS  18 , at step ( 3 ), provides a packet data gateway or a wireless application gateway (PDG/WAG) address to the GMSC/IWSMC  26  and the GMSC/IWSMC  26 , at step S 4 , forwards the SMS message to the PDG/WAG  28 . The PDG/WAG  28 , at step S 5 , queries the WTRU  12  (through WLAN access network  22  shown in  FIG. 3 ) about its SMS capabilities and WTRU  12 , at step S 6 , and through WLAN access network  22 , lists all service capabilities and provides a report to the PDG/WAG  28 . Then, if successful, the PDG/WAG  28 , at step S 7 , delivers SMS to WTRU  12 . If not successful, the PDG/WAG  28  denies service, at step S 7 A. 
     It should be noted that although the present invention has been described in connection with an interworking 3GPP and WLAN, it is important to note that the present invention may be implemented in all types of wireless communication systems and further in any combination.

Technology Classification (CPC): 7