Short message delivery method and device and computer readable storage medium

Abstract

The embodiment of the invention provides a short message delivery method, electronic equipment and a computer readable storage medium, and the method comprises the steps: determining whether to be offline and reactivate a target terminal according to a first strategy under the condition that a terminating short message for the target terminal fails to be delivered; and re-delivering the terminating short message through an IP multimedia subsystem IMS domain under the conditions that the terminal is offline, the target terminal is reactivated and the terminating short message is cached. Therefore, the delivery success rate of the terminating short message in the IMS domain can be improved.

Description

Technical Field

[0001] This document relates to the field of mobile communication technology, and in particular to a short message delivery method, device and computer-readable storage medium. Background Art

[0002] There are two forms of joint attachment of terminals to the network: 2G / 4G dual attachment and 4G / 5G dual attachment. When the terminal is jointly attached, the short message center will give priority to delivering short messages through the IP short message gateway (IP-Short-Message-Gateway, IPSMGW) in the 4G network. If the delivery fails, the IP short message gateway will try to deliver the short message through the 2G network.

[0003] When a 2G / 4G dual-attached terminal fails to deliver a message in the 4G (IP Multimedia Subsystem (IMS) domain), it can normally switch to the 2G (Circuit Switch (CS) domain) to continue delivery. Delivery in two different domains will increase core network signaling and increase the final call delivery delay. There may also be various anomalies such as terminal or network timeouts, resulting in delivery failure. In addition, with the development of 5G, operators are gradually withdrawing 2G from the network, and there is no longer 2G / 4G joint attachment for 4G users. At this time, if an abnormality occurs in the IMS domain of the 4G network, the 4G terminal will not be able to receive short messages when the short message delivery fails and cannot be restored. When the terminal is jointly attached to 4G / 5G, short messages only go through the 4G channel. When an abnormality occurs in the IMS domain in the 4G network, the 4G terminal will not be able to receive short messages.

[0004] It can be seen that the existing short message delivery methods based on the IMS domain either have a large delay or are prone to delivery failure, resulting in an unsatisfactory delivery success rate, and need to be improved. Summary of the invention

[0005] The embodiments of the present specification provide a short message delivery method, device and computer-readable storage medium, which are used to solve the problems of long delay and / or unsatisfactory delivery success rate of current short message delivery solutions.

[0006] To solve the above technical problems, the embodiments of this specification are implemented as follows:

[0007] In a first aspect, a short message delivery method is provided, which is applied to an IP short message gateway IPSMGW, and the method comprises:

[0008] In the case where the delivery of the terminated short message to the target terminal fails, determining whether to go offline and reactivate the target terminal according to the first strategy;

[0009] When the target terminal is offline and reactivated, and the terminated short message is cached, the terminated short message is re-delivered through the IP Multimedia Subsystem IMS domain.

[0010] In a second aspect, a short message delivery device is provided, which is applied to an IP short message gateway IPSMGW, and the device comprises:

[0011] A first determination module, configured to determine whether to go offline and reactivate the target terminal according to a first strategy when a terminated call short message to the target terminal fails to be delivered;

[0012] The re-delivery module is used to re-deliver the terminated short message through the IP Multimedia Subsystem IMS domain when the target terminal is offline and reactivated and the terminated short message is cached.

[0013] According to a third aspect, an electronic device is provided, including:

[0014] processor;

[0015] a memory for storing instructions executable by the processor;

[0016] The processor is configured to execute the instructions to implement the method as described in the first aspect.

[0017] According to a fourth aspect, a computer-readable storage medium is provided. When instructions in the storage medium are executed by a processor of an electronic device, the electronic device can execute the method described in the first aspect.

[0018] In the embodiments of the present specification, when the delivery of the terminated short message to the target terminal fails, the target terminal can be taken offline and reactivated according to the policy, and the terminated short message can be redelivered through the IMS domain after the target terminal is reactivated. Therefore, the success rate of IMS domain short message delivery can be improved, and because the delivery is redelivered in the IMS domain instead of being transferred to the CS domain, the delivery delay can also be reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0020] Figure 1 The present invention relates to a process for delivering a terminated call short message for a 2G / 4G dual-attached terminal when an IMS domain is abnormal in the related art.

[0021] Figure 2 This is a process for delivering terminated call short messages for 4G / 5G dual-attached terminals when an IMS domain is abnormal in the related art.

[0022] Figure 3 It is a process for delivering terminated call short messages in the related art for a 4G terminal that has exited a 2G / 3G network when an IMS domain exception occurs.

[0023] Figure 4 It is a flowchart of a short message delivery method provided by an embodiment of this specification.

[0024] Figure 5 It is a schematic diagram of an implementation structure of a short message delivery method provided in an embodiment of this specification.

[0025] Figure 6 It is a flow chart of applying a short message delivery method provided in an embodiment of this specification to a first scenario for delivering a terminated short message, wherein the first scenario is a scenario in which an abnormal response of the SIP layer in the IMS domain of a 4G / 5G terminal causes failure in delivery of the terminated short message.

[0026] Figure 7 It is a detailed flow chart of applying a short message delivery method provided in an embodiment of this specification to deliver a terminated short message for the first scenario.

[0027] Figure 8 It is a schematic diagram of a process of triggering terminal offline reactivation in a short message delivery method provided in an embodiment of this specification.

[0028] Fig. 9 It is a schematic diagram of a terminal offline reactivation process in a short message delivery method provided in an embodiment of this specification.

[0029] Fig.10 It is a flow chart of applying a short message delivery method provided in an embodiment of this specification to deliver a terminated short message for a second scenario, wherein the second scenario is a scenario in which an abnormal response of the RP layer in the IMS domain of a 4G / 5G terminal causes failure in delivery of the terminated short message.

[0030] Fig.11 It is a schematic diagram of the terminated short message delivery process after applying a short message delivery method provided by an embodiment of this specification to the first scenario or the second scenario.

[0031] Fig.12 It is a schematic diagram of the structure of an electronic device according to an embodiment of the present specification.

[0032] Fig.13 It is a structural diagram of a short message delivery device according to an embodiment of the present specification. DETAILED DESCRIPTION

[0033] In order to enable those skilled in the art to better understand the technical solutions in the embodiments of this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this document.

[0034] The terms "first", "second", etc. in this specification and claims are used to distinguish similar objects, and are not used to describe a particular order or precedence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of this specification can be implemented in an order other than those illustrated or described herein. In addition, "and / or" in this specification and claims means at least one of the connected objects, and the character " / " generally means that the objects associated with each other are in an "or" relationship.

[0035] The terms used in the embodiments of this specification include:

[0036] IP Short Message Gateway (IP-Short-Message-Gateway, IPSMGW);

[0037] Short Message Service Center (SMSC);

[0038] Service-Call Session Control Function (SCSCF);

[0039] Mobile Switching Center (MSC);

[0040] Home Subscriber Server (HSS);

[0041] Mobile Management Entity (MME);

[0042] Circuit Switch (CS) domain;

[0043] IP Multimedia Subsystem domain (IP Multimedia Subsystem, IMS domain).

[0044] In order to more clearly understand the problem to be solved by the short message delivery method provided in this specification, the following first describes how the related technology processes the terminated short message when the IMS domain is abnormal.

[0045] For 2G / 4G dual-attached terminals, the related technology provides the following process for delivering terminated short messages when the IMS domain is abnormal: Figure 1 As shown, the process includes:

[0046] Step 101: SMSC sends a terminating short message sending request (MTFWD) to IPSMGW.

[0047] The terminated call short message is generally a terminated call text message.

[0048] Step 102: IPSMGW delivers a terminated short message to SCSCF in the IMS domain.

[0049] After step 102, there are two possibilities:

[0050] ALT1: SIP layer delivery failed

[0051] Step 103, SCSCF returns a response result of SIP layer delivery failure and a corresponding failure code to IPSMGW;

[0052] Step 104, IPSMGW transfers to the CS domain to deliver the terminated short message;

[0053] Step 108: IPSMGW returns a terminated SMS delivery confirmation message (MTFWDACK) to the SMSC.

[0054] ALT2: Delivery at the SIP layer succeeds, but delivery at the RP layer fails

[0055] Step 105, SCSCF returns a message to IPSMGW indicating that the SIP layer delivery is successful;

[0056] Step 106, SCSCF returns the RP layer delivery failure to IPSMGW;

[0057] Step 107, IPSMGW transfers to the CS domain to deliver the terminated short message;

[0058] Step 108: IPSMGW returns a terminated SMS delivery confirmation message (MTFWDACK) to the SMSC.

[0059] for Figure 1In the delivery process of terminated short messages shown in the figure, the IMS domain cannot automatically recover in some failure code scenarios, and the short message delivery in the IMS domain will always fail for the user equipment (UE); then, IPSMGW switches to the CS domain for delivery. However, the delivery delay in the CS domain is relatively large, which may cause the front-end network element to time out and retry, resulting in problems such as sending multiple messages at once.

[0060] For 4G / 5G dual-attached terminals, the related technology has the following process for delivering terminated short messages when the IMS domain is abnormal: Figure 2 As shown, the process includes:

[0061] Step 201: SMSC sends a terminating short message sending request (MTFWD) to IPSMGW.

[0062] Step 202: IPSMGW delivers a terminated short message to SCSCF in the IMS domain.

[0063] After step 202, there are two possibilities:

[0064] ALT1: SIP layer delivery failed

[0065] Step 203, SCSCF returns a response result of SIP layer delivery failure and a corresponding failure code to IPSMGW;

[0066] Step 204: IPSMGW fails to transfer the CS domain to deliver the terminated short message.

[0067] Since the 4G / 5G dual-attached terminal cannot transfer to the CS domain, the delivery of the terminated short message fails, and then the process proceeds to step 208 to return a confirmation message of the failure of the delivery of the terminated short message to the SMSC.

[0068] Step 208: IPSMGW returns a terminated SMS delivery confirmation message (MTFWDACK) to the SMSC.

[0069] ALT2: Delivery at the SIP layer succeeds, but delivery at the RP layer fails

[0070] Step 205: SCSCF returns a message indicating that the SIP layer delivery is successful to IPSMGW.

[0071] Step 206, SCSCF returns the RP layer delivery failure to IPSMGW;

[0072] Step 207: IPSMGW fails to transfer the CS domain to deliver the terminated short message.

[0073] Since the 4G / 5G dual-attached terminal cannot transfer to the CS domain, the delivery of the terminated short message fails, and then the process proceeds to step 208 to return a confirmation message of the failure of the delivery of the terminated short message to the SMSC.

[0074] Step 208: IPSMGW returns a terminated SMS delivery confirmation message (MTFWDACK) to the SMSC.

[0075] for Figure 2 In the terminated call short message delivery process shown in the figure, since the IMS domain cannot automatically recover in some failure code scenarios for 5G users, the user terminal will always fail to deliver in the IMS domain. At the same time, IPSMGW cannot transfer delivery to the CS domain for 5G user terminals, resulting in the 5G terminals being unable to receive short messages and a low success rate of short message delivery.

[0076] For 4G terminals exiting the 2G / 3G network, the related technology has the following process for delivering terminated short messages when the IMS domain is abnormal: Figure 3 As shown, the process includes:

[0077] Step 301: SMSC sends a terminating short message sending request (MTFWD) to IPSMGW.

[0078] Step 302: IPSMGW delivers a terminated short message to SCSCF in the IMS domain.

[0079] After step 302, there are two possibilities:

[0080] ALT1: SIP layer delivery failed

[0081] Step 303, SCSCF returns a response result of SIP layer delivery failure and a corresponding failure code to IPSMGW;

[0082] Step 304: IPSMGW fails to transfer the CS domain to deliver the terminated short message.

[0083] Since the 4G terminal exiting the 2G / 3G network cannot transfer to the CS domain, the delivery of the terminated short message fails, and then the process proceeds to step 308 to return a confirmation message of the failure of the delivery of the terminated short message to the SMSC.

[0084] Step 308: IPSMGW returns a terminated SMS delivery confirmation message (MTFWDACK) to the SMSC.

[0085] ALT2: Delivery at the SIP layer succeeds, but delivery at the RP layer fails

[0086] Step 305: SCSCF returns a message indicating that the SIP layer delivery is successful to IPSMGW.

[0087] Step 306, SCSCF returns the RP layer delivery failure to IPSMGW;

[0088] Step 307: IPSMGW fails to transfer the CS domain to deliver the terminated short message.

[0089] Since the 4G terminal exiting the 2G / 3G network cannot transfer to the CS domain, the delivery of the terminated short message fails, and then the process proceeds to step 308 to return a confirmation message of the failure of the delivery of the terminated short message to the SMSC.

[0090] Step 308: IPSMGW returns a terminated SMS delivery confirmation message (MTFWDACK) to the SMSC.

[0091] for Figure 3 As shown in the terminated call short message delivery process, since the IMS domain cannot automatically recover in some failure code scenarios for 4G users, the user terminal will always fail to deliver in the IMS domain. At the same time, IPSMGW cannot switch to CS domain delivery for user terminals that have exited the 2G / 3G network, resulting in the 4G terminal being unable to receive short messages and a low short message delivery success rate.

[0092] In order to solve the problem of unsatisfactory delivery success rate and / or long delay of the short message delivery solution in the above-mentioned related art, this specification proposes a short message delivery method, which can be applied to IPSMGW.

[0093] Figure 4 A short message delivery method according to an embodiment of the present specification is shown. The method can be applied to IPSMGW. The method may include the following steps:

[0094] Step 401: When a terminated short message to a target terminal fails to be delivered, determine whether to log off and reactivate the target terminal according to a first strategy.

[0095] The target terminal can be any user terminal that receives the terminated call short message via IPSMGW.

[0096] After receiving the terminated short message from the short message service center SMSC, the IPSMGW delivers the terminated short message to the target terminal through the IMS domain, and receives a delivery response to the terminated short message.

[0097] Optionally, IPSMGW may also update the delivery status of the terminated call message according to the delivery response, wherein the delivery status includes delivery failure or delivery success.

[0098] Optionally, when IPSMGW determines that the terminated call short message is delivered successfully, it may detect whether the terminated call short message is cached, and if so, delete the cached terminated call short message.

[0099] Optionally, IPSMGW may also update the number of consecutive delivery failures of the terminated short message according to the historical delivery status of the terminated short message.

[0100] Specifically, after receiving the delivery response, IPSMGW will determine whether the delivery is successful based on the delivery response. If successful, the delivery status of the terminated short message is updated to successful delivery. Furthermore, it can also detect whether the terminated short message is cached. If cached, the cached terminated short message is deleted; if it is determined that the delivery fails, the terminated short message that fails to be delivered in the IMS domain is processed based on a pre-established processing strategy, and the delivery status of the terminated short message is updated to failure.

[0101] Optionally, in IPSMGW, the delivery status of the terminated short message and the number of consecutive delivery failures may be recorded according to the IP Multimedia Public Identity (IMPU) of the target terminal.

[0102] The delivery response generally includes a response code and a response type. The response code is a pre-agreed status code for different response results; the response type generally includes two types: internal error (link abnormality) or external error (terminal itself / SIP layer abnormality / RP layer abnormality).

[0103] As an example, step 401 may include: determining whether to log off and reactivate the target terminal according to the delivery response and the first policy (IMS domain delivery exception handling policy).

[0104] The first strategy may include but is not limited to at least one of the following:

[0105] 1) If the delivery response includes a response result of a SIP layer response timeout, then log off and reactivate the terminal;

[0106] 2) If the delivery response includes a response result that the SIP layer is unreachable, then log off and reactivate the terminal;

[0107] 3) If the delivery response includes a response result of RP layer response timeout, log off and reactivate the terminal;

[0108] 4) If the delivery response includes a response result that cannot be received due to the terminal's own reasons, the terminal is offline and reactivated or the terminal is not offline, wherein the own reasons include but are not limited to at least one of memory full and decoding failure.

[0109] In the specific implementation, a policy table can be prepared in advance, in which the corresponding relationship between the response code, response type and IMS domain delivery exception handling policy is listed. In this way, IPSMGW can query the policy table to determine the specific IMS domain delivery exception handling policy after receiving the delivery response of the terminal short message.

[0110] In addition, when the delivery of the terminated short message to the target terminal fails, when to determine whether to go offline and reactivate the target terminal according to the first strategy can be divided into but not limited to the following three situations:

[0111] 1) When the delivery of the terminated short message to the target terminal fails, immediately determine whether to log off and reactivate the target terminal according to the first strategy.

[0112] 2) when the delivery of the terminated short message to the target terminal fails and the number of consecutive delivery failures of the terminated short message reaches a first threshold, determining whether to go offline and reactivate the target terminal according to a first strategy;

[0113] As described above, when the delivery status of the terminated short message is stored according to the IMPU, the historical delivery status of the terminated short message can be queried according to the IMPU, and the number of consecutive delivery failures can be determined accordingly.

[0114] 3) When the delivery of the terminated short message to the target terminal fails and the short message delivery success rate of the target terminal is less than or equal to the second threshold, determining whether to go offline and reactivate the target terminal according to the first strategy.

[0115] As mentioned above, when the delivery status of the terminated short message is stored according to the IMPU, the historical delivery status of the terminated short message can be queried according to the IMPU, and the short message delivery success rate of the target terminal within the specified time can be calculated accordingly. Generally speaking, the specified time is the validity period of the registration of the target terminal, and of course it can also be a period of time closest to the current time.

[0116] If it is determined in step 401 to log off and reactivate the target terminal, then the log off and reactivate the target terminal may include the following two methods.

[0117] The first method: Downline reactivation led by SCSCF

[0118] The offline and reactivation of the target terminal includes: sending a message to S-CSCF to trigger the offline of the target terminal, the S-CSCF is used to notify the HSS to reactivate the target terminal after receiving the message, and the HSS is used to MME to send a recovery indication, and the recovery indication is used to indicate the reactivation of the target terminal.

[0119] The second method: offline reactivation led by HSS

[0120] The offline and reactivating the target terminal includes: sending a notification of reactivating the target terminal to the HSS, wherein the HSS is used to send a recovery indication to the MME, and the recovery indication is used to instruct the reactivation of the target terminal.

[0121] Optionally, when the target terminal is offline and reactivated, it may be determined whether to cache the terminated short message according to a second strategy.

[0122] The second strategy may include but is not limited to:

[0123] 1) Do not cache the terminated short message, and process the terminated short message according to the delivery failure processing method in the related art

[0124] 2) caching the terminated short message;

[0125] 3) not caching the terminated short message, but processing the terminated short message according to a delivery failure processing method in the related art; if the terminated short message is successfully delivered according to the delivery failure processing method, not caching the terminated short message; if the delivery of the terminated short message fails according to the delivery failure processing method, caching the terminated short message.

[0126] Among them, the delivery failure processing method in the related technology includes: transferring the delivery to the CS domain according to conditions or terminating the process to return a specific error code to the SMSC to trigger the SMSC to retry according to the policy.

[0127] Optionally, if it is determined to cache the terminated short message, a specific error code is returned to the short message service center SMSC, and the specific error code is used to instruct the SMSC not to trigger redelivery of the terminated short message, so as to avoid the SMSC redeliving the terminated short message, thereby avoiding wasting network resources and avoiding problems such as sending to multiple recipients.

[0128] Step 402: when the target terminal is offline and reactivated, and the terminated short message is cached, the terminated short message is re-delivered through the IP Multimedia Subsystem IMS domain.

[0129] Exemplarily, step 402 may include: when a trigger condition is met, determining whether the terminated short message is cached; and if it is determined that the terminated short message is cached, re-delivering the terminated short message through the IMS domain.

[0130] The triggering conditions include but are not limited to at least one of the following:

[0131] 1) receiving reactivation information of the target terminal;

[0132] 2) Satisfy the redelivery strategy.

[0133] Optionally, if the number of delivery times of the terminated call short message exceeds a certain threshold, the terminated call short message is no longer re-delivered, but the cached terminated call short message is deleted.

[0134] Optionally, when it is determined that the terminated short message is delivered successfully, the delivery status of the terminated short message is updated to delivery success according to the delivery response.

[0135] Optionally, when it is determined that the terminated short message is delivered successfully, the cached terminated short message is deleted to avoid occupying storage resources of IPSMGW.

[0136] A short message delivery method provided in an embodiment of the present specification can, when the delivery of a terminated short message to a target terminal fails, log off and reactivate the target terminal according to a policy, and redeliver the terminated short message through the IMS domain after reactivating the target terminal, thereby improving the success rate of short message delivery in the IMS domain, and since the delivery is redelivered in the IMS domain instead of being transferred to the CS domain for delivery, the delivery delay can also be reduced.

[0137] Figure 5 FIG. 1 is a schematic diagram showing an implementation structure of a short message delivery method provided in an embodiment of this specification. Figure 5 As shown, a service processing module 501, a policy decision module 502 and an offline reactivation processing module 503 may be provided in the IPSMGW.

[0138] The business processing module 501 is used to complete the codec adaptation with the MAP protocol, DIAMETER, SIP protocol, etc., to achieve intercommunication with external network elements; store the IMS delivery status corresponding to the IMPU; decide the subsequent terminated short message processing flow according to the IMS delivery response, i.e., the preset policy table; in the case of IMS domain delivery failure, trigger the offline reactivation processing module and the cached message re-delivery process according to the policy.

[0139] The policy decision module 502 is used to perform signaling selection in the IMS domain.

[0140] The offline reactivation processing module 503 is used to trigger the offline reactivation of the user terminal according to the policy, cache the short message according to the policy and process the terminated short message to be redelivered according to the policy.

[0141] The relationship between the above three modules is as follows:

[0142] After receiving the 4G / 5G short message, the service processing module 501 delivers the short message in the IMS domain. When receiving the delivery response, the policy decision module 502 is triggered according to the response code, response type and preset policy table. The policy decision module 502 triggers the offline reactivation processing module 503 according to the decision result, and caches the delivery status of the short message according to the IMPU according to the policy.

[0143] The following will introduce the functions implemented by the above three modules with specific examples. Here we will only give a brief description.

[0144] Figure 6 A flow chart of applying a short message delivery method provided in an embodiment of this specification to a first scenario for delivering a terminated short message is shown, wherein the first scenario is a scenario in which an abnormal response of the SIP layer in the IMS domain of a 4G / 5G terminal causes failure in delivery of the terminated short message.

[0145] like Figure 6 As shown, applying a short message delivery method provided in an embodiment of this specification, the delivery process of the terminated short message in the first scenario may include:

[0146] Step 601, SMSC sends a terminated short message sending request (IMTFWDREQ) to IPSMGW.

[0147] Step 602: IPSMGW delivers a terminated short message (IMS MT MESSAGE) to SCSCF in the IMS domain.

[0148] Step 603: SCSCF returns a response result of SIP layer delivery failure and a corresponding failure code / RP layer error message to IPSMGW.

[0149] Step 604: IPSMGW processes the failed delivery terminated short message according to the policy.

[0150] Specifically, IPSMGW can determine whether to go offline and reactivate the target terminal according to the first strategy. If yes, it continues to process in one of the following two ways:

[0151] ALT1: Terminal offline strategy led by SCSCF

[0152] Step 605, IPSMGW sends a terminal offline reactivation message (a message that triggers the target terminal to go offline) to SCSCF;

[0153] Step 606, SCSCF notifies HSS to reactivate the target terminal;

[0154] Step 607, the HSS sends a recovery indication to the MME, where the recovery indication is used to instruct the reactivation of the target terminal;

[0155] Step 608: HSS returns a terminal offline reactivation response to IPSMGW.

[0156] ALT2: Terminal offline strategy led by HSS

[0157] Step 609, IPSMGW notifies HSS to reactivate the target terminal;

[0158] Step 610, the HSS sends a recovery indication to the MME, where the recovery indication is used to instruct to reactivate the target terminal;

[0159] Step 611: HSS returns a terminal offline reactivation response to IPSMGW.

[0160] Step 612: Process the terminated short message that fails to be delivered according to the policy.

[0161] Specifically, when the trigger condition is met, it is determined whether the terminated short message is cached; if it is determined that the terminated short message is cached, the terminated short message is re-delivered through the IMS domain.

[0162] The trigger condition includes at least one of the following:

[0163] receiving reactivation information of the target terminal;

[0164] Satisfy the redelivery policy.

[0165] Step 613: IPSMGW feeds back a response to the SCSCF indicating successful delivery of the terminated short message.

[0166] Step 614: IPSMGW returns the terminated short message delivery confirmation information to SMSC.

[0167] from Figure 6 It can be seen that for the first scenario (the scenario where the abnormal response of the SIP layer in the IMS domain of the 4G / 5G terminal leads to the failure of the delivery of the terminated short message), after applying a short message delivery method provided in an embodiment of this specification, the delivery success rate of the terminated short message can be improved and the delivery delay of the terminated short message can be reduced by re-delivering in the IMS domain.

[0168] Figure 7 This is a detailed flow chart of applying a short message delivery method provided in the embodiment of this specification to deliver a terminated short message for the first scenario. Figure 7 As shown, the process may include:

[0169] Step 701, SMSC sends a terminating short message sending request (MTFWD) to the service processing module 501 in IPSMGW.

[0170] The terminated call short message is generally a terminated call text message.

[0171] Step 702: The service processing module 501 delivers a terminated short message to the SCSCF.

[0172] Step 703: SCSCF transmits the terminated call short message in the core network.

[0173] Step 704: The core network delivers a terminated short message to the UE via the IMS domain.

[0174] Step 705 , the SCSCF returns a response result of the SIP layer delivery failure and a corresponding failure code / RP layer error message to the service processing module 501 .

[0175] Step 706: the business processing module 501 determines the delivery status.

[0176] If the delivery status is that the SIP layer delivery is successful, execute step 707; if the delivery status is that the SIP layer delivery fails, execute step 709.

[0177] ALT1: SIP layer delivery is successful

[0178] Step 707: When the service processing module 501 determines that the terminated short message is successfully delivered at the SIP layer, it updates the delivery status of the terminated short message to successfully delivered, and deletes the cached terminated short message.

[0179] Step 708: The service processing module 501 returns the terminated short message delivery confirmation information to the SMSC.

[0180] ALT1: SIP layer delivery failed

[0181] Step 709: When the service processing module 501 determines that the terminated short message fails to be delivered at the SIP layer, the service processing module 501 updates the delivery status of the terminated short message to delivery failure.

[0182] Step 710 , the service processing module 501 obtains the offline reactivation processing policy (including but not limited to the policy for deciding whether to offline reactivate the target terminal) from the policy decision module 502 .

[0183] Step 711, the service processing module 501 triggers the offline reactivation module 503 to execute the terminal offline reactivation processing flow (see Figure 8 ).

[0184] Figure 8 FIG. 1 is a schematic diagram of a process of triggering a terminal offline reactivation in a short message delivery method provided in an embodiment of this specification. Figure 8 As shown, the process may include:

[0185] Step 801 , the service processing module 501 obtains an offline reactivation processing policy (including but not limited to a policy for deciding whether to offline reactivate a target terminal) from the policy decision module 502 .

[0186] Step 802 : the policy decision module 502 returns the offline reactivation processing policy to the service processing module 501 .

[0187] Depending on the first strategy returned, after step 802, there may be the following three situations:

[0188] ALT1: Single Strategy

[0189] If the returned policy is a single policy (ie, when the delivery of the terminated short message to the target terminal fails, whether to go offline and reactivate the target terminal is determined according to the first policy), step 803 is executed.

[0190] Step 803 , the service processing module 501 triggers the offline reactivation module 503 to execute the terminal offline reactivation processing flow.

[0191] ALT2: Continuous Abnormal Threshold Strategy

[0192] If the returned policy is a continuous abnormal threshold policy (i.e., when the delivery of the terminated short message to the target terminal fails and the number of consecutive delivery failures of the terminated short message reaches a first threshold, determine whether to go offline and reactivate the target terminal according to the first policy), execute step 804.

[0193] Step 804: the service processing module 501 obtains the historical delivery status of the terminated short message, and determines the number of consecutive delivery failures for the terminated short message based on the historical delivery status.

[0194] Step 805 , the service processing module 501 determines whether the number of consecutive delivery failures reaches a threshold (first threshold); if not, execute step 806 ; otherwise, execute step 807 .

[0195] Step 806: the service processing module 501 triggers the IMS domain failure processing flow (ie, re-delivery).

[0196] Step 807 , the service processing module 501 triggers the offline reactivation module 503 to execute the terminal offline reactivation processing flow.

[0197] Step 808: The service processing module 501 saves or updates the delivery status of the terminated short message.

[0198] ALT3: Success rate threshold strategy

[0199] If the returned policy is a success rate threshold policy (i.e., when the delivery of the terminated short message to the target terminal fails and the short message delivery success rate of the target terminal is less than or equal to the second threshold, determine whether to go offline and reactivate the target terminal according to the first policy), execute step 809.

[0200] Step 809: the service processing module 501 obtains the historical delivery status of the terminated short message, and determines the delivery success rate of the terminated short message to the target terminal within a specified time based on the historical delivery status.

[0201] In step 810, the service processing module 501 determines whether the delivery success rate of the terminated short message reaches a threshold (a second threshold); if not, execute step 811; otherwise, execute step 812.

[0202] Step 811, the service processing module 501 triggers the IMS domain failure processing flow (ie, re-delivery).

[0203] Step 812: the service processing module 501 triggers the offline reactivation module 503 to execute the terminal offline reactivation processing flow.

[0204] Step 813: the service processing module 501 saves or updates the delivery status of the terminated short message.

[0205] Fig. 9 FIG. 1 is a schematic diagram of a terminal offline reactivation process in a short message delivery method provided in an embodiment of this specification. Fig. 9 As shown, the process may include:

[0206] Step 901: the offline reactivation processing module 503 obtains an offline reactivation processing strategy (including but not limited to a first strategy) from the strategy decision module 502.

[0207] Step 902 : the policy decision module 502 returns the offline reactivation processing policy to the offline reactivation processing module 503 .

[0208] Specifically, the offline reactivation processing module 503 can determine whether to offline and reactivate the target terminal according to the first strategy, and if yes, continue processing in one of the following two ways:

[0209] ALT1: Terminal offline strategy led by SCSCF

[0210] Step 903, the service processing module 501 triggers the offline reactivation processing module 503 to execute the offline reactivation processing flow;

[0211] Step 904, the offline reactivation processing module 503 sends a request to the service processing module 501 to reactivate the song terminal offline. The request carries user information and is used to remove the user and make the user offline.

[0212] Step 905, the service processing module 501 sends a terminal offline reactivation request (a message that triggers the target terminal to go offline) to the SCSCF;

[0213] Step 906, SCSCF notifies HSS to reactivate the target terminal;

[0214] Step 907, the HSS sends a recovery indication to the MME, where the recovery indication is used to instruct the reactivation of the target terminal;

[0215] Step 908 : The SCSCF returns a terminal offline reactivation response to the service processing module 501 .

[0216] Step 909 , the service processing module 501 returns a terminal offline reactivation response to the offline reactivation processing module 503 .

[0217] ALT2: Terminal offline strategy led by HSS

[0218] Step 910, the service processing module 501 triggers the offline reactivation processing module 503 to execute the offline reactivation processing flow;

[0219] Step 911, the offline reactivation processing module 503 sends a request to the service processing module 501 to reactivate the song terminal offline. The request carries user information and is used to remove the user and make the user offline.

[0220] Step 912, the service processing module 501 sends a terminal offline reactivation request (a message that triggers the target terminal to go offline) to the HSS;

[0221] Step 913, the HSS sends a recovery indication to the MME, where the recovery indication is used to instruct to reactivate the target terminal;

[0222] Step 914: The SCSCF returns a terminal offline reactivation response to the service processing module 501.

[0223] Step 915 , the service processing module 501 returns a terminal offline reactivation response to the offline reactivation processing module 503 .

[0224] It can be understood that the offline reactivation of the target terminal can be achieved through the above process.

[0225] Optional, such as Fig. 9 As shown, after the target terminal is offline and reactivated, a short message delivery method provided in this specification may further include:

[0226] Step 916: Determine whether to cache the terminated short message according to the second strategy.

[0227] There are three specific situations:

[0228] ALT1: Do not cache, go to step 917.

[0229] Step 917, triggering the delivery failure processing method in the related art.

[0230] ALT2: Cache, execute step 918.

[0231] Step 918: Cache the terminated short message according to the ID of the terminated short message.

[0232] Step 919: Return a specific error code to the SMSC, where the specific error code is used to instruct the SMSC not to trigger redelivery of the terminated short message.

[0233] ALT3: Finally fail and cache

[0234] Specifically, the terminated short message is not cached, and the terminated short message is processed according to a delivery failure processing method in the related art; if the terminated short message is successfully delivered according to the delivery failure processing method, the terminated short message is not cached; if the delivery of the terminated short message fails according to the delivery failure processing method, the terminated short message is cached.

[0235] For example, execute step 920 to transfer to the CS domain for delivery.

[0236] Optionally, step 921 is executed to return a specific error code to the SMSC, where the specific error code is used to instruct the SMSC not to trigger redelivery of the terminated short message.

[0237] In the case of a delivery failure according to the delivery failure processing method in the related art, step 924 is executed: the terminated short message is cached according to the ID of the terminated short message. Optionally, step 925 is executed to return a specific error code to the SMSC, the specific error code is used to instruct the SMSC not to trigger redelivery for the terminated short message.

[0238] It can be understood that caching the terminated short message that fails to be delivered in the IMS domain according to different situations can prepare for the future redelivery of the terminated short message in the IME domain, thereby improving the efficiency of redelivery.

[0239] Fig.10 This is a flow chart of applying a short message delivery method provided in an embodiment of this specification to deliver a terminated short message for the second scenario, wherein the second scenario is a scenario where the RP layer of the IMS domain of a 4G / 5G terminal responds abnormally, resulting in a failure in the delivery of the terminated short message. Fig.10 As shown, the process may include:

[0240] Step 1001, SMSC sends a terminating short message sending request (MTFWD) to the service processing module 501 in IPSMGW.

[0241] Step 1002: The service processing module 501 delivers a terminated call short message to the SCSCF.

[0242] Step 1003: SCSCF transmits the terminated call short message in the core network.

[0243] Step 1004: The core network delivers a terminated short message to the UE via the IMS domain.

[0244] Step 1005 , the SCSCF returns a response result indicating successful SIP layer delivery to the service processing module 501 .

[0245] Step 1006 , the SCSCF returns a response result of RP layer timeout to the service processing module 501 .

[0246] Step 1007: the business processing module 501 determines the delivery status.

[0247] Step 1008: The decision result of the service processing module 501 is that the RP layer delivery fails.

[0248] Step 1009 , the service processing module 501 obtains the offline reactivation processing policy (including but not limited to the policy for deciding whether to offline reactivate the target terminal) from the policy decision module 502 .

[0249] Step 1010, the service processing module 501 triggers the offline reactivation module 503 to execute the terminal offline reactivation processing flow (see Figure 8 ).

[0250] from Fig.10 It can be seen that for the second scenario (the scenario where the abnormal response of the RP layer in the IMS domain of the 4G / 5G terminal causes the failure of the delivery of the terminated short message), after applying a short message delivery method provided in an embodiment of this specification, the delivery success rate of the terminated short message can be improved and the delivery delay of the terminated short message can be reduced by re-delivering in the IMS domain.

[0251] Fig.11 This is a schematic diagram of the process of delivering a terminated short message after applying a short message delivery method provided by an embodiment of this specification to the first scenario or the second scenario. Fig.11 As shown, the process may include:

[0252] Step 1101, SMSC sends a terminated short message sending request (IMTFWDREQ) to IPSMGW.

[0253] Step 1102: IPSMGW delivers a terminated short message (IMS MT MESSAGE) to SCSCF in the IMS domain.

[0254] Step 1103: SCSCF returns a response indicating successful SIP layer delivery to IPSMGW.

[0255] Step 1104: SCSCF transmits the terminated call short message in the core network.

[0256] Step 1105: The core network delivers a terminated short message to the UE via the IMS domain.

[0257] Step 1106: SCSCF returns a response (IMS MTRPACK MESSAGE) indicating successful RP layer delivery to IPSMGW.

[0258] Step 1007: IPSMGW returns a response indicating successful SIP layer delivery to SCSCF.

[0259] Step 1008: IPSMGW returns the terminated short message delivery confirmation information to SMSC.

[0260] pass Fig.11 It is not difficult to see that after applying a short message delivery method provided in an embodiment of this specification, the terminated short message can be successfully delivered in the IMS domain through re-delivery, thereby improving the delivery success rate of the terminated short message.

[0261] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0262] Fig.12 This is a schematic diagram of the structure of an electronic device according to an embodiment of this specification. Fig.12 At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. The memory may include a memory, such as a high-speed random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage. Of course, the electronic device may also include hardware required for other services.

[0263] The processor, network interface and memory can be interconnected through an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.12 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0264] The memory is used to store the program. Specifically, the program may include a program code, and the program code includes a computer operation instruction. The memory may include a memory and a non-volatile memory, and provides instructions and data to the processor.

[0265] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a short message delivery device at the logical level. The processor executes the program stored in the memory and is specifically used to perform the following operations:

[0266] In the case where the delivery of the terminated short message to the target terminal fails, determining whether to go offline and reactivate the target terminal according to the first strategy;

