Short message disaster recovery system and method, SMSF network element, registration center and storage medium

Abstract

The invention provides a short message disaster recovery method, and relates to the technical field of communication. According to the specific implementation scheme, the method comprises the steps of firstly receiving a to-be-processed short message, then sending an information query request to a registration center under the condition that context information associated with an identifier of a terminal device is not included, and finally forwarding the short message based on the context information under the condition that the context information sent by the registration center is received. Therefore, by introducing the registration center, the context information of the user is efficiently recovered, and the processing efficiency of the short message disaster recovery method is also improved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a short message disaster recovery system, method, SMSF network element, registration center and storage medium. Background Art

[0002] In the relevant communication system, the core network evolution adopts microservice architecture, and the cross-region active-active disaster recovery method is used between various network functions to restore data. The existing disaster recovery capability is completed through the signaling process. In the cross-region scenario, short message network elements need to interact with signaling processes across regions multiple times to restore data, which makes the business process complex and the business processing delay large. Summary of the invention

[0003] The first aspect of the present application proposes a short message disaster recovery system, characterized in that it includes: a short message service center SMSC, a registration center and multiple network element groups, wherein each network element group includes a short message service function SMSF network element, an access and mobility management function AMF network element and a unified data management UDM network element;

[0004] Wherein, the registration center is connected to the SMSC and the SMSF in each of the network element groups respectively;

[0005] The SMSC is respectively connected to the UDM in each of the network element groups;

[0006] The SMSF in each of the network element groups is respectively connected to the AMF and UDM in the same network element group.

[0007] The second aspect of the present application provides a short message disaster recovery method, which is executed by a short message service function SMSF network element, and includes:

[0008] Receiving a short message to be processed, wherein the short message includes an identification of a terminal device;

[0009] In the case where the context information associated with the identifier of the terminal device is not included, sending an information query request to a registration center, wherein the query request includes the identifier of the terminal device;

[0010] When the context information sent by the registration center is received, the short message is forwarded based on the context information.

[0011] Optionally, the receiving a short message to be processed includes:

[0012] Receiving the short message to be processed sent by the access and mobility management function AMF network element; or,

[0013] Receive the short message to be processed sent by the short message service center SMSC.

[0014] Optionally, forwarding the short message based on the context information includes:

[0015] In the case where the short message is sent by the AMF network element, forwarding the short message according to the originating short message MO disaster recovery process based on the context information; or,

[0016] In the case that the short message is sent by the SMSC, the short message is forwarded according to the disaster recovery process of the called short message MT based on the context information.

[0017] Optionally, the registration center includes a primary registration center and a backup registration center, and sending the information query request to the registration center includes:

[0018] Sending an information query request to the primary registration center;

[0019] When the context information returned by the primary registration center is not received within a first preset time, the information query request is sent to the backup registration center.

[0020] Optionally, after sending the information query request to the registration center, the method further includes:

[0021] If the context information returned by the registration center is not received within the second preset time, the unified data management UDM network element and the AMF network element are discovered through the NRF service based on the identification of the terminal device to obtain the context information.

[0022] Optionally, the SMS disaster recovery method further includes:

[0023] Receive a first registration request sent by an AMF network element, wherein the first registration request includes an identifier of the terminal device and first address information of the AMF network element;

[0024] Send a second registration request to the registration center, wherein the second registration request includes the identifier of the terminal device, the first address information of the AMF network element, and the second address information of the SMSF network element.

[0025] The third aspect of the present application provides a short message disaster recovery method, which is executed by a registration center network element and includes:

[0026] Receiving a first information query request sent by a short message service function SMSF network element, wherein the first information query request includes an identifier of a terminal device;

[0027] Based on the identifier of the terminal device, query the registration data table to obtain context information associated with the identifier of the first terminal device;

[0028] Sending context information associated with the identity of the terminal device to the SMSF.

[0029] Optionally, before the receiving the first information query request sent by the short message service function SMSF network element, the method further includes:

[0030] Receiving a registration request sent by the SMSF network element, wherein the registration request includes an identifier of the terminal device, first address information of the AMF network element, and second address information of the SMSF network element;

[0031] The identification of the terminal device, the first address information of the AMF network element and the second address information of the SMSF network element are associated and stored in the registration data table.

[0032] Optionally, before the receiving the first information query request sent by the short message service function SMSF network element, the method further includes:

[0033] Receiving a second information query request sent by a short message service center SMSC, wherein the second information query request includes an identifier of the terminal device, wherein the terminal device is a receiving terminal device of the short message to be processed in the SMSC;

[0034] Based on the identification of the terminal device, query the registration data table to obtain second address information of the SMSF network element associated with the identification of the terminal device;

[0035] The second address information is sent to the SMSC.

[0036] Optionally, the receiving a second information query request sent by a short message service center SMSC includes:

[0037] A second information query request sent by the SMSC is received through a stream control transmission protocol (SCTP) interface.

[0038] A fourth aspect of the present application provides a short message service function SMSF network element, characterized in that the SMSF network element is as described in the first aspect above, and the SMSF network element includes a memory, a transceiver, and a processor; the memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations:

[0039] Receiving a short message to be processed, wherein the short message includes an identification of a terminal device;

[0040] In the case where the context information associated with the identifier of the terminal device is not included, sending an information query request to a registration center, wherein the query request includes the identifier of the terminal device;

[0041] The transceiver is controlled to forward the short message based on the context information when receiving the context information sent by the registration center.

[0042] Optionally, the processor is specifically configured to perform the following operations:

[0043] Receiving the short message to be processed sent by the access and mobility management function AMF network element; or,

[0044] Receive the short message to be processed sent by the short message service center SMSC.

[0045] Optionally, the processor is specifically configured to perform the following operations:

[0046] In the case where the short message is sent by the AMF network element, forwarding the short message according to the originating short message MO disaster recovery process based on the context information; or,

[0047] In the case that the short message is sent by the SMSC, the short message is forwarded according to the disaster recovery process of the called short message MT based on the context information.

[0048] Optionally, the processor is specifically configured to perform the following operations:

[0049] Sending an information query request to the primary registration center;

[0050] When the context information returned by the primary registration center is not received within a first preset time, the information query request is sent to the backup registration center.

[0051] Optionally, after sending the information query request to the registration center, the processor is further configured to perform the following operations:

[0052] If the context information returned by the registration center is not received within the second preset time, the unified data management UDM network element and the AMF network element are discovered through the NRF service based on the identification of the terminal device to obtain the context information.

[0053] Optionally, the processor is specifically configured to perform the following operations:

[0054] Receive a first registration request sent by an AMF network element, wherein the first registration request includes an identifier of the terminal device and first address information of the AMF network element;

[0055] Send a second registration request to the registration center, wherein the second registration request includes the identifier of the terminal device, the first address information of the AMF network element, and the second address information of the SMSF network element.

[0056] A fifth aspect of the present application provides a registration center, characterized in that the registration center is as described in the first aspect above, and includes a memory, a transceiver, and a processor; the memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations:

[0057] Receiving a first information query request sent by a short message service function SMSF network element, wherein the first information query request includes an identifier of a terminal device;

[0058] Based on the identifier of the terminal device, query the registration data table to obtain context information associated with the identifier of the first terminal device;

[0059] Sending context information associated with the identity of the terminal device to the SMSF.

[0060] Optionally, before receiving the first information query request sent by the short message service function SMSF network element, the processor is further configured to perform the following operations:

[0061] Receiving a registration request sent by the SMSF network element, wherein the registration request includes an identifier of the terminal device, first address information of the AMF network element, and second address information of the SMSF network element;

[0062] The identification of the terminal device, the first address information of the AMF network element and the second address information of the SMSF network element are associated and stored in the registration data table.

[0063] Optionally, the processor is further configured to perform the following operations:

[0064] Receiving a second information query request sent by a short message service center SMSC, wherein the second information query request includes an identifier of the terminal device, wherein the terminal device is a receiving terminal device of the short message to be processed in the SMSC;

[0065] Based on the identification of the terminal device, query the registration data table to obtain second address information of the SMSF network element associated with the identification of the terminal device;

[0066] The second address information is sent to the SMSC.

[0067] Optionally, the processor is specifically configured to perform the following operations:

[0068] A second information query request sent by the SMSC is received through a stream control transmission protocol (SCTP) interface.

[0069] The sixth aspect of the present application provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the short message disaster recovery method described in the above embodiment.

[0070] This application has the following technical effects:

[0071] In the embodiment of the present application, a short message disaster recovery method is proposed, which first receives the short message to be processed, then sends an information query request to a registration center without containing context information associated with the identification of the terminal device, and finally forwards the short message based on the context information after receiving the context information sent by the registration center. By introducing the registration center, not only the recovery of user context information is efficiently achieved, but also the processing efficiency of the short message disaster recovery method is improved.

[0072] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0073] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0074] Figure 1 It is a structural diagram of a short message disaster recovery system in the related technology;

[0075] Figure 2 A schematic diagram of the structure of a short message disaster recovery system provided for the present application example;

[0076] Figure 3 A flowchart of a short message disaster recovery method provided in an embodiment of the present application;

[0077] Figure 4 A flowchart of a short message disaster recovery method provided in an embodiment of the present application;

[0078] Figure 5 A flowchart of a short message disaster recovery method provided in an embodiment of the present application;

[0079] Figure 6 A flowchart of a short message disaster recovery method provided in an embodiment of the present application;

[0080] Figure 7A schematic diagram of a MO short message disaster recovery process provided in an embodiment of the present application;

[0081] Figure 8 A schematic diagram of a MT short message disaster recovery process provided in an embodiment of the present application;

[0082] Fig. 9 A schematic diagram of the structure of a short message service function SMSF network element provided in an embodiment of the present application;

[0083] Fig.10 A schematic diagram of the structure of a registration center provided in an embodiment of the present application. DETAILED DESCRIPTION

[0084] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0085] Combine the following Figure 1 The short message disaster recovery method in the related art is described. Figure 1 The system diagram of a short message disaster recovery method in the related art. In the figure, DC1 and DC2 both mean large areas, STP1 and STP2 both stand for the abbreviation of Spanning Tree Protocol (STP), SMSC stands for the abbreviation of Short Message Service Center (SMSC) network element, SMSF1 and SMSF2 both stand for the abbreviation of Short Message Service Function (SMSF), NRF1 and NRF2 both stand for the abbreviation of Network Functions Repository Function (NRF), UDM1 and UDM2 both stand for Unified Data Management (UDM), and AMF1 and AMF2 both stand for Access and Mobility Management Function (AMF).

[0086] In the related technologies, when deployed across large regions, the data recovery process in the SMSF disaster recovery scenario is relatively complicated, and the requirements for the surrounding network functions (NF) are relatively high. The main disadvantages are as follows:

[0087] (1) In cross-region scenarios, SMSF needs to find the unified data management (UDM) through the network storage function NRF service. At this time, it is necessary to discover the service based on the user permanent identifier (SUPI). NRF needs to support UDM discovery based on SUPI, so that the previously registered UDM can be found across regions.

[0088] (2) SMSF needs to perform signaling interaction with UDM to obtain the user's contract management data, and then needs to complete the data recovery process through multiple signaling interactions across regions.

[0089] (3) In the disaster recovery scenario, SMSF cannot directly obtain the address information of the access and mobility management function AMF. Therefore, when SMSF sends a message to AMF as a client, it needs to obtain the registration information of AMF from UDM through the Subscriber Data Management (SDM) service, thereby obtaining the Network Functions Identification (NFID) of AMF, and then discover the link information of AMF through the NRF service.

