WO2013044782A1 - 一种实现短消息重发的方法和装置 - Google Patents

一种实现短消息重发的方法和装置 Download PDF

Info

Publication number
WO2013044782A1
WO2013044782A1 PCT/CN2012/081871 CN2012081871W WO2013044782A1 WO 2013044782 A1 WO2013044782 A1 WO 2013044782A1 CN 2012081871 W CN2012081871 W CN 2012081871W WO 2013044782 A1 WO2013044782 A1 WO 2013044782A1
Authority
WO
WIPO (PCT)
Prior art keywords
short message
receiving end
sent
service center
message
Prior art date
Application number
PCT/CN2012/081871
Other languages
English (en)
French (fr)
Inventor
衣强
Original Assignee
华为终端有限公司
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 华为终端有限公司 filed Critical 华为终端有限公司
Priority to EP12834832.3A priority Critical patent/EP2713638B1/en
Publication of WO2013044782A1 publication Critical patent/WO2013044782A1/zh
Priority to US14/145,418 priority patent/US9769631B2/en
Priority to US15/680,774 priority patent/US10750330B2/en

Links

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
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • 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/23—Reliability checks, e.g. acknowledgments or fault reporting
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and apparatus for implementing short message retransmission. Background technique
  • MSISDN MS international PSTN/ISDN number
  • M2M machine to machine
  • the scenario involving communication without relying on the MSISDN includes: SMS (Short Message Service) communication between the server and the MSI-free terminal, and no MSISDN terminal and SMS communication without the MSISDN terminal.
  • SMS Short Message Service
  • the identity of the SIP URI can be used in the IMS (IP multimedia subsystem, IP).
  • the multimedia subsystem transmits short messages for communication.
  • Embodiments of the present invention provide a method and apparatus for implementing short message retransmission to implement a short message request for resending a transmission failure.
  • a method for implementing short message retransmission includes: When the IP short message gateway (IP-SM-GW) learns that the short message sent to the receiving end in the IP Multimedia Subsystem (IMS) domain fails to be sent, the IP-SM- The GW sends the short message to the service center, so that the service center stores the short message;
  • IP-SM-GW IP short message gateway
  • IMS IP Multimedia Subsystem
  • the IP-SM-GW When the receiving end corresponding to the short message becomes available, the IP-SM-GW receives the stored short message sent by the service center, and resends the short message to the receiving end by using the IMS domain.
  • a method for implementing short message retransmission includes:
  • the IP-SM-GW When the IP-SM-GW learns that the short message sent to the receiving end in the IMS domain fails to be sent, the IP-SM-GW stores the short message request corresponding to the short message that fails to be sent;
  • the IP-SM-GW resends the stored processed short message to the receiving end through the IMS domain.
  • An apparatus for implementing short message retransmission comprising:
  • a storage processing module configured to: when the short message sent to the receiving end in the IMS domain fails to be sent, send the short message to the service center, so that the service center stores the short message; When the receiving end corresponding to the short message becomes available, the stored short message sent by the service center is received, and sent to the receiving end by using the IMS domain.
  • An apparatus for implementing short message retransmission comprising:
  • a storage processing module configured to: when the short message sent to the receiving end in the IMS domain fails to be sent, store the short message request corresponding to the short message that fails to be sent;
  • a retransmission module configured to resend the stored processed short message to the receiving end by using the IMS domain when the receiving end corresponding to the short message becomes available.
  • the embodiment of the present invention provides a technical solution, in the IMS domain, when the receiving end fails to send a short message request to the receiving end due to unavailability, the short message request is stored, and when the receiving end becomes available When the short message request is resent to the receiving end, the short message request for resending the sending failure can be re-transmitted, thereby improving the availability of sending the short message request in the IMS, and improving The user experience.
  • FIG. 1 is a schematic flowchart of a method for implementing short message retransmission according to an embodiment of the present invention
  • FIG. 2A is a flow chart of a method for implementing short message retransmission according to Embodiment 1 of the present invention
  • FIG. 2B is a flow chart showing the step S22 of the method for implementing short message retransmission provided in FIG. 2A;
  • 2C is a flow chart showing the step S24 of the method for implementing short message retransmission provided in FIG. 2A;
  • FIG. 3A is a flowchart of a method for implementing short message retransmission according to Embodiment 2 of the present invention.
  • FIG. 3B is a flow chart showing the step S34 of the method for implementing short message retransmission provided in FIG. 3A;
  • FIG. 3C is a flow chart showing the step S35 of the method for implementing short message retransmission provided in FIG. 3A;
  • FIG. 4 is a flowchart of a method for implementing short message retransmission according to Embodiment 3 of the present invention
  • FIG. 5A is a flowchart of a method for implementing short message retransmission according to Embodiment 4 of the present invention
  • Figure 5B is a flow chart showing the first step S54 of the method for implementing short message retransmission provided in Figure 5A;
  • FIG. 5C shows a second step S54 of the method for implementing short message retransmission provided by FIG. 5A.
  • FIG. 5D is a third flowchart of step S54 of the method for implementing short message retransmission provided in FIG. 5A;
  • FIG. 6A is a flow chart showing a method for implementing short message retransmission according to Embodiment 5 of the present invention.
  • Figure 6B is a first flow chart showing the step S63 of the method for implementing short message retransmission provided in Figure 6A;
  • 6C is a second flowchart of step S63 of the method for implementing short message retransmission provided in FIG. 6A;
  • 6D is a third flowchart of step S63 of the method for implementing short message retransmission provided in FIG. 6A;
  • FIG. 7A is a flowchart of a method for implementing short message retransmission according to Embodiment 6 of the present invention.
  • Figure 7B is a first flow chart showing the step S73 of the method for implementing short message retransmission provided in Figure 7A;
  • FIG. 7C is a second flowchart of step S73 of the method for implementing short message retransmission provided in FIG. 7A;
  • Figure 7D is a third flow chart showing the step S73 of the method for implementing short message retransmission provided in Figure 7A;
  • FIG. 8 is a structural diagram of an apparatus for implementing short message retransmission provided in Embodiment 7;
  • FIG. 9 is a structural diagram of an apparatus for implementing short message retransmission according to Embodiment 8;
  • FIG. 11 is a structural diagram of an apparatus for implementing short message retransmission provided in Embodiment 9;
  • FIG. 12 is a structural diagram of an apparatus for implementing short message retransmission provided in Embodiment 9;
  • a structure diagram of a device for implementing short message retransmission is provided. detailed description
  • the network of the sender may include a sender, a S-CSCF (Serving Call Session Control Function) to which the sender belongs, and an IP-SM-GW to which the sender belongs ( IP-Short-Message-Gateway, IP Short Message Gateway, SC (Service Centre, Business Center).
  • SC refers to the service center of the short message.
  • the sender sends a short message to the receiver
  • the user terminal/server can send a short message request to the receiver through the S-CSCF.
  • the network on the sending end is called the sending side, and the sending end may include a User Equipment (UE) or a server (server).
  • UE User Equipment
  • server server
  • the network where the receiving end is located may include a receiving end, an S-CSCF (Serving Call Session Control Function) to which the receiving end belongs, and an IP-SM to which the receiving end belongs.
  • -GW IP-Short-Message-Gateway, IP Short Message Gateway.
  • the network may also include HSS (Home Subscriber Server, Home Subscriber Register), SMS-IWMSC (Interworking MSC For Short Message Service), SMS-GMSC (service Call Session Control Function, service)
  • the network where the receiving end is located may be referred to as the receiving side, and the receiving end may be the user equipment UE.
  • the sender sends a short message request to the S-CSCF of the network where the receiver is located through the S-CSCF of the sender, and then the short message request received by the S-CSCF of the network of the receiver ends.
  • the IP-SM-GW processes, or is directly processed by the S-CSCF.
  • FIG. 1 is a schematic flowchart of a method for implementing short message retransmission according to an embodiment of the present invention.
  • step S10 determining whether the short message request sent to the receiving end in the IMS domain fails to be sent; in this embodiment, in the IMS domain, both the S-CSCF and the IP-SM-GW can be The short message request is processed, and thus, in an embodiment, the S-CSCF or the IP-SM-GW may determine whether the short message request sent to the receiving end fails to be transmitted.
  • Step S12 When it is determined that the transmission fails, the short message request is stored.
  • the short message request in the IMS domain, when the receiving end is in the process of sending, the short message cannot be sent to the receiving end due to the abnormality.
  • the short message requesting the short message may be stored by the SC in the network of the receiving end, or the short message request may be stored in the IP-SM-GW, or the short message request may be stored in the SMS.
  • the above method is not the only embodiment and is optional.
  • Step S14 When the corresponding receiving end of the short message request becomes available, the short message request of the storage processing is sent to the receiving end through the IMS domain.
  • the short message is stored by the SC in the network at the receiving end, when the receiving end cancels the abnormality, the short message is sent to the IP-SM-GW, and then the IP is sent.
  • the SM-GW sends the request to the receiving end for retransmission through the IMS domain; or, the request for sending the short message is stored in the IP-SM-GW, and after the receiving end cancels the abnormality, the IP-SM-GW is triggered again.
  • the short message is sent to the receiving end by the IMS domain, or the request for sending the short message is stored in the SMS-AS. After the receiving end cancels the abnormality, the SMS-AS is triggered to be sent to the receiving end through the IMS domain. Resend the short message.
  • the embodiment provided by the present invention in the IMS domain, when the receiving end fails to send a short message request sent to the receiving end due to unavailability, the short message request is stored, and when the receiving end becomes available When the short message request is resent to the receiving end, the short message request for resending the sending failure can be resent, thereby improving the availability of sending the short message request in the IMS and improving the user experience.
  • FIG. 2A is a flow chart showing a method for implementing short message retransmission according to Embodiment 1 of the present invention.
  • the short message requesting to send the short message passes through the IP-SM-GW of the receiving end network.
  • the short message request cannot be successfully sent to the receiving end due to an abnormal reason.
  • the transmission fails.
  • the short message can be stored by the SC. After the receiving end cancels the abnormality, the short message request is retransmitted.
  • Step S20 The IP-SM-GW receives the short message request sent by the sending side that is sent by the S-CSCF.
  • the short message request includes the short message content and the receiving end UE information.
  • other information may be included, such as the SC address information of the short message stored when the short message is sent, and the SC address is the SC address to which the sender carries when sending the short message.
  • the short message request is a Session Initiation Protocol (SIP) request message.
  • SIP Session Initiation Protocol
  • Step S21 The IP-SM-GW determines whether the short message is successfully sent to the receiving UE, and the IP-SM-GW determines whether the short message is sent to the receiving end UE.
  • the IP-SM-GW may determine, according to the received response message, whether the short message is successfully sent to the receiving UE.
  • the receiving end if the receiving end is unreachable, the memory of the receiving end UE is full, or the SIP message type is not supported, the receiving end network returns a response message of the failure or a response message of the short message failure report to the IP-SM-GW. Therefore, the IP-SM-GW may determine that the short message is not successfully sent to the receiving UE by using the returned response message, and may consider that the short message is sent.
  • Step S22 When it is determined that the short message request cannot be successfully sent to the receiving UE, the IP-SM-GW sends the short message corresponding to the short message request to the SC for storage.
  • the step of the IP-SM-GW sending the short message to the SC for storage may further include, as shown in FIG. 2B.
  • Step S220 The IP-SM-GW generates a Mobile Terminated Correlation ID (MT Correlation ID) or an SMSC (corresponding number), and the IP-SM-GW saves the MT Correlation ID or the SMSNN and the short message.
  • the identity of the receiving side in the form of a SIP URI.
  • the IP-SM-GW may also store the identity of the MT Correlation ID or the SIP URI of the SMSC and the sender and the receiver of the short message.
  • the MT Correlation ID format is MCC (3 digits) + MNC (3 digits) + send ID (9 digits), the MCC is the country code, the MNC is the carrier code, and the Sender ID is the 9-digit value randomly generated by the terminal.
  • the bit value shall include the HSS identification number of the receiving UE, so that the sender ID of the receiving end can be determined by the sender ID in the MT Correlation ID; the SMSCN is a 3-digit value generated by the terminal;
  • the IP-SM-GW generates an association identifier (MT Correlation ID) ilSMSCN for the receiving end, and the role is that after the UE is available, the SC matches the corresponding short message by using the MT Correlation ID or the SMSNN, and retransmits the information, and
  • the IP-SM-GW matches the identity of the SIP URI of the short message sending end or the receiving end according to the MT Correlation ID or the SMSNN, and then generates a SIP request message carrying the short message content, and sends the SIP request message to the receiving end UE.
  • Step S221 The IP-SM-GW acquires the SC address.
  • the short message is sent to the SC address to which the receiving end belongs, or the SC address to which the sending end belongs is obtained, and the obtained address is stored.
  • the SC address is directly extracted; if the IP-SM-GW does not know the receiving end UE
  • the SC address to which the UE is located is obtained by the IP-SM-GW from the HSS to which the receiver UE belongs.
  • the IP-SM-GW queries the HSS for the SC address to which the receiving UE belongs; if the HSS does not configure the SC address for the receiving UE, the HSS according to the identity information of the receiving UE (SIP URI, IMSI)
  • the SC address is allocated to the receiving UE.
  • the SC address needs to be saved.
  • the IP-SM-GW extracts the SC address to which the sender belongs from the short message request received in step S20, and saves the SC address.
  • Step S222 The IP-SM-GW notifies the HSS of the failure to send the short message.
  • the notification message includes at least a receiver identity (IMSI or SIP URI), an SC address, an association identifier, or an SMSCN, and may also include an IP-SM-GW address and a reason for the failure of transmission, and the HSS receives the notification. After that, save the above information in the WMD ( message waiting data ) message.
  • Step S223 Extracting a short message according to the short message request; in the embodiment, the short message includes short message content, a source address, and a destination address, and the source address and the destination address in the extracted short message by the IP-SM-GW. Make changes, the content of the short message is not modified.
  • the I P-SM-G W modifies the source address in the short message of the sending end to the MT Correlation ID, and modifies the destination address to the SC address, and the short message content is not modified; or The source address in the short message is modified to the SMSN and the IP-SM-GW ID, and the destination address is modified to the SC address, and the short message content is not modified.
  • IP -SM-GW does not generate the MT Correlation ID or SMSN
  • IP - The SM-GW can look up the subscription information of the receiving end to the HSS according to the SIP URI of the receiving end, and find the IMSI of the receiving end.
  • the sending end also carries the identity information in the form of its own telephone number in the short message, such as the IMSI of the transmitting end, IP-
  • IP- The SM-GW stores the identity of the sender (such as IMSI) and the identifier of the receiver (IMSI).
  • the IP-SM-GW modifies the source address in the short message of the sender to the special prefix and the IMSI of the sender.
  • the special prefix indicates the short message.
  • the destination address will be modified to the called IMSI, and the short message content will not be modified.
  • the short message sent by the sender has different RP (Relay-Layer Protocol) formats, the first type is RP-M0-DATA, and the second type is RP-MT-DATA.
  • RP Relay-Layer Protocol
  • the IP-SM-GW When the IP-SM-GW needs to send a short message that fails to be sent to the SC, it will identify the format of the short message of the sender.
  • the format of the short message of the sender When the format of the short message of the sender is the first format, the format of the short message does not need to be modified. Only need to modify the source address and destination address;
  • the format of the short message of the sender is the second format, the format is converted into the first format, and then the source address and the destination address are falsified.
  • Step S224 The IP-SM-GW sends the short message to the SC for storage, and receives the status report after the SC is stored.
  • the IP-SM-GW sends the short message to the SC through the SMS-IWMSC, and receives the status report of the short message stored by the SC through the SMS-IWMSC.
  • the SC judges that the short message is a short message that fails to be sent by identifying the MT Correlation ID or SMSCN or a special prefix value, and stores only the short message and does not continue to transmit.
  • the SC stores the received short message and stores the short message with the MT Correlation ID or SMSCN or the receiving end IMSI.
  • Step 23 When the HSS learns that the state of the receiving UE becomes available, the SC is triggered to resend the short message related to the receiving end.
  • the HSS when the UE is powered on for IMS registration, or the memory is available, or the SIP short message is changed to support the SIP short message, or the UE is reachable, the HSS can learn that the receiving UE is unavailable. The status becomes available.
  • the HSS can The SC is triggered to resend the short message by sending a prompt SC (alert service centre) message.
  • the HSS may send an alert service centre message to the SC through the SMS-IWMSC.
  • the HSS may carry the MT Correlation ID or the SMSCN or the IMSI of the receiving UE in the alert service centre message.
  • the SC may obtain the short message corresponding to the short message from the stored short message according to the IM Correlation ID or the SMSNre of the receiving service UE message, that is, the short message associated with the MT Correlation ID or the SMSNN may be found according to the MT Correlation ID.
  • the message or the short message according to the destination address is the IMSI of the receiving UE.
  • Step 24 The SC sends the stored short message to the IP-SM-GW.
  • the step may include, as shown in FIG. 2C.
  • Step S240 The SC modifies the source address and the destination address of the stored short message.
  • the SC modifies the source address of the stored short message to the SC address, and the destination address is modified to the MT Correlation ID, and the short message content is not modified; or
  • the source address is the SMSNN and the IP-SM-GW ID in the stored short message
  • the source address of the stored short message is modified to the SC address, and the destination address is modified to the SMSNN and the IP-SM-GW ID, and the short message content is not modified.
  • the source address in the stored short message is a special prefix and a sender IMSI
  • the source address of the stored short message is modified to be the primary identity, the destination address, and the short message content is not modified.
  • Step S241 The SC sends the modified short message to the SMS-GMSC;
  • Step S242 The SMS-GMSC obtains the routing information by querying the HSS, that is, obtains the IP-SM-GW address to which the receiving end belongs, and returns it to the SMS-GMSC.
  • the SMS-GMSC may find the HSS where the receiving end is located according to the MT Correlation ID, and the HSS further finds the address of the corresponding IP-SM-GW according to the MT Correlation ID; or finds the corresponding IP by using the IMSI of the transmitting end and the receiving end. - The address of the SM-GW.
  • step S242 only the destination address of the short message sent by the SC is the MT Correlation ID or the called party.
  • the IMSI situation is only implemented.
  • Step S243 The SMS-GMSC sends the short message sent by the SC to the IP-SM-GW.
  • Step S25 The IP-SM-GW generates a short message request according to the short message sent by the SC, and passes the
  • the S-CSCF is sent to the receiving end U E.
  • the IP-SM-GW finds a SIP URI of the corresponding sender and the receiver according to the source address or the destination address in the short message sent by the SC, thereby generating a short message request, where the short message request may be SIP. Request message.
  • the corresponding receiving SIP URI or the SIP URI of the sending end and the receiving end may be found according to the MT Correlation ID, or the corresponding receiving SIP URI or the SIP URI of the sending end and the receiving end may be found according to the SMSNN, or according to the sending side.
  • the IMSI of the sender finds the corresponding SIP URI of the receiver and the SIP URI of the sender.
  • the IP-SM-GW when the receiving end fails to send a short message request to the receiving end due to unavailability, the IP-SM-GW sends the short message corresponding to the short message request to the SC for storage. Processing, and when the receiving end becomes available, resending the short message request to the receiving end, the retransmission short message request can be resent, thereby improving the availability of sending the short message request in the IMS, and improving User experience.
  • FIG. 3A is a flow chart showing a method for implementing short message retransmission according to Embodiment 2 of the present invention.
  • the short message request for sending the short message does not pass through the IP-SM-GW of the receiving end network.
  • Step S30 The S-CSCF receives the short message request sent by the sending side.
  • the short message request includes the short message content and the receiving end UE information.
  • other information may be included, such as the SC address information of the short message stored when the short message is sent, and the SC address is the SC address to which the sender carries when sending the short message.
  • the short message request is a SIP request message.
  • Step S31 The S-CSCF determines whether the short message is successfully sent to the receiving UE.
  • the S-CSCF may determine whether the short message is successfully sent to the receiving UE according to the registration information of the receiving UE or the received response message.
  • the S-CSCF saves the registration information of the receiving UE as the offline or the offline information, that is, the S-CSCF can determine whether the receiving UE is powered off by using the registration information of the receiving UE that is saved by itself.
  • the short message cannot be successfully sent to the receiving end UE; or the receiving end UE fails to return the failed response message or the short message if the memory of the receiving end UE is full or does not support the SIP message type.
  • the reported response message is sent to the S-CSCF. Therefore, the S-CSCF can determine that the short message is not successfully sent to the receiving UE by using the returned response message, and can also consider that the short message is sent.
  • Step S32 When it is determined that the short message request cannot be successfully sent to the receiving UE, the S-CSCF obtains the IP-SM-GW address to which the receiving UE belongs.
  • the S-CSCF itself saves the IP-SM-GW address to which the receiving UE belongs, the IP-SM-GW address is directly extracted; if the S-CSCF does not save the IP of the receiving UE, The SM-GW address is used to obtain the IP-SM-GW address from the HSS to which the receiving UE belongs.
  • the HSS if the HSS does not configure the IP-SM-GW address for the receiving UE, the HSS is based on the receiving end.
  • the identity information (SIP URI, IMSI) of the UE allocates an I P-SM-G W address to the receiving UE.
  • Step S33 The S-CSCF notifies the IP-SM-GW that the short message transmission fails.
  • the notification message carries a short message.
  • Step S34 After determining that the received short message fails to be sent, the IP-SM-GW extracts the short message, and sends the short message to the SC for storage.
  • the step of the IP-SM-GW sending the short message to the SC for storage may further include, as shown in FIG. 3B.
  • Step S340 The IP-SM-GW generates a Mobile Terminated Correlation ID (MT Correlation ID) ilSMSCN (SMS-correlation number) associated value; and the IP-SM-GW stores the MT Correlation ID or the SIP URI of the SMSNN and the receiving end of the short message. Form of identity.
  • the IP-SM-GW may also store the identity of the MT Correlation ID or the SIP URI of the SMSC and the sender and the receiver of the short message.
  • the MT Correlation ID format is MCC (3 digits) + MNC (3 digits) + send ID (9 digits), the MCC is the country code, the MNC is the carrier code, and the Sender ID is the 9-digit value randomly generated by the terminal.
  • the bit value should contain the receiver UE HSS identification number, so that the sender ID can be determined by the sender ID in the MT Correlation ID; the SMSCN is a 3-digit value generated for the terminal; in this embodiment, the IP-SM-GW is receiving
  • the party terminal generates an association identifier (MT Correlation ID) or SMSNN, and after the UE is available, the SC matches the corresponding short message by the MT Correlation ID or SMSNN, retransmits it, and the IP-SM-GW according to the MT Correlation ID or
  • the SMSCN matches the identity of the SIP URI of the short message sender or the receiver, and then generates a SIP request message carrying the short message content, and sends the SIP request message to the receiving UE.
  • Step S341 The IP-SM-GW acquires the SC address.
  • the short message may be sent to the SC address to which the receiving end belongs, or the SC address to which the sending end belongs may be obtained, and the obtained address is stored.
  • the IP-SM-GW If the short message is sent to the SC address to which the receiving end belongs, if the IP-SM-GW itself saves the SC address to which the receiving end UE belongs, the SC address is directly extracted; if the IP-SM-GW does not know the UE of the receiving end The SC address, the IP-SM-GW acquires the SC address to which the receiving UE belongs from the HSS to which the receiving UE belongs. In this embodiment, the IP-SM-GW queries the HSS for the SC address to which the receiving UE belongs; if the HSS does not configure the SC address for the receiving UE, the HSS according to the identity information of the receiving UE (SIP URI, IMSI) The SC address is allocated to the receiving UE. In this embodiment, after the IP-SM-GW acquires the SC address to which the receiving end belongs, the SC address needs to be saved.
  • the IP-SM-GW extracts the SC address to which the sender belongs from the short message request received in step S20, and saves the SC address.
  • Step S342 The IP-SM-GW notifies the HSS of the failure to send the short message.
  • the notification message includes at least a receiver identity (IMSI or SIP URI), an SC address, an association identifier, or an SMSCN, and may also include an IP-SM-GW address and a reason for the failure of transmission, and the HSS receives the notification. After that, save the above information in the WMD ( message waiting data ) message.
  • Step S343 Extracting a short message according to the short message request; in the embodiment, the short message includes information such as a short message content, a source address, and a destination address, and the source address and the destination address in the extracted short message by the IP-SM-GW. Make changes, the content of the short message is not modified.
  • the I P-SM-G W modifies the source address in the short message of the sending end to the MT Correlation ID, and modifies the destination address to the SC address, and the short message content is not modified; or the short message in the sending end
  • the source address is modified to the SMSNN and the IP-SM-GW ID, and the destination address is modified to the SC address, and the short message content is not modified.
  • the IP-SM-GW can According to the SIP URI of the receiving end, the HSS is searched for the subscription information of the receiving end, and the IMSI of the receiving end is found.
  • the sending end also carries the identity information in the form of its own telephone number in the short message, such as the IMSI of the sending end, and the IP-SM-GW saves and sends.
  • the identity of the endpoint such as IMSI
  • the identifier of the receiver IMSI
  • the IP-SM-GW modifies the source address in the short message of the sender to the special prefix and the IMSI of the sender.
  • the special prefix indicates that the short message is short.
  • the message will modify the destination address to the called IMSI, and the short message content will not be modified.
  • the short message sent by the sender has different RP (Relay-Layer Protocol) formats, the first type is RP-M0-DATA, and the second type is RP-MT-DATA.
  • RP Relay-Layer Protocol
  • the IP-SM-GW When the IP-SM-GW needs to send a short message that fails to be sent to the SC, it will identify the format of the short message of the sender.
  • the format of the short message of the sender When the format of the short message of the sender is the first format, the format of the short message does not need to be modified. Only need to modify the source address and destination address;
  • the format of the short message of the sender is the second format, the format is converted into the first format, and then the source address and the destination address are falsified.
  • Step S344 The IP-SM-GW sends the short message to the SC for storage, and receives the status report after the SC is stored.
  • the IP-SM-GW sends the short message to the SC through the SMS-IWMSC, and receives the status report of the short message stored by the SC through the SMS-IWMSC.
  • the SC judges that the short message is a short message that fails to be sent by identifying the MT Correlation ID or SMSCN or a special prefix value, and stores only the short message and does not continue to transmit.
  • the SC stores the received short message and stores the association relationship between the short message and the MT Correlation ID or SMSCN or the receiving end IMSI.
  • Step S35 When the HSS learns that the state of the receiving UE becomes available, the SC is triggered to resend the short message related to the receiving end.
  • the HSS can know that the receiving UE changes from the unavailable state to the available state.
  • the HSS may trigger the SC to resend the short message by sending a message indicating the SC (alert service centre).
  • the HSS sends a prompt service center message to the service center, where the prompt service center message carries an association identifier or an SMSSI or an IMSI of the receiver UE, and after receiving the message, the service center sends and The association identifies a stored short message associated with the association.
  • the HSS may send an alert service centre message to the SC through the SMS-IWMSC.
  • the HSS may carry the MT Correlation ID or the SMSCN or the IMSI of the receiving UE in the alert service centre message.
  • the SC may obtain the short message corresponding to the short message from the stored short message according to the IM Correlation ID or the SMSNre of the receiving service UE message, that is, the short message associated with the MT Correlation ID or the SMSNN may be found according to the MT Correlation ID.
  • the message or the short message according to the destination address is the IMSI of the receiving UE.
  • Step 35 The SC sends the stored short message to the IP-SM-GW.
  • the step may include, as shown in FIG. 3C:
  • Step S350 The SC modifies the source address and the destination address of the stored short message.
  • the SC modifies the source address of the stored short message to the SC address, and the destination address is modified to the MT Correlation ID, and the short message content is not modified; or
  • the source address is the SMSNN and the IP-SM-GW ID in the stored short message
  • the source address of the stored short message is modified to the SC address, and the destination address is modified to the SMSNN and the IP-SM-GW ID, and the short message content is not modified.
  • the source address in the stored short message is a special prefix and a sender IMSI
  • the source address of the stored short message is modified to be the primary identity, the destination address, and the short message content is not modified.
  • Step S351 The SC sends a new short message to the SMS-GMSC;
  • Step S352 The SMS-GMSC obtains the routing information by querying the HSS, that is, obtains the IP-SM-GW address to which the receiving end belongs, and returns it to the SMS-GMSC.
  • the SMS-GMSC can find the HSS where the receiving end is located according to the MT Correlation ID, and the HSS further finds the address of the corresponding IP-SM-GW according to the MT Correlation ID; or finds the address of the corresponding IP-SM-GW through the IMSI of the transmitting end and the receiving end. .
  • Step S352 is performed only when the destination address of the short message sent by the SC is the MT Correlation ID or the called IMSI.
  • Step S353 The SMS-GMSC sends the short message sent by the SC to the IP-SM-GW.
  • Step 36 The IP-SM-GW generates a short message request according to the short message sent by the SC, and sends the short message request to the receiving end U E through the S-CSCF.
  • the IP-SM-GW finds a SIP URI of the corresponding sender and the receiver according to the source address or the destination address in the short message sent by the SC, thereby generating a short message request, where the short message request may be SIP. Request message.
  • the corresponding receiving SIP URI or the SIP URI of the sending end and the receiving end may be found according to the MT Correlation ID, or the corresponding receiving SIP URI or the SIP URI of the sending end and the receiving end may be found according to the SMSNN, or according to the sending side.
  • the IMSI of the sender finds the corresponding SIP URI of the receiver and the SIP URI of the sender.
  • the IP-SM-GW when the receiving end fails to send a short message request to the receiving end due to unavailability, the IP-SM-GW sends the short message corresponding to the short message request to the SC for storage. Processing, and when the receiving end becomes available, resending the short message request to the receiving end, the retransmission short message request can be resent, thereby improving the availability of sending the short message request in the IMS, and improving User experience.
  • FIG. 4 is a flowchart of a method for implementing short message retransmission according to Embodiment 3 of the present invention.
  • the short message requesting to send the short message passes through the IP-SM-GW of the receiving end network.
  • the short message cannot be sent to the receiving end due to the abnormality.
  • the short message request may be stored in the IP-SM-GW.
  • the IP address is triggered again.
  • the SM-GW resends the short message request.
  • Step S40 The IP-SM-GW receives the short message request forwarded by the S-CSCF.
  • the short message request includes short message content and receiving UE information.
  • it can also include the sender
  • the indication information is used to indicate that if the short message request fails to be sent, the short message request is locally stored, and the network entity stores the short message request that failed to be sent on the receiving end according to the indication.
  • IP-SM-GW to which the UE belongs.
  • Step S41 The IP-SM-GW determines whether the short message is successfully sent to the receiving UE.
  • the IP-SM-GW may determine whether the short message is successfully sent to the receiving UE according to the received response message.
  • the receiving end UE when the receiving end UE is unreachable, or the memory is full or does not support the SIP message type, the receiving end UE returns a failure response message or a short message failure report response message to the IP-SM-GW, and thus, the IP The SM-GW may determine that the short message is not successfully sent to the receiving UE by using the returned response message, and may consider that the short message is sent.
  • Step S42 When it is determined that the short message request cannot be successfully sent to the receiving UE, the IP-SM-GW stores the short message request, and stores the receiving end U E identity information corresponding to the short message request.
  • Step S43 When the IP-SM-GW learns that the receiving UE becomes available, the S-CSCF sends the stored short message request to the receiving UE.
  • the IP-SM-GW It can be known that the receiving UE changes from an unavailable state to an available state.
  • the IP-SM-GW performs the short message request storage processing, and when the receiving end When the status is changed to the available state, the short message request is resent to the receiving end, so that the short message request for resending the sending failure can be re-transmitted, thereby improving the availability of the short message request sent by the IMS and improving the user experience.
  • FIG. 5A is a flow chart of a method for implementing short message retransmission according to Embodiment 4 of the present invention.
  • the short message request for sending the short message does not pass through the IP-SM-GW.
  • the short message cannot be sent to the receiving end because of the abnormality.
  • the short message request can be sent and stored in the IP-SM-GW. After the receiving end eliminates the abnormality, trigger The IP-SM-GW resends the short message request.
  • Step S50 The S-CSCF receives the short message request sent by the sending side.
  • the short message request is a SIP request message
  • the short message request includes information such as short message content, receiving UE information, and the like.
  • the indication information carried by the sender may be further included, where the indication information is used to indicate that the short message or the short message request is locally stored if the short message request fails to be sent, and the network entity sends a failed short message or short message according to the indication.
  • Request the IP-SM-GW stored at the receiving end.
  • Step S51 The S-CSCF determines whether the short message is successfully sent to the receiving UE.
  • the S-CSCF may determine whether the short message is successfully sent to the receiving UE according to the registration information of the receiving UE or the received response message.
  • the receiving end UE if the receiving end UE is powered off, the registration information of the receiving end UE saved by the S-CSCF itself is offline or not in the network, that is, the S-CSCF saves the registration information of the receiving UE by itself. It can be determined whether the receiving end UE is powered off.
  • the receiving end UE may return a failure response message or a response message of the short message failure report to the S-CSCF. Therefore, the S-CSCF may determine that the short message is not successfully sent to the receiving UE by using the returned response message, and may also consider the short message to be sent. failure.
  • Step S52 When it is determined that the short message request cannot be successfully sent to the receiving UE, the S-CSCF obtains the IP-SM-GW address to which the receiving UE belongs.
  • the S-CSCF itself saves the IP-SM-GW address to which the receiving UE belongs, the IP-SM-GW address is directly extracted; if the S-CSCF does not save the IP of the receiving UE, The SM-GW address is used to obtain the IP-SM-GW address from the HSS to which the receiving UE belongs.
  • the HSS if the HSS does not configure the IP-SM-GW address for the receiving UE, the HSS is based on the receiving end.
  • the identity information (SIP URI or IMSI) of the UE allocates an IP-SM-G W address to the receiving UE.
  • Step S53 The S-CSCF sends a short message request that fails to be sent to the IP-SM-GW for storage.
  • the IP-SM-GW determines to receive the short message request that failed to be transmitted, and stores it, it returns the confirmation information to the S-CSCF.
  • the indication information may be carried in the request to indicate that the IP-SM-GW requests the short message to be sent, so that the request is stored, and the indication information can be implemented as follows:
  • the Content-Disposition header adds a failing SMS field, indicating that the message body of the request is a failed short message, and does not need to be sent, but only saved, meaning that the request corresponding to the short message is saved;
  • the Subject header adds a save SMS request field indicating that the purpose of the request message is to save the request.
  • Step S54 When it is known that the receiving UE becomes available, the IP-SM-GW is triggered to resend the short message request to the receiving UE.
  • the IP-SM-GW is triggered to resend the short message request to the receiving UE.
  • it can be implemented in three different ways.
  • Step S540 After the S-CSCF confirms that the short message request fails to be sent, and receives the acknowledgement information sent by the IP-SM-GW, the S-CSCF stores the status and information of the short message request transmission failure.
  • the information may include identity information of the receiving UE, an IP-SM-GW address for storing the short message request, and a reason why the short message request fails to be sent;
  • Step S541 When the S-CSCF learns that the receiving UE becomes available, if the UE starts to perform IMS registration, or the memory is available, or the SIP short message is changed to support the SIP short message or is reachable again, the IP is triggered. - the SM-GW sends the stored short message request;
  • Step S542 The IP-SM-GW resends the stored short message request to the receiving end UE through the S-CSCF.
  • Step S543 The IP-SM-GW subscribes to the HSS for status information of whether the receiving end UE is available.
  • Step S544 When the HSS learns that the receiving end UE becomes available, if the UE starts the IMS registration, or the memory is available, or When the SIP short message is changed to support the SIP short message or reachable again, the available status information is notified to the IP-SM-GW;
  • Step S545 The IP-SM-GW sends the stored short message request to the receiving end through the S-CSCF.
  • Step S546 The IP-SM-GW notifies the HSS of the failure to send the short message.
  • the HSS adds the following record in the waiting data (MWD, message waiting data) corresponding to the short message, including the UE information of the receiving end, the IP-SM-GW address for storing the short message request, and the sending of the short message request failed. s reason;
  • Step S547 When the HSS learns that the receiving UE becomes available, if the UE starts to perform IMS registration, or the memory is available, or the SIP short message is changed to support the SIP short message or is reachable again, the receiving end is checked.
  • Step S548 When it is determined that the MWD is not empty, send a prompt message to the designated IP-SM-GW to alert the service center message;
  • Step S549 The IP-SM-GW sends the stored short message request to the receiving end through the S-CSCF.
  • the IP-SM-GW performs the short message request storage processing, and when the receiving end When the status is changed to the available state, the short message request is resent to the receiving end, so that the short message request for resending the sending failure can be re-transmitted, thereby improving the availability of the short message request sent by the IMS and improving the user experience.
  • FIG. 6A is a flow chart showing a method for implementing short message retransmission according to Embodiment 5 of the present invention.
  • the short message request for sending the short message passes through the IP-SM-GW.
  • the IP-SM-GW processes the transmission failure.
  • the receiving end is abnormal.
  • the short message cannot be sent to the receiving end.
  • the short message request can be stored in the SMS-AS. After the receiving end cancels the abnormality, the SMS-AS is triggered to resend the short message.
  • Step S60 The IP-SM-GW receives the short message request forwarded by the S-CSCF.
  • the short message request includes short message content, receiving UE, and the like.
  • the indication information may be further configured to indicate that if the short message request fails to be sent, the short message request is locally stored, and the network entity stores the short message request that failed to be sent in the SMS-AS of the receiving end according to the indication.
  • Step S61 The IP-SM-GW determines whether the short message is successfully sent to the receiving UE. In this embodiment, the IP-SM-GW may determine, according to the received response message, whether the short message is successfully sent to the receiving UE.
  • the receiving end UE if the receiving end UE is unreachable, or the memory is full or does not support the SIP message type, the receiving end UE returns a failure response message or a short message failure report response message to the IP-SM-GW, and thus, The IP-SM-GW may determine that the short message is not successfully sent to the receiving UE by using the returned response message, and may consider that the short message is sent.
  • Step S62 When it is determined that the short message request cannot be successfully sent to the receiving UE, the IP-SM-GW sends the short message request to the SMS-AS for storage. In this embodiment, after the SMS-AS stores the short message request, an acknowledgment message is returned to the IP-SM-GW.
  • Step S63 When it is known that the receiving UE becomes available, the SMS-AS is triggered to resend the short message request.
  • the SMS-AS is triggered to resend the short message request.
  • it can be implemented in three different ways.
  • Step S630 After the IP-SM-GW sends the short message request that fails to be sent to the SMS-AS, the IP-SM-GW stores the status and information of the short message request failure.
  • the information may include identity information of the receiving UE, an SMS-AS address for storing the short message request, and a reason for the short message request failure to be sent;
  • Step S631 when the IP-SM-GW learns that the receiving UE becomes available, such as when the UE is powered on for IMS registration, or the memory is available, or when the SIP short message is not supported to support the SIP short message or reachable again, Notifying the SMS-AS to send the stored short message request;
  • Step S632 The SMS-AS sends the short message request to the receiving end through the S-CSCF.
  • Step S633 The SMS-AS subscribes to the HSS for the status information of the receiving end UE.
  • Step S634 When the HSS learns that the receiving end UE becomes available, if the UE starts the IMS registration, or the memory is available, or does not support the SIP short When the message becomes a SIP short message or is reachable again, the available status information is notified to the SMS-AS;
  • Step S635 The SMS-AS resends the stored short message request to the receiving end UE through the S-CSCF.
  • Step S636 The SMS-AS notifies the HSS that the short message request failed to be sent.
  • the HSS records the message waiting data (MWD, message waiting data) corresponding to the short message, and the MWD includes the UE information of the receiving end, the SMS-AS address for storing the short message request, and the reason why the short message request fails to be sent. ;
  • Step S637 When the HSS learns that the receiving UE is in an available state, if the UE is powered on for IMS registration, or the memory is available, or when the SIP short message is not supported to support the SIP short message or reachable again, the receiving UE is checked. MWD;
  • Step S638 when it is determined that the MWD is not empty, send a prompt message to the SMS-AS to alert the service center message;
  • Step S639 The SMS-AS sends the stored short message request to the receiving end through the S-CSCF.
  • the IP-SM-GW when the receiving end fails to send a short message request to the receiving end due to unavailability, the IP-SM-GW sends the short message request to the SMS-AS for storage processing. And when the receiving end becomes available, resending the short message request to the receiving end, the retransmission short message request may be resent, thereby improving the availability of the short message request sent by the IMS, and improving the user's Experience.
  • FIG. 7A is a flow chart showing a method for implementing short message retransmission according to Embodiment 6 of the present invention.
  • the short message request for sending the short message does not pass through the IP-SM-GW, and the S-CSCF handles the failure of the short message transmission.
  • the short message cannot be sent to the receiving end due to the abnormality.
  • the short message request may be stored in the SMS-AS.
  • the SMS-trigger is triggered.
  • the AS resends the short message.
  • Step S70 The S-CSCF receives the short message request sent by the sending side.
  • the The short message request includes short message content and receiving UE information.
  • the short message request is a SIP request message.
  • the indication information carried by the sender may be further included, and the indication information is used to indicate that the short message request is locally stored if the short message request fails to be sent, and the network entity stores the short message request that failed to be sent in the SMS of the receiving end according to the indication. -AS.
  • Step S71 The S-CSCF determines whether the short message is successfully sent to the receiving UE.
  • the S-CSCF may determine whether the short message is successfully sent to the receiving UE according to the registration information of the receiving UE or the received response message.
  • the receiving end UE if the receiving end UE is powered off, the registration information of the receiving end UE saved by the S-CSCF itself is offline or not in the network, that is, the S-CSCF saves the registration information of the receiving UE by itself.
  • the receiving end UE It can be determined whether the receiving end UE is powered off, and if it is determined that the receiving end UE is in the power-off state, the short message cannot be successfully sent to the receiving end UE; or when the receiving end UE's memory is full or does not support the SIP message type, the receiving end UE returns The failed response message or the response message of the short message failure report is sent to the S-CSCF. Therefore, the S-CSCF may determine that the short message is not successfully sent to the receiving UE by using the returned response message, and may also consider that the short message transmission fails.
  • Step S72 The S-CSCF sends the short message request to the SMS-AS for storage.
  • the confirmation message is returned to the S-CSCF.
  • Step S73 When it is learned that the receiving UE is in an available state, trigger the SMS-AS to resend the short message request.
  • the SMS-AS When it is learned that the receiving UE is in an available state, trigger the SMS-AS to resend the short message request.
  • it can be implemented in three different ways.
  • Step S730 After the S-CSCF confirms that the short message request fails to be sent, and receives the acknowledgement message sent by the SMS-AS, the S-CSCF stores the status and information of the short message request transmission failure.
  • the information may include identity information of the receiving UE, an SMS-AS address for storing the short message request, and a reason why the short message request fails to be sent;
  • Step S731 When the S-CSCF learns that the receiving UE becomes available, if the UE starts to perform IMS registration, or the memory is available, or the SIP short message is changed to support the SIP short message or is reachable again, the SMS is notified. - the AS sends the stored short message request; Step S732: The SMS-AS sends the short message request to the receiving end UE through the S-CSCF.
  • Step S733 The SMS-AS subscribes to the HSS to subscribe to the UE for availability status information
  • Step S734 When the HSS learns that the receiving UE becomes available, if the UE is powered on for IMS registration, or the memory is available, or the SIP short message is changed to support the SIP short message or reachable again, the available state is obtained.
  • Information notification SMS-AS
  • Step S735 The SMS-AS sends the stored short message request to the receiving end through the S-CSCF.
  • Step S736 The SMS-AS notifies the HSS that the short message request failed to be sent.
  • the HSS records the message waiting data (MWD, message waiting data) corresponding to the short message, and the MWD includes the UE information of the receiving end, the SMS-AS address for storing the short message request, and the reason why the short message request fails to be sent. ;
  • Step S737 When the HSS learns that the receiving UE becomes available, if the UE starts the IMS registration, or the memory is available, or the SIP short message is changed to support the SIP short message or is reachable again, the receiving end is checked.
  • UE's MWD When the HSS learns that the receiving UE becomes available, if the UE starts the IMS registration, or the memory is available, or the SIP short message is changed to support the SIP short message or is reachable again, the receiving end is checked.
  • Step S738 When it is determined that the MWD is not empty, send a prompt message to the SMS-AS to alert the service center message;
  • Step S739 The SMS-AS retransmits the stored short message request to the receiving end UE through the S-CSCF.
  • the S-CSCF when the receiving end fails to send a short message request to the receiving end due to unavailability, the S-CSCF sends the short message request to the SMS-AS for storage processing, and when When the receiving end becomes available, the short message request is resent to the receiving end, and the short message request for resending the sending failure can be implemented, thereby improving the availability of sending the short message request in the IMS and improving the user experience.
  • FIG. 8 is a structural diagram of an apparatus for implementing short message retransmission according to Embodiment 7.
  • the apparatus may include a determining module 80, a storage processing module 82, and a retransmission module 84.
  • the determining module 80 is configured to determine whether a short message request sent to the receiving end in the IMS domain fails to be sent.
  • the storage processing module 82 is configured to perform storage processing on the short message request when the determining module 80 determines that the short message request fails to be sent.
  • the short message cannot be sent to the receiving end due to the abnormality, and the storage processing module 82 may request the short message corresponding to the short message.
  • the SC sent to the network in the receiving end is stored, and may be sent to the SC to which the sending end corresponding to the short message belongs, and the storage processing module 82 may also store the short message request in the IP-SM-GW, and the storage processing is performed.
  • the module 82 may also store the short message request in the SMS-AS.
  • the above manner is not the only implementation and is optional.
  • the retransmission module 84 is configured to send the short message request of the storage process to the receiving end through the IMS domain when the receiving end corresponding to the short message request becomes available.
  • the device provided by the embodiment of the present invention may be embedded in an IP-SM-GW or an S-CSCF.
  • the device provided by the embodiment of the present invention in the IMS domain, when the receiving end fails to send a short message request sent to the receiving end due to unavailability, the short message request is stored, and when the receiving end becomes When the status is available, the short message request is resent to the receiving end, and the short message request for resending the sending failure can be resent, thereby improving the availability of the short message request sent by the IMS and improving the user experience.
  • FIG. 9 is a structural diagram of an apparatus for implementing short message retransmission according to Embodiment 8.
  • the device shown in Fig. 8 is embedded in the IP-SM-GW.
  • the apparatus further includes a receiving module 90, configured to receive a short message request sent by the sending side forwarded by the S-CSCF.
  • the determining module 80 is specifically configured to determine whether the short message received by the receiving module 90 is successfully sent to the receiving end UE.
  • the storage processing module 82 is specifically configured to: when the determining module 80 determines that the short message request fails to be sent, send the short message corresponding to the short message request to the SC for storage. It can also be understood that when the determining module 80 learns that the short message sent to the receiving end in the IMS domain fails to be sent, the storage processing module 82 sends the short message to the service center, so that the service center stores the short message.
  • the storage processing module 82 is further configured to generate an association identifier or an SMSCN, and save the association identifier and a SIP URI (SIP Universal Resource Identifier, a universal resource identifier in the form of a SIP) of the receiving end of the short message An identity identifier, or an identity identifier in the form of a SIP URI that is sent by the sender and the receiver of the associated identifier and the short message that failed to be sent.
  • SIP URI SIP Universal Resource Identifier
  • the storage processing module 82 is further configured to acquire, by the IP-SM-GW, an address of the service center, and send the short message to the service center according to the acquired address, so that the service center stores The short message, where the short message includes the association identifier, or the short message includes the self address of the SMSNN and the IP-SM-GW.
  • the storage processing module 82 may specifically include: a generating submodule 900, an obtaining submodule 901, a notification submodule 902, and a sending submodule 903.
  • the generating sub-module 900 is used by the IP-SM-GW to generate an MT Correlation ID or SMSCN.
  • the acquisition submodule 901 is used to obtain the SC address.
  • the obtaining sub-module 901 can obtain the SC address to which the short message is sent to the receiving end, and can also obtain the SC address to which the sending end belongs.
  • the notification sub-module 902 is configured to notify the HSS of the failure to send the short message.
  • the obtaining submodule 901 is further configured to obtain a short message according to the short message request.
  • the sending submodule 903 is configured to send the obtained short message to the SC for storage according to the obtained SC address.
  • the retransmission module 84 is configured to receive the stored short message sent by the service center when the receiving end corresponding to the short message becomes available, and send the short message to the receiving end by using the IMS domain.
  • the retransmission module 84 when the corresponding receiving end of the short message request becomes available, the retransmission module 84 further generates a short message request according to the short message sent by the SC, and sends the short message request to the receiving end UE through the S-CSCF.
  • the retransmission module 84 is specifically configured to receive the service center. Sending the stored short message, and generating an IMS domain SIP message by using the association identifier or the identity information in the form of a SIP URI corresponding to the SMSN, and sending the message to the receiving end, where the IMS domain SIP message includes the receiving Short message.
  • the S-CSCF when the S-CSCF receives the short message request sent by the sending side, the S-CSCF sends the short message request to the receiving end UE.
  • the S-CSCF fails to send the short message request, it sends a failure notification message to the IP-
  • the receiving module 90 can also receive the failure notification message sent by the S-CSCF.
  • the determining module 80 can also determine, according to the failure notification, that the short message request sent to the receiving UE fails to be sent.
  • the storage processing module 82 sends the short message corresponding to the short message request to the SC for storage.
  • the short message requesting to the receiving end fails to be sent due to the unavailability of the receiving end
  • the short message corresponding to the short message request of the IP-SM-GW is sent to the SC for storage. Processing, and when the receiving end becomes available, resending the short message request to the receiving end, retransmission of the short message request failed to be sent, thereby improving the availability of sending the short message request in the IMS, and improving User experience.
  • FIG. 10 is a structural diagram of an apparatus for implementing short message retransmission provided in Embodiment 9.
  • the device shown in Fig. 8 is embedded in the IP-SM-GW.
  • the apparatus further includes a receiving module 100, configured to receive a short message request sent by the sending side forwarded by the S-CSCF.
  • the determining module 80 is specifically configured to determine whether the short message received by the receiving module 100 is successfully sent to the receiving UE.
  • the storage processing module 82 is specifically configured to store the short message request when the determining module 80 determines that the short message request fails to be sent. In this embodiment, it is also understood that when the determining module 80 learns that the short message sent to the receiving end in the IMS domain fails to be sent, the storage processing module 82 stores the short message request corresponding to the short message that failed to be sent.
  • the retransmission module 84 may resend the stored processed short message to the receiving end through the IMS domain.
  • the retransmission module 84 is specifically configured to: when the determining module 80 determines that the corresponding receiving end of the short message request is changed When the state is available, the short message request stored by the storage processing module 82 is sent to the receiving UE through the S-CSCF.
  • the receiving module 100 is further configured to receive information that is available to the receiving end sent by the S-CSCF, or receive a notification message that is available to the receiving end sent by the HSS.
  • the determining module 80 is further configured to: when the receiving module 100 receives the information that is available to the receiving end sent by the S-CSCF or receives the notification message that is sent by the receiving end that is sent by the HSS, determine that the short message request corresponds to The receiving end becomes available.
  • the S-CSCF when the S-CSCF receives the short message request sent by the sending side, the S-CSCF sends the short message request to the receiving end UE.
  • the S-CSCF fails to send the short message request, it sends a failure notification message to the IP-
  • the receiving module 100 may also receive a failure notification message sent by the S-CSCF.
  • the determining module 80 can also determine, according to the failure notification, that the short message request sent to the receiving UE fails to be sent.
  • the storage processing module 82 stores the short message request.
  • the S-CSCF determines that the corresponding receiving end of the short message request becomes available, the S-CSCF notifies the retransmission module 84 to send the stored short message request to the S-CSCF, and sends the S-CSCF to the receiving UE through the S-CSCF. .
  • the IP-SM-GW performs the storage processing of the short message request, and when the receiving end When the status is changed to the available state, the short message request is resent to the receiving end, so that the short message request for resending the sending failure can be re-transmitted, thereby improving the availability of the short message request sent by the IMS and improving the user experience.
  • FIG. 11 is a structural diagram of an apparatus for implementing short message retransmission according to Embodiment 9.
  • the device shown in Fig. 8 is embedded in the IP-SM-GW.
  • the apparatus further includes a receiving module 1 10, configured to receive a short message request sent by the sending side forwarded by the S-CSCF.
  • the determining module 80 is specifically configured to determine whether the short message received by the receiving module 1 10 is successfully sent to the receiving UE.
  • the storage processing module 82 is specifically configured to: when the determining module 80 determines that the short message request fails to be sent, send the short message request to the SMS-AS for storage.
  • the retransmission module 84 is specifically configured to trigger the SMS-AS to resend the short message request when the corresponding receiving end of the short message request becomes available.
  • the IP-SM-GW when the receiving end fails to send a short message request to the receiving end due to unavailability, the IP-SM-GW sends the short message request to the SMS-AS for storage processing. And when the receiving end becomes available, resending the short message request to the receiving end, the resending short message request may be resent, thereby improving the availability of the short message request sent by the IMS, and improving the user's Experience.
  • FIG. 12 is a structural diagram of an apparatus for implementing short message retransmission according to Embodiment 9.
  • the device shown in Fig. 8 is embedded in the S-CSCF.
  • the apparatus further includes a receiving module 120, configured to receive a short message request sent by the sending side.
  • the determining module 80 is specifically configured to determine whether the short message received by the receiving module 120 is successfully sent to the receiving UE.
  • the storage processing module 82 is specifically configured to: when the determining module 80 determines that the short message request fails to be sent, send the short message request to the SMS-AS for storage.
  • the retransmission module 84 is specifically configured to trigger the SMS-AS to resend the short message request when the corresponding receiving end of the short message request becomes available.
  • the IP-SM-GW when the receiving end fails to send a short message request to the receiving end due to unavailability, the IP-SM-GW sends the short message request to the SMS-AS for storage processing. And when the receiving end becomes available, resending the short message request to the receiving end, the retransmission short message request may be resent, thereby improving the availability of the short message request sent by the IMS, and improving the user's Experience.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).
  • ROM read-only memory
  • RAM random access memory

Abstract

本发明公开一种实现短消息重发的方法，包括：当IP-SM-GW获知在IMS域中发送至接收端的短消息发送失败时，所述IP-SM-GW将所述短消息发送到业务中心，以使得所述业务中心存储所述短消息；当所述短消息对应的接收端变为可用状态时，所述IP-SM-GW接收所述业务中心发送的所述存储的短消息，并通过所述IMS域重新发送至所述接收端，从而可以实现重发发送失败的短消息请求，从而提高在IMS发送短消息请求的可用度，并提高了用户的体验。

Description

一种实现短消息重发的方法和装置
技术领域 本发明涉及通信技术领域， 尤其涉及一种实现短消息重发的方法和装置。 背景技术
传统的移动终端之间通信业务（例如呼叫、 短消息） 都依赖于终端的
MSISDN (MS international PSTN/ISDN number, 移动台国际 PSTN/ISDN号 码）， 而对于由 M2M(machine to machine, 机器对机器)通信产生的一种通信 终端， 此类终端没有 MSISDN , 无法依赖于 MSISDN进行通信。
在现有技术中， 涉及到不依赖于 MSISDN进行通信的场景包括：服务器与 无 MSISDN终端之间通过 SMS ( Short Message Service, 短消息业务）通信、 无 MSISDN终端与无 MSISDN终端通过 SMS通信。
在现有技术中，由于双方终端可以通过 SIP URK SIP Universal Resource Identifier, SIP形式的通用资源标志符） 身份进行相互识别， 因而， 可以通过 双方的 SIP URI形式的身份在 IMS ( IP multimedia subsystem , IP多媒体子 系统）传输短消息进行通信。
然而， 发明人发现在现有技术中， 在现有技术的传输短消息过程中， 如 果被叫方由于无法接收当前的短消息时， 该短消息无法在该传输过程中被存 储， 就会造成当该被叫方有能力接收短消息时， 无法接收到该短消息。 发明内容
本发明的实施例提供一种实现短消息重发的方法和装置， 以实现重发发 送失败的短消息请求。
为达到上述目的， 本发明的实施例釆用如下技术方案：
一种实现短消息重发的方法， 包括： 当 IP 短消息网关 （ Internet Protocol Short Message Gateway, IP-SM-GW ) 获知在 IP 多媒体子系统 ( Internet Protocol Multimedia Subsystem, IMS )域中发送至接收端的短消息发送失败时， 所述 IP-SM-GW 将所述短消息发送到业务中心， 以使得所述业务中心存储所述短消息；
当所述短消息对应的接收端变为可用状态时， 所述 IP-SM-GW接收所述 业务中心发送的所述存储的短消息， 并通过所述 IMS域重新发送至所述接收 端。
一种实现短消息重发的方法， 包括：
当 IP-SM-GW获知在 IMS域中发送至接收端的短消息发送失败时， 所述 IP-SM-GW存储所述发送失败的短消息对应的短消息请求；
当所述短消息对应的接收端变为可用状态时， 所述 IP-SM-GW将所述存 储处理的短消息通过所述 IMS域重新发送至所述接收端。
一种实现短消息重发的装置， 所述装置包括：
存储处理模块， 用于当获知在 IMS域中发送至接收端的短消息发送失败 时， 将所述短消息发送到业务中心， 以使得所述业务中心存储所述短消息； 重发模块， 用于当所述短消息对应的接收端变为可用状态时， 接收所述 业务中心发送的所述存储的短消息， 并通过所述 IMS域发送至所述接收端。
一种实现短消息重发的装置， 所述装置包括：
存储处理模块， 用于当获知在 IMS域中发送至接收端的短消息发送失败 时， 存储所述发送失败的短消息对应的短消息请求；
重发模块， 用于当所述短消息对应的接收端变为可用状态时， 将所述存 储处理的短消息通过所述 IMS域重新发送至所述接收端。
本发明实施例提供技术方案，在 IMS域中， 当接收端由于不可用造成发送 给该接收端的短消息请求发送失败时， 对该短消息请求进行存储处理， 并当 该接收端变为可用状态时， 重新发送短消息请求至该接收端， 就可以实现重 发发送失败的短消息请求，从而提高在 IMS发送短消息请求的可用度， 并提高 了用户的体验。 附图说明
为了更清楚地说明本发明实施例中的技术方案， 下面将对实施例描述中 所需要使用的附图作一简单地介绍， 显而易见地， 下面描述中的附图仅仅是 本发明的一些实施例， 对于本领域普通技术人员来讲， 在不付出创造性劳动 性的前提下， 还可以根据这些附图获得其他的附图。
图 1所示为本发明实施例提供的一种实现短消息重发的方法的总体流程 图；
图 2A所示为本发明实施例一提供的一种实现短消息重发的方法的流程 图；
图 2B所示为图 2A提供的一种实现短消息重发的方法的步骤 S22的流程 图；
图 2C所示为图 2A提供的一种实现短消息重发的方法的步骤 S24的流程 图；
图 3A所示为本发明实施例二提供的一种实现短消息重发的方法的流程 图；
图 3B所示为图 3A提供的一种实现短消息重发的方法的步骤 S34的流程 图；
图 3C所示为图 3A提供的一种实现短消息重发的方法的步骤 S35的流程 图；
图 4所示为本发明实施例三提供的一种实现短消息重发的方法的流程图； 图 5 A所示为本发明实施例四提供的一种实现短消息重发的方法的流程 图；
图 5B所示为图 5A提供的一种实现短消息重发的方法的步骤 S54的第一种 流程图；
图 5C所示为图 5A提供的一种实现短消息重发的方法的步骤 S54的第二种 流程图；
图 5D所示为图 5A提供的一种实现短消息重发的方法的步骤 S54的第三种 流程图；
图 6A所示为本发明实施例五提供的一种实现短消息重发的方法的流程 图；
图 6 B所示为图 6A提供的一种实现短消息重发的方法的步骤 S63的第一种 流程图；
图 6C所示为图 6A提供的一种实现短消息重发的方法的步骤 S63的第二种 流程图；
图 6D所示为图 6A提供的一种实现短消息重发的方法的步骤 S63的第三种 流程图；
图 7A所示为本发明实施例六提供的一种实现短消息重发的方法的流程 图；
图 7 B所示为图 7A提供的一种实现短消息重发的方法的步骤 S73的第一种 流程图；
图 7C所示为图 7A提供的一种实现短消息重发的方法的步骤 S73的第二种 流程图；
图 7D所示为图 7A提供的一种实现短消息重发的方法的步骤 S73的第三种 流程图；
图 8所示为实施例七提供的一种实现短消息重发的装置的结构图； 图 9所示为实施例八提供的一种实现短消息重发的装置的结构图； 图 10所示为实施例九提供的一种实现短消息重发的装置的结构图； 图 1 1所示为实施例九提供的一种实现短消息重发的装置的结构图； 图 12所示为实施例九提供的一种实现短消息重发的装置的结构图。 具体实施方式
下面将结合本发明实施例中的附图， 对本发明实施例中的技术方案进行 清楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而 不是全部的实施例。 基于本发明中的实施例， 本领域普通技术人员在没有做 出创造性劳动前提下所获得的所有其它实施例， 都属于本发明保护的范围。
在本实施例中， 在 IMS域中， 发送端的网络可以包括发送端、 发送端所属 的 S-CSCF ( Serving Call Session Control Function, 服务会话控制功能实 体） 、 发送端所属的 IP-SM-GW ( IP-Short-Message-Gateway, IP短消息网 关） 、 SC ( Service Centre, 业务中心） 。 在本实施例中， SC指短消息的业 务中心。 当发送端向接收端发送短消息时，用户终端 /服务器可以通过 S-CSCF 将短消息请求发送至接收端。 在本实施例中， 发送端的网络称为发送侧， 发 送端可以包括用户设备 ( User Equipment, UE )或服务器（server ) 。
在本实施例中， 在 IMS域中， 接收端所处的网络可以包括接收端、 接收端 所属的 S-CSCF ( Serving Call Session Control Function, 服务会话控制功能 实体） 、 接收端所属的 IP-SM-GW ( IP-Short-Message-Gateway, IP短消息 网关） 。 当然该网络还可以包括 HSS ( Home Subscriber Server, 家乡签约 寄存器 ) 、 SMS-IWMSC ( Interworking MSC For Short Message Service, 短消息业务的移动交换中心交互实体） 、 SMS-GMSC ( serving Call Session Control Function, 服务会话控制功能实体） 、 SC ( Service Centre, 业务中 心及 AS ( Application Server, 应用服务器） 。 在本实施例中， 接收端所处的 网络可以称为接收侧， 接收端可以为用户设备 UE。
在本实施例中， 在 IMS域中， 发送端通过发送端的 S-CSCF将短消息请求 发送至接收端所在网络的 S-CSCF, 再由接收端的网络的 S-CSCF所接收的短 消息请求通过 IP-SM-GW处理， 或者直接由 S-CSCF处理。
图 1所示为本发明实施例提供的一种实现短消息重发的方法的总体流程 图。
在本实施例中， 步骤 S10、 确定在 IMS域中发送至接收端的短消息请求是 否发送失败； 在本实施例中， 在 IMS域中， 由于 S-CSCF和 IP-SM-GW都可以 对该短消息请求进行处理， 因而， 在实施例中， 可以 S-CSCF或 IP-SM-GW来 确定发送至接收端的短消息请求是否发送失败。
步骤 S12、 当确定发送失败时， 对该短消息请求进行存储处理； 在本实施 例中， 在 IMS域中， 当在发送的过程中， 接收端由于异常的原因， 该短消息不 能发送至接收端， 此时， 可以通过接收端的网络中的 SC将该短消息请求对应 的短消息进行存储，也可以将该短消息请求存储在 IP-SM-GW,也可以将该短 消息请求存储在 SMS-AS中， 上述的方式不是唯一的实施方式， 为可选的。
步骤 S14、 当该短消息请求对应的接收端变为可用状态时， 将该存储处理 的该短消息请求重新通过 IMS域发送至该接收端。
在本实施例中， 在 IMS域中， 当通过接收端的网络中的 SC将该短消息进 行存储时， 当接收端消除异常后， 再将该短消息发送到 IP-SM-GW, 再由 IP-SM-GW通过 IMS域发送至该接收端进行重发； 或者， 将该发送该条短消息 的请求存储在 IP-SM-GW中， 当接收端消除异常后， 再触发 IP-SM-GW通过 IMS域发送至该接收端重发该短消息， 或者， 将该发送短消息的请求存储在 SMS-AS中， 当接收端消除异常后， 再触发 SMS-AS通过 IMS域发送至该接收 端重发该短消息。
本发明提供的实施例，在 IMS域中， 当接收端由于不可用造成发送给该接 收端的短消息请求发送失败时， 对该短消息请求进行存储处理， 并当该接收 端变为可用状态时， 重新发送短消息请求至该接收端， 就可以实现重发发送 失败的短消息请求，从而提高在 IMS发送短消息请求的可用度， 并提高了用户 的体验。
下面将针对上面的不同情况进行详细描述。
图 2A所示为本发明实施例一提供的一种实现短消息重发的方法的流程 图。
在本实施例中， 发送短消息的短消息请求经过接收端网络的 IP-SM-GW。 当在发送的过程中， 接收端由于异常的原因， 该短消息请求不能成功发送至 接收端， 即发送失败， 此时， 可以通过 SC将该短消息进行存储， 当接收端消 除异常后， 再将该短消息请求进行重发。
步骤 S20、 IP-SM-GW接收 S-CSCF转发的发送侧发送的短消息请求； 在 本实施例中， 该短消息请求包括短消息内容、 接收端 UE信息。 当然， 还可以 包括其它信息， 如当短消息发送失败时的存储短消息的 SC地址信息， 该 SC 地址为发送端在发送短消息时携带的发送端所属的 SC地址。 该短消息请求为 会话初始协议 ( Session Initiation Protocol, SIP) 请求消息。
步骤 S21、 IP-SM-GW确定该短消息是否成功发送至接收端 UE, 可以理 解为， IP-SM-GW确定该短消息发送至接收端 UE是否失败。 在本实施例中， IP-SM-GW可以根据收到的响应消息来确定该短消息是否成功发送至接收端 UE。 在本实施例中， 接收端不可达、 接收端 UE的内存已满或不支持 SIP消息 类型等情况， 接收端网络会返回失败的响应消息或短消息失败报告的响应消 息给 IP-SM-GW, 因而， IP-SM-GW可以通过返回的响应消息判断该短消息没 有成功发送至接收端 UE, 可以认为该短消息发送失败。
步骤 S22、当确定该短消息请求无法成功发送至接收端 UE时， IP-SM-GW 将该短消息请求对应的短消息发送至 SC进行存储。 在本实施例中， 该 IP-SM-GW将该短消息发送至 SC进行存储的步骤还可以包括， 如图 2B所示。
步骤 S220: IP-SM-GW生成关联标识（ Mobile Terminated Correlation ID, MT Correlation ID )或 SMSCN ( SMS-correlation number, 短消息关联值 )； IP-SM-GW保存 MT Correlation ID或 SMSCN与短消息的接收端的 SIP URI形 式的身份标识。 当然， 可选的， IP-SM-GW也可以保存 MT Correlation ID或 SMSCN与短消息的发送端及接收端的 SIP URI形式的身份标识。 其中， MT Correlation ID格式为 MCC(3位) +MNC(3位) +send ID(9位）， MCC为国家码， MNC为运营商码， Sender ID为终端随机生成的 9位数值，该 9位数值应包含接 收方 UE所在的 HSS识别号， 以使得通过关联标识 （ MT Correlation ID ) 中的 sender ID能够确定接收端所在的 HSS; SMSCN为终端生成的 3位数值； 在本 实施例中， IP-SM-GW为接收端生成关联标识（ MT Correlation ID )ilSMSCN , 其作用是为使 UE可用后， SC通过 MT Correlation ID或 SMSCN匹配到对应短 消息， 将其重新发送， 及 IP-SM-GW根据 MT Correlation ID或 SMSCN匹配到 该条短消息发送端或接收端的 SIP URI的身份标识， 进而生成携带短消息内容 的 S I P请求消息， 将 S I P请求消息发送到接收端 U E。
步骤 S221 : IP-SM-GW获取 SC地址； 在本实施例中， 可以获取短消息发 送至接收端所属的 SC地址，也可以获取发送至发送端所属的 SC地址， 并存储 获取的地址；
若获取短消息发送至接收端所属的 SC地址时， 若 IP-SM-GW自身保存了 该接收端 UE所属的 SC地址， 则直接提取该 SC地址； 若 IP-SM-GW不知道接 收端 UE所属的 SC地址， IP-SM-GW从接收端 UE所属的 HSS获取接收端 UE所 属的 SC地址。 在本实施例中， IP-SM-GW向 HSS查询该接收端 UE所属的 SC 地址； 若 HSS也没有为接收端 UE配置 SC地址， 则 HSS根据接收端 UE的身份 信息（SIP URI、 IMSI )为该接收端 UE分配 SC地址；在本实施例中， IP-SM-GW 获取接收端所属的 SC地址后， 需要保存该 SC地址。
若获取发送至发送端所属的 SC地址时， IP-SM-GW从步骤 S20中收到的 短消息请求中提取发送端所属的 SC地址， 并保存该 SC地址。
步骤 S222: IP-SM-GW将该短消息发送失败的信息通知 HSS。 在本实施 例中， 在该通知消息中至少包括接收端身份（IMSI或 SIP URI ) 、 SC地址、 关联标识或 SMSCN , 还可以包括 IP-SM-GW的地址及发送失败原因， HSS接 收到通知后， 保存上述的信息在 WMD ( message waiting data )信息中。
步骤 S223: 根据该短消息请求提取短消息； 在本实施例中短消息中包括 短消息内容、 源地址及目的地址等信息， IP-SM-GW将提取的短消息中的源地 址及目的地址进行修改， 短消息内容不修改。
在本实施例中， I P-SM-G W将发送端的短消息中的源地址修改为 MT Correlation ID, 将目的地址修改为 SC地址， 短消息内容不修改； 或者将发送 端的短消息中的源地址修改为 SMSCN和 IP-SM-GW ID, 将目的地址修改为 SC地址，短消息内容不修改； 或者， 当 IP-SM-GW没有生成 MT Correlation ID 或 SMSCN时， IP-SM-GW可以根据接收端的 SIP URI , 向 HSS查找接收端的 签约信息， 找到接收端的 IMSI , 当然， 发送端也将自身电话号码形式的身份 信息在短消息中携带，如发送端的 IMSI , IP-SM-GW保存发送端的身份标识（如 IMSI ) 和接收端身份标识 （IMSI ) , IP-SM-GW将发送端的短消息中的源地 址修改为特殊前缀和发送端的 IMSI , 特殊前缀表示该短消息为发送失败的短 消息， 将将目的地址修改为被叫的 IMSI , 短消息内容不修改。
在本实施例中， 发送端发送的短消息具有不同的 RP ( Relay-Layer Protocol , 中继层协议） 格式， 第一种为 RP-M0-DATA , 第二种为 RP-MT-DATA。
当 IP-SM-GW需要将发送失败的短消息发送给 SC时， 会识别发送端的短 消息的格式， 当发送端的短消息的格式为第一种格式时， 该短消息的格式不 需要修改， 只需要修改其中的源地址和目的地址； 当发送端的短消息的格式 为第二种格式时， 将该格式转换成第一种格式， 再将其中的源地址和目的地 址进行爹改。
步骤 S224: IP-SM-GW将短消息发送至 SC进行存储， 并接收 SC存储后 的状态报告。在本实施例中， IP-SM-GW通过 SMS-IWMSC将该短消息发送给 SC, 并通过该 SMS-IWMSC接收 SC发送的存储该短消息的状态报告。 SC通 过识别 MT Correlation ID或 SMSCN或特殊前缀值判断出该条短消息为发送 失败的短消息， 只将其存储而不再继续发送。 SC存储收到的短消息， 并存储 了短消息与 MT Correlation ID或 SMSCN或接收端 IMSI。
步骤 23、 当 HSS获知接收端 UE的状态变为可用状态时， 触发 SC重新发 送与接收端相关的短消息。 在本实施例中， 当 UE开机进行 IMS注册后， 或内 存可用，或由不支持 SIP短消息变为支持 SIP短消息，或 UE可达等情况下， HSS 可以获知该接收端 UE由不可用状态变为可用状态。 在本实施例中， HSS可以 通过发送提示 SC ( alert service centre )消息的方式触发 SC重新发送短消息。 在本实施例中， HSS可以通过 SMS-IWMSC将 alert service centre消息发送给 SC。
在本实施例中， HSS可以在 alert service centre消息中携带 MT Correlation ID或 SMSCN或接收端 UE的 IMSI。 SC可以根据 alert service centre消息中携带 MT Correlation ID或 SMSCN或接收端 UE的 IMSI从存储的 短消息中获取与之对应的短消息， 即可以根据 MT Correlation ID找到与 MT Correlation ID或 SMSCN关联的短消息或根据目的地址为接收端 UE的 IMSI的 短消息。
步骤 24、 SC将存储的短消息发送至 IP-SM-GW。 在本实施例中， 该步骤 可以包括， 如图 2C所示。
步骤 S240: SC修改存储的短消息的源地址及目的地址。
在本实施例中， 针对存储的短消息中源地址为 MT Correlation ID的情况， SC将存储的短消息的源地址修改 SC地址， 目的地址修改为 MT Correlation ID , 短消息内容不修改； 或者， 针对存储的短消息中源地址为 SMSCN和 IP-SM-GW ID的情况， 将存储的短消息的源地址修改 SC地址， 目的地址修改 为 SMSCN和 IP-SM-GW ID, 短消息内容不修改； 或者， 针对存储的短消息中 源地址为特殊前缀和发送端 IMSI的情况下， 将存储的短消息的源地址修改为 主叫身份、 目的地址及短消息内容不修改。
步骤 S241 : SC将修改后的短消息发送至 SMS-GMSC;
步骤 S242: 该 SMS-GMSC通过向 HSS询问以获取路由信息， 即获取该接 收端所属的 IP-SM-GW地址， 并将其返回给 SMS-GMSC。 在本实施例中， SMS-GMSC可以根据 MT Correlation ID找到接收端所在的 HSS, HSS进一步 根据 MT Correlation ID找到对应的 IP-SM-GW的地址；或者通过发送端和接收 端的 IMSI找到对应的 IP-SM-GW的地址。
步骤 S242只在 SC发出短消息的目的地址是 MT Correlation ID或被叫 IMSI的情况才执行。
步骤 S243: SMS-GMSC将 SC发送的短消息发送至 IP-SM-GW。
步骤 S25、 IP-SM-GW根据 SC发送的短消息生成短消息请求， 并通过
S-CSCF发送至接收端 U E。
在本实施例中， IP-SM-GW根据该 SC发送的短消息中的源地址或目的地 址找到对应的发送端和接收端的 SIP URI , 从而生成短消息请求， 此处短消息 请求可以是 SIP请求消息。 在本实施例中， 可以根据 MT Correlation ID找到对 应的接收端 SIP URI或发送端和接收端的 SIP URI ,或者根据 SMSCN找到对应 的接收端 SIP URI或发送端和接收端的 SIP URI , 或者根据发送方和发送端的 IMSI找到对应的接收端 SIP URI和发送端的 SIP URI。
本发明提供的实施例，在 IMS域中， 当接收端由于不可用造成发送给该接 收端的短消息请求发送失败时， IP-SM-GW将该短消息请求对应的短消息发送 至 SC进行存储处理， 并当该接收端变为可用状态时， 重新发送短消息请求至 该接收端， 就可以实现重发发送失败的短消息请求，从而提高在 IMS发送短消 息请求的可用度， 并提高了用户的体验。
图 3A所示为本发明实施例二提供的一种实现短消息重发的方法的流程 图。
在本实施例中， 发送短消息的短消息请求不经过接收端网络的 IP-SM-GW。
步骤 S30、 S-CSCF接收发送侧发送的短消息请求； 在本实施例中， 该短 消息请求包括短消息内容、 接收端 UE信息。 当然， 还可以包括其它信息， 如 当短消息发送失败时的存储短消息的 SC地址信息，该 SC地址为发送端在发送 短消息时携带的发送端所属的 SC地址。 该短消息请求为 S I P请求消息。
步骤 S31、 S-CSCF确定该短消息是否成功发送至接收端 UE。在本实施例 中， S-CSCF可以根据自身保存的接收端 UE的注册信息或收到的响应消息等 信息来确定该短消息是否成功发送至接收端 UE。在本实施例中， 若接收端 UE 关机了， S-CSCF自身保存的接收端 UE的注册信息为下线或不在网的信息， 即， S-CSCF通过自身保存的接收端 UE的注册信息就可以确定接收端 UE是否 关机， 若确定接收端 UE为关机状态， 则无法将短消息成功发送至接收端 UE; 或接收端 UE的内存已满或不支持 SIP消息类型等情况下， 接收端 UE会返回失 败的响应消息或短消息失败报告的响应消息给 S-CSCF, 因而， S-CSCF可以 通过返回的响应消息判断该短消息没有成功发送至接收端 U E , 也可以认为该 短消息发送失败。
步骤 S32、 当确定该短消息请求无法成功发送至接收端 UE时， S-CSCF 获取接收端 UE所属的 IP-SM-GW地址。 在本实施例中， 若 S-CSCF自身保存 了接收端 UE所属的 IP-SM-GW地址， 则直接提取该 IP-SM-GW地址； 若 S-CSCF自身没有保存接收端 UE所属的 IP-SM-GW地址， 则向接收端 UE所属 的 HSS请求获取该 IP-SM-GW地址； 在本实施例中， 若 HSS也没有为接收端 UE配置 IP-SM-GW地址， 则 HSS根据接收端 UE的身份信息（SIP URI、 IMSI ) 为该接收端 U E分配 I P-SM-G W地址。
步骤 S33、 S-CSCF通知 IP-SM-GW该短消息发送失败。 在本实施例中， 该通知消息中携带短消息。
步骤 S34、 IP-SM-GW确定收到的短消息发送失败后， 提取短消息， 将该 短消息发送至 SC进行存储。 在本实施例中， 该 IP-SM-GW将该短消息发送至 SC进行存储的步骤还可以包括， 如图 3B所示。
步骤 S340: IP-SM-GW生成关联标识（ Mobile Terminated Correlation ID, MT Correlation ID )ilSMSCN( SMS-correlation number )关联值； IP-SM-GW 保存 MT Correlation ID或 SMSCN与短消息的接收端的 SIP URI形式的身份标 识。 当然， 可选的， IP-SM-GW也可以保存 MT Correlation ID或 SMSCN与短 消息的发送端及接收端的 SIP URI形式的身份标识。 其中， MT Correlation ID 格式为 MCC(3位) +MNC(3位) +send ID(9位)， MCC为国家码， MNC为运营商 码， Sender ID为终端随机生成的 9位数值， 该 9位数值应包含接收方 UE所在 的 HSS识别号， 以使得通过关联标识 （ MT Correlation ID ) 中的 sender ID能 够确定接收端所在的 HSS; SMSCN为为终端生成的 3位数值； 在本实施例中， IP-SM-GW为接收方终端生成关联标识 （ MT Correlation ID )或 SMSCN , 其 作用为使 UE可用后， SC通过 MT Correlation ID或 SMSCN匹配到对应短消 息， 将其重新发送， 及 IP-SM-GW根据 MT Correlation ID或 SMSCN匹配到该 条短消息发送端或接收端的 SIP URI的身份标识，进而生成携带短消息内容的 SIP请求消息， 将 SIP请求消息发送到接收端 UE。
步骤 S341 : IP-SM-GW获取 SC地址； 在本实施例中， 可以获取短消息 发送至接收端所属的 SC地址， 也可以获取发送至发送端所属的 SC地址， 并存 储获取的地址；
若获取短消息发送至接收端所属的 SC地址， 若 IP-SM-GW自身保存了该 接收端 UE所属的 SC地址， 则直接提取该 SC地址； 若 IP-SM-GW不知道接收 端 UE所属的 SC地址， IP-SM-GW从接收端 UE所属的 HSS获取接收端 UE所属 的 SC地址。 在本实施例中， IP-SM-GW向 HSS查询该接收端 UE所属的 SC地 址； 若 HSS也没有为接收端 UE配置 SC地址， 则 HSS根据接收端 UE的身份信 息（SIP URI、 IMSI )为该接收端 UE分配 SC地址； 在本实施例中， IP-SM-GW 获取接收端所属的 SC地址后， 需要保存该 SC地址
若获取发送至发送端所属的 SC地址时， IP-SM-GW从步骤 S20中收到的 短消息请求中提取发送端所属的 SC地址， 并保存该 SC地址。
步骤 S342: IP-SM-GW将该短消息发送失败的信息通知 HSS。 在本实施 例中， 在该通知消息中至少包括接收端身份（IMSI或 SIP URI ) 、 SC地址、 关联标识或 SMSCN , 还可以包括 IP-SM-GW的地址及发送失败原因， HSS接 收到通知后， 保存上述的信息在 WMD ( message waiting data )信息中。
步骤 S343: 根据该短消息请求提取短消息； 在本实施例中短消息中包括 短消息内容、 源地址及目的地址等信息， IP-SM-GW将提取的短消息中的源地 址及目的地址进行修改， 短消息内容不修改。 在本实施例中， I P-SM-G W将发送端的短消息中的源地址修改为 MT Correlation ID, 将目的地址修改为 SC地址， 短消息内容不修改； 或者将发送 端的短消息中的源地址修改为 SMSCN和 IP-SM-GW ID, 将目的地址修改为 SC地址，短消息内容不修改； 或者， 当 IP-SM-GW没有生成 MT Correlation ID 或 SMSCN时， IP-SM-GW可以根据接收端的 SIP URI , 向 HSS查找接收端的 签约信息， 找到接收端的 IMSI , 当然， 发送端也将自身电话号码形式的身份 信息在短消息中携带，如发送端的 IMSI , IP-SM-GW保存发送端的身份标识（如 IMSI ) 和接收端身份标识 （IMSI ) , IP-SM-GW将发送端的短消息中的源地 址修改为特殊前缀和发送端的 IMSI , 特殊前缀表示该短消息为发送失败的短 消息， 将将目的地址修改为被叫的 IMSI , 短消息内容不修改。
在本实施例中， 发送端发送的短消息具有不同的 RP ( Relay-Layer Protocol , 中继层协议） 格式， 第一种为 RP-M0-DATA , 第二种为 RP-MT-DATA。
当 IP-SM-GW需要将发送失败的短消息发送给 SC时， 会识别发送端的短 消息的格式， 当发送端的短消息的格式为第一种格式时， 该短消息的格式不 需要修改， 只需要修改其中的源地址和目的地址； 当发送端的短消息的格式 为第二种格式时， 将该格式转换成第一种格式， 再将其中的源地址和目的地 址进行爹改。
步骤 S344: IP-SM-GW将短消息发送至 SC进行存储， 并接收 SC存储后 的状态报告。在本实施例中， IP-SM-GW通过 SMS-IWMSC将该短消息发送给 SC, 并通过该 SMS-IWMSC接收 SC发送的存储该短消息的状态报告。 SC通 过识别 MT Correlation ID或 SMSCN或特殊前缀值判断出该条短消息为发送 失败的短消息， 只将其存储而不再继续发送。 SC存储收到的短消息， 并存储 了短消息与 MT Correlation ID或 SMSCN或接收端 IMSI的关联关系。
步骤 S35、 当 HSS获知接收端 UE的状态变为可用状态时， 触发 SC重新发 送与接收端相关的短消息。 在本实施例中， 当 UE开机进行 IMS注册后， 或内 存可用，或由不支持 SIP短消息变为支持 SIP短消息，或 UE可达等情况下， HSS 可以获知该接收端 UE由不可用状态变为可用状态。 在本实施例中， HSS可以 通过发送提示 SC ( alert service centre )消息的方式触发 SC重新发送短消息。 在本实施例中， 所述 HSS向所述业务中心发送提示业务中心消息， 所述提示 业务中心消息中携带关联标识或 SMSCN或接收端 UE的 IMSI , 业务中心收到 所述消息后，发送与所述关联标识关联的存储的短消息。在本实施例中， HSS 可以通过 SMS-IWMSC将 alert service centre消息发送给 SC。
在本实施例中， HSS可以在 alert service centre消息中携带 MT Correlation ID或 SMSCN或接收端 UE的 IMSI。 SC可以根据 alert service centre消息中携带 MT Correlation ID或 SMSCN或接收端 UE的 IMSI从存储的 短消息中获取与之对应的短消息， 即可以根据 MT Correlation ID找到与 MT Correlation ID或 SMSCN关联的短消息或根据目的地址为接收端 UE的 IMSI的 短消息。
步骤 35、 SC将存储的短消息发送至 IP-SM-GW。 在本实施例中， 该步骤 可以包括， 如图 3C所示：
步骤 S350: SC修改存储的短消息的源地址及目的地址。
在本实施例中， 针对存储的短消息中源地址为 MT Correlation ID的情况， SC将存储的短消息的源地址修改 SC地址， 目的地址修改为 MT Correlation ID , 短消息内容不修改； 或者， 针对存储的短消息中源地址为 SMSCN和 IP-SM-GW ID的情况， 将存储的短消息的源地址修改 SC地址， 目的地址修改 为 SMSCN和 IP-SM-GW ID, 短消息内容不修改； 或者， 针对存储的短消息中 源地址为特殊前缀和发送端 IMSI的情况下， 将存储的短消息的源地址修改为 主叫身份、 目的地址及短消息内容不修改。
步骤 S351 : SC将新的短消息发送至 SMS-GMSC;
步骤 S352: 该 SMS-GMSC通过向 HSS询问以获取路由信息， 即获取该接 收端所属的 IP-SM-GW地址， 并将其返回给 SMS-GMSC。 在本实施例中， SMS-GMSC可以根据 MT Correlation ID找到接收端所在的 HSS, HSS进一步 根据 MT Correlation ID找到对应的 IP-SM-GW的地址；或者通过发送端和接收 端的 IMSI找到对应的 IP-SM-GW的地址。
步骤 S352只在 SC发出短消息的目的地址是 MT Correlation ID或被叫 IMSI的情况才执行。
步骤 S353: SMS-GMSC将 SC发送的短消息发送至 IP-SM-GW。
步骤 36、 IP-SM-GW根据 SC发送的短消息生成短消息请求， 并通过 S-CSCF发送至接收端 U E。
在本实施例中， IP-SM-GW根据该 SC发送的短消息中的源地址或目的地 址找到对应的发送端和接收端的 SIP URI , 从而生成短消息请求， 此处短消息 请求可以是 SIP请求消息。 在本实施例中， 可以根据 MT Correlation ID找到对 应的接收端 SIP URI或发送端和接收端的 SIP URI ,或者根据 SMSCN找到对应 的接收端 SIP URI或发送端和接收端的 SIP URI , 或者根据发送方和发送端的 IMSI找到对应的接收端 SIP URI和发送端的 SIP URI。
本发明提供的实施例，在 IMS域中， 当接收端由于不可用造成发送给该接 收端的短消息请求发送失败时， IP-SM-GW将该短消息请求对应的短消息发送 至 SC进行存储处理， 并当该接收端变为可用状态时， 重新发送短消息请求至 该接收端， 就可以实现重发发送失败的短消息请求，从而提高在 IMS发送短消 息请求的可用度， 并提高了用户的体验。
图 4所示为本发明实施例三提供的一种实现短消息重发的方法的流程图。 在本实施例中， 发送短消息的短消息请求经过接收端网络的 IP-SM-GW。 在发送的过程中， 接收端由于异常的原因， 该短消息不能发送至接收端， 此 时， 可以将该短消息请求存储在 IP-SM-GW中， 当接收端消除异常后， 再触发 IP-SM-GW重发该短消息请求。
步骤 S40、 IP-SM-GW接收 S-CSCF转发的短消息请求。 在本实施例中， 该短消息请求包括短消息内容、 接收端 UE信息。 当然， 还可以包括发送方携 带的指示信息， 该指示信息用于指示若该短消息请求发送失败， 将短消息请 求进行本地存储， 网络实体根据指示将发送失败的短消息请求存储在接收端
UE所属的 IP-SM-GW。
步骤 S41、 IP-SM-GW确定该短消息是否成功发送至接收端 UE。 在本实 施例中， IP-SM-GW可以根据收到的响应消息来确定该短消息是否成功发送 至接收端 UE。 在本实施例中接收端 UE不可达， 或内存已满或不支持 SIP消息 类型时， 接收端 UE会返回失败的响应消息或短消息失败报告的响应消息给 IP-SM-GW, 因而， IP-SM-GW可以通过返回的响应消息判断该短消息没有成 功发送至接收端 UE, 可以认为该短消息发送失败。
步骤 S42、当确定该短消息请求无法成功发送至接收端 UE时， IP-SM-GW 存储该短消息请求， 并存储了该短消息请求对应的接收端 U E身份信息。
步骤 S43、 当 IP-SM-GW获知接收端 UE变为可用状态时， 通过 S-CSCF 发送存储的该短消息请求至接收端 UE。 在本实施例中， 当 UE开机进行 IMS注 册后， 或内存可用， 或由不支持 SIP短消息变为支持 SIP短消息或再次可达等 情况下， 在本实施例中， IP-SM-GW可以获知该接收端 UE由不可用状态变为 可用状态。
本发明提供的实施例，在 IMS域中， 当接收端由于不可用造成发送给该接 收端的短消息请求发送失败时， IP-SM-GW将该短消息请求进行存储处理， 并 当该接收端变为可用状态时， 重新发送短消息请求至该接收端， 就可以实现 重发发送失败的短消息请求，从而提高在 IMS发送短消息请求的可用度， 并提 高了用户的体验。
图 5 A所示为本发明实施例四提供的一种实现短消息重发的方法的流程 图。
在本实施例中，发送短消息的短消息请求不经过 IP-SM-GW。在发送的过 程中， 接收端由于异常的原因， 该短消息不能发送至接收端， 此时， 可以将 该短消息请求发送并存储在 IP-SM-GW中， 当接收端消除异常后， 再触发 IP-SM-GW重发该短消息请求。
步骤 S50、 S-CSCF接收发送侧发送的短消息请求； 在本实施例中， 该短 消息请求为 SIP请求消息， 该短消息请求包括短消息内容、 接收端 UE信息等 信息。 当然， 还可以包括发送方携带的指示信息， 该指示信息用于指示若该 短消息请求发送失败， 将短消息或短消息请求进行本地存储， 网络实体根据 指示将发送失败的短消息或短消息请求存储在接收端的 IP-SM-GW。
步骤 S51、 S-CSCF确定该短消息是否成功发送至接收端 UE。在本实施例 中， S-CSCF可以根据自身保存的接收端 UE的注册信息或收到的响应消息来 确定该短消息是否成功发送至接收端 UE。在本实施例中，若接收端 UE关机了， S-CSCF自身保存的接收端 UE的注册信息为下线或不在网的信息， 即， S-CSCF通过自身保存的接收端 UE的注册信息就可以确定接收端 UE是否关 机， 若确定接收端 UE为关机状态， 则无法将短消息成功发送至接收端 UE; 或 接收端 UE不可达， 或内存已满或不支持 SIP消息类型时， 接收端 UE会返回失 败的响应消息或短消息失败报告的响应消息给 S-CSCF, 因而， S-CSCF可以 通过返回的响应消息判断该短消息没有成功发送至接收端 U E , 也可以认为该 短消息发送失败。
步骤 S52、 当确定该短消息请求无法成功发送至接收端 UE时， S-CSCF 获取接收端 UE所属的 IP-SM-GW地址。 在本实施例中， 若 S-CSCF自身保存 了接收端 UE所属的 IP-SM-GW地址， 则直接提取该 IP-SM-GW地址； 若 S-CSCF自身没有保存接收端 UE所属的 IP-SM-GW地址， 则向接收端 UE所属 的 HSS请求获取该 IP-SM-GW地址； 在本实施例中， 若 HSS也没有为接收端 UE配置 IP-SM-GW地址， 则 HSS根据接收端 UE的身份信息（ SIP URI或 IMSI ) 为该接收端 U E分配 I P-SM-G W地址。
步骤 S53、 S-CSCF将发送失败的短消息请求发送至 IP-SM-GW进行存储。 在本实施例中， 当 IP-SM-GW确定收到发送失败的短消息请求， 将其存储后， 返回确认信息至 S-CSCF。 在该请求中可以携带指示信息，以指示 IP-SM-GW该请求为发送失败的短 消息请求， 令其存储该请求， 指示信息可以通过如下方式实现：
Content-Disposition头增加 failing SMS字段，表明该请求的消息体为失败 的短消息， 无需发送， 仅保存， 意为将该短消息对应的请求保存；
或 Subject头增加 save SMS request字段， 表明请求消息的目的是保存 该请求。
步骤 S54、 当获知接收端 UE变为可用状态时， 触发 IP-SM-GW重新发送 该短消息请求至接收端 UE。在本实施例中，可以通过三种不同的方式来实现。
第一种情况， 如图 5B所示：
步骤 S540、 当 S-CSCF确认短消息请求发送失败， 并接收到 IP-SM-GW 发送的确认信息后， S-CSCF存储该短消息请求发送失败的状态及信息。 在本 实施例中， 该信息可以包括接收端 UE的身份信息、 存储该短消息请求的 IP-SM-GW地址及该短消息请求发送失败的原因；
步骤 S541、 当 S-CSCF获知接收端 UE变为可用状态时， 如 UE开机进行 IMS注册后， 或内存可用， 或由不支持 SIP短消息变为支持 SIP短消息或再次 可达时， 触发 IP-SM-GW发送存储的短消息请求；
步骤 S542、 IP-SM-GW通过 S-CSCF将存储的短消息请求重新发送至接 收端 UE。
第二种情况， 如图 5C所示：
步骤 S543、 IP-SM-GW向 HSS订阅接收端 UE是否可用的状态信息； 步骤 S544、 当 HSS获知接收端 UE变为可用状态时， 如 UE开机进行 IMS 注册后， 或内存可用， 或由不支持 SIP短消息变为支持 SIP短消息或再次可达 时， 将该可用状态信息通知 IP-SM-GW;
步骤 S545、 IP-SM-GW将存储的短消息请求通过 S-CSCF,发送至接收端
UE。
第三种情况， 如图 5D所示： 步骤 S546、 IP-SM-GW将该短消息发送失败的消息通知 HSS。此时， HSS 在该短消息对应的等待数据 ( MWD, message waiting data ) 中增加如下记 录， 包括接收端 UE身份信息、 存储该短消息请求的 IP-SM-GW地址及该短消 息请求发送失败的原因；
步骤 S547、 当 HSS获知接收端 UE变为可用状态时， 如 UE开机进行 IMS 注册后， 或内存可用， 或由不支持 SIP短消息变为支持 SIP短消息或再次可达 时， 检查该接收端 UE的 MWD;
步骤 S548、 当确定该 MWD不为空时， 向指定的 IP-SM-GW发送提示业务 中心 （ alert service centre message ) 的提示消息；
步骤 S549、 IP-SM-GW将存储的短消息请求通过 S-CSCF,发送至接收端
UE。
本发明提供的实施例，在 IMS域中， 当接收端由于不可用造成发送给该接 收端的短消息请求发送失败时， IP-SM-GW将该短消息请求进行存储处理， 并 当该接收端变为可用状态时， 重新发送短消息请求至该接收端， 就可以实现 重发发送失败的短消息请求，从而提高在 IMS发送短消息请求的可用度， 并提 高了用户的体验。
图 6A 所示为本发明实施例五提供的一种实现短消息重发的方法的流程 图。
在本实施例中，发送短消息的短消息请求经过 IP-SM-GW, 当短消息发送 失败时由 IP-SM-GW处理发送失败的情况， 当在发送的过程中，接收端由于异 常的原因， 该短消息不能发送至接收端， 此时， 可以将该短消息请求存储在 SMS-AS中， 当接收端消除异常后， 再触发 SMS-AS重发该短消息。
步骤 S60、 IP-SM-GW接收 S-CSCF转发的短消息请求。 在本实施例中， 该短消息请求包括短消息内容、 接收端 UE等信息。 当然， 还可以包括指示信 息， 该指示信息用于指示若该短消息请求发送失败， 将短消息请求进行本地 存储， 网络实体根据指示将发送失败的短消息请求存储在接收端的 SMS-AS。 步骤 S61、 IP-SM-GW确定该短消息是否成功发送至接收端 UE。 在本实 施例中， IP-SM-GW可以根据收到的响应消息来确定该短消息是否成功发送至 接收端 UE。 在本实施例中若接收端 UE不可达， 或内存已满或不支持 SIP消息 类型时， 接收端 UE会返回失败的响应消息或短消息失败报告的响应消息给 IP-SM-GW, 因而， IP-SM-GW可以通过返回的响应消息判断该短消息没有成 功发送至接收端 UE, 可以认为该短消息发送失败。
步骤 S62、当确定该短消息请求无法成功发送至接收端 UE时， IP-SM-GW 将该短消息请求发送至 SMS-AS进行存储。 在本实施例中， 当 SMS-AS存储该 短消息请求后， 返回确认消息至 IP-SM-GW。
步骤 S63、 当获知接收端 UE变为可用状态时， 触发 SMS-AS重新发送该 短消息请求。 在本实施例中， 可以通过三种不同的方式来实现。
第一种情况， 如图 6B所示：
步骤 S630、 当 IP-SM-GW将发送失败的短消息请求发送至 SMS-AS后， IP-SM-GW存储该短消息请求发送失败的状态及信息。在本实施例中，该信息 可以包括接收端 UE的身份信息、 存储该短消息请求的 SMS-AS地址及该短消 息请求发送失败的原因；
步骤 S631、 当 IP-SM-GW获知接收端 UE变为可用状态时， 如 UE开机进 行 IMS注册后， 或内存可用， 或由不支持 SIP短消息变为支持 SIP短消息或再 次可达时， 通知 SMS-AS发送存储的该短消息请求；
步骤 S632、 SMS-AS将该短消息请求通过 S-CSCF , 重新发送至接收端
UE。
第二种情况， 如图 6C所示：
步骤 S633、 SMS-AS向 HSS订阅接收端 UE是否可用状态信息； 步骤 S634、 当 HSS获知接收端 UE变为可用状态时， 如 UE开机进行 IMS 注册后， 或内存可用， 或由不支持 SIP短消息变为支持 SIP短消息或再次可达 时， 将该可用状态信息通知 SMS-AS; 步骤 S635、SMS-AS将存储的该短消息请求通过 S-CSCF重新发送至接收 端 UE。
第三种情况， 如图 6D所示：
步骤 S636、 SMS-AS将该短消息请求发送失败的消息通知 HSS。 此时， HSS会记录该短消息对应的消息等待数据（ MWD, message waiting data ) , 该 MWD包括接收端 UE身份信息、存储该短消息请求的 SMS-AS地址及该短消 息请求发送失败的原因；
步骤 S637、 当 HSS获知接收端 UE处于可用状态时， 如 UE开机进行 IMS 注册后， 或内存可用， 或由不支持 SIP短消息变为支持 SIP短消息或再次可达 时， 检查该接收端 UE的 MWD;
步骤 S638、当确定该 MWD不为空时，向 SMS-AS发送提示业务中心（alert service centre message ) 的提示消息；
步骤 S639、 SMS-AS将存储的该短消息请求通过 S-CSCF发送至接收端
UE。
本发明提供的实施例，在 IMS域中， 当接收端由于不可用造成发送给该接 收端的短消息请求发送失败时， IP-SM-GW将该短消息请求发送至 SMS-AS进 行存储处理， 并当该接收端变为可用状态时， 重新发送短消息请求至该接收 端， 就可以实现重发发送失败的短消息请求，从而提高在 IMS发送短消息请求 的可用度， 并提高了用户的体验。
图 7A 所示为本发明实施例六提供的一种实现短消息重发的方法的流程 图。
在本实施例中， 发送短消息的短消息请求不经过 IP-SM-GW, 由 S-CSCF 来处理短消息发送失败的情况。 当在发送的过程中， 接收端由于异常的原因， 该短消息不能发送至接收端， 此时， 可以将该短消息请求存储在 SMS-AS中， 当接收端消除异常后， 再触发 SMS-AS重发该短消息。
步骤 S70、 S-CSCF接收发送侧发送的短消息请求； 在本实施例中， 该 短消息请求包括短消息内容、 接收端 UE信息。 该短消息请求为 SIP请求消 息。 当然， 还可以包括发送方携带的指示信息， 该指示信息用于指示若该短 消息请求发送失败， 将短消息请求进行本地存储， 网络实体根据指示将发送 失败的短消息请求存储在接收端的 SMS-AS。
步骤 S71、 S-CSCF确定该短消息是否成功发送至接收端 UE。在本实施例 中， S-CSCF可以根据自身保存的接收端 UE的注册信息或收到的响应消息来 确定该短消息是否成功发送至接收端 UE。在本实施例中，若接收端 UE关机了， S-CSCF自身保存的接收端 UE的注册信息为下线或不在网的信息， 即， S-CSCF通过自身保存的接收端 UE的注册信息就可以确定接收端 UE是否关 机， 若确定接收端 UE为关机状态， 则无法将短消息成功发送至接收端 UE; 或 接收端 UE的内存已满或不支持 SIP消息类型时， 接收端 UE会返回失败的响应 消息或短消息失败报告的响应消息给 S-CSCF, 因而， S-CSCF可以通过返回 的响应消息判断该短消息没有成功发送至接收端 UE, 也可以认为该短消息发 送失败。
步骤 S72、 S-CSCF将该短消息请求发送至 SMS-AS进行存储。 在实施例 中， 当 SMS-AS存储该发送失败的短消息请求后， 返回确认信息至 S-CSCF。
步骤 S73、 当获知接收端 UE处于可用状态时， 触发 SMS-AS重新发送该 短消息请求。 在本实施例中， 可以通过三种不同的方式来实现。
第一种情况， 如图 7B所示：
步骤 S730、 当 S-CSCF确认短消息请求发送失败，并接收到 SMS-AS发送 的确认信息后， S-CSCF存储该短消息请求发送失败的状态及信息。 在本实施 例中， 该信息可以包括接收端 UE的身份信息、 存储该短消息请求的 SMS-AS 地址及该短消息请求发送失败的原因；
步骤 S731、 当 S-CSCF获知接收端 UE变为可用状态时， 如 UE开机进行 IMS注册后， 或内存可用， 或由不支持 SIP短消息变为支持 SIP短消息或再次 可达时， 通知 SMS-AS发送存储的该短消息请求； 步骤 S732、 SMS-AS通过 S-CSCF发送该短消息请求至接收端 UE。
第二种情况， 如图 7C所示：
步骤 S733、 SMS-AS向 HSS订阅接收端 UE是否可用状态信息；
步骤 S734、 当 HSS获知接收端 UE变为可用状态时， 如 UE开机进行 IMS 注册后， 或内存可用， 或由不支持 SIP短消息变为支持 SIP短消息或再次可达 时， 将该可用状态信息通知 SMS-AS;
步骤 S735、 SMS-AS将存储的该短消息请求通过 S-CSCF,发送至接收端
UE。
第三种情况， 如图 7D所示：
步骤 S736、 SMS-AS将该短消息请求发送失败的消息通知 HSS。 此时， HSS会记录该短消息对应的消息等待数据（ MWD, message waiting data ) , 该 MWD包括接收端 UE身份信息、存储该短消息请求的 SMS-AS地址及该短消 息请求发送失败的原因；
步骤 S737、 当 HSS获知接收端 UE变为可用状态时， 如 UE开机进行 IMS 注册后， 或内存可用， 或由不支持 SIP短消息变为支持 SIP短消息或再次可达 时， 检查该接收端 UE的 MWD;
步骤 S738、当确定该 MWD不为空时，向 SMS-AS发送提示业务中心（alert service centre message ) 的提示消息；
步骤 S739、 SMS-AS将存储的该短消息请求通过 S-CSCF,重新发送至接 收端 UE。
本发明提供的实施例，在 IMS域中， 当接收端由于不可用造成发送给该接 收端的短消息请求发送失败时， S-CSCF将该短消息请求发送至 SMS-AS进行 存储处理， 并当该接收端变为可用状态时， 重新发送短消息请求至该接收端， 就可以实现重发发送失败的短消息请求，从而提高在 IMS发送短消息请求的可 用度， 并提高了用户的体验。
图 8所示为实施例七提供的一种实现短消息重发的装置的结构图。 在本实施例中， 该装置可以包括确定模块 80、 存储处理模块 82、 重发模 块 84。
在本实施例中，确定模块 80用于确定在 IMS域中发送至接收端的短消息 请求是否发送失败。
存储处理模块 82用于当确定模块 80确定该短消息请求发送失败时， 对 该短消息请求进行存储处理。 在本实施例中， 在 IMS域中， 当在发送的过程 中， 接收端由于异常的原因， 该短消息不能发送至接收端， 此时， 存储处理 模块 82可以将短消息请求对应的短消息发送至接收端的网络中的 SC进行存 储，也可以发送至该短消息对应的发送端所属的 SC进行存储，存储处理模块 82可以也可以将该短消息请求存储在 IP-SM-GW, 存储处理模块 82可以也 可以将该短消息请求存储在 SMS-AS中， 上述的方式不是唯一的实施方式， 为可选的。
重发模块 84用于当获知该短消息请求对应的接收端变为可用状态时，将 该存储处理的该短消息请求重新通过 IMS域发送至该接收端。
本发明实施例提供的装置， 可以内嵌在 IP-SM-GW或 S-CSCF。
本发明提供的实施例提供的装置， 在 IMS域中， 当接收端由于不可用造 成发送给该接收端的短消息请求发送失败时， 对该短消息请求进行存储处理， 并当该接收端变为可用状态时， 重新发送短消息请求至该接收端， 就可以实 现重发发送失败的短消息请求， 从而提高在 IMS发送短消息请求的可用度， 并提高了用户的体验。
以下进行分别详细描述。
图 9所示为实施例八提供的一种实现短消息重发的装置的结构图。 在本 实施例中， 图 8所示的装置内嵌于 IP-SM-GW。
在本实施例中， 该装置还包括接收模块 90, 用于接收 S-CSCF转发的发 送侧发送的短消息请求。 确定模块 80具体用于确定接收模块 90所接收的该 短消息是否成功发送至接收端 UE。 存储处理模块 82具体用于当确定模块 80确定该短消息请求发送失败时， 将该短消息请求对应的短消息发送至 SC进行存储。也可以理解为， 当确定模 块 80获知在 IMS域中发送至接收端的短消息发送失败时， 存储处理模块 82 将所述短消息发送到业务中心， 以使得所述业务中心存储所述短消息。
所述存储处理模块 82进一步用于生成关联标识或 SMSCN , 并保存所述 关联标识与所述发送失败的短消息的接收端的 SIP URI ( SIP Universal Resource Identifier, SIP形式的通用资源标志符）形式的身份标识， 或保存 所述关联标识与所述发送失败的短消息的发送端和接收端的 SIP URI形式的 身份标识。
所述存储处理模块 82进一步用于所述 IP-SM-GW获取所述业务中心的 地址， 并根据所述获取的地址将所述短消息发送至所述业务中心， 以使所述 业务中心存储所述短消息， 其中， 所述短消息中包含所述关联标识， 或者所 述短消息中包含所述 SMSCN及 IP-SM-GW的自身地址。
在本实施例中， 存储处理模块 82可以具体包括： 生成子模块 900、 获取 子模块 901、 通知子模块 902、 发送子模块 903。
在本实施例中 ,生成子模块 900用于 IP-SM-GW生成 MT Correlation ID 或 SMSCN。 获取子模块 901 用于获取 SC地址。 在本实施例中， 获取子模 块 901 可以获取短消息发送至接收端所属的 SC地址， 也可以获取发送至发 送端所属的 SC地址。 通知子模块 902用于将该短消息发送失败的信息通知 HSS。获取子模块 901还用于根据该短消息请求获取短消息。发送子模块 903 用于根据获取的 SC地址， 将获取的短消息发送至 SC进行存储。
重发模块 84用于当所述短消息对应的接收端变为可用状态时，接收所述 业务中心发送的所述存储的短消息， 并通过所述 IMS域发送至所述接收端。
在本实施例中， 当该短消息请求对应的接收端变为可用状态时， 重发模 块 84进一步根据 SC发送的短消息生成短消息请求，并通过 S-CSCF发送至 接收端 UE。 在本实施例中， 所述重发模块 84具体用于接收所述业务中心发 送的所述存储的短消息， 并使用关联标识或 SMSCN对应的 SIP URI形式的 身份信息生成 IMS域 SIP消息， 及发送至所述接收端， 其中， 所述 IMS域 SIP消息中包含所述接收的短消息。
在本实施例中，当 S-CSCF接收发送侧发送的短消息请求后，由 S-CSCF 发送给接收端 UE, 当 S-CSCF发送该短消息请求失败后，会发送失败通知消 息给 IP-SM-GW, 接收模块 90还可以接收 S-CSCF发送的失败通知消息。 确定模块 80还可以根据该失败通知确定发送至接收端 UE的短消息请求发送 失败。 此时， 存储处理模块 82将该短消息请求对应的短消息发送至 SC进行 存储。
本发明提供的实施例， 在 IMS域中， 当接收端由于不可用造成发送给该 接收端的短消息请求发送失败时， 对 IP-SM-GW该短消息请求对应的短消息 发送至 SC进行存储处理，并当该接收端变为可用状态时，重新发送短消息请 求至该接收端， 就可以实现重发发送失败的短消息请求， 从而提高在 IMS发 送短消息请求的可用度， 并提高了用户的体验。
图 10所示为实施例九提供的一种实现短消息重发的装置的结构图。在本 实施例中， 图 8所示的装置内嵌于 IP-SM-GW。
在本实施例中， 该装置还包括接收模块 100, 用于接收 S-CSCF转发的 发送侧发送的短消息请求。确定模块 80具体用于确定接收模块 100所接收的 该短消息是否成功发送至接收端 UE。
存储处理模块 82具体用于当确定模块 80确定该短消息请求发送失败时， 存储该短消息请求。在本实施例中，也可以理解为，当确定模块 80获知在 IMS 域中发送至接收端的短消息发送失败时，存储处理模块 82存储所述发送失败 的短消息对应的短消息请求。
在本实施例中， 当所述短消息对应的接收端变为可用状态时， 重发模块 84可以将所述存储处理的短消息通过所述 IMS域重新发送至所述接收端。
重发模块 84具体用于当确定模块 80确定该短消息请求对应的接收端变 为可用状态时，将该存储处理模块 82存储的短消息请求通过 S-CSCF发送至 接收端 UE。
在本实施例中， 所述接收模块 100进一步用于接收 S-CSCF发送的所述 接收端可用的信息， 或接收 HSS发送的所述接收端可用的通知消息。 ， 所述 确定模块 80进一步用于当所述接收模块 100接收 S-CSCF发送的所述接收 端可用的信息或接收 HSS发送的所述接收端可用的通知消息时， 确定所述短 消息请求对应的接收端变为可用状态。
在本实施例中，当 S-CSCF接收发送侧发送的短消息请求后，由 S-CSCF 发送给接收端 UE, 当 S-CSCF发送该短消息请求失败后，会发送失败通知消 息给 IP-SM-GW, 接收模块 100还可以接收 S-CSCF发送的失败通知消息。 确定模块 80还可以根据该失败通知确定发送至接收端 UE的短消息请求发送 失败。 此时， 存储处理模块 82存储该短消息请求。 同时， 当 S-CSCF确定该 短消息请求对应的接收端变为可用状态时， S-CSCF通知重发模块 84发送存 储的短消息请求至 S-CSCF, 并通过 S-CSCF发送至接收端 UE。
本发明提供的实施例， 在 IMS域中， 当接收端由于不可用造成发送给该 接收端的短消息请求发送失败时， IP-SM-GW将该短消息请求进行存储处理， 并当该接收端变为可用状态时， 重新发送短消息请求至该接收端， 就可以实 现重发发送失败的短消息请求， 从而提高在 IMS发送短消息请求的可用度， 并提高了用户的体验。
图 1 1所示为实施例九提供的一种实现短消息重发的装置的结构图。在本 实施例中， 图 8所示的装置内嵌于 IP-SM-GW。
在本实施例中， 该装置还包括接收模块 1 10, 用于接收 S-CSCF转发的 发送侧发送的短消息请求。确定模块 80具体用于确定接收模块 1 10所接收的 该短消息是否成功发送至接收端 UE。
存储处理模块 82具体用于当确定模块 80确定该短消息请求发送失败时， 将该短消息请求发送至 SMS-AS进行存储。 重发模块 84具体用于当该短消息请求对应的接收端变为可用状态时，触 发 SMS-AS重新发送该短消息请求。
本发明提供的实施例， 在 IMS域中， 当接收端由于不可用造成发送给该 接收端的短消息请求发送失败时， IP-SM-GW 将该短消息请求发送至 SMS-AS 进行存储处理， 并当该接收端变为可用状态时， 重新发送短消息请 求至该接收端， 就可以实现重发发送失败的短消息请求， 从而提高在 IMS发 送短消息请求的可用度， 并提高了用户的体验。
图 12所示为实施例九提供的一种实现短消息重发的装置的结构图。在本 实施例中， 图 8所示的装置内嵌于 S-CSCF。
在本实施例中， 该装置还包括接收模块 120, 用于接收发送侧发送的短 消息请求。确定模块 80具体用于确定接收模块 120所接收的该短消息是否成 功发送至接收端 UE。
存储处理模块 82具体用于当确定模块 80确定该短消息请求发送失败时， 将该短消息请求发送至 SMS-AS进行存储。
重发模块 84具体用于当该短消息请求对应的接收端变为可用状态时， 触 发 SMS-AS重新发送该短消息请求。
本发明提供的实施例，在 IMS域中， 当接收端由于不可用造成发送给该接 收端的短消息请求发送失败时， IP-SM-GW将该短消息请求发送至 SMS-AS进 行存储处理， 并当该接收端变为可用状态时， 重新发送短消息请求至该接收 端， 就可以实现重发发送失败的短消息请求，从而提高在 IMS发送短消息请求 的可用度， 并提高了用户的体验。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流 程， 是可以通过计算机程序来指令相关的硬件来完成， 所述的程序可存储于 一计算机可读取存储介质中， 该程序在执行时， 可包括如上述各方法的实施 例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体（ Read-Only Memory, ROM )或随机存储记忆体（ Random Access Memory, RAM )等。 以上所述， 仅为本发明的具体实施方式， 但本发明的保护范围并不局限 于此， 任何熟悉本技术领域的技术人员在本发明揭露的技术范围内， 可轻易 想到的变化或替换， 都应涵盖在本发明的保护范围之内。 因此， 本发明的保 护范围应该以权利要求的保护范围为准。

Claims

权 利 要求 书
1、 一种实现短消息重发的方法， 其特征在于， 包括：
当 IP短消息网关 （ Internet Protocol Short Message Gateway, IP-SM-GW ) 获知在 IP多媒体子系统 ( Internet Protocol Multimedia Subsystem, IMS )域中 发送至接收端的短消息发送失败时，所述 IP-SM-GW将所述短消息发送到业务中 心， 以使得所述业务中心存储所述短消息；
当所述短消息对应的接收端变为可用状态时，所述 IP-SM-GW接收所述业务 中心发送的所述存储的短消息， 并通过所述 IMS域重新发送至所述接收端。
2、 根据权利要求 1所述的方法， 其特征在于， 还包括：
所述 IP-SM-GW接收 S-CSCF ( Serving Call Session Control Function , 服 务会话控制功能实体）发送的会话初始协议（Session Initiation Protocol , SIP) 请求消息， 所述 SIP请求消息中包含所述发送失败的短消息。
3、 根据权利要求 1所述的方法， 其特征在于， 所述将所述短消息发送到业 务中心之前包括：
所述 IP短消息网关生成关联标识 ( Mobile Terminated Correlation ID, MT Correlation ID ) ；
保存所述关联标识与所述发送失败的短消息的接收端的 SIP URI ( SIP Universal Resource Identifier, SIP形式的通用资源标志符）形式的身份标识， 或保存所述关联标识与所述发送失败的短消息的发送端和接收端的 SIP URI形 式的身份标识。
4、 根据权利要求 1或 3所述的方法， 所述的将所述短消息发送到业务中心之 前的步骤包括：
所述 IP-SM-GW获取所述业务中心的地址。
5、 根据权利要求 4所述的方法， 所述 IP-SM-GW获取所述业务中心的地址 的步骤进一步包括： 所述 IP-SM-GW获取所述短消息对应的接收端所属的业务中心地址。
6、 根据权利要求 5所述的方法， 所述获取所述短消息对应的接收端所属的 业务中心地址进一步包括：
所述 IP-SM-GW通过查询自身存储的所述接收端所属的业务中心地址或查 询所述接收端所属的 HSS ( Home Subscriber Server, 家乡签约寄存器）存储 的所述接收端所属的业务中心地址来获取所述短消息对应的所述接收端所属的 业务中心地址。
7、 根据权利要求 4所述的方法， 所述获取所述业务中心的地址的步骤进一 步包括：
所述 IP-SM-GW获取所述短消息对应的发送端所属的业务中心地址。
8、 根据权利要求 7所述的方法， 所述获取所述短消息对应的发送端所属的 业务中心地址进一步包括：
所述 IP-SM-GW通过查询发送所述短消息的短消息请求中携带的业务中心 地址来获取所述短消息对应的发送端所属的业务中心地址。
9、 根据权利要求 3所述的方法， 其特征在于， 所述将所述短消息发送到业 务中心之前还包括：
所述 IP-SM-GW向 HSS发送短消息传输状态报告消息，所述短消息传输状态 报告消息中至少包含所述关联标识、 所述业务中心地址、 所述短消息接收端的 身份标识， 以使 HSS保存上述信息。
10、 根据权利要求 4所述的方法， 所述的将所述短消息发送到业务中心步骤 包括：
根据所述获取的业务中心地址将所述短消息发送至所述业务中心， 以使所 述业务中心存储所述短消息， 其中， 所述短消息中包含所述关联标识。
1 1、 根据权利要求 1或 3所述的方法， 其特征在于， 所述当所述短消息对应 的接收端变为可用状态时，所述 IP-SM-GW接收所述业务中心发送的所述存储的 短消息的步骤包括： 所述 HSS向所述业务中心发送提示业务中心消息， 所述提示业务中心消息 中携带关联标识；
业务中心收到所述消息后， 发送与所述关联标识关联的存储的短消息； 所述 IP-SM-GW接收所述存储的短消息；
其中， 所述发送的短消息中包含关联标识。
12、 根据权利要求 1 1所述的方法， 其特征在于， 所述发送与关联标识关联 的存储的短消息包括：
SMS-GMSC ( Gateway Mobile Switching Center For Short Message Service, 短消息业务的移动交换中心网关）接收所述发送的短消息， 根据所述 发送短消息中的关联标识向 HSS获取 IP-SM-GW地址信息；
所述 SMS-GMSC将所述短消息发送至所述 IP-SM-GW。
13、 根据权利要求 1或 1 1或 12所述的方法， 所述通过 IMS域发送至所述接收 端的步骤包括：
所述 IP-SM-GW接收所述发送的短消息，根据所述接收的短消息中的关联标 识对应的 SIP URI形式的身份信息生成 IMS域 SIP消息， 所述 IMS域 SIP消息中包 含所述接收的短消息；
发送至所述接收端。
14、 一种实现短消息重发的方法， 其特征在于， 包括：
当 IP-SM-GW获知在 IMS域中发送至接收端的短消息发送失败时， 所述 IP-SM-GW存储所述发送失败的短消息对应的短消息请求；
当所述短消息对应的接收端变为可用状态时，所述 IP-SM-GW将所述存储的 短消息请求通过所述 IMS域重新发送至所述接收端。
15、 根据权利要求 14所述的方法， 其特征在于， 还包括：
所述 IP-SM-GW接收 S-CSCF服务会话控制功能实体发送的 SIP消息， 所述 SIP消息中包含所述发送失败的短消息。
16、根据权力要求 14所述的方法， 其特征在于， 所述 SIP消息中包含短消息 发送失败的指示信息或存储请求指示信息。
17、 根据权利要求 14所述的方法， 其特征在于， 所述当所述短消息对应的 接收端变为可用状态的步骤包括：
IP-SM-GW获知所述短消息对应的接收端变为可用的状态。
18、 根据权利要求 17所述的方法， 所述 IP-SM-GW获知所述短消息对应的 接收端变为可用的状态的步骤包括：
所述 IP-SM-GW接收 S-CSCF发送的所述接收端可用的信息； 或
所述 IP-SM-GW向 HSS订阅所述接收端可用的信息， 当所述接收端可用时， IP-SM-GW接收 HSS发送的所述接收端可用的通知消息。
19、 根据权利要求 14所述的方法， 其特征在于， 所述当所述短消息对应的 接收端变为可用状态时，将所述存储处理的短消息通过 IMS域重新发送至所述接 收端包括：
所述 IP-SM-GW向 HSS发送所述短消息发送状态报告消息，所述短消息发送 状态报告消息指示所述短消息发送失败； 以使得当所述接收端可用时， IP-SM-GW接收 HSS发送的提示消息， 以将所述存储处理的短消息通过所述 IMS 域重新发送至所述接收端。
20、 一种实现短消息重发的装置， 其特征在于， 所述装置包括：
存储处理模块， 用于当获知在 IMS域中发送至接收端的短消息发送失败时， 将所述短消息发送到业务中心， 以使得所述业务中心存储所述短消息；
重发模块， 用于当所述短消息对应的接收端变为可用状态时， 接收所述业 务中心发送的所述存储的短消息， 并通过所述 IMS域重新发送至所述接收端。
21、 根据权利要求 20所述的装置， 其特征在于， 还包括：
确定模块， 用于在 IMS域中发送至接收端的短消息是否发送失败。
22、 根据权利要求 20所述的装置， 其特征在于， 还包括：
接收模块， 用于接收 S-CSCF发送的 SIP消息， 所述 SIP消息中包含所述发 送失败的短消息。
23、 根据权利要求 20所述的装置， 其特征在于， 所述存储处理模块进一步 用于生成关联标识， 并保存所述关联标识与所述发送失败的短消息的接收端的 SIP URI形式的身份标识， 或保存所述关联标识与所述发送失败的短消息的发送 端和接收端的 SIP URI形式的身份标识。
24、 根据权利要求 20所述的装置， 其特征在于， 所述存储处理模块进一步 用于获取所述业务中心的地址， 并根据所述获取的地址将所述短消息发送至所 述业务中心， 以使所述业务中心存储所述短消息， 其中， 所述短消息中包含所 述关联标识， 。
25、 根据权利要求 20所述的装置， 其特征在于， 所述重发模块进一步用于 接收所述业务中心发送的所述存储的短消息， 并使用关联标识对应的 SIP URI 形式的身份信息生成 IMS域 SIP消息， 及发送至所述接收端， 其中， 所述 IMS域 SIP消息中包含所述接收的短消息。
26、 一种实现短消息重发的装置， 其特征在于， 所述装置包括：
存储处理模块， 用于当获知在 IMS域中发送至接收端的短消息发送失败时， 存储所述发送失败的短消息对应的短消息请求；
重发模块， 用于当所述短消息对应的接收端变为可用状态时， 将所述存储 处理的短消息通过所述 IMS域重新发送至所述接收端。
27、 根据权利要求 26所述的装置， 其特征在于， 还包括：
确定模块， 用于在 IMS域中发送至接收端的短消息是否发送失败。
28、 根据权利要求 26所述的装置， 其特征在于， 还包括：
接收模块， 用于接收 S-CSCF发送的 SIP消息， 所述 SIP消息中包含所述发 送失败的短消息。
29、 根据权利要求 26所述的装置， 其特征在于， 所述接收模块进一步用于 接收 S-CSCF发送的所述接收端可用的信息，或接收 HSS发送的所述接收端可用 的通知消息。
30、 根据权利要求 29所述的装置， 其特征在于， 所述确定模块进一步用于 当所述接收模块接收 S-CSCF发送的所述接收端可用的信息或接收 HSS发送的 所述接收端可用的通知消息时， 确定所述短消息请求对应的接收端变为可用状 态。
PCT/CN2012/081871 2011-09-30 2012-09-25 一种实现短消息重发的方法和装置 WO2013044782A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP12834832.3A EP2713638B1 (en) 2011-09-30 2012-09-25 Method and device for re-sending short message
US14/145,418 US9769631B2 (en) 2011-09-30 2013-12-31 Method and apparatus for implementing resending of short message
US15/680,774 US10750330B2 (en) 2011-09-30 2017-08-18 Method and apparatus for implementing resending of short message

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110297790.0 2011-09-30
CN201110297790.0A CN103037328B (zh) 2011-09-30 2011-09-30 一种实现短消息重发的方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/145,418 Continuation US9769631B2 (en) 2011-09-30 2013-12-31 Method and apparatus for implementing resending of short message

Publications (1)

Publication Number Publication Date
WO2013044782A1 true WO2013044782A1 (zh) 2013-04-04

Family

ID=47994260

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/081871 WO2013044782A1 (zh) 2011-09-30 2012-09-25 一种实现短消息重发的方法和装置

Country Status (4)

Country Link
US (2) US9769631B2 (zh)
EP (1) EP2713638B1 (zh)
CN (2) CN103037328B (zh)
WO (1) WO2013044782A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3038032A4 (en) * 2013-08-22 2016-06-29 Zte Corp SERVICE MESSAGE TRANSMISSION METHOD AND DEVICE

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9253611B2 (en) * 2012-12-18 2016-02-02 Htc Corporation Method of handling a short message service re-delivery
CN106470152A (zh) * 2015-08-21 2017-03-01 中兴通讯股份有限公司 Ip短信网关及其实现路由的方法
ES2912279T3 (es) 2015-11-06 2022-05-25 Alcatel Lucent Soporte de entrega de mensajes cortos terminados en móvil para un equipo de usuario en DRX en modo inactivo
CN105827660B (zh) * 2016-05-31 2018-12-14 浪潮集团有限公司 一种ip-sm-gw应用与数据分离的服务器及实现方法
CN108810830A (zh) * 2017-04-27 2018-11-13 中兴通讯股份有限公司 一种短消息中心提醒方法及短信网关
CN107566997A (zh) * 2017-07-05 2018-01-09 宇龙计算机通信科技(深圳)有限公司 短消息传输方法、装置、用户终端及计算机可读存储介质
CN110856125A (zh) * 2018-08-20 2020-02-28 中国电信股份有限公司 短信重发方法、装置及融合短消息中心
US10880432B1 (en) * 2019-05-24 2020-12-29 Berryville Holdings, LLC Non-associative telephony and SMS messaging
CN114025315A (zh) * 2020-07-16 2022-02-08 中兴通讯股份有限公司 一种短信投递失败的处理方法、装置及系统
CN115396827B (zh) * 2021-05-24 2024-01-30 成都鼎桥通信技术有限公司 信息处理的方法、装置、设备、存储介质及程序产品
CN116261106A (zh) * 2021-12-10 2023-06-13 中国电信股份有限公司 终端主叫短信服务化实现方法和系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101529833A (zh) * 2006-10-24 2009-09-09 朗讯科技公司 供接收者稍后进行获取的数据消息的存储
CN101971584A (zh) * 2008-02-06 2011-02-09 高通股份有限公司 用于消息的递送确认的方法和设备
CN102027461A (zh) * 2008-07-04 2011-04-20 3Rd布兰德私人有限公司(公司注册号200719143G) 扩展的消息收发平台

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6108559A (en) * 1993-10-26 2000-08-22 Telefonaktiebolaget Lm Ericsson System and method for routing messages in radiocommunication systems
FI105873B (fi) * 1997-04-03 2000-10-13 Nokia Networks Oy Lyhytsanomien välitys pakettiradioverkossa
US7290041B2 (en) * 2000-08-28 2007-10-30 Chikka Pte Ltd Instant messaging system and method for remote networks using a sequential message handshaking protocol
KR100492959B1 (ko) * 2002-09-11 2005-06-07 삼성전자주식회사 공중 이동통신망과 연동되는 사설 무선망의 단문 메시지서비스 서버 및 방법
GB0406119D0 (en) * 2004-03-18 2004-04-21 Telsis Holdings Ltd Telecommunications services apparatus and method
US7715856B2 (en) * 2004-06-02 2010-05-11 Interdigital Technology Corporation Reporting terminal capabilities for supporting short message service
KR100824043B1 (ko) * 2005-04-08 2008-04-21 삼성전자주식회사 이동 통신 단말의 인스턴트 메시지 전송 방법 및 시스템
CN1859319A (zh) * 2005-10-13 2006-11-08 华为技术有限公司 多媒体消息的接收方法
EP1949616B1 (en) * 2005-11-14 2019-03-27 Mavenir Systems, Inc. Method for processing a message
CN101127731A (zh) * 2006-08-18 2008-02-20 华为技术有限公司 Ip多媒体业务子系统中传递短消息的方法、设备及系统
CN101090372B (zh) * 2006-08-28 2010-05-12 华为技术有限公司 一种短信路由控制系统及方法
EP2081348A4 (en) * 2006-11-15 2009-12-09 Huawei Tech Co Ltd MESSAGE INTERFUNCTION METHOD, SYSTEM, ENTITY AND METHOD OF MESSAGE DISTRIBUTION REPORT PROCESSING, SYSTEM, ENTITY, TERMINAL FOR MESSAGE INTERFUNCTION
US8254971B1 (en) * 2007-11-29 2012-08-28 At&T Mobility Ii Llc System and method for determining an SMS message retransmission schedule
US8655960B2 (en) * 2008-06-19 2014-02-18 Verizon Patent And Licensing Inc. Location-aware instant messaging
GB0902014D0 (en) * 2009-02-09 2009-03-11 Vodafone Plc SMS delivery technique
US8768388B2 (en) * 2009-04-09 2014-07-01 Alcatel Lucent Method and apparatus for UE reachability subscription/notification to facilitate improved message delivery
US8935413B2 (en) * 2010-10-26 2015-01-13 Alcatel Lucent Delivery report for text messages in SIP communications
WO2012082045A1 (en) * 2010-12-17 2012-06-21 Telefonaktiebolaget L M Ericsson (Publ) Method in a ue, a network node and a client node in a wireless communications network
US8848604B2 (en) * 2011-01-10 2014-09-30 Alcatel Lucent Application-originated text messages delivered over a packet-switched network
KR101830986B1 (ko) * 2011-06-30 2018-04-04 엘지전자 주식회사 메시지 전달 방법 및 장치

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101529833A (zh) * 2006-10-24 2009-09-09 朗讯科技公司 供接收者稍后进行获取的数据消息的存储
CN101971584A (zh) * 2008-02-06 2011-02-09 高通股份有限公司 用于消息的递送确认的方法和设备
CN102027461A (zh) * 2008-07-04 2011-04-20 3Rd布兰德私人有限公司(公司注册号200719143G) 扩展的消息收发平台

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2713638A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3038032A4 (en) * 2013-08-22 2016-06-29 Zte Corp SERVICE MESSAGE TRANSMISSION METHOD AND DEVICE

Also Published As

Publication number Publication date
US9769631B2 (en) 2017-09-19
CN108848471A (zh) 2018-11-20
CN103037328A (zh) 2013-04-10
US20170353843A1 (en) 2017-12-07
US10750330B2 (en) 2020-08-18
EP2713638B1 (en) 2016-05-04
EP2713638A1 (en) 2014-04-02
EP2713638A4 (en) 2014-11-26
US20140112257A1 (en) 2014-04-24
CN103037328B (zh) 2018-08-21
CN108848471B (zh) 2022-12-30

Similar Documents

Publication Publication Date Title
WO2013044782A1 (zh) 一种实现短消息重发的方法和装置
KR100946900B1 (ko) Ｉｍｓ 재등록 방법 및 이를 위한 시스템
TWI289984B (en) Method and system for handling service failures
US20100087215A1 (en) Method, system, and message service interworking module for implementing message service interworking
JP5666020B2 (ja) パケット交換ネットワークを介してアプリケーション発信テキスト・メッセージを配送するための方法および装置
JP2011259472A (ja) ショートメッセージサービスをサポートする、ターミナルのケーパビリティのレポーティング
WO2008094330A1 (en) Ims reliability mechanisms
EP2633657B1 (en) Delivery report for text messages in sip communications
EP1962521A1 (en) A method, system and apparatus for implementing video sharing service
US9210596B1 (en) Selective bearer re-initiation upon communication failure
US20190116140A1 (en) Method of notification of the unavailability of a terminal
WO2008138252A1 (fr) Procédé pour obtenir et transmettre une information de position d'un utilisateur et son dispositif de réseau
EP2007152B1 (en) Message route method, system and device based on ip transmission
CN105792147B (zh) 短信投递失败处理方法、装置及系统
US20130097331A1 (en) Submit Report Handling In SMSIP
US8868114B2 (en) Network entity for mobile communications
US7574203B2 (en) Method for retrieving and delivering multimedia messages using the session initiation protocol
JP5343551B2 (ja) 移動網システム及びガイダンスメッセージ提供方法
WO2006099812A1 (fr) Procédé de transmission de message
KR101467970B1 (ko) 패킷-스위치된 네트워크를 통해 ao 문자 메시지들을 전달하기 위한 방법 및 장치

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: 12834832

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2012834832

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE