Message routing system for cellular to satellite networks

Abstract

To enable a user device to automatically switch between satellite and cellular modes, thereby enabling improved messaging services and enhancing communication between users on different networks.SOLUTION: A system for delivering and receiving a Short Message Service (SMS) between users connected to satellite networks and cellular networks includes user devices, a satellite service provider, a satellite proxy network, and a cellular operator. A method comprises monitoring a network mode of a user device, relaying information about the user device's connection to the satellite network, and registering the user device with a cellular operator when in a satellite mode. The satellite proxy network serves as an anchoring point for sending and receiving SMS messages for exchanging seamless message between satellite network users and cellular network users.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates generally to the field of multi-band network service interoperability. More specifically, the present invention relates to a system for routing message replies over a cellular network to a different network platform, such as a satellite-based sender. [Background technology]

[0002] Satellite-based communication services are typically used in remote locations or situations where traditional cellular networks are unavailable or unreliable. Three well-known providers of satellite phone services are known by the brands Iridium, Globalstar, and Inmarsat. Phones that can operate in both satellite and cellular modes are known as hybrid or dual-mode satellite phones. They are designed to seamlessly switch between satellite and cellular networks, providing users with broader coverage and ensuring continuous connectivity. The phone uses the cellular network when it is available and switches to the satellite network when cellular coverage is poor or nonexistent. Summary of the Invention [Problem to be solved by the invention]

[0003] However, a device in satellite mode (i.e., connected to satellite service) can send a message to a cellular-based recipient and not receive the message in reply from the recipient's cellular network. Thus, an unmet need exists for a method for redirecting messaging services between satellite and cellular networks. [Means for solving the problem]

[0004] The present invention relates to a method and system for facilitating messaging services between a cellular network and a satellite network, the method and system being performed and implemented by a satellite proxy network. This is accomplished through the network receipt of a special Short Message Service (SMS) message or Application Programming Interface (API) call from a satellite service provider. These messages or calls are received when a communication device transitions to a satellite mode. The communication device is capable of functioning in both cellular and satellite modes and has the same Mobile Station International Subscriber Directory Number (MSISDN) in both modes. Receipt of the special SMS message or API call signifies that the communication device is connected to the satellite network.

[0005] When the satellite proxy network receives these signals, it registers itself with the Home Location Register (HLR) of the communication device as a Visitor Location Register and Mobile Switching Center (VMSC). As the VMSC, the satellite proxy network is responsible for sending and receiving SMS messages related to the communication device while the communication device is in satellite mode. The satellite proxy network receives SMS from the communication device in satellite mode and transmits the messages to a designated operator. The satellite proxy network also receives SMS messages from other devices or operators and transmits these messages to the communication device in satellite mode via the satellite connection. This facilitates the exchange of messages between the satellite service provider and other devices or operators while handling messaging services to and from the communication device.

[0006] The satellite proxy network similarly receives a deregistration message from the communication device upon returning to a cellular mode, indicating that the communication device has transitioned from the satellite network to the cellular network, and in response to the deregistration, the satellite proxy network updates the HLR to indicate the transition.

[0007] If a period of inactivity occurs between the communication device and the satellite proxy network, specifically for a period ranging from 5 minutes to 30 minutes, or more than 30 minutes, a Purge Mobile Station (MS) is sent to the HLR. In return, the HLR sends a Purge MS response to the satellite proxy network. The satellite phone timeout value for inactivity can be dependent on a variety of factors, including the particular satellite phone network used, the network configuration, device settings, and even the satellite service provider's policies. In general, satellite networks are designed to maximize the efficient use of limited satellite bandwidth. This often involves disconnecting inactive devices after a period of time to free up resources for other devices. The exact timeout period can vary widely.

[0008] The HLR may similarly send a de-registration to the satellite proxy network upon detecting that the communications device is registered with another VMSC.

[0009] For a fuller understanding of the present invention, reference should be made to the following detailed disclosure taken in conjunction with the accompanying drawings. [Brief description of the drawings]

[0010] Figure 1 illustrates the operation of the satellite mode call flow for checking whether a communication device is registered in the operator network using the home operator HLR.

[0011] FIG. 2 illustrates another embodiment of the satellite mode call flow operation in which the update location procedure is set to cellular redirect.

[0012] FIG. 3 shows a failed device satellite registration attempt error with no retries.

[0013] FIG. 4 shows a successful device satellite registration attempt with a retry after an initial error.

[0014] FIG. 5 illustrates device satellite deregistration.

[0015] FIG. 6 illustrates the Transaction Detail Record (TDR) process for billing analysis.

