Title of Invention

A METHOD TO MAINTAIN MAPPING BETWEEN UNIQUE IDENTIFIERS ASSIGNED TO MULTI-MODE EQUIPMENT

Abstract

The invention relates in general to a method to maintain mapping between unique identifiers assigned to multimode equipment more particularly to inter-RAT handovers in wireless domain and in particular to handoff between HRPD and 1x networks. For facilitating these handoffs and cross paging, a mapping is required at the network side between the different identifiers used on the involved networks. This invention describes a method for maintaining a mapping at network level between different identifiers namely IMSI and UATI for 1x and HRPD networks respectively to attain cross paging at the IWS.

Full Text

FIELD OF INVENTION This invention relates in general to wireless networks. Further, this invention relates to maintenance of a mapping between various identifiers used by the multi-mode access equipment to access different networks. More particularly, this invention relates to a method to maintain mapping between unique identifiers assigned to multi-mode equipment. DESCRIPTION OF THE RELATED ART The multi-mode Access Terminal (AT) supporting both 1x and HRPD standard uses different identifiers to talk on respective networks. For cross paging between these two networks, it is mandatory to keep a mapping between the two at the network level. Currently, both networks have the knowledge about the identifiers used with their link only. Current management of IMSI or UATI in 1x and HRPD networks respectively is done independently. HRPD network has no knowledge of IMSI and similarly 1x network does not know about the UATI assigned to the multimode AT. Therefore, in the said circumstances, cross paging would not possible between HRPD and 1x. Further, the hybhd AT has to keep looking at 1x control channel for getting pages destined for itself when in HRPD network. Moreover, no method is presently available to inform the network of the movement to the other network. SUMMARY OF THE INVENTION The primary object of this invention is to invent a method to maintain the mapping between various unique identifiers associated with multi-mode AT to access different radio access technologies. This mapping is mandated at network in order to facilitate the cross paging between the access technologies that multi-mode AT supports. It is another object of this invention to invent a method for maintenance of IMSI and UATI, the unique identifiers used in 1x and HRPD networks respectively with IMSI being the pivot as UATI is a temporary identifier. The invention relates in general to inter-RAT handovers in wireless domain and in particular to handoff between HRPD and 1x networks. For facilitating these handoffs and cross paging, a mapping is required at the network side between the different identifiers used on the involved networks. Both CDMA2000 1x and HRPD (also known as EVDO) are deployed widely in many parts of the world. The advantages of HRPD are the high data rate and its customization to increase efficiency to cater for data only. At the other hand 1x is widely present and caters to the basic and mostly used voice services and data also. If the best of both networks can be utilized in the deployed areas, then a much better service can be provided to the end users. This invention provides for a method to maintain the mapping between UATI (identifier at HRPD) and IMSI (identifier at 1x). The invention describes a method for maintaining a mapping at network level between different identifiers namely IMSI and UATI for 1x and HRPD networks respectively to attain cross paging at the IWS. Accordingly the present invention relates to a method for maintaining a mapping at network level between different identifiers namely IMSI and UATI for 1x and HRPD networks respectively to attain cross paging at the IWS. Accordingly the present further relates to a method for maintaining a mapping at network level between different identifiers namely IMSI and UATI wherein the call flow for TIA-878 architecture includes, registering the AT at the end of UATI assignment procedure with the IWS by the HRPD AN; triggering sending of registration message of 1x with IMSI as identifier by AT; extracting the IMSI from encapsulated registration message; and maintaining the IMSI-UATI mapping by the IWS. Accordingly the present invention further relates to a method for maintaining a mapping at network level between different identifiers namely I MSI and UATI wherein the mapping for TIA-1878 architecture includes, registering the AT at the end of UATI assignment procedure with the IWS by the PCF; triggering sending of registration message of 1x with IMS! as identifier by the AT; extracting the IMSI from encapsulated registration message; and maintaining the IMSI-UATI mapping by IWS. Accordingly the present invention further relates to a method for maintaining a mapping at network level between different identifiers namely IMSI and UATI wherein the call flow for the maintenance of mapping for TIA-878 architecture comprise the steps of, sending a UATI Request message by the AT(A1); generating a UATI and assigns it to AT via UATlAssignment message by HRPD AN (H1); assigning UATI to AT and sending UATlComplete message to HRPD AN (A2); sending IWS Registartion ind message with UATI by HRPD AN (H2); storing the UATI and its context as to which HRPD AN it is connected to by the IWS (11); triggering sending of 1x Registration message on 3G1x notification application by AT (A3); foHA/arding the 3G1x packet to IWS in IWS recv frame message with UATI by the HRPD AN (H3); and getting the UATI and looks into the 1x message by the IWS (12). Accordingly the present invention further relates to a method for maintaining a mapping at network level between different identifiers namely IMS! and UATI the call flow for the maintenance of mapping for TIA-1878 architecture comprises the steps of, sending a UATlRequest message by the AT (A1); generating a UATI and assigns it to AT via UATlAssignment message by HRPD AN and starts T14-UATI-Req timer(HI); generating a UATI and sends it to HRPD AN in A14-UATIAssignment message by PCF (PI); sending the assigned UATI to AT in UATlAssignment message by HRPD AN (H2) and stops T14-UATI-Req timer; assigning UATI to AT and sending UATlComplete message to HRPD AN (A2); sending A14- UATIComplete message to PCF(H3) and Starts T14-UATI-Comp timer; sending A14 UATICompleteAck to HRPD AN and IWS Registartion ind message with UATI to IWS over H1 interface by PCF (P2); stopping T14-UATI-Comp timer(H4); storing the UATI and its context as to which PCF it is connected to by the IWS (11); triggering sending of 1x Registration message on 3G1x notification application by AT (A3); foHA/arding the 3G1x packet to PCF in A14-IWS recv frame message with UATI by the HRPD AN (H5); forwarding the 301 x packet to IWS in IWS recv frame message with UATI by PCF (P3);and getting the UATI and looks into the 1x message by IWS (12). These and other objects, features and advantages of the present invention will become more readily apparent from the detailed description taken in conjunction with the drawings and the claims. BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS Figure 1 shows the current network architecture with hybrid AT. Figure 2 shows the network architecture with a proposed new node named IWS (Interworking Solution) to handle cross interactions between the two kinds of network interfaces. Figure 3 shows UATI and IMSI mapping call flow for TIA-878 architecture, Figure 4 shows UATI and IMSI mapping forTIA-1878 architecture. DETAILED DESCRIPTION OF THE INVENTION A preferred embodiment of the present invention will now be explained with reference to the accompanying drawings. It should be understood however that the disclosed embodiment is merely exemplary of the invention, which may be embodied in vahous forms. The following description and drawings are not to be construed as limiting the invention and numerous specific details are described to provide a thorough understanding of the present invention, as the basis for the claims and as a basis for teaching one skilled in the art on how to make and/or use the invention. However in certain instances, well-known or conventional details are not described in order not to unnecessarily obscure the present invention in detail. Before describing the various aspects and details of the present invention it will be useful to deschbe the context in which the invention is used. Consequently, a preliminary discussion that refers to Figures 1, Figure 2, Figure 3 and Figure 4 is hereby provided. Figure 1 shows the current network architecture with hybrid AT. The AT maintains two separate stacks and the interaction between air interfaces for the two is nonexistent. The HAT uses UATI as identifier on the HRPD network and IMSI as an identifier on the 1x network. The correlation between IMSI and UATI is known only to HAT and no entity on the network side is aware of this mapping in this current architecture. The coordination between the two networks is done at the HAT level only and thus it looks for both the network messages by doing time multiplexing. Referring to Figure 2 it shows the network architecture with a proposed new node named IWS (Interworking Solution) to handle cross interactions between the two kinds of network interfaces. 201 refers to the new network entity i.e. Interworking Solution (IWS) that will be a part of the HRPD RAN. The IWS interfaces to the MSC via an lOS A1 interface, and also to the SC/MM via a new H1 interface. The SC/MM may be located in either the AN or the PCF in the EVDO RAN. The primary function of the IWS is to translate A1 messages to CDMA 2000 LAC messages, which are then sent to the SC/MM for eventual transmission to the HAT. If the SC/MM is located in the AN, the AN will send the message directly to the HAT using the 3G1x Services Notification Application protocol. If the SC/MM is in the PCF, the SC/MM must first send the CDMA 2000 LAC message to the AN over the A14 interface. Likewise, messages received from the HAT (such as Connection Request messages) by the AN may result in the SC/MM sending update messages to the IWS; the IWS may then send an A1 1oS message (e.g. Location Updating Request) to the MSC. 202 refers to the new interface between the IWS and the SC/MM. The protocol stack is based on TCP/IP, with a I OS layer above that. Messages carry the encapsulated 3G LAC messages for delivery to the SC/MM; also carries information from the SC/MM to the iWS. This interface connects the IWS to the SC/MM in the HRPD architecture. The interface is IP-based and carries 3G1X LAC encapsulated PDUs in an lOS-defined protocol. The H1 interface is an IP-based interface. The Figure 2 shows the protocol stacks for the architecture based on TIA-878. A similar figure can be created for the architecture based on TIA-1878; the only change would be that the SC/MM would be in the PCF, and there would be an A14 interface between the PCFandtheAN. Figure 3 shows UATI and IMSI mapping call flow for TIA-878 architecture. It is explained in detail later with reference to this figure. 301 is a new step introduced at HRPD AN. The HRPD AN has to register the AT at end of UATI assignment procedure with the IWS. 302 is the new step at AT and AT needs to trigger sending of registration message of 1x with IMSI as identifier. 303: The IWS extracts the IMSI from encapsulated registration message and maintains the IMSI-UATI mapping. Figure 4 shows UATI and IMSI mapping for TIA-1878 architecture. It is explained in detail later with reference to this figure. 401 is a new step introduced at PCF. The PCF has to register the AT at end of UATI assignment procedure with the IWS. 402 is the new step at AT and AT needs to trigger sending of registration message of 1x with IMSI as identifier. 403: The IWS extracts the IMSI from encapsulated registration message and maintains the IMSI-UATI mapping. Messages on HI interface those are required for attaining the mapping between IMSI and UATI are as follows. IWS RecvFrame MSGJD The message identifier set to 0x01 by IWS. ATID The unique identifier to distinguish this message is for which AT. In case of HRPD system, this ID can be set to UATI. ACK_REQD This bit is set to 1 by IWS if an ack is mandated for this 1x packet. SEQ_NUM The sequence number for acknowledgement purpose. This field is present only if ACK_REQD is set to 1. PDU_LENGTH Length of 1x LAC PDU. RESERVED To make the message octet aligned. It is set to 0. 1x LAC PDU The IWS forms and put the 1x LAC PDU of required 1x message like GPM, DBM etc.. IWSRegistrationInd MSGJD The message identifier set to 0x05 by HRPD. ATID The unique identifier to distinguish this message is for which AT. In case of HRPD system, this ID can be set to UATI. RESERVED This field is set to 0 and is present to make the message octet aligned. IWSRegistrationAck MSGJD The message identifier set to 0x03 by IWS. ATID The unique identifier to distinguish this message is for which AT. In case of HRPD system, this ID can be set to UATI. Mapping maintenance call flow: Note: Following convention is used with call flows: Each step is identified by two a letter and a numeric like Xn, where X can take on following values: A Hybrid AT H HRPD AN M 1xMSC P PCF B 1xBSC I IWS And n is a numeric value stating the nth step at that node. For e.g. A2 means step 2 at hybrid AT in the call context. The call flow for the maintenance of mapping for TIA-878 architecture is as shown in figure 3. A1 AT sends a UATIRequest message. H1 HRPD AN generates a UATI and assigns it to AT via UATIAssignment message. A2 UATI is assigned to AT and it sends UATIComplete message to HRPD AN. H2 HRPD AN sends IWS Registartion ind message with UATI. II IWS stores the UATI and its context as to which HRPD AN it is connected to. Config negotiation procedures are carried out and 3G1x Notification service is negotiated along with other parameters for the AT. A3 AT triggers sending of 1x Registration message on 3G1x notification application. The LAC PDU contains the IMSI value in address sublayer fields. H3 The HRPD AN forwards the 3G1x packet to IWS in IWS recv frame message with UATI. 12 IWS gets the UATI and looks into the 1x message. As the 1x message is Registration, it takes out IMSI and populates its structures for UATI and IMSI mapping. The mapping is maintained with IMSI as reference (as UATI is temporary id). So whenever UATI is (re)assigned, the hybrid AT sends a 1x registration message with IMSI and IWS updates the table i.e. if an entry exists with this IMSI, it is overwritten or else a new entry is created. For the alternate HRPD architecture viz. TIA-1878 architecture is as shown in figure 4. A1 AT sends a UATIRequest message. H1 HRPD AN generates a UATI and assigns it to AT via UATIAssignment message. Starts T14-UAT1-Req timer. P1 PCF generates a UATI and sends it to HRPD AN in A14-UATIAssignment message. H2 HRPD AN sends the assigned UATI to AT in UATIAssignment message. Stops T14-UATI-Req timer. A2 UATI is assigned to AT and it sends UATIComplete message to HRPD AN. H3 Sends A14-UATIComplete message to PCF. Starts T14-UATI-Comp timer. P2 PCF sends A14 UATICompleteAck to HRPD AN and IWS Registartion ind message with UATI to IWS over H1 interface. H4 Stops T14-UATI-Comp timer. 11 IWS stores the UATI and its context as to which PCF it is connected to. Configuration negotiation procedures are carried out and 3G1x Notification service is negotiated along with other parameters for the AT. A3 AT triggers sending of 1x Registration message on 3G1x notification application. The LAC PDU contains the IMSI value in address sublayer fields. H5 The HRPD AN forwards the 3G1x packet to PCF in A14-IWS recv frame message with UATI. P3 PCF forwards the 3G1x packet to IWS in IWS recv frame message with UATI. 12 IWS gets the UATI and looks into the 1x message. As the 1x message is Registration, it takes out IMSI and populates its structures for UATI and IMSI mapping. The mapping is maintained with IMSI as reference (as UATI is temporary id). So whenever UATI is (re)assigned, the hybrid AT sends a 1x registration message with IMSI and IWS updates the table i.e. if an entry exists with this IMSI, it is overwritten or else a new entry is created. The foregoing description of a preferred embodiment of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Obvious modifications or variations are possible in light of the above teachings. Although the invention has been described with respect to specific embodiments thereof, these embodiments are merely illustrative, and not restrictive of the invention. For example, a receiver device can also include other elements such as copier, printer, disk drives etc. Memory also contains additional information such as applications programs, network, communication programs, operating system software data etc. Although the scanning and sending of the document is done by the interface between the scanner and the GSM module, Local Area Network, Internet or the Bluetooth mobile as have been described, it should be apparent that other methods and types of scanning and forwarding can be provided. In the description herein, numerous specific details are provided, such as examples of components and/or methods, to provide a thorough understanding of embodiments of the present invention. One skilled in the relevant art will recognize, however, that an embodiment of the invention can be practiced without one or more of the specific details, or with other apparatus, systems, assemblies, methods, components, materials, parts, and/or the like. In other instances, well-known structures, materials, or operations are not specifically shown or described in detail to avoid obscuring aspects of embodiments of the present invention. Embodiments of the invention may be implemented by using a programmed general purpose digital computer, by using application specific integrated circuits. programmable logic devices, field programmable gate arrays, optical, chemical, biological, quantum or nano-engineered systems, components and mechanisms may be used. In general, the functions of the present invention can be achieved by any means as is known in the art. Distributed or networked systems, components and circuits can be used. Communication, or transfer, of data may be wired, wireless, or by any other means. It will also be appreciated that one or more of the elements depicted in the drawings/figures can also be implemented in a more separated or integrated manner, or even removed or rendered as inoperable in certain cases, as is useful in accordance with a particular application. It is also within the spirit and scope of the present invention to implement a program or code that can be stored in a machine-readable medium to permit a computer to perform any of the methods described above. Additionally, any signal arrows in the drawings/Figures should be considered only as exemplary, and not limiting, unless otherwise specifically noted. Furthermore, the term "or" as used herein is generally intended to mean "and/or" unless otherwise indicated. Combinations of components or steps will also be considered as being noted, where terminology is foreseen as rendering the ability to separate or combine is unclear. As used in the description herein and throughout the claims that follow, "a", "an", and "the" includes plural references unless the context clearly dictates otherwise. Also, as used in the description herein and throughout the claims that follow, the meaning of "in" includes "in" and "on" unless the context clearly dictates otherwise. Thus, while the present invention has been described herein with reference to particular embodiments thereof, a latitude of modification, various changes and substitutions are intended in the foregoing disclosures, and it will be appreciated that in some instances some features of embodiments of the invention will be employed without a corresponding use of other features without departing from the scope and spirit of the invention as set forth. Therefore, many modifications may be made to adapt a particular situation or material to the essential scope and spirit of the present invention. It is intended that the invention not be limited to the particular terms used in following claims and/or to the particular embodiment disclosed as the best mode contemplated for carrying out this invention, but that the invention will include any and all embodiments and equivalents falling within the scope of the appended claims. GLOSSARY OF TERMS AND THEIR DEFINITIONS HRPD: High Rate Packet Data network defined as per C.S0024 standard of 3GPP2. 1X: CDMA 2000 network defined as per C.S0002 to C.S0006 standards of 3GPP2. AN: Access Network BSC: Base Station Controller (used in 1x network for Access network) MSC: Mobile Switching Centre AT: Access Terminal, same as the Mobile terminal of CDMA2000. Hybrid AT: An AT that supports both HRPD and 1x. IWS: Inter Working Solution. RAT: Radio Access Technology. Examples: CDMA2000, GSM, UMTS, 4G etc IMSI: International Mobile Subscriber Identity UATI : Unique Access Terminal Identifier SO/MM: Session Control/Mobility Management WE CLAIM 1. A method for maintaining a mapping at network level between different identifiers namely IMS! and UATI for 1x and HRPD networks respectively to attain cross paging at the IWS. 2. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein it relates to inter-RAT handovers in wireless domain and in particular to handoff between HRPD and 1x networks. 3. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein for facilitating handoffs and cross paging, a mapping is provided at the network side between the different identifiers used on the involved networks. 4. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein a new node named IWS Interworking Solution that will be a part of the HRPD RAN is introduced to handle cross interactions between the two kinds of network interfaces for the architecture based on TIA-878. 5. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein the IWS interfaces to the MSC via an lOS A1 interface, and also to the SC/MM via a H1 interface. 6. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein the SC/MM is located in the AN or the PCF in the EVDO RAN. 7. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein the function of the IWS is to translate A1 messages to cdma2000 LAC messages, which are then sent to the SC/MM for transmission to the HAT. 8. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein if the SC/MM is located in the AN, the AN will send the message directly to the HAT using the 3G1x Services Notification Application protocol and if the SC/MM is in the PCF, the SC/MM first send the cdma2000 LAC message to the AN over the A14 interface. 9. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein messages received from the HAT by the AN result in the SC/MM sending update messages to the IWS and the IWS then send an A1 lOS message to the MSC. 10. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein a new interface between the IWS and the SC/MM is introduced which is TCP/IP based, with a lOS layer that carry the encapsulated 3G LAC messages for delivery to the SC/MM and also carry information from the SC/MM to the IWS. 11. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein the said interface connects the IWS to the SC/MM in the HRPD architecture and carhes 3G1X LAC encapsulated PDUs in an lOS-defined protocol. 12.A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI wherein the call flow for TIA-878 architecture includes: (a) registering the AT at the end of UATI assignment procedure with the IWS by the HRPD AN; (b) triggering sending of registration message of 1x with IMSI as identifier by AT; (c) extracting the IMSI from encapsulated registration message; and (d) maintaining the IMSI-UATI mapping by the IWS. 13. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI wherein the mapping for TIA-1878 architecture includes: (a) registering the AT at the end of UATI assignment procedure with the IWS by the PCF; (b) triggering sending of registration message of 1x with IMSI as identifier by the AT; (c) extracting the IMSI from encapsulated registration message; and (d) maintaining the IMSI-UATI mapping by IWS. 14. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein messages on HI interface those are required for attaining the mapping between IMSI and UATI includes IWS RecvFrame, IWSRegistrationInd and IWSRegistrationAck. 15. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein IWS RecvFrame includes fields MSGJD, ATID, ACK_REQUIRED, SEQ_NUM, PDU_LENGTH, RESERVED, 1x LAC PDU. 16. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein MSGJD field in IWS RecvFrame represent the message identifier set to 0x01 by IWS. 17.A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein ATID field in IWS RecvFrame represents the unique identifier to distinguish the message is for which AT. 18. A method for maintaining a mapping at network level between different identifiers namely IMSl and UATI as claimed in claim 1 wherein ACK_REQD field in IWS RecvFrame is set to 1 by IWS if an ack is mandated for 1x packet. 19. A method for maintaining a mapping at network level between different identifiers namely IMSl and UATI as claimed in claim 1 wherein SEQ_NUM field in IWS RecvFrame represent the sequence number for acknowledgement and the field is present if ACK_REQD is set to 1. 20. A method for maintaining a mapping at network level between different identifiers namely IMSl and UATI as claimed in claim 1 wherein PDU_LENGTH field in IWS RecvFrame represent length of 1x LAC PDU. 21. A method for maintaining a mapping at network level between different identifiers namely IMSl and UATI as claimed in claim 1 wherein RESERVED field in IWS RecvFrame is set to 0 to make the message octet aligned. 22. A method for maintaining a mapping at network level between different identifiers namely IMSl and UATI as claimed in claim 1 wherein 1x LAC PDU field in IWS RecvFrame represent the IWS forms and put the 1x LAC PDU of required 1x message like GPM, DBM. 23. A method for maintaining a mapping at network level between different identifiers namely IMSl and UATI as claimed in claim 1 wherein IWSRegistrationInd includes fields MSGJD, ATID, RESERVED. 24. A method for maintaining a mapping at network level between different identifiers namely IMSl and UATI as claimed in claim 1 wherein MSGJD field in IWSRegistrationInd represents the message identifier set to 0x05 by HRPD. 25. A method for maintaining a mapping at network level between different identifiers namely IMSI and DAT! as claimed in claim 1 wherein ATID field in IWSRegistrationInd represents the unique identifier to distinguish the message is for which AT, and the ID can be set to UATI for HRPD system. 26. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein RESERVED field in IWSRegistrationInd is set to 0 and is present to make the message octet aligned. 27. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein IWSRegistrationAck includes fields MSGJD, ATID. 28. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein MSGJD field in IWSRegistrationAck represent the message identifier set to 0x03 by IWS. 29. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein ATID field in IWSRegistrationAck represent the unique identifier to distinguish the message is for which AT and the ID can be set to UATI for HRPD system. 30. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI wherein the call flow for the maintenance of mapping for TIA-878 architecture comprise the steps of: (a) sending a UATI Request message by the AT(A1); (b) generating a UATI and assigns it to AT via UATIAssignment message by HRPD AN (H1); (c) assigning UATI to AT and sending UATlComplete message to HRPD AN (A2); (d) sending IWS Registartion ind message with UATI by HRPD AN (H2); (e) storing the UATI and its context as to which HRPD AN it is connected to by the IWS (11); (f) triggering sending of 1x Registration message on 3G1x notification application by AT (A3); (g) forwarding the 3G1x packet to IWS in IWS recv frame message with UATI by the HRPD AN (H3); and (h) getting the UATI and looks into the 1x message by the IWS (12). 31. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein the mapping is maintained with IMSI as reference and whenever UATI is reassigned, the hybrid AT sends a 1x registration message with IMSI and IWS updates the table. 32. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI the call flow for the maintenance of mapping for TIA-1878 architecture comprises the steps of: (a) sending a UATIRequest message by the AT (A1); (b) generating a UATI and assigns it to AT via UATIAssignment message by HRPD AN and starts T14-UATI-Req timer(HI); (c) generating a UATI and sends it to HRPD AN in A14-UATlAssignment message by PCF (PI); (d) sending the assigned UATI to AT in UATIAssignment message by HRPD AN (H2) and stops T14-UATI-Req timer; (e) assigning UATI to AT and sending UATlComplete message to HRPD AN (A2); (f) sending A14"UATIComplete message to PCF(H3) and Starts T14-UATI-Comp timer; (g) sending A14 UATICompleteAck to HRPD AN and IWS Registartion ind message with UATI to IWS over H1 interface by PCF (P2); (h) stopping T14-UATI-Comp timer(H4); (i) storing the UATI and its context as to which PCF it is connected to by the IWS (11); (j) triggering sending of 1x Registration message on 3G1x notification application by AT (A3); (k) forwarding the 3G1x packet to PCF in A14-IWS recv frame message with UATI by the HRPD AN(H5); (I) forwarding the 3G1x packet to IWS in IWS recv frame message with UATI by PCF (P3);and (m)getting the UATI and looks into the 1x message by IWS (12). 33. A method for maintaining a mapping at network level between different identifiers namely IMSI and UATI as claimed in claim 1 wherein the mapping is maintained with IMSI as reference and whenever UATI is reassigned, the hybrid AT sends a 1x registration message with IMSI and IWS updates the table. 34. A method for maintaining a mapping at network level between different identifiers such as substantially herein described particularly with reference to

Documents:

1238-che-2004-abstract.pdf

1238-che-2004-claims filed.pdf

1238-che-2004-claims grand.pdf

1238-che-2004-correspondnece-others.pdf

1238-che-2004-correspondnece-po.pdf

1238-che-2004-description(complete) filed.pdf

1238-che-2004-description(complete) grand.pdf

1238-che-2004-drawings.pdf

1238-che-2004-form 1.pdf

1238-che-2004-form 19.pdf

1238-che-2004-form 26.pdf