[0267] When the target terminal is offline and reactivated, and the terminated short message is cached, the terminated short message is re-delivered through the IP Multimedia Subsystem IMS domain.

[0268] The above is as in this manual Fig.12 The method performed by the short message delivery device disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of this specification can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiments of this specification can be directly embodied as a hardware decoding processor for execution, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0269] The electronic device may also perform Figure 4 Method, and implement short message delivery device in Figure 4 The functions in the illustrated embodiments will not be described in detail in this specification.

[0270] Of course, in addition to software implementation, the electronic device of this specification does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc., that is to say, the executor of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0271] The embodiment of the present specification also provides a computer-readable storage medium, which stores one or more programs, wherein the one or more programs include instructions, which, when executed by a portable electronic device including a plurality of application programs, enable the portable electronic device to execute Figure 4 The method of the embodiment shown is specifically used to perform the following operations:

[0272] In the case where the delivery of the terminated short message to the target terminal fails, determining whether to go offline and reactivate the target terminal according to the first strategy;

[0273] When the target terminal is offline and reactivated, and the terminated short message is cached, the terminated short message is re-delivered through the IP Multimedia Subsystem IMS domain.

[0274] Fig.13 This is a schematic diagram of the structure of a short message delivery device 1300 according to an embodiment of the present specification. Fig.13 In a software implementation, the short message delivery device 1300 may include: a first determination module 1301 and a redelivery module 1302 .

[0275] The first determining module 1301 is configured to determine whether to log off and reactivate the target terminal according to a first strategy when a terminated short message to the target terminal fails to be delivered.

[0276] The target terminal can be any user terminal that receives the terminated call short message via IPSMGW.

[0277] After receiving the terminated short message from the short message service center SMSC, the IPSMGW delivers the terminated short message to the target terminal through the IMS domain, and receives a delivery response to the terminated short message.

[0278] Optionally, the device 1300 may further include: a first updating module, configured to update a delivery status of the terminated call message according to the delivery response, wherein the delivery status includes a delivery failure or a delivery success.

[0279] Optionally, the device 1300 may further include: a cache module, which is used to detect whether the terminated short message is cached when it is determined that the terminated short message is delivered successfully, and if so, delete the cached terminated short message.

[0280] Optionally, the apparatus 1300 may further include: a second updating module, configured to update the number of consecutive delivery failures of the terminated short message according to the historical delivery status of the terminated short message.

[0281] As an example, the first determining module 1301 may be used to determine whether to log off and reactivate the target terminal according to the delivery response and the first policy (IMS domain delivery exception handling policy).

[0282] The first strategy may include but is not limited to at least one of the following:

[0283] 1) If the delivery response includes a response result of a SIP layer response timeout, then log off and reactivate the terminal;

[0284] 2) If the delivery response includes a response result that the SIP layer is unreachable, then log off and reactivate the terminal;

[0285] 3) If the delivery response includes a response result of RP layer response timeout, log off and reactivate the terminal;

[0286] 4) If the delivery response includes a response result that cannot be received due to the terminal's own reasons, the terminal is offline and reactivated or the terminal is not offline, wherein the own reasons include but are not limited to at least one of memory full and decoding failure.

[0287] In addition, when the delivery of the terminated short message to the target terminal fails, when the first determination module 1301 is triggered to determine whether to go offline and reactivate the target terminal according to the first strategy can be divided into but not limited to the following three situations:

[0288] 1) When the delivery of the terminated short message to the target terminal fails, immediately determine whether to log off and reactivate the target terminal according to the first strategy.

[0289] 2) when the delivery of the terminated short message to the target terminal fails and the number of consecutive delivery failures of the terminated short message reaches a first threshold, determining whether to go offline and reactivate the target terminal according to a first strategy;

[0290] As described above, when the delivery status of the terminated short message is stored according to the IMPU, the historical delivery status of the terminated short message can be queried according to the IMPU, and the number of consecutive delivery failures can be determined accordingly.

[0291] 3) When the delivery of the terminated short message to the target terminal fails and the short message delivery success rate of the target terminal is less than or equal to the second threshold, determining whether to go offline and reactivate the target terminal according to the first strategy.

[0292] If it is determined in the first determining module 1301 to log off and reactivate the target terminal, then the log off and reactivate the target terminal may include the following two methods.

[0293] The first method: Downline reactivation led by SCSCF

[0294] The offline and reactivation of the target terminal includes: sending a message to S-CSCF to trigger the offline of the target terminal, the S-CSCF is used to notify the HSS to reactivate the target terminal after receiving the message, and the HSS is used to MME to send a recovery indication, and the recovery indication is used to indicate the reactivation of the target terminal.

[0295] The second method: offline reactivation led by HSS

[0296] The offline and reactivating the target terminal includes: sending a notification of reactivating the target terminal to the HSS, wherein the HSS is used to send a recovery indication to the MME, and the recovery indication is used to instruct the reactivation of the target terminal.

[0297] Optionally, the device 1300 may further include: a second determination module, configured to determine whether to cache the terminated call short message according to a second strategy when the target terminal is offline and reactivated.

[0298] The second strategy may include but is not limited to:

[0299] 1) Do not cache the terminated short message, and process the terminated short message according to the delivery failure processing method in the related art

[0300] 2) caching the terminated short message;

[0301] 3) not caching the terminated short message, but processing the terminated short message according to a delivery failure processing method in the related art; if the terminated short message is successfully delivered according to the delivery failure processing method, not caching the terminated short message; if the delivery of the terminated short message fails according to the delivery failure processing method, caching the terminated short message.

[0302] Among them, the delivery failure processing method in the related technology includes: transferring the delivery to the CS domain according to conditions or terminating the process to return a specific error code to the SMSC to trigger the SMSC to retry according to the policy.

[0303] Optionally, the device 1300 may further include: an error code returning module, which is used to return a specific error code to the short message service center SMSC if it is determined that the terminated short message is cached, and the specific error code is used to instruct the SMSC not to trigger redelivery of the terminated short message, so as to avoid the SMSC redeliving the terminated short message, thereby avoiding wasting network resources and avoiding problems such as sending to multiple recipients.

[0304] The re-delivery module 1302 is used to re-deliver the terminated short message through the IP Multimedia Subsystem IMS domain when the target terminal is offline and reactivated and the terminated short message is cached.

[0305] Exemplarily, the redelivery module 1302 may be used to: determine whether the terminated short message is cached when a trigger condition is met; and redeliver the terminated short message through the IMS domain if it is determined that the terminated short message is cached.

