Title of Invention	SYSTEM AND METHODS FOR INTEGRATION OF THIRD GENERATION (3G) UNIVERSAL MOBILE TELECOMMUNICATIONS SYSTEM (UMTS) AND WIRELESS METROPOLITAN AREA NETWORKS (WMAN)
Abstract	The invention explains a system and method for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) comprising: IEEE 802.16 system having a MT, AP and AR; UMTS system having a UE, node B and the RNC ; a mobile user terminal (MUT) which has a dual mode capability and is adapted to associate with both the UMTS system as well as the IEEE 802.16 system; and UMTS-802.16 Integrator.

Title of Invention

SYSTEM AND METHODS FOR INTEGRATION OF THIRD GENERATION (3G) UNIVERSAL MOBILE TELECOMMUNICATIONS SYSTEM (UMTS) AND WIRELESS METROPOLITAN AREA NETWORKS (WMAN)

Abstract

The invention explains a system and method for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) comprising: IEEE 802.16 system having a MT, AP and AR; UMTS system having a UE, node B and the RNC ; a mobile user terminal (MUT) which has a dual mode capability and is adapted to associate with both the UMTS system as well as the IEEE 802.16 system; and UMTS-802.16 Integrator.

Full Text	FIELD OF TECHNOLOGY This invention relates to the filed of heterogeneous wireless networks such as Third Generation Universal Mobile Telecommunications System and Wireless Metropolitan Area Networks. More particularly, this invention relates to a system and methods for integration of third generation Universal Mobile Telecommunications Systems and Wireless Metropolitan Area Networks. DESCRIPTION OF RELATED ART A typical IEEE 802.16d/e [1],[2] wireless metropolitan area network (WMAN) consists of mobile stations (MS) or mobile terminals (MT), base station (BS) or access points (AP) and access point controller (APC) or access router (AR), as shown in Fig. 1. A session is defined as a shared state between an MS and an AP. Each session is composed of multiple connections, where a connection is defined as the active portion of a session that requires resources at the air interface. The IEEE 802.16d/e standard specifies a connection oriented medium access control (MAC) in which each connection is assigned a connection identifier (CID) to enable the AP to allocate resources to the connection. At the beginning of every session, it is necessary for the AP and the MS to negotiate the protocols and protocol configurations for the session so as to enable efficient resource allocation and provide the necessary quality of service (QoS). The IEEE 802.16 system has a connection oriented MAC and each flow is identified by a unique connection identifier (CID). The radio resource management is based on the CID, which specifies the required quality of service (QoS) for each flow. The standards to support mobility in such networks are provided in [2]. Efficient mobility management mechanisms for such networks were discussed in [3]. The QoS provisioning is enabled by classifying traffic into 4 categories namely, unsolicited grant service (UGS) for ATM CBR like services, real time polling service (RT PS) for VoIP, streaming video services, non-real time polling service (nRT PS) for FTP traffic and best effort. The MT registers with the AP using the REG-REQ and REG-RSP commands. The bandwidth request MAC header enables the MT to request the AP for bandwidth according to the application. The DSA-REQ command is sent by the MT to the AP specifying the application and traffic category for QoS negotiation. The UMTS system [4] consists of a mobile terminal (MT) also referred to as the user equipment (UE), a base station (BS), also called as node-B and a radio network controller (RNC), which, in turn, is connected to the GSM core network. The basic architecture for a UMTS system is shown in Fig. 2. The interfaces between the network components are also defined and are shown in Fig. 2. The network shown in Fig. 2 is also called as the UMTS terrestrial radio access network (UTRAN). The RNC controlling a base station is called as the controlling RNC for the corresponding node B. From the UE point of view, there is a serving RNC which terminates the mobile link layer communications. There could be one or more drift RNC's which terminate the mobile physical layer communications. The splitting and combining of uplink and downlink traffic are done at the node B, the serving RNC and the drift RNC's. The interfaces at the UMTS networks are as follows [5]. The lu interface (between the RNS and the core network) is also considered as the reference point. The RNC's are connected by the lur interface that enables the UMTS network to operate as an autonomous network from the core GSM network The RNC and the base stations are connected by the lub interface and the air interface between the UE and the node B is called as the Uu interface. The user plane of the lu interface allocates resources to various flows over the physical link. Resources are allocated upon activity and re-allocated during idle periods. When an RNC wants to disassociate from an SGSN, it issues an lu_Release command, upon receiving which, the lu can be released. The packet switched traffic is routed from the RNS to the SGSN using the lu-PS interface. This interface is also responsible for the mobility management. The RNC is responsible for frequency allocation and the allocated frequency or channel set to each node B is conveyed to the respective node B's through the lub interface. The mobility management in the UMTS system is as follows. As soon as the UE powers up it is in the PMM-DETATCHED state in which there is no communication between the UE and the node B. When the GPRS attach procedure is completed, the MS moves to the PMM-CONNECTED state. When PS signaling is released, the state changes to PMM-IDLE, which is a state indicating that the PS signaling to the 3G-SGSN is broken. If the UE is out of coverage or if the URA update timer expires or if the radio resource controller connection cannot be established, then the UE is detached from then SGSN and the state changes to PMM-DETATCHED. The state transitions at the UE are shown in Fig. 3. The state transition diagram at the SGSN is as shown in Fig. 4. The signals leading to the state transitions are as at the UE except that the state remains at PMM-CONNECTED if the serving RNC changes. The network operation mode could be of two types: Type I when the Gs interface is present and Type II when Gs interface is not present. When the Gs interface is present, the UE can initiate combined update procedures. However, the mode should be the same for the entire routing area. The radio resource controller (RRC) state machine for UTRAN is shown in Fig. 5. When there is no radio resource allocated to a UE, the RRC is in the RRC Idle Mode, in which, the MS can receive paging messages about the CN. In the RRC Connected Mode, the main states are Cell Connected and URA connected. When the UE is tracked at cell level the RRC state is in the Cell Connected state and if the UE is tracked at the routing area level, then the state is URA connected. No dedicated radio resources are used at the URA Connected state. The UE in the RRC URA Connected state is paged by the RNC before a downlink transfer. In response, the UE sends a Cell Update message, upon receiving which, the state changes to the RRC Cell Connected state, and then, the RNC transfers the data and the signaling messages to the UE. To provide quality of service (QoS) to users, the traffic is classified into 4 categories, namely, interactive, voice, stream and best effort. In the current technology, there is no efficient architecture and interfaces defined for the integration of WMAN and 3G wireless networks. SUMMARY OF THE INVENTION The present invention presents an architecture for integrating 3G UMTS and IEEE 802.16 networks, it is possible to have both a tightly and a loosely coupled system. Tightly coupled architecture involves lesser handoff latency and is considered more useful for delay sensitive applications which are predominantly present in IEEE 802.16 networks. In the tightly coupled system, the WMAN network is made to appear as a foreign 30 network to an existing 3G network. Similarly the 3G network is made to appear as a foreign WMAN network to an existing WMAN network. The tightly coupled architecture requires an integrating component that has the functionalities of both the 3G as well as the WMAN networks. Accordingly this invention explains a system for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) comprising : IEEE 802.16 system having a MT, AP and AR; UMTS system having a UE, node B and the RNC ; a mobile user terminal (MUT) which has a dual mode capability and is adapted to associate with both the UMTS system as well as the IEEE 802.16 system; and UMTS-802.16 Integrator. Accordingly this invention explains a system for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) comprising an MUT which does not have a dual mode capability and has only 3G UMTS or IEEE 802.16 capabilities wherein the MUT registers with the network depending on its capabilities. Accordingly this invention also explains a system for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) comprising the integrator wherein the said integrator has the functionalities of the SGSN, the RNC, and the IEEE 802.16 AR where when an MUT powers up in the UMTS domain, it registers with the serving RNC. Accordingly this invention also explains a system for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) when the IEEE 802.16 network is used as a back haul to the UMTS network comprising the integrator wherein the said integrator has an air interface connection to the IEEE 802.16 AP resulting in a two hop wireless network to transfer traffic into the back bone network where the IEEE 802.16 AP treats the integrator as an IEEE 802.16 MT. Accordingly this invention also explains a method for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN). BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS Figure 1: shows a typical IEEE 802.16d/e wireless metropolitan area network (WMAN) Figure 2: shows a typical UMTS network Figure 3: shows state transition diagram at UE for mobility management in UMTS Figure 4: shows state transition diagram at SGSN for mobility management in UMTS Figure 5: shows state transition diagram for RRC in UMTS Figure 6: shows architecture for UMTS-802.16 Integration - Type 1 Figure 7: shows Handover signaling: IEEE 802.16 to UMTS network: Type 1 Figure 8: shows Handover signaling: UMTS to IEEE 802.16 network: Type 1 Figure 9: shows MUT Protocol Stack Figure 10: shows Type I Architecture: Components and Interfaces Figure 11: shows alternate Type 1 Architecture: Components and Interfaces Figure 12: shows Type 2 Architecture: Components and Interfaces DETAILED DESCRIPTION OF THE INVENTION This invention presents a tightly coupled architecture for the integration of UMTS and IEEE 802.16 networks. There are two cases considered here: 1. When the UMTS and the 802.16 networks are at the same level, i.e., we have a one hop wireless network 2. When the coverage is only by UMTS but the traffic to the back bone network is back-hauled to an IEEE 802.16 network, thus resulting in a two hop wireless network It first provides the architecture for case 1 mentioned above, and then extend the architecture to include case 2. For the Type 1 network mentioned above, we present the architecture shown in Fig. 6. In the figure, we have the MT, AP and AR that belong to the IEEE 802.16 system, and the UE, node B and the RNC that belongs to the UMTS system. We define mobile user terminal (MUT) which has a dual mode capability and can associate with both the UMTS system as well as the IEEE 802.16 system. The UMTS-802.16 Integrator shown in Fig. 6 has the following functions. The integrator is expected to have the SGSN as well as the 802.16 APC/AR functionalities built in it because is to be connected to the backbone network as well as the GGSN of a 3G core network. The 3G GGSN treats the integrator as another SGSN, while the IEEE 802.16 AR treats the integrator as another AR. When an MUT registers with a 3G-UMTS network and decides to send traffic over the 3G network, then the data is transmitted to the back bone network through the SGSN. The integrator is connected to the AR of the 802.16 network as well as the back bone network. When an MUT moves from an 802.16 WMAN network to a 3G UMTS network, the integrator corresponds to the appropriate GGSN through the back bone network and also mentions the IP address of the target RNC. The GGSN treats this as an SGSN-SGSN handover and the existing handover mechanisms for inter SGSN defined in the 3GPP standards can be used. However, these result in additional signals to the RNC and the node B's since the registration process into the 3G handover is now initiated by the SGSN, and not the UE. The UE capabilities in UMTS [4] consist of the UMTS UE radio capability information, including power control, code resource, UE mode, ciphering and PDCP capabilities. When a dual mode MUT undergoes a hand off from an IEEE 802.16 network and indicates a handoff from an IEEE 802.16 network to a UMTS network, it shall inform the AP of its UMTS capabilities along with target UMTS RNC, which in turn, transfers this information to the IEEE 802.16 AR along with the context of the active flows. The integrator then performs a registration of the MUT at the SGSN. The MUT capabilities are then communicated to the appropriate RNC. Once the MUT hands off to the UMTS network, it shall then perform the UMTS power up procedures. The choice of the SGSN and RNC are however made after taking into account, information on the context of the flows incident on the mobile and the QoS requirements. The signaling for an IEEE 802.16 to UMTS handover is shown in Fig. 7. In the figure, the MOB_HOJND message is the hand off indication message that is given by the IEEE 802.16 AR to the integrator. The integrator obtains the mobile registration information and communicates to the SGSN, the UMTS RNC and the Node B. The mobile then registers in the UMTS network following the UMTS power up procedures This also requires the SBC-REQ and the SBC-RSP messages in the IEEE 802.16 network to be suitably modified to incorporate dual mode capability of the MT and the appropriate 3G MS ID and the IEEE 802.16 MAC address. The SBC-REQ message in the IEEE 802.16 standards [1] has an 8 bit field for the management message type and a variable length field which is TLV encoded information. In the TLV encoded information the MUT shall communicate the dual mode capability along other capabilities. The MOB_HOJND message for the IEEE 802.16e standard [2] has an 8 bit field for management message type and a 6 bit reserved field. It also contains a 2 bit field for the hand off type. The handoff type 11 is currently reserved. The reserved handoff type is now used for indicating vertical handoff. Following the handoff type field is a 48 bit field for the target AP MAC address. This field is used only for the horizontal handoff, i.e., from one IEEE 802.16 network to another. When the vertical handoff type message is received by an AP, the AP sends a UBC_REQ message to the MUT. This message is the UMTS basic capabilities request message. The MUT responds with the UBC_RSP message which contains the UMTS capabilities of the MUT. The AP communicates this information to the AR, which, in turn communicates this to the SGSN, from which the RNC and node B obtain the capabilities and the context information. The MUT then powers up performs the UMTS network re-entry process at the UMTS node B. The modified MOB_HOJND message is shown in Table 1. The UBC_REQ and UBC_RSP message formats are shown in Tables 2 and 3, respectively. The TLV encoded information for the UBC_REQ message shall include the RNC and the node B in which the MUT can be expected to register after handoff to the UMTS network. The UBC^RSP message format is shown in Table 3. The TLV encoded information shall include the UMTS capabilities of the MUT as well as the UMTS MS-ID. Ta T Table 3: UBC_RSP message for Type 1 architecture Similarly, the registration process in the 3G network and the capability negotiation in the 3G network require additional fields to incorporate the dual mode capability of the terminals. When handover takes place from the 3G UMTS to the IEEE 802.16 network, then the integrator is treated as a new AR and L3 handover mechanisms are required for completing the handover process. The mobile traffic context and the MAC address is informed to the corresponding AP and radio resource management and the registration processes are performed. However, the handover process also requires changes to the UMTS standards because the registration at the IEEE 802.16 network is now performed by the AR and not the MT as specified in the standards [1], [2]. Instead, we present a set of hand over signals as shown in Fig. 8. In the figure, the RA_Update message is the message sent by the UE to the node B indicating a change in the routing area. The integrator assigns a care-of-address (CoA) to the UE and also maps the CoA to the IEEE 802.16 IP address. When the handover is indicated by the routing area update with the new SGSN/RNC id corresponding to that of the integrator, the MUT capabilities are transferred to the IEEE 802.16 AR, which, in turn, initiates the registration and network entry process. It is also essential that the mobile context and QoS categories be mapped appropriately. The integrator therefore maps all the 3G categories of the incident flows to the appropriate IEEE 802.16 QoS classes. Hence, the integrator and the associated IEEE 802.16 network is made to appear as a foreign 3G UMTS network. The MUT stack is shown in Fig. 9. It contains both the 802.16 device driver as well as the UMTS device driver. The UMTS device driver implements the UMTS user and control functions [4]. When an MUT powers up in the UMTS coverage area, it runs the UMTS- GPRS power up procedure through the serving RNC (SRNC). The GPRS attach and the authentication procedures are followed and the best effort bearer set up is also performed. When powered up in the 802.16 network, the MUT exchanges the REG-REQ, REG-RSP messages to register and the basic capability negotiation is performed with the SBC-REQ and SBC-RSP messages. Depending on the QoS required for the service, radio resource availability and the network conditions an MUT could choose to handover from one network to the other. In the following, we present some of the basic messages in the integrated system and the interfaces between the various components of the integrated system. The interfaces for the Type 1 architecture mentioned earlier are provided in Fig. 10. The functions of the interfaces are as follows. The integrator acts as a foreign 3G network and the authentication and accounting is performed through the 3G AAA server. As mentioned earlier, the integrator consists of GGSN functionalities of the GPRS-UMTS system. When an MUT powers on in the 3G network it communicates with the node B over the Uu interface. The other interfaces are explained as follows: > Gn/Gp: This is the interface between an SGSN and a GGSN. The Gn interface is used if both the SGSN as well as the GGSN belong to the same PLMN and the Gp interface is used, otherwise. This interface allows an SGSN to communicate user data while changing SGSN. > Wz: This reference point occurs between the 802.16 AAA server and the AR. This reference point allows the 802.16 AAA server to authenticate 3G users in the WMAN cell. Functions of this reference point are similar to the Wy reference point mentioned below. > Wr': This interface connects the 802.16 network to the 3G network through the integrator. The reference point exists between the integrator and the AR. The functionalities of this reference point include ^ Data for authentication signaling between MT and the 3G ^ Signaling for WMAN AR and the 3G authentication ^ Purging data for 802.16 access termination > Wy: This interface exists between the 3G AAA server and the 3G home subschber system i.e., the home GGSN. The prime purpose is for the 802.16 AAA infra structure and the HSS. This shall be RADIUS based. Some of the functionalities of this reference point include / Registration of theSGPP server for authorized 802.16 access ^ Purge procedure between 3GPP AAA and HSS / Retrieval of online and offline charging function addresses from the HSS An alternate architecture is one in which the MUT does not have a dual mode capability and has only 3G UMTS or IEEE 802.16 capabilities. In this case the MUT registers with the network depending on its capabilities. If the MUT has only 3G capabilities and wants to move to the IEEE 802.16 network, the flows handled by the MUT needs to be mapped to appropriate service flow ID (SFID) and the connection ID (CID). It is also essential for the MUT to obtain a care of address (CoA). The integrator provides the CoA for the MUT and acts as a foreign network for the home 3G network. The signaling shown in Fig. 8 can be applied to this scenario for the handoff from UMTS network to IEEE 802.16 network. However, the basic capabilities need not be registered with the IEEE 802.16 AR. The CoA can be appropriately mapped to a virtual mobile in the IEEE 802.16 network. All packets from the correspondent node are then transferred to the appropriate IEEE 802.16 AR, with IP tunneling. Similariy, when the MUT has IEEE 802.16 capabilities and wants to hand over to the 3G UMTS network, then the service class of the flows need to be appropriately mapped to the 3G traffic category and the CoA and the SRNC is assigned to the MUT. The integrator now acts as a foreign 3G network and the message exchanges are suitably performed (i.e., the 802.16 REG and MUT capability messages are suitably changed to the 3G messages). A third type of architecture for the Type 1 network is as shown in Fig. 11. In this type of architecture, the integrator has to have the functionalities of the SGSN, the RNC, and the IEEE 802.16 AR built in it. Here, when an MUT powers up in the UMTS domain, It registers with the serving RNC. When a handover takes place to another RNC, the UMTS handover procedures are followed. When the MUT moves from an 802.16 network to a UMTS network, the integrator is treated as a new RNC or a new SGSN depending on the target SGSN. Then, one of the inter-RNC or inter-SGSN handover procedures can be applied accordingly. The handover from UMTS to IEEE 802.16 network is as explained in the previous architecture shown in Fig. 10. It is also possible to upgrade the integrator to include functions of the node B also. This results in added complexity and overheads, but may result in reduced vertical handoff latency time. We also present an architecture for the integration of a UMTS and an IEEE 802.16 network, when the IEEE 802.16 network is used as a back haul to the UMTS network. A schematic of this scenario is shown in Fig. 12. In the figure, it is shown that the integrator has an air interface connection to the IEEE 802.16 AP. Thus there exists a two hop wireless network to transfer traffic into the back bone network. In this scenario the IEEE 802.16 AP treats the integrator as an IEEE 802.16 MT. The Registration request and response messages now contain the MAC address of the integrator. However, it is noted that the packets that are transmitted by the SGSN are IP packets whereas the AP can only decipher MAC packets. Hence, the integrator needs to include the IEEE 802.16 MAC headers before transmitting the packets to the AP. The MAC address of the integrator shall then be used by the AR to de-capsulate the IP packets and then transmit it over the back bone network. Similarly, when the AR receives IP packets from the back bone network corresponding to the IP address of the UMTS MUT, the AR forwards the packet to the appropriate AP. The AP then encapsulates the IP packet with the appropriate MAC packets and transmits to the integrator. This architecture therefore requires that when the SGSN registers with an AP it also mentions to the AP about the IP addresses of the MUTs associated with it. Hence, it requires the following changes to the registration process at the IEEE 802.16 AP. The REG-REQ message in the IEEE 802.16 standards [1] has an 8 bit field for the management message type and a variable length field which is TLV encoded information. In the TLV encoded information the integrator shall add the IP addresses of the MUT or the SGSN along with other capabilities. The architecture shown in Fig. 12 is valid or MUT with dual mode capabilities or with UMTS capabilities. For an MUT with IEEE 802.16 capabilities alone, the MUT cannot handover to the UMTS network as there is no link to the back bone network. To handover to a UMTS network that is back hauled to another IEEE 802.16 AP-_ -Mechanisms in [31 can be adopted to perform an inter-IEEE 802.16 AP handover. If the UMTS network belongs to a different AR, then L3 handover mechanisms are applied to perform the handover to the UMTS network. The above-presented description is of the best mode contemplated for carrying out the present invention. The manner and process of making and using it is in such a full, clear, concise and exact terms as to enable to any person skilled in the art to which it pertains to make and use this invention. New embodiments in particular, which also lie within the scope of the invention can be created, in which different details of the different examples can in a purposeful way be combined with one another. This invention is however, susceptible to modifications and alternate constructions from that disclosed above which are fully equivalent. Consequently, it is not the intention to limit this invention to the particular embodiment disclosed. On the contrary, the intention is to cover all modifications and alternate constructions coming within the spirit and scope of the invention as generally expressed by the following claims which particularly point out and distinctly claim the subject matter of the invention. Glossary of Terms and their Definitions MT: IEEE 802.16 mobile terminal, it is the wireless terminal used by the IEEE 802.16 user to transmit data to the wireless network AP: IEEE 802.16 access point, it is the node the MT communicates with, to access the wireless medium AR/APC: IEEE 802.16 access router/access point controller, it connects the IEEE 802.16 network to the back bone network UMTS: Universal mobile telecommunications system GPRS: Generalized packet radio service UE: UMTS user equipment, it is the wireless terminal used by the UMTS user to transmit data to the wireless network Node B: The UMTS base station, it is the node the UE communicates with, to access the wireless network RNC: UMTS radio network controller, this is the node that interfaces the UMTS to the GPRS network UMTS: Universal mobile telecommunications system GGSN: Gateway GPRS support node, this is the node that connects the GPRS network to the back bone network SGSN: Serving GPRS support node, this node controls all the GPRS base station controllers and the UMTS RNC Uu: The air interface between the UMTS node B and the UMTS UE lu: The interface between the UMTS RNC and the SGSN lub: The interface between the UMTS RNC and node B lur: The interface between one UMTS RNC and another RNS: The UMTS radio network system consisting of the RNC and node B PMM: Packet mobility management in UMTS MUT: Mobile user terminal in the integrated UMTS-IEEE802.16 network. This could have the capabilities of a UMTS UE or an IEEE 802.16 MT or both MOB__HOJND: Mobile handoff indication message in IEEE 802.16e. This indicates handoff to the serving AP SBC_REQ: The MT basic capabilities request message in IEEE 802.16d/e. This message is used by the AP to request the MT for its capabilities SBC_RSP: The MT basic capabilities response message in IEEE 802.16d/e. This message is used by the MT to inform the AP of its capabilities TLV: Type, length, value, a format for encoding messages UBC_REQ: UMTS basic capabilities request. This message is used by the AP to request the dual mode MUT in the IEEE 802.16 network to specify the UMTS capabilities of the MUT UBC_RSP: UMTS basic capabilities response. This message is used by the dual mode MUT in the IEEE 802.16 network to specify the UMTS capabilities of the MUT to the AP MOB^COA: MUT Care-of address, this address is allocated by the UMTS-IEEE 802.16 integrator to the MUT for mobility management between the UMTS and the IEEE 802.16 network MAC: Medium access control UTRAN: UMTS Radio Access Network REG_REQ: IEEE 802.16 registration request message, this is sent by the MT to the AP to request for registration into the IEEE 802,16 networks REG_RSP: IEEE 802.16 registration response message, this is sent by the AP to the MT to for registration into the IEEE 802,16 networks Gn/Gp: Interface between the SGSN and GGSN AAA: Authentication authorization and accounting server, this is used in integrated networks for security and billing purposes when the MUT is roaming between networks Wy: Interface between UMTS AAA server and the 3G home subscriber. Wz: Interface between the IEEE 802.16 AAA server and the SGSN. Wr': Interface between IEEE 802.16 AR and the integrator SFID: Service flow ID for each flow in an IEEE 802.16 network CID: Connection ID for each flow in an IEEE 802.16 network. A service flow can be comprised of many connections References [1] Part 16: Air interface for fixed broadband wireless access systems: Draft IEEE standard for wireless local and metropolitan area networks, IEEE P802.16- Revd/D3-2004. [2] Part 16: Air interface standard for fixed and mobile broadband wireless systems: Amendment for physical and medium access control layers for combined fixed and mobile operation in licensed bands, IEEE P802.16e/D2. April 2004. [3] Mukesh Taneja, Anand Santhanakrishnan, and Ganapathy Viswanath, "Methods and System for recommended and active set selection for handoff in wireless multimedia networks," Patent filed, Application Number 190/CHE/2004. [4] 3""^ generation partnership project (3GPP); Technical specification group services and system aspects; Generalized packet radio service (GPRS); Service description; 3GPP TS 23.060 V 4.5.0, June 2002. [5] 3^^ generation partnership project; Technical specification group services and system aspects; Network architecture Release 4, 3GPP TS 23.002 V 4.4.0, January 2002. We Claim 1. A System for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) comprising : IEEE 802.16 system having an MT, AP and AR; UMTS system having a UE, node B and the RNC ; a mobile user terminal (MUT) which has a dual mode capability and is adapted to associate with both the UMTS system as well as the IEEE 802.16 system; and UMTS-802.16 Integrator. « 2. A system as claimed in claim 1 wherein the integrator has the SGSN and the 802.16 APC/AR functionalities for connecting to the backbone network and the GGSN of a 3G core network. 3. A system as claimed in claim 1 wherein the 3G GGSN treats the integrator as another SGSN and the IEEE 802.16 AR treats the integrator as another AR. 4. A system as claimed in claim 1 wherein when an MUT registers with a 3G-UMTS network and sends traffic over the 3G network, then the data is transmitted to the back bone network through the SGSN. 5. A system as claimed in claim 1 wherein the integrator is connected to the AR of the 802.16 network and the back bone network and when an MUT moves from an 802.16 WMAN network to a 3G UMTS network, the integrator corresponds to the appropriate GGSN through the back bone network and mentions the IP address of the target RNC. 6. A system as claimed in claim 1 wherein the GGSN treats the correspondence as an SGSN-SGSN handover and uses an existing handover mechanism. 7. A system as claimed in claim 1 wherein the UE capabilities in UMTS comprise UMTS UE radio capability information, power control, code resource, UE mode, ciphering and PDCP capabilities. 8. A system as claimed in claim 1 wherein when a dual mode MUT undergoes a hand off from an IEEE 802.16 network and indicates a handoff from an IEEE 802.16 network to a UMTS network, It inrorm the AP of its UMTS capabilities along with target UMTS RNC, which, transfers the information to the IEEE 802.16 AR along with the context of the active flows. 9. A system as claimed in claim 1 wherein the integrator performs a registration of the MUT at the SGSN and the MUT capabilities are communicated to the appropriate RNC. 10. A system as claimed in claim 1 wherein once the MUT hands off to the UMTS netsNork, it perform the UMTS power up procedures and the choice of the SGSN and RNC are made after taking into account, information on the context of the flows incident on the mobile and the QoS requirements. 11. A system as claimed in claim 1 wherein the signaling for an IEEE 802.16 to UMTS handover comprise MOB_HOJND message which is the hand off indication message given by the IEEE 802.16 AR to the integrator where the integrator obtains the mobile registration information and communicates to the SGSN, the UMTS RNC and the Node B. 12. A system as claimed in claim 1 wherein the mobile registers in the U^ATS network following the UMTS power up procedures where the SBC-REQ and the SBC-RSP messages in the IEEE 802.16 network are modified to incorporate dual mode capability of the MT and the appropriate 3G MS ID and the IEEE 802.16 MAC address. 13. A system as claimed in claim 1 wherein the SBC-REQ message in the IEEE 802.16 standards has an 8 bit field for the management message type and a variable length field which is TLV encoded information where the MUL communicate the dual mode capability along with other capabilities. 14. A system as claimed in claim 1 wherein the MOB_HOJND message for the IEEE ^02.16e standard has an 8 bit field for management message type, a 6 bit reserved field and a 2 bit field for the hand off type. 15. A system as claimed in claim 1 wherein the reserved handoff type is used for indicating vertical handoff where the handoff type field is a 48 bit field for the target AP MAC address and the field is used for the horizontal handoff from one IEEE 802.16 network to another. 16. A system as claimed in claim 1 wherein when the vertical handoff type message is received by an AP, the AP sends a UBC_REQ message to the MUT where the said message is the UMTS basic capabilities request message. 17. A system as claimed in claim 1 wherein the MUT responds with the UBC_RSP message which contains the UMTS capabilities of the MUT and the AP communicates the said information to the AR, which communicates it to the SGSN, from which the RNC and node B obtain the capabilities and the context information. 18. A system as claimed in claim 1 wherein the MUT performs the UMTS network re-entry process at the UMTS node B and the TLV encoded information for the UBC_REQ message include the RNC and the node B in which the MUT register after handoff to the UMTS network where the TLV encoded information include the UMTS capabilities of the MUT and the UMTS MS-ID. 19. A system as claimed in claim 1 wherein the registration process in the 3G network and the capability negotiation in the 30 network use an additional fields to incorporate the dual mode capability of the terminals where when handover takes place from the 3G UMTS to the IEEE 802.16 network, the integrator is treated as a new AR and an L3 handover mechanisms is used for completing the handover process. 20. A system as claimed in claim 1 wherein the mobile traffic context and the MAC address is informed to the corresponding AP and radio resource management and the registration processes are performed. 21. A system as claimed in claim 1 wherein the RA_Update message is the message sent by the UE to the node B indicating a change in the routing area where the integrator assigns a care-of-address (CoA) to the UE and also maps the CoA to the IEEE 802.16 IP address and when the handover is indicated by the routing area update with the new SGSN/RNC id corresponding to that of the integrator, the MUT capabilities are transferred to the IEEE 802.16 AR, which, initiates the registration and network entry process. 22. A system as claimed in claim 1 wherein the mobile context and QoS categories are mapped where the integrator maps all the 3G categories of the incident flows to the appropriate IEEE 802.16 QoS classes making the integrator and the associated IEEE 802.16 network appear as a foreign 3G UMTS network. 23. A system as claimed in claim 1 wherein the UMTS device driver implements the UMTS user and control functions and when an MUT powers up in the UMTS coverage area, the UMTS- GPRS power up procedure runs through the serving RNC (SRNC) and the GPRS attach and the authentication procedures are followed and the best effort bearer set up is a performed. 24. A system as claimed in claim 1 wherein when powered up in the 802.16 network, the MUT exchanges the REG-REQ, REG-RSP messages to register and the basic capability negotiation is performed with the SBC-REQ and SBC-RSP messages and depending on the QoS required for the service, radio resource availability and the network conditions an MUT chooses to handover from one network to the other. 25. A system as claimed in claim 1 wherein the integrator acts as a 3G network and the authentication and accounting is performed through the 3G AAA server where , the integrator consists of GGSN functionalities of the GPRS-UMTS system. 26. A system as claimed in claim 1 wherein when an MUT powers on in the 3G network it communicates with the node B over the Uu interface. 27. A system as claimed in claim 1 wherein an interface Wz occurs between the 802.16 AAA server and the AR which allows the 802.16 AAA server to authenticate 3G users in the WMAN ceil. 28. A system as claimed in claim 1 wherein an interface Wr occurs between the integrator and the AR which allows data for authentication signaling between MT and the 3G, signaling for WMAN AR and the 3G authentication and Purging data for 802.16 access termination. 29. A system as claimed in claim 1 wherein an interface Wy occurs between the 3G AAA server and the 3G home subscriber system which allows registration of the 3GPP server for authorized 802.16 access, purging procedure between 3GPP AAA and HSS and retrieval of online and offline charging function addresses from the HSS . 30. A System for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) comprising an MUT which does not have a dual mode capability and has only 3G UMTS or IEEE 802.16 capabilities wherein the MUT registers with the network depending on its capabilities. 31. A system as claimed in claim 30 wherein if the MUT has only 3G capabilities and wants to move to the IEEE 802.16 network, the flows handled by the MUT are mapped to appropriate service flow ID (SFID) and the connection ID (CID) and the MUT obtains a care of address. 32. A system as claimed in claim 30 wherein the integrator provides the CoA for the MUT and acts as a foreign network for the home 3G network where the CoA appropriately mapped to a virtual mobile in the IEEE 802.16 network. 33. A system as claimed in claim 30 wherein all packets from the correspondent node are transferred to the appropriate IEEE 802.16 AR, with IP tunneling and when the MUT has IEEE 802.16 capabilities and wants to hand over to the 3G UMTS network, the service class of the flows are mapped to the 3G ASC and the CoA and the SRNC is assigned to the MUT. 34. A system as claimed in claim 30 wherein the integrator acts as a foreign 3G network and the 802.16 REG and MUT capability messages are suitably changed to the 3G messages. 35. A System for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) comprising the integrator wherein the said integrator has the functionalities of the SGSN, the RNC, and the IEEE 802.16 AR where when an MUT powers up in the UMTS domain, it registers with the serving RNC. 36. A system as claimed in claim 35 wherein when a handover takes place to another RNC, the UMTS handover procedures are followed and when the MUT moves from an 802.16 network to a UMTS network, the integrator is treated as a new RNC or a new SGSN depending on the target SGSN and one of the inter-RNC or inter-SGSN handover procedures is applied accordingly. 37. A System for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) when the IEEE 802.16 network is used as a back haul to the UMTS network comprising the integrator wherein the said integrator has an air interface connection to the IEEE 802.16 AP resulting in a two hop wireless network to transfer traffic into the back bone network where the IEEE 802.16 AP treats the integrator as an IEEE 802.16 MT. 38. A system as claimed in claim 37 wherein the Registration request and response message contain the MAC address of the integrator where the packets that are transmitted by the SGSN are IP packets and the AP decipher only MAC packets. 39. A system as claimed in claim 37 wherein the integrator include the IEEE 802.16 MAC headers before transmitting the packets to the AP where the MAC address of the integrator is used by the AR to de-capsulate the IP packets and transmit it over the back bone network. 40. A system as claimed in claim 37 wherein , when the AR receives IP packets from the back bone network corresponding to the IP address of the UMTS MUT, the AR forwards the packet to the appropriate AP and the AP encapsulates the IP packet with the appropriate MAC address and transmits to the integrator. 41. A system as claimed in claim 37 wherein when the SGSN registers with an AP it mentions to the AP about the IP addresses of the MUTs associated with it. 42. A system as claimed in claim 37 wherein the REG-REQ message in the IEEE 802.16 standards has an 8 bit field for the management message type and a variable length field which is TLV encoded information where in the TLV encoded information the integrator adds the IP addresses of the MUT or the SGSN along with capabilities. 43. A system as claimed in claim 37 wherein if the UMTS network belongs to a different AR, then L3 handover mechanisms are applied to perform the handover to the UMTS network. 44. A method for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) utilizing the said system as claimed in claim 1 to 43. 45. A system for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) substantially as herein described particularly with reference to the drawings. 46. A method for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) substantially as herein described particularly with reference to the drawings. Dated this 25*^ day of May 2005

Full Text

FIELD OF TECHNOLOGY
This invention relates to the filed of heterogeneous wireless networks such as Third Generation Universal Mobile Telecommunications System and Wireless Metropolitan Area Networks. More particularly, this invention relates to a system and methods for integration of third generation Universal Mobile Telecommunications Systems and Wireless Metropolitan Area Networks.
DESCRIPTION OF RELATED ART
A typical IEEE 802.16d/e [1],[2] wireless metropolitan area network (WMAN) consists of mobile stations (MS) or mobile terminals (MT), base station (BS) or access points (AP) and access point controller (APC) or access router (AR), as shown in Fig. 1. A session is defined as a shared state between an MS and an AP. Each session is composed of multiple connections, where a connection is defined as the active portion of a session that requires resources at the air interface. The IEEE 802.16d/e standard specifies a connection oriented medium access control (MAC) in which each connection is assigned a connection identifier (CID) to enable the AP to allocate resources to the connection. At the beginning of every session, it is necessary for the AP and the MS to negotiate the protocols and protocol configurations for the session so as to enable efficient resource allocation and provide the necessary quality of service (QoS).
The IEEE 802.16 system has a connection oriented MAC and each flow is identified by a unique connection identifier (CID). The radio resource management is based on the CID, which specifies the required quality of service (QoS) for each flow. The standards to support mobility in such networks are provided in [2]. Efficient mobility management mechanisms for such networks were discussed in [3]. The QoS provisioning is enabled by classifying traffic into 4 categories namely, unsolicited grant service (UGS) for ATM CBR like services, real time polling service (RT PS) for VoIP, streaming video services, non-real time polling service (nRT PS) for FTP traffic and best effort. The MT registers with the AP using the REG-REQ and REG-RSP commands. The bandwidth request MAC header enables the MT to request the AP for bandwidth according to the application. The DSA-REQ command is sent by the MT to the AP specifying the application and traffic category for QoS negotiation.
The UMTS system [4] consists of a mobile terminal (MT) also referred to as the user equipment (UE), a base station (BS), also called as node-B and a radio network controller (RNC), which, in turn, is connected to the GSM core network. The basic architecture for a UMTS system is shown in Fig. 2. The interfaces between the network components are also defined and are shown in Fig. 2. The network shown in Fig. 2 is also called as the UMTS terrestrial radio access network (UTRAN). The RNC controlling a base station is called as

the controlling RNC for the corresponding node B. From the UE point of view, there is a serving RNC which terminates the mobile link layer communications. There could be one or more drift RNC's which terminate the mobile physical layer communications. The splitting and combining of uplink and downlink traffic are done at the node B, the serving RNC and the drift RNC's.
The interfaces at the UMTS networks are as follows [5]. The lu interface (between the RNS and the core network) is also considered as the reference point. The RNC's are connected by the lur interface that enables the UMTS network to operate as an autonomous network from the core GSM network The RNC and the base stations are connected by the lub interface and the air interface between the UE and the node B is called as the Uu interface. The user plane of the lu interface allocates resources to various flows over the physical link. Resources are allocated upon activity and re-allocated during idle periods. When an RNC wants to disassociate from an SGSN, it issues an lu_Release command, upon receiving which, the lu can be released. The packet switched traffic is routed from the RNS to the SGSN using the lu-PS interface. This interface is also responsible for the mobility management. The RNC is responsible for frequency allocation and the allocated frequency or channel set to each node B is conveyed to the respective node B's through the lub interface.
The mobility management in the UMTS system is as follows. As soon as the UE powers up it is in the PMM-DETATCHED state in which there is no communication between the UE and the node B. When the GPRS attach procedure is completed, the MS moves to the PMM-CONNECTED state. When PS signaling is released, the state changes to PMM-IDLE, which is a state indicating that the PS signaling to the 3G-SGSN is broken. If the UE is out of coverage or if the URA update timer expires or if the radio resource controller connection cannot be established, then the UE is detached from then SGSN and the state changes to PMM-DETATCHED. The state transitions at the UE are shown in Fig. 3.
The state transition diagram at the SGSN is as shown in Fig. 4. The signals leading to the state transitions are as at the UE except that the state remains at PMM-CONNECTED if the serving RNC changes.
The network operation mode could be of two types: Type I when the Gs interface is present and Type II when Gs interface is not present. When the Gs interface is present, the UE can initiate combined update procedures. However, the mode should be the same for the entire routing area.
The radio resource controller (RRC) state machine for UTRAN is shown in Fig. 5. When there is no radio resource allocated to a UE, the RRC is in the RRC Idle Mode, in which, the MS can receive paging messages about the CN. In the RRC Connected Mode, the main states are Cell Connected and URA connected. When the UE is tracked at cell

level the RRC state is in the Cell Connected state and if the UE is tracked at the routing area level, then the state is URA connected. No dedicated radio resources are used at the URA Connected state. The UE in the RRC URA Connected state is paged by the RNC before a downlink transfer. In response, the UE sends a Cell Update message, upon receiving which, the state changes to the RRC Cell Connected state, and then, the RNC transfers the data and the signaling messages to the UE. To provide quality of service (QoS) to users, the traffic is classified into 4 categories, namely, interactive, voice, stream and best effort.
In the current technology, there is no efficient architecture and interfaces defined for the integration of WMAN and 3G wireless networks.
SUMMARY OF THE INVENTION
The present invention presents an architecture for integrating 3G UMTS and IEEE 802.16 networks, it is possible to have both a tightly and a loosely coupled system. Tightly coupled architecture involves lesser handoff latency and is considered more useful for delay sensitive applications which are predominantly present in IEEE 802.16 networks. In the tightly coupled system, the WMAN network is made to appear as a foreign 30 network to an existing 3G network. Similarly the 3G network is made to appear as a foreign WMAN network to an existing WMAN network. The tightly coupled architecture requires an integrating component that has the functionalities of both the 3G as well as the WMAN networks.
Accordingly this invention explains a system for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) comprising :
IEEE 802.16 system having a MT, AP and AR;
UMTS system having a UE, node B and the RNC ;
a mobile user terminal (MUT) which has a dual mode capability and is adapted to
associate with both the UMTS system as well as the IEEE 802.16 system; and
UMTS-802.16 Integrator.
Accordingly this invention explains a system for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) comprising an MUT which does not have a dual mode capability and has only 3G UMTS or IEEE 802.16 capabilities wherein the MUT registers with the network depending on its capabilities.
Accordingly this invention also explains a system for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) comprising the integrator wherein the said integrator has the

