WO2018196715A1

WO2018196715A1 - Short message centre reminding method and short message gateway

Info

Publication number: WO2018196715A1
Application number: PCT/CN2018/084123
Authority: WO
Inventors: 张丽; 信斌
Original assignee: 中兴通讯股份有限公司
Priority date: 2017-04-27
Filing date: 2018-04-23
Publication date: 2018-11-01
Also published as: CN108810830A

Abstract

Provided are a short message centre reminding method and a short message gateway. The method comprises: a short message gateway determining accessibility of a receiving terminal based on the registration of the receiving terminal on an application server, acquiring a failed delivery record stored for a short message to be redelivered to the receiving terminal, and then triggering short message centre reminding according to the failed delivery record.

Description

Short message center reminding method and short message gateway

Technical field

The present disclosure relates to the field of communications, and in particular, to a short message center reminding method and a short message gateway.

Background technique

The short message gateway and the short message center are network elements that provide a short message service for the contracted user, wherein the short message center can implement short message receiving, storing, forwarding, short message report generation, short message inquiry, and short message charging, etc. Features. The short message gateway can provide routing and interworking functions between different short message systems. The short message of the traditional circuit domain is mainly provided by the short message center, and is carried by the No. 7 signaling; and the IP short message is implemented by the SIP (Session Initiation Protocol) MESSAGE. In order to reduce the transformation of the existing network circuit domain and IMS domain, the traditional short message mechanism is reused, and IP-SM-GW (IP-Short-Message-Gateway) is introduced into the network of IMS (IP Multimedia Subsystem). The protocol short message gateway provides IP short message service.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiment of the present disclosure provides a short message center reminding method and a short message gateway.

The embodiment of the present disclosure provides a short message center reminding method, including:

The short message gateway determines that the receiving terminal is reachable based on the registration of the receiving terminal by the application server;

The short message gateway obtains a failed delivery record stored for the short message to be re-submitted by the receiving terminal, and the failed delivery record is generated when the short message gateway fails to deliver the short message to be re-sent to the receiving terminal;

The short message gateway triggers the short message center reminder according to the failed delivery record to instruct the short message center to resend the to-be-resubmitted short message to the receiving terminal.

The embodiment of the present disclosure further provides a short message gateway, including:

a recording module, configured to store a failed delivery record for the short message to be re-sent after failing to deliver the short message to the receiving terminal;

Determining a module, configured to determine that the receiving terminal is reachable based on a registration of the receiving terminal at the application server;

An obtaining module, configured to acquire a failed delivery record stored for the short message to be re-submitted by the receiving terminal;

The reminding module is configured to trigger the short message center reminder according to the failed delivery record to instruct the short message center to resend the to-re-submission short message loss to the receiving terminal.

The embodiment of the present disclosure further provides a computer storage medium, where the computer storage medium stores computer executable instructions for executing the short message center reminding method.

The beneficial effects of the present disclosure are:

According to the short message center reminding method and the short message gateway and the computer storage medium provided by the embodiment of the present disclosure, the short message gateway determines that the receiving terminal is reachable based on the registration of the receiving terminal by the receiving terminal, and acquires a failure to store the short message to be received by the receiving terminal. The record is posted, and then the short message center reminder is triggered according to the failed delivery record to inform the short message center to resend the short message to be re-submitted to the receiving terminal. The solution provided by the embodiment of the present disclosure utilizes the short message gateway to directly know the registration of the receiving terminal on the application server. Therefore, the short message gateway does not go to the HLR/HSS (Home Location Register/Home Subscriber Server, home location register/home subscriber server). When you subscribe to the reachability of the receiving terminal, you can directly know when the receiving terminal is reachable. When the short message gateway determines that the receiving terminal is reachable, it acquires a pre-recorded stored failed posting record for the receiving terminal, and triggers a short message center reminder according to the failed delivery record. Since the HLR/HSS does not provide terminal reachability in the process of implementing the short message center reminder, the functional requirements of the HLR/HSS are reduced, and the application scenario is wider than the existing solution; The HLR/HSS does not interact and cooperate with the MME (Mobility Management Entity), etc., which saves the communication resources and processing resources of the system, and is beneficial to the optimal configuration of resources.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

DRAWINGS

FIG. 1 is a schematic diagram of a system networking of a short message system including an internet protocol short message gateway;

2 is an interactive flow chart for performing a short message center reminder;

FIG. 3 is a flowchart of a short message center reminding method according to Example 1 of the present disclosure;

4 is a flowchart of a short message gateway triggering a short message center reminder according to a failed delivery record according to an example of the present disclosure;

FIG. 5 is a flowchart of a short message center reminding method provided by example 2 of the present disclosure;

6 is an interaction flowchart of three types of storage failure posting records provided by an example of the present disclosure;

FIG. 7 is an interaction flowchart of performing short message center reminding in the initial registration situation of the receiving terminal provided by three examples of the present disclosure;

8 is an interaction flowchart of performing short message center reminding in a refreshing registration situation of a receiving terminal provided by three exemplary embodiments of the present disclosure;

FIG. 9 is a schematic structural diagram of a short message gateway provided in Example 4 of the present disclosure;

FIG. 10 is a schematic structural diagram of a short message gateway provided in Example 5 of the present disclosure;

FIG. 11 is a schematic structural diagram of hardware of a server for deploying a short message gateway according to Example 6 of the present disclosure.

detailed description

