FR3003424A1 - CELLULAR NETWORK SYSTEM WITH DUAL IDENTIFIER MULTI-SERVICE SIM CARD - Google Patents

Abstract

The invention relates to a mobile system registered in a set of networks with a dual ID SIM card. The first of the two identifiers of the SIM card is called 'IMSI switching-of-circuit'. With the circuit-switched IMSI a subscriber who registers to a first visited network may consume any circuit-switched mobile telephony service (such as voice, SMS, etc.) available in that network. two identifiers is called 'IMSI switching-of-packet' With the 'IMSI switching-of-packet' a subscriber who registers to a second visited network can consume any mobile packet-switched service (such as internet connection, The invention relates to a device enabling the subscriber to: • Consume mobile communications services at optimized prices according to the types of services requested (circuit-switched, packet-switched) • Have only one telephone number The device according to the invention is particularly intended for subscribers traveling internationally.

Description

Field of the Invention: The present invention relates to a system of mobiles registered in a set of networks with a dual SIM card (called SIM card 'Double-IMSI').

Throughout the description, the abbreviations defined hereinafter and in the glossary will be used. The first of the two identifiers of the SIM-IMS1 'SIM card is called' IMSI switching-of-circuit 'referenced IMSI.

The identifier IMSIcs allows a subscriber to register to a PLMN network referenced PLMNcs. With the IMSI identifier, the subscriber can consume any circuit-switched mobile telephony service (such as voice, SMS, etc.) available in PLMNcs. A cellular operator is responsible for the operation and operation of the PLMNcs: he possesses the necessary equipment to operate the PLMNcs network and to control the IMSIcs of his subscribers. The PLMNcs network may be the home network of the subscriber; in this case, it will be referenced HPLMNcs The PLMNcs network may also be a visited network, which is used by the subscriber temporarily, for example 20 in case of roaming; in this case, the network will be referenced VPLMNcs. Regardless of the (home or visited) attribute of the PLMNcs network, it will be possible for the subscriber to consume any circuit-switched mobile telephony service once the IMSIcs identifier is authenticated and authorized on the PLMNcs network. The second of the two identifiers of the dual SIM card IMS1 'is called' IMSI switching-of-4a 'referenced IMSIps. The IMSIps identifier allows a subscriber to register to a PLMN network referenced PLMNps. With the IMSIps identifier, the subscriber can consume any packet switched mobile service (such as internet connection, email, etc.) available in PLMNps. A cellular operator is responsible for the operation and operation of the PLMNps: he has the necessary equipment to operate the PLMNps network and to control the IMSIps of his subscribers.

The PLMNps network may be the home network of the subscriber; in this case, it will be referenced HPLMNps. The PLMNps network can also be a visited network, which is used by the subscriber temporarily, for example in case of roaming; in this case, the network will be referenced VPLMNps Regardless of the attribute (domestic or visited) of the PLMNps network it will be possible for the subscriber to consume any mobile packet-switched service once the IMSIps identifier is authenticated and authorized on the PLMNps network.

Several configurations are possible for PLMNcs and PLMNps network operations According to a non-limitative list: A single mobile operator can be responsible for authentication and authorization of IMSI 'IMSI' and 'IMSIps'. In this case, the operator is responsible for the operation of the PLMNIcs and PLMNps networks. Typically, only one integrity key KI is used in correspondence of the two IMSIs. Two different mobile operators may be responsible for the authentication and authorization of IMSI 'IMSIcs' and 'IMSIps' respectively. In this case, two operating modes are possible: o The two mobile operators can delegate a third party operator (usually called "Full MVNO" or "Ungrouped Operator") for authentication and authorization of IMSI 'IMSIcs' and 'IMSIps' . In this case, the third-party operator has entered into an agreement with the two operators in order to obtain the rights to use the two PLMNcs and PLMNps networks. This implies that the third-party operator is responsible for generating and using a single KI integrity key. o Each of the two operators is responsible for - respectively - the authentication and authorization of IMSI 'IMSI' and 'IMSIps'. Each operator therefore acts - in principle - independently. This case is more complicated because two K1 integrity keys will be generated by each respective operator. It is also necessary for both operators to be able to approve IMSI change policies (that is, to switch from 'IMSI' to 'IMSIps' or vice versa): generally, these policies are implemented by applications (or "applets") encoded on the SIM card. In the remainder of the description, in order to simplify the exposure of the implementation techniques, reference will be made to the case of a single mobile operator or of a third operator of the "Unbundled Operator" type; in both cases, we will speak generically of OPERATEURcs_ps. These two cases are equivalent to operational procedures. Any expert in the art will recognize that operational procedures and features can be easily generalized to the case of the two autonomous operators. With the dual-IMS1 'SIM card provided by the OPERATORcs_ps a subscriber can: Consume circuit-switched mobile telephony services (such as voice, SMS, etc.) available in any PLMNcs (home or visited), through using the identifier 'IMSIcs'. Consume mobile packet-switched services (such as internet connection, email, etc.) available in any PLMNps (domestic or visited), through the use of the identifier 'IMSIps'. In general, PLMNcs and PLMNps can be different even in the same country (domestic or visited). It is therefore possible for the OPERATEURcs_ps to offer optimized prices, depending on the type of mobile service consumed by the subscriber and - in the case of roaming the subscriber - according to the roaming agreements with the operators of the 25 networks visited VPLMNcs and VPLMNps respectively Organization of PLMNcs and PLMNps networks As a service provider in the subscriber's home country, the OPERATORcs-ps owns and operates the equipment necessary for the operation of the HPLMNcs and HPLMNps home networks. Each subscriber to the system according to the invention corresponds to: an 'IMSI switching-of-circuit' (IMSIcs), corresponding to the network HPLMNcs. - An 'IMSI switching-of-packet' (IMSIps), corresponding to the HPLMNps network. According to the description of the embodiments of the invention (description to be made later) the subscriber will have 'differentiated' communication rates depending on the type of mobile service consumed and regardless of the country (domestic or visited). In particular, in the case of the roaming subscriber: If the subscriber wishes to consume any circuit-switched mobile telephony service (such as voice, SMS, etc.), the IMSIcs will be activated and allow him to use the circuit switched equipment available in the visited network VPLMNcs. If the subscriber wishes to consume any mobile packet-switched service (such as internet connection, email, etc.), the IMSIps will be activated and allow him to use the packet-switched equipment available in the visited network VPLMNps. In practice, it is important to differentiate between a subscriber in his home country and a roaming subscriber. In the home country of the subscriber, the Operators offer mobile packages with advantageous rates for all the services, whether circuit-switched or packet-switched. By way of example, in the system according to the invention, the OPERATORcs_ps is French. Any subscriber who consumes mobile telephony services in France can benefit from advantageous rates and / or package on a single HPLMN home network and with a single and unique IMSI identifier for his SIM card. The distinction between HPLMNcs and HPLMNps is - therefore - purely functional. In this case, there is no need to distinguish between IMSIcs and IMSIps. In other words, for a subscriber in France IMSIps = In the remainder of the description, the HPLMNcs connotation will be used to indicate the features and equipments of the HPLMN network that provide the circuit switched services. Similarly, the HPLMNps connotation will be used to indicate the features and equipment of the HPLMN network that provide the packet switched services.

In an exemplary context a roaming subscriber in Hong Kong can consume mobile services on the visited network belonging to the local operator `CSL 'or that owned by the local operator' China Mobile HK '. However, it is possible that: The roaming agreements between the OPERATEURcs-ps and its Hong Kong counterpart `CSL 'could allow the subscriber to have a good price for circuit-switched services (and lower prices for packet switched services). Vice-versa, the roaming agreements between the OPERATEURcs-ps and its Hong Kong counterpart 'China Mobile HK' could allow the subscriber to have a good price for packet-switched services (and lower prices for circuit switched services). In the system according to the invention (and in the exemplary context considered) 15 the roaming subscriber in Hong Kong will be able to benefit at the same time: - Roaming agreements between the OPERATEURcs_ps and its Hong Kong counterpart `CSL 'for services circuit-switched through the use of the IMSI switching-circuit '(IMSIcs). Roaming agreements between the OPERATORcs_ps and its Hong Kong counterpart 'China Mobile HK' for packet switched services through the use of IMSI packet-switching '(IMSIps). STATE OF THE ART The system according to the invention can be implemented in the 'domestic' country of the subscriber and / or in a visited country. In practice, the system will be used more advantageously in a visited country, that is to say, when a subscriber is in a situation known as international roaming. Calls from and / or to a mobile phone, as well as the communications given, are known to be expensive in an international roaming situation. In order to lower the cost of this type of communication, many international travelers choose to change the SIM card ("Subscriber Identity Module") and replace it with a SIM card specific to the cellular networks of the country in which they have just arrived. However, although this practice is a source of savings, it has the disadvantage of changing the number of the owner of the mobile phone, and make it "unreachable" or "unidentified" for its usual correspondents. There are already systems with two (or more) SIM cards: a 'nominal' SIM card and one or more 'auxiliary' SIM cards (patent EP 1942695 AI); the subscriber will use the 'nominal' SIM card or an 'auxiliary' SIM card depending on its geographical location or economic considerations. In the patent cited the subscriber keeps - in all cases - his mobile number. There are also systems whereby one (or more) network operator (s) VPLMN allocates (allocates) one or more IMSIs to the operator of an HPLMN to provide these HPLMN subscribers with IMSI SIMs. 'and `Multi-MSISDN': these subscribers will be able to benefit from local rates in each VPLMN network whose IMSI is part of the SIM` Multi-IMSI '. According to the patent WO 2005/018245 A2 a signaling gateway operating between the different GMSCs of each operator 20 (VPLMN or HPLMN) allows the realization of the invention. The concepts set forth in WO 2005/018245 A2 can be applied only if each operator (VPLMN or HPLMN) has control of its own IMSI, i.e., whether it is MNO or 'Full MVNO'. No distinction is made on the nature of the services consumed; in other words, the concept of differentiating between 'IMSI switching-of-circuit' (IMSIcs) and 'IMSI switching-of-packet' (IMSIps) is not introduced. The first claim of US Pat. No. 7640038 states that a SIM card may at the same time contain an IMSI and an IP address in order to allow simultaneous connection to a cellular network and to an Internet network, in particular of the 'Wireless Local Area Network' type. WLAN "). Unlike the present invention, the concept of 'IMSI switching-of-circuit' (IMSIcs) and 'IMSI switching-of-packet' (IMSIps) is not introduced. Among the `3GPP 'standards, the technical specifications such as 3GPP TS 23.122 or 3GPP TS 25.331 describe the operations of' Shared networks': several PLMNs share the same access network (whether it is of type 2G, 2.5G, 3G or 4G). The identifier of the different PLMNs is broadcast on the beacon channel (BCCH) so that a mobile phone can select the most appropriate PLMN according to the policies of its original operator.

The registration on the selected PLMN is done with a single IMSI: the concept of 'IMSI switching-of-circuit' (IMSIcs) and 'IMSI switching-package' (IMSIps) is not introduced. Cellular systems operating according to the IP Multimedia Subsystem (IMS) architecture provide that a mobile phone, compatible with the IMS functionalities, can consume circuit-switched services thanks to a traditional architecture (2G or 3G) and services. with packet switching thanks to the 'IMS' architecture, as explained in 3GPP TS 24.301. Simultaneous recording on both architectures is done with a single IMSI: the concept of 'IMSI switching-of-circuit' (IMSIcs) and 'IMSI switching-of-packet' (IMSIps) is not introduced. Advantages of the invention (subscribers side) In roaming, the system according to the invention makes it possible to differentiate and optimize the costs of mobile services according to their nature (circuit or packet switching). Advantages of the invention (OPERATORcs-Ps side) The OPERATORcs_ps can negotiate with other operators separate roaming agreements for circuit and packet switched services, respectively. Depending on the volume and type of traffic estimated in each country visited, OPERATEURcs_ps has a very high flexibility in the choice of networks visited and the operators who control them. SUMMARY OF THE INVENTION The present invention relates to a mobile system registered in a network with a SIM card belonging to an HPLMN network and containing: a first identification code IMSIcs which allows access to any switching communication service circuit, such as the mobile phone service. A second IMSIps identification code that allows access to any packet-switched communication service, such as the mobile Internet or email service. This mobile system operates - in particular - in a roaming situation using: - The first identification code IMSIcs allowing registration, authentication and location in a visited network VPLMNcs belonging to a first operator who has roaming agreements with the OPERATORcs_ps of the HPLMN network for circuit-switched communication services only. - The second identification code IMSIps allowing - at the same time - the recording, authentication and location in a visited network VPLMNps belonging to a second operator that has roaming agreements with the OPERATEURcs-Ps HPLMN network for packet switched communication services only.

In particular, the dual-1MS 'SIM card (IMSIcs, IMSIps) contains the following functional elements: - A first file structure of the electrical profile, these files being dedicated to operations management (mobility, authentication, authorizations, etc.) in a visited network VPLMNcs in correspondence of the first identification code IMSIcs. A second file structure of the electrical profile, these files being dedicated to the management of operations (mobility, authentication, authorizations, etc.) in a visited network VPLMNps in correspondence of the second identification code IMSIps. - A third file structure of the electrical profile, these files containing information independent of IMSIcs and IMSIps identification codes. This information includes the subscriber's telephone number, the parameters for managing short messages, and so on. - The set of parameters and procedures for performing authentication operations, generation of encryption keys and encryption. Among these parameters is the integrity key (K1). A table containing as many lines as the number of countries in which a subscriber of the system according to the invention can go, each line of the table containing - for each country visited - the list of VPLMNcs networks which have roaming agreements for circuit switched communication services only, the list of VPLMNps networks which have roaming agreements for packet-switched communication services only, the first IMSIcs identification code allowing the recording, authentication and the location in the visited networks VPLMNcs, the second identification code IMSIps allowing registration, authentication and location in the visited networks VPLMNps. An application software that manages the use of IMSIcs and IMSIps identification codes according to the data of the table described above.

In particular, said identification codes IMSIcs and / or IMSIps can belong to the OPERATEURcs_ps of the HPLMN network or to other operators that have roaming agreements with the operators of the visited networks VPLMNcs and VPLMNcs and - at the same time - interconnection agreements with the OPERATORcs-ps of the HPLMN network.

The system according to the invention provides simultaneous recording procedures of a mobile system with a first identification code IMSIcs allowing registration, authentication and location in a visited network VPLMNcs for the only communication services to circuit switching and with a second identification code IMSIps allowing the recording, authentication and location in a visited network VPLMNps for the only packet switched communication services according to the following steps: - Once the communication link established with the SIM card and the PIN entered by the subscriber and verified by the phone, the latter reads the IMSIcs and IMSIps identification codes contained in the SIM card. - A cell selection process is triggered by the mobile phone to know the country visited. - The mobile phone starts an application software contained in the SIM card; the application software takes control of the operations by triggering the following steps: o Reading a table hosted by the SIM card and containing as many lines as the number of countries in which a subscriber can go, each line of the table containing - for each country visited - the list of VPLMNcs networks whose operators have roaming agreements for circuit-switched communication services only, the list of VPLMNps networks whose operators have roaming agreements for the services only packet-switched communication, a first identification code IMSIcs and a second identification code IMSIps, the identification code IMSIcs (respectively IMSIps) belonging to the OPERATEURcs-ps of the HPLMN network or to any other operator which has roaming agreements with network operators VPLMNcs (respectively VPLMNps) and - at the same time - interconnection agreements with the OPERATEURcs-ps of the HPLMN bucket. o The selection of the IMSIcs and IMSIps identification codes corresponding to the country visited o The writing of the IMSIcs and IMSIps identification codes selected in the corresponding files that form part of the SIM card's electrical profile. o Sending the REFRESH 'command to the mobile phone to alert it of the change in content of the SIM card files that store IMSIcs and IMSIps identification codes. - The mobile phone resumes control of the operations by triggering the following steps: o A cell selection process is started again by the mobile phone to identify a cell belonging to a VPLMNps network that is not prohibited. o Once a cell belonging to a non-prohibited VPLMNps network is identified, the registration, authentication and location procedures are started using the IMSIps identification code. At the end of these procedures, the subscriber can consume any packet switched service on the visited network VPLMNps. o A second cell selection process is triggered by the mobile phone to identify a cell belonging to a VPLMNcs network that is not prohibited. o Once a cell belonging to a non-prohibited VPLMNcs network has been identified, the procedures for registration, authentication and localization are started using the IMSIcs identification code. At the end of these procedures, the subscriber can consume any switched service. circuit on the visited network VPLMNcs. According to an advantageous characteristic of the invention, the procedures for recording, authentication and localization on the visited network VPLMNps comprise the steps which consist in: - sending a signaling message `GMM_ATTACH_REQUEST 'from the mobile telephone to the SGSN service node of the visited network VPLMNps which controls the cell in which the mobile phone is located. The message `GMM_ATTACH_REQUEST 'contains the IMSIPS identification code. - Sending a `MAP_SEND_AUTHENTICATION_INFO 'signaling message from the SGSN service node to the subscriber's HPLMN primary location register (HLR). The message `MAP_SEND_AUTHENTICATION_INFO '30 contains the IMSIps identification code. - Sending a `MAP_SEND_AUTHENTICATION_INFO_ACK 'signaling message from the subscriber's HPLMN primary location register (HLR) to the SGSN service node of the visited network VPLMNps. The message `MAP_SEND_AUTHENTICATION _INFO_ACK 'contains the identification parameters to enable the SGSN service node to authenticate the mobile phone. - The sending of a authentication request `GMM_AUTHENTICATION_AND_CIPHERING_REQUEST 'from the SGSN service node of the visited network VPLMNps to the mobile phone. The message `GMM_AUTHENTICATION_AND_CIPHERING_REQUEST 'contains the parameters necessary for the mobile phone to trigger the encryption key authentication and calculation algorithm. - The sending of a signaling message `GMM_AUTHENTICATION_AND_CIPHERING_RESPONSE 'from the mobile phone to the SGSN service node of the visited network VPLMNps. The message `GMM_AUTHENTICATION_AND_CIPHERING_RESPONSE 'contains the response to the authentication request. This response allows the SGSN service node to verify the identity of the mobile phone. - The sending of a MAP UPDATE GPRS LOCATION signaling message from the SGSN service node of the visited network VPLMNps to the home location register (HLR) of the subscriber's HPLMN network. The MAP UPDATE GPRS LOCATION message contains the IMSIps identification code. - The sending of a signaling message `MAP_INSERT_ SUBSCRIBER DATA 'from the subscriber HPLMN main location register (HLR) of the subscriber to the SGSN service node of the visited network VPLMNps. The message `MAPINSERT_SUBSCRIBER_DATA 'contains access permissions to the visited network VPLMNps, including access to only packet-switched services. - The sending of a signaling message `GMM_ATTACH_ACCEPT 'from the SGSN service node of the visited network VPLMNps to the mobile phone. The message `GMM_ATTACH_ACCEPT 'contains the temporary identification code P-TMSIps, valid for triggering any packet-switched communication initiated by the mobile phone. According to another advantageous characteristic, the procedures for recording, authentication and localization on the visited network VPLMNCS comprise the steps which consist in: - sending a signaling message `GMM_ATTACH_REQUEST 'from the mobile telephone to the SGSN service node visited network VPLMNCS which controls the cell in which the mobile phone is located. The message `GMM_ATTACH_REQUEST 'contains the identification code lMSl. - Sending a `MAP_SEND_AUTHENTICATION_INFO 'signaling message from the SGSN service node to the subscriber's HPLMN primary location register (HLR). The message `MAP_SEND_AUTHENTICATION_INFO 'contains the IMSIcs identification code. - Sending a `MAP_SEND_AUTHENTICATION_INFO_ACK 'signaling message from the subscriber's HPLMN home location register (HLR) to the SGSN service node of the visited network VPLMNcs. The message `MAP_SEND_AUTHENTICATIONINFO_ACK 'contains the identification parameters to enable the SGSN service node to authenticate the mobile phone. - The sending of a authentication request `GMM_AUTHENTICATION_AND_CIPHERING_REQUEST 'from the SGSN service node of the visited network VPLMNcs to the mobile phone. The message `GMM_AUTHENTICATION_AND_CIPHERING_REQUEST 'contains the parameters necessary for the mobile phone to trigger the encryption key authentication and calculation algorithm. - The sending of a signaling message `GMM_AUTHENTICATION_AND_CIPHERING_RESPONSE 'from the mobile phone to the SGSN service node of the visited network VPLMNcs. The message `GMM_AUTHENTICATION_AND_CIPHERING_RESPONSE 'contains the response to the authentication request. This response allows the SGSN service node to verify the identity of the mobile phone. - The sending of a MAP UPDATE GPRS LOCATION signaling message from the SGSN service node of the visited network VPLMNcs to the home location register (HLR) of the subscriber's HPLMN network. The MAP UPDATE GPRS LOCATION message contains the IMSics identification code. - The sending of a signaling message `MAP_INSERT_ SUBSCRIBER DATA 'from the subscriber HPLMN main location register (HLR) of the subscriber to the SGSN service node of the visited network VPLMNcs. The message `MAP_INSERT_SUBSCRIBER_DATA 'contains access permissions to the visited network VPLMNcs, including access to only circuit-switched services. - The sending of a signaling message `BSSAP-F LOCATION UPDATE REQUEST 'from the SGSN service node of the visited network VPLMNcs to the visited location register (VMSCNLR) of the VPLMNcs network. The message `BSSAP + LOCATION UPDATE REQUEST 'contains the IMSIcs identification code. - The sending of a signaling message `MAP_UPDATE_LOCATION 'from the visited location register (VMSCNLR) of the VPLMNcs network to the main location register (HLR) of the HPLMN network of the subscriber. The message `MAP_UPDATE_LOCATION 'contains the IMSIcs identification code. - The sending of a signaling message `MAP_INSERT_ SUBSCRIBER_DATA 'from the home location register (HLR) of the HPLMN network of the subscriber to the visited location register (VMSCNLR) of the network VPLMNcs. The message MAP INSERT SUBSCRIBER DATA contains the access permissions to the visited network VPLMNcs, including access to any circuit-switched service. - The sending of a signaling message `13SSAP + LOCATION UPDATE_ACCEPT 'from the visited location register (VMSCNLR) of the VPLMNcs network to the SGSN service node of the same network. The message `13SSAP + LOCATION UPDATE_ACCEPT 'contains the temporary identification code TMSIcs allocated by the visited location register (VMSC / VLR) of the VPLMNcs network. - Sending a 'GMM_ATTACH_ACCEPT' signaling message from the SGSN service node to the mobile phone. The message `GMM_ATTACH_ACCEPT 'contains the temporary identification code TMSIcs, valid for triggering any circuit-switched communication initiated by the network or mobile phone.

According to another advantageous characteristic, the procedures for triggering a packet-switched communication from a mobile phone registered on the visited network VPLMNps, whose operator has roaming agreements with the OPERATORcs_ps of the HPLMN network. , include the steps of: - sending a signaling message `ACTIVATE PDP CONTEXT REQUEST 'from the mobile phone to the SGSN service node of the visited network VPLMNps which controls the cell in which the mobile phone is located. The `ACTIVATE PDP CONTEXT REQUEST 'message contains the APN, the name of the logical gateway for access to packet-switched services. A message exchange between the SGSN service node and DNS servers in order to translate the APN name into an IP address of the GGSN interconnection gateway of the HPLMN network, this message exchange containing: The identifier of the HPLMN network, of which the OPERATORcs-ps has roaming agreements with the operator of the visited network VPLMNps. o The packet switched service identifier, this service being provided by the HPLMN SC-OPERATOR via the GGSN interconnection gateway. According to another advantageous characteristic, the operator of the visited network VPLMNps may have roaming agreements with a third party operator which, in turn, has interconnection agreements with the OPERATORcs_ps of the HPLMN network; this implies that the exchange of messages between the SGSN service node and DNS servers to translate the APN name into the IP address of the GGSN interconnection gateway of the HPLMN network contains: - The operator network identifier third party, which has roaming agreements with the visited network operator VPLMNps. - The identifier of the packet switched service, this service being provided by the OPERATORcs_ps of the HPLMN network through the GGSN interconnection gateway. According to another advantageous characteristic, the procedures for triggering an incoming call to a mobile phone registered on the visited network VPLMNcs, whose operator has roaming agreements with a third party operator which, in turn, has access agreements. interconnection with the OPERATORcs-ps of the HPLMN network, comprises the steps of: - sending an ISUP IAM signaling message to the GMSC gateway switch of the HPLMN network. The message 'ISUP IAM' contains the phone number of the recipient. - Sending a MAP SEND ROUTING INFORMATION signaling message from the GMSC gateway switch of the HPLMN network to the primary location register (HLR) of the subscriber's same HPLMN network. The MAP SEND ROUTING INFORMATION message contains the recipient's phone number. - The sending of a MAP PROVIDE ROAMING NUMBER signaling message from the subscriber's HPLMN main location register (HLR) to the visited location register (VMSCNLR) of the VPLMNcs network. The MAP PROVIDE ROAMING NUMBER message contains the IMSIcs identification code belonging to the third-party operator that has roaming agreements with the visited network operator VPLMNcs. The MAP PROVIDE ROAMING NUMBER message is relayed by the GMSC gateway switch of the third-party operator. - The sending of a MAP PROVIDE ROAMING NUMBER RESULT signaling message from the visited location register (VMSCNLR) of the VPLMNcs network to the main location register (HLR) of the subscriber's HPLMN network. The MAP PROVIDE ROAMING NUMBER RESULT message contains the MSRN temporary telephone number allocated by the visited location register (VMSCNLR) of the VPLMNcs network. The message% AAP PROVIDE ROAMING NUMBER RESULT is relayed by the gateway switch GMSC of the third party operator. - Sending a MAP SEND ROUTING INFORMATION RESULT message from the HPLMN home location register (HLR) of the subscriber to the GMSC gateway-switch of the same network. The MAP SEND ROUTING INFORMATION RESULT message contains the MSRN temporary telephone number and the visited location register address (VMSCNLR) of the VPLMNcs network. - The sending of an ISUP IAM signaling message from the GMSC gateway switch of the HPLMN network to the visited location register (VMSCNLR) of the VPLMNcs network. The message 'ISUP IAM' contains the MSRN temporary telephone number of the recipient. - The sending of a signaling message `13SSAP + _PAGING_REQUEST 'from the visited location register (VMSCNLR) of the VPLMNcs network to the SGSN service node of the same network. The `13SSAP + PAGING REQUEST 'message contains the IMSIcs identification code. - The sending of a signaling message `BSSMAP_PAGING 'from the SGSN service node of the VPLMNcs network to the BSS radio access equipment of the same network. The message `BSSMAP_PAGING 'contains the temporary identification code TMSIcs which makes it possible to send to the mobile telephone recipient the alert message of the incoming call. Drawings The present invention will be described below in more detail using the exemplary context described in the organization part of networks 10 PLMNcs and PLMNps The OPERATEURCS-PS operates an HPLMN network in France (functionally, HPLMN consists of a circuit-switched part - HPLMNcs and a packet-switched part - HPLMNps); one of the subscribers travels to Hong Kong: 15 He consumes any circuit-switched service through the IMSIcs according to the roaming agreements between the OPERATEURcs_ps and his Hong Kong counterpart `CSL '- He consumes any switched service of package through IMSIps according to roaming agreements between OPERATEURcs-ps and its Hong Kong counterpart `China Mobile HK 'Any expert in the art will recognize that the exemplary context described in no way limits the scope of this invention. In addition, the invention will be described with the aid of an embodiment shown in the appended drawings in which: FIG. 1 represents the constituent elements of the network of the invention FIG. 2 represents the main elements constituting the profile Figure 3 shows the details of the electrical profile of the Dual-1MS SIM card (IMSIcs, IMSIps) according to the invention - Figure 4 shows the software architecture of the 'Application Processor' of a mobile phone hosting the DoubleIMSI SIM card (IMSIcs, IMSIps) according to the invention Figure 5 shows the procedure for setting up the mobile phone and - in particular - functional interactions between the phone and the SIM-IMSI SIM card (IMSIcs, IMSIps) according to the invention - Figure 6 shows the registration, authentication and localization procedure in a visited network to 'comm VPLMNps - Figure 7 shows the procedure for registering, authenticating and locating in a VPLMNcs 'packet switched' visited network - Figure 8 shows the procedure for triggering a data communication (switched) packet) when the subscriber is in a visited network Figure 9 shows the procedure for triggering a (circuit-switched) voice communication when the subscriber is in a visited network - Figure 10 shows the procedure for Incoming Call DESCRIPTION OF THE EMBODIMENTS Following the exemplary context described in the scope part of the invention, FIG. 1 represents the system according to the invention: the set (10) of the HPLMNcs and HPLMNps networks is deployed in France by the OPERATORcs-PS. The equipment that is part of the network (10) is an HLR 'Multi-IMSI' (101), a GMSC (102), an SMSC (103), a GGSN (104) and - optionally - a CAMEL platform (105) which implements any logic necessary for the operation of the Service Control Point (SCP). The network (10) is attached to the international signaling network SS7 (50) in order to exchange: Any signaling message for the management of authentication, mobility, etc. from / to the mobile networks visited (20) and (30) Any signaling message for the routing of calls or short messages from / to the visited mobile network (30) The network (10) is also attached to the international network of GRX interconnect (60) for exchanging any signaling message for routing data sessions from / to the visited mobile network (20). The OPERATORcs-ps of the network (10) has roaming agreements with the operator of the visited network (20) (the Hong Kong operator 'China Mobile HK' in the exemplary context considered), these agreements concerning only any communication to packet switching (data communication). OPERATORcs_ps of the network (10) also has roaming agreements with the operator of the visited network (30) (the Hong Kong operator `CSL 'in the exemplary context considered), these agreements concerning only any circuit-switched communication (voice communication / SMS / Additional services). OPERATEURcs_ps subscribers use dual-IMSI '(150) SIM cards. The SIM card IMSIps (150) allows a subscriber who is roaming in Hong Kong to consume packet switched mobile services, which services are available through the visited network equipment (20); among the attributes (160) of the SIM card (150) which are attached to the subscriber are: - The IMSI 'packet switching' IMSIps, starting with the 5 digits '208XX' (corresponding MCC '208' identifier to France, identifier MNC `XX 'corresponding to the network HPLMNps) - A MSISDN French MSISDNFR, starting with the 2 digits' 33' (telephone identifier of France). The SIM card IMSIcs (150) allows the same roaming subscriber in Hong Kong to consume circuit-switched mobile services, which services are available through the visited network equipment (30); among the attributes (260) of the SIM card (150) which are attached to the subscriber are: - IMSI 'circuit-switched IMSI', starting with the 5 digits '208YY' (matching MCC '208') to France, MNC identifier 'YY' corresponding to the HPLMNcs network) - The same French MSISDN MSISDNFR, starting with the 2 digits '33' (France's telephone identifier). SIM cards (150) with attributes (160) and (260) are stored in the HLR 'Multi-IMSI' (101).