functionalities of the SGSN, the RNC, and the IEEE 802.16 AR where when an MUT powers up in the UMTS domain, it registers with the serving RNC.
Accordingly this invention also explains a system for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) when the IEEE 802.16 network is used as a back haul to the UMTS network comprising the integrator wherein the said integrator has an air interface connection to the IEEE 802.16 AP resulting in a two hop wireless network to transfer traffic into the back bone network where the IEEE 802.16 AP treats the integrator as an IEEE 802.16 MT. Accordingly this invention also explains a method for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN).
BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS
Figure 1: shows a typical IEEE 802.16d/e wireless metropolitan area network (WMAN)
Figure 2: shows a typical UMTS network
Figure 3: shows state transition diagram at UE for mobility management in UMTS
Figure 4: shows state transition diagram at SGSN for mobility management in UMTS
Figure 5: shows state transition diagram for RRC in UMTS
Figure 6: shows architecture for UMTS-802.16 Integration - Type 1
Figure 7: shows Handover signaling: IEEE 802.16 to UMTS network: Type 1
Figure 8: shows Handover signaling: UMTS to IEEE 802.16 network: Type 1
Figure 9: shows MUT Protocol Stack
Figure 10: shows Type I Architecture: Components and Interfaces
Figure 11: shows alternate Type 1 Architecture: Components and Interfaces
Figure 12: shows Type 2 Architecture: Components and Interfaces
DETAILED DESCRIPTION OF THE INVENTION
This invention presents a tightly coupled architecture for the integration of UMTS and IEEE 802.16 networks. There are two cases considered here:
1. When the UMTS and the 802.16 networks are at the same level, i.e., we have a one hop wireless network
2. When the coverage is only by UMTS but the traffic to the back bone network is back-hauled to an IEEE 802.16 network, thus resulting in a two hop wireless network
It first provides the architecture for case 1 mentioned above, and then extend the architecture to include case 2.

