ES2365958B2

Method and system for providing piggyback roaming for sponsoring split roaming relationships

Abstract

Method to facilitate the exchange of one or more signaling messages between a client network and an HSRP network. This method includes the identification by an SPRS router associated with a client network of one or more parameters of the received signaling messages, in order to determine from said parameters one or more of the roaming agreements required between the client network and the HSRP network, to allow the exchange of signaling messages. Furthermore, the method facilitates, by the SPRS router, the exchange of the signaling messages between the client network and the HSRP network through one or more SPRS hubs, when the SPRS router determines that the required roaming agreements do not exist. Also, the method facilitates, via the SPRS router, the direct exchange of signaling messages between the client network and the HSRP network, as soon as the SPRS router determines that the required roaming agreements exist.

ES2365958B2, drawing sheet 1 — Sheet 1 of 14

Term

1.5 yearsleft in the term

Expires 27 March 2028.

33 claims: 4 independent, 29 dependent

1
ES 2 365 958 B2 REIVINDICACIONES 1. Método para facilitar el intercambio de un mensaje de señalización, que comprende:- la identificación, a través de un enrutador del sistema de retransmisión de señales por paquetes (SPRS) asociado con una red cliente, de al menos un parámetro del mensaje de señalización recibido en dicho enrutador SPRS para, de este modo, determinar a partir de por lo menos un parámetro uno o más acuerdos de itinerancia entre la red cliente y una red del socio de itinerancia soportado por el anfitrión (HSRP) y, por tanto, permitir el intercambio del mensaje de señalización entre la red cliente y la red HSRP;- si el enrutador SPRS determina que al menos no hay uno o más acuerdos de itinerancia, facilitar, a través de dicho enrutador SPRS, el intercambio del mensaje de señalización entre la red cliente y la red HSRP por medio de uno o más concentradores SPRS;y - si el enrutador SPRS determina que al menos hay uno o más acuerdos de itinerancia, facilitar, a través de este enrutador SPRS, el intercambio directo del mensaje de señalización entre la red cliente y la red HSRP;y que se caracteriza porque comprende la detección, a través de al menos uno o más concentradores SPRS o del enrutador SPRS, de un intento de registro de un abonado itinerante receptor en la red cliente proveniente de la red HSRP, la retención, en el enrutador SPRS, de un mensaje de registro recibido del abonado itinerante receptor;- el encapsulado del mensaje de registro y la transmisión de este mensaje de registro encapsulado a la red HSRP bien directamente o a través de uno o más concentradores SPRS;- la transmisión, a través del enrutador SPRS y tras recibir una indicación de que el abonado itinerante receptor no ha sido redireccionado a una red diferente a la red cliente, del mensaje de registro guardado o los mensajes de registro subsiguientes del abonado itinerante receptor directamente a la red HSRP;y - la transmisión, a través del enrutador SPRS y tras recibir una indicación de que el abonado itinerante receptor está siendo redireccionado a otra red diferente a la red cliente, del mensaje de registro guardado o los mensajes de registro subsiguientes a la red HSRP por medio de al menos uno o más concentradores SPRS;y donde el enrutador SPRS transmite los mensajes de registro subsiguientes a por lo menos uno o más concentradores SPRS hasta que el enrutador SPRS detecte que se ha logrado el registro o todos los concentradores SPRS fracasen en la finalización del registro del abonado itinerante receptor con la red cliente.
2
El método de la reivindicación 1, en donde la identificación de al menos un parámetro incluye la detección de la dirección de la parte de destino (CdPA) de la parte de control de conexión de la señalización (SCCP), el número de subsistemas (SSN) y el contenido de la parte de aplicación de transacción de capacidades (TCAP) en el mensaje de señalización.
3
El método de la reivindicación 1, que además comprende el encapsulado del mensaje de señalización, a través del enrutador SPRS, antes de transmitir los mensajes de señalización a uno o más concentradores SPRS.
4
El método de la reivindicación 3, que además comprende el desencapsulado del mensaje de señalización encapsulado, a través de al menos uno o más concentradores SPRS, antes de retransmitir el mensaje de señalización encapsulado a la red HSRP.
5
El método de la reivindicación 1, que además comprende permitir el intercambio selectivo del mensaje de señalización entre la red cliente y la red HSRP a través de al menos uno o más concentradores SPRS, en donde cada uno o más de estos concentradores SPRS intercambia selectivamente el mensaje de señalización en base a los criterios de las listas negra y blanca.
6
El método de la reivindicación 1, en donde un punto de transferencia de señalización (STP) está asociado con la red cliente, estando dicho STP configurado para enrutar el mensaje de señalización al enrutador SPRS.
7
El método de la reivindicación 1, en donde un STP está asociado con la red cliente, estando este STP configurado para enrutar el mensaje de señalización a un STP internacional (ISTP) asociado con un servicio portador internacional (ISC), al detectarse un fallo del enrutador SPRS.
8
El método de la reivindicación 1, que además comprende la detección, a través de al menos uno o más concentradores SPRS, de un intento de registro de un abonado itinerante emisor de la red cliente en la red HSRP, si este abonado itinerante emisor utiliza un número de identidad internacional del abonado móvil (IMSI) asociado con la red cliente para registrase con la red HSRP. ES 2 365 958 B2
9
El método de la reivindicación 8, en donde, si el mensaje de señalización está enrutado a una red cliente o al menos a uno o más concentradores SPRS, la red HSRP lleva a cabo uno de los pasos seleccionados de un grupo consistente en:- la configuración de un registro de localización del abonado visitante (VLR) y un nodo de soporte para el sistema servidor general de radio por paquetes (SGSN) para utilizar el análisis IMSI en un código del país para móviles (MCC) o un código de red de teléfonos móviles (MNC) de la red cliente, estando tanto el VLR como el SGSN asociados con la red HSRP;- la configuración de un STP asociado con la red HSRP o una red de terceros para examinar el número de subsistemas (SSN) asociado con una dirección de la parte de origen (CgPA) y una dirección de la parte de destino (CdPA) de los mensajes de señalización destinados a la red cliente;y - la configuración del STP asociado con la red HSRP para enrutar el mensaje de señalización destinado a la red cliente a uno o más concentradores SPRS.
10
El método de la reivindicación 8, que además comprende la modificación, a través de por lo menos uno o más concentradores SPRS, de un número itinerante del HSRP para funcionar como un número itinerante del concentrador que se corresponde con el número itinerante de HSRP, tras recibir el número de HSRP desde un VLR asociado con la red HSRP y, de este modo, enrutar la llamada terminada en el móvil (MT) al número internacional de abonado de la estación móvil (MSISDN) del abonado itinerante emisor a través de al menos un centro de conmutación móvil pasarela (GMSC) acoplado de manera conveniente a por lo menos uno o más concentradores SPRS.
11
El método de la reivindicación 1, que además comprende, con el fin de facilitar un SMS MT a un abonado itinerante emisor de la red cliente, cuando el centro servidor de mensajes cortos (SMSC) que transmite el servicio de mensajes cortos (SMS) MT al MSISDN del abonado itinerante emisor es un SMSC de red no cliente, la modificación, a través del enrutador SPRS, de uno de los pasos seleccionados de un grupo consistente en:- si el abonado itinerante emisor utiliza una modalidad dual IMSI SIM para registrarse con la red HSRP, un IMSI del abonado itinerante emisor por el IMSI anfitrión de dicho abonado itinerante emisor;y - una dirección del centro de conmutación móvil visitado (VMSC)/SGSN a una dirección VMSC/SGSN asociada con al menos uno o más concentradores SPRS.
12
El método de la reivindicación 1, que además comprende:- la retención, en el enrutador SPRS, de un mensaje de registro recibido del abonado itinerante receptor cuando este enrutador SPRS determina, a partir de dicho mensaje de registro, la presencia de un soporte de itinerancia en la red cliente y que al menos no hay uno o más acuerdos de itinerancia entre la red cliente y la red HSRP;- el encapsulado del mensaje de registro y la transmisión de este mensaje de registro encapsulado a la red HSRP a través de por lo menos uno o más concentradores SPRS;y - la recepción, en el enrutador SPRS, de una indicación de si el abonado itinerante receptor es o no un abonado itinerante preferido.
13
El método de la reivindicación 12, que además comprende la realización, en el caso de que se indique que el abonado itinerante receptor es un abonado itinerante no preferido, de uno de los pasos seleccionados de un grupo consistente en:- la transmisión de un mensaje de error a la red cliente en respuesta al mensaje de registro recibido;y - la transmisión directa de un mensaje de registro subsiguiente del abonado itinerante receptor a la red HSRP.
14
El método de la reivindicación 12, que además comprende la realización, en el caso de que se indique que el abonado itinerante receptor es un abonado itinerante preferido, de uno de los pasos seleccionados de un grupo consistente en:- la transmisión de un mensaje de error a la red cliente en respuesta al mensaje de registro recibido;y - la transmisión de un mensaje de registro subsiguiente del abonado itinerante receptor a la red HSRP a través de uno o más concentradores SPRS. ES 2 365 958 B2
15
El método de la reivindicación 12, que además comprende, en el caso de que se indique que el abonado itinerante receptor es un abonado itinerante preferido, la transmisión, a través del enrutador SPRS, del mensaje de registro guardado a la red HSRP por medio de al menos uno o más concentradores SPRS.
16
El método de la reivindicación 12, que además comprende, en el caso de que se indique que el abonado itinerante receptor es un abonado itinerante no preferido, la transmisión, a través del enrutador SPRS, del registro guardado directamente a la red HSRP.
17
El método de la reivindicación 1, en donde un STP asociado con la red cliente está configurado para enrutar el mensaje de señalización, destinado a la red HSRP, al enrutador SPRS cuando la red HSRP intenta redireccionar el tráfico del abonado itinerante receptor independientemente de la red cliente.
18
El método de la reivindicación 1, que además comprende:- la transmisión del mensaje de registro del abonado itinerante receptor a la red HSRP bien directamente o a través de por lo menos uno o más concentradores SPRS;- la determinación de si el abonado itinerante receptor es un abonado itinerante prepago o de contrato;- la transmisión, en el caso de que se determine que el abonado itinerante receptor es prepago, del mensaje de registro o de un mensaje de registro subsiguiente del abonado itinerante prepago desde el abonado itinerante receptor a la red HSRP a través de al menos uno o más concentradores SPRS;y - la transmisión, en el caso de que se determine que el abonado itinerante receptor es de contrato, del mensaje de registro o de un mensaje de registro subsiguiente del abonado itinerante de contrato a la red HSRP.
19
El método de la reivindicación 1, en donde el enrutador SPRS encamina el mensaje de señalización a la red HSRP a través de al menos uno o más concentradores SPRS en un formato identificable por dicha red HSRP.
20
El método de la reivindicación 1, en donde al menos uno o más concentradores SPRS soportan por lo menos uno o más acuerdos de itinerancia, estando dichos acuerdos establecidos entre una pluralidad de redes cliente y una pluralidad de redes HSRP.
21
El método de la reivindicación 20, que además comprende el almacenamiento en uno o más concentradores SPRS de al menos:- una lista negra o una lista blanca de la pluralidad de redes HSRP;y - los mapeos de identidad asociados con cada una de dicha pluralidad de redes cliente.
22
El método de la reivindicación 1, en donde la red cliente mantiene una pluralidad de acuerdos de itinerancia con una pluralidad de redes anfitrión que se corresponden con cada uno o más concentradores SPRS y, en donde, el enrutador SPRS almacena la información relacionada con cada uno o más acuerdos de itinerancia entre la red cliente y la pluralidad de redes HSRP y cada una de dicha pluralidad de acuerdos de itinerancia con la pluralidad de redes anfitrión correspondientes con cada uno o más concentradores SPRS.
23
Método para facilitar el intercambio de un mensaje de señalización, que comprende:- la identificación, a través de un enrutador SPRS asociado con una red cliente, de uno o más parámetros de los mensajes de señalización recibidos en dicho enrutador SPRS para, de este modo, determinar a partir de los parámetros identificados uno o más acuerdos de itinerancia con la red cliente y permitir, por tanto, el intercambio del mensaje de señalización desde la red cliente;- si el enrutador SPRS determina que no hay uno o más acuerdos de itinerancia, facilitar, a través de este enrutador SPRS, el intercambio indirecto del mensaje de señalización desde la red cliente;y - si el enrutador SPRS determina que al menos hay uno o más acuerdos de itinerancia, facilitar, a través de este enrutador SPRS, el intercambio directo del mensaje de señalización desde la red cliente.
24
Sistema para facilitar el intercambio de un mensaje de señalización, que comprende:- una red cliente;- una red HSRP accesible a través de la red cliente;ES 2 365 958 B2 - uno o más concentradores SPRS accesibles a través de la red cliente, y - un enrutador SPRS asociado con la red cliente para identificar al menos un parámetro del mensaje de señalización recibido en el enrutador SPRS para determinar a partir de al menos un parámetro uno o más acuerdos de itinerancia entre la red cliente y la red HSRP y, de esto modo, permitir el intercambio del mensaje de señalización entre la red cliente y la red HSRP;en donde, si el enrutador SPRS determina que al menos no existe uno o más acuerdos de itinerancia, este enrutador SPRS facilita el intercambio del mensaje de señalización entre la red cliente y la red HSRP a través de al menos uno o más concentradores SPRS;y, en donde, si el enrutador SPRS determina que al menos existe uno o más acuerdos de itinerancia, dicho enrutador SPRS facilita el intercambio directo del mensaje de señalización entre la red cliente y la red HSRP.
25
El sistema de la reivindicación 24, en donde al menos uno de los enrutadores SPRS o uno o más concentradores SPRS está asociado con un STP de la red cliente o un STP de una red anfitrión.
26
El sistema de la reivindicación 24, en donde un operador de red anfitrión o un concentrador de conectividad abierta (OC) despliega al menos uno o más concentradores SPRS.
27
El sistema de la reivindicación 24, en donde un concentrador OC despliega por lo menos uno o más concentradores SPRS, y en donde dicho(s) concentrador(es) SPRS desplegado(s) está(n) integrado(s) con el enrutador SPRS.
28
El sistema de la reivindicación 24, en donde al menos uno o más concentradores SPRS se comunican con el enrutador SPRS utilizando uno de los protocolos seleccionados de un grupo consistente en:sistema de señalización n° 7 (SS7), protocolo de Internet (IP) y transporte de señalización (SIGTrAN).
29
Un producto de programa informático que comprende un medio utilizable por ordenador incluyendo un código de programación utilizable por ordenador para facilitar el intercambio de un mensaje de señalización, y:- un código de programación utilizable por ordenador para identificar, a través de un enrutador SPRS asociado con una red cliente, al menos un parámetro del mensaje de señalización recibido en dicho enrutador SPRS para, de este modo, determinar a partir de por lo menos un parámetro uno o más acuerdos de itinerancia entre la red cliente y una red HSRP y, por tanto, permitir el intercambio de los mensajes de señalización entre la red cliente y la red HSRP;- un código de programación utilizable por ordenador para que en el caso de que el enrutador SPRS determine que no hay uno o más acuerdos de itinerancia, facilitar, a través del dicho enrutador SPRS, el intercambio de los mensajes de señalización entre la red cliente y la red HSRP por medio de uno o más concentradores SPRS;y - un código de programación utilizable por ordenador para que en el caso de que el enrutador SPRS determine que al menos hay uno o más acuerdos de itinerancia, facilitar, a través de este enrutador SPRS, el intercambio directo de los mensajes de señalización entre la red cliente y la red HSRP.
30
El método de la reivindicación 1, que además comprende la ejecución de un servicio avanzado.
31
El método de la reivindicación 23, que además comprende la ejecución de un servicio avanzado.
32
El sistema de la reivindicación 24, en donde la red cliente lleva a cabo un servicio avanzado.
33
El sistema de la reivindicación 24, en donde al menos uno o más concentradores SPRS llevan a cabo un servicio avanzado.

Independent claims33

304 paragraphs in 10 sections, as filed

ES 2 365 958 B2

DESCRIPTION

Method and system for providing overlapping roaming and sponsoring partial roaming relationships.

Related requests

This application claims priority from United States Provisional Patent Application No. 60 / 907,287 entitled "Overlapping Roaming with Two-Node Architecture to Sponsor Partial Roaming Relationship," filed March 27, 2007. Likewise, this application is related to United States patent application No. 10 / 778,861 "Packet Relay and Signaling System including General Packet Radio Services (GPRS)" filed on February 14, 2004, which claims priority from United States Provisional Application No. 60 / 447,533 with the same title and filed on February 14, 2003. In addition, it is related to United States Patent No. 7,072,651, filed on July 4, 2006, entitled "Method and system to redirect network traffic in mobile connections", which claims the priority of the provisional application of United States No. 60 / 401,362 filed August 5, 2002. Each of the above referenced patent applications is incorporated herein by reference in its entirety.

Field of the invention

The present invention relates generally to mobile communication of roaming subscribers. More specifically, the invention facilitates mobile communication of sender roamers from a client network in visited networks and receiving roamers from home networks in the client network independent of client network roaming relationships with these visited and home networks.

Background of the invention

Due to the increasing popularity of travel and mobile wireless telecommunications services, different network operators compete with each other to increase their roaming revenues. "Roaming" occurs when a subscriber, from a "home" network, uses their own device to communicate over a "visited" network while traveling.

In general, these mobile public wireless network operators mutually establish roaming agreements to provide various mobile services (such as call and non-call related services) to their sending and receiving roaming subscribers in different countries (or in different areas of the same country). . The establishment of roaming agreements generally requires bilateral agreements (or relationships), which implies commercial roaming agreements, connection configurations, tests of the International Roaming Expert Group (IREG International Roaming Expert Group) and the International Data Group of Transferred Accounts (TADIG Transfer Accounting Data International Group). These bilateral agreements allow a network operator to provide different roaming services, such as Global Mobile Communication System (GSM), General Packet Radio Service (GPRS), Custom Applications for Mobile Network Enhanced Logic (CAMEL ), third generation mobile (3G), etc., to their sender and receiver roamers, ultimately attracting more receiving roamers from preferred networks to their networks, and forces more of your sender roaming subscribers to sign up with their preferred networks. On the other hand, the network operator can even establish a unilateral agreement (for example, CAMEL to increase its income for incoming roaming) with other network operators. Preferred networks are those that have bilateral or unilateral agreements with the network operator.

However, in certain cases, large network operators prefer not to have roaming agreements with newer or smaller network operators. In other words, maintaining the roaming agreement with these smaller network operators is not a priority for the large network operators. Furthermore, these small network operators cannot even provide the resources for establishing and maintaining the roaming relationship with these large network operators. Also, some network operators may wish to launch their services quickly or offer new services to their roaming subscribers, in both cases it is necessary for these network operators to establish roaming relationships with other network operators. However, network operators (those who launch their services) cannot afford to rely on the delay of the commercial agreement process with other network operators. Thus, such network operators end up providing mobile services to their roamers on a few preferred networks with limited services.

Consequently, most network operators look for alternative ways to establish roaming agreements that increase their roaming coverage and provide various mobile services to their sending and receiving roamers. In one of these techniques, a new network operator establishes a roaming agreement with an intermediary operator to acquire all roaming agreements with other network operators within an ecosystem consisting of member networks maintained by the intermediary operator. In this case, however, the new network operator may not join the ecosystem unless it is large and covers the roaming agreements required by this new network operator. Also, this technique still requires an intermediary operator to set up the connection settings and IREG and TADIG tests for the new operator.

Another technique requires a new network operator to overlap existing bilateral or unilateral roaming agreements with a host network operator (such as GSM, CAMEL and GPRS agreements) to provide services.

ES 2 365 958 B2 mobiles to their sender and receiver roamers. In this case, the new network operator uses the host network's roaming agreements to exchange signaling messages with selected networks that do not have direct (bilateral) roaming agreements with the new network but have such roaming agreements with the network. host. The host network corresponds to a network that sponsors the new network operator to extend its roaming coverage to GSM, CAMEL, GPRS or a combination thereof. Unlike the intermediary operator solution where the ecosystem members define the roaming coverage, the roaming coverage of the overlay solution for the new network operator is characterized by host network roaming agreements with other networks. Consequently, the new network operator can also be superimposed on the host network connection configuration and requires or not less IREG and TADIG testing compared to the intermediary operator solution.

One or more of the aforementioned techniques does not consider the situation where the new (or established) network operator already has a roaming agreement with a roaming partner but wants to use the overlay technique to establish another roaming relationship with this roaming partner through the host network operator. For example, an operator "X" may already have a GSM roaming agreement with a roaming partner "Y"; however, you may also want to establish GPRS roaming agreement with roaming partner “Y” (or any other roaming partner) that does not have GPRS roaming agreement with operator “X”. Since each relationship provides different roaming coverage, such a situation is known as partial roaming.

Despite the importance of voice accounts for most roaming revenue, data agreements (such as GPRS agreements) play a significant role in influencing device selection across networks. For example, the 3G device first searches for networks that support 3G. Similarly, GPRS devices such as Blackberry and multimedia messaging service (MMS) enable devices that typically search first for networks that support GPRS. As a result, although these devices could still primarily use voice, networks that do not have data agreements with home networks using these inbound roaming devices lose receiving roaming subscribers (and thus incoming roaming subscribers) by using those devices. for roaming charged to them). Similarly, networks that do not support CAMEL agreements lose out on CAMEL-based prepaid receiver roamers whose home networks can apply addressing techniques to divert them to networks that support CAMEL agreements with these home networks.

In accordance with the above, the art needs a computer system, method and product, which supports the partial roaming situation to expand the roaming coverage of a network operator.

Summary

The present invention is directed to a method of facilitating the exchange of one or more signaling messages between a client network and an HSRP network. This method includes the identification by means of an SPRS router associated with a client network, one or more parameters of the signaling messages received in said SPRS router in order, in this way, to determine from the parameters one or more of the required roaming agreements between the client network and the HSRP network and therefore allow the exchange of signaling messages. Furthermore, the method facilitates, by means of the SPRS router, the exchange of the signaling messages between the client network and the HSRP network through one or more SPRS hubs, as soon as the SPRS router determines that the required roaming agreements do not exist. Also, the method facilitates, by means of the SPRS router, the direct exchange of the signaling messages between the client network and the HSRP network when this SPRS router determines that the required roaming agreements exist.

Another aspect of the present invention relates to a system for facilitating the exchange of one or more signaling messages between a client network and an HSRP network. The system includes an SPRS router deployed on the client network. This SPRS router identifies one or more parameters of the received signaling messages in order to, in this way, determine from said parameters one or more of the required roaming agreements between the client network and an HSRP network and therefore allow the exchange of signaling messages. Furthermore, the SPRS router facilitates the exchange of the signaling messages between the client network and the HSRP network through one or more SPRS hubs, as soon as this SPRS router determines that the required roaming agreements do not exist. Also, the SPRS router facilitates the direct exchange of signaling messages between the client network and the HSRP network when this router determines that the required roaming agreements exist.

In yet another aspect of the present invention a computer program product is provided that includes computer-usable programming code to facilitate the exchange of one or more signaling messages between a client network and an HSRP network by identification by an SPRS router. associated with the client network, of one or more parameters of the signaling messages received in said SPRS router to, in this way, determining from these parameters one or more of the required roaming agreements between the client network and an HSRP network and thus allowing the exchange of the signaling messages. In addition, the software product facilitates the exchange of the signaling messages by the SPRS router between the client network and the HSRP network through one or more SPRS hubs. Also, the software product facilitates the direct exchange of signaling messages by the SPRS router between the client network and the HSRP network.

ES 2 365 958 B2

Brief description of the figures

In the drawings, the same or similar reference numerals identify like elements or performances.

Figure 1 illustrates a two-node packet signal relay (SPRS) system for a client network to overlap the host network's roaming relationships with one or more host-supported roaming partner (HSRP) networks. , according to an embodiment of the present invention;

Figure 2 illustrates the interconnection between a plurality of host networks and a plurality of client networks, in accordance with an embodiment of the present invention;

Figure 3 depicts a flow chart for expanding the roaming coverage of the client network, according to an embodiment of the present invention;

Figure 4 represents a flow diagram to facilitate the call terminated in the mobile (MT) to the sending roamer using the dual mode IMSI (international mobile subscriber identification number) and SIM (subscriber identification module), according to an embodiment of the present invention;

Figure 5 depicts a flow chart for facilitating MT Short Message Service (SMS) from a client Short Message Server Center (SMSC) to the sending roamer using the IMSI SIM dual mode, according to a first embodiment of the present invention;

Figure 6 represents a flow chart for providing the SMS MT, using the interworking function of the SMSC, to the sender roamer using the IMSI SIM dual mode, according to a second embodiment of the present invention;

Figure 7 depicts a flow chart to facilitate General Packet Radio Service (GPRS) or SMS or Custom Application Based Call for Mobile Network Enhanced Logic (CAMEL), all mobile originated ( MO), by the sending roamer using the dual mode IMSI SIM, according to an embodiment of the present invention;

Figure 8 depicts a flow chart of client Home User Location Registration (HLR) RESET while the client network sender roamer is registered with an HSRP network using a host IMSI or a client IMSI, according to an embodiment herein invention;

Fig. 9 depicts a flow chart for registering the receiving roamer in the client network using an HSRP network SIM, according to a first embodiment of the present invention;

Figures 10A and 10B depict a flow chart for first routing the CAMEL-supported receiving roamer registration in the client network to an SPRS hub, according to a second embodiment of the present invention;

Figures 11A and 11B depict a flow chart for first routing the receiving roamer's record directly to the HSRP network, according to a third embodiment of the present invention; Y

Fig. 12 depicts a flow chart for facilitating the CAMEL MO, SMS MO, or GPRS MO call by the receiving roamer in the client network, according to an embodiment of the present invention.

Detailed description

In the following description the specific configurations, materials, and numbers are set forth for clarification purposes to provide a thorough understanding of the present invention. However, it will be apparent to one of ordinary skill in the art that the present invention can be carried out without these specific details. In some cases, well-known features may be omitted or simplified to avoid confusion in understanding the present invention. Furthermore, when the specification refers to "certain embodiment" or "an embodiment" it means that a special feature, structure or characteristic described in connection with the embodiment is included in at least some embodiment of the present invention. The appearance of the phrase "in one embodiment", in various parts of the specification, does not necessarily refer to the same embodiment. The present invention provides a computer program system, method and product where a client network "overlaps" one or more roaming relationships (interchangeably referred to as agreements) of the host network with one or more networks of the supported roaming partner. by the host (HSRP), allowing the client network to provide roaming telecommunications services to its sending roamers, and that the subscribers of the visited networks visit (roaming) the coverage area that is within the client network. An HSRP network may correspond to a mobile network operator who has established a roaming agreement with the host network, to enable inbound roaming to the subscribers of the host network, and outbound roaming to its own subscribers. Generally, a good candidate to play the role of a host network operator according to the present invention would have bilateral roaming agreements with several HSRP network operators. But the client network operator itself lacks that many bilateral roaming agreements and is therefore looking for an agreement with which it can enjoy the

ES 2 365 958 B2 benefit from the host network operator's roaming agreements with those HSRP networks. An object of the present invention is to enable "overlay" where a client network or host network can implement a system, a method or apparatus that enables a client network to effectively expand its roaming coverage to include two-way roaming with such HSRP networks by virtue of reaching an agreement with a host network allowing the client network to enjoy the benefit of relationships of the host network's own roaming with those HSRP networks.

In a preferred embodiment the "overlay" allows the customer network operator to propose inbound and outbound roaming with those HSRP networks without itself establishing such bilateral roaming agreements with said HSRP networks. In various embodiments of the present invention, the overlay enables the client network to exchange signaling messages with the HSRP networks, thereby allowing the client network operator to provide roaming services to roaming subscribers from the HSRP networks ( hereinafter referred to as receiving roamers) or roaming in HSRP networks (hereinafter referred to as sender roamers). As will be apparent to a person skilled in the art, roaming services include standard call and non-call related activities such as, but not limited to, mobile originated call (MO), mobile terminated call (MT), service short messages (SMS), packet data network (PDN), and other value-added services (VASs).

In a certain embodiment of the present invention, although the client network may have a GSM (global mobile communication system) roaming agreement (unilateral, bilateral, or multilateral) with the HSRP network, it may not have a GPRS roaming agreement with said network. (general packet radio service) (unilateral, bilateral or multilateral). In such a case, if the host network has bilateral GPRS roaming agreements with the client network and the HSRP network, the client network uses the host network's GPRS roaming relationship (i.e. by overlay) with the HSRP network to establish the GPRS roaming agreement required with this HSRP network.

In a first embodiment of the present invention, the client operator has a GSM roaming agreement (including voice, SMS and CAMEL) with the HSRP network, and overlaps with one or more host networks to establish other roaming agreements with said HSRP network. This case is referred to hereinafter interchangeably as partial roaming. These roaming agreements can be, but are not limited to, GPRS (including GPRS, SMS and CAMEL), custom applications for mobile network enhanced logic (CAMEL) and third generation mobile (3G). In addition, with the advent of technology, the client network operator can use various embodiments of the present invention to provide support and roaming agreements for other emerging technologies such as, but not limited to, WiFi, WiMax, Voice over Internet Protocol (VoIP). ), IP Multimedia Subsystem (IMS) and Session Initiation Protocol (SIP). For example, when the client network does not have IMS roaming agreement with the HSRP network, the client network can overlap the host network's IMS roaming agreement with the HSRP network to achieve the required IMS roaming agreement with this HSRP network. Therefore, one or more host networks are those that support one or more required roaming agreements between the client network and the HSRP networks.

In a second embodiment of the present invention, the client network operator requires at least two roaming agreements with the HSRP network, where the client network may or may not have any existing roaming agreements with said HSRP network. Even in this case, the client network overlaps one or more host network roaming agreements with the HSRP network to maintain the required roaming agreements. Various embodiments of the present invention consider this scenario as partial roaming. Both partial roaming scenarios result in an extension of the roaming coverage of the client network using the roaming coverage of one or more host networks.