[0090] From the above process, the data recovery process requires multiple signaling interactions across regions before normal Mobile Originated (MO) and Mobile Terminated (MT) services can be continued. The signaling interaction process is complicated, the service processing delay is large, and the user experience is not friendly.

[0091] The following describes the short message disaster recovery system, method, SMSF network element, registration center and storage medium of the embodiments of the present application with reference to the accompanying drawings.

[0092] Figure 2 A schematic diagram of the structure of a short message disaster recovery system provided in an embodiment of the present application.

[0093] like Figure 2 As shown, the short message disaster recovery system includes: a short message service center SMSC, a registration center and multiple network element groups, wherein each network element group includes a short message service function SMSF network element, an access and mobility management function AMF network element and a unified data management UDM network element;

[0094] Among them, the registration center is connected to the SMSC and the SMSF in each network element group respectively; the SMSC is connected to the UDM in each network element group respectively; the SMSF in each network element group is connected to the AMF and UDM in the same network element group respectively.

[0095] Among them, the registration center is a network element device provided by the network side for storing context information of terminal devices, which can communicate based on the network element protocol and / or the SMS center protocol.

[0096] In some possible implementation forms, in order to further improve the reliability of data, the network side may include a primary registration center and a backup registration center, wherein the data stored in the backup registration center is completely consistent with the data stored in the primary registration center.

[0097] It should be noted that the access and mobility management function AMF network element and the unified data management UDM network element can also be referred to as the access and mobility management function AMF entity and the unified data management UDM entity respectively.

[0098] Combine the following Figure 2 The structure of a short message disaster recovery system provided in an embodiment of the present application is further described. Figure 2 As shown, DC1 and DC2 both mean large areas. The short message service center SMSC is connected to the primary / backup registration center center, the UDM1 network element in DC1, and the UDM2 network element in DC2 respectively. At the same time, the spanning tree protocol (Spanning Tree Protocol, STP) STP1 protocol is used in DC1, and the STP2 protocol is used in DC2; the primary / backup registration center is connected to the SMSC network element, the SMSF1 network element in DC1, and the SMSF2 network element in DC2 respectively; the UDM1 network element in DC1 is connected to the SMSC network element and the SMSF1 network element respectively, and the UDM2 network element in DC2 is connected to the SMSC network element and the SMSF2 network element respectively; the SMSF1 network element in DC1 is connected to the UDM1 network element and the primary / backup registration center respectively, and the SMSF2 network element in DC2 is connected to the UDM2 network element and the primary / backup registration center network element respectively; the network storage function (NF Repository) in DC1 Function, NRF) NRF1 network element is connected to NRF2 network element in DC2; AMF1 network element in DC1 is connected to SMSF1 network element, and AMF2 network element in DC2 is connected to SMSF2 network element.

[0099] In the embodiment of the present application, by introducing a registration center, user context rapid recovery can be efficiently implemented, which has great advantages in cross-regional scenarios. At the same time, a large number of signaling process interactions within the core network business to restore user data are avoided, thereby improving processing efficiency. The SMS disaster recovery method proposed in the present application is applicable to a variety of scenarios.

[0100] Figure 3 A flowchart of a short message disaster recovery method provided in an embodiment of the present application.

[0101] The short message disaster recovery method of the embodiment of the present application can be applied to network equipment, such as access network equipment or core network equipment.

[0102] Among them, the access network device is exemplified by a base station. The base station may include multiple cells that provide services for terminal devices. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The access network device can be used to interchange received air frames with Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The access network device can also coordinate the attribute management of the air interface. For example, the access network device involved in the embodiments of the present application may be an access network device (Base TransceiverStation, BTS) in the Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), or an access network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary access network device (eNB or e-NodeB) in the long term evolution (LTE) system, or a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present application. In some network structures, the base station may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be arranged geographically separately.

[0103] The core network equipment may include various functional network elements, such as Short Message Service (SMS) network elements, Short Message Service Function (SMSF) network elements, Access and Mobility Management Function (AMF) network elements, Unified Data Management (UDM) network elements, Network Storage Function (NF Repository Function, NRF) network elements, Short Message Service Center (SMSC) network elements, etc.

[0104] The terminal device may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. In different systems, the names of the terminal devices may also be different. For example, in a 5G system, the terminal device may be called a user equipment (UE). The wireless terminal device may communicate with one or more core network (CN) devices via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a wireless access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDA) and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited in the embodiments of the present application.

[0105] The following takes the short message disaster recovery method performed by the SMSF network element as an example to describe the short message disaster recovery method provided by the present application in detail. Figure 3 As shown, the short message disaster recovery method includes:

[0106] Step 301: receiving a short message to be processed, wherein the short message includes an identifier of a terminal device.

[0107] The short message to be processed may be a short message based on the Internet of Things. The identifier of the terminal device may be any identifier of the terminal device that is used to uniquely indicate the association of the short message to be processed, for example, it may be SUPI, or it may be a mobile phone number (Mobile Station international ISDN number, MSISDN) of a user of the terminal device, etc., which is not limited in this application.

[0108] In some possible implementation forms, the SMSF network element can receive pending short messages sent by the AMF network element.

[0109] For example, in the MO service, the AMF network element may detect that SMSF1 has a fault through a service timeout response, PING link detection, or NRF notification, and then send the MO short message to SMSF2.

[0110] In some possible implementation forms, the SMSF network element may also receive a short message to be processed sent by a short message service center (Short Message Service Center, SMSC).

[0111] For example, in the MT service, the SMSC first obtains the address of SMSF1 associated with the MT short message to be forwarded. If the SMSF1 fails through the Stream Control Transmission Protocol (SCTP) heartbeat detection, the short message can be sent to SMSF2.

[0112] Step 302: In the case where the context information associated with the identifier of the terminal device is not included, an information query request is sent to a registration center, wherein the query request includes the identifier of the terminal device.

[0113] Among them, the context information associated with the terminal device's identification may include the user's SUPI, AMF address, SMS current network element address, SMSF address, etc., which is not limited in this application.

[0114] For example, in MO service, SMSF can directly find the AMF previously registered by the user based on the AMF address in the context information associated with the terminal device's identity. Alternatively, in MT service, the SMSC can find the target SMSF based on the SMSF address included in the context information associated with the terminal device's identity.

[0115] In this application, after receiving a short message, the SMSF can first query the user context information according to the terminal device identifier in the short message. If the user context information is found locally, the SMSF can perform the short message recovery process based on the user context information. If the user context information is not found locally, it is necessary to query the context information of the terminal device from the registration center.

[0116] In some possible implementation forms, the SMSF may first send an information query request to the primary registration center, and then send an information query request to the backup registration center if no context information returned by the primary registration center is received within a first preset time.

[0117] The first preset time is a time threshold for receiving context information returned by the main registration center that is preset according to business needs, and this application does not limit this.

[0118] In this application, the SMSF sends an information query request to the primary registration center. When the context information returned by the primary registration center is not received within the first preset time, it can be considered that the primary registration center has failed, and then the information query request can be sent to the backup registration center.

[0119] Step 303: when the context information sent by the registration center is received, the short message is forwarded based on the context information.

[0120] In the present application, after the SMSF receives the context information sent by the registration center, it can forward the short message based on the context information, thereby realizing the recovery of the short message.

[0121] For example, for an MO short message, the MO short message can be forwarded based on the MO service process and context information; for an MT short message, the MT short message can be forwarded based on the MT service process and context information.

[0122] In some possible implementation forms, if the SMSF does not receive the context information returned by the registration center within the second preset time, it can discover the unified data management UDM network element and AMF network element through the NRF service based on the identification of the terminal device to obtain the context information.

[0123] The second preset time is a time threshold for receiving context information returned by the registration center preset according to business needs, and this application does not limit this. The second preset time can be the same as or different from the first preset time length, and this application does not limit this.

[0124] In this application, when the SMSF does not receive the context information returned by the registration center within the second preset time, it can be considered that both the primary and backup registration centers have failed. At this time, the SMSF can perform short message recovery based on the short message disaster recovery method in the relevant technology. In other words, based on the identifier of the terminal device in the short message, the UDM network element and the AMF network element are discovered through the NRF service, and the signaling recovery data process is performed to obtain the user context information.

[0125] In the embodiment of the present application, after receiving the short message to be processed, if the SMSF network element finds that there is no context information associated with the identification of the terminal device, it sends an information query request to the registration center, and after receiving the context information sent by the registration center, it forwards the short message based on the context information. Therefore, by introducing the registration center, not only the recovery of user context information is efficiently achieved, but also the processing efficiency of the short message disaster recovery method is improved.

[0126] Combine the following Figure 4 Taking the short message disaster recovery method executed by the SMSF network element as an example, the short message disaster recovery method provided by the present application is further described in detail. Figure 4 A flow chart of a short message disaster recovery method provided in an embodiment of the present application. Figure 4 As shown, the short message disaster recovery method includes:

[0127] Step 401, receiving a first registration request sent by an AMF network element, wherein the first registration request includes an identifier of a terminal device and first address information of the AMF network element.

[0128] The first registration request is sent by the AMF network element to the SMSF network element after the user registers information in the AMF network element. The first address information is the unique address of the AMF network element in the network system, and other network elements can communicate with the AMF network element based on the first address information.

[0129] Step 402: Send a second registration request to the registration center, wherein the second registration request includes the identifier of the terminal device, the first address information of the AMF network element, and the second address information of the SMSF network element.

[0130] The second address information is the unique address of the SMSF network element in the network system, and other network elements can communicate with the SMSF network element based on the second address information.

[0131] In this application, after the SMSF network element receives the first registration request sent by the AMF network element, it registers the information of the user associated with the terminal device identifier, and then the SMSF network element can send a second registration request to the registration center, sending the terminal device identifier, the first address information of the AMF network element, and the second address information of the SMSF network element to the registration center, that is, sending the context information of the terminal device to the registration center. The registration center can then store the context information of the terminal device for query and use by each network element.

[0132] In some possible implementation forms, the SMSF network element may also determine whether the context information of the terminal device is synchronized based on whether the registration response returned by the registration center is received. For example, if the SMSF network element does not receive the registration response sent by the registration center, it can be determined that the registration has failed, and a second registration request can be resent to the registration center until a registration response returned by the registration center is received.

[0133] It should be noted that the SMSF network element may first send a second registration request to the primary registration center, and then, if it does not receive a successful registration response from the primary registration center after waiting for a certain period of time, send the second registration request to the backup registration center. Alternatively, the SMSF network element may also send a second registration request to the primary registration center and the backup registration center at the same time to synchronize the context information of the terminal device to the primary registration center and the backup registration center at the same time, which is not limited in this application.

[0134] Step 403: receiving a short message to be processed, wherein the short message includes an identifier of the terminal device.

[0135] Step 404: In the case where the context information associated with the identifier of the terminal device is not included, an information query request is sent to the registration center, wherein the query request includes the identifier of the terminal device.

[0136] Step 405: when the context information sent by the registration center is received, the short message is forwarded based on the context information.

[0137] In the present application, after receiving the context information sent by the registration center, the SMSF network element can forward the pending short message based on the context information and the short message disaster recovery method in the related technology, that is, perform short message recovery. For example, after obtaining the user's context information, the SMSF network element can first re-register and subscribe to the user information with the UDM network element. Then, if the short message is sent by the AMF network element, the SMSF network element can forward the MO short message based on the MO service process; if the short message is sent by the SMSC, the SMSF network element can forward the MT short message based on the MT service process.