Still according to Figure 1 the system according to the invention is also composed of the visited network VPLMNps (20), deployed in Hong Kong by the Hong Kong operator 'China Mobile HK'. The devices that are part of the subnet (20) and with which the network (10) dialogues are a VLR / VMSC (201) and an SGSN (204). The network (20) is attached to the international signaling network SS7 (50) and to the international GRX interconnection network (60) in order to exchange with the network (10) any signaling message for the control of authentication and authentication. subscriber mobility as well as for the routing of data sessions. The VLRNMSC (201) and the SGSN (204) are connected by a logical connection (90) (at protocol and / or service level) according to the BSSAP + protocol defined in 3GPP TS 29.018: 3rd Generation Partnership Project; Technical Specification Core Network and Terminais Group; General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); The networks (10) and (20) must configure their respective E.214 tables so that the signaling received in correspondence of the attributes (160) of the SIM card (150) is directed towards the HLR. 'Multi-IMSI' (101).

Still according to Figure 1 the system according to the invention is also composed of the visited network VPLMNcs (30), deployed in Hong Kong by the Hong Kong operator `CSL '. The devices that are part of the subnet (30) and with which the network (10) dialogues are a VLR / VMSC (301) and an SGSN (304). The network (30) is attached to the international signaling network SS7 (50) in order to exchange with the network (10) any signaling message for the control of the authentication and the mobility of the subscriber as well as for the routing calls or short messages. Similar to the network (20), the VLR / VMSC (301) and the SGSN (304) are connected by a logical connection (90) (at the level of the protocol and / or services) according to the BSSAP + protocol. The networks (10) and (30) must configure their respective E.214 tables so that the signaling received in correspondence of the attributes (260) of the SIM card (150) is directed to the HLR `Multi-IMS1 '(101).

According to Figure 1, the networks (10) and (20) are interconnected by the logical connections (at the level of the protocol and / or services) as follows: The dashed line (70) denotes a connection according to the MAP protocol, defined in 3GPP TS 09.02: 3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile Application Part (MAP) specification (Release 1998) and - if necessary - according to the CAP protocol, defined in 3GPP TS 03.78: 3rd Generation Partnership Project; Technical Specification Group Core Network; Customized Applications for Mobile Network Enhanced Logic (CAMEL) Phase 2; Stage 2 (Release 1998) The continuous line (80) denotes a connection according to the GTP protocol defined in 3GPP TS 29.060: 3rd Generation Partnership Project; Technical Specification Core Network and Terminais Group; General Packet Radio Service (GPRS); GPRS Tunneling Protocol (GTP) across the Gn and Gp interface (Release 9) Still according to Figure 1, the networks (10) and (30) are interconnected by the logical connections (at protocol and / or services level) following: - The dotted line (70) denotes a connection according to the MAP protocol, and - if necessary - according to the CAP protocol; in addition, the dotted line (70) also denotes a connection according to the ISUP call control protocol defined in the Q.76x series of FITU-T The HLR 'Multi-IMSI' (101) of the network (10 ) must control and authorize communications based on the attributes (160) and (260) of the SIM card (150). In particular the HLR (101) must: - Allow all data communication between the network (20) and the network (10) by checking that such communication is initiated with the IMSIps. The procedures for controlling and authorizing data communications will be explained later. - Allow any circuit switched communication (voice, SMS) between the network (30) and the network (10) by checking that such communication is initiated with the IMSI. The procedures for control and authorization of circuit-switched communications will be explained later. Following the exemplary context described in the field part of the invention, FIG. 2 represents a part of the electrical profile (the file structure) of the dual SIM card. According to the invention: The attributes (160) of the electrical profile of the SIM card (150) contain the structure of the files dedicated to the management of the operations (mobility, 20 authorizations, etc.) in correspondence of the IMSI to IMSIps packet switching. The attributes (260) of the electrical profile of the SIM card (150) contain the structure of the files dedicated to the management of the operations (mobility, authorizations, etc.) in correspondence with the IMSI circuit-switched IMSI 25. The attributes identified by the couple (160, 260) contain the structures of the files in common, that is, the files that do not depend on the use of the IMSIps or the IMSIcs. The part (270) of the SIM card (150) contains the parameters and the algorithms for the security procedures, in particular: The integrity key KI, used by the algorithms known as `A3 'and` A8' - The algorithm `A3 ', allowing the authentication of a subscriber - The algorithm` A8', allowing the generation of encryption keys Kc and KCGPRS - The algorithm `A5 ', allowing the encryption / decryption on the radio channel - L' 'GPRS-A5' algorithm, allowing the encryption / decryption on the ILC layer (Logical Link Control) in the visited network (20) The parameters, algorithms and network elements involved in the security procedures are defined in the 3GPP standard TS 03.20: 3rd Generation Partnership Project; Security related network functions (Release 2000) The part (270) of the SIM card (150) is unique, regardless of the set of attributes used and - in particular - the IMSIps or IMSIcs. This uniqueness is consistent with the business model adopted in the description: a single mobile operator or a third operator such as "Full MVNO" ("Unbundled Operator") is responsible for the operation of IMSI 'IMSIcs' and' IMSIps.

Following the exemplary context described in the field part of the invention, FIG. 3 represents the details of the electrical profile (the file structure) of the SIM-IMSI SIM card according to the invention. The description of the functional / physical elements shown in Figure 3 refers to the standards: - 3GPP TS 11.11: 3rd Generation Partnership Project; Technical Specification Group Terminais; Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface (Release 1999) - ETR 174: European digital cellular telecommunications system (Phase 2); The interface between Phase 1 and Phase 2 (GSM 09.91) According to a preferred embodiment, the hierarchical file structure of the SIM card consists of: The Master File MF (160, 260). The MF is the source directory of the SIM card. Its identifier ("File ID" - FID) is "3F00". Among the Elementary File (EF) files that are directly attached to the MF are: - The EF which contains the unique identification number of the SIM card. Its identifier T'ID 'is 2FE2'.

In Figure 3, the MF is identified by the pair (160, 260) because its structure is not affected by the use of IMSIps or IMSIcs. In other words, the content of the MF (160, 260) is in common with the directories (160) and (260) because it consists of general information on the SIM card.

The Directory File '(DF) GSM (260) is the directory which contains all the EFs with the OPERATORcs_ps specific information of the network (10). In the case of the system according to the invention, this information refers to the use of IMSI 'circuit switching' IMSIcs 'The identifier' FID 'of the DF GSM (260) is 7F20'. Among the EFs that are attached to the GSM DF (260) are: The EF ACM '(Accumulated Call Meter), which contains the number of accumulated call units. Its identifier T'ID 'is `6F39'. The Forbidden Public Land Mobile Network (FPLMN), which contains the list of forbidden networks (networks in which the user has no permission to consume circuit-switched services). Its identifier T'ID 'is `6F7B'. The EF IMS / cs'. Its identifier T'ID 'is `6F07'. The EF Xc ', which contains the key Kc to encrypt any circuit-switched communication (such as voice or SMS) on the radio channel. Its `FID 'identifier is` 6F20'. EF 'LOCI' (LOCation Information), which contains information on the current location of the mobile phone (40). Its identifier T'ID 'is `6F7E'. Two fields are part of this information: o The Temporary Mobile Subscriber Identity (TMS1) field. The Location Area Information (LAI) field, which contains the geographic data of the location area (see also the 'GLOSSARY' section). ) The EF `LP '(Language Preference), which contains the language chosen for the user interface. Its `FID 'identifier is` 6F05'.

The Public Land Mobile Network Selector (PLMNSel 'EF), which contains the list of preferred networks (networks that have the best roaming agreements - for circuit-switched services - with the OPERATORs-es). Its `FID 'identifier is` 6F30'.

The Service Provider Name (EF), which contains the name of the service provider (the name of the OPERATORcs_ps). Its identifier 'FID' is `6F46 '. - The SIM Service Table (SST), which contains the list of available circuit switched services, in addition to the voice communication service. Its `FID 'identifier is` 6F38'. The Directory File '(DF) Telecom (160, 260) is the directory that contains all EFs with cell-specific information. The DF Telecom is identified by the pair (160, 260) because its structure is not affected by the use of IMSIps or IMSIcs. In other words the content of the DF Telecom (160, 260) is in common compared to the directories (160) and (260), the identifier T'ID 'of the DF Telecom (160, 260) is 7F10'.Among the EFs that are attached to the DF Telecom (160, 260) are: - The EF 'DNA' (Abbreviated Dialing Numbers), which contains the short numbers (and the names of the respective services). Its identifier T'ID 'is `6F3A'. - The Fixed Dialing Numbers (FDN), which contains the list of the only numbers that the user can call under certain conditions. Its identifier T'ID 'is `6F38'.

The EF `MSISDN, which contains the telephone number associated with the subscriber '. Its identifier T'ID 'is `6F40'. - The 'SMSP' EF, which contains the configuration necessary for the use of SMS services (for example, the address of the `SMS Center '(SMSC) belonging to the OPERATEURcs-ps). Its `FID 'identifier is` 6F42'.

