US20100233992A1 - Methods, systems, and computer readable media for short message service (sms) forwarding - Google Patents
Methods, systems, and computer readable media for short message service (sms) forwarding Download PDFInfo
- Publication number
- US20100233992A1 US20100233992A1 US12/722,141 US72214110A US2010233992A1 US 20100233992 A1 US20100233992 A1 US 20100233992A1 US 72214110 A US72214110 A US 72214110A US 2010233992 A1 US2010233992 A1 US 2010233992A1
- Authority
- US
- United States
- Prior art keywords
- message
- message service
- forwarding
- destination
- mobile terminated
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
- H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/214—Monitoring or handling of messages using selective forwarding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/58—Message adaptation for wireless communication
Definitions
- the subject matter described herein relates to delivering SMS messages. More specifically, the subject matter relates to methods, systems, and computer readable media for providing SMS message forwarding.
- call forwarding is a feature that allows an incoming call to a called party to be redirected to another telephone number of the called party's choosing.
- the first type of call forwarding is called unconditional forwarding and may include automatically forwarding all calls from a first telephone number to a second telephone number, regardless of any conditions. For example, if subscriber B has setup unconditional forwarding to C, all calls to B will be redirected to C.
- the second type of call forwarding is called conditional forwarding and may include initially trying to reach the called party at a first number, and if the called party is unavailable (i.e., the condition), forwarding the call to a second number. For example, if subscriber B has setup conditional forwarding to C, all calls to B will first be tried on B and when B is not available, the call will be redirected to C.
- One method includes performing steps by a message service message proxy separate from a short message service center and implemented on a computing platform including at least one processor.
- the steps include receiving a message service message routing information response message containing message service message routing information for a first destination.
- the response message is modified to direct a mobile terminated message service message intended for the first destination to the message service message proxy.
- the mobile terminated message service message is then received at the message service message proxy and the message service message proxy determines whether a message service message forwarding feature is enabled for the first destination.
- it is determined whether the mobile terminated message service message is eligible for forwarding to a second destination.
- signaling is initiated to forward the mobile terminated message service message to the second destination.
- a system for providing SMS forwarding includes a message service message proxy for receiving a message service message routing information response message containing message service message routing information for a first destination.
- the response message is modified by the message service message proxy to direct a mobile terminated message service message intended for the first destination to the message service message proxy.
- the mobile terminated message service message is then received at the message service message proxy and the message service message proxy determines whether a message service message forwarding feature is enabled for the first destination.
- the message service message proxy determines whether the mobile terminated message service message is eligible for forwarding to a second destination.
- the message service message proxy initiates signaling to forward the mobile terminated message service message to the second destination.
- the subject matter described herein for providing SMS forwarding may be implemented using a non-transitory computer readable medium to having stored thereon executable instructions that when executed by the processor of a computer control the processor to perform steps.
- Exemplary non-transitory computer readable media suitable for implementing the subject matter described herein include chip memory devices or disk memory devices accessible by a processor, programmable logic devices, and application specific integrated circuits.
- a computer readable medium that implements the subject matter described herein may be located on a single computing platform or may be distributed across plural computing platforms.
- FIG. 1 is a message flow diagram illustrating an exemplary basic unconditional SMS forwarding scenario according to an embodiment of the subject matter described herein;
- FIG. 2 is a message flow diagram illustrating an exemplary enhanced unconditional SMS forwarding scenario according to an embodiment of the subject matter described herein;
- FIG. 3 is a message flow diagram illustrating an exemplary conditional SMS forwarding scenario according to an embodiment of the subject matter described herein;
- FIG. 4 is a message flow diagram illustrating an exemplary conditional SMS forwarding scenario according to an embodiment of the subject matter described herein;
- FIG. 5 is a message flow diagram illustrating an exemplary conditional SMS forwarding scenario according to an embodiment of the subject matter described herein;
- FIG. 6 is a message flow diagram illustrating an exemplary SMS forwarding scenario including lawful surveillance and intercept functionality according to an embodiment of the subject matter described herein;
- FIG. 7 is a flow chart showing exemplary steps for providing SMS forwarding according to an embodiment of the subject matter described herein.
- FIG. 8 is a block diagram of an exemplary system for providing SMS forwarding according to an embodiment of the subject matter described herein.
- the subject matter described herein includes methods and systems for providing SMS forwarding. Specifically, a new network element for providing conditional and/or unconditional SMS Forwarding service is disclosed.
- GSM global system for mobile communications
- MT/SMs mobile terminated short messages
- SMSC short message service centre
- a GSM subscriber always submits a mobile originated short message (MO/SM) to its home SMSC and a GSM SMSC always delivers the MT/SM directly.
- MO/SM mobile originated short message
- SMS messages do not flow between SMSCs. Therefore, if a mobile operator implements SMS forwarding service in its SMSC, the service would only affect the SMS messages submitted by its own subscribers, which may be undesirable. Instead, it may be more desirable for any SMS forwarding service to affect the short messages delivered to its subscribers. Due to the limitations of conventional SMSCs and their operations, the SMS forwarding service described herein may be implemented by a new network element. This network element, which may hereinafter be referred to as a “message service message proxy server” or “MT/SM proxy”, should receive all MT/SMs of any subscriber that registers with the SMS forwarding service.
- the message service message proxy may be separate from the SMSC and may be implemented on a computing platform having one or more processors.
- FIG. 1 is a message flow diagram illustrating an exemplary basic unconditional SMS forwarding scenario according to an embodiment of the subject matter described herein. It may be appreciated that basic unconditional SMS forwarding may be the simplest method to implement unconditional forwarding by intercepting the SendRoutingInfoForSm request from the SMSC, changing the mobile station international subscriber directory number (MSISDN) parameter, and relaying the request to the home location register (HLR).
- MSISDN mobile station international subscriber directory number
- SMSC 100 may be responsible for relaying and store-and-forwarding of short messages between a short messaging entity (SME) and mobile station.
- SME short messaging entity
- An SME is an entity that may receive or send short messages.
- the SME may be located in the fixed network, a mobile station, or another service center.
- MT/SM proxy 102 may be responsible for providing SMS forwarding service to subscribers.
- HLR C 104 is a database that contains details of each mobile phone subscriber that is authorized to use the GSM core network. It is appreciated that there can be several logical and/or physical HLRs per public land mobile network (PLMN).
- MSC C 106 may process requests for service connections from mobile devices and land line callers and route calls between base stations and the public switched telephone network (PSTN). MSC C 106 may also receive dialed digits, create and interpret call processing tones, and route call paths.
- PSTN public switched telephone network
- SMSC 100 may begin by sending a SendRoutingInfoForSm Request message for MSISDN B to MT/SM proxy 102 .
- MT/SM proxy 102 may modify the MSISDN parameter from B to C, and forward a SendRoutingInfoForSm Request message including MSISDN C to HLR C 104 .
- HLR C 104 may return a SendRoutingInforForSm Response message including message parameters for international mobile subscriber identity (IMSI) C and serving MSC C 106 in step 112 .
- IMSI international mobile subscriber identity
- SMSC 100 may then receive and forward the SendRoutingInfoForSm Response message, unmodified, to SMSC 100 in step 114 .
- SMSC 100 may send an MtForwardSm Request message including IMSI C and an identifier for serving MSC C to serving MSC C 106 .
- Serving MSC C 106 may then return MtForwardSm Response message in step 118 .
- the basic unconditional forwarding described above may have some drawbacks. For example, it may be difficult to detect (and break) forwarding loops.
- a simple forwarding loop is a case where B has setup forwarding to C and C to B.
- Using basic unconditional forwarding if B and C are subscribers of different mobile networks, a loop might result in SendRoutingInfoForSm requests bouncing between B's network and C's network.
- Another drawback to basic unconditional SMS forwarding is that while some MT/SM types may be eligible for forwarding, others may not.
- Exemplary MT/SM types that should not be forwarded may include a subscriber identify module (SIM) data download message and a GSM status report message. With a SIM data download message, a mobile operator provisions settings on a mobile.
- SIM subscriber identify module
- an SMSC informs the sender of an SMS about the delivery result of the SMS (e.g. successful, failed, expired).
- a method for enhanced unconditional forwarding will now be described below with respect to FIG. 2 .
- FIG. 2 is a message flow diagram illustrating an exemplary enhanced unconditional SMS forwarding scenario according to an embodiment of the subject matter described herein.
- the enhanced unconditional forwarding method may transparently relay the SendRoutingInfoForSm request to the HLR and modify the SendRoutingInfoForSm response in such a way that the MtForwardSm request is routed to the MT/SM Proxy.
- MT/SM Proxy 102 may check whether the MT/SM is eligible for forwarding. If the MT/SM is eligible for forwarding, MT/SM Proxy 102 may issue a SendRoutingInfoForSm and a MtForwardSm for the forwarding destination.
- FIG. 2 subscriber B is the MT/SM's recipient and has set up unconditional forwarding to C.
- FIG. 2 includes HLR B 200 that is the HLR for B.
- SMSC 100 may begin by sending a SendRoutingInfoForSm Request message to MT/SM proxy 102 .
- MT/SM proxy 102 may forward the SendRoutingInfoForSm Request message, unmodified, to HLR B 200 .
- HLR B 200 may return a SendRoutingInfoForSm Response message including IMSI B and an identifier for serving MSC B (not shown) to MT/SM proxy 102 in step 206 .
- MT/SM proxy 102 may manipulate the IMSI and serving MSC parameters to enforce termination of MtForwardSm on MT/SM proxy 102 with the possibility to correlate SendRoutingInfoForSm and MtForwardSm requests. Therefore, MT/SM proxy 102 may send SendRoutingInfoForSm Response message including IMSI B′ and serving MSC B′ parameters to SMSC 100 in step 208 . In response, SMSC 100 may send a MtForwardSm Request message including parameters for IMSI B′ and serving MSC B′ to MT/SM proxy 102 in step 210 .
- MT/SM proxy 102 may determine whether the MtForwardSm Request is eligible for SMS forwarding service. In this case, MtForwardSm Request is eligible, and therefore, in step 212 , MT/SM proxy 102 may send SendRoutingInfoForSm Request message including MSISDN C for HLR C 104 . In step 214 , HLR C 104 may return a SendRoutingInfoForSm Response message to MT/SM proxy 102 . In step 216 , MT/SM proxy 102 may then generate and send a MtForwardSm Request message including parameters for IMSI C and serving MSC C to serving MSC C 106 . Serving MSC C 106 may return a MtForwardSm response message to MT/SM proxy 102 in step 218 and MT/SM proxy 102 may forward the MtForwardSm response message to SMSC 100 in step 220 .
- FIG. 3-5 illustrate message flows for conditional SMS forwarding.
- Conditional forwarding works similar to the enhanced conditional forwarding, however, before querying the HLR for the forward destination, MT/SM Proxy 102 may attempt to deliver the MT/SM to the original recipient. If delivery fails (e.g., an Absent Subscriber error), then MT/SM proxy 102 may attempt to deliver the MT/SM to the designated forward destination.
- subscriber B is the MT/SM's recipient and has setup conditional forwarding to C. It is appreciated that FIGS. 3-5 do not display the SendRoutingInfoForSm dialogue for B as this dialogue is the same as for the enhanced unconditional forwarding scenario described above with respect to FIG. 2 .
- FIGS. 3-5 illustrate three different conditional forwarding scenarios. In FIG. 3 , B is available. In FIG. 4 , B is unavailable and C is available. In FIGS. 5 , B and C are both unavailable.
- FIG. 3 is a message flow diagram illustrating an exemplary conditional SMS forwarding scenario according to an embodiment of the subject matter described herein.
- serving MSC B 300 may send MtForwardSm Request message including message parameters for IMSI B′ and serving MSC B′ to MT/SM proxy 102 .
- MT/SM proxy 102 may modify the message parameters to refer to IMSI B and serving MSC B and send the modified MtForwardSm Request message to serving MSC B 300 .
- serving MSC B 300 may return a MtForwardSm Response message to MT/SM proxy 102 in step 306 .
- MT/SM proxy 102 may forward the MtForwardSm response message to SMSC 100 .
- FIG. 4 is a message flow diagram illustrating an exemplary conditional SMS forwarding scenario according to an embodiment of the subject matter described herein.
- SMSC 100 may send MtForwardSm Request message including message parameters for IMSI B′ and serving MSC B′ to MT/SM proxy 102 .
- MT/SM proxy 102 may modify the message parameters to refer to IMSI B and serving MSC B and send the modified MtForwardSm Request message to serving MSC B 300 .
- serving MSC B 300 may return a MtForwardSm Response message to MT/SM proxy 102 indicating that subscriber B is not available (e.g., absent subscriber error) in step 404 .
- MT/SM proxy 102 may send a SendRoutingInfoForSm Request message including MSISDN C to HLR C 104 .
- HLR C 104 may respond by returning a SendRoutingInfoForSm Response message to MT/SM proxy 102 in step 408 .
- MT/SM proxy 102 may send a MtForwardSm Request message including IMSI C and serving MSC C to serving MSC C 106 . If delivery to C was successful, serving MSC C 106 may return a MtForwardSm response message indicating success to MT/SM proxy 102 in step 412 .
- MT/SM proxy 102 may forward the MtForwardSm response message indicating success to SMSC 100 .
- FIG. 5 is a message flow diagram illustrating an exemplary conditional SMS forwarding scenario according to an embodiment of the subject matter described herein.
- SMSC 100 may send MtForwardSm Request message including message parameters for IMSI B′ and serving MSC B′ to MT/SM proxy 102 .
- MT/SM proxy 102 may modify the message parameters to refer to IMSI B and serving MSC B and send the modified MtForwardSm Request message to serving MSC B 300 .
- serving MSC B 300 may return a MtForwardSm Response message to MT/SM proxy 102 indicating that subscriber B is not available (e.g., absent subscriber error) in step 504 .
- MT/SM proxy 102 may send a SendRoutingInfoForSm Request message including MSISDN C to HLR C 104 .
- HLR C 104 may respond by returning a SendRoutingInfoForSm Response message to MT/SM proxy 102 in step 508 .
- MT/SM proxy 102 may send a MtForwardSm Request message including IMSI C and serving MSC C to serving MSC C 106 .
- C is not available and therefore delivery will not be successful.
- serving MSC C 106 may return a MtForwardSm response message indicating that subscriber C is also not available (e.g., absent subscriber error) to MT/SM proxy 102 in step 512 .
- MT/SM proxy 102 may forward the MtForwardSm response message including the error to SMSC 100 .
- a simple approach for preventing forwarding loops may include denying SMS forwarding service to subscribers of other mobile networks. For example, if B has set up SMS forwarding to C, MT/SM Proxy 102 would only forward to C if B and C belong to the same mobile network.
- a more enhanced method to prevent forwarding loops may be to add a marker to MtForwardSm requests for the forwarding destination. While 3rd Generation Partnership Project (3GPP) technical specification (TS) 23.040, which is incorporated by reference herein, does not define a specific forwarding marker, it does however allow a vendor to define its own information elements in the user data header. A specific range for information element identifier has been allocated for this purpose. MT/SM proxy 102 may add a vendor-specific information element for messages to forwarded messages. Thus, an enhanced method to prevent forwarding loops may be that whenever MT/SM Proxy 102 receives an MtForwardSm request, MT/SM Proxy 102 may check whether the vendor-specific information element for forwarding is present.
- 3GPP 3rd Generation Partnership Project
- TS technical specification
- MT/SM Proxy 102 may inspect the data of the information element to determine whether the MtForwardSm can be forwarded. It is appreciated that adding a vendor-specific information element may cause the User Data parameter of an MtForwardSM to be extended.
- International Patent No. WO 2005/101872 entitled, “Method for Preventing the Delivery of Short Message Service Message Spam” describes one method for extending the User Data parameter and enforcing the MtForwardSm to the MT/SM proxy and is incorporated by reference herein.
- FIG. 6 is a message flow diagram illustrating an exemplary SMS forwarding scenario including lawful surveillance and intercept functionality according to an embodiment of the subject matter described herein. Shown in FIG. 6 is an embodiment of the subject matter described herein that includes call detail record generation function/lawful surveillance (CDR/LS) function 600 which is associated with MT/SM proxy 102 . According to one aspect, CDR/LS 600 function may be adapted to generate and store a record that documents the forwarding of a message service message from an original called subscriber/B-party to a forward-to called subscriber/B-party.
- CDR/LS 600 function may be adapted to generate and store a record that documents the forwarding of a message service message from an original called subscriber/B-party to a forward-to called subscriber/B-party.
- the CDR/LS record may include a complete copy of the forwarded messaging service message (e.g., routing layer info+payload info), or may alternatively contain a portion of the information in the forwarded message service message.
- Exemplary message parameters stored in the record may include, but are not limited to, originating SMSC identifier, calling subscriber/A-party, called party/B-party, originating point code (OPC), destination point code (DPC), global title address (GTA), signaling connection control part (SCCP) layer information, TCAP layer information, MAP layer information.
- OPC originating point code
- DPC destination point code
- GTA global title address
- SCCP signaling connection control part
- the CDR/LS record may contain some, or all, of the messaging service message (e.g., header information, payload).
- the record may also include date and timestamp information.
- the CDR/LS record may include sufficient information to associate the original messaging service message with the forwarded-to message because such provide information may be useful in tracing the delivery process associated with a messaging service message that has been forwarded.
- CDR/LS 600 may store or cache CDR/LS records in a database co-located with MT/SM proxy 102 .
- CDR/LS 600 may generate records and transmit these records to a remote application/storage facility (not shown) via a local area network (LAN), wide area network (WAN), or other network connection.
- LAN local area network
- WAN wide area network
- CDR/LS function 600 may include, or have access to, a list of subscriber identifiers that have been placed under lawful surveillance (i.e., watched entities). CDR/LS function 600 may be adapted to check the forwarded-to subscriber identifier and determine if the forwarded to subscriber is a watched entity. If the forwarded-to subscriber is a watched entity, then CDR/LS 600 may generate a record of the forwarding event (as described above). The record may be stored or relayed to a surveillance authority. An exemplary lawful surveillance scenario is described below.
- SMSC 100 may send a SendRoutingInfoForSm request message including MSISDN B to MT/SM proxy 102 .
- MT/SM proxy 102 may modify the MSISDN parameter to include MSISDN C and, in step 604 , may forward modified SendRoutingInfoForSm request message to HLR C 104 .
- HLR C 104 may return a SendRoutingInfoForSm response message including message parameters IMSI C and serving MSC C.
- MT/SM proxy 102 may forward the SendRoutingInfoForSm message to SMSC 100 .
- SMSC 100 may send a MtForwardSm request message including message parameters IMSI C and serving MSC C to serving MSC C 106 .
- serving MSC C 106 may return a MtForwardSm response message to SMSC 100 .
- FIG. 7 is a flow chart showing exemplary steps for providing SMS forwarding according to an embodiment of the subject matter described herein.
- a message service message routing information response message may be received, where the response message contains routing information for a first destination.
- a SendRoutingInfoForSm response message for MSISDN B that includes IMSI B and serving MSC Bmay be received by an MT/SM proxy from the HLR of B.
- the response message may be modified to direct a MT/SM that was intended for the first destination to a MT/SM proxy instead.
- the MSISDN included in the SendRoutingInfoForSm Request message may be modified from MSISDN B to MSISDN B′.
- the MT/SM may be received by the MT/SM proxy.
- an MtForwardSm request message including IMSI B′ and serving MSC B′ may be received by the MT/SM proxy 102 from originating SMSC 100 .
- step 706 it may be determined whether a message service forwarding feature is enabled for the first destination.
- MT/SM proxy 102 may consult a list of subscriber identifiers associated with the SMS forwarding service in order to determine whether subscriber B has enabled SMS forwarding service.
- SMS forwarding service has not been enabled for the first destination
- control may proceed to step 708 where conventional message delivery may be performed.
- conventional message delivery may include when an VMSC/SGSN indicates a short message delivery failure, the SMSC may send a message to the HLR using the MAP_REPORT_SM_DELIVERY_STATUS procedure.
- the SMSC may indicate the reason for the delivery failure and request that the SMSC be put on a list of SMSCs wanting to be notified when the destination party becomes available again.
- the HLR may set a flag against the destination account, indicating that it is unavailable for short message delivery, and store the SMSC's address in a message waiting data (MWD) list for the destination party.
- Valid flags may include Mobile Not Reachable Flag (MNRF), Memory Capacity Exceeded Flag (MCEF) and Mobile Not Reachable for GPRS (MNRG).
- MNRF Mobile Not Reachable Flag
- MEF Memory Capacity Exceeded Flag
- MNRG Mobile Not Reachable for GPRS
- the HLR may be informed of a subscriber becoming available for short message delivery in several ways. First, where the subscriber has been detached from the network, a reattach may trigger a Location Update to the HLR. Second, where the subscriber has been out of coverage, but not fully detached from the network, upon coming back into coverage the subscriber will respond to page requests from the Visitor Location Register (VLR) and the VLR may then send a Ready-for-SM (mobile present) message to the HLR. Third, where the MS formerly had its memory full, but now it does not (e.g., the subscriber deletes some texts), a Ready-for-SM (memory available) message may be sent from the VMSCNLR to the HLR.
- VLR Visitor Location Register
- the HLR may send an AlertSC mobile application part (MAP) message to each of the SMSCs registered in the MWD list for the subscriber, causing the SMSC to start the short message delivery process again.
- MAP AlertSC mobile application part
- the SMSC may go into a retry schedule, attempting to periodically deliver the SM at certain time intervals, without getting an alert.
- the retry schedule interval may depend on the original failure cause so that transient network failures may result in a short retry schedule, while out-of-coverage network failures may result in a longer retry schedule.
- SMS forwarding service is enabled for the first destination, it may be determined in step 710 whether the MT/SM is eligible for forwarding to a second destination. For example, the MT/SM may determine whether forwarded-to destination C is eligible for forwarding by consulting a list of subscriber identifiers associated with the SMS forwarding service. Like above, if SMS forwarding service is not enabled for the second destination, control may proceed to step 708 where conventional message delivery may be performed.
- SMS forwarding service is enabled for the second destination
- signaling may be initiated to forward the MT/SM to the second destination.
- the MT/SM may send a SendRoutingInfoForSm request message for MSISDN C to the HLR for C.
- the MT/SM may send a MtForwardSm request for IMSI C to serving MSC C.
- the MtForwardSm response message received from serving MSC C may be forwarded by the MT/SM to the originating SMSC.
- FIG. 8 is a block diagram of an exemplary system for providing SMS forwarding according to an embodiment of the subject matter described herein.
- message service message proxy 102 may be separate from an SMSC and may be implemented on a computing platform including at least one processor (not shown).
- Message service message proxy 102 may include network interface 800 and message service message forwarding module 802 .
- Network interface 800 may receive a message service message routing information response message containing message service message routing information for a first destination.
- Message service message forwarding module 802 may modify the response message to direct a mobile terminated message service message intended for the first destination to message service message proxy 102 .
- Message service message forwarding module 802 may receive the mobile terminated message service message and determine whether a message service message forwarding feature is enabled for the first destination. In response to determining that a message service message forwarding feature is enabled for the first destination, message service message forwarding module 802 may determine whether the mobile terminated message service message is eligible for forwarding to a second destination and, in response to determining the mobile terminated message service message is eligible for forwarding, message service message forwarding module 802 may initiate signaling to forward the mobile terminated message service message to the second destination.
Abstract
Description
- This application claims the benefit of U.S. Provisional Patent Application Ser. No. 61/159,337 filed on Mar. 11, 2009; the disclosure of which is incorporated herein by reference in its entirety.
- The subject matter described herein relates to delivering SMS messages. More specifically, the subject matter relates to methods, systems, and computer readable media for providing SMS message forwarding.
- Today, it is possible to setup forwarding for calls (hereinafter, “call forwarding”). Call forwarding is a feature that allows an incoming call to a called party to be redirected to another telephone number of the called party's choosing. Two different types of call forwarding may exist. The first type of call forwarding is called unconditional forwarding and may include automatically forwarding all calls from a first telephone number to a second telephone number, regardless of any conditions. For example, if subscriber B has setup unconditional forwarding to C, all calls to B will be redirected to C. The second type of call forwarding is called conditional forwarding and may include initially trying to reach the called party at a first number, and if the called party is unavailable (i.e., the condition), forwarding the call to a second number. For example, if subscriber B has setup conditional forwarding to C, all calls to B will first be tried on B and when B is not available, the call will be redirected to C.
- In contrast to forwarding services provided for calls, no such service is available for forwarding SMS messages. In other words, present SMS message delivery systems do not provide for forwarding SMS messages, either conditionally or unconditionally, as is provided for calls.
- Accordingly, in light of these difficulties, a need exists for improved methods, systems, and computer readable media for SMS message delivery.
- Methods, systems, and computer readable media for SMS forwarding are disclosed. One method includes performing steps by a message service message proxy separate from a short message service center and implemented on a computing platform including at least one processor. The steps include receiving a message service message routing information response message containing message service message routing information for a first destination. The response message is modified to direct a mobile terminated message service message intended for the first destination to the message service message proxy. The mobile terminated message service message is then received at the message service message proxy and the message service message proxy determines whether a message service message forwarding feature is enabled for the first destination. In response to determining that a message service message forwarding feature is enabled for the first destination, it is determined whether the mobile terminated message service message is eligible for forwarding to a second destination. In response to determining the mobile terminated message service message is eligible for forwarding, signaling is initiated to forward the mobile terminated message service message to the second destination.
- A system for providing SMS forwarding is also disclosed. The system includes a message service message proxy for receiving a message service message routing information response message containing message service message routing information for a first destination. The response message is modified by the message service message proxy to direct a mobile terminated message service message intended for the first destination to the message service message proxy. The mobile terminated message service message is then received at the message service message proxy and the message service message proxy determines whether a message service message forwarding feature is enabled for the first destination. In response to determining that a message service message forwarding feature is enabled for the first destination, the message service message proxy determines whether the mobile terminated message service message is eligible for forwarding to a second destination. In response to determining the mobile terminated message service message is eligible for forwarding, the message service message proxy initiates signaling to forward the mobile terminated message service message to the second destination.
- The subject matter described herein for providing SMS forwarding may be implemented using a non-transitory computer readable medium to having stored thereon executable instructions that when executed by the processor of a computer control the processor to perform steps. Exemplary non-transitory computer readable media suitable for implementing the subject matter described herein include chip memory devices or disk memory devices accessible by a processor, programmable logic devices, and application specific integrated circuits. In addition, a computer readable medium that implements the subject matter described herein may be located on a single computing platform or may be distributed across plural computing platforms.
- The subject matter described herein will now be explained with reference to the accompanying drawings of which:
-
FIG. 1 is a message flow diagram illustrating an exemplary basic unconditional SMS forwarding scenario according to an embodiment of the subject matter described herein; -
FIG. 2 is a message flow diagram illustrating an exemplary enhanced unconditional SMS forwarding scenario according to an embodiment of the subject matter described herein; -
FIG. 3 is a message flow diagram illustrating an exemplary conditional SMS forwarding scenario according to an embodiment of the subject matter described herein; -
FIG. 4 is a message flow diagram illustrating an exemplary conditional SMS forwarding scenario according to an embodiment of the subject matter described herein; -
FIG. 5 is a message flow diagram illustrating an exemplary conditional SMS forwarding scenario according to an embodiment of the subject matter described herein; -
FIG. 6 is a message flow diagram illustrating an exemplary SMS forwarding scenario including lawful surveillance and intercept functionality according to an embodiment of the subject matter described herein; -
FIG. 7 is a flow chart showing exemplary steps for providing SMS forwarding according to an embodiment of the subject matter described herein; and -
FIG. 8 is a block diagram of an exemplary system for providing SMS forwarding according to an embodiment of the subject matter described herein. - The subject matter described herein includes methods and systems for providing SMS forwarding. Specifically, a new network element for providing conditional and/or unconditional SMS Forwarding service is disclosed. When a global system for mobile communications (GSM) subscriber registers with the SMS Forwarding service described herein, it may be desirable for all of its mobile terminated short messages (MT/SMs) to be subject to the SMS forwarding service. However, a conventional short message service centre (SMSC) may not be the best network element to perform SMS forwarding because not all MT/SMs for a given GSM subscriber flow through its own SMSC. For example, in conventional SMS messaging, a GSM subscriber always submits a mobile originated short message (MO/SM) to its home SMSC and a GSM SMSC always delivers the MT/SM directly. SMS messages do not flow between SMSCs. Therefore, if a mobile operator implements SMS forwarding service in its SMSC, the service would only affect the SMS messages submitted by its own subscribers, which may be undesirable. Instead, it may be more desirable for any SMS forwarding service to affect the short messages delivered to its subscribers. Due to the limitations of conventional SMSCs and their operations, the SMS forwarding service described herein may be implemented by a new network element. This network element, which may hereinafter be referred to as a “message service message proxy server” or “MT/SM proxy”, should receive all MT/SMs of any subscriber that registers with the SMS forwarding service. The message service message proxy may be separate from the SMSC and may be implemented on a computing platform having one or more processors.
-
FIG. 1 is a message flow diagram illustrating an exemplary basic unconditional SMS forwarding scenario according to an embodiment of the subject matter described herein. It may be appreciated that basic unconditional SMS forwarding may be the simplest method to implement unconditional forwarding by intercepting the SendRoutingInfoForSm request from the SMSC, changing the mobile station international subscriber directory number (MSISDN) parameter, and relaying the request to the home location register (HLR). - Referring to
FIG. 1 , network components may includeSMSC 100, MT/SM proxy 102, HLRC 104, and serving mobile switching center (MSC)C 106. SMSC 100 may be responsible for relaying and store-and-forwarding of short messages between a short messaging entity (SME) and mobile station. An SME is an entity that may receive or send short messages. The SME may be located in the fixed network, a mobile station, or another service center. MT/SM proxy 102 may be responsible for providing SMS forwarding service to subscribers. HLR C 104 is a database that contains details of each mobile phone subscriber that is authorized to use the GSM core network. It is appreciated that there can be several logical and/or physical HLRs per public land mobile network (PLMN). MSC C 106 may process requests for service connections from mobile devices and land line callers and route calls between base stations and the public switched telephone network (PSTN).MSC C 106 may also receive dialed digits, create and interpret call processing tones, and route call paths. - In
FIG. 1 , subscriber B is the intended recipient of the MT/SM and has set up unconditional forwarding to C. For example, instep 108,SMSC 100 may begin by sending a SendRoutingInfoForSm Request message for MSISDN B to MT/SM proxy 102. Instep 110, MT/SM proxy 102 may modify the MSISDN parameter from B to C, and forward a SendRoutingInfoForSm Request message including MSISDN C toHLR C 104. In response,HLR C 104 may return a SendRoutingInforForSm Response message including message parameters for international mobile subscriber identity (IMSI) C and servingMSC C 106 instep 112. MT/SM proxy 102 may then receive and forward the SendRoutingInfoForSm Response message, unmodified, toSMSC 100 instep 114. Instep 116,SMSC 100 may send an MtForwardSm Request message including IMSI C and an identifier for serving MSC C to servingMSC C 106. ServingMSC C 106 may then return MtForwardSm Response message instep 118. - The basic unconditional forwarding described above may have some drawbacks. For example, it may be difficult to detect (and break) forwarding loops. A simple forwarding loop is a case where B has setup forwarding to C and C to B. Using basic unconditional forwarding, however, if B and C are subscribers of different mobile networks, a loop might result in SendRoutingInfoForSm requests bouncing between B's network and C's network. Another drawback to basic unconditional SMS forwarding is that while some MT/SM types may be eligible for forwarding, others may not. Exemplary MT/SM types that should not be forwarded may include a subscriber identify module (SIM) data download message and a GSM status report message. With a SIM data download message, a mobile operator provisions settings on a mobile. With a GSM status report message, an SMSC informs the sender of an SMS about the delivery result of the SMS (e.g. successful, failed, expired). In order to overcome the drawbacks of basic unconditional SMS forwarding, a method for enhanced unconditional forwarding will now be described below with respect to
FIG. 2 . -
FIG. 2 is a message flow diagram illustrating an exemplary enhanced unconditional SMS forwarding scenario according to an embodiment of the subject matter described herein. In contrast to the basic unconditional forwarding method described above with respect toFIG. 1 , the enhanced unconditional forwarding method may transparently relay the SendRoutingInfoForSm request to the HLR and modify the SendRoutingInfoForSm response in such a way that the MtForwardSm request is routed to the MT/SM Proxy. Upon receipt of the MtForwardSm request, MT/SM Proxy 102 may check whether the MT/SM is eligible for forwarding. If the MT/SM is eligible for forwarding, MT/SM Proxy 102 may issue a SendRoutingInfoForSm and a MtForwardSm for the forwarding destination. - In
FIG. 2 , subscriber B is the MT/SM's recipient and has set up unconditional forwarding to C. In addition to the network components shown inFIG. 1 ,FIG. 2 includesHLR B 200 that is the HLR for B. Instep 202,SMSC 100 may begin by sending a SendRoutingInfoForSm Request message to MT/SM proxy 102. Instep 204, MT/SM proxy 102 may forward the SendRoutingInfoForSm Request message, unmodified, toHLR B 200.HLR B 200 may return a SendRoutingInfoForSm Response message including IMSI B and an identifier for serving MSC B (not shown) to MT/SM proxy 102 instep 206. Instep 208, MT/SM proxy 102 may manipulate the IMSI and serving MSC parameters to enforce termination of MtForwardSm on MT/SM proxy 102 with the possibility to correlate SendRoutingInfoForSm and MtForwardSm requests. Therefore, MT/SM proxy 102 may send SendRoutingInfoForSm Response message including IMSI B′ and serving MSC B′ parameters toSMSC 100 instep 208. In response,SMSC 100 may send a MtForwardSm Request message including parameters for IMSI B′ and serving MSC B′ to MT/SM proxy 102 instep 210. - Also in
step 210, MT/SM proxy 102 may determine whether the MtForwardSm Request is eligible for SMS forwarding service. In this case, MtForwardSm Request is eligible, and therefore, instep 212, MT/SM proxy 102 may send SendRoutingInfoForSm Request message including MSISDN C forHLR C 104. Instep 214,HLR C 104 may return a SendRoutingInfoForSm Response message to MT/SM proxy 102. Instep 216, MT/SM proxy 102 may then generate and send a MtForwardSm Request message including parameters for IMSI C and serving MSC C to servingMSC C 106. ServingMSC C 106 may return a MtForwardSm response message to MT/SM proxy 102 instep 218 and MT/SM proxy 102 may forward the MtForwardSm response message toSMSC 100 instep 220. -
FIG. 3-5 illustrate message flows for conditional SMS forwarding. Conditional forwarding works similar to the enhanced conditional forwarding, however, before querying the HLR for the forward destination, MT/SM Proxy 102 may attempt to deliver the MT/SM to the original recipient. If delivery fails (e.g., an Absent Subscriber error), then MT/SM proxy 102 may attempt to deliver the MT/SM to the designated forward destination. InFIGS. 3-5 , subscriber B is the MT/SM's recipient and has setup conditional forwarding to C. It is appreciated thatFIGS. 3-5 do not display the SendRoutingInfoForSm dialogue for B as this dialogue is the same as for the enhanced unconditional forwarding scenario described above with respect toFIG. 2 .FIGS. 3-5 illustrate three different conditional forwarding scenarios. InFIG. 3 , B is available. InFIG. 4 , B is unavailable and C is available. InFIGS. 5 , B and C are both unavailable. -
FIG. 3 is a message flow diagram illustrating an exemplary conditional SMS forwarding scenario according to an embodiment of the subject matter described herein. Referring toFIG. 3 , in addition to the network components shown inFIGS. 1 and 2 , servingMSC B 300 is shown. Instep 302,SMSC 100 may send MtForwardSm Request message including message parameters for IMSI B′ and serving MSC B′ to MT/SM proxy 102. Instep 304, MT/SM proxy 102 may modify the message parameters to refer to IMSI B and serving MSC B and send the modified MtForwardSm Request message to servingMSC B 300. In response, servingMSC B 300 may return a MtForwardSm Response message to MT/SM proxy 102 instep 306. Finally, instep 308, MT/SM proxy 102 may forward the MtForwardSm response message toSMSC 100. -
FIG. 4 is a message flow diagram illustrating an exemplary conditional SMS forwarding scenario according to an embodiment of the subject matter described herein. Referring toFIG. 4 , instep 400,SMSC 100 may send MtForwardSm Request message including message parameters for IMSI B′ and serving MSC B′ to MT/SM proxy 102. Instep 402, MT/SM proxy 102 may modify the message parameters to refer to IMSI B and serving MSC B and send the modified MtForwardSm Request message to servingMSC B 300. In response, servingMSC B 300 may return a MtForwardSm Response message to MT/SM proxy 102 indicating that subscriber B is not available (e.g., absent subscriber error) instep 404. Instep 406, MT/SM proxy 102 may send a SendRoutingInfoForSm Request message including MSISDN C toHLR C 104.HLR C 104 may respond by returning a SendRoutingInfoForSm Response message to MT/SM proxy 102 instep 408. Instep 410, MT/SM proxy 102 may send a MtForwardSm Request message including IMSI C and serving MSC C to servingMSC C 106. If delivery to C was successful, servingMSC C 106 may return a MtForwardSm response message indicating success to MT/SM proxy 102 instep 412. Instep 414, MT/SM proxy 102 may forward the MtForwardSm response message indicating success toSMSC 100. -
FIG. 5 is a message flow diagram illustrating an exemplary conditional SMS forwarding scenario according to an embodiment of the subject matter described herein. Referring toFIG. 5 , instep 500,SMSC 100 may send MtForwardSm Request message including message parameters for IMSI B′ and serving MSC B′ to MT/SM proxy 102. Instep 502, MT/SM proxy 102 may modify the message parameters to refer to IMSI B and serving MSC B and send the modified MtForwardSm Request message to servingMSC B 300. In response, servingMSC B 300 may return a MtForwardSm Response message to MT/SM proxy 102 indicating that subscriber B is not available (e.g., absent subscriber error) instep 504. Instep 506, MT/SM proxy 102 may send a SendRoutingInfoForSm Request message including MSISDN C toHLR C 104.HLR C 104 may respond by returning a SendRoutingInfoForSm Response message to MT/SM proxy 102 instep 508. Instep 510, MT/SM proxy 102 may send a MtForwardSm Request message including IMSI C and serving MSC C to servingMSC C 106. In contrast toFIG. 4 , C is not available and therefore delivery will not be successful. Thus, servingMSC C 106 may return a MtForwardSm response message indicating that subscriber C is also not available (e.g., absent subscriber error) to MT/SM proxy 102 instep 512. Instep 514, MT/SM proxy 102 may forward the MtForwardSm response message including the error toSMSC 100. - A simple approach for preventing forwarding loops may include denying SMS forwarding service to subscribers of other mobile networks. For example, if B has set up SMS forwarding to C, MT/
SM Proxy 102 would only forward to C if B and C belong to the same mobile network. - A more enhanced method to prevent forwarding loops may be to add a marker to MtForwardSm requests for the forwarding destination. While 3rd Generation Partnership Project (3GPP) technical specification (TS) 23.040, which is incorporated by reference herein, does not define a specific forwarding marker, it does however allow a vendor to define its own information elements in the user data header. A specific range for information element identifier has been allocated for this purpose. MT/
SM proxy 102 may add a vendor-specific information element for messages to forwarded messages. Thus, an enhanced method to prevent forwarding loops may be that whenever MT/SM Proxy 102 receives an MtForwardSm request, MT/SM Proxy 102 may check whether the vendor-specific information element for forwarding is present. If the information is present, MT/SM Proxy 102 may inspect the data of the information element to determine whether the MtForwardSm can be forwarded. It is appreciated that adding a vendor-specific information element may cause the User Data parameter of an MtForwardSM to be extended. International Patent No. WO 2005/101872 entitled, “Method for Preventing the Delivery of Short Message Service Message Spam” describes one method for extending the User Data parameter and enforcing the MtForwardSm to the MT/SM proxy and is incorporated by reference herein. -
FIG. 6 is a message flow diagram illustrating an exemplary SMS forwarding scenario including lawful surveillance and intercept functionality according to an embodiment of the subject matter described herein. Shown inFIG. 6 is an embodiment of the subject matter described herein that includes call detail record generation function/lawful surveillance (CDR/LS) function 600 which is associated with MT/SM proxy 102. According to one aspect, CDR/LS 600 function may be adapted to generate and store a record that documents the forwarding of a message service message from an original called subscriber/B-party to a forward-to called subscriber/B-party. The CDR/LS record may include a complete copy of the forwarded messaging service message (e.g., routing layer info+payload info), or may alternatively contain a portion of the information in the forwarded message service message. Exemplary message parameters stored in the record may include, but are not limited to, originating SMSC identifier, calling subscriber/A-party, called party/B-party, originating point code (OPC), destination point code (DPC), global title address (GTA), signaling connection control part (SCCP) layer information, TCAP layer information, MAP layer information. In session initiation protocol (SIP) messaging embodiments, the CDR/LS record may contain some, or all, of the messaging service message (e.g., header information, payload). The record may also include date and timestamp information. - The CDR/LS record may include sufficient information to associate the original messaging service message with the forwarded-to message because such provide information may be useful in tracing the delivery process associated with a messaging service message that has been forwarded.
- CDR/
LS 600 may store or cache CDR/LS records in a database co-located with MT/SM proxy 102. In an alternate embodiment, CDR/LS 600 may generate records and transmit these records to a remote application/storage facility (not shown) via a local area network (LAN), wide area network (WAN), or other network connection. - In another embodiment, CDR/
LS function 600 may include, or have access to, a list of subscriber identifiers that have been placed under lawful surveillance (i.e., watched entities). CDR/LS function 600 may be adapted to check the forwarded-to subscriber identifier and determine if the forwarded to subscriber is a watched entity. If the forwarded-to subscriber is a watched entity, then CDR/LS 600 may generate a record of the forwarding event (as described above). The record may be stored or relayed to a surveillance authority. An exemplary lawful surveillance scenario is described below. - Referring to
FIG. 6 , instep 602,SMSC 100 may send a SendRoutingInfoForSm request message including MSISDN B to MT/SM proxy 102. MT/SM proxy 102 may modify the MSISDN parameter to include MSISDN C and, instep 604, may forward modified SendRoutingInfoForSm request message toHLR C 104. Instep 606,HLR C 104 may return a SendRoutingInfoForSm response message including message parameters IMSI C and serving MSC C. Instep 608, MT/SM proxy 102 may forward the SendRoutingInfoForSm message toSMSC 100. In response, instep 610,SMSC 100 may send a MtForwardSm request message including message parameters IMSI C and serving MSC C to servingMSC C 106. Finally, instep 612, servingMSC C 106 may return a MtForwardSm response message toSMSC 100. -
FIG. 7 is a flow chart showing exemplary steps for providing SMS forwarding according to an embodiment of the subject matter described herein. Referring toFIG. 7 , instep 700, a message service message routing information response message may be received, where the response message contains routing information for a first destination. For example, a SendRoutingInfoForSm response message for MSISDN B that includes IMSI B and serving MSC Bmay be received by an MT/SM proxy from the HLR of B. - In
step 702, the response message may be modified to direct a MT/SM that was intended for the first destination to a MT/SM proxy instead. For example, the MSISDN included in the SendRoutingInfoForSm Request message may be modified from MSISDN B to MSISDN B′. - In
step 704, the MT/SM may be received by the MT/SM proxy. For example, an MtForwardSm request message including IMSI B′ and serving MSC B′ may be received by the MT/SM proxy 102 from originatingSMSC 100. - In
step 706, it may be determined whether a message service forwarding feature is enabled for the first destination. For example, MT/SM proxy 102 may consult a list of subscriber identifiers associated with the SMS forwarding service in order to determine whether subscriber B has enabled SMS forwarding service. - If SMS forwarding service has not been enabled for the first destination, then control may proceed to step 708 where conventional message delivery may be performed. For example, conventional message delivery may include when an VMSC/SGSN indicates a short message delivery failure, the SMSC may send a message to the HLR using the MAP_REPORT_SM_DELIVERY_STATUS procedure. During the MAP_REPORT_SM_DELIVERY_STATUS procedure, the SMSC may indicate the reason for the delivery failure and request that the SMSC be put on a list of SMSCs wanting to be notified when the destination party becomes available again. The HLR may set a flag against the destination account, indicating that it is unavailable for short message delivery, and store the SMSC's address in a message waiting data (MWD) list for the destination party. Valid flags may include Mobile Not Reachable Flag (MNRF), Memory Capacity Exceeded Flag (MCEF) and Mobile Not Reachable for GPRS (MNRG). The HLR may then start responding to SRI-for-SM requests with a failure, indicating the failure reason, and automatically adding the requesting SMSC's address to the MWD list for the destination party.
- The HLR may be informed of a subscriber becoming available for short message delivery in several ways. First, where the subscriber has been detached from the network, a reattach may trigger a Location Update to the HLR. Second, where the subscriber has been out of coverage, but not fully detached from the network, upon coming back into coverage the subscriber will respond to page requests from the Visitor Location Register (VLR) and the VLR may then send a Ready-for-SM (mobile present) message to the HLR. Third, where the MS formerly had its memory full, but now it does not (e.g., the subscriber deletes some texts), a Ready-for-SM (memory available) message may be sent from the VMSCNLR to the HLR. Upon receipt of an indication that the destination party is now ready to receive short messages, the HLR may send an AlertSC mobile application part (MAP) message to each of the SMSCs registered in the MWD list for the subscriber, causing the SMSC to start the short message delivery process again.
- Additionally, the SMSC may go into a retry schedule, attempting to periodically deliver the SM at certain time intervals, without getting an alert. The retry schedule interval may depend on the original failure cause so that transient network failures may result in a short retry schedule, while out-of-coverage network failures may result in a longer retry schedule.
- If SMS forwarding service is enabled for the first destination, it may be determined in
step 710 whether the MT/SM is eligible for forwarding to a second destination. For example, the MT/SM may determine whether forwarded-to destination C is eligible for forwarding by consulting a list of subscriber identifiers associated with the SMS forwarding service. Like above, if SMS forwarding service is not enabled for the second destination, control may proceed to step 708 where conventional message delivery may be performed. - If SMS forwarding service is enabled for the second destination, in
step 712, signaling may be initiated to forward the MT/SM to the second destination. For example, the MT/SM may send a SendRoutingInfoForSm request message for MSISDN C to the HLR for C. After receiving a SendRoutingInfoForSm response message from HLR C, the MT/SM may send a MtForwardSm request for IMSI C to serving MSC C. The MtForwardSm response message received from serving MSC C may be forwarded by the MT/SM to the originating SMSC. -
FIG. 8 is a block diagram of an exemplary system for providing SMS forwarding according to an embodiment of the subject matter described herein. Referring toFIG. 8 , messageservice message proxy 102 may be separate from an SMSC and may be implemented on a computing platform including at least one processor (not shown). Messageservice message proxy 102 may includenetwork interface 800 and message servicemessage forwarding module 802.Network interface 800 may receive a message service message routing information response message containing message service message routing information for a first destination. Message servicemessage forwarding module 802 may modify the response message to direct a mobile terminated message service message intended for the first destination to messageservice message proxy 102. Message servicemessage forwarding module 802 may receive the mobile terminated message service message and determine whether a message service message forwarding feature is enabled for the first destination. In response to determining that a message service message forwarding feature is enabled for the first destination, message servicemessage forwarding module 802 may determine whether the mobile terminated message service message is eligible for forwarding to a second destination and, in response to determining the mobile terminated message service message is eligible for forwarding, message servicemessage forwarding module 802 may initiate signaling to forward the mobile terminated message service message to the second destination. - It will be understood that various details of the subject matter described herein may be changed without departing from the scope of the subject matter described herein. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation, as the subject matter described herein is defined by the claims as set forth hereinafter.
Claims (15)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/722,141 US20100233992A1 (en) | 2009-03-11 | 2010-03-11 | Methods, systems, and computer readable media for short message service (sms) forwarding |
US13/658,128 US8909266B2 (en) | 2009-03-11 | 2012-10-23 | Methods, systems, and computer readable media for short message service (SMS) forwarding |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15933709P | 2009-03-11 | 2009-03-11 | |
US12/722,141 US20100233992A1 (en) | 2009-03-11 | 2010-03-11 | Methods, systems, and computer readable media for short message service (sms) forwarding |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/658,128 Continuation US8909266B2 (en) | 2009-03-11 | 2012-10-23 | Methods, systems, and computer readable media for short message service (SMS) forwarding |
Publications (1)
Publication Number | Publication Date |
---|---|
US20100233992A1 true US20100233992A1 (en) | 2010-09-16 |
Family
ID=42729101
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/722,141 Abandoned US20100233992A1 (en) | 2009-03-11 | 2010-03-11 | Methods, systems, and computer readable media for short message service (sms) forwarding |
US13/658,128 Expired - Fee Related US8909266B2 (en) | 2009-03-11 | 2012-10-23 | Methods, systems, and computer readable media for short message service (SMS) forwarding |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/658,128 Expired - Fee Related US8909266B2 (en) | 2009-03-11 | 2012-10-23 | Methods, systems, and computer readable media for short message service (SMS) forwarding |
Country Status (2)
Country | Link |
---|---|
US (2) | US20100233992A1 (en) |
WO (1) | WO2010105043A2 (en) |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120258743A1 (en) * | 2009-07-02 | 2012-10-11 | Nec Corporation | Femtocell base station, gateway system, map-gw apparatus, communication system, control method, and program |
WO2013105976A1 (en) * | 2012-01-13 | 2013-07-18 | Nokia Siemens Networks Oy | Native short message service for long term evolution |
WO2013133564A1 (en) * | 2012-03-09 | 2013-09-12 | 주식회사 케이티 | Method and apparatus for providing short message services for packet switching-only subscription in mobile communications network |
US20130311654A1 (en) * | 2011-04-29 | 2013-11-21 | Huawei Technologies Co., Ltd. | Internet Service Control Method, and Relevant Device and System |
US20140128113A1 (en) * | 2011-04-04 | 2014-05-08 | Samsung Electronics Co., Ltd. | Messaging over a network |
US8909266B2 (en) | 2009-03-11 | 2014-12-09 | Tekelec Netherlands Group, B.V. | Methods, systems, and computer readable media for short message service (SMS) forwarding |
US8908864B2 (en) | 2009-03-11 | 2014-12-09 | Tekelec Netherlands Group, B.V. | Systems, methods, and computer readable media for detecting and mitigating address spoofing in messaging service transactions |
US20150109966A1 (en) * | 2012-03-09 | 2015-04-23 | Kt Corporation | Method and apparatus for providing short message services for packet switching-only subscription in mobile communications network |
US9565564B2 (en) | 2012-12-07 | 2017-02-07 | At&T Intellectual Property I, L.P. | Providing a masked short message service in a wireless network |
CN106797369A (en) * | 2014-08-27 | 2017-05-31 | 瑞典爱立信有限公司 | Call forwarding during packet voice is intercepted is detected |
US10277552B2 (en) | 2015-02-09 | 2019-04-30 | Markport Limited | Relating to messaging gateways |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11463484B2 (en) | 2020-08-29 | 2022-10-04 | Oracle International Corporation | Methods, systems, and computer readable media for routing of packets for lawful interception |
US11700510B2 (en) | 2021-02-12 | 2023-07-11 | Oracle International Corporation | Methods, systems, and computer readable media for short message delivery status report validation |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US731980A (en) * | 1903-03-09 | 1903-06-23 | Alva T Upton | Riding-harrow. |
US20020187794A1 (en) * | 2001-05-04 | 2002-12-12 | Comverse Network Systems, Ltd. | SMS automatic reply and automatic handling |
US20040171393A1 (en) * | 2001-04-18 | 2004-09-02 | Robert Harding | Managing text message traffic in mobile telephone networks |
US20060136560A1 (en) * | 2004-12-06 | 2006-06-22 | Roamware Inc. | Scalable message forwarding |
US20070093260A1 (en) * | 2005-06-23 | 2007-04-26 | Billing John D | Method and System for Customizing Distributed Short Message Routing |
US7269431B1 (en) * | 2004-01-16 | 2007-09-11 | Cingular Wireless Ii, Llc | System for forwarding SMS messages to other devices |
US20080171549A1 (en) * | 2007-01-11 | 2008-07-17 | Cingular Wireless Ii, Llc | Multi-way messaging with forwarding |
US20080207181A1 (en) * | 2007-02-28 | 2008-08-28 | Roamware | Method and system for applying value added services on messages sent to a subscriber without affecting the subscriber's mobile communication |
Family Cites Families (113)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB0328606D0 (en) | 2003-11-21 | 2004-01-14 | Intellprop Ltd | Telecommunications services apparatus and method |
US6047327A (en) | 1996-02-16 | 2000-04-04 | Intel Corporation | System for distributing electronic information to a targeted group of users |
US5684951A (en) | 1996-03-20 | 1997-11-04 | Synopsys, Inc. | Method and system for user authorization over a multi-user computer system |
US5768509A (en) | 1996-04-08 | 1998-06-16 | Adc Newnet, Inc. | Short message server without local customer database |
US9418381B2 (en) | 2000-04-14 | 2016-08-16 | Citigroup Credit Services, Inc. (USA) | Method and system for notifying customers of transaction opportunities |
SE508514C2 (en) | 1997-02-14 | 1998-10-12 | Ericsson Telefon Ab L M | Method and apparatus for transmitting short messages in a telecommunication system comprising a mobile communication system |
FI106603B (en) | 1998-03-26 | 2001-02-28 | Nokia Networks Oy | Sending multicast services to the target area |
US6308075B1 (en) | 1998-05-04 | 2001-10-23 | Adc Telecommunications, Inc. | Method and apparatus for routing short messages |
US6597688B2 (en) | 1998-06-12 | 2003-07-22 | J2 Global Communications, Inc. | Scalable architecture for transmission of messages over a network |
KR100325961B1 (en) | 1999-07-16 | 2002-03-07 | Method and system for providing customized information during call setup process in telecommunication systems | |
EP1230815B1 (en) | 1999-11-17 | 2005-10-19 | Swisscom Mobile AG | Method and system for preparing and transmitting sms messages in a mobile radio network |
US20020010745A1 (en) | 1999-12-09 | 2002-01-24 | Eric Schneider | Method, product, and apparatus for delivering a message |
US7136634B1 (en) | 1999-12-22 | 2006-11-14 | Nokia Corporation | System and method for displaying information included in predetermined messages automatically |
FI110975B (en) | 1999-12-22 | 2003-04-30 | Nokia Corp | Prevention of fraud in telecommunication systems |
US6564055B1 (en) | 2000-01-21 | 2003-05-13 | Telecommunication Systems, Inc. | Intelligent roaming database (IRDB) updating |
AU2001234620A1 (en) | 2000-01-28 | 2001-08-07 | Ibeam Broadcasting Corporation | Method and apparatus for client-side authentication and stream selection in a content distribution system |
EP2160039B1 (en) | 2000-03-07 | 2012-06-06 | Tekelec | Screening of mobile application part (map) messages |
US20040221011A1 (en) | 2000-04-10 | 2004-11-04 | Steven Smith | High volume electronic mail processing systems and methods having remote transmission capability |
US6577723B1 (en) | 2000-07-13 | 2003-06-10 | At&T Wireless Service, Inc. | Application of TCAP criteria in SCCP routing |
US7394818B1 (en) | 2000-09-22 | 2008-07-01 | Qwest Communications International Inc. | Extended multi-line hunt group communication |
FI114000B (en) | 2000-11-08 | 2004-07-15 | Mikko Kalervo Vaeaenaenen | Electronic short message and marketing procedure and corresponding devices |
US7155001B2 (en) | 2001-10-24 | 2006-12-26 | Sbc Properties, L.P. | System and method for restricting and monitoring telephone calls |
EP1213931A3 (en) | 2000-12-05 | 2003-03-19 | Siemens Aktiengesellschaft | Method for sending and receiving Short Messages in a mobile radio network |
US7177917B2 (en) | 2000-12-27 | 2007-02-13 | Softwired Ag | Scaleable message system |
FI112153B (en) | 2000-12-28 | 2003-10-31 | Nokia Corp | Management of messages in a communication system |
US7072976B2 (en) | 2001-01-04 | 2006-07-04 | Sun Microsystems, Inc. | Scalable routing scheme for a multi-path interconnection fabric |
US7343317B2 (en) | 2001-01-18 | 2008-03-11 | Nokia Corporation | Real-time wireless e-coupon (promotion) definition based on available segment |
US6947738B2 (en) | 2001-01-18 | 2005-09-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Multimedia messaging service routing system and method |
FI115744B (en) | 2001-02-08 | 2005-06-30 | Nokia Corp | communication Service |
KR20020071296A (en) | 2001-03-06 | 2002-09-12 | 삼성전자 주식회사 | Method for forwarding short message in mobile telecommunication system |
WO2002076077A1 (en) | 2001-03-16 | 2002-09-26 | Leap Wireless International, Inc. | Method and system for distributing content over a wireless communications system |
US7533409B2 (en) | 2001-03-22 | 2009-05-12 | Corente, Inc. | Methods and systems for firewalling virtual private networks |
SE0101087D0 (en) | 2001-03-26 | 2001-03-26 | Obnex Technologies Hb | System for distribution of position-dependent information |
US20020147928A1 (en) | 2001-04-10 | 2002-10-10 | Motorola, Inc. | Method of information dissemination in a network of end terminals |
TW511365B (en) | 2001-05-15 | 2002-11-21 | Corbett Wall | Method allowing individual user to record song and forward to others for listening by connecting to a service provider with telecommunication device signal |
GB2393886B (en) | 2001-06-22 | 2005-05-11 | Emblaze Systems Ltd | MMS system and method with protocol conversion suitable for mobile/portable handset display |
KR20030000491A (en) * | 2001-06-25 | 2003-01-06 | 에스케이 텔레콤주식회사 | Method for forwarding a short message |
US7389118B2 (en) | 2001-06-29 | 2008-06-17 | Nokia Corporation | System and method for person-to-person messaging with a value-added service |
WO2003024136A1 (en) | 2001-09-12 | 2003-03-20 | Aircross Co., Ltd. | Push advertisement in mobile communications network and mobile terminal suitable for the same |
US20030069991A1 (en) | 2001-10-09 | 2003-04-10 | Brescia Paul T. | Location-based address provision |
US6996579B2 (en) | 2001-11-02 | 2006-02-07 | At&T Corp. | E-coupon service for location-aware mobile commerce which determines whether to supply requested e-coupons based on the number of requests received in a processing cycle, and a threshold number of requests required to make expected returns from redeemed coupons greater than advertising fees |
US7116972B1 (en) | 2001-11-16 | 2006-10-03 | Sprint Spectrum L.P. | Method and system for control over call handling |
US7072667B2 (en) | 2001-12-31 | 2006-07-04 | Nokia Corporation | Location information service for a cellular telecommunications network |
US7644436B2 (en) | 2002-01-24 | 2010-01-05 | Arxceo Corporation | Intelligent firewall |
ITPI20020025A1 (en) | 2002-04-18 | 2003-10-20 | Pietro Baracco | METHOD TO MODIFY THE TEXT OF A MESSAGE SENT BETWEEN TWO TELEPHONE TERMINALS |
WO2004010257A2 (en) | 2002-07-19 | 2004-01-29 | M-Qube, Inc. | System and method to initiate a mobile data communication utilizing a trigger system |
US20040019695A1 (en) * | 2002-07-25 | 2004-01-29 | International Business Machines Corporation | Messaging system and method using alternative message delivery paths |
FR2844948B1 (en) | 2002-09-23 | 2005-01-07 | Eastman Kodak Co | METHOD FOR ARCHIVING MULTIMEDIA MESSAGES |
US20040203581A1 (en) | 2002-10-07 | 2004-10-14 | Msafe Ltd. | Method system and device for monitoring data pushed to a wireless communication device |
US20050021666A1 (en) | 2002-10-08 | 2005-01-27 | Dinnage David M. | System and method for interactive communication between matched users |
KR100511300B1 (en) | 2002-12-31 | 2005-08-31 | 엘지전자 주식회사 | Method for enhanced short message service |
DE10303958B4 (en) | 2003-01-31 | 2005-03-03 | Siemens Ag | Method and system for inserting a multimedia message multiple element into a multimedia message |
US7248857B1 (en) | 2004-02-27 | 2007-07-24 | Cingular Wireless Ii, Llc | System and method for enhanced message notification |
DE602004010098T3 (en) | 2003-05-06 | 2014-09-04 | Apple Inc. | METHOD FOR MODIFYING A MESSAGE STORAGE AND TRANSMISSION NETWORK SYSTEM AND DATA ANSWERING SYSTEM |
CA2528452C (en) | 2003-05-08 | 2017-04-18 | Ari Kahn | Call management protocol for insufficient credit |
WO2004102345A2 (en) | 2003-05-09 | 2004-11-25 | Tekelec | Methods and systems for providing short message gateway functionality in a telecommunications network |
US7299050B2 (en) | 2003-05-12 | 2007-11-20 | Tekelec | Methods and systems for generating, distributing, and screening commercial content |
EP1705885B1 (en) | 2003-05-15 | 2013-02-13 | Huawei Technologies Co., Ltd. | A system and method for providing rbt in communication network |
CA2526415C (en) | 2003-05-16 | 2014-09-16 | Gerald Hewes | Mobile messaging short code translation and routing system and method |
US20040243719A1 (en) | 2003-05-28 | 2004-12-02 | Milt Roselinsky | System and method for routing messages over disparate networks |
US7660898B2 (en) | 2003-07-29 | 2010-02-09 | At&T Intellectual Property I, L.P. | Presence enhanced telephony service architecture |
US20080125117A1 (en) | 2004-02-18 | 2008-05-29 | John Yue Jun Jiang | Method and system for providing roaming services to outbound roamers using home network Gateway Location Register |
WO2005048019A2 (en) | 2003-09-04 | 2005-05-26 | Emc Corporation | Data message mirroring and redirection |
US7447219B2 (en) | 2003-09-29 | 2008-11-04 | Redknee Inc. | System and method for implementing a universal messaging gateway (UMG) |
CN1625146A (en) | 2003-12-02 | 2005-06-08 | 华为技术有限公司 | Method and system for realizing sharing intelligent route |
US20050130685A1 (en) | 2003-12-12 | 2005-06-16 | Mark Jenkin | Method and apparatus for inserting information into an unused portion of a text message |
US8112103B2 (en) | 2004-01-16 | 2012-02-07 | Kuang-Chao Eric Yeh | Methods and systems for mobile device messaging |
GB0406119D0 (en) | 2004-03-18 | 2004-04-21 | Telsis Holdings Ltd | Telecommunications services apparatus and method |
EP1730975A1 (en) | 2004-03-29 | 2006-12-13 | Intellprop Limited | Telecommunications services apparatus and method for modifying the routing of mobile terminated short messages (sms) |
US7961663B2 (en) | 2004-04-05 | 2011-06-14 | Daniel J. LIN | Peer-to-peer mobile instant messaging method and device |
WO2005101863A2 (en) | 2004-04-12 | 2005-10-27 | Bayne Anthony J | System and method for the distribution of advertising and associated coupons via mobile media platforms |
US7403537B2 (en) | 2004-04-14 | 2008-07-22 | Tekelec | Methods and systems for mobile application part (MAP) screening in transit networks |
EP1736016B1 (en) | 2004-04-14 | 2015-06-24 | MBalance Research B.V. | Method for preventing the delivery of short message service message spam |
US7120455B1 (en) | 2004-05-20 | 2006-10-10 | Cellco Partnership | Method and system for mobile instant messaging using multiple interfaces |
US7155243B2 (en) | 2004-06-15 | 2006-12-26 | Tekelec | Methods, systems, and computer program products for content-based screening of messaging service messages |
CN101053264B (en) | 2004-08-14 | 2011-03-23 | 基鲁萨有限公司 | Methods for identifying messages and communicating with users of a multimodal message service |
US20060047572A1 (en) | 2004-08-26 | 2006-03-02 | Jeffery Moore | Text and multimedia messaging-based layered service and contact method, auction method and method of conducting business |
IES20040693A2 (en) | 2004-10-14 | 2006-04-19 | Anam Mobile Ltd | A messaging system and method |
ATE415790T1 (en) | 2004-10-27 | 2008-12-15 | Intellprop Ltd | DEVICE AND METHOD FOR TELECOMMUNICATION SERVICES |
GB0425905D0 (en) | 2004-11-25 | 2004-12-29 | Intellprop Ltd | Telecommunications services apparatus and method |
US7870201B2 (en) | 2004-12-03 | 2011-01-11 | Clairmail Inc. | Apparatus for executing an application function using a mail link and methods therefor |
US7454164B2 (en) | 2004-12-28 | 2008-11-18 | Lucent Technologies Inc. | Providing a multimedia message with a multimedia messaging service message in a mobile environment |
US7941165B2 (en) | 2005-03-02 | 2011-05-10 | Cisco Technology, Inc. | System and method for providing a proxy in a short message service (SMS) environment |
US20060211406A1 (en) | 2005-03-17 | 2006-09-21 | Nokia Corporation | Providing security for network subscribers |
US20060218613A1 (en) | 2005-03-22 | 2006-09-28 | Bushnell William J | System and method for acquiring on-line content via wireless communication device |
US8014762B2 (en) | 2005-03-31 | 2011-09-06 | Qualcomm Incorporated | Time and location-based non-intrusive advertisements and informational messages |
US8099114B2 (en) | 2005-07-28 | 2012-01-17 | At&T Mobility Ii Llc | Personal short codes for SMS |
EP1935204A4 (en) | 2005-09-23 | 2013-04-03 | Grape Technology Group Inc | Enhanced directory assistance system and method including location and search functions |
US8677020B2 (en) | 2005-10-17 | 2014-03-18 | Amobee Inc. | Device, system and method of wireless delivery of targeted advertisements |
US20080051066A1 (en) | 2005-12-05 | 2008-02-28 | Fonemine, Inc. | Digital personal assistant and automated response system |
IL173011A (en) | 2006-01-08 | 2012-01-31 | Picscout Ltd | Image insertion for cellular text messaging |
US20070168432A1 (en) | 2006-01-17 | 2007-07-19 | Cibernet Corporation | Use of service identifiers to authenticate the originator of an electronic message |
US20070206747A1 (en) | 2006-03-01 | 2007-09-06 | Carol Gruchala | System and method for performing call screening |
US7817987B2 (en) | 2006-03-07 | 2010-10-19 | Motorola, Inc. | Apparatus and method for handling messaging service message adaptation |
US7912908B2 (en) | 2006-03-27 | 2011-03-22 | Alcatel-Lucent Usa Inc. | Electronic message forwarding control |
US7747264B2 (en) | 2006-05-18 | 2010-06-29 | Myriad Group Ag | Method and apparatus for delivering advertisements to mobile users |
US8170584B2 (en) | 2006-06-06 | 2012-05-01 | Yahoo! Inc. | Providing an actionable event in an intercepted text message for a mobile device based on customized user information |
US9219952B2 (en) | 2006-06-09 | 2015-12-22 | Starscriber Corporation | Voiding calls to signal supplementary services |
KR20080006225A (en) * | 2006-07-11 | 2008-01-16 | 에스케이 텔레콤주식회사 | Service system and method of instant transmission premium sms |
US8121624B2 (en) | 2006-07-25 | 2012-02-21 | Alcatel Lucent | Message spoofing detection via validation of originating switch |
US7606202B2 (en) | 2006-07-28 | 2009-10-20 | Tekelec | Methods, systems, and computer program products for offloading call control services from a first network of a first type to a second network of a second type |
US8204057B2 (en) | 2006-10-26 | 2012-06-19 | Tekelec Global, Inc. | Methods, systems, and computer program products for providing an enriched messaging service in a communications network |
US8199892B2 (en) | 2006-10-26 | 2012-06-12 | Tekelec | Methods, systems, and computer program products for providing a call attempt triggered messaging service in a communications network |
US20080113677A1 (en) | 2006-11-11 | 2008-05-15 | Rajeev Kumar Madnawat | Mobile to mobile service invocation framework using text messsaging |
KR100850734B1 (en) | 2006-12-13 | 2008-08-06 | 삼성전자주식회사 | Method For Transmitting Message Of Portable Terminal |
US20080161028A1 (en) | 2007-01-03 | 2008-07-03 | Tekelec | Methods, systems and computer program products for a redundant, geographically diverse, and independently scalable message service (MS) content store |
US7930208B2 (en) | 2007-03-30 | 2011-04-19 | Wmode Incorporated | Method and system for delivery of advertising content in short message service (SMS) messages |
KR20080111175A (en) | 2007-03-30 | 2008-12-23 | (주)옴니텔 | System and method for advertisement using free sms |
US20080287150A1 (en) | 2007-04-16 | 2008-11-20 | John Yue Jun Jiang | Method and system for inserting advertisment content into a text message |
US8326265B2 (en) | 2008-10-17 | 2012-12-04 | Tekelec Netherlands Group, B.V. | Methods, systems, and computer readable media for detection of an unauthorized service message in a network |
US20100210292A1 (en) | 2009-02-16 | 2010-08-19 | Eloy Johan Lambertus Nooren | Extending a text message with content |
US20100235911A1 (en) | 2009-03-11 | 2010-09-16 | Eloy Johan Lambertus Nooren | Systems, methods, and computer readable media for detecting and mitigating address spoofing in messaging service transactions |
US20100233992A1 (en) | 2009-03-11 | 2010-09-16 | Eloy Johan Lambertus Nooren | Methods, systems, and computer readable media for short message service (sms) forwarding |
-
2010
- 2010-03-11 US US12/722,141 patent/US20100233992A1/en not_active Abandoned
- 2010-03-11 WO PCT/US2010/026964 patent/WO2010105043A2/en active Application Filing
-
2012
- 2012-10-23 US US13/658,128 patent/US8909266B2/en not_active Expired - Fee Related
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US731980A (en) * | 1903-03-09 | 1903-06-23 | Alva T Upton | Riding-harrow. |
US20040171393A1 (en) * | 2001-04-18 | 2004-09-02 | Robert Harding | Managing text message traffic in mobile telephone networks |
US7761105B2 (en) * | 2001-04-18 | 2010-07-20 | Solent Text Limited | Managing text message traffic in mobile telephone networks |
US20020187794A1 (en) * | 2001-05-04 | 2002-12-12 | Comverse Network Systems, Ltd. | SMS automatic reply and automatic handling |
US7269431B1 (en) * | 2004-01-16 | 2007-09-11 | Cingular Wireless Ii, Llc | System for forwarding SMS messages to other devices |
US20060136560A1 (en) * | 2004-12-06 | 2006-06-22 | Roamware Inc. | Scalable message forwarding |
US20070093260A1 (en) * | 2005-06-23 | 2007-04-26 | Billing John D | Method and System for Customizing Distributed Short Message Routing |
US20080171549A1 (en) * | 2007-01-11 | 2008-07-17 | Cingular Wireless Ii, Llc | Multi-way messaging with forwarding |
US20080207181A1 (en) * | 2007-02-28 | 2008-08-28 | Roamware | Method and system for applying value added services on messages sent to a subscriber without affecting the subscriber's mobile communication |
Cited By (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8909266B2 (en) | 2009-03-11 | 2014-12-09 | Tekelec Netherlands Group, B.V. | Methods, systems, and computer readable media for short message service (SMS) forwarding |
US8908864B2 (en) | 2009-03-11 | 2014-12-09 | Tekelec Netherlands Group, B.V. | Systems, methods, and computer readable media for detecting and mitigating address spoofing in messaging service transactions |
US20120258743A1 (en) * | 2009-07-02 | 2012-10-11 | Nec Corporation | Femtocell base station, gateway system, map-gw apparatus, communication system, control method, and program |
US9088880B2 (en) * | 2009-07-02 | 2015-07-21 | Nec Corporation | Femtocell base station, gateway system, MAP-GW apparatus, communication system, control method, and program |
US9848307B2 (en) * | 2011-04-04 | 2017-12-19 | Samsung Electronics Co., Ltd. | Messaging over a network |
US20140128113A1 (en) * | 2011-04-04 | 2014-05-08 | Samsung Electronics Co., Ltd. | Messaging over a network |
US20130311654A1 (en) * | 2011-04-29 | 2013-11-21 | Huawei Technologies Co., Ltd. | Internet Service Control Method, and Relevant Device and System |
US9391864B2 (en) * | 2011-04-29 | 2016-07-12 | Huawei Technologies Co., Ltd. | Internet service control method, and relevant device and system |
WO2013105976A1 (en) * | 2012-01-13 | 2013-07-18 | Nokia Siemens Networks Oy | Native short message service for long term evolution |
US9392425B2 (en) * | 2012-03-09 | 2016-07-12 | Kt Corporation | Method and apparatus for providing short message services for packet switching-only subscription in mobile communications network |
KR101554219B1 (en) | 2012-03-09 | 2015-09-21 | 주식회사 케이티 | Short Message Service Providing Method and Apparatus for Packet Switched Only Subscription in Mobile Communication Network |
US20150109966A1 (en) * | 2012-03-09 | 2015-04-23 | Kt Corporation | Method and apparatus for providing short message services for packet switching-only subscription in mobile communications network |
WO2013133564A1 (en) * | 2012-03-09 | 2013-09-12 | 주식회사 케이티 | Method and apparatus for providing short message services for packet switching-only subscription in mobile communications network |
US9565564B2 (en) | 2012-12-07 | 2017-02-07 | At&T Intellectual Property I, L.P. | Providing a masked short message service in a wireless network |
US9693230B2 (en) | 2012-12-07 | 2017-06-27 | At&T Intellectual Property I, L.P. | Providing a masked short message service in a wireless network |
US10104067B2 (en) | 2012-12-07 | 2018-10-16 | At&T Intellectual Property I, L.P. | Providing a masked short message service in a wireless network |
CN106797369A (en) * | 2014-08-27 | 2017-05-31 | 瑞典爱立信有限公司 | Call forwarding during packet voice is intercepted is detected |
US20170237852A1 (en) * | 2014-08-27 | 2017-08-17 | Telefonaktiebolaget Lm Ericsson (Publ) | Call forwarding detection in voice over packet interception |
US10542134B2 (en) * | 2014-08-27 | 2020-01-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Call forwarding detection in voice over packet interception |
US10277552B2 (en) | 2015-02-09 | 2019-04-30 | Markport Limited | Relating to messaging gateways |
Also Published As
Publication number | Publication date |
---|---|
US8909266B2 (en) | 2014-12-09 |
US20130137471A1 (en) | 2013-05-30 |
WO2010105043A2 (en) | 2010-09-16 |
WO2010105043A3 (en) | 2011-01-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8909266B2 (en) | Methods, systems, and computer readable media for short message service (SMS) forwarding | |
US20080207181A1 (en) | Method and system for applying value added services on messages sent to a subscriber without affecting the subscriber's mobile communication | |
US8275372B2 (en) | Method and system for providing CAMEL services to a home network's outbound roamer without need for CAMEL support or agreement | |
JP5671552B2 (en) | Missed call notification for roaming subscribers | |
CA2643881C (en) | A method and a system for the delivery of short messages | |
US20060136560A1 (en) | Scalable message forwarding | |
US20060240820A1 (en) | Inbound roamer call control system | |
CN105191366A (en) | Method for serving visitor subscribers in a mobile communication system | |
US20110223881A1 (en) | Method for sending emergency messages to mobile terminals | |
WO2008146097A1 (en) | A method for the forwarding of sms in a mobile communication system | |
US9420438B2 (en) | Method, system and server for feeding back state of receiving end | |
EP1733575B1 (en) | A method and apparatuses for sending message to a mobile station by addressing the hardware part | |
TWI511601B (en) | Routing call to uma-capable terminals using a geographic number | |
US11337043B2 (en) | Universal packet signaling messaging system | |
US7389115B2 (en) | Method for handling service requests in a mobile telecommunication network | |
GB2435156A (en) | Communication system for accessing more than one device at a single address | |
WO2008073234A2 (en) | Method and system for applying value added services on messages sent to a subscriber without affecting the subscriber's mobile communication | |
KR101054085B1 (en) | Message read confirmation service method and mobile communication system therefor | |
GB2492049A (en) | Distributing status information for a telecommunications network subscriber |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: TEKELEC, NORTH CAROLINA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NOOREN, ELOY JOHAN LAMBERTUS;REEL/FRAME:024432/0822 Effective date: 20100407 |
|
AS | Assignment |
Owner name: WILMINGTON TRUST, NATIONAL ASSOCIATION, MINNESOTA Free format text: SECURITY INTEREST;ASSIGNORS:TEKELEC;CAMIANT, INC.;REEL/FRAME:028035/0659 Effective date: 20120127 |
|
AS | Assignment |
Owner name: TEKELEC GLOBAL, INC., NORTH CAROLINA Free format text: CHANGE OF NAME;ASSIGNOR:TEKELEC;REEL/FRAME:028078/0287 Effective date: 20120130 |
|
AS | Assignment |
Owner name: TEKELEC NETHERLANDS GROUP, B.V., NETHERLANDS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TEKELEC INTERNATIONAL SPRL;REEL/FRAME:028853/0469 Effective date: 20120812 Owner name: TEKELEC AND CAMIANT, INC., NORTH CAROLINA Free format text: TERMINATION OF SECURITY INTERESTS;ASSIGNOR:WILMINGTON TRUST, NATIONAL ASSOCIATION;REEL/FRAME:028856/0396 Effective date: 20120812 Owner name: TEKELEC INTERNATIONAL SPRL, BELGIUM Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TEKELEC GLOBAL, INC.;REEL/FRAME:028853/0324 Effective date: 20120812 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |