Data recovery method, device and system

Abstract

The present invention discloses a data recovery method, device and system. In the process of control signaling interaction between the main network element and the backup network element through the control channel, the backup network element directly receives the service data from the main network element through the data channel synchronously; then the synchronously received service data is recovered. In this way, in the process of data interaction between the main and backup network elements, the present invention no longer uses a database as a data backup method between the main and backup network elements (that is, the service data storage database is omitted as an intermediate medium), and adopts a direct real-time data synchronization and recovery method, which greatly reduces the transition time of the switching of the main and backup network elements, and effectively improves the data recovery efficiency and reliability.

Description

Technical Field

[0001] The present invention relates to data processing technology, and in particular to a data recovery method, device and system. Background Art

[0002] At present, 4G core network, private network and 5G private network continue to use the high availability cluster (HA) deployment solution of 4G. The core idea is to use the database to realize data backup and recovery between the master and the slave, under the premise of separating business data from business processing logic. The deployment method is as follows: Figure 1 As shown in the figure. The key business data generated by the primary network element is cached in the database, and the primary and backup network elements only exchange necessary control signals. When the primary and backup network elements switch, the backup network element obtains business data from the database for recovery and processes subsequent business.

[0003] However, if Figure 1 As shown, during the switching process between the active and standby network elements, the backup network element has a low efficiency in obtaining service data from the database and restoring it, which significantly increases the transition time of the active and standby switching. Summary of the invention

[0004] In order to solve the above-mentioned defects of the existing active-standby network element switching solution, the embodiments of the present invention creatively provide a data recovery method, device and system.

[0005] According to a first aspect of the present invention, a data recovery method is provided, the method comprising: in a process in which a primary network element and a backup network element interact with each other through a control channel, the backup network element synchronously receives service data from the primary network element through a data channel; the backup network element performs data recovery on the synchronously received service data.

[0006] According to an embodiment of the present invention, the method further includes: the backup network element executing subsequent service processes using the service data after successful data recovery.

[0007] According to an implementation manner of the present invention, the network element is a session management function (SMF) network element, and the control channel and the data channel both communicate using a transmission control protocol (TCP).

[0008] According to an embodiment of the present invention, the control channel is interconnected by network ports with a first bandwidth, and the data channel is interconnected by network ports with a second bandwidth; wherein the first bandwidth is smaller than the second bandwidth.

[0009] According to one embodiment of the present invention, a message type is set corresponding to the key data in the business data; accordingly, the backup network element synchronously receives the business data from the main network element through the data channel, including: the backup network element synchronously receives the key data in the business data through the data channel according to the set message type.

[0010] According to one embodiment of the present invention, the key data in the business data are designed with time tags according to the order of data generation time; accordingly, the backup network element performs data recovery on the business data received synchronously, including: the backup network element pushes the key data received synchronously into the label stack according to the time tag; the backup network element performs data recovery on the pushed key data in the order of popping the data.

[0011] According to the second aspect of the present invention, a data recovery device is also provided, which is applied to a backup network element. The device includes: a receiving module, which is used to synchronously receive business data from the main network element through a data channel during the process of control signaling interaction between the main network element and the backup network element through a control channel; and a data recovery module, which is used to recover the synchronously received business data.

[0012] According to an embodiment of the present invention, the device further includes: an execution module, configured to execute subsequent business processes using the business data after the data is successfully recovered.

[0013] According to an embodiment of the present invention, the key data in the business data is correspondingly set with a message type; accordingly, the receiving module is specifically used to synchronously receive the key data in the business data through a data channel according to the set message type.

[0014] According to one embodiment of the present invention, the key data in the business data are designed with time tags according to the order of data generation time; accordingly, the data recovery module is specifically used to push the key data received synchronously into the label stack corresponding to the time tag; and recover the key data after being pushed into the stack according to the order of being popped.

[0015] According to the third aspect of the present invention, a data recovery system is provided, which includes a main network element and a backup network element; the main network element is used to exchange control signals with the backup network element through a control channel; and is also used to synchronize service data to the backup network element in real time through a data channel; the backup network element is used to synchronously receive service data from the main network element through the data channel; and is also used to recover the synchronously received service data.

[0016] In the data recovery method, device and system of the embodiment of the present invention, during the process of control signaling interaction between the primary network element and the backup network element through the control channel, the backup network element directly and synchronously receives the service data from the primary network element through the data channel; and then performs data recovery on the synchronously received service data. In this way, during the data interaction between the primary and backup network elements, the present invention no longer uses a database as a data backup method between the primary and backup network elements (i.e., the service data storage database is omitted as an intermediate medium), and adopts a direct real-time data synchronization and recovery method, which greatly reduces the transition time of the primary and backup network element switching, while effectively improving the data recovery efficiency and reliability.

