MXPA00011886A - Integrated radio telecommunications network and method of interworking an ansi-41 network and the general packet radio service (gprs) - Google Patents

Abstract

An integrated radio telecommunications network which integrates an ANSI-41 circuit switched network and a General Packet Radio Service (GPRS) packet data network to support a mobile station which operates in both the ANSI-41 network and the GPRS network. An interworking function (37) interfaces a mobile switching center (MSC) (23) in the ANSI-41 network with a serving GPRS switching node (SGSN) (32) in the GPRS network by mapping circuit switched signaling utilized by the MSC into GPRS packet switched signaling utilized by the SGSN, and mapping GPRS packet switched signaling into circuit switched signaling. An interworking GPRS base station controller (39) interfaces the SGSN with a GPRS/ANSI-136 base station (26) which supports both ANSI-136 operations and GPRS operations. The interworking GPRS base station controller adapts the traffic signaling format utilized by the SGSN into an air interface traffic signaling format utilized by the GPRS/ANSI-136 base station. An authentication center interface (F1) passes the authentication state of the mobile station between an ANSI-41 home location register/authentication center (HLR/AC) (21) in the ANSI-41 network, and a GPRS home location register/authentication center (HLR/AUC) (31) in the GPRS network.

Description

INTEGRATED RADIOTELECOMMUNICATION NETWORK AND METHOD OF INTERCONNECTION OF AN ANSI-41 NETWORK AND THE GENERAL PACKET RADIO SERVICE (GPRS) RELATED REQUESTS AND PRIORITY DECLARATION This non-provisional application, which discloses subject material related to the material subject of the United States patent application number 09 / 217,385 filed on December 21, 1998, claims priority based on the following co-pending applications from the United States: (i) "Radio Telecommunications Network Integrating the General Packet Radio Service (GPRS) and Digital Advanced Mobile Phone System (D) -AMPS) (Radiotelecomunicaciones Network that Integrates the General Packet Radio Service and the Advanced Mobile Telephony System), Serial Number 60 / 090,810, presented on June 26, 1998 in the name of Francis Lupien, Paul Lee, John Diachina , Gunnar Rydnell and Gunnar Thrysin, and (ii) "Merged Radio Telecommunications Network Interworking ANSI-41 and the General Packet Radio Service (GPRS)" (Radiotelecommunications Network Interconnection Unit ANSI-41 and the General Package Radio Service "Serial No. 60 / 087,516, filed June 1, 1998 in the name of Francis Lupien and Paul Lee. BACKGROUND OF THE INVENTION Technical Field of the Invention This invention relates to a telecommunications system and, more particularly, to an integrated radio telecommunications network which interconnects switched circuit services and packet switched services, and an interconnection method of an ANSI. -41 radio-telecommunications network and the General Radio Packet Service (GPRS) of the data packet network. Description of the Related Art Two approaches to data switching are circuit switching and packet switching. The old telephone service (POTS) and cellular voice services, for example, use circuit switching. Switching tracks of fixed circuits are established between parties involved in a call exchanging messages which contain the addresses of the parties and request the establishment of a physical switching track. The signaling messages are exchanged between the addresses and the switching centers, and between the switching centers. The switches respond to the requests in the signaling messages by establishing the physical switching track between the addresses. A data switch can be similarly set to provide a circuit of switched data services. Packet switching, on the other hand, uses data packets which are comparatively short blocks of message data. The packets can be of fixed length as in the asynchronous transfer mode (ATM), or they can be of variable length as in the sending of frames or in the Internet protocol (IP). Full data messages are divided into short packets, each with a header. These packages can be sent on different routes to their eventual destination. Because packets often travel on different routes, they may not reach the remote receiving node in sequential order. Therefore, the remote mode must have the ability to store incoming packets and arrange them in sequential order. The destination node reformats the message as sent by the author and sends it to its final destination. Packet switching can be considered more efficient when compared to circuit switching due to the multiplexing effects which make better use of the available transport bandwidth. Each service or user uses only the bandwidth it needs, leaving the bandwidth not used for other services or users. A plurality of tracks exists from the originating node to the destination node for the operation of the service since an alternate route may be used in the case of failure or congestion of a given route. GPRS is a data packet transmission service 5 which is designed to work with the Global Mobile Communications System (GSM) to allow mobile stations (MSs) that can access both switched or switched circuit data packet network services voice. A standard GPRS data pack • 10 proposed defines MS service classes and infrastructures to allow MSs to use the GPRS network. However, the GPRS standard assigns interconnection requirements for GSM, but does not deal with interconnection requirements for networks of radiotelecommunications based on ANSI / TIA standards such as those used in most of North America. The network architecture and the interface between • specific nodes of data packets and specific circuit switched nodes is designed to GSM. GPRS does not fit within the ANSI-41 network. A system and a method to interconnect GPRS and ANSI-41 networks is required in order for all GPRS functionality (example, services, interface protocols, node functionality, etc.) can be supported from the perspective of radio access logic, network logic and service logic in ANSI-41 networks. Nowadays, the ANSI-41 and ANSI-136 networks only provide voice or circuit switched services. Therefore, an operator can not benefit from the advantages and flexibility provided by packet switching when the operator is providing Internet access to subscribers using cellular networks based on ANSI-41/136. A dial-up access connection or an analogue modem connection must be made to the Internet. For a direct dial access connection, for example, a circuit switched connection is provided between an MS and the Internet access gateway. A call is established to the gateway, and then a Transmission Control Protocol / Internet Protocol (TCP / IP) session is established to an Internet provider is established on that connection. This solution does not provide the benefits of multiplexing over the air interface and through circuit switched facilities since dedicated resources are used for the duration of the Internet connection. This is very inefficient since, in a typical Internet connection, data packets are not sent continuously in the connection. Therefore, a voice channel on the air interface is occupied for the duration of the Internet connection, and the associated switched resources in the network are not optimally used. The existing solution is also not very flexible in terms of data packet network access because only one connection can be established at a time. It is not possible to make multi-part connections for data calls in such a way that last-party voice connections are made. Therefore, the simultaneous switching of services • 10 voice and data can not be provided while connected through a circuit switched connection to the Internet. If a voice call is directed to a mobile station during an Internet session, the subscriber can not take the call and then continue with the Internet connection without interruption. The voice call should be rejected, directed to voice mail or directed to another number.

• Additionally, the user can not originate voice calls during the data call because the call data is switched in circuit between the mobile station and the Internet access input. In order to avoid the disadvantages in the existing solutions, it would be advantageous to have a method to integrate infrastructures and switched services of GPRS package with infrastructure and services of ANSI-41 switched circuits, thereby enabling services similar to those available in GSM. The present invention provides said method and network • integrated. 5 COMPENDIUM OF THE INVENTION In one aspect, the present invention is a radio telecommunications network which integrates an ANSI-41 integrated circuit network and a General Radio Packet Service (GPRS) radio packet network. Network • 10 integrated radio telecommunications includes a mobile switching center (MSC) in the ANSI-41 network that provides circuit switched services to a mobile station which operates both the ANSI-41 network and the GPRS network, and a switching node that serves GPRS (SGSN) in the GPRS network that provides packet switched services to the mobile station. An interconnection function interconnects the MSC with the SGSN, and transforms the integrated circuit signaling used by the MSC into GPRS signaling packets. packet switching used by the SGSN, and transforms the packet switching signaling GPRS into circuit switched signaling. A GPRS base station controller interconnects the SGSN with a GPRS / ANSI-136 base station which supports both ANSI-136 operations and GPRS operations. The GPRS base station controller adapts a signaling format used by the SGSN in an air interface signaling format and passes traffic signaling between the SGSN and the GPRS / ANSI-136 base station. The network also includes means to transparently transfer ANSI-136 information between the mobile station and the ANSI-41 network by adding the ANSI-136 information to selected GPRS messages. The ANSI-136 information that is added to the selected GPRS messages may include registration and authentication information such as the Mobile Identification Number (MIN), an Electronic Serial Number (ESN) and an ANSI-41 Authentication Response (AUTHR). . The selected GPRS messages to which the ANSI-136 information is aggregated include a Request Set message which is sent from the mobile station to the SGSN during a GPRS Set procedure, and a Request to Update Location which is sent from the SGSN to the interconnection function that connects the MSC with the SGSN. In another aspect, the present invention is an integrated radio telecommunications network which integrates an ANSI-41 switched circuit network and a GPRS data packet network including a class D mobile station which only operates on 30 kHz channels in both the ANSI-41 network and the GPRS network. An MSC and ANSI-41 network provides circuit-switched services to the mobile station, and a GPRS switching node of • Service (SGSN) in the GPRS network provides packet switched services to the mobile station. An interconnection function interconnects the MSC with the SGSN, and transforms circuit signaling used by MSC in GPRS packet signaling used by SGSN, and transforms packet signaling • W 10 switched in circuit switched signaling. A GPRS base station controller interconnects SGSN with a GPRS / ANSI-136 base station which supports both ANSI-136 operations and GPRS operations. The interconnected GPRS base station controller is adapts to the signaling format used by SGSN to an air interface signaling format and passes traffic signaling between SGSN and the GPRS / ANSI-136 base station. The mobile station of class D is equipped with a International Mobile Station Identification (IMSI) which is used in the GPRS network. The interconnection function includes means for translating the International Mobile Station Identification (IMSI) of the mobile station used in the ANSI-41 network into an IMSI used in the GPRS network. An integrated telecommunication network can also include a GPRS Home Location Register (GPRS HLR) in the GPRS network which authenticates the mobile D class station for the purpose of data packets, and a center / home location register ANSI-41 (HLR / AC) in the ANSI-41 network which authenticates the class D mobile station for circuit switched purposes. The integrated network may also include a class E mobile station which operates only on 30 kHz channels in the GPRS network. The class E mobile station is in a packet control channel (PCCH) as its normal mode of operation and it is only changed to a digital control channel (DCCH) at power up to verify service availability of data packets. The mobile station of class E is equipped with IMSI and the GPRS HLR includes means for authenticating the mobile station of class E. BRIEF DESCRIPTION OF THE DRAWINGS The present invention will be better understood and its numerous objectives and advantages will be more apparent to those with skill in the art with reference to the following drawings in conjunction with the accompanying specifications, in which: FIGURE 1 is an illustrative drawing of a radio network showing the relationship between various areas of the GPRS network and the areas of an ANSI-41 network. FIGURE 2 is a simplified block diagram of an integrated GPRS / ANSI-41 network according to a first embodiment of the present invention. FIGURE 3 is a simplified block diagram of an integrated GPRS / ANSI-41 network according to a second embodiment of the present invention. FIGURE 4 is a simplified block diagram of an integrated GPRS / ANSI-41 network according to a third • Embodiment of the present invention. FIGURE 5 is a simplified block diagram of an integrated GPRS / ANSI-41 network according to a fourth embodiment of the present invention. FIGURE 6 is a message flow diagram 15 illustrating the flow of signaling messages between nodes of the integrated network of FIGURE 5 when the GPRS aggregation procedure is carried out. • FIGURE 7 is a message flowchart illustrating the flow of signaling messages during an Intra-SGSN Area Update process.

Routes . FIGURE 8 is a message flow diagram illustrating the flow of signaling messages during an Inter-SGSN 25-Area Area Update procedure.

FIGURE 9 is a message flow diagram illustrating the flow of signaling messages during a Cell Update procedure when an M-ES in the READY state enters a new cell in the current Route Area 5. FIGURE 10 is a message flow diagram illustrating the flow of signaling messages between the nodes of the integrated network of FIGURE 5 when an incoming voice call is received for an M-ES in the • 10 STANDBY state. FIGURE 11 is a message flow diagram illustrating the flow of signaling messages between the integrated network of FIGURE 5 when a Short Message Service Message (SMS) is received for an M-ES Class D in the STANDBY state. FIGURE 12 is a message flowchart illustrating the flow of signaling messages between • nodes in the integrated network of FIGURE 5 when an M-ES initiates a Detach procedure; and FIGURE 13 is a message flow diagram illustrating the flow of signaling messages when a Class D M-ES in the CONVERSATION state initiates a call disconnection while on a Digital Traffic Channel. 25 DETAILED DESCRIPTION OF INCORPORATIONS As indicated above, GPRS is a data packet transmission service which is designed to work with a GSM system to allow a mobile station to access both switched voice / circuit network services and data packet network services. The present invention defines the interface requirements for using GPRS with ANSI-41 / ANSI-136 networks. The "interface does not involve a direct reuse of the GSM interface because the GPRS service reuses part of the GSM network functions, which is why the interface is different and more complicated with ANSI-41 networks. signage involved in authentication and location updates When an interface between GPRS and ANSI-41 networks is defined, alternative approaches are possible since the GPRS service reuses part of the functions of the GSM network In a first approach, some of the GSM network functions are migrated to the ANSI-41 network, for example, for authentication services, the functionality of the GSM authentication center can be implemented in the ANSI-41 network, in this way, the GPRS nodes and the functionality of the network, to a large extent, are left intact, but the ANSI-41 nodes and functionality are greatly impacted.Alternatively, the GPRS infrastructure can be modified to remove the logical to GSM of the GPRS nodes and network functionality, and implement the ANSI-41 logic in them. For example, the ANSI-41 functionality can be modified to not reuse the GSM authentication center to provide authentication services, instead it uses the ANSI-41 authentication center to provide the services to the GPRS network. The preferred embodiment keeps the integration amount as low as possible while maintaining the integrity of each network and node function both on the GPRS side of the interface and on the ANSI-41 side. The problem with attempting more extensive integration is that the two systems originate from two different standards, and have two different evolutionary paths. Thus, it is advantageous to limit the amount of GSM functionality that is integrated into the ANSI-41 infrastructure since future GSM / GPRS developments may cause greater integration problems in ANSI-41 networks. Additionally, decoupling networks to a greater degree is the most efficient way to provide independent clues for the evolution of the system. This allows the "future development of both networks." The radio air interface in the integrated ANSI-41 / GPRS system is based on ANSI-136, which is obviously different from the GSM / GPRS air interface. the interfaces between the critical nodes in the GPRS architecture in the ANSI-41 nodes, this is also done to provide data packet integration and voice service in an efficient manner I. Description ANSI-41/136 A. Handling Radio Resources It is useful to define some terms used in the following description of the radio network configuration (corresponding to the RR sub-layer) An area to be served MSC is a group of cells with associated carriers and channel functions controlled by an MSC A switched voice / circuit service area is a subset of an MSC service area An ANSI-136 MSC service area or exchange area is constructed of a number of cells, each cell supporting a number of channel functions. The characteristics of the voice / circuit switched service area within the ANSI-136 service area are as follows: 1. The MSC service area can be divided into a number of location areas (Las). Each location area is formed of a number of cells, and is associated with a voice / circuit switched service area. 2. Both the location areas and the MSC service areas are viewed by the mobile station as recording areas, and are used in the location tracking mechanism. 3. The MSC service area can also be divided into a number of search areas (PA), formed from a number of location areas. Typically an LA has an associated PA, a PA is associated with voice / circuit switched service areas. 4. Both the LA and the PA can be used to track the mobile station. 5. The MSC has a neighboring MSC, and the service area of the neighboring MSC can be expressed by defining a satellite tracking area (SPA). A SPA is associated with a voice / circuit switched service area. A SPA in a neighboring MSC is tied to a PA in the MSC. B. Mobility Management (MM) 1. Location Tracking in an MSC Service Area From the point of view of a cellular network, mobility management has a set of rules based on a hierarchical node model. The rules are designed to limit network interaction in order to minimize ambiguity in the true location of the mobile station. An HLR monitors the mobility of the mobile station between VLRs, and a central VLR monitors the mobility of the mobile station between one or more service MSC / VLRs. Therefore, all the rules for executing cellular services and other functions (example, authentication) are based on the established MM network concept. The location of the mobile station within the service system service area is tracked forcing the mobile station to report its location. The mobile station reports its location through a "geographic" registration mechanism when it crosses predefined geographic areas. Typically, said geographic areas are "formed from and identified by the mobile station through LOCAREA transmissions and SID system identification parameters." In the present invention, the LA is tracked in the VLR in mobile station registry accesses. regardless of the type of record (this being independent of the event that triggered the record access.) This process ensures that the most current LA is used for tracking.LA is used in the first attempt to trace to a mobile station. The LA can also point to a PA. The PA and the entire service area can be used - potentially in the tracking of a mobile station in subsequent attempts when a response to a first (or second) attempt at tracking is not received. The activity of a mobile station is tracked by forcing the mobile station to register at power on, at power down and at a constant interval while it is active through a periodic logging mechanism. 2. Tracking Location Along Service Areas MSC The location of a mobile station along a service area (VLR id, MSC id, etc.) is tracked forcing the mobile station to register. The SID typically identifies the system operator and therefore marks the limit of the service area. The MSC limits within the same SID area are identified as different because it is essential that the mobile station reports its location when it crosses the boundaries of the service area. A first registration access in a service area causes the following: a. The MSC serving the system in the VEL functions determines that "the mobile station is not active and is not authenticated." An authentication transaction to the CA is thrown in. From the perspective of the IS-41 network, there is a difference between the validation of subscribers and subscriber authentication b.To successful mobile station authentication, the location of the mobile station (LA, MSC id, VLR id) is updated in the system database served in the local system database through transaction procedures towards the VLR and HLR • If the mobile station was active in another service area before the first access, the previous service area VLR or MSC may be called by AC to obtain the "account" "of the authentication call history." The HLR requests the previous service system to remove the mobile station from the active list by launching • 10 a record cancellation transaction. C. Network Security and Authentication Procedures ANSI-41 The security process in an ANSI-41 network is based on algorithm-only interactions (CAVE) to generate and update Shared Secret Data (SSD) (authentication and encryption keys), for access authentication. The security process also involves validation of network parameters such as an "account". The SSD generation process involves: res interactions: SSD, AUTHU (for single challenge) and AÜTHBS (for BS challenge). Subsequently, each mobile station access requires an interaction to generate an Authentication Response (AUTHR) ANSI-41. The SSD generation is triggered by the AC, and is based on Key A and random number generation.

A random number is common between the AC and the mobile station (RANSSD) and is generated by the AC at the time of SSD generation. The random number is used to challenge • Unique (RANDU) can be generated in the AC or in the 5 MSV / VRL when the SSD is shared. In the latter case, AUTHU and AUTHBS calculations are also local to the MSC / VLR. The generation of AUTHR is based on SSD, RAND and marked digits, etc. It is assumed that RAND is locally generated at the MSC level, and transmitted on the train of • 10 higher messages (OMT) or Transmission Control Channel (BCCH). When SSD is not shared, authentication occurs in the AC and in the mobile station in AUTHR and RAND sent to AC. When the SSD is shared, the AUTHR calculation and validation are carried out in the MSC / VLR. II. Description GPRS In the description that follows, the term "simultaneous" expresses the requirement to simultaneously support GPRS packet switched services, switched circuit and Short Message Service (SMS). ' The range of MS services considered "standard" GPRS functions works as follows: • Simultaneous initial registration (Identification of International Fixing Mobile Station (IMIS) and GPRS setting), simultaneous activation (data packet services and circuit switched services). • Simultaneous monitoring (switched packet services and circuit switched in a single control channel). • Simultaneous invocation of 5 circuit switched calls and packet channel transactions. Some subscribers may have limited simultaneous invocation (in standby type approach it is used for one of the invocations). • Simultaneous traffic (on equal frequencies or • 10 different). Some subscribers do not have this capacity (this being, without simultaneous traffic); Y • Some subscribers can only use switched circuit services and packet switched services alternately, when both services are supported. The GPRS standard specifies the GPRS central functions as independent functional entities for services • existing circuit-switched GPS, while allowing data packet transactions during services circuit switched. The intent of the specification is to introduce GPRS functions that are not included or to invoke GSM central switched circuit service functions in order to deliver switched packet services. 25 Mobile station class of service requirements must be supported through the integration of GPRS into the ANSI-41 reference network. The integration must involve radio access logic, network logic and service logic. This implies impact on the infrastructure, node functionality and interface protocols for (1) radio access and resource management, (2) data track connections with enhanced GPRS ANSI-136 access functions, and (3) management of service control and mobility management with ANSI-41 nodes and node functionality through signaling protocol interfaces. From the radio frequency physical link perspective, the radio resource management sub-layer, the management functionality of radio and ANSI-136 specific radio frequencies can be integrated into the GPRS architecture. From the perspective of a network and service logic, the impact on the ANSI-41 architecture in terms of functions, interfaces / messages and means of transport vary depending on the degree of integration that is attempted. The logical GPRS functional architecture is based on the same functional layer principles found in the GSM functional architecture. The most important functional plane defines the functions of layer 3, or as they are known in the GPRS standard, the sub-layers of layer 3 and their associated entities. There are four sub-layers in the GPRS protocol architecture: Radio Resource Management (RR), Logical Link Control (LLC), Mobility Management (MM) and Connection Management (CM). The sub-layers of layer 3 are functionally orthogonal for GPRS services and for non-GPRS services. The important sub-layer entities are briefly described below. Typically, each sub-layer entity is defined by a single protocol between related protocol entities in the mobile station and in the network. A. Sub-layer RR The RR sub-layer is composed of the following functional blocks: 1. Dedicated node node RR for non-GPRS services; and 2. Shared Mode GPRS RR (Radio Link Control / Media Access Control (RLC / MAC)) for GPRS services. A data packet area is a group of cells in which the data packet functions are controlled by an SGSN. Typically, this is a subset of an area MSC service. The Switching Node service area serving GPRS is a data packet service area, and may consist of an overlay of one or more MSC service areas. The SGSN service area may also be an overlay of a subset of the MSC service area. The cells in the SGSN service area have support for a channel • GPRS data packet (channel functions (PCCH) .The 5 characteristics of an SGSN data packet service area within the ANSI-136 MSC service area are the following: • An SGSN service area is constructed of a number of route areas (RA) .A RA is an area of data packet service and is identified by an RA key (RAC). • The RAs consist of a number of cells that support GPRS PCCH channel functions. • A GPRS RAC is tied to a location area of 15 voice / circuit switched services (LAI = LA Id.) In unique relation: RAÍ = RAC + LAI, (RAI = RA Id). LAI represents an overlay in the voice / circuit switched service area and the data packet service area; and 20 • The RAs are sized to fit an area less than or equal to a GSM LA to better control the call load due to incoming GPRS traffic.

B. LLC sub-layer The LLC sub-layer includes a number of functional blocks which can handle Quality of Service (QoA) and signaling traffic. The LLC sub-layer is responsible for transporting higher layer information between the GPRS Service Node (SGSN) and the mobile station. • C. Sub-layer MM 5 The MM sub-layer includes the following blocks: • Mobility of non-GPRS services (MM entity). • GPRS Mobility (GMM entity), and • Anonymous access GMM (GMM-AA entity) GMM and GMM-AA are implemented with similar in SGSN, and • 10 the mobile station only. MM is implemented with similar in the mobile station MSC / VLR. Common GMM procedures include Temporary Layer Link Identifier Assignment (TLLI), assignment, (P-TMSI) of Mobile Station Identification 15 of Temporary Packet, encryption and GPRS Authentication, GPRS Identification and GPRS Information that are initiated by the network. once the PDP context is established. The GMM procedures include: • A procedure initiated by the network or by the mobile station and used to detach the IMSI in the network for GPRS services and / or non-PGRS services and release a GMM context: drop GPRS. • A procedure initiated by the mobile station and used to attach or detach the IMSI in the network for GPRS services and / or for non-GPRS services and to establish or release the GMM context: Fix GPRS, Fix Combined, GPRS release and GPRS merge. • A procedure initiated by the mobile station once the GMM context has been established, and used to maintain the mobility context (states, location, etc.) synchronously in the mobile station and the network: RA updates, combined updates RA and Periodic updates RA. 1. Location Tracking Within and Through GPRS Service Areas Depending on the class of mobile station, a mobile station may adhere to either IMSI circuit switched services, GPRS packet switched services or both types of service as an IMSI / GPRS. The adhesion procedure can be compared to an ignition record. The separation procedure can be compared to either a shutdown or a registration termination procedure. While traveling within data packet service areas, GPRS subscribers with class A or B mobile station may be attached to the GPRS network and / or the circuit switched network. Subscribers with a class C mobile station may be attached to the GPRS network only. From the perspective of the GPRS network, the trace is made if the mobile station has a terminal operating in Class A / B or Class C. For Class A / B, location updates may be RA / LA update procedures combined or independent RA and LA update procedures, while in Class C, RA location updates are carried out. The combined RA / LA updates allow simultaneous updates of the location of the mobile station for both switched voice / circuit service areas and data packet service areas. The present invention introduces a new Class D and a new Class E mobile station which are described below in relation to the CM sub-layer. 2. Tracking of Route Area and Location Area The identification of Ruto Area parameters (RAI) and Location Area Identification (LAI) are transmitted in the GPRS control channel. This allows the mobile station to track MSC (VLR and RA while in standby or GPRS ready mode.) Therefore, two independent network processes are involved: • The mobile station detects a new Route (RA) area within the area of current location (this being a new RAC within LAI with no change.) This triggers an RA update.