Figure 1 illustrates a two-node (100) packet signal relay (SPRS) system that allows a client network (102) to overlap the roaming relationships of a host network (104) with one or more HSRP networks. , according to an embodiment of the present invention. The client network (102) includes an SPRS router (106) and the host network (104) consists of an SPRS hub (108). Under an earlier point of view, as taught by the inventor of US Patent Application No. 10 / 778,861, filed on February 14, 2004, a method and system is provided to allow a client network to overlap relationships of GPRS roaming of a host network. Hereinafter, this record is referred to as "prior SPRS record": In various embodiments of the present invention, the SPRS hub 108 corresponds to an SPRS node from the prior SPRS record. In this case, the SPRS router 106 communicates with the SPRS node to implement various embodiments of the present invention. In another embodiment of the present invention, the SPRS concentrator 108 is a third operator deployed concentrator. The operation of the SPRS router (106) in the client network (102) does not affect the functionality of the third hub or the SPRS node of the "previous SPRS record." The client network (102), which in any case is unable to support the required roaming agreement (eg GSM, GPRS, CAMEL, 3G, etc.) with HSRP networks, uses the SPRS router (106) and the hub SPRS (108) to establish the required roaming agreement with HSRP networks. In a certain embodiment of the present invention, a receiving roamer registers from an HSRP network with the client network (102). In another embodiment of the present invention, a sender roamer from the client network (102) registers with the HSRP network.

In addition, the SPRS (100) includes in the client network (102), a home user location register (HLRC) (110), a gateway mobile switching center (GMSC-C) (112), a data transfer point signaling (STPC) (114), a signaling control point (SCP-C) (116) and a short message server center (SMSC-C) (118). Also, the client network (102) comprises a Visited Subscriber Location Register (VLR-C) (120) that is integrated with a Visited Mobile Switching Center (VMSC). Since the VLR-C (120) communicates

ES 2 365 958 B2 with its integrated VMSC using an internal communication interface (called B-interface) and a number of subsystems (SSN), and which jointly reside in the client network (102), hereinafter referred to interchangeably as VMSC / VLR-C (120). The SPRS router (106), the HLR-C (110), the GMSC-C (112), the STP-C (114), the SCP-C (116), the SMSC-C (118) and the VMSC / VLR-C (120) are interconnected, and communicate with each other through Signaling System No. 7 (SS7) links (as illustrated in Figure 1 by dotted lines). Additionally, in the event that the client network (102) supports GPRS, said network also includes a domain name service (DNS-C) (122), a support node for the GPRS server system (SGSN-C) ( 124) and a gateway GPRS support node (GGSN-C) (126) which are interconnected, and communicate with each other through an Internet protocol (IP) connection.

Furthermore, the SPRS (100) includes in the host network (104), a GMSC-H (128), a STP-H (130), and a DNS-H (132). The SPRS hub (108) uses a SPRS-global title (GT) functional module (134) to relay from SS7 and a SPRS-IP functional module (136) to relay from GPRS-IP. The SPRS concentrator (108) uses these functional modules to substitute the addresses of the client network (102) (that is, GT or IP addresses) with the corresponding ones of said concentrator (108). In one embodiment of the present invention, the SPRS router (106) and the SPRS hub (108) are logic modules that are integrated with elements present in the network such as STPs. In this case, the SPRS router (106) can be integrated with the STP-C (114), and the SPRS hub (108) with the STP-H (130). In another embodiment of the present invention, the SPRS hub (108) is integrated with the SPRS router (106), and they are deployed by the host network (104) or by the client network (102). Additionally, these logic modules can be deployed on the same platform or on separate platforms, and communicate with each other through a bearer signaling protocol that includes, but is not limited to, IP, Signaling Transport (SIGTRAN), and SS7. The GMSC-H (128), the STP-H (130) and the SPRS-GT (134) are interconnected, and communicate with each other through SS7 links. Similarly, DNS-H (132) and SPRS-IP (136) are interconnected, and communicate with each other over the IP connection. Also, the GMSC-H (128) communicates with the GMSC-C (112) through a voice trunk connection. As will be evident to a person skilled in the art, in the event that the client network (102) and the host network (104) reside in different countries, the SPRS (100) will also include an international bearer service (ISC) between both networks. (102 and 104). As will be equally apparent to one of ordinary skill in the art, the client network (102) and the host network (104) may also include various network components, depending on the architecture under consideration.

Furthermore, the plurality of host networks and the plurality of client networks can communicate with each other to extend the roaming coverage of these client networks. Figure 2 illustrates the interconnection between the plurality of host networks and the plurality of client networks, according to an embodiment of the present invention. The plurality of client networks includes a client-1 network (202), a client-2 network (204), and a client-3 network (206). The client-1 network (202), the client-network (204) and the client-3 network (206) comprise a router-1 SPRS (208), a router-2 SPRS (210) and a router-

SPRS (212), respectively. In one embodiment of the present invention, in the event that there is a group of client network operators across multiple circuits within the same country sharing the SPRS router, it is deployed at a central location with an international SS7 bearer.

The plurality of host networks includes a host-1 network (214), a host-2 network (216), and a host-3 network (218). The host network-1 (214), the host network-2 (216) and the host network-3 (218) comprise a router-1 SPRS (220), a router-2 SPRS (222) and a router-3 SPRS (224), respectively. In a first embodiment of the present invention, the host network-1 (214) uses the SPRS hub-1 (220) to support the plurality of client networks (client network-1 (202) and client network-3 (206), as shown in figure 2), where each client network has an associated SPRS router. Since host-1 network (214) can have GPRS, CAMEL, or 3G roaming agreements with many HSRP networks, this host-1 network (214) can extend these agreements to plurality of client networks. In such a case, the SPRS hub-1 (220) stores information that includes, but is not limited to, the blacklist and whitelist of HSRP networks and identity mappings (for example, host IMSI mappings and of the client IMSI in case of roaming agreement with the IMSI dual mode, mapping of the client network entities and SPRS hub-1 (220), mapping of the HSRP network entities and SPRS hub-1 (220), etc.) for each client network supported in your database. For example, the SPRS hub-1 (220) can store a mapping between the HSRP network entity as the VMSC / VLR in the HSRP network and the SPRS hub-1 (220), and a mapping between the client network entity as the VMSC / VLR on client network and SPRS hub-1 (220). Detailed explanation of these examples will be described later in the context of the present invention. Using the criteria of black and white lists, the SPRS Hub-1 (220) allows the selective exchange of signaling messages between its client networks (that is, the client network-1 (202) and the client network-3 (206)) and HSRP networks through this SPRS hub-1 (220). This means that in the event that the SPRS hub-1 (220) receives the signaling messages destined for a HSRP network "X" that is whitelisted in the SPRS hub-1 database (220), said hub allows the routing of these signaling messages. However, when the SPRS hub-1 (220) receives the signaling messages destined for a HSRP "Y" network that is blacklisted in the SPRS hub-1 database (220), that hub prevents routing. of the signaling message through itself. In a certain embodiment of the present invention, these restricted messages are rejected and therefore are never processed. In another embodiment of the present invention, the SPRS hub-1 (220) sends a signaling connection control part (SCCP) data transfer services unit (UDTS) message with a recurring header such as, but not limited to, “destination is unreachable” and “no conversion for destination” to client-1 network (202) (if client-1 network (202) is the only one that has transmitted the signaling message before towards the HSRP network "Y").

ES 2 365 958 B2

To extend roaming coverage, the client-1 network (202) overlaps the plurality of host networks (for example, host network-1 (214) and host network-2 (216) as shown in the figure 2), where each host network has an associated SPRS hub, according to a second embodiment of the present invention. The SPRS router-1 (208) then stores the information about each host network in its database. This information includes, but is not limited to, the roaming agreements between the plurality of HSRP networks and the plurality of host networks, and the required roaming agreements of the client-1 network operator (202) with the plurality of network operators. host. This information allows the SPRS router-1 (208) to determine which host network is required by the client network operator-1 (202) to overlay and establish a particular required roaming agreement with the HSRP network operator.

In one embodiment of the present invention, the plurality of host networks share a common SPRS hub-1 (220) deployed at the central location. In another embodiment of the present invention, the host network (s) deploys multiple hubs at a location where there is a local SS7 connection between the host network (s). In yet another embodiment of the present invention, each host network deploys multiple SPRS hubs to support the client-1 network (202) for the different roaming arrangements required with the HSRP network (s). In one of the examples, the host-1 network (214) supports CAMEL roaming with the HSRP network, and the host-2 network (216) supports both GPRS and 3G roaming with the same HSRP network. In another example, the client-1 network (202) establishes a GSM roaming agreement with the HSRP network through the host-1 network (214), and a GPRS roaming agreement with the same HSRP network through the network. host-2 (216). This is done by overlaying the first the GSM roaming agreement of the host-1 network (214), and the latter the GPRS roaming agreement of the host-2 network (216) with the HSRP network. In this case, when the client-1 network (202) provides the receiving roamer from the HSRP network, the associated HLR of the receiving roamer with the HSRP network may have a client1 network VmSC / YLR address (202) and a Host Network SGSN-2 (216). Consequently, the HSRP network believes that its roamer is registered in the GSM with the client network-1 (202) and in the GPRS with the host network-2 (216). However, from the perspective of the roamer's device, it is registered in GSM and GPRS with the same client network1 (202) that has the same network code for GSM and GPRS. As will be apparent to a person skilled in the art, neither the 3GPP standard (third generation partnership project) nor any existing HLR prohibits such a situation. In fact, the 3GPP standard (for example, GSM 29.002 and GSM 23.012) allows this situation where a mobile device can be registered at the same time in GSM with one network and in GPRS with another network; although, the mobile device will try to sync its record with the same network. For example, a Blackberry device registered with network A that supports both GSM and GPRS searches for an alternative network B with GPRS support when the existing network A loses GPRS coverage for this device. So, in this case, there is a time interval in which the Blackberry device is registered in the GSM with network A and in the GPRS with network B, although said device will later synchronize its registration through the GSM registration with the network B.

In the aforementioned case of partial roaming, the TAP records submitted by two different networks (ie, one for GSM and one for GPRS) to the client-1 network (202) may cover the same or similar time slots. These networks can be in the same country or in different countries. Furthermore, in such cases fraud is not incurred, since the 3GPP standards allow to have the GSM and GPRS records in different networks. This partial roaming billing situation is similar to the overlapping roaming billing concept explained in the previous SPRS file, where the TAP records of a competing network operator (corresponding to the HSRP network operator of the present invention) are can overlap the client network operator and the TAP records of the host network operator can overlap the client network operator and, in both cases, instantly (for example, seconds, minutes, etc.).

In a third embodiment of the present invention, the client-2 network (204) overlaps the host-2 network (216) and the host-3 network (218) to support GSM and GPRS roaming with the HSRP network. The SPRS concentrator-2 (222) supports the GSM agreement with the HSRP network and this SPRS concentrator-2 (222) subsequently interacts with the SPRS concentrator-3 (224) to establish the required GPRS agreement with the HSRP network. Similarly, the client network3 (206) can overlap roaming relationships with the host network-1 (214) and the host network-3 (218) to establish the required roaming agreements with the HSRP network.

In a third embodiment of the present invention, the SPRS hubs and the SPRS routers are cascaded. In this case, a first host network uses an SPRS hub to support the required roaming agreements of the client network operator, and the first host network also deploys an SPRS router to overlap a second host network that also deploys an SPRS hub. This benefits the customer network operator who has some roaming agreements with network operators and requires:

a) Other roaming agreements with the same or other network operators, or

b) Similar types of roaming agreements with other network operators to offer a complete package of roaming services to the customer network operator.

For example, an N1 network that has many GSM, GPRS and 3G relationships, but few CAMEL relationships can be a host network operator for many client network operators. By overlaying the CAMEL agreements of an N2 network, the N1 network can also offer the CAMEL extension to its client networks. From the perspective of the N1 client networks, this N1 network provides the CAMEL extension although it is actually managed in the background by the N2 network. In this case, each client network on the N1 network needs to have an SPRS router to manage the scenario.

ES 2 365 958 B2 partial roaming. Also, the N1 network needs to have an SPRS router and an SPRS hub. In this case, in order to manage CAMEL billing, the client network of N1 sends the bill to the network N1, which can then send it to the network N2. Finally, the N2 network sends the bill to the HSRP network. As will be apparent to one skilled in the art, any combination of partial roaming is possible within the scope of the present invention.

To support the required roaming agreements of the client network operator (102) with the HSRP network operator, the client network (102) first needs to determine which roaming agreements are required, and based on this determination the client network (102) it then overlays the selected host network (s) that support those required roaming agreements. A flow chart for extending the roaming coverage of the client network 102 is shown in Figure 3, in accordance with an embodiment of the present invention. In step 302, the SPRS router (106) identifies one or more parameters of the signaling messages received at the SPRS router (106) to determine from these parameters one or more of the required roaming agreements between the client network. (102) and the HSRP network. These roaming agreements allow the exchange of signaling messages between the client network (102) and the HSRP network. In one embodiment of the present invention, the received signaling messages originate in the client network 102 and are destined for the HSRP network. The signaling messages include a routing information send (SRI), a FwdSMS (SMS forwarding), a SRI-SM-ACK, a RESET and a separate subscriber data insert (ISD) in the case of roaming scenario overhang which will be explained later in the context of the present invention. Similarly, signaling messages include a location update (LUP), a GPRS-LUP, a FwdSMS, and the CAMEL application part (CAP) of the signaling service switching point-signaling control point (SSP-SCP). in case of inbound roaming scenario as will also be explained later in the context of the present invention. In one embodiment of the present invention, the client network operator (102) configures the STP-C (114) so that the SCCP addresses the signaling messages using a destination party address (CdPA) with the national code prefix. country code (CC) dialing (NDC) from the HSRP network to the SPRS router (106). In this case, the STP-C (114) whose client network (102) does not have a bilateral GSM / GPRS / CAMEL / 3G agreement with the HSRP network routes all the signaling messages destined for the HSRP network to the SPRS router (106). To resolve the failure of the SPRS router (106), the client network operator (102) configures the STP-C (114) to secondarily route (backup copy) the signaling messages to an international STP (ISTP) associated with the ISC. This is done to have at least normal roaming configurations in case the SPRS router (106) fails.

In one embodiment of the present invention, the SPRS router (106) is capable of determining the host networks that support the required roaming agreements. Detailed explanation on the method for determining the host network is provided below in the context of the present invention. In an embodiment of the present invention, the SPRS router (106) detects the SSN of a CdPA and the content of the Transaction Capabilities Application Part (TCAP) (for example, 3G parameters in case of 3G signaling messages and parameters CAMEL in case of CAMEL signaling messages) as the parameters of the signaling messages and uses these parameters to determine the routing path of these messages. In another embodiment of the present invention, if two CdPAs of the signaling messages have the identical SSN, the SPRS router (106) identifies the routing path based on the CdPA of the signaling message. In both of the above embodiments, the routing path is determined by identifying the type of roaming agreements required corresponding to said signaling messages. The types of required roaming agreements considered are, but not limited to, GSM, GPRS, CAMEL, 3G, and high speed packet download access (HSDPA). For GSM roaming, the SSN can be HLR (SSN = 6), VLR (SSN = 7), GMSC (SSN = 8), VMSC (SSN = 8), SMSC (SSN = 8), and so on. For GPRS roaming, the SSN can be SGSN (SSN = 95) and GGSN (SSN = 96). For CAMEL Application Protocol (CAP) messages, the SSN can be CAP (SSN = 92) and SCP (SSN = 93). For 3G roaming, the SSN can be RANAP (SSN = 8E) and RNSAP (SSN = 8F). For 3G and CAMEL roaming, unless mobile application part (MAP) parameters can be distinguished (e.g. CAMEL profile, CAMEL support, immediate service termination (1ST), supercharge support, etc.) as 3G , the SPRS router (106) uses the 3G SSN to determine the required roaming agreements.

Once, using the parameters, the type of roaming agreements required in the signaling message destined for the HSRP network has been determined, the SPRS router (106) checks, in step 304, if the required roaming agreements already exist. . The SPRS router (106) releases the client network STPs (102) as of when it has decided to determine the routing path of the signaling messages destined for the HSRP network (that is, the bilateral route to the HSRP network or to through the host network (104)). This avoids complex interactions in the STPs that may be required to determine the routing path. If in step 304, the SPRS router (106) determines that the required roaming agreements already exist, then this SPRS router (106), in step 306, diverts the signaling message directly to the HSRP network without modification. Subsequent signaling messages are also exchanged directly between the client network (102) and the HSRP network. The direct path of signaling messages between the client network (102) and the HSRP network bypassing the host network (104), is hereinafter referred to as a bilateral route, according to an embodiment of the present invention. Direct routing can also be done using an alternative STP (either on the client network (102) or at the ISC) or with the same STP-C (114) using a different conversion type (TT) to avoid infinite loops.

On the other hand, if in step 304, the SPRS router (106) identifies that the roaming agreement does not exist, then this SPRS router (106) facilitates, in step 308, the exchange of the signaling messages between the client network. (102) and the HSRP network through one or more SPRS hubs. For the sake of convenience, only the SPRS concentrator 108 is considered to explain various embodiments of the present invention. In one embodiment of the present

In the invention, the SPRS router (106) encapsulates the signaling messages destined for the HSRP network before sending these encapsulated messages to the SPRS hub (108). Encapsulation is done primarily to avoid the use of leased line and GT tampering. As will be apparent to one of ordinary skill in the art, the SPRS router (106) can encapsulate the signaling messages using various existing techniques. Some examples of these encapsulation techniques include, but are not limited to:

• An IP connection to send the signaling message through an IP protocol (for example, Short Message Port-to-Port (SMPP), Hypertext Transfer Protocol (HTTP), Socket, SIGTRAN, etc.), • A format of MAP-SS7 message per SS7 connection (possibly over IP, for example SIGTRAN), • Routing prefixes where the CdPA of the signaling message has the destination prefix of the SPRS hub (108), • Simple message transfer part (MTP) level routing of the signaling message over a commissioned connection (eg leased line), and • An international signaling point code to route the signaling message to the SPRS hub ( 108).

Once the SPRS hub (108) receives the encapsulated signaling messages, it de-encapsulates them before relaying them to the HSRP network. The SPRS hub (108) then allows the exchange of subsequent signaling messages between the client network (102) and the HSRP network for the required roaming agreement. Accordingly, the host network (104) expands the roaming relationships of the client network (102) to support both the sender and receiver roamers of this client network (102). For outgoing roaming, the sender roamer of the client network (102) uses a dual mode IMSI SIM containing a host IMSI (hereinafter referred to as IMSI-H) and a client IMSI (hereinafter referred to as IMSI-C) to transit over the HSRP network, according to an embodiment of the present invention. Hereinafter, this case of outbound roaming is referred to as "IMSI dual mode solution for outbound roaming". Furthermore, in another embodiment of the present invention, the sender roamer uses his client SIM containing the IMSI-C to roam the HSRP network. Hereinafter, this case of outbound roaming is referred to as "individual IMSI solution for outbound roaming".

Outbound roaming solutions

Various embodiments of the IMSI dual-mode solution of the present invention for managing partial roaming scenarios are the same as those for the IMSI dual-mode solution from the previous SPRS file. However, some configurations are made in the HSRP and host networks (104) to manage the "individual IMSI solution for outbound roaming" solution of the present invention. In one embodiment of the present invention, the client network operator (102) selects some HSRP networks to implement individual IMSI logistics. The single IMSI solution does not require the sending roamer to change their client network SIM (102), thereby avoiding interactions of a dual IMSI SIM application with existing SIM applications. However, the host network (104) needs to provide the client network information (102) (such as IMSI-C, SMSC-C (118), SCP-C (116), etc.) to its HSRP networks over various IR PRDs. 21, AA. 13, AA. 14, AA. 19, AA. 31, etc., of the GSMA (GSM association). Since the GMSA BARG group BA.21 document for "inbound roaming network extension" may contain such a client network information provisioning process (102), the individual IMSI solution for outbound roaming can be taken and added .

Therefore, to manage the individual IMSI solution for outbound roaming, the HSRP network operator configures its VMSC / VLR in case of GSM overlay roaming (or HSRP SGSN of the sending roamer in case of GPRS overlay roaming) with IMSI analysis in a Mobile Country Code (MCC) or Client Network Mobile Phone Network Code (MNC) (102) to associate in one of two ways:

1. To an address of the SPRS hub (108), and

2. To an NDC of the client network CC (102).

Also, the HSRP SGSN or the host SGSN need to devise a path (for example, through an internal DNS or a GRX DNS (GPRS roaming exchange)) to perform DNS resolution on an access point number ( APN) of client network (102) to access the data packet of the GGSN-C (126).

Furthermore, when the client network operator (102) requires a GSM roaming agreement with the HSRP network operator, this operator needs to configure its HSRP STP to modify the GT in order to route the signaling messages destined for the client network ( 102) to the SPRS hub (108). This is done by changing "SCCP CdPA = <NDC of client network CC (102)> <remainder of GT>" to "SCCP CdPA = <NDC of host network CC (104)> <SPRS hub prefix (108)> <remainder of GT> ”. Such modification will manage the access cases to the E.164 number of the HLR-C (110) (for example, LUP, unstructured supplementary service data (USSD), supplementary services (SS), ISD-ACK etc.), to the SMSC -C (118) (for example, SMS MO, Fwd-SMS-ACK MT, etc.) and to SCP-C (116) (for example, Initial DP (IDP) for CAMEL, SmS, GPRS, etc.) by network roamer

ES 2 365 958 B2 client (102) in the HSRP network. The interconnection of SMS and SMS MO will also be managed by the sender roamer from the HSRP network to the client network (102). Since STPs can generally manage the GT extension above 18 digits, the HSRP network operator can add the host network CC NDC (104) and the SPRS hub prefix (108) to the CdPA used by the network. SCCP until the GT extension is 18 digits. However, in some cases such GT modification is not possible or the extent of the modified GT exceeds the limit that the HSRP STP can administer. In these cases, the SPRS concentrator (108) uses the TCAP parameters such as IMSI to reproduce the real CdPA as it happens with HLR, SMSC, SCP, VLR, VMSC, etc.

To deal with the case where the HSRP network already has a GSM roaming agreement with the client network (102), and the operator of this client network (102) requires CAMEL, GPRS or 3G through the host network operator (104), HSRP network needs to distinguish SCCP signaling between normal GSM and CAMEL / GPRS / 3G. This is achieved by having different types of IMSI analysis between the VMSC / VLR and the SGSN of the HSRP network, according to a first embodiment of the present invention. For example, the HSRP VMSC / VLR can use the client network CC NDC (102), while the HSRP SGSN can use the SPRS hub prefix (108). However, for the HSRP network to distinguish SMS and CAMEL messages between GSM and CAMEL bearer services, the HSRP SGSN and HSRP VMSC / VLR or a host SMSC corresponding to SMSC-C (118) and an SCP are used. host corresponding to SCP-C (116). Similarly, to manage the SMS interconnect messages are sent to an SMS interconnect gateway. In a second embodiment of the present invention, the HSRP network uses an extended STP to examine the SSN of the source party address (CgPA) and the CdPA of signaling messages destined for the client network (102). To distinguish 3G and CAMEL in MAP messages, the HSRP network operator requires the HSRP Extended STP or SGSN / VMSC / VLR which examines TCAP messages and offers differentiated routing based on different types of TCAP messages. This extended STP can be provided by the HSRP network operator or by a third-party network operator (eg, a GSMA-defined OC (open connectivity) hub or an international SCCP bearer). In one embodiment of the present invention, the HSRP network operator uses the existing extended STP to examine TCAP messages in order to manage the individual IMSI solution for outbound roaming.

The GSM and GPRS registration process of the sender roamer for the IMSI dual mode solution follows the previous SPRS file, where the SPRS node of said file functions as the SPRS concentrator (108). Similarly, the sender roamer's GSM and GPRS registration process for the individual IMSI solution follows the IMSI dual mode solution explained in the previous SPRS file, except that IMSI-H is replaced by IMSI-C. However, in an embodiment of the present invention for the individual IMSI solution, the SPRS concentrator (108) detects an attempted registration of the sender roamer in the HSRP network, where this subscriber uses the IMSI-C to register with the HSRP network. . Likewise, in this case, when the SPRS concentrator (108) receives the LUP message (or LUP-GPRS) from the HSRP VMSC / VLR, the SPRS concentrator (108) does not modify the CgPA of the LUP message used by the SCCP (that is, that is, the CgPA is set as the VLR of HSRP). Therefore, when the HLR-C (110) returns an ISD message to the HSRP VLR, the STP-C (114) relays it to the SPRS router (106). The detailed participation of the SPRS router (106) will later be shown in other outgoing roaming signal streams. Since the HLR-C (110) has the current location / address of the sending roamer (i.e. the VMSC / VLR / SGSN), it can determine the correct roaming profile to apply and assist those value-added applications (such as traffic routing, welcome SMS, prepaid for senders, etc.) which depend on the current location of the sender roamer.

Consequently, the SPRS router (106) facilitates the MT call to the sending roamer by exchanging the signaling messages between the HSRP network and the client network (102) through the SPRS hub (108) when these two networks do not have each other the required GSM agreement. Figure 4 depicts a flow chart for facilitating the MT call to the sender roamer using the dual mode IMSI SIM, according to an embodiment of the present invention. All call flows for outgoing roaming solutions consider the sending roamer as "A". When A is called by a calling party B, the GMSC-C (112) receives, in step 402, an IAM message (B, A) from the ISDN user part (ISUP). Next, in step 404, the GMSC-C (112) transmits an SRI (A) message of the MAP to HLR-C (110) of A. Then, the HLR-C (110) transmits a PRN of the MAP (IMSI-C) to the VMSC / VLR-S (405) associated with the HSRP network. Hereinafter, all network elements of the HSRP network are referred to with an "S" notation (for example, the VMSC of the HSRP network is referred to as VMSC-S). However, in steps 406 and 408, the STP-C (114) routes the signaling message destined for the HSRP network (ie, the PRN (IMSI-C)) to the SPRS router (106).

Therefore, this SPRS router (106) determines the required roaming agreement from the PRN message (i.e. GSM in this case) by examining the SSN of the CdPA used by the SCCp and the TCAP content of the PRN message (e.g. , 3G and CAMEL parameters). In a certain embodiment of the present invention, the SPRS router (106) determines using its database that there is a bilateral GSM roaming relationship between the client network (102) and the HSRP network, where this HSRP network is determined using the CC's NDC of VMSC / VLR-S (405). Accordingly, the SPRS router (106) forwards the PRN message to VMSC / VLR-S (405), and the standard MT call flow proceeds independently of the SPRS hub (108).

Furthermore, in another embodiment of the present invention, the SPRS router (106) determines that the required GSM roaming agreement does not exist between the HSRP network and the client network (102) and, therefore, the host network (104) is required. to support the required GSM roaming agreement. Consequently, in step 410, the SPRS router (106)

ES 2 365 958 B2 encapsulates the PRN message, and sends it to the SPRS hub (108). Hereinafter, all encapsulated signaling messages are represented by double back quotes (eg, "PRN (IMSI-C)"), according to various embodiments of the present invention. Next, in step 412, the SPRS concentrator (108) decapsulates the PRN message, modifies the CgPA of the SCCP from HLR-C (110) to the SPRS-HLR GT of the SPRS concentrator (108) and also changes the IMSI- C by IMSI-H before relaying the PRN message to VMSC / VLR-S (405). Then, in step 414, the VMSC / VLR-S (405) returns an HSRP roaming number such as the mobile station roaming number (MSRN) to the HSRP network in a PRN-ACK message from MAP to the hub. SPRS (108).

In a certain embodiment of the present invention, the SPRS concentrator (108) relays, in step 416, the PRN-ACK message to HLR-C (110). Then, in step 418, the HLR-C (110) sends an SRI-ACK (MSRN) message to GMSCC (112). In the event that the client network (102) already has the link path that goes directly from its network to the MSRN ranges of the HSRP network, in step 420, the GMSC-C (112) continues with the establishment IAM call (B, MSRN) to the VMSC / VLR-S (405).

On the other hand, in another embodiment of the present invention, when the client network (102) does not have any link path that goes directly from its network to the MSRN ranges of the HSRP network, after step 414, the SPRS concentrator (108 ) again sends a host roaming number, such as the host MSRN corresponding to the HSRP MSRN, to HLR-C (110). Then the HLR-C (110) sends the SRI-ACK (host MSRN) to GMSC-C (112). Subsequently, the GMSC-C (112) continues with the call setup IAM (B, host MSRN) towards the GMSCH (128). As will be apparent to a person skilled in the art, in the event that one or more host networks meet the required GSM roaming agreement of the client network operator (102), the MT call will be routed to the sender roaming subscriber through the GMSCs of the corresponding host networks. For example, if two host networks H1 and H2 simultaneously support (as mentioned above according to figure 2) the required GSM roaming agreement between the client network (102) and the HSRP network, the MT call will then be routed to subscriber A via GMSC of H1 and GMSC of H2. However, for the sake of convenience, we have considered a single hub on a single host network (that is, the SPRS hub (108) on the host network (104)). The GMSC-H (128) then routes the signaling message through a message interface to the SPRS hub (108), which then returns, through the message interface, the MSRN from HSRP to GmSC-H ( 128). The message interface can be, but is not limited to, ISUP, Intelligent Network (IN), Telephone User Part (TUP), etc. The GMSC-H (128) therefore routes the MT call with the HSRP MSRN to VMSC / VLR-S (405).

Similarly, the call flow for the MT call towards the sending roamer in the case of the individual IMSI solution for outgoing roaming follows the call flow explained above according to Figure 4, except that the IMSI-H is replaced by the IMSI- C.

The sending roamer can also receive SMS on the HSRP network as long as he is registered with this HSRP network. Figure 5 depicts a flow chart for providing SMS MT from SMSC-C (118) to the sender roamer using dual mode IMSI SIM, according to a first embodiment of the present invention. When the SMSC-C (118) receives the SMS MT from a sender B, the SMSC-C (118), in step 502, transmits an SRISM message (A) to HLR-C (110). Next, in step 504, the HLR-C (110) returns an SRI-SM-ACK message with the VMSC / VLR-S address (405) (or the host HSRP / SGSN SGSN address in case of GPRS) and the IMSI-C from A to SMSC-C (118) which forwards the SMS MT from IMSI-C to VMSC / VLR-S (405). However, in steps 506 and 508, the STP-C (114) routes the FwdSMS (IMSI-C) message destined for VmSc / VLR-S (405) to the SPRS router (106).

Next, the SPRS router (106) determines the required roaming agreement from the FwdSMS (IMSI-C) message in a manner similar to that explained above for the PRN message (according to FIG. 4). Subsequently, in step 510, the SPRS router (106) encapsulates the FwdSMS message, and sends it to the SPRS hub (108), when it has been determined that the required roaming agreement does not exist. Then, in step 512, the SPRS hub (108) decapsulates the FwdSMS message, modifies the CgPA of the SCCP from HLR-C (110) to the SPRS-HLR GT of the SPRS hub (108) and also changes the IMISI-C by IMSI-H before relaying the FwdSMS message to VMSC / VLR-S (405). Finally, in steps 514 and 516, the VMSC / VLR-S (405) returns a FwdSMSACK message from the MAP to SMSC-C (118) through the SPRS hub (108).

Similarly, the signal flow for the SMS MT towards the sender roamer in the case of the individual IMSI solution for outbound roaming follows the signal flow explained above according to Figure 5, except that the IMSI-H is replaced by the IMSI- C.

In some cases, sender B may belong to a different network than the client network (102). Figure 6 represents a flow chart to facilitate SMS MT using the interworking function of the SMSC (601) (hereinafter referred to as SMSC-I (601)) to the sender roamer using the dual mode IMSI SIM, according to a second embodiment of the present invention. When the SMSC-I (601) receives the SMS MT from sender B, this SMSCI (601), in step 602, transmits an SRI-SM message (A) to HLR-C (110). Then the HLR-C (110) returns the SRI-SM-ACK message to SMSC-I (601). In one embodiment of the present invention, the client network operator (102) configures the STP-C (114) to address all signaling messages (such as SRI-SM-ACK), originated in the client network (102) and destined to the non-client network SMSCs, to the SPRS router (106) when said non-client SMSCs have an SMS interconnection agreement with the client network (102). Since, the SMSC-I (601) is a non-client network SMSC that has an SMS interconnection agreement with the client network (102), in steps 604 and 606, the STPC (114) addresses the SRI-SM message -ACK to the SPRS router (106).

ES 2 365 958 B2

Next, the SPRS router (106) determines from the SRI-SM-ACK message if the HSRP network has the required roaming agreement with the client network (102) in a similar way to that explained above for the PRN message (according to the figure 4). When the SSN indicates a GSM relationship, the SPRS router (106) determines using its database that there is a bilateral GSM roaming relationship between the HSRP network and the client network (102). In this case, the SPRS router (106) forwards the message to SMSC-I (601) without any modification and follows the standard SMS MT flow. Therefore, in steps 608 and 610, the SPRS router (106) routes the received SRI-SM-ACK message to SMSC-I (601) through STP-C (114). Then the SMSC-I (601) routes the SMS MT directly to VMSC / VLR-S (405).

On the other hand, in case the SPRS router (106) determines using its database that the required GSM / GPRS / CAMEL / 3G roaming agreement does not exist, this SPRS router (106) determines, from its database , the host network (104) is sponsored. Then, in steps 612 and 614, the SPRS router (106) modifies the SRI-SM-ACK message (IMSI-C, VMSC / VLR-S) to a SRI-SM-ACK message (IMSI-H, SPRS-VMSC / SPRS-VLR), and routes the modified message to SMSC-I (601) through STP-C (114). The VMSC / VLR-S address (405) in the SRISM-ACK message corresponds to the usual VMSC / VLR address of the sending roamer, and the SPRSVMSC / SPRS-VLR address corresponds to the VMSC / VLR address associated with the hub SPRS (108), according to an embodiment of the present invention. On the other hand, the SPRS router (106) only changes the IMSI-C to IMSI-H in the SRI-SM-ACK message. As will be apparent to a person skilled in the art, in the case of GPRS, VMSC / VLRS (405) and SPRS-VMSC / SPRS-VLR will be replaced by SGSN from HSRP and SPRS-SGSN associated with the SPRS hub (108), respectively. . Additionally, in steps 616 and 618, SMSC-I (601) forwards the IMSIH SMS MT to VMSC / VLR-S (405) through SPRS hub (108). Finally, in steps 620 and 622, VMSC / VLR-S (405) sends a FwdSMS-ACK message to SMSC-I (601) through SPRS hub (108).

Similarly, the signal flow for SMS MT from SMSC-I (601) to the sending roamer in the case of the individual IMSI solution for outbound roaming follows the signal flow explained above according to Figure 6, except that the IMSI-H it is replaced by IMSI-C.

Apart from MT activities, the sender roamer can also perform MO activities in the HSRP network. Fig. 7 depicts a flow chart for facilitating GPRS MO or SMS MO or CAMEL-based MO call by the sending roamer using the IMSI SIM dual mode, according to an embodiment of the present invention. When, in step 702, the GPRS MO, SMS MO, or CAMEL-based MO call is received at the VMSC / VLRS (405), the VMSC / VLRS (405) sends an SSP-SCP CAP message (e.g. Initial DP (IDP) , basic call status event notification model (ERB), and its equivalents in SMS and GPRS) to the SPRS concentrator (108). The SSP-SCP CAP message corresponds to a CAP message that is originated at the SSP node and terminated at an SCP node. Previously, during the outgoing roamer registration process with the HSRP network, the SPRS hub (108) modified an SCP address in a CSI (if any) in the SPRS hub's ISD to GT message profile information (108) (hereinafter referred to as SPRS-SCP) which corresponds to SCP-C (116). Then, when the SPRS hub (108) receives the IMSI-H and SPRS-SCP parameters (if they exist) from the CAP message from SSP-SCP, the SPRS hub (108) modifies them to IMSI-C and SCP-C (116) , respectively, where the CgPA of the SCCP is changed from VMSC / VLR-S address (405) to SPRS-VMSC / SPRS-VLR address (or SPRS-SGSN in case of GPRS). In step 704, the SPRS hub (108) sends the modified SSP-SCP CAP message to SCPC (116) which returns an SCP-SSP CAP message, in step 706, (e.g. continue, connect, control release, cancel and their equivalents in SMS and GPRS) to the SPRS hub (108). The SCP-SSP CAP message corresponds to a CAP message that originated at the SCP node and terminated at the SSP node. Finally, in step 708, the SPRS concentrator (108) modifies the SCCP's CgPA to SPRS-SCP and the SCCP's CdPA to VMSC / VLR-S (405) and relays the modified SCP-SSP CAP message to VMSC / VLR-S (405).

The signal flow for the SMS MO by the sending roamer in the case of the IMSI dual mode solution for outgoing roaming follows the signal flow of the CAMEL-based MO call explained above according to Figure 7, except that the CAP messages of SSP-SCP and SCP-SSP CAP are replaced by FwdSMS and FwdSMSACK messages, respectively. As will be apparent to a person skilled in the art, in this case of SMS MO, the SCP-C (116) is replaced by the SMSC-C (118).

Similarly, the signal flow for SMS MO and CAMEL / SMS / GPRS MO-based call by the sending roamer in the case of the individual IMSI solution for outbound roaming follows the signal flow of the IMSI dual mode solution for outbound roaming such and as explained above, except that IMSI-H is substituted for IMSI-C. However, in one embodiment of the present invention, the SPRS concentrator (108) does not modify the SCCP CgPA for the SSP-SCP CAP message which is received from the VMSC / VLR-S (405) and therefore , relays it directly to the client network (102). In this case, when the STP-C (120) receives the CAP message from SCP-SSP from the SCP-C (116) that is destined for the HSRP network, the STP-C (120) routes the CAP message from SCP- SSP to SPRS hub (108) through SPRS router (106).

Here are some common signal flows for both IMSI dual mode and single IMSI SIM solutions. Figure 8 depicts a flow chart of HLR-C RESET while the sender roamer of the client network (102) is registered with the HSRP network using an IMSI-H or an IMSIC, according to an embodiment of the present invention. In step 802, the HLR-C (110) restarts and therefore RESET (IMSI-client list, HLR-C) is received at the STP-C (114) from the HLR-C (110), where the SCCP CgPA is HLR-C (110) and SCCP CdPA is VMSC / VLR-S (405). Then, in step 804, the STP-C (114) redirects the received RESET message destined for the HSRP network to the SPRS router (106). Then this SPRS router

ES 2 365 958 B2 (106) determines the required roaming agreement from the RESET message in a similar way to that explained above for the PRN message (according to figure 4). Subsequently, in step 806, the SPRS router (106) encapsulates the RESET message, and sends it to the SPRS hub (108), when it has been determined that the required roaming agreement does not exist. Next, in step 808, the SPRS concentrator (108) decapsulates the REINICO message, modifies the CgPA of the SCCP from HLR-C (110) to GT of SPRS-HLR from the SPRS concentrator (108) and also changes the IMSI list -client by IMSI-host list (ie in case the sending roamer is using IMSI SIM dual mode) before relaying the RESET message to VMSC / VLR-S (405). The IMSI-host list is the list of host network IMSIs (104) that corresponds to the IMSI-client list. On the other hand, in the event that the outgoing roamer is using its client network SIM (102), the SPRS concentrator (108) decapsulates the RESET message without modifying the IMSI-client list, and sends this decapsulated message to VMSC / VLR-S (405).

Various steps of the signal flow of an independent ISD message from HLR-C (110) to VMSC / VLR-S (405) (or the HSRP SGSN) follow those of the signal flows of the RESET message explained above according to figure 8 The independent ISD message corresponds to a message that the HLR-C (110) sends to the VMSC / VLR-S (405) after completing the LUP process of the sending roamer. However, one of the following two steps will be performed once the SPRS hub (108) decapsulates the ISD independent encapsulated message (profile) received from the SPRS router (106):

1. In case the sending roamer is using the client network SIM (102), the SPRS hub (108) sends the ISD independent encapsulated message profile to VMSC / VLR-S (405). This profile is the modified information of the profile, according to an embodiment of the present invention. In one example, the SPRS hub (108) can modify the SCP-C address (116) in the profile information to SPRS-SCP which corresponds to SCP-C (116). In another example, the SPRS hub (108) modifies the profile in the ISD message to replace the client APN with a host APN (which corresponds to the client APN) when the data connection (i.e. GPRS) between the HSRP network and the client network (102) needs to be established through the host network (104).

2. In case the sending roamer is using the IMSI SIM dual mode, the SPRS concentrator (108) sends an ISD independent encapsulated message profile to VMSC / VLR-S (405). In one example, the SPRS hub (108) modifies the profile in the ISD message to replace the client APN with the host APN when the client APN has the same name as the host APN or the data connection between the HSRP network and the network Client (102) needs to be established through the host network (104).

Inbound roaming solution

This section describes the signal flows for the mobile communication of the client network receiver roamer (102) from the HSRP network, where the receiving roamer uses his HSRP IMSI (hereinafter referred to as IMSI-S) to transit through the client network (102). This solution is referred to hereinafter interchangeably as "individual IMSI solution for inbound roaming". Various embodiments of the individual IMSI solution for inbound roaming of the present invention for managing the partial roaming situation are the same as those for the individual IMSI solution for inbound roaming of the previous SPRS record. We will assume that in various inbound roaming call flows the client network (102) overlaps the host network's roaming agreement (104) with the HSRP network to allow the receiving roamers to transit, from the HSRP network, in the network. customer (102). A flow chart for registering the receiving roamer in the client network 102 using the HSRP network SIM, according to a first embodiment of the present invention, is depicted in Fig. 9. When the receiving roamer tries to register with the client network (102), the VMSC / VLR-C (120) transmits a LUP message on the IMSI-S to an HLR-S (901). Since the SCCP CdPA cC NDC (i.e. the VMSC / VLR-C HSRP network (120)) has no bilateral GSM / GPRS / CAMEL / 3G roaming agreement with the client network (102), the STP-C (114) that receives the LUP message from the VMSC / VLR-C (120), redirects, in steps 902 and 904, the received message to the SPRS router (106).

Next, the SPRS router (106) detects the recipient roamer's attempted registration in the client network (102) and determines the required roaming agreement from the LUP message. Subsequently, in step 906, the SPRS router (106) encapsulates the LUP message, and sends it to the SPRS hub (108), when the absence of the required roaming agreement has been determined. The SPRS concentrator (108) then detects the recipient roamer's attempted registration in the client network (102) after receiving the encapsulated LUP message. Later, in step 908, the SPRS concentrator (108) decapsulates the encapsulated LUP message, modifies the MAP parameter of VMSC / VLR-C in the SPRS-VMSC / SPRS-VLR message LUP to GT of the SPRS concentrator (108) and SCCP CgPA from VLR-C (120) to SPRS-VLR, before forwarding the LUP message to HLR-S (901). Then, in step 910, the HLR-S (901) again sends an ISD message (profile) to the SPRS hub (108). In one embodiment of the present invention, the SPRS hub 108 modifies the ISD message profile information as described above for the outbound roaming solutions of the present invention. Therefore, in step 912, the SPRS hub (108) sends the modified ISD message profile information to VMSC / VLR-C (120) after modifying the CgPA from the SCCP to SPRS-HLR or maintaining the same CgPA. of the SCCP than that of the HLR-S (901). Subsequently, in steps 914 and 916, the VMSC / VLR-C (120) sends an ISD-ACK message to HLR-S (901) through the SPRS hub (108). Then, in step 918, the HLR-S (901) confirms the registration of the sending roamer by sending a LUP-ACK message with the HLR-S address to the SPRS concentrator (108). Finally, in step 920, the SPRS hub (108) relays the LUP-ACK message to VMSC / VLR-C (120), where the CgPA

The SCCP ES 2 365 958 B2 and the HLR-S address are set as SPRS-HLR or HLR-S address. As will be apparent to a person skilled in the art, in the case of GPRS, VMSC / VLR-C (120) and SPRS-VMSC / SPRS-VLR will be replaced by SGSNC (124) and SPRS-SGSN, respectively.

In one embodiment of the present invention, although the client network operator (102) already has GSM and GPRS roaming agreements with the HSRP network operator, it may nevertheless require CAMEL agreement with the HSRP network operator to support the subscribers. roaming prepaid CAMEL receivers from this HSRP network. The client network (102) can achieve said CAMEL roaming agreement by overlapping that of the host network (104) with the HSRP network. As mentioned above, the SPRS router (106) can segregate the CAP interface based on the SSN of the CdPA: However, the CAMEL parameters can be embedded in a MAP transaction of the GSM (or GPRS), and could be removed during a GSM (or GPRS) LUP process in the client network (102) when there is no bilateral CAMEL agreement between the client network (102) and the HSRP network. To solve this problem, the client network operator 102 first needs to enable CAMEL support for receiving roamers from the HSRP network. In one embodiment of the present invention, the client network operator (102) configures its STP-C (114) to route a TCAP message, corresponding to the receiving roamer, to the SPRS router (106) when CAMEL support is enabled for the receiving roamer and the TCAP message CC NDC indicate that there is no CAMEL agreement between the client network (102) and the HSRP network. In this case, the STP-C (114) routes the TCAP message regardless of whether the client network (102) already has GSM and GPRS roaming agreements with the HSRP network.

Figures 10A and 10B depict a flow chart for first routing the CAMEL-supported receiving roamer record in the client network (102) to an SPRS hub (108), according to a second embodiment of the present invention. When the receiving roamer tries to register in the client network (102), the VMSC / VLRC (120) transmits a LUP message on the IMSI-S with CAMEL and the VMSC / VLR-C address (120) as parameters to HLR-S (901). Steps 1002 and 1004 are the same as Steps 902 and 904, where the STP-C (114) redirects the LUP message to the SPRS router (106). However, in step 1006, the SPRS router (106) detects the recipient roamer's attempted registration in the client network (102), saves the LUP message (which could also include CAMEL support phases), encapsulates it, and finally sends the encapsulated LUP message to the SPRS hub (108). As will be apparent to a person skilled in the art, the presence of CAMEL parameters in the LUP message indicates that there is CAMEL roaming support in the client network (102).

Then, the SPRS router (106) identifies that the required CAMEL roaming agreement does not exist between the client network (102) and the HSRP network. Next, in step 1008, the SPRS concentrator (108) decapsulates the encapsulated LUP message and sends it to HLR-S (901) and then, in step 1010, the HLR-S (901) returns the ISD message (profile ) to the SPRS concentrator (108). In a certain embodiment of the present invention, the profile information received from the ISD message at the SPRS concentrator 108 does not contain a CAMEL profile (such as CSI, etc.), that is, the receiving roamer is not a CAMEL roamer, and, therefore, it is a non-preferred roamer for the client network operator (102). In this case, the SPRS hub (108), with TCAP content, aborts the TCAP transaction with the HLR-S (901). Therefore, in step 1012, the SPRS hub (108) sends an abort TCAP message to HLR-S (901). Then, the SPRS hub (108) informs the SPRS router (106) of the abort command through an encapsulation interface with the SPRS router (106). In one embodiment of the present invention, the host network operator (104) configures the SPRS hub (108) to encapsulate the signaling messages destined for the SPRS router (106), such as "proceed normal with LUP" and "release saved LUP." , before relaying these messages to the SPRS router (106). Accordingly, in steps 1014 and 1016, the SPRS hub (108) sends the messages "proceed normal with LUP" and "release saved LUP" to the SPRS router (106). The message "proceed normal with LUP" indicates that the receiving roamer is non-preferred and therefore the SPRS router (106) diverts the saved LUP message (that is, it has been saved after step 1004) to the HSRP network. . This means that the standard LUP process is followed, where the SPRS router (106) relays the saved LUP message to HLR-S (901) with the CgPA set to VMSC / VLR-C (120) and then other exchanges are made. log messages (that is, ISD, ISD-ACK, and LUP-ACK) directly between HLR-S (901) and VMSC / VLR-C (120).

However, if the profile information in the ISD message (in step 1010) contains the CAMEL profile, that is, the receiving roamer is a CAMEL roamer and therefore a preferred roamer for the client network operator (102), the SPRS hub (108) then informs the SPRS router (106) about the release of the saved LUP message through the encapsulation interface with the SPRS router (106). This release indication allows the SPRS router (106) to determine that the receiving roamer is a preferred roamer and thus that sponsorship of the host network (104) is required in this case. Then steps 1018 to 1026 are carried out which are the same as steps 912 to 920, where ISD, ISD-ACK and LUPACK messages are exchanged between VMSC / VLR-C (120) and HLR-S (901) through the SPRS concentrator (108).

Instead of routing the LUP message first through the SPRS (108) hub path and then the two-sided (or SPRS hub (108)) path (i.e., as shown in Figures 10A and 10B) , the SPRS router (106), in an alternative method, first routes the LUP message through the bilateral route and depending on the LUP response, then routes the SCCP signaling corresponding to the LUP process through the SPRS hub (108) or the bilateral route. Figures 11A and 11B depict a flow chart for first routing the receiving roamer's record directly to the HSRP network, according to a third embodiment of the present invention. When the receiving roamer tries to register in the client network (102), the VMSC / VLR-C (120) transmits the LUP message on the IMSI-S with CAMEL and VMSC / VLR-C (120) parameters to HLR-S ( 901). Steps 1102 and 1104 are the same as Steps 1002 and 1004, where STP-C (114) redirects the received LUP message

ES 2 365 958 B2 from VMSC / VLR-C (120) to SPRS router (106). Then, in step 1106, the SPRS router (106) relays the received LUP message directly to HLR-S (901), after modifying the SCCP's CgPA to the recipient roamer's SPRSVMSC / VLR router address.

Then, in step 1108, the HLR-S (901) returns the ISD message (profile) to the SPRS router (106). In one embodiment of the present invention, the SPRS router (106) examines the ISD message profile and records that the receiving roamer is not a CAMEL (and therefore non-preferred) subscriber. In another embodiment of the present invention, the SPRS router (106) examines the ISD message profile and records that the receiving roamer is a CAMEL (and therefore preferred) roamer. If preferred, the SPRS router (106) modifies, in step 1110, the profile information of the iSd message, and sends the modified ISD message to VMSC / VLR-C (120), after modifying the CgPA of the SCCP to address SPRS-HLR router of the receiving roamer. Later, in steps 1112 and 1114, the VMSC / VLR-C (120) returns the ISD-ACK message to HLR-S (901) through the SPRS router (106). When, in step 1116, the SPRS router (106) receives the LUP-ACK message (HLR-S) from HLR-S (901), the SPRS router (106) sends, in step 1118, an error message, such as an abort TCAP message, a cancel MAP location message, or a LUP-ACK (error) message to VMSC / VLR-C (120) to abort the receiving roamer's registration attempt at VMSC / VLR-C (120 ). The error message sent in the LUP-ACK message is, but is not limited to, system failure (SF), unexpected data value (UDV), and lost data (MD). This technique of aborting roaming subscriber registration with the client network (102) is similar to that of redirecting traffic taught by the inventor of US Patent Application No. 10 / 635,804 filed on August 5, 2003.

As will be apparent to one of ordinary skill in the art, a handset attempts to register with another network after all four registration attempts with a particular network have failed. Since the receiving roamer's handset has attempted to register only once with the client network (102), it retries another LUP attempt on that network (102). In this case, steps 1120 to 1122 (the same as steps 1102 and 1104, respectively) are carried out, where the SPRS router (106) receives the LUP message from VMSC / VLR-C (120) through STP -C (114). In the event that the SPRS router (106) has already determined that the receiving roamer is a non-preferred roamer (i.e., in step 1108), this router (106) then forwards the new LUP message (i.e. Subsequent LUP) directly to HLR-S (901). The standard LUP process is then followed where the log messages are exchanged directly between HLR-S (901) and VMSC / VLR-C (120). On the other hand, in the event that the SPRS router 106 determines that the receiving roamer is a preferred roamer, steps 1124 to 1138 are performed (the same as steps 906 to 920, respectively), where the message LUP is received at HLR-S (901), which exchanges ISD, ISD-ACK and LUP-ACK messages with VMSC / VLR-C (120) through SPRS concentrator (108).

In some cases, the client network operator (102) may overlap the host network (104) to thereby establish CAMEL prepaid roaming with some HSRP networks. In such cases, the SPRS router (106) applies logic to determine if the CAMEL roamer is prepaid and, if so, routes the CAMEL roamer signaling to the HSRP network through the SPRS hub (108). The SPRS router (106) can apply this logic via the HSRP network operator for prepaid and / or contract roamers CAMEL. Once the CAMEL roamer type has been determined, and if it is not the one desired by the client network operator (102), the SPRS router (106) initiates the bilateral route of the saved LUP message or subsequent LUP as shown. described above. For example, in the case that the client network operator (102) only wants prepaid CAMEL roamers, if the CAMEL roamer is contract, the SPRS router (106) routes the saved LUP message or subsequent LUP through the bilateral route. In a certain embodiment of the present invention, the SPRS router (106) determines whether a CAMEL roamer is prepaid or contract using a service key, an IMSI, an MSISDN, or an SCP address. In another embodiment of the present invention, a default roamer type is assumed, if not determinable.

As described above according to Figures 11A and 11B, the SPRS router (106) can route the registration signaling messages to the HSRP network first through the two-way path or the SPRS hub (108) and then over the SPRS hub (108) or the bilateral route. In this case, the SPRS router (106) sends error messages (i.e. abort TCAP, CancelLoc (cancel paging), or LUP-ACK (error)) to VMSC / VLR-C (120) and routes the subscriber's subsequent LUP receiver roamer to the HSRP network through the SPRS hub (108), when the ISD, LUP-ACK or CancelLoc message during the first registration attempt of the receiver roamer in the client network (102) shows, but is not limited to, any of the following indications:

• Illegal Roaming (RNA), System Failure (SF), Unexpected Data Value (UDV) and Lost Data (MD) in LUP-ACK or CancelLoc message, or restricted roaming due to unsupported function (RRDuF) on the ISD message. For example, when the HSRP network only allows prepaid roaming in networks that have a CAMEL agreement with the HSRP network and the client network (102) does not have this agreement with said HSRP network, • Blocking for a specific operator (ODB) for MO calls by the receiving roamer of the HSRP network, and • Call blocking (CB) for MO calls by the receiving roamer.

The above indications allow the SPRS router (106) to determine that the receiving roamer is the preferred prepaid roamer of the client network (102). This preferred prepaid roamer determination should be applied with caution, as many network operators allow their roamers (including

ES 2 365 958 B2 contract) CAMEL support real-time billing, Virtual Personal Environment (VHE) services, fraud control, home routing, and Calling Line Identification (CLI) broadcast. The customer network operator 102 needs, before applying this technique, to ensure that the HSRP network provides only CAMEL services to its prepaid roamers. In some cases, the HSRP network may even apply the addressing mechanism to move its sender roamers to networks that support CAMEL agreements with this HSRP network.

Furthermore, in one embodiment of the present invention, the host network operator (104) configures its SPRS hub (108) to convert CAMEL versions (e.g., CAMEL phase I to CAMEL phase III) while the LUP message is retransmitted. through the SPRS concentrator (108). In this case, the CAP transactions that are relayed through the SPRS hub (108) are converted to the corresponding version supported by the service switching function (SSF) or the service control function (SCF) of the HSRP network. This allows the host network (104) to make the HLR-S (901) perceive that the client network (102), with which the receiving roamer is registered, has CAMEL support (with the same version as the network HSRP) and CAMEL agreement with the HSRP network.

In one embodiment of the present invention, although the client network 102 already has bilateral GSM roaming agreements with HSRP network operators, some of these operators may prevent certain class of sender roamers (e.g. roaming subscribers receiving high-end voice and data services in the case of Blackberry) register with the GSM roaming of the client network (102) in the event that this class of roaming subscribers is better served by a network that has more agreement Advanced roaming (s) with these HSRP networks than the client network (102). In an example scenario, some HSRP network operators (for example, Wireless ATT, CSL) prevent their Blackberry subscribers from registering with a GSM network (even with manual selection of the GSM network, such as China Unicom) you don't have GPRS roaming agreement with them. In another example scenario, some HSRP network operators (eg European operators) prevent their prepaid CAMEL subscribers from registering with the GSM network (even with manual selection) that does not have a CAMEL agreement with them. As a result, such GSM network operators lose some classes of roamers. In fact, these GSM network operators may possibly end up losing the majority of their prepaid roaming subscriber base to HSRP network operators.

To solve the aforementioned problems, the client network operator (102) detects (for example, through monitoring) or knows in advance that the HSRP network sends RNA to the client network (102) for a class of roaming subscribers from the HSRP network because there is no required roaming agreement (eg GPRS or CAMEL), according to an embodiment of the present invention. In this case, the client network operator (102) configures its STP-C (114) to route the E.214 signaling message from the SCCP (for example, LUP) destined for the HSRP network, to the SPRS router (106) , when the HSRP network applies traffic routing (for example, by sending RNA to the client network (102) in response to the LUP attempt on said network (102)) on some kind of roamers trying to register with the network customer (102). This traffic routing allows the HSRP network operator to prevent said class of roamers from registering with the client network (102) by redirecting them to another network other than this client network (102). This case considers the receiving roamer of the HSRP network as one of those belonging to said class of roamers.

Therefore, when the receiving roamer tries to register with the client network (102), the STP-C (114) redirects the LUP message destined for the HSRP network and received from VMSC / VLR-C (120), to the SPRS router ( 106). Next, this router (106) saves the received LUP message with its own GT as CgPA even though there is a bilateral GSM agreement between the client network (102) and the HSRP network. As described above according to Figures 10A, 10B, 11A and 11B, the SPRS router (106) routes the encapsulated LUP message to the HSRP network either directly or through the SPRS hub (108). Subsequently, if the LUP response is RNA (that is, the receiving roamer can be redirected to a different network than the client network (102)), the SPRS router (106) routes the saved LUP message to the HSRP network through the SPRS hub (108) or sends a reject LUP message with a no RNA error (for example, SF, UDV, or CancelLoc), to VMSC / VLR-C (120) to thereby force the receiving roamer's mobile device to attempt another LUP attempt on the client network (102). In the latter case, the SPRS router (106) routes the subsequent LUP message to the HSRP network through the SPRS hub (108).

Since the client network (102) is not sure about the cause for RNA, according to an embodiment of the present invention, the SPRS router (106) selects, from several available SPRS hubs, a list of them to route the messages. signaling signaling roamer (as LUP message). In one embodiment of the present invention, the SPRS router (106) attempts this routing of signaling messages to multiple SPRS hubs until one of them completes the registration of the receiving roamer with the client network (102) or all SPRS hubs. fail to complete the registration of this receiving roamer with said client network (102). In the first case, the SPRS router 106 stores the appropriate SPRS hub to route subsequent signaling messages from the receiving roamer to this SPRS hub. In one embodiment of the present invention, the SPRS router (106) routes the receiving roamer signaling through the appropriate hub for a configurable period of time that is defined by the client network operator (102). In the latter case, the SPRS router (106) stores the receiving roamer as non-preferred and consequently retransmits the received RNA response in the next LUP response to VMSC / VLR-C (120). In one embodiment of the present invention, the SPRS router (106) relays all future RNA responses from the receiving roamer's LUP attempt in the client network (102), to VMSC / VLR-C (120) for a configurable period of time. which is defined by the client network operator (102).

ES 2 365 958 B2

In some cases, the HSRP network operator applies roaming addressing (SoR) techniques to redirect roamers trying to register with the client network (102) to preferred networks even though there is a bilateral GSM agreement between the client network (102 ) and the HSRP network. As a result, the client network operator 102, which becomes a non-preferred operator of the visited network for the HSRP network operator, loses the roaming revenue of the roamers from the HSRP network. Therefore, to solve this problem, the client network operator (102) applies an anti-SoR technique to oppose the SoR of the HSRP network, without violating the BA.30 and IR.73 standards of the GSMA which do not They allow a visited network operator to apply opposition measures that directly override the SoR. In this anti-SoR technique, the SPRS router (106) applies the logic in a similar way as explained above for the roamer class. Similarly, the technique for managing roaming subscribers from the HSRP network who have had SoR applied with a non-RNA error (e.g. SF, UDV, CancelLoc, etc.) is the same as the aforementioned roaming. partial for roamer class.

Furthermore, as described above according to Figures 10A and 10B, various steps of the signal flow for the registration process of the receiving roamer with 3G support in the client network (102) are the same as those of the signal flow for the registration process of the receiving roamer with CAMEL support in the client network (102). In the case of receiving roamer with 3G support, the client network operator (102) configures its STP-C (114) to route a TCAP message corresponding to the receiving roamer, to the SPRS router (106) when 3G support is enabled of the receiving roamer and the CC's NDC in the TCAP message indicates that there is no 3G agreement between the client network (102) and the HSRP network. In this case, the STP-C (114) routes the TCAP message to the SPRS router (106) regardless of whether the client network (102) already has GSM and GPRS roaming agreements with the HSRP network. Also, the SPRS concentrator 108 determines whether the receiving roamer is a 3G roamer using the profile information from the ISD message (i.e., the receiving roamer is a 3G roamer if the profile information contains 3G profile as services. bearers (BS) n = 30), as described above according to Figures 10A and 10B for the CAMEL roamer.

Furthermore, the receiving roamer in the client network (102) can also receive SMS and calls while registered with said client network (102). The signal flow of the SMS MT and the MT call of the receiving roamer follows the signal flow corresponding to the SMS MT and the MT call explained in the previous SPRS record, in which the SPRS node operates similarly to the SPRS hub. (108).

Apart from MT activities, the receiving roamer in the client network (102) can also perform various MO activities. Figure 12 depicts a flow chart for facilitating GPRS MO, SMS MO, or CAMEL-based MO call by the receiving roamer in the client network (102), according to an embodiment of the present invention. When the VMSC / VLR-C (120) receives GPRS MO, SMS MO or CAMEL-based MO call, it sends the CAP message of the SSP-SCP with the CdPA of the SCCP of an SCP associated with the HSRP network (hereinafter referred to as SCP-S (1201)). Since the SCCP CdPA CC NDC (i.e., the SCP-S HSRP network (1201)) does not have a bilateral GSM / GPRS / CAMEL / 3G roaming agreement with the client network (102), the STP -C (114) that receives the LUP message from VMSC / VLR-C (120) redirects the received message to the SPRS router (106) (steps 1202 and 1204). Next, the SPRS router (106) determines the required roaming agreement from the SSP-SCP CAP message. Subsequently, in step 1206, the SPRS router (106) encapsulates the CAP message from SSP-SCP, and sends it to the SPRS hub (108), when it has been determined that the required roaming agreement does not exist.

Then, in step 1208, the SPRS concentrator (108) decapsulates the message "CAP from SSP-SCP", and modifies the CgPA of the SCCP from VMSC / VLR-C (120) to SPRS-VMSC / SPRS-VLR, before of relaying the CAP message from SSP-SCP to SCP-S (1201) which sends it, in step 1210, to the SPRS hub (108). Finally, in step 1212, the SPRS concentrator (108) relays the received SCP-SSP CAP message to VMSC / VLR-C (120), after modifying the CgPA from the SCCP to SPRS-SCP.

The signal flow for the receiving roamer's SMS MO follows the signal flow of the CAMEL-based MO call explained above according to Figure 12, except that the CAP messages from SSP-SCP and SCP-SSP are replaced by FwdSMS messages. and FwdSMS-ACK, respectively. As will be apparent to a person skilled in the art, in this case of SMS MO, the SCP-S (1201) is replaced by an SMSC associated with the HSRP network.

On the other hand, the GPRS activation signal flow and PDU transfer in case of the IMSI dual mode solution for outgoing roaming and the individual IMSI solution for inbound roaming (both subscribers and network initiated) follows the signal flow of the solutions corresponding to the previous SPRS file. Also, the GPRS activation and PDU transfer signal flow for the individual IMSI solution for outbound roaming (both subscribers and network initiators) follows the signal flow for the IMSI dual mode solution for outbound roaming from the previous SPRS file. However, in the individual IMSI solution for outbound roaming of the present invention, the host APN and the IMSI-H are replaced by the client APN and IMSI-C, respectively.

Billing

The partial roaming billing process involves splitting the detailed call record (CDR) by the TAP procedure (Transferred Accounts Procedure). In order to manage the recipient roaming subscribers of the client network (102), the operator of said network (102) separates the CDRs for bilateral roaming agreements from the CDRs for the roaming agreements required of the client network operator (102), that is, I agree

ES 2 365 958 B2 two sponsored by the host network (104). The client network operator (102) distinguishes the different types of CDRs through their corresponding indicators, for example, GPRS through GPRS fields (for example, APN, SGSN, etc.), CAMEL through CAMEL fields (for example, number connected by CAMEL , CAMEL support phase, etc.), 3G via 3G fields (eg BS n = 30 in bearer information). Then, the client network operator (102) sends the CDRs for bilateral roaming agreements to the TAP processor through the bilateral interoperator rate (IOT) using the code of the Transferred Account Data Interchange Group, TADIG) of the HSRP network operator and the TADIG code of the client network operator (102). However, the client network operator (102) sends the CDRs for the required roaming agreements of the client network operator (102) to the same TAP processor through different IOTs stipulated by the HSRP network operator. Furthermore, in this case of required roaming agreements, the host network operators (104) and client network (102) use the TADIG codes of the HSRP network and client network operators (102) (the client network TADIG code ( 102) is normally different from the standard TADIG code) for the purpose of overlay. On the other hand, following the standard document BA.21 of the GSMA this IOT can be that of the host network operator (104) with respect to the HSRP network operator or that of the client network operator (102). Overlapping TAP files from different host networks are sent to their respective host networks, which then forward them to the HSRP network operators. HSRP network operators pay the host network operators who ultimately pay the benefits to the client network operator (102). In this inbound roaming scenario, the host network operators bear the responsibility for fraud (eg heavy usage report) from the client network operator (102).

Furthermore, according to an embodiment of the present invention, where the client network (102) already has a direct bilateral GSM roaming relationship with the HSRP network operator, instead of sending the TAP files through the host network (104), the client network operator (102) sends them directly to the HSRP network operator, provided that the HSRP network and host network operators (104) accept such an agreement.

To manage the billing of the client network sender roamers (102), the HSRP network operator sends these TAP records of the sender roamers to the host networks that identify them by their IMSIs. Since these TAP records are mixed with the TAP records of the usual sender roamers on the host networks, the host network operators divide their TAP records based on the IMSI ranges used for each client network, and send them in separate files to the host network. client network operator (102). In this case, the client network operator (102) pays the benefits to the host network operators who subsequently pay the HSRP network operator. In one embodiment of the present invention, the host network operators assume financial responsibility for the HSRP network operator, regardless of whether the client network operator (102) credited the benefits to these host network operators.

Open Connectivity (OC)

The network operator community and the GSMA have promoted the Open Connectivity Initiative (OCI) as a cost-effective and efficient means for network operators to establish or expand their roaming relationships. In this model, network operators could, in effect, "outsource" their roaming operations to a hub operator. Although each network operator would require a single agreement with that outsourced hub operator, the outsourced hub operator would still be responsible for bilateral IOT, IREG and TADIG testing, signaling, and settlement with each participating network operator. Although OCI may not generally require support for the overlap technique (explained in the previous SPRS dossier and in various embodiments of the present invention) or an intermediary operator model (where an intermediary acts as a mediator between the network operators to establish roaming IOT with these network operators), the implementation of this initiative does not seem to exclude these models.

Various embodiments of the partial roaming scenarios for overlapping roaming can equally be applied to the OCI environment for differential routing of signaling messages between the roaming agreements supported by Oc and the bilateral ones. The host network 104 described above in various embodiments of the present invention could function as an OC hub rather than a network operator. This OC hub would not have any bilateral roaming agreement with HSRP networks; and rather it would facilitate or function according to the existing roaming agreement between the different network operators (for example, between the client network (102) and the HSRP network). However, in this case of the OC concentrator, possibly only the individual IMSI solution could be applied for inbound and outbound roaming.

Consequently, as a host network cascades over to another host network, OC hubs can also be cascaded to establish the roaming relationship between two client network operators supported by their respective SPRS hubs.

In one embodiment of the present invention, the client network operator (102) of the OC hub deploys the SPRS router (106) on its network. In another embodiment of the present invention, the client network SCCP bearer (102) deploys the SPRS router (106) in its network. In yet another embodiment of the present invention, the client network OC hub (102) deploys the SPRS router (106) on its network. In this embodiment, the OC hub may configure its STP to first route all SCCP signaling messages to the SPRS router (106). Next, the SPRS router 106 decides to split the SCCP signaling in a manner similar to that described above for the inbound and outbound roaming solutions of the present invention. Also, as with the operator of

ES 2 365 958 B2 host network (104), the OC concentrator deploys the SPRS concentrator (108) in its network, according to an embodiment of the present invention. In another embodiment of the present invention, the OC hub could deploy the SPRS hub (108), which is optionally integrated with the SPRS router (106), in its network.

As will be apparent to a person skilled in the art, the roaming service using the above-described partial roaming scenarios can also be applied to code division multiple access (CDMA) / American National Standards Institute No. 41 (ANSI-41 ) and other technologies such as, but not limited to, VoIP, WiFi, 3GSM, and inter-standard roaming. For example, a CDMA roamer traveling with an HPMN CDMA handset. Another example is a CDMA roamer traveling with HPMN's GSM SIM and a GSM handset. Another example is a GSM roamer traveling with HPMN's CDMA RUIM and a CDMA handset. As would be apparent to a person skilled in the art, these two interfaces in different directions do not have to be the same technologies. Also, it could be various types of interfaces in both directions.

The following table describes an example mapping list between GSM MAP and ANSI-41 for reference.

<td>Location / ISD update</td><td>NOREG</td>

<td>Cancel location</td><td>ALLOW REG</td>

<td>Register SS</td><td>FEATURE REQUEST</td>

<td>Ask SS</td><td>FEATURE REQUEST</td>

<td>SRI-SM</td><td>SMS REQUEST</td>

<td>SRI</td><td>LOCATION REQUEST</td>

<td>ForwardSMS</td><td>SMS DPP</td>

<td>Ready for SMS</td><td>SMS NOTIFICATION</td>

<td>Alert the server center</td><td>SMS NOTIFICATION</td>

<td>Report SMS broadcast</td><td>SMS DPP</td>

<td>Provide roaming number</td><td>ROUTING REQUEST</td>

A client network operator uses one or more variants of the present invention to overlap one or more roaming relationships of the host network (such as GSM, GPRS, CAMEL or 3G) with one or more HSRP networks, to provide its roaming subscribers receivers and senders, when the client network does not have these roaming relationships with HSRP networks. This is beneficial for new or established client networks that have limited roaming agreements, as they can expand their roaming coverage using one or more embodiments of the present invention. Since the present invention provides an overlay solution for partial roaming, the cost of establishing expensive and time-consuming direct roaming agreements between the customer network and the HSRP network is reduced. This increases roaming revenue for the client network operator by getting more recipient roamers to register with their network. Also, the client network is able to provide better roaming coverage (eg if only GSM roaming agreement exists, CAMEL roaming coverage is provided by overlay) to its sending roamers. Additionally, this also benefits the host and HSRP networks since their sender roamers can both roam the client network as well as provide to the receiving roamers from the client network. Furthermore, the present invention also enables the client network to oppose any traffic redirection mechanism that may be applied by HSRP networks to divert their sender roamers from the client network. The client network can also determine if the receiving roamer of a particular HSRP network is a preferred roamer (eg, prepaid roamer or CAMEL or 3G), and if so, then the client network uses various embodiments of the present invention. to provide the preferred receiving roamer.

Advanced services that work in concert with partial roaming

Of course, a client network operator benefits when it provides partial roaming according to the present invention, insofar as it is able to sell additional types of telecommunication services (data, or CAMEL roaming for voice and data) due to the overlap to the host network operator's relationships with HSRPs. You can even benefit much more, even in an open connectivity scenario, by offering those receiving and sending roaming subscribers various advanced value-added services aimed at further stimulating roaming usage.

Additionally, partial roaming for data (such as 3G / WCDMA, Edge, or GPRS) can encourage receiving “smartphone” roamers to use the client network. A "smartphone" is a handset

ES 2 365 958 B2 mobile which, in addition to offering voice calls, allows the user to interact with other data services, and is normally capable of storing and executing a variety of computer programs installed and configured on demand. Examples of smartphones include the Blackberry, Palm Treo, Apple iPhone, LG Voyager, and a variety of handsets offered by other major providers. Smartphones are normally more expensive than normal ones. Smartphone users are often travelers who are likely to use telecommunications services more generally when traveling.

Part of the benefit of partial roaming for data and roaming agreements may come automatically, for smartphones that are configured to prefer roaming on visited networks that offer data coverage.

But a client network according to the present invention, or a host network, can further increase the potential increase in roaming usage by offering today's advanced value-added services of particular interest to smartphone users and roaming subscribers who receive data services but not. voice. Examples include the Blackberry server service offering for receiving roamers using RIM handsets, or the newly proposed push-email or business services for receiving roaming subscribers using iPhone, or other similar services for Incoming roamers who own certain types of customer equipment. According to another embodiment, the client network offers the receiving data roamers, or the host network offers the data sender roamers, so-called "roaming content portal" products, in which the applicable network would identify the subscribers. roaming the home network and the location visited, and would offer data and media services relevant to their usual locations but in their own national language.

Similarly, client and host networks according to the present invention can greatly benefit from offering partial roaming over CAMEL offering advanced services of particular interest to prepaid roaming subscribers. As an example, it includes the offer to prepaid roaming subscribers of a local number in the place where they are visiting, and which would be billed to their usual prepaid account. Or offer all roaming subscribers this local number free of charge, whereby they would receive free incoming local calls to encourage them, while traveling, to use their phones for outgoing calls, or as a bonus for acquiring other services such as roaming prepaid.

Furthermore, a client network or host network operator according to the present invention can also benefit greatly from any of the overlapping roaming or OC implementations by offering a variety of value-added services generally designed to drive roaming. Examples include products called "virtual home environment", which allow roaming subscribers to dial telephone numbers according to the numbering plans and abbreviated code of their home locations, allows the caller ID to be directed to their handsets in roaming and allows voicemails to be deposited and retrieved. Roaming routing or so-called traffic management services allow the client or host network to achieve synergies by granting outgoing or incoming roaming traffic to the networks with which they have agreed favorable ranges.

All these types of advanced services can help client and host networks to benefit greatly from executing an overlapping roaming or OC implementation of the present invention and similarly, according to the present invention, roamers can also benefit greatly. .

The present invention may take the form of an embodiment. hardware only, a software only embodiment, or an embodiment containing both. According to one embodiment of the present invention, the invention is implemented in software, including, but not limited to, firmware, resident software, microcode, etc.

Accordingly, the invention may take the form of a computer program product, accessible from a usable or computer-readable medium, provided with programming code for use by, or in connection with, a computer or any computer execution system. instructions. For the purposes of this description, a usable or computer-readable medium can be any device that can contain, store, communicate, propagate, or transport the program to be used by, or in connection with, the device, apparatus or execution system. Instructions.

The medium may be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. Examples of a computer-readable medium include a hard disk or semiconductor memory, a magnetic tape, a removable floppy disk, a random access memory (RAM), a read-only memory (ROM), a hard magnetic disk, and an optic disc. Common examples of optical discs include compact disc read-only memory (CDROM), compact disc read-write (CD-R / W), and digital versatile disc (DVD).

The computer-usable medium provided below includes a computer-usable programming code, which when executed, facilitates the exchange of signaling messages between a client network and an HSRP network, providing roaming services to receiving roamers. and senders on the client network, even though both networks do not have a direct roaming agreement. To do this, the client network