For the Type 1 network mentioned above, we present the architecture shown in Fig. 6. In the figure, we have the MT, AP and AR that belong to the IEEE 802.16 system, and the UE, node B and the RNC that belongs to the UMTS system. We define mobile user terminal (MUT) which has a dual mode capability and can associate with both the UMTS system as well as the IEEE 802.16 system. The UMTS-802.16 Integrator shown in Fig. 6 has the following functions. The integrator is expected to have the SGSN as well as the 802.16 APC/AR functionalities built in it because is to be connected to the backbone network as well as the GGSN of a 3G core network. The 3G GGSN treats the integrator as another SGSN, while the IEEE 802.16 AR treats the integrator as another AR. When an MUT registers with a 3G-UMTS network and decides to send traffic over the 3G network, then the data is transmitted to the back bone network through the SGSN. The integrator is connected to the AR of the 802.16 network as well as the back bone network. When an MUT moves from an 802.16 WMAN network to a 3G UMTS network, the integrator corresponds to the appropriate GGSN through the back bone network and also mentions the IP address of the target RNC. The GGSN treats this as an SGSN-SGSN handover and the existing handover mechanisms for inter SGSN defined in the 3GPP standards can be used. However, these result in additional signals to the RNC and the node B's since the registration process into the 3G handover is now initiated by the SGSN, and not the UE. The UE capabilities in UMTS [4] consist of the UMTS UE radio capability information, including power control, code resource, UE mode, ciphering and PDCP capabilities. When a dual mode MUT undergoes a hand off from an IEEE 802.16 network and indicates a handoff from an IEEE 802.16 network to a UMTS network, it shall inform the AP of its UMTS capabilities along with target UMTS RNC, which in turn, transfers this information to the IEEE 802.16 AR along with the context of the active flows. The integrator then performs a registration of the MUT at the SGSN. The MUT capabilities are then communicated to the appropriate RNC. Once the MUT hands off to the UMTS network, it shall then perform the UMTS power up procedures. The choice of the SGSN and RNC are however made after taking into account, information on the context of the flows incident on the mobile and the QoS requirements. The signaling for an IEEE 802.16 to UMTS handover is shown in Fig. 7. In the figure, the MOB_HOJND message is the hand off indication message that is given by the IEEE 802.16 AR to the integrator. The integrator obtains the mobile registration information and communicates to the SGSN, the UMTS RNC and the Node B. The mobile then registers in the UMTS network following the UMTS power up procedures This also requires the SBC-REQ and the SBC-RSP messages in the IEEE 802.16 network to be suitably modified to incorporate dual mode capability of the MT and the appropriate 3G MS ID and the IEEE 802.16 MAC address. The SBC-REQ message in the IEEE 802.16 standards [1] has an 8 bit field for the management message

