FR2941832A1 - Operators e.g. mobile network operators, interconnecting system for e.g. general packet radio service networks, has server whose selection is determined to authenticate user whose device houses software, during launching of software - Google Patents

Abstract

The system has a set of mobile terminal devices (100) i.e. third generationmobile telephones, where each device houses an applicative software i.e. MIDLET(RTM: application for mobile information device profile) (110) for communicating with an interconnection server (200). The server is placed in country where a user of the device is found. Selection of the server communicating with the device is determined by an authentification, authorization and accounting server device (500) to authenticate the user whose device houses the software, during launching of the software.

Description

The present invention relates to an innovative system and device for enabling interconnection between different cellular networks. The present invention is designed to allow the operator of a cellular network to reduce the costs of interconnection between his network and the network. another operator. The present invention also enables a user of a cellular network to reduce his communications costs for any short call or message sent / received to / from a mobile phone abroad. In addition, the user can also reduce their communications costs when they are "homeless" (roaming refers to the ability of users to access their mobile services from a network or foreign country). Remarkable feature of the present invention is its applicability to several cellular telephony standards (such as 'GSM' (Global System for Mobile Communication) or 'CDMA' (Multiple Division Access Code)). Another remarkable feature of the present invention is the use of existing protocols, methods, and functionalities without any need to modify the infrastructures already in place: in fact, only minor modifications to a part of the databases and / or software are required. Today's global demand for mobile communications is driving the need for global roaming services that keep us connected all over the world. Roaming services require, in particular, agreements between the operators concerned, so that a cellular subscriber traveling in a visited country can benefit from the mobile services provided by the operator of his country of origin. Ideally, a global roaming system should comply with the following specifications: Low cost interconnection between the operators concerned Low cost of communications guarantee. Ideally, any voice and short message should be billed at the cost of a call from a fixed line to another fixed line, regardless of the roaming of the user. 30 No developments for support infrastructures for operators and / or service providers. Simple and flexible business models The present invention meets all the elements of the specifications described. The solutions available on the market or described in the state of the art (patents or publications) do not make it possible to respond adequately to all of the specifications described. Indeed, the existing solutions can be divided according to the technology and / or the business model, according to the following classification: 2941832 -2- The classical solutions, in conformity with the standards `3GPP '(3rd Generation Partnership Project, which specifies the GSM system) or `CDG '(CDMA Development Group, which specifies the CDMA system). Conventional solutions are based on the use of the Mobile Station Roaming Number (MSRN). The function of the MSRN is to allow the routing of incoming calls directly from the originating network gateway switch (GMSC) to the mobile station's current switch (MSC), which current switch is controlled by the visited network. The MSRN is allocated to the mobile station temporarily. Conventional solutions also support the transmission of short messages, according to the principle described. Disadvantage of conventional solutions is the need to use international switched networks and their constituent nodes ('STP', Signaling Transfer Points and 'SSP', Service Switching Points). These international switched networks are often operated by international operators, who charge the originating operator for international transit. In addition, the visited network charges the originating operator the allocation of voice traffic (or short message) to the (temporary) MSRN number. This over-billing to the mobile operator generates additional costs for the user roaming; these additional costs are, in general, very high. Solutions based on the interconnection of networks of different operators via third party networks, such as that described in patent FR-0209667 "Optimal routing system for short messages from one message center to another, with global address translation ": a third-party network has an identifier (MGT -" Mobile Global Title ") that starts with the digits 338. Existing devices (either they are the GMSC -" Gateway Mobile Switching Center "or the SMSC -" Short Message Service Center '), which is responsible for performing an address translation, add the prefix 338 to the MGT received from the HLR - Home Location Register. In this way, the underlying signaling will be routed to through the third party network. This solution makes it possible to interconnect networks whose operators do not have roaming agreements. On the other hand, the overbilling mentioned in conventional solutions can not be avoided because the solution is based entirely on existing circuit-switched protocols (ie protocols based on the Signaling System 7 signaling system). '(SS7), well known by art experts).

Gateway-based solutions for interconnecting existing cellular networks, such as that described in the "Signalling Gateway with Multiple IMSI with Multiple MSISDN Service in a Single SIM for Multiple Roaming Partners" (authors: YJ Jiang), involve deployment. additional equipment in cellular networks and a consequent evolution of signaling. This type of approach involves a complete overhaul of the business model of the operators and / or service providers and does not necessarily reduce the interconnection costs for the operators. Figure 1 shows an example of an existing international interconnection between different cellular operators, this interconnection making use of protocols and identifiers according to SS7 standards. Figure 1 follows the lessons presented in the 'SMS and MMS Interworking in Mobile Networks' book (authors: A. Henry-Labordère, V. Jonack). The Mobile Operator Networks [300], which operate in different countries, 10 are interconnected by an international network [900], which network is generally - under the responsibility of a provider of international gateways (International Gateway Provider). PGI). The IGP provides access to each network [300] on the international SS7 network. This access conforms to the Signaling Connection Control Part (SCCP) and Message Transfer Part Level 3 (MTP3) protocol layers of the SS7 protocol, according to which: Cellular network equipment (such as [310], [320], [330] etc., these elements being shown in Figure 3) are identified by a telephone number of type E.164, called `Global Title '. The SCCP layer of the SS7 network uses these numbers to route messages within the SS7 network. The equipment of an SS7 network (cellular or other network) is also identified by the `Point Codes' (PC) which, too, allow routing of the messages between the different nodes of the telephone network. While the Global Title is an indirect, virtual address that identifies a telecom resource, the Point Code is a true digital forwarding address for routing messages between 25 physical devices. The set of `Point Codes' (PC) constitutes a subsequent routing layer [910] (called Message Transfer Part Layer 3 layer (MTP3)) inside the network [900]. The Mobile Operator Networks [300] can thus access the international SS7 network by using input nodes (respectively IGP-PC1 for the network 30 of the Operator 1, IGP-PC2 for the network of the Operator 2 and IGP-PC3 for the Operator Network 3). Inside the network [900], the set of `Point Codes' (PC A, ..., PC E) allows the routing of messages from an original device on the network of a Cellular operator to a recipient device of another Cellular Operator. Assuming now that a cell operator subscriber 1 is roaming and can send / receive any communication under the control of Cellular Operator (foreign) 2, Cellular Operator 1 to route the messages to destination of its subscriber must pay the costs of the international connection 2941832 -4 to the IGP provider and the costs of local terminations to the Cell Operator 2. This case is the simplest is implies that the Cellular Operators 1 and 2 have mutual roaming. It can also be assumed that the Cellular Operators 1 and 2 do not have roaming agreements and that the intermediation of a third party Cellular Operator (Operator 3) is necessary in order to allow the roaming of the subscribers of the cell. Cellular operator 1 on the Cellular Operator 2 network (and vice versa). In this case, interconnection costs become even more important.

The system and device according to the invention make it possible to remedy all the drawbacks found in the state of the art with regard to international connections between cellular operators, by providing a global interconnection model and associated services which offer all advantages mentioned in the specifications. The system comprises an architecture which is based on the implementation of the following devices and methods: A network of gateways between mobile networks, these gateways being interconnected by the public Internet network - A registration procedure a mobile terminal which can logically be connected (by any mobile network and internet equipment) to a gateway of the network (gateways), from the identifier of the associated user and from his geographical location. - A gateway configuration procedure that allows the user to make / receive calls (voice, simple messaging, multimedia messaging) from / to his mobile terminal according to three separate links: 25 o A first cellular-type local link between the mobile terminal of the user and the cellular network of the operator of the country in which the user is located. o A second internet-type link between the same cellular network and a preferred gateway, this gateway being part of the gateway network. o A third Internet-type link between two gateways of the network (gateways), thus allowing the user to reach a correspondent whose mobile terminal is under the control of another cellular operator. In the following description, the GSM / GPRS system will be considered as a reference cellular network and the signaling on the IP network will be in accordance with the Session Initiation Protocol (SIP) standards. It is understood that these hypotheses constitute a possible exemplary embodiment: the principles of the invention can be extended to other cellular systems (such as CDMA or UMTS) and to other types of signaling on the networks. IP.

The accompanying drawings illustrate the invention. Figure 2 shows the overall system of the invention according to its preferred configuration. The overall system is based on the following devices: a MOBILE TERMINAL device [100], an INTERCONNECTION SERVER device [200], a MIDLET device [110] which represents an application software installed on the MOBILE TERMINAL [100].

Figure 2 shows that: The MOBILE TERMINAL [100] communicates with the MOBILE OPERATOR NETWORK [300] (similarly to Figure 1, in Figure 2 three networks are shown, these networks being controlled by three different operators). Any voice, short message (SMS), multimedia message (MMS) communication between TERMINAL MOBILE [100] and MOBILE OPERATOR NETWORK [300] conforms to the standard defined by the 3rd Generation Partnership Project (3GPP). MOBILE TERMINAL [100] and MOBILE OPERATOR NETWORK [300] support all the features and protocols required by 3GPP. The MOBILE TERMINAL [100] hosts application software [110] (such as a `MIDLET 'if TERMINAL MOBILE [100] supports the Java 2 Micro Edition software platform (JM2E) or other application if such a platform is not In the remainder of the description, the term `MIDLET 'is to be considered generic) to allow the user to take advantage of the interconnection services described. Indeed, it will be shown later that the invention offers pricing advantages to any user of TERMINAL MOBILE [100] who is in a roaming situation.

The INTERCONNECT SERVER [200] device guarantees a logical and physical connection between the MOBILE OPERATOR NETWORK [300] and the INTERNET (public) network. In this sense, the device [200] provides the features of the `Softswitch 'type known in the state of the art: signaling translation between the SIP format and the ISUP telephone format, translation of the media transport protocols between the two networks etc. In the context of the invention, several INTERCONNECT SERVERS [200] are interconnected via one or more Internet exchange points [400]: the set of several INTERCONNECT SERVERS [200]. ] constitutes a "shadow network" of interconnection equipment / functionalities, this network being superimposed and operating in parallel with the MOBILE OPERATOR NETWORKS [300] and the existing international interconnection networks [900] and [910] and guaranteeing an optimal interconnection (in terms of quality / price ratio) between them. Figure 3 shows a block diagram of the INTERCONNECT SERVER [200] in accordance with the general principle of the invention. List of sub-devices that make up the INTERCONNECT SERVER [200]: PROXY SIP [210] for the purpose of functionally isolating the SS7 INTERCONNECTION GATEWAY device [220] from the MEDIA GATEWAY device [230] and the B2BUA device [240] ]. PROXY SIP [210] is also useful as a protocol translator in the case of INTERCONNECTION GATEWAY SS7 [220] and / or B2BUA [240] not based on SIP protocols. GATEWAY INTERCONNECTION SS7 [220] includes the necessary functionalities for any signaling exchange with the cellular network (via SS7 gateway [360]) and with the IP network. Figure 4 shows the typical protocol layers involved in signaling transport between an SS7 network element and an IP network element (such as INTERCONNECT SERVER [200]), which signaling is intercepted and adapted by appropriate gateway (such as the SS7 BRIDGE [360]). It may be noted that, on the SS7 network side, we find the 'SCCP' and 'MTP3' layers mentioned in the description of FIG. 1. On the IP network side, these same layers are interpreted and exploited by the INTERCONNECTION GATEWAY device SS7 [220], thanks to the mediation of the SS7 gateway device [360] which acts as a protocol converter in particular by using the protocol and the `Signal Transport Working Group '(SIGTRAN) procedures, well known by the 25 experts of the 'art. - INTERCONNECTION MEDIA GATEWAY [230] for opening, maintaining and closing a data link (voice or other) between the IP network and the MOBILE OPERATOR NETWORK [300] (and in particular some constituent elements thereof, such as the `MOBILE SWITCHING CENTER / 30 VISITING LOCATION REGISTER '(VLR / MSC [310]), and the` GATEWAY MOBILE SWITCHING CENTER' (GMSC [320])), through a network element, such as the `MEDIA GATEWAY '(MGW [340]). The element [340] is well known to those skilled in the art: it makes it possible to perform a protocol conversion in order to allow the interconnection between the network elements [310] and [320] and the GATEWAY INTERCONNECTION. MEDIA [230]. B2BUA Back-to-Back User Agent [240] for the purpose of establishing a signaling link with PROXY SIP [210], with a DATABASE [250] and with an external SERVER AAA [500] device, which makes it possible to authenticate the users of the interconnection services. In general, B2BUA [240] is used to establish the data link (voice or other) between two remote INTERCONNECT SERVER [200] devices. DATABASE [250] all includes the types of memory (such as ROM, RAM, FLASH or other) necessary to store temporary or permanent information of the users of the interconnection services. The main information stored in DATABASE [250] is: o One or more telephone identifiers associated with a user of the interconnection services; these identifiers include the Mobile Subscriber ISDN Number (MSISDN), or the cell phone number. Other identifiers may consist of a second MSISDN and / or the number of a fixed telephone line (home and / or office or other) associated with the user. The context of use of the telephone identifiers will be explained later. o A telephone identifier associated with the INTERCONNECT SERVER [200] which is connected with the user's original cellular network [300] (ie, the network [300] belonging to the Cellular Operator with whom the user has a contract) o A telephone identifier associated with the INTERCONNECTION SERVER [200] that is connected to the cellular network of the visited country, in the event that the user is in a roaming situation . O One or more IP addresses associated with the corresponding INTERCONNECT SERVER (s) [200] o One or more `Fully Qualified Domain Name (s) '(FQDN (s)) associated with the ( s) INTERCONNECTING SERVER (s) [200] corresponding 30 o A Mobile Roaming Number (MSRN), or a temporary local telephone identifier assigned to the roaming user by the local network of the country visited. This MSRN is allocated on a temporary basis whenever the roaming user receives a call. 35 o Data relating to the detailed recording of communications (calls, SMS, MMS, others) for each user: called number, duration, caller's telephone identifiers (including the MSRN), etc. SIP REGISTRAR [260] intended to register users of interconnection services, to enable them to use these services from their country of origin or from a visited country. SMS RELAY [270] for the purpose of receiving SMS messages and converting them into a format that can relay such SMS messages to B2BUA. The interconnection between SMS RELAY [270] and the `Short Message Service Center '(SMSC [350]) is of logical type: SMS RELAY [270] and SMSC [350] exchange messages according to the protocols defined for SMS transmission and according to the OSI interconnection layers associated and well known by the experts of the art. In the remainder of the description it will be apparent that SMS RELAY [270] can be realized in different ways, depending on the business models considered and, therefore, the physical interconnection between SMS RELAY [270] and SMSC [350]. ]

Figure 5 shows an interconnection diagram between the MOBILE OPERATOR NETWORK elements [300] and between MOBILE OPERATOR NETWORK [300] and INTERCONNECTION SERVER [200]. Figure 5 is necessary to understand the operational scenarios (described later) which shows the role of the INTERCONNECT SERVER [200] in the context of the invention. The elements [310], [320] (already described) as well as the devices `HOME LOCATION REGISTER '(HLR 20 [330]) and` SHORT MESSAGE SERVICE CENTER' (SMSC [350]) are interconnected with the device GATEWAY SS7 [ 360] through the `Signaling System n 'interfaces. 7 '(SS7). Between the SS7 GATEWAY device [360] and the INTERCONNECT SERVER [200], the `SIGTRAN 'protocol (ie the SS7 protocol on an IP transport layer, as described in Figure 4) is used . Several INTERCONNECT SERVERS [200] are shown in FIG. 5. Indeed, the network operator [300] can interconnect to several other operator networks [300] through as many INTERCONNECT SERVERS. [200]. Several (at least two) SS7 [360] GATEWAYS are also represented, for reasons of redundancy and / or load sharing. A typical case of application of the invention is that of a user traveling in a foreign country. Indeed, it is in this case of application that the interconnection system presented shows its advantages, from the point of view of the cellular operators involved and from the point of view of the end user. The following assumptions are made in this case of application: The cellular subscriber uses a mobile phone that hosts a SIM card provided by its original operator. The SIM card (and its identifiers) is registered in the HLR [330] of the subscriber's original operator. 2941832 -9- - Interconnection services are provided by an 'Interconnection Operator', which must have received from the concerned Cellular Operator rights of access to its HLR [330]. Alternatively, the Interconnection Operator and the affected Cellular Operators may associate to provide the interconnection services. In all cases, the SIM cards of the cellular subscribers who are also users of the interconnection services are registered in the HLR [330] so as to allow the interconnection operations to proceed smoothly. Interconnection has subscribed with the Interconnection Operator. As a result of this subscription, the user was authorized to download the MIDLET [110] on his mobile phone [100]. In addition, at the act of subscription, the user has registered one or more of his telephone identifiers (at least the MSISDN corresponding to his SIM card)

The remainder of the description (and the accompanying figures) describes possible exemplary operational scenarios to show the operation of the INTERCONNECT SERVERS [200] and its interactions with the MIDLET [110]. Those skilled in the art will recognize that these procedures and the associated protocols may change without violating the spirit of the invention. 20 REGISTRATION PROCEDURE - COUNTRY VISITED - Exemplary context: the user of interconnection services is French. He travels to Italy and keeps his SIM card (whose phone ID is MSISDNFR). When MOBILE TERMINAL [100] is powered up the authentication and location procedures are performed with the local (Italian) cellular operator. Figure 6 shows a sequence of steps numbered as these steps being part of the registration procedures with the Interconnection Operator in the country visited (Italy). - Step 1. The user selects the 'Visited Country' option in the MIDLET 30 Menu [110] and enters the country ID (`IT 'in the example). - Step 2. MIDLET [110] starts a given connection (GPRS) by opening a `PDP context 'with the gateway GPRS Support Node (GGSN) of the originating cellular operator. - Step 3. MIDLET [110] is the originator of HTTPS message exchange `PUT '35 with SERVER AAA [500]. The body of the HTTPS message contains the registration information in Step 1. Note: The (public) IP address of the AAA SERVER [500] is fixed in the MIDLET code [110]. 2941832 - 10- Step 4. SERVER AAA [500] is at the origin of an exchange of messages HTTPS `PUT 'with MIDLET [110]. The body of the HTTPS message contains an access request (that is, credentials). The access request appears to the user through an appropriate MIDLET interface [110]. Step 5. The user types a password on an appropriate interface of MIDLET [110]. Step 6. MIDLET [110] is the originator of HTTPS message exchange `PUT 'with SERVER AAA [500]. The body of the HTTPS message contains the password (encrypted). 10 - Step 7. After verification (positive) credentials, SERVER AAA [500] can associate the following information: {MSISDNFR (and also any other telephone number registered by the user to the act of the subscription) , 'FR' (country of origin), `IT '(country visited)}. - Step 8. SERVER AAA [500] is at the origin of an exchange of messages HTTPS 15 `PUT 'with the INTERCONNECTION SERVER [200] (in France and in Italy). Once these messages are received, the INTERCONNECT SERVERS [200] will be able to trigger subscriber registration procedures with SIP REGISTRARs [260]. Note: the registration procedure in the country of origin is almost the same. It can be triggered simply by changing Step 1 (and therefore Steps 7, 8) with the country of origin ID.

OUTSTANDING CALL PROCEDURE WITH UNSTRUCTURED SUPPLEMENTARY SERVICE DATA (USSD), FROM COUNTRY VISITED 25 Background: The (French) user of the interconnection services registered in Italy according to the previous procedure. It makes a call to a French correspondent, also user of interconnection services and having registered for these services in France. Figure 7 shows a sequence of numbered steps that describe this procedure from Italy to France. The numbered steps described hereinafter refer to procedures standardized in the `3GPP 'standards (3rd Generation Partnership Project), well known to those skilled in the art. Step 1. The user selects the option `Call 'in the MIDLET Menu [110] and selects the party to call from his address book. Step 2. MIDLET [110] makes a call according to the USSD syntax: 35 * XYZ * MSISDNFR-APPELE where MSISDNFR-APPELE is the telephone identifier of the correspondent to be called and * XYZ * is a numeric code decided by the Cellular Operator so start recall procedures. Step 3. The USSD message is sent by the cellular phone to the USSD platform of the subscriber's originating Operator. The body of the USSD message contains the telephone identifier of the correspondent to be called. Note: Mobile Application Part (MAP) messages, such as messages 5 `MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_REQ / CNF ', etc. are not detailed: in fact, these messages, as well as the components of the network [300] that route them, are well known by those skilled in the art. Step 4. In turn, the Subscriber's Originator's USSD platform relays the USSD message to a USSD processing center; this processing center may be managed by a third party operator (or by a service provider, in particular the Interconnection Operator) which has interconnection agreements with the subscriber's originating Operator. It will be assumed that the connection between the USSD platform and the USSD processing center is based on the `Short Message Point-to-Point Protocol '(SMPP) protocol: indeed, this protocol is widespread among the 15 service providers based on USSD. In order to relay the USSD message, an SMPP message of the type 'deliver_sm' will be used. The body of the message contains the telephone identifier of the correspondent to be called. - Step 5. The USSD processing center is initiating an exchange of HTTP `PUT 'messages with SERVER AAA [500]. The body of the HTTP message contains the telephone identifier of the calling party and that of the party to be called. The purpose of Step 5 is to allow callback procedures to start depending on the geographic location of the caller (called party). Step 6. Following the registration procedures of the caller (in Italy) and the called party (in France), SERVEUR AAA [500] recorded the following links: 25 For the caller: {MSISDNFR, `FR ' (country of origin), `IT '(visited country)}. For the called party: {MSISDNFR, 'FR' (country of origin)}. These links allow the AAA SERVER [500] to alert INTERCONNECT SERVER [200] (especially the PROXY SIP [210] and B2BUA [240] functional blocks to start callback procedures to both parties ( caller and called party.) - Step 7. In this case of outgoing call, the two correspondents are subscribers to the same French Cellular Operator, therefore SERVER AAA [500] is the originator of an exchange of HTTP `PUT 'messages with the same INTERCONNECT SERVER [200] located in France (in particular, the message is received by the B2BUA device [240]; The body of the` PUT' http message contains the identifiers of the two correspondents ( in general, their cellular telephone numbers.) Step 8. B2BUA [240] verifies the status of the registration of the two correspondents 2941832 -12- - Step 9. A message of the type A SIP INVITE is sent by the B2BUA [ 240] to PROXY SIP [210] The recipient of this message is the calling subscriber - Step 10 (call back to the caller). Following the received SIP INVITE message, the PROXY SIP block [210] of the INTERCONNECTION SERVER [200] in France alerts the SS7 gateway INTERCONNECTION block [220] to send a message of the type `ISDN USER INITIAL ADDRESS MESSAGE '(IAM) to the GMSC block [320] of the French cellular operator [300]. Note: the device [340] (which serves as a protocol intermediary between [220] and [320] is not shown for simplicity, however, its functionality is necessary, as any expert in the art will recognize. 11 (recall to the caller) The GMSC [320] (in the French cellular network) interrogates the HLR [330] (in the French cellular network, because the caller is subscribed to a French Cellular Operator) in order to In general, this identifier allows the GMSC [320] to route the call in the Italian cellular network, in order to reach the caller - Step 12 (call back to the mobile cellular roaming number (MSRN) of the caller. the caller) A message exchange between HLR [330] (French network) and MSCNLR [310] (Italian network) allows HLR [330] to know such MSRN, which will be of type + 39MSISDNAPPELANT: indeed, the MSRN is a temporary identifier assigned to a called subscriber while in the visited network (d In this case, the called subscriber is indeed the calling party who is called back by the network.) The subscriber identifier allows the HLR [330] to know that it can take advantage of the interconnection services; this information is sent to the GMSC [320]. Step 13 (recall to the caller). The HLR [330] sends the GMSC [320] the MSRN (+ 39MSISDNAPPELANT); this message allows the GMSC [320] to know the geographical location of the subscriber, as a user of the interconnection services. Step 14 (callback to the caller). After consulting the routing tables, the GSMC 30 [320] sends an ISUP IAM type message to the INTERCONNECT SERVER INTERCONNECTION block SS7 [220] in Italy, in order to alert the PROXY SIP block [ 210] to send call setup messages to the Italian cellular network. Note: the device [340] (which serves as a protocol intermediate between [220] and [320]) is not shown for simplicity; however, its features are necessary, as any art expert will recognize. Step 15 (calling back to the caller). In turn, the PROXY SIP block [210] of the INTERCONNECT SERVER [200] in Italy sends a 2941832 -13- 'ISUP IAM' message to the GMSC [320] block of the Italian Cellular Operator [300] . This step makes it possible to exploit the interface between a local INTERCONNECT SERVER [200] and the corresponding local cellular network. Step 16 (call back to the caller). In turn, the GMSC [320] block of the Italian Cellular Operator [300] sends an ISUP IAM message to the MSCNLR block [310] of the same network. This step corresponds to the establishment of a local call from a local fixed network, because the recipient of the call is identified by the MSRN (+ 39MSISDNAPPELANT) is the sender of the call is the SERVER D ' INTERCONNECTION [200] local. 10 - Step 17 (callback to the caller). The MSCNLR block [310] of the Italian Cellular Operator [300] sends a message of the type 'CC Setup' to the recipient (that is, the caller, whose temporary identifier is (+ 39MSISDNAPPELANT) .. Step 18 (callback to caller) Call set-up messages (ie 'CC Connect' and 'ANswer Message' - ANM) are sent back from the recipient (ie Ie, the caller) to the MSCNLR [310] block of the Italian Cellular Operator [300], from the MSCNLR block [310] to the GMSC block [320] and finally to the PROXY SIP [210] and B2BUA blocks. [240] Italian INTERCONNECT SERVER [200] The (local) connection between the calling party and the INTERCONNECT SERVER [200] is established .. Step 19 (called party callback) A SIP type A message INVITE is sent by the B2BUA [240] to the PROXY SIP [210] of the French INTERCONNECTION SERVER [200] The recipient of this message is the called subscriber This step is functionally identical in step 9. previous - The The following steps are functionally identical to the steps that describe callback procedures to the caller. Since the called subscriber is not roaming, there will be no need to know the MSRN. At the end of the callback procedure, a (local) connection between the called party and the French INTERCONNECT SERVER [200] will be established. It is interesting to note that in the procedure described the role of the GMSC [320] ] 30 of the French Cellular Operator only consists in routing the callback signal appropriately; GMSC [320] does not act as a switch of the phone call. The roaming call procedure therefore becomes a local callback procedure. In addition, any expert in the art will recognize that the routing of the callback signaling may be effected otherwise: indeed: Step 14 (callback to caller) could be modified as follows: routing tables, the GSMC [320] sends an 'ISUP IAM' type message to the INTERCONNECTION GATEWAY INTERCONNECTION block SS7 [220] of the INTERCONNECT SERVER [200] in France, in order to trigger an establishment message 2941832 - 14 - call PROXY SIP [210] to its peer in Italy. Indeed, SERVER INTERCONNECT [200] in France has retained the identifiers of subscribers recall: it does not need any additional information from the GSMC [320]. 5 - Step 15 (recall to the caller) could be modified in the following way: in turn, the PROXY SIP block [210] of the INTERCONNECT SERVER [200] in France sends a message of type `SIP INVITE 'to the PROXY SIP block [210] of the INTERCONNECT SERVER [200] in Italy.

If the called party is also in a foreign country the described procedure is easily generalized: in step 11, the device GMSC [320] (in the French cellular network) interrogates the HLR [330] (in the network French cell, because the called party is subscribed to a French Cellular Operator) in order to obtain the Mobile Station Roaming Number (MSRN) of the called party. This identifier enables the GMSC [320] to route the call into the cellular network in which the called party is located. Indeed, according to step 14, after consultation of the routing tables, the GSMC [320] sends a message of the type `ISUP IAM 'to the gateway INTERCONNECTION block SS7 [220] of the INTERCONNECT SERVER [200] in the visited country the called party. Another generalization of the procedure described corresponds to the case of a call to a correspondent whose originating operator is foreign, the correspondent may himself be in a roaming situation; as an example, it will be assumed that the called party is Spanish, that he has subscribed to his cellular subscription with `Telefonica 'and that he is traveling in Germany. According to step 6 and following the 25 registration procedures of the called party, SERVEUR AAA [500] recorded the following links: {MSISDNES, `ES '(country of origin),` AL' (visited country)} . In step 11, the GMSC device [320] (in the Spanish cellular network) interrogates the HLR [330] (in the Spanish cellular network, since the called party is subscribed to the Operator `Telefonica ') in order to obtain the Mobile Station Roaming Number (MSRN) of the called party. This identifier 30 allows the GMSC [320] to route the call in the cellular network in which the called party is located. In fact, according to step 14, after consultation of the routing tables, the GSMC [320] sends an 'ISUP IAM' type message to the INTERCONNECTION GATEWAY INTERCONNECTION block SS7 [220] of the INTERCONNECT SERVER [200] in Germany. Yet another generalization of the described procedure corresponds to the case of a caller and / or a called party who change the telephone identifier (for example by changing the SIM card or even by changing the cell phone in the case of a mobile phone. different cellular technology, such as cdmaOne). For example, it will be assumed that the calling party is Spanish, that he has subscribed to his cellular subscription with `Telefonica 'and that he is traveling to Korea, where he rented a telephone. cell operating according to the cdmaOne standard. In step 6 and following the caller registration procedures, SERVEUR AAA [500] recorded the following links: {MSISDNES, `ES '(country of origin), MSISDNKR,` KR' (country visited )}. In this case, it will be possible to initiate a recall procedure from the INTERCONNECT SERVER [200] in Korea without going for the GMSC [320] and HLR [330] devices of the Spanish cellular network); indeed, the mobile station roaming number (MSRN) of the caller corresponds to the Korean temporary identifier MSISDNKR. In addition, thanks to the information contained in SERVER AAA [500], and in particular the links between the temporary and permanent telephone identifier, it will be possible for the various INTERCONNECT SERVERS [200] to initiate the recall procedures the called subscriber can still recognize the permanent identifier of his calling party (provided that the subscriber's Cellular Operator offers the Caller ID service). It is important to note that no INTERCONNECT SERVER [200] may, in general, substitute the calling party's permanent identifier for its temporary identifier, except in the case that the caller is an employee and the INTERCONNECTING SERVER [200] is operated under the responsibility of its employer: this prohibition falls within the legislations in terms of call traceability and is not due to technical reasons. Yet another generalization of the procedure described corresponds to the case of the need to change the national telephone identifier. For example, in Korea so-called 'third generation' (3G) cell phones are not yet adopted by most 'second generation' (2G) technology subscribers, although 3G technology has shown significant progress in terms of increased mobile service availability and improved quality in terms of communication quality. From the point of view of the subscriber to 2G technology, the main barrier to switching to 3G technology is the constraint of changing the phone identifier, adding a prefix `010 '. The foregoing descriptions (registration and calling procedures) show that the Interconnection Operator could act as a 2G portability provider to a 3G number. In fact, the databases contained in SERVEUR AAA [500] could also make it possible to link subscribers' 2G and 3G identifiers by guaranteeing the migration of services associated with 2G technology to 3G technology. The role of the various system components in the routing operations described in Figure 7 can be clarified with reference to Figure 8. In Figure 8 an example of the routing configuration and the ' is represented. Note: `Global Title Translation '(GTT) is the equivalent of IP routing in SS7 networks. The 'translation' operation consists in examining the destination address of the network node (ie the number called) and deciding how to identify this node in the telephone network and how to convey the messages to it. . In accordance with the description of Figure 1, the following assumptions are made: - In general, the cellular network equipment (such as [310], [320], [330], etc.) is identified by a telephone number of the type E.164. The HLR [330], the GMSC [320] and the SS7 network will use this number as an input for the 10 `GTT 'operations, in order to route the messages to the SS7 GATEWAY [360] and finally to the SERVERS. INTERCONNECTION [200] recipients - Network devices are also identified by the 'Point Codes' (PCs) which, in turn, allow routing of messages between the different nodes of the telephone network. While the Global Title is an indirect, virtual address that identifies a telecom resource, the Point Code is a true digital direct address for routing messages between physical devices. As already explained the INTERCONNECT SERVERS [200] are not necessarily part of the cellular network (that is, they can be controlled and managed by third party operators or service providers, or providers of services. interconnection or by an Interconnection Operator); fictitious Dot Codes are assigned to them. SS7 GATEWAY [360] allows the link between these real fake Point Codes and the actual SSRs of the SS7 network equipment - the SS7 GATEWAY [360] and the INTERCONNECTION SERVER [200] are 25 also identified by IP addresses, according to the protocol layers described in Figure 4. Figure 8 shows that: In the HLR [330], the routing tables according to the IMSI and / or the MSRN indicate the routing of the messages to a specific INTERCONNECT SERVER [200] according to the MSRN format assigned to the user's telephone. In addition, the routing tables according to the E.164 identifier of each INTERCONNECT SERVER [200] indicate the routing of the messages to the SS7 GATEWAY [360], the latter routing to be performed through the ` Point Code '35 In the GMSC [320], the routing tables according to the E.164 identifier of each INTERCONNECT SERVER [200] also indicate the routing of messages to the SS7 GATEWAY [360], the latter routing to be done via `Point Code '2941832 -17- - In SS7 GATEWAY [360], the E.164 identifier of each INTERCONNECT SERVER [200] corresponds to a dummy' Point Code '. In addition, each dummy 'Point Codes' corresponds to the IP address of each INTERCONNECT SERVER [2001: thanks to this last match, it will be possible to logically link each equipment / functionality of the cellular network with each feature of the network. interconnection network described, according to the protocol layers of Figure 4. - In each INTERCONNECTION SERVER [200], routing tables are constructed according to the SS7 signaling criteria and also IP networks. Although, according to the exemplary configuration described, the SS7 signaling is not used directly in the INTERCONNECT SERVER [200] (the SS7 signaling being converted to IP signaling according to the `SIGTRAN 'protocol of FIG. Adopted routing model allows direct interfacing with the SS7 network.

Figure 9 depicts steps 10 to 14 of Figure 7 in more detail according to the routing tables shown in Figure 8. Explanations of Figure 9: Details of Step 10 (Figure 7) Call to Caller ). An `ISDN USER INITIAL ADDRESS MESSAGE '(IAM) type message is received by the GMSC block [320] of the French Cellular Operator. This message contains the caller's telephone identifier, which is in a roaming situation and must be called back by the network. - Details of the Step II (Figure 7 - call back to the caller). The device GMSC [320] (in the French cellular network) interrogates the HLR [330] (in the French cellular network, because the caller is subscribed to a French Cellular Operator) in order to obtain the Mobile Station Roaming Number (MSRN). ) of the appellant. This identifier allows the GMSC [320] to route the call in the Italian cellular network, in order to reach the caller. - Details of Step 12 (Figure 7 - callback to caller). A message exchange between HLR [330] (French network) and MSC / VLR [310] (Italian network) allows HLR 30 [330] to know such MSRN, which will be of the type + 39MSISDNAPPELANT HLR [330] examines its tables of routing: the MSRN (and therefore the geographical collocation of the subscriber) allows to derive the identifier `Point Code 'of the equipment which is supposed to handle the recall procedures (that is to say the INTERCONNECTING SERVER [200] in Italy). In the case of the invention this `Point Code 'is fictitious, without thereby impacting conventional HLR procedures [330]. The E.164 address of the INTERCONNECT SERVER [200] (in Italy) is also known by HLR [330]: according to the routing tables, a routing towards this destination implies the passage through the intermediate node [360] (identified by its `Point Code 'PC-360') 2941832 -18- Details of Step 13 (Figure 7 - callback to caller) The HLR [330] sends to the GMSC [320] the MSRN (+ 39MSISDNAPPEI, ANT); this message enables the GMSC [320] to know the geographical location of the subscriber as the user of the interconnection services In the message, the E.164 address of the final destination 5 (c ' that is, the INTERCONNECT SERVER [200] in Italy) is also indicated Intermediate step, not explained in Figure 7: GMSC [320] examines its routing tables: the E.164 address of the final destination (c that is, the INTERCONNECT SERVER [200] in Italy) involves routing messages 10 to the intermediate node GATEWAY SS7 [360], defined as `Destina Point Code '(DPC) with a `PC-360' identifier - Intermediate step, not explained in Figure 7: GMSC [320] relays the` IAM 'message to GATEWAY SS7 [360]. The link is made at the point codes: the `Origination Point Code '(OPC) and the` Destination Point Code' (DPC) 15 correspond to `PC-320 'and` PC-360' respectively. For the functional level link, the E.164 address of the final destination (that is, the INTERCONNECT SERVER [200] in Italy) is also sent to GATEWAY SS7 [360]. - Intermediate step, not explained in Figure 7: GATEWAY SS7 [360] examines 20 its routing tables: the E.164 address of the final destination (i.e. INTERCONNECT SERVER [200] in Italy ) implies the routing of messages according to an IP link: the E.164 address is replaced by the IP address of the INTERCONNECT SERVER [200] in Italy. Intermediate step, not explained in FIG. 7: GATEWAY SS7 [360] relays the message 'IAM' to the destination INTERCONNECT SERVER [200] (in Italy). The protocol used is `M3UA '(` MTP Level 3 User Adaptation Layer', shown in Figure 4), a protocol for routing SS7-compatible signaling over IP networks. The routing is done according to the criteria of the SS7 protocol (that is, by specifying the origin and destination 'Point Codes', the destination 'Point Code' being the dummy of the INTERCONNECT SERVER. [200]) and according to the criteria of the IP networks, according to the `SCTP 'protocol (Stream Control Transmission Protocol). Details of Step 14 (Figure 7 - callback to caller). Step 14 of Figure 7 is composed of the intermediate steps described above. The routing tables described in Figure 8, and the details of the corresponding operations of Figure 9, are an example of implementation. This example shows that the protocol layers of the SS7 systems and their implementation in the support equipment can be fully respected, while adopting a flexible business model for the implementation of an interconnection system according to the DESCRIPTION OF THE INVENTION Anyone skilled in the art will recognize that other implementation options are possible without contravening the spirit of the invention. 5 PROCEDURE FOR SENDING SMS FROM THE COUNTRY VISITED Background: The (French) user of the interconnection services registered in Italy according to the procedure described above. It sends an SMS to a French correspondent, also a user of the interconnection services and having registered for these services in Germany (this case is general, and makes it easy to deduce the case of one of the two registered users in France. ). Firstly, reference will be made to a business model represented in FIG. 10, in which only a subset of the elements present in FIG. 2 is illustrated: in particular, the SMS RELAY [270] consists of a VLR / MSC [310], installed and controlled by the original French Operator in the visited network. This VLR / MSC [310] is logically connected to all the nodes of the local SS7 network, as it respects SS7 connection protocol standards; the VLRIMSC [310] communicates using a very low bit rate connection (eg 64 kbit / s) with the other nodes of the local SS7 network. The purpose of the VLRIMSC [310] is to be able to permanently register a telephone number [311] (or several telephone numbers [311]) belonging to the original French Operator, this number [311] being of the type (+ 33MSISDNRELAIs-sMS) and thus belonging to a database of the original operator: in fact, the adoption of such a configuration would correspond to consider a SIM card associated with the number as being still roaming and always recorded 25 from the same VLRIMSC [310] in the country visited. Functionally, the number [311] (+ 33MSISDNRELAIs-sMS) is also part of the SMS RELAY [270]. Physically, the SMS RELAY [270] (and its constituent VLR / MSC [310]) can be realized purely in software; it will be apparent in the following description that the constraints are very low in terms of physical interfacing (low bit rate) and in terms of 30 computing processors. According to Figure 10, the VLR / MSC [310] of the SMS RELAY [270] can interconnect to the Visited Operator's network according to two possible options: A direct SS7 connection (Figure 10 continuous line, connecting SMS RELAY [270] and VLRIMSC [310] of the visited network); in this case, SMS RELAY [270] exchanges messages according to SS7 protocols and network procedures 35 An SS7 over IP connection (dashed line of Figure 10, connecting SMS RELAY [270] and VLR / MSC [310] of the visited network via the INTERCONNECTION GATEWAY device SS7 [220] and the GATEWAY device SS7 [360]); in this case, SMS RELAY [270] exchanges messages according to the protocols and procedures called `SIGTRAN ', whose OSI layers are shown in Figure 4. The two interconnection options are equivalent to the operation of the system according to the invention. Figure 11 shows a sequence of numbered steps that describe this procedure for sending SMS from Italy to Germany. The numbered steps described below refer to standardized procedures in the `3GPP '(3rd Generation Partnership Project) standards; these procedures will not be explained in detail because well known to those skilled in the art. - Step 1. The user (having a French identifier MSISDNFR-ORIG) chooses the option `SMS 'in the MIDLET menu [110] and selects the correspondent to whom he wishes to send the SMS from his address book . - Step 2. MIDLET [110] is the originator of HTTPS message exchange `PUT 'with AAA SERVER [500]. The body of the HTTPS message contains a request to send SMS. Note: the (public) IP address of the SERVER AAA [500] is fixed in the MIDLET code [110]. - Step 3. Following registration procedures of the "calling" user (in Italy) SERVER AAA [500] recorded the link: {MSISDNFR-0RIG, `FR '(country of origin), 20` IT' (country visited)}. This link allows the SERVER AAA [500] to check, with the RELAIS DE SMS [270] (in Italy) the availability of a number [311]. Step 4. SERVER AAA [500] is the originator of a message exchange HTTPS `PUT 'with MIDLET [110]. The body of the HTTPS message contains an available identifier [311] of the type + 33MSISDNRELais-SMS • 25 Step 5. MIDLET [110] formats the SMS composed by the "calling" user and sends the message to the identifier [311] received by SERVER AAA [500]. The body of the message contains the identifier of the recipient correspondent (MSISDNFR-DEST) and the actual text of the message. Note: the total length of an SMS is limited to 180 characters, the text of the message will be limited to 165 characters, 15 characters are reserved 30 to the recipient number - Step 6. The SIM card of the mobile phone of the user contains the 'E.164' number of the SMSC [350] of the original French Operator. This SMSC [350] must know the geographical location of the destination number [311]. For this purpose, a message exchange of the type SEND_ROUTING_INFO_FOR_SM_REQ 35 (SENDROUTINGINFOFORSMCNF) takes place between SMSC [350] and HLR [330]. This exchange is not explained in Figure 11, as well known by the art experts. As shown in Figure 10, the destination number [311] is permanently allocated to the VLR / MSC [310] in the destination network, this VLR / MSC [310] 2941832 -21 - forming part of the SMS RELAY [ 270] (in Italy). The message SEND ROUTING INFO FOR CNF SM will therefore contain the identifier 'E.164' of such VLR / MSC [310] - Step 7. Thanks to the information obtained in Step 6, SMSC [350] can relay the 5 message to the recipient number [311], using the procedure `FORWARD_SMMTREQ ', well known to those skilled in the art. In accordance with Step 5, the body of the message contains the identifier of the recipient correspondent (MSISDNFR-DEST) and the actual text of the message Step 8. Once the message has been received, the SMS RELAY processor [270] (at 10 Italy) splits the actual message text from the recipient ID. - Step 9. SMS RELAY [270] is at the origin of an exchange of messages HTTPS `PUT 'with the B2BUA [240] (SMS RELAY [270] and B2BUA [240] are part of the same device SERVER D INTERCONNECTION [200]). The body of the HTTPS message contains the text of the message and the identifier of the recipient, according to Step 8. - Step 10. In turn, B2BUA [240] is at the origin of an exchange of messages HTTPS `PUT 'with the with SERVER AAA [500]. The body of the HTTPS message is the same as for the previous step. The purpose of step 10 is to enable B2BUA [240] to discover its 'peer' (ie the B2BUA [240] on which the recipient correspondent registered). Step 11. Following the registration procedures of the recipient user (in Germany) SERVER AAA [500] has registered the link: {MSISDNFR_DEST, `FR '(country of origin),` ALL' (visited country)}. - Step 12. SERVER AAA [500] is at the origin of an exchange of messages HTTPS 25 `PUT 'with the B2BUA [240] (in Italy). The body of the HTTPS message contains the name (and / or address) of the B2BUA [240] (in Germany) on which the receiving party registered. Step 13. B2BUA [240] (in Italy) sends a message of the SIP MESSAGE type (well known to those skilled in the art) to its counterpart (B2BUA [240] in Germany). The `From 'and` To' fields of the message header correspond respectively to the "calling" and receiving party. The body of the message (SMS PDU) is the text of the SMS - Step 14. B2BUA [240] is at the origin of an exchange of messages HTTPS `PUT 'with the RELAIS OF SMS [270] (RELAIS OF SMS [270 ] and B2BUA [240] are part of the same INTERCONNECT SERVER [200] device in Germany). The body of the HTTPS message contains the message text, the recipient ID, and the sender ID. 2941832 - 22 - Step 15. The SMS RELAY [270] processor (in Germany) combines the actual text of the sender identifier message into a single message body. Step 16. The VLR / MSC [310] that composes the SMS RELAY [270] device (in Germany) needs to know the local global address of the local VLR / MSC [310]. MSISDNFR_DEST recipient is registered. As such, it sends a request 'MAP _PROVIDE ROUTING _INFORMATION' to the HLR [300]. Normally, this request is sent by a GMSC [320], i.e., by the element operatively located at the boundary of the cellular network, to route the messages out of such a network. In the case of the invention, the request 'MAP_PRO VIDE ROUTING INFORMATION' is sent by an element [310] internal to the local network (in Germany). However, since this element [310] is controlled by the original French Operator, it must be considered as at the border between the local network (in Germany) and the network of origin (in France). In any case, it is up to the HLR [300] to accept or reject the MAP PROVIDE ROUTING INFORMATION messages; it is sufficient that, vis-à-vis the HLR [300], the VLR / MSC [310] which composes the device RELAIS DE SMS [270] is considered as GMSC [320]. Step 17. HLR [300] responds to the request of Step 16 by sending the MAP PROVIDE ROUTING INFORMATION ACK message. This message will contain the Global Title of the local VLR / MSC [310] on which the destination MSISDNFR_ DEST number is registered. Step 18. The VLR / MSC [310] which composes the SMS RELAY [270] device (in Germany) has all the information to be able to send a message 25 'FORWARD_SM_MT_REQ' (well known by the art experts) to the VLRIMSC [310] of the local network. In accordance with Step 15, the body of the message contains the identifier of the sending correspondent (MSISDNFR-oRIG) and the real text of the SMS Step 19. The local VLR / MSC [310] relays a message `SMS-MT '. known to those skilled in the art) to the recipient correspondent. Step 20. MIDLET [110] decodes the received SMS, so as to split the real text of the SMS that will be presented to the user, as well as the identity of the sending correspondent.

The presented method has advantages in terms of interconnection cost and, as a result, can be interesting in order to lower the costs of sending SMS when roaming. In fact: 2941832 - 23 - In the first phase of the procedure (SMS sent from the "calling" correspondent's telephone to SMS RELAY [270] in the same country calling ") the messages are routed inside the local network (in Italy), in addition, the SMS receiver is controlled by the original French Operator.The costs of this SMS correspond to the local transit costs in the visited network. only messages that must pass through an international provider (which usually provides connectivity at the Signaling Convection Control Part, `SCCP 'level) are the messages from step 6. - In the last phase of the procedure (SMS sent the number [311] of the SMS RELAY 10 [270] in the same recipient's country to the recipient's telephone) the messages are routed within the visited local network (in Germany), in addition to the number [311] which bewitching ie the SMS is controlled by the original French Operator. The costs of this SMS are equivalent to local transit costs in the visited network. For the international connection, the only 15 messages that must pass through an international provider (which usually provides connectivity at Signaling Connection Control Part, `SCCP ') are the messages in steps 16 and 17. - In the intermediate phase, the messages transit through the public Internet network, without any cost for the French Cellular Operator. Steps 2 and 4 are performed via an internet connection, via the GPRS network. According to recent pricing models, a roaming GPRS connection is charged at around 15 per megabyte, typically with prepaid subscriptions. If the messages passing through steps 2 and 4 are estimated at 200 bytes, the cost for starting the SMS sending procedure is about 0.3 cents for user.

The method presented has advantages over existing procedures in `cdmaOne 'type networks (ie for cdmaOne subscribers on roaming and for interconnection between different networks such as GSM / GPRS / UMTS 30 and cdmaOne). Indeed, the procedures for the transmission of SMS, according to the standard known as the cdmaOne standard, are based on the following principles: - In order to send an SMS to the recipient's phone, the message must be sent to the `Message Center '(MC) recipient, this MC may be in a country visited by the recipient. In order to deliver the message to the recipient MC, the original MSC [310] (called MSC `anchor 'in IS-41) or the MC of the sender must translate the identifier of the recipient mobile phone (connected but not equivalent to MSISDN) by identifying the recipient MC. 2941832 -24- - The interconnection between the sending and receiving MC is provided by an 'SMS Router' which also guarantees interoperability between different networks such as GSM / GPRS / UMTS and cdmaOne. The principles of the cdmaOne standard show that the functionality of several network elements must be linked to ensure the proper sending of the SMS; in addition, depending on the business models considered it is necessary to register the 'SMS Router' on the originating and / or destination network. Those skilled in the art will appreciate that the invention can simplify these SMS sending procedures and thereby reduce the interconnection costs. Indeed, it can be seen that: The sending MC can relay the text to a number [311] of the SMS RELAY [270], this SMS RELAY [270] having a logical interface with the sending MC. Since the number [311] is registered in the same network of the sending telephone, any recipient MC would be local. 15 - The SMS RELAY [270] can relay the text to its 'peer' in the destination network. This interconnection is provided by the public Internet network A number [311] of the SMS RELAY [270] in the destination network can send the text to the final destination, via a sending MC and a possible recipient MC, both MC being in the same local network (recipient). The SMS sending procedure described is generalized in the case of a sender and / or a recipient who change the telephone identifier (for example by changing the SIM card or even by changing the cell phone in the case of a different cellular technology, such as cdmaOne). By way of example, it will be assumed that the sender is Spanish, that he has subscribed to his cellular subscription with `Telefonica 'and that he is traveling to Korea, where he rented a cellular telephone operating according to the cdmaOne standard. Following the caller registration procedures, SERVEUR AAA [500] recorded the following links: {MSISDNES, `ES '(country of origin), MSISDNKR,` KR' (visited country)}. In a preferred embodiment of this generalization, the SMS RELAY [270] will consist of one or more mobile phones, equipped with corresponding SIM cards; functionally, these mobile phones will interconnect with the MOBILE OPERATOR NETWORK [300] (especially the Short Message Service Center - SMSC [350] local). In this case, the original French operator 35 does not need to install and operate a VLR / MSC [310] in the visited network. Therefore, steps 1 through 9 of the SMS sending procedure are modified according to the following description: Step lA (change of sender ID). The user (having a Spanish identifier MSISDNES-oRIG) chooses the option `SMS 'in the MIDLET menu [110] and selects the correspondent to whom he wishes to send the SMS from his address book. 5 - Step 2A (change of identifier of the sender). MIDLET [110] is the originator of HTTPS message exchange `PUT 'with SERVER AAA [500]. The body of the HTTPS message contains a request to send SMS. Note: the (public) IP address of the SERVER AAA [500] is fixed in the MIDLET code [110]. Step 3A (change of identifier of the sender). Following the sender registration procedures (in Korea) SERVER AAA [500] recorded the link: {MSISDNES, `ES '(country of origin), MSISDNKR,` KR' (visited country)}. This link allows the AAA SERVER [500] to check, with the SMS RELAY [270] (in Korea) the availability of a telephone receiver associated with a number [311]. Step 4A (change of identifier of the sender). AAA SERVER [500] is at the origin of an HTTPS message exchange `PUT 'with MIDLET [110]. The body of the HTTPS message contains an available identifier [311] of the type + 82MSISDNRELAIs_ SMS. (+82 is the country identifier for Korea) - Step 5A (change of sender ID). MIDLET [110] formats the SMS dialed by the "calling" user and sends the message to the receiver [311] whose identifier [311] has been received from SERVER AAA [500]. The body of the message contains the identifier of the recipient correspondent and the actual text of the message. Step 6A. (change of identifier of the sender). The mobile phone rented by the sender contains the 'E.164' number of Korean Operator's 'Message Center' (MC). This MC must know the geographical location of the receiving receiver [311] through a SEND ROUTING INFO FOR SM REQ message exchange (SEND_ROUTING_INFO_FORSMCNF) with the HLR. This message exchange is local, inside the Korean Operator's network. Step 7A. (change of identifier of the sender). Thanks to the information obtained in Step 6, the MC can relay the message to the recipient receiver [311], using the `FORWARD_SM_MT_REQ 'procedure. According to Step 5, the body of the message contains the identifier of the receiving party and the actual text of the message 35 - Step 8A. (change of identifier of the sender). Once the message is received, the SMS RELAY [270] processor (in Korea) splits the actual message text from the recipient's ID. Step 9A. (change of identifier of the sender). As for the corresponding step of the SMS sending procedure previously described

The SMS registration, call and send / receive procedures described characterize the invention in its generalities. Indeed, those skilled in the art will recognize the main novelties in the disclosed interconnection system, in particular: An interconnection system between cellular networks (these networks being able to be installed in different countries) according to which the equipment and the functionalities of the interconnection are based on the public Internet protocols, these equipments and 10 functionalities operating in an alternative way to the traditional equipments and functionalities based on the protocols and infrastructures known as 'SS7'. The possibility for Cellular Network Operators to operate such an interconnection system, by simplifying roaming agreements between them, by being able to create new roaming agreements quickly and efficiently and by reducing the costs of interconnections (International), including so-called 'transits' costs and those related to the use of 'SS7' interconnection infrastructure operated by third parties. The possibility for Cellular Network Operator subscribers to benefit from advantageous pricing when they are in a roaming situation, in particular through an interconnection service between Cellular Operators which exploits the system and the interconnection devices described and which uses software applications (called `Midlet 'in the description) which are installed in the mobile phones of the subscribers and which make it possible to manage any cellular communication according to the described principles. 25 - INTERCONNECTION SERVERS [200] which form the basis of the interconnection system described, these servers being installed in `` Point-of-Presence '' in each country where the interconnection system is deployed, these servers are INTERCONNECTION [200] capable of connecting the different cellular networks to the public Internet network, the interface between a cellular network and one (or more) INTERCONNECT SERVER [200] being able to be done by means of SS7 identifiers (called `Point Codes' '), these identifiers being dummy in the INTERCONNECT SERVERS [200]. - The use of such 'dummy Point Codes' of the INTERCONNECT SERVERS [200] in order to be able to route calls to roaming cellular subscribers via the Mobile Station Roaming Number (MSRN), although known to those skilled in the art, this MSRN being used locally (i.e., within a local cellular network) for any incoming call. 2941832 - 27 - SMS RELAYS [270] that are part of the INTERCONNECT SERVERS [200]. These SMS RELAYS [270] make it possible to reduce the cost of transporting SMS between different cellular networks; the SMS RELAYS [270] are composed of MSCNLR [310] functionalities managed by the Cellular Operator in foreign cellular networks and by telephone numbers [311] (also managed by Cellular Operators in foreign cellular networks) which are registered on such MSCNLR [310] permanently. Such a configuration of the SMS RELAYS [270] makes it possible to separate the SMS send / receive procedures into separate sections, where the cellular sections are local and do not use the international SS7 procedures and protocols. The described method is compatible with the specifications of an interconnection system as described above.

Embodiments There are alternative embodiments with respect to the preferred configuration of the method which refers to the described voice and SMS communications procedures. These variants can be divided into different classes: CLASS 1: VARIANTS IN RELATION TO THE PROGRESSIVE DEPLOYMENT OF THE INTERCONNECTION SYSTEM AND THE ASSOCIATED SERVICES It is obvious that the deployment of a system according to the description and the support of the associated services is done in a progressive way. Indeed, the system can be adopted by some Cellular Operators and not by others. The system could also be offered by Interconnection Operators, which provide physical and logical network solutions (protocols, procedures) for interconnecting different communication networks. In any case, the progressive deployment of such a solution implies that subscribers to the interconnection services will be able to communicate with correspondents who are not subscribed to such services. An alternative embodiment therefore consists in establishing communication procedures between subscribers and non-subscribers so as to generate interest for the described interconnection service and thus be able to facilitate its expansion. These communication procedures between subscribers and non-subscribers are described in three phases: allocation of a number to the subscriber, call diversion, call from a non-subscriber to a subscriber. Subscriber number assignment 2941832 - 28 - The Interconnection user has subscribed with the Interconnection Provider (such as an Interconnection Operator, or a Cellular Operator). Or other). As a result of this subscription, the user was authorized to download the MIDLET [110] on his mobile phone [100]. In addition, at the act of subscription, the user has registered one or more of his telephone identifiers (at least the MSISDN corresponding to his SIM card). In addition, the Interconnection Provider reserves a fixed number to the user, which number is generally a local number in the home country of the subscriber. Alternatively, this number can be a `global 'number, for example a number with prefix` 883', recently standardized by the International Telecommunications Union (ITU). This number could be known only to the MIDLET [110] and the AAA SERVER [500], without the subscriber having any knowledge; otherwise, the subscriber might be aware of this number. The terms of reservation of this number may be various, depending on the contract between the subscriber and the Interconnection Services Provider and do not affect the spirit of the invention. In the sequel, the number will be defined as `UserNumberAbout '. Call Forwarding Before traveling to a foreign country, the user of the interconnection services 20 will initiate call forwarding procedures to the 'CalledNumberAllowed' reserved to him by the Interconnection Provider. These procedures will preferably be of the type `Cali Forwarding Not Reachable ': if the user can not be reached, the call will be diverted to the number` RingNumberAbout'. According to the principles of the invention, the call deflection procedure could be initiated by MIDLET [110] which, in particular, could contain - in a secure memory area - the number 'AttachedNumberAllowed'. Preferably, the call deflection procedure should be started when the user is still in his home country: it is then the network of the original Cell Operator that would support this procedure, signaling this condition to the HLR [330] which thus updates the profile of the user. If the call deflection procedure were to be initiated from a visited country (and thus once the user is under the control of a visited Cellular Operator) there is a risk that the call deflection procedure would be not treated appropriately. The call deflection procedure is described in Figure 12, which illustrates the start of such procedure using the MIDLET menu [110] (Step 1), by triggering a `SUPPLEMENTARY SERVICE REGISTER 'message (SS REGISTER ) from MIDLET [110] to the Operator's USSD Platform, this message containing the `Cali Forwarding Not Reachable 'request (CFNR) and the destination number (Step 2), starting a` MAP' type message exchange REGISTER SS 'and 2941832 -29- `MAPINSERT_SUBSCRIBERDATA' (well known by the art experts) between the USSD platform of the Operator and the HLR [330], this exchange of messages to record this condition on the user profile (Step 3), closing the message sequence and sending the result of the procedure to the user interface (Steps 4 and 5). Calling a non-subscriber to a subscriber Vis-à-vis a non-subscriber, the subscriber is presented as `detached '(detached) in relation to the visited cellular network: in his database, the HLR [ 330] marks the subscriber as `not reachable ': any call to the subscriber from a non-subscriber 10 takes place according to the so-called Early Cali Forwarding rules, which are illustrated in Figure 13, according to which : Step 1. The caller (non-subscriber to the Interconnection Services) dials the correspondent's number (subscriber of such services). As the caller is not subscribed, he does not have access to the MIDLET [110]. Following the call procedure, an ISUP 15 IAM message is sent to the GMSC [320] located in the network of the originating French Operator of the called party. Note: any intermediate network element is not mentioned, for simplicity. Step 2. The GMSC [320] device (in the French cellular network) interrogates the HLR [330] (in the French cellular network, since the caller is subscribed to a French Cellular Operator) in order to obtain the Mobile Station Roaming Number (MSRN) of the caller. Step 3. The HLR [330] returns to GMSC [320] the call diversion number `AwnAbledNumber ', which number is stored in the HLR database [330], following the call diversion procedure performed by the subscriber before moving to the foreign country. Step 4. After consulting the routing tables, the GSMC [320] sends an ISUP IAM message to the INTERCONNECTION GATEWAY INTERCONNECTION SS7 [220] block of the INTERCONNECTION SERVER [200] in France, to alert the B2BUA block. [240] to trigger the procedures of step 5. Note: SS7 INTERCONNECTION DEVICE 30 [220] as well as the device [340] (which serves as a protocol intermediary between [220], and [320] are not shown for simplicity, however, their functionality is necessary, as any expert in the art will recognize Step 5. B2BUA [240] verifies the registration status of the two correspondents, in particular with appropriate interaction. with SERVER AAA [500] (interaction not shown, for simplicity) it will be possible to determine that the caller is not subscribed to the Interconnection Services) 2941832 -30- - Step 6. An answering machine (Interactive Voice Response) ', IVR) can be triggered, in order to signal to the ap that the called party is roaming, and that it can be reached at a reduced price by using specific interconnection services. Indeed, this step can be usefully exploited to send advertisements on the interconnection services and to explain the benefits for the Operators and for the general public. The IVR can thus give instructions to the caller, depending on whether he wants to continue the call or terminate it or leave a message. Step 7. Assuming the caller continues the calling process, he presses a key of his telephone keypad to alert the B2BUA [240] that the appeal procedure can continue. It is obvious that steps 6. and 7. are optional, and that the calling procedure can continue without necessarily having an interaction with the caller. Step 8. A message of the type A SIP INVITE is sent by the B2BUA [240] of the INTERCONNECT SERVER [200] in France to the PROXY SIP [210]. It is assumed here that the called party (subscriber of Interconnection Services) is traveling in Italy. The SIP INVITE message is relayed to the PROXY SIP [210] of the INTERCONNECT SERVER [200] in Italy. Step 9. Following the received INVITE SIP message, the PROXY SIP block [210] of the INTERCONNECT SERVER [200] in Italy alerts the SS7 INTERLOCKING INTERCONNECTION block [220] (not shown for the sake of simplicity) so that it sends an `ISUP IAM 'type message to the GMSC block [320] of the visited Cellular Operator. Note: the device [340] (which serves as a protocol intermediary between [220] and [320] is not shown for simplicity, however, its features are necessary, as any expert in the art will recognize. It is important to note that the triggering of the 'ISUP IAM' procedure by the PROXY SIP block [210] of the INTERCONNECT SERVER [200] in Italy does not use the `Mobile Station Roaming Number 'to identify the recipient of The call, as described in steps 15., 16., 17. in Figure 7. Indeed, in Figure 7 the case considered was that of an Interconnection Services subscriber who called another subscriber: both subscribers could therefore take advantage of the 'local' feature of any call between them, and in Figure 13 the caller does not subscribe to the services, so it is normal for the caller not to be charged for local criteria: 35 in all cases, and as any expert in the art will recognize, the The call according to the description of Figure 13 will have a reduced cost for the Interconnection Operator, the link between the cellular networks not making use of conventional interconnections 'SS7'. For the called party, the only additional cost that he must assume is that of call diversion. It is also important to note that the system should not have the same functional behavior as the case of a call from an Interconnection Services subscriber to another subscriber (Figure 7 calling procedure). or as the case of a call from a non-subscriber to a subscriber (call procedure of Figure 13). Indeed, according to Figure 7, local calling procedures must be triggered, these procedures using the Mobile Station Roaming Number (MSRN) to identify the caller (subscriber) and the called party (subscriber); however, according to Figure 13, call deflection procedures must be triggered. Figure 14 describes the general procedure, which is valid in all cases. In Figure 14 it is shown that the distinction between the two cases can be made at the level of the dialogue between the GMSC [320] and the HLR [330], these two devices being part of the cellular network of the Originator the caller (subscriber), the called party (subscriber) and the caller (non-subscriber). In the following description, it will be assumed that such original Operator is French, that the called party is roaming in Italy and that the caller (subscriber or non-subscriber) is in France. Figure 14 shows a sequence of numbered steps which detail the dialogue between the GMSC [320] and the HLR [330]: - Step 1. A message of the type 'ISDN USER INITIAL ADDRESS MESSAGE' (IAM) is received by the block GMSC [320] of the French Cellular Operator. This message contains the caller's phone identifier. The caller could be a subscriber to Interconnection Services who is roaming and needs to be called back by the network. Alternatively, the caller could be a non-subscriber and the call should be redirected to the'NoAbledNumber '. It is therefore necessary for the GMSC [320] to recognize the caller type and alert the HLR [330] accordingly. Step 2. The device GMSC [320] (in the French cellular network) interrogates the HLR [330] (in the French cellular network, because the caller is subscribed to a French Cellular Operator) in order to obtain the Mobile Station Roaming Number 30 (MSRN) of the caller (if the caller is subscribed to the Interconnection Services) or the Forward-to-Number (FTN) if the caller does not subscribe to the Interconnection Services . In order for the HLR [330] to respond according to the state of the caller (subscriber or non-subscriber), the GMSC [320] may exploit one of the optional parameters of the SEND_ROUTING_INFO_REQ message and use it to provide the HLR [330] 35 information on the status of the caller. For example, the `Network Indication of Alerting 'parameter can be used: this parameter is optional; the HLR [330] must be able to recognize and treat it. 2941832 - 32 - Step 3. It is assumed that the HLR [330] can support the `Network Indication of Alerting 'parameter, which is part of the SEND_ROUTINGINFO_REQ message sent by the GMSC [320]. In this case, a specific configuration of this parameter may be recognized by the HLR [330], which will therefore be able to perform the appropriate actions depending on the state of the caller (subscriber or non-subscriber). Step 4. This step is executed only if the caller is subscribed to the Interconnection Services. In this case, a message exchange between HLR [330] (French network) and MSC / VLR [310] (network in Italy) allows HLR [330] to know the MSRN, as described in Step 12 of Figure 7. Step 5. HLR [330] examines its routing tables: if the caller is subscribed to the Interconnection Services, the MSRN obtained in step 4 derives the 'Point Code' identifier from the equipment who is supposed to handle the recall procedures (ie the INTERCONNECT SERVER [200] in Italy). In this case, Step 5 is identical to Step 12 of Figure 7. If the caller does not subscribe to the Interconnection Services, the called party's profile is examined in order to know the number. call deflection 'FTN'. Step 6. Following Step 5, the HLR [330] sends to the GMSC: o either the MSRN (+ 39MSISDNAPPELANT), and the E.164 address of the final destination which will allow the call routing in the visited network (that is, the INTERCONNECT SERVER [200] in Italy). In the SEND_ROUTING_INFOCNF message, the `Roaming Number 'parameter will have the value of the MSRN. o Let 'FTN' (`AllowedNumber '), and the E.164 address of the destination which will allow call routing in the visited network (i.e. INTERCONNECT SERVER [200 ] in France, because the called party has diverted the call to a French identifier, such identifier being registered in the SERVER OF INTERCONNECT [200] of the country of origin, as explained in Figure 12). In the SEND_ROUTING_INFO_CNF message 30, the `Forwarded to Number 'parameter will be set to` RingNumberAbout'. Steps 7, 8, 9, 10 are equivalent to steps 14 and 15 of Figure 7 (and the explanations detailed in Figure 9). The only difference is the need on the part of the GMSC [320] to route the call to the PROXY SIP [210] belonging to the INTERCONNECT SERVER [200] in Italy (in the case of a caller subscribing to 'Interconnection) or to the PROXY SIP [210] belonging to the INTERCONNECT SERVER [200] in France (in the case of a caller not subscribed to such services). Following step 6 and its routing tables, the GMSC [320] 2941832 - 33 - may route the call signaling to the appropriate INTERCONNECT SERVER [200].

The described procedure requires a specific customization of the messages exchanged between the GMSC [320] and the HLR [330]. Although the customization, as described in Steps 2 and 3 of Figure 14 is particularly simple, it requires the implementation of specific software procedures and an adaptation of the databases of the original Operator of the 'caller (and called party). It will be shown later that the use of known functionalities under the acronym `CAMEL '(Customized Mobile Network Enhanced Logic Applications) allows a simple introduction of all the procedures described in the invention It is interesting to note that the use of a telephone identifier per subscriber (identifier called `NumeroAllouéAbonné ') is not strictly necessary and reduces the cost related to the purchase of such identifier. Indeed, it is possible to use statistical calculations to consider the necessary identifier numbers, according to certain traffic assumptions. For example: Number of subscribers to Interconnection Services = 10000. Percentage of subscribers who are simultaneously roaming = 20%. (2000 roaming subscribers) 20 - Traffic of 0.075 Erlangs per roaming subscriber (this means that every subscriber makes or receives a call with a 15% probability in the hours of heavy traffic). Therefore, the support of a traffic of (2000 x 0.075) = 150 Erlangs is necessary - This support implies the need of about 170 simultaneous channels, with a probability of rejection of call of 1% 25 Therefore, it will be necessary to allocate 170 telephone identifiers for the 10,000 subscribers (1 identifying all 58 subscribers around). With such a dimensioning, there is no longer a unambiguous correspondence between each subscriber to the roaming services and its call diversion number. This implies that it is not possible for an INTERCONNECT SERVER [200] (on which the call diversion numbers are recorded) to know the identity of the called party directly. One possibility to work around this problem is as follows: The MIDLET [110] installed on the subscriber's MOBILE TERMINAL [100] is used to boot the address book (from the SIM card or MOBILE TERMINAL 35 [100]. ]) to save a copy on the AAA SERVER [500]. - The call deflection procedure described in Figure 12 will be slightly modified: before starting the exchange of messages `USSD 'with the HLR [330], the 2941832 - 34 - MIDLET [110] will have received beforehand a call diversion number from SERVER AAA [500]. - When the caller (non-subscriber) calls his correspondent (subscriber), the call is diverted to the number provided by the SERVER AAA [500]. 5 - Upon receipt of the call signaling, the INTERCONNECT SERVER [200] (on which the call diversion numbers are registered) can not know the identity of the called party (subscriber). On the other hand, from the address book of the called party (subscriber), INTERCONNECT SERVER [200] can search if a match exists between one of the entries of the address book and the number of the caller. . In this case, the identity of the called party can be deduced. - If the caller's number is not present in the address book, the answering machine (IVR) in Step 6 of Figure 13 will prompt the caller to re-type the caller's number. Such number will be received by B2BUA [240] from the INTERCONNECT SERVER [200] by means of the `DTMF 'tones, according to Step 7 of Figure 13. A generalization of the described procedure corresponds to the case of a called party ( subscriber Interconnection Services) that changes phone identifier (for example by changing SIM card or even changing cell phone in the case of a different cellular technology, such as cdmaOne). The procedures for Call Forwarding and Calling from a non-subscriber to a subscriber remain very similar to the descriptions in Figure 13 and Figure 14. For example, it will be assumed that the called party is French, that he has subscribed to his cellular subscription with `SFR 'and that he is traveling to Korea, where he rented a cell phone operating under the cdmaOne standard. According to the explanations of the registration procedures, SERVEUR AAA [500] has recorded the following links: {MSISDNFR, 'FR' (country of origin), MSISDNKR, 'KR' (visited country)}. In addition, it will be assumed that the calling party is French, that he too has subscribed to his cellular subscription with `SFR 'and that he is in France. In this case, it should be noted that: If the caller is also subscribed to the Interconnection Services, it will be possible to initiate an appeal procedure from the INTERCONNECT SERVER [200] in Korea without for the GMSC [320] and HLR [330] devices of the French cellular network); in fact, the mobile station roaming number (MSRN) of the called party corresponds to the Korean temporary identifier MSISDNKR. - If the caller does not subscribe to the Interconnection Services, a call deflection procedure of the 'CFNR' type (triggered by the called party before traveling to Korea) will route the call. to the INTERCONNECT SERVER [200] in Korea from the INTERCONNECT SERVER [200] in France (where the call diversion number is registered), the latter SERVER 2941832 - 35 - INTERCONNECT [200] in France having received call signaling from the GMSC [320] of the French cellular network, which GMSC [320] is aware of the call diversion number through a signaling exchange with the HLR [330] (of the network French cell). 5 CLASS 2: VARIANTS IN RELATION TO THE BUSINESS MODEL. The business model considered until now assumes that the interconnection services are provided by an 'Interconnection Operator', which must have received from the concerned Cellular Operator access rights to its HLR [ 330]. Alternatively, the Interconnection Operator and the affected Cellular Operators may associate to provide the interconnection services. In all cases, the SIM cards of cellular subscribers who are also users of the interconnection services are registered in the HLR [330] so as to allow interconnection operations to proceed smoothly. A significant implementation variant is to assume that 1 "Interconnection Operator" (Interconnection Services Manager) has no industrial or commercial link with cellular Operators for the provision of these services. is therefore: - Accountable to its cellular operator for the telephony services, SMS, etc. 20 Accountable to 1 "Interconnection Operator" for the provision of Interconnection Services, in order to reduce the costs of its communications when it is located in a situation of homelessness. In practice, this business model implies that the "Interconnection Operator" must be able to operate cellular networks as well as public Internet networks to provide these Interconnection Services, without having to agree with Cellular Operators. for an update of their infrastructures The exploitation of existing networks and resources by the "Interconnection Operator" may lead to changes in the registration, call, etc. procedures. These changes (if any) will be examined later. 30 Registration Procedure - Country Visited No changes from Figure 6 and its Steps. Outgoing call procedure: call back via HTTP connection The same introductory context as in Figure 7 is used: the (French) user of the Interconnection Services registered in Italy according to the procedure 35 d 'recording. He makes a call to a French correspondent, also a user of Interconnection Services and having registered for these services in France. Figure 15 shows a series of numbered steps that describe this procedure from Italy to France: 2941832 -36- Step 1. The user chooses the option `Call 'in the MIDLET Menu [110] and selects the correspondent to call from his address book. Step 2. MIDLET [110] starts a given connection (GPRS) by opening a `PDP context 'with the` Gateway GPRS Support Node' (GGSN) of the cellular operator 5 of the visited network (in Italy). Step 3. MIDLET [110] is the originator of HTTPS message exchange `PUT 'with SERVER AAA [500]. The body of the HTTPS message contains the information about the caller ID and the caller ID. Note: the (public) IP address of the SERVER AAA [500] is fixed in the MIDLET code [110]. 10 - Step 4 Following the registration procedures of the caller (in Italy) and the called party (in France), SERVEUR AAA [500] recorded the following links: For the caller: {MSISDNFR, `FR ' (country of origin), `IT '(visited country)}. For the called party: {MSISDNFR, `FR '(country of origin)}. These links allow the AAA SERVER [500] to alert INTERCONNECT SERVER [200] (especially the PROXY SIP [210] and B2BUA [240] functional blocks to start callback procedures to both parties ( caller and called party) - Step 5. In this case of outgoing call, the two correspondents are subscribers to the same French Cellular Operator, therefore SERVER AAA [500] is at the origin of an exchange. of HTTP messages `PUT 'with the same INTERCONNECT SERVER [200] located in France (in particular, the message is received by the B2BUA device [240]; The body of the` PUT' http message contains the identifiers of the two correspondents ( in general, their cellular telephone numbers).) Step 6. B2BUA [240] verifies the status of the registration of the two correspondents Step 7 (callback to the caller) A message of the SIP INVITE type is sent by the B2BUA [240] to PROXY SIP [210] (both devices are part of the INTERC SERVER ONNEXION [200] in France). The PROXY SIP device [210], in turn, relays the SIP INVITE message to the PROXY SIP [210] which is part of the INTERCONNECT SERVER [200] in Italy. The recipient of this message is the calling subscriber Step 8 (callback to caller). The PROXY SIP block [210] of the INTERCONNECT SERVER [200] in Italy sends an ISUP IAM message to the GMSC block [320] of the Italian Cellular Operator [300]. This step makes it possible to exploit the interface between a local INTERCONNECT SERVER [200] and the corresponding local cellular network. 2941832 - 37 - - Step 9 (callback to the caller). In turn, the GMSC block [320] of the Italian Cellular Operator [300] sends a message of the type `ISUP IAM 'to the block MSC / VLR [310] of the same network. - Step 10 (calling back to the caller). The MSC / VLR [310] block of the Italian Cellular Operator [300] sends a message of the type 'CC Setup' to the recipient (i.e., the caller). The steps that describe the call-to-called procedure are functionally identical to the steps that describe callback procedures to the caller. Anyone skilled in the art will recognize that, by using call-back procedures via Internet-based signaling messages, interconnection costs will decrease and, ultimately, roaming costs will decrease for subscribers. Interconnection Services. Details on roaming costs will be provided in the section `INDUSTRIAL APPLICATIONS AND APPLICATION FIELDS '. A generalization of the described procedure corresponds to the case of a caller and / or a called party who change their telephone identifier (for example by changing the SIM card or even by changing cell phones in the case of a cellular technology different, such as cdmaOne). As an example, it will be assumed that the calling party is Spanish, that he has subscribed to his cellular subscription with `Telefonica 'and that he is traveling to Korea, where he rented a cell phone 20 operating according to the cdmaOne standard. In step 4 and following the caller registration procedures, SERVEUR AAA [500] recorded the following links: {MSISDNES, `ES '(country of origin), MSISDNKR,` KR' (visited country) }. Thanks to the information contained in SERVER AAA [500], and in particular the links between the temporary telephone identifier (MSISDNKR) and permanent (MSISDNES), it will be possible for the various INTERCONNECT SERVERS [200] (in particular those in Spain and Korea) to initiate recall procedures so that the called subscriber can still recognize the permanent identifier of his calling party (provided that the subscriber's Cellular Operator offers the identification service of the subscriber Once again, it is important to note that no INTERCONNECT SERVER [200] can, in general, substitute the calling party's permanent identifier for its temporary identifier, except in the case where the caller is a caller. employee and that the SERVER INTERCONNECT [200] is operated under the responsibility of his employer: this prohibition is legislations in terms of call traceability and is not due to technical reasons The same introductory context as in Figure 11 is used: the (French) user of the Interconnection Services has registered in Italy according to the procedure for sending the SMS from the country visited. recording. It sends an SMS to a French correspondent, also a user of interconnection services and having registered for these services in Germany (this case is general, and allows to easily deduce the case of one of the two users registered in France). Figure 16 shows a sequence of numbered steps that describe this procedure for sending SMS 5 - Step 1. The user (having a French identifier MSISDNFR-ExPEDITEUR) chooses the option `SMS 'in the MIDLET Menu [ 110] and selects the correspondent to whom he wishes to send the SMS from his address book. The user composes his SMS. - Step 2. MIDLET [110] starts a given connection (GPRS) by opening a `` PDP 10 context '' with the `` Gateway GPRS Support Node '' (GGSN) of the cellular operator of the visited network (in Italy) Step 3. MIDLET [110] is causing HTTPS message exchange `PUT 'with SERVER AAA [500]. The body of the HTTPS message contains the information about the sender's identifier and the SMS recipient's identifier; the body of the message 15 also contains the text of the SMS. Note: the (public) IP address of the SERVER AAA [500] is fixed in the MIDLET code [110]. Step 4 Following the registration procedures of the sender (in Italy) and the recipient (in Germany), SERVEUR AAA [500] has recorded the following links: For the sender: {MSISDNFR, `FR '(country of origin), `IT '(visited country)}. 20 For the recipient: {MSISDNFR, `FR '(country of origin),` AL' (visited country)}. Step 5. The two correspondents subscribe to the same French Cellular Operator. Therefore, SERVER AAA [500] is at the origin of a message exchange HTTP `PUT 'with the same INTERCONNECT SERVER [200] located in France (in particular, the message is received by the device B2BUA [240 The body of the http `PUT message contains the identifiers of the two correspondents and the text of the SMS message). Step 6. B2BUA [240] checks the registration status of both parties. Step 7. A message of the SIP INVITE type is sent by the B2BUA [240] to the PROXY SIP [210] (the two devices are part of the INTERCONNECTION SERVER 30 [200] in France). The PROXY SIP device [210], in turn, relays the SIP INVITE message to the PROXY SIP [210] which is part of the INTERCONNECT SERVER [200] in Germany. The recipient of this message is the receiving subscriber of the SMS. Note: the calling number (indicated by Identifier- [200] -France in Figure 16) is known by the MIDLET [110] of subscribers 35 to the Interconnection Services. Upon receipt of a call from this calling number, the MIDLET [110] must be able to recognize that this call corresponds to an alert message that indicates that an SMS is available to the recipient. 2941832 - 39 - Step 8 (callback to the caller). The PROXY SIP block [210] of the INTERCONNECT SERVER [200] in Germany sends an ISUP IAM message to the GMSC block [320] of the German Cellular Operator (this GMSC [320] is not represented for the sake of simplicity). The message 'ISUP IAM' and subsequently relayed to the MSC / VLR [310] of the same network (this MSC / VLR [310] is not shown for the sake of simplicity). Finally, the MSC / VLR [310] of the German cellular operator sends a message of the type 'CC Setup' to the recipient of the SMS. Step 9. The SMS sender's MIDLET [110] recognizes the caller's identifier (as described in Step 7) and, without picking up the call (i.e. 'call') starts the procedure for receiving the SMS. - Step 10. MIDLET [110] of the recipient starts a given connection (GPRS) by opening a `context PDP 'with the` Gateway GPRS Support Node' (GGSN) of the cellular operator of the visited network (in Germany). 15 - Step 11. SERVER AAA [500] is at the origin of an exchange of messages HTTPS `PUT 'with MIDLET [110] of the recipient. The body of the HTTPS message contains the information about the sender's identifier and the SMS recipient's identifier; the body of the message also contains the SMS text. Note: the (public) IP address of the SERVER AAA [500] is fixed in the recipient's MIDLET code [110]. Step 12. MIDLET [110] of the recipient decodes the SMS received, so as to split the real text of the SMS that will be presented to the user, as well as the identity of the sender correspondent. According to the description of Steps 7 and 9 of Figure 16, MIDLET [110] must know the identification of the calling number (i.e., the number allocated in the INTERCONNECT SERVER [200] in France, the origin of subscribers) and must also be able to recognize the identity of the caller through Calling Line Identifier (CLI) procedures; indeed, it is following this recognition of the caller that MIDLET [110] avoids picking up the call and decides to start the procedure for receiving the SMS (Steps 10, 11, 12 of Figure 16). The `CLI 'features are provided by the visited country Operator. The Interconnection Operator must therefore know if these functionalities are available in each country where the Interconnection Services are available (ie in each country where an INTERCONNECT SERVER [200] has been deployed). If these `CLI 'features are not available, in Step 3 of Figure 16 SERVER AAA [500] will instruct 35 sender [110] of the sender to start a normal procedure for sending SMS. Eventually, the sender will be informed of this situation and may decide not to send the SMS. Anyone skilled in the art will recognize that, by using the SMS sending / receiving procedures described in Figure 16, the interconnection costs will drop and, ultimately, the roaming costs will decrease for subscribers to the Interconnection Services. Details on roaming costs for SMS applications will be given in the section 'INDUSTRIAL APPLICATIONS AND APPLICATION FIELDS' In the case of an Interconnection Services subscriber who wants to send an SMS to a correspondent who does not is not subscribed to these services, the normal procedure will be followed; indeed, in Step 4 of Figure 16, SERVER AAA [500] will recognize that the recipient is not subscribed to the Interconnection Services and, therefore, instruct MIDLET [110] of the sender to start a normal procedure for sending SMS. In the case of a sender and / or a recipient who change phone ID (eg changing SIM card or even changing cell phone in the case of a different cellular technology, such as cdmaOne ), the generalization of the procedure of Figure 11 applies: indeed, in a preferred embodiment of this generalization, the SMS RELAY [270] will consist of one or more mobile phones, equipped with corresponding SIM cards; functionally, these mobile phones will interconnect with the MOBILE OPERATOR NETWORK [300] (especially the Short Message Service Center - SMSC [350] local). In this case, steps lA to 9A of the SMS sending procedure can be adopted even in the business model considered in this variant embodiment.

25 CLASS 3: VARIANTS IN RELATION TO THE EVOLUTIONS OF COMMUNICATIONS NETWORKS AND INFRASTRUCTURE. Today in the world, several strategies for the evolution of wireless cellular networks are under study and / or are beginning to be deployed. Among these solutions, a special effort on the part of cellular operators is dedicated to setting up the IP Multimedia Subsystem (IMS), which makes it possible to provide fixed and mobile multimedia services to subscribers. An intermediate step towards this type of evolution is the so-called CAMEL (Customized Applications Mobile Network Enhanced Logic) service support platform. CAMEL is the reference service architecture for mobile operators. The standardization work initiated by the European Telecommunication Standard Institute (ETSI) and then continued by the 3GPP, consisted in adapting to the mobile context the concept of intelligent network developed by the International Telecommunications Union (ITU). A multitude of services can be supported by a CAMEL platform. For example, with the support of a service like the "prepaid card", CAMEL has contributed significantly to the success of GSM. The deployment of CAMEL by the majority of mobile operators attests to its stability and maturity The procedures described in the invention lend themselves to development and deployment compatible with CAMEL; in this context, the architecture, protocols and procedures must be adapted to use the methods, primitives and interconnections described in the CAMEL standard. Nevertheless, the basic principles of the invention remain similar. Figure 17 shows a principle architecture of a cellular system that supports CAMEL and also a possible way of grafting the system according to the invention. To simplify the description, the architecture instead refers to CAMEL's 'Phase 1'. Any expert in the art subsequently recognizes that the principles of the description can be applied to CAMEL's 'Phase 2' as well. It should also be noted that only a subset of the functional blocks of the cellular network [300] is shown in FIG. 17 so as not to unnecessarily complicate the rest of the description. The main features of CAMEL are well known by the art experts. Nevertheless it is useful to make some reminder, in connection with the representation of Figure 17: - gsmSCF [710] (SCF stands for `Service Control Function ') is the entity where the CAMEL services reside. gsmSCF [710] is controlled by the originating Cell Operator. The node in which gsmSCF resides is called Service Control Point (SCP [700]). SCP [700] supports the following protocols: o MAP (Mobile Application Part), standardized by the 3GPP organization, shown with a solid line in Figure 17, and which allows interfacing between SCP [700] and HLR [330] . o CAP (CAMEL Application Part), standardized by the 3GPP organization, represented with a continuous line in Figure 17, and which allows interfacing between SCP [700] and gsmSSF [720]. o One or more IP-based protocol (s) for communicating with the INTERCONNECT SERVER [200] in the country of the original Cellular Operator. This type of protocol is not standardized. It will therefore be based on a proprietary implementation. It is interesting to note that the INTERCONNECT SERVER [200] can be controlled by an 'Interconnection Operator', while the original Cellular Operator 35 controls the SCP [700]. Access and interfacing agreements must be established between the two Operators. Alternatively, the INTERCONNECTION SERVER [200] can be controlled by the Cellular Operator (although the development and deployment of such an INTERCONNECT SERVER 2941832 - 42 - [200] can be outsourced to subcontractors) In all cases, according to the model of Figure 17, the interface between the cellular network [300] (including the CAMEL functionalities) and the INTERCONNECTION SERVER network [200] can be implemented flexibly and efficiently. . 5 gsmSSF [720] (SSF stands for `Service Switching Function ') is a' functional entity that resides in the GMSC [320] (in the original Cell Operator network) and in the VLR / MSC [310] ( in the network of the original Cellular Operator or visited). The GSMC [320] (VLR / MSC [310]) which hosts the gsmSSF [720] supports the following protocols: 10 o MAP (Mobile Application Part), standardized by the 3GPP organization, represented with a continuous line in FIG. 17, and which allows interfacing between GSMC [320] (VLR / MSC [310]) and HLR [330]. o CAP (CAMEL Application Part), standardized by the 3GPP organization, shown with a solid line in Figure 17, and which allows the interfacing between SCP [700] and GSMC [320] (VLR / MSC [310]). INTERCONNECTION SERVERS [200] and SERVER AAA [500] which are operatively linked by IP-based protocols (shown with a solid line in Figure 17). In addition, INTERCONNECTION SERVERS [200] are operatively connected to the Cell Operator networks through the MGW block [340], as already explained. In the remainder of the description, the adaptation of the procedures of the invention to the CAMEL platform will be explained.

Registration Procedure - Visited Country 25 Functionally, there are no changes from Figure 6 and its Steps. However, it is necessary for the HLR [330] to be aware that its subscribers may be users of the Interconnection Services. As such, a specific field can be introduced into the CAMEL profile of the subscriber. It is interesting to note that there is no need to standardize the syntax of this field because it is related to the use of the IP protocol between the SCP [700] and the INTERCONNECTION SERVER [200], this protocol being entirely proprietary. Outgoing Call Procedure: Recall by USSD The call procedure described in Figure 7 will be referred to as this procedure uses the `USSD 'signaling, this type of signaling being supported in CAMEL 35` Phase 2'. In order for the callback procedure to be handled correctly by the CAMEL platform, it is necessary to define an identifier of this callback service in the database of the HLR [330]: in particular, the element called `UG-CSI ' (USSD Generic CAMEL Subscription Information) must contain the code of the USSD service 2941832 - 43 - callback (code `* XYZ * 'in Figure 7) and the logical address of the gsmSCF [710] which will process the message USSD once he will be received. The same introductory context as in Figure 7 is used: the (French) user of the Interconnection Services registered in Italy according to the registration procedure. He makes a call to a French correspondent, also a user of the Interconnection Services and having registered for these services in France. Figure 18 shows a series of numbered steps that describe this procedure from Italy to France using USSD messages and the CAMEL platform for interpreting and processing these messages: Step 1. The user chooses the option `Call 'in the MIDLET Menu [110] and 10 selects the party to call from his address book. - Step 2. MIDLET [110] makes a call according to the USSD syntax: * XYZ * MSISDNFR-APPELE where MSISDNFR-APPELE is the telephone identifier of the correspondent to be called and * XYZ * is the USSD service code defined in the `UG - CSI '. The request from the USSD service is relayed from the HLR [330] to the gsmSCF [710] contained in the SCP [700]. Step 3 The gsmSCF [710] contained in the SCP [700] is at the origin of an exchange of HTTP messages "PUT" with B2BUA [240] (contained in the INTERCONNECT SERVER [200] in France) . The body of the HTTP message contains the telephone identifier of the caller and that of the correspondent to be called. The purpose of step 3 is to allow callback procedures to start depending on the geographical location of the caller and called party. The exchange of such messages is done through the IP interface (proprietary) between the SCP [700] and the INTERCONNECT SERVER [200]. - Step 4. B2BUA [240] checks the registration status of both parties. Step 5. A message of type A SIP INVITE is sent by B2BUA [240] to PROXY SIP [210]. The recipient of this message is the calling subscriber Step 6 (Caller Callback). As a result of the received SIP INVITE message, the PROXY SIP block [210] alerts the SS7 INTERCONNECTION gateway block [220] to send a message of type 'ISDN USER INITIAL ADDRESS 30 MESSAGE' (IAM) to the block GMSC [320]. ] of the French Cellular Operator [300]. Note: the devices [340] (which serves as a protocol intermediary between [220] and [320]) and the block [220] are not shown for simplicity; however, their features are necessary, as any art expert will recognize. - Step 7 (calling back to the caller). An Initial Detection Point (IDP) message is sent by the gsmSSF [720] (contained in the GMSC [320]) to the gsmSCF [710] (contained in the SCP [700]) to obtain instructions on how to process the IAM message received in Step 6. The exchange of messages between the gsmSSF [720] and the gsmSCF [710] is done through the CAP protocol. 2941832 - 44 - Step 8 (callback to the caller). A `Connect 'type message (CON) is sent by the gsmSCF [710] (contained in the SCP [700]) to the gsmSSF [720] (contained in the GMSC [320]) to allow the CAMEL callback service to modify certain parameters in the recall procedure. According to the spirit of the invention, and as an example of implementation it will be possible to use the `Redirecting Party ID 'parameter to redirect the call to the PROXY SIP [210] (from the SERVER OF INTERCONNECTION [200] in Italy). Indeed, this redirection can be carried out on behalf of the PROXY SIP block [210] (of the INTERCONNECTION SERVER [200] in France), because it is indeed this block that becomes 10 'calling' in the recall procedure. Step 9 (calling back to the caller). The device GMSC [320] (in the French cellular network) interrogates the HLR [330] (in the French cellular network) in order to obtain the mobile station roaming number (MSRN) of the caller (which becomes 'called' in the recall procedure). In general, this identifier enables the GMSC [320] to route the call into the Italian cellular network. - Step 10 (calling back to the caller). The HLR [330] refers to the GMSC [320] the MSRN; this message allows the GMSC [320] to know the geographical location of the subscriber, as a user of the interconnection services. Note: the message exchange between HLR [330] (French network) and MSCNLR [310] (Italian network) in order to obtain the MSRN is not shown, for reasons of simplicity. - Step 11 (call back to the caller). After consulting the routing tables, the GSMC [320] sends an 'ISUP IAM' type message to the SS7 INTERCONNECTION GATEWAY INTERCONNECTION [220] block of the INTERCONNECTION SERVER [200] in Italy, to alert the PROXY SIP block [210]. ] to send call setup messages to the Italian cellular network. Note: the devices [340] (which serves as a protocol intermediary between [220] and [320]) and the block [220] are not shown for simplicity; however, their functionalities are necessary, as any expert in the art will recognize The rest of the procedure is functionally identical to the procedure of Figure 7. 30 SMS sending procedure, from the visited country Compared to the procedure of the Figure 11, there is not much interest in introducing SMS management mechanisms with a CAMEL platform. In fact, the CAMEL procedures for SMS can make it possible to intelligently manage the routing of the SMS and to be able to choose, optionally, an SMSC [350] dynamically. Figure 11 already shows this behavior, without the need to use CAMEL. In addition, it is from CAMEL's 'Phase 3' that SMS management is present. Most mobile operators use CAMEL `Phase 2 '(or even CAMEL` Phase 1'). 2941832 - 45 - INDUSTRIAL APPLICATIONS AND FIELDS OF APPLICATION Any cellular and IP system and infrastructure is compatible with the process, devices and operational steps described. Indeed, the embodiment of the invention mainly involves the implementation of hardware and software necessary for communication between the devices and sub-devices of the different Figures. The principles of the invention can be advantageously applied by the following economic actors: Conventional cellular operators (such as Vodafone, Orange, etc.) can exploit the invention in order to considerably reduce international interconnection charges. In addition, Cellular Operators who adopt incompatible technologies (for example, Orange with GSM / GPRS / UMTS and Korea Telecom with cdmaOne) can benefit from a simple solution to ensure compatibility in the provision of services, such as voice and SMS. In addition, a Cellular Operator who does not have roaming agreements with the Cellular Operator of a foreign country, may adopt the interconnection solution presented in order to implement roaming agreements without having to resort to intermediation of third party operators. Mobile Virtual Network Operators (MVNOs) can exploit the invention in order to increase the coverage of their services without having to resort to the intermediation of third party operators. for example, IIJ - Internet Initiative Japan, NTT Communications, AIH - Asia Internet Holding, TI-Sparkle), 25 which can offer the solution object of the invention as a new interconnection service for mobile operators, this offer making it possible to reduce the interconnection costs between them. Companies with channels in foreign countries: they can adopt the solution to have a roaming service at very low cost, to allow a sharp reduction in communication costs (telephone, SMS, data) for employees Traveling It is also useful to give an example of reducing roaming costs for end users (such as individuals traveling for business or leisure). Indeed, a reduction in interconnection costs may result in a decrease in the international call charges for users. The following example illustrates the cost reduction that can be achieved: Basis of comparison: a call of 4 minutes duration across Europe, with the caller roaming and prepaid subscription ù (figures shown) come from an official source of the Information Society of the European Community Cost of the call according to the existing procedures: 2.2 {5 Cost of the call according to the procedures of the invention (in particular the recall procedure of Figure 15): 1.041 {(The average cost of a roaming Internet connection is 0.95 {per block of 64 kilobytes .. The signaling required for the implementation of the call is 200 octets)

Preferably, the invention relates to the following objects: 1) A system for interconnection between mobile communications networks characterized by an architecture that comprises: An interconnecting server device network [200], which devices are hosted in different country, each interconnect server [200] allowing the interconnection between one or more cellular networks controlled by operators of the country that hosts such interconnect server [200] and the public Internet network, each interconnect server [200]. ] also allowing an interconnection with any other interconnect server [200] hosted in another country. A set of mobile terminal devices [100], each hosting application software [110] to enable said mobile terminal [100] to communicate with a specific interconnect server [200], this interconnect server [200] being hosted in the country where the mobile terminal user [100] is located, the choice of the interconnect server [200] to communicate with the mobile terminal [100] is determined by an AAA server device [500], which authenticates each user whose mobile terminal [100] hosts the application software [110], this authentication being performed at the launch of the application software [110].

2) Device [200] according to object 1), comprising: A device [210] acting as an entry point for the device [200] to the public internet network. A device [220] which comprises the functionalities necessary for any exchange of the signaling data with the cellular network on one side and with the internet network on the other side and to which the identifier of the device [200] refers. A device [230] that includes the functionality necessary for any exchange of media data with the cellular network on one side and with the internet network on the other side and to which the device identifier [240] refers. A device [240] that allows the creation of media streams necessary for any communication between two devices [200], this device [240] being in communication with AAA server [500] to associate any communication between two devices [200] with any user whose mobile terminal [100] hosts the application software [110] and whose mobile terminal [100] is in connection with an interconnecting server device [200]. A device [250] which acts as a database for storing the information of any user whose mobile terminal [100] hosts the application software [110], the interconnect server [200] communicating with said mobile terminal [100], The association between such interconnect server [200] and said mobile terminal [100] being managed by AAA server [500] at the act of authentication of the user of such mobile terminal [100]. A device [260] which, following the AAA server managed authentication procedures [500], retains the state of the user registration of the mobile terminal device [100], this state of the registration being communicated to the device [250]

