Short message delivery method, device, and computer-readable storage medium

Abstract

Embodiments of the present description provide a short message delivery method, an electronic device, and a computer-readable storage medium. The method comprises: when delivery of a terminating short message to a target terminal fails, according to a first policy, determining whether to enable the target terminal to go offline and be reactivated; and when the target terminal goes offline and is reactivated, and the terminating short message is cached, re-delivering the terminating short message by means of an IP multimedia subsystem (IMS) domain.

Description

Short message delivery method, device and computer-readable storage medium

[0001] Cross-references

[0002] The present invention claims priority to a Chinese patent application filed with the Patent Office of China on June 30, 2023, with application number 202310797850.8 and invention name “A short message delivery method, device and computer-readable storage medium”. The entire contents of the application are incorporated herein by reference. Technical Field

[0003] 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

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

[0005] When a 2G / 4G dual-attached terminal fails to deliver in the 4G (IP Multimedia Subsystem (IMS) domain), it can normally switch to the 2G (Circuit Switch (CS) domain) to continue delivery. Deliveries in two different domains will increase core network signaling and increase the final call delivery delay. Various anomalies such as terminal or network timeouts may also occur, 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 short message delivery fails and cannot be restored, and the 4G terminal will not be able to receive the short message. When the terminal is jointly attached to 4G / 5G, the short message only goes 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.

[0006] 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.

[0007] Summary of the Invention

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

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

[0010] In a first aspect, a short message delivery method is provided, which is applied to an IP short message gateway IPSMGW. The method includes: in the case where the delivery of a terminated short message to a target terminal fails, determining whether to go offline and reactivate the target terminal according to a first strategy; in the case where the target terminal is offline and reactivated, and the terminated short message is cached, re-delivering the terminated short message through the IP Multimedia Subsystem IMS domain.

[0011] In the second aspect, a short message delivery device is provided, which is applied to the IP short message gateway IPSMGW. The device includes: a first determination module, which is used to determine whether to go offline and reactivate the target terminal according to a first strategy when the delivery of the terminated short message to the target terminal fails; a redelivery module, which is used to redeliver 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.

[0012] According to a third aspect, an electronic device is provided, comprising: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the method described in the first aspect.

[0013] In a fourth aspect, a computer-readable storage medium is provided. When the instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the method described in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. 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 any creative labor.

[0015] FIG1 is a flow chart of a call termination short message delivery process for a 2G / 4G dual-attached terminal when an IMS domain anomaly occurs in the related art.

[0016] FIG2 is a flowchart of a terminating short message delivery process for a 4G / 5G dual-attached terminal in the related art when an IMS domain anomaly occurs.

[0017] FIG3 is a flow chart of a related art showing a terminated call short message delivery process for a 4G terminal that has exited a 2G / 3G network and has an abnormal IMS domain.

[0018] FIG4 is a flow chart of a short message delivery method provided by an embodiment of this specification.

[0019] FIG5 is a schematic diagram of an implementation structure of a short message delivery method provided in an embodiment of this specification.

[0020] Figure 6 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 first scenario, wherein the first scenario is a scenario where the terminating short message delivery fails due to an abnormal response of the SIP layer in the IMS domain of a 4G / 5G terminal.

[0021] FIG. 7 is a schematic diagram of a detailed flow of delivering a terminated short message using a short message delivery method provided in an embodiment of this specification for the first scenario.

[0022] FIG8 is a schematic diagram of a process for triggering terminal offline reactivation in a short message delivery method provided by an embodiment of this specification.

[0023] FIG9 is a schematic diagram of a terminal offline reactivation process in a short message delivery method provided by an embodiment of this specification.

[0024] Figure 10 is a flow chart of delivering terminated short messages using a short message delivery method provided in an embodiment of this specification for the second scenario, wherein the second scenario is a scenario where the 4G / 5G terminal IMS domain RP layer responds abnormally, resulting in a failure in the delivery of the terminated short message.

[0025] FIG11 is a schematic diagram of a terminated short message delivery process after applying a short message delivery method provided by an embodiment of this specification for the first scenario or the second scenario.

[0026] FIG12 is a schematic structural diagram of an electronic device according to an embodiment of the present specification.

[0027] FIG13 is a schematic structural diagram of a short message delivery device according to an embodiment of the present specification. DETAILED DESCRIPTION

[0028] In order to help those skilled in the art 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 making creative efforts should fall within the scope of protection of this document.

[0029] The terms "first," "second," and the like in this specification and claims are used to distinguish similar objects and are not intended to describe a particular order or precedence. It should be understood that such terms are interchangeable where appropriate, so that the embodiments of this specification can be implemented in orders other than those illustrated or described herein. Furthermore, the term "and / or" in this specification and claims refers to at least one of the connected objects, and the character " / " generally indicates that the connected objects are in an "or" relationship.

[0030] The terms involved in the embodiments of this specification include: IP Short Message Gateway (IPSMGW); Short Message Service Center (SMSC); Service-Call Session Control Function (SCSCF); Mobile Switching Center (MSC); Home Subscriber Server (HSS); Mobile Management Entity (MME); Circuit Switch (CS domain); IP Multimedia Subsystem (IMS domain).

[0031] 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 terminated short messages when an IMS domain is abnormal.

[0032] For 2G / 4G dual-attached terminals, the related technology's terminated call short message delivery process when the IMS domain is abnormal is shown in Figure 1. The process includes:

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

[0034] The terminated short message is generally a terminated text message.

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

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

[0037] ALT1: SIP layer delivery failed.

[0038] Step 103: The SCSCF returns a response result of the SIP layer delivery failure and a corresponding failure code to IPSMGW.

[0039] Step 104: IPSMGW transfers the call termination short message to the CS domain.

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

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

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

[0043] Step 106: SCSCF returns a message indicating that the RP layer delivery has failed to IPSMGW.

[0044] Step 107: IPSMGW transfers the call termination short message to the CS domain.

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

[0046] In the terminated SMS delivery process shown in Figure 1, the IMS domain cannot automatically recover in some failure code scenarios. SMS delivery to the user equipment (UE) in the IMS domain will continue to fail. The IPSMGW then switches to the CS domain for delivery. However, the CS domain delivery delay is relatively large, which may cause the front-end network element to timeout and retry, leading to problems such as multiple receptions at the same time.

[0047] For 4G / 5G dual-attached terminals, the related technology's terminated call short message delivery process when the IMS domain is abnormal is shown in Figure 2. The process includes:

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

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

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

[0051] ALT1: SIP layer delivery failed.

[0052] Step 203: The SCSCF returns a response result of the SIP layer delivery failure and a corresponding failure code to IPSMGW.

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

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

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

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

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

[0058] Step 206: SCSCF returns a message indicating that the RP layer delivery has failed to IPSMGW.

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

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

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

[0062] For the terminated short message delivery process shown in Figure 2, 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 terminal being unable to receive short messages and a low short message delivery success rate.

[0063] For 4G terminals exiting the 2G / 3G network, the related technology's terminated call short message delivery process when an IMS domain exception occurs is shown in Figure 3. The process includes:

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

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

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

[0067] ALT1: SIP layer delivery failed.

[0068] Step 303: The SCSCF returns a response result of the SIP layer delivery failure and a corresponding failure code to IPSMGW.

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

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

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

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

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

[0074] Step 306: SCSCF returns a message indicating that the RP layer delivery has failed to IPSMGW.

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

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

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

[0078] For the terminated short message delivery process shown in Figure 3, since the IMS domain of 4G users cannot automatically recover in some failure code scenarios, 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.

[0079] 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.

[0080] FIG4 shows a short message delivery method according to an embodiment of the present specification. The method can be applied to IPSMGW. The method may include the following steps:

[0081] 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.

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

[0083] 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.

[0084] 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.

[0085] When determining that the terminated short message is delivered successfully, the IPSMGW may detect whether the terminated short message is cached, and if so, delete the cached terminated short message.

[0086] The 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.

[0087] 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 will be updated to successful delivery. Furthermore, it can also detect whether the terminated short message is cached. If it is cached, the cached terminated short message will be deleted. If it is determined that the delivery fails, the terminated short message that fails to be delivered in the IMS domain will be processed based on a pre-established processing strategy, and the delivery status of the terminated short message will be updated to failure.

[0088] 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.

[0089] A delivery response typically includes a response code and a response type. The response code is a pre-agreed status code for different response results. The response type typically includes internal errors (link anomalies) or external errors (terminal itself / SIP layer anomalies / RP layer anomalies).

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

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

[0092] 1) If the delivery response includes a response result indicating a SIP layer response timeout, the terminal is offline and reactivated.

[0093] 2) If the delivery response includes a SIP layer unreachable response result, the terminal is offline and reactivated.

[0094] 3) If the delivery response includes a response result indicating that the RP layer has timed out, the terminal is offline and reactivated.

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

[0096] In specific implementation, a policy table can be pre-defined to list the corresponding relationships between response codes, response types, and IMS domain delivery exception handling policies. In this way, after receiving the delivery response of the terminal short message, IPSMGW can query the policy table to determine the specific IMS domain delivery exception handling policy.

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

[0098] 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.

[0099] 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 log off and reactivate the target terminal according to a first strategy.

[0100] 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 number of consecutive delivery failures can be determined accordingly.

[0101] 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 a second threshold, determining whether to log off and reactivate the target terminal according to the first strategy.

[0102] As previously described, when the terminated short message delivery status is stored per IMPU, the historical delivery status of the terminated short message can be queried per IMPU, and the short message delivery success rate for the target terminal within a specified time period can be calculated accordingly. Generally, the specified time period is the validity period of the target terminal's registration, but it can also be a period closest to the current time.

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

[0104] The first method: offline reactivation led by SCSCF.

[0105] The offline and reactivation of the target terminal includes: sending a message to the 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 send a recovery indication to the MME, and the recovery indication is used to instruct the reactivation of the target terminal.

[0106] The second method: offline reactivation led by HSS.

[0107] 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.

[0108] In the case where the target terminal is offline and then reactivated, it may also be determined whether to cache the terminated short message according to a second policy.

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

[0110] 1) The terminated short message is not cached, and the terminated short message is processed according to the delivery failure processing method in the related art.

[0111] 2) Cache the terminated short message.

[0112] 3) not caching the terminated short message, but processing the terminated short message according to a delivery failure processing method in the relevant technology; if the terminated short message is successfully delivered according to the delivery failure processing method, not caching the terminated short message; if the terminated short message fails to be delivered according to the delivery failure processing method, caching the terminated short message.

[0113] Among them, the delivery failure processing methods in related technologies include: transferring delivery to the CS domain according to conditions or terminating the process and returning a specific error code to the SMSC to trigger the SMSC to retry according to the policy.

[0114] If it is determined that the terminated short message is cached, a specific error code is returned to the short message service center SMSC. 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.

[0115] 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.

[0116] 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.

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

[0118] 1) Receive reactivation information of the target terminal.

[0119] 2) Satisfy the redelivery strategy.

[0120] If the number of delivery times of the terminated short message exceeds a certain threshold, the terminated short message will not be re-delivered, but the cached terminated short message will be deleted.

[0121] 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.

[0122] 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.

[0123] A short message delivery method provided in an embodiment of the present specification can, when a terminated short message delivery 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. This can improve the success rate of short message delivery in the IMS domain, and because the delivery is redelivered in the IMS domain instead of being transferred to the CS domain for delivery, it can also reduce the delivery delay.

[0124] Figure 5 shows a schematic diagram of an implementation structure of a short message delivery method provided by an embodiment of this specification. As shown in Figure 5, a service processing module 501, a policy decision module 502 and an offline reactivation processing module 503 can be set in the IPSMGW.

[0125] The service processing module 501 is used to complete the codec adaptation with the MAP protocol, DIAMETER protocol, 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 process based on the IMS delivery response, that is, the preset policy table; in the event of IMS domain delivery failure, trigger the offline reactivation processing module and the cached message redelivery process according to the policy.

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

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

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

[0129] 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 at the same time caches the delivery status of the short message according to the IMPU according to the policy.

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

[0131] Figure 6 shows a flow chart of delivering terminated short messages using a short message delivery method provided in an embodiment of this specification for a first scenario, wherein the first scenario is a scenario where the terminating short message delivery fails due to an abnormal response of the SIP layer in the IMS domain of a 4G / 5G terminal.

[0132] As shown in FIG6 , 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:

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

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

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

[0136] Step 604: IPSMGW processes the terminated short message that fails to be delivered according to the policy.

[0137] Specifically, IPSMGW may determine whether to log off and reactivate the target terminal according to the first strategy. If so, it may continue processing in one of the following two ways:

[0138] ALT1: Terminal offline strategy led by SCSCF.

[0139] Step 605: IPSMGW sends a terminal offline reactivation message (a message that triggers the target terminal to go offline) to SCSCF.

[0140] Step 606: The SCSCF notifies the HSS to reactivate the target terminal.

[0141] 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.

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

[0143] ALT2: Terminal offline strategy led by HSS.

[0144] Step 609: IPSMGW notifies HSS to reactivate the target terminal.

[0145] Step 610: The HSS sends a recovery indication to the MME, where the recovery indication is used to instruct the reactivation of the target terminal.

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

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

[0148] 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.

[0149] The triggering condition includes at least one of the following:

[0150] Reactivation information of the target terminal is received; and a redelivery strategy is satisfied.

[0151] Step 613: IPSMGW feeds back a response to the SCSCF indicating that the terminated short message has been successfully delivered.

[0152] Step 614: IPSMGW returns a terminated short message delivery confirmation message to SMSC.

[0153] As can be seen from Figure 6, for the first scenario (the scenario where the abnormal response of the SIP 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, by re-delivering in the IMS domain, the delivery success rate of the terminated short message can be improved and the delivery delay of the terminated short message can be reduced.

[0154] FIG7 is a schematic diagram of a detailed process of delivering a terminated short message using a short message delivery method provided by an embodiment of this specification for the first scenario. As shown in FIG7 , the process may include:

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

[0156] The terminated short message is generally a terminated text message.

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

[0158] Step 703: The SCSCF transmits the terminated short message in the core network.

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

[0160] 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 .

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

[0162] If the delivery status is that the SIP layer delivery is successful, step 707 is executed; if the delivery status is that the SIP layer delivery is failed, step 709 is executed.

[0163] ALT1: SIP layer delivery is successful.

[0164] In 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 delivery success and deletes the cached terminated short message.

[0165] In step 708, the service processing module 501 returns a terminated short message delivery confirmation message to the SMSC.

[0166] ALT1: SIP layer delivery failed.

[0167] In step 709 , when the service processing module 501 determines that the delivery of the terminated short message fails at the SIP layer, the service processing module 501 updates the delivery status of the terminated short message to delivery failure.

[0168] In 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 .

[0169] In step 711 , the service processing module 501 triggers the offline reactivation module 503 to execute the terminal offline reactivation processing flow (see FIG. 8 ).

[0170] FIG8 is a schematic diagram of a process for triggering a terminal offline reactivation in a short message delivery method provided in an embodiment of this specification. As shown in FIG8 , the process may include:

[0171] In 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 .

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

[0173] Depending on the first policy returned, after step 802, the following three situations may occur:

[0174] ALT1: Single strategy.

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

[0176] In step 803 , the service processing module 501 triggers the offline reactivation module 503 to execute the terminal offline reactivation processing flow.

[0177] ALT2: Continuous abnormal threshold strategy.

[0178] If the returned policy is a continuous exception 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.

[0179] In 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.

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

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

[0182] In step 807 , the service processing module 501 triggers the offline reactivation module 503 to execute the terminal offline reactivation processing flow.

[0183] In step 808, the service processing module 501 saves or updates the delivery status of the terminated short message.

[0184] ALT3: Success rate threshold strategy.

[0185] If the returned policy is a success rate threshold policy (i.e., when the terminated short message delivery 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.

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

[0187] 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 .

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

[0189] In step 812, the service processing module 501 triggers the offline reactivation module 503 to execute the terminal offline reactivation processing flow.

[0190] In step 813, the service processing module 501 saves or updates the delivery status of the terminated short message.

[0191] FIG9 is a schematic diagram of a terminal offline reactivation process in a short message delivery method provided by an embodiment of this specification. As shown in FIG9 , the process may include:

[0192] In step 901 , the offline reactivation processing module 503 obtains an offline reactivation processing policy (including but not limited to the first policy) from the policy decision module 502 .

[0193] In step 902 , the policy decision module 502 returns the offline reactivation processing policy to the offline reactivation processing module 503 .

[0194] Specifically, the offline reactivation processing module 503 may determine whether to offline and reactivate the target terminal according to the first strategy. If yes, the processing may be continued in one of the following two ways:

[0195] ALT1: Terminal offline strategy led by SCSCF.

[0196] Step 903 : The service processing module 501 triggers the offline reactivation processing module 503 to execute the offline reactivation processing flow.

[0197] 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 for removing the user and making the user offline.

[0198] 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.

[0199] Step 906: The SCSCF notifies the HSS to reactivate the target terminal.

[0200] 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.

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

[0202] Step 909 : The service processing module 501 returns a terminal offline reactivation response to the offline reactivation processing module 503 .

[0203] ALT2: Terminal offline strategy led by HSS.

[0204] Step 910: The service processing module 501 triggers the offline reactivation processing module 503 to execute the offline reactivation processing flow.

[0205] In 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 for removing the user and making the user offline.

[0206] 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.

[0207] Step 913: The HSS sends a recovery indication to the MME, where the recovery indication is used to instruct the reactivation of the target terminal.

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

[0209] Step 915 : The service processing module 501 returns a terminal offline reactivation response to the offline reactivation processing module 503 .

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

[0211] As shown in FIG9 , after the target terminal is offline and reactivated, the short message delivery method provided in this specification may further include:

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

[0213] There are three specific situations:

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

[0215] Step 917: triggering a delivery failure processing method in related technologies.

[0216] ALT2: Cache, execute step 918.

[0217] Step 918: Cache the terminated short message according to its ID.

[0218] 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.

[0219] ALT3: Finally fail and then cache.

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

[0221] For example, execute step 920 and switch to the CS domain for delivery.

[0222] Execute step 921 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.

[0223] If delivery fails according to the delivery failure handling method in the related art, step 924 is executed: the terminated short message is cached according to the ID of the terminated short message. Step 925 is executed to return a specific error code to the SMSC, which is used to instruct the SMSC not to trigger redelivery of the terminated short message.

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

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

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

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

[0228] Step 1003: The SCSCF transmits the terminated short message in the core network.

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

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

[0231] Step 1006 : The SCSCF returns a response result indicating that the RP layer has timed out to the service processing module 501 .

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

[0233] Step 1008: The service processing module 501 determines that the RP layer delivery fails.

[0234] In 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 .

[0235] In step 1010 , the service processing module 501 triggers the offline reactivation module 503 to execute the terminal offline reactivation processing flow (see FIG. 8 ).

[0236] As can be seen from Figure 10, for the second scenario (the scenario where the 4G / 5G terminal IMS domain RP layer responds abnormally, resulting in the failure of the terminated short message delivery), 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 by re-delivering it in the IMS domain, and the delivery delay of the terminated short message can be reduced.

[0237] FIG11 is a schematic diagram of a terminated short message delivery process after applying a short message delivery method provided by an embodiment of this specification for the first scenario or the second scenario. As shown in FIG11 , the process may include:

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

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

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

[0241] Step 1104: The SCSCF transmits the terminated short message in the core network.

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

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

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

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

[0246] It is not difficult to see from FIG11 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 success rate of terminated short message delivery.

[0247] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0248] FIG12 is a schematic diagram of the structure of an electronic device according to an embodiment of the present specification. Referring to FIG12 , 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 device. Of course, the electronic device may also include hardware required for other services.

[0249] The processor, network interface, and memory can be interconnected via an internal bus, such as an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus. These buses can be classified as address buses, data buses, and control buses. For ease of illustration, FIG12 shows only one bidirectional arrow, but this does not imply that there is only one bus or only one type of bus.

[0250] The memory is used to store programs. Specifically, the program may include program code, which includes computer operating instructions. The memory may include internal memory and non-volatile memory, and provides instructions and data to the processor.

[0251] The processor reads the corresponding computer program from the non-volatile memory into the internal 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:

[0252] In the case that the delivery of the terminated short message to the target terminal fails, it is determined whether to log off and reactivate the target terminal according to the first strategy.

[0253] 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.

[0254] The method performed by the short message delivery device disclosed in the embodiment shown in Figure 12 of this specification can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by hardware integrated logic circuits in the processor or software instructions. 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 gate or transistor logic devices, or discrete hardware components. The various 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 any conventional processor. The steps of the method disclosed in conjunction with the embodiments of this specification can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.

[0255] The electronic device can also execute the method of FIG. 4 and realize the functions of the short message delivery device in the embodiment shown in FIG. 4 , and the embodiments of this specification will not be described in detail here.

[0256] Of course, in addition to software implementation, the electronic device in 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 execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0257] The embodiments of this specification also provide a computer-readable storage medium, which stores one or more programs. The one or more programs include instructions. When executed by a portable electronic device including multiple application programs, the instructions enable the portable electronic device to perform the method of the embodiment shown in FIG. 4 , and are specifically configured to perform the following operations:

[0258] In the event that a terminated short message to a target terminal fails to be delivered, determining whether to log off and reactivate the target terminal according to a first strategy;

[0259] 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.

[0260] FIG13 is a schematic diagram of the structure of a short message delivery device 1300 according to an embodiment of the present disclosure. Referring to FIG13 , in a software implementation, the short message delivery device 1300 may include: a first determination module 1301 and a redelivery module 1302 .

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

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

[0263] 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.

[0264] The apparatus 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 delivery failure or delivery success.

[0265] The apparatus 1300 may further include: a cache module configured 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.

[0266] 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.

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

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

[0269] 1) If the delivery response includes a response result indicating a SIP layer response timeout, the terminal is offline and reactivated.

[0270] 2) If the delivery response includes a SIP layer unreachable response result, the terminal is offline and reactivated.

[0271] 3) If the delivery response includes a response result indicating that the RP layer has timed out, the terminal is offline and reactivated.

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

[0273] In addition, when the delivery of the terminated short message to the target terminal fails, when the first determining 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:

[0274] 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.

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

[0276] 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 number of consecutive delivery failures can be determined accordingly.

[0277] 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 a second threshold, determining whether to log off and reactivate the target terminal according to the first strategy.

[0278] If it is determined in the first determining module 1301 that the target terminal is to be offline and reactivated, then the offline and reactivation of the target terminal may include the following two methods.

