CN117527539A - Network disaster recovery method, device and storage medium - Google Patents

Abstract

The application discloses a network disaster recovery method, a device and a storage medium, relates to the technical field of communication, and is used for solving the problem that disaster recovery switching cannot be performed rapidly and accurately when a network element fails. The method comprises the following steps: determining a first network device that failed based on network parameters of each of the plurality of network devices; wherein the network parameters include: monitoring at least one of a signaling timeout parameter, a heartbeat message parameter, and a network state parameter; determining a second network device connected to the first network device; determining a network disaster recovery mechanism based on disaster recovery parameters of the first network device; the disaster recovery parameter includes at least one of: a device type of the first network device, a device type of the second network device, and a failure parameter of the first network device; and sending a network disaster recovery mechanism to the second network device.

Description

Network disaster recovery method, device and storage medium

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a network disaster recovery method, device, and storage medium.

Background

With the high-speed development of the internet, the requirements of users on network services are higher and higher, so that in order to ensure the stability of the network, disaster recovery switching needs to be performed rapidly and accurately under the condition of network element faults in the network.

At present, a fault network element in a network is generally obtained according to heartbeat monitoring among network elements, but because of different heartbeat monitoring mechanisms among network elements, the response time of the network elements to the fault is different, so that the time of switching between standby network elements of each network element is different, and the disaster recovery switching efficiency is further affected.

Disclosure of Invention

The application provides a network disaster recovery method, a device and a storage medium, which are used for solving the problem that disaster recovery switching cannot be performed rapidly and accurately when network elements in a general method are in failure.

In order to achieve the above purpose, the present application adopts the following technical scheme:

in a first aspect, a network disaster recovery method is provided, including: determining a first network device that failed based on network parameters of each of the plurality of network devices; wherein the network parameters include: monitoring at least one of a signaling timeout parameter, a heartbeat message parameter, and a network state parameter; determining a second network device connected to the first network device; determining a network disaster recovery mechanism based on disaster recovery parameters of the first network device; the disaster recovery parameter includes at least one of: a device type of the first network device, a device type of the second network device, and a failure parameter of the first network device; and sending a network disaster recovery mechanism to the second network device.

Optionally, in the case that the network parameter includes a monitoring signaling timeout parameter, the method for determining the first network device that fails based on the network parameter of each of the plurality of network devices includes: respectively sending first indication information to each network device, wherein the first indication information is used for indicating the network device to send monitoring signaling to the monitoring device in a target period; and when monitoring signaling of any network device in the plurality of network devices is not received in the target period, determining that any network device is the first network device with faults.

Optionally, in the case that the network parameter includes a heartbeat message parameter, the method for determining the first network device that is malfunctioning based on the network parameter of each of the plurality of network devices includes: receiving a fault report message from a third network device; the third network device is a network device of the plurality of network devices; the fault report message is used for representing that the third network device does not receive the heartbeat message of the fourth network device within preset time; the fourth network device is a network device connected with the third network device in the plurality of network devices; the fourth network device is determined to be the failed first network device.

Optionally, in the case that the network parameter includes a network status parameter, the method for determining the first network device that fails based on the network parameter of each of the plurality of network devices includes: respectively sending simulation messages to each network device; the simulation message is used for simulating the message sent by the user to each network device; receiving network state parameters fed back by each network device; the network state parameter includes at least one of a route of the network, a network device state, a device link state; and determining the first network equipment with faults based on the network state parameters fed back by each network equipment.

Optionally, the network disaster recovery mechanism includes a disaster recovery mechanism and a flow control mechanism, and the second network device includes: upstream and downstream devices of the first network device; based on the disaster recovery parameter of the first network device, the method for determining the network disaster recovery mechanism comprises the following steps: determining a flow control mechanism corresponding to upstream equipment based on the disaster recovery parameter, and determining a disaster recovery mechanism corresponding to downstream equipment based on the disaster recovery parameter; sending a network disaster recovery mechanism to a second network device, comprising: and sending a flow control mechanism to the upstream equipment and sending a disaster recovery mechanism to the downstream equipment.

Optionally, after determining the failed first network device based on the network parameter of each of the plurality of network devices, the method further comprises: generating a fault alarm message of the first network device; the fault alert message includes at least one of: time and location of failure; sending a fault alarm message to a fifth network device; the fifth network device is a device other than the first network device among the plurality of network devices.

Optionally, after sending the network disaster recovery mechanism to the second network device, the method further includes: sending a second indication message to a second network device; the second indication message is used for indicating the second network equipment to acquire the recovery state of the first network equipment; receiving a recovery state of a first network device from a second network device; and adjusting a network disaster recovery mechanism based on the recovery state of the first network device.

In a second aspect, a network disaster recovery apparatus is provided, which is applied to a monitoring device, where the monitoring device is connected to a plurality of network devices, and includes: a processing unit and a communication unit; a processing unit configured to determine a first network device that has failed based on a network parameter of each of the plurality of network devices; wherein the network parameters include: monitoring at least one of a signaling timeout parameter, a heartbeat message parameter, and a network state parameter; the processing unit is also used for determining a second network device connected with the first network device; the processing unit is also used for determining a network disaster recovery mechanism based on the disaster recovery parameters of the first network equipment; the disaster recovery parameter includes at least one of: a device type of the first network device, a device type of the second network device, and a failure parameter of the first network device; and the communication unit is used for sending the network disaster recovery mechanism to the second network equipment.

Optionally, in the case that the network parameter includes a monitoring signaling timeout parameter, the processing unit is specifically configured to: respectively sending first indication information to each network device, wherein the first indication information is used for indicating the network device to send monitoring signaling to the monitoring device in a target period; and when monitoring signaling of any network device in the plurality of network devices is not received in the target period, determining that any network device is the first network device with faults.

Optionally, in case the network parameter comprises a heartbeat message parameter, the processing unit is configured to: receiving a fault report message from a third network device; the third network device is a network device of the plurality of network devices; the fault report message is used for representing that the third network device does not receive the heartbeat message of the fourth network device within preset time; the fourth network device is a network device connected with the third network device in the plurality of network devices; the fourth network device is determined to be the failed first network device.

Optionally, in the case that the network parameter includes a network status parameter, the processing unit is specifically configured to: respectively sending simulation messages to each network device; the simulation message is used for simulating the message sent by the user to each network device; receiving network state parameters fed back by each network device; the network state parameter includes at least one of a route of the network, a network device state, a device link state; and determining the first network equipment with faults based on the network state parameters fed back by each network equipment.

Optionally, the network disaster recovery mechanism includes a disaster recovery mechanism and a flow control mechanism, and the second network device includes: upstream and downstream devices of the first network device; the processing unit is specifically used for: determining a flow control mechanism corresponding to upstream equipment based on the disaster recovery parameter, and determining a disaster recovery mechanism corresponding to downstream equipment based on the disaster recovery parameter; sending a network disaster recovery mechanism to a second network device, comprising: and sending a flow control mechanism to the upstream equipment and sending a disaster recovery mechanism to the downstream equipment.

Optionally, after determining the failed first network device based on the network parameter of each of the plurality of network devices, the processing unit is specifically configured to: generating a fault alarm message of the first network device; the fault alert message includes at least one of: time and location of failure; sending a fault alarm message to a fifth network device; the fifth network device is a device other than the first network device among the plurality of network devices.

Optionally, after sending the network disaster recovery mechanism to the second network device, the processing unit is further configured to: sending a second indication message to a second network device; the second indication message is used for indicating the second network equipment to acquire the recovery state of the first network equipment; receiving a recovery state of a first network device from a second network device; and adjusting a network disaster recovery mechanism based on the recovery state of the first network device.

In a third aspect, a network disaster recovery device is provided, including a memory and a processor; the memory is used for storing computer execution instructions, and the processor is connected with the memory through a bus; when the network disaster recovery device runs, the processor executes the computer execution instructions stored in the memory, so that the network disaster recovery device executes the network disaster recovery method of the first aspect or any implementation manner thereof.

The network disaster recovery device may be a network device, or may be a part of a device in the network device, for example, a chip system in the network device. The system-on-chip is configured to support the network device to implement the functions involved in the first aspect and any one of possible implementations thereof, for example, obtain, determine, and send data and/or information involved in the network disaster recovery method. The chip system includes a chip, and may also include other discrete devices or circuit structures.

In a fourth aspect, a computer-readable storage medium is provided, the computer-readable storage medium comprising computer-executable instructions that, when run on a computer, cause the computer to perform the network disaster recovery method of the first aspect.

In a fifth aspect, there is also provided a computer program product comprising computer instructions which, when run on a network disaster recovery device, cause the network disaster recovery device to perform the network disaster recovery method as described in the first aspect above.

It should be noted that the above-mentioned computer instructions may be stored in whole or in part on a computer-readable storage medium. The computer readable storage medium may be packaged together with the processor of the network disaster recovery device, or may be packaged separately from the processor of the network disaster recovery device, which is not limited in this application.

The description of the second, third, fourth and fifth aspects of the present application may refer to the detailed description of the first aspect; the advantages of the second aspect, the third aspect, the fourth aspect and the fifth aspect may be referred to as analysis of the advantages of the first aspect, and will not be described here.

In this application, the names of the above-mentioned network disaster recovery devices do not limit the devices or functional modules, and in actual implementation, these devices or functional modules may appear under other names. Insofar as the function of each device or function module is similar to the present application, it is within the scope of the claims of the present application and the equivalents thereof.

These and other aspects of the present application will be more readily apparent from the following description.

The technical scheme provided by the application at least brings the following beneficial effects:

Based on any one of the above aspects, the present application provides a network disaster recovery method, where a monitoring device may be set up, so that the monitoring device is connected to a plurality of network devices, to implement continuous monitoring on each device, and the monitoring device generates a network disaster recovery mechanism of other devices after the device fails, and sends the network disaster recovery mechanism to the other devices. In this way, other devices perform disaster recovery switching according to the network disaster recovery mechanism uniformly generated by the monitoring device, and the other devices switch the standby network elements at the same time, so that the disaster recovery switching efficiency is prevented from being influenced.

Drawings

Fig. 1 is a schematic structural diagram of a network disaster recovery system according to an embodiment of the present application;

fig. 2 is a schematic diagram of a network architecture of a network disaster recovery system according to an embodiment of the present application;

fig. 3 is a schematic hardware structure diagram of a communication device according to an embodiment of the present application;

fig. 4 is a schematic hardware structure diagram of a communication device according to the embodiment of the present application;

fig. 5 is a schematic flow chart of a network disaster recovery method according to an embodiment of the present application;

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

fig. 7 is a flowchart of a network disaster recovery method according to an embodiment of the present application;

Fig. 8 is a flow chart diagram of a network disaster recovery method according to an embodiment of the present application;

fig. 9 is a flow chart diagram of a network disaster recovery method provided in an embodiment of the present application;

fig. 10 is a flowchart of a network disaster recovery method according to an embodiment of the present application;

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

fig. 12 is a schematic structural diagram of a network disaster recovery device according to 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 clearly and completely with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

It should be noted that, in the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

In order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, the terms "first", "second", and the like are used to distinguish the same item or similar items having substantially the same function and effect, and those skilled in the art will understand that the terms "first", "second", and the like are not limited in number and execution order.

As shown in the background art, the fault network elements in the network are usually monitored by the peripheral network elements of the fault network elements through heartbeat monitoring among the network elements, and as the heartbeat mechanism of each network element in the peripheral network elements is different from that of the fault network elements, the time for acquiring the fault information of the network elements is different, and the time for switching the standby network elements of each network element is different, thereby affecting the disaster recovery switching efficiency.

Aiming at the technical problems, the embodiment of the application provides a network disaster recovery method, wherein a monitoring device can be arranged to be connected with a plurality of network devices, so that continuous monitoring of each device is realized, and the monitoring device generates a network disaster recovery mechanism of other devices after the device fails and sends the network disaster recovery mechanism to the other devices. In this way, other devices perform disaster recovery switching according to the network disaster recovery mechanism uniformly generated by the monitoring device, and the other devices switch the standby network elements at the same time, so that the disaster recovery switching efficiency is prevented from being influenced.

The network disaster recovery method is suitable for the network disaster recovery system. Fig. 1 shows a schematic diagram of a network disaster recovery system 100. As shown in fig. 1, the network disaster recovery system 100 includes: monitoring device 101, a plurality of network devices (fig. 1 illustrates "a plurality of network devices including network device 102, network device 103, and network device 104 as an example").

Alternatively, the monitoring device 101 and the plurality of devices may be connected by a wired or wireless means.

Optionally, the monitoring device 101 is configured to discover a faulty device in the network and perform real-time control on the network.

Optionally, the network device 102, the network device 103, and the network device 104 may be routers, switches, and servers, or may be network elements in a network.

Illustratively, the monitoring device 101 periodically acquires monitoring signaling of a plurality of network devices, and when the network device 103 does not send the monitoring signaling to the monitoring device 101 in a period, the monitoring device 101 may determine that the network device 103 is a fault device. Network device 102 is an upstream device of network device 103, network device 104 is a downstream device of network device 103, monitoring device 101 sends a flow control mechanism to network device 102, and sends a disaster recovery mechanism to network device 104. The network device 102 and the network device 104 respectively make corresponding operations according to the flow control mechanism and the disaster recovery mechanism.

In one embodiment, the network disaster recovery method in the present application may also be applied to network element disaster recovery of the 5G core network. Fig. 2 shows a network architecture diagram of a network disaster recovery system. In the schematic diagram, a network architecture of a network disaster recovery system includes the following network element functional entities: a User Equipment (UE), a radio access network (R) AN, a user plane function (user plane function, UPF), a Data Network (DN), and a network element function entity in a network disaster recovery system. The network element functional entity in the network disaster recovery system comprises: an authentication service function (authentication server function, AUSF), an access and mobility management function (access and mobility management function, AMF), a session management function (session management function, SMF), a network slice selection function (network slice selection function, NSSF), a network capability open function (network exposure function, NEF), a network storage function (network repository function, NRF), a policy control function (policy control function, PCF), a unified data management function (unified data management, UDM), an application layer function (application function, AF).

The specific functions of the network element functional entity are as follows: the UPF is used for being responsible for user plane processing; the AMF is used for being responsible for access and mobility management of the user; SMF is used for protocol (internet protocol, IP) address allocation and management responsible for tunnel maintenance, inter-network interconnections; the AUSF is used for receiving the request of the AMF for carrying out the identity verification on the UE, and forwarding the key issued by the UDM to the AMF for carrying out the authentication processing by requesting the key from the UDM; NSSF is responsible for providing network slice services; the NEF is responsible for opening the capabilities of the fifth generation mobile communication technology (5th generation mobile communication technology,5G) network to external systems; the NRF is used for registering network function services, monitoring states and the like; the PCF is used for controlling the strategy of the user, including the strategy of the session, the mobility strategy and the like; the UDM is used for being responsible for subscription data management of the user; the AF is responsible for interworking with the core network to provide services for the user.

The connection relation of the network element functional entities is as follows:

the UE is connected with the AMF through an N1 interface. The (R) AN and the AMF are connected through AN N2 interface. The (R) AN and UPF are connected through AN N3 interface. The UPF and the SMF are connected through an N4 interface. The UPF and DN are connected through an N6 interface.

The service architecture adopts an IT bus: the AMF accesses the bus via a service-based interface Namf. The SMF accesses the bus via a service-based interface Nsmf. The AUSF accesses the bus via a traffic-based interface Nausf. NSSF accesses the bus via a service-based interface Nnssf. The NEF accesses the bus via a service-based interface Nnef. The NRF accesses the bus via a service-based interface Nnrf. The PCF accesses the bus via a service-based interface Npcf. The UDM accesses the bus via a traffic based interface Nudm. The AF accesses the bus via a traffic-based interface Naf.

In connection with fig. 1, a monitoring device 101 and a plurality of network devices in a network disaster recovery system each include elements included in the communication apparatus shown in fig. 3 or fig. 4. The hardware configuration of the monitoring apparatus 101 will be described below taking the communication devices shown in fig. 3 and 4 as an example.

Fig. 3 is a schematic hardware structure of a communication device according to an embodiment of the present application. The communication device comprises a processor 21, a memory 22, a communication interface 23, a bus 24. The processor 21, the memory 22 and the communication interface 23 may be connected by a bus 24.

The processor 21 is a control center of the communication device, and may be one processor or a collective term of a plurality of processing elements. For example, the processor 21 may be a general-purpose central processing unit (central processing unit, CPU), or may be another general-purpose processor. Wherein the general purpose processor may be a microprocessor or any conventional processor or the like.

As one example, processor 21 may include one or more CPUs, such as CPU 0 and CPU 1 shown in fig. 3.

Memory 22 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (random access memory, RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), magnetic disk storage or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

In a possible implementation, the memory 22 may exist separately from the processor 21, and the memory 22 may be connected to the processor 21 by a bus 24 for storing instructions or program code. When the processor 21 invokes and executes the instructions or the program codes stored in the memory 22, the network disaster recovery method provided in the following embodiments of the present invention can be implemented.

In another possible implementation, the memory 22 may also be integrated with the processor 21.

The communication interface 23 is used for connecting the communication device with other devices through a communication network, such as ethernet, radio access network, wireless local area network (wireless local area networks, WLAN), etc. The communication interface 23 may include a receiving unit for receiving data, and a transmitting unit for transmitting data.

Bus 24 may be an industry standard architecture (industry standard architecture, ISA) bus, an external device interconnect (peripheral component interconnect, PCI) bus, or an extended industry standard architecture (extended industry standard architecture, EISA) bus, among others. The bus may be classified as an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in fig. 3, but not only one bus or one type of bus.

Fig. 4 shows another hardware configuration of the communication apparatus in the embodiment of the present invention. As shown in fig. 4, the communication device may include a processor 31 and a communication interface 32. The processor 31 is coupled to a communication interface 32.

The function of the processor 31 may be as described above with reference to the processor 21. The processor 31 also has a memory function and can function as the memory 22.

The communication interface 32 is used to provide data to the processor 31. The communication interface 32 may be an internal interface of the communication device or an external interface of the communication device (corresponding to the communication interface 23).

It should be noted that the structure shown in fig. 3 (or fig. 4) does not constitute a limitation of the communication apparatus, and the communication apparatus may include more or less components than those shown in fig. 3 (or fig. 4), or may combine some components, or may be arranged in different components.

The network disaster recovery method provided by the embodiment of the application is described in detail below with reference to the accompanying drawings.

The network disaster recovery method provided by the embodiment of the present application may be applied to the monitoring device 101 in the application scenario shown in fig. 1. As shown in fig. 5, the network disaster recovery method includes:

s501, the monitoring device determines a first network device with a fault based on network parameters of each of a plurality of network devices.

Wherein the network parameters include: at least one of a signaling timeout parameter, a heartbeat message parameter, and a network status parameter is monitored.

In one possible implementation, the monitoring device instructs each network device to periodically send its own monitoring signaling, and when the monitoring device does not receive the monitoring signaling of one of the network devices within a set period, the monitoring device may determine that the network device is the first network device that fails.

In one possible implementation manner, heartbeat monitoring exists between devices in the network, when one of the devices does not receive the heartbeat message of the opposite terminal device within the target time, the opposite terminal device can be considered to be faulty, at this time, the device which does not receive the heartbeat message of the opposite terminal device can send a fault report message to the monitoring device to inform the opposite terminal device that the opposite terminal device is faulty, and the monitoring device determines the opposite terminal device as the first network device after receiving the fault report message.

In one possible implementation, the monitoring device generates a plurality of analog users, the analog users send flows of registration, call, etc. to the plurality of network devices, the analog users pass through the plurality of network devices, each network device processes a request of the user, and the network state parameters of each network device are returned to the monitoring device. The monitoring device analyzes the network state parameters of each network device and determines the first network device with faults.

S502, the monitoring device determines a second network device connected with the first network device.

In one possible implementation, there is a device in the network that is connected to the first network and a device that is not connected to the first network device. In the case of a failure of a first network device, the monitoring device only needs to send a network disaster recovery mechanism to a second network device connected to the first network device, so the monitoring device needs to determine the second network device.

S503, the monitoring device determines a network disaster recovery mechanism based on the disaster recovery parameters of the first network device.

Wherein the disaster recovery parameter comprises at least one of the following: the device type of the first network device, the device type of the second network device, and the failure parameter of the first network device.

Optionally, the fault parameters include at least one of location, scale, etc.

In one implementation, the monitoring device first analyzes and generates a fault assessment early warning based on a fault parameter of the first network device and a device type of the first network device, and then determines a network disaster recovery mechanism of the second network device based on the device type of the second network device.

In one implementation, the monitoring network element determines a flow control mechanism of the second network device based on a device type of the second network device when the second network device is an upstream device of the first network device, and determines a disaster recovery mechanism of the second network device based on a device type of the second network device when the second network device is a downstream device of the first network device.

S504, the monitoring equipment sends a network disaster recovery mechanism to the second network equipment.

In one implementation, a monitoring device sends a flow control mechanism to an upstream device of a first network device, the upstream device receives the flow control mechanism, and performs a flow control operation based on the flow control mechanism. The monitoring device sends a disaster recovery mechanism to a downstream device of the first network device, and the downstream device receives the disaster recovery mechanism and switches to a standby device of the corresponding first network device based on the disaster recovery mechanism.

The technical scheme provided by the embodiment at least brings the following beneficial effects: as can be seen from S501-S504, the present application provides a network disaster recovery method, where a monitoring device may be configured to connect with multiple network devices, so as to implement continuous monitoring of each device, and generate a network disaster recovery mechanism of other devices after the device fails by the monitoring device, and send the network disaster recovery mechanism to the other devices. In this way, other devices perform disaster recovery switching according to the network disaster recovery mechanism uniformly generated by the monitoring device, and the other devices switch the standby network elements at the same time, so that the disaster recovery switching efficiency is prevented from being influenced.

In an alternative embodiment, as shown in fig. 6 in connection with fig. 5, in the case where the network parameters include the monitored signaling timeout parameter, the determining, in the above step S501, the first network device that fails based on the network parameters of each of the plurality of network devices may be specifically implemented by the following steps S601-S602:

s601, the monitoring device sends first indication information to each network device respectively.

The first indication information is used for indicating the network equipment to send monitoring signaling to the monitoring equipment in a target period.

Alternatively, the target period may be 10 minutes, 1 minute, or the like, which is not limited in this application.

S602, when the monitoring device does not receive the monitoring signaling of any network device in the plurality of network devices in the target period, determining any network device as the first network device with the fault.

In one possible implementation, the monitoring device sends the first indication information to each network device, and indicates that the network device sends the monitoring signaling to the monitoring device every 5 minutes, and the network device receives the first indication information and sends the monitoring signaling to the monitoring device every 5 minutes from the beginning, and when the monitoring device does not receive the monitoring signaling of any network device within 5 minutes, the monitoring device determines that the network device is the first network device with the fault.

In the 5G network, the monitoring network element sends the first indication information to the AMF network element, the SMF network element, the UDM network element and the NSSF network element in the network every 10 minutes, the SMF network element, the UDM network element and the NSSF network element send the monitoring signaling to the monitoring network element after receiving the first indication information of the monitoring network element, the monitoring network element receives the monitoring signaling of the SMF network element, the UDM network element and the NSSF network element in 10 minutes, and does not receive the monitoring signaling of the AMF network element, so the monitoring network element determines that the AMF network element is a fault network element.

The technical scheme provided by the embodiment at least brings the following beneficial effects: as can be seen from S601 to S602, the present application establishes a monitoring device, and the monitoring device sends first indication information to each network device, so as to instruct the network device to send monitoring signaling to the monitoring device in a target period, and when the monitoring device does not receive the monitoring signaling of any network device, it can determine that the device is a fault device in the network, and further, the monitoring device can quickly and accurately instruct other network devices to start a network disaster recovery mechanism.

In an alternative embodiment, in conjunction with fig. 5, as shown in fig. 7, in the case where the network parameters include heartbeat message parameters, the process of determining the first network device that fails based on the network parameters of each of the plurality of network devices in S501 may be specifically implemented by the following S701-S702:

s701, the monitoring device receives a fault report message from the third network device.

Wherein the third network device is a network device of the plurality of network devices. The fault report message is used for indicating that the third network device does not receive the heartbeat message of the fourth network device within a preset time. The fourth network device is a network device connected to the third network device among the plurality of network devices.

Alternatively, the preset time may be 1 minute, 5 minutes, 15 minutes, or the like, which is not limited in the present application.

S702, the monitoring device determines that the fourth network device is the first network device with the fault.

In an exemplary embodiment, among a plurality of devices in the network, there is heartbeat monitoring between the devices, and there is heartbeat monitoring between the third network device and the fourth network device, when the third network device does not receive the heartbeat message of the fourth network device within 5 minutes, the third network device sends a fault report message to the monitoring device, and after the monitoring device receives the fault report message, the monitoring device may determine that the fourth network device is the first network device that has failed.

In the 5G network, when the monitoring device is a monitoring network element and the third network device is an NRF network element, a plurality of network elements in the network all send heartbeat messages to the NRF network element, when the NRF network element does not receive the heartbeat messages of the SMF network element within 10 minutes, the NRF network element sends a fault report message to the monitoring network element, the monitoring network element receives the fault report message, and determines that the first network device where the SMF network element does not fail.

The technical scheme provided by the embodiment at least brings the following beneficial effects: as known from S701-S702, the present application may determine a fault device based on heartbeat monitoring between devices in a network, and compared with the prior art, the present application may send a fault report message to a monitoring device after the device discovers the fault device, the monitoring device determines the fault device, and the monitoring device sends a network disaster recovery mechanism to a plurality of devices, so as to ensure that the network devices perform disaster recovery operation simultaneously, and avoid affecting the efficiency of the disaster recovery operation.

In an alternative embodiment, in connection with fig. 5, as shown in fig. 8, in the case where the network parameters include network status parameters, the process of determining the first network device that has failed based on the network parameters of each of the plurality of network devices in S501 may be specifically implemented by the following S801 to S803:

s801, the monitoring equipment respectively sends simulation messages to each network equipment.

Wherein the simulation message is used to simulate the message sent by the user to each network device.

S802, the monitoring equipment receives the network state parameters fed back by each network equipment.

Wherein the network state parameter comprises at least one of a route of the network, a network device state, a device link state.

S803, the monitoring device determines the first network device with the fault based on the network state parameters fed back by each network device.

Illustratively, there are multiple network elements in the 5G network, the monitoring network element generates one Registration Request message and simulates a single user sending the Registration Request message to the (R) AN network element. The Registration Request message is sent to the AMF network element through the (R) AN network element, the AMF network element authenticates according to the AUSF according to the user information in the Registration Request message, and after the authentication is completed, the AMF registers with the UDM and acquires subscription information to complete the registration of the simulation user. The AMF feeds back Registration Accept message to the monitoring network element, which indicates that the simulated user registration is successful, and the monitoring network element receives Registration Accept message.

The monitoring network element generates PDU Session Establishment Request a session establishment request message that completes the session establishment via the network element AMF, SMF, PCF, UDM, etc., and returns PDU Session Establishment Request the session establishment request message to the monitoring network element.

The monitoring network element receives Registration Accept information returned by the AMF network element and receives PDU Session Establishment Request a session establishment request message.

After receiving the Registration Accept message returned by the AMF network element, the monitoring network element analyzes the time interval between Registration Accept message and Registration Request message, and determines that the network is normal when the time interval is smaller than the preset time interval.

After receiving the PDU Session Establishment Request session establishment request message, the monitoring network element determines that the process of establishing the session is overtime, simulates a user data packet, and analyzes network delay and network element link state through network elements such as (R) AN and UPF, and further, as the user registration process is normal, namely AMF, AUSF, UDM and other network element faults, the monitoring network element sends heartbeat messages to the PCF network element, and judges PCF network congestion in the network, namely the monitoring network element determines the PCF network element as the network element with faults.

The technical scheme provided by the embodiment at least brings the following beneficial effects: as can be seen from S801 to S802, the present application determines the playing time of the target text information in the target video by allocating numbers to the first text display area in the third image frame and the text information of the target video, thereby determining the position of the target text information in the target video, and accurately positioning the target text information.

In an alternative embodiment, as shown in fig. 9 in conjunction with fig. 5, the network disaster recovery mechanism includes a disaster recovery mechanism and a flow control mechanism, and the second network device includes: the process of determining the network disaster recovery mechanism in the step S503 based on the disaster recovery parameter of the first network device may be specifically implemented by the following steps S901 to S902:

s901, the monitoring equipment determines a flow control mechanism corresponding to the upstream equipment based on the disaster recovery parameter, and determines a disaster recovery mechanism corresponding to the downstream equipment based on the disaster recovery parameter.

In one possible implementation manner, there is a network device a, a network device b, a network device c, and a network device d in the network, where the network devices a, b, and c are connected in sequence, the network device d is a standby device of the network device a, and when the monitoring device determines that the network device b fails, the monitoring device determines a flow control mechanism of the network device a based on a failure parameter of the network device b, and the monitoring device determines a disaster recovery mechanism of the network device c based on a failure parameter of the network device b.

S902, the monitoring device sends a flow control mechanism to the upstream device and sends a disaster recovery mechanism to the downstream device.

In one possible implementation manner, the implementation process of the monitoring device sending the network disaster recovery mechanism to the second network device may be: the monitoring device sends a flow control mechanism to the network device a, the network device receives the flow control mechanism and limits the flow passing through the network device b based on the flow control mechanism, the monitoring device sends a disaster recovery mechanism to the network device c, and the network device c receives the disaster recovery mechanism and changes the route based on the disaster recovery mechanism to be in butt joint with the network device d.

The technical scheme provided by the embodiment at least brings the following beneficial effects: as can be seen from S901-S902, the present application may instruct different devices to start different network disaster recovery mechanisms, by sending the flow control mechanism to the upstream device, the flow can be effectively controlled, network congestion is avoided, and by sending the disaster recovery mechanism to the downstream device, the downstream device can be helped to connect with the standby device quickly, thereby ensuring the stability of the network.

In an alternative embodiment, as shown in fig. 10 in conjunction with fig. 9, after determining the first network device that fails based on the network parameter of each of the plurality of network devices, the method further includes:

S1001, the monitoring equipment generates a fault alarm message of the first network equipment.

Wherein the fault alert message includes at least one of: time, location of failure.

S1002, the monitoring device sends a fault alarm message to the fifth network device.

Wherein the fifth network device is a device other than the first network device among the plurality of network devices.

In one implementation manner, after the monitoring device determines the first network device, the monitoring device sets the current network state as abnormal, records the time, the position, the degree and the like of occurrence of the fault, generates a fault alarm message by the monitoring network element, sends the fault alarm message to all devices except the first network device in the plurality of network devices, and learns that the first network device has a fault after the fifth network device receives the fault alarm message.

When the monitoring network element monitors that the AMF1 network element fails, the monitoring network element sets the current network state as abnormal, records the current time and the AMF1 network element failure, sends an option message to the network element NR, SMF, UPF, PCF, UDM and the like, informs all network elements AMF1 network element failures except the AMF1 network element in the network, and requires the network element to perform early warning.

For example, after determining that the PCF network element is a fault network element, the monitoring network element generates Registration Request message and PDU Session Establishment Request message, and sends a fault alarm message to the network element in the network, where the fault alarm message carries network fault parameters: pcf error, wherein the network element receives the fault alarm message. The monitoring network element sends an instruction to the PCF network element, the instruction is used for indicating the PCF network element to carry out bypass operation, and the PCF network element opens a bypass function, so that the network elements connected to the PCF network element can be mutually conducted without passing through the PCF network element, the monitoring network element sends a flow control mechanism to the AMF network element, and the AMF network element reacts based on the flow control mechanism.

The technical scheme provided by the embodiment at least brings the following beneficial effects: as can be seen from S1001 to S1002, after the monitoring device acquires the fault device, the present application may send a fault alarm message to a third network device in the network, except for the fault device, in addition to sending a network disaster recovery mechanism to the second network device, so as to inform the third network device of the fault device in the network, thereby avoiding expansion of the network fault.

In an alternative embodiment, as shown in fig. 11 in conjunction with fig. 5, after sending the network disaster recovery mechanism to the second network device, the method further includes:

S1101, the monitoring device sends a second indication message to the second network device.

The second indication message is used for indicating the second network device to acquire the recovery state of the first network device.

S1102, the monitoring device receives a recovery status of the first network device from the second network device.

Illustratively, the monitoring network element sends a second indication message to the NR, SMF, UPF network element, the NR, SMF, UPF network element receives the second indication message and continuously monitors the recovery state of the AMF1 network element, the NR, SMF, UPF network element uploads the recovery state of the AMF1 network element to the monitoring network element, and the monitoring network element receives the recovery state of the AMF1 network element.

S1103, the monitoring device adjusts a network disaster recovery mechanism based on the recovery state of the first network device.

Illustratively, when the AMF1 network element recovers 50%, the monitoring network element sends an option message to the NR network element, the NR network element receives the option message and reduces the flow control to 30%, and when the AMF1 network element recovers 80%, the network monitoring network element instructs the NR network element to close the flow control. When the AMF1 network element is completely recovered, the network monitoring network element sends an option message to the SMF network element and the UPF network element, the SMF network element and the UPF network element are instructed to update the route, the SMF network element and the UPF network element receive the option message and are in butt joint with the AMF1 again, and the monitoring network element sets the network state to be normal.

The technical scheme provided by the embodiment at least brings the following beneficial effects: as known from S1101-S1103, after the monitoring device sends the network disaster recovery mechanism to the second network device, the present application may further instruct the second network device to continuously monitor the recovery condition of the first network device, and adjust the disaster recovery mechanism according to the recovery condition of the first network device, so as to improve the utilization efficiency of network resources and reduce the cost of the network.

The foregoing description of the solution provided in the embodiments of the present application has been mainly presented in terms of a method. To achieve the above functions, it includes corresponding hardware structures and/or software modules that perform the respective functions. Those of skill in the art will readily appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

According to the embodiment of the application, the network disaster recovery device can be divided into the functional modules according to the method example, for example, each functional module can be divided corresponding to each function, and two or more functions can be integrated into one processing module. The integrated modules may be implemented in hardware or in software functional modules. Optionally, the division of the modules in the embodiments of the present application is schematic, which is merely a logic function division, and other division manners may be actually implemented.

Fig. 12 is a schematic structural diagram of a network disaster recovery device according to an embodiment of the present application. The network disaster recovery device may be used to perform the network disaster recovery method shown in fig. 5 to 11. The network disaster recovery device shown in fig. 12 includes: a processing unit 1201, a communication unit 1202.

A processing unit 1201, configured to determine a first network device that fails based on network parameters of each of the plurality of network devices; wherein the network parameters include: at least one of a signaling timeout parameter, a heartbeat message parameter, and a network status parameter is monitored.

The processing unit 1201 is further configured to determine a second network device connected to the first network device.

The processing unit 1201 is further configured to determine a network disaster recovery mechanism based on the disaster recovery parameter of the first network device; the disaster recovery parameter includes at least one of: the device type of the first network device, the device type of the second network device, and the failure parameter of the first network device.

A communication unit 1202, configured to send a network disaster recovery mechanism to the second network device.

Optionally, in the case that the network parameter includes a monitoring signaling timeout parameter, the processing unit 1201 is specifically configured to: respectively sending first indication information to each network device, wherein the first indication information is used for indicating the network device to send monitoring signaling to the monitoring device in a target period; and when monitoring signaling of any network device in the plurality of network devices is not received in the target period, determining that any network device is the first network device with faults.

Optionally, in case the network parameter includes a heartbeat message parameter, the processing unit 1201 is configured to: receiving a fault report message from a third network device; the third network device is a network device of the plurality of network devices; the fault report message is used for representing that the third network device does not receive the heartbeat message of the fourth network device within preset time; the fourth network device is a network device connected with the third network device in the plurality of network devices; the fourth network device is determined to be the failed first network device.

Optionally, in the case that the network parameters include network status parameters, the processing unit 1201 is specifically configured to: respectively sending simulation messages to each network device; the simulation message is used for simulating the message sent by the user to each network device; receiving network state parameters fed back by each network device; the network state parameter includes at least one of a route of the network, a network device state, a device link state; and determining the first network equipment with faults based on the network state parameters fed back by each network equipment.

Optionally, the network disaster recovery mechanism includes a disaster recovery mechanism and a flow control mechanism, and the second network device includes: upstream and downstream devices of the first network device; the processing unit 1201 is specifically configured to: determining a flow control mechanism corresponding to upstream equipment based on the disaster recovery parameter, and determining a disaster recovery mechanism corresponding to downstream equipment based on the disaster recovery parameter; sending a network disaster recovery mechanism to a second network device, comprising: and sending a flow control mechanism to the upstream equipment and sending a disaster recovery mechanism to the downstream equipment.

Optionally, after determining the failed first network device based on the network parameter of each of the plurality of network devices, the processing unit 1201 is specifically configured to: generating a fault alarm message of the first network device; the fault alert message includes at least one of: time and location of failure; sending a fault alarm message to a fifth network device; the fifth network device is a device other than the first network device among the plurality of network devices.

Optionally, after sending the network disaster recovery mechanism to the second network device, the processing unit 1201 is further configured to: sending a second indication message to a second network device; the second indication message is used for indicating the second network equipment to acquire the recovery state of the first network equipment; receiving a recovery state of a first network device from a second network device; and adjusting a network disaster recovery mechanism based on the recovery state of the first network device.

The embodiment of the application also provides a computer readable storage medium, which includes computer execution instructions that when executed on a computer, cause the computer to execute the network disaster recovery method provided in the above embodiment.

The embodiment of the application also provides a computer program which can be directly loaded into a memory and contains software codes, and the computer program can realize the network disaster recovery method provided by the embodiment after being loaded and executed by a computer.

Those skilled in the art will appreciate that in one or more of the examples described above, the functions described in the present invention may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, these functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer-readable storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

From the foregoing description of the embodiments, it will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of functional modules is illustrated, and in practical application, the above-described functional allocation may be implemented by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to implement all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and, for example, the division of modules or units is merely a logical function division, and other manners of division may be implemented in practice. For example, multiple units or components may be combined or may be integrated into another device, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form. The units described as separate parts may or may not be physically separate, and the parts shown as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed in a plurality of different places. 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 the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units. The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be essentially or a part contributing to the general technology or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, where the software product includes several instructions to cause a device (may be a single-chip microcomputer, a chip or the like) or a processor (processor) to execute all or part of the steps of the methods of the embodiments of the present invention. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, etc.

The present invention is not limited to the above embodiments, and any changes or substitutions that can be easily understood by those skilled in the art within the technical scope of the present invention are intended to be included in the scope of the present invention. Therefore, the protection scope of the invention is subject to the protection scope of the claims.

Claims (10)

1. A network disaster recovery method, applied to a monitoring device, where the monitoring device is connected to a plurality of network devices, comprising:

determining a first network device that failed based on network parameters of each of the plurality of network devices; wherein the network parameters include: monitoring at least one of a signaling timeout parameter, a heartbeat message parameter, and a network state parameter;

determining a second network device connected to the first network device;

determining a network disaster recovery mechanism based on the disaster recovery parameters of the first network device; the disaster recovery parameter comprises at least one of the following: the device type of the first network device, the device type of the second network device, and the failure parameter of the first network device;

and sending the network disaster recovery mechanism to the second network equipment.

2. The method of claim 1, wherein, in the case where the network parameter comprises a monitoring signaling timeout parameter, the determining the failed first network device based on the network parameter of each of the plurality of network devices comprises:

respectively sending first indication information to each network device, wherein the first indication information is used for indicating the network device to send monitoring signaling to the monitoring device in a target period;

And when monitoring signaling of any network device in the plurality of network devices is not received in a target period, determining the any network device as the first network device with faults.

3. The method of claim 1, wherein, in the case where the network parameter includes a heartbeat message parameter, the determining the failed first network device based on the network parameter of each of the plurality of network devices comprises:

receiving a fault report message from a third network device; the third network device is a network device of the plurality of network devices; the fault report message is used for representing that the third network device does not receive the heartbeat message of the fourth network device within preset time; the fourth network device is a network device connected with the third network device in the plurality of network devices;

and determining the fourth network device as the first network device with the fault.

4. The method of claim 1, wherein, in the case where the network parameter comprises a network status parameter, the determining the failed first network device based on the network parameter of each of the plurality of network devices comprises:

Respectively sending simulation information to each network device; the simulation message is used for simulating the message sent by the user to each network device;

receiving network state parameters fed back by each network device; the network state parameter comprises at least one of a route of a network, a network device state and a device link state;

and determining the first network equipment with faults based on the network state parameters fed back by each network equipment.

5. The method according to any of claims 1-4, wherein the network disaster recovery mechanism comprises a disaster recovery mechanism and a flow control mechanism, and wherein the second network device comprises: upstream and downstream devices of the first network device; the determining a network disaster recovery mechanism based on the disaster recovery parameter of the first network device includes:

determining a flow control mechanism corresponding to the upstream equipment based on the disaster recovery parameter, and determining a disaster recovery mechanism corresponding to the downstream equipment based on the disaster recovery parameter;

the sending the network disaster recovery mechanism to the second network device includes:

and sending the flow control mechanism to the upstream equipment and sending the disaster recovery mechanism to the downstream equipment.

6. The method of claim 5, further comprising, after determining the failed first network device based on the network parameters of each of the plurality of network devices:

generating a fault warning message of the first network device; the fault alert message includes at least one of: time and location of failure;

sending the fault warning message to a fifth network device; the fifth network device is a device other than the first network device among the plurality of network devices.

7. The method according to any of claims 1-4, further comprising, after sending the network disaster recovery mechanism to the second network device:

sending a second indication message to the second network device; the second indication message is used for indicating the second network equipment to acquire the recovery state of the first network equipment;

receiving a recovery state of the first network device from the second network device;

and adjusting the network disaster recovery mechanism based on the recovery state of the first network device.

8. A network disaster recovery device, applied to a monitoring device, the monitoring device being connected to a plurality of network devices, comprising: a processing unit and a communication unit;

The processing unit is used for determining a first network device with faults based on network parameters of each network device in the plurality of network devices; wherein the network parameters include: monitoring at least one of a signaling timeout parameter, a heartbeat message parameter, and a network state parameter;

the processing unit is further configured to determine a second network device connected to the first network device;

the processing unit is further configured to determine a network disaster recovery mechanism based on the disaster recovery parameter of the first network device; the disaster recovery parameter comprises at least one of the following: the device type of the first network device, the device type of the second network device, and the failure parameter of the first network device;

the communication unit is configured to send the network disaster recovery mechanism to the second network device.

9. The network disaster recovery device is characterized by comprising a memory and a processor; the memory is used for storing computer execution instructions, and the processor is connected with the memory through a bus; when the network disaster recovery device is running, the processor executes the computer-executed instructions stored in the memory to cause the network disaster recovery device to perform the network disaster recovery method according to any one of claims 1-7.

10. A computer readable storage medium comprising computer executable instructions which, when run on a computer, cause the computer to perform the network disaster recovery method of any of claims 1-7.