[0016] FIG. 7 is a schematic diagram of a process according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] The present invention provides a novel and non-obvious solution to the above problem. The solution for providing messaging services between cellular and satellite networks is done by redirecting messages through an intermediate network. This is done by the satellite service provider constantly monitoring the device for its network mode (either cellular or satellite mode). The device has the same MSISDN whether it is in cellular or satellite mode. When the device switches to satellite mode, the satellite service provider sends a special SMS to the intermediate network (e.g., offered under the brand SYNIVERSE) indicating that the device is connected to the satellite network. The intermediate network then registers the device with the cellular operator.

[0018] Once the device is registered with the intermediate network, the cellular operator handles the messaging services to the device. From that point on, the intermediate network becomes the anchoring point for the sending / receiving device related SMS messages. The intermediate network receives SMS from the device and sends the SMS to the destination operator (device to MO). The intermediate network receives SMS from other devices / operators and sends them to the satellite device.

[0019] When the device returns to cellular mode, it registers directly with the service operator and sends a device de-registration message to the intermediate network, which then updates the back-end system that the device has moved from the satellite network to the cellular network.

[0020] Cellular Network Mobile Device Registration:

[0021] For cellular networks, mobile device registration typically consists of the following steps: (a) when the mobile device powers up or enters the coverage area of ​​a cellular network, it begins searching for available networks and attempts to register with one that it is programmed or authorized to access (based on the user's subscription plan); (b) the mobile device sends a registration request to the network, including its International Mobile Equipment Identity (IMEI) number and International Mobile Subscriber Identity (IMSI) number; (c) the cellular network verifies the mobile device's IMEI and checks the IMSI against a subscriber database, and if the mobile device and subscriber are valid, the cellular network registers the mobile device and assigns a temporary identifier, such as a Temporary Mobile Subscriber Identity (TMSI), and (d) the mobile device is now registered on the network and can access voice, text, and data services.

[0022] Satellite Network Mobile Device Registration:

[0023] For satellite networks, mobile device registration typically consists of the following steps: (a) when a mobile device is powered on and does not have cellular coverage, it must first request a connection to the satellite network, usually by first locating and then communicating with the nearest satellite in the satellite network, and once connected, by manually activating a button to establish a connection with the satellite network; the mobile device transmits or receives any data required based on what has been queued on either side; (b) the mobile device sends a registration request to the satellite, including its unique device identifier and subscriber information; (c) the satellite forwards the registration request to a ground-based Network Operations Center (NOC), where the device identifier and subscriber information are verified; (d) if the device and subscriber are valid, the NOC registers the mobile device in its database and sends a confirmation to the satellite, which then communicates a registration confirmation to the mobile device; and (e) the mobile device is now registered with the satellite network and can access text and data services.

[0024] FIG. 1 illustrates a call flow diagram of an embodiment of the present invention related to verifying whether a satellite / cellular hybrid device 12 is part of a mobile operator network, in this case a customer Home Location Register (HLR) 26. A collection of services forms the satellite proxy 24. These services include a satellite API gateway 14, a messaging gateway 16, and a cellular redirect 18. The device 12 creates a satellite activation request 34, which may be created by an API call to the satellite API gateway 14. The API call data payload may include attributes of the device 12 along with Short Message Service Center (SMSC) information. The satellite API gateway 14 then passes the satellite activation request to the messaging gateway 16. The messaging gateway 16 then interfaces with the cellular redirect 18, which passes the satellite activation request 38. The cellular redirect 18 sends an authorization information request 40 to the customer HLR 26 conveying the satellite proxy 24 as a Visitor Location Register (VLR) Mobile Switching Center (MSC) (VMSC) node. The HLR 26 sends an authorization confirmation 42 back to the cellular redirect 18. The cellular redirect 18 then passes the authorization confirmation 42 back to the messaging gateway 16, the satellite API gateway 14, and finally to the device 12 passing satellite activation confirmations 44a-c, respectively.

[0025] In FIG. 2, the device 12 generates a satellite activation request 46, which may be made by an API call to the satellite API gateway 14 or a mobile operator (MO) SMS message. The data payload to the API gateway may include attributes of the device 12 along with SMSC information. The satellite API gateway 14 passes the satellite activation request 48 to the messaging gateway 16. The messaging gateway 16 then connects with the cellular redirect 18, which passes the satellite activation request 50. The cellular redirect 18 sends an authorization information request 52 to the customer HLR 26, which conveys the satellite proxy 24 as a VMSC node. The HLR 26 sends an authorization information confirmation 53 back to the cellular redirect 18. The cellular redirect 18 then sends an update location request to the HLR 26 as a sponsored VMSC node 54. The subscriber data 56 is sent from the HLR to the cellular redirect 18, which generates a response 58 and sends it back to the HLR 26. The HLR 26 then sends an update location response 60, effectively creating a visiting location registration in the satellite proxy network 24 where the device 12 is roaming for messaging. The cellular redirect 18 sends satellite up confirmations 44a-44c downstream through the messaging gateway 16 and satellite API gateway 14, and ultimately to the device 12.

[0026] FIG. 3 shows a call flow where the HLR 26 returns an error 60 without any retry attempt. This exception is passed down 62a-62c, respectively, to the cellular redirect 18, the messaging gateway 16, the satellite API gate 14 and finally to the device 12. In FIG. 4, an exception error 61 is sent from the HLR 26 to the cellular redirect 18 in response to an update location response. However, in contrast to FIG. 3, a retry is attempted, which successfully updates the location request 54b after an initial failed update location request 54a. The satellite operation takes the normal path, which includes sending the subscriber data 56 from the HLR to the cellular redirect 18, which generates a response 58 and sends the response 58 back to the HLR 26. The HLR 26 then sends an update location response 60, which effectively creates a visited location registration in the satellite proxy network 24 where the device 12 is roaming for messaging. The cellular redirect 18 sends satellite activation confirmations 44a-44c downstream through the messaging gateway 16 and the satellite API gateway 14 and ultimately to the device 12.

[0027] In Figure 5, after a period of inactivity 64, the satellite proxy network 24 issues a Purge Mobile Station (MS) 66 to the HLR 26 to remove or purge the temporary data stored in the mobile station. When the device is inactive, the network's Visited Location Register (VLR), in this case emulated by the satellite proxy network 24, holds temporary information about the device, such as its current location. If the device remains inactive long enough, the network decides to purge or remove this data to conserve resources. When the mobile station becomes active again, the network updates the data.

[0028] Alternatively, the device 12 may move onto another VLR or revert to its HLR 26, in which case the HLR 26 will proactively issue a cancel registration 70 to the cellular redirect 18. The HLR 26 may also receive a cancel registration confirmation 72 from the cellular redirect 18. In either case, the cellular redirect 18 will send a cancel satellite registration 74 to the satellite API gateway 14 and receive a response 76 from the satellite API gateway 14. The cellular redirect 18 will then issue an offload request 78 to the messaging gateway 16, where the message will be queued for offload 80. The satellite API gateway 14 will offload the SMS 82 to a delivery gateway 84. An offload queue response 86 will be issued from the satellite API gateway 14 to the messaging gateway 16. FIG. 6 illustrates an embodiment of the present invention that manages retrieval of TDR billing records 88 from the cellular redirect 18 and storage in the database 20.

[0029] In FIG. 7, the hybrid satellite / cellular device 12 switches to satellite mode. The device 12 communicates with the satellite 13 and passes a satellite activation request 34 received by the satellite API gateway 14. The satellite activation request 38 is sent from the satellite API gateway 14 to the cellular direct 18. The cellular direct 18 creates a satellite registration 40 with the customer HLR 26. The satellite API gateway 14 sends a message for the mobile device, an SMS MT (Mobile Terminated) message 36, to the messaging gateway 16. The messaging gateway 16 acts as an intermediary to manage communication between various networks or systems. The messaging gateway 16 receives the SMS MT from the satellite API gateway 14 and then sends a message 92 to the customer SMSC (Short Message Service Center) 28, which is responsible for storing, routing and delivering the SMS message within the network. After receiving the SMSMT 92 from the messaging gateway 16, the SMSC 28 sends a mobile device initiated SMSMO (Mobile Originated) message 94 to the cellular redirect 18.

[0030] The present invention as described above is a communication management system for a hybrid satellite / cellular network operating within a mobile operator network. The central component of the system is a satellite proxy that is composed of several services, namely, a satellite API gateway, a messaging gateway, and a cellular redirect. These elements work together to handle the transition of a device between the cellular and satellite networks. An activation request, facilitated by an API call, is passed from the device to the satellite API gateway, then to the messaging gateway, and finally to the cellular redirect. The cellular redirect communicates with the home location register (HLR) to authenticate the satellite proxy as a visitor location register (VLR) mobile cellular networker (MSC) node. Exception errors and retry attempts are accommodated within the system. In case of device inactivity, the system can purge temporary data about the mobile station to conserve resources, and update the temporary data when the device is activated again. When the device switches to another VLR or returns to the HLR, the system can cancel the satellite registration. Finally, the system transitions the device into satellite mode, manages communications via SMS messages through various network elements, and coordinates management of TDR billing records.

[0031] Registration Error Code Mapping

[0032] Table 1 provides a list of error codes associated with mobile device registration in a telecommunications network. Each error code corresponds to a particular issue or condition that prevents the device from being successfully registered. The table also indicates whether the registration notification error code should be sent to the messaging gateway (GW) and whether a retry should be attempted for each particular error.

[0033] [Table 1]

[0034] Rest API

[0035] The POST / API / SatelliteModeNotification / RepeatStateTransition (REST)Notification Application Programming Interface (API) is sent by the messaging gateway (GW) 28 to the SYNIVERSE API 30 when the device switches to satellite mode. The message is a request in JavaScript Object Notation (JSON). Table 2 shows the API request.

[0036] [Table 2]

[0037] response

[0038] Table 3 shows the API response

[0039] [Table 3]

[0040] Error responses

[0041] Table 4 shows the error response

[0042] [Table 4]

[0043] POST / API / CancelLocationNotification / This REST notification API is sent by the messaging GW28 to the Syniverse API30 when the device switches to satellite mode. The message is in JSON format.

[0044] request

[0045] Table 5 shows the cellular registration request.

[0046] [Table 5]

[0047] response

[0048] Table 6 shows the cellular registration response.

[0049] [Table 6]

[0050] Database design

[0051] The following tables enable embodiments of the solution: MCC_MNC_List - This table lists the MCC, MNC for a Carrier ID. Represents a Mobile Country Code in the context of mobile device telecommunications. It is a three digit numeric code that uniquely identifies a particular country or region in which a mobile device network operates. The MCC is used in combination with a Mobile Network Code (MNC), which is a two or three digit numeric code that identifies a particular mobile network operator within a country.

[0052] Table 7 MCC and MNC for Carrier ID

[0053] [Table 7]

[0054] Carrier Table - The table contains the carrier name and country code for each carrier id.

[0055] [Table 8]

[0056] IMSI_RANGE_MAP - This table contains IMSI to HLR mapping.

[0057] Table 9 IMSI range map

[0058] [Table 9]

[0059] Registration_info - This table contains the IMSI and HLR number mapping to the originating MME host.

[0060] Table 10. Registration information

[0061] [Table 10]

[0062] Sample JSON file format title: SatModeNotification host: 'localhost:54990' basePath: / tags: - name: Notification description: Sends Notification paths: / Notification / SatModeNotification: post: tags: - Notification v1 summary: SendNotification operationId: SendNotificationUsingPOST consumes: - application / json produces: - application / json parameters: - in: body Name: imsi description: imsi required: true type: string - in: body name: msisdn description: msisdn required: true type: string - in: body name: opid description: operationid required: true type: string - name: int-companyId in: header description: Unique ID identifying the company associated with the application. required: true type: string response ‘200': description: success ‘400’ Error Response Cancel Location Sample File title: CanLocNotification host: 'localhost:54990' basePath: / tags: - name: Notification description: Sends Notification paths: / Notification / CanLocNotification: post: tags: - Notification v1 summary: CanLocNotification operationId: CanLocNotificationUsingPOST consumes: - application / json produces: - application / json parameters: - in: body Name: imsi Description: imsi required: true type: string - in: body name: opid description: operationid required: true type: string - name: int-companyId in: header description: Unique ID identifying the company associated with the application. required: true type: string response '200': description: success

[0063] TDR-Transaction Details and Analysis

[0064] The transaction details are sent by the cellular redirect server 32 to the TDR process 64. A billing and analysis component is optionally integrated to receive the TDR data for billing purposes.

[0065] 6, the Cellular Redirect Server 32 sends a GRPC message for each event (Update Location Request 34, Update Location Response 35, Cancel Location Request 55, Cancel Location Response 56) to the TDR process 64, which periodically logs information for debugging / research purposes. These event details from the TDR 64 can be read by the Billing and Analysis Portal 66 for billing purposes, if required.

[0066] Table 11 - TDR Fields Table

[0067] [Table 11]

[0068] FIG. 7 shows a hybrid satellite device 12 having a selector 74 for switching between satellite mode 75 and cellular mode 76. In either satellite mode 75 or cellular mode 76, the hybrid satellite device 12 has the same MISIDN. When the satellite service provider 72 switches to satellite mode 75, it sends a zero byte SMS to the queue 14, which is received by the gateway 16. The gateway sends the unique 15 digit IMEI derived from the zero byte SMS to the ENUM system 18. ENUM (short for E.164 Number Mapping) is a protocol used in telecommunications that maps E.164 telephone numbers to other resources on the Internet. E.164 is an ITU-T recommendation that defines the international public telecommunications numbering plan used in the PSTN (Public Switched Telephone Network) and several other data networks. The ENUM system 18 returns the IMSI, MSISDN, and OPID to the gateway 16. The gateway 16 sends a JSON payload to the API 30 containing the IMSI, MSISDN and OPID received from the ENUM system 18. The API 30 and cell redirect 32 constitute an intermediate network 71 that registers the device 12 with the HLR 22. The intermediate network 71 receives inbound SMS 30 messages and transmits them back to the satellite service provider 72 via the intermediate network 71, satellite connection 77. In this way, the hybrid device 12 can seamlessly switch between satellite mode 75 and cell mode 76 while still receiving SMS messages sent through the intermediate network 71.

[0069] Hardware and software configuration examples

[0070] The various techniques described herein may be implemented in connection with hardware or software, or a combination of both, where appropriate. Thus, the methods and systems described herein, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in a tangible medium, such as a hard drive, solid-state drive, or any other machine-readable storage medium. When the program code is loaded and executed by a machine, such as a computing device, the machine becomes a device for practicing the invention. When executing program code on a programmable computer, the computing device typically includes a processor, a storage medium readable by the processor (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device. The programs may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and may be combined with hardware implementations.

[0071] The present invention may be implemented through communication embodied in the form of program code transmitted over some transmission medium, such as electrical wiring or cable using fiber optics, or other forms of transmission. Here, when executed by a machine, e.g., an EPROM, a gate array, a programmable logic device (PLD), a client computer, or other machine that receives and loads the program code, the machine becomes a device for implementing the present invention. When implemented on a general-purpose processor, the program code combines with the processor to provide a unique device that operates to cause the functionality of the present invention. Additionally, any storage techniques used in connection with the present invention may be a combination of hardware and software.

[0072] Glossary

[0073] An API, or Application Programming Interface, is a set of rules and protocols that allow different software systems to communicate with each other. It defines the methods and data formats that programs can use to perform tasks such as requesting services or retrieving data from other software applications.

[0074] Cancel Location Request (CancelLocReq) refers to a message or procedure used in mobile networks, especially in the context of location-based services or roaming scenarios. A Cancel Location Request is typically sent by the HLR to the VLR when the HLR determines that the mobile device is no longer in a visited network or when the HLR wishes to cancel location information previously provided to the VLR. This can occur in various scenarios, such as when the mobile device returns to its home network, when it switches to another visited network, or when the mobile device is inactive or deregistered. When the VLR receives a Cancel Location Request, it updates its records and removes the location information for the particular mobile device. This maintains accurate and up-to-date location information for roaming devices and reduces unnecessary resource usage in the network.

[0075] Cancel Location Response (CancelLocRsp) refers to the procedure used by the Home Location Register (HLR) to inform a Visited Location Register (VLR) or Serving GPRS Support Node (SGSN) that the subscriber's location information should be removed from its database. The procedure is typically initiated when the subscriber's service is terminated or when the subscriber moves to a different VLR or SGSN. Cancel Location Response (CancelLocRsp) is a message sent back by the VLR or SGSN to the HLR to acknowledge successful receipt and processing of the cancel location request. The response confirms that the subscriber's location information has been removed from the VLR or SGSN as requested.

[0076] A cellular network refers to a communications network that uses radio frequency (RF) signals to provide wireless connectivity to mobile devices such as smartphones, tablets, and laptops. Cellular networks are designed with a grid of interconnected cells served by base stations, also known as cell sites or cell towers. These cells work together to create coverage areas that allow users to make calls, send text messages, and access the Internet on their devices. The term "cellular" comes from the way these networks divide geographic areas into smaller hexagonal or square regions called cells. Each cell has a base station that communicates with mobile devices within its coverage area. As a user moves from one cell to another, the cellular network automatically transitions the user's active connection from one base station to the next, ensuring seamless communication.

[0077] The Domain Name System (DNS) is used to map readable strings of characters (e.g., Syniver·com) to the numerical Internet Protocol addresses needed to locate services and devices.

[0078] HLR stands for Home Location Register and is a database that contains subscription data about subscribers who are authorized to use the GSM core network. HLRs store details of every SIM card issued by a mobile phone operator.

[0079] IMEI stands for International Mobile Equipment Identity. It is a specification used to identify multiple devices across multiple mobile networks. It is a unique 15-digit number assigned to each mobile device, such as a mobile phone or cellular-enabled tablet.

[0080] IMSI stands for International Mobile Subscriber Identity. It is a specification used to uniquely identify a subscriber to a mobile phone service. IMSI is used within GSM networks nationally and is adopted on almost all cellular networks. The IMSI is a 50-bit field, usually 15 digits, that identifies the home country and carrier of the phone. The 15-digit number has two parts. The first part consists of 6 digits in North American standard and 5 digits in European standard. IMSI identifies the GSM network operator in the particular country where the subscriber holds the account. The second part is assigned by the network operator to uniquely identify the subscriber. For GSM, UMTS and LTE networks, this number is set up on the SIM card, and in CDMA2000, on the phone directly or on the R-UIM card (CDMA2000 analog to the SIM card for GSM).

[0081] The Messaging Gateway (Messaging GW) handles messaging communications between the satellite and multiple cellular networks.

[0082] MMS (Multimedia Messaging Service) is an extension of the core SMS (Short Message Service) protocol, developed to allow the transmission of multimedia content via text messages. MMS messages can contain text, pictures, audio, and video, allowing mobile users to send and receive much more dynamic content than standard SMS.

[0083] Mobile device registration refers to the process of associating a mobile device with a particular network, either a cellular or satellite network, for the purpose of enabling communication services. This registration allows the network to recognize, authenticate, and manage the mobile device, and enables the mobile device to access voice, text, and data services.

[0084] Mobile Switching Center (MSC) means the Primary Service Delivery Node for GSM / CDMA, responsible for routing voice calls and SMS as well as other services. The MSC establishes and releases end-to-end connections, administers mobility and handover requirements during calls, overseas charging, and real-time prepaid account monitoring.

[0085] MSISDN stands for Mobile Station International Subscriber Directory Number and is configured for use by calling mobile device subscribers. The MSISDN is the mapping of a phone number to a mobile or cellular phone SIM card (or directly in hardware CDMA2000) and is the number that is normally dialed to connect a call to a mobile device. A SIM card has a unique IMSI and does not change, but the MSIDN can change over time (e.g., phone number portability).

[0086] OPID stands for operation identification.

[0087] RCS (Rich Communication Services) is a communications protocol intended to replace SMS and provide a richer, two-way experience for standard messaging on multiple devices. RCS supports high-resolution photo sharing, group messaging, multiple receipt reading, multiple indicator typing, and more. RCS is often seen as an evolution of SMS and MMS, providing a more engaging two-way form of text-based communication.

[0088] A satellite network is a communication system that uses satellites orbiting the Earth to provide wireless connectivity for voice, data, and multimedia services. Satellite networks enable communication between widely distributed locations or in areas where terrestrial infrastructure such as cellular networks or wired connections are limited or unavailable. In a satellite network, signals are transmitted from ground-based transmitters (known as Earth or terrestrial stations) to satellites in space. The satellites receive the signals, amplify them, and then retransmit them back to Earth, where they are received by other ground stations or users' satellite dishes. This communication process is often referred to as uplink (from Earth to satellite) and downlink (from satellite to Earth).

[0089] A satellite proxy network refers to an intermediate server or collection of servers that resides between two disparate network systems (e.g., satellite and cellular) and allows requests and responses to be sent and received. In the context of this invention, the satellite proxy network acts as an intermediary to manage SMS messages, but can include other types of messaging protocols, including but not limited to MMS, RCS, and others. This satellite proxy network receives incoming messages on the cellular network and forwards them to the destination satellite phone using its connection. Conversely, the satellite proxy network also receives messages from the satellite service and sends them to the intended recipient on the cellular network. In both cases, the satellite proxy network manages and reroutes the communication.

[0090] SMS stands for Short Message Service. SMS is a telecommunications service that allows users to send and receive text messages containing up to 160 characters (70 characters for languages ​​that use non-Latin alphabets such as Chinese and Arabic). SMS is a widely used feature of mobile phones and is supported by many wireless networks and devices. SMS messages are sent through a store-and-forward system that uses multiple cellular networks. When an SMS is sent, it is stored at a Short Message Service Center (SMSC) before being sent to the recipient's mobile device. If the recipient's device is unavailable or out of range, the SMSC stores the message and attempts to deliver it later.

[0091] Update Location Request (UpdateLocationReq) refers to a message or procedure used in the context of several mobile networks, especially GSM (Terrestrial Mobile Telecommunications System) and UMTS (Universal Mobile Telecommunications System) networks. This message is part of the location update procedure, which is essential to keep track of the subscriber's location as he moves within the network or roams to other networks. An Update Location Request is typically sent from a Mobile Switching Center / Visitor Location Register (MSC / VLR) to a Home Location Register (HLR) when a mobile device performs a location update. An Update Location Request can occur under various circumstances, such as (a) when the mobile device enters a new location area (LA) and needs to inform the network of its new location, (b) when the mobile device turns on or re-enters the network coverage area after being out of range, and (c) when a periodic location update is required by the network to maintain a record of the subscriber's latest location. The purpose of the Update Location Request message is to request the HLR to update its records with the subscriber's new location information. The HLR responds with an Update Location Confirm message indicating whether the request was successful or not. In addition to location updating, this procedure can also be used for several other purposes, such as authentication, to ensure that the mobile device is a valid subscriber and not an unauthorized device attempting to access the network.

[0092] Update Location Response (UpdateLocationRsp) refers to the message returned by the HLR in response to an Update Location Request. The Update Location Response confirms that the HLR has successfully updated the location information for the mobile subscriber. When the new MSC receives the Update Location Response, the MSC knows that the subscriber's location information is accurate and up-to-date, and can provide seamless mobile services to the subscriber within the new location area.

[0093] Visitor Location Register (VLR) means a database that stores data about mobile phones that have recently joined a particular area of ​​a mobile operator's network. The VLR keeps track of roamed mobile subscribers and communicates with the HLR to determine whether the mobile phone is a permanent or temporary subscriber.

[0094] The VMSC, or Visitor Location Registration Mobile Switching Center, is a key component of the mobile network infrastructure that manages the operation of mobile devices roaming within its coverage area. The Mobile Switching Center (MSC) is the primary service delivery node for GSM (Global System for Mobile Communications) and is responsible for fare ticketing, network interface, common channel signaling, etc. When a mobile device is roaming (i.e., operating outside its home network), the mobile device is served by what is known as the Visitor Location Registration Mobile Switching Center (VMSC). The VMSC performs a number of functions. For example, (a) the VMSC checks the visitor's mobile device's right to access the network and its services, (b) the VMSC routes calls to mobile devices within its jurisdiction, and (c) the VMSC manages the location updates of the mobile device to ensure that the network knows where to route the call. In the context of the present invention, the satellite proxy network registers as a VMSC in the Home Location Register (HLR) of the mobile device. This allows the satellite proxy network to manage the sending and receiving of messages related to the mobile device when the mobile device is operating in satellite mode.

[0095] The advantages set forth above and apparent from the foregoing disclosure are efficiently accomplished. Since certain changes may be made in the above configurations without departing from the scope of the invention, it is intended that all matter contained in the above disclosure or shown in the accompanying drawings be interpreted as illustrative and not in a limiting sense. The present invention enables cellular redirection services for messaging originating from non-cellular platforms (e.g., multiple satellite services). [Explanation of symbols]

[0096] 12 Device 13 Satellite 14 Satellite API Gateway 16 Messaging Gateway 18 Cellular Redirect 20 Database 24 Satellite Proxy 26 Customer Home Location Register (HLR) 28 Customer SMSC (Short Message Service Center) 34 Satellite Activation Request 36 SMS MT (Mobile Terminated) Message 38 Satellite Activation Request 40 Satellite Registration 40 Authorization Information Request 42 Authorization Confirmation 44a-44c Satellite Activation Confirmation 46 Satellite Activation Request 48 Satellite Activation Request 50 Satellite Activation Request 52 Authorization Information Request 53 Authorization Information Confirmation 54a Initial Failure Update Location Request 54b Location Request 56 Subscriber Data 58 Response 60...Update location response 61...Exception error 64...Inactivity period 66...Purge mobile station (MS) 70...Cancel registration 72...Cancel registration confirmation 74...Cancel satellite registration 76...Response 78...Offload request 80...Offload 82...SMS 84...Delivery gateway 86...Offload queue response 88...TDR billing record 92...SMSMT 94...SMSMO message

Claims

1. A method performed by a satellite proxy network for providing messaging services between a cellular network and a satellite network, comprising the steps of: receiving a special Short Message Service (SMS) message or an Application Programming Interface (API) call from a satellite service provider when a communications device operable in both a cellular mode and a satellite mode, the communications device having the same Mobile Station International Subscriber Directory Number (MSISDN) in both the cellular mode and the satellite mode, switches to the satellite mode, wherein the special SMS message or API call indicates that the communications device is connecting to the satellite network; the satellite proxy network registering as a visitor location registration mobile switching station (VMSC) in a home location register (HLR) of the communication device upon receiving the special SMS message or API call from the satellite service provider; the satellite proxy network serving as a VMSC for sending and receiving SMS messages associated with the communication device when the communication device is in the satellite mode; the satellite proxy network receiving an SMS from the communication device in the satellite mode and finally transmitting the SMS to a destination operator; and The satellite proxy network facilitates message exchange between the satellite service provider and the other device or operator by receiving SMS from the other device or operator and redirecting the SMS over a satellite connection to the communication device in the satellite mode, and handles messaging services to and from the communication device.

2. The method of claim 1 , wherein the communications device sends a deregistration message to the satellite proxy network when returning to the cellular mode.

3. The method of claim 2 , wherein the deregistration message indicates that the communications device has moved from the satellite network to the cellular network.

4. 3. The method of claim 2, wherein the satellite proxy network updates the HLR upon receiving the deregistration message from the communication device indicating a transition from the satellite network to the cellular network.

5. 5. The method of claim 4, further comprising the satellite proxy network sending a purge mobile station (MS) to the HLR, and the HLR returning a purge MS response to the satellite proxy network.

6. 6. The method of claim 5, wherein the purge MS is sent to the HLR in response to a timeout function representative of a period of inactivity between the communications device and the satellite proxy network.

7. The method of claim 5 , wherein the period of inactivity is between 5 minutes and 30 minutes.

8. 2. The method of claim 1, wherein in response to the HLR detecting that the communications device has been registered with another VMSC, the HLR sends a de-registration to the satellite proxy network.

9. 1. A system implemented by a satellite proxy network for providing messaging services between a cellular network and a satellite network, comprising: a communications interface configured to receive a special Short Message Service (SMS) message or an Application Programming Interface (API) call from a satellite service provider when a communications device operable in both a cellular mode and a satellite mode and having the same Mobile Station International Subscriber Directory Number (MSISDN) in both modes switches to the satellite mode, the special Short Message Service (SMS) message or the Application Programming Interface (API) call indicating that the communications device is connected to the satellite network; a registration component operably coupled to the communication interface, the registration component configured to register the satellite proxy network as a visitor location registration mobile switching center (VMSC) with a home location register (HLR) of the communication device upon receiving the special short message service (SMS) message or the application programming interface (API) call; a messaging component configured to serve as the VMSC to send and receive SMS messages related to the communication device when the communication device is in the satellite mode; a component configured to receive an SMS from the communication device when the communication device is in the satellite mode and to transmit the SMS to a destination operator; and a distribution component configured to receive SMS from other devices or operators and transmit the SMS to the communication device in the satellite mode via a satellite connection, facilitating message exchange between the satellite service provider and the other devices or operators, and handling messaging services from or to the communication device.

10. The system of claim 9 , further comprising a notification component configured to receive a deregistration message from the communication device when the communication device returns to the cellular mode.

11. 11. The system of claim 10, wherein the deregistration message indicates that the communications device has moved from the satellite network to the cellular network.

12. 11. The system of claim 10, further comprising an update component configured to update the Home Location Register (HLR) upon receiving the deregistration message from the communication device indicating a transition from the satellite network to the cellular network.

13. 13. The system of claim 12, wherein the update component is further configured to send a purged mobile station (MS) to the HLR, the HLR configured to return a purged MS in response to the satellite proxy network.

14. 14. The system of claim 13, wherein the purge MS is triggered by a timeout function indicative of a period of inactivity between the communication device and the satellite proxy network.

15. 15. The system of claim 14, wherein the period of inactivity is between 5 minutes and 30 minutes.

16. 13. The system of claim 12, wherein the HLR is further configured to send a de-registration to the satellite proxy network in response to detecting that the communication device has been registered with another Visitor Location Registration and Mobile Switching Center (VMSC).

17. A method performed by a satellite proxy network for providing messaging services between a cellular network and a satellite network, comprising the steps of: receiving a special Short Message Service (SMS) message or an Application Programming Interface (API) call from a satellite service provider when a communications device operable in both a cellular mode and a satellite mode, the communications device having the same Mobile Station International Subscriber Directory Number (MSISDN) in both the cellular mode and the satellite mode, switches to the satellite mode, wherein the special SMS message or API call indicates that the communications device is connecting to the satellite network; registering with a Home Location Register (HLR) of the communications device as a Visitor Location Register Mobile Switching Station (VMSC) upon receiving the special SMS message or API call from the satellite service provider; serving as a VMSC for sending and receiving SMS messages associated with said communications device when said communications device is in said satellite mode; receiving an SMS from the communication device in the satellite mode and transmitting the SMS to a destination operator; receiving SMS from other devices or operators and transmitting said SMS over a satellite connection to said communications device in said satellite mode, thereby facilitating message exchange between said satellite service provider and other devices or operators; receiving a deregistration message from the communication device when the communication device switches to the cellular mode, the deregistration message indicating that the communication device has moved from the satellite network to the cellular network; and updating the HLR upon receiving the deregistration message from the communication device indicating that the communication device has moved from the satellite network to the cellular network.

18. 20. The method of claim 17, further comprising the step of sending a purge mobile station (MS) to the HLR in response to a timeout function representative of a period of inactivity between the communication device and the satellite proxy network.

19. 20. The method of claim 18, wherein the period of inactivity is between 5 minutes and 30 minutes.

20. 20. The method of claim 17, comprising receiving, by the satellite proxy network, a de-registration from the HLR in response to the HLR detecting that the communications device has been registered with another VMSC.

Images