[0279] The first method: offline reactivation led by SCSCF.

[0280] The offline and reactivation of the target terminal includes: sending a message to the 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 send a recovery indication to the MME, and the recovery indication is used to instruct the reactivation of the target terminal.

[0281] The second method: offline reactivation led by HSS.

[0282] 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.

[0283] The apparatus 1300 may further include: a second determining module configured to determine whether to cache the terminated call short message according to a second policy when the target terminal is offline and reactivated.

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

[0285] 1) The terminated short message is not cached, and the terminated short message is processed according to the delivery failure processing method in the related art.

[0286] 2) Cache the terminated short message.

[0287] 3) not caching the terminated short message, but processing the terminated short message according to a delivery failure processing method in the relevant technology; if the terminated short message is successfully delivered according to the delivery failure processing method, not caching the terminated short message; if the terminated short message fails to be delivered according to the delivery failure processing method, caching the terminated short message.

[0288] Among them, the delivery failure processing methods in related technologies include: transferring delivery to the CS domain according to conditions or terminating the process and returning a specific error code to the SMSC to trigger the SMSC to retry according to the policy.

[0289] The device 1300 may also 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 to cache the terminated short message, and the specific error code is used to instruct the SMSC not to trigger the 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 and receiving multiple messages.

[0290] The redelivery module 1302 is configured to redeliver 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.

[0291] Exemplarily, the redelivery module 1302 may be configured 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.

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

[0293] 1) Receive reactivation information of the target terminal.

[0294] 2) Satisfy the redelivery strategy.

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

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

[0297] 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.

[0298] A short message delivery device 1300 provided in an embodiment of this specification can, when 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. This can improve the success rate of short message delivery in the IMS domain, and because the message is redelivered in the IMS domain instead of being transferred to the CS domain for delivery, it can also reduce the delivery delay.

[0299] The short message delivery device 1300 provided in the embodiment of this specification can also execute the method of FIG. 4 and realize the functions of the short message delivery device 1300 in the embodiment shown in FIG. 4 , which will not be described in detail in this embodiment of this specification.

[0300] In short, the above description is only a preferred embodiment of this specification and is not intended to limit the scope of protection of this specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this specification shall be included in the scope of protection of this specification.

[0301] The systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or entities, or by products having 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 smartphone, 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.

[0302] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The 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 disc read-only memory (CD-ROM), digital versatile disc (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 transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0303] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0304] The various embodiments in this specification are described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the system embodiments are generally similar to the method embodiments, so the description is relatively simple. For relevant parts, refer to the description of the method embodiments.

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 restoration indication to a mobility management entity MME, where the restoration 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