The Directory File '(DF) DCS (160) is a second directory which contains all the EFs with the OPERATORcs-ps specific information of the network (10). In the case of the system according to the invention, this information refers to the use of the IMSI 'switching of uet "IMSIEls." _, ID `FID' DF DF (160) is left free to the manufacturer SIM card, according to OPERATORcs-ps specifications. The remainder of the description will show that the functionalities and operations of the mobile phone (40) that hosts the SIM card (150) according to the invention must be compatible with the presence of the DF DCS (160). In an arbitrary manner, the identifier T'ID 'of the DF DCS (160) is fixed at 7F21'. The adoption of the name DCS 'for the DF (160) is arbitrary: it refers to the old specification GSM 09.91, which provided that the same SIM card could be inserted also in older phones compatible with the DCS1800' radio band. In addition, a DF DCS ', with identifier' FID 'equal to' 7F21 'is defined in the GSM 09.91 specification. Among the EFs that are attached to the DCS DF (160) are: The Forbidden Public Land Mobile Network (FPLMN), which contains the list of forbidden networks (networks in which the user has no permission to consume the packet switched services). In general, EF `FPLMN 'will be different from its counterpart of the GSM DF. Indeed, in the system according to the invention OPERATEURcs_ PS can prohibit certain visited networks relative to the IMSIps, while the same networks can be allowed in relation to the IMSIcs. The identifier 'FID' is (6F7B '(as for its counterpart of the GSM DF) The EF IMS, Ips' Its identifier 'FID' is `6F07 '(as for its counterpart of the GSM DF) The EF KcGpRs' , which contains the key KcGpRs to encrypt any packet-switched communication on the radio channel Its 'FID' identifier is `6F52 'The EF tocIGPRS' (LOCATION Information - GPRS), which contains information about the current location of the phone mobile (40), its 'FID' identifier is `6F53 'Two fields are part of this information: o The '13 -TMS1' field (Packet Temporary Mobile Subscriber Identity) o The 'RAI' field (Routing Area Information), which contains the geographical data of the area of location with respect to the GPRS network (see also the section 'GLOSSARY') The EF PLMNSel '(Public Land Mobile Network Selector), which contains the list of the preferred networks (networks which have the best agreements roaming - for packet switched services - with the OPERATORcs_ps). In general, EF PLMNSer will be different from its counterpart of the GSM DF. Indeed, in the system according to the invention the OPERATORcs_ps can have a list of preferred visited networks compared to the IMSIps, this list being different from the IMSIcs. Its identifier 'FID' is `6F30 '(as for its counterpart of the GSM DF).

In Figure 3 the ADF directory (Application DF) US / M (Universal Subscriber Identity Module) is not shown. The ADF USIM has the same structure as the DF GSM and DCS. The 'FID' identifier of the ADF US / M may have the value `5F1X or` 5F2X (where 'X' is a hexadecimal digit between '0' and 'F'). USW ADFs can: - Have specific content - Have shared content with the peer EFs of the GSM DF or DF DCS. In the context of the system according to the invention, among the EFs with shared content are: o The EF `/ MS / ', the content of which can be shared with the EF 1MS / cs' of the GSM DF or with the 'EF 1MS / ps' of DF DCS, according to OPERATORcs-ps preferences. o EF TPLMN ', the content of which can be shared with the EF `FPLMN' of the GSM DF or with the EF TPLMN 'of the DF DCS, according to the OPERATORcs-ps preferences. o EF 'LOCI', the content of which is shared with the EF 'LOCI' of the GSM DF. In general, the directory ADF US / M allows the management of the features of the SIM card (150) and its interfaces with the telephone (40) on networks type '3G'. Nevertheless, the same functionalities and interfaces can be managed from GSM DFs and DCS DFs. The OPERATORcs-ps will therefore have to define the procedures for accessing GSM and DCS DFs as well as their respective RUs on 3G networks. In the rest of the description, among the operational procedures will be shown how it will be possible for the subscriber's mobile phone (40): - To have access to circuit-switched services by using the IMSIcs whatever the type visited network (2G or 3G) - Have access to packet switched services using the IMSIps regardless of the type of network visited (2G or 3G or - possibly - 4G) Following the exemplary context described in the Domain section of the invention Figure 4 shows the software architecture of the 'Application Processor' (AP) feature of the mobile phone (40). Indeed, according to 3GPP TS 27.010: 3rd Generation Partnership Project; Technical Specification Core Network and Terminais Group; Terminal Equipment to User Equipment (TE-UE) multiplexer protocol (Release 11)), the software architecture of a mobile phone consists of two functional parts: The Application Processor (400), shown in Figure 4. Its purpose is to convert any command from / to the subscriber into a series of binary packets that are transmitted / received to / from the 'Band-Base Processor' (BP).

The 'Band-Base Processor' (BP), not shown in Figure 4. Its purpose is to format the received / transmitted binary packets from / to the Application Processor (400) in order to be able to transmit / receive them on the radio channel. In this sense, the 'Band-Base Processor' (BP) implements the protocol layers according to the corresponding 3GPP standards. The communication between the Application Processor (400) and the 'Band-Base Processor' (BP) consists of a 'UART' type physical link (Universal Asynchronous Receiver Transmitter) whose Figure 4 represents its termination (406 ). With the functional components (405) and (406) of Figure 4, several data channels can pass between the Application Processor (400) and the 'Band-Base' Processor (BP): call management and network information , SMS, packet switched communications data, etc. It is therefore possible to establish a virtual connection between a software process running in the Application Processor (400) and a corresponding software process in the 'Band-Base Processor' (BP). According to Figure 4, the main functional components of the Application Processor (400) are: The user interfaces (401) and (402) to enable triggering of circuit-switched communications (voice, SMS, supplementary services) and packet-switched communications (internet browsing, messaging services, etc.) through the use of the telephone keypad or a touch screen - The 'API API' and 'Data API' programming interfaces (403), which allow the interaction between user interfaces (401), (402) and software processes that must transfer communications data to the 'Band-Base Processor' (BP). - A Telephony Application Programming Interface (TAPI) server and an associated command processor (404) which must differentially process each type of circuit-switched communication (voice, SMS, supplementary services) before transmitting the content to it. software module (405). - A software module (405) which consists of several software processes which must recover all the information necessary for the activation of the 'Band-Base Processor' (BP) for the implementation of any circuit-switched communication or of package. Among these software processes we find: A management software module (407) which coordinates all the commands received from the modules (404) and (403). Its main role is to collect the information necessary for the proper execution of the command, format this information according to the different protocol layers of the 'Band-Base Processor' (BP), manage the sending of this information to the 'Band Processor' - Base '(BP) based on the state of a queue and the availability of resources (channels) in the virtual connection between the Application Processor (400) and the' Band-Base 'Processor (BP). Two storage modules (408) and (409), whose purpose is to create and maintain two 'virtual SIM' in the phone's RAM. The module (408) contains an image of some EF files of the GSM DF (260) (see Figure 3), while the module (409) contains an image of some EF files of the DF DCS (160). The purpose of the modules (408) and (409) is to allow very fast read / write access to information that is used very frequently by the 'Band-Base' processor (BP) for establishing communications. Among the information stored in the module (408) are: - The temporary key Kc ', which makes it possible to encrypt any circuit-switched communication (such as voice or SMS) on the radio channel. - The information 'LOCI' which contains the parameters of the current location of the mobile phone (40) in the visited network (30). As already mentioned in the description of Figure 3, the fields 'TMSI' and 'LAI' are part of these parameters. Among the information stored in the module (409) are: - The temporary key YCGPRS ', which encrypts any packet-switched communication. - The information tOCIGPRS 'which contains the parameters of the current location of the mobile phone (40) in the visited network (20). As already mentioned in the description of FIG. 3, the `P-TMS1 'and` RAI' fields are part of these parameters. It should therefore be noted that in the system according to the invention two `virtual SIM '(408) and (409) are stored in the RAM of the telephone (40). The `virtual SIM '(408) contains the information necessary to establish any circuit-switched communication on the visited network (30), once the authentication on the network (30) has been performed with the identifier 'IMSIcs' The 'virtual SIM' (409) contains the information necessary to establish any packet-switched communication on the visited network (20), once authentication on the network (20) has been performed with the identifier 'IMSIps'.

Operating Procedure for Turning On the Mobile Phone (40) Preamble The mobile phone (40) is compatible with the SIM Application Toolkit (SAT). The `SIM Application Toolkit 'allows the SIM card (150) to access certain features of the mobile phone (40), such as controlling the screen, monitoring the keyboard (or touch screen), sending SMS and - more in general - control any feature that allows for the implementation of value-added services. Ultimately, the `SIM Application Toolkit 'is a set of software tools that allow to implement applications on the SIM card (150). SAT is described in 3GPP TS 11.14: Digital cellular telecommunications system (Phase 2+); Specification of the SIM Application Toolkit (SAT) for the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface (version 8.17.0 Release 1999) In the context of the system according to the invention, the SIM card (150) will have to host a application called 'Application IMSIcs - IMSIps'; this application must handle multiple couples (IMSIcs, IMSIps). Each pair will be activated according to: - The country visited by the OPERATEURcs-Ps subscriber - The roaming agreements between the OPERATEURcs-Ps and his counterparts in each country visited. It is therefore necessary that 'Application IMSIcs - IMSIps' can refer to a table which connects the identifier of the visited country (its MCC) and the corresponding pair (IMSIcs, IMSIps). As an example, a possible excerpt from this table is shown in Table 1 below: Country MCCMNC IMSIcs IMSIps France 208 208YY 208YY Italy 222 208YY 208YY Canada 302220, 302221 310260 (T-Mobile) 316010 (Nextel) Mexico 334 208YY 316010 (Nextel) Hong Kong 45400, 45409 208YY 208XX Table 1 According to Table 1 and with reference to the PLMNcs and PLMNps network organization section Any subscriber who is in his home country (France) can benefit from tariffs and / or advantageous package on a single HPLMN home network and with a single and unique IMSI identifier for its SIM card (150). In other words, for a subscriber in France IMSIps = IMSIcs. According to the explanations of Figure 1, IMSIcs begins with the 5 digits 208YY '(MCC' 208 'identifier corresponding to France, MNC identifier' YY 'corresponding to the HPLMNcs network of the OPERATEURcs-ps) Any subscriber who is roaming in Italy can benefit from tariffs and / or advantageous package according to roaming agreements between the OPERATEURcs-ps and its Italian counterparts. According to Table 1, these roaming agreements are valid on any Italian VPLMN visited network with a single and unique IMSI identifier for the SIM card. In other words, for a roaming subscriber in Italy IMSIps = IMSIcs. According to the explanations of Figure 1, IMSIcs begins with the 5 digits 208YY '(MCC identifier' 208 'corresponding to France, identifier MNC' rie 'corresponding to the HPLMNcs network of the OPERATEURcs-ps) Any subscriber who is roaming in Hong Kong can benefit from tariffs and / or advantageous package according to the roaming agreements between OPERATEURcs_ps and its Hong Kong counterparts. According to Table 1, these roaming agreements are valid only: o On the network visited `CSL 'for circuit switched services through the use of IMSI switching-of-circuit' (IMSIcs). Visited network `CSL 'acts as VPLMNcs for circuit switched services only; according to Table 1, the network identifier is MCCMNC = 45400 o On the network visited 'China Mobile HK' for packet switched services through the use of IMSI packet-switching '(IMSIps). The visited network 'China Mobile HK' acts as VPLMNps for packet switched services only; according to Table 1, the network identifier is MCCMNC = 45409 In other words, for a subscriber roaming in Hong Kong an IMSIps and an IMSIcs are adopted at the same time to register on the network VPLMNcs `CSL 'for circuit switched services and the `China Mobile HK' VPLMNps network for packet switched services. According to the explanations of Figure 1: o The IMSIcs begins with the 5 digits 208YY '(MCC' 208 'identifier corresponding to France, MNC identifier' YY 'corresponding to the HPLMNcs network of the OPERATEURcs-ps) o The IMSIps starts with the 5 digits' 208XX '(MCC identifier' 208 'corresponding to France, identifier MNC `XX' corresponding to the HPLMNps network of the OPERATEURcs-ps) The case of a roaming subscriber in Canada is treated according to hypotheses different, according to Table 1. Indeed, the purpose is to show that the system according to the invention can also apply in the case that the OPERATEURcs-ps is "Full MVNO" ("Unbundled Operator") also in a other country, besides France. The case of Table 1 shows that no roaming agreement exists between the OPERATEURcs-ps French network and the Canadian networks of its counterparts. On the other hand, the OPERATORcs_ps acts as "Unbundled Operator" also in the United States; As such, it has entered into interconnection agreements with T-Mobile USA (for any circuit-switched service) and Nextel (for any packet-switched service). As part of these "interconnection" agreements, T-Mobile USA and Nextel have reserved ranges of their IMSI for the exclusive use of the OPERATORcs-ps. Any subscriber who is roaming in Canada may benefit from tariffs and / or preferential rates according to roaming agreements between T-Mobile USA and Nextel and its Canadian counterparts. According to Table 1, these roaming agreements are valid only o On the network visited 'TELUS Communication' for circuit switched services through the use of IMSI switching-of-circuit '(IMSIcs). The visited network 'TELUS Communication' acts as VPLMNcs (30) for circuit switched services only; according to Table 1, the network identifier is MCCMNC = 322220 On the visited network 'Airter for packet switched services through the use of IMSI packet-switching' (IMSIps). The visited network 'Airter acts as VPLMNps (20) for packet switched services only; according to Table 1, the network identifier is MCCMNC = 322221 In other words, for a roaming subscriber in Canada an IMSIcs and an IMSIps are adopted at the same time in order to register on the VPLMNcs (30) network. 'TELUS Communication' for circuit switched services and Airter's VPLMNps (20) network for packet switched services. According to Table 1: o The IMSIcs starts with the 6 digits '310260' (MCC '310' corresponding to the United States, MNC '260' corresponding to the T-Mobile USA network.) IMSIcs is part of a range of 'IMSI that T-Mobile USA has allocated to the OPERATORcs-ps for its exclusive use as part of their' interconnection 'agreement. "Vis-à-vis the visited network VPLMNcs (30) of' TELUS Communication ', The user appears as a subscriber of T-Mobile USA, since he is identified by an IMSIcs belonging to T-Mobile USA (and allocated to the OPERATORcs-ps) Thanks to the interconnection agreements between T-Mobile USA and the OPERATOR -ps, all traffic originating (destination) of the network VPLMNcs (30) of 'TELUS Communication' will have for destination (origin) the network HPLMNcs (10) of the OPERATEURcs-Ps o The IMSIps starts with the 6 figures '316010' (MCC identifier '316' corresponding to the United States, MNC identifier '010' corresponding to Nextel's network. IMSI that Nextel has allocated to the OPERATORcs-ps for its exclusive use as part of their 'interconnection' agreement. Vis-à-vis the visited network VPLMNps (20) of 'Airter, the user appears as subscriber of Nextel, since it is identified by an IMSIps belonging to Nextel (and allocated to the OPERATEURcs-ps). Thanks to the interconnection agreements between Nextel and the OPERATEURcs-ps, all traffic originally (destination) of the network VPLMNps (20) of 'Assist will have for destination (origin) the network HPLMNps (10) of the OPERATORcs- ps.

The case of a roaming customer in Mexico is treated according to still different assumptions. According to Table 1, unfavorable roaming agreements exist between the French OPERATORcs-ps network and the Mexican networks of its counterparts for any packet-switched communication. The same roaming agreements provide more favorable conditions for any circuit-switched communication. As part of its interconnection agreements with the US operator Nextel (for any packet switched service), the OPERATORcs-ps acts as a "Unbundled Operator" also in the United States and may exploit the agreements of roaming between Nextel and the Mexican networks of its counterparts for any packet-switched communication. As a result, any subscriber who is roaming in Mexico may benefit from preferential roaming rates and / or packages depending on the roaming arrangements between: o The OPERATORcs-ps and all its Mexican counterparts for circuit-switched services through 'use of the IMSI' switching-of-circuit '(IMSIcs). All the Mexican networks visited can act as VPLMNcs (30) for circuit-switched services only; indeed, according to Table 1 the identifier of the visited network contains only the country code MCC = 334 (Mexico) o The operator Nextel and all its Mexican counterparts for packet switched services through the use of `switching- de-packet '(IMSIps). All Mexican networks visited can act as VPLMNps (20) for packet switched services only. In other words, for a subscriber roaming in Mexico, IMSIcs and IMSIps are adopted at the same time in order to register on any Mexican network visited. According to Table 1: o The IMSIcs starts with the 5 digits 208YY '(MCC identifier' 208 'corresponding to France, MNC identifier' YY 'corresponding to the HPLMNcs network of the OPERATEURcs-ps) o IMSIps starts with the 6 digits '316010' (MCC '316' corresponding to the United States, MNC '010' corresponding to the Nextel network.) IMSIps is part of an IMSI range that Nextel has allocated to the OPERATORcs_ps for its exclusive use as part of the of their "interconnection" agreement. "Vis-à-vis any visited network VPLMNps (20), the user appears as subscriber of Nextel, since it is identified by an IMSIps belonging to Nextel (and allocated to the OPERATEURcs- Thanks to the interconnection agreements between Nextel and the OPERATORcs_ps, all traffic originally (destination) of the network VPLMNps (20) will have for destination (origin) the network HPLMNps (10) of the OPERATEURcs-ps. Figure 5 shows - in a synthetic way - the different stages of commissioning mobile phone (40). These steps focus on the activities of the phone (40) with the SIM card (150). Once again, Figure 5 will be commented on using the exemplary context described in the Organization part of PLMNcs and PLMNps networks. The OPERATEURcs-ps subscriber moves to Hong Kong: He consumes any circuit-switched service thanks to the IMSIcs according to roaming agreements between the OPERATEURcs-ps and its Hong Kong counterpart `CSL 'It consumes any packet switched service thanks to the IMSIps according to the roaming agreements between the OPERATEURcs-ps and his Hong Kong counterpart 'China Mobile HK' The procedures in Figure 5 refer to the case of the first start-up of the phone (40) after arrival in Hong Kong.