3) System according to objects 1) and 2) and which guarantees the association between a mobile terminal device [100] and an interconnect server device [200] according to the following operations: A signaling exchange between mobile terminal [100] ] and AAA server [500] this exchange being started by the application software [110] hosted in mobile terminal [100], this signaling exchange being transported by the given transport protocol of the underlying cellular network and to transmit to the server AAA 25 [500] geographical information describing the country in which the mobile terminal user [100] is located. A signaling exchange between the mobile terminal [100] and the AAA server [500], this exchange making it possible to verify the identity of the mobile terminal user [100], the verification of the identity being done by means of secure protocols exchanged between the application software [110] hosted in mobile terminal [100] and the server AAA [500]. A signaling exchange between the mobile terminal [100] and AAA server [500] this exchange being started by the AAA server [500] and making it possible to communicate to the application software [110] hosted in the mobile terminal [100] the identifiers of the server. interconnection [200] with which the mobile terminal device [100] can communicate, which identifiers may consist of one or more telephone numbers and one or more Internet identifiers. 4) System according to the objects 1), 2) and 3) and which uses voice callback procedures between two correspondents whose respective mobile terminals [100] have been associated with interconnection servers [200], such interconnect server [200] can be hosted in different countries, depending on the geographical location of the 5 correspondents, voice callback procedures operating according to the following operations: - a signaling exchange between mobile terminal [100] and AAA server [ 500] this exchange being started by the application software [110] hosted in mobile terminal [100], this signaling exchange being transported by the so-called USSD transport protocol of the underlying cellular network and making it possible to transmit to the AAA server [500] ] the call information as well as the identifiers of the calling party and the called party. A signaling exchange between AAA server [500] and interconnect server [200] this exchange being started by AAA server [500] and directed to the interconnect server [200] hosted in the country in which the cellular network is located. The origin of each correspondent resides, this signaling exchange allowing the interconnection server [200] of the calling party's country of origin to start callback procedures to such a calling party, this signaling exchange also allowing the interconnection server [200] of the called party's home country 20 to initiate call procedures to such called party. A call message sent by the interconnecting server [200] from the calling party's home country to the originating cellular network gateway of the calling party, this message being used to trigger a cell network interrogation procedure. in which the calling party is in order to obtain the roaming number of the calling party, the roaming number being subsequently sent by the interconnection server [200] from the calling party's home country to the server interconnection [200] associated with the calling end device [100] of the caller, following the association procedures 30 described in object 3). A call message sent by the interconnection server [200] associated with the calling end device [100] of the caller, this message being used to trigger a local callback procedure of the interconnection server [200] associated with the terminal device mobile [100] of the caller and such mobile terminal [100], which is identified by its roaming number. A call message sent by the interconnection server [200] from the called party's home country to the gateway of the called party's originating cellular network, this message making it possible to trigger a polling procedure 2941832 -49- of the cellular network in which the called party is in order to obtain the roaming number of the called party, the roaming number being subsequently sent by the interconnection server [200] of the called party's country of origin. to the interconnection server [200] associated with the called mobile terminal device [100], following the association procedures described in object 3). A call message sent by the interconnection server [200] associated with the called mobile terminal device [100], this message making it possible to trigger a local call procedure of the interconnection server [200] associated with the device Mobile terminal [100] of the called party and such mobile terminal [100], which is identified by its roaming number

5) A system according to the object 4) and in which the interconnection server devices [200] are identified by dummy code points according to the protocols and conventions of the interconnection network SS7, these dummy code points making it possible to consider the interconnection server devices [200] as part of an SS7 network, even though such interconnect servers [200] communicate physically through internet-based protocols and can be controlled and operated by third-party operators. 6) System according to objects 1) to 4) and which uses SMS sending procedures between two correspondents whose respective mobile terminals [100] have been associated with interconnection server [200], such server of interconnection [200] which may be hosted in different countries, depending on the geographical location of the correspondents, the SMS sending procedures operating according to the following operations: A signaling exchange between mobile terminal [100] and AAA server [500] this exchange being started by the application software [110] hosted in the mobile terminal [100] of the sending correspondent, this signaling exchange being transported by an internet transport protocol, such as http or https, using the given connections of the cellular network underlying and for transmitting to the AAA server [500] a request to send SMS and the identifiers of the sending correspondent and the correspondent destiny the AAA server device [500] responding to this request by sending to the application software [110] the identifier 35 of an SMS relay device [311] such SMS relay [311] constituting a functional component of the cellular network. an operator of the country in which the sending correspondent is located, this SMS relay [311] being controlled by the originating operator of the sending correspondent.

- 50 - An SMS sending procedure triggered by the application software [110] hosted in the mobile terminal [100] of the sending correspondent, this procedure making it possible to send an SMS message from the mobile terminal [100] to the device SMS relay [311] associated with the cellular network of an operator of the country in which the sending correspondent is located, the content of the sent SMS being composed of the identifier of the receiving party and the text of the SMS message. An SMS redirection procedure, triggered by the SMS relay device [311], this procedure for sending the identifier of the recipient correspondent and the text of the SMS message to the interconnection server [200] associated with the mobile terminal device [100] of the sending correspondent, the identifier of the recipient correspondent and the text of the SMS message being relayed by the interconnection server [200] associated with the mobile terminal device [100] of the sending correspondent to the interconnection server [200] associated with the mobile terminal device [100] of the receiving party. An SMS redirection procedure triggered by the interconnection server device [200] associated with the mobile terminal device [100] of the destination recipient to SMS relay [311] associated with the cellular network of an operator of the country in which the corresponding sender is found, this procedure to send the identifier of the sender correspondent and the text of the SMS message to such SMS relay [311], so that it can redial an SMS that must contain the entire identifier sending correspondent and the text of the message. A routing information request sent by the cellular network of an operator of the country in which the recipient correspondent is located and whose associated SMS relay [311] constitutes a functional component, this SMS relay [311] being controlled by the originating operator of the recipient correspondent, this routing information request making it possible to obtain the identifier of the equipment of the cellular network which controls the mobile terminal device [100] of the recipient recipient, so that it can enable the sending the SMS from the SMS relay [311] to the recipient's mobile terminal [100].

