WO2011106657A1 - Distribution automatique de messages - Google Patents

Distribution automatique de messages Download PDF

Info

Publication number
WO2011106657A1
WO2011106657A1 PCT/US2011/026262 US2011026262W WO2011106657A1 WO 2011106657 A1 WO2011106657 A1 WO 2011106657A1 US 2011026262 W US2011026262 W US 2011026262W WO 2011106657 A1 WO2011106657 A1 WO 2011106657A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
subscriber
msisdn
active
smsc
Prior art date
Application number
PCT/US2011/026262
Other languages
English (en)
Inventor
Rod Makin
Andrew Smith
John Bunyan
Original Assignee
Convergys Cmg Utah, Inc.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Convergys Cmg Utah, Inc. filed Critical Convergys Cmg Utah, Inc.
Publication of WO2011106657A1 publication Critical patent/WO2011106657A1/fr
Priority to US13/232,082 priority Critical patent/US20120220319A1/en
Priority to US14/643,877 priority patent/US9414209B2/en

Links

Classifications

    • 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/48—Message addressing, e.g. address format or anonymous messages, aliases
    • 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
    • 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]

Definitions

  • SMS messages are communicated from a message sender to a message recipient in the following manner, defined by Global System for Mobile Communications (GSM) technical specification 03.40.
  • GSM Global System for Mobile Communications
  • the sender creates a message to be delivered (e.g., by typing it into the keypad of a mobile telephone), and specifies the recipient for the message (e.g., by typing a mobile phone number for the intended recipient of the message).
  • the message would then be sent from the sender to his or her SMS service center (SMSC) which would query a database called a home location register (HLR) to identify how to route the message, and would then send the message to the intended recipient based on the information received from the HLR.
  • SMSSC SMS service center
  • HLR home location register
  • the SMSC would receive a delivery confirmation message. If the recipient does not receive the message (e.g., if it was sent to a mobile number which was turned off), then the SMSC would retry sending the message until it either receives a delivery confirmation, or a predefined message storage period (e.g., two weeks) expires.
  • a predefined message storage period e.g., two weeks
  • an SMS message addressed to one of the recipient's inactive numbers might not reach the recipient (or might only reach the recipient if the recipient reactivates the inactive number), even though the recipient might have an active subscription when the SMS message was sent.
  • the number for an intended recipient is mutable (e.g., where a subscriber can switch between active numbers)
  • the standard delivery and retry mechanisms could fail, with the SMSC trying to redeliver the message to the original (inactive) number, rather than being able to adapt to the changes made by the subscriber.
  • the disclosed technology can be implemented in a variety of manners.
  • a machine comprising a processor, a network interface, and a memory storing instructions which, when executed by the processor, are operable to cause a set of acts to be performed.
  • Such acts could comprise parsing a message received via the network interface, and sending a delivery confirmation in response to receiving the message.
  • the delivery confirmation could be sent before providing the message to the message recipient.
  • Corresponding methods could be performed, and computer readable media could also be implemented.
  • Figure 1 shows components and communications which can be used to deliver a message to a recipient at a number other than that entered by the sender of the message.
  • Figures 2a-2b show components and communications which can be used in delivering a message to a recipient who is unavailable at the time the message is sent.
  • Figure 3 shows components and communications which can be used to deliver a message to a recipient at a number other than that entered by the sender of the message.
  • Figures 4a-4b show components and communications which can be used in delivering a message to a recipient who is unavailable at the time the message is sent.
  • Figure 5 depicts components and communications which can be used in delivering a message reply.
  • Figures 6a-6b depict components which could be used in an SMS service center.
  • Figures 7a-7b depict components and communications which could be used in delivering a message to a recipient who is unavailable at the time the message is sent.
  • FIG 1 that figure depicts components which can be used in delivering an SMS message to a subscriber with multiple numbers when the subscriber's active number is different from the number the SMS was addressed to. In practice, this might occur when the subscriber has an acquaintance in one geographic area (e.g., Australia, as depicted), who is aware only of the subscriber's number in that geographic area (e.g., 61 - 2222).
  • geographic area e.g., Australia, as depicted
  • the subscriber's active number at the time the SMS was sent was not in the sender's geographic area (e.g., the subscriber was in the UK, rather than Australia) a mechanism would be necessary to have the message delivered to the subscriber's active number (e.g., 44-2222), rather than to the number entered by the sender.
  • the components depicted in figure 1, along with the illustrated data communications, can be used to provide this mechanism.
  • an SMS message would initially be created by entering it, and the number associated with the subscriber in the sender's geographic area (in this case 61-2222), into the sender's mobile device [101]. This information would then be sent [120] to the sender's serving SMSC [102] which would query [121] the serving HLR [103] to establish a location for the recipient based on the number entered by the sender (i.e., 61 - 2222).
  • the serving HLR [103] would recognize the recipient number as being associated with a subscriber having multiple numbers, and would (e.g., per a previous agreement between the entity maintaining the serving HLR [103] and the subscriber's service provider) forward the request [122] from the sender's serving SMSC [102] to a second SMSC [104] maintained by the subscriber's service provider.
  • the second SMSC [104] would then send [123] the sender's serving SMSC [102] a response to its query. In that response, the second SMSC [104] would indicate that the SMS should be delivered to the second SMSC [104].
  • [104] would send a delivery confirmation message [125] to the sender's serving SMSC [102], indicating that the message had been successfully delivered.
  • the second SMSC [104] would then send [126] the message (e.g., via short message peer to peer protocol, otherwise known as SMPP), along with a request to identify the handset of the subscriber which is currently active, to an active subscriber identity system [105].
  • the active subscriber identity system [105] would respond by sending a message [127] to the second SMSC [104] which would inform the second SMSC [104] of the number for the subscriber which is currently active (in this case, 44-2222).
  • the second SMSC [104] would query [128] its local HLR [106] for the mobile switching center (MSC) [107] serving the subscriber's currently active number. Once the address for the MSC [107] had been sent [129], the second SMSC [104] would send [130] the MSC [107] the subscriber's active number, and the message originally entered into the sender's mobile device [101]. The MSC [107] would then deliver [131] the message to the subscriber's mobile device [108] despite the fact that the active number on that device (in this case, 44-2222) was different from the number the SMS message had originally been sent to (61-2222).
  • FIG. 1 depicts a scenario which might take place when an SMS message is placed to a subscriber who is simply not available.
  • the steps of this scenario could be largely the same as those discussed in figure 1 above (e.g., the serving HLR [103] forwards the request [122] from the sender's serving SMSC [102] to a second SMSC [104]; the second SMSC [104] sends a delivery confirmation [125] after the SMS had been sent [124] to the second SMSC [104]; etc).
  • the second SMSC [104] queries [128] the local HLR [106] for the MSC associated with the subscriber's last known active number (in this case, 44-2222), the local HLR [106] would send back a message indicating that the subscriber's handset is not available [129a] (rather than sending back a message indicating the address for the MSC serving the subscriber's currently active number [129]).
  • the second SMSC [104] would respond to the message that the subscriber's handset was not available by sending set message waiting data [132] to the local HLR [106].
  • the second SMSC [104] would also send a message [133] to the active subscriber identity system [105] indicating that the SMS had not been successfully delivered to the subscriber's last known active number.
  • FIG 2b that figure depicts steps which might take place to actually deliver a message to a subscriber who was unavailable during a previous delivery attempt. As shown in figure 2b, this process could start with a message being sent [201] from the subscriber's mobile device [108] indicating that the subscriber is active at a new number (in this case 61-2222).
  • MTSO mobile telephone switching office
  • the active subscriber identity system [105] would know that there was an SMS message waiting for the subscriber, and would send a notification [202] to the second SMSC [104] indicating that the subscriber has become available to receive the message.
  • the second SMSC [104] would then request [203] information from the HLR [103] serving the area where the mobile device [108] was located for routing the SMS to the mobile device.
  • the HLR [103] would send [204] a message indicating the MSC serving the mobile device [108].
  • the SMS [205] to the appropriate MSC [109], which would deliver [206] it to the mobile device [108].
  • the SMS would be sent to the subscriber as soon as he or she is available, regardless of the number the message was originally sent to, and regardless of the number the subscriber had indicated was active (but which proved to be inactive) at the time of the SMS,
  • FIG 3 depicts a system in which an SMS message is delivered to a number other than the number entered when the message was originally created using different communications than discussed above with respect to figure 1.
  • an SMS message would initially be created by entering it, and the number associated with the recipient in the sender's geographic area (in this case, 61 -2222) into the sender's mobile device [101].
  • the sender's serving SMSC [102] would then query [121] the serving HLR [103] to establish a location for the recipient, and, as was the case with figure 1 , the serving HLR [103] would recognize the recipient number as being associated with a subscriber having multiple numbers. However, unlike in figure 1, in the diagram of figure 3, the serving HLR [103] would respond to the request by sending [320] the query to a local SMSC [300] maintained by the subscriber's service provider (again, this would likely take place based on a prior agreement between the entity maintaining the serving HLR [103] and the subscriber's service provider).
  • the local SMSC [300] would then provide [321 ] its own address to the sender's serving SMSC [102] as a response to the initial query sent to the HLR [103].
  • the sender's serving SMSC [102] would send [322] the SMS to the local SMSC [300], and the local SMSC [300] would send a confirmation [323] indicating that the SMS had been successfully delivered.
  • the local SMSC [300] would query [324] the active subscriber identity system [105] to determine the number at which the subscriber could be reached. For example, this could take place by the local SMSC [300] parsing the message to extract information identifying the message recipient (e.g., the phone number of the recipient entered into the mobile device [101] when the message was created) and asking for the active number for the subscriber associated with that information.
  • the local SMSC [300] could also send the message itself to the active subscriber identity system [105] along with the query.
  • the active subscriber identity system [105] could respond [325] to this query by sending the local SMSC [300] information such as the phone number (MSISDN) and international mobile subscriber identity (IMSI) which its records indicated were active for the subscriber, as well as an address for an SMSC (in this case, the second SMSC [104]) in the same geographic area as the subscriber's active number.
  • the local SMSC [300] would then send [326] (e.g., via SMPP) the SMS message to the SMSC (in this case, the second SMSC [104]) indicated by the active subscriber identity system [105].
  • the second SMSC [104] could (though it might not do so in all implementations) requery [327] the active subscriber identity system [105], which would return [328] the MSISDN and IMSI active at that time for the SMS recipient.
  • the system of figure 3 could complete the delivery process in the same manner as described for figure 1. That is, by querying the local HLR [106] for the MSC [107] serving the subscriber's currently active number, then sending the SMS to that MSC [107], and ultimately to the subscriber's mobile device [108].
  • a system such as shown in figure 4a might function in exactly the same way as described for that figure except that the active subscriber identity system [105], rather than providing information about where the subscriber could be reached, responds to the query from the local SMSC [300] by sending a message [400] indicating that the subscriber is not available.
  • FIG 4b shows how the SMS from figure 4a could eventually be delivered once the subscriber becomes available.
  • the active subscriber identity system [105] discovers that the subscriber has become available (e.g., through a message sent by a toolkit, a message from an MTSO, etc)
  • an alert [420] would be sent to the local SMSC [300] where the SMS had been delivered from the sender's serving SMSC [102] (in such an implementation, the active subscriber identity system [105] would previously have stored a flag or some other data indicating that there was a message waiting at the local SMSC [300] at the time that it was queried for the original SMS to the absent subscriber).
  • This alert could include essentially the same information which would have been provided to the local SMSC [300] if the subscriber had been available when the original query was sent [324] (e.g., address of the second SMSC [104], subscriber's IMSI and/or MSISDN). With this data, the delivery of the message could proceed essentially as if the subscriber had been available when the message was originally sent. That is, the local SMSC [300] could send [326] the message and associated data to the second SMSC [104], the second SMSC [104] could requery [327] the active subscriber identity system [105] to verify that the information received from the local SMSC [300] was still accurate, and the message could be delivered using the communications described previously with respect to figure 1.
  • SMSCs For instance, in situations where it is not economically justifiable to purchase SMSCs for different jurisdictions, or in situations where it is not possible to enter into agreements with entities that have SMSCs in multiple jurisdictions in which those entities agree to let their SMSCs be configured to perform functions such as shown in figures 3, 4a and 4b.
  • the approach shown in figure 4a could be modified so that, instead of the active subscriber identity system [105] informing the local SMSC [300] when the subscriber is not available, the active subscriber identity system [105] could inform the local SMSC [300] of the last active number at which the subscriber was available, and the discovery of the subscriber's unavailability could take place upon interaction with the relevant HLR and be handled as shown in figure 2a.
  • the local HLR [103] rather than forwarding a query from the sender's serving SMSC [102] to an intermediate SMSC (e.g., the local SMSC [300] or the second SMSC [104]), could be configured to send a response to the sender's serving SMSC [102] indicating the SMS should be sent to the appropriate intermediate SMSC (in the case of figure 1, the second SMSC [104]; in the case of figure 3, the local SMSC [300]).
  • an intermediate SMSC e.g., the local SMSC [300] or the second SMSC [104]
  • SMSC [102] rather than sending the sender's serving SMSC [102] messages that the SMS had been delivered to a subscriber, when in fact it had only been delivered to an intermediate SMSC, it is possible that a delivery confirmation message could be sent to the sender's serving SMSC [102] only when the message is actually delivered to the subscriber. This could have the beneficial effect of making the sender's serving SMSC [102] responsible for retries in the event of an absent subscriber, thereby relieving the intermediate SMSCs (i.e., the second SMSC [104] and the local SMSC [300]) of the need to store messages.
  • intermediate SMSCs i.e., the second SMSC [104] and the local SMSC [300]
  • the active subscriber identity system [105] would then respond by sending [523] the number which should be used as the origin number on the return SMS. For example, the active subscriber identity system [105] could determine the geographic location of the destination on the return SMS, then check to see if the subscriber was associated with any numbers in that jurisdiction. If the subscriber was associated with any numbers in that jurisdiction, the active subscriber identity system [105] could return one of those numbers, which could potentially allow the subscriber to avoid international roaming charges by sending the return SMS such that it appeared to originate in the same jurisdiction as its destination. Similarly, in some cases, an active subscriber identity system [105] could keep a record of SMS messages, which the system could use to identify the message as a reply SMS, and to identify the number that was originally entered as the destination of the SMS being replied to.
  • the second SMSC [104] could modify the SMS message so that that number appears as the origin number, and send [524] a request to the HLR [501] in the destination jurisdiction for the address of the MSC serving the destination number.
  • the second SMSC [104] could send [526] the SMS message to the MSC [500] serving the destination number, which could deliver [527] that message to the handset [101] of the recipient.
  • a system for message delivery could be scaled up to include more than the two networks used in the example of figures l-4b.
  • FIGs of figures 7a and 7b which present a high level depiction of components and interactions which could be used to scale the disclosed technology to operate over three (or more) networks in different jurisdictions.
  • a sender initially tries to send [701] a message to a number associated with a network in Australia.
  • the number that the message is sent to is inactive.
  • the request will be sent [702] to a SMSC maintained by the subscriber's service provider [104]. That SMSC [104] would then query [703] the active subscriber identity system [105] to identify the last known active number for the subscriber. The active subscriber identity system [105] responds [704] by informing the SMSC [104] of the last known active number which, in the scenario shown in figure 7a, is located in the UK. The SMSC [104] then requests [705] the location of the MSC serving the last known active number, such as by using an SRI SM.
  • the HLR [103] would then respond [706], either by giving a destination MSC which (given that the scenario of figure 7a is one in which there is no currently active number) could be tried for an unsuccessful delivery attempt, or by sending a message that the number is not currently active.
  • the SMSC [104] would then send [707] a message to the active subscriber identity system [105] indicating that there is a message waiting for the UK MSISDN (as that was the most recently active number).
  • the active subscriber identity system [105] could acknowledge [708] that message, and the SMSC [104] could store the message which was originally sent to the subscriber's Australian number.
  • the SMSC [104] could also send [709] a message to the UK HLR [106] to set the message waiting flag for the UK MSISDN.
  • FIG 7b that figure depicts communications which might take place once the subscriber turns his or her handset on.
  • the HLR for the jurisdiction of the subscriber's active number in this case, the UK
  • the HLR for the jurisdiction of the subscriber's active number would send a notification [710] that the subscriber is back on the network.
  • the SMSC [104] could request [71 1] (e.g., using a SOAP message) that the active subscriber identity system [105] inform it of all of the phone numbers for the subscriber associated with the phone number that was activated.
  • the active subscriber identity system [105] could then respond [712] with all the numbers associated with the subscriber.
  • this could include the Australian number the message was originally sent to, as well as numbers in other jurisdictions (e.g., a United States number).
  • the SMSC [104] would then retrieve from its storage the messages which had been sent to the subscriber while the subscriber was unavailable, and deliver them [713] to the active number on the subscriber's handset [108].
  • the two network system such as shown in figures l-4b could be scaled to any number of networks, and the messages sent to a subscriber could be reliably delivered regardless of the number they were originally sent to.
  • figures 7a and 7b are high level diagrams, and that they are not intended to imply that scaling to additional networks requires using the particular communications shown in those figures.
  • figure 7a depicts a message being sent [702] directly from an originating mobile device [101 ] to a SMSC [104] that communicates with the active subscriber identity system [105], such direct communication is not a requirement.
  • the message would first be passed through (or routed using) other components, such as the sender's serving SMSC [102], and a serving HLR [103].
  • the SMSC [104] could set message waiting flags on the HLRs for all of the numbers associated with the subscriber, so that, regardless of which number the subscriber activates next, the HLR would send a message indicating that activation to the SMSC [104].
  • an active subscriber identity system [105] could be combined with an intermediate SMSC (e.g., the second SMSC [104]).
  • an intermediate SMSC e.g., the second SMSC [104]
  • subscribers might have multiple handsets (or multiple SIM cards which would be swapped out of a single mobile device to change active numbers)
  • the subscriber might have a single phone with a single SIM where the SIM hosts multiple international mobile subscriber identities (IMSI) with associated phone numbers (referred to as MSISDN).
  • IMSI international mobile subscriber identities
  • MSISDN international mobile subscriber identities
  • the phone might have a toolkit which would allow the subscriber to designate an active IMSI (and which would communicate that designation to the active subscriber identity system [105]). Combinations are also possible.
  • an active subscriber identity system [105] might not store messages, relying instead on some other component (e.g., an intermediate SMSC, such as the second SMSC [104]) for message storage. Variations are also possible in the types of messages handled by the system.
  • a SMSC could include a signal processing unit [601] which could include a communications device, such as an SS7 card [602] for communicating with an MSC and/or other devices (e.g., the sender's serving SMSC [102]) which use SS7 signaling to communicate message, as well as software [603] which could configure it to perform functionality such as described above with respect to figures 1 -4b (e.g., when that software is retrieved from a memory and executed by a processor in the SMSC).
  • a signal processing unit [601] which could include a communications device, such as an SS7 card [602] for communicating with an MSC and/or other devices (e.g., the sender's serving SMSC [102]) which use SS7 signaling to communicate message, as well as software [603] which could configure it to perform functionality such as described above with respect to figures 1 -4b (e.g., when that software is retrieved from a memory and executed by a processor in the SMSC).
  • the SMSC could also use various networks (e.g., internal LAN [604], external LAN [605], or even the Internet [608]) to communicate with external systems, such as a call detail record server [606], and/or external short message entity clients [607]. Further, in some implementations, the SMSC could also communicate with systems such as a customer care system [609], in case it appeared that there was a problem with a particular account which could be tracked to the SMSC, or to data which could be accessed through the SMSC.
  • networks e.g., internal LAN [604], external LAN [605], or even the Internet [608]
  • external systems such as a call detail record server [606]
  • the SMSC could also communicate with systems such as a customer care system [609], in case it appeared that there was a problem with a particular account which could be tracked to the SMSC, or to data which could be accessed through the SMSC.
  • FIG. 6a shows how the architecture of figure 6a could be modified to include components such as a second signal processing unit [610] and a RAID [61 1], which could provide additional stability, and remove the risk of a single point of failure (i.e., the signal processing unit [601]) from the architecture of figure 6a.
  • a second signal processing unit [610] and a RAID [61 1]
  • FIG. 6b shows how the architecture of figure 6a could be modified to include components such as a second signal processing unit [610] and a RAID [61 1], which could provide additional stability, and remove the risk of a single point of failure (i.e., the signal processing unit [601]) from the architecture of figure 6a.
  • other modifications e.g., different network topologies to support communication between components, additional redundant features to further reduce the risk of failure, etc
  • a and an should be understood to mean one or more.
  • a reference to “a processor” should be understood to embrace architectures with a single “processor,” as well as architectures which include multiple processors (e.g., multi-core CPUs, distributed computing architectures, etc).
  • the modifier "active" should be understood to mean presently operable for its intended function. For example, if a cellular phone has multiple MSISDNs, and the user of that phone indicates (e.g., using a toolkit) that calls made to or from that phone should be routed as if they were directed to a specific one of those MSISDNs, then that MSISDN would be "active," while the other MSISDNs would not.
  • a statement that a thing is "associated with” something else means that the thing has some connection to that with which it is “associated”. For example, if a database record indicates that a subscriber has purchased multiple cellular telephones, each of which has a unique MSISDN, then the subscriber is "associated with” each of those MSISDNs.
  • a statement that an act happens "before” some subsequent act should be understood to mean that, if the subsequent act takes place, it will take place at a point in time which is later than the act which happens "before” it. The subsequent act may not take place, even if the act which happens "before” it is completed.
  • a "computer” should be understood to refer to a combination of devices comprising a processor and a memory which is capable of performing one or more logical operations based on a set of data.
  • a "computer readable medium” should be understood to refer to any article of manufacture (including combinations of articles of manufacture) which can be used to store or maintain data so that it can be retrieved by a computer.
  • a computer When used in the claims, to "configure” a computer should be understood to refer to providing the computer with specific data (which may include instructions) which can be used in performing the specific acts the computer is being “configured” to do. For example, installing Microsoft WORD on a computer “configures” that computer to function as a word processor, which it does using the instructions for Microsoft WORD in combination with other inputs, such as an operating system, and various peripherals (e.g., a keyboard, monitor, etc).
  • specific data which may include instructions
  • Microsoft WORD installed on a computer “configures” that computer to function as a word processor, which it does using the instructions for Microsoft WORD in combination with other inputs, such as an operating system, and various peripherals (e.g., a keyboard, monitor, etc).
  • data should be understood to mean information which is represented in a form which is capable of being processed, stored and/or transmitted.
  • a "delivery confirmation" for a message should be understood to refer to a communication indicating that the message has been provided to the message recipient.
  • instructions should be understood to refer to data which describes operations which a device which executes those “instructions” (e.g., a processor) is to perform.
  • IP signaling should be understood to refer to communicating information using a connectionless protocol used for transferring data as packets between computers.
  • a "memory” should be understood to refer to an object, substance, or combination of objects or substances, capable of storing data or instructions in a form in which they can be retrieved and/or processed by a device.
  • a "memory” not be limited to any particular type or organization, and should be understood to include distributed and decentralized systems however they are physically or logically disposed, as well as storage objects of systems which are located in a defined and/or circumscribed physical and/or logical space. Examples of “memory” include hard drives, solid state memories, optical disc memories, random access memory, and tape drives.
  • a "message” should be understood to refer to a defined unit of communication.
  • a "message body” should be understood to be information communicated by a message. For example, when using SMS to send the text "Happy Christinas" from one mobile phone to another, the “message body” of the message would be "Happy Christmas”.
  • a “message recipient” should be understood to be data which indicates where a message should be delivered. For example, in an SMS message, the phone number of the device where the message body should be displayed (in the case of a displayable message) would be considered the “message recipient.”
  • the term “message recipient” also embraces data which is treated as indicating where the message should be delivered, even if that data is inaccurate (e.g., because the original "message recipient" was replaced while the message is in transit).
  • a "message sender” should be understood to be data which indicates where a message originates, For example, in an SMS message, the phone number of the device the message is sent from would be considered the “message sender.”
  • the term “message sender” also embraces data which is treated as indicating where the message originates, even if that data is inaccurate (e.g., because the original "message sender” was replaced while the message is in transit).
  • a "MSISDN” should be understood to refer to a number which identifies one (and only one) subscription in a mobile network. The phone number of a cellular phone is an example of an "MSISDN,”
  • network interface should be understood to refer to a device which is installed in another device that can allow communication of information over a network.
  • network interfaces include modems, and SS7 cards.
  • processor should be understood to mean a device (or combination of devices) which can read instructions and perform operations (or cause operations to be performed) based on those instructions.
  • a statement that a message is a "reply" to an earlier message should be understood to mean that the later message is sent from the target of the earlier message, that it is sent to the originator of the earlier message, and that it is sent as a response to the target of the earlier message receiving that message (e.g., by selecting a "reply” button on an e-mail after reading the contents of the email).
  • SMS message should be understood to refer to a message sent using the Short Message Service features included in mobile telephones or similar devices.
  • SS7 signaling should be understood to refer to sending information using a channel specified for transmission of control information in a telecommunications network (e.g., a band used for out of band signaling for a voice telephone call).
  • a "store and forward message” should be understood to refer to a message where, if the recipient is disconnected at the time the message is sent, the message will be automatically delivered at a later time based on the protocol used to deliver the message
  • subscriber should be understood to refer to an individual who is authorized to receive communications on a communication network.
  • An individual who has signed up for wireless service, and been assigned (or selected) a MSISDN is an example of a "subscriber.”

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

Selon l'invention, à l'aide de composants, tels que des centres de services de messages courts intermédiaires et des systèmes d'identités d'abonnés de services actifs, il est possible de distribuer un message à un abonné à un numéro différent du numéro qui a été entré par l'expéditeur du message au moment de l'envoi du message. Ces composants peuvent être également utilisés pour distribuer le message en cas de non disponibilité de l'expéditeur au moment de l'envoi initial du message. Des communications entre des composants peuvent être réalisées de différentes manières, comprenant l'utilisation de protocoles Internet (IP) propriétaires, et les composants peuvent être configurés pour assumer la responsabilité d'essayer à nouveau de distribuer le message par fourniture d'une confirmation de distribution une fois que le message les a atteints, plutôt que de fournir une confirmation de distribution une fois que le message a atteint son destinataire final.
PCT/US2011/026262 2010-02-26 2011-02-25 Distribution automatique de messages WO2011106657A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US13/232,082 US20120220319A1 (en) 2011-02-25 2011-09-14 Automatic delivery of messages
US14/643,877 US9414209B2 (en) 2010-02-26 2015-03-10 Automatic delivery of messages

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US30847110P 2010-02-26 2010-02-26
US61/308,471 2010-02-26

Publications (1)

Publication Number Publication Date
WO2011106657A1 true WO2011106657A1 (fr) 2011-09-01

Family

ID=43799621

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2011/026262 WO2011106657A1 (fr) 2010-02-26 2011-02-25 Distribution automatique de messages

Country Status (1)

Country Link
WO (1) WO2011106657A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102413440A (zh) * 2011-12-08 2012-04-11 四川联友电讯技术有限公司 基于综合业务平台的单卡双待业务信息收发方法及系统
CN103596148A (zh) * 2012-08-17 2014-02-19 四川联友电讯技术有限公司 基于ismp平台的单卡双待的副号码接收短信装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040185888A1 (en) * 2003-03-18 2004-09-23 Nokia Corporation Solving mobile station identity in a multi-SIM situation
US20040185877A1 (en) * 2001-06-18 2004-09-23 Atul Asthana System and method for managing message attachment and information processing from a mobile data communication device
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

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040185877A1 (en) * 2001-06-18 2004-09-23 Atul Asthana System and method for managing message attachment and information processing from a mobile data communication device
US20040185888A1 (en) * 2003-03-18 2004-09-23 Nokia Corporation Solving mobile station identity in a multi-SIM situation
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 (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102413440A (zh) * 2011-12-08 2012-04-11 四川联友电讯技术有限公司 基于综合业务平台的单卡双待业务信息收发方法及系统
CN103596148A (zh) * 2012-08-17 2014-02-19 四川联友电讯技术有限公司 基于ismp平台的单卡双待的副号码接收短信装置

Similar Documents

Publication Publication Date Title
US8676180B2 (en) Virtual SIM monitoring mode for mobile handsets
EP1815697B1 (fr) Appareil et procedes pour services de telecommunications
EP1726171B1 (fr) Messagerie fondée sur la position
EP2454898B1 (fr) Procédé et appareil permettant de vérifier un numéro de téléphone
US20060136560A1 (en) Scalable message forwarding
US20120094642A1 (en) Enhanced missed call notification
EP1255414A2 (fr) Réponse et traitement automatique de SMS
EP2184932B1 (fr) Procédé, dispositif et système d'interfonctionnement entre un message instantané et un message court
EP1350402A2 (fr) Procede pour la delivrance de messages par retransmission dans un service d'envoi de messages courts
US9420438B2 (en) Method, system and server for feeding back state of receiving end
US9414209B2 (en) Automatic delivery of messages
US8549083B2 (en) Message waiting notification to external message centers
US20080194277A1 (en) Multimedia message center, terminal and method for multimedia message
WO2011106657A1 (fr) Distribution automatique de messages
US7826828B2 (en) Method and system for detecting availability of a wireless device
US20100323666A1 (en) Sequential message delivery for fda processing and store-and-forward processing
WO2008073234A2 (fr) Procédé et système pour appliquer des services à valeur ajoutée sur des messages envoyés vers un abonné sans affecter les communications mobiles de l'abonné
GB2492049A (en) Distributing status information for a telecommunications network subscriber
WO2004016013A2 (fr) Agencement et procede destines a des reseaux de telecommunication mobile
CN103634756A (zh) 一种物联网应用与短消息增值业务交互的处理方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11706726

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11706726

Country of ref document: EP

Kind code of ref document: A1