CN117675530A - Disaster recovery method, first network storage function network element and storage medium - Google Patents

Abstract

The application discloses a disaster recovery method, which comprises the following steps: and under the condition that a data synchronization interface between the first NRF and the second NRF fails, obtaining the performance information of the first NF managed by the second NRF. Wherein the performance information includes at least one of: an operating state of the first NF; configuration parameters of the first NF. The application also discloses a first network storage function network element and a computer readable storage medium.

Description

Disaster recovery method, first network storage function network element and storage medium

Technical Field

The present disclosure relates to the field of computers, and in particular, to a disaster recovery method, a first network element with a network storage function, and a computer readable storage medium.

Background

With the development of the fifth generation mobile communication technology (5th Generation Mobile Communication Technology,5G), in the evolution process of the core Network architecture of the 5G Network, a cloud-based, virtualized technology and a Network Function (NF) -centered service Network architecture is proposed, in which a Network Function repository Function (NF Repository Function, NRF) is a Network Function that provides registration and discovery functions for serving NF. The NRF is used as a service discovery provider to master the running states and service information of all the service network elements of the network, and needs to provide cross-region and cross-data center redundancy backup. In a backup mode supported by NRF in the related art, the NRF to be backed up transmits its own data to the NRF to be backed up through a data synchronization interface between NRFs.

However, if the data synchronization interface between NRFs is abnormal, the NRF cannot acquire information of another NF managed NF, so that when querying is performed on the NF service, there is an abnormality in the query result, and when the information of the NF changes, other NFs subscribed to the NF information cannot acquire a corresponding notification message.

Disclosure of Invention

The embodiment of the application provides a disaster recovery method, a first network storage function network element and a computer readable storage medium, and provides a scheme capable of acquiring performance information of NF managed by another NRF without resorting to synchronous links among NRFs.

In a first aspect, a disaster recovery method is provided, applied to a network element with a first network storage function, including:

obtaining performance information of a first NF managed by a second NRF under the condition that a data synchronization interface between the first NRF and the second NRF fails;

wherein the performance information includes at least one of:

an operating state of the first NF;

configuration parameters of the first NF.

In a second aspect, a first network storage function network element is provided, the first network storage function network element comprising:

an obtaining module, configured to obtain performance information of a first NF managed by a second NRF in a case where a data synchronization interface between the first NRF and the second NRF fails;

Wherein the performance information includes at least one of:

an operating state of the first NF;

configuration parameters of the first NF.

In a third aspect, a first network storage function network element, the first network storage function network element comprising:

a memory for storing executable instructions;

and the processor is used for realizing the disaster recovery method when executing the executable instructions stored in the memory.

In a fourth aspect, an embodiment of the present application provides a chip, configured to implement the foregoing disaster recovery method;

the chip comprises: and the processor is used for calling and running the computer program from the memory so that the equipment provided with the chip executes the disaster recovery method.

In a fifth aspect, embodiments of the present application provide a computer-readable storage medium storing a computer program, where the computer program causes a computer to execute the disaster recovery method described above.

In a sixth aspect, embodiments of the present application provide a computer program product including computer program instructions for causing a computer to perform the disaster recovery method described above.

In a seventh aspect, embodiments of the present application provide a computer program that, when executed on a computer, causes the computer to perform the disaster recovery method described above.

In the disaster recovery method provided in the embodiment of the present application, the method includes: and under the condition that a data synchronization interface between the first NRF and the second NRF fails, obtaining the performance information of the first NF managed by the second NRF. Wherein the performance information includes at least one of: an operating state of the first NF; configuration parameters of the first NF. That is, the present application provides a method in which, after a synchronization link between at least two NRFs that are mutually backup is abnormal, one NRF can still obtain performance information of NFs managed by other NRFs without the help of the synchronization link; thus, the problem of abnormal NF service discovery results is avoided, and when the information of the NF managed by other NRFs changes, other NF subscribed to the NF information can still obtain corresponding notification information; the method reduces the business influence caused by the problems of NF service discovery, subscription notification abnormality and the like, reduces the alarm in the communication network and enhances the operation and maintenance capability.

Drawings

Fig. 1 is a schematic diagram of the interaction of a primary NRF1 and a backup NRF2 in the related art;

FIG. 2 is a schematic diagram of the interaction of primary NRF1 and primary NRF2 in the related art;

FIG. 3 is a schematic diagram II of the interaction of primary NRF1 and primary NRF2 in the related art;

FIG. 4 is a schematic flow chart of a disaster recovery method according to an embodiment of the present disclosure;

FIG. 5 is a second flow chart of a disaster recovery method according to an embodiment of the present disclosure;

