CN117858147A

CN117858147A - Disaster recovery processing method and related equipment

Info

Publication number: CN117858147A
Application number: CN202211210200.0A
Authority: CN
Inventors: 许盛宏; 肖祥益; 欧亮; 庄恒全; 戴高远
Original assignee: China Telecom Corp Ltd
Current assignee: China Telecom Corp Ltd
Priority date: 2022-09-30
Filing date: 2022-09-30
Publication date: 2024-04-09

Abstract

The embodiment of the disclosure provides a disaster recovery processing method and related equipment, and relates to the technical field of communication. The disaster recovery processing method comprises the following steps: if the UPF network element detects that the first SMF network element fails or the first SMF network element recovers from the failure, the UPF network element sends a PFCP node report request message to the target SMF network element, wherein the PFCP node report request message carries a disaster recovery identifier and session disaster recovery data; the target SMF network element sends a service update request message to the NRF network element according to the disaster recovery identifier and the session disaster recovery data; the NRF network element sends a status notification request message to the subscribing network element, so that the subscribing network element updates the SMF network element identifier to the target SMF network element identifier. The disaster recovery processing method solves the problem that the service is interrupted because the original session of the failed SMF network element cannot be taken over in real time by the taken over SMF network element.

Description

Disaster recovery processing method and related equipment

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a disaster recovery processing method, a disaster recovery processing system, an electronic device, and a computer readable storage medium.

Background

In a 5G communication network, SMF (Session Management function ) network elements are mainly responsible for session management functions. When abnormal conditions such as software functions, bearer network, power interruption and the like occur, the SMF network element is failed and can not continue to provide service, so that service access of the UE (User Equipment) through the core network is affected, and at the moment, the influence on the service access of the UE due to the SMF network element failure can be reduced through a disaster recovery technology.

In the related art, if a serving SMF network element fails, an AMF (Access and Mobility Management Function ) network element releases an original session context of the failed SMF network element, and after a UE reestablishes a session, another available SMF network element in a POOL (a resource POOL formed by a plurality of SMF network elements) performs session service takeover.

However, since there is no data synchronization between SMF network elements in the POOL, the takeover SMF network element cannot take over the original session of the failed SMF network element in real time, resulting in service interruption and adversely affecting the service with high continuity requirements.

It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the present disclosure and thus may include information that does not constitute prior art known to those of ordinary skill in the art.

Disclosure of Invention

The embodiment of the disclosure provides a disaster recovery processing method, a disaster recovery processing system, electronic equipment and a computer readable storage medium, which at least solve the problem that service interruption is caused by taking over an original session of an SMF network element which fails to take over the SMF network element in real time.

Other features and advantages of the present disclosure will be apparent from the following detailed description, or may be learned in part by the practice of the disclosure.

According to one aspect of the present disclosure, there is provided a disaster recovery processing method, the method including: if the UPF network element detects that the first SMF network element fails or the first SMF network element fails to recover, the UPF network element sends a PFCP node report request message to the target SMF network element, wherein the PFCP node report request message carries disaster recovery identification and session disaster recovery data; the target SMF network element sends a service update request message to an NRF network element according to the disaster recovery identifier and the session disaster recovery data; and the NRF network element sends a state notification request message to a subscription network element so that the subscription network element updates the SMF network element identifier to the target SMF network element identifier.

In some embodiments of the present disclosure, the session disaster recovery data includes: IMSI, AMF network element identification, SMF network element identification, PCF network element identification, CP-SEID, UP-SEID, F-TEID, session control policy, and QoS policy.

In some embodiments of the present disclosure, if the UPF network element detects that the first SMF network element fails, the target SMF network element is a second SMF network element, the disaster recovery identifier is a disaster recovery switching identifier, and the SMF network element identifier is the first SMF network element identifier.

In some embodiments of the present disclosure, the sending, by the target SMF network element, a service update request message to an NRF network element according to the disaster recovery identifier and the session disaster recovery data, includes:

And triggering the service update request message to the NRF network element by the second SMF network element according to the disaster recovery switching identifier and the session disaster recovery data, wherein the service update request message carries the AMF network element identifier, the PCF network element identifier, the first SMF network element identifier and the second SMF network element identifier.

In some embodiments of the present disclosure, the status notification request message is configured to instruct updating the first SMF network element identifier to the second SMF network element identifier; the NRF network element sends a status notification request message to a subscription network element, so that the subscription network element updates an SMF network element identifier to the target SMF network element identifier, including: the NRF network element sends the state notification request message to an AMF network element according to the AMF network element identifier, so that the first SMF network element identifier of the AMF network element update session context is the second SMF network element identifier; and the NRF network element sends the state notification request message to the PCF network element according to the PCF network element identifier, so that the first SMF network element identifier of the PCF network element updating session policy is the second SMF network element identifier.

In some embodiments of the present disclosure, if the UPF network element detects that the first SMF network element is recovered from the fault, the target SMF network element is the first SMF network element, the disaster recovery identifier is a disaster recovery switch back identifier, and the SMF network element identifier is the second SMF network element identifier.

In some embodiments of the present disclosure, the sending, by the target SMF network element, a service update request message to an NRF network element according to the disaster recovery identifier and the session disaster recovery data, includes: and triggering the service update request message to the NRF network element by the first SMF network element according to the disaster recovery switching back identification and the session disaster recovery data, wherein the service update request message carries the AMF network element identification, the PCF network element identification, the first SMF network element identification and the second SMF network element identification.

In some embodiments of the present disclosure, the status notification request message is configured to instruct updating the second SMF network element identifier to the first SMF network element identifier; the NRF network element sends a status notification request message to a subscription network element, so that the subscription network element updates an SMF network element identifier to the target SMF network element identifier, including: the NRF network element sends the state notification request message to an AMF network element according to the AMF network element identifier, so that the second SMF network element identifier of the AMF network element update session context is the first SMF network element identifier; and the NRF network element sends the state notification request message to the PCF network element according to the PCF network element identifier, so that the second SMF network element identifier of the PCF network element updating session policy is the first SMF network element identifier.

In some embodiments of the present disclosure, the method further comprises: the NRF network element detects that the first SMF network element breaks down or the first SMF network element breaks down and recovers.

In some embodiments of the present disclosure, the method further comprises: in the process of establishing a session through the first SMF network element, the first SMF network element sends an N4 session modification request message to the UPF network element, wherein the N4 session modification request message carries the session disaster recovery data, and the SMF network element identifier in the session disaster recovery data is the first SMF network element identifier; if the first SMF network element fails, the UPF network element updates the first SMF network element identifier in the session disaster recovery data to the second SMF network element identifier; and if the first SMF network element is recovered from faults, the UPF network element updates the second SMF network element identifier in the session disaster recovery data to the first SMF network element identifier.

According to still another aspect of the present disclosure, there is provided a disaster recovery processing system including: a UPF network element, a first SMF network element, a second SMF network element and an NRF network element; the UPF network element is used for sending a PFCP node report request message carrying disaster recovery switching identification and session disaster recovery data to the second SMF network element under the condition that the first SMF network element is detected to be faulty; under the condition that the first SMF network element fault recovery is detected, sending a PFCP node report request message carrying a disaster recovery switching back identifier and the session disaster recovery data to the first SMF network element; the first SMF network element is configured to send a service update request message to the NRF network element according to the disaster recovery switching identifier and the session disaster recovery data when the first SMF network element fails; the second SMF network element is configured to send a service update request message to the NRF network element according to the disaster recovery switch back identifier and the session disaster recovery data when the first SMF network element fails to recover; the NRF network element is configured to send a status notification request message to a subscription network element when the first SMF network element fails, so that the subscription network element updates an SMF network element identifier to the second SMF network element identifier; and sending a status notification request message to the subscribing network element under the condition of the first SMF network element fault recovery, so that the subscribing network element updates the SMF network element identifier to the first SMF network element identifier.

According to still another aspect of the present disclosure, there is provided an electronic apparatus including: one or more processors; and a storage device configured to store one or more programs that, when executed by the one or more processors, cause the one or more processors to implement the disaster recovery processing method as described in the above embodiments.

According to still another aspect of the present disclosure, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the disaster recovery processing method as described in the above embodiments.

According to the disaster recovery processing method provided by the embodiment of the disclosure, after the UPF network element detects that the first SMF network element fails or the first SMF network element fails to recover, the PFCP node report request message carrying disaster recovery identification and session disaster recovery data can be sent to the target SMF network element, and then the target SMF network element sends the service update request message to the NRF network element according to the disaster recovery identification and the session disaster recovery data, and the NRF network element notifies the state notification request message to the subscription network element so as to trigger the subscription network element to update the SMF network element identification to the target SMF network element identification, thereby solving the problem that service interruption is caused by that the original session of the failed SMF network element cannot be taken over in real time by the taken over by the SMF network element, completing the switching of the SMF network element under the condition that UE does not have perception, and ensuring that user data transmission is not interrupted.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.

FIG. 1 is a schematic diagram of a disaster recovery processing system according to an embodiment of the disclosure;

FIG. 2 shows a flow chart of a disaster recovery processing method according to an embodiment of the disclosure;

fig. 3 illustrates a flow chart of establishing a session under normal operation of a first SMF network element in an embodiment of the present disclosure;

fig. 4 shows a flowchart of a disaster recovery processing method in the case of a failure of a first SMF network element according to an embodiment of the present disclosure;

fig. 5 shows a flowchart of a disaster recovery processing method in the case of failure recovery of the first SMF network element according to an embodiment of the present disclosure;

FIG. 6 is a flow chart of a disaster recovery processing method according to another embodiment of the present disclosure;

FIG. 7 is a schematic diagram of a disaster recovery processing system according to another embodiment of the disclosure;

fig. 8 shows a block diagram of an electronic device in an embodiment of the disclosure.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software or in one or more hardware modules or integrated circuits or in different networks and/or processor devices and/or microcontroller devices.

It should be noted that, the embodiments of the present disclosure refer to ordinal terms such as "first," "second," etc. for distinguishing a plurality of objects, and are not used to define an order, a timing, a priority, or an importance of the plurality of objects, and the descriptions of "first," "second," and the like do not necessarily define that the objects are different.

Fig. 1 shows a schematic structural diagram of a disaster recovery processing system according to an embodiment of the disclosure. As shown in fig. 1, disaster recovery processing system 100 may include: UE 101, UPF (User Plane Function ) network element 102, first SMF network element 103, second SMF network element 104, NRF (Network Repository Function ) network element 105, AMF network element 106, and PCF (Policy Control function ) network element 107.

The UPF network element 102 may determine the primary SMF network element and the backup SMF network element according to pre-configured data. Specifically, the UPF network element 102 may determine that the primary SMF network element is the first SMF network element 103, and the standby SMF network element is the second SMF network element 104. If the UPF network element finds that the main SMF network element fails, a disaster recovery switching function can be started to switch to the standby SMF network element; and when the UPF network element discovers the failure recovery of the main SMF network element, a disaster recovery switching back function can be started to switch back to the main SMF network element.

The UE 101 may establish a session through the first SMF network element 103. In the process of establishing a session, the first SMF network element 103 sends session disaster recovery data to the UPF network element 102, and the UPF network element 102 stores the session disaster recovery data. In this way, the session disaster recovery data may be used to take over the original session when the first SMF network element 103 fails or the first SMF network element 103 fails to recover.

If the UPF network element 102 detects that the first SMF network element 103 fails, a PFCP (Packet Forwarding Control Protocol ) node report request message may be sent to the second SMF network element 104, where the PFCP node report request message carries a disaster recovery handover identifier and session disaster recovery data. The second SMF network element 104 may send a service update request message to the NRF network element 105 according to the disaster recovery switching identifier and session disaster recovery data, where the NRF network element 105 notifies the subscription network element of the status notification request message to trigger the subscription network element to update the SMF network element identifier to the second SMF network element identifier, so as to implement real-time switching of the original session service of the first SMF network element to the second SMF network element, and complete switching of the SMF network element under the condition that the UE does not have awareness, and also ensure that user data transmission is not interrupted.

If the UPF network element 102 detects that the first SMF network element 103 recovers from a fault, a PFCP node reporting request message may be sent to the first SMF network element 103, where the PFCP node reporting request message carries a disaster recovery switch back identifier and session disaster recovery data. The first SMF network element 103 may send a service update request message to the NRF network element 105 according to the disaster recovery switch back identifier and session disaster recovery data, and the NRF network element 105 notifies the subscription network element of the status notification request message, so as to trigger the subscription network element to update the SMF network element identifier to the first SMF network element identifier, thereby enabling the first SMF network element with fault recovery to recover the original service load, recovering the POOL load balance of the SMF network element in real time, avoiding the risk of service instability caused by the POOL load imbalance, and ensuring stable and reliable operation of the POOL.

Communication connection can be realized among the UE 101, the UPF network element 102, the first SMF network element 103, the second SMF network element 104, the NRF network element 105, the AMF network element 106 and the PCF network element 107 through a network, and the network can be a wired network or a wireless network.

Alternatively, the wireless network or wired network described above uses standard communication techniques and/or protocols. The network is typically the Internet, but may be any network including, but not limited to, a LAN (Local Area Network ), a MAN (Metropolitan Area Network, metropolitan area network), a WAN (Wide Area Network ), a mobile, wired or wireless network, a private network, or any combination of virtual private networks. In some embodiments, the data exchanged over the network is represented using techniques and/or formats including HTML (HyperText Mark-up Language), XML (Extensible MarkupLanguage ), and the like. All or some of the links may also be encrypted using conventional encryption techniques such as SSL (Secure Socket Layer ), TLS (Transport Layer Security, transport layer security), VPN (Virtual Private Network ), ipsec (Internet ProtocolSecurity, internet protocol security), etc. In other embodiments, custom and/or dedicated data communication techniques may also be used in place of or in addition to the data communication techniques described above.

The UE 101 can be a variety of electronic devices including, but not limited to, smartphones, tablets, laptop portable computers, desktop computers, wearable devices, augmented reality devices, virtual reality devices, and the like.

Alternatively, the clients of the applications installed in different UEs 101 are the same, or clients of the same type of application based on different operating systems. The specific form of the application client may also be different based on the different terminal platforms, for example, the application client may be a mobile phone client, a PC client, etc.

The UPF network element 102, the first SMF network element 103, the second SMF network element 104, the NRF network element 105, the AMF network element 106, and the PCF network element 107 may be servers with corresponding functions.

Those skilled in the art will appreciate that the number of UEs 101, first SMF network elements 103, and second SMF network elements 104 in fig. 1 is merely illustrative, and any number of UEs and SMF network elements may be provided according to actual needs, and embodiments of the present disclosure are not limited in this respect.

Fig. 2 shows a flowchart of a disaster recovery processing method according to an embodiment of the disclosure. As shown in fig. 2, the disaster recovery processing method specifically includes the following steps S201 to S203.

Step S201: if the UPF network element detects that the first SMF network element fails or the first SMF network element recovers from the failure, the UPF network element sends a PFCP node report request message to the target SMF network element, wherein the PFCP node report request message carries a disaster recovery identifier and session disaster recovery data;

step S202: the target SMF network element sends a service update request message to the NRF network element according to the disaster recovery identifier and the session disaster recovery data;

step S203: the NRF network element sends a status notification request message to the subscribing network element, so that the subscribing network element updates the SMF network element identifier to the target SMF network element identifier.

Wherein the first SMF network element is a primary SMF network element, and the second SMF network element is a standby SMF network element. In order to determine the state of the first SMF network element, the UPF network element needs to detect the first SMF network element in real time to determine whether the first SMF network element operates normally. Specifically, the UPF network element sends a PFCP heartbeat request message to the first SMF network element; if the first SMF network element does not return the PFCP heartbeat response message, determining that the first SMF network element fails; and if the first SMF network element returns the PFCP heartbeat response message, determining that the first SMF network element operates normally. Or the times that the UPF network element does not receive the PFCP heartbeat response message reach a set threshold value or the times that the UPF network element does not receive the PFCP heartbeat response message reach a set duration, determining that the first SMF network element fails. The specific values of the set threshold and the set duration are not limited in the embodiment of the disclosure, and may be set empirically. Of course, there are other ways in which the UPF network element may detect the first SMF network element, which is not limited by the embodiments of the present disclosure.

It should be noted that, the failure of the first SMF network element includes that the link from the UPF network element to the first SMF network element is not available, and the reason why the link from the UPF network element to the first SMF network element is not available may be that the first SMF network element fails.

If the UPF network element detects that the first SMF network element fails or the first SMF network element fails to recover, the UPF network element sends a PFCP node report request message carrying disaster recovery identification and session disaster recovery data to the target SMF network element, and then the target SMF network element can trigger a service update request to the NRF network element according to the disaster recovery identification and the session disaster recovery data, and the NRF network element notifies the state notification request message to the subscription network element so as to trigger the subscription network element to update the SMF network element identification to the target SMF network element identification.

In some embodiments of the present disclosure, during the session establishment by the first SMF network element, the first SMF network element sends an N4 session modification request message to the UPF network element, where the N4 session modification request message carries session disaster recovery data.

Session disaster recovery data is information related to a PDU session, and may include: IMSI (International Mobile Subscriber Identification Number, international mobile subscriber identity), AMF ID (AMF element identification), SMF ID (SMF element identification), PCF ID (PCF element identification), CP-SEID (Control Plane-Security Environment Identity, security environment application identity of Control Plane, i.e. session identification of Control Plane), UP-SEID (User Plane-Security Environment Identity, security environment application identity of User Plane, i.e. session identification of User Plane), F-TEID (Fully Qualified Tunnel Endpoint Identifier, full tunnel endpoint identification), session Control policy and QoS (Quality of Service ) policy. The SMF ID in the session disaster recovery data sent by the first SMF network element to the UPF network element is SMF1 ID (first SMF network element identifier), and the AMF ID and PCF ID are network element identifiers for providing service currently.

In the embodiment of the disclosure, after receiving the N4 session modification request message carrying the session disaster recovery data, the UPF network element may store the session disaster recovery data, so that when the first SMF network element fails or recovers from the failure, the service may be recovered in real time according to the session disaster recovery data.

Fig. 3 shows a flow chart of setting up a session under normal operation of a first SMF network element according to an embodiment of the present disclosure. As shown in fig. 3, the session establishment procedure may include:

step S301, after UE registers network, send PDU conversation and establish the solicited message to AMF network element, AMF network element send this conversation solicited message to the first SMF network element;

step S302, a first SMF network element selects a UPF network element according to a strategy and sends an N4 session establishment request message to the UPF network element;

step S303, the UPF network element sends an N4 session establishment response message to the first SMF network element;

step S304, the first SMF network element sends an N2 session establishment request message to the gNB (base station) through the AMF network element;

step S305, gNB network element sends N2 session establishment request response message to the first SMF network element through AMF network element;

step S306, the first SMF network element sends an N4 session modification request message to the UPF network element, and the parameters of the message are expanded PFCP Session Modification Request to carry session disaster recovery data, wherein the session disaster recovery data comprises IMSI, AMF ID, SMF1 ID, PCF ID, CP-SEID, UP-SEID, F-TEID, session control strategy and QoS strategy;

Step S307, UPF network element stores session disaster tolerance data and sends N4 session modification response information to the first SMF network element;

step S308, the first SMF network element sends a session establishment acceptance message to the UE through the AMF network element;

step S309, the UE and UPF network element establish user plane channel to realize user data transmission.

It should be noted that fig. 3 illustrates a procedure for establishing a session by one UE. In the embodiment of the disclosure, one or more UEs may send a session establishment request to a first SMF network element through an AMF network element, then the first SMF network element selects a corresponding UPF network element for each UE according to a policy, sends session disaster recovery data of each UE to the corresponding UPF network element, and finally each UE establishes a user plane channel with the corresponding UPF network element, so as to implement user data transmission.

For example, the users UE1 to UE10 send a session establishment request to the SMF1 network element through the AMF network element. For users UE1 to UE5, the SMF1 network element selects a UPF1 network element to establish an N4 session, and the UPF1 network element can store session disaster tolerance data of the UE1 to the UE5, and the UE1 to the UE5 and the UPF1 network element establish a user plane channel to realize data transmission. For the users UE6 to UE10, the SMF1 network element selects the UPF2 network element to establish the N4 session, and the UPF2 network element can store session disaster tolerance data of the UE6 to the UE10, and the UE6 to the UE10 and the UPF2 network element establish a user plane channel to realize data transmission.

In the disaster recovery processing method provided by the embodiment of the disclosure, under the condition that the first SMF network element operates normally, the UE establishes a session with the first SMF network element, and in the session establishment process, the first SMF network element sends session disaster recovery data to the UPF network element, so that the UPF network element stores the session disaster recovery data, and in this way, when the first SMF network element fails or the first SMF network element fails to recover, the UPF network element can send the session disaster recovery data to the target SMF network element, so that the target SMF network element can recover services in real time according to the session disaster recovery data. And the session disaster recovery data is stored through the existing signaling interaction flow, so that the signaling is not additionally increased, the synchronous backup of the session disaster recovery data is not required, the cost is not additionally increased, and the consumption of additional resources is reduced.

Next, a specific process of disaster recovery processing in the case where the first SMF network element fails and the first SMF network element fails to recover will be described, respectively.

If the UPF network element detects that the first SMF network element fails, the target SMF network element is a second SMF network element, and the disaster recovery identifier is a disaster recovery switching identifier, namely the UPF network element sends a PFCP node report request message carrying the disaster recovery switching identifier and session disaster recovery data to the second SMF network element. Wherein the second SMF network element may be an available SMF network element other than the first SMF network element in a POOL (a resource POOL composed of a plurality of SMF network elements); the SMF ID in the session disaster recovery data is an SMF1 ID (first SMF network element identification). And then, the second SMF network element can trigger a service update request to the NRF network element according to the disaster recovery switching identification and the session disaster recovery data, and the NRF network element notifies the subscription network element of the state notification request message so as to trigger the subscription network element to update the SMF network element identification to the second SMF network element identification.

In some embodiments of the present disclosure, the disaster recovery processing method further includes: if the first SMF network element fails, the UPF network element sends a PFCP node report request message carrying disaster recovery identification and session disaster recovery data to the second SMF network element, and then the UPF network element updates the first SMF network element identification in the stored session disaster recovery data to the second SMF network element identification.

After the first SMF network element fails, the SMF network element identifier in the session disaster recovery data sent by the UPF network element to the second SMF network element is SMF1 ID, so that the second SMF network element can definitely fail to be the first SMF network element, and needs to take over the first SMF network element. Then, the UPF network element modifies the SMF network element identifier in the session disaster recovery data from the SMF1 ID to the SMF2 ID (second SMF network element identifier), so that the session disaster recovery data stored by the UPF network element is the identifier of the second SMF network element for taking over, and the session disaster recovery data stored by the UPF network element can be ensured to be the latest PDU session related information.

In some embodiments of the present disclosure, the disaster recovery processing method further includes: the second SMF network element sends a PFCP node reporting response message to the UPF network element.

After detecting that the first SMF network element fails, the UPF network element sends a PFCP node report request message carrying disaster recovery switching identification and session disaster recovery data to the second SMF network element, and then the second SMF network element returns a PFCP node report response message to the UPF network element.

In some embodiments of the present disclosure, the disaster recovery processing method further includes: the NRF network element detects that the first SMF network element has failed.

The NRF network element is mainly used for providing registration and discovery functions of the network element or services provided by the network element. After the NRF network element detects that the first SMF network element fails, the subscription network element may be notified that the first SMF network element fails, so that the subscription network element knows that the first SMF network element fails, and performs corresponding update.

In some embodiments of the present disclosure, the sending, by the target SMF network element, a service update request message to the NRF network element according to the disaster recovery identifier and the session disaster recovery data may include: the second SMF network element triggers a service update request message to the NRF network element according to the disaster recovery switching identification and the session disaster recovery data, wherein the service update request message carries an AMF network element identification, a PCF network element identification, a first SMF network element identification and a second SMF network element identification. And the NRF network element sends a service update response message to the second SMF network element after receiving the service update request message sent by the second SMF network element.

After receiving the PFCP node report request message carrying the disaster recovery switching identification and the session disaster recovery data, the second SMF network element initiates a service update request message to the NRF network element, and carries the SMF2ID and the AMF ID, PCF ID and SMF1 ID in the session disaster recovery data through the extension parameters. Wherein, AMF ID and PCF ID are subscription network element identifications, SMF1 ID is failed SMF network element identification, SMF2ID is taken over SMF network element identification. The NRF network element may send a status notification request message to the AMF network element and the PCF network element, notifying the AMF network element and the PCF network element to replace the SMF1 ID with the SMF2 ID. The status notification request message is used for indicating that the first SMF network element identifier is updated to the second SMF network element identifier, and the specific status notification request message extension parameter carries the replacement of the SMF1 ID to the SMF2 ID.

In some embodiments of the present disclosure, the NRF network element sending a status notification request message to the subscribing network element, so that the subscribing network element updates the SMF network element identifier to the target SMF network element identifier, may include:

(1) And the NRF network element sends a state notification request message to the AMF network element according to the AMF network element identifier so that the first SMF network element identifier of the AMF network element update session context is a second SMF network element identifier.

And the NRF network element sends a state notification request message to the AMF network element according to the AMF ID, and notifies the AMF network element to update the SMF1 ID of the session context to be the SMF2 ID. After receiving the state notification request message sent by the NRF network element, the AMF network element updates the SMF1 ID of the session context to the SMF2 ID, and sends a state notification response message to the NRF network element.

(2) And the NRF network element sends a status notification request message to the PCF network element according to the PCF network element identifier, so that the first SMF network element identifier of the PCF network element updating session policy is a second SMF network element identifier.

And the NRF network element sends a state notification request message to the PCF network element according to the PCF ID, and notifies the PCF network element to update the SMF1 ID of the session context to be the SMF2 ID. After receiving the state notification request message sent by the NRF network element, the PCF network element updates the SMF1 ID of the session policy to the SMF2 ID, and sends a state notification response message to the NRF network element.

After receiving the PFCP node report request message carrying the disaster recovery switching identifier and the session disaster recovery data, the second SMF network element may trigger a service update request to the NRF network element according to the disaster recovery switching identifier and the session disaster recovery data, and the NRF network element notifies the AMF network element and the PCF network element of the status notification request message, so as to trigger the AMF network element and the PCF network element to update the first SMF network element identifier to the second SMF network element identifier, thereby ensuring subsequent interactive update of the session, and realizing uninterrupted user data transmission.

Fig. 4 shows a flowchart of a disaster recovery processing method in a case where a first SMF network element fails according to an embodiment of the present disclosure. As shown in fig. 4, the flow of the disaster recovery processing method may include:

step S401, if the first SMF network element is normal, the first SMF network element provides service, and normal data transmission is realized between the UE and the UPF network element;

step S402, the UPF network element detects that the first SMF network element fails;

step S403, UPF network element starts disaster recovery session processing function, selects second SMF network element to make session switch, generates PFCP Node Report Request message (PFCP node report request message), carries disaster recovery switch identification and session disaster recovery data through message expansion parameter, the session disaster recovery data is all session disaster recovery data under the first SMF network element stored before, specifically including IMSI, AMF ID, SMF1 ID, PCF ID, CP-SEID, UP-SEID, F-TEID, session control strategy and QoS strategy, UPF network element sends PFCP Node Report Request message to second SMF network element; and the UPF network element modifies the SMF1 ID in the session disaster recovery data into the SMF2 ID;

Step S404, the second SMF network element sends a PFCP node report response message to the UPF network element;

step S405, a second SMF network element starts a disaster recovery take-over processing function, triggers a service update request message to an NRF network element according to a disaster recovery switching identifier and session disaster recovery data, and carries an AMF ID, a PCF ID, a failed SMF1 ID and a taken-over SMF2 ID related to a disaster recovery session through message expansion parameters;

step S406, the NRF network element sends a service update response message to the second SMF network element;

step S407, the NRF network element detects that the first SMF network element fails, and the specific NRF network element can detect that the first SMF network element fails through a heartbeat message;

step S408, the NRF network element starts the disaster recovery processing function of the SMF network element, and sends a status notification request message to the AMF network element, wherein the status notification request message is used for indicating the AMF network element to change the SMF1 ID into the SMF2 ID, and specifically, the SMF1 ID is changed into the SMF2 ID through the message extension parameter;

step S409, AMF network element sends state notice response message to NRF network element, and starts disaster tolerant session keeping function, updates SMF1 ID of session context as SMF2 ID, keeps original session;

step S410, the NRF network element starts the disaster recovery processing function of the SMF network element, and sends a status notification request message to the PCF network element, wherein the status notification request message is used for indicating the PCF network element to change the SMF1 ID into the SMF2 ID, and specifically, the SMF1 ID is changed into the SMF2 ID through the message extension parameter;

Step S411, PCF network element sends state notification response message to NRF network element, and starts session address update function, and the SMF1 ID of update session strategy is SMF2 ID;

step S412, the AMF network element, the PCF network element and the second SMF network element update the session control information, switch the session to the second SMF network element, and continue transmitting data between the UE and the UPF network element, so as to realize uninterrupted user data transmission.

The disaster recovery processing method shown in fig. 4 is described by taking one UE as an example. As already explained above, there may be one or more UEs establishing a session with the first SMF network element, each UE corresponding to a respective UPF network element. For each UPF network element, after detecting that the first SMF network element fails, a different second SMF network element may be selected to take over the first SMF network element.

In the above description, the example that "the user UE1 to UE10 send the session establishment request to the SMF1 network element through the AMF network element" is described, after the UPF1 network element detects that the SMF1 network element fails, the SMF2 network element may be selected to take over the SMF1 network element, and the disaster recovery switching identifier and the session disaster recovery data from the UE1 to UE5 are sent to the SMF2 network element. Then, the SMF2 network element may trigger a service update request to the NRF network element according to the disaster recovery handover identifier and session disaster recovery data from the UE1 to the UE5, and the NRF network element notifies the AMF network element and the PCF network element of the status notification request message, so as to trigger the AMF network element and the PCF network element to update the service SMF network elements from the UE1 to the UE5 to the SMF2 network element. Thus, the original session service from UE1 to UE5 on the SMF1 network element can be switched to the SMF2 network element in real time.

After detecting that the SMF1 network element fails, the UPF2 network element may select the SMF3 network element to take over the SMF1 network element, and send the disaster recovery switching identifier and session disaster recovery data from the UE6 to the UE10 to the SMF3 network element. Then, the SMF3 network element may trigger a service update request to the NRF network element according to the disaster recovery handover identifier and session disaster recovery data from the UE6 to the UE10, and the NRF network element notifies the AMF network element and the PCF network element of the status notification request message, so as to trigger the AMF network element and the PCF network element to update the service SMF network element from the UE6 to the UE10 to the SMF3 network element. Thus, the original session service from UE6 to UE10 on the SMF1 network element can be switched to the SMF3 network element in real time.

And secondly, if the UPF network element detects that the first SMF network element is in fault recovery, the target SMF network element is the first SMF network element, and the disaster recovery mark is a disaster recovery switching mark, namely the UPF network element sends a PFCP node report request message carrying the disaster recovery switching mark and session disaster recovery data to the first SMF network element. The SMF ID in the session disaster recovery data is an SMF2 ID (first SMF network element identifier). Then, the first SMF network element may trigger a service update request to the NRF network element according to the disaster recovery switch back identifier and the session disaster recovery data, and the NRF network element notifies the subscription network element of the status notification request message, so as to trigger the subscription network element to update the SMF network element identifier to the first SMF network element identifier.

In some embodiments of the present disclosure, the disaster recovery processing method further includes: if the first SMF network element is recovered from faults, after the UPF network element sends a PFCP node report request message carrying disaster recovery identification and session disaster recovery data to the first SMF network element, the UPF network element updates a second SMF network element identification in the stored session disaster recovery data to the first SMF network element identification.

After the first SMF network element recovers from the fault, the SMF network element identifier in the session disaster recovery data sent by the UPF network element to the first SMF network element is an SMF2 ID, so that the first SMF network element may explicitly need to take over the second SMF network element. Then, the UPF network element modifies the SMF network element identification in the session disaster recovery data from the SMF2 ID to the SMF1 ID, so that the session disaster recovery data stored by the UPF network element is the identification of the first SMF network element for fault recovery, and the session disaster recovery data stored by the UPF network element can be ensured to be the latest PDU session related information.

In some embodiments of the present disclosure, the disaster recovery processing method further includes: the first SMF network element sends a PFCP node reporting response message to the UPF network element.

After detecting that the first SMF network element is in fault recovery, the UPF network element sends a PFCP node report request message carrying disaster recovery switch back identification and session disaster recovery data to the first SMF network element, and then the first SMF network element returns a PFCP node report response message to the UPF network element.

In some embodiments of the present disclosure, the disaster recovery processing method further includes: the NRF network element detects a first SMF network element failure recovery.

After the NRF network element detects the first SMF network element fault recovery, the subscription network element may be notified of the first SMF network element fault recovery, so that the subscription network element knows the first SMF network element fault recovery, and further performs corresponding update.

In some embodiments of the present disclosure, the sending, by the target SMF network element, a service update request message to the NRF network element according to the disaster recovery identifier and the session disaster recovery data may include: the first SMF network element triggers a service update request message to the NRF network element according to the disaster recovery switch back identification and the session disaster recovery data, wherein the service update request message carries an AMF network element identification, a PCF network element identification, a first SMF network element identification and a second SMF network element identification. And the NRF network element sends a service update response message to the first SMF network element after receiving the service update request message sent by the first SMF network element.

After receiving the PFCP node report request message carrying the disaster recovery switch back identification and the session disaster recovery data, the first SMF network element initiates a service update request message to the NRF network element, and carries the SMF1ID and the AMF ID, PCF ID and SMF2 ID in the session disaster recovery data through the extension parameters. Wherein, AMF ID and PCF ID are subscription network element identifications, SMF1ID is fault recovery SMF network element identification, SMF2 ID is takeover SMF network element identification. The NRF network element may send a status notification request message to the AMF network element and the PCF network element, notifying the AMF network element and the PCF network element to replace the SMF2 ID with the SMF1 ID. The status notification request message is used for indicating that the second SMF network element identifier is updated to the first SMF network element identifier, and the specific status notification request message extension parameter carries the replacement of the SMF2 ID to the SMF1 ID.

(1) And the NRF network element sends a state notification request message to the AMF network element according to the AMF network element identifier so that the second SMF network element identifier of the AMF network element update session context is the first SMF network element identifier.

And the NRF network element sends a state notification request message to the AMF network element according to the AMF ID, and notifies the AMF network element to update the SMF2 ID of the session context to be the SMF1 ID. After receiving the state notification request message sent by the NRF network element, the AMF network element updates the SMF2 ID of the session context to the SMF1 ID, and sends a state notification response message to the NRF network element.

(2) And the NRF network element sends a status notification request message to the PCF network element according to the PCF network element identifier so that the second SMF network element identifier of the PCF network element updating session policy is the first SMF network element identifier.

And the NRF network element sends a state notification request message to the PCF network element according to the PCF ID, and notifies the PCF network element to update the SMF2 ID of the session context to be the SMF1 ID. After receiving the state notification request message sent by the NRF network element, the PCF network element updates the SMF2 ID of the session policy to the SMF1 ID, and sends a state notification response message to the NRF network element.

After receiving the PFCP node report request message carrying the disaster recovery switch back identifier and the session disaster recovery data, the first SMF network element may trigger a service update request to the NRF network element according to the disaster recovery switch back identifier and the session disaster recovery data, and the NRF network element notifies the AMF network element and the PCF network element of the status notification request message, so as to trigger the AMF network element and the PCF network element to update the second SMF network element identifier to the first SMF network element identifier, thereby ensuring subsequent interactive update of the session and realizing uninterrupted user data transmission.

Fig. 5 shows a flowchart of a disaster recovery processing method in the case of failure recovery of the first SMF network element according to an embodiment of the present disclosure. As shown in fig. 5, the flow of the disaster recovery processing method may include:

step S501, in case of failure of the first SMF network element, the second SMF network element provides service, and normal data transmission is realized between the UE and the UPF network element;

step S502, UPF network element detects first SMF network element fault recovery;

step S503, the UPF network element starts the disaster recovery session processing function, selects the second SMF network element to carry out session switching back, generates PFCP Node Report Request information (PFCP node report request information), carries disaster recovery switching back identification and session disaster recovery data through information expansion parameters, the session disaster recovery data can comprise IMSI, AMF ID, SMF2 ID, PCF ID, CP-SEID, UP-SEID, F-TEID, session control strategy and QoS strategy, and the UPF network element sends PFCP Node Report Request information to the first SMF network element; and the UPF network element modifies the SMF2 ID in the session disaster recovery data into the SMF1 ID;

Step S504, the first SMF network element sends a PFCP node report response message to the UPF network element;

step S505, the first SMF network element starts the disaster recovery takeover processing function, triggers the service update request message to the NRF network element according to the disaster recovery switching identification and the session disaster recovery data, and carries the AMF ID, PCF ID, fault recovery SMF1 ID and takeover SMF2ID related to the disaster recovery session through the message expansion parameters;

step S506, the NRF network element sends a service update response message to the first SMF network element;

step S507, the NRF network element detects the first SMF network element fault recovery, and the specific NRF network element can detect the first SMF network element fault recovery through a heartbeat message;

step S508, the NRF network element starts the disaster recovery processing function of the SMF network element, and sends a status notification request message to the AMF network element, wherein the status notification request message is used for indicating the AMF network element to change the SMF2ID into the SMF1 ID, and specifically, the SMF2ID is changed into the SMF1 ID through the message extension parameter;

step S509, the AMF network element sends a status notification response message to the NRF network element, and starts a disaster recovery session keeping function, updates the SMF2ID of the session context to be the SMF1 ID, and keeps the original session;

step S510, NRF network element starts SMF network element disaster recovery processing function, sends state notification request message to PCF network element, the state notification request message is used for instructing PCF network element to change SMF2ID into SMF1 ID, and specifically, the SMF2ID is changed into SMF1 ID through message extension parameter carrying;

Step S511, PCF network element sends state notification response message to NRF network element, and starts session address updating function, and the SMF2 ID of updating session strategy is SMF1 ID;

in step S512, the AMF network element, the PCF network element, and the first SMF network element have updated session control information, and the session is switched to the first SMF network element, so that data is continuously transmitted between the UE and the UPF network element, and user data transmission is not interrupted.

The disaster recovery processing method shown in fig. 5 is described by taking one UE as an example. As already explained above, there may be one or more UEs establishing a session with the first SMF network element, each UE corresponding to a respective UPF network element. For each UPF network element, after detecting that the first SMF network element is failed and recovering, session services on all second SMF network elements may be switched back to the first SMF network element in real time.

The above example of "the user UE1 to UE10 send the session establishment request to the SMF1 network element through the AMF network element" is described, where after detecting that the SMF1 network element fails to recover, the UPF1 network element sends the disaster recovery switch back identifier and the session disaster recovery data of the UE1 to UE5 to the SMF1 network element. Then, the SMF1 network element may trigger a service update request to the NRF network element according to the disaster recovery switch back identifier and session disaster recovery data from the UE1 to the UE5, and the NRF network element notifies the AMF network element and the PCF network element of the status notification request message, so as to trigger the AMF network element and the PCF network element to update the service SMF network elements from the UE1 to the UE5 to the SMF1 network element. Thus, the original session service from UE1 to UE5 on the SMF2 network element can be switched back to the SMF1 network element in real time.

After detecting that the SMF1 network element is recovered, the UPF2 network element sends a disaster recovery switch back identification and session disaster recovery data from the UE6 to the UE10 to the SMF1 network element. Then, the SMF1 network element may trigger a service update request to the NRF network element according to the disaster recovery switch back identifier and session disaster recovery data from the UE6 to the UE10, and the NRF network element notifies the AMF network element and the PCF network element of the status notification request message, so as to trigger the AMF network element and the PCF network element to update the service SMF network element from the UE6 to the UE10 to the SMF1 network element. In this way, the original session service from UE6 to UE10 on the SMF3 network element can be switched back to the SMF1 network element in real time.

Fig. 6 shows a flowchart of a disaster recovery processing method according to another embodiment of the present disclosure. As shown in fig. 6, the disaster recovery processing method may include:

step S601, UE establishes PDU conversation through the first SMF network element, and in the process of establishing PDU conversation, UPF network element stores conversation disaster tolerance data, wherein the conversation disaster tolerance data comprises IMSI, AMF ID, SMF1 ID, PCF ID, CP-SEID, UP-SEID, F-TEID, conversation control strategy and QoS strategy;

step S602, a UPF network element detects that a first SMF network element has a fault;

step S603, a UPF network element starts a disaster recovery session processing function, selects a second SMF network element to perform session switching, sends a PFCP node report request message to the second SMF network element, carries a disaster recovery switching identifier and session disaster recovery data through a message extension parameter, and modifies an SMF1 ID in the session disaster recovery data into an SMF2 ID; receiving a PFCP node report response message returned by the second SMF network element;

Step S604, the second SMF network element starts a disaster recovery take-over processing function, triggers a service update request message to the NRF network element according to a disaster recovery switching identifier and session disaster recovery data, and carries an AMF ID, a PCF ID, a failed SMF1 ID and a taken-over SMF2 ID related to a disaster recovery session through message expansion parameters; receiving a service update response message sent by an NRF network element;

step S605, the NRF network element detects that the first SMF network element fails, and the specific NRF network element may detect that the first SMF network element fails through a heartbeat message;

step S606, the NRF network element starts the disaster recovery processing function of the SMF network element, and sends a status notification request message to the AMF network element to notify the AMF network element to replace the SMF1 ID with the SMF2 ID; the AMF network element starts a disaster recovery session maintaining function, updates the SMF1 ID of the session context to be the SMF2 ID, and maintains the original session;

step S607, the NRF network element starts the disaster recovery processing function of the SMF network element, and sends a status notification request message to the PCF network element to notify the PCF network element to replace the SMF1 ID with the SMF2 ID; the PCF network element starts a session address updating function, and the SMF1 ID of the session policy is updated to be the SMF2 ID;

step S608, the AMF network element, the PCF network element and the second SMF network element update the session control information, the session is switched to the second SMF network element, and the data is continuously transmitted between the UE and the UPF network element, so that the user data transmission is not interrupted;

Step S609, the UPF network element detects the fault recovery of the first SMF network element;

step S610, a UPF network element starts a disaster recovery session processing function, a first SMF network element is selected to carry out session switching back, a PFCP node report request message is sent to the first SMF network element, a disaster recovery switching back identifier and session disaster recovery data are carried through message expansion parameters, and the UPF network element modifies an SMF2 ID in the session disaster recovery data into an SMF1 ID; receiving a PFCP node report response message returned by the first SMF network element;

step S611, the first SMF network element starts the disaster recovery takeover processing function, triggers a service update request message to the NRF network element according to the disaster recovery switch back identification and the session disaster recovery data, and carries an AMF ID, a PCF ID, a fault recovery SMF1 ID and a takeover SMF2 ID related to the disaster recovery session through message expansion parameters; receiving a service update response message sent by an NRF network element;

step S612, the NRF network element detects the first SMF network element fault recovery, and the specific NRF network element can detect the first SMF network element fault recovery through a heartbeat message;

step S613, the NRF network element starts the disaster recovery processing function of the SMF network element, and sends a status notification request message to the AMF network element to notify the AMF network element to replace the SMF2 ID with the SMF1 ID; the AMF network element starts a disaster recovery session maintaining function, updates the SMF2 ID of the session context to be the SMF1 ID, and maintains the original session;

Step S614, the NRF network element starts the disaster recovery processing function of the SMF network element, and sends a status notification request message to the PCF network element to notify the PCF network element to replace the SMF2 ID with the SMF1 ID; the PCF network element starts a session address updating function, and the SMF2 ID of the session policy is updated to be the SMF1 ID;

in step S615, the AMF network element, the PCF network element, and the first SMF network element have updated session control information, and the session is switched back to the first SMF network element, so that data is continuously transmitted between the UE and the UPF network element, and user data transmission is not interrupted.

Step S601 is session establishment, in which the UPF network element may store session disaster recovery data, so as to recover services in real time through the session disaster recovery data when the first SMF network element fails or recovers from a failure.

Step S602 to step S608 are disaster recovery processing methods under the condition that the first SMF network element fails. In this case, the UPF network element may send the disaster recovery switching identifier and the session disaster recovery data to the second SMF network element, and the second SMF network element may trigger a service update request to the NRF network element according to the disaster recovery switching identifier and the session disaster recovery data, and the NRF network element may notify the AMF network element and the PCF network element of the status notification request message, so as to trigger the AMF network element and the PCF network element to update the SMF network element identifier to the second SMF network element identifier. Therefore, the original session service of the first SMF network element can be switched to the second SMF network element in real time, the uninterrupted transmission of user data can be ensured, and the switching of the SMF network element can be completed under the condition that the UE does not sense.

Step S609 to step S615 are disaster recovery processing methods under the condition of failure recovery of the first SMF network element. In this case, the UPF network element may send the disaster recovery switch back identifier and the session disaster recovery data to the first SMF network element, and the first SMF network element may trigger a service update request to the NRF network element according to the disaster recovery switch back identifier and the session disaster recovery data, and the NRF network element may notify the AMF network element and the PCF network element of the status notification request message, so as to trigger the AMF network element and the PCF network element to update the SMF network element identifier to the first SMF network element identifier. Therefore, the first SMF network element with fault recovery can recover the original service load, and the POOL load balance of the SMF network element is recovered in real time, so that the risk of unstable service caused by unbalanced POOL load is avoided, and the stable and reliable operation of the POOL is ensured.

Fig. 7 is a schematic diagram of a disaster recovery processing system according to another embodiment of the disclosure. As shown in fig. 7, the disaster recovery processing system may include: UPF network element 701, SMF network element 702, NRF network element 703, AMF network element 704, and PCF network element 705.

The UPF network element 701 may include an information storage module 7011 and a disaster recovery session processing module 7012. The information storage module 7011 is configured to: session disaster recovery data including IMSI, AMF ID, SMF ID, PCF ID, CP-SEID, UP-SEID, F-TEID, session control policy, and QoS policy is stored. The disaster recovery session processing module 7012 is configured to: determining that the main SMF network element is a first SMF network element and the standby SMF network element is a second SMF network element according to the preconfigured data; under the condition that the first SMF network element is detected to be faulty, a PFCP node report request message carrying disaster recovery switching identification and session disaster recovery data is sent to a second SMF network element; and under the condition that the first SMF network element fault recovery is detected, sending a PFCP node report request message carrying the disaster recovery switch back identification and the session disaster recovery data to the first SMF network element.

The SMF network element 702 may include a disaster recovery takeover processing module 7021, and the SMF network element 702 may be a first SMF network element or a second SMF network element.

If the SMF network element 702 is the first SMF network element, the disaster recovery takeover processing module 7021 is configured to: in the process of establishing PDU session, an N4 session modification request message is sent to UPF network element 701, and the request message carries session disaster tolerance data; receiving a PFCP node report request message sent by the UPF network element 701 under the condition that the UPF network element 701 detects that the first SMF network element is in fault recovery, wherein the message comprises a disaster recovery switch back identifier and session disaster recovery data, and an SMF ID in the session disaster recovery data is an SMF2 ID; and sending a service update request message to the NRF network element according to the disaster recovery switch back identification and the session disaster recovery data, wherein the service update request message carries an AMF ID, a PCF ID, an SMF1 ID and an SMF2 ID.

If the SMF network element 702 is a second SMF network element, the disaster recovery takeover processing module 7021 is configured to: receiving a PFCP node report request message sent by the UPF network element 701 when the UPF network element 701 detects that the first SMF network element sends a fault, wherein the message comprises a disaster recovery switch back identifier and session disaster recovery data, and an SMF ID in the session disaster recovery data is an SMF1 ID; and sending a service update request message to the NRF network element according to the disaster recovery switch back identification and the session disaster recovery data, wherein the service update request message carries an AMF ID, a PCF ID, an SMF1 ID and an SMF2 ID.

NRF network element 703 may include SMF disaster recovery processing module 7031 for: in case of failure of the first SMF network element, receiving a service update request message sent by the second SMF network element, and then sending a status notification request message to the AMF network element 704 and the PCF network element 705 to trigger the AMF network element 704 and the PCF network element 705 to update the SMF1 ID to the SMF2 ID; and in the case of failure recovery of the first SMF network element, receiving a service update request message sent by the first SMF network element, and then sending a status notification request message to the AMF network element 704 and the PCF network element 705 to trigger the AMF network element 704 and the PCF network element 705 to update the SMF2 ID to the SMF1 ID.

The AMF network element 704 may include a disaster recovery session maintenance module 7041 configured to: in case of failure of the first SMF network element, receiving a status notification request message sent by the NRF network element 703, and updating the SMF1 ID of the session context to be the SMF2 ID; and receiving a state notification request message sent by the NRF network element 703 in the case of failure recovery of the first SMF network element, and updating the SMF2 ID of the session context to the SMF1 ID.

PCF network element 705 may include session address update module 7051 to: receiving a state notification request message sent by the NRF network element 703 when the first SMF network element fails, and updating the SMF1 ID of the session policy to be an SMF2 ID; and receiving a state notification request message sent by the NRF network element 703 in the case of failure recovery of the first SMF network element, and updating the SMF2 ID of the session policy to be the SMF1 ID.

Fig. 8 shows a block diagram of an electronic device in an embodiment of the disclosure. An electronic device 800 according to such an embodiment of the invention is described below with reference to fig. 8. The electronic device 800 shown in fig. 8 is merely an example and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.

As shown in fig. 8, the electronic device 800 is embodied in the form of a general purpose computing device. Components of electronic device 800 may include, but are not limited to: the at least one processing unit 810, the at least one storage unit 820, a bus 830 connecting the different system components (including the storage unit 820 and the processing unit 810), and a display unit 840.

Wherein the storage unit stores program code that is executable by the processing unit 810 such that the processing unit 810 performs steps according to various exemplary embodiments of the present invention described in the above section of the "exemplary method" of the present specification.

The storage unit 820 may include readable media in the form of volatile storage units, such as Random Access Memory (RAM) 8201 and/or cache memory 8202, and may further include Read Only Memory (ROM) 8203.

Storage unit 820 may also include a program/utility 8204 having a set (at least one) of program modules 8205, such program modules 8205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.

Bus 830 may be one or more of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

The electronic device 800 may also communicate with one or more external devices 870 (e.g., keyboard, pointing device, bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 800, and/or any device (e.g., router, modem, etc.) that enables the electronic device 800 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 850. Also, electronic device 800 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 860. As shown, network adapter 860 communicates with other modules of electronic device 800 over bus 830. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 800, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.

In an exemplary embodiment of the present disclosure, a computer-readable storage medium having stored thereon a program product capable of implementing the method described above in the present specification is also provided. In some possible embodiments, the various aspects of the invention may also be implemented in the form of a program product comprising program code for causing a terminal device to carry out the steps according to the various exemplary embodiments of the invention as described in the "exemplary methods" section of this specification, when said program product is run on the terminal device.

A program product for implementing the above-described method according to an embodiment of the present invention may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may be run on a terminal device such as a personal computer. However, the program product of the present invention is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The computer readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).

It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.

Furthermore, although the steps of the methods in the present disclosure are depicted in a particular order in the drawings, this does not require or imply that the steps must be performed in that particular order or that all illustrated steps be performed in order to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform, etc.

From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, including several instructions to cause a computing device (may be a personal computer, a server, a mobile terminal, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A disaster recovery processing method, the method comprising:

if a user plane function UPF network element detects that a first session management function SMF network element fails or the first SMF network element fails to recover, the UPF network element sends a Packet Forwarding Control Protocol (PFCP) node report request message to a target SMF network element, wherein the PFCP node report request message carries a disaster recovery identifier and session disaster recovery data;

The target SMF network element sends a service update request message to a network warehouse function NRF network element according to the disaster recovery identifier and the session disaster recovery data;

and the NRF network element sends a state notification request message to a subscription network element so that the subscription network element updates the SMF network element identifier to the target SMF network element identifier.

2. The method of claim 1, wherein the session disaster recovery data comprises: international mobile subscriber identity IMSI, access and mobility management function AMF network element identification, SMF network element identification, policy control function PCF network element identification, session identification CP-SEID of control plane, session identification UP-SEID of user plane, full tunnel endpoint identification F-TEID, session control policy and quality of service QoS policy.

3. The method of claim 2 wherein if the UPF network element detects that the first SMF network element is faulty, the target SMF network element is a second SMF network element, the disaster recovery identifier is a disaster recovery switching identifier, and the SMF network element identifier is the first SMF network element identifier.

4. A method according to claim 3, wherein the target SMF network element sends a service update request message to an NRF network element according to the disaster recovery identifier and the session disaster recovery data, comprising:

5. The method of claim 4, wherein the status notification request message is configured to instruct updating the first SMF network element identification to the second SMF network element identification;

the NRF network element sends a status notification request message to a subscription network element, so that the subscription network element updates an SMF network element identifier to the target SMF network element identifier, including:

the NRF network element sends the state notification request message to an AMF network element according to the AMF network element identifier, so that the first SMF network element identifier of the AMF network element update session context is the second SMF network element identifier;

and the NRF network element sends the state notification request message to the PCF network element according to the PCF network element identifier, so that the first SMF network element identifier of the PCF network element updating session policy is the second SMF network element identifier.

6. The method of claim 2 wherein if the UPF network element detects that the first SMF network element is failed to recover, the target SMF network element is the first SMF network element, the disaster recovery flag is a disaster recovery switch back flag, and the SMF network element flag is the second SMF network element flag.

7. The method of claim 6, wherein the target SMF network element sending a service update request message to an NRF network element according to the disaster recovery flag and the session disaster recovery data, comprising:

and triggering the service update request message to the NRF network element by the first SMF network element according to the disaster recovery switching back identification and the session disaster recovery data, wherein the service update request message carries the AMF network element identification, the PCF network element identification, the first SMF network element identification and the second SMF network element identification.

8. The method of claim 6, wherein the status notification request message is configured to instruct updating the second SMF network element identification to the first SMF network element identification;

The NRF network element sends the state notification request message to an AMF network element according to the AMF network element identifier, so that the second SMF network element identifier of the AMF network element update session context is the first SMF network element identifier;

and the NRF network element sends the state notification request message to the PCF network element according to the PCF network element identifier, so that the second SMF network element identifier of the PCF network element updating session policy is the first SMF network element identifier.

9. The method according to any one of claims 1 to 8, further comprising:

the NRF network element detects that the first SMF network element breaks down or the first SMF network element breaks down and recovers.

10. The method according to any one of claims 1 to 8, further comprising:

in the process of establishing a session through the first SMF network element, the first SMF network element sends an N4 session modification request message to the UPF network element, wherein the N4 session modification request message carries the session disaster recovery data, and the SMF network element identifier in the session disaster recovery data is the first SMF network element identifier;

if the first SMF network element fails, the UPF network element updates the first SMF network element identifier in the session disaster recovery data to the second SMF network element identifier;

And if the first SMF network element is recovered from faults, the UPF network element updates the second SMF network element identifier in the session disaster recovery data to the first SMF network element identifier.

11. A disaster recovery processing system, comprising: a UPF network element, a first SMF network element, a second SMF network element and an NRF network element;

the UPF network element is used for sending a PFCP node report request message carrying disaster recovery switching identification and session disaster recovery data to the second SMF network element under the condition that the first SMF network element is detected to be faulty; under the condition that the first SMF network element fault recovery is detected, sending a PFCP node report request message carrying a disaster recovery switching back identifier and the session disaster recovery data to the first SMF network element;

the first SMF network element is configured to send a service update request message to the NRF network element according to the disaster recovery switching identifier and the session disaster recovery data when the first SMF network element fails;

the second SMF network element is configured to send a service update request message to the NRF network element according to the disaster recovery switch back identifier and the session disaster recovery data when the first SMF network element fails to recover;

The NRF network element is configured to send a status notification request message to a subscription network element when the first SMF network element fails, so that the subscription network element updates an SMF network element identifier to the second SMF network element identifier; and sending a status notification request message to the subscribing network element under the condition of the first SMF network element fault recovery, so that the subscribing network element updates the SMF network element identifier to the first SMF network element identifier.

12. An electronic device, comprising:

one or more processors;

storage means configured to store one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1 to 10.

13. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the method according to any one of claims 1 to 10.