[0306] The triggering conditions include but are not limited to at least one of the following:

[0307] 1) receiving reactivation information of the target terminal;

[0308] 2) Satisfy the redelivery strategy.

[0309] Optionally, the apparatus 1300 may further include: a first deleting module, configured to not re-deliver the terminated short message but to delete the cached terminated short message if the number of delivery times of the terminated short message exceeds a certain threshold.

[0310] Optionally, the apparatus 1300 may further include: a third updating module, configured to update the delivery status of the terminated short message to successful delivery according to a delivery response when it is determined that the terminated short message is successfully delivered.

[0311] Optionally, the apparatus 1300 may further include: a second deleting module, configured to delete the cached terminated short message when it is determined that the terminated short message is delivered successfully, so as to avoid occupying storage resources of the IPSMGW.

[0312] A short message delivery device 1300 provided in an embodiment of the present specification can, when the delivery of a terminated short message to a target terminal fails, go offline and reactivate the target terminal according to a policy, and redeliver the terminated short message through the IMS domain after reactivating the target terminal. Therefore, the success rate of short message delivery in the IMS domain can be improved, and because the delivery is redelivered in the IMS domain instead of being transferred to the CS domain for delivery, the delivery delay can also be reduced.

[0313] The short message delivery device 1300 provided in the embodiment of this specification can also execute Figure 4The method is implemented by the short message delivery device 1300. Figure 4 The functions of the illustrated embodiments will not be described in detail in the embodiments of this specification.

[0314] In short, the above description is only a preferred embodiment of this specification and is not intended to limit the protection scope of this specification. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this specification shall be included in the protection scope of this specification.

[0315] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0316] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0317] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0318] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

Claims

1. A short message delivery method, applied to an IP short message gateway IPSMGW, the method comprising: In the case where the delivery of the terminated short message to the target terminal fails, determining whether to go offline and reactivate the target terminal according to the first strategy; When the target terminal is offline and reactivated, and the terminated short message is cached, the terminated short message is re-delivered through the IP Multimedia Subsystem IMS domain.

2. The method according to claim 1, before determining whether to go offline and reactivate the target terminal according to the first policy, the method further comprises: Receiving the terminated short message from a short message service center SMSC; Delivering the terminated short message to the target terminal via the IMS domain; receiving a delivery response to the terminated short message; Wherein, determining whether to go offline and reactivate the target terminal according to the first strategy includes: Determine whether to go offline and reactivate the target terminal according to the delivery response and a first strategy, wherein the first strategy includes at least one of the following: If the delivery response includes a response result of a SIP layer response timeout, then log off and reactivate the terminal; If the delivery response includes a response result that the SIP layer is unreachable, then log off and reactivate the terminal; If the delivery response includes a response result of RP layer response timeout, then log off and reactivate the terminal; If the delivery response includes a response result that cannot be received due to the terminal's own reasons, the terminal is offline and reactivated or the terminal is not offline, and the own reasons include at least one of memory full and decoding failure.

3. The method according to claim 2, further comprising: The delivery status of the terminated call message is updated according to the delivery response, wherein the delivery status includes delivery failure or delivery success.

4. The method according to claim 3, further comprising: The number of consecutive delivery failures of the terminated short message is updated according to the historical delivery status of the terminated short message.

5. The method according to claim 4, wherein, in the case where the delivery of the terminated short message to the target terminal fails, determining whether to go offline and reactivate the target terminal according to the first strategy comprises: In the case where the delivery of the terminated short message to the target terminal fails, determining whether to go offline and reactivate the target terminal according to the first strategy; or, When the delivery of the terminated short message to the target terminal fails and the number of consecutive delivery failures of the terminated short message reaches a first threshold, determining whether to go offline and reactivate the target terminal according to a first strategy; or, When the delivery of the terminated short message to the target terminal fails and the short message delivery success rate of the target terminal is less than or equal to the second threshold, it is determined whether to log off and reactivate the target terminal according to the first strategy.

6. The method according to claim 1, wherein the step of shutting down and reactivating the target terminal comprises: Sending a message to trigger the target terminal to go offline to a serving call session control function S-CSCF, wherein the S-CSCF is used to notify a home subscriber server HSS to reactivate the target terminal after receiving the message, and the HSS is used to send a recovery indication to a mobility management entity MME, wherein the recovery indication is used to instruct to reactivate the target terminal; or, A notification of reactivating the target terminal is sent to a home subscriber server HSS, and the HSS is used to send a recovery indication to a mobility management entity MME, where the recovery indication is used to instruct the reactivation of the target terminal.

7. The method according to claim 1, before redelivering the terminated short message through the IMS domain, the method further comprises: In the case of going offline and reactivating the target terminal, determining whether to cache the terminated short message according to a second strategy.

8. The method according to claim 7, wherein the second strategy comprises at least one of the following: The terminated short message is not cached, and the terminated short message is processed according to a delivery failure processing method in the related art; caching the terminated short message; The terminated short message is not cached, and the terminated short message is processed according to a delivery failure processing method in the related art; if the terminated short message is successfully delivered according to the delivery failure processing method, the terminated short message is not cached; if the delivery of the terminated short message fails according to the delivery failure processing method, the terminated short message is cached.

9. The method according to claim 8, further comprising: If it is determined to cache the terminated short message, a specific error code is returned to a short message service center SMSC, where the specific error code is used to instruct the SMSC not to trigger redelivery of the terminated short message.

10. The method according to claim 1, wherein when the target terminal is offline and reactivated and the terminated short message is cached, the terminated short message is re-delivered through the IMS domain, comprising: When the trigger condition is met, determining whether the terminated short message is cached; In the case where it is determined that the terminated short message is cached, re-delivering the terminated short message through the IMS domain; The trigger condition includes at least one of the following: receiving reactivation information of the target terminal; Satisfy the redelivery policy.

11. The method according to any one of claims 1 to 10, further comprising: When it is determined that the terminated short message is delivered successfully, the delivery status of the terminated short message is updated to delivery success according to the delivery response.

12. The method according to claim 11, further comprising: When it is determined that the terminated short message is delivered successfully, the cached terminated short message is deleted.

13. An electronic device, comprising: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the method according to any one of claims 1 to 12.

14. A computer-readable storage medium, when instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the method according to any one of claims 1 to 12.

Images