fig. 6 is a flow chart diagram III of a disaster recovery method according to an embodiment of the present application;

fig. 7 is a flow chart diagram of a disaster recovery method according to an embodiment of the present application;

fig. 8 is a schematic block diagram of a first network storage function network element provided in an embodiment of the present application;

fig. 9 is a schematic structural diagram of a communication device according to an embodiment of the present application;

FIG. 10 is a schematic block diagram of a chip provided in an embodiment of the present application;

fig. 11 is a schematic block diagram of a communication system provided in an embodiment of the present application.

Detailed Description

The following description of the technical solutions in the embodiments of the present application will be made with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be arbitrarily combined with each other.

Before explaining the present application, a main-standby disaster recovery mode and a mutual-standby disaster recovery mode supported by NRF in the related art are described herein:

as shown in fig. 1, data synchronization is maintained in real time between the primary NRF1 and the backup NRF 2. When the NF detects that the primary NRF is abnormal/unavailable, the NF can normally continue the service using the standby NRF. Wherein, the primary NRF1 is in the primary Domain Control (DC) and the standby NRF2 is in the standby DC. It should be noted that NRF data is one-way synchronous between the main and standby disaster recovery modes.

Illustratively, when NF1 uses transmission channel a, NF1 interacts with standby NRF2 using transmission channel a'. When NF2 uses transmission channel B, NF2 interacts with standby NRF2 using transmission channel B'.

As shown in fig. 2, the primary NRF1 and the primary NRF2 operate simultaneously, are backup to each other, and synchronize their own data in real time between the NRFs. Either NRF fails and the other NRF may take over the traffic of the failed NRF. When the NF detects that the primary NRF is abnormal/unavailable, the NF can normally continue the service using the standby NRF. The NRF is connected abnormally with a certain NF, so that the NRF and other NF services cannot be damaged. Wherein, the primary NRF1 is in the primary DC and the primary NRF2 is in the backup DC. In the disaster recovery mode, data between NRFs are synchronized bidirectionally.

As shown in fig. 3, data synchronization is maintained in real time between the primary NRF1 and the primary NRF 2. The NF managed by the primary NRF1 comprises NF1 and NF2; the NF managed by the primary NRF2 includes NF3. After the synchronous link between the primary NRF1 and the primary NRF2 is interrupted, if the NF3 network element is changed to be unavailable, the state of NF3 on the primary NRF2 for managing NF3 is changed to be suspend; however, since the synchronization link between the primary NRF1 and the primary NRF2 is interrupted, the primary NRF1 cannot acquire the latest state of NF3, and the state of NF3 on the primary NRF1 remains registered. When NF1 managed by the active NRF1 initiates an NF3 service discovery query to the active NRF1, the NRF1 returns a state other than NF3, which results in discovery errors.

As shown in fig. 3, data synchronization is maintained in real time between the primary NRF1 and the primary NRF 2. The NF managed by the primary NRF1 comprises NF1 and NF2; the NF managed by the primary NRF2 includes NF3. If the NF3 network element attribute is changed after the synchronization link between the primary NRF1 and the primary NRF2 is interrupted, for example, NF3 change supports slice information change, the primary NRF1 cannot acquire the latest attribute of NF3 due to the interruption of the synchronization link between the primary NRF1 and the primary NRF 2; when NF1 managed by the primary NRF1 initiates an NF3 service discovery query to the primary NRF1, the NRF1 returns a latest attribute other than NF3, which results in discovery errors and damaged service.

Fig. 4 is a flow chart of a disaster recovery method provided in an embodiment of the present application, as shown in fig. 4, where the method is applied to a first NRF in a communication network, and the communication network includes at least one first NRF and at least one second NRF, and the method includes:

step 401, in the case that a data synchronization interface between the first NRF and the second NRF fails, the first NRF obtains performance information of the first NF managed by the second NRF.

Wherein the performance information includes at least one of:

an operating state of the first NF;

configuration parameters of the first NF.

In the embodiment of the application, the first NRF and the second NRF are mutually backup, and can synchronize their own data in real time through the data synchronization interface. Here, the second NRF may be one or a plurality of; that is, the present application can be applied to a communication network in which at least two NRFs are disposed. Each NRF provides services such as registration, service discovery, and authorization for its managed NFs, and different NRFs cannot directly access between NFs managed by the NRF. Illustratively, the second NRF receives an NF discovery request from the first NF instance it manages, and provides information of the discovered NF instance (discovered) to the first NF instance.

When implementing the scheme of the present application, the first NRF and the second NRF may be functional entities such as a network element, a controller, or a server. Here, the network element may be either a network element implemented on dedicated hardware, or a software instance running on dedicated hardware, or an instance of virtualized functionality on a suitable platform.

In this embodiment of the present application, the first NF managed by the second NRF may be a network function that has completed registration on the second NRF. Here, the first NF includes, but is not limited to, an access and mobility management function (Access and Mobility Management Function, AMF), a session management function (Session Management Function, SMF), a user plane function (User Plane Function, UPF), a network slice selection function (Network Slice Selection Function, NSSF), an authentication service function (Authentication Server Function, AUSF), a unified data management (Unified Data Management, UDM) function, and a unified data warehouse (Unified Data Repository, UDR) function.

In this embodiment of the present application, the first NF managed by the second NRF may be one or multiple.

In the present embodiment, the obtaining in step 401 may be understood as active obtaining or passive obtaining or receiving. That is, there are various ways in which the performance information of the first NF may be obtained, so that, in the case that the data synchronization interface between the first NRF and the second NRF fails, it is ensured that the first NRF can obtain the performance information of the first NF managed by the second NRF. The disaster recovery backup capability of the NRF network element is enhanced, and furthermore, as the NRF relates to the interconnection and interworking functions of all the service network elements, the disaster recovery enhancement of the NRF greatly ensures the stability of the communication network.

In this embodiment, the operation state of the first NF is used to indicate whether the first NF is available, and the operation state includes a fault state, such as a suspended (suspended) state and a normal state, such as a registered (registered) state.

In this embodiment of the present application, the configuration parameters of the first NF include an attribute supported by the first NF, for example, the first NF supports slice information change.

In this embodiment of the present application, the failure of the data synchronization interface between the first NRF and the second NRF includes a failure of a communication link between the first NRF and the second NRF, and the interface in the first NRF and/or the second NRF cannot process data.

In this embodiment of the present application, part or all of the performance information of the first NF may be encrypted and/or integrity protected by using a key, and then sent to the first NRF.

The technical scheme of the embodiment of the application can be applied to various communication systems; by way of example, various communication systems include, but are not limited to, long term evolution (Long Term Evolution, LTE) systems, LTE time division duplexing (Time Division Duplex, TDD), universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS), internet of things (Internet of Things, ioT) systems, narrowband internet of things (Narrow Band Internet of Things, NB-IoT) systems, enhanced Machine-type communication (eMTC) systems, fifth generation mobile telecommunications technology (5th Generation Mobile Communication Technology,5G) communication systems, also known as New Radio, NR) communication systems, or future communication systems.

In the disaster recovery method provided in the embodiment of the present application, the method includes: and under the condition that a data synchronization interface between the first NRF and the second NRF fails, obtaining the performance information of the first NF managed by the second NRF. Wherein the performance information includes at least one of: an operating state of the first NF; configuration parameters of the first NF. That is, after the synchronization link between at least two NRFs that are mutually backup is abnormal, one NRF can still obtain performance information of NFs managed by other NRFs without the help of the synchronization link, so that the problem of abnormal NF service discovery results is avoided, and when the information of NFs managed by other NRFs changes, other NFs subscribing to the NF information can still obtain corresponding notification messages; the method reduces the business influence caused by the problems of NF service discovery, subscription notification abnormality and the like, reduces the alarm in the communication network and enhances the operation and maintenance capability.

The embodiment of the application provides a method for acquiring performance information of NF managed by another NRF without resorting to a synchronous link between NRFs, which shares the load in the synchronous link between two NRFs, reduces the load of the main NRFs in the main and standby schemes, avoids resource waste and avoids overlong message paths.

In some embodiments, obtaining the performance information of the first NF managed by the second NRF in step 401 may be achieved by:

and step A1, receiving a first message sent by the first NF.

The first message carries performance information of the first NF.

In this embodiment of the present application, the first message further carries identification information of the first NF. Here, each NF has unique identification information. In some embodiments, the identification information includes color identification, graphic identification, text identification, numerical identification, location identification, and the like. In the same communication network, different NFs may use the same type of identification information; of course, the types of the identification information of the NFs may not be completely the same, or the types of the identification information of the NFs may be completely different.

In this embodiment of the present application, the first message may be a request, a response, an indication, a reply, a heartbeat, or the like.

In this embodiment of the present application, the first NF sends the first message in the manner that: in-band, out-of-band, media, signaling, data, messages, control plane, user plane, etc. The first message can be realized by means of a media channel in the related technology, so that the first message is better compatible with the existing system and the cost for system reconstruction is reduced. In addition, when the multiple NRFs are mutually backed up, the media plane communication channel which can be established by the first NF is a one-to-many multicast/broadcast communication channel, so that only the first message is sent once through the established group/broadcast communication channel, other NRFs can receive the first message, and the sending quantity of the messages is effectively reduced.

Further, the first message includes a heartbeat (heartbeat) message, and the step A1 of receiving the first message sent by the first NF may be implemented by step a 11:

and step A11, receiving a heartbeat message sent by the first NF to the first NRF in an nth period of the plurality of periods.

The nth period is a period after the next period when the first NRF determines that the data synchronization interface between the first NRF and the second NRF fails, and n is a positive integer.

In some embodiments, the nth period is a period after a period in which the first NRF determines that the data synchronization interface between the second NRF and the first NRF is failed. That is, the nth cycle may be any cycle after the cycle in which the first NRF determines that the data synchronization interface between the second NRF and the first NRF is failed, and the present application is not limited thereto.

Here, the heartbeat message carries performance information of the first NF.

In the embodiment of the present application, the first NF managed by the second NRF may periodically send, to the first NRF, a heartbeat message carrying performance information of the first NF, so that the first NRF may master the performance information of the first NF in time; when the second NRF breaks down, the first NRF can manage the first NF, so that the influence of data synchronization link interruption on service is avoided.

It should be noted that, the NF managed by each NRF does not perceive that the link between at least two NRFs is abnormal, and may continue to interact with the NRF managed by each NRF. However, the performance information, such as the latest state, of the NF managed by the other NRF cannot be obtained between the first NRF or the second NRF, which results in abnormal NF discovery results. According to the method and the device, the NF periodically sends the heartbeat message carrying the NF performance information to the NRF, so that the NRF can timely master the NF performance information managed by the other NRF, and the problem that the NF discovery result is abnormal is effectively avoided.

In this embodiment of the present application, the period in which the first NF sends the heartbeat message to the first NRF may be preset, or may be set by the user according to an actual communication scenario. For example, the period may be set to send a heartbeat message once a day, or the period may be set to send a heartbeat message once an hour, which is not particularly limited in this application.

Further, after receiving the heartbeat message sent by the first NF in the nth cycle of the multiple cycles in step a11, the first NRF updates the performance information of the first NF stored in the first NRF to the updated performance information in the received heartbeat message sent by the first NRF. Here, the heartbeat message carries the performance information updated by the first NF.

In this embodiment of the present application, only if the performance information of the first NF carried by the heartbeat message in the nth cycle is changed compared with the performance information of the first NF stored in the first NRF, the first NRF updates the performance information of the first NF stored in the first NRF with the performance information of the first NF carried by the heartbeat message in the nth cycle.

Of course, in other embodiments of the present application, the first NRF may further perform update determination before update, and in determining that the performance information of the first NF carried by the heartbeat message in the nth period is unchanged compared with the performance information of the first NF stored in the first NRF, no update is required.

In the embodiment of the present application, the first NRF updates the performance information of the first NF stored in the first NRF into updated performance information in the heartbeat message; that is, stored in the first NRF is the latest performance information of the first NF. Therefore, when other NFs inquire the performance information of the first NF from the first NRF, the first NRF can provide accurate performance information, and the problem of resource waste caused by the fact that the first NRF cannot timely master the performance information of the first NF and provide error information for other NFs is avoided.

In some embodiments, the first NRF may also send a second message to the first NF. Here, the second message is used to indicate that the second message received the performance information of the first NF. The indication here may be that the second message includes a specific indication field, or may be that the second message itself indicates that the second message receives the performance information of the first NF, or the like.

Note that, the first NRF may not reply to the second message indicating successful reception of the performance information of the first NF.

In the embodiment of the present application, the second message includes, but is not limited to, an indication message, a response message, an Acknowledgement (ACK) message, and the like.

Fig. 5 is a flow chart of a disaster recovery method according to an embodiment of the present application. The NF managed by the primary NRF2 includes a first NF, which may be NF service Consumer; the primary NRF1 and the primary NRF2 are backup to each other. After the first NF service registration is completed, the first NF periodically initiates a heartbeat message to the two NRFs that are mutually standby, and updates the state recorded in the NRFs.

In step 501, the first NF sends update messages to the active NRF1 and the active NRF2 to update its own status.

Wherein the Update message comprises an nrf NFManagement NF Update request message.

It should be noted that, the first NF may send a message to the active NRF1 and the active NRF at the same time; the messages may be sent to the primary NRF1 and the primary NRF2 sequentially, which is not specifically limited in this application.

Step 502, the state of the first NF is updated (updated) by the master NRF1 and the master NRF 2.

In this embodiment of the present application, the primary NRF1 and the primary NRF2 may update the state of the first NF immediately after receiving the update message, or may update the state of the first NF after the current working processes of the primary NRF1 and the primary NRF2 are finished; the present application is not particularly limited in this regard.

Here, the state of updating (update) the first NF may be to update a profile file corresponding to the first NF stored in the primary NRF1 and the primary NRF2, that is, update NF profile.

Step 503, the primary NRF1 and the primary NRF2 send response messages to the first NF.

In this embodiment of the present application, the response message includes an nrf_nfmanagement_nf_update_response message, where the response message further carries status information of whether the primary NRF1 and the primary NRF2 successfully receive the first NF.

In other embodiments of the present application, the receiving the first message sent by the first NF in step A1 may be implemented through steps a12 to a 14:

step a12, determining a first NF managed by the second NRF.

In this embodiment of the present application, for a scenario in which two NRFs are mutually backed up, part of NFs in the communication scenario are managed by the first NRF, and the remaining part of NFs are managed by the second NF. In a scenario where multiple NRFs are back-up to each other, a first portion NF is managed by the first NRF, a second portion NF is managed by the second NRF, and a third portion is managed by other NRFs. Here, NFs managed by each NRF do not coincide.

In some embodiments, when the first NRF and the second NRF perform backup, the first NRF or the second NRF directly transmits the NF managed by itself to the other NRF in advance.

For example, each NRF managed NF may be pre-stored in an NF profile; the NF profile may be backed up to other NRFs when at least two NRFs are backed up to each other. Then the first NRF can determine the NF managed by the other NRF from the NF profile only; i.e. the first NRF may determine the second NRF managed first NF from the second NRF managed NF profile. Here, the first NF may be one or a plurality of first NFs.

In some embodiments, the first NRF may obtain the second NRF-managed first NF from other devices associated with the second NRF; or the first NRF may directly send the query message to the NFs in the communication scenario, and determine, through a response of each NF to the query message, the first NF managed by the second NRF.

And step A13, sending a third message to the first NF.

The third message is used for acquiring performance information of the first NF.

In the embodiment of the application, the first NRF sends a third message for indicating the first NF to report the own performance information to the first NF; if the first NF is a plurality of NF, the third message can be sent in a multicast/broadcast mode; thus, the number of messages sent is effectively reduced.

In the embodiment of the present application, the third message is sent in the manner that: in-band, out-of-band, media, signaling, data, messages, control plane, user plane, etc. Here, the first NRF may transmit the third message by means of a media channel in the related art to be more compatible with the existing system and reduce the cost of system modification.

And step A14, receiving a first message sent by the first NF.

Wherein the first message is generated by the first NF based on the third message.

In the embodiment of the present application, when the first NF receives the third message, the first NF generates a first message carrying the own performance information, and sends the first message to the first NRF; the first NRF receives the first message sent by the first NF, so that the first NRF can timely master the performance information of the first NF, and can timely manage the first NF when the second NRF fails.

Fig. 6 is a flow chart of a disaster recovery method according to an embodiment of the present application. The NF managed by the primary NRF2 includes NF3; the primary NRF1 and the primary NRF2 are backup to each other.

In step 601, the primary NRF1 detects that data synchronization cannot be performed between the primary NRF1 and the primary NRF 2.

In this embodiment of the present application, the failure to synchronize data between the primary NRF1 and the primary NRF2 includes two inter-NRF link failures, namely NRF1 detects the link between NRF and NRF1 is down.

Step 602, the master NRF1 actively sends an HTTP Ping frame (e.g. HTTP 2_ping) message to the NF3 in reverse.

Wherein the NF managed by the primary NRF2 includes NF3.

Step 603, NF3 sends an HTTP Ping frame response (e.g., HTTP2 Ping response) message to the master NRF 1.

The HTTP Ping frame response message comprises an HTTP2_ping response message.

Step 604, after the primary NRF1 receives the response message sent by NF3, the status of NF3 is obtained from the response, and the status of NF3 stored in the primary NRF1, that is, NRF1 update NF3status, is updated.

In this embodiment of the present application, after a link between two NRFs is abnormal, the NRF actively transmits an HTTP Ping frame to the NF that is synchronized in reverse, and detects the state of the NF.

In other embodiments of the present application, the first message includes an update message, and the receiving the first message sent by the first NF in step A1 may be implemented by step a 15:

and step A15, under the condition that the configuration parameters of the first NF are updated, receiving an update message which is sent by the first NF and carries the updated configuration parameters of the first NF.

In some embodiments, the triggering first NF sends the first message to the first NRF if the current communication scenario satisfies the triggering scenario. Here, the trigger scenario includes at least one of:

a second NRF managing the first NF fails;

the configuration parameters or the running state in the performance information of the first NF are updated.

Under the condition that the configuration parameters or the running states in the performance information of the first NF are updated or the running states, the updated configuration parameters or the updated running states are carried in the information sent by the first NF.

Further, after receiving the update message carrying the updated configuration parameters on the first NF sent by the first NF in step a15, the first NRF determines a second NF that subscribes to the notification of the configuration parameter change of the first NF on the first NRF; and sending a notification message carrying the updated attribute information on the first NF to the second NF.

Wherein the second NF is the first NRF or the second NRF managed NF.

In the embodiment of the application, the second NF subscribes to the attribute change notification of the first NF in advance to the first NRF, and when the attribute of the first NF changes, the first NF actively reports the update to the first NRF; then, the first NRF needs to send a subscription notification to all second NFs subscribing to the first NF attribute change.

Fig. 7 is a flow chart of a disaster recovery method according to an embodiment of the present application. The NF managed by the primary NRF2 includes NF3; the NF managed by the primary NRF1 comprises NF1; the primary NRF1 and the primary NRF2 are backup to each other.

In step 701, the primary NRF2 detects that data synchronization cannot be performed between the primary NRF1 and the primary NRF 2.

In this embodiment of the present application, the failure to synchronize data between the primary NRF1 and the primary NRF2 includes two inter-NRF link failures, namely NRF2 detects the link between NRF and NRF1 is down.

Step 702, NF3 updates its own configuration (profile) file (NF 3 update its profile).

The profile file records configuration parameters of NF 3; for example, the supported slice/data network names (Data Network Name, DNN) are changed in the profile file of NF3.

Step 703, NF3 sends an update notification message to the primary NRF 2.

In the embodiment of the application, NF3 sends an update notification message to the active NRF2, so that the active NF2 updates the attribute information associated with NF3 stored in the active NF2 based on the update communication message.

Wherein the Update notification message includes an nrf NFManagement NF Update request message.

Step 704, the primary NRF2 sends an update response message to NF3.

Wherein the Update response message includes an nrf NFManagement NF Update response message.

In the embodiment of the application, the primary NRF2 updates the profile file associated with NF3 stored in the primary NRF2, and sends an nrf_nfmanagement_nf_update_response message to NF3.

Step 705, the active NRF2 sends a subscription notification to NF1 subscribing to the NF3 attribute change.

In the embodiment of the application, the subscription notification may be implemented through an nrf_nfmanagement_nf_status_notify message.

It should be noted that, step 704 and step 705 may be performed simultaneously, or step 704 may be performed before step 705, or step 705 may be performed before step 704, which is not specifically limited in this application.

An embodiment of the present application provides a first network storage function network element, where the first network storage function network element may be used to implement a disaster recovery method provided in the embodiment corresponding to fig. 4, and referring to fig. 8, the first network storage function network element 80 includes:

an obtaining module 801, configured to obtain performance information of a first NF managed by a second NRF in a case where a data synchronization interface between the first NRF and the second NRF fails;

wherein the performance information includes at least one of:

an operating state of the first NF;

configuration parameters of the first NF.

In other embodiments of the present application, the first network storage function network element 80 further includes a receiving module 802;

a receiving module 802, configured to receive a first message sent by a first NF;

the first message carries performance information of the first NF.

In other embodiments of the present application, a receiving module 802 is configured to receive a heartbeat message sent by a first NF in an nth cycle of a plurality of cycles; the nth period is a period after the next period when the first NRF determines that the data synchronization interface between the first NRF and the second NRF fails, and n is a positive integer.

In other embodiments of the present application, the first network storage function network element 80 further includes a processing module 803 and a sending module 804;

A processing module 803, configured to update the performance information of the first NF stored in the first NRF to updated performance information in the heartbeat message sent by the received first NRF;

a sending module 804, configured to send a second message to the first NF; the second message is used for indicating that the first NRF receives the performance information of the first NF.

In other embodiments of the present application, the processing module 803 is configured to determine a first NF managed by a second NRF;

a sending module 804, configured to send a third message to the first NF; the third message is used for acquiring performance information of the first NF;

a receiving module 802, configured to receive a first message sent by a first NF; wherein the first message is generated by the first NF based on the third message.

In other embodiments of the present application, the receiving module 802 is configured to receive, when the configuration parameters of the first NF are updated, an update message sent by the first NF and carrying updated configuration parameters on the first NF.

In other embodiments of the present application, the processing module 803 is configured to determine a second NF that subscribes to a configuration parameter change notification of the first NF on the first NRF; the second NF is the NF managed by the first NRF or the second NRF;

a sending module 804, configured to send a notification message carrying the updated attribute information on the first NF to the second NF.

The first network storage function network element 80 may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, an IoT device, a satellite handset, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handset with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolution network, etc.

The description of the apparatus embodiments above is similar to that of the method embodiments above, with similar advantageous effects as the method embodiments. For technical details not disclosed in the apparatus embodiments of the present application, please refer to the description of the method embodiments of the present application for understanding.

It should be noted that, in the embodiment of the present application, if the disaster recovery method is implemented in the form of a software functional module, and is sold or used as a separate product, the disaster recovery method may also be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or part contributing to the related art, and the computer software product may be stored in a storage medium, and include several instructions to cause a terminal device to execute all or part of the methods of the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a magnetic disk or an optical disk. Thus, embodiments of the present application are not limited to any specific combination of hardware and software.

Fig. 9 is a schematic structural diagram of a communication device 900 provided in an embodiment of the present application. The communication device may be a first network storage function network element or a first network function network element. The communication device 900 shown in fig. 9 comprises a first processor 910, and the first processor 910 may call and run a computer program from a memory to implement the method in the embodiments of the present application.

Optionally, as shown in fig. 9, the communication device 900 may further include a first memory 920. The first processor 910 may invoke and execute a computer program from the first memory 920 to implement the method in the embodiments of the present application.

The first memory 920 may be a separate device independent of the first processor 910, or may be integrated in the first processor 910.

Optionally, as shown in fig. 9, the communication device 900 may further include a transceiver 930, and the first processor 910 may control the transceiver 930 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

Wherein transceiver 930 may include a transmitter and a receiver. Transceiver 930 may further include antennas, the number of which may be one or more.

Optionally, the communication device 900 may be specifically a first network storage function network element in the embodiment of the present application, and the communication device 900 may implement a corresponding flow implemented by the first network storage function network element in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 900 may be specifically a first network function network element in the embodiment of the present application, and the communication device 900 may implement a corresponding flow implemented by the first network function network element in each method in the embodiment of the present application, which is not described herein for brevity.

Fig. 10 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 1000 shown in fig. 10 includes a second processor 1010, and the second processor 1010 may call and run a computer program from a memory to implement the method in the embodiments of the present application.

Optionally, as shown in fig. 10, the chip 1000 may further include a second memory 1020. Wherein the second processor 1010 may call and run a computer program from the second memory 1020 to implement the methods in embodiments of the present application.

The second memory 1020 may be a separate device from the second processor 1010 or may be integrated into the second processor 1010.

Optionally, the chip 1000 may also include an input interface 1030. The second processor 1010 may control the input interface 1030 to communicate with other devices or chips, and in particular, may obtain information or data sent by the other devices or chips.

Optionally, the chip 1000 may further include an output interface 1040. Wherein the second processor 1010 may control the output interface 1040 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

Optionally, the chip may be applied to the first network function network element in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the first network function network element in each method of the embodiment of the present application, which is not described herein for brevity.

Optionally, the chip may be applied to the first network storage function network element in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the first network storage function network element in each method of the embodiment of the present application, which is not described herein for brevity.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

Fig. 11 is a schematic block diagram of a communication system 110 provided in an embodiment of the present application. As shown in fig. 11, the communication system 110 includes a first network function network element 1101, a first network storage function network element 1102, and a second network storage function network element 1103.

The first network function network element 1101 may be used to implement a corresponding function implemented by the first NF in the above method, and the first network storage function network element 1102 may be used to implement a corresponding function implemented by the first NRF in the above method, and the second network storage function network element 1103 may be used to implement a corresponding function implemented by the second NRF in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

As one embodiment, the processor may include one or more general purpose central processing units (Central Processing Unit, CPU). Each of these processors may be a single-core (single-CPU) processor or may be a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer-executable instructions).

It will be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a ROM, a Programmable ROM (PROM), an Erasable Programmable EPROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Embodiments of the present application also provide a computer-readable storage medium for storing a computer program.

Optionally, the computer readable storage medium may be applied to the first network storage function network element in the embodiments of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the first network storage function network element in each method of the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to the first network function network element in the embodiments of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the first network function network element in each method of the embodiments of the present application, which is not described herein for brevity.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product.

The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). Computer readable storage media can be any available media that can be stored by a computer or data storage devices such as servers, data centers, etc. that contain an integration of one or more available media. Usable media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid State Disks (SSDs)), among others.

The disaster recovery method, the first network storage function network element and the storage medium provided by the embodiment of the application are described in detail, and specific examples are applied to the description of the principle and the implementation of the application, and the description of the above embodiment is only used for helping to understand the method and the core idea of the application; meanwhile, as those skilled in the art will have modifications in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.

It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment of the present application" or "the foregoing embodiments" or "some implementations" or "some embodiments" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" or "an embodiment of the present application" or "the foregoing embodiments" or "some implementations" or "some embodiments" in various places throughout this specification are not necessarily referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application. The foregoing embodiment numbers of the present application are merely for describing, and do not represent advantages or disadvantages of the embodiments.

In the case where no special description is made, the first network storage function element/the first network function element performs any step in the embodiments of the present application, which may be performed by a processor of the first network storage function element/the first network function element. The embodiments of the present application do not limit the order in which the first network storage function element/first network function element performs the following steps unless specifically stated. In addition, the manner in which the data is processed in different embodiments may be the same method or different methods.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above described device embodiments are only illustrative, e.g. the division of the units is only one logical function division, and there may be other divisions in practice, such as: multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. In addition, the various components shown or discussed may be coupled or directly coupled or communicatively coupled to each other via some interface, whether indirectly coupled or communicatively coupled to devices or units, whether electrically, mechanically, or otherwise.

The units described above as separate components may or may not be physically separate, and components shown as units may or may not be physical units; can be located in one place or distributed to a plurality of network units; some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may be separately used as one unit, or two or more units may be integrated in one unit; the integrated units may be implemented in hardware or in hardware plus software functional units.

The methods disclosed in the several method embodiments provided in the present application may be arbitrarily combined without collision to obtain a new method embodiment.

The features disclosed in the several product embodiments provided in the present application may be combined arbitrarily without conflict to obtain new product embodiments.

The features disclosed in the several method or apparatus embodiments provided in the present application may be arbitrarily combined without conflict to obtain new method embodiments or apparatus embodiments.

Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the above method embodiments may be implemented by hardware related to program instructions, and the foregoing program may be stored in a computer storage medium, where the program, when executed, performs steps including the above method embodiments; and the aforementioned storage medium includes: various media capable of storing program codes, such as a removable storage device, a ROM, a magnetic disk, or an optical disk.

Alternatively, the integrated units described above may be stored in a computer storage medium if implemented in the form of software functional modules and sold or used as a stand-alone product. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or partially contributing to the related art, and the computer software product may be stored in a storage medium, and include several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a removable storage device, a ROM, a magnetic disk, or an optical disk.

As used in this application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

In the embodiments of the present application, all or part of the steps may be performed, so long as a complete technical solution can be formed.

The foregoing is merely an embodiment of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (10)

1. A disaster recovery method applied to a first network storage function network element NRF, the method comprising:

obtaining performance information of a first NF managed by a second NRF under the condition that a data synchronization interface between the first NRF and the second NRF fails;

wherein the performance information includes at least one of:

an operating state of the first NF;

Configuration parameters of the first NF.

2. The method of claim 1, wherein the obtaining performance information of the second NRF managed first NF comprises:

receiving a first message sent by the first NF;

the first message carries performance information of the first NF.

3. The method of claim 2, wherein the first message comprises a heartbeat message, and wherein the receiving the first message sent by the first NF comprises:

receiving a heartbeat message sent by the first NF to the first NRF in an nth period of a plurality of periods; the nth period is a period after a next period when the first NRF determines that a data synchronization interface between the first NRF and the second NRF fails, and n is a positive integer.

4. A method according to claim 3, characterized in that the method further comprises:

updating the performance information of the first NF stored in the first NRF to updated performance information in the heartbeat message sent by the received first NRF;

sending a second message to the first NF; the second message is used for indicating that the first NRF receives the performance information of the first NF.

5. The method of claim 2, wherein the receiving the first message sent by the first NF, the method further comprises:

determining a first NF managed by the second NRF;

sending a third message to the first NF; the third message is used for acquiring performance information of the first NF;

receiving a first message sent by the first NF; wherein the first message is generated by the first NF based on the third message.

6. The method of claim 2, wherein the first message comprises an update message, and wherein the receiving the first message sent by the first NF comprises:

and under the condition that the configuration parameters of the first NF are updated, receiving an update message which is sent by the first NF and carries the updated configuration parameters of the first NF.

7. The method of claim 6, wherein after the receiving the first message sent by the first NF, the method further comprises:

determining a second NF subscribing to a configuration parameter change notification of the first NF on the first NRF; wherein the second NF is an NF managed by the first NRF or the second NRF;

and sending a notification message carrying the updated attribute information on the first NF to the second NF.

8. A first NRF, characterized in that said first NRF comprises:

an obtaining module, configured to obtain performance information of a first NF managed by a second NRF in a case where a data synchronization interface between the first NRF and the second NRF fails;

wherein the performance information includes at least one of:

an operating state of the first NF;

configuration parameters of the first NF.

9. A first NRF, characterized in that said first NRF comprises:

a memory for storing executable instructions;

a processor for implementing the disaster recovery method according to any one of claims 1 to 7 when executing the executable instructions stored in the memory.

10. A computer-readable storage medium storing one or more programs executable by one or more processors to implement the disaster recovery method of any one of claims 1 to 7.