[0138] Among them, the specific implementation forms of steps 403 to 405 can refer to the detailed description of other embodiments of the present application and will not be repeated here.

[0139] In the embodiment of the present application, after receiving the first registration request sent by the AMF network element, the SMSF network element can send a second registration request to the registration center to synchronize the context information of the terminal device to the registration center, and then when receiving the short message to be processed, if it is found that there is no context information associated with the identification of the terminal device, an information query request is sent to the registration center, and after receiving the context information sent by the registration center, the short message is forwarded based on the context information. Therefore, during the registration process, the SMSF network element directly synchronizes the registration information of the terminal device to the registration center, and when processing the short message service, the user context information is queried from the registration center, which not only improves the processing efficiency of the short message disaster recovery method, but also simplifies the process of user context information recovery.

[0140] Combine the following Figure 5 Taking the short message disaster recovery method executed by the registration center network element as an example, the short message disaster recovery method provided by the present application is described in detail. Figure 5 A flowchart of a short message disaster recovery method provided in an embodiment of the present application.

[0141] like Figure 5 As shown, the short message disaster recovery method includes:

[0142] Step 501: receiving a first information query request sent by a short message service function SMSF network element, wherein the first information query request includes an identifier of a terminal device.

[0143] The first information query request is a request sent by the SMSF network element and received by the registration center network element to query the user context information associated with the terminal device identifier.

[0144] In some possible implementation forms, in order to further improve the reliability of data, the registration center network element includes a primary registration center and a backup registration center, wherein the data stored in the backup registration center is completely consistent with the data stored in the primary registration center.

[0145] In this application, when the registration center network element receives the first information query request sent by the SMSF network element, it indicates that the SMSF network element that received the short message did not find the user context information associated with the terminal device identifier locally. In other words, after receiving the first information query request, the registration center network element will query the user context information associated with the terminal device identifier.

[0146] Step 502: Based on the identifier of the terminal device, query the registration data table to obtain context information associated with the identifier of the first terminal device.

[0147] Among them, the registration data table is a registration information table composed of the user's context information and the user's terminal device identification. The registration data table can be preset according to business needs, or can also be set according to the historical data information of the business. This application does not limit this.

[0148] Among them, the context information associated with the identification of the first terminal device may include the user's SUPI, AMF address, current network element address of the SMS, SMSF address, etc., which is not limited in this application.

[0149] In this application, after receiving the first information query request sent by the SMSF network element, the registration center network element queries the registration data table based on the identifier of the first terminal device in the first information query request. If the identifier of the first terminal device is found in the registration data table, the user context information associated with it is obtained.

[0150] Step 503: Send the context information associated with the identifier of the terminal device to the SMSF.

[0151] In some possible implementation forms, if the main registration center network element does not return the context information to the SMSF network element within a certain time after receiving the first information query request, the backup registration center network element will receive the first information query request to query the context information associated with the terminal device identifier and return the context information to the SMSF network element within a certain time.

[0152] In the present application, after the registration center network element queries the context information associated with the terminal device's identification in the registration data table, it sends the context information to the SMSF network element.

[0153] In the embodiment of the present application, the registration center network element first receives the first information query request sent by the short message service function SMSF network element, and then queries the registration data table based on the identifier of the terminal device in the first information query request, obtains the context information associated with the identifier of the first terminal device, and then sends the context information associated with the identifier of the terminal device to the SMSF network element. Therefore, by introducing the registration center network element, not only the processing efficiency of the short message disaster recovery method is improved, but also the recovery of user context information is efficiently completed.

[0154] Combine the following Figure 6 Taking the short message disaster recovery method executed by the registration center network element as an example, the short message disaster recovery method provided by the present application is further described in detail. Figure 6 A flowchart of a short message disaster recovery method provided in an embodiment of the present application.

[0155] like Figure 6 As shown, the short message disaster recovery method includes:

[0156] Step 601, receiving a registration request sent by an SMSF network element, wherein the registration request includes an identifier of the terminal device, first address information of the AMF network element, and second address information of the SMSF network element.

[0157] The first address information is the unique address of the AMF network element in the network system, and other network elements can communicate with the AMF network element based on the first address information. The second address information is the unique address of the SMSF network element in the network system, and other network elements can communicate with the SMSF network element based on the second address information.

[0158] In the present application, after the SMSF network element registers the information of the user associated with the terminal device identifier, the registration center network element will receive the registration request sent by the SMSF network element, and receive the identifier of the terminal device, the first address information of the AMF network element and the second address information of the SMSF network element, that is, receive the context information associated with the terminal device.

[0159] Step 602, associate the terminal device identifier, the first address information of the AMF network element, and the second address information of the SMSF network element and store them in a registration data table.

[0160] In this application, after receiving the registration request sent by the SMSF network element, the registration center network element obtains and associates the terminal device identifier, the first address information of the AMF network element and the second address information of the SMSF network element from the registration request, and stores them in the registration data table.

[0161] Step 603: receiving a second information query request sent by a short message service center SMSC, wherein the second information query request includes an identifier of a terminal device, wherein the terminal device is a receiving terminal device of a short message to be processed in the SMSC.

[0162] The second information query request is a request sent by the SMSC network element and received by the registration center network element for querying the SMSF network element address information associated with the terminal device identifier.

[0163] In some possible implementation forms, the second information query request sent by the SMSC is received through a stream control transmission protocol (SCTP) interface.

[0164] In the present application, in the MT SMS service scenario, after receiving the short message to be processed, the SMSC network element first detects the target SMSF network element associated with the terminal device identifier in the short message through the stream control transmission protocol SCTP heartbeat. If the target SMSF network element is found to have a fault, the SMSC network element will send a second information query request to the registration network element center to query the address of the SMSF network element in the registration center network element.

[0165] Step 604: Based on the identifier of the terminal device, query the registration data table to obtain the second address information of the SMSF network element associated with the identifier of the terminal device.