• The mobile station detects a new Location (LA) area (this being the LAI is different). This triggers a combined RA / LA update since the • associated MSC service area may be different, and a new association between SGSN and MSC / VLR must be carried out. 3. Circuit Service Connection Support Switched on GPRS Nodes In order to support circuit switched services on the GPRS network, the following functions are implemented in • SGSN, and some adaptation is carried out in the functions of mobility management and call control in GSM MSC / VLR. • Adhering / releasing IMSI to the MSC / VLR, and indicating 15 adhere / release GPRS. • LA updates to the MSC / VLR (including periodic updates). B • Tracing order for the service SGSN for circuit switched connection; and 20 • Alert procedures for non-GPRS services. 4. Network Security Functions Based on existing procedures / algorithms, GPRS nodes should use identity confidentiality (for example: based on Layer Link Identifier) Temporary (TLLI)), authentication procedures for validation to the mobile station and encryption keys for encrypting LLC PDUs. A triple vector must be available to the SGSN together with the encryption algorithm and the encryption key sequence number. Subscriber identity confidentiality can be maintained using the Temporary Mobile Station Identifier (TMSI). The TMSI addressing function requires network assignment of a temporary identity for the moving mobile station. In the GPRS scope, the MSC / VLR can return a TMSI to the SGSN after successfully updating the LA (for MS using TMSI in the SGSM-MS interface). Therefore, as long as the TMSI addressing in the SGSN is optional, a TMSI does not have to be assigned. Otherwise the SGSN must be updated to optionally remove the TMSI. As stated above, subscriber identity confidentiality can also be maintained using the Temporary Layer Link Identifier (TLLI). The TLLI addressing in the LLC protocol requires network assignment as a temporary identity, and is local to the GPRS nodes. TLLIs are assigned in RA updates. In GPRS, the subscriber identity confidentiality and the TMSI transfer to the mobile station is carried out in encrypted mode in the acknowledgment of the location update to the mobile station. Subscriber identity and encryption authentication requirements include the following: • MS id key (Ki) and key generation algorithms (A3, A8) in the AUC and in the mobile station. • Generation of Security Related Information such as encryption key (Kc), security result (SRES) «and random number vectors (RAND). The vectors are distributed to the SGSN (and GSM MSC / VLR). Only the RAND is transferred to the mobile station for its internal generation of Kc and SRES to the authentication request of the network; and • Typical in GSM, DCCH and TCH are encrypted with the encryption key Kc applied with the encryption / decryption algorithm A5 at BSS level. Therefore, the sequence of events in the GSM / GPRS network related to security functions are as follows: a. In the first access, or in adhering IMSI / GPRS, the triple vector (RAND, SRES, Kc) is generated by the AUC. SRES and Kc are generated using RAND and Ki (key A equivalent). The triple vector is transferred from AUC to MSC / VLR or SGSN. Note that an interaction is carried out from two algorithms in parallel, and no algorithm is computed is required in SGSN or MSC / VLR. b.The MSC / VLR or SGSN has control over which the RAND in the vector is going to be used for a given authentication cycle. The RAND is sent to the station • mobile (in air) when authentication 5 is requested by the MSC / VLR or SGSN through an explicit "authentication request" to the mobile station. An authentication request message follows any location update message from the mobile station (in the location or area system of • 10 registration). c. The mobile station uses RAND and ANSI to generate SRES, which is sent to BSS / MSC / VLR or SGSN in an "authentication response" message. d. The mobile station internally generates the Kc using 15 RAND and Ki. A new Ki is used to encrypt onwards in order of MSC / VLR or SGSN. This happens at each location update. • e. When the mobile station performs a "location update" accesses a new area 20 MSC / VLR, the new VLR brings the vectors from the previous VLR. Once all the keys have been used in the vector, the MSC / VLR or SGSN requests a new set of HLR / AUC. 25 Note also that in the GSM architecture, the layer 3 messages (control plane) are together (this being, mobile station to MSC / VLR). The BSS acts only as transport, except for the encryption air interface # where it is directly involved in the application of the 5 A5 algorithm. there is no RAND transmission, etc. 5. Authentication synchronization between SGSN and MSC / VLR While the mobile station is controlled by the GPRS network nodes, the MSC / VLR does not authenticate the mobile station by means of SGSN upon adhesion or updates of location. The SGSN and MSC / VLR can handle the process • security independently. The MSC / VLR may vary its authentication procedure in connection with circuit switched connection services. The mobile station can use IMSI for calls relative accesses if TMSI has not been assigned before. Note that all call accesses received in the GPRS control channel are sent to MSC / VLR (not SGSN). A new RAND is used to authenticate (generate SRES) to encrypt (generate Kc). No need to coordinate the selection of RAND between MSC / VLR and SGSN. The SGSN and MSC / VLR can use the triple vector independently. D. Sub-layer CM The CM sub-layer includes functional blocks for GPRS services and functional blocks that support GPRS short message service control (GSMS). The functional blocks for GPRS services are implemented in SGSN and mobile station only, and include Session Management (SM) functions. The main role of the SM function is to support the mobile station PDP context handling. The SM functions include procedures for identifying PDP context activation, deactivation and modification as well as activation and deactivation of anonymous PDP context. The SM procedures for identified access can only be carried out if a GMM context has been established between the mobile station and the network. If the GMM context has not been established, the MM sub-layer must initiate the establishment of a GMM context for use of the GMM procedures. After establishing the GMM context, the SM functions use services which are offered by GMM (see GSM 04.07). The SM procedures are suspended during the execution of the GMM procedure. For non-GPRS services, the CM sub-layer includes functions such as Call Control (CC) entity, Support for SMS entity, Supplementary Services entity (SS), Group Call Control entity and Call Transmission Control. These functions are implemented in the GPRS network core nodes only. For inter-operation processes, a small set of layer 3 GPRS functions were horizontally integrated with the GSM core functions. (Note: the network core functions refer to GPRS functions with the exception of those in BSS, mobile terminal (MT) and terminal equipment (TE), folng the layer approach, the set of layer 3 GPRS functions include the folng functions: 1. In the MM sub-layer The concepts of the GSM network core were reused • 10 as specific GPRS instances and introduced in the GPRS network core model. These are: • The specific GPRS address location register (GPRS HLR) for profile and management of location update in the GPRS network core; and • The reuse of the authentication algorithm of the GSM authentication center (AUC) for generation • of a triple vector. The functions above are supported through the specific GPRS interface (Gr), modeled on the "D" interface between the GPRS HLR and the SGSN. • Mobility between GSM and GPRS network cores. To support concurrent or simultaneous access to GSM and GPRS services, mobility functions between GSM and GPRS networks are integrated in the VLR level. The SGSN is seen as an access node from the perspective of a GSM service node. The functional relationship between GSM MSC / VLR and the SGSN is comparable • to the sub-set of an "A" interface (this being the Gs interface), and is of lesser scope than interface A. • MS mobility between the radio access network and the GPRS network core. For mobility management purposes, the relationship between BSS and SGSN is similar to # 10 that of BSS and MSC / VLR. The "mobility context" is maintained through MM signaling between the GPRS core network and BSS, and involves the uplink transfer of location information (cell identity and radio status) and orders search on the downlink. The MM signaling is carried through the Gb interface instead of the A interface. The Gb interface also multiplexes virtual circuits for MS user data and MS user signaling for management of GPRS mobility and SMS messages. 2. In the Sub-layer in RR The GPRS core network assumes that the radio bearer services packets. { GPRS - specific RR layer functions) are available from a radio access node BSS. He Handling and traffic management of both dedicated circuit switched mode and packet switched radio mode bearers are integrated in BSS. The shared RR mode is integrated with the RR dedicated mode in BSC. This includes the management and handling of traffic components. At the base station receiver transmitter (BTS) level, the GPRS radio channel structure is added to the existing GSM circuit switched channel definition. Noting that the HLR and BSS can be GPRS specific, the GPRS infrastructure can be deployed separately from the GSM circuit infrastructure. III. GPRS / ANSI-41 integration The problem in defining the interface between the GPRS service and the ANSI-41 network is to reconcile the GPRS RR, MM, SM and SMS sub-layer entities with the ANSI-136 counterparts and integrate the two systems. There are alternative approaches to this integration process. First, the integration can be carried out through selective horizontal integration of MM and security. This approach preserves the functional integrity of the GPRS / GSM core network and the ANSI-41 core network allowing them to coexist while maintaining the orthogonality of the GPRS / GSM and ANSI-41 switched circuit networks with the VLR level interconnection for the purposes of mobility management. A second approach is the full vertical integration of MM and security. This can be done in two ways, either by adapting GPRS nodes to operate with the mobility management procedures and • ANS-41 authentication or implementing GSM 5 requirements for handling authentication and mobility, etc., as part of the ANSI-41 core network (functions and messages). If the GPRS nodes are adapted to operate with ANSI-41 procedures, the ANSI-41 authentication center algorithms and keys are reused and • 10 implemented in the nodes and mobile terminals GPRS. In the present invention, selective horizontal integration is carried out. The separation and independence between functional sub-layer entities of GPRS and GSM core service provides the basis for defining the GPRS and ANSI-41 / ANSI-136 integration. This independence allows selective horizontal integration, thereby preserving the integrity of each architecture. This approach is flexible since it selects sub-layer parts that can be integrated. This approach is also more simple because the required changes are focused on only a part of the architecture. The approach is also more efficient than the alternatives because it allows services of both architectures to be provided with a low complexity solution. 25 Therefore, when a number of simple requirements in network coexistence and interconnection are satisfied, it is possible to push the existing ANSI-136/41 and GPRS standards to an extensive field and minimize the development of infrastructure standards coinciding with systems impact. respective. The GSM-GPRS architecture described above is adapted to replace GSM core functions with circuit service infrastructure infrastructures based on ANSI-41 and ANSI-136. More specifically, the GSM core network logical nodes (MSC / VLR, HLR, AUC, EIR, SM-SC) are replaced with logical core network nodes ANSI-41 (HLR / AC, MSC / VLR, MC / OTAF ). In addition, the functions associated with the dedicated GSM RR mode (radio resource management) for circuit switched services are replaced by ANSI-136 base circuit access bearers and radio network concepts. To obtain these requirements and coexistence, the present invention defines a new sub-layer ANSI-136 RR which includes a new access control means ANSI-136 (MAC) that provides services to layers superior to the sub-layer GPRS LLC. The circuit switched network core functions consist of ANSI-41/136 core network infrastructure with ANSI-41 MSC / CLR, MC and HLR / SCP / AC. The present invention also allows an ANSI-136 user to signal information flowing from the mobile station to the ANSI-136 infrastructure through the GPRS service node. The ANSI-136 information can be transparently transferred between the mobile station and the ANSI-136 infrastructures based on ANSI-136 transported information in GPRS messages. This is known as ANSI-136 information tunnel. The ANSI-41 authentication-registration information (MIN, ESN, Authentication Response (AUTHR), etc.) is carried through the GPRS infrastructure to the ANSI-41 infrastructure during the GPRS accession procedure. This procedure is illustrated in more detail in FIGURE 6. With the GPRS network layer with ANSI-136 base (the LLC sub-layer and function layers) in place, one is free to move to channels (EDGE) GSM Evolution of Enhanced Data ratios for data packet services at any point without having to change the network signaling (LLC sub-layer and above) again. The required network layer signaling changes required for data packet services on 30 kHz channels are fully applicable and / or sufficient for EDGE channels. This approach therefore provides a smooth migration path to EDGE channels since the LLC and higher layers can be reused from ANSI-136 since they are independent of the RR sub-layers (RLC, MAC) and are physical layers for channels. 30 kHz and EDGE channels. A. In the CM Sub-layer In the SM sub-layer, the present invention introduces a new class of mobile station, Class D, with the ability to concurrently access GPRS data packet service and ANSI-136 switched circuit services. The mobile station of class D is similar to the mobile station of class B GPRS, but is only capable of operating on 30 kHz channels and is attached to the ANSI-41 infrastructure instead of the GSM infrastructure for circuit switched services. The class D mobile station has the ability to access GPRS and ANS-136 and associated services while it is connected through the GPRS radio packet access network (camping in PCCH). This type of mobile station has associated call control, service interaction management and teleservice management carried out within the ANSI-41 infrastructures. The service notification transfer between the mobile station and ANSI-41 MSC / VLR is subject to the mobility management clause of the MM sublayer. Class D mobile station camping in the packet control channel as its normal mode of operation, and only go to DCCH in three cases, (1) at power-up to verify the availability of the data packet service and the presence of a Beacon PCCH, (2) the establishment of a voice call, and (3) at release GPRS. The present invention also introduces a new Class E mobile station 5 which is only capable of GPRS data packet service. The mobile station of class E is similar to the mobile station GPRS Class C, but is only capable of operating on 30kHz channels. The class E mobile station has the ability to acquire • 10 ANSI-136 associated services while connected through circuit switched radio access network (camping in DCCH) only. The Class E mobile station camps in the packet control channel as its normal mode of operation, and only passes to DCCH in the ignition to verify the availability of data packet services and the presence of Beacon PCCH. Both Class D and Class E mobile station • they have PDP context associated procedures, and they are supported through functions (SM) of Management of Existing sessions. Calls terminated at the mobile station originate within the ANSI-41 infrastructure and are completed by means of the ANSI-41 Unsolicited Response message (UNSOLRES). 25 The Class D and Class E mobile station is equipped with an IMSI that is used only within the context of the GPRS infrastructure. The INSI can be provided by an SM card as described in the GPRS standards, and therefore does not require support through the ANSI-136 OTA procedures or entry into an ANSI-41 subscriber profile. The GPRS-VLR IWF 37 (see FIGURE 5) translates ANSI-41 MINs into the associated INSI established during the GPRS adhesion procedure. The SGSN 31 then translates between the IMSI and TLLI. B. In the MM sub-layer In the MM sub-layer, the GPRS service profile of the mobile station resides in GPRS HLR. The switched circuit service profile of the mobile station resides in ANSI-41 HLR. For circuit switched purposes, the location update and the subscriber profile update are carried out by ANSI-41 HLR. When the mobile station operates in the GPRS mode, the associated ANSI-136 information is sent to 7 from the associated infrastructures. For data packet purpose, the location update and the subscriber data update for the mobile station are provided by the GPRS HLR. The security functions related to GPRS data packets for the mobile station are also provided by the GPRS HLR. The execution of the security functions are within the scope of the GPRS core network. Authentication of the Class D and Class E mobile station for data packet purpose is carried out by GPRS HLR / AUC. The authentication of the Class D mobile station for circuit switched purpose is carried out by an ANSI-41 HLR / AC. Since data encryption is provided by the LLC sub-layer in accordance with the GPRS data packet security functions, there is no need to provide ANSI-136 message encryption and privacy functions on PCCH. An optional interface (Fl) is established between ANSI-41 HLR / AC and GPRS HLR / AUC for authentication synchronization between circuit switched and packet switched services. The GPRS HLR / AUC informs the ANSI-41 HLR / AC of its authentication status. If the subscriber is successfully authenticated in the GPRS system, the ANSI-41 HLR and MSC / VLR do not wait for the AUTHR of the mobile station in non-call accesses. When the subscriber is active and is authenticated in the GPRS system, the ANSI-41 HLR and MSC / VLR only invoke security functions for call access (originating and terminating). The relationship described above between the GPRS MSC / VLR and the GPRS service mode is retained to support similar mobility functions between the mobile station and the SGSN and the ANSI-41 MSC / VLR. Some ANSI-136 miscellaneous signaling and mobility functions are supported through new signaling messages between MSC / VLR and the GPRS service mode. The GPRS signaling procedures use an INSDI base MSDI domiciliary scheme. The ANSI-136 base signaling procedures use the base MSID direct dial scheme. The SGSN must be able to detect when the location update to the ANSI-41 network is carried out. The use of transmission location areas and route areas in PCCH defines the relationship between GPRS MSC / VLR serving the LA area and the GPRS serving the RA areas. The mobile station must inform SGSN of the need to carry out the location update whenever a new LAI is detected in PCCH, which also matches the new RAI detected. The mobile station updates the SGSN in its position by sending a Route Area Update Request and also indicating that an LA update will be performed. The RAIs are used to identify the association between SGSN and the GPRS MSC / VLR through translation tables. SGSN then sends an LA update to GPRS MSC / VLR. This RA and LA update can be referred to as "RA / LA Combined Update". The same approach is used to keep the handling consistent with the pure GPRS system, with the following • difference. The combined LA / RA update is 5 implemented when the transmission areas and route areas in the PCCH define a relationship between ANSI-41 MSC / VLR which serves the LAs and the GPRS SGSN which serves the RAs. Therefore, the use of transmission location area and route area in the PCCH defines a The relationship between the LAs and the RAs so that a location area can represent a set of cells with DCCH coverage which can also match, or share the cell coverage of one or more route areas constructed of cells with PCCH coverage. In the In this invention, the relationship LA and RA defines an association between the GPRS SGSN Ras and ANSI-41 MSC / VLR. In order to support the above, the mobile station • updates the SGSN in its position by sending a Route Area Update Request, also indicating that an LA update should be carried out. RAIs can be used to identify the association between SGSN and GPRS-VLR IWF / ANSI-41 G-MSC through translation tables. The SGSN can send the update LA to GPRS-VLR IWF. The network administrator coordinates the association between RAI, ANSI-41 MSC / VLR and GPRS-VLR I F / ANSI-41 G-MSC IDS. GPRS and ANSI-136 geographic location triggers are based on the concept that RAIs will not span more than one SGSN service area, and will be unique within and between SGSN. Therefore: • The scope of an LAI is defined so that it does not cover more than one SGSN service area. • The scope of an LAI can be defined to cover a subset of the SGSN service area. • The scope of an LAI is defined so that it does not cover more than one ANSI-41 service area serving MSC / VLR. • The scope of an LAI can be defined to encompass a subset of an ANSI-41 serving MSC / VLR. • RACs are unique within the scope of an LAI, and therefore within the scope of a RAI. Therefore, the scope of a RAC is defined so that it can not exceed the scope of an LAI. A mobile station performs the Route Area Update procedure and an ANSI-136 Record when the mobile station perceives a change in RAI due to an LAI that is different from that applied before to the current cell selection or re-selection. More specifically: • The new cell belongs to a new SGSN service area and a new ANSI-41 service area serving MSC / VLR, or "• The new cell belongs to a new SGSN service area and the same ANSI-41 serving MSC / VLR, • The new cell belongs to the same SGSN service area and a new ANSI-41 service area serving MSC / VLR C. In the RR Sub-layer The ANSI-136 sub-layer has a shared mode and a dedicated mode specifying all the radio network and access functions with traffic management and handling entities. These are implemented in the BS and ANSI-41 MSC / VLR. The shared mode RR sub-layer of ANSI-136 is defined through a specific MAC physical layer ANSI-136. the physical layer and the RLC / MAC layer are specified to accommodate 30 kHz ANSI-136 channels. The GPRS radio resource function is also modified to accommodate ANSI-136 30 kHz channels. The shared mode RR sub-layer supports Recognize and Not Recognize operation modes. The shared mode RR management entity (RRME) of the radio network and access functions include a specific component of the BS interface and a BS network component. The network component BS is implemented in an Interconnection GPRS Base Station Controller (BSC) and in ANSI-41 MSC / VLR. The ANSI-41 MSC / VLR component is linked with the RR management entity dedicated mode for (1) to manage the channel and time segment configuration (spectrum management and channel management), (2) support channel management specific GPRS and ANSI-136 for DCCH and GPRS packet control channel selection and (3) process other operation, administration, maintenance and parameters (OAM &P) information (PBCCH) transmission control channel, including transmission of RAND authentication, and other access and system parameters related to the operation of the RR sub-layer. A radio resource management interface (F3) can be provided between the GPRS BSC and ANSI-41 MSC / VLR interconnection to coordinate the three handling functionalities. The traffic management entity RR of shared mode ANSI-136 of the radio network and access functions also have a specific component of air interface BS and a traffic management component specific to the BS network. The specific component of air interface BS managed the relay on the MAC air interface. The network-specific traffic management component BS handles an equivalent Gb interface termination and provides a relay between the Gb interface and the BS. The network-specific component implemented in the GPRS BSC Interconnection 'which can be physically located in BS or ANSI-41 MSC / VLR. The PCCH and the PTCH are configurable using GPRS logical channel configuration tools which can be modified as necessary. The PCCH is used for signaling control and delivery of data packet loads in the uplink and in the downlink. This allows initial deployments to consist of a simple total PCCH at any given ANSI-136 channel frequency. The PCCH uses the same frame format (module 32) as ANSI-136 DCCH channels. The PCCH frames consist of transmission X segments (PBCCH) and Y call segments (PCCH) where X + Y = 32. The configured PCCH segments PPCH can also be used to carry control information or information packet data loading (PARCH) D. In the LLC Sublayers Below is the possible combination of modes when the ANSI-136 is shared mode RR (ANSI-136 RLC / MAC) and LLC considered together: • LLC Not recognized - RLC Not recognized This mode is possible when there is a short message network layer exchange (segments 1-2) where the recognition is built into the network layer that signals itself. An example is where the system sends a Search and the mobile station sends a response (any LLC framework serves as an answer by GPRS). Apart from the network greeting, the only recognition that takes place is the confirmation in the RLC layer of a successful contention during which the response was sent. Upon receipt of the Search Response the RLC base station confirms the reception by transmitting a control plane message indicating "Received" to the winning mobile station. The Response to Search is important to the infrastructure because it allows the mobile station to be considered as having been notified successfully. The mobile station must therefore ensure that its Search Response was successfully transmitted. If the mobile station does not receive an RLC control plane confirmation within, for example, 120 s, and resends its Search Response. • LLC Not Recognized - Recognized RLC This mode can be useful in any of the following cases: (i) Longer network layers will be sent, associated network layer acknowledgments have a very large delay associated with them and mode recognized only in The RLC layer is considered sufficiently reliable. (ii) the LLC can not operate in recognition mode • Recognized LLC - RLC Not Recognized This mode may be unlikely. Having only one of these layers operating in the recognition mode would make the RLC preferable as your ARQ based on smaller segments. • Recognized LLC - RLC Not Recognized This mode can be useful when sending longer and very secure network layer messages and / or reliable transmission if desired. E. Description of FIGURES FIGURE 1 is an illustrative drawing of a radio network structure MSC / VLR 10 showing the relationship between several GPRS network areas and GPRS network areas in the integrated GPRS / ANSI-41 network. Illustrated at the lowest level is an exchange service / exchange area 11 MSC. The MSC service / exchange area is shown divided into a plurality of voice / circuit switched service cells 12 defining a voice / circuit switched service area, and a plurality of data packet service cells 13 defining the area of service. data packet service. A GPRS Service Node serving area 14 encompassing a data packet service area may overlap or share the cell coverage of a portion of one or more MSC service / exchange areas. As shown in the next level, the SGSN service area can be divided into a plurality of route areas 15. Similarly, as shown in the next two levels, the MSC service / exchange area of route areas 11 encompassing a The voice / circuit switched area may be divided into a plurality of location areas 16 with search areas 17. FIGURE 2 is a simplified block diagram of an integrated GPRS / ANSI-41 network according to a first embodiment of this invention. On the ANSI-41 side of the network, there is an Authentication Center / Home Location Registration ANSI-41 (HLR / AC) 21 which is connected by a CD interface to MSC / VLR 22 and 23. The MSC / VLRs are illustrated as Serving, Visitor, or Exit (S / V / G) MSC. The MSC / VLR, in turn, are connected to the Base Stations (BS) 24-26. within the ANSI-41 network, access to the GPRS data packet network can be provided on a subset of MSC / VLR service areas, therefore, FIGURE 2 shows MSC / VLR 22 controlling a standard base station ANSI-136 and a GPRS / ANSI-136 base station. BS 24 is shown as an ANSI-136 base station while BS 25 and BS 26 are shown as a GPRS / ANSI-136 base station. The GPRS / ANSI-136 base station is an ANSI-136 base station that are capable of GPRS. • On the GPRS side, there is an Authentication Center / GPRS Address Location Register 5 (HLR / AUC) 31 which is connected by an interface Gr to a GPRS Service Switching Node (SGSN 32, and is connected by an interface Ge to a GPRS Output Switching Node (GGSN) 33. The GGSN is connected by a Gi interface to • 10 a Data Packet Network 34, and is connected to a Gn-Gp interface to the SGSN 32. The GGSN, which the GPRS equivalent for an Internet access entry, and its interfaces are reused without modification. The SGSN can be connected by a Gn interface to others SGSN in the GPRS network, and by a Gf interface to an Equipment Identity Register (EIR) 36. The Gn interface of the SGSN to other SGSNs in the GPRS network is reused without • modification. Similarly, the Gf interface of the SGSN to the EIR is reused without modification. 20 To support the integration of voice services and data packets without too much integration of the GPRS and ANSI-41 functions, an interface is required between the switched service node (such as MSV / VLR 23) and the packet service node switched (such as SGSN 32). The The interface is provided by introducing a new F2 interface between MSC / VLR and a GPRS of GPRS Visitor Location Record Interconnect Functions (GPRS-VLR IWF) 37. The GPRS-VLR IWF transforms the MSC / VLR signaling and interconnects it with SGSN through the protocol of the Gs / Gd interface. Thus, one aspect of the GPRS / ANSI-41 integration is to transform the signaling between the switched circuit serving the MSC / VLT and the standard Gs / Gd interfaces of GPRS. With this approach, the MSC / VLR23 and the SGSN 32 are decoupled as much as possible with GPRS-VLR IWF 37 to translate between them. In the embodiment shown in FIGURE 2, the dotted box 38 indicates a specific implementation to the MSC / VLR 23 and the GPRS-VLR IWF 37. If the GPRS-VLR I F is integrated into the MSC / VLR, there is no open interface F2. There are two different types of mobile station, and some may have simultaneous access to circuit switched and data packet services. For that mobile station, the failure mode is to access the GPRS network and then inform the associated switched circuit network that the mobile station is active and registered in the GPRS network. When the mobile station registers in the GPRS network, the SGSN 32 informs MSC / VLR 23 of the registration through the interface between them. When this information is received in the MSC / VLR, it triggers the location update function in the circuit switched network, updating the location in ANSI-41 HLR / AC 21. An interface (Gb ') is also required between SGSN 32 and the base station GPRS / ANSI-136 26. This interface is a modification of the specified GPRS interface (Gb) which connects the SGSN with the GSM base station and the subsystems (BSS) (not shown). An Interconnection GPRS Base Station Controller (I GPRS BSC) 39 logically provides the termination of the interface • 10 Gb 'of SGSN 32. The I GPRS BSC may be physically located at the base station, but it is not mandatory. The Gb 'interface supports the specific GPRS signaling and the data that passes between the mobile station and the SGSN (being this, traffic) which requires to pass through I GPRS BSC. A resource management interface (F3) is implemented to connect the MSC / VLR of Radio Resource Management Entity (RRME) • with an associated component in IW GPRS BSC. A traffic interface 40 is provided between the IW GPRS BSC and the base station GPRS / ANSI-136 26. From IW GPRS BSC there is a semi-permanent connection through MSC / VLR 23 to bring traffic to the base station GPRS / ANSI .136. The traffic interface is not standard, and is specific to each manufacturer. The signaling of The switched packet is used between SGSN and the mobile station by means of IW GPRS BSC and the base station GPRS / ANSI-136. A relay function adapts the signaling format of the Gb 'interface to the signaling format of the air interface for use by the base station. The lower layers of the interface are also adapted. This can be done by adapting from an IT to a channeled IT, or between a channeled IT and digital cross connections (DXC). Free IT is not segmented into multiplexed DDOs while pipelined IT is segmented into 24 multiplexed DSOs. Therefore, between SGSN 32 and the IW GPRS BSC 39, there may be one or more logical DSOs, and the I GPRS BSC may carry DXC functions. From IW GPRS BSC to the base station GPRS / ANS-136 26, there may be one or more DSOs assigned with a semi-permanent base. »There may also be an interface Fl between ANSI-41 HLR / AC 21 and the GPRS HLR / AUC 31 to ensure that the authentication status of the mobile station is retained in the reciprocal network while the mobile station is in the service mode of switched circuit or packet switched service mode. The authentication functions are typically carried out at the first access to the network, and the authentication data is passed on the interface Fl between the HLRs. Therefore, authentication is carried out by GPRS HLR / AUC, the Fl interface is used to inform ANSI-41 HLR / AUC of successful authentication. When the mobile station is registered in both networks, • can receive circuit switched calls during a data packet transaction. Circuit-switched calls to the mobile station are delivered to the MSC / VLR 23 serving the switched circuit where the mobile station is registered. MSV / VLR uses the F2 interface through GPRS-VLR IWF 37 to request • 10 to SGSN 32 searching for the mobile station in preparation for the delivery of the circuit switched call. The SGSN searches for the mobile station at the known location. The mobile station responds to the search and this fact is passed to the MSC / VLR. The call is completed through of the GPRS / ANSI-136 base station 26. The radio access to the GPRS network is a multiple access, so that all users are multiplexed into a channel for data packet access. This makes the most efficient use of interface resources and also allows the switching of the data packet mode to the circuit switched mode and vice versa. Therefore, the mobile station can switch from the data packet mode to a circuit switched circuit air traffic channel to receive a call. When completes a call, the mobile station switches back to data packet mode. FIGURE 3 is a simplified block diagram of an integrated GPRS / ANSI-41 network according to a second embodiment of the present invention. In this embodiment, the GPRS-VLR I F 37 is integrated with SGSN 32 on the GPRS side of the interface. The IWF GPRS BSC 39 is associated with the ANSI-41 network, and can be implemented with MSC / VLR 23. The functionality described in relation to FIGURE 2 remains the same. FIGURE 4 is a simplified block diagram of an integrated GPRS / ANSI-41 network according to a third embodiment of the present invention. In this incorporation, there is no Fl interface between ANSI-41 HLR / AC 21 and GPRS HLR / AUC 31. Modifying the ANSI-41 signaling, ANSI-41 authentication center is modified to the initial registration and location update that the mobile station is accessing the network GPRS. The ANSI-41 HLR / AC can defer authentication to the GPRS network until the mobile station switches back to the circuit switched network. When the mobile station accesses the GPRS network, the SGSN 32 is notified. If it is a type access of a location update, the SGSN initiates the location update signaling to MSC Gate 41 of the associated ANSI-41 switched circuit. The MSC Gate, in turn, carries out the location update to the HLR / AC 21 with Authentication Request (AUTHREQ) and Registration Notification (REGNOT). A new type of access is introduced with indications that the mobile station has accessed the • GPRS network in the control channel. 5 FIGURE 5 is a simplified block diagram of an integrated GPRS / ANSI-41 network according to a fourth embodiment of the present invention. The GPRS integration with the ANSI-41 network is carried out logically through the addition of two new network nodes, ANSI-41 G-MSC / VLR 42 and • 10 GRPS-VLR I F 37. The GPRS network structure is in accordance with what is currently defined in GSM standards. The SGSN 32 is the only GPRS node that is visible to the ANSI-41 network. The ANSI-41 portion of the network includes an ANSI-41 HLR / AC 21, a MSC / VLR gate according to ANSI-41 (G-MSC / VLR) 42, an ANSI-41 MSC / VLR 43, a Message Center (MC) 44 according to ANSI-41, a Short Message Entity (SME) 45. The ANSI-41 G-MSC / VLR is connected to the GPRS portion of the network through from • GPRS-VLR I F 37. The GPRS portion of the network includes an SGSN 32 which is connected to GPRS-VLR IWF, a first GGSN 33 which is connected to PDN 34, and a second GGSN 46 which is part of another PLMN 47. The SGSN 32 is also shown as connected with a second SGSN 35, an EIR 36 a GPRS HLR 48 and a base station (BS) 49. The BS, in turn, is connected to a Mobile End System (M-ES) 51 and a Terminal Equipment (TE) 52. FIGURES 2 to 4 illustrate an Interconnected GPRS Base Station Controller (IW GPRS-BSC) 39. In FIGURE 5, the IW GPRS-BSC has been integrated into ANS-41 G-MSC / VLR 42 or BS 49. The GPRS-VLR IWF 37 and ANSI-41 G-MSC / VLR 42 are new network elements. The purpose of the GPRS-VLR IWF 37 is to act as a visitor location register from the point of view of SGSN 32 when the mobile station is Class D. From the point of view of G-MSC / VLR 42, the GPRS -VLR IWF acts as a GPRS service node. The GPRS-VLR IWF handles the following functions: (1) Subscriber connection to SGSN; (2) provide a network interface and protocol adaptation to and from BSSAP + of the Gs interface. New or modified transactions may be required to handle mobile station policies and orders originating from ANSI-41 MSC-HLR; (3) Management of the Gx interface to and from ANSI-41 G-MSC / VLR 42 to search for call delivery, location update, suspension and summary, etc., for other potential mobile station policies and for SMS messages from origin / termination. (4) Send SMS messages that originate in the ANSI-41 network to SGSN 32. In the GPRS-GSM network, this is the role played by the MSC SMS (SMS-GMSC) output. However, the GPRS-VLR IWF 37 does not require to examine the destinations of the M-ES address and does not need to send the Send Route Info for Short Message to GPRS HLR 48, since • that this information is already provided by ANSI-41 5 G-MSC / VLR 42. The main benefit provided by GPRS-VLR IWF 37 is that only small changes are required to SGSN 32 as described above when interconnecting to a network ANSI-41. It is estimated of benefit, the GPRS-VLR IWF can be integrated with the SGSN. In an integration introduction phase ANSI-41 and GPRS, the GPRS-VLR I F 37 and ANSI-41 G-MSC / VLR 42 can be combined. At a later stage, they can be separated and integrated with SGSN and MSC, respectively. The ANSI-41 G-MSC / VLR 42 performs the following 15 functions: (1) provide VLR functions for the purpose of PLMN switched circuit services when the service node is a GPRS SGSN, allowing for output functions to and from the GPRS network. This element leads to out search control towards SGSN 32 and record handling towards ANSI-41 HLR / AC 21. (2) Provide cellular output functions when the service node is GPRS SGSN. For this reason, the call route, redirected from calls and interactions of supplementary service are handled by ANSI-41 G-MSC / VLR. The main benefit provided by ANSI-41 G-MSC / VLR is that there is no need to update any ANSI-41 MSC / VLR • when GPRS is entered. If determined beneficial, the 5 ANSI-1 G-MSC / VLR 42 can be integrated with ANSI-41 MSC / VLR 43. The ANSI-41 HLR / AC 21, the SGSN 32, the BS 49 and the M-ES 51 are modified in the present invention. The ANSI-41 HLR / AC requires modification for the following reason. While it is served by a packet control channel (PCCH) system, the Class D mobile station is managed by the GPRS network, including GPRS subscriber authentication. The ANSI-41 HLR / AC should know that the mobile station is being serviced by a PCCH system that additional authentication of a Subscriber must be handled differently when the mobile station is served by a DCCH or ACC. The SGSN 32 is modified to handle addressing of specific ANSI-41 messages and / or parameters to support MIN fixation and authentication functionality such as MIN, ESN, COUNT, RANDC, etc. The BS 49 corresponds to the reference model BSS and GPRS. It includes additional functions to handle ANSI-136 data packet channels in the MAC / RLC layer. It also handles the Gz interface to SGSN which is based on the Gb interface. The M-ES corresponds to the terminal mobile data / voice in the GPRS-ANSI reference model.