[0017] It should be understood that the teachings of the present invention are not required to achieve all of the beneficial effects described above, but specific technical solutions can achieve specific technical effects, and other embodiments of the present invention can also achieve beneficial effects not mentioned above. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The above and other objects, features and advantages of the exemplary embodiments of the present invention will become readily understood by reading the detailed description below with reference to the accompanying drawings. In the accompanying drawings, several embodiments of the present invention are shown in an exemplary and non-limiting manner, in which:

[0019] In the drawings, the same or corresponding reference numerals represent the same or corresponding parts.

[0020] Figure 1 The diagram shows the core network element HA data backup architecture in the related art;

[0021] Figure 2 The improved core network element HA data backup architecture diagram of the present invention is shown;

[0022] Figure 3 A schematic diagram showing the interaction process of the data recovery method according to an embodiment of the present invention is shown;

[0023] Figure 4 A schematic diagram of the implementation process of the data recovery method according to an embodiment of the present invention is shown;

[0024] Figure 5 A schematic diagram showing the structure of a data recovery device according to an embodiment of the present invention is shown;

[0025] Figure 6 A schematic diagram of the structure of a data recovery system according to an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0026] The principles and spirit of the present invention will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided only to enable those skilled in the art to better understand and implement the present invention, and are not intended to limit the scope of the present invention in any way. On the contrary, these embodiments are provided to make the present invention more thorough and complete, and to fully convey the scope of the present invention to those skilled in the art.

[0027] The technical solution of the present invention is further described in detail below in conjunction with the accompanying drawings and specific embodiments.

[0028] Figure 1 The diagram shows the core network element HA data backup architecture in the related art; Figure 2 The improved core network element HA data backup architecture diagram of the present invention is shown; Figure 3 A schematic diagram of the process interaction of the data recovery method according to an embodiment of the present invention is shown.

[0029] refer to Figure 1 , the key business data generated by the main network element is cached in the business data storage database, and the main and backup network elements only exchange necessary control signals. When a switch occurs, the backup network element obtains data from the database and restores it, and then continues to be responsible for subsequent business processing. This solution has a certain degree of versatility, but it ignores the efficiency of network elements obtaining business data from the database and replying, which increases the transition time of the main and backup switching, which is precisely a key technical indicator of the HA solution of 4G and 5G core networks, and there is room for optimization.

[0030] The present invention fully considers Figure 1 The data backup between the traditional core network elements shown in the figure uses a database method, which increases the switching process time. An improved core network element HA data backup architecture diagram is creatively provided.

[0031] refer to Figure 2 The improved core network element HA data backup solution of the present invention no longer uses a database as a data backup method between the primary and backup network elements, but adopts a direct real-time data synchronization and recovery method, that is, the key data generated by the primary network element is synchronized to the backup network element in real time through the data channel for recovery. In this way, once a switch occurs, the backup network element can quickly complete data recovery and continue to execute subsequent business processing.

[0032] based on Figure 2 The improved core network element HA data backup architecture shown in FIG. 1 and the process of the data recovery method according to the embodiment of the present invention are as follows: Figure 3As shown, it includes: when the primary and backup network elements are exchanged, the primary network element and the backup network element interact with each other through the control channel through control signaling; the primary network element synchronizes the service data to the backup network element in real time through the data channel; the backup network element recovers the service data received synchronously; further, the backup network element continues to execute subsequent business processes using the service data after successful data recovery.

[0033] In this way, during the data interaction process between the primary and backup network elements, the present invention no longer uses the database as a data backup method between the primary and backup network elements (that is, the business data storage database is eliminated as an intermediate medium), and adopts a direct real-time data synchronization and recovery method. While greatly reducing the transition time of switching between the primary and backup network elements, it effectively improves data recovery efficiency and reliability.

[0034] Figure 4 A schematic diagram of the implementation flow of the data recovery method according to an embodiment of the present invention is shown.

[0035] refer to Figure 4 An embodiment of the present invention provides a data recovery method on a backup network element side, including: operation 401, during the process of control signaling interaction between the main network element and the backup network element through the control channel, the backup network element synchronously receives service data from the main network element through the data channel; operation 402, the backup network element performs data recovery on the synchronously received service data.

[0036] In one possible implementation, after operation 402, the backup network element uses the service data after the data is successfully restored to execute subsequent service processes.

[0037] Here, the network element is the core network element. Taking the network element as an SMF network element as an example, the control channel and the data channel both use TCP for communication, that is, the control channel and the data channel between the primary and standby SMF network elements both use TCP for communication. Among them, the data channel uses a network port with a larger bandwidth for interconnection, and the control channel can use a network port with a smaller bandwidth for interconnection. For example, the control channel uses a network port with a first bandwidth for interconnection, and the data channel uses a network port with a second bandwidth for interconnection; wherein the first bandwidth is smaller than the second bandwidth.