type and a variable length field which is TLV encoded information. In the TLV encoded information the MUT shall communicate the dual mode capability along other capabilities. The MOB_HOJND message for the IEEE 802.16e standard [2] has an 8 bit field for management message type and a 6 bit reserved field. It also contains a 2 bit field for the hand off type. The handoff type 11 is currently reserved. The reserved handoff type is now used for indicating vertical handoff. Following the handoff type field is a 48 bit field for the target AP MAC address. This field is used only for the horizontal handoff, i.e., from one IEEE 802.16 network to another. When the vertical handoff type message is received by an AP, the AP sends a UBC_REQ message to the MUT. This message is the UMTS basic capabilities request message. The MUT responds with the UBC_RSP message which contains the UMTS capabilities of the MUT. The AP communicates this information to the AR, which, in turn communicates this to the SGSN, from which the RNC and node B obtain the capabilities and the context information. The MUT then powers up performs the UMTS network re-entry process at the UMTS node B. The modified MOB_HOJND message is shown in Table 1. The UBC_REQ and UBC_RSP message formats are shown in Tables 2 and 3, respectively. The TLV encoded information for the UBC_REQ message shall include the RNC and the node B in which the MUT can be expected to register after handoff to the UMTS network. The UBC^RSP message format is shown in Table 3. The TLV encoded information shall include the UMTS capabilities of the MUT as well as the UMTS MS-ID.
Ta

T

Table 3: UBC_RSP message for Type 1 architecture
Similarly, the registration process in the 3G network and the capability negotiation in the 3G network require additional fields to incorporate the dual mode capability of the terminals.
When handover takes place from the 3G UMTS to the IEEE 802.16 network, then the integrator is treated as a new AR and L3 handover mechanisms are required for completing the handover process. The mobile traffic context and the MAC address is informed to the corresponding AP and radio resource management and the registration processes are performed. However, the handover process also requires changes to the UMTS standards because the registration at the IEEE 802.16 network is now performed by the AR and not the MT as specified in the standards [1], [2]. Instead, we present a set of hand over signals as shown in Fig. 8. In the figure, the RA_Update message is the message sent by the UE to the node B indicating a change in the routing area. The integrator assigns a care-of-address (CoA) to the UE and also maps the CoA to the IEEE 802.16 IP address. When the handover is indicated by the routing area update with the new SGSN/RNC id corresponding to that of the integrator, the MUT capabilities are transferred to the IEEE 802.16 AR, which, in turn, initiates the registration and network entry process. It is also essential that the mobile context and QoS categories be mapped appropriately. The integrator therefore maps all the 3G categories of the incident flows to the appropriate IEEE 802.16 QoS classes. Hence, the integrator and the associated IEEE 802.16 network is made to appear as a foreign 3G UMTS network.

The MUT stack is shown in Fig. 9. It contains both the 802.16 device driver as well as the UMTS device driver.
The UMTS device driver implements the UMTS user and control functions [4]. When an MUT powers up in the UMTS coverage area, it runs the UMTS- GPRS power up procedure through the serving RNC (SRNC). The GPRS attach and the authentication procedures are followed and the best effort bearer set up is also performed. When powered up in the 802.16 network, the MUT exchanges the REG-REQ, REG-RSP messages to register and the basic capability negotiation is performed with the SBC-REQ and SBC-RSP messages. Depending on the QoS required for the service, radio resource availability and the network conditions an MUT could choose to handover from one network to the other. In the following, we present some of the basic messages in the integrated system and the interfaces between the various components of the integrated system.
The interfaces for the Type 1 architecture mentioned earlier are provided in Fig. 10. The functions of the interfaces are as follows.
The integrator acts as a foreign 3G network and the authentication and accounting is performed through the 3G AAA server. As mentioned earlier, the integrator consists of GGSN functionalities of the GPRS-UMTS system. When an MUT powers on in the 3G network it communicates with the node B over the Uu interface. The other interfaces are explained as follows:
> Gn/Gp: This is the interface between an SGSN and a GGSN. The Gn interface is used if both the SGSN as well as the GGSN belong to the same PLMN and the Gp interface is used, otherwise. This interface allows an SGSN to communicate user data while changing SGSN.
> Wz: This reference point occurs between the 802.16 AAA server and the AR. This reference point allows the 802.16 AAA server to authenticate 3G users in the WMAN cell. Functions of this reference point are similar to the Wy reference point mentioned below.
> Wr': This interface connects the 802.16 network to the 3G network through the integrator. The reference point exists between the integrator and the AR. The functionalities of this reference point include
^ Data for authentication signaling between MT and the 3G ^ Signaling for WMAN AR and the 3G authentication ^ Purging data for 802.16 access termination
> Wy: This interface exists between the 3G AAA server and the 3G home subschber
system i.e., the home GGSN. The prime purpose is for the 802.16 AAA infra
structure and the HSS. This shall be RADIUS based. Some of the functionalities of

this reference point include
/ Registration of theSGPP server for authorized 802.16 access
^ Purge procedure between 3GPP AAA and HSS
/ Retrieval of online and offline charging function addresses from the HSS An alternate architecture is one in which the MUT does not have a dual mode capability and has only 3G UMTS or IEEE 802.16 capabilities. In this case the MUT registers with the network depending on its capabilities. If the MUT has only 3G capabilities and wants to move to the IEEE 802.16 network, the flows handled by the MUT needs to be mapped to appropriate service flow ID (SFID) and the connection ID (CID). It is also essential for the MUT to obtain a care of address (CoA). The integrator provides the CoA for the MUT and acts as a foreign network for the home 3G network. The signaling shown in Fig. 8 can be applied to this scenario for the handoff from UMTS network to IEEE 802.16 network. However, the basic capabilities need not be registered with the IEEE 802.16 AR. The CoA can be appropriately mapped to a virtual mobile in the IEEE 802.16 network. All packets from the correspondent node are then transferred to the appropriate IEEE 802.16 AR, with IP tunneling. Similariy, when the MUT has IEEE 802.16 capabilities and wants to hand over to the 3G UMTS network, then the service class of the flows need to be appropriately mapped to the 3G traffic category and the CoA and the SRNC is assigned to the MUT. The integrator now acts as a foreign 3G network and the message exchanges are suitably performed (i.e., the 802.16 REG and MUT capability messages are suitably changed to the 3G messages).
A third type of architecture for the Type 1 network is as shown in Fig. 11. In this type of architecture, the integrator has to have the functionalities of the SGSN, the RNC, and the IEEE 802.16 AR built in it. Here, when an MUT powers up in the UMTS domain, It registers with the serving RNC. When a handover takes place to another RNC, the UMTS handover procedures are followed. When the MUT moves from an 802.16 network to a UMTS network, the integrator is treated as a new RNC or a new SGSN depending on the target SGSN. Then, one of the inter-RNC or inter-SGSN handover procedures can be applied accordingly. The handover from UMTS to IEEE 802.16 network is as explained in the previous architecture shown in Fig. 10. It is also possible to upgrade the integrator to include functions of the node B also. This results in added complexity and overheads, but may result in reduced vertical handoff latency time.
We also present an architecture for the integration of a UMTS and an IEEE 802.16 network, when the IEEE 802.16 network is used as a back haul to the UMTS network. A schematic of this scenario is shown in Fig. 12. In the figure, it is shown that the integrator has an air interface connection to the IEEE 802.16 AP. Thus there exists a two hop wireless network to transfer traffic into the back bone network. In this scenario the IEEE 802.16 AP