Receipt of said SMS by the application software [110] hosted in the recipient's mobile terminal [100] in order to split the identifier of the sending correspondent and the text of the message for the final presentation to the recipient correspondent. 7) System according to the objects 1), 3), 4, 6) and using procedures that allow communications from subscribers to cellular operators whose mobile terminal device [100] does not host the application software [ 110] to users of such application software [110] installed on their mobile terminals [100], its procedures operating according to the following operations: A preliminary call deflection procedure initiated by the application software device [110] so that users of such application software [110] installed on their mobile terminals [100] can divert received calls to numbers uniquely allocated to each user, this call forwarding procedure being enabled if such users are not not be reachable, the call diversion numbers can also be allocated dynamically, according to an exchange of messages between the application software [110] and AAA server [500], such AAA server [500] informing the application software [110] of a call diversion number available at the initiation of the call deflection procedure from the application software [110] . An invocation procedure by subscribers to cellular operators without intervention of the device [110] to call users of such application software [110] installed on their mobile terminals [100], this procedure being processed by the device [320] which, following a message exchange with the device [330] is aware of the call diversion number reserved for the users of the application software [110], the device [320] being able to send the call to such call diversion number, this call diversion number being recorded on the interconnection server [200] of the called party's country of origin, the interconnection server [200] thus being able to receive the call from the called party. name of the receiving party. A call message sent by the interconnection server [200] from the called party's home country to the gateway of the cellular network where the called party is located. A method that allows the device [330] to send to the device [320] is the roaming number of the called users, such users having the application software [110] installed on their mobile terminals [100], in the case that the corresponding callers are also users of the application software [110], 30 is the call diversion number of called users, such users having the application software [110] installed on their mobile terminals [100], in the case that the calling parties are not users of the application software [110], the choice of the roaming number or the call diversion number being made by the device [330] on the basis of indications sent by the device [320] ], these indications using one or more optional parameters which are available in the protocol syntax of interconnection between the device [330] and the device [320], these indications allowing the device [ 330] to understand whether the calling parties are users of the application software [110]. 2941832 - 52 - 8) System according to the objects 1), 3), 4), 6), 7) and which allows a subscribers to a cellular operator whose mobile terminal device [100] hosts the application software [110] of temporarily change the telephone identifier while being able to benefit from the application software [110] in another possible mobile terminal [100], thus retaining the possibility of being reached by means of voice calls or SMS sends, these calls or SMS being transmitted to the identifier provided by the cellular operator with which the user of the application software [110] has subscribed the subscription, the methods for obtaining such an attack being based on the following operations: A signaling exchange call between mobile terminal [100] and AAA server [500] this exchange being started by the application software [110] hosted in mobile terminal [100], this signaling exchange being transported by the http or htt transport protocol ps and allowing the call information and the identifiers of the calling party and the called party to be transmitted to the AAA server [500], this signaling exchange being relayed by AAA server [500] to the interconnection server [200]. ] hosted in the country in which the originating cellular network of each correspondent resides, this signaling exchange allowing the interconnecting server [200] of the calling party's home country to start callback procedures to such calling party , this signaling exchange also allowing the interconnection server [200] of the called party's home country to start call procedures to such called party. An SMS signaling exchange between mobile terminal [100] and AAA server [500] this exchange being started by the application software [110] hosted in mobile terminal [100], this signaling exchange being transported by the so-called transport protocol. http or https and for transmitting to the AAA server [500] the SMS information and the identifiers of the sending correspondent and the recipient correspondent, this signaling exchange being relayed by AAA server [500] to the interconnection server [200]. ] hosted in the country in which the recipient's originating cellular network resides, this signaling exchange allowing the interconnection server [200] of the recipient party's home country to initiate call procedures to such correspondent recipient, these call procedures being interpreted as SMS alert messages by the application software [110] hosted in mobile terminal [10]. 0] of the recipient correspondent, these alert messages enabling said application software [100] to start a signaling exchange with AAA server [500], such signaling exchange allowing the application software [110] to receive the SMS sent by The sender, the contents of this SMS as well as the identifiers of the sending correspondent and the recipient correspondent being stored by AAA server [500].

9) System according to the objects 1), 2), 3), 4), 5), 6), 7), according to which the infrastructure 5 of a cellular operator hosts a CAMEL platform, such platform that can communicate with the server interconnection [200] hosted in the country in which the cellular network of said operator resides, the communication between the device [700] of the CAMEL platform and such interconnection server [200] being based on Internet protocols, such protocols allowing an exchange of messages between said CAMEL platform and the interconnection server [200] so that the requests sent to the device [700] of the CAMEL platform from the device [720] of the CAMEL platform enable the device [710] from the CAMEL platform to relay these requests to the interconnect server [200] which, in turn, can send responses to the CAMEL device [710] so that it can give appropriate instructions to the device [720] the CA platform MEL, the aforementioned message exchange being able to allow an 'implementation of the call procedures according to the object 4), these procedures being based on the following operations: A signaling exchange between the mobile terminal [100] and the device [710] this exchange being started by the application software [110] hosted in mobile terminal 20 [100], this signaling exchange being transported by the so-called USSD transport protocol, this signaling exchange being relayed by the device [330] of the cellular network under -Jacent and to transmit to the device [710] the call information and the identifiers of the calling party and the called party.

A signaling exchange between device [710] and interconnect server [200] that is initiated by device [710] and sent to the interconnect server [200] hosted in the country in which the originating cellular network of each correspondent resides, this signaling exchange allowing the interconnection server [200] of the calling party's home country to start callback procedures to such a calling party, this signaling exchange also allowing the interconnection server [ 200] of the called party's home country to initiate call procedures to said called party. A call message sent by the interconnection server [200] from the calling party's home country to the gateway of the originating cellular network of the calling party, this message making it possible to trigger a polling procedure on the part from the device [320] to the device [710] through the device [720] to obtain the device identifier [310]. of the cellular network 2941832 - 54 - in which the calling party is located in order to obtain the roaming number or the calling party, the roaming number subsequently being sent by the interconnection server [200] of the home country. origin of the calling party to the interconnection server [200] associated with the calling end device [100] of the caller, following the association procedures described in object 3). A call message sent by the originating cellular network device [320] of the calling party to the device [330] to obtain the roaming number of the calling party A call message sent by the device [320] ] of the calling party's originating cellular network to the interconnection server [200] associated with the calling end device [100] of the caller following the association procedures described in the object 3), this message permitting triggering a local callback procedure of the interconnect server [200] associated with the calling end device [100] of the caller and such mobile terminal [100], which is identified by its roaming number. 15