[0038] In one possible implementation, the key data in the service data is correspondingly set with a message type; accordingly, in operation 402, the backup network element synchronously receives the key data in the service data through the data channel according to the set message type. Here, the key data is data that can fully represent the main information in the service data. In actual applications, data that is sufficient to express information can be customized as key data according to specific business needs.

[0039] In one example, taking the SMF network element as an example, the SMF mainly involves multiple key data: 1) UE information; 2) UE-associated session information; 3) User Port Function (UPF) information for session management. The SMF network element will involve creating, modifying and deleting the above data information in the process of processing session-related services. However, the dependency relationship of the above data information is that the UE information is generated first, and then the UE-associated session information is generated, and then the associated UPF information will be generated in the process of UE session information. Therefore, in order to better and more accurately realize data synchronization, it is necessary to design corresponding message types for the above different key data (the message content needs to include data that can be restored on the backup network element).

[0040] In one possible implementation mode, key data in the business data are designed with time tags according to the order of data generation time; accordingly, in operation 402, the backup network element first pushes the synchronously received key data into the label stack corresponding to the time tag based on the dependency order of the key data during data recovery; and then recovers the pushed key data in the order of popping.

[0041] Specifically, the backup network element first pushes the key data received synchronously into the label stack corresponding to the time label based on the dependency order of the key data when performing data recovery; then performs data recovery on the key data after being pushed into the stack according to the popping order. The popping order corresponds to the dependency order of the key data when performing data recovery. For example, the recovery of data C depends on data B, and the recovery of data B depends on data A, then the popping order is CBA. This ensures that different key data can be recovered in the dependency order during transmission.

[0042] In an application example, also taking the SMF network element as an example, UE information, UE-associated session information and UPF information are recorded as message types A, B and C respectively. Assuming that the UE first session establishment process is taken as an example, the data recovery process is specifically described as follows:

[0043] Step 1: SMF receives the first session creation request from UE, extracts and creates UE information from the request message and synchronizes the information to the device SMF. The information type is A.

[0044] Step 2, then extract the session request from the request message and create part of the session information (note that the session information is not complete at this time) and select the appropriate UPF and create a session on the UPF. After the UPF responds (after receiving the response, the UPF information of the session will be synchronized, information type C), continue to create and synchronize the session information, information type B,

[0045] Step 3, at this point, the data generated by the session creation process are synchronized to the backup network element in real time and restored. The other processes of SMF are similar to this and will not be repeated. However, there is a problem with this process: the recovery of data C depends on data B, and the recovery of data B depends on data A. However, in the above process, A is synchronized first, followed by C, and finally B, so there is a problem with the data recovery of C. The application example of the present invention involves a set of associated data synchronization mechanisms that can ensure that the A, B, and C messages can be fully synchronized to the backup data and restored in the above dependency order.

[0046] Step 4: The key data in the business data are designed with time tags according to the order of data generation time, that is, the corresponding tag message pairs SA, EA, SB, EB, SC, EC are designed. SA is sent before sending A, SB is sent before generating C, SC and EC are sent before and after sending C, EB is sent after sending B, and EA is sent last. In summary, the messages sent are SA->A->SB->B>SC->C->EC->EB->EA.

[0047] Step 5: After receiving the key data, the backup network element pushes the label stack pair corresponding to the time label into the stack based on the dependency order of the key data in the subsequent data recovery, that is, C message is pushed into the stack first, B message is pushed into the stack later, and A message is pushed into the stack last. After all label pairs are matched, they are processed in the order of being popped out of the stack. If a label does not match, it is directly discarded. This ensures that the associated information can be restored in the dependency order during transmission.

[0048] Based on the above steps 1 to 5, when the SMF network element performs a network element switch, the backup network element will immediately discard the unrecovered historical data and use the successfully recovered data to process subsequent services. The entire process avoids the delay caused by the traditional solution using the database method, and greatly improves the switching transition efficiency between the SMF active and standby network elements.

[0049] Similarly, based on the data recovery method described above, an embodiment of the present invention further provides a data recovery device, which is applied to a backup network element, referring to Figure 5 The device 50 includes: a receiving module 501, which is used to synchronously receive service data from the primary network element through a data channel during the process of control signaling interaction between the primary network element and the backup network element through a control channel; a data recovery module 502, which is used to recover the synchronously received service data.

[0050] According to one embodiment of the present invention, Figure 5 As shown, the device 50 further includes: an execution module 503, which is used to execute subsequent business processes using the business data after the data recovery is successful.

[0051] According to an embodiment of the present invention, the key data in the business data is correspondingly set with a message type; accordingly, the receiving module 501 is specifically used to synchronously receive the key data in the business data through the data channel according to the set message type.

[0052] According to one embodiment of the present invention, the key data in the business data are designed with time tags according to the order of data generation time; accordingly, the data recovery module 502 is specifically used to push the key data received synchronously into the label stack corresponding to the time tag; and recover the key data after being pushed into the stack according to the order of being popped.

[0053] According to an implementation manner of the present invention, the network element is an SMF network element, and the control channel and the data channel both communicate in TCP mode.

[0054] According to an embodiment of the present invention, the control channel is interconnected by network ports with a first bandwidth, and the data channel is interconnected by network ports with a second bandwidth; wherein the first bandwidth is smaller than the second bandwidth.

[0055] Furthermore, based on the data recovery method described above, an embodiment of the present invention provides a data recovery system, such as Figure 6 As shown, the system includes: a main network element 601 and a backup network element 602; wherein the main network element 601 is used to perform control signaling interaction with the backup network element 602 through a control channel; and is also used to synchronize service data to the backup network element 602 in real time through a data channel; the backup network element 602 is used to synchronously receive service data from the main network element 601 through a data channel; and is also used to perform data recovery on the synchronously received service data.

[0056] It should be noted that the above description of the data recovery device or system embodiment is different from the above description. Figures 2 to 4 The description of the method embodiment shown is similar, with the same Figures 2 to 4 The method embodiment shown in the figure has similar beneficial effects, so it will not be described in detail. For technical details not disclosed in the data recovery device or system embodiment of the present invention, please refer to the aforementioned Figures 2 to 4 The description of the method embodiment shown in the figure can be understood, and in order to save space, it will not be repeated.

[0057] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0058] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0059] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units; they may be located in one place or distributed on multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0060] In addition, all functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0061] A person skilled in the art can understand that all or part of the steps of implementing the above method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above method embodiment; and the aforementioned storage medium includes: mobile storage devices, read-only memories (ROM), magnetic disks or optical disks, etc., various media that can store program codes.

[0062] Alternatively, if the above-mentioned integrated unit of the present invention is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present invention can be essentially or partly reflected in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0063] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A data recovery method, characterized in that: The method comprises: During the process of control signaling interaction between the primary network element and the backup network element through the control channel, the backup network element synchronously receives service data from the primary network element through the data channel; The backup network element performs data recovery on the synchronously received service data; The key data in the service data is correspondingly provided with a message type; accordingly, the backup network element synchronously receives the service data from the primary network element through the data channel, including: the backup network element synchronously receives the key data in the service data through the data channel according to the set message type; The key data in the business data are designed with time tags according to the order of data generation time; accordingly, the backup network element performs data recovery on the business data received synchronously, including: the backup network element pushes the key data received synchronously into the label stack corresponding to the time tag based on the dependency order of the key data when performing data recovery; the backup network element performs data recovery on the pushed key data in the order of popping the data.

2. The method according to claim 1, characterized in that The method further comprises: The backup network element uses the service data after the data is successfully restored to execute subsequent service processes.

3. The method according to claim 1, characterized in that The network element is an SMF network element, and the control channel and the data channel both communicate in TCP mode.

4. The method according to claim 3, characterized in that The control channel is interconnected by a network port with a first bandwidth, and the data channel is interconnected by a network port with a second bandwidth; wherein the first bandwidth is smaller than the second bandwidth.

5. A data recovery device, characterized in that: Applied to backup network elements, the device comprises: A receiving module, used for synchronously receiving service data from the primary network element through a data channel during the process of control signaling interaction between the primary network element and the backup network element through a control channel; A data recovery module, used to recover synchronously received business data; The key data in the business data is correspondingly provided with a message type; accordingly, the receiving module is specifically used to synchronously receive the key data in the business data through the data channel according to the set message type; The key data in the business data are designed with time tags according to the order of data generation time; accordingly, the data recovery module is specifically used to push the synchronously received key data into the label stack corresponding to the time tag based on the dependency order of the key data during data recovery; and recover the pushed key data according to the popping order.

6. The device according to claim 5, characterized in that The device also includes: The execution module is used to execute subsequent business processes using the business data after successful data recovery.

7. A data recovery system, characterized in that: The system includes a primary network element and a backup network element; The master network element is used to perform control signaling interaction with the backup network element through the control channel; and is also used to synchronize service data to the backup network element in real time through the data channel; The backup network element is used to synchronously receive the service data from the primary network element through the data channel; It is also used to recover synchronously received business data; The key data in the service data is correspondingly provided with a message type; accordingly, the backup network element is specifically used to synchronously receive the key data in the service data through the data channel according to the set message type; The key data in the business data are designed with time tags according to the order of data generation time; accordingly, the backup network element is also specifically used to push the synchronously received key data into the label stack corresponding to the time tag based on the dependency order of the key data during data recovery; and restore the pushed key data in the order of popping.

8. The system according to claim 7, characterized in that The network element is an SMF network element, and the control channel and the data channel both communicate in TCP mode.

Images