ES 2 365 958 B2 uses an SPRS router to exchange the signaling messages of these roamers with the HSRP network through one or more SPRS hubs. The computer program product further includes a computer-usable programming code to identify one or more parameters of the signaling messages received at the SPRS router, thereby determining one or more of the roaming agreements from said parameters. required between the client network and the HSRP network and, therefore, allow the exchange of signaling messages between the client and HSRP networks. The software product also includes computer-usable programming code to facilitate, via the SPRS router, the exchange of signaling messages between the client network and the HSRP network through the SPRS hubs, as soon as the SPRS router determines that the required roaming agreements do not exist. The software product further includes a computer-usable programming code to facilitate, via the SPRS router, the direct exchange of signaling messages between the client network and the HSRP network, as soon as the SPRS router determines that the communication agreements exist. required roaming.

The components of the present two-node SPRS described above include any combination of computing devices and components running at the same time. The components of the present two-node SPRS can also be components or subsystems that are within a large network or computer system. The components of the present two-node SPRS can also be coupled with various components (not shown) such as other buses, controllers, memory devices, and data input and output services, and in numerous combinations. Additionally, many combinations of other processor-based components can perform the functions of the present two-node SPRS.

It must be taken into account that several of the components disclosed here can be described using computer-aided design tools, and / or expressed (or represented) as data and / or instructions, interpreted in various computer-readable media, in terms of its behavior, register transfer, logic component, transistor, format geometries, and / or other characteristics. Computer-readable media on which such formatted data and / or instructions can be interpreted include, but are not limited to, permanent storage media in various forms (eg, optical, magnetic, or semiconductor storage media) and carrier waves. which can be used to transfer this formatted data and / or instructions through wireless, optical or wired signaling means or any combination thereof.

Unless the context clearly requires otherwise, throughout the description and the claims, the words "comprises" "comprising" and the like are to be understood in an inclusive sense compared to an exclusive or exhaustive sense, that is, in the sense of "including, but not limited to". Words that use the singular or plural number also include the plural or singular number respectively. Additionally, the words "hereinafter, below or here", "below", "before, before or before (s)", "next", and words of similar meaning refer to this application in its entirety and do not to any particular part of it. When the word "or" is used in reference to a list of two or more items, that word encompasses all of the following interpretations: any or all or any combination of the items on the list.

The above description of illustrated embodiments of the present two-node SPRS is not intended to be exhaustive or limit the system to precisely disclosed form. While specific embodiments of, and examples of, the present two-node SPRS have been described herein for illustrative purposes, those skilled in the art will recognize that various equivalent modifications are possible within the scope of the present two-node SPRS. The teachings of the present two-node SPRS provided herein can be applied to other processing systems and methods. These systems and methods may not be limited to those described above.

The elements and performances of the various embodiments described above can be combined to provide additional embodiments. These and other changes can be made in light of the above detailed description.

Other variants

As specified above, the detailed illustrations are intended to teach those of ordinary skill in the art without intending to limit the scope of the invention, and correspond to a scheme that facilitates the exchange of one or more signaling messages between a client network and an HSRP network. Of course, numerous variations and modifications will occur to those of ordinary skill in the art that are included within the spirit of the present invention in light of the disclosed embodiments. For example, the present invention is implemented primarily from the point of view of GSM mobile networks as described in the embodiments. However, the present invention can also be effectively implemented in GPRS, 3G, CDMA, WCDMA, WiMax, etc., or in any other telecommunications network provided by a common carrier in which end users are normally determined to operate within a “home” network to which they are generally subscribed, and also in other neighboring networks, which may even cross international boundaries.

The examples according to the two-node SPRS of the present invention detailed in the illustrative examples contained therein are described using terms and constructions largely taken from the GSM mobile telephone infrastructure. However, the use of these examples should not be construed as limiting the invention to those means. The two-node SPRS and the method that can be used and provided directly to any type of telecommunication medium, include but are not limited to: (i) any mobile phone network that includes, but is not limited to, GSM, 3GSM , 3G, CDMA, Wimax, VoIP, HSDPA, SIP, IMS, WCDMA or GPRS,

ES 2 365 958 B2 satellite phones or other mobile phone systems or networks; (ii) any device known as WiFi normally used on a subscribed or home network but which is also configured for use on a visited or non-home or unusual network, including non-telecommunications devices such as personal computers and mobile devices Palm-type or Windows Mobile; (iii) an entertainment console platform such as Sony Playstation, PSP or other devices capable of sending and receiving telecommunications services over home or non-home networks, or even (iv) fixed line devices designed to receive communication services but that can be deployed at numerous locations while keeping subscriber ID constant like Dlink's eye2eye devices, or telecommunications equipment intended for voice over the IP communications system such as those provided by Vonage or Packet8.

In describing certain embodiments of the system according to the present invention, this specification follows the path of a call over a telecommunications service, from a calling party to a called party. For the avoidance of doubt, this call can be a normal voice call, in which the subscriber's telecommunications equipment can also display visual, audiovisual or moving images. On the other hand, those devices or calls can be text, video, images or other communicated data.

In the above specification, specific embodiments of the present invention have been described. However, one of ordinary skill in the art will appreciate that various changes and modifications can be made without departing from the scope of the present invention as set forth in the following claims. Accordingly, the specification and figures are to be construed in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of the present invention. The benefits, advantages, solutions to problems, and other element (s) that may benefit, provide advantages or solutions, or become more accentuated, should not be understood as a critical, required, or essential element or particularity of any or all claims.

Technical references

AA. 13 - Common Annex for all roaming partners

AA. 14 - Individual annex for a roaming partner

AA. 19 - SMS interconnection agreement with a roaming partner

AA. 31 - GPRS roaming agreement with a roaming partner

GSM 9.02 over MAP specification

Digital Mobile Telecommunications System (Phase 2+) Mobile Application Part (MAP) Specification (3GPP TS 09.02, Version 7.9.0, Publication Year: 1998)

GSM 3.40 over SMS

Digital mobile telecommunications system (phase 2+)

Technical realization of the short message service (SMS) (GSM 03.40, version 7.4.0, year of publication: 1998)

GSM 3.78 over CAMEL

Digital mobile telecommunications system (phase 2+)

Custom Applications for Mobile Network Enhanced Logic (CAMEL)

Phase 2; Stage 2 (GSM 03.78, version 6.7.0, year of publication: 1997)

3GPP CAMEL GSM Standard 23.078

GSM 9.78 over CAMEL application protocol

ES 2 365 958 B2

Digital mobile telecommunications system (phase 2+);

Custom Applications for Mobile Network Enhanced Logic (CAMEL);

CAMEL Application Part Specification (CAP) (GSM 09.78, Version 7.1.0, Release Year: 1998)

3GPP GSM Standard 29.002 - Mobile Application Part and Signaling Procedures (MAP) (year of publication: 1999)

GSM 3.60 over GPRS,

GSM 23.060 over GPRS R99,

GSM 9.60 over GPRS GTP 0,

GSM 29.060 over GPRS GTP 1,

GSM 3.79 over CAMEL support for optimal routing,

GSM 3.18 on basic CAMEL call handling,

GSM 3.20 - Security-related network functions

GSM 23.012 - Location management

IR 21 - Network information exchange via international roaming for roaming partners

Q1214-Q1218 on smart grids,

Q701-704 over SS7 MTP,

Q711-Q714 about SS7 SCCP,

Q760-Q769 on SS7 ISUP

Jiang 2003 SIMM: P roviding Multiple MSISDNs in a SIM with a single IMSI for multiple roaming partners

Jiang 2003 MIMM / MISM: Providing Multiple / Single MSISDNs and Multiple IMSIs in a SIM for multiple roaming partners

Jiang 2007 SIMM Variation: Method and System for Multiple MSISDNs in a SIM with a single IMSI for multiple roaming partners withoút changing SIM

Jiang 2007 Multiple SIMs: Method and system for Multiple MSISDNs with multiple SIMs for multiple roaming partners

Jiang et al 2003 TR: Cellúlar Traffic Redirection

Jiang 2006 IR 73 TR: IR 73 Compliant passive traffic steering

Jiang 2005 DCG-O: Dynamic Camel Gateway for other roamers

Jiang 2005 DCG-I: Dynamic Camel Gateway for inboúnd roamers

Jiang 2007 Passive Inbound: A passive monitoring-based method and system for providing mobile inboúnd roaming commúnication corresponding to multiple MSISDNs associated with a single IMSI for multiple roaming partners

Joss Marcel and Werner Hirzel 2004: Signaling method and conversion device for telecommúnications networks, US Patent No. 6684073 B1, issued on 27th Janúary 2004

Open Connectivity, GSMA OC-18 related initiatives, 2007.

ES 2 365 958 B2

Appendix

<td>Acronym</td><td>Description</td>

<td>3G</td><td>Third generation of mobiles</td>

<td>AA</td><td>International roaming agreement</td>

<td>ANSI-41</td><td>American National Standards Institute # 41</td>

<td>BARG</td><td>Billing, Accounting and Roaming Group</td>

<td>CAMEL</td><td>Custom App for Enhanced Mobile Network Logic</td>

<td>CHAP</td><td>CAMEL application part</td>

<td>CB</td><td>Call blocking</td>

<td>DC</td><td>Country code</td>

<td>CdPA</td><td>Destination party address</td>

<td>CgPA</td><td>Address of the party of origin</td>

<td>CSI</td><td>CAMEL subscription information</td>

<td>ERB</td><td>Basic model of call state event notification by CAP</td>

<td>GMSC</td><td>MSC catwalk</td>

<td>GMSC-C</td><td>GMSC in client network</td>

<td>GMSC-H</td><td>GMSC on host network</td>

<td>GPRS</td><td>General packet radio system</td>

<td>GSM</td><td>Global mobile communication system</td>

<td>GSMA</td><td>GSM Association</td>

<td>GT</td><td>Global Title</td>

<td>HLR</td><td>Home user location record</td>

<td>HLR-C</td><td>Client Network HLR</td>

<td>HLR-H</td><td>Host network HLR</td>

<td>HPMN</td><td>Home mobile public network</td>

<td>HSRP</td><td>Roaming partner supported by host</td>

<td>YO SOY</td><td>Initial address message</td>

<td>IDP</td><td>IN / CAP initial DP message</td>

<td>IMSI</td><td>International Mobile Subscriber Identification Number</td>

<td>IMSI-C</td><td>Client network IMSI</td>

<td>IMSI-H</td><td>Host network IMSI</td>

<td>IN</td><td>Intelligent Network</td>

<td>IP</td><td>Internet protocol</td>

<td>IREG</td><td>Expert Group on International Roaming</td>

ES 2 365 958 B2

<td>ISC</td><td>International carrier service</td>

<td>ISD</td><td>MAP-based subscriber data entry</td>

<td>ISTP</td><td>International STP</td>

<td>LUP</td><td>MAP location update</td>

<td>MAP</td><td>Mobile application part</td>

<td>MCC</td><td>Country code for mobile</td>

<td>MMS</td><td>Multimedia messaging service</td>

<td>MNC</td><td>Mobile phone network code</td>

<td>MO</td><td>Originated from mobile</td>

<td>MSC</td><td>Mobile switching center</td>

<td>MSISDN</td><td>International subscriber number of the mobile station</td>

<td>MSRN</td><td>Roaming number of mobile station</td>

<td>MT</td><td>Finished on mobile</td>

<td>MTP</td><td>Message transfer part</td>

<td>NDC</td><td>National dialing code</td>

<td>OC</td><td>Open connectivity</td>

<td>ODB</td><td>Lock for a specific operator</td>

<td>PRD</td><td>Permanent reference document</td>

<td>PRN</td><td>Provision of roaming number by MAP</td>

<td>RNA</td><td>Roaming not allowed</td>

<td>RR</td><td>Restricted roaming due to unsupported feature</td>

<td>RRB</td><td>Basic call status request notification model</td>

<td>SCCP</td><td>Signaling connection control part</td>

<td>SCP</td><td>Service control point</td>

<td>SGSN</td><td>Support node for GPRS server system</td>

<td>SIM</td><td>Subscriber identification module</td>

<td>SMS</td><td>Short message service</td>

<td>SMSC</td><td>Short Message Server Center</td>

<td>SMSC-C</td><td>SMSC client network</td>

<td>SoR</td><td>Roaming addressing</td>

<td>SPRS</td><td>Packet signal relay system</td>

<td>SRI</td><td>Sending routing information by MAP</td>

<td>SRI-SM</td><td>Sending routing information by MAP for short messages</td>

<td>H.H</td><td>Supplementary services</td>

<td>SS7</td><td>Signaling system n ° 7</td>

<td>SSN</td><td>Number of subsystems</td>

<td>SSP</td><td>Service switching point</td>

<td>STP</td><td>Signaling transfer point</td>

<td>STP-C</td><td>STP client network</td>

<td>STP-H</td><td>Host network STP</td>

ES 2 365 958 B2

<td>TADIG</td><td>Transfer Accounting Data International Group</td>

<td>TAP</td><td>Transfer accounts procedure</td>

<td>TCAP</td><td>Capabilities transaction application part</td>

<td>TT</td><td>Conversion type</td>

<td>VLR</td><td>Visiting subscriber location record</td>

<td>VMSC</td><td>MSC visited</td>

<td>UDTS</td><td>Data transfer service unit</td>

<td>VPMN</td><td>Visited mobile public network</td>

13 members in 4 offices

This recordMember, by publication datePriority claim

Priority claims9

Priority claims
Document	Office	Kind	Date
60907287	United States of America	–	2007-03-27
90728707	United States of America	P	2007-03-27
90728707	United States of America	P	2007-03-27
2008003966	United States of America	W	2008-03-27
2008003966	United States of America	W	2008-03-27
60907287	–	–	–
PCTUS2008003966	–	–	–
US20070907287P	–	–	–
WO2008US03966	–	–	–

Members13

Family members, oldest first
Document	Office	Kind
WO2008118471A2	World Intellectual Property Organization (WIPO)	A2	2008-10-02
WO2008144022A2	World Intellectual Property Organization (WIPO)	A2	2008-11-27
WO2008118471A3	World Intellectual Property Organization (WIPO)	A3	2009-02-26
WO2008144022A3	World Intellectual Property Organization (WIPO)	A3	2009-03-12
GB0920591D0	United Kingdom	D0	2010-01-06
GB2461678A	United Kingdom	A	2010-01-13
US2010128685A1	United States of America	A1	2010-05-27
ES2365958A1	Spain	A1	2011-10-14
GB2461678B	United Kingdom	B	2012-03-28
ES2365958B2This record	Spain	B2	2012-06-18
US8254918B2	United States of America	B2	2012-08-28
US2012244859A1	United States of America	A1	2012-09-27
US8761760B2	United States of America	B2	2014-06-24

2 legal events, as the office reported them to INPADOC

Over the term

Point at a mark for the event

Events

Legal events, newest first
	Event	Code
2022-09-28	Transfer of patentPC2A	PC2A
2012-06-18	Definitive protectionFG2A	FG2A

Method and system for providing piggyback roaming for sponsoring split roaming relationships

Abstract

Term

ES 2 365 958 B2

DESCRIPTION

ES 2 365 958 B2

ES 2 365 958 B2

ES 2 365 958 B2

ES 2 365 958 B2

ES 2 365 958 B2

ES 2 365 958 B2

ES 2 365 958 B2

ES 2 365 958 B2

Priority claims9

Members13

Over the term

Events

Numbers

Titles2

Classification