See Figure 1 for the IMS system networking diagram. The Internet Protocol Short Message Gateway 11 provides protocol interaction between the IP-based UE (User Equipment) 12 and the SMSC (Short Message Service Center) 13 for sending and receiving short messages. When the user edits the short message on the sending terminal and selects to send, the short message will be delivered to the short message center. After receiving the short message, the short message center will send the short message to the internet protocol short message gateway 11 on the receiving terminal side, and the internet protocol short message gateway 11 will deliver the short message to the corresponding network element for delivery to the receiving terminal. When the receiving terminal cannot receive the short message due to factors such as shutdown or signal difference, the delivery of the short message will fail. In the case of a short message delivery failure, a mechanism for subscribing to the receiving terminal is established in the 3GPP standard (see 3GPP TS 23.204 for details): after the short message delivery fails, the internet protocol short message gateway 11 sends a short message delivery status report to the HLR/HSS 14 ( Map-Report-SM-Delivery-Status), and subscribe to the HSS to receive the reachability of the terminal. After the receiving terminal is reachable, the internet protocol short message gateway 11 receives the notification of the home location register/home subscriber server 14. Upon receiving the reachability notification, the Internet Protocol Short Message Gateway 11 sends MAP-READY-FOR-SM to the Home Location Register/Home Subscriber Server 14. After receiving the message, the home location register/home subscriber server 14 triggers an Alert SC (short message center reminder) procedure for the short message center to resend the short message that failed to be delivered before. For the specific process, refer to the interaction diagram shown in Figure 2:

S202. The IP-SM-GW sends a short message delivery status report to the HLR/HSS and subscribes to the reachable notification of the receiving terminal.

The short message delivery result is included in the status report. In this example, the short message is a delivery failure. The IP-SM-GW subscribes to the reachability of the receiving terminal by sending a Map-Any-Time-Modification to the HLR/HSS.

S204. The HLR/HSS instructs the MME to report the reachability of the receiving terminal.

If the receiving terminal is already registered in the MME, the HLR/HSS may send an IDR request message (UE reachability notification) to the MME, indicating that the MME reports the reachability of the receiving terminal. If the receiving terminal is not registered with the MME, the HLR/HSS does not send a request message.

S206. The MME notifies the HLR/HSS receiving terminal that the terminal is reachable.

When the receiving terminal is reachable, the MME notifies the HLR/HSS that the receiving terminal is reachable through NOR.

S208. The HLR/HSS sends a reachability notification to the IP-SM-GW.

The HLR/HSS determines that the receiving terminal is reachable according to the NOR notification of the MME, and sends a reachability notification to the IP-SM-GW according to the previous subscription of the IP-SM-GW.

S210. The IP-SM-GW sends a MAP-READY-FOR-SM message to the HLR/HSS.

After knowing that the receiving terminal is reachable according to the reachable notification, the IP-SM-GW determines that the short message can be re-delivered to the receiving terminal. Therefore, the LR-READY-FOR-SM can be used to notify the HLR/HSS to trigger to the SC. Alert SC process.

S212. The HLR/HSS triggers the Alert SC process to the SC.

After receiving the MAP-READY-FOR-SM, the HLR/HSS can trigger the SMS center to reschedule the delivery of the failed short message for the receiving terminal.

According to the above introduction, it can be understood that the process of triggering the short message center reminder depends on the HLR/HSS notifying the IP-SM-GW of the reachability of the receiving terminal, once the HLR/HSS does not support the reachability subscription of the IP-SM-GW. , based on the program can not achieve the delivery of failed short messages. On the other hand, the IP-SM-GW needs to cooperate with multiple network elements such as HLR/HSS and MME to perform the terminal reachability subscription to the HLR/HSS, thus increasing the processing load of these network elements, which is not conducive to processing resources. Optimization.

The embodiments of the present disclosure will be further described in detail below with reference to the accompanying drawings.

Example 1:

Because the short message center reminder after the short message delivery failure depends on the HLR/HSS to provide the IP-SM-GW with the service that the terminal can reach the subscription, the short message center reminds the HLR/HSS to support the reachability subscription, and Because the HLR/HSS needs to interact and cooperate with the MME when providing the reachable subscription, it needs to occupy a large amount of processing resources and communication resources, so it is not conducive to optimal configuration of resources. For these problems, this example provides a short message center reminding method, please refer to the flow chart of the short message center reminding method shown in FIG. 3:

S302. The short message gateway determines that the receiving terminal is reachable based on the registration of the receiving terminal by the application server.

Suppose the sending terminal sends a short message to the receiving terminal, "Do you have time on Saturday?", after the sending terminal chooses to send, the short message will be first transmitted to the short message center, and the short message center will arrange to receive it. The short message gateway on the terminal side delivers the short message. If the short message is delivered by the short message gateway, the receiving terminal is turned off or the communication quality is extremely poor and cannot be connected, the delivery of the short message gateway will fail. Under normal circumstances, a short message delivery failure means that the short message is to be re-delivered.

Therefore, the short message gateway in this example records the failed short message for the failed short message, that is, the failed delivery record of the short message to be re-submitted, so that the corresponding receiving terminal is re-submitted again when the corresponding receiving terminal is reachable. Delivery of the message. The failed delivery record stored by the short message gateway can indicate which short message is to be re-invested without recording the specific content of the failed short message, because the specific content of the failed short message is recorded by the short message center.

Although the failed delivery record is required by the short message gateway to trigger the short message center reminder, that is, the failed delivery record is required by the short message gateway itself, so in theory, the failed delivery record is stored on the short message gateway, but due to one After the terminal enters the power-on state from the power-off state, it will register once on the AS. The registration process is called initial registration. When the terminal is initially registered, the data stored locally for the terminal by the SMS gateway will be cleared. Before the re-posting of the short message to be re-delivered, the failed delivery record for the short message to be re-invested is required, so the short message gateway cannot store the failed delivery record locally, at least the failed delivery record. Stored in a place that won't be arbitrarily cleared. So, in this example, the SMS Gateway will store a failed delivery record on the HLR/HSS. In addition to the HLR/HSS, the SMS gateway can store the failed delivery record to other external storage as long as the data in the storage location is not deleted as the terminal is turned off.

In addition, since the short message gateway itself needs to use the failed delivery record, the short message gateway does not clear the locally stored data for the receiving terminal as long as the receiving terminal does not temporarily register on the application server, so in this example In the middle, the failed delivery record can also be stored locally in the SMS gateway, so that as long as the receiving terminal does not perform the initial registration, the SMS gateway can obtain the local delivery record when it obtains the failed delivery record, as opposed to in any case. Obtaining a failed delivery record from an external storage location can well avoid the problem of taking a large amount of time to obtain a failed delivery record from an external storage location.

The timing at which the short message gateway re-delivers the re-sending short message is not randomly determined by the short message center or the short message gateway, but is determined by the receiving terminal. Only when the receiving terminal is reachable, the short message gateway will trigger the short message center reminder to notify the short message center to reschedule the delivery of the failed short message. In this example, the short message gateway can directly obtain the information that the terminal can reach from the AS (Application Server) instead of receiving the terminal reachability subscription to the HLR/HSS. After the receiving terminal enters the power-on state from the power-off state, the initial registration is performed on the AS, and the receiving terminal is available at this time. In addition, after the initial registration between the receiving terminal and the application server, the application server is required to perform a refresh registration at intervals to notify the application server that it is currently reachable, so the short message gateway can receive the terminal on the AS. Initial registration and refresh registration to understand the reachable information of the receiving terminal.

S304. The short message gateway acquires a failed delivery record stored for the short message to be re-submitted by the receiving terminal.

When the short message gateway knows that the receiving terminal is reachable according to the registration of the receiving terminal on the AS, the short message gateway can obtain the failed delivery record stored for the short message to be re-submitted by the receiving terminal. For example, if the short message gateway only stores the failed delivery record of the receiving terminal on the external memory, or the registration of the current receiving terminal on the AS belongs to the initial registration, the short message gateway can directly obtain the failed delivery record to the external memory. If the current receiving terminal refreshes the registration when registering on the AS, and the terminal not only stores the failed delivery record in the external memory, but also stores the failed delivery record locally, the short message gateway can obtain the failed delivery record locally. The SMS gateway stores the failed delivery record locally, which can be performed in at least one of the following two situations:

First, when the short message gateway stores the failed delivery record to an external memory, such as HLR/HSS, etc., the short message gateway also stores the failed delivery record locally. If the failed delivery record acquired by the short message gateway after receiving the terminal registration is stored locally in this way, the receiving terminal does not perform the initial registration after the failed delivery record is stored locally.

Secondly, after generating the failed delivery record, the short message gateway only stores the failed delivery record on the external storage, but after the receiving terminal first registers or refreshes the registration, the short message gateway acquires the failure for the receiving terminal from the external storage. After the record is posted, the obtained failed delivery record will be stored locally.

Therefore, after the short message gateway stores the failed delivery record to the local by any of the above two methods, after the receiving terminal completes the refresh registration on the AS, the short message gateway can obtain the failed delivery record locally.

S306. The short message gateway triggers the short message center reminder according to the failed delivery record.

After the SMS gateway obtains the failed delivery record, it will trigger the short message center reminder according to the failed delivery record. The following describes the process of triggering the short message center reminder by the short message gateway in this example with reference to FIG. 4:

S402. The short message gateway sends a MAP-Ready-for-SM message to the HLR/HSS.

MAP-Ready-for-SM is a message defined by the MAP about short message service, which is usually sent by the short message gateway to the HLR when the receiving terminal can receive the short message. When the HLR/HSS receives the MAP-Ready-for-SM message sent by the SMS gateway, it usually sends a corresponding response message to the SMS gateway, "MAP-Ready-for-SM-rsp".

S404. The HLR/HSS sends a MAP-Alert-Service-Center message to the short message center.

MAP-Alert-Service-Center is a short message center reminder message, which is used to inform the short message center that the receiving terminal is currently reachable, and can arrange to re-deliver the short message to be re-submitted to the receiving terminal. When the short message center receives the MAP-Alert-Service-Center message, it also sends "MAP-Alert-Service-Center-rsp" to the HLR/HSS as a response.

In this example, after the short message delivery failure, the short message gateway generates a failed delivery record for the short message, and stores the failed delivery record, and learns the receiving terminal when it registers with the corresponding receiving terminal on the application server. When reachable, the failed delivery record can be obtained, and the reminder to the short message center is triggered according to the failed delivery record, and the short message center is arranged to arrange the re-delivery of the re-investment short message. In this example, the SMS gateway can directly learn the reachable information of the receiving terminal from the application server without subscribing to the HLR/HSS, so the HLR/HSS is not required to support the reachability subscription, and the HLR/HSS is reduced. Claim. More importantly, in this example, the short message gateway understands that the receiving terminal is reachable in a simple manner, and can be implemented without the cooperation of the HLR/HSS and the MME, thereby reducing the requirements for system processing resources and communication resources.

Example two:

In order to make the advantages and details of the short message center reminding method in the present disclosure more clear, this example continues to introduce the short message center reminding method based on the first example, as shown in FIG. 5:

S502. The short message gateway stores a failed delivery record for the short message after the short message delivery fails.

In this example, the short message gateway may be an IP-SM-GW, ie an internet protocol short message gateway. The SMS gateway can store the failed delivery record on both local and external storage. Assuming that the external memory is the memory on the HLR/HSS, the following describes the process of storing the failed delivery record to the HLR/HSS by the SMS gateway:

Since the short message gateway sends a PUR (Profile Update Request) to the HLR/HSS, in this example, the short message gateway and the HLR/HSS pre-arrange a setting of a delivery-fail flag in the PUR, that is, a failure identifier. Used by the SMS gateway to notify the HLR/HSS that a short message delivery failed. In the subsequent process, when the SMS gateway wants to obtain the failed delivery record, the HLR/HSS can directly carry the delivery-fail flag in the user data record and return it to the SMS gateway.

Of course, since the short message delivery, the short message gateway will send a MAP-REPORT-SM-DELIVERY-STATUS message to the HLR/HSS, that is, a short message delivery status report. After the short message delivery failure, the short message delivery status report also includes the relevant information of the short message delivery failure. Therefore, the short message gateway can also send the short delivery delivery status report to the HLR/HSS to store the failed delivery record. HLR/HSS. In this example, the short message gateway will send a PUR carrying the failure identifier to the HLR/HSS, and will also send a short message delivery status report.

S504. When it is detected that the receiving terminal corresponding to the to-be-re-transmitted short message is registered on the AS, the short message gateway acquires the failed delivery record.

After the short message gateway determines that the receiving terminal registers on the application server AS, the short message gateway can obtain the pre-stored failed delivery record. If the receiving terminal performs the initial registration, the short message gateway obtains the failed delivery record from the external storage location such as the HLR/HSS, and stores the obtained failed delivery record locally, in case the current short message retransmission is unsuccessful, and the subsequent receiving is performed. When the terminal performs refresh registration, the failed delivery record can be obtained directly from the local, thereby saving the time for obtaining the failed delivery record.

If the receiving terminal performs refresh registration on the application server, since the short message gateway previously stores the failed delivery record locally in this example, the short message gateway can directly obtain the failed delivery record from the local.

S506. The short message gateway triggers the short message center reminder according to the failed delivery record.

The process of the SMS gateway triggering the short message center reminder based on the failed delivery record has been described in detail in Example 1, and will not be described here.

S508. The short message gateway determines whether the short message to be re-sent is successfully delivered.

When the short message center controls the short message gateway to re-deliver the short message, there will only be two kinds of results. One is that the short message to be re-sent is successfully delivered, and the other is naturally the re-sending of the short message. Delivery failed. If the result of the determination is YES, then S510 is executed, otherwise the re-sending short message is to be delivered, so the process goes to S504.

S510. The short message gateway clears the failed delivery record for the short message to be re-sent.

Since the short message gateway obtains the failed delivery record and re-delivers the corresponding failed short message when the receiving terminal registers, the short message will continue to send the short message to the receiving user after the successful retransmission of the short message. This causes a poor user experience and wastes communication resources. In this example, after the re-investment of the short message to be re-successful is successful, the short message gateway will clear the failed delivery record for the short message. The SMS gateway clears the failed delivery records on all storage locations, including local and external storage.

The short message center reminding method provided in this example can store the failed delivery record of the short message for delivery failure to the HLR/HSS by using the configuration file update request carrying the failure identifier to the HLR/HSS, and utilize the HLR/HSS, etc. The external memory does not clear the advantage of the failed delivery record due to the change of the state of the receiving terminal, so that the short message gateway can obtain the failed delivery record for the receiving terminal to re-send the short message even after the initial registration of the receiving terminal, thereby the failure short message. Make a heavy shot. In addition, the short message center reminding method provided by the example also deletes the failed delivery record of the short message stored on the local and external memory after the successful retransmission of the failed short message, so as to avoid the SMS gateway always has a short delivery success. Messages are delivered repeatedly, wasting communication resources and reducing user experience.

Example three:

This example is further introduced to the short message center reminder with a specific example. In this example, the short message gateway is assumed to be an IP-SM-GW. The IP-SM-GW can be deployed as an independent network element or deployed with other logical network elements. Together. In this example, the IP-SM-GW is deployed on the application server, so that the receiving terminal registers with the application server, which is equivalent to registering with the IP-SM-GW. It is worth noting that the "equivalent" mentioned here is essentially from the perspective of physical entities. It is the internal network element that omits the application server and the internal logic of IP-SM-GW. It is not It is exactly the same.

The following describes the three processes of storing the failed delivery record, the short message center reminder at the time of initial registration, and the short message center reminder at the time of refreshing registration. Please refer to the interaction of storing the failed delivery record shown in FIG. 6 first. Figure:

S601. The IP-SM-GW sends a short message delivery status report to the HLR/HSS.

S602: The IP-SM-GW saves the failed delivery record locally;

S603. The IP-SM-GW sends a PUR message to the HLR/HSS.

S604. The HLR/HSS sends a PUA message to the IP-SM-GW.

In this example, the IP-SM-GW sends a PUR message to the HLR/HSS carrying a delivery-fail flag, which can indicate to the HLR/HSS that the short message delivery failed. Of course, the HLR/HSS can also know the delivery result of the short message from the short message delivery status report. The IP-SM-GW will also send a PUR message carrying the failure identifier to the HLR/HSS if it can understand the short message delivery result in the short message delivery status report. This is mainly because the short message delivery status report is present. As specified in the communication protocol, the IP-SM-GW will send it to the HLR/HSS regardless of the success or failure of the delivery of the short message. In this example, when the subsequent IP-SM-GW obtains the failed delivery record, it is only necessary to know which short messages failed to be delivered, and does not care about the short messages that are successfully delivered. Therefore, if the IP-SM-GW only sends a short message delivery status report to the HLR/HSS, the HLR/HSS may also need to filter according to the received message to provide a failed delivery record to the IP-SM-GW, therefore, in order to avoid the HLR. The /HSS filters according to the short message delivery status report. In this example, the IP-SM-GW sends a PUR message carrying the failure identifier to the HLR/HSS after the short message delivery failure.

The three processes S601, S602, and S603 do not have strict timing constraints. The SMS gateway can select the execution sequence according to its actual needs. Since the PUA message sent by the HLR/HSS to the IP-SM-GW is a response to the PUR message sent by the IP-SM-GW, S604 must be after S603.

Please refer to the interaction diagram of the short message center reminder of the IP-SM-GW shown in FIG. 7 according to the initial registration of the receiving terminal on the AS:

S701. The receiving terminal initiates an initial registration with the AS.

Since the AS is deployed with the IP-SM-GW, that is, the IP-SM-GW is deployed to the application server, some functions of the IP-SM-GW can be assumed by the application server. Therefore, when the receiving terminal initiates registration with the AS, the IP-SM-GW can immediately know the information.

S702. The IP-SM-GW sends a user data request UDR to the HLR/HSS.

S703. The HLR/HSS sends a user data response UDA to the IP-SM-GW.

The UDR (User Data Request) enables the HLR/HSS to send the stored user data to the IP-SM-GW. Among the UDAs sent by the HLR/HSS to the IP-SM-GW, the IP-SM-GW is included. The delivery-fail flag pre-sent to the HLR/HSS.

S704. The IP-SM-GW sends a subscription notification request SNR to the HLR/HSS.

S705. The HLR/HSS sends a subscription notification request SNA to the IP-SM-GW.

The process of sending the SNR (Subscribe Notification Request) and receiving the SNA (Subscribe Notification Answer) is the process that the existing terminal registers on the application server, and is not the short message center reminder in this example. The necessary process.

S706. The IP-SM-GW sends a 200 OK message to the receiving terminal.

After the IP-SM-GW receives the user data response SNA sent by the HLR/HSS, it indicates that the initial registration of the receiving terminal on the application server has succeeded, so the IP-SM-GW sends a 200 OK message to the receiving terminal side as the receiving terminal. Send a response to the registration request.

S707. The IP-SM-GW sends a MAP-Ready-for-SM message to the HLR/HSS.

S708. The HLR/HSS sends a MAP-Ready-for-SM-rsp message to the IP-SM-GW.

The IP-SM-GW sends a MAP-Ready-for-SM message to the HLR/HSS to inform the HLR/HSS to perform a MAP-Alert-Service-Center alert to the short message center, while the MAP-Ready-for-SM-rsp is The response message of the HLR/HSS to the IP-SM-GW after receiving the MAP-Ready-for-SM.

S709. The HLR/HSS sends a MAP-Alert-Service-Center message to the short message center.

S710: The short message center sends a MAP-Alert-Service-Center-rsp message to the HLR/HSS.

The MAP-Alert-Service-Center message sent by the HLR/HSS to the short message center can be used to remind the short-message center that the current receiving terminal is reachable, and can re-deliver the short message that failed to be delivered before. After receiving the MAP-Alert-Service-Center, the short message center will respond to the HLR/HSS with a MAP-Alert-Service-Center-rsp message as a response.

The following assumes that the short message center reschedules the delivery of the short message that was originally failed to be delivered and the delivery result is successful. The IP-SM-GW also deletes the failed delivery record for the short message:

S711. The IP-SM-GW deletes the failed delivery record of the local storage.

S712. The IP-SM-GW sends a PUR message that does not carry the failure identifier to the HLR/HSS.

S713. The HLR/HSS sends a PUA message to the IP-SM-GW.

In Fig. 7, S712 and S713 are for clearing the failed delivery record stored on the HLR/HSS, and S711 is for clearing the failed delivery record stored locally at the IP-SM-GW. However, the IP-SM-GW may first clear the failed delivery record of the local storage, or may first clear the failed delivery record stored on the HLR/HSS. Therefore, the S711 may be before S712 or after S713.

Please refer to FIG. 8 for an interaction diagram of the short message center reminder by the IP-SM-GW according to the initial registration of the receiving terminal on the AS:

S801. The receiving terminal initiates a refresh registration to the AS.

S802. The AS returns a 200 OK message to the receiving terminal.

Since the refresh registration does not cause the IP-SM-GW to clear the locally stored data of the receiving terminal, in this example, the IP-SM-GW does not acquire user data from the HLR/HSS after refreshing the registration, and the AS receives the data. After the registration is refreshed, a 200 OK message can be directly returned to the receiving terminal to respond.

S803. The IP-SM-GW sends a MAP-Ready-for-SM message to the HLR/HSS.

S804. The HLR/HSS sends a MAP-Ready-for-SM-rsp message to the IP-SM-GW.

The IP-SM-GW sends a MAP-Ready-for-SM message to the HLR/HSS according to the locally stored failed delivery record to notify the HLR/HSS to perform a MAP-Alert-Service-Center reminder to the short message center, and MAP-Ready- The for-SM-rsp is a response message to the IP-SM-GW after the HLR/HSS receives the MAP-Ready-for-SM.

S805. The HLR/HSS sends a MAP-Alert-Service-Center message to the short message center.

S806. The short message center sends a MAP-Alert-Service-Center-rsp message to the HLR/HSS.

In this example, if the short message center arranges the IP-SM-GW to re-deliver the failed short message and delivers it successfully, the IP-SM-GW clears the failed delivery record stored locally and on the HLR/HSS, the process and the initial The process after registration is the same and will not be described here. If the delivery fails, it continues to wait for the receiving terminal to refresh registration or initial registration on the AS.

The short message center reminding method provided by the embodiment of the present disclosure, the IP-SM-GW is deployed together with the application server, so some functions of the two can be jointly assumed. When the receiving terminal registers with the application server, the IP-SM-GW can By quickly obtaining the registration message, the IP-SM-GW can understand that the receiving terminal accessibility subscription to the HLR/HSS can obtain the time that the receiving terminal can reach more quickly and reduce the processing resources of the system. The occupation of communication resources is conducive to the optimal configuration of resources.

Example four:

The present example provides a short message gateway. Referring to FIG. 9 , the short message gateway 90 includes a recording module 902 , a determining module 904 , an obtaining module 906 , and a reminding module 908 .

Suppose the sending terminal sends a short message to the receiving terminal, "Do you have time on Saturday?", after the sending terminal chooses to send, the short message will be first transmitted to the short message center, and the short message center will arrange to receive it. The short message gateway 90 on the terminal side delivers the short message. If the short message is sent by the short message gateway 90, the receiving terminal is turned off or the communication quality is extremely poor and cannot be connected, the delivery of the short message gateway 90 will fail. Under normal circumstances, a short message delivery failure means that the short message is to be re-delivered.

Therefore, the recording module 902 in this example records the failed delivery message for the failed short message, that is, the failed delivery record of the short message to be re-submitted when the corresponding receiving terminal is reachable. Delivery of short messages. The failed delivery record stored by the recording module 902 can characterize which short message is to be re-invested without recording what the specific content of the failed short message is because the specific content of the failed short message is recorded by the short message center.

Although the failed delivery record is required by the reminder module 908 to trigger the short message center reminder, that is, the failed delivery record is required by the short message gateway 90 itself, so in theory, the failed delivery record is stored on the short message gateway 90. However, after a terminal enters the power-on state from the power-off state, it will register once on the AS. The registration process is called initial registration. When the terminal is initially registered, the data stored locally by the SMS gateway 90 for the terminal will be cleared. Drop it. Before the re-posting of the short message to be re-delivered, the failed delivery record for the short message to be re-sent is required, so the recording module 902 cannot store the failed delivery record locally, at least the failed delivery record. Stored in a place that won't be arbitrarily cleared. Therefore, in this example, the logging module 902 will store a failed delivery record on the HLR/HSS. In addition to the HLR/HSS, the logging module 902 can also store the failed posting record on other external memory as long as the data in the storage location is not deleted as the terminal is turned off.

In addition, since the short message gateway 90 itself needs to use the failed delivery record, the short message gateway 90 does not clear the locally stored data for the receiving terminal as long as the receiving terminal temporarily does not perform the initial registration on the application server, so In this example, the recording module 902 can also store the failed delivery record in the local area of the short message gateway 90. Thus, as long as the receiving terminal does not perform the initial registration, the obtaining module 906 can obtain the local delivery when the failed delivery record is acquired. The problem of obtaining a failed delivery record from an external storage location in any case can well avoid the problem of taking a large amount of time to obtain a failed delivery record from an external storage location.

The timing at which the short message gateway 90 re-delivers the re-sending short message is not determined by itself or the short message center, but is determined by the receiving terminal. Only when the receiving terminal is reachable, the reminding module 908 triggers the short message center reminder to notify the short message center to reschedule the delivery of the failed short message. In this example, the determining module 904 can directly obtain the information reachable by the receiving terminal from the AS (Application Server) instead of receiving the terminal reachability subscription to the HLR/HSS. After the receiving terminal enters the power-on state from the power-off state, the initial registration is performed on the AS, and the receiving terminal is available at this time. In addition, after the initial registration between the receiving terminal and the application server, the application server is required to perform a refresh registration at intervals to notify the application server that it is currently reachable, so the determining module 904 can receive the terminal on the AS. The initial registration is to refresh the registration to know the reachable information of the receiving terminal.

When the determining module 904 knows that the receiving terminal is reachable according to the registration of the receiving terminal on the AS, the obtaining module 906 can acquire the failed posting record stored for the receiving terminal to be re-sending the short message. For example, if the recording module 902 stores the failed delivery record of the receiving terminal only on the external memory, or the registration of the current receiving terminal on the AS belongs to the initial registration, the obtaining module 906 can directly obtain the failed delivery record to the external memory. If the current receiving terminal refreshes the registration at the time of registration on the AS, and the terminal not only stores the failed posting record on the external memory in advance, but also stores the failed delivery record locally, the obtaining module 906 can obtain the failed delivery record locally. Recording module 902 storing the failed delivery record locally can be done in both cases:

First, when the recording module 902 stores the failed posting record to an external memory, such as HLR/HSS, etc., the failed posting record is also stored locally. If the failed delivery record acquired by the acquisition module 906 after receiving the terminal registration is stored locally in this manner, the receiving terminal has not made the initial registration after the failed delivery record is stored locally.

Second, the recording module 902 stores only the failed delivery record on the external memory after generating the failed delivery record, but after the receiving terminal first registers or refreshes the registration, the obtaining module 906 acquires from the external memory for the receiving terminal. After the failed delivery record, the recording module 902 will store the obtained failed delivery record to the local.

Therefore, after the recording module 902 stores the failed posting record to the local by at least one of the above two methods, after the determining module 904 learns that the receiving terminal completes the refresh registration on the AS, the obtaining module 906 can obtain the local obtaining. Failed to post records.

After the acquisition module 906 obtains the failed delivery record, the short message center reminder is triggered according to the failed delivery record. The reminder module 908 can trigger a short message center reminder by sending a MAP-Ready-for-SM to the HLR/HSS, which is a message defined by the MAP about the short message service, which is usually received by the short message gateway. It can be sent to the HLR when it receives a short message. When the HLR/HSS receives the MAP-Ready-for-SM message sent by the reminder module 908, a corresponding response message "MAP-Ready-for-SM-rsp" is usually also fed back to the reminder module 908.

After receiving the MAP-Ready-for-SM, the HLR/HSS sends a short message center reminder message to the short message center, that is, the MAP-Alert-Service-Center message, which is used to inform the short message center that the receiving terminal is currently reachable, and can arrange the pair. The receiving terminal performs re-delivery of the short message to be re-submitted. When the short message center receives the MAP-Alert-Service-Center message, it also sends "MAP-Alert-Service-Center-rsp" to the HLR/HSS as a response.

In this example, after the short message delivery failure, the short message gateway generates a failed delivery record for the short message, and stores the failed delivery record, and learns the receiving terminal when it registers with the corresponding receiving terminal on the application server. When reachable, the failed delivery record can be obtained, and the reminder to the short message center is triggered according to the failed delivery record, and the short message center is arranged to arrange the re-delivery of the re-investment short message. In this example, the SMS gateway can directly learn the reachable information of the receiving terminal from the application server without subscribing to the HLR/HSS, so the HLR/HSS is not required to support the reachability subscription, and the HLR/HSS is reduced. Claim. More importantly, in this example, the short message gateway understands that the receiving terminal is reachable in a simple manner, and can be implemented without the cooperation of the HLR/HSS and the MME, thereby reducing the requirements for processing resources and communication resources of the system.

Example five:

In order to make the advantages and details of the short message center reminding method in the present disclosure clearer, the present example continues to introduce the short message gateway based on the fourth example. Referring to FIG. 10, the short message gateway 90 further includes a clearing module 910.

The logging module 902 stores a failed posting record for the short message after the short message delivery failure. In this example, the short message gateway 90 may be an IP-SM-GW, ie an internet protocol short message gateway. The logging module 902 can store the failed posting records on both local and external storage. Assuming that the external memory is a memory on the HLR/HSS, the following describes the process by which the logging module 902 stores the failed posting record to the HLR/HSS:

Since the short message gateway 90 sends a PUR (Profile Update Request) to the HLR/HSS, in this example, the recording module 902 and the HLR/HSS pre-agreed to set a delivery-fail flag in the PUR, that is, the failure The identifier is used by the recording module 902 to notify the HLR/HSS that a short message delivery has failed. In the subsequent process, when the obtaining module 906 wants to obtain the failed delivery record, the HLR/HSS can directly carry the delivery-fail flag in the user data record and return it to the obtaining module 906.

Of course, since the short message delivery, the short message gateway 90 will send a MAP-REPORT-SM-DELIVERY-STATUS message to the HLR/HSS, that is, a short message delivery status report. After the short message delivery failure, the short message delivery status report also includes the relevant information of the short message delivery failure, so the recording module 902 can also send the short message delivery status report to the HLR/HSS to store the failed delivery record. Go to HLR/HSS. In this example, the short message gateway 90 will both send a PUR carrying a failure identifier to the HLR/HSS and a short message delivery status report.

After determining that the receiving terminal is registered on the application server AS, the obtaining module 906 can acquire the pre-stored failed posting record. If the receiving terminal performs the initial registration, the obtaining module 906 obtains the failed delivery record from the external storage location such as the HLR/HSS, and stores the obtained failed delivery record locally, in case the current short message re-investment is unsuccessful, and subsequent When the receiving terminal performs refresh registration, the failed delivery record can be obtained directly from the local, thereby saving the time for obtaining the failed delivery record.

If the receiving terminal performs refresh registration on the application server, since the recording module 902 previously stored the failed posting record locally, the obtaining module 906 can directly obtain the failed posting record locally.

The process of the reminder module 908 triggering the short message center reminder according to the failed delivery record has been described in more detail in the example 1, and will not be described here.

After the short message center controls the short message gateway 90 to re-submit the re-sending short message, there are only two kinds of results, one is that the short message to be re-sent is successfully delivered, and the other is naturally to be re-send the short message. The re-delivery failed. If the short message delivery is to be successfully posted, the clearing module 910 clears the failed delivery record for the short message to be re-submitted.

Since the obtaining module 906 is sure to obtain the failed delivery record when the receiving terminal registers with the application server, and notifies the reminding module 908 to perform the re-delivery of the corresponding failed short message, so in order to avoid the short message re-delivery after the original delivery fails, the short message gateway succeeds. 90 will continue to send SMS, causing a poor user experience for the receiving user, wasting communication resources. In this example, after the re-investment of the short message to be re-successful, the clearing module 910 will clear the failure for the short message. Delivery record. The clearing module 910 is to clear the failed posting record on all storage locations including the local and external storage.

The short message gateway provided in this example can store the failed delivery record of the short message for delivery failure to the HLR/HSS by sending a configuration file update request carrying the failure identifier to the HLR/HSS, and using an external memory such as HLR/HSS. The advantage of the failed delivery record is cleared because the status of the receiving terminal is changed, so that the short message gateway can obtain the failed delivery record for the receiving terminal to re-send the short message even after the initial registration of the receiving terminal, thereby re-investing the failed short message. . In addition, the short message center reminding method provided by the example also deletes the failed delivery record of the short message stored on the local and external memory after the successful retransmission of the failed short message, so as to avoid the SMS gateway always has a short delivery success. Messages are delivered repeatedly, wasting communication resources and reducing user experience.

Example six:

The short message gateway in the foregoing embodiments may be deployed as a single network element on a physical entity, or may share a physical entity with other logical network elements. In this example, the short message gateway is deployed on the server. The hardware structure of the short message gateway in the embodiments of the present disclosure is introduced in conjunction with FIG. 11 :

The server 100 includes at least an input/output (IO) bus 110, a processor 140, a memory 130, a memory 120, and a communication device 150.

Among them, the input/output (IO) bus 110 is respectively connected to other components of the server to which it belongs (the processor 140, the memory 130, the memory 120, and the communication device 150), and provides transmission lines for other components.

The computer 120 can store a computer program for implementing the short message center reminding method. When the server 100 executes the short message center reminding method, the processor 140 reads the code from the memory 120 to compile and control each component to cooperate with each other. The short message center reminds each process in the method.

When the short message gateway is to store the failed delivery record locally, the memory 130 may store the failed delivery record under the control of the processor 140.

The processor 140 typically controls the overall operation of the server to which it belongs. For example, the processor 140 performs operations such as calculations and confirmations. The processor 140 may be a central processing unit (CPU).

Communication device 150 typically includes one or more components that permit radio communication between a server to which it belongs and a wireless communication system or network. When the short message gateway is to interact with the application server or the HLR/HSS, the communication device 150 assumes the corresponding communication task under the control of the processor 140.

The functions of the recording module, the determining module, the obtaining module, and the clearing module in the short message gateway provided by the example 4 and the example 5 can be implemented by the processor 140 and the memory 130 and the communication device 150. The function of the reminder module can be implemented by both the processor and the communication device. After the short message delivery failure, the processor 140 may store the failed delivery record in the local memory 130 while controlling the communication device 150 to store the failed delivery record in an external memory, such as to the HLR/HSS. When the receiving terminal performs initial registration or refresh registration on the application server AS, the communication device 150 can understand that the receiving terminal is available through interaction with the application server. If the registration of the receiving terminal belongs to the initial registration, the processor 140 may control the communication device 150 to send a request message to an external memory such as the HLR/HSS to acquire the previously stored failed storage record. After obtaining the failed delivery record, the processor 140 controls the memory 130 to store the acquired failed delivery record. And controlling the communication device 150 to interact with the HLR/HSS according to the failed delivery record, thereby causing the HLR/HSS to send a MAP-Alert-Service-Center message to the short message center. If the registration of the receiving terminal belongs to the refresh registration, the processor 140 may directly obtain the failed delivery record from the local storage 130, and notify the communication device 150 to interact with the HLR/HSS, and let the HLR/HSS send the MAP-Alert-Service to the short message center. -Center message completes the short message center reminder.

In addition, the short message gateway in the foregoing example may also be deployed on the same server as the application server. In this case, the receiving terminal interacts with the communication device of the application server to implement registration, which is essentially interacting with the short message gateway, so the short message gateway The information that is reachable by the receiving terminal can be directly obtained, which saves access time and reduces resource waste.

Embodiments of the present disclosure also provide a computer readable storage medium storing computer executable instructions that, when executed by a processor, implement the short message center reminder method described above.

Those of ordinary skill in the art will appreciate that all or some of the steps, systems, and functional blocks/units of the methods disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be composed of several physical The components work together. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on a computer readable medium, which may include computer storage media (or non-transitory media) and communication media (or transitory media). As is well known to those of ordinary skill in the art, the term computer storage medium includes volatile and nonvolatile, implemented in any method or technology for storing information, such as computer readable instructions, data structures, program modules or other data. Sex, removable and non-removable media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridge, magnetic tape, magnetic disk storage or other magnetic storage device, or may Any other medium used to store the desired information and that can be accessed by the computer. Moreover, it is well known to those skilled in the art that communication media typically includes computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and can include any information delivery media. .

The above content is a further detailed description of the embodiments of the present disclosure in conjunction with the specific embodiments, and the specific implementation of the present disclosure is not limited to the description. It will be apparent to those skilled in the art that the present invention is to be construed as being limited to the scope of the present disclosure.

Industrial applicability

According to the short message center reminding method and the short message gateway and the computer storage medium provided by the embodiment of the present disclosure, the short message gateway determines that the receiving terminal is reachable based on the registration of the receiving terminal by the receiving terminal, and acquires a failure to store the short message to be received by the receiving terminal. The record is posted, and then the short message center reminder is triggered according to the failed delivery record to inform the short message center to resend the short message to be re-submitted to the receiving terminal. The solution provided by the embodiment of the present disclosure utilizes the short message gateway to directly know the registration of the receiving terminal on the application server. Therefore, the short message gateway can directly learn the receiving terminal without subscribing to the HLR/HSS subscription terminal reachability. When is it possible? When the short message gateway determines that the receiving terminal is reachable, it acquires a pre-recorded stored failed posting record for the receiving terminal, and triggers a short message center reminder according to the failed delivery record. Since the HLR/HSS does not provide terminal reachability in the process of implementing the short message center reminder, the functional requirements of the HLR/HSS are reduced, and the application scenario is wider than the existing solution; When the HLR/HSS does not interact and cooperate with the MME, the communication resources and processing resources of the system are saved, which is beneficial to the optimal configuration of resources.

Claims

A short message center reminder method, including:

The short message gateway determines that the receiving terminal is reachable based on the registration of the receiving terminal by the application server;

The short message gateway acquires a failed delivery record stored for the short message to be re-submitted by the receiving terminal, and the failed delivery record is generated when the short message gateway fails to deliver the short message to be re-sent to the receiving terminal;

The short message gateway triggers the short message center reminder according to the failed delivery record to instruct the short message center to resend the to-be-resubmitted short message to the receiving terminal.
The short message center reminding method according to claim 1, wherein the method further comprises:

After the re-delivery of the short message to be re-sent, the short message gateway clears the failed delivery record for the short message to be re-sent.
The short message center reminding method according to claim 1 or 2, wherein the short message gateway further comprises: before the receiving terminal determines that the receiving terminal is reachable based on the registration of the application server, the short message gateway records the failed delivery record. Stored on external storage.
The short message center reminding method according to claim 3, wherein the storing, by the short message gateway, the failed posting record to an external memory comprises:

The short message gateway carries a failure identifier in the configuration file update request sent to the home location register/home subscriber network to notify the home location register/home subscriber server that the delivery of the short message fails, and the The failed delivery record of the short message is stored on the home location register/home subscriber network.
The short message center reminding method according to claim 3, wherein the short message gateway, based on the registration of the receiving terminal on the application server, determines that the receiving terminal is reachable, and the obtaining the failed delivery record comprises:

The short message gateway obtains the failed delivery record on the external memory when the receiving terminal determines that the receiving terminal is reachable according to the initial registration of the receiving terminal on the application server.
The short message center reminding method according to claim 3, wherein the method further comprises: the short message gateway storing the failed delivery record to the external memory while storing the failed delivery record to the local;

or,

After the SMS gateway obtains the failed delivery record from the external storage, the obtained failed delivery record is stored locally;

or,

The short message gateway stores the failed delivery record to the local while storing the failed delivery record to the local storage, and after the short message gateway obtains the failed delivery record from the external storage, the acquired location The failed delivery record is stored locally.
The short message center reminding method according to claim 6, wherein the short message gateway, based on the registration of the receiving terminal on the application server, determines that the receiving terminal is reachable, and the obtaining the failed delivery record comprises:

The short message gateway obtains the failed delivery record locally when the receiving terminal determines that the receiving terminal is reachable according to the refresh registration of the receiving terminal on the application server.
A short message gateway, including:

a recording module, configured to store a failed delivery record for the short message to be re-sent after failing to deliver the short message to the receiving terminal;

Determining a module, configured to determine that the receiving terminal is reachable based on a registration of the receiving terminal at the application server;

An obtaining module, configured to acquire a failed delivery record stored for the short message to be re-submitted by the receiving terminal;

The reminding module is configured to trigger the short message center reminder according to the failed delivery record to instruct the short message center to resend the to-be-resubmitted short message to the receiving terminal.
The short message gateway of claim 8 wherein said recording module is arranged to store said failed posting record on an external memory.
The short message gateway according to claim 9, wherein the obtaining module is set to be from the outside when the determining module determines that the receiving terminal is reachable according to the initial registration of the receiving terminal on the application server The failed delivery record is obtained on the memory.
A computer readable storage medium storing computer executable instructions that, when executed by a processor, implement the method of any of claims 1-7.