treats the integrator as an IEEE 802.16 MT. The Registration request and response messages now contain the MAC address of the integrator. However, it is noted that the packets that are transmitted by the SGSN are IP packets whereas the AP can only decipher MAC packets. Hence, the integrator needs to include the IEEE 802.16 MAC headers before transmitting the packets to the AP. The MAC address of the integrator shall then be used by the AR to de-capsulate the IP packets and then transmit it over the back bone network. Similarly, when the AR receives IP packets from the back bone network corresponding to the IP address of the UMTS MUT, the AR forwards the packet to the appropriate AP. The AP then encapsulates the IP packet with the appropriate MAC packets and transmits to the integrator. This architecture therefore requires that when the SGSN registers with an AP it also mentions to the AP about the IP addresses of the MUTs associated with it. Hence, it requires the following changes to the registration process at the IEEE 802.16 AP. The REG-REQ message in the IEEE 802.16 standards [1] has an 8 bit field for the management message type and a variable length field which is TLV encoded information. In the TLV encoded information the integrator shall add the IP addresses of the MUT or the SGSN along with other capabilities. The architecture shown in Fig. 12 is valid or MUT with dual mode capabilities or with UMTS capabilities. For an MUT with IEEE 802.16 capabilities alone, the MUT cannot handover to the UMTS network as there is no link to the back bone network. To handover to a UMTS network that is back hauled to another IEEE 802.16 AP-_ -Mechanisms in [31 can be adopted to perform an inter-IEEE 802.16 AP handover. If the UMTS network belongs to a different AR, then L3 handover mechanisms are applied to perform the handover to the UMTS network.
The above-presented description is of the best mode contemplated for carrying out the present invention. The manner and process of making and using it is in such a full, clear, concise and exact terms as to enable to any person skilled in the art to which it pertains to make and use this invention. New embodiments in particular, which also lie within the scope of the invention can be created, in which different details of the different examples can in a purposeful way be combined with one another.
This invention is however, susceptible to modifications and alternate constructions from that disclosed above which are fully equivalent. Consequently, it is not the intention to limit this invention to the particular embodiment disclosed. On the contrary, the intention is to cover all modifications and alternate constructions coming within the spirit and scope of the invention as generally expressed by the following claims which particularly point out and distinctly claim the subject matter of the invention.

Glossary of Terms and their Definitions
MT: IEEE 802.16 mobile terminal, it is the wireless terminal used by the IEEE 802.16 user to
transmit data to the wireless network
AP: IEEE 802.16 access point, it is the node the MT communicates with, to access the
wireless medium
AR/APC: IEEE 802.16 access router/access point controller, it connects the IEEE 802.16
network to the back bone network
UMTS: Universal mobile telecommunications system
GPRS: Generalized packet radio service
UE: UMTS user equipment, it is the wireless terminal used by the UMTS user to transmit
data to the wireless network
Node B: The UMTS base station, it is the node the UE communicates with, to access the
wireless network
RNC: UMTS radio network controller, this is the node that interfaces the UMTS to the GPRS
network
UMTS: Universal mobile telecommunications system
GGSN: Gateway GPRS support node, this is the node that connects the GPRS network to
the back bone network
SGSN: Serving GPRS support node, this node controls all the GPRS base station controllers
and the UMTS RNC
Uu: The air interface between the UMTS node B and the UMTS UE
lu: The interface between the UMTS RNC and the SGSN
lub: The interface between the UMTS RNC and node B
lur: The interface between one UMTS RNC and another
RNS: The UMTS radio network system consisting of the RNC and node B
PMM: Packet mobility management in UMTS
MUT: Mobile user terminal in the integrated UMTS-IEEE802.16 network. This could have the
capabilities of a UMTS UE or an IEEE 802.16 MT or both
MOB__HOJND: Mobile handoff indication message in IEEE 802.16e. This indicates handoff
to the serving AP
SBC_REQ: The MT basic capabilities request message in IEEE 802.16d/e. This message is
used by the AP to request the MT for its capabilities
SBC_RSP: The MT basic capabilities response message in IEEE 802.16d/e. This message
is used by the MT to inform the AP of its capabilities
TLV: Type, length, value, a format for encoding messages

UBC_REQ: UMTS basic capabilities request. This message is used by the AP to request the
dual mode MUT in the IEEE 802.16 network to specify the UMTS capabilities of the MUT
UBC_RSP: UMTS basic capabilities response. This message is used by the dual mode MUT
in the IEEE 802.16 network to specify the UMTS capabilities of the MUT to the AP
MOB^COA: MUT Care-of address, this address is allocated by the UMTS-IEEE 802.16
integrator to the MUT for mobility management between the UMTS and the IEEE 802.16
network
MAC: Medium access control
UTRAN: UMTS Radio Access Network
REG_REQ: IEEE 802.16 registration request message, this is sent by the MT to the AP to
request for registration into the IEEE 802,16 networks
REG_RSP: IEEE 802.16 registration response message, this is sent by the AP to the MT to
for registration into the IEEE 802,16 networks
Gn/Gp: Interface between the SGSN and GGSN
AAA: Authentication authorization and accounting server, this is used in integrated networks
for security and billing purposes when the MUT is roaming between networks
Wy: Interface between UMTS AAA server and the 3G home subscriber.
Wz: Interface between the IEEE 802.16 AAA server and the SGSN.
Wr': Interface between IEEE 802.16 AR and the integrator
SFID: Service flow ID for each flow in an IEEE 802.16 network
CID: Connection ID for each flow in an IEEE 802.16 network. A service flow can be
comprised of many connections

References
[1] Part 16: Air interface for fixed broadband wireless access systems: Draft IEEE
standard for wireless local and metropolitan area networks, IEEE P802.16-
Revd/D3-2004. [2] Part 16: Air interface standard for fixed and mobile broadband wireless systems:
Amendment for physical and medium access control layers for combined fixed and
mobile operation in licensed bands, IEEE P802.16e/D2. April 2004. [3] Mukesh Taneja, Anand Santhanakrishnan, and Ganapathy Viswanath, "Methods
and System for recommended and active set selection for handoff in wireless
multimedia networks," Patent filed, Application Number 190/CHE/2004. [4] 3""^ generation partnership project (3GPP); Technical specification group services
and system aspects; Generalized packet radio service (GPRS); Service
description; 3GPP TS 23.060 V 4.5.0, June 2002. [5] 3^^ generation partnership project; Technical specification group services and
system aspects; Network architecture Release 4, 3GPP TS 23.002 V 4.4.0,
January 2002.

We Claim
1. A System for integration of third generation (3G) universal mobile telecommunications
system (UMTS) and wireless metropolitan area networks (WMAN) comprising :
IEEE 802.16 system having an MT, AP and AR;
UMTS system having a UE, node B and the RNC ;
a mobile user terminal (MUT) which has a dual mode capability and is adapted to
associate with both the UMTS system as well as the IEEE 802.16 system; and
UMTS-802.16 Integrator.
«
2. A system as claimed in claim 1 wherein the integrator has the SGSN and the 802.16 APC/AR functionalities for connecting to the backbone network and the GGSN of a 3G core network.
3. A system as claimed in claim 1 wherein the 3G GGSN treats the integrator as another SGSN and the IEEE 802.16 AR treats the integrator as another AR.
4. A system as claimed in claim 1 wherein when an MUT registers with a 3G-UMTS network and sends traffic over the 3G network, then the data is transmitted to the back bone network through the SGSN.
5. A system as claimed in claim 1 wherein the integrator is connected to the AR of the 802.16 network and the back bone network and when an MUT moves from an 802.16 WMAN network to a 3G UMTS network, the integrator corresponds to the appropriate GGSN through the back bone network and mentions the IP address of the target RNC.
6. A system as claimed in claim 1 wherein the GGSN treats the correspondence as an SGSN-SGSN handover and uses an existing handover mechanism.
7. A system as claimed in claim 1 wherein the UE capabilities in UMTS comprise UMTS UE radio capability information, power control, code resource, UE mode, ciphering and PDCP capabilities.
8. A system as claimed in claim 1 wherein when a dual mode MUT undergoes a hand off from an IEEE 802.16 network and indicates a handoff from an IEEE 802.16 network to a

UMTS network, It inrorm the AP of its UMTS capabilities along with target UMTS RNC, which, transfers the information to the IEEE 802.16 AR along with the context of the active flows.
9. A system as claimed in claim 1 wherein the integrator performs a registration of the MUT
at the SGSN and the MUT capabilities are communicated to the appropriate RNC.
10. A system as claimed in claim 1 wherein once the MUT hands off to the UMTS netsNork, it perform the UMTS power up procedures and the choice of the SGSN and RNC are made after taking into account, information on the context of the flows incident on the mobile and the QoS requirements.
11. A system as claimed in claim 1 wherein the signaling for an IEEE 802.16 to UMTS handover comprise MOB_HOJND message which is the hand off indication message given by the IEEE 802.16 AR to the integrator where the integrator obtains the mobile registration information and communicates to the SGSN, the UMTS RNC and the Node B.
12. A system as claimed in claim 1 wherein the mobile registers in the U^ATS network following the UMTS power up procedures where the SBC-REQ and the SBC-RSP messages in the IEEE 802.16 network are modified to incorporate dual mode capability of the MT and the appropriate 3G MS ID and the IEEE 802.16 MAC address.
13. A system as claimed in claim 1 wherein the SBC-REQ message in the IEEE 802.16 standards has an 8 bit field for the management message type and a variable length field which is TLV encoded information where the MUL communicate the dual mode capability along with other capabilities.

14. A system as claimed in claim 1 wherein the MOB_HOJND message for the IEEE ^02.16e standard has an 8 bit field for management message type, a 6 bit reserved field and a 2 bit field for the hand off type.
15. A system as claimed in claim 1 wherein the reserved handoff type is used for indicating vertical handoff where the handoff type field is a 48 bit field for the target AP MAC address and the field is used for the horizontal handoff from one IEEE 802.16 network to another.

16. A system as claimed in claim 1 wherein when the vertical handoff type message is received by an AP, the AP sends a UBC_REQ message to the MUT where the said message is the UMTS basic capabilities request message.
17. A system as claimed in claim 1 wherein the MUT responds with the UBC_RSP message which contains the UMTS capabilities of the MUT and the AP communicates the said information to the AR, which communicates it to the SGSN, from which the RNC and node B obtain the capabilities and the context information.
18. A system as claimed in claim 1 wherein the MUT performs the UMTS network re-entry process at the UMTS node B and the TLV encoded information for the UBC_REQ message include the RNC and the node B in which the MUT register after handoff to the UMTS network where the TLV encoded information include the UMTS capabilities of the MUT and the UMTS MS-ID.
19. A system as claimed in claim 1 wherein the registration process in the 3G network and the capability negotiation in the 30 network use an additional fields to incorporate the dual mode capability of the terminals where when handover takes place from the 3G UMTS to the IEEE 802.16 network, the integrator is treated as a new AR and an L3 handover mechanisms is used for completing the handover process.
20. A system as claimed in claim 1 wherein the mobile traffic context and the MAC address is informed to the corresponding AP and radio resource management and the registration processes are performed.
21. A system as claimed in claim 1 wherein the RA_Update message is the message sent by the UE to the node B indicating a change in the routing area where the integrator assigns a care-of-address (CoA) to the UE and also maps the CoA to the IEEE 802.16 IP address and when the handover is indicated by the routing area update with the new SGSN/RNC id corresponding to that of the integrator, the MUT capabilities are transferred to the IEEE 802.16 AR, which, initiates the registration and network entry process.
22. A system as claimed in claim 1 wherein the mobile context and QoS categories are
mapped where the integrator maps all the 3G categories of the incident flows to the
appropriate IEEE 802.16 QoS classes making the integrator and the associated IEEE
802.16 network appear as a foreign 3G UMTS network.

23. A system as claimed in claim 1 wherein the UMTS device driver implements the UMTS user and control functions and when an MUT powers up in the UMTS coverage area, the UMTS- GPRS power up procedure runs through the serving RNC (SRNC) and the GPRS attach and the authentication procedures are followed and the best effort bearer set up is a performed.
24. A system as claimed in claim 1 wherein when powered up in the 802.16 network, the MUT exchanges the REG-REQ, REG-RSP messages to register and the basic capability negotiation is performed with the SBC-REQ and SBC-RSP messages and depending on the QoS required for the service, radio resource availability and the network conditions an MUT chooses to handover from one network to the other.
25. A system as claimed in claim 1 wherein the integrator acts as a 3G network and the authentication and accounting is performed through the 3G AAA server where , the integrator consists of GGSN functionalities of the GPRS-UMTS system.
26. A system as claimed in claim 1 wherein when an MUT powers on in the 3G network it communicates with the node B over the Uu interface.
27. A system as claimed in claim 1 wherein an interface Wz occurs between the 802.16 AAA server and the AR which allows the 802.16 AAA server to authenticate 3G users in the WMAN ceil.
28. A system as claimed in claim 1 wherein an interface Wr occurs between the integrator and the AR which allows data for authentication signaling between MT and the 3G, signaling for WMAN AR and the 3G authentication and Purging data for 802.16 access termination.
29. A system as claimed in claim 1 wherein an interface Wy occurs between the 3G AAA server and the 3G home subscriber system which allows registration of the 3GPP server for authorized 802.16 access, purging procedure between 3GPP AAA and HSS and retrieval of online and offline charging function addresses from the HSS .
30. A System for integration of third generation (3G) universal mobile telecommunications
system (UMTS) and wireless metropolitan area networks (WMAN) comprising an MUT
which does not have a dual mode capability and has only 3G UMTS or IEEE 802.16

capabilities wherein the MUT registers with the network depending on its capabilities.
31. A system as claimed in claim 30 wherein if the MUT has only 3G capabilities and wants to move to the IEEE 802.16 network, the flows handled by the MUT are mapped to appropriate service flow ID (SFID) and the connection ID (CID) and the MUT obtains a care of address.
32. A system as claimed in claim 30 wherein the integrator provides the CoA for the MUT and acts as a foreign network for the home 3G network where the CoA appropriately mapped to a virtual mobile in the IEEE 802.16 network.
33. A system as claimed in claim 30 wherein all packets from the correspondent node are transferred to the appropriate IEEE 802.16 AR, with IP tunneling and when the MUT has IEEE 802.16 capabilities and wants to hand over to the 3G UMTS network, the service class of the flows are mapped to the 3G ASC and the CoA and the SRNC is assigned to the MUT.
34. A system as claimed in claim 30 wherein the integrator acts as a foreign 3G network and the 802.16 REG and MUT capability messages are suitably changed to the 3G messages.
35. A System for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) comprising the integrator wherein the said integrator has the functionalities of the SGSN, the RNC, and the IEEE 802.16 AR where when an MUT powers up in the UMTS domain, it registers with the serving RNC.
36. A system as claimed in claim 35 wherein when a handover takes place to another RNC, the UMTS handover procedures are followed and when the MUT moves from an 802.16 network to a UMTS network, the integrator is treated as a new RNC or a new SGSN depending on the target SGSN and one of the inter-RNC or inter-SGSN handover procedures is applied accordingly.
37. A System for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) when the IEEE 802.16 network is used as a back haul to the UMTS network comprising the integrator wherein the said integrator has an air interface connection to the IEEE 802.16 AP resulting in a two hop

wireless network to transfer traffic into the back bone network where the IEEE 802.16 AP treats the integrator as an IEEE 802.16 MT.
38. A system as claimed in claim 37 wherein the Registration request and response message contain the MAC address of the integrator where the packets that are transmitted by the SGSN are IP packets and the AP decipher only MAC packets.
39. A system as claimed in claim 37 wherein the integrator include the IEEE 802.16 MAC headers before transmitting the packets to the AP where the MAC address of the integrator is used by the AR to de-capsulate the IP packets and transmit it over the back bone network.
40. A system as claimed in claim 37 wherein , when the AR receives IP packets from the back bone network corresponding to the IP address of the UMTS MUT, the AR forwards the packet to the appropriate AP and the AP encapsulates the IP packet with the appropriate MAC address and transmits to the integrator.
41. A system as claimed in claim 37 wherein when the SGSN registers with an AP it mentions to the AP about the IP addresses of the MUTs associated with it.
42. A system as claimed in claim 37 wherein the REG-REQ message in the IEEE 802.16 standards has an 8 bit field for the management message type and a variable length field which is TLV encoded information where in the TLV encoded information the integrator adds the IP addresses of the MUT or the SGSN along with capabilities.
43. A system as claimed in claim 37 wherein if the UMTS network belongs to a different AR, then L3 handover mechanisms are applied to perform the handover to the UMTS network.
44. A method for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) utilizing the said system as claimed in claim 1 to 43.
45. A system for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) substantially as herein described particularly with reference to the drawings.

46. A method for integration of third generation (3G) universal mobile telecommunications system (UMTS) and wireless metropolitan area networks (WMAN) substantially as herein described particularly with reference to the drawings.
Dated this 25*^ day of May 2005

Documents:

0483-che-2004 abstract-duplicate.jpg

0483-che-2004 abstract-duplicate.pdf

0483-che-2004 claims-duplicate.pdf

0483-che-2004 description (complete)-duplicate.pdf

0483-che-2004 drawings-duplicate.pdf

483-che-2004-abstract.pdf

483-che-2004-claims.pdf

483-che-2004-correspondnece-others.pdf

483-che-2004-correspondnece-po.pdf

483-che-2004-description(complete).pdf

483-che-2004-description(provisional).pdf

483-che-2004-drawings.pdf

483-che-2004-form 1.pdf

483-che-2004-form 26.pdf

483-che-2004-form 5.pdf

483-che-2004-form 9.pdf

« Previous Patent

Next Patent »

Patent Number

228946

Indian Patent Application Number

483/CHE/2004

PG Journal Number

12/2009

Publication Date

20-Mar-2009

Grant Date

13-Feb-2009

Date of Filing

27-May-2004

Name of Patentee

SAMSUNG INDIA SOFTWARE OPERATIONS PRIVATE LIMITED

Applicant Address

BAGMANE LAKEVIEW, BLOCK 'B', NO. 66/1, BAGMANE TECH PARK, CV RAMAN NAGAR, BYRASANDRA, BANGALORE 560 093,

Inventors:

#	Inventor's Name	Inventor's Address
1	ANAND, SANTHANAKRISHNAN	BAGMANE LAKEVIEW, BLOCK 'B', NO. 66/1, BAGMANE TECH PARK, CV RAMAN NAGAR, BYRASANDRA, BANGALORE 560 093,
2	VISWANATH, GANAPATHY	BAGMANE LAKEVIEW, BLOCK 'B', NO. 66/1, BAGMANE TECH PARK, CV RAMAN NAGAR, BYRASANDRA, BANGALORE 560 093,
3	TANEJA, MUKESH	BAGMANE LAKEVIEW, BLOCK 'B', NO. 66/1, BAGMANE TECH PARK, CV RAMAN NAGAR, BYRASANDRA, BANGALORE 560 093,

PCT International Classification Number

H04Q7/22

PCT International Application Number

N/A

PCT International Filing date

PCT Conventions:

#	PCT Application Number	Date of Convention	Priority Country
1			NA