Claims (9)

CLAIMS1) A system for interconnection between mobile communications networks characterized by an architecture that comprises: A network of interconnecting server devices [200], these devices being hosted in different countries, each interconnect server [200] enabling interconnection between one or more cellular networks controlled by operators of the country hosting said interconnection server [200] and the public Internet network, each interconnection server [200] also allowing interconnection with any other interconnection server [ 200] hosted in another country. - A set of mobile terminal devices [100], each hosting application software [110] to enable said mobile terminal [100] to communicate with a specific interconnect server [200], which interconnect server [200] is hosted in the country where the mobile terminal user [100] is located, the choice of the interconnect server [200] to communicate with the mobile terminal [100] being determined by an AAA server device [500], which allows authenticate each user whose mobile terminal [100] hosts the application software [110], this authentication being performed at the launch of the application software [110]. 2) System according to claim 1) characterized in that the device [200] comprises: A device [210] acting as an entry point for the device [200] vis-à-vis the public internet network. A device [220] which comprises the functionalities necessary for any exchange of the signaling data with the cellular network on one side and with the internet network on the other side and to which the identifier of the device [200] refers. A device [230] which comprises the functionalities necessary for any exchange of the media data with the cellular network on one side and with the internet on the other side and to which the identifier of a device [240] refers . A device [240] that allows the creation of the media streams necessary for any communication between two devices [200], the device [240] being in communication with the AAA server [500] to associate any communication between two devices [200]. ] with any user whose mobile terminal [100] hosts the application software [110] and whose mobile terminal [100] is in connection with an interconnection server device [200]. A device [250] which acts as a database for storing the information of any user whose mobile terminal [100] hosts the application software [110], the interconnection server [200] communicating with said mobile terminal [100], the association between the interconnect server [200] and the mobile terminal [100] being managed by a server AAA [500] at the act of authentication of the user of the mobile terminal [100] . A device [260] which, following the authentication procedures managed by the AAA server [500] makes it possible to keep the state of the user's record of the mobile terminal device [100], this state of the registration being communicated to the device [250] 10 3) System according to claims 1) and 2) characterized in that it works by ensuring the association between a mobile terminal device [100] and an interconnection server device [200] according to the following operations: A signaling exchange between the mobile terminal [100] and the AAA server [500] this exchange being started by the application software [110] hosted in the mobile terminal [100], this signaling exchange being carried by the transport protocol data of the cellular network underlying and for transmitting to the AAA server [500] the geographical information describing the country in which the user of the mobile terminal [100] is located. A signaling exchange between the mobile terminal [100] and the AAA server [500] 20 this exchange to verify the identity of the user of the mobile terminal [100], the verification of the identity being done through secure protocols exchanged between the application software [110] hosted in the mobile terminal [100] and the AAA server [500]. A signaling exchange between the mobile terminal [100] and the AAA server [500] 25 this exchange being started by the AAA server [500] and for communicating to the application software [110] hosted in the mobile terminal [100] the identifiers the interconnect server [200] with which the mobile terminal device [100] can communicate, which identifiers may consist of one or more telephone numbers and one or more Internet identifiers. 30 4) System according to claims 1), 2) and 3) characterized in that it operates using voice callback procedures between two parties whose respective mobile terminals [100] have been associated with interconnection server [200]. ], said interconnection server [200] being able to be hosted in different countries, depending on the geographical location of the correspondents, the voice recall procedures operating according to the following operations: A signaling exchange between the mobile terminal [100] and the AAA server [500] this exchange being started by the application software [110] hosted in the mobile terminal [100], this signaling exchange being transported by the so-called USSD transport protocol of the underlying cellular network and allowing transmitting the call information and the identifiers of the calling party and the called party to the AAA server [500]. A signaling exchange between the AAA server [500] and the interconnect server [200], which exchange is started by the AAA server [500] and directed to the interconnect server [200] hosted in the country in which the The original cellular network of each correspondent resides, this signaling exchange enabling the interconnection server [200] of the calling party's home country to start callback procedures to the calling party, this signaling exchange also allowing the interconnect server [200] of the called party's home country to initiate call procedures to the called party. A call message sent by the interconnection server [200] from the calling party's country of origin to the gateway of the originating cellular network of the calling party, this message being used to trigger a cell network interrogation procedure in which the calling party is in order to obtain the roaming number of the calling party, the roaming number being subsequently sent by the interconnecting server [200] of the calling party's home country to the interconnection server [200] associated with the calling end device [100] of the caller, following the association procedures described in claim 3). A call message sent by the interconnect server [200] associated with the calling end device [100] of the caller, this message being used to trigger a local callback procedure of the interconnection server [200] associated with the device mobile terminal [100] from the caller to the mobile terminal [100], which is identified by its roaming number. A call message sent by the interconnection server [200] from the called party's home country to the gateway of the called party's home cellular network, this message being used to trigger a cell network interrogation procedure in which the called party is in order to obtain the roaming number of the called party, the roaming number being subsequently sent by the interconnection server [200] of the country of origin of the called party to the server interconnection [200] associated with the called mobile end device [100], following the association procedures described in claim 3). A call message sent by the interconnect server [200] associated with the called mobile end device [100], this message for initiating a local call procedure of the interconnect server [200] associated with the mobile terminal device [100] of the called party to the mobile terminal [100], which is identified by its roaming number 5) System according to claim 4) characterized in that the interconnect server devices [200] are identified by dummy code points according to the protocols and conventions of the interconnection network SS7, these dummy code points making it possible to consider the devices interconnection server [200] as part of an SS7 network, even though said interconnect server [200] physically communicates through internet-based protocols and can be controlled and operated by third-party operators. 6) System according to claims 1) to 4) characterized in that it operates using SMS sending procedures between two parties whose respective mobile terminals [100] have been associated with interconnection server [200] , the interconnection server [200] being able to be hosted in different countries, depending on the geographical location of the correspondents, the SMS sending procedures operating according to the following operations: A signaling exchange between the mobile terminal [100] and the AAA server [500] this exchange being started by the application software [110] hosted in the mobile terminal [100] of the sending correspondent, this signaling exchange being transported by an Internet transport protocol, such as http or https, using the data connections of the underlying cellular network and making it possible to transmit to the server AAA [500] a request for sending SMS as well as the identifiers of the correspo sender and recipient recipient, the AAA server device [500] responding to this request by sending the application software [110] the identifier of an SMS relay device [311], the SMS relay [311] constituting a component functional cellular network of an operator of the country in which the sending correspondent is located, this SMS relay [311] being controlled by the originating operator of the sender correspondent. An SMS sending procedure, triggered by the application software [110] hosted in the mobile terminal [100] of the sending correspondent, this procedure for sending an SMS from the mobile terminal [100] to the relay device of SMS [311] associated with the cellular network of an operator of the country in which the sending correspondent is located, the content of the sent SMS being composed of the identifier of the receiving party and the text of the SMS message. An SMS redirection procedure triggered by the SMS relay device [311], this procedure making it possible to send the identifier of the recipient correspondent and the text of the SMS message to the associated interconnection server [200]; to the mobile terminating device [100] of the sending correspondent, the identifier of the recipient correspondent and the text of the SMS message being relayed by the interconnection server [200] associated with the mobile terminal device [100] of the sending correspondent to the server of interconnection [200] associated with the mobile terminal device [100] of the receiving party. An SMS redirection procedure triggered by the interconnection server device [200] associated with the recipient's mobile terminal device [100] to the SMS relay [311] associated with the cellular network of an operator of the country in which the sender correspondent is, this procedure for sending the identifier of the sending correspondent and the text of the SMS message to said SMS relay [311], so that it can recompose an SMS which must contain all of the identifier of the sender correspondent and the text of the message. A routing information request sent by the cellular network of an operator of the country in which the recipient correspondent is located and whose associated SMS relay [311] constitutes a functional component, this SMS relay [311] being controlled by the originating operator of the recipient correspondent, this routing information request making it possible to obtain the identifier of the equipment of the cellular network which controls the mobile terminal device [100] of the recipient correspondent, in order to enable the sending the SMS from the SMS relay [311] to the recipient's mobile terminal [100]. The receipt of said SMS by the application software [110] hosted in the mobile terminal [100] of the recipient recipient in order to split the identifier of the sender correspondent and the text of the message for the final presentation to the recipient correspondent. 7) System according to claims 1), 3), 4, 6) characterized in that it operates using procedures that allow communications from subscribers to cellular operators whose mobile terminal device [100] n ' does not host the application software [110] to users of the application software [110] installed on their mobile terminals [100], its procedures operating according to the following operations: A preliminary call deflection procedure triggered by the application software [110] so that users of the application software [110] installed on their mobile terminals [100] can divert the received calls to numbers uniquely allocated to each user, this call deflection procedure being activated if said users result not to be the call diversion numbers 2941832 - 60 - can also be allocated dynamically, according to an exchange of messages between the application software [110] and the AAA server [500], the AAA server [500] informing the application software [110] of a call diversion number available at the initiation of the call deflection procedure by the application software 5 [110]. An invocation procedure by subscribers to cellular operators without intervention of the device [110] to call users of the application software [110] installed on their mobile terminals [100], this procedure being processed by a device [ 320] which, following a message exchange with a device [330] is aware of the call diversion number reserved for the users of the application software [110], the device [320] being able to send the call to said number call forwarding number, this call diversion number being registered on the interconnection server [200] of the called party's country of origin, the interconnection server [200] thus being able to receive the call on behalf of the called party. corresponding 15 recipient. A call message sent by the interconnection server [200] from the country of origin of the called party to the gateway of the cellular network where the called party is located. A method which peHnet device [330] to send to the device [320] is the roaming number of called users, these users having the application software [110] installed on their mobile terminals [100], in the case that the calling parties are also users of the application software [110], ie the call diversion number of the called users, these users having the application software [110] installed on their mobile terminals [100], in the case that the calling parties are not users of the application software [110], the choice of the roaming number or the call diversion number being made by the device [330] on the basis of indications sent by the device [ 320], these indications using one or more optional parameters which are available in the protocol syntax of interconnection between the device [330] and the device 30 [320], these indications allowing the device [330] to understand whether the calling parties are users of the application software [110]. 8) System according to claims 1), 3), 4), 6), 7) characterized in that it operates by allowing a subscriber to a cellular operator whose mobile terminal device [100] hosts the application software [ 110] to temporarily change the telephone identifier while being able to benefit from the application software [110] in another possible mobile terminal [100], thus preserving the possibility of being reached by means of voice calls or sending SMS messages. , these calls or SMS being issued to the identifier 2941832 - 61 - provided by the cellular operator with which the user of the application software [110] has subscribed the subscription, the methods for obtaining said possibility of being joined being based on the following operations: A call signaling exchange between the mobile terminal [100] and the server 5 AAA [500] this exchange being started by the application software [110] hosted in the mobile terminal [100], this exchange of signali sation being transported by the http or https transport protocol and making it possible to transmit to the AAA server [500] the call information as well as the identifiers of the calling party and the called party, this signaling exchange being relayed by the AAA server. [500] to the interconnection server [200] hosted in the country in which the originating cellular network of each correspondent resides, this signaling exchange enabling the interconnection server [200] of the correspondent's home country. calling party to initiate callback procedures to the calling party, this signaling exchange also allowing the interconnection server [200] of the called party's home country to initiate call procedures to the called party. An SMS signaling exchange between mobile terminal [100] and AAA server [500] this exchange being started by the application software [110] hosted in the mobile terminal [100], this signaling exchange being transported by the transport protocol 20 said http or https and for transmitting to the AAA server [500] the SMS information and the identifiers of the sending correspondent and the recipient correspondent, this signaling exchange being relayed by the AAA server [500] to the interconnection server [200] hosted in the country in which the originating party's originating cellular network resides, this signaling exchange enabling the interconnect server [200] of the recipient party's home country to initiate call procedures to the recipient correspondent, these call procedures being interpreted as SMS alert messages by the application software [110] hosted in the terminal mo bile [100] of the recipient correspondent, these alert messages enabling said application software [100] to start a signaling exchange with the AAA server [500], the signaling exchange enabling the application software [110] to receive the SMS sent by the sender, the contents of this SMS as well as the identifiers of the sender correspondent and the recipient correspondent being stored by the server AAA [500]. 35 9) System according to claims 1), 2), 3), 4), 5), 6), 7), characterized in that the infrastructure of a cellular operator hosts a CAMEL platform, said platform can communicate with the interconnect server [200] hosted in the country in which the cellular network of said operator resides, the communication between a device [700] of the CAMEL platform and the interconnect server [200] being protocol-based Internet, these protocols allowing an exchange of messages between said CAMEL platform and the interconnection server [200] so that the requests sent to the device [700] of the CAMEL platform from a device 5 [720] of the platform CAMEL allow a device [710] of the CAMEL platform to relay these requests to the interconnection server [200] which, in turn, can send responses to the device [710] of the CAMEL platform so that it can give data. appropriate instructions to the disp ositif [720] of the CAMEL platform, the mentioned message exchange being able to allow an 'implementation of the call procedures according to claim 4), these procedures being based on the following operations: A signaling exchange between the mobile terminal [ 100] and the device [710] this exchange being started by the application software [110] hosted in the mobile terminal [100], this signaling exchange being transported by the so-called USSD transport protocol, this signaling exchange being relayed by the device [330] of the underlying cellular network for transmitting to the device [710] the call information as well as the identifiers of the calling party and the called party. A signaling exchange between the device [710] and the interconnect server [200] that is initiated by the device [710] and directed to the interconnect server [200] hosted in the country in which the cellular network Each originator of each correspondent resides, this signaling exchange allowing the interconnection server [200] of the calling party's home country to start callback procedures to such a calling party, this signaling exchange also allowing the server interconnection [200] of the called party's home country to initiate call procedures to the called party. A call message sent by the interconnecting server [200] from the calling party's home country to the gateway of the originating cellular network of the calling party, this message being used to trigger a polling procedure on the part from the device [320] to the device [710] through the device [720] to obtain the identifier of a device [310]. of the cellular network in which the calling party is located in order to obtain the roaming number of the calling party, the roaming number being subsequently sent by the interconnection server [200] of the correspondent's country of origin. calling to the interconnect server [200] associated with the calling end device [100] of the caller, following the association procedures described in claim 3). - 63 - A call message sent by the originating cellular network device [320] from the calling party to the device [330] to obtain the roaming number of the calling party A call message sent by the device [320] of the originating cellular network of the calling party to the interconnect server [200] associated with the mobile terminating device [100] of the caller following the association procedures described in claim 3), this message permitting triggering a local callback procedure of the interconnect server [200] associated with the calling end device [100] of the caller to the mobile terminal [100], which is identified by its roaming number.