It has a new functionality to handle ANSI-136 data packet channels on the Um interface including the MAC / RLC layer, and a higher layer protocol. This allows the • communication with the GPRS network, for example with SGSN 32. 5 The ANSI-41 MC 44, the ANSI-41 SME 45, the GPRS HLR 48 the EIR 36 and the GGSN 33 are not changed. The following interfaces are illustrated in FIGURE 5. C: This is an ANSI-41 signaling interface between HLR / AC 21 and MSC / VLR 43 for all application signaling • 10 involving MSC functions to redirect call, call transfer, etc. D: this is an ANSI-41 signaling interface between HLR / AC 21 and MSC / VLR 43 for all applications involving VLR functions such as Call Delivery, Authentication, Location Tracking, directives for mobile station, etc. Interface D is updated for Authentication Requests with an indication that the registration was made in the packet control channel. This additional data element in an existing data field which does not affect MSC / VLR 43, but only G-MSC / VLR 42 and HLR / AC 21. E: This interface is only required if G-MSC / VLR 42 and MSC / VLR 43 are not integrated. Interface E is used to transfer the Unsolicited Response message from the service MSC / VLR to G-MSC / VLR. 25 Gx: This interface is required only if G-MSC / VLR 42 and GPRS-VLR IWF 37 are not integrated. The Gx interface carries ANSI-41 messages to and from the GPRS network signaling transactions such as location updates, search, authentication, SMS, etc. Gz: This is a transport interface between SGSN 32 and BS 49. The Gz interface relieves LLC PDUs for data information and user control. Gd: it is a signaling MAP interface for SMS delivery and origin of SMS signaling in the GPRS reference model. In the present invention, the Gd interface is supported between GPRS-VLR IWF 37 and SGSN to allow origin and destination ANSI-41 SMS for mobile station camping in PCCH. The GPRS-VLR IWF delivers the terminal SMS messages to SGSN when they are received from G-MSC / VLR 42. The GPRS-VLR IWF delivers SMS origin messages to the mobile station to the G-MSC / VLR. Gf: This is an optional MAP-based signaling interface used for terminal authentication. Gi: This is a GPRS interface with no change. Gn: This is a GPRS interface with no change. Gp: This is a GPRS interface with no change. Gr: This is a MAP base signaling interface between SGSN 32 and GPRS HLR 48 which is used for transactions such as authentication and retrieval of subscriber data. Gs: This interface is used between SGSN 32 and GPRS-VLR IWF 37, and is only required if SGSN and GPRS-VLR IWF are not integrated. The Gs interface is implemented in accordance with GPRS standards except that a smaller subset of defined messages is used, and some messages are modified to carry information for ANSI-41 integration. For example, the information is portada for transactions such as location updates, search, authentication, etc. Additional data such as MIN, ESN, COUNT, RANDC, etc. are transferred in the Location Update Request message. The Gs interface is a subset of BSSAP. M: This is an ANSI-41 signaling interface between SME and MC, from one MC to another MC and from one SME to another SME. The M interface also serves as the transport of SMS messages. N: This is an ANSI-41 signaling interface between MC 44 and HLR / AC 21. Q: This is an ANSI-41 signaling interface between MC 44 and G-MSC / VLR 42. The Q interface also serves as the interface of transport for SMS messages. A: This is a GPRS interface with no change. Um: This is a radio interface according to TR45.3 standards. FIGURE 6 is a message flow diagram illustrating the flow of signaling messages between the nodes of the integrated network of Figure 5 when a Class D final mobile station (M-ES) performs the GPRS fixation procedure. In a. Fixing procedure, the M-ES provides its service node with its previous MIN, IMSI or P-TMSI and the previous RAI in an indication of what type of fixation should be executed. The different types of fixing are GPRS fixing, MIN fixing and GPRS / MIN combined fixing. A fixed GPRS M-ES makes a MIN fix to an ANSI-41 by means of SGSN. An M-ES that is not fixed GPRS makes a MIN fix as defined in ANSI-41 standards. The IMSI or the previous P-TMSI and the previous RAI are used as identifiers during the fixation procedure until the new P-TMSI is assigned. The MIN is used for identification in the ANSI-41 network. After executing the GPRS fix, the M-ES is in the READY state, and MM contexts are established in M-ES in SGSN. The M-ES can then activate PDP contexts. The SGSN location number of this particular M-ES is stored in GPRS-HLR so that changes in subscriber data can be communicated to SGSN. If little subscriber data is received in SGSN, and if the M-ES is set to GPRS, the SGSN may, if required, send the M-ES to make a new GPRS fix and a new PDP context activation to use the new subscriber data. At 61, the M-ES 51 turns on and finds a DCCH, and starts reading F-BCCH and E-BCCH. If the data packet is not supported, or is supported but in a modulation scheme the M-ES is not capable of (or the M-ES does not want data packet service), the M-ES remains in Camped state DCCH and performs any DCCH record • necessary. If the data packet service 5 is supported using a modulation scheme the M-ES is capable of supporting and the M-ES wants the data packet service, the M-ES tunes to the Beacon PCCH at 62 and reads F- BCCH on it to determine its Assigned PCCH. If it is not in your Assigned PCCH, the M-ES tunes it. The M-ES reads the NL information in its • 10 assigned PCCH. At 63, the M-ES makes its identification (IMSI or P-TPMS) for a new SGSN 32 by the transmission of a Fixation Request (IMSI or P-TMSI and previous RAI, CKSN, Type of Fixation, Params DRX, Signature Previous P-TMSI, MIN, ESN, COUNT, RAN DC, AUTHR) to the new SGSN. Class M-ES indicates that the M-ES is a Class D M-ES (this being, it uses ANSI-41 for circuit switched services). The Class Mark contains the ANSI- • 136 of the M-ES multi-segment capability and encryption algorithms supported by GPRS. The Fixation Type indicates that type of fixing procedure must be carried out (this being, only GPRS Fixation, MIN only or Combined GPRS MIN Fixation). The combined GPRS MIN is also used in a GPRS Fix when M-ES is already set MIN. The DRX parameters indicate whether or not the M-ES uses discontinuous reception. If M-ES uses a discontinuous reception, then the DRX parameters also indicate when M-ES is in a sleep mode capable of receiving location requests and channel assignments. The DRX parameters are represented in the Location Table Class according to ANSI-41. If M-ES uses its old P-TMSI to identify itself, and if it has also stored its old signature of P-TMSI, then M-ES includes the old signature P-TMSI in the posting request message. Note that new parameters must be added to the GPRS fix message (MIN, ESN, COUNT, RANDC and AUTHR). In addition, the class mark indicates a multi-segment capability according to ANSI-136 (ie, 1 to 3 time segments instead of 1 to 8 time segments). Steps 64 to 75 are carried out as described in Figure 15, section 6.5 of GSM 03.60, which is incorporated herein by reference. At 64, an Identification Request is sent from the new SGSN 32 to the previous SGSN 35. The previous SGSN responds with an ID Response message 65. At 66, an Identity Request is sent from SGSN to M-ES 51. The M-ES responds with an 'Identity Response message 67. Then it is carried out an authentication procedure at 68 between M-ES and the new SGSN, and GPRS HLR 48. At 69, an IMEI verification is performed between M-ES, the new SGSN and EIR 36. At 71, the new SGSN 32 sends a Location Update message to GPRS HLR 48. The GPRS HLR sends a Cancel Location message 72 to the previous SGSN 35 which corresponds to 73 with a Location Abort Acknowledgment. In 74 the GPRS • HLR sends subscriber data to the new SGSN which sends a 5 acknowledgment to 75. The GPRS HLR reports the Location Update message to 76. If a MIN fix is carried out via GPRS-VLR IWF 37 to ANSI 41 G-MSC / VLR 42. The GPRS-VLR IWF number is derived from the RA information. If the M-ES is already set MIN and is carrying out a fixation • 10 Combined GPRS / MIN, an association is created by sending a Location Update Request via GPRS-VLR I F to ANSI-41 G-MSC / VLR. This marks M-ES as set to GPRS in ANSI 41 G-MSC / VLR. At 77, the new SGSN 32 sends an Update Request Location (with new LAI, IMSI, SGSN, M-ES, MIN, ESN, COUNT, RANDC and AUTHR) to the GPRS-VLR IWF 37. GPRS-VLR IEF creates an association with the new SGSN by storing the Number SGSN and Class M-ES. The GPRS-VLR IWF stores MIN and IMSI in order to carry out the home translation. The MIN, ESN, COUNT, RANDC and AUTHR parameters must be added to the Location Update Request message. At 78, the GPRS-VLR IWF sends a Registration Request message with MIN, ESN, COUNT, RANDC and AUTHR to ANSI-41 G-MSM / VLR 42 using the Gx interface. The ANSI-41 G-MSC / VLR sends a message of Invoke Qualification Request (QUALREQ) 79 to ANSI-41 HLR / AC 21 in order to quickly carry out profile validation. The domiciled MIN and ESN are used to identify the subscriber in the transaction. The ANSI-41 HLR / AC 21 identifies the M-ES 51 and returns the subscriber profile in a QUALREQ 81 to ANSI-41 G-MSC / VLR 42 with successful validation of the subscriber. At 82, the ANSI-41 G-MSC / VLR sends an Authentication Request (AUTHREQ) to ANSI-41 HLT / AC 21. This message includes information indicating that the Registration has been made on the Packet Control channel. The "System Access Type" parameter in the AUTHR message receives a new value, "PCCH access", which indicates to the HLR / AC according to ANSI-41 that the connection is made through GPRS. The ANSI-41 HLR / AC 21 responds by sending a Return Result AUTHREQ 83 to ANSI-41 G-MSC / VLR 42. The ANSI-41 G-MSC / VLR sends a Registration Notification (REGNOT) 84 with MIN, ESN , COUNT, RANDC and AUTHR to ANSI-41 HLR / AC. If the REGNOT involves an MSC change, the HLR / AC sends a Registration Cancellation (REGCANC) 85 to ANSI-41 MSC 43 above. This is done in the case of GPRS connection for an M-ES already fixed through MIN to a different MSC. The old MSC according to ANSI-41 acknowledges receipt with an R EGCANC 86 Result Return message. Upon completion of the inter MSC registration notification procedures, the ANSI-41 HLR / AC 21 responds by sending a REGNOT 87 to ANSI-41 G- MSC / VLR 42. The G-MSC / VLR of ANSI-41 then sends an acknowledgment of receipt of Record 88 to GPRS-VLR IWF 37. GPRS-VLR IWF responds with a message 89 of Acceptance of • Location Update to the new SGSN 32. The new SGSN sends a message of OK Fixation 91 to M-ES 51 and includes the P-TMSI, PLMN-supported MT capabilities and P-TMSI signature. If P-TMSI changed, the M-ES acknowledges receipt of P-TMSI received with a Full Fix message 92 that includes P-TMSI. If the Application for Fixation can not be accepted, the • 10 new SGSN returns a Fixed Rejection message (not shown) to M-ES and includes the IMSI and Cause. Table 1 below summarizes the changes made to various messages and the information elements described above. Message / change element comment 15 Information Request for setting new parameters MIN, ESN, COUNT, RANDC, AUTHR • Class M-ES new classes M-ES class D = equivalent to class B of ANSI-41, class E = • class C of GPRS except that it can only operate on 25 channels of 30 kHz Brand of new class meaning indicates a capacity of multiple segments se- according to ANSI-136 (full speed at triple speed = 1 Request for update of parameters MIN, ESN, COUNT, location determination RANDC, AUTHR type of access to new value of indicates "access system ANSI-41 parameter PCCH" in the AUTHREQ menu Table 1 FIGURE 7 is a diagram of message flow illustrating the signaling flow of messages during an Intra-SGSN Route Area Update (RA) procedure. An RA update is carried out when the fixed GPRS M-ES in the STANDBY or READY state detects that it has entered a new RA or when the periodic update time RA has expired. The SGSN detects that the update is an intra-SGSN route area update because the SGSN also handles previous RA. In this case, the SGSN has the necessary information regarding M-ES, and therefore there is no need to inform GGSNs or HLR of GPRS regarding the new location of M-ES. A periodic RA update is always found in an intra-SGSN routing area update. An M-ES in the READY state due to anonymous access does not perform RA updates. If the M-ES has entered a new route area, an Anonymous Access PDP Context Activation procedure is initiated. The previous context is implicitly eliminated at the expiration of the READY time. Figure 7 assumes a simple case involving the M-ES 51, the BS 49 and the service SGSN 35 of Figure 5. In step 101, the M-ES 51 acquires services in the new service PCCH and reads a complete cycle of transmission information. The transmission information includes a neighboring list (NL), the coincidental DCCH coverage of the service cell and the Identity of the Route Area. When a new Routing Area ID is detected, the MS then sends a Routing Area Update Request 102 to SGSN and includes authentication data and subscriber identification according to ANSI-41 (MIN, ESN, AUTHR, RAND, etc.). ) in addition to the old RAI, and the old P-TMSI signature. The BS adds an identifier of the cell where the message was received before passing the message to SGSN. The SGSN derives the new RAI from the aggregated cell identifier (see GSM 08.18). In 103, security functions can be executed. These procedures are defined in the subclause "Security Functions" of GSM 3.60. Security procedures can be invoked towards the M-ES such as, for example, Authentication. The SGSN 35 then validates the presence of M-ES in the new RA according to the procedure specified in GSM 3.60. If due to regional, national or international restrictions the M-ES is not allowed to be set in the RA, or the subscription verification fails, then SGSN rejects the RA update with an appropriate cause. If all verifications are successful then SGSN updates the MM context for the M-ES. A new P-TMSI can also be assigned. A Routing Area Update Acceptance message 104 (with P-TMSI, signature P-TMSI) is then returned to the MS. If P-TMSI was reassigned, M-ES acknowledges receipt of the new P-TMSI with a completion message Route Area Update (with P-TMSI). If the RA update procedure fails a maximum number of times allowable, or if the SGSN returns a message (cause) of Rejection of Route Area Update, the M-ES 51 enters IDLE state. For the integrated network, this means that an implicit non-binding is performed which forces the M-ES to return to camp in DCCH using the DCCH coincidental pointer acquired when it obtains service in PCCH. Table 2 below summarizes the changes made to various messages and information elements described above. Message / change element comment information Area update New parameters MIN, ESN, COUNT, RANDC Routing, AUTRH Table 2 FIGURE 8 is a message flow diagram illustrating the flow of signaling messages during an area update procedure. Route when the M-ES is in the STANDBY state. It is assumed that a new SGSN 32 is connected to a new ANSI-41 G-MSC through a new GPRS-VLT IWF 37. At 111, the M-ES 51 selects the new new cell PCCH, and reads the complete cycle transmission information including the neighbor list, the coincident DCCH coverage of the cell list including the neighbor list, and the Area Indicators. Location and Location Area (LAI and RAI) The M-ES acquires services on the new service PCCH and discovers a new Location Area Id and Location Area Id The M-ES sends an Update Request message RA 102 to the new SGSN 32. If the M-ES is set MIN, and if the RA Update request 102 requires a combined RA / LA, then before invoking the location update, the SGSN validates the presence of M-ES In the new RA, if due to regional, national or international restrictions the M-ES is not allowed to be set in the RA, or the subscription verification fails, then SGSN rejects the RA update with an appropriate cause. verifications are successful sas then • SGSN updates the MM context for the M-ES and the process passes 5 to step 142. Otherwise, authentication data and subscriber identification according to ANSI-41 (MIN, ESN, AUTHR, RAND, etc.), in addition to the old RAI, the former signature P-TMSI to SGSN are transmitted in the RA Update Request. Steps 113 to 125 are the same as e described in • 10 steps 2 to 9 in GSM 3.60 V 6.0.0 section 6.9.1.3.2. At 113, the new SGSN 32 sends a SGSN Context Request message to the old SGSN 35, and the old SGSN returns a SGSN Context Response 114. The previous SGSN sends packets to the new SGSN at 115. In 116 the authentication procedures are carried out between M-ES 51, the new SGSN 32, and the GPRS HLR 48. At 117, the new SGSN sends a PDP Update Context Request to • GGSN 33 and the GGSN returns an updated PDP Context Response to 118. The new SGSN 32 then sends a Update Location 119 message to GPRS HLR 48. GPRS HLR then sends a Cancel Location message 121 to the old SGSN 35, and the old SGSN returns a Location Cancellation Receipt Acknowledgment 11. At 123, GPRS HLR sends a message of Insert Subscriber Data to the new SGSN that returns an acknowledgment of receive at 124. GPRS HLR then returns a Location Update Receipt 125 to the new SGSN. The SGSN identifies the GPRS-VLR IWF (or Id) number of the RAI using an internal translation table and a location update procedure is carried out in steps 126 to 141. The new SGSN sends a Location Update Request 126 to the new GPRS-VLR IWF 37 and includes the identification and authentication data of M-Ess (MIN, ESN, AUTHR, etc.). The new SGSN stores the new identity number of GPRS-VLR IWF. The new GPRS-VLR IWF 37 informs the new ANSI-41 G-MSC / VLR 42 of the IMP implicit subscriber setting by sending a "Location Update Request" 127 including the identification of M-ES and authentication data (MIN, ESN, AUTHR, etc.). Note that the association between GPRS-VLR IWF and ANSI-41 G-MSC is one-to-one. The new G-MS / VLR 42 according to ANSI-41 sends an Invoke message QUALREQ 128 to HLR / AC 21 according to ANSI-41 in order to easily perform the subscriber profile validation. The MIN and ESN addresses are used to identify the subscriber in this application transaction. The ANSI-41 HLR / AC identifies M-ES 51 and returns the profile in a return message qualreg 129 to ANSI-41 G-MSC / VLR upon successful validation of the subscriber. Authentication procedures are required in MSC or AC. The ANSI-41 G-MSC identifies M-ES as ANSI-41 HLR / AC, and sends an AUTHREQ of Invocation 131 to the identified HLR / AC. Tentatively, the Access System Type parameter in AUTHREQ is used to indicate a • access in a PCCH. In this way, HLR / AC of ANSI-41 is informed to apply a specific authentication procedure such as the need for Buffer Authentication and possibly other MS instructions, until M-ES returns either in a DCCH or fine DTC. When the access type system indicates access to PCCH, a ANSI-41 HLT / AC 21 applies the authentication response algorithm associated with access type PCCH. For example, the single challenge initiated as AC, SSD updates and COUNT update history are deferred or buffered. At 132, a request response from authentication is returned to the specified subscriber. Upon successful MS authentication, the new G-MSC / VLR according to ANSI-41 42 sends a Warning message of »Registration 133 and includes the new G-MSC / VLR ID according to ANSI-41 to inform the address system of subscribers ANSI-41 HLR / AC 21 of the new subscriber location ANSI-41 G-MSC / VLR. The M-ES address ANSI-41 HLR / AC then validates the M-ES location update request. After a location update procedure of M-ES successful, the HLR / AC according to ANSI-41 of M-ES's sends a Request of Cancellation of Record 134 to the previous location of M-ES's (former MSC (G-MSC 43 according to ANSI-41) to remove the M-ES The following sequence must be carried out: First, ANSI-41 MSC / VLR 43 above responds to ANSÍ HLR /? C with a message of cancellation result of record 135. Next, the ANSI- 41 M? C / VLR sends a Subscriber Cancellation Request 136 to M-ES in the previous GWP-VLR IWF 53 to remove any reference from the subscriber that has been connected to SGSN through the previous GPRS-VLR IWF. Old VLR IF acknowledges 137. Upon validation of successful M-ES, an ANSI-41 HLR / AC 21 responds accordingly by sending the subscriber profile and a registration notification 138 to ANSI-41 G-MSC / VLR 42 using the stored Id node At 141, the new GPRS-VLR IWF responds to the SGSN 126 Location Update Request message by sending an Ac use Location Update to the new SGSN 32. When the RA or the subscription validation has failed, the new SGSN 32 rejects the RA Update with an appropriate cause. The ANSI-4 authentication result is sent to M-ES 51. If all verifications are successful, then the new SGSN establishes MM and PDP contexts for M-ES. A logical link is established between the new SGSN and M-ES. The new SGSN responds to M-ES with an Acceptance message from Area 142 Update (with P-TMSI, VLR TMSI, LLC and P-TMSI). The LLC Ack parameter contains acknowledgments for each LLC connection used by the M-ES, thereby confirming all successful mobile N-PDUs transferred before the start of the update procedure. The result of authentication according to ANSI-41 is new information returned to M-ES. M-ES confirms the reassignment of the TMSIs by sending a Routing Area Update 143 message (with P-TMSI, VLR, TMSI, and LLC Ack) to the new SGSN. The LLC Ack parameter contains the acknowledgments for each LLC connection used by the M-ES, thus confirming all successfully terminated mobile N-PDUs transferred before the start of the update procedure. If LLC Ack confirms receipt of N-PDUs that were sent from the previous SGSN, then these N-PDUs are discarded by the new SGSN. LLC and SNDCP in M-ES are reinitialized locally. In the case of a routing area update operation rejected, due to Routing Area restrictions, the new SGSN does not construct an MM context. A rejection is returned to the M-ES with an appropriate cause. The M-ES does not try again a routing area update to this RA. The value of RAI is removed when M-ES is activated. In case of absence of response from GGSN, the new SGSN does not build an MM context. A rejection is returned to M-ES with an appropriate cause. M-ES can retry to update with the same RA. As an option, the new SGSN can attempt the operation before rejecting the routing area update. If the routing area update procedure fails a maximum allowable number of times, or if the SGSN returns a Routing Area Update Reject message (Cause), M-ES enters the INACTIVE state. An implicit detach is made which forces M-ES to return to the encamped DCCH using the matching DCCH pointer (s) from the service cell acquired when service is obtained at the PCCH. If the update time RA expires and a Location Cancellation (IMSI) of the HLR has not been received, then the previous SGSN 35 interrupts the sending of the N-PDU to the new SGSN 32 and proceeds as if the SGSN context of the Request message 113 it was not received. If the Accept Location Update 141 message indicates a rejection, then this is indicative to M-ES and the M-ES does not access non-GPRS services until a successful location update is performed. Table 3 below summarizes the changes made to various messages and information elements described above. Message / change item comment Information Update Area new parameters MIN, ESN, COUNT, RANDC Routing, AUTHR Class M-ES new class class D = equiM-ES valid to class B of ANSI-41 Brand new class meaning indicates capacity of multiple segments according to ANSI -136 (total speed up to triple speed = 1 to 3 TS) Request of current new parameters MIN, ESN, COUNT, location determination RANDC, AUTHR Type of access to its new value of indicates "Access issues according to ANSÍ-41 parameter PCCH" in the AUTHREQ message Table 3 Table 4 provides additional information for the Gx interface. Message / element meaning information comment Registration request record Registration acknowledgment Cancellation cancellation of the M-ES record in the old GPRS-VLR IWF in exchange for ANSI-41 G-MSC Cancellation acknowledgment Table 4 Reselection of Inter-SGSN Route Area when the M-ES is in the READY state is carried out in the same manner as Figure 8. FIGURE 9 is a message flow diagram illustrating the flow of signaling messages during the Update procedure of Cell when M-ES in READY status enters a new cell in the current Route Area. An M-ES in READY status due to Anonymous Access does not carry out route area updates. If the M-ES has entered a new route area, an Anonymous Access PDP Context Activation procedure is initiated. The previous context is explicitly deleted when the READY time expires. A cell update occurs when the M-ES enters a new cell within the current RA and the M-ES is in the READY state. If the RA has changed, an RA Update is run instead of a cell update. At 151, the M-ES 51 reselects a new PCCH cell and reads the complete cycle transmission information. The transmission information includes a neighboring list, (NL), the coincidental DCCH coverage of the service cell and the Identity of the Route Area. The M-ES acquires services in the • New service PCCH and automatically resumes transmission on the new channel at 152 by transmitting an LLC uplink frame of any type containing the identity of M-ES to SGSN 35. The cell update consists of any valid received PDU LLC cover within BSGP PDU. BS 49 adds an identifier of the cell to • 10 all BSGP frames transmitted to the SGSN. The SGSN notifies the cell update when BSGP contains the cell identifier of a new cell. Note: from the RLC perspective, the appropriate mechanism must be in place to allow M-ES to resume reception / transmission on the new channel with the. minor penalty in delay. The SGSN records the cell change of M-ES and also directs the traffic to the M-ES on the new cell. The SGSN is responsible for buffering, and retransmitting the recognition of LLC frames in 153, when the recognition mode is used. FIGURE 10 is a message flow diagram illustrating the flow of signaling messages between nodes of the integrated network of Figure 5 when an incoming voice call is received for an M-ES in the STANDBY state. A mobile station in STANDBY state is assumed to have already carried out a Power On successful and therefore he has already received the TLLI assignment. In this case, an incoming voice call was first received by an ANSI-41 infrastructure and sent to the GPRS infrastructure. Communication between GPRS-VLR IWF 37 and ANSI-41 G-MSC 42b is • shows using the dotted line to indicate messages 5 are not required to follow the ANSI-41 MAP format. At 161, an M-ES 51 Class D is camped on a PCCH served by the SGSN 32. It has already carried out a GPRS Fixing procedure successfully and has therefore received TLLI assignment. Upon receiving an incoming call to M-ES, an MSC (0-MSC) 54 sends a LOCREQ of Invocation 162 (indicating voice call) to ANSI-41 HLR / AC 43 corresponding to the called network address. Upon receipt of the LOCREQ message, ANSI-41 HLR / AC identifies the white MSID associated with the address to which the call is made and sends a message invoking ROUTREQ 163 (indicating a voice call) to ANSI-41 VLR 42a. Upon receiving the ROUTREQ message, ANSI-1 VLR sends a ROUTREQ 164 message (indicating voice call) to ANSI-41 G-MSC 42b serving as an MSID target. Upon receiving the ROUTREQ message, ANSI-41 G-MSC sends a associated search message 165 to GPRS-VLR I F 37 and initiates a search response time for target MSID included in the search message. GPRS-VLR IWF 37 converts the white MSID into its associated IMSI GPRS and then sends a message to the SGSN 32 location 166 (with IMSI, Required Channel and Priority). The priority consists of a circuit switched location priority parameter according to what is defined in GSM 08.08. SGSN represents the priority to QoS.

• SGSN then sends a location request message 5 BSGP 167 (with IMSI, TLLI, Area, Required Channel, and QoS) to the BS 49 serving the M-ES 51. TLLI and Area are derived from the context of MM of M-ES's in SGSN. The Area indicates a single cell of an M-ES in the READY state or a Routing Area for an M-ES in the state of • 10 WAITING. The Required Channel is included only if it is received from GPRS-VLR IWF. If the Required GPRS-VLR IWF Channel was not received, then a default Required Channel parameter indicating the switched circuit location is included by the SGSN is included. QoS indicates the priority of this Location Request in relation to other Location Request messages stored in buffer memory by the BS. • The BS 49 moves the incoming BSGP Search Request into a Radio Search Request per call. If assigned a radio resource dedicated to M-ES in a cell (for example, the M-ES is in the READY state), then BS transmits a Search Request message 168 (with IMSI, TLLI and Required Channel) in this radio resource , without stopping potential data transfers in progress. Of other In this way, the BS searches for M-ES with a Search Request message in the appropriate search channel in each cell domiciled. This is described in GSM 03.64. Upon receiving a Location Request message for a • Circuit switched service, the M-ES 51 can decide 5 to respond to the request. If the M-ES accepts the circuit switched service, it tunes to the mother DCCH and starts reading the information from F-BCCH at 169. Upon receiving a complete information cycle from F-BBCH, the M-ES begins to search an access opportunity in the RACH. When finding a • 10 access opportunity, the M-ES sends a Location Response message 171 to a service MSC (S-MSC) 55 according to ANSI-41. Upon receipt of the Location Response message, the S-MSC according to ANSI-41 determines that the response is not requested. The S-MSC according to ANSI-41 then sends a message Summon Authentication Request (AUTHREQ) 172 to ANSI-41 HLR / AC 43. ANSI-41 HLR / AC verifies the MSID profile and returns an Authentication Request Return Result 173 message (authreq) to the S-MSC according to ANSI-41. The ANSI-41 S-MSC sends a 174 message of DTC Assignment to the M-ES in the DCCH. The S-MSC according to ANSI-41 also selects a TLDN and creates a message 175 of Response Invocation not .Solicitada (UNSOLRES) 175 that includes the selected TLDN, and the MSID of the M-ES for which the unsolicited location response was received. 25 The ANSI-41 S-MSC sends an UNSOLRES message to the list of MSCs that has been configured to contact in case of receiving an unsolicited response search. Upon receipt of the UNSOLRES message, the ANSI-41 G-MSC 42b uses the dedicated MSDI for • identify outstanding ANSI-41 transactions. The ANSI-41 5 G-MSC treats the UNSOLRES as the response to the search message previously sent to the indicated MSDI. Note that this message can be sent in combination with the AUTHREQ message. The ANSI-41 G-MSC returns a message (unsolres) Unsolicited Response Return Result 176 to the ANSI- • 10 41 S-MSC 55. After having identified the pending transaction according to ANSI-41, the G-MSC 42b ANSI-41 follows its response to the UNSOLRES message received by sending a Routing Request Return Result message 177 (routreq) to VLR 42a according to 7? NSI-41 and includes the TLDN. He ANSI-41 VLR sends a routreq message to ANSI-41 HLR / AC 43 and includes the TLDN. ANSI-41 HLR / AC, in turn, sends a message • 179 of Localization Request Return Result (locreq) to 0-MSC 54 according to ANSI-41 and includes the TLDN. He ANSI-41 O-MSC then makes a call at 181 to the S-MSC 55 according to ANSI-41 in the PSTN network using the TLDN. Upon receiving the call for the selected TDLN, the ANSI-41 S-MSC sends an Alert 182 message to the M-ES 51 in the DCCH. The M-ES answers the call, and in 183 a voice path back to the O-MSC 54 according to ANSI- 41. The S-MSC 55 according to ANSI-41 treats the Unsolicited Location Response as the equivalent of a record and sends a message to Invoke REGNOT 184 to the ANSI- 41 HLR / AC • 43. The ANSI-41 HLR / AC sends a REGCANC 185 message to the ANSI-41 5 G-MSC 42b that clears the MSID record according to ANSI-41 associated. The G-MSC according to ANSI-41 sends an MSID message gone 186 to GPRS-VLR IWF, 37 to remove the associated MSID record. The GPRS-VLR IWF 37 sends a message from Suspend 187 to SGSN 32 which flags the associated IMSI as available for • 10 data packet service. The SGSN acknowledges the receipt of the Suspend message by sending an Suspend 188 Akc to GPRS-VLR I F. The GPRS-VLR IWF responds by sending an MSDI Sent Reply 189 to ANSI-41 G-MSC 42b. The G-MSC according to ANSI-41 then confirms receipt of the message REGCANC 185 through the return of a Record Cancellation Refund Result (regcanc) message 191 to ANSI-41 HLR / AC 43. The ANSI-41 HLR / AC then responds to the REGNOT 184 message by returning a 192 Return Result message of Registration Notice (regnot) 192 back to S-MSC 55 according to ANSI-41. FIGURE 11 is a message flow diagram illustrating the flow of signaling messages between the nodes of the integrated network of Figure 5 when a Short Message Service (SMS) message is received for a Class D M-ES in STANDBY state. Note: Communications between ANSI-41 G-MSC 42 and GPRS-VLR I F 37 are shown using dashed lines to indicate that the message does not need to follow the ANSI-41 or GSM MAP formats. The names are presented in italics and • generic, not following any existing standard 5 message name. In 201, an M-ES Class D is camped on a PCCH served by SGSN 32. It has already successfully performed a GPRS Fixing procedure and has therefore received TLLI assignment. An ANSI-41 Message Center (MC) 56 receives and accepts a • 10 Point-to-Point Short Message Delivery (SMDPP) 202, requesting delivery of an SMS message to an SME with M-ES base, destination SME 51. The source of the SMS message is ANSI-41 origin SME (0-SME) 57 The ANSI-41 responds with a Return Result SMDPP (s dpp) 203 since it is required to positive recognition to ANSI-41 O-SME. If ANSI-41 MC does not have a current temporary SMS routing address or status for the SME based on M-ES to which it is addressing, • sends an SMS Request message 204 (SMSREQ) to the HLR 43 according to ANSI-41 associated with the SME based on M-ES. Without However, if ANSI-41 MC does not have a current temporary SMS routing address or status for the SME based on M-ES to which it is addressing, the process jumps to step 208. In the case in which the SME of destination is a camping M-ES in a PCCH, and in the case in which only the identity of G-MSC / VLR is required, the process jumps to step 207. In the case in which the destination SME is encamped in PCCH, and when the current temporary SME routing address and status are required, the following 5 conditions apply: (1) If the ANSI-41 HLR has no current temporary SMS route address and the status for the M-ES based SME, it sends the SMREQ message in 205 to ANSI-41 G-MSC / VLR 42 associated with the base M-ES SME. The ANSI-41 G-MSC / VLR answers in 206. • 10 (2) If ANSI-41 HLR has current temporary SMS route address and status for the temporary M-ES base SME the process jumps to step 207 where ANSI-41 HLR sends a smreq of ANSI-response message 41 MC 56. The ANSI-41 G-MSC / VLR 42 responds by sending a smreq message 206 containing the temporary SMS route address for the base SMS M-ES served to ANSI-41 HLR 43. The ANSI-41 HLR sends the smreq containing the temporary SMS route address for • the M-ES base SME served to ANSI-41 MC 56. ANSI-41 MC sends a SMDPP 208 message to the destination SME using the temporary SMS routing address for the SME based on M-ES. The SMDPP is received by ANSI-41 G-MSC / VLR 42 associated with the SME based on destination M-ES. The SMDPP is removed from all the header information, and only the SMS payload is retained. The ANSI-41 G-MSC / VLR then sends a message (SMS delivery) 209 to GPRS-VLR I F 37, which contains the SMS payload and the address of M-ES's. GPRS-VLR IWF sends a Forward Short Message 211 containing the SMS payload to the SGSN 32 serving the M-ES 51. In order for the SMS payload originating from the ANSI-1 network to be understood by the GPRS destination network, the ANSI-41 character is set and another SMS integrity payload must be understood by the GPRS network which understands GSM character sets. In the present invention, the character sets are preferably as defined in the ANSI-41 / IS-136 standards, and the M-ES Class D displays these character sets. The GPRS nodes simply transmit the SM payload between the ANSI-41 network and the M-ES base SME. The payload size between GPRS and ANSI-41 for short messages must also be aligned. Currently, SMS Ported Data is theoretically limited to a maximum of 212 octets in length. In addition, the SMS Teleservice overdraft is 10 octets. Additionally, ANSI SS7 has an overdraft of 50 octets. In total, the absolute maximum limit of the entire SS7 TCAP message is 272 octets, due to the SS7 limitation. (Actually, the SMS Bearer Data can span between 129 and 175 uplink octets and 117 to 175 downlink bytes). The GPRS Short Message payload may be greater than 212 bytes, therefore, a shorter limit may be set on the short message lengths according to GPRS. Additionally, the SMS teleservice identifier may require transformation-translation. The teleservice identifier is an example of an SMDPP parameter which is required to be transformed to an IS-136 R-DATA message. These parameters also require transformation between ANSI-41 and the GPRS network. At 212, the SGSN 32 transfers a short message to M-ES 51 in the LLC layers. The SGSN returns a Short Message Sending Result message 213 to GPRS-VLR IWF 37 indicating the successful delivery of SM. The GPRS-VLR IWF sends an SMS 214 delivery message to ANSI-41 G-MSC / VLR 42, indicating successful delivery of the SMS payload to the M-ES destination. The ANSI-41 G-MSC / VLR returns a positive acknowledgment SMDPP 215 to ANSI-41 MC 56 which is the source of the corresponding SMDPP. An SMS input message with the M-ES in the READY state is handled in the same manner as shown in FIGURE 11. FIGURE 12 is a flow chart illustrating the flow of signaling messages between the nodes of the integrated network of Figure 5 when an M-ES is READY state initiates a Release procedure. The detach function allows a Class D M-ES to inform the network that when a GPRS and / or a Detached MIN is desired, and allows SGSN to report to an M-ES that has been detached and allows the SGSN to M-ES that GPRS has been released through the network. The different types of Detached are Released MIN (only initiated by M-ES), Detached GPRS and Detached combined GPRS / MIN (initiated only by M-ES). If M-ES wants to make GPRS detached, but wants to remain fixed MIN, can perform a GPRS Unplug, or can perform a GPRS / MIN Unbundling and return to DCCH and do a DCCH Register as specified in ANSI-41 in order to Attach to ANSI-41 S-MSC. The M-ES can be detached from GPRS either explicitly or implicitly. In the explicit Unclaimed: the SGSN or M-ES explicitly requests the Unprepared. In an implicit Unclamp, there is a logical link, and either a STANDBY time expires indicating the lack of activity, or an irrevocable radio error occurs causing the logical link to be disconnected. In the explicit Disclaimer, a Release Request (with TLLI and Cause) is sent by SGSN to the M-ES or by M-ES to the SGSN. The M-ES can do a MIN Detach in one of two ways depending on whether it is set to GPRS or not. First, an M-ES set to GPRS sends a Request for Unseen SGSN, indicating a Disappeared MIN. This can be done in combination with a Destroyed GPRS. The Request for Detachment message indicates whether or not the detachment is due to a shutdown. This information is necessary to determine whether or not a Release Request message must be returned. In the Disengage Request message originated by SGSN there may be an indication for M-ES that it is required to initiate GPRS Fixation and an Activation PDP Context for the previously activated PDP contexts. Second, an M-ES not fixed to GPRS makes a Fixed 5 MIN as defined in ANSI-41. With reference to Figure 12, a Release procedure is initiated by M-ES and is illustrated. In 221, M-ES is released by sending a Release Request (with TLLI, Type of Unattached and Off) to SGSN 32. The Type of • 10 Unseen indicates what type of Unseeded should be carried out (being that, Unleashed GPRS alone, Unleashed MIN alone or Unleashed combined GPRS / MIN). Off indicates whether the Unattached is due to a power down situation. If the type of Detached is a detached GPRS, the SGSN sends a PDP Context Request Delete 222 (with TID) to GGSN 33 in order to disable active PDP contexts in the GGSN associated with a particular M-ES. The GGSN accuses with a • PDP Context Response Delete 223 (with TID). If the type of Detached is a Detached MIN, the SGSN 32 sends a Release Statement MIN 224 (with IMSI) to GPRS-VLR IWF 37. The GPRS-VLR IF translates IMSI to MIN and sends a Retired Message 225 to ANSI-41 G-MSC 42. The G-MSC according to ANSI- 41 sends a message of MS Inactive (MSINACT) 226 to HLR / AC 43 according to ANSI-41, which then marks the M-ES no available for service. The ANSI-41 HLR / AC 43 sends a message (msinact) Result of Inactive Return 227 to ANSI-41 G-MSC. The ANSI-41 G-MSC sends a Withdrawal Acknowledgment message 228 to GPRS-VLR IWF. If M-ES 51 wishes to remain set MIN and is doing GPRS Disengaging, the SGSN 32 sends a Disengage Indication message 229 (with IMSI) to GPRS-VLR I F 37. The GPRS-VLR IWF removes the association with the SGSN. The M-ES then passes to the DCCH and makes a DCCH Register in accordance with that specified in ANSI-41 in order to be fixed with the S-MSC according to ANSI-41. If Disconnection indicates that the detachment is not due to a disconnection situation, the SGSN 32 sends a Release Acceptance message 231 (with TLLI) to M-ES 5 1. If M-ES remains MIN Fixed and is doing a GPRS Detachment , M-ES returns to DCCH and makes a DCCH 232 Register as specified in ANSI-41 in order to set to ANSI-41 S-MSC. The Detach MIN procedure is mutually exclusive to the procedure for GPRS Fix / Stay Fixed MIN. Therefore, the following sequences of the steps shown in FIGURE 10 can be carried out for different types of Detached. For a Detached MIN, steps 221, 224 to 228 and 231 are carried out. For Released GPRS, steps 221 to 223 and 229 to 232 are carried out. For a GPRS / MIN Compounder Unselected (off), steps 221 to 228 are carried out.

Table 5 below provides additional information for the Gx interface. Message / element of meaning comment Information Receding a sent message from separation GPRS-VLR IWF to G-MSC according to ANSI-41 to indicate a MIN separation of M-ES Separation receive acknowledgment Table 5 When the procedure Descending by SGSN 32, the procedure is the same as shown in Section 6.1.6.2 of GSM 03.60. FIGURE 13 is a flow chart illustrating the flow of signaling messages when a Class D M-ES in the CONVERSATION state initiates a call disconnection while on a Digital Traffic Channel. A Class D M-ES in the CONVERSATION state which initiates a call disconnection while in DTC, tunes to a PCCH, performs a location update procedure and then enters a STANDBY state. In 241, an M-Es Class D is in the CONVERSATION state in DTC.

The SGSN 32 has received a SUSPEND message (not shown) as a result of an M-ES that is served by the ANSI-41 infrastructure. Therefore, the M-ES is not • receiving any data packet transaction. On 242, 5 either M-ES or ANSI-41 S-MSC 55 disconnects the call. The M-ES finds a DCCH at 243 and reads the BCCH information there. If the M-ES wants a packet data service, the packet data service is supported using a modulation scheme suitable for M-ES, the M-ES reads information from • 10 orientation PCCHs to determine where the packet data service is available. The M-ES then tunes the orientation PCCH to 244 and reads the P-BCCH information there. If the M-ES is not in its assigned PCCH, it tunes to its assigned PCCH and reads P-BCCH. In 245, the M-ES sends a Route Area Update Request to initiate the location update as previously described (this being, Intra-SGSN Route Update or Inter-SGSN Route Update). Following the completion of the location update, the M-ES remains once again available for both data packet service and circuit switched service. It is believed that the operation and construction of the present invention will be apparent from the foregoing description. While the system and method shown and described have been characterized as preferred, it is readily apparent that various changes and modifications can be made to the present invention without departing from the scope of the invention described in the following claims. • 10 15 • 20 25

Claims (13)

1. CLAIMS An integrated radio telecommunication network which integrates a circuit switched network according to ANSI-41 and a packet data network according to the General Packet Radio Service (GPRS), said integrated radio telecommunications network comprising: a mobile switching center ( MSC) in the ANSI-41 network that provides circuit switching services to a mobile station which operates both in ANSI-41 network and in GPRS network; a switching node (SGSN) serving GPRS in the GPRS network providing switched data packet services to the mobile station; an interconnection function that interfaces to MSC with SGSN, said interconnection function transforms the switched signaling used in MSC into GPRS packet switched signaling used by SGSN, and transforms the GPRS packet switched signaling into circuit switched signaling; a GPRS interworking base station controller providing an SGSN interface with a GPRS / ANSI-136 base station which supports both ANSI-136 operations and GPRS operations, said interworking GPRS base station adapts a signaling format used by SGSN in air interface signaling format, and passes the traffic signaling between SGSN and the GPRS / ANSI-136 base station; and • means to transparently transfer ANSI-136 information between the mobile station and the ANSI-41 network by adding ANSI-136 information to the selected GPRS messages.
2. The integrated radio telecommunications network of Claim 1 wherein the ANSI-136 information • W 10 that is added to selected GPRS messages includes registration and authentication information.
3. The integrated radio telecommunications network of Claim 2 wherein the registration and authentication information includes an Identification Number 15 Mobile (MIN), an Electronic Serial Number (ESN) and an ANSI-41 Authentication Response.
4. 4. The integrated radio telecommunications network of Claim 1 wherein the selected GPRS messages to which the information is aggregated 20 ANSI-136 includes a Sending Request message which is sent from the mobile station to SGSN during the GPRS Fix procedure, and a Location Update Request which is sent from SGSN to the interconnection function that gives 25 interface between MSC and SGSN.
5. The integrated radio telecommunications network which integrates an ANSI-41 switched circuit network and a packet data network of the General Packet Radio Service (GPRS), said integrated radio telecommunications network comprises: a Class D mobile station which operates both only on 30 kHz channels in both the ANSI-41 network and the GPRS network; a mobile switching center (MSC) in the network # 10 ANSI-41 providing circuit switched circuit services to the mobile station; a service GPRS switching node (SGSN) in the GPRS network that provides packet switched services to the mobile station; 15 an interconnection function that interfaces to MSV with SGSN, this interconnection function transforms the circuit switching signaling used • by MSC in packet switching signaling used by GPRS, and transforms the signaling 20 switched GPRS packet in circuit switched signaling; and an interconnection GPRS base station controller that interfaces to SGSN with the GPRS / ANSI-136 base station which supports operations 25 ANSI-136 and GPRS operations, said interconnected GPRS base station adapts a signaling format used by SGSN in the air interface of signaling format and passes traffic of • Signaling between SGSN and the base station GPRS / ANSI-136.
6. The integrated radio telecommunications network of Claim 5 wherein the Class D mobile station is camping in a packet control channel (PCCH) as its normal mode of operation and only changes to a • 10 digital control channel (DCCH) at power-up, when establishing a voice call and when unhooking from GPRS.
7. The integrated radio telecommunications network of Claim 5 wherein the mobile class station 15 D is equipped with an International Mobile Station Identification (IMSI) that is used in the GPRS network.
8. 8. The integrated radio telecommunications network of claim 7 wherein the function of The interconnection includes means for translating the Mobile Identification Number (MIN) of the Class D mobile station used in the ANSI-41 network into an associated IMSI used in the GPRS network.
9. The integrated radio-telecommunications network of the Claim 8 comprising adepts: a GPRS Address Registration (GPRS HLR) in the GPRS network which authenticates the Class D mobile station for packet purposes • of data; and 5 an ANSI-41 authentication address / home location register in the ANSI-41 network authenticating the Class D mobile station for circuit switching purposes.
10. 10. The integrated radio-telecommunications network of the • Claim 9 further comprising a Class E mobile station which operates only over 30 kHz channels, and only in the GPRS network, said Class E mobile station encamps in a packet control channel (PCCH) as its mode normal operation and only 15 switches to a digital control channel (DCCH) at power up to verify the availability of data packet service.
11. 11. The integrated radio telecommunications network of Claim 10 wherein the mobile station of Class E is equipped with an IMSI, and the GPRS HLR includes means for authenticating the Class E mobile station. The integrated radio telecommunications network of Claim 5 further comprising means for 25 operating the Class D mobile station on one or more channels of enhanced data rates for GSM Evolution (EDGE) for data packet service. The integrated radio telecommunications network of Claim 5 further comprising means for moving the operation of the Class D mobile station from 30 kHz channels to one or more channels of enhanced data rates for GSM Evolution (EDGE). • The integrated radio telecommunications network of claim 13 further comprising means for moving the operation of the Class D mobile station from enhanced data rate channels for GSM Evolution (EDGE) to the 30 kHz channels. fifteen • twenty 25 SUMMARY OF THE INVENTION An integrated radio telecommunications network is presented which integrates an ANSI-41 switched circuit network and a • 5 Packet Radio General Service (GPRS) packet data network to support a mobile station that operates in both the ANSI-41 network and the GTRS network. An interconnection function (37) interconnects a mobile switching center (MSC) (23) in the ANSI-41 network with a service GPRS switching node (SGSN) (32) in 10 the GPRS network by transforming a circuit switched signaling used by the MSC into a packet switched signaling according to GPRS used by the SGSN, and by transforming the switched signaling of GPRS packets into signaling 15 switched circuits. An interworking GPRS base station controller (39) interconnects the SGSN with a GPRS / ANSI-136 base station (26) that supports ANSI-136 type operations and also GPRS type operations. The GPRS base station controller of The interconnection adapts the traffic signaling format used by the SGSN in an air interface traffic signaling format employed by the GPRS / ANSI-136 base station. An authentication center interface (Fl) passes the status of 25 authentication of the mobile station between an ANSI-41 authentication authenticating address / authentication registry (HLR / AC) (21) in the ANSI-41 network, and a GPRS address location registration / authentication center. • Authentication (HLR / AUC) (31) in the GPRS network. •