[0166] In the present application, after receiving the second information query request sent by the SMSC network element, the registration center network element queries the registration data table based on the identifier of the terminal device in the second information query request. If the identifier of the terminal device in the second information query request is found in the registration data table, the second address information of the SMSF network element associated with it is obtained.

[0167] Step 605: Send the second address information to the SMSC.

[0168] In the present application, the registration center network element searches the registration data table for the second address information of the SMSF network element associated with the identifier of the terminal device, and sends the address information to the SMSC network element.

[0169] In the embodiment of the present application, the registration network element center first receives the registration request sent by the SMSF network element, and associates the terminal device's identifier, the first address information of the AMF network element, and the second address information of the SMSF network element into the registration data table. In the MT service scenario, when the SMSC network element detects that the SMSF network element has failed, the registration center network element will receive the second information query request sent by the SMSC network element, and then query the registration data table based on the identifier of the terminal device, obtain the second address information of the SMSF network element associated with the identifier of the terminal device, and finally send the second address information to the SMSC network element. Thus, the registration information of the terminal device is synchronized to the registration center through the SMSF network element, and when the MT service is processed, the SMSC network element queries the SMSF network element address information from the registration center network element, which not only improves the processing efficiency of the short message disaster recovery method, but also efficiently completes the recovery of user context information.

[0170] Figure 7 A schematic diagram of a MO short message disaster recovery process provided by an embodiment of the present application. In the figure, UE is a user terminal device (User Equipment, UE), RCENTER is a registration center, SMS-GSMC is a mobile switching center gateway for short message service center (Gateway Mobile Switching Center For Short Message Service, SMS-GSMC), SC is a short message service center (Service Center, SC), mobility management function network element AMF, and two short message service function network elements SMSF1 and SMSF2.

[0171] like Figure 7 As shown in the figure, the MO short message disaster recovery process includes:

[0172] Step 701: UE sends a short message to the AMF network element.

[0173] Step 702, the AMF network element detects whether the SMSF1 network element fails.

[0174] Step 703, when it is determined that the SMSF1 network element fails, the AMF network element sends a short message to the SMSF2 network element.

[0175] Step 704: When the SMSF2 network element finds that there is no user context information after receiving the short message, it requests the RCENTER network element for user context information.

[0176] Step 705: SMSF2 network element forwards the short message based on the received user context information.

[0177] In the embodiment of the present application, for the MO short message disaster recovery process, the UE first sends a short message to the AMF network element, and then when the AMF network element detects that the SMSF1 network element fails, the AMF network element sends a short message to the SMSF2 network element, and then the SMSF2 network element requests the user context information from the RCENTER network element when it is determined that there is no user context information, and finally the SMSF2 network element forwards the short message based on the received user context information to complete the MO short message recovery. Therefore, by introducing the RCENTER network element, not only the processing efficiency of the MO short message disaster recovery method is improved, but also the recovery of the user context information is efficiently completed.

[0178] Figure 8 A schematic diagram of a MT short message disaster recovery process provided by an embodiment of the present application. In the figure, UE is a user terminal device (User Equipment, UE), RCENTER is a registration center, SMS-GSMC is a mobile switching center gateway for short message service center (Gateway Mobile Switching Center For Short Message Service, SMS-GSMC), SC is a short message service center (Service Center, SC), a mobility management function network element AMF, and two short message service function network elements SMSF1 and SMSF2.

[0179] like Figure 8 As shown in the figure, the MT short message disaster recovery process includes:

[0180] Step 801: The SMSC network element receives a short message.

[0181] Step 802: The SMSC network element detects whether the SMSF1 network element fails.

[0182] Step 803: When it is determined that the SMSF1 network element fails, the SMSC network element sends a short message to the SMSF2 network element.

[0183] Step 804: When the SMSF2 network element finds that there is no user context information after receiving the short message, it requests the RCENTER network element for user context information.

[0184] Step 805: SMSF2 network element forwards the short message based on the received user context information.

[0185] In the embodiment of the present application, for the MT short message disaster recovery process, first, the SMSC network element receives the short message, and when the SMSC network element detects that the SMSF1 network element fails, the SMSC network element sends the short message to the SMSF2 network element, and then the SMSF2 network element requests the user context information from the RCENTER network element when it is determined that there is no user context information, and finally the SMSF2 network element forwards the short message based on the received user context information to complete the MT short message recovery process. Therefore, by introducing the RCENTER network element, not only the processing efficiency of the MT short message disaster recovery method is improved, but also the recovery of the user context information is efficiently completed.

[0186] In order to implement the above embodiment, the present application embodiment further proposes a short message service function SMSF network element, Fig. 9 A schematic diagram of the structure of a short message service function SMSF network element provided in an embodiment of the present application.

[0187] like Fig. 9 As shown, the short message service function SMSF network element 900 includes: a transceiver 901, a processor 902, and a memory 903;

[0188] The transceiver 901 is used to send and receive data under the control of the processor 902.

[0189] Among them, Fig. 9In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 902 and memory represented by memory 903. The bus architecture may also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 901 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and the like. The processor 902 is responsible for managing the bus architecture and general processing, and the memory 903 may store data used by the processor 902 when performing operations.

[0190] The processor 902 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0191] The processor 902 is used to call the computer program stored in the memory and perform the following operations:

[0192] receiving a short message to be processed, wherein the short message includes an identification of the terminal device;

[0193] In the case where the context information associated with the identifier of the terminal device is not included, sending an information query request to the registration center, wherein the query request includes the identifier of the terminal device;

[0194] When the context information sent by the registration center is received, the short message is forwarded based on the context information.

[0195] Optionally, the processor 902 is used to receive a text message to be processed, and specifically performs the following operations:

[0196] Receiving a short message to be processed sent by an access and mobility management function AMF network element; or,

[0197] Receive the short message to be processed sent by the short message service center SMSC.

[0198] Optionally, the processor 902 forwards the short message based on the context information by specifically performing the following operations:

[0199] In the case where the short message is sent by the AMF network element, the short message is forwarded according to the disaster recovery process of the originating short message MO based on the context information; or,

[0200] In the case where the short message is sent by the SMSC, the short message is forwarded based on the context information according to the disaster recovery process of the called short message MT.

[0201] Optionally, the registration center includes a primary registration center and a backup registration center, and the processor 902 sends an information query request to the registration center, and specifically performs the following operations:

[0202] Send information query request to the main registration center;

[0203] When the context information returned by the primary registration center is not received within the first preset time, an information query request is sent to the backup registration center.

[0204] Optionally, after sending the information query request to the registration center, the processor 902 is further configured to perform the following operations:

[0205] If the context information returned by the registration center is not received within the second preset time, the unified data management UDM network element and the AMF network element are discovered through the NRF service based on the identification of the terminal device to obtain the context information.

[0206] Optionally, the processor is further configured to perform the following operations:

[0207] Receive a first registration request sent by the AMF network element, wherein the first registration request includes an identifier of the terminal device and first address information of the AMF network element;

[0208] A second registration request is sent to the registration center, wherein the second registration request includes the identification of the terminal device, the first address information of the AMF network element, and the second address information of the SMSF network element.

[0209] It should be noted that the SMSF network element provided in the embodiment of the present application can realize the above Figure 3 to Figure 4 All the method steps implemented in the method embodiment can achieve the same technical effect, and the parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0210] In order to implement the above embodiment, the present application embodiment also proposes a registration center. Fig.10 A schematic diagram of the structure of a registration center provided in an embodiment of the present application.

[0211] like Fig.10As shown, the registration center 1000 includes: a transceiver 1001, a processor 1002, and a memory 1003;

[0212] The transceiver 1001 is used to send and receive data under the control of the processor 1002.

[0213] Among them, Fig.10 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 1002 and memory represented by memory 1003. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1001 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and the like. The processor 1002 is responsible for managing the bus architecture and general processing, and the memory 1003 may store data used by the processor 1002 when performing operations.

[0214] The processor 1002 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0215] The processor 1002 is used to call the computer program stored in the memory and perform the following operations:

[0216] Receiving a first information query request sent by a short message service function SMSF network element, wherein the first information query request includes an identifier of a terminal device;

[0217] Based on the identifier of the terminal device, query the registration data table to obtain context information associated with the identifier of the first terminal device;

[0218] Send the context information associated with the terminal device's identity to the SMSF.

[0219] Optionally, before receiving the first information query request sent by the short message service function SMSF network element, the processor 1002 specifically performs the following operations:

[0220] Receive a registration request sent by the SMSF network element, wherein the registration request includes an identifier of the terminal device, first address information of the AMF network element, and second address information of the SMSF network element;

[0221] The terminal device identification, the first address information of the AMF network element and the second address information of the SMSF network element are associated and stored in the registration data table.

[0222] Optionally, the processor 1002 specifically performs the following operations:

[0223] Receiving a second information query request sent by a short message service center SMSC, wherein the second information query request includes an identifier of a terminal device, wherein the terminal device is a receiving terminal device of a short message to be processed in the SMSC;

[0224] Based on the identification of the terminal device, query the registration data table to obtain the second address information of the SMSF network element associated with the identification of the terminal device;

[0225] The second address information is sent to the SMSC.

[0226] Optionally, the processor 1002 receives a second information query request sent by a short message service center SMSC, and specifically performs the following operations:

[0227] A second information query request sent by the SMSC is received through a stream control transmission protocol (SCTP) interface.

[0228] It should be noted that the registration center provided in the embodiment of the present application can achieve the above Figures 5 and 6 All the method steps implemented in the method embodiment can achieve the same technical effect, and the parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0229] It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0230] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network side device, etc.) or a processor (processor) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store program codes.

[0231] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0232] On the other hand, an embodiment of the present application further provides a processor-readable storage medium, the processor-readable storage medium storing a computer program, the computer program is used to enable the processor to execute the present application Figure 3 , Figure 4 , Figure 5 , Figure 6 The method shown in the embodiment.

[0233] Among them, the above-mentioned processor-readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO)), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NANDFLASH), solid-state drive (SSD)), etc.

[0234] In the description of this specification, the terms "first" and "second" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of this application, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0235] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in this field can change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A short message disaster recovery system, characterized in that: include: Short Message Service Center SMSC, Registration Center and multiple network element groups, wherein each network element group includes a Short Message Service Function SMSF network element, an Access and Mobility Management Function AMF network element and a Unified Data Management UDM network element; Wherein, the registration center is connected to the SMSC and the SMSF in each of the network element groups respectively; The SMSC is respectively connected to the UDM in each of the network element groups; The SMSF in each of the network element groups is respectively connected to the AMF and UDM in the same network element group.

2. The system according to claim 1, characterized in that The registration center includes a primary registration center and a backup registration center.

3. A short message disaster recovery method, characterized in that: The method is performed by the SMSF network element as claimed in claim 1 or 2, and the method comprises: Receiving a short message to be processed, wherein the short message includes an identification of a terminal device; In the case where the context information associated with the identifier of the terminal device is not included, sending an information query request to a registration center, wherein the query request includes the identifier of the terminal device; When the context information sent by the registration center is received, the short message is forwarded based on the context information.

4. The method according to claim 3, characterized in that The receiving of a short message to be processed comprises: Receiving the short message to be processed sent by the access and mobility management function AMF network element; or, Receive the short message to be processed sent by the short message service center SMSC.

5. The method according to claim 4, characterized in that The forwarding the short message based on the context information includes: In the case where the short message is sent by the AMF network element, forwarding the short message according to the originating short message MO disaster recovery process based on the context information; or, In the case that the short message is sent by the SMSC, the short message is forwarded according to the disaster recovery process of the called short message MT based on the context information.

6. The method according to claim 3, characterized in that The registration center includes a primary registration center and a backup registration center, and sending an information query request to the registration center includes: Sending an information query request to the primary registration center; When the context information returned by the primary registration center is not received within a first preset time, the information query request is sent to the backup registration center.

7. The method according to claim 3, characterized in that After sending the information query request to the registration center, the method further includes: If the context information returned by the registration center is not received within the second preset time, the unified data management UDM network element and the AMF network element are discovered through the NRF service based on the identification of the terminal device to obtain the context information.

8. The method according to any one of claims 3 to 7, characterized in that: Also includes: Receive a first registration request sent by an AMF network element, wherein the first registration request includes an identifier of the terminal device and first address information of the AMF network element; Send a second registration request to the registration center, wherein the second registration request includes the identifier of the terminal device, the first address information of the AMF network element, and the second address information of the SMSF network element.

9. A short message disaster recovery method, characterized in that: The method is performed by a registration center as claimed in claim 1 or 2, and the method comprises: Receiving a first information query request sent by a short message service function SMSF network element, wherein the first information query request includes an identifier of a terminal device; Based on the identifier of the terminal device, query the registration data table to obtain context information associated with the identifier of the first terminal device; Sending context information associated with the identity of the terminal device to the SMSF.

10. The method according to claim 9, characterized in that Before the receiving the first information query request sent by the short message service function SMSF network element, the method further includes: Receiving a registration request sent by the SMSF network element, wherein the registration request includes an identifier of the terminal device, first address information of the AMF network element, and second address information of the SMSF network element; The identification of the terminal device, the first address information of the AMF network element and the second address information of the SMSF network element are associated and stored in the registration data table.

11. The method according to claim 10, characterized in that Also includes: Receiving a second information query request sent by a short message service center SMSC, wherein the second information query request includes an identifier of the terminal device, wherein the terminal device is a receiving terminal device of the short message to be processed in the SMSC; Based on the identification of the terminal device, query the registration data table to obtain second address information of the SMSF network element associated with the identification of the terminal device; The second address information is sent to the SMSC.

12. The method according to claim 11, characterized in that The receiving a second information query request sent by a short message service center SMSC comprises: A second information query request sent by the SMSC is received through a stream control transmission protocol (SCTP) interface.

13. A short message service function SMSF network element, characterized in that: The SMSF network element is as described in claim 1 or 2, wherein the SMSF network element comprises a memory, a transceiver, and a processor; the memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: Receiving a short message to be processed, wherein the short message includes an identification of a terminal device; In the case where the context information associated with the identifier of the terminal device is not included, sending an information query request to a registration center, wherein the query request includes the identifier of the terminal device; When the context information sent by the registration center is received, the short message is forwarded based on the context information.

14. The SMSF network element according to claim 13, characterized in that: The processor is specifically configured to perform the following operations: Receiving the short message to be processed sent by the access and mobility management function AMF network element; or, Receive the short message to be processed sent by the short message service center SMSC.

15. The SMSF network element according to claim 14, characterized in that: The processor is specifically configured to perform the following operations: In the case where the short message is sent by the AMF network element, forwarding the short message according to the originating short message MO disaster recovery process based on the context information; or, In the case that the short message is sent by the SMSC, the short message is forwarded according to the disaster recovery process of the called short message MT based on the context information.

16. The SMSF network element according to claim 13, characterized in that: The processor is specifically configured to perform the following operations: Sending an information query request to the primary registration center; When the context information returned by the primary registration center is not received within a first preset time, the information query request is sent to the backup registration center.

17. The SMSF network element according to claim 13, characterized in that: After sending the information query request to the registration center, the processor is further configured to perform the following operations: If the context information returned by the registration center is not received within the second preset time, the unified data management UDM network element and the AMF network element are discovered through the NRF service based on the identification of the terminal device to obtain the context information.

18. The SMSF network element according to claims 13-17, characterized in that: The processor is specifically configured to perform the following operations: Receive a first registration request sent by an AMF network element, wherein the first registration request includes an identifier of the terminal device and first address information of the AMF network element; Send a second registration request to the registration center, wherein the second registration request includes the identifier of the terminal device, the first address information of the AMF network element, and the second address information of the SMSF network element.

19. A registration center, characterized in that: The registration center is the registration center as claimed in claim 1 or 2, and the registration center comprises a memory, a transceiver, and a processor; the memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: Receiving a first information query request sent by a short message service function SMSF network element, wherein the first information query request includes an identifier of a terminal device; Based on the identifier of the terminal device, query the registration data table to obtain context information associated with the identifier of the first terminal device; Sending context information associated with the identity of the terminal device to the SMSF.

20. The registration center according to claim 19, characterized in that: Before receiving the first information query request sent by the short message service function SMSF network element, the processor is further configured to perform the following operations: Receiving a registration request sent by the SMSF network element, wherein the registration request includes an identifier of the terminal device, first address information of the AMF network element, and second address information of the SMSF network element; The identification of the terminal device, the first address information of the AMF network element and the second address information of the SMSF network element are associated and stored in the registration data table.

21. The registration center according to claim 20, characterized in that: The processor is further configured to perform the following operations: Receiving a second information query request sent by a short message service center SMSC, wherein the second information query request includes an identifier of the terminal device, wherein the terminal device is a receiving terminal device of the short message to be processed in the SMSC; Based on the identification of the terminal device, query the registration data table to obtain second address information of the SMSF network element associated with the identification of the terminal device; The second address information is sent to the SMSC.

22. The registration center according to claim 21, characterized in that: The processor is specifically configured to perform the following operations: A second information query request sent by the SMSC is received through a stream control transmission protocol (SCTP) interface.

23. A processor-readable storage medium, characterized in that: The processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute any one of the methods of claims 3-12.

Images