Step (501) of Figure 5: As soon as the phone (40) is switched on, a physical / logical link with the SIM card is established. The phone receives the command 'Answer To Reset' (ATR) from the SIM card: this command allows the phone (40) to ensure that the SIM card (150) is inserted and to know the protocol settings for the exchange of data with the SIM card. Step (502) of Figure 5: At the end of step (501), the telephone (40) and the SIM card (150) have established a communication link. Among the Elementary Files (EF) read by the telephone (40) is the EF IP '(Language Preference - see Figure 4). The phone displays a message to the subscriber asking him to enter his four-digit PIN; the message is displayed according to the subscriber's preferred language, this language being defined in the IP EF '. The subscriber enters his PIN code, the veracity of which is verified by the phone which also checks the number of times that an erroneous PIN code has been entered. Step (503) of Figure 5: The phone (40) reads the following information from the SIM card (150): - The SIM Service Table (SST), belonging to the GSM Directory File (DF) (260), and which contains the list of available circuit switched services, in addition to the voice communication service. - The 1SCID 'SIM Service Table (MF) belonging to the Master File (MF) (160, 260), which contains the unique identification number of the SIM card. - The EF 1MS / cs 'and 1MS / ps', belonging respectively to the directories DF GSM (260) and DF DCS (160) described in Figure 3. Note: in the state of the art a single and unique EF 'IMSI' is read by the mobile phone. In the system according to the invention it is necessary to read the EF 1MS / cs 'and 1MS / ps'. According to the exemplary context and use case mentioned above, the telephone (40) had been turned off on French soil. Before the phone was switched off, the subscriber was in his home country; therefore, according to Table 1, at the start of the phone in Hong Kong we will have IMSIps = IMSIcs = 208YY. Step (504) of Figure 5: The telephone (40) initiates the cell selection process. It searches for all radio frequency channels available in Hong Kong (for example, channels belonging to a GSM / GPRS 900 system, and / or a GSM / GPRS 1800 system and / or a 'UNITS 3G' system). For each detected channel, the telephone (40) measures the power level of the received wireless signal. This operation gives rise to the selection of the radiofrequency channel with the highest power level. The telephone (40) synchronizes on this channel, reads the information contained therein and verifies whether it is a BCCH (Broadcast Control Channel) logical channel. If so, the telephone (40) decodes the system information contained in the BCCH channel. According to 3GPP TS 44.018: 3rd Generation Partnership Project; Technical Specification Group GSM / EDGE Radio Access Network; Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol (Release 11) System information known as 'SYSTEM INFORMATION TYPE 2 to 4, and optionally TYPE 1, 2bis, 2ter, 7, 8, 13, 16 and 17' are broadcast continuously. If the telephone (40) can decode this information without errors and check that the corresponding cell belongs to a non-forbidden VPLMN, it is possible to correctly recover the information `MCC ', corresponding to the country in which the subscriber is located. In the example case described, MCC = 454 (Hong Kong Country ID). Step (505) of Figure 5: The IMSIPS application - IMSIps' hosted by the SIM card (150) takes control. It is triggered as soon as the MCC has been detected at the end of Step (504). As already explained in the Preamble section, the IMSIcs - 1114Sips' Application contains a table that links the MCC of each visited country to the optimal pair (IMSIps, IMSIcs). With reference to Table 1, the Application IMSIcs - IMSIps' verifies that - in correspondence with the MCC = 454 - the IMSIps must be replaced with respect to its value at the time of the extinction of the telephone (40). Step (506) of Figure 5: The IMSIps-IMSIps Application writes: - The new value of the IMSIps in the EF 1MS / ps' of the DCS DE (160). According to Table 1 and the exemplary context (roaming subscriber in Hong Kong), the new value of the IMSIps begins with the 5 digits '208XX' (MCC identifier '208' corresponding to France, MNC identifier 'XX' corresponding to the network HPLMNps) The new value of the IMSIcs in the EF 1MS / cs' DE GSM (260). According to Table 1 and the exemplary context (roaming subscriber in Hong Kong), the new value of the IMSIcs begins with the 5 digits 208YY '(MCC' 208 'identifier corresponding to France, MNC' XX 'identifier corresponding to the network HPLMNIcs of the OPERATORcs-ps). Note: in the exemplary context described the value of IMSIcs has not changed compared to the time of the extinction of the phone (40). Nevertheless, the two IMSIs are replaced in order to deal with the example case more generally. Step (507) of Figure 5: The SIM (150) sends the telephone (40) the command REFRESH '. The purpose is to alert the phone that the contents of the EF 1MS / ps 'of the DF DCS (160) and 1114Sics' of the GSM DE (260) has changed. According to 3GPP TS 11.14: Digital cellular telecommunications system (Phase 2+); Specification of the SIM Application Toolkit (SA T) for the Subscriber Identity Module - Mobile Equipment (SIM-ME) Interface (Release 8.17.0 Release 1999) The `SIM Initialization and File Change Notification 'rule must apply to the REFRESH command . In this case, the phone (40) will trigger the so-called 'Mobility Management (MM) Restart' procedures, according to 3GPP TS 23.122: 3rd Generation Partnership Project specifications; Technical Specification Core Network and Terminais Group; Figure 5: The phone (40) triggers the cell selection process again; the cell must have a visited network VPLMNps 20 in the uel - according to the system set forth in the invention - only packet switched communications are allowed. The cell selection process includes the features described in Step (504). Once the identification of the cell is complete, it is considered as 'candidate'. Before registering on the VPLMNps network, the telephone (40) must verify that: The VPLMN to which the 'candidate' cell belongs does not belong to the list of forbidden networks. This list is contained in the EF `FPLMN 'of the DE DCS (160) of the SIM card (150). The VPLMN to which the 'candidate' cell belongs belongs to the list of allowed networks. This list is contained in the EF PLMNSer of the DE DCS (160) of the SIM card (150). In the exemplary context considered, the EF PLMNSel 'must contain the identifier `MCCMNC' = 45409, corresponding to the visited network of the operator 'China Mobile HK'. If the two conditions above are validated, the telephone (40) fear to start registration procedures on the network VPLMNps (20) belonging to the operator 'China Mobile HK'. This record is made with the identifier 'IMSIps' of Table 1; the details of the registration procedures - with the interactions between the telephone (40), the SIM card (150) and the network elements (10) and (20) - will be explained later. Step (509) of Figure 5: After the network registration procedure VPLMNps is complete, the telephone (40) triggers the cell selection process again; the cell must belong to a visited network VPLMNcs 30 in the uel - according to the system set forth in the invention - only circuit switched communications are allowed. The cell selection process includes the features described in Step (504). Once the identification of the cell is complete, it is considered as 'candidate'. Indeed, before recording on the network VPLMNcs (30) the telephone (40) must verify that: - The VPLMN to which the 'candidate' cell belongs is not part of the list of prohibited networks. This list is contained in the EF `FPLMN 'of the GSM DF (260) of the SIM card (150). - The VPLMN to which the 'candidate' cell belongs belongs to the list of allowed networks. This list is contained in the EF PLMNSel 'of the GSM DF (260) of the SIM card (150). In the exemplary context considered, the EF PLMNSel 'must contain the identifier `MCCMNC' = 45400, corresponding to the visited network of the operator` CSL 'If the two conditions above are validated, the telephone (40) can start the VPLMNcs (30) network registration procedures belonging to the `CSL 'operator. This record is made with the identifier 'IMSIcs' of Table 1; the details of the registration procedures - with the interactions between the telephone (40), the SIM card (150) and the network elements (10) and (30) - will be explained later. Anyone skilled in the art will recognize that the steps shown in Figure 5 form part of the phone's start-up procedures (40).

Only the essential steps of the communication between the telephone (40) and the SIM card (150) in the context of the system according to the invention are described.

Operational Procedures for Network Registration, Authentication, Mobility Management Preamble It is appropriate to make assumptions about the telephone (40) and the network organization (20) and (30). The telephone (40) operates in the so-called 'Class A' mode. According to this mode of operation, it simultaneously supports recording, activation, monitoring, and session establishment procedures on both networks (circuit and packet switching, respectively). It should be noted that - if necessary - any transaction between the telephone (40) and the circuit-switched visited network VPLMNcs (30) must be able to be on an `ARFCN '(Absolute Radio Frequency Channel Number) different from another` ARFCN 'which will be dedicated to any transaction between the telephone (40) and the visited packet-switched network VPLMNcs (20). Indeed, in the exemplary context of the system according to the invention (roaming subscriber in Hong Kong), the network VPLMNcs belongs to the Hong Kong operator `CSL 'while the VPLMNps network belongs to the Hong Kong operator' China Mobile HK ' . According to Figure 1, the VPLMNcs (30) and VPLMNps (20) networks operate in the 'NOM' mode: The 'Gs' interface (dashed line (90) in Figure 1) is present - respectively - between the VMSCNLR (201) and the SGSN (204) of the network (20) and between the VMSCNLR (301) and the SGSN (304) of the network (30). Therefore: - The SGSN (304) of the network (30) performs paging to the telephone (40) for any establishment of a received call. - The `attach 'and registration procedures for networks (20) and (30) are performed at SGSNs (204) and (304), respectively. As for the 'attach' procedure and registration to the VPLMNcs (30) network, there will therefore be an attempt to register GSM / GPRS / UMTS on the network (30) in the same way: the registration requests will be received by the SGSN (304) will be responsible for informing VMSCNLR (301). It will be shown later that it is possible to perform combined `attach 'and record procedures on the VPLMNcs (30) and VPLMNps (20) networks even if: o Only circuit-switched communications are possible on the network. network (30) o Only packet-switched communications are possible on the network (20) The following description explains the synoptics corresponding to the different procedures (authentication, mobility, control of incoming / outgoing communications, etc.) .

In general, the different steps of the synoptics describe the messages exchanged between a source equipment and a destination equipment. A message exchanged in the 'core' part of each network is represented at its application layer (MAP, ISUP, BSSAP +) and its interconnection layer (SCCP), according to the following formalisms: For MAP and BSSAP + applications: MAP_APPLICATION_ID (or BSSAP + _APPLICATION _ID) (Parameters) SCCP CdPA: (GT, SSN, TT) - SCCP CgPA: (GT, SSN, TT) For ISUP applications: ISUP MESSAGE (Parameters) Where: - CdPA, CgPA: addresses WG of the receiving and transmitting equipment, respectively Recording, authentication, mobility management on the network 25 VPLMNps (20) On the VPLMNps (20) network only packet-switched communications are allowed. Examination of Figure 6 shows that this condition can be satisfied at the act of registration / authentication / mobility management. Subsequently, it will be shown that this condition is satisfied also at the initiation of a communication session by the telephone (40). Figure 6 details the equipment and the message exchanges to ensure the registration, authentication and location procedures between the network (10) and the VPLMNps network (20).

Following the activation of the mobile (40), the step 508 of Figure 5 ends with the operation 'Registration on the VPLMNps with IMSIps'. It is this operation which is detailed in Figure 6 and whose numbered steps are commented on immediately: 1. (Step 1, Figure 6) a signaling message `GMM ATTACH REQUEST 'is sent from the mobile (40) to the SGSN (204) of the visited network VPLMNps (20). The syntax and parameters of the `GMM_ATTACH_REQUEST 'message are defined in 3GPP TS 24.008: 3rd Generation Partnership Project; Technical Specification Core Network and Terminais Group; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 (Release 9). The main parameters of this message are: - Mobile Station Network Capabilities (mandatory parameter): this parameter makes it possible to inform the VPLMNps (20) about the characteristics of the mobile (40) with respect to the GPRS network. The various pieces of information that are part of this parameter are described in section 10.5.5.2 of 3GPP TS 24.008. In the case of the system according to the invention, the important information elements are related to SMS: the mobile (40) allows the transmission / reception of SMS only on a circuit switched network. - Attach Type (mandatory parameter): with this parameter the mobile (40) informs the VPLMNps (20) that it supports simultaneous recording on circuit and packet switched networks. - Ciphering Key Sequence Number (parameter required in the case of an authentication): this is the parameter that allows the network (20) to identify the KCGPRS encryption key stored in the SIM card (150) (see Figure 3) . - Mobile Identity (mandatory parameter): with this parameter the mobile (40) identifies itself with the VPLMNps (20); according to section 10.5.5.2 of the 3GPP TS 24.008 standard, it can be an IMSI, an TMSI or a P-TMSI. We will make the assumption here that - in the case of the first startup of the mobile (40) once the subscriber arrived in Hong Kong - no TMSI or P-TMSI is available. Therefore, in the case of the system according to the invention, Mobile Identity = IMSIps (as shown in Figure 6). - Old routing area identification (RAI) (mandatory parameter): with this parameter the mobile (40) informs the VPLMNps (20) on the last RAI, which is defined in section 10.5.5.15 of the 3GPP TS 24.008 standard and explained synthetically in the Glossary section. In the exemplary context described the last RAI refers to the HPLMNps network of the OPERATORcs-ps. It is therefore useless for the visited network VPLMNps (20). - MS Radio Access capability (mandatory parameter): this parameter informs the VPLMNps (20) about the characteristics of the mobile (40) with respect to its ability to support the different radio channels. The various pieces of information that are part of this parameter are described in section 10.5.5.12a of 3GPP TS 24.008. Examples of these elements of information: the support / non-support of different 3G technologies, 4G (LTE), etc. This parameter is important because it can impact how the heart network of the VPLMNps (20) processes the operations of the mobile (40). 2. (Step 2, Figure 6) A message message `MAP_SEND_AUTHENTICATION INFO 'is sent from the SGSN (204) of the visited network VPLMNps (20) to the HLR (101) of the network (10). The syntax and parameters of the `MAP SEND AUTHENTICATION INFO 'message are defined in 3GPP TS 09.02: 3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile Application Part (MAP) specification (Release 1998). The message is routed to the HLR (101) through the GMSC (102). The main parameters of this message are: At the MAP level: the IMSIps (indicated in Figure 6) with which the mobile (40) has identified itself with the SGSN (204) At the SCCP level: - Transmission GT address: SGSN (204) (E.164 number), SSN = 149 (SGSN), TT = 0 - GT destination address: MGTps (E.214 number derived from IMSIps), SSN = 6 (HLR), TT = 0. The MGTps allows the initialization of SCCP routing between the SGSN (204) and the HLR (101). 3. (Step 3, Figure 6) A MAP_ SEND _ AUTHENTICATION _ INFO _ACK message is returned from the HLR (101) of the network (10) to the SGSN (204) of the visited network VPLMNps (20). The syntax and parameters of the `MAP SEND AUTHENTICATION INFO ACK 'message are defined in the _ _ _ _ 3GPP TS 09.02: 3rd Generation Partnership Project standard; Technical Specification Group Core Network; Mobile Application Part (MA P) specification (Release 1998). The message is routed to the SGSN (204) through the GMSC (102). The main parameters of this message are: MAP level: IMSIps and authentication parameters (RAND and SRES). This triplette (IMSIps, RAND, SRES) is known as `vector 'or' triplet '(shown in Figure 6). The SRES parameter was calculated by the HLR (101) with the secret integrity key KI and using the authentication algorithm called `A3 'At the SCCP level: - Transmission GT address: HLR (101) (number E.164), SSN = 6 (HLR), TT = 0 - GT destination address: SGSN (204) (E.164 number), SSN = 149 (SGSN), TT = 0 4. (Step 4, Figure 6 ) a message message `GMM_AUTHENTICATION_AND_CIPHERING_REQUEST 'is sent from the SGSN (204) of the visited network VPLMNps (20) to the mobile (40). The syntax and parameters of the `GMM AUTHENTICATION_AND_CIPHERING_REQUEST 'message are defined in 3GPP TS 24.008: 3rd Generation Partnership Project; Technical Specification Core Network and Terminais Group; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 (Release 9). The main parameters of this message are: - Ciphe ring algorithm (mandatory parameter): this parameter is used to instruct the mobile (40) on the encryption algorithm to use on the radio channel. This parameter is described in section 10.5.5.3 of 3GPP TS 24.008. Indeed, the 3GPP standards define eight possible encryption algorithms; they are grouped under the acronym `A5 '. - Authentication parameter "RAND)): this is the parameter that is part of the triplette (IMSIps, RAND, SRES) received from the HLR (101) in the Step 3 to allow the mobile (40) to calculate a SRES 'with secret integrity key KI and using the authentication algorithm said `A3', according to the structure (270) of the SIM card (150) (see Figure 2). - Ciphering Key Sequence Number (mandatory parameter in the case of an authentication): see Step 1. - Authentication Parameter "AUTN" (mandatory parameter in the case of an authentication): this is the parameter that allows the mobile (40) to authenticate the network, particularly in the case of 3G and 4G networks. 5. (Step 5, Figure 6) a message message `GMM_AUTHENTICATION_AND_CIPHERING_RESPONSE 'is returned from the mobile (40) to the SGSN (204) of the visited network VPLMNps (20). The syntax and parameters of the `GMM_AUTHENTICATION_AND_CIPHERING_RESPONSE 'message are defined in 3GPP TS 24.008: 3rd Generation Partnership Project; Technical Specification Core Network and Terminais Group; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 (Release 9). The main parameter of this message is the Authentication Response Parameter "SRES", calculated by the SIM card (150) with the secret integrity key KI and using the authentication algorithm called `A3 ', according to the structure (270). This parameter (described in section 10.5.5.3 of 3GPP TS 24.008) allows the SGSN (204) to verify the identity of the mobile (40). 6. (Step 6, Figure 6) a% AAP UPDATE GPRS LOCATION 'signaling message is sent from the SGSN (204) of the visited network VPLMNps (20) to the HLR (101) of the network (10). The syntax and parameters of the `MAP_UPDATE GPRS LOCATION 'message are defined in 3GPP TS 09.02: 3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile Application Part (MAP) specification (Release 1998). The message is routed to the HLR (101) through the GMSC (102). The main parameters of this message are: At the MAP level: the IMSIps (indicated in Figure 6) with which the mobile (40) has identified itself with the SGSN (204) At the SCCP level: - Transmission GT address: SGSN (204) (E.164 number), SSN = 149 (SGSN), TT = 0 - GT destination address: HLR (101) (E.164 number), SSN = 6 (HLR), TT = 0. 7. (Step 7, Figure 6) A message message `MAP_INSERT_ SUBSCRIBER DATA 'is sent from the HLR (101) of the network (10) to the SGSN (204) of the visited network VPLMNps (20). This message is sent in response to the `MAP UPDATE GPRS LOCATION 'message in Step 6. With this message, the SGSN (204) controlling the subscriber knows the profile and access rights to the network (20). this last. The syntax and parameters of the MAP_INSERT_SUBSCRIBER_DATA message are defined in 3GPP TS 09.02: 3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile Application Part (MAP) specification (Release 1998). In the context of the system according to the invention, the main parameters of this message are: At the MAP level (section 8.8.1 of the 3GPP TS 09.02 standard): 3 00 3 4 2 4 50 - Network access mode (parameter 'conditions') : This parameter makes it possible to force the access of the mobile (40) to the only 'packet-switched' part of the network (20). It is described in section 17.7.1 of 3GPP TS 09.02. Indeed, the HLR 5 (101) is aware that the mobile (40) is registering the network (20) with its IMSIps: it can therefore decide to return the value 'onlySGSN' in correspondence of this parameter. In the system according to the invention, the use of the Network access mode parameter is a first option for the HLR (101) to prevent any circuit switched communication to the mobile (40). This option will be referred to later as 'OPTION Network Access Mode OnlySGSN' - the IMSIps (parameter 'conditioner'): with which the mobile (40) 15 has identified itself with the SGSN (204) - Operator Determined Barring General data (204) 'conditional' parameter): this parameter is part of the Subscriber Status' and describes the communication categories that are prohibited in the visited network VPLMNps (20), including any incoming / outgoing call and the supplementary services (such as forwarding). call). Note: Any information related to the prohibition of additional calls / services is ignored by the SGSN (204). - GPRS Subscription Data (parameter 'conditioner): this parameter describes the type of `PDP-contexts' to which the subscriber has subscribed. - MSISDN ('conditional' parameter): the telephone number of the subscriber. Note: in principle, this parameter is not necessary because the network registration VPLMNps (20) 30 comprises the consumption of only packet switching services. Subsequently, the explanations in Figure 8 will show that the MSISDN can be used by the SGSN (204) for setting up a packet-switched communication. At the SCCP level: - Transmission GT address: HLR (101) (E.164 number), SSN = 6 (HLR), TT = 0 - GT destination address: SGSN (204) (E.164 number), SSN = 149 (SGSN), TT = 0 8. (Step 8, Figure 6) a message message `MAP_INSERT_ SUBSCRIBER DATA RESPONSE 'is returned from the SGSN (204) of the visited network VPLMNps (20) to the HLR (101) of the network (10), in order to acknowledge the message `MAP _INSERT_ SUBSCRIBER DATA 'from the previous step. The main parameters of this message are: At the MAP level: any parameter is optional (the contents of the message can be empty), except in case of error. At the SCCP level: - Transmission GT address: SGSN (204) (E.164 number), SSN = 149 (SGSN), TT = 0 - GT destination address: HLR (101) (E.164 number), SSN = 6 (HLR), TT = 0 9. ([step 9, Figure 6) a% AAP UPDATE GPRS LOCATION RESPONSE 'signaling message is returned from the HLR (101) to the SGSN (204) of the visited network VPLMNps (20). ), in order to acknowledge the `MAP_UPDATE_GPRS_LOCATION 'message in Step 6. The main parameters of this message are: At MAP level: any parameter is optional (the contents of the message may be empty), except in case of error. At the SCCP level: - Transmission GT address: HLR (101) (E.164 number), SSN = 6 (HLR), TT = 0 - GT destination address: SGSN (204) (E.164 number), SSN = 149 (SGSN), TT = 0 10. (Step 10, Figure 6) a 'BSSAP + LOCATION UPDATE REQUEST' signaling message is sent from the SGSN (204) of the visited network VPLMNps (20) to the VMSCNLR (201) of the same network. With this message, the SGSN (204) controlling the subscriber requests the VMSCNLR (201) to initiate the registration and location procedures for the 'circuit-switched' portion of the VPLMNps (20) network. The syntax and parameters of the `BSSAP + _LOCATION_UPDATE_REQUEST 'message are defined in 3GPP TS 29.018: 3rd Generation Partnership Project; Technical Specification Core Network and Terminais Group; General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification (Release 11). Attention: in Figure 6, the arrow corresponding to Step 10. is in dashed line. Indeed, with reference to Step 7, if the HLR (101) returned the parameter `Network Access Mode 'according to the option described as' OPTION Network Access Mode OnlvSGSN', Steps 10. to 15. are not not executed. In the context of the system according to the invention, the main parameters of the message `BSSAP + LOCATION UPDATE REQUEST 'are: At the BSSAP + level (section 17.1.11 of the 3GPP TS 29.018 standard): - the IMSIps (mandatory parameter): with which the mobile (40) has identified itself with the SGSN (204) - Update type (mandatory parameter): this parameter indicates to the VMSCNLR (201) that a 'Location Update' procedure is the only one necessary; indeed, the procedures of 'Attachment' and authentication have already been executed. - New Cell global identity: This parameter provides the identity of the cell on which the phone is 'encamped'. The format of this parameter is defined in section 11.3.9 of 3GPP TS 48.018: "Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)". As explained later, the identity of the cell is one of the parameters that the core network (in this case the SGSN (204)) knows through an exchange of messages with the 'Base Station Subsystem' (BSS). Thanks to the parameter New Cell global identity the VMSCNLR (201) will be able to know the 'Location Area' in which the mobile (40) is currently located (even if no circuit-switched communication is allowed on the network (20) ). At SCCP level: - Transmission GT address: SGSN (204) (E.164 number), SSN = 149 (SGSN), TT = 0 - GT destination address: VMSCNLR (201) (E.164 number), SSN = 7 (VMSCNLR), TT = 0 11. (Step 11, Figure 6, dotted line according to the adoption of the "Network Access Mode OnlySGSN OPTION" from the HLR (101)) a message message `MAP_UPDATE_LOCATION 'is sent from the VMSCNLR (201) of the visited network VPLMNps (20) to the HLR (101) of the network (10) The syntax and parameters of the message% AAP_ UPDATE_LOCATION 'are defined in the 3GPP standard TS 09.02: 3rd Generation Partnership Project Technical Specification Group Core Network Mobile Application Part (MA P) specification (Release 1998) The message is routed to the HLR (101) through the GMSC (102) The main parameters of this message are: At MAP level: the IMSIps (shown in Figure 6) with which the mobile (40) has identified itself to the SGSN (204) At the SCCP level: - Transmit GT address: VMSCNLR (201) (naked E.164), SSN = 7 (VMSCNLR), TT = 0 - GT destination address: HLR (101) (E.164 number), SSN = 6 (HLR), TT = 0. 12. (Step 12, Figure 6, dashed line according to the adoption of I "OPTION Network Access Mode_OnlySGSN 'from the HLR (101)) a message message` MAP_INSERT_ SUBSCRIBER DATA' is sent from the HLR (101) of the network (10) to the VMSCNLR (201) of the visited network VPLMNps (20). This message is sent in response to the `MAP_UPDATE_ LOCATION 'message in Step 11. With this message, the VMSC / VLR (201) knows the profile and access rights to the network (20) of the latter. The syntax and parameters of the `MAP INSERT SUBSCRIBER DATA 'message are defined in 3GPP TS 09.02: 3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile Application Part (MAP) specification (Release 1998). In the context of the system according to the invention, the main parameters of this message are: At the MAP level (section 8.8.1 of the 3GPP TS 09.02 standard): the IMSIps (parameter 'conditioner'): with which the mobile (40 ) has identified itself with the SGSN (204) - Operator Determined General Data Barring (parameter 'conditionner'): this parameter is part of the Subscriber Status' and describes the categories of communication that are prohibited in the visited network VPLMNps (20), in particular any incoming / outgoing call and additional services (such as call transfer).

At SCCP level: - Transmission GT address: HLR (101) (E.164 number), SSN = 6 (HLR), TT = 0 - GT destination address: VMSCNLR (201) (E.164 number), SSN = 7 (VMSCNLR), TT = 0 13. ([Step 13, Figure 6, dashed line following the adoption of I "OPTION Network Access Mode OnlySGSN 'from the HLR (101)) a signaling message` MAP INSERT SUBSCRIBER DATA RESPONSE 'is returned from the _ _ VMSCNLR (201) of the visited network VPLMNps (20) to the HLR (101) of the network (10), in order to acknowledge the message `MAP INSERT _SUBSCRIBER DATA' from the previous step The main parameters of this message are: At the MAP level: any parameter is optional (the contents of the message can be empty), except in case of error.

At SCCP level: - Transmission GT address: VMSCNLR (201) (E.164 number), SSN = 7 (SGSN), TT = 0 - GT destination address: HLR (101) (E.164 number), SSN = 6 (HLR), TT = 0 14. (Step 14, Figure 6, dotted line according to the adoption of I "OPTION Network Access Mode OnlySGSN 'from the HLR (101)) a signaling message MAP_UPDATE_ LOCATION RESPONSE' is returned from the HLR (101) to the VMSCNLR (201) of the visited network VPLMNps (20), in order to acknowledge the message `MAP_UPDATE_LOCATION 'in Step 11. The main parameters of this message are: MAP level: all parameter is optional (the contents of the message may be empty), except when an error occurs.

At SCCP level: - Transmission GT address: HLR (101) (E.164 number), SSN = 6 (HLR), TT = 0 - GT destination address: VMSCNLR (201) (E.164 number), SSN = 7 (VMSCNLR), TT = 0 15. (Step 15, Figure 6, dotted line according to the adoption of I "OPTION Network Access Mode OnlySGSN 'from the HLR (101)) a signaling message` 13SSAP + LOCATION UPDATE ACCEPT 'is returned from the VMSCNLR (201) of the visited network VPLMNps (20) to the SGSN (204) of the same network in response to the message in Step 10. The syntax and parameters of the `13SSAP + LOCATION UPDATE_ACCEPT' message are defined in 3GPP Standard TS 29.018: 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; General Packet Radio Service (GPRS); GPRS Serving GPRS Support Node (SGSN); In the context of the system according to the invention, the main parameters of the message 13SSAP + LOCATION UPDATE_ACCEPT 'are : At the BSSAP + level (section 17.1.9 of the 3GPP TS 29.018 standard): - the IMSIps (mandatory parameter): with which the mobile (40) has identified itself with the SGSN (204) - Location Area Identifier (mandatory parameter ): This parameter is calculated by the VMSCNLR (201) using the New Cell global identity parameter (see Step 10). - New TMSI (optional parameter): this parameter (defined in section 18.4.17 of 3GPP TS 29.018) provides the temporary identity of the mobile (40) to the SGSN (204) with respect to the circuit-switched part 'of VPLMNps (20). In Figure 6, the New TMSI is denoted TMSIps At the SCCP level: - Transmission GT address: VMSCNLR (201) (E.164 number), SSN = 7 (VMSCNLR), TT = 0 - GT destination address: SGSN (204) (E.164 number), SSN = 149 (SGSN), TT = 0 16. (Step 16, Figure 6) a 'GMM_ATTACH_ACCEPT' signaling message is sent from the SGSN (204) of the visited network VPLMNps (20). ) to the mobile (40). The syntax and parameters of the `GMM_ATTACH_REQUEST 'message are defined in 3GPP TS 24.008: 3rd Generation Partnership Project; Technical Specification Core Network and Terminais Group; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 (Release 9). The main parameters of this message are: - Attach Result (mandatory parameter): with this parameter the VPLMNps (20) informs the mobile (40) if an 'Attach' combined with the 'circuit switched' and 'switched' part. package 'took place. In the case of the adoption of the "OPTION Network Access Mode_OnlySGSN" on the part of the HLR (101) the only `Attach 'to the' packet switched 'part has occurred - Routing Area Identification (mandatory parameter): Thanks to the New Cell global identity parameter (see Step 10), the SGSN (204) will be able to know the 'Routing Area' in which the mobile (40) is currently located - Allocated P-TMSI (optional parameter This parameter provides temporary identity to the mobile (40) relative to the SGSN (204) that controls it.In Figure 6, the Allocated P-TMSI is denoted P-TMSIps - MS Identity (optional parameter): this parameter provides mobile (40) temporary identity against VMSCNLR (201), shown in parentheses in Figure 6 Indeed, its presence depends on the HLR's "Network Access Mode OnlySGSN" (101). In the case of an 'Attach' combined with the 'circuit-switched' and 'packet-switched' part, the MS Identity is the TMSIps received by the SGSN (204) in Step 15. 17. (Step 17, Figure 6) a 'GMM_ATTACH_COMPLETE' signaling message is sent from the mobile (40) to the SGSN (204) of the visited network VPLMNps (20). The syntax and parameters of the `GMM_ATTACH_REQUEST 'message are defined in 3GPP TS 24.008: 3rd Generation Partnership Project; Technical Specification Core Network and Terminais Group; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 (Release 9). This message is mandatory because at least the P-TMSIps was sent by the SGSN (204) in the previous step. 18. (Step 18, Figure 6, dashed line following the adoption of I "OPTION Network Access Mode_OnlySGSN 'from HLR (101)) a' 13SSAP + TMSI REALLOCATION COMPLETE 'signaling message is returned from the SGSN (204) from the visited network VPLMNps (20) to the VMSCNLR (201) The syntax and parameters of the `BSSAP + _ TMSI REALLOCATION COMPLETE 'message are defined in the 3GPP standard TS 29.018: 3rd Generation Partnership Project and Technical Specification Core Network and Terminals General Packet Radio Service (GPRS); GPRS Supporting Node (SGSN); Gs interface layer 3 specification (Release 11). The main parameters of the `BSSAPTMS1 REALLOCATION COMPLETE 'message are: At BSSAP + level ( section 17.1.22 of 3GPP TS 29.018): - the IMSIps (mandatory parameter, indicated in Figure 6): identifier with which the mobile (40) has identified itself with the SGSN (204) At the SCCP level: - Address Issue WG: SGSN (204) (E.164 number ), SSN = 149 (SGSN), TT = 0 - GT destination address: VMSCNLR (201) (E.164 number), SSN = 7 (VMSCNLR), TT = 0 Registration, authentication, network mobility management VPLMN (30) Once the procedure of registration, authentication, mobility management on the network VPLMNps (20) has been completed, the mobile (40) must also register on the network VPLMNIcs (30). With reference to Figure 5, step 509 ends with the operation 'Saving VPLMIVcs with IMSIcs'. On the VPLMNcs network (30) only circuit switched communications are allowed. As already explained in the Preamble of the Operational Procedures section (Network Registration, Authentication, Mobility Management), according to Figure 1, the VPLMNcs (30) network operates in the 'NAME' mode: The `Gs' interface (dashed line) (90) in Figure 1) is present between the VMSCNLR (301) and the SGSN (304) of the network (30). Therefore, the SGSN (304) of the network (30) performs the gpaging 'to the telephone (40) for any establishment of a received call. The registration and location procedures on the VPLMNcs (30) network - described in Figure 7 - are very similar to those described in Figure 6. The differences, step-by-step, are as follows: 1. ( Step 1, Figure 7) a GMM ATTACH REQUEST message is sent from the mobile (40) to the SGSN (304) of the visited network VPLMNcs (30). The main parameters of this message are: - Mobile Station Network Capabilities: description identical to that of Step 1 of Figure 6, replacing VPLMNps (20) by VPLMNcs (30). - Attach Type: description identical to that of Step 1 of Figure 6, replacing VPLMNps (20) by VPLMNIcs (30). - CIPhering Key Sequence Number description identical to that of Step 1 of Figure 6, replacing network (20) by network (30). - Mobile Identity: description identical to that of Step 1 of Figure 6, replacing VPLMNps (20) by VPLMNIcs (30). Note: in the case of the system according to the invention, Mobile Identity = IMSIcs (as shown in Figure 7). - Old routing area identification (RAI): description identical to that of Step 1 of Figure 6, replacing VPLMNps (20) by VPLMNcs (30). - MS Radio Access capability: same description as in Step 1 of Figure 6, replacing VPLMNps (20) with VPLMNcs (30). 2. (Step 2, Figure 7) A message message `MAP_SEND_AUTHENTICATION_INFO 'is sent from the SGSN (304) visited network VPLMNcs (30) to the HLR (101) of the network (10). The main parameters of this message are: At the MAP level: the IMSIcs (shown in Figure 7) with which the mobile (40) has identified itself to the SGSN (304) At the SCCP level: - Transmission GT address: SGSN (304) (E.164 number), SSN = 149 (SGSN), TT = 0 - GT destination address: MGTcs (E.214 number derived from IMSIcs), SSN = 6 (HLR), TT = 0. The MGTcs allows the initialization of SCCP level routing between the SGSN (304) and the HLR (101). 3. (Step 3, Figure 7) A message message `MAP_SEND_AUTHENTICATION_INFO_ACK 'is returned from the HLR (101) of the network (10) to the SGSN (304) of the visited network VPLMNcs (30). The main parameters of this message are: At the MAP level: the IMSIcs and the authentication parameters (RAND and SRES). This triplette is - obviously - different from that described in Figure 6. At the SCCP level: - Transmission GT address: HLR (101) (E.164 number), SSN = 6 (HLR), TT = 0 - GT address of destination: SGSN (304) (E.164 number), SSN = 149 (SGSN), TT = 0 4. (Step 4, Figure 7) a signaling message `GMM_AUTHENTICATION_AND_CIPHERING_REQUEST 'is sent from the SGSN (304) of the visited network VPLMNcs (30) to the mobile (40). The main parameters of this message are: - Ciphering algorithm: description identical to that of Step 4 of Figure 6. - Authentication parameter "RAND": description identical to that of Step 4 of Figure 6. Obviously, the value of "RAND" is different for authentication on the network (30). - Ciphering Key Sequence Number: see Step 1. - Authentication Parameter "AUTN" description identical to that in Step 4 of Figure 6. 5. (Step 5, Figure 7) a signaling message `GMM_AUTHENTICATION_AND_CIPHERING_RESPONSE 'is returned from the mobile (40) to the SGSN (304) of the visited network VPLMNcs (30). The description is identical to that of Step 5 of Figure 6, replacing SGSN (204) with SGSN (304). Obviously, the value of "SRES" is different for authentication on the network (30). 6. (Step 6, Figure 7) A MAP UPDATE GPRS LOCATION signaling message is sent from the SGSN (304) of the visited network VPLMNcs (30) to the HLR (101) of the network (10). The main parameters of this message are: At the MAP level: the IMSIcs (shown in Figure 7) with which the mobile (40) has identified itself to the SGSN (304) At the SCCP level: - Transmission GT address: SGSN (304) (E.164 number), SSN = 149 (SGSN), TT = 0 - GT destination address: HLR (101) (E.164 number), SSN = 6 (HLR), TT = 0. 7. (Step 7, Figure 7) A message message `MAP_INSERT_ SUBSCRIBER DATA 'is sent from the HLR (101) of the network (10) to the SGSN (304) of the visited network VPLMNcs (30). This message is sent in response to the `MAP UPDATE GPRS LOCATION 'message in Step 6. In the context of the system according to the invention, the main parameters of this message are: At MAP level (section 8.8.1 of the 3GPP standard TS 09.02): - Network access mode (parameter 'conditioner'): this parameter makes it possible to force the access of the mobile (40) to the only 'circuit-switched' part of the network (30). It is described in section 17.7.1 of 3GPP TS 09.02. Indeed, the HLR (101) is aware that the mobile (40) is registering the network (30) with its IMSIcs: it will return the value conlyMSC 'in correspondence of this parameter.

In the system of the invention, the use of the Network access mode parameter allows the HLR (101) to prevent packet-switched communication to the mobile (40). - the IMSIcs ('conditional' parameter): with which the mobile (40) has identified itself with the SGSN (304) - Operator Determined Barring General data (parameter 'conditionner'): this parameter is part of the Subscriber Status' and described the categories of communication that are prohibited in the visited network VPLMNcs (30): in the case of the system according to the invention, any incoming / outgoing call and additional services (such as call transfer) are allowed. It will therefore be possible for the SGSN (304) to send paging messages (incoming call) to the mobile (40). - MSISDN (parameter 'conditioner'): the telephone number of the subscriber. This parameter is used by the SGSN (304) and the VMSC / VLR (301) for the incoming call to the mobile (40). At SCCP level: - Transmission GT address: HLR (101) (E.164 number), SSN = 6 (HLR), TT = 0 - GT destination address: SGSN (304) (E.164 number), SSN = 149 (SGSN), TT = 0 8. (Step 8, Figure 7) This step is identical to Step 8 of Figure 6, replacing SGSN (204) with SGSN (304). 9. (Step 9, Figure 7) This step is identical to Step 9 of Figure 6, replacing SGSN (204) with SGSN (304) and VPLMNps (20) with VPLMNcs (30) 10. (Step 10, Figure 7) A signaling message `BSSAP + LOCATION UPDATE REQUEST 'is sent from the SGSN (304) of the visited network VPLMNcs (30) to the VMSCNLR (301) of the same network. With this message, the SGSN (304) controlling the subscriber requests the VMSCNLR (301) to initiate the registration and location procedures for the 'circuit-switched' portion of the VPLMNcs network (30). Caution: unlike Figure 6, the corresponding arrow in Step 10 is in solid line. Indeed, with reference to Step 7, the HLR (101) returned the `Network Access Mode 'parameter allowing only access to the circuit switched portion of the network (30). In the context of the system according to the invention, the main parameters of the `BSSAP + LOCATION UPDATE REQUEST 'message are: At the BSSAP + level (section 17.1.11 of the 3GPP TS 29.018 standard): - the IMSIcs, with which the mobile (40 ) has identified itself with the SGSN (304) - Update type: description identical to that of Step 10 of Figure 6. - New Cell global identity (mandatory parameter): description identical to that of Step 10 of the Figure 6, replacing SGSN (204) with SGSN (304) and VMSCNLR (201) with VMSCNLR (301). At SCCP level: - Transmission GT address: SGSN (304) (E.164 number), SSN = 149 (SGSN), TT = 0 - GT destination address: VMSCNLR (301) (E.164 number), SSN = 7 (VMSCNLR), TT = 0 11. (Step 11, Figure 7) a MAP UPDATE LOCATION signaling message is sent from the VMSCNLR (301) of the visited network VPLMNcs (30) to the HLR (101) of the network (10). The main parameters of this message are: At the MAP level: the IMSIcs (shown in Figure 7) with which the mobile (40) has identified itself with the SGSN (304) At the SCCP level: - Transmit GT address: VMSCNLR (301) (E.164 number), SSN = 7 (VMSCNLR), TT = 0 - GT destination address: HLR (101) (E.164 number), SSN = 6 (HLR), TT = 0. 12. (Step 12, Figure 6, a message message `MAPINSERT_ SUBSCRIBER DATA 'is sent from the HLR (101) of the network (10) to the VMSCNLR (301) of the visited network VPLMNcs (30) With this message, the VMSC / VLR (301) knows the profile and access rights of the subscriber to the network (30) In the context of the system according to the invention, the main parameters of this message are: At the MAP level (section 8.8.1 of the 3GPP TS 09.02 standard): - the IMSIcs ('conditioner' parameter): with which the mobile (40) has identified itself with the SGSN (304) - Operator Determined Barring General data (parameter 'conditioner'): no prohibition of call rant / outgoing and additional services (such as call transfer) in the visited network VPLMNIcs (30) At SCCP level: - Transmission GT address: HLR (101) (E.164 number), SSN = 6 ( HLR), TT = 0 - Destination GT address: VMSCNLR (301) (E.164 number), SSN = 7 (VMSCNLR), TT = 0 13. (Step 13, Figure 7): This step is identical to the Step 13 of Figure 6, replacing VMSCNLR (201) with VMSCNLR (301). 14. (Step 14, Figure 7): This step is identical to Step 14 of Figure 6, replacing VMSCNLR (201) with VMSCNLR (301) and VPLMNps (20) with VPLMNcs (30). 15. (Step 15, Figure 7): A signaling message `BSSAP + LOCATION UPDATE_ACCEPT 'is returned from the VMSCNLR (301) of the visited network VPLMNIcs (30) to the SGSN (304) of the same network in response to the message of the Step 10. In the context of the system according to the invention, the main parameters of the `BSSAP + _LOCATION_UPDATE_ACCEPT 'message are: At the BSSAP + level (section 17.1.9 of the 3GPP TS 29.018 standard): - the IMSIcs (mandatory parameter): with which the mobile (40) has identified itself with the SGSN (304) - Location Area Identifier (mandatory parameter): this parameter is calculated by the VMSCNLR (301) thanks to the received New Cell global identity parameter. - New TMSI (optional parameter): This parameter provides the temporary identity of the mobile (40) to the SGSN (304) with respect to the 'circuit-switched' part of the VPLMNcs (30). In Figure 7, the New TMSI is denoted TMSIcs At the SCCP level: - Transmission GT address: VMSCNLR (301) (E.164 number), SSN = 7 (VMSCNLR), TT = 0 - GT destination address: SGSN (304) (E.164 number), SSN = 149 (SGSN), TT = 0 16. (Step 16, Figure 7) a 'GMM_ATTACH_ACCEPT' signaling message is sent from the SGSN (304) of the visited network VPLMNcs (30) ) to the mobile (40). The main parameters of this message are: - Attach Result (mandatory parameter): with this parameter the VPLMNcs (30) informs the mobile (40) if an 'Attach' combined with the 'circuit switched' and 'switched' part. package 'took place. In the case of the system according to the invention a combined 'Attach' has taken place. - Routing Area Identification: identical parameter to that of Step 16 of Figure 6, replacing SGSN (204) by SGSN (304). - Allocated P-TMSI: identical parameter to that of Step 16 of Figure 6, replacing SGSN (204) by SGSN (304). In Figure 6, the Allocated P-TMSI is denoted P-TMSIcs - MS Identity: same parameter as in Step 16 of Figure 6, replacing SGSN (204) with SGSN (304), VMSCNLR (201) with VMSCNLR (301) and TMSIps by TMSIcs. 17. (Step 17, Figure 7) This step is identical to Step 17 of Figure 6, replacing SGSN (204) with SGSN (304) and VPLMNps (20) with VPLMNcs (30). 18. (Step 18, Figure 7), a signaling message `BSSAP + _TMSI_REALLOCATION_COMPLETE 'is returned from the SGSN (304) of the visited network VPLMNcs (30) to the VMSCNLR (301). The main parameters of the `BSSAP + _ TMSI REALLOCATION COMPLETE 'message are: At the BSSAP + level (section 17.1.22 of the 3GPP TS 29.018 standard): - the IMSIcs (mandatory parameter, indicated in Figure 7): identifier with which the mobile (40) identified with SGSN (304) At SCCP level: - Transmission GT address: SGSN (304) (E.164 number), SSN = 149 (SGSN), TT = 0 - GT destination address : VMSCNLR (301) (E.164 number), SSN = 7 (VMSCNLR), TT = 0 Special cases: As already mentioned in the Preamble of the Operational Procedures section (network registration, authentication, mobility management), according to FIG. 1 shows that the VPLMNps (20) and VPLMNcs (30) networks operate in the 'NOM' mode: a simultaneous registration / authentication / localization procedure with respect to the SGSN (204) (respectively (304)) and the VMSCNLR (201) (respectively (301)) is therefore possible, as explained with the help of Figures 6 and 7. It may be that the network VPLMNps ( 20) and / or VPLMNcs (30) operates in the mode of 'NAME II' or 'NAME III'. In this case, the `Gs' interface (90) is not present. The following cases should be discussed: Case A.: The VPLMNps (20) network operates in the 'NAME' mode, the VPLMNcs (30) operates in 'NAME II' or 'NOM III' mode. In this case, there will be a simultaneous registration / authentication / location procedure with respect to SGSN (204) and VMSCNLR (201). On the other hand, a registration / authentication / localization procedure vis-à-vis only VMSCNLR (301) will be carried out: it will be possible for the VPLMNcs network (30) to send paging signaling only via the VMSCNLR ( Case B.: The network VPLMNps (20) operates according to the mode 'NAME II' or 'NAME III', the VPLMNcs (30) operates according to the mode 'NOM I'.

In this case, there will be a registration / authentication / location procedure vis-à-vis the only SGSN (204). On the other hand, a simultaneous registration / authentication / localization procedure vis-à-vis the SGSN (304) and the VMSCNLR (301) will be performed: it will be possible for the network VPLMNIcs (30) to send a paging signaling either via the VMSCNLR (301) or via the SGSN (304). Case C.: The networks VPLMNps (20) and VPLMNcs (30) operate according to the mode 'NAME II' or 'NAME III'. In this case, there will be a registration / authentication / localization procedure for only SGSN (204) and only VMSCNLR (301) will be performed: it will be possible for the VPLMNcs (30) network to send paging signaling only via the VMSC / VLR (301). It is also possible that a separate registration / authentication / location procedure on the VPLMNps (20) and VPLMNcs (30) networks is chosen by the mobile (40). In this case: For the recording on the network VPLMNIcs (30) the mobile (40) triggers a procedure `MM_LOCATION_UPDATING_REQUEST '(Section 9.2.15 of the 3GPP standard TS 24.008: 3rd Generation 10 Partnership Project, Technical Specification Group Core Network and Terminais, mobile radio interface Layer 3 specification, core network protocols, Stage 3 (release 9)). In the context of the system according to the invention, the main parameters of this procedure are: o Location updating type (mandatory parameter): with this parameter the mobile (40) triggers a recording / authentication / localization on the single network ( 30). o Mobile Identity (mandatory parameter): with this parameter the mobile (40) identifies itself to the VPLMNcs (30) with the IMSIcs. - For recording on the network VPLMNps (20) the mobile (40) 20 triggers a `GMMATTACI-LREQUEST 'procedure, already explained in Step 1 of Figures 6 and 7. In the case of an attachment request only to the network (20), the main parameters of this procedure is: o Attach Type: with this parameter the mobile (40) informs the VPLMNps (20) that it triggers a recording on the only packet-switched network. Anyone skilled in the art will recognize that, regardless of the method of registration / authentication / location adopted on the initiative of the mobile (40) and / or VPLMNps (20) and VPLMNcs (30) networks, the result of the procedure registration / authentication / location allows the mobile (40): - To register to the network VPLMNps (20) with the IMSIps identifier of the SIM card (150) for only packet-switched services - To register to the network VPLMNIcs (30) with the identifier IMSIcs of the SIM card (150) for the only switched circuit services Operational procedures for triggering a communication 5 data by the mobile (40) Preamble In order to simplify the description, it It is appropriate to focus on the logical connection between the mobile (40) and the SGSN (204) of the VPLMNps (20): the so-called 'Radio Access Network' part of the VPLMNps network (20) will not be mentioned. Indeed, any communication between the mobile (40) and the SGSN (204) is relayed by the 'Radio Access Network'; a correspondence exists between the identifiers of the mobile (40) at the level of the 'Radio Access Network' and the SGSN (204) according to the following rules: - thanks to the P-TMSIps received by the SGSN (204) (Step 16 of Figure 6 ), the mobile (40) can calculate: o The parameter `TLLI '(Temporary Link Layer Identifier) if the' Radio Access Network 'and type 2G or 2.5G o The parameter (RNT1' (Radio Network Temporary Identity) if the 20 'Radio Access Network' and type 3G - The SGSN (204) performs the same calculations - The mobile (40) triggers a data communication through a signaling procedure to the 'Radio Access Network', among the signaling parameters l 'TLLI' (or `RNTI ') is sent in. 25 In turn, the' Radio Access Network 'relays the signaling to the SGSN (204), so the SGSN (204) receives the TLLI' (where RNTI ') and can deduce from it the P-TMSIps of the mobile (40) requesting the establishment of the connection, therefore the mobile (40) does not need to send the P-TMSIps 30 for a request to establish a data connection. Triggering a data communication from the mobile (40) - Procedures Figure 8 details the equipment and the message exchanges to ensure the procedures for triggering a data communication between the mobile (40) and the VPLMNps network (20). ). According to the exemplary context of the invention, the subscriber (roaming in Hong Kong) has recorded on the VPLMNps (20) network for any packet switched communication. The network VPLMNps (20) belongs to the operator 'China Mobile HK'. The numbered steps are commented on immediately: 1. (Step 1, Figure 8) an 'ACTIVATE PDP CONTEXT REQUEST' signaling message is sent from the mobile (40) to the SGSN (204) of the visited network VPLMNps (20). The syntax and parameters of the 'ACTIVATE PDP CONTEXT REQUEST' message are defined in 3GPP TS 24.008: 3rd Generation Partnership Project; Technical Specification Core Network and Terminais Group; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 (Release 9). The main parameters of this message are: - Requested NSAP / (mandatory parameter): this parameter unambiguously identifies the communication session data; it is an integer number, randomly selected by the mobile (40) - Requested QoS (mandatory parameter): this parameter describes the constraints in terms of quality of service for the requested communication; information items such as rate and error rate are shown. - Access Point Name (APN) (optional parameter): The purpose of this parameter - usually present - is to identify the data network to which the subscriber wishes to connect. In addition, the Access Point Name allows the SGSN (204) to know the access point of such data network Note: as already explained in the Preamble, the identifier IMSIps (or P-TMSIps) of the mobile (40) is deduced by the SGSN (204) through its connection with the 'Radio Access Network', which carries the 'TLLI' (or `RNTI ') in its communication protocol. It is for this reason that the TLL1 '(or `RNTI') is indicated in gray in Figure 8. 2. (Step 2, Figure 8) The SGSN (204) sends a message of type 'QUERY' to the root server of Domain Name System (DNS): The goal is to obtain the IP address of the GGSN (104) in correspondence of the APN received from the mobile (40). In general, the root DNS server belongs to the operator of the international GRX interconnection network (60). The main parameter of the message 'QUERY' is the APN, which must contain: - The identifier of the operator providing the connection to the data network requested by the mobile (40), through its GGSN (104) . In the exemplary context of the system according to the invention (see Table 1 of the Preamble of section Operational procedure for powering up the mobile phone (40)) it is the identifier of the OPERATORcs_ps that must be present. For example, this identifier will be web.OPERATORcs-Ps.COm (the identifier format must comply with the GSMA IR.67 standard - DNS / ENUM Guidelines for Providers & GRX / IPX Providers, version 4.1) - The network identifier that contains - among the other devices - the DNS 'Authoritative' server (see Step 3 below). Still according to Table 1 of the Preamble of the section Mobile phone power up procedure (40) this identifier corresponds to the `MCC 'and` EVINCI' parts of the IMSIps (208XX). The APN parameter of the 'QUERY' message will therefore be : APN = web.

OPERATORcs-ps-com.mcc208.mncXX.gprs 3. ([step 3, Figure 8) The root DNS server returns a REFERRAL command to the SGSN (204) so that it can send a 'QUERY' command to a server again `Authoritative 'DNS; the `Authoritative 'server is - in general - part of the network that contains the GGSN (104). The `Authoritative 'server address is contained in the root DNS server database, corresponding to the network identifier received in Step 3 (mcc208.mnc) 0C.gprs). 4. (Step 4, Figure 8) The SGSN (204) sends a new message of type 'QUERY' to the DNS 'Authoritative' server: the goal is to obtain the IP address of the GGSN (104) in correspondence with the APN received from the mobile (40). As for Step 2, the main parameter of the message 'QUERY' is the APN, which must contain the identifier of the operator providing the connection to the data network requested by the mobile (40), through his GGSN (104). In the exemplary context of the system according to the invention and by way of example, this identifier will be web. OPERATEURcs_ps.com. Note: the network identifier is no longer needed because the DNS 'Authoritative' server is - functionally - part of the network (10). The APN parameter of the second message 'QUERY' will be: APN = web. OPERATORcs-Ps-com 5. (Step 5, Figure 8) The DNS 'Authoritative' server returns a RESPONSE 'message, which contains the IP address of the GGSN (104). This address is named @GGSN in Figure 8. 6. (Step 6, Figure 8) a 'CREATE PDP CONTEXT REQUEST' signaling message is sent from the SGSN (204) of the visited network VPLMNps (20) to the GGSN (101) of the network (10). The syntax and parameters of the `CREATE PDP CONTEXT REQUEST 'message are defined in 3GPP TS 29.060: 3rd Generation Partnership Project; Technical Specification Core Network and Terminais Group; General Packet Radio Service (GPRS); GPRS Tunneling Protocol (GTP) across the Gn and Gp interface (Release 9). The main parameters of this message are: - the IMSIps (parameter 'conditioner'): with which the mobile (40) has identified itself with the SGSN (204) - the MSISDN ('conditional' parameter): this parameter can be used by the GGSN (104) to provide the identity of the subscriber to any application server that requests secure access. - The parameters that unambiguously identify the 'tunnel' between the SGSN (204) and the GGSN (104): NSAPI, SGSN IP address (204), quality of service, etc. Note: The SGSN (204) can provide two IP addresses: a first address for signaling and a second address for the given traffic. - The 'End User Address' (conditional parameter): this parameter denotes the type of IP address to identify the mobile (40). In general, a dynamic IP address is provided to the mobile (40) through a Dynamic Host Configuration Protocol (DHCP) server which is part of the GGSN (104) functionally. 7. (Step 7, Figure 8) a CREATE PDP CONTEXT RESPONSE signaling message is sent from the GGSN (101) of the network (10) to the SGSN (204) of the visited network VPLMNps (20). The syntax and parameters of the `CREATE PDP CONTEXT RESPONSE 'message are defined in 3GPP TS 29.060. The answer just contains an acknowledgment message. 8. (Step 8, Figure 8) an 'ACTIVATE PDP CONTEXT ACCEPT' signaling message is sent from the SGSN (204) visited network VPLMNps (20) to the mobile (40). The syntax and parameters of the `ACTIVATE PDP CONTEXT ACCEPT 'message are defined in 3GPP TS 24.008: 3rd Generation Partnership Project; Technical Specification Core Network and Terminais Group; Mobile radio interface Layer 3 specification Core network protocols; Stage 3 (Release 9). The main parameters of this message are: - Negotiated NSAP / (mandatory parameter): this parameter unambiguously identifies the communication session data; it is an integer number, randomly selected by the mobile (40) - Negotiated QoS (mandatory parameter): this parameter describes the quality of service that the network can guarantee for the requested communication; information items such as rate and error rate are shown. - PDP Address (optional parameter): this parameter denotes the type of IP address assigned to the mobile (40). Although optional, this parameter is usually present because a dynamic IP address is assigned.

At the end of Step 8, a data communication is established between the mobile (40) and an IP server provided by an Internet Service Provider (ISP or ISP in Figure 8). The communication consists of three sections: A first section between the mobile (40) and the SGSN (204); the data passing through it is formatted according to 3GPP TS 04.65: 3rd Generation Partnership Project; Technical Specification Group Core Network; Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDCP) (Release 1999) A second section between the SGSN (204) and the GGSN (104); the data passing through it is formatted according to 3GPP TS 29.060: 3rd Generation Patinership Project; Technical Specification Core Network and Terminais Group; General Packet Radio Service (GPRS); GPRS Tunneling Protocol (GTP) across the Gn and Gp interface (Release 9) A third leg between the GGSN (104) and an Internet server (or lntranet) provided by the ISP (or ISP in Figure 8) Special cases: As already mentioned in the Preamble of the Operational section for powering up the mobile phone (40) (Table 1), the IMSIps with which the mobile (40) triggers the registration and establishment of a communication session with the network VPLMNps (20) depends on the roaming agreements. Thus, for a subscriber roaming in Mexico the IMSIps will be that of the operator Nextel (MCC-MNC = 316010). With respect to the procedure "Triggering a data communication from the mobile (40)", only Steps 2, 3, 4, 5 of Figure 8 are affected, according to the following explanations: 2. (Step 2, Figure 8) The main parameter (APIV) of the message 'QUERY' must contain: The identifier of the operator providing the connection to the data network requested by the mobile (40), through its GGSN (104). In the exemplary context of the system according to the invention and by way of example, this identifier will be web. OPERATORcs.ps.com (unchanged) - The network identifier that contains - among other devices - the DNS 'Authoritative' server (see Step 3). In the case of the roaming subscriber in Mexico, this identifier corresponds to the `MCC 'and` IVINC' part of the Nextel operator IMSIps (316010) The APN parameter of the 'QUERY' message will therefore be: APN = web . OPERATORcs_ps.com.mcc316.mnc010.gprs 3. (Step 3, Figure 8) The root DNS server returns a REFERRAL command to the SGSN (204) so that the latter can send a 'QUERY' command again to an 'Authoritative' server DNS in the case of the interconnection agreement between Nextel and the OPERATEURcs-ps, the `Authoritative 'server is - in general - part of the Nextel network, while the GGSN (104) is part of the HPLMNps network (10) OPERATORcs_ps. The `Authoritative 'server address is contained in the root DNS server database, corresponding to the network identifier received in Step 3 (mcc316.mnc010.gprs). 4. (Step 4, Figure 8) The SGSN (204) sends a new message of type 'QUERY' to the DNS 'Authoritative' server: the goal is to obtain the IP address of the GGSN (104) in correspondence with the APN received from the mobile (40). As for Step 2, the main parameter of the message 'QUERY' is the APN, which must contain the identifier of the operator providing the connection to the data network requested by the mobile (40), through his GGSN (104). In the exemplary context of the system according to the invention and by way of example, this identifier will be web. OPERATEURcs-ps-com. The APN parameter of the second message 'QUERY' will be: APN = web. OPERATORcs-ps-com 5. ([step 5, Figure 8) the DNS 'Authoritative' server returns a RESPONSE 'message, which contains the IP address of the GGSN (104) of the OPERATOR's HPLMNps (10) network. ps. This address is named @GGSN in Figure 8. It is obvious that the Nextel operator must configure its `Authoritative 'server so that any' QUERY 'message received with APN = web.OPERATORcs_ps.com can match the IP address of the GGSN (104); this configuration is part of the interconnection agreements between Nextel and the OPERATEURcs-PS - Operational procedures for triggering a mobile voice communication (40) Preamble In order to simplify the description, it is necessary to focus on the logical connection between the mobile (40) and the VMSCNLR (301) of the VPLMNcs (30): the so-called 'Radio Access Network' part of the network VPLMNcs (30) will not be mentioned.

Triggering a voice communication from the mobile (40) - Procedures Figure 9 details the equipment and the message exchanges to ensure the procedures for triggering a data communication between the mobile (40) and the VPLMNcs network (30). ). According to the exemplary context of the invention, the subscriber (roaming in Hong Kong) has recorded on the VPLMNcs network (30) for any circuit switched communication. The network VPLMNcs (30) belongs to the operator `CSL '. The numbered steps are commented on immediately: 1. (Step 1, Figure 9) a 'CM SERVICE REQUEST' signaling message is sent from the mobile (40) to the VMSCNLR (301) visited network VPLMNcs (30). The goal is to ask the network to set up a circuit-switched communication session (outgoing call, in the case of Figure 9). The syntax and parameters of the message 'CM SERVICE REQUEST' are defined in 3GPP TS 24.008: 3rd Generation Partnership Project; Technical Specification Core Network and Terminais Group; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 (Release 9). The main parameters of this message are: - CM service type (mandatory parameter): this parameter identifies the type of service requested by the mobile (40) (outgoing call) - Ciphering Key Sequence Number (mandatory parameter in the case of authentication ): this is the parameter that allows the network (30) to identify the encryption key Kc stored in the SIM card (150) (see Figure 3) - Mobile Identity (mandatory parameter): with this parameter the mobile (40) ) identifies with the VPLMNcs (30); according to section 10.5.5.2 of the 3GPP TS 24.008 standard, it can be an IMSI, an TMSI or a P-TMSI. Following the registration of the temporary identifier TMSIcs on the VPLMNcs (30) network and its allocation, Mobile Identity = TMSIcs (as shown in Figure 9). 2. (Step 2, Figure 9) a 'CM SERVICE ACCEPT' signaling message is returned from the VMSCNLR (301) of the visited network VPLMNcs (30) to the mobile (40). The syntax and parameters of the 'CM SERVICE ACCEPT' message are defined in 3GPP TS 24.008: 3rd Generation Partnership Project; Technical Specification Core Network and Terminais Group; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 (Release 9). 3. (Step 3, Figure 9) The mobile (40) sends a signaling message `CALL SETUP 'to the VMSCNLR (301). The message contains - among other things - the telephone number of the called party. The syntax and parameters of the `CALL SETUP 'message are defined in the ITU-T Q.931 standard: ISDN user-network interface layer 3; specification for basic call control. 4. (Step 4, Figure 9) The VMSC / VLR (301) sends a signaling message `CALL PROCEEDING 'to the mobile (40). The goal is to inform the mobile (40) that the outgoing call procedure is in progress. The syntax and parameters of the `CALL PROCEEDING 'message are defined in the ITU-T Q.931 standard: ISDN user-net work interface layer 3; specification for basic call control. 5. (Step 5, Figure 9) The VMSCNLR (301) sends an ISUP IAM signaling message to the circuit-switched public network (PSTN in Figure 9). The goal is to route call signaling to the destination number. The syntax and parameters of the ISUP IAM message are defined in the ITU-T Q.767 Standard: 6. (Step 6, Figure 9) The VMSCNLR (301) receives an ISUP ACM signaling message from the circuit-switched public network (PSTN in Figure 9). The purpose is to indicate to the VMSCNLR (301) that the correspondent's phone is ringing. The syntax and parameters of the ISUP IAM message are defined in the ITU-T Q.767 Standard: 7. (Step 7, Figure 9) In turn, the VMSCNLR (301) informs the mobile (40) that the correspondent's telephone is ringing (CALL ALERTING signaling message defined in the ITU-T Q.931 standard). 8. (Step 8, Figure 9) The VMSCNLR (301) receives an ISUP ANM signaling message from the circuit-switched public network (PSTN in Figure 9). The purpose is to indicate to the VMSCNLR (301) that the correspondent has dropped out. The syntax and parameters of the 'ISUP ANM' message are defined in the ITU-T Q.767 standard. 9. (Step 9, Figure 9) In turn, the VMSCNLR (301) informs the mobile (40) that the correspondent has off-hook (CALL CONNECT signaling message defined in the ITU-T Q.931 standard). At the end of Step 9, voice communication is established between the mobile (40) and its correspondent. The communication consists of three sections: - A first section between the mobile (40) and the VMSCNLR (301) A second section between the VMSCNLR (301) and the public switched network (PSTN) - A third section (not shown in Figure 9) between the public switched network (PSTN) and the called party. Special cases: As already mentioned in the Preamble of the Operational procedure for powering up the mobile phone (40) (Table 1), the IMSIcs with which the mobile (40) triggers the registration and establishment operations of the mobile phone (40). a communication session with the VPLMNcs network (30) depends on the roaming agreements. Thus, for a roaming subscriber in Canada the IMSIcs will be that of the T-Mobile operator (MCC-MNC = 310260). With respect to the procedure "Triggering a voice communication from the mobile (40)", no step of FIG. 9 is affected: indeed, the identifier with which the mobile (40) requests the establishment of a communication voice is the TMSIcs (temporary identifier). Anyone skilled in the art will recognize that the triggering of other circuit-switched services (short messages, supplementary services, etc.) is performed according to known standards and procedures; indeed, in the system according to the invention it is Step 1 of Figure 9 which is fundamental: the mobile (40) must identify with the visited network 'circuit switched' VPLMNcs (30) with its 'circuit-switched' identifier (TMSIcs OR IMSIcs) 20 Incoming mobile-to-mobile operational procedures (40) Preamble In order to simplify the description, it is necessary to focus on the logical connection between the mobile (40) and the mobile VMSCNLR (301) of the VPLMNcs (30): however, the so-called 'Radio Access Network' part of the VPLMNcs (30) network will also be mentioned, as it plays an important role in establishing the dialogue between the mobile (40) and VMSCNLR (301). As already mentioned in the Preamble of the Operational section for powering up the mobile telephone (40) (Table 1), the IMSIcs with which the mobile (40) triggers the registration and establishment operations communication session with the network VPLMNcs (30) depends on roaming agreements. Thus, for a roaming subscriber in Canada the IMSIcs will be that of the T-Mobile operator (MCC-MNC = 310260).

In the case of an incoming call, the case of a roaming subscriber in Canada will be considered: this case will make it possible to describe how the interconnection agreements between the OPERATEURcs-ps and T-Mobile allow a correct routing of the call to the mobile (40). Before describing all the steps of the incoming call, it is important to highlight the following aspects: The OPERATEURcs-ps subscriber is French. Its call number contains a French prefix (+336 or +337) According to Table 1, the mobile (40) performed the registration / authentication / location steps on the visited network VPLMNcs (30) belonging to 'TELUS Communication for circuit-switched services; the record was made with an IMSI 'circuit-switched' (IMSIcs) starting with the 6 digits '310260' (T-Mobile USA). This IMSIcs is part of an IMSI range that T-Mobile USA has allocated to OPERATORcs-ps for its exclusive use as part of their 'Interconnection Agreement'. Triggering a voice communication from the network to the mobile (40) - Incoming call procedures Figure 10 details the equipment and the message exchanges to ensure the correct progress of the incoming call when the subscriber is roaming in Canada. 1. (Step 1, Figure 10) An ISUP IAM message is sent to the GMSC (102) of the HPLMN network (10). The called number, contained in the message, is the subscriber's MSISDN telephone identifier. The syntax and parameters of the ISUP IAM message are defined in the ITU-T Q.767 Standard: 2. (Step 2, Figure 10) A message message `MAP_SEND_ROUTING_INFORMATION 'is sent from the GMSC (102) to the HLR (101) of the network (10). The syntax and parameters of the `MAP_SEND_ROUTING_INFORMATION 'message are defined in 3GPP TS 09.02: 3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile Application Part (MAP) specification (Release 1998). The main parameters of this message are: At the MAP level: the MSISDN telephone identifier. At SCCP level: - Transmission GT address: GMSC (102) (E.164 number), SSN = 8 (GMSC), TT = 0 - GT destination address: HLR (101) (E.164 number), SSN = 6 (HLR), TT = 0 3. (Step 3, Figure 10) A MAP PROVIDE ROAMING NUMBER message is sent from the HLR (101) of the network (10) to the VMSCNLR (301) of the VPLMNcs network. (30). NOTE 1: The HLR (101) must support the 'muftiIMSI' feature, which allows multiple 'IMSI' to be associated with the same MSISDN. Many core network manufacturers (such as Alcatel, Huawei, Tekelec, and others) provide the `multi-IMS1 'feature, usually as an optional software package. The multi-IMSI feature allows the HLR to know the IMSI with which a SIM card (150) has registered with a visited network. In the case of the roaming subscriber in Canada, IMSI = IMSIcs for circuit switched services (as shown in Figure 10). Note 2: vis-à-vis the TELUS Communication 'VPLMNIcs (30) visited network, the user appears as a subscriber of T-Mobile USA, since he is identified by an IMSIcs belonging to T-Mobile USA (and allocated to 'OPERATEURcs-ps). The MAP PROVIDE ROAMING NUMBER message must therefore be relayed by the GMSC of the T-Mobile network. This relaying operation is indicated in Figure 10; in this sense, the GMSC of the T-Mobile network acts as a Signaling Transfer Point (STP), its function being to transform the input / output GTs to ensure the logical connection between the HLR (101) and VMSCNLR (301); art experts will recognize that this functionality of 'transformation of GT' is well known in the operating mode of Roaming Hubs'. The syntax and parameters of the `MAP PROVIDE ROAMING NUMBER 'message are defined in 3GPP TS 09.02: 3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile Application Part (MAP) specification (Release 1998). The main parameters of this message are: At the MAP level (Section 10.2 of the 3GPP TS 09.02 standard): - the IMSI IMSIcs (mandatory parameter) - The number (GT address) of the destination VMSCNLR (301) At the SCCP level, between T-Mobile HLR (101) and GMSC: - Transmission GT address: HLR (101) (E.164 number), SSN = 6 (HLR), TT = 0 - GT destination address: GMSC of T -Mobile (E.164 number), SSN = 8 (GMSC), TT = 0 At SCCP level, between T-Mobile GMSC and VMSCNLR (301): - Transmit GT address: T-Mobile GMSC ( E.164 number), SSN = 8 (GMSC), TT = 0 - GT destination address: VMSCNLR (301) (E.164 number), SSN = 7 (VMSCNLR), TT = 0 4. (Step 4, Figure 10) A MAP PROVIDE ROAMING NUMBER RESULT message is returned from the VMSCNLR (301) of the VPLMNcs network (30) to the HLR (101) of the network (10). Similar to the previous step, this message is relayed by the GMSC of the T-Mobile network. The syntax and parameters of the `MAP_PROVIDE_ROAMING_NUMBER_RESULT 'message are defined in 3GPP TS 09.02: 3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile Application Part (MAP) specification (Release 1998). The main parameters of this message are: At MAP level: - The temporary mobile phone roaming number (MSRN). - The VMSCNLR (301) destination number (GT address) At the SCCP level, between the VMSCNLR (301) and the T-Mobile GMSC: - Transmission GT address: VMSCNLR (301) (E.164 number), SSN = 7 (VMSCNLR), TT = 0 - GT destination address: T-Mobile GMSC (E.164 number), SSN = 8 (GMSC), TT = 0 SCCP level, between T-Mobile GMSC and the HLR (101): - Transmission GT address: T-Mobile GMSC (E.164 number), SSN = 8 (GMSC), TT = 0 - GT destination address: HLR (101) (E.164 number ), SSN = 6 (HLR), TT = 0 5. (Step 5, Figure 10) A MAP SEND ROUTING INFORMATION RESULT message is returned from the HLR (101) to the GMSC (102) of the network (10). ). The syntax and parameters of the `MAP SEND ROUTING INFORMATION RESULT 'message are defined in 3GPP TS 09.02: 3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile Application Part (MAP) specification (Release 1998). The main parameters of this message are: At MAP level: routing information. In this case, it is: - The MSRN telephone identifier. - Number (GT address) of destination VMSCNLR (301) At SCCP level: - Transmission GT address: HLR (E.164 number), SSN = 6 (HLR), TT = 0 - GT destination address: GMSC (E.164 number), SSN = 8 (GMSC), TT = 0 6. (Step 6, Figure 10) An ISUP IAM message is sent from the GMSC (102) of (10) to VMSCNLR (301) of the VPLMNcs network (30). The goal is to route the call signaling to the destination number (the MSRN received by the GMSC (102) in Step 5). The syntax and parameters of the `ISUP IAM 'message are defined in the ITU-T Q.767 standard: 7. (Step 7, Figure 10) As already mentioned in the Preamble of the section Operational Procedures for Network Registration, Authentication and Mobility Management, the VPLMNcs (30) network operates in the 'NAME' mode: the 'Gs' interface (dashed line (90) in Figure 1) is present between the VMSCNLR (301) and the SGSN (304) of the network (30); therefore, the SGSN (304) of the network (30) performs paging to the telephone (40) for any establishment of a received call. A signaling message `BSSAP + PAGING REQUEST 'is sent from the VMSCNLR (301) of the visited network VPLMNcs (30) to the SGSN (304) of the same network. The syntax and parameters of the `BSSAP + LOCATION UPDATE REQUEST 'message are defined in 3GPP TS 29.018: 3rd Generation Partnership Project; Technical Specification Core Network and Terminais Group; General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification (Release 11). In the context of the system according to the invention, the main parameters of the `BSSAP + PAGING_REQUEST 'message are: At the BSSAP + level (section 17.1.19 of the 3GPP TS 29.018 standard): - the IMSIcs, with which the mobile (40) identified with SGSN (304) - VLR number The number (GT address) of the VMSCNLR (301). At SCCP level: - Transmission GT address: VMSCNLR (301) (E.164 number), SSN = 7 (VMSCNLR), TT = 0 - GT destination address: SGSN (304) (E.164 number), SSN = 149 (SGSN), TT = 0 8. (Step 8, Figure 10) As explained in section 4.7.9.2 of 3GPP TS 24.008: 3rd Generation Partnership Project; Technical Specification Core Network and Terminais Group; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 (Release 9) the SGSN (304) of the VPLMNIcs network (30) must establish a connection with the Base Station Support System (BSS) of the same network so that the latter can send the 'Paging' signal over the radio interface . A message `BSSMAP_PAGING 'is transmitted to the BSS, this message containing the temporary identifier TMSIcs which has been allocated to the mobile (40) and which is known to the SGSN (304). The `BSSMAP PAGING 'message is part of the Radio Resource Control (RRC) layer. The following steps ([step 9 to step 12) will not be explained in detail because they concern the operation of the BSS and its interaction with the mobile (40) on the RRC layer: the skilled person will recognize that the system according to the invention does not imply any change in the operation of the BSS and the RRC layer. 9. (Step 9, Figure 10) The BSS of the VPLMNcs network (30) sends the RRC_PAGING_REQUEST message (TMSIcs) to all cells that are part of the 'Location Area' in which the mobile (40) is located. As shown in Figure 10, this message contains the temporary identifier TMSIcs that was allocated to the mobile (40) 10. (Step 10, Figure 10) The mobile (40), recipient of the RRC message PAGING REQUEST, recognizes that the TMSIcs content in the message corresponds to its own TMSIcs. In order to respond to the 'Paging' message, the establishment of a dedicated channel of the RRC layer is negotiated between the mobile (40) and the BSS of the VPLMNcs network (30). 11. ([step 11, Figure 10) The mobile (40) sends a RRC PAGING RESPONSE message to the BSS of the VPLMNcs network (30). 12. (Step 12, Figure 10) The BSS of the VPLMNcs network (30) establishes an SCCP connection with the VMSCA / LR (301) of the same network. Thanks to this connection, the message RRC_PAGING_RESPONSE can be relayed to the VMSC / VLR (301). Caution: Even though it is the SGSN (304) that sent the 'Paging' request to the BSS (see Step 8), the latter sends the response directly to the VMSC / VLR (301). Indeed, when the VMSCNLR (301) sends the message `BSSAP + PAGING REQUEST 'it remains waiting for an SCCP connection from the recipient BSS. 13. (Step 13, Figure 10) The VMSCNLR (301) sends a signaling message 'GALL SETUP' to the mobile (40). The message contains - among other things - the telephone number of the caller. The syntax and parameters of the `CALL SETUP 'message are defined in the ITU-T Q.931 standard: ISDN user-network interface layer 3; specification for basic call control. 14. (Step 14, Figure 10) The mobile (40) informs the VMSCNLR (301) that the telephone is ringing (GALL ALERTING signaling message defined in the ITU-T Q.931 standard). 15. ([step 15, Figure 10) The VMSCNLR (301) sends an ISUP ACM signaling message to the GMSC (102) of the network (10). The purpose is to indicate to the latter that the recipient's phone rings. The syntax and parameters of the ISUP ACM message are defined in the ITU-T Q.767 Standard: 16. (Step 16, Figure 10) The mobile (40) informs the VMSCNLR (301) that the recipient has off-hook (CALL CONNECT signaling message defined in the ITU-T Q.931 standard). 17. (Step 17, Figure 10) The VMSCNLR (301) sends an ISUP ANM signaling message to the GMSC (102) of the network (10). The purpose is to indicate to the latter that the recipient has dropped out. The syntax and parameters of the ISUP ACM message are defined in the ITU-T Q.767 standard. At the end of Step 17, a voice call is established between the mobile (40) (recipient of the call) and its correspondent. The communication consists of three sections: A first section (not shown in Figure 10) between the public switched network (PSTN) and the GMSC (102). A second section between the GMSC (102) and the VMSCNLR (301) A third section between the VMSCNLR (301) and the mobile (40) GLOSSARY AND ABBREVIATIONS USED 3GPP: "3rd Generation Partnership Project", cooperation between regional standardization bodies Telecommunications to produce technical specifications for 3rd (3G) and 4th generation (4G) mobile networks. A3: Authentication algorithm of the SIM card. This algorithm is executed in the hardware layer of the SIM card and in the HLR / AuC of the core network A5: Encryption / decryption algorithm of all the information transmitted on the radio channel (signaling, voice or data) using the key Kc (or KCGPRS) and the current frame number. A8: Encryption key generation algorithm Kc (or KCGPRS). This algorithm is executed in the hardware layer of the SIM card and in the HLR / AuC of the APN core network: "Access Point Name", name of a logical gateway between a packet switched mobile network (GPRS, 3G, 4G ) and an external network (usually the public Internet). ARFCN: Absolute radio Frequency channel Number, an integer number (usually between 0 to 1023) designating a carrier uniquely in GSM / GPRS / UMTS systems. 20 ATR: "Answer To Reset", message from a SIM card to a mobile phone. The ATR is sent following an electronic reset received from the phone. AuC: "Authentication Center", authentication function of the Subscriber Identity Module (SIM) card used on a GSM mobile network. AuC 25 is associated with the HLR (Home Location Register). This authentication normally takes place after the BCCH "Broadcast Control CHannel" mobile phone is turned on, a logical channel on which periodically varying system information is periodically broadcast. 30 BSC: "Base Station Controller", Base Station Controller. This equipment controls one or more BTSs and manages the radio resource (allocation of a channel for a call, etc.).

BSS: "Base Station Subsystem", a radio subsystem consisting of a BSC and a BTS. A BSS generally refers to a BSC and the BTS that depend on it. BSSAP +: "BSS Application Part + (GPRS)", protocol between SGSN and 5 VMSCNLR mainly allowing a coordinated management of the location between GPRS and GSM BSSAP + LOCATION UPDATE: service of the BSSAP + protocol used to exchange the location information of a mobile between an SGSN and a VMSCNLR. 10 BSSAP + TMSI REALLOCATION: A BSSAP + protocol service for exchanging temporary mobile identification information between an SGSN and a VMSCNLR. BSSAP + PAGING REQUEST: A BSSAP + protocol service used to send the SGSN a paging request from the VMSCNLR. 15 BSSMAP: "BSS Management APplication", which governs the BSC-MSC dialog for all messages relating to the management of the radio resource. BTS: "Base Transceiver Station", equipment consisting of radio transmitters / receivers and constituting the interface between the BSC and the 20 mobiles. CAMEL: "Customized Applications for Mobile Network Enhanced Logic", a set of functionalities that takes the basic principles of the Intelligent Network by adding a mobile CAP dimension: "CAMEL Application Part", a high-level 25 GSM standard protocol that performs all exchanges between the various functional elements of the CAMEL CdPA platform: "Called Party Address", address or telephone number of a called entity (or recipient) CciPA: "Calling Party Address", address or telephone number of a calling entity ( or issuer) DHCP: Dynamic Host Configuration Protocol, a network protocol whose role is to ensure the automatic configuration of the IP parameters of a station (such as a mobile phone), including automatically assigning an IP address and an IP address. subnet mask.

DNS: "Domain Name System", a service used to translate a domain name into information of several types associated with it, in particular to the IP addresses of the machine with the name DPC: "Destination Point Code", "Point Code" of equipment receiving a message MAP, CAP or ISUP E.164: definition - according to the SS7 network standard - of a MSISDN. According to the E164 standard, an MSISDN has the format (country code, national destination code, subscriber number) E.214: The SS7 standard E.214 defines a hybrid number, in which the country code and the code of national destination have the E.164 format, while the subscriber identification number is in E.212 format. The existence of the E.214 format is justified by the fact that the international SS7 networks require an E.164-type header in order to route the signaling messages (for the definition of the E.212 format refer to the definition of 15 'IMSI') Full MVNO: "Full Mobile Virtual Network Operator" is a mobile operator that does not have a spectrum concession or infrastructure for transmission over the air, enters into agreements with MNO to interconnect its equipment. A Full MVNO owns the core network equipment (such as HLR, GMSC, GGSN, etc.); he is also responsible for the manufacture and exploitation of his own GGSN SIM cards: "Gateway GPRS Support Node", gateway for interconnection between the mobile packet network (GPRS or UMTS) and external IP networks 25 GMM: "GPRS Mobility Management ", a level 3 sub-layer between a mobile phone and the SGSN that manages roaming and security. The GMM is part of the GMSC GPRS signaling plan: "Gateway MSC", a telephone switch that provides access to an operator's mobile network over an SS7 connection and 30 GRX roaming agreements: "GPRS Roaming Exchange , A secure IP-based routing network for mobile operators, allowing their subscribers to switch between multiple carriers while still accessing data services on their home network GT: "Global Title", the address used for routing messages signaling in telecommunication networks. Any equipment, such as GMSC, HLR, etc. has his own 'GT'. GTP: "GPRS Tunneling Protocol", protocol over TCP / IP or 5 UDP / IP that allows encapsulation of data packets in IP datagrams and signaling exchange between SGSN and GGSN. HLR: "Home Location Register" main location register of a mobile subscriber HPLMN: Home Public Land Mobile Network, subscription network of a mobile HPLMNcs: in the system according to the invention, part of the HPLMN network which controls access to circuit-switched services. HPLMNps: in the system according to the invention, part of the HPLMN network which controls access to packet switched services. 15 IMS: IP Multimedia Subsystem, a standardized architecture for telephony operators that provides fixed and mobile multimedia services. This architecture truly converges the Internet and the world of cellular telephony; it uses cellular technologies to provide access anywhere, and Internet technologies to provide the IMSI services: International Mobile Subscriber Identity, internal numbering (15 or 16 digits) to an HPLMN network. The first field of this numbering is the MCC (Mobile Country Code - 3 digits), the second field is the MNC (Mobile Network Code - usually 2 or 3 digits). The remaining ten digits respectively define the HLR controlling the IMSI (2 digits) and the subscriber identifier (8 digits). As an example, for a German HPLMN MCC = 262, for a French HPLMN MCC = 208. The format of the IMSI complies with the so-called 'E.212' standard of SS7 networks. ISUP: "ISDN User Part", which is part of the SS7 network and is used for the management of telephone calls in ISUP ACM public switched networks: "Address Complete Message", message returned by the destination switch as soon as the recipient's phone rings.

ISUP ANM: "ANswer Message", message returned by the destination switch as soon as the recipient goes off-hook. ISUP IAM: "Initial Address Message", the first message sent to inform the partner switch that a call establishment must be made to the destination number contained among the parameters of the message. ITU-T: "International Telecommunication Union", a United Nations agency specializing in information and communication technologies, based in Geneva, Switzerland. 10 LA: "Location Area" is a set of cells in which the mobile phone does not initiate the update of the location in relation to the GSM network in which the mobile phone is located. LAC: "Location Area Code", code of a location area within a given network. 15 LAI: "Location Area Identification", identification of a location area in the world. It contains the MCC country code, the MNC network code and the LAC code. "Integrity Key", a key shared between the SIM card and the core network (HLR / AuC) which allows the authentication and authorization operations as well as the generation of the Kc (or KcGPRS) LLC encryption key: " Logical Link Control ", a link protocol between the mobile and the SGSN that provides, among other things, encryption for GPRS. MAP: "Mobility Application Part", a high-level standard GSM protocol that performs all exchanges related to mobility, call control and supplementary services MAP INSERT SUBSCRIBER DATA: MAP protocol service to send from the HLR the description of the subscriber's profile (MSISDN, etc.) when it is in a VPLMN. The message is received by the VMSCNLR of the VPLMN MAP PROVIDE ROAMING NUMBER: A MAP service that requests the VMSC / VLR to dial a temporary telephone number to route calls to the mobile. The message is sent by the HLR 3003 42 4 91 MAP SEND AUTHENTICATION INFO: The MAP protocol service used to request information from the HLR to authenticate the mobile. The message is sent by the VMSCNLR of the VPLMN MAP SEND ROUTING INFO: A MAP service used to request information from the HLR to route calls to the mobile. The message is sent by the GMSC of the HPLMN. MAP UPDATE GPRS LOCATION: A MAP protocol service used to record in the HLR the presence of a subscriber in a VPLMN. The message is sent by the SGSN of the VPLMN. 10 MAP UPDATE LOCATION: The MAP protocol service used to register the presence of a subscriber in a VPLMN in the HLR. The message is sent by the VMSCNLR of the VPLMN. MCC: "Mobile Country Code", see the definition of IMSI MGT: "Mobile Global Title", conversion of the IMSI in a format "routable" 15 by the network SS7 (see also the definition of E.214) MNO: Mobile Network Operator, a mobile phone operator that owns a spectrum spectrum concession and / or the own network infrastructure. The infrastructure consists of components allowing the mobile link over the air and the core network components. 20 MSC: "Mobile Switching Center", MSISDN mobile telephone switch: "Mobile Station ISDN Number", the "known to the public" number of the GSM or UMTS subscriber as opposed to the IMSI number. It is this identifier, commonly called the telephone number, which will be dialed in order to reach the subscriber. MSRN: "Mobile Station Roaming Number", a temporary roaming number dynamically assigned to each incoming call request by the VPLMN. MTP: Message Transfer Part, network layer of SS7 systems providing services such as addressing (via 'Point Code') and routing (each node of the SS7 network has a preconfigured routing table to the next node to pass to forward a packet to the destination) NP: "Numbering Plan", an integer number corresponding to a type of number (E.164, E.214, etc.) in the SS7 NSAPI dial plan: " Network Service Access Point Identifier ", the access point identifier of a network entity (such as IP, X.25, etc.) that uses SNDCP. The NSAPI is exchanged between the mobile and the SGSN. OPC: "Origination Point Code", "Point Code" of a transmitting device 5 of a MAP, CAP or ISUP P-TMSI message: "Packet - Temporary Mobile Subscriber Identity", temporary identity allocated by the SGSN. Refer to the acronym `TMS1 '. PC: "Point Code", address at the MTP layer in the SS7 signaling network 10 PDP: "Packet Data Protocol", designation of any packet network protocol for which GPRS offers compatibility. PSTN: "Public Switched Telephone Network" RA: "Routing Area", set of cells in which the mobile phone does not initiate the update of the location with respect to the GPRS network in which the mobile phone is located. In general, one or more RAs are contained in the same LA. RAC: "Routing Area Code", code of a routing area within a given network. 20 RAI: "Routing Area Identification", identification of a routing area in the world. It contains the MCC country code, the MNC network code, the LAC code and the RAC code. RAM: Random Access Memory, computer memory in which a computer places the data during its processing RNTI: "Radio Network Temporary Identity", temporary identity that identifies a particular mobile for the SGSN. The RNTI is used in 3G roaming networks: contractual and technical arrangements allowing a mobile subscriber to use his phone in networks other than his own. 30 RRC: "Radio Resource Control", part of the network layer present between the mobile and the BSC that manages the radio resource (channel allocation, encryption, etc.) SAT: "SIM Application Toolkit", set of procedures that allow SIM card management actions that can be used for value-added services. SCCP: "Signaling Connection Control Part", a standard protocol for SS7 networks that provides network level services for Global Title (GT) interconnection between different devices. SCP: "Service Control Point", functional component of CAMEL networks, used for the control (initialization, start-up, termination, billing ...) of the services.

SGSN: "Serving GPRS Support Node", a gateway for routing data within GPRS mobile networks SMSC: "Short Message Service Center", manages the transfer of SMS messages (text or binary) between mobile phones SNDCP "Sub Network Dependent Convergence Protocol," GPRS Level 3 protocol 15 that specifies the features and messages between a mobile phone and the SGSN. SPC: "Signaling Point Code", unique address for a network node called "Signaling Point". The SPC is similar to the IP address in a packet-switched network. SS7: "Signaling System no. 7 ", interconnection network used between mobile networks for the transmission of signaling for any circuit-switched communication (voice, short messages, etc.) SSN:" Sub-System Number ", which identifies a user function ( HLR, GMSC, SGSN, etc.) in SCCP 25 STP: "Signaling Transfer Point", switching function of SS7 signaling messages within a national network. TLLI: "Temporary Logical Link Identity", temporary identity that identifies a particular mobile for the SGSN. The TLLI is used in 2G and 2.5G 30 TMSI networks: "Temporary Mobile Subscriber Identity", temporary identity allocated by the VLR to avoid - except in special cases - the transmission of the IMSI over the radio channel. Indeed, the IMSI must be transmitted as little as possible in order to minimize the risk of interception and tracing.

U: "Translation Type", fields of the SCCP protocol which makes it possible to address the appropriate address translator in the international SS7 interconnections UART: "Universal Asynchronous Receiver Transmitter", Universal Asynchronous Receiver Transmitter USIM: "Universal Subscriber Identity Module" , an application stored and executed on the UICC platform (Universal Integrated Circuit Card) of a SIM card. The USIM application is mainly defined by the specifications ETSI TS 102 221 (SIM application), 3GPP TS 31.102 10 (USIM application) and TS 21.1111 (USIM card). VLR: "Visited Location Register", VMSC / VLR visited location register: all the functionalities of the MSC and VLR in a VPLMN network; although distinct, these functionalities are often considered as a whole in the architectural presentations in order to simplify the description. VPLMN: Visited Public Land Mobile Network, network visited by a roaming mobile VPLMNcs: in the system according to the invention, part of the VPLMN network that manages access to circuit-switched services.

VPLMNps: in the system according to the invention, part of the VPLMN network which manages access to packet switched services.

Claims (10)

REVENDICATIONS1. System for mobile phones registered in a network with a SIM card belonging to an HPLMN network and containing: A first IMSIcs identification code which allows access to any circuit switched communication service, such as the mobile telephone service. A second IMSIps identification code that allows access to any packet-switched communication service, such as the mobile Internet or email service. 2. System according to claim 1, characterized in that in a roaming situation in a visited country: - The first identification code IMSIcs allows the registration, authentication and location in a visited network VPLMNcs belonging to a first operator that has roaming agreements with the HPLMN network operator for circuit-switched communication services only. - The second identification code IMSIps allows - at the same time - the registration, authentication and location in a visited network VPLMNps belonging to a second operator that has roaming agreements with the network operator HPLMN for only packet switched communication services. 3. System according to claims 1 and 2, characterized in that the SIM card consists of the following functional elements: - A first file structure of the electrical profile, these files being dedicated to the management of operations (mobility, authentication, authorizations, etc.) in a visited network VPLMNcs in correspondence of the first identification code IMSIcs. A second file structure of the electrical profile, these files being dedicated to the management of operations (mobility, authentication, authorizations, etc.) in a visited network VPLMNps in correspondence of the second identification code IMSIps. - A third file structure of the electrical profile, these files containing information independent of IMSIcs and IMSIps identification codes. This information includes the subscriber's telephone number, the parameters for managing short messages, and so on. - The set of parameters and procedures for performing authentication operations, generation of encryption keys and encryption. Among these parameters is the integrity key (K1). A table containing as many lines as the number of countries in which a subscriber of the system according to the invention can go, each line of the table containing - for each country visited - the list of VPLMNIcs networks which have roaming agreements for circuit switched communication services only, the list of VPLMNps networks which have roaming agreements for packet-switched communication services only, the first IMSIcs identification code allowing the recording, authentication and the location in the visited networks VPLMNcs, the second identification code IMSIps allowing registration, authentication and location in the visited networks VPLMNps. An application software that manages the use of IMSIcs and IMSIps identification codes according to the data of the table described above. 4. System according to claim 3, characterized in that the IMSIcs and / or IMSIps identification codes may belong to the operator of the HPLMN network or to other operators who have roaming agreements with the operators of the visited networks. VPLMNcs and VPLMNcs and - at the same time - interconnection agreements with the operator of the HPLMN network. 5. Simultaneous recording method of a mobile system with a first identification code IMSIcs allowing the recording, authentication and location in a visited network VPLMNcs for lesseuls circuit switched communication services and with a second IMSIps identification code for registration, authentication and location in a visited network VPLMNps for packet switched communication services only, characterized in that the following steps are performed for the provisioning of a telephone mobile: - Once the communication link has been established with the SIM card and the PIN entered by the subscriber and verified by the phone, the latter reads the IMSIcs and IMSIps identification codes contained in the SIM card - A selection process cell is triggered by the mobile phone in order to know the country visited. - The mobile phone starts an application software contained in the SIM card; the application software takes control of the operations by triggering the following steps: - Reading a table hosted by the SIM card and containing as many lines as the number of countries in which a subscriber can go, each line of the table containing - for each country visited - the list of VPLMNcs networks whose operators have roaming agreements for circuit-switched communication services only, the list of VPLMNps networks whose operators have roaming agreements for the services only packet-switched communication, a first identification code IMSIcs and a second identification code IMSIps, the identification code IMSIcs (respectively IMSIps) belonging to the operator of the network HPLMN or any other operator that has access agreements roaming with network operators VPLMNcs (respectively VPLMNps) and - at the same time - interconnection agreements with the operator of the HPL network MN. - The selection of IMSIcs and IMSIps identification codes corresponding to the country visited. - The writing of the IMSIcs and IMSIps identification codes selected in the corresponding files that form part of the SIM card's electrical profile.- The sending of the REFRESH 'command to the mobile phone to alert the latter of the change of contents of the SIM card files that store IMSIcs and IMSIps identification codes; the mobile phone resumes control of operations by triggering the following steps: - A cell selection process is started again by the mobile phone to identify a cell belonging to a VPLMNps network that is not prohibited. - Once a cell belonging to a non-prohibited VPLMNps network has been identified, the procedures for registration, authentication and localization are started using the IMSIps identification code. At the end of these procedures, the subscriber may consume any switched service. packet on the visited network VPLMNps. - A second cell selection process is triggered by the mobile phone to identify a cell belonging to a VPLMNcs network that is not prohibited. - Once a cell belonging to a non-prohibited VPLMNcs network is identified, the registration, authentication and location procedures are started using the IMSIcs identification code. At the end of these procedures, the subscriber may consume any circuit-switched service on the visited network VPLMNcs. 6. Method according to claim 5, characterized in that the procedures for recording, authentication and location on the visited network VPLMNps comprise the steps which consist of: - The sending of a signaling message `GMM_ATTACH_REQUEST 'from the mobile phone to the SGSN service node of the visited network VPLMNps which controls the cell in which the mobile phone is located. The message `GMM_ATTACH_REQUEST 'contains the IMSIps identification code. - Sending a message message `MAP_SEND_AUTHENTICATION_INFO 'from said SGSN service node to the main location register (HLR) of the HPLMN network of the subscriber. The message `MAP_SEND_AUTHENTICATION_INFO 'contains the IMSIps identification code. - The sending of a `MAP_SEND_AUTHENTICATIONINFO_ACK 'signaling message from the subscriber's HPLMN main location register (HLR) to the SGSN service node of the visited network VPLMNps. The message `MAP _ SEND _ AUTHENTICATION _ INFO _ACK 'contains the identification parameters to enable the SGSN service node to authenticate the mobile phone. - The sending of a authentication request `GMM_AUTHENTICATION_AND_CIPHERING_REQUEST 'from the SGSN service node of the visited network VPLMNps to the mobile phone. The message `GMM_AUTHENTICATION_AND_CIPHERING_REQUEST 'contains the parameters necessary for the mobile phone to trigger the encryption key authentication and calculation algorithm. - The sending of a signaling message `GMM_AUTHENTICATION_AND_CIPHERING_RESPONSE 'from the mobile phone to the SGSN service node of the visited network VPLMNps. The message `GMM_AUTHENTICATION_AND_CIPHERING_RESPONSE 'contains the response to the authentication request. This response allows the SGSN service node to verify the identity of the mobile phone. - The sending of a MAP UPDATE GPRS LOCATION signaling message from the SGSN service node of the visited network VPLMNps to the home location register (HLR) of the subscriber's HPLMN network. The MAP UPDATE GPRS LOCATION message contains the IMSIps identification code. - The sending of a signaling message `MAP_INSERT_ SUBSCRIBER DATA 'from the subscriber HPLMN main location register (HLR) of the subscriber to the SGSN service node of the visited network VPLMNps. The message `MAP_INSERT_SUBSCRIBER_DATA 'contains access permissions to the visited network VPLMNps, including access to only packet-switched services. - The sending of a signaling message `GMM_ATTACH_ACCEPT 'from the SGSN service node of the visited network VPLMNps to the mobile phone. The message `GMM_ATTACH_ACCEPT 'contains the temporary identification code P-TMSIps, valid for triggering any packet-switched communication initiated by the mobile phone. 7. Method according to claim 5, characterized in that the procedures for recording, authentication and location on the visited network VPLMNcs include the steps which consist of: - The sending of a signaling message `GMM_ATTACH_REQUEST 'from the mobile phone to the SGSN service node of the visited network VPLMNcs which controls the cell in which the mobile phone is located. The message `GMM_ATTACH_REQUEST 'contains the identification code IMSIcs - The sending of a signaling message` MAP_SEND_AUTHENTICATION_INFO' from the said SGSN service node to the main location register (HLR) of the subscriber's HPLMN network. The message `MAP_SEND_AUTHENTICATION_INFO 'contains the IMSIcs identification code. - Sending a `MAP _ SEND _ AUTHENTICATION _ INFO _ACK 'signaling message from the subscriber's HPLMN main location register (HLR) to the SGSN service node of the visited network VPLMNcs. The message% AAP _ SEND _ AUTHENTICATION _ INFO _ACK 'contains the identification parameters to enable the SGSN service node to authenticate the mobile phone. - The sending of a authentication request `GMM_AUTHENTICATION_AND_CIPHERING_REQUEST 'from the SGSN service node of the visited network VPLMNcs to the mobile phone. The message `GMM_AUTHENTICATION_AND_CIPHERING_REQUEST 'contains the parameters necessary for the mobile phone to trigger the encryption key authentication and calculation algorithm. - The sending of a signaling message `GMM_AUTHENTICATION_AND_CIPHERING_RESPONSE 'from the mobile phone to the SGSN service node of the visited network VPLMNcs. The message `GMM_AUTHENTICATION_AND_CIPHERING_RESPONSE 'contains the response to the authentication request. This response allows the SGSN service node to verify the identity of the mobile phone. - The sending of a MAP UPDATE GPRS LOCATION signaling message from the SGSN service node of the visited network VPLMNcs to the home location register (HLR) of the subscriber's HPLMN network. The% AAP UPDATE GPRS LOCATION 'message contains the IMSIcs identification code. - The sending of a signaling message `MAP_INSERT_ SUBSCRIBER DATA 'from the subscriber HPLMN main location register (HLR) of the subscriber to the SGSN service node of the visited network VPLMNcs. The message `MAP_INSERT_SUBSCRIBER_DATA 'contains access permissions to the visited network VPLMNcs, including access to only circuit-switched services. - The sending of a signaling message (BSSAP-F LOCATION UPDATE REQUEST ') from the SGSN service node of the visited network VPLMNcs to the visited location register (VMSCNLR) of the VPLMNcs network The message ESSAP + LOCATION UPDATE REQUEST' contains the identification code IMSIcs - The sending of a signaling message `MAP_UPDATE_LOCATION 'from the visited location register (VMSCNLR) of the VPLMNcs network to the main location register (HLR) of the subscriber's HPLMN network. MAP_UPDATE_LOCATION 'contains the identification code IMSIcs - The sending of a MAP INSERT_ SUBSCRIBER_DATA signaling message from the subscriber's HPLMN main location register (HLR) to the visited location register (VMSCNLR) The message `MAP_INSERT_SUBSCRIBER_DATA 'contains access permissions to the visited network VPLMNcs, including access to any circuit-switched service - Sending a signal message sation `BSSAP + LOCATION UPDATE_ACCEPT 'from the visited location register (VMSCNLR) of the VPLMNcs network to the SGSN service node of the same network. The message `BSSAP + LOCATION UPDATE_ACCEPT 'contains the temporary identification code TMSIcs allocated by the visited location register (VMSCNLR) of the VPLMNcs network. - Sending a 'GMM_ATTACH_ACCEPT' signaling message from the SGSN service node to the mobile phone. The message `GMM_ATTACH_ACCEPT 'contains the temporary identification code TMSIcs, valid for triggering any circuit-switched communication initiated by the network or mobile phone. 8. Method according to claims 5 and 6, characterized in that the procedures for triggering a packet-switched communication from a mobile phone registered on the visited network VPLMNps, whose operator has chords. roaming with the operator of the HPLMN network, comprising the steps of: - sending a signaling message `ACTIVATE PDP CONTEXT REQUEST 'from the mobile phone to the SGSN service node of the visited network VPLMNps which controls the cell in which is the mobile phone. The `ACTIVATE PDP CONTEXT REQUEST 'message contains the APN, the name of the logical gateway for access to packet-switched services - A message exchange between the SGSN service node and DNS servers to translate the APN name into IP address of the GGSN interconnection gateway of the HPLMN network, this message exchange containing: The identifier of the HPLMN network, whose operator has roaming agreements with the operator of the visited network VPLMNps. - The identifier of the packet switched service, this service being provided by the HPLMN network operator through the GGSN interconnection gateway. 9. Method according to claim 8, characterized in that the operator of the visited network VPLMNps has roaming agreements with a third party operator which, in turn, has interconnection agreements with the operator of the HPLMN network. which involves a message exchange between the SGSN service node and DNS servers in order to translate the APN name into an IP address of the GGSN interconnection gateway of the HPLMN network, this message exchange containing: - The network identifier of the network third-party operator, which has roaming agreements with the operator of the visited network VPLMNps. - The identifier of the packet switched service, this service being provided by the HPLMN network operator through the GGSN interconnection gateway. Method according to claims 5 and 7, characterized in that the procedures for initiating an incoming call to a mobile telephone registered on the visited network VPLMNcs, whose operator has roaming agreements with a third party operator which, in turn, has interconnection agreements with the operator of the HPLMN network, include the steps of: - Sending an ISUP IAM signaling message to the GMSC gateway-switch of the HPLMN network. The message 'ISUP IAM' contains the recipient's telephone number.- Sends a MAP SEND ROUTING INFORMATION message from the GMSC gateway switch of the HPLMN network to the primary location register (HLR) of the same network . The MAP SEND ROUTING INFORMATION message contains the recipient's phone number. - The sending of a% AAP PROVIDE ROAMING NUMBER signaling message from the subscriber's HPLMN main location register (HLR) to the visited location register (VMSCNLR) of the VPLMNcs network. The MAP PROVIDE ROAMING NUMBER message contains the IMSIcs identification code belonging to the third-party operator that has roaming agreements with the visited network operator VPLMNcs. The MAP PROVIDE ROAMING NUMBER message is relayed by the GMSC gateway switch of the third-party operator. - The sending of a MAP PROVIDE ROAMING NUMBER RESULT signaling message from the visited location register (VMSCNLR) of the VPLMNcs network to the main location register (HLR) of the subscriber's HPLMN network. The MAP PROVIDE ROAMING NUMBER RESULT message contains the MSRN temporary telephone number allocated by the visited location register (VMSCNLR) of the VPLMNcs network. The MAP PROVIDE ROAMING NUMBER RESULT message is relayed by the GMSC gateway switch of the third-party operator. - Sending a MAP SEND ROUTING INFORMATION RESULT message from the HPLMN home location register (HLR) of the subscriber to the GMSC gateway-switch of the same network. The MAP SEND ROUTING INFORMATION RESULT message contains the MSRN temporary telephone number and the visited location register address (VMSCNLR) of the VPLMNcs network. - The sending of an ISUP IAM signaling message from the GMSC gateway switch of the HPLMN network to the visited delocalization register (VMSC / VLR) of the VPLMNcs network. The message 'ISUP IAM' contains the MSRN temporary telephone number of the recipient. - The sending of a signaling message `BSSAP + _PAGING_REQUEST 'from the visited location register (VMSC / VLR) of the VPLMNcs network to the SGSN service node of the same network. The `BSSAP + PAGING REQUEST 'message contains the IMSIcs identification code. - The sending of a signaling message `BSSMAP_PAGING 'from the SGSN service node of the VPLMNcs network to the BSS radio access equipment of the same network. The `BSSMAP_PAGING 'message contains the TMSIcs temporary identification code which makes it possible to send the incoming mobile phone the alert message of the incoming call.