WO2022100719A1 - 数据处理方法、装置、系统和计算机可读存储介质 - Google Patents

数据处理方法、装置、系统和计算机可读存储介质 Download PDF

Info

Publication number
WO2022100719A1
WO2022100719A1 PCT/CN2021/130483 CN2021130483W WO2022100719A1 WO 2022100719 A1 WO2022100719 A1 WO 2022100719A1 CN 2021130483 W CN2021130483 W CN 2021130483W WO 2022100719 A1 WO2022100719 A1 WO 2022100719A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration data
underlay
data
difference
forwarding plane
Prior art date
Application number
PCT/CN2021/130483
Other languages
English (en)
French (fr)
Inventor
梁体云
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2022100719A1 publication Critical patent/WO2022100719A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • H04L41/0813Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00Packet switching elements
    • H04L49/55Prevention, detection or correction of errors
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00Packet switching elements
    • H04L49/60Software-defined switches

Definitions

  • the embodiments of the present application relate to, but are not limited to, the technical field of data processing, and in particular, relate to a data processing method, apparatus, system, and computer-readable storage medium.
  • Embodiments of the present application provide a data processing method, apparatus, system, and computer-readable storage medium.
  • an embodiment of the present application provides a data processing method, including: acquiring first difference configuration data between a control plane and a forwarding plane device, and obtaining first Underlay configuration data according to the first difference configuration data; Obtain second Underlay configuration data, where the second Underlay configuration data is configuration data in the forwarding plane device that is not repaired by the control plane; update the second Underlay configuration data according to the first Underlay configuration data, and obtain the updated The updated second Underlay configuration data is removed from the configuration data of the forwarding plane device, so as to obtain target configuration data that satisfies the repair condition.
  • an embodiment of the present application further provides a data processing apparatus, including: an auditing and reconciliation unit that acquires first difference configuration data between devices on the control plane and the forwarding plane, and obtains the first difference configuration data according to the first difference configuration data
  • the first Underlay configuration data the first data obtaining unit obtains second Underlay configuration data, where the second Underlay configuration data is configuration data in the forwarding plane device that is not repaired by the control plane; the first data updating unit, according to the second Underlay configuration data
  • An Underlay configuration data updates the second Underlay configuration data to obtain the updated second Underlay configuration data;
  • the data repair unit repairs the target configuration data in the forwarding plane device according to the updated second Underlay configuration data,
  • the target configuration data does not include the updated second Underlay configuration data.
  • an embodiment of the present application further provides a data processing system, including: a memory, a processor, and a computer program stored in the memory and running on the processor, the processor implements the computer program when the processor executes the computer program
  • a data processing system including: a memory, a processor, and a computer program stored in the memory and running on the processor, the processor implements the computer program when the processor executes the computer program
  • an embodiment of the present application further provides a computer-readable storage medium storing computer-executable instructions, where the computer-executable instructions are used to execute the data processing method described in the first aspect.
  • FIG. 1 is a schematic diagram of a system architecture platform for executing a data processing method provided by an embodiment of the present application
  • FIG. 2 is a flowchart of a data processing method provided by an embodiment of the present application.
  • FIG. 3 is a flowchart of obtaining first differential configuration data provided by an embodiment of the present application.
  • FIG. 5 is a flowchart of filtering out the third Underlay configuration data from the first Underlay configuration data provided by an embodiment of the present application;
  • FIG. 8 is a flowchart of a data processing method provided by an embodiment of the present application.
  • FIG. 9 is a flowchart of an implementation device for auditing, reconciling, and repairing device configuration of a control plane and a forwarding plane provided by an embodiment of the present application;
  • FIG. 10 is a schematic diagram of a data processing apparatus provided by an embodiment of the present application.
  • SDN Software Defined Network, Software Defined Network
  • SDN plays the role of the brain as the control plane to be responsible for orchestration and distribution of forwarding policies.
  • SDN API Application Programming Interface, Application programming interface
  • the connectivity between the control plane and the management network of the forwarding plane is abnormal, and the configuration delivery of the forwarding plane fails, resulting in inconsistent data between the control plane and the forwarding plane. , so that the business cannot be used normally.
  • the switches on the device side of the forwarding plane will also have some exceptions. In some examples, these include: switch software failures, hardware defects, malicious attacks, artificial Configuration data exceptions caused by incorrect configuration and other reasons.
  • the relevant operation and maintenance technology can solve the above abnormal situation through auditing, reconciliation and repair.
  • the control plane and the forwarding plane will identify the forwarding plane equipment when auditing, reconciling and repairing. All configurations, but the Overlay and Underlay configuration data of forwarding plane devices are not distinguished.
  • the control plane is repaired, if the basic underlay configuration of the device is repaired, the basic configuration of the forwarding plane device will be deleted, causing the device to become paralyzed and unavailable.
  • the present application provides a data processing method, apparatus, system and computer-readable storage medium, wherein the data processing method includes the following steps: acquiring first difference configuration data between the control plane and forwarding plane devices, and Obtain first Underlay configuration data according to the first difference configuration data; obtain second Underlay configuration data, where the second Underlay configuration data is configuration data in the forwarding plane device that is not repaired by the control plane; configure the second Underlay according to the first Underlay configuration data The data is updated to obtain the updated second Underlay configuration data; the updated second Underlay configuration data is removed from the configuration data of the forwarding plane device, so as to obtain the target configuration data that satisfies the repair condition.
  • the embodiments of the present application can acquire the first Underlay configuration data and the second Underlay configuration data between the current control plane and the forwarding plane devices, and combine the first Underlay configuration data and the second Underlay configuration data
  • the comparison processing is performed to update the second Underlay configuration data. Since the second Underlay configuration data is configuration data in the forwarding plane device that cannot be repaired by the control plane, this embodiment of the present application can be excluded from the configuration data of the forwarding plane device.
  • the above-mentioned updated second Underlay configuration data is used to obtain target configuration data that satisfies the repair condition.
  • the embodiment of the present application can automatically identify the Underlay configuration data that does not need to be repaired in the current forwarding plane device, so that when the control plane initiates repair, the updated second Underlay configuration data in the forwarding plane device will be automatically shielded. Therefore, , the embodiment of the present application can not only improve the automation rate of network system environment operation and maintenance, but also improve the stability of the network system environment.
  • FIG. 1 is a schematic diagram of a system architecture platform for a data processing method provided by an embodiment of the present application.
  • the system architecture platform includes a data processing system 100, wherein the above-mentioned data processing system 100 is provided with a processor 110 and a memory 120, wherein the processor 110 and the memory 120 may be connected by a bus or in other ways, In Figure 1, the connection through the bus is taken as an example.
  • the memory 120 can be used to store non-transitory software programs and non-transitory computer-executable programs. Additionally, memory 120 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, memory 120 may include memory 120 located remotely from processor 110, which may be connected to the system architecture platform through a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
  • system architecture platform can be applied to a 3G communication network system, an LTE communication network system, a 5G communication network system, and a subsequently evolved mobile communication network system, etc., which is not specifically limited in this embodiment.
  • system architecture platform shown in FIG. 1 does not constitute a limitation on the embodiments of the present application, and may include more or less components than those shown in the figure, or combine some components, or different Component placement.
  • the processor 110 can call the data processing program stored in the memory 120 to execute the data processing method.
  • FIG. 2 is a flowchart of a data processing method provided by an embodiment of the present application.
  • the method includes but is not limited to step S100 , step S200 , step S300 and step S400 .
  • Step S100 acquiring first difference configuration data between the control plane and forwarding plane devices, and obtaining first Underlay configuration data according to the first difference configuration data;
  • Step S200 acquiring second Underlay configuration data, where the second Underlay configuration data is configuration data in the forwarding plane device that is not repaired by the control plane;
  • Step S300 updating the second Underlay configuration data according to the first Underlay configuration data to obtain the updated second Underlay configuration data
  • Step S400 Remove the updated second Underlay configuration data from the configuration data of the forwarding plane device to obtain target configuration data that satisfies the repair condition.
  • the data processing method according to the embodiment of the present application can be applied to the scenario where the control plane manages the forwarding plane for the first time and is not configured and delivered, and can also be applied to the scenario after the control plane is configured and delivered.
  • the control plane manages the forwarding plane for the first time and is not configured and delivered
  • the control plane is configured and delivered.
  • the control plane when the control plane manages the forwarding plane for the first time and the configuration is not issued, the control plane can audit and reconcile the configuration data of the forwarding plane devices, so as to obtain the information between the control plane and the forwarding plane.
  • the first differential configuration data, and the first differential configuration data is filtered and integrated to obtain the first Underlay configuration data corresponding to the first differential configuration data; Therefore, the obtained second Underlay configuration data is empty; then, the first Underlay configuration data is compared with the second Underlay configuration data, thereby adding all the first Underlay configuration data to the second Underlay configuration data, To obtain the updated second Underlay configuration data, since the updated second Underlay configuration data is the updated configuration data in the forwarding plane device that will not be repaired by the control plane, when the control plane needs to repair the configuration data in the forwarding plane device.
  • the updated second Underlay configuration data When configuring the data, the updated second Underlay configuration data will be removed from the configuration data of the forwarding plane device, so that the configuration and repair of the updated second Underlay configuration data will not be performed, thereby preventing the device from being paralyzed and unavailable due to repair. Case.
  • the configuration data of the control plane and the forwarding plane are inconsistent.
  • it includes: the management network of the control plane is disconnected Software defects, hardware failures, malicious attacks on the switch side, and human misconfigurations on the switch side may cause inconsistent configurations between the control plane and the switch's forwarding plane, resulting in data traffic not being forwarded normally. Therefore, in this embodiment of the present application, after the configuration and distribution of the control plane, the second Underlay configuration data stored in the history needs to be updated again.
  • the control plane will audit and reconcile the configuration data of the forwarding plane device again to obtain the control plane and forwarding the first difference configuration data between the planes, and filtering and integrating the first difference configuration data to obtain the first Underlay configuration data corresponding to the first difference configuration data; then, the embodiment of the present application will obtain the historically stored For the second Underlay configuration data, the first Underlay configuration data and the second Underlay configuration data are compared to obtain the updated second Underlay configuration data. Since the updated second Underlay configuration data is the updated one in the forwarding plane device Configuration data that will not be repaired by the control plane. Therefore, when the control plane needs to repair the configuration data in the forwarding plane device, the updated second Underlay configuration data will be removed from the configuration data of the forwarding plane device. After the second Underlay configuration data is used for configuration repair, the device can be prevented from being paralyzed and unavailable due to repair.
  • the embodiments of the present application can automatically identify the Underlay configuration data that does not need to be repaired in the current forwarding plane device, that is, the updated second Underlay configuration data, so that when the control plane initiates repair, the The updated second Underlay configuration data in the forwarding plane device is automatically shielded, so as to prevent the device from being paralyzed and unavailable due to repair. Therefore, the embodiment of the present application can not only improve the automation rate of network system environment operation and maintenance, but also improve the The stability of the network system environment.
  • control plane serves as the data source of the forwarding plane
  • configuration data of the forwarding plane to be repaired needs to be based on the data of the control plane.
  • FIG. 3 is a flowchart of a data processing method provided by an embodiment of the present application.
  • the above-mentioned step S100 includes but is not limited to step S500 .
  • Step S500 obtaining historical configuration data and current configuration data of the forwarding plane device delivered by the control plane to the forwarding plane device, and obtaining first difference configuration data between the control plane and the forwarding plane device according to the historical configuration data and the current configuration data, and obtain the first Underlay configuration data according to the first difference configuration data.
  • step S500 it can be executed when the control plane manages the forwarding plane for the first time and the configuration is not issued, or can be executed after the control plane is configured and issued, as follows:
  • the control plane when the control plane manages the forwarding plane for the first time and the configuration and delivery are not performed, the control plane audits and reconciles the configuration data of the forwarding plane device, so as to obtain the control plane and deliver it to the forwarding plane device.
  • the historical configuration data of the forwarding plane is the first time that the control plane manages the forwarding plane and has not been configured and distributed. Therefore, the above historical configuration data is empty; at the same time, the control plane will obtain the current configuration data of the forwarding plane devices; The configuration data and the current configuration data are audited and reconciled, so as to obtain the first difference configuration data between the devices on the control plane and the forwarding plane.
  • control plane after the control plane is configured and delivered, the control plane will audit and reconcile the configuration data of the forwarding plane devices again, so as to obtain the historical configuration data delivered by the control plane to the forwarding plane devices.
  • historical configuration data select the last configured and delivered data.
  • control plane will obtain the current configuration data of the forwarding plane devices; then, the control plane will audit and reconcile the historical configuration data with the current configuration data, so as to obtain the first difference configuration data between the control plane and the forwarding plane devices.
  • FIG. 4 is a flowchart of a data processing method provided by an embodiment of the present application.
  • obtaining the first Underlay configuration data according to the first difference configuration data includes but is not limited to the following steps: S600.
  • Step S600 when the historical configuration data does not include the second configuration data and the current configuration data includes the second configuration data, the second configuration data is used as the first Underlay configuration data.
  • the control plane after the control plane audits and reconciles the configuration data of the forwarding plane device, it will obtain the first difference configuration data, that is, the historical configuration data sent by the control plane to the forwarding plane device and the current configuration of the forwarding plane device.
  • the difference configuration data between the data then the embodiment of the present application will perform filtering and integration processing on the first difference configuration data to obtain the first Underlay configuration data corresponding to the first difference configuration data.
  • the specific filtering and integration processing can refer to the following four cases :
  • the configuration data of the control plane is used as the standard, and the instance is used as the granularity to control the configuration data sent to the forwarding plane. In some examples, it does not appear that the control plane does not have the data of the vpls instance zenic_123, while the forwarding plane device has the configuration of the vpls instance zenic_123.
  • the configuration data of the control plane is used as the standard and the instance is used as the granularity.
  • the instance data is the configuration data sent by the control plane to the forwarding plane , but when the attribute value corresponding to the instance data in the control plane configuration data is inconsistent with the attribute value corresponding to the forwarding plane configuration data, this embodiment of the present application will filter out the instance data and not add it to the first Underlay configuration data .
  • both the control plane and the forwarding plane configuration data have the vpls instance zenic_123 data, but the attribute vni-label value of the control plane vpls instance zenic_123 is 100, and the attribute vni-label value of the forwarding plane vpls instance zenic_123 is 200, then The vpls instance zenic_123 will be filtered out and not added to the first Underlay configuration data.
  • the configuration data of the control plane is used as the standard, and the instance is used as the granularity.
  • the instance data will be filtered out and Not added to the first Underlay configuration data.
  • the control plane configuration data has vpls instance zenic_123, but the forwarding plane configuration data does not have vpls instance zenic_123, the vpls instance zenic_123 will be filtered out and not added to the first Underlay configuration data.
  • the fourth filtering integration processing situation The configuration data of the control plane is used as the standard, and the instance is used as the granularity. When there is no instance data on the control plane, but this instance data is available on the forwarding plane, the instance data will be added to the first An Underlay configuration data.
  • the control plane configuration data does not have the vpls instance zenic_123, but the forwarding plane configuration data has the vpls instance zenic_123, then the vpls instance zenic_123 needs to be added to the first Underlay configuration data.
  • step S600 when there is a fourth filtering integration processing situation, as shown in step S600, when the historical configuration data does not include the second configuration data and the current configuration data includes the second configuration data, the second configuration data is used as the first Underlay configuration data .
  • FIG. 5 is a flowchart of a data processing method provided by an embodiment of the present application. Before the foregoing step S300 , the method further includes, but is not limited to, steps S710 and S720 .
  • Step S710 obtaining third Underlay configuration data, where the third Underlay configuration data is configuration data that fails to be deleted after the forwarding plane device receives the deletion task of the control plane;
  • Step S720 Delete configuration data consistent with the third Underlay configuration data from the first Underlay configuration data.
  • step S300 is continued.
  • the above-mentioned third Underlay configuration data is the configuration data that fails to be deleted after the forwarding plane device receives the deletion task of the control plane.
  • the control plane service deletion refinement is to delete the instances or attributes of the forwarding plane device according to a certain dependency relationship.
  • the embodiment of this application not only ensures the reliability of the deletion process of the control plane service deletion, but also performs the deletion results. Inspection of. Among them, the situations in which the task of deleting service data on the control plane is issued can be divided into the following three types:
  • the first case of service data deletion task delivery the control plane service data deletion task fails to be delivered, the control plane service data remains undeleted, and the forwarding plane device configuration data remains undeleted.
  • the second case of service data deletion task delivery The control plane service data deletion task is successfully delivered, but the forwarding plane device fails to delete an instance or attribute data, and the forwarding plane device returns the error reason and sends it to the control plane.
  • the control plane receives the error report, it sends an alarm, and the alarm includes the specific cause of the error when the device on the forwarding plane deletes the error.
  • the service data on the control plane is deleted, and the instance data that fails to be deleted on the forwarding plane device is added to the third Underlay configuration data.
  • the third scenario of service data deletion task delivery The service data deletion task on the control plane is successfully delivered, and the control plane detects a connectivity problem with the forwarding plane. If the retransmission to the upper limit fails, it will be recorded and an alarm will be recorded. For this failure, the configuration audit and repair methods can be used to re-manage the configuration delivered to the device side.
  • instance data is added to the third Underlay configuration data only in the second type of service data deletion task delivery situation. Therefore, when there is a situation in which the second type of service data deletion task is issued, after obtaining the first Underlay configuration data, the embodiment of the present application also needs to obtain the pre-stored third Underlay configuration data, and delete and delete from the first Underlay configuration data Configuration data consistent with the pre-stored third Underlay configuration data.
  • the third underlay configuration data is that the forwarding plane fails to delete related configuration data when the service data delivered by the control plane is deleted, and subsequent configuration auditing and repair methods cannot clear such residual configuration data. Therefore, control The plane saves the configuration data that fails to be deleted to the third Underlay configuration data.
  • FIG. 6 is a flowchart of a data processing method provided by an embodiment of the present application, and the method further includes, but is not limited to, steps S810 and S820 .
  • Step S810 obtaining second difference configuration data according to the first Underlay configuration data and the third Underlay configuration data;
  • Step S820 Update the third Underlay configuration data according to the second difference configuration data.
  • the embodiment of the present application further updates the third Underlay configuration data after auditing and reconciling the first Underlay configuration data and the pre-stored third Underlay configuration data.
  • the update method of the third Underlay configuration data is specifically as follows: the pre-stored third Underlay configuration data has certain configuration data but the first Underlay configuration data does not have the configuration data, then the pre-stored third Underlay configuration data contains this configuration data. Configuration data will be deleted. In some examples, when the third Underlay configuration data includes the first configuration data and the second difference configuration data does not include the first configuration data, the first configuration data is deleted from the third Underlay configuration data.
  • FIG. 7 is a flowchart of a data processing method provided by an embodiment of the present application.
  • the above-mentioned step S300 includes, but is not limited to, steps S910 and S920 .
  • Step S910 obtaining third difference configuration data according to the first Underlay configuration data and the second Underlay configuration data;
  • Step S920 Update the second Underlay configuration data according to the third difference configuration data to obtain the updated second Underlay configuration data.
  • this embodiment of the present application will audit the deleted first Underlay configuration data and the second Underlay configuration data. account to obtain the third difference configuration data, and then update the second Underlay configuration data according to the third difference configuration data to obtain the updated second Underlay configuration data.
  • update methods of the above-mentioned second Underlay configuration data include the following two methods:
  • the first update method when the second Underlay configuration data includes the third configuration data and the third difference configuration data does not include the third configuration data, delete the third configuration data from the second Underlay configuration data;
  • the second update method when the third difference configuration data includes the fourth configuration data and the second Underlay configuration data does not include the fourth configuration data, the fourth configuration data is added to the second Underlay configuration data.
  • first configuration data second configuration data
  • third configuration data third configuration data
  • fourth configuration data an instance may be used as a granularity.
  • FIG. 8 is a flowchart of a data processing method provided by an embodiment of the present application
  • FIG. 9 is a control plane and a forwarding plane device provided by an embodiment of the present application. The flow chart of configuring the realization device of audit reconciliation and repair.
  • the control plane when the control plane manages the forwarding plane for the first time and does not perform configuration delivery, the control plane may perform the first audit and reconciliation on the configuration data of the forwarding plane device 220, so as to obtain the initial information between the control plane and the forwarding plane. Difference configuration data, and obtain initial second Underlay configuration data according to the initial difference configuration data, the initial second Underlay configuration data is the initial reserved Underlay configuration data that will not perform configuration repair, and this embodiment of the present application will also use the initial underlay configuration data.
  • the second Underlay configuration data is stored in the database 230 .
  • the configuration data of the control plane and the forwarding plane are inconsistent.
  • control plane will audit and reconcile the configuration data of the forwarding plane device 220 again. , obtain the first differential configuration data between the current control plane and the forwarding plane, and perform data reconciliation processing on the first differential configuration data; wherein, the data reconciliation processing includes filtering and integrating the first differential configuration data.
  • the data reconciliation processing also includes filtering according to Integrate the processed first Underlay configuration data and the third Underlay configuration data to update the third Underlay configuration data, and then obtain the updated third Underlay configuration data; then, after the above data reconciliation processing, the embodiment of the present application will Auditing and reconciling the updated first Underlay configuration data and the initial second Underlay configuration data is performed, thereby updating the initial second Underlay configuration data to obtain updated second Underlay configuration data.
  • the sending module 210 in FIG. 9 it is configured to send configuration data to the forwarding plane device 220; specifically, the sending module 210 is configured to store the service data in the database 230; then the adaptation layer decomposes the service data into device dimensions Finally, the decomposed service data will be delivered to the forwarding plane device 220.
  • the embodiment of the present application provides an application example for description.
  • the control plane when the service orchestrated by the northbound network orchestrator is delivered, the control plane will orchestrate and deliver the service configuration, and the service orchestration data of one control plane will be split into N configurations on the device side and delivered to the device.
  • the control plane records and stores the equipment on demand with the service data delivered.
  • the control plane when the management network connection between the control plane and the forwarding plane is abnormal, the control plane will try to retransmit and deliver the service configuration. If the service data on the plane is inconsistent, you need to use the configuration audit reconciliation and repair method to ensure that the data on the control plane and the forwarding plane are consistent. To repair, you need to obtain the current first Underlay configuration of the forwarding plane device during audit reconciliation. data and the pre-stored second Underlay configuration data, and then review and update to obtain the latest second Underlay configuration data of the forwarding plane device.
  • the execution steps of the control plane may include: the control plane network management obtains the configuration of the forwarding plane equipment; then the control plane converts the configuration data returned by the equipment into the data structure of the network management, and stores it in the operation database; then the control plane network management
  • the device inventory data of the control plane and the operation library data obtained from the device layer are converted into xml, and the instances and attributes are compared one by one.
  • the parts that are inconsistent in the network management comparison are marked in red; then the difference configuration data displayed in red on the control plane network management is displayed on the device.
  • the controller network management After adding the initial second Underlay configuration data, the controller network management will no longer display the difference configuration data in the irreparable Underlay configuration data; then, on the control plane network management, select one or more devices for auditing and reconciling the devices to obtain the device and control The difference between the latest first Underlay configuration data and the second Underlay configuration data on the face; after the data review, choose to update the second Underlay configuration data, and update the second Underlay configuration data of different devices on the control plane; after the second Underlay configuration data is updated, the controller The NMS will no longer display the difference configuration data in the irreparable Underlay configuration data; finally, the repaired configuration results will be returned to the NMS, and there will be an alarm notification and specific reasons for repair failures.
  • configuration auditing is an important inspection tool.
  • the timing function of the configuration auditing can also be configured by the network management through the embodiments of the present application. It can inspect whether the configuration of the forwarding plane is abnormal, and whether the equipment on the forwarding plane is abnormal, such as: hardware damage, software failure, malicious attack, artificial misconfiguration, and can repair it in time.
  • the data processing method of the embodiment of the present application can also be applied to other fields of configuration delivery.
  • the technical solutions of the embodiments of the present application can be combined with a timing framework to perform regular inspection of the network system and automatically repair abnormal configuration of the system at regular intervals; it can also be combined with the configuration data issued by the control plane to configure the auditing and reconciliation display configuration data delivery. It can also be combined with the control plane repair function to avoid the operation of the Underlay configuration of the forwarding plane device, which will cause the device to be paralyzed.
  • FIG. 10 is a schematic diagram of a data processing apparatus 300 provided by an embodiment of the present application.
  • the data processing apparatus 300 includes, but is not limited to, an audit reconciliation unit 310, a first data acquisition unit 320, and a first data update unit. unit 330 and data repair unit 340.
  • the auditing and reconciliation unit 310 is configured to obtain the first difference configuration data between the control plane and the forwarding plane devices, and obtain the first Underlay configuration data according to the first difference configuration data; the first data obtaining unit 320 is configured to Acquire second Underlay configuration data, where the second Underlay configuration data is configuration data in the forwarding plane device that is not repaired by the control plane; the first data updating unit 330 is configured to update the second Underlay configuration data according to the first Underlay configuration data, Obtain the updated second Underlay configuration data; the data repair unit 340 is configured to repair the target configuration data in the forwarding plane device according to the updated second Underlay configuration data, the target configuration data does not include the updated second Underlay configuration data.
  • the data processing apparatus 300 shown in FIG. 10 further includes, but is not limited to, a second data acquisition unit 350 and a data deletion unit 360 .
  • the second data acquisition unit 350 is configured to acquire third Underlay configuration data, which is the configuration data that fails to be deleted after the forwarding plane device receives the deletion task of the control plane; the data deletion unit 360 is configured to The configuration data consistent with the third Underlay configuration data is deleted from the first Underlay configuration data.
  • the data processing apparatus 300 shown in FIG. 10 further includes, but is not limited to, a second data updating unit 370 .
  • the second data updating unit 370 is configured to obtain the second difference configuration data according to the first Underlay configuration data and the third Underlay configuration data, and update the third Underlay configuration data according to the second difference configuration data.
  • the above-mentioned second data updating unit 370 is configured to delete the first configuration data from the third Underlay configuration data when the third Underlay configuration data includes the first configuration data and the second difference configuration data does not include the first configuration data.
  • Configuration Data is configured to delete the first configuration data from the third Underlay configuration data when the third Underlay configuration data includes the first configuration data and the second difference configuration data does not include the first configuration data.
  • the auditing and reconciliation unit 310 it is also configured to obtain the historical configuration data and current configuration data of the forwarding plane devices sent by the control plane to the forwarding plane devices, and obtain the control plane and the current configuration data according to the historical configuration data and the current configuration data. Forward the first difference configuration data between the plane devices, and obtain the first Underlay configuration data according to the first difference configuration data. Secondly, the auditing and reconciliation unit 310 is further configured to use the second configuration data as the first Underlay configuration data when the historical configuration data does not include the second configuration data and the current configuration data includes the second configuration data.
  • first data updating unit 330 it is also configured to obtain third difference configuration data according to the first Underlay configuration data and the second Underlay configuration data, and update the second Underlay configuration data according to the third difference configuration data , to obtain the updated second Underlay configuration data.
  • the first data updating unit 330 is further configured to delete the third configuration data from the second Underlay configuration data when the second Underlay configuration data includes the third configuration data and the third difference configuration data does not include the third configuration data;
  • the first data updating unit 330 is further configured to add the fourth configuration data to the second Underlay configuration data when the third difference configuration data includes the fourth configuration data and the second Underlay configuration data does not include the fourth configuration data.
  • the auditing and reconciliation unit 310 the first data acquisition unit 320 , the first data update unit 330 , the data repair unit 340 , the second data unit 310 and the second data unit in FIG. 10 may be correspondingly included.
  • one embodiment of the present application provides a data processing system including: a memory, a processor, and a computer program stored on the memory and executable on the processor.
  • the processor and memory may be connected by a bus or otherwise.
  • the data processing system in this embodiment may correspond to the data processing system in the system architecture platform in the embodiment shown in FIG. 1 , and may constitute a part of the system architecture platform in the embodiment shown in FIG. 1 .
  • both belong to the same inventive concept, so both have the same realization principle and beneficial effects, and will not be described in detail here.
  • the non-transitory software programs and instructions required to implement the data processing method of the above embodiment are stored in the memory, and when executed by the processor, the data processing method of the above embodiment is executed, for example, the method in FIG. 2 described above is executed Steps S100 to S400, method step S500 in FIG. 3, method step S600 in FIG. 4, method steps S710 to S720 in FIG. 5, method steps S810 to S820 in FIG. 6, method steps S910 to S920 in FIG. 7 .
  • an embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to execute the above-mentioned data processing method.
  • the above-mentioned data processing system embodiment can cause the above-mentioned processor to execute the data processing method in the above-mentioned embodiment, for example, execute the above-described method steps S100 to S400 in FIG. method steps S500 in FIG. 4 , method steps S600 in FIG. 4 , method steps S710 to S720 in FIG. 5 , method steps S810 to S820 in FIG. 6 , and method steps S910 to S920 in FIG. 7 .
  • the embodiments of the present application include: the embodiments of the present application can acquire the first Underlay configuration data and the second Underlay configuration data between the current control plane and the forwarding plane device, and compare the first Underlay configuration data and the second Underlay configuration data. Thus, the second Underlay configuration data is updated. Since the second Underlay configuration data is configuration data in the forwarding plane device that cannot be repaired by the control plane, this embodiment of the present application can remove the above-mentioned updated configuration data from the configuration data of the forwarding plane device. The second Underlay configuration data to obtain the target configuration data that satisfies the repair condition.
  • the embodiments of the present application can automatically identify the Underlay configuration data that does not need to be repaired in the current forwarding plane device, so that the updated information in the forwarding plane device will be automatically shielded when the control plane initiates repair.
  • the second Underlay configuration data therefore, the embodiment of the present application can not only improve the automation rate of network system environment operation and maintenance, but also improve the stability of the network system environment.
  • Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, magnetic disk storage or other magnetic storage devices, or may Any other medium used to store desired information and which can be accessed by a computer.
  • communication media typically include computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and can include any information delivery media, as is well known to those of ordinary skill in the art .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种数据处理方法、装置、系统和计算机可读存储介质,包括:获取控制面和转发面设备之间的第一差异配置数据,并根据第一差异配置数据得到第一Underlay配置数据(S100);获取第二Underlay配置数据,第二Underlay配置数据为转发面设备中不被控制面修复的配置数据(S200);根据第一Underlay配置数据对第二Underlay配置数据进行更新,得到更新后的第二Underlay配置数据(S300);从转发面设备的配置数据中剔除更新后的第二Underlay配置数据,以得到满足修复条件的目标配置数据(S400)。

Description

数据处理方法、装置、系统和计算机可读存储介质
相关申请的交叉引用
本申请基于申请号为202011266973.1、申请日为2020年11月13日的中国专利申请提出,并要求该中国专利申请的优先权,该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请实施例涉及但不限于数据处理技术领域,尤其涉及一种数据处理方法、装置、系统和计算机可读存储介质。
背景技术
当控制面和转发面设备的配置数据出现不一致的情况时,会导致流量转发不正常,对此,现有的解决办法是对控制面和转发面设备不一致的配置数据进行修复,而该解决办法会识别转发面设备的所有配置,但是不会区分转发面设备的Overlay(重叠)和Underlay(底层承载)配置数据,当控制面进行修复时如果对设备基础的Underlay配置数据进行修复则会导致转发面设备的基础配置被删除,从而导致设备瘫痪不可用。因此,该解决办法还需要通过人工识别转发面设备的Underlay配置数据,但是随着通信业务量的爆发式增加,网络设备的配置数据也越来越复杂、庞大,因此,通过人工来识别转发面设备的Underlay配置数据的方式越来越难以实现。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本申请实施例提供了一种数据处理方法、装置、系统和计算机可读存储介质。
第一方面,本申请实施例提供了一种数据处理方法,包括:获取控制面和转发面设备之间的第一差异配置数据,并根据所述第一差异配置数据得到第一Underlay配置数据;获取第二Underlay配置数据,所述第二Underlay配置数据为转发面设备中不被控制面修复的配置数据;根据所述第一Underlay配置数据对所述第二Underlay配置数据进行更新,得到更新后的第二Underlay配置数据;从转发面设备的配置数据中剔除所述更新后的第二Underlay配置数据,以得到满足修复条件的目标配置数据。
第二方面,本申请实施例还提供了一种数据处理装置,包括:审计对账单元,获取控制面和转发面设备之间的第一差异配置数据,并根据所述第一差异配置数据得到第一Underlay配置数据;第一数据获取单元,获取第二Underlay配置数据,所述第二Underlay配置数据为转发面设备中不被控制面修复的配置数据;第一数据更新单元,根据所述第一Underlay配置数据对所述第二Underlay配置数据进行更新,得到更新后的第二Underlay配置数据;数据修复单元,根据所述更新后的第二Underlay配置数据修复转发面设备中的目标配置数据,所述目标配置数据不包括所述更新后的第二Underlay配置数据。
第三方面,本申请实施例还提供了一种数据处理系统,包括:存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序,所述处理器执行所述计算机程序时实现如上述第一方面所述的数据处理方法。
第四方面,本申请实施例还提供了一种计算机可读存储介质,存储有计算机可执行指令,所述计算机可执行指令用于执行如上述第一方面所述的数据处理方法。
附图说明
附图用来提供对本申请技术方案的进一步理解,并且构成说明书的一部分,与本申请的实施例一起用于解释本申请的技术方案,并不构成对本申请技术方案的限制。
图1是本申请一个实施例提供的用于执行数据处理方法的系统架构平台的示意图;
图2是本申请一个实施例提供的数据处理方法的流程图;
图3是本申请一个实施例提供的获取第一差异配置数据的流程图;
图4是本申请一个实施例提供的根据第一差异配置数据得到第一Underlay配置数据的流程图;
图5是本申请一个实施例提供的从第一Underlay配置数据中过滤掉第三Underlay配置数据的流程图;
图6是本申请一个实施例提供的更新第三Underlay配置数据的流程图;
图7是本申请一个实施例提供的更新第二Underlay配置数据的流程图;
图8是本申请一个实施例提供的数据处理方法的流程框架图;
图9是本申请一个实施例提供的控制面和转发面设备配置审计对账、修复的实现装置的流程图;
图10是本申请一个实施例提供的数据处理装置的示意图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白,以下结合附图及实施例,对本申请进行进一步详细说明。应当理解,此处所描述的具体实施例仅用以解释本申请,并不用于限定本申请。
需要说明的是,虽然在装置示意图中进行了功能模块划分,在流程图中示出了逻辑顺序,但是在某些情况下,可以以不同于装置中的模块划分,或流程图中的顺序执行所示出或描述的步骤。说明书、权利要求书或上述附图中的术语“第一”、“第二”等是用于区别类似的对象,而不必用于描述特定的顺序或先后次序。
对于SDN(Software Defined Network,软件定义网络)框架,SDN作为控制面扮演大脑的角色来负责编排和转发策略的下发,通过集中控制的方式,网络管理员可以通过SDN的API(Application Programming Interface,应用程序编程接口)来编写定制程序,从而实现自动化的业务部署,很大程度地缩短了业务部署周期,使得业务能够满足按需的动态调整。
而在SDN网络架构应用过程中,常常会出现当业务数据在下发的过程中,控制面和转发面的管理网出现了连通性异常,转发面配置下发失败导致控制面和转发面的数据不一致,从而导致业务无法正常使用。另外,除了因为管理网的连通性导致的异常,转发面设备侧的交换机也会出现一些异常,在一些示例中,包括:交换机软件的故障、硬件的缺陷、遭受到的 恶意的攻击、人为的错误的配置等原因带来的配置数据异常。
当出现以上异常情况后,控制面和数据转发面设备的配置不一致,流量转发就会不正常,对此,相关的运维技术能够通过审计对账和修复来解决上述异常情况。在配置审计对账、修复的运维技术中,由于转发面设备正常运行都需要基础的网络配置,例如接口地址等,控制面和转发面进行审计对账、修复的时候会识别转发面设备的所有配置,但是不会区分转发面设备的Overlay和Underlay配置数据。控制面进行修复的时候如果对设备基础的Underlay配置进行修复则会导致转发面设备的基础配置被删除,导致设备瘫痪不可用。随着通信业务量的爆发式增加,在大型通信网络环境中往往有重量级的网络设备,网络设备的配置数据也越来越复杂、庞大,通过运维人员识别转发面设备的基础Underlay配置数据越来越不可行。
基于上述情况,本申请提供了一种数据处理方法、装置、系统和计算机可读存储介质,其中,数据处理方法包括如下步骤:获取控制面和转发面设备之间的第一差异配置数据,并根据第一差异配置数据得到第一Underlay配置数据;获取第二Underlay配置数据,第二Underlay配置数据为转发面设备中不被控制面修复的配置数据;根据第一Underlay配置数据对第二Underlay配置数据进行更新,得到更新后的第二Underlay配置数据;从转发面设备的配置数据中剔除更新后的第二Underlay配置数据,以得到满足修复条件的目标配置数据。根据本申请实施例的技术方案,本申请实施例能够获取当前控制面和转发面设备之间的第一Underlay配置数据以及第二Underlay配置数据,并将第一Underlay配置数据和第二Underlay配置数据进行对比处理从而实现第二Underlay配置数据的更新,由于第二Underlay配置数据为转发面设备中不会被控制面修复的配置数据,因此,本申请实施例能够从转发面设备的配置数据中剔除上述更新后的第二Underlay配置数据,以得到满足修复条件的目标配置数据。因此,本申请实施例能够自动识别出当前转发面设备中不需要被修复的Underlay配置数据,从而使得控制面发起修复时会自动屏蔽掉转发面设备中的更新后的第二Underlay配置数据,因此,本申请实施例不仅能够提高网络系统环境运维的自动化率,而且还能够提高网络系统环境的稳定性。
下面结合附图,对本申请实施例作进一步阐述。
如图1所示,图1是本申请一个实施例提供的用于数据处理方法的系统架构平台的示意图。
在图1的示例中,该系统架构平台包括数据处理系统100,其中,上述的数据处理系统100设置有处理器110和存储器120,其中,处理器110和存储器120可以通过总线或者其他方式连接,图1中以通过总线连接为例。
存储器120作为一种非暂态计算机可读存储介质,可用于存储非暂态软件程序以及非暂态性计算机可执行程序。此外,存储器120可以包括高速随机存取存储器,还可以包括非暂态存储器,例如至少一个磁盘存储器件、闪存器件、或其他非暂态固态存储器件。在一些实施方式中,存储器120可包括相对于处理器110远程设置的存储器120,这些远程存储器可以通过网络连接至该系统架构平台。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
本领域技术人员可以理解的是,该系统架构平台可以应用于3G通信网络系统、LTE通信网络系统、5G通信网络系统以及后续演进的移动通信网络系统等,本实施例对此并不作具体限定。
本领域技术人员可以理解的是,图1中示出的系统架构平台并不构成对本申请实施例的限定,可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置。
在图1所示的系统架构平台中,处理器110可以调用储存在存储器120中的数据处理程序,从而执行数据处理方法。
基于上述系统架构平台,下面提出本申请的数据处理方法的各个实施例。
如图2所示,图2是本申请一个实施例提供的数据处理方法的流程图,该方法包括但不限于有步骤S100、步骤S200、步骤S300和步骤S400。
步骤S100,获取控制面和转发面设备之间的第一差异配置数据,并根据第一差异配置数据得到第一Underlay配置数据;
步骤S200,获取第二Underlay配置数据,第二Underlay配置数据为转发面设备中不被控制面修复的配置数据;
步骤S300,根据第一Underlay配置数据对第二Underlay配置数据进行更新,得到更新后的第二Underlay配置数据;
步骤S400,从转发面设备的配置数据中剔除更新后的第二Underlay配置数据,以得到满足修复条件的目标配置数据。
关于本申请实施例的数据处理方法,可以应用在控制面初次纳管转发面并且在未进行配置下发的场景,也可以应用在控制面进行配置下发之后的场景,具体可参照如下分析:
在一实施例中,当控制面初次纳管转发面并且在未进行配置下发的情况下,控制面可以对转发面设备的配置数据进行审计对账从而能够得到控制面和转发面之间的第一差异配置数据,并对该第一差异配置数据进行过滤整合处理以得到与第一差异配置数据对应的第一Underlay配置数据;其次,由于控制面是初次纳管转发面并且未进行配置下发,因此,所获取到的第二Underlay配置数据为空;然后,将第一Underlay配置数据和第二Underlay配置数据进行对比,从而将第一Underlay配置数据全部添加至第二Underlay配置数据中,以得到更新后的第二Underlay配置数据,由于更新后的第二Underlay配置数据为转发面设备中更新后的不会被控制面修复的配置数据,因此,当控制面需要修复转发面设备中的配置数据时,会从转发面设备的配置数据中剔除更新后的第二Underlay配置数据,从而不会对更新后的第二Underlay配置数据进行配置修复,从而避免出现因修复而导致设备瘫痪不可用的情况。
需要说明的是,在控制面初次纳管转发面并且未进行配置下发的情况下,由于所获取到的第二Underlay配置数据为空,因此,上述的第一Underlay配置数据和更新后的第二Underlay配置数据是一致的。
在一实施例中,在控制面进行配置下发之后,由于SDN网络架构中会存在各种的问题导致控制面和转发面的配置数据不一致,在一些示例中,包括:控制面的管理网断链、交换机设备侧的软件缺陷、硬件故障、交换机侧遭受到的恶意攻击、人为的误配置等,从而可能会导致控制面和交换机的转发面的配置不一致,进而造成数据流量无法正常转发。因此,本申请实施例会在控制面进行配置下发之后要重新对历史所存储的第二Underlay配置数据进行更新,因此控制面会再次对转发面设备的配置数据进行审计对账,以得到控制面和转发面之间的第一差异配置数据,并对该第一差异配置数据进行过滤整合处理以得到与第一差异配置数据对应的第一Underlay配置数据;然后,本申请实施例会获取历史所存储的第二Underlay配置数据,将第一Underlay配置数据和第二Underlay配置数据进行对比,以得到更新后的 第二Underlay配置数据,由于更新后的第二Underlay配置数据为转发面设备中所更新后的不会被控制面修复的配置数据,因此,当控制面需要修复转发面设备中的配置数据时,会从转发面设备的配置数据中剔除更新后的第二Underlay配置数据,从而不会对更新后的第二Underlay配置数据进行配置修复,从而避免了因修复而导致设备瘫痪不可用。
根据本申请实施例的技术方案,本申请实施例能够自动识别出当前转发面设备中不需要被修复的Underlay配置数据,即更新后的第二Underlay配置数据,从而可以使得控制面发起修复时会自动屏蔽掉转发面设备中的更新后的第二Underlay配置数据,避免了因修复而导致设备瘫痪不可用,因此,本申请实施例不仅能够提高网络系统环境运维的自动化率,而且还能够提高网络系统环境的稳定性。
需要说明的是,由于控制面作为转发面的数据来源,因此修复转发面的配置数据需要以控制面的数据为准。
另外,如图3所示,图3是本申请一个实施例提供的数据处理方法的流程图,关于上述步骤S100,包括但不限于有步骤S500。
步骤S500,获取控制面下发给转发面设备的历史配置数据和转发面设备的当前配置数据,并根据历史配置数据和当前配置数据得到控制面和转发面设备之间的第一差异配置数据,并根据第一差异配置数据得到第一Underlay配置数据。
关于上述步骤S500,可以在控制面初次纳管转发面并且在未进行配置下发的情况下执行,也可以在控制面进行配置下发之后的情况下执行,具体如下所示:
在一实施例中,当控制面初次纳管转发面并且在未进行配置下发的情况下,控制面会对转发面设备的配置数据进行审计对账,从而获取到控制面下发给转发面设备的历史配置数据,由于控制面是初次纳管转发面并且未进行配置下发,因此,上述的历史配置数据为空;同时,控制面会获取转发面设备的当前配置数据;然后,控制面会对历史配置数据和当前配置数据进行审计对账,从而得到控制面和转发面设备之间的第一差异配置数据。
在一实施例中,在控制面进行配置下发之后,控制面会再次对转发面设备的配置数据进行审计对账,从而获取到控制面下发给转发面设备的历史配置数据,如果存在多次的历史配置数据,则选择最后一次所配置下发的数据。同时,控制面会获取转发面设备的当前配置数据;然后,控制面会对历史配置数据和当前配置数据进行审计对账,从而得到控制面和转发面设备之间的第一差异配置数据。
另外,如图4所示,图4是本申请一个实施例提供的数据处理方法的流程图,在上述步骤S500中的根据第一差异配置数据得到第一Underlay配置数据,包括但不限于有步骤S600。
步骤S600,当历史配置数据没有包括第二配置数据并且当前配置数据包括第二配置数据,将第二配置数据作为第一Underlay配置数据。
在一实施例中,当控制面对转发面设备的配置数据进行审计对账之后,会得到第一差异配置数据,即控制面下发给转发面设备的历史配置数据和转发面设备的当前配置数据之间的差异配置数据,接着本申请实施例会对第一差异配置数据进行过滤整合处理以得到与第一差异配置数据对应的第一Underlay配置数据,具体的过滤整合处理可以参照如下四种情况:
第一种过滤整合处理情况:以控制面的配置数据作为标准,以实例作为粒度,控制面向转发面下发的配置数据,不会出现控制面没有某个实例而转发面有的情况。在一些示例中,不会出现控制面没有vpls实例zenic_123的数据,而转发面设备有zenic_123这个vpls实 例的配置。
第二种过滤整合处理情况:以控制面的配置数据作为标准,以实例作为粒度,当控制面和转发面都有某个实例数据,并且该实例数据是控制面下发给转发面的配置数据,但是当该实例数据在控制面配置数据中对应的属性值与在转发面配置数据中对应的属性值不一致时,则本申请实施例会将这个实例数据过滤掉而不加入至第一Underlay配置数据。在一些示例中,控制面和转发面配置数据都有vpls实例zenic_123数据,但是控制面vpls实例zenic_123的属性vni-label值为100,而转发面vpls实例zenic_123的属性vni-label值为200,则vpls实例zenic_123会被过滤掉而不加入至第一Underlay配置数据中。
第三种过滤整合处理情况:以控制面的配置数据作为标准,以实例作为粒度,当出现控制面有某个实例数据,而转发面没有这个实例数据时,则这个实例数据会被过滤掉而不加入至第一Underlay配置数据。在一些示例中,控制面配置数据有vpls实例zenic_123,而转发面配置数据没有vpls实例zenic_123,则vpls实例zenic_123会被过滤掉而不加入至第一Underlay配置数据中。
第四种过滤整合处理情况:以控制面的配置数据作为标准,以实例作为粒度,当出现控制面没有某个实例数据,而转发面有这个实例数据时,则这个实例数据会被加入到第一Underlay配置数据中。在一些示例中,控制面配置数据没有vpls实例zenic_123,而转发面配置数据有vpls实例zenic_123,则vpls实例zenic_123需要加入至第一Underlay配置数据中。
因此,基于上述四种过滤整合处理情况,其中只有第四种过滤整合处理情况才不会将实例数据过滤,而是会将实例数据加入至第一Underlay配置数据中。因此,当存在第四种过滤整合处理情况时,如步骤S600所示,当历史配置数据没有包括第二配置数据并且当前配置数据包括第二配置数据,将第二配置数据作为第一Underlay配置数据。
另外,如图5所示,图5是本申请一个实施例提供的数据处理方法的流程图,在上述步骤S300之前,该方法还包括但不限于有步骤S710和步骤S720。
步骤S710,获取第三Underlay配置数据,第三Underlay配置数据为转发面设备接收到控制面的删除任务之后删除失败的配置数据;
步骤S720,从第一Underlay配置数据中删除与第三Underlay配置数据一致的配置数据。
在一实施例中,当得到第一Underlay配置数据之后,还需要从第一Underlay配置数据中过滤掉控制面删除下发给转发面由于异常出现残留的不一致的配置数据,因此,本申请实施例会获取第三Underlay配置数据,并从第一Underlay配置数据中删除与第三Underlay配置数据一致的配置数据,接着才继续执行步骤S300。
值得注意的是,关于上述的第三Underlay配置数据,是转发面设备接收到控制面的删除任务之后删除失败的配置数据。控制面业务删除细化是对转发面设备的实例或者属性按照一定的依赖关系进行删除,本申请实施例不仅会在删除控制面业务删除流程上进行可靠性的保证,同时也会对删除结果进行检查。其中,控制面业务数据删除任务下发的情况,可以分为如下三种:
第一种业务数据删除任务下发情况:控制面业务数据删除任务下发失败,控制面业务数据保持不删除,转发面设备配置数据保持未删除。
第二种业务数据删除任务下发情况:控制面业务数据删除任务下发成功,转发面设备某 个实例或者属性数据删除失败,转发面设备返回报错原因并上送控制面。控制面收到报错发出告警,告警包括具体的转发面设备删除报错的具体原因。控制面业务数据删除,并将在转发面设备删除失败的实例数据加入到第三Underlay配置数据中。
第三种业务数据删除任务下发情况:控制面业务数据删除任务下发成功,控制面检测到和转发面出现连通性问题,控制面下发删除任务南向队列会进行规定次数的重传,到上限的重传失败,则记录并告警,这种失败可以采用配置审计和修复的手段来重新管理下发至设备侧的配置。
因此,基于上述三种业务数据删除任务下发情况,其中只有第二种业务数据删除任务下发情况才会将实例数据加入至第三Underlay配置数据中。因此,当存在第二种业务数据删除任务下发情况时,本申请实施例在得到第一Underlay配置数据之后,还需要获取预存的第三Underlay配置数据,并且从第一Underlay配置数据中删除与预存的第三Underlay配置数据一致的配置数据。
需要说明的是,第三Underlay配置数据是控制面下发业务数据删除时转发面进行相关配置数据删除失败,后续采用配置审计和修复的手段也无法对此类残留配置数据进行清除,因此,控制面将执行删除失败的配置数据保存到第三Underlay配置数据中。
可以理解的是,转发面设备首次接入时第三Underlay配置数据为空。
另外,如图6所示,图6是本申请一个实施例提供的数据处理方法的流程图,该方法还包括但不限于有步骤S810和步骤S820。
步骤S810,根据第一Underlay配置数据和第三Underlay配置数据得到第二差异配置数据;
步骤S820,根据第二差异配置数据对第三Underlay配置数据进行更新。
在一实施例中,本申请实施例还会对第一Underlay配置数据和预存的第三Underlay配置数据进行审计对账之后更新第三Underlay配置数据。
需要说明的是,第三Underlay配置数据的更新方式具体为:预存的第三Underlay配置数据有某个配置数据但是第一Underlay配置数据没有该配置数据,则预存的第三Underlay配置数据中的该配置数据将会被删除。在一些示例中,当第三Underlay配置数据包括第一配置数据并且第二差异配置数据没有包括第一配置数据,则从第三Underlay配置数据中删除第一配置数据。
另外,如图7所示,图7是本申请一个实施例提供的数据处理方法的流程图,关于上述步骤S300,包括但不限于有步骤S910和步骤S920。
步骤S910,根据第一Underlay配置数据和第二Underlay配置数据得到第三差异配置数据;
步骤S920,根据第三差异配置数据对第二Underlay配置数据进行更新,得到更新后的第二Underlay配置数据。
在一实施例中,当从第一Underlay配置数据中删除与第三Underlay配置数据一致的配置数据之后,本申请实施例会将删除操作后的第一Underlay配置数据和第二Underlay配置数据进行审计对账,得到第三差异配置数据,再根据第三差异配置数据对第二Underlay配置数据进行更新,得到更新后的第二Underlay配置数据。
值得注意的是,上述第二Underlay配置数据的更新方式包括如下两种方式:
第一种更新方式:当第二Underlay配置数据包括第三配置数据并且第三差异配置数据没有包括第三配置数据,从第二Underlay配置数据中删除第三配置数据;
第二种更新方式:当第三差异配置数据包括第四配置数据并且第二Underlay配置数据没有包括第四配置数据,增加第四配置数据至第二Underlay配置数据。
可以理解的是,关于上述的第一配置数据、第二配置数据第三配置数据和第四配置数据,可以以实例为粒度。
根据上述的数据处理方法,如图8和图9所示,图8是本申请一个实施例提供的数据处理方法的流程框架图,图9是本申请一个实施例提供的控制面和转发面设备配置审计对账、修复的实现装置的流程图。
在一实施例中,当控制面初次纳管转发面并且未进行配置下发时,控制面可以对转发面设备220的配置数据进行首次审计对账,从而得到控制面和转发面之间的初始差异配置数据,并根据初始差异配置数据得到初始的第二Underlay配置数据,该初始的第二Underlay配置数据为不会进行配置修复的初始保留Underlay配置数据,同时本申请实施例还会将该初始的第二Underlay配置数据存入至数据库230。接着,当在控制面进行配置下发之后,由于SDN网络架构中会存在各种的问题导致控制面和转发面的配置数据不一致,因此控制面会对转发面设备220的配置数据进行再次审计对账,得到当前的控制面和转发面之间的第一差异配置数据,并对该第一差异配置数据进行数据对账处理;其中,数据对账处理包括对该第一差异配置数据进行过滤整合处理,以得到第一Underlay配置数据,再从第一Underlay配置数据中删除与第三Underlay配置数据一致的配置数据,进而得到更新后的第一Underlay配置数据;另外,数据对账处理还包括根据过滤整合处理后的第一Underlay配置数据和第三Underlay配置数据来对第三Underlay配置数据进行更新,进而得到更新后的第三Underlay配置数据;接着,在上述数据对账处理之后,本申请实施例会将更新后的第一Underlay配置数据和初始的第二Underlay配置数据进行审计对账,从而对初始的第二Underlay配置数据进行更新,得到更新后的第二Underlay配置数据。
关于图9中的发送模块210,被设置成向转发面设备220下发配置数据;具体地,发送模块210被设置成将业务数据存入数据库230;接着适配层将业务数据分解为设备维度的配置数据;最后会将分解的业务数据下发给转发面设备220。
对于上述数据处理方法,本申请实施例提供了一种应用实例进行说明。在一些示例中,当北向网络编排器编排的业务下发下来,控制面会去编排下发业务配置,一条控制面的业务编排数据会被拆分为设备侧的N条的配置下发给设备,控制面以业务数据下发的设备按需记录入库。在控制面下发业务数据的过程中,当控制面和转发面管理网络连接异常,控制面会尝试重传下发业务配置,在达到重传次数上限之后业务配置下发失败,造成控制面和转发面业务数据不一致,此时就需要使用配置审计对账、修复的方法来保证控制面和转发面的数据一致,要进行修复,需要在审计对账时先获取转发面设备当前的第一Underlay配置数据和预存的第二Underlay配置数据,然后审核更新得到转发面设备最新的第二Underlay配置数据。
另外,关于控制面的执行步骤,可以包括:控制面网管获取到转发面设备配置;然后控制面将设备返回的配置数据转换成网管的数据结构,并存入操作库中;接着控制面网管将控制面设备存库数据和从设备层面获取操作库数据转换成xml并进行实例和属性的逐一比对,网管对比不一致的部分标红显示;接着控制面网管上标红显示的差异配置数据在设备首次接 入进行审计对账时,可以全部加入到设备配置数据的初始第二Underlay配置数据中。加入初始第二Underlay配置数据之后,控制器网管不再显示不可修复Underlay配置数据中的差异配置数据;接着控制面网管上在设备进行审计对账之后选择一个或者多个设备进行审核得到设备和控制面最新的第一Underlay配置数据和第二Underlay配置数据差异;数据审核之后选择更新第二Underlay配置数据,控制面不同设备的第二Underlay配置数据更新;在第二Underlay配置数据更新之后,控制器网管不再显示不可修复Underlay配置数据中的差异配置数据;最后,修复配置结果会返回给网管,修复失败有告警通知和具体原因。
可以理解的是,配置审计是一个重要的巡检工具,除了修复控制面和转发面的连通性异常产生的数据不一致的问题外,也可以通过本申请实施例,网管配置配置审计的定时功能,可以巡检转发面的配置是否异常,转发面设备是否出现异常,如:硬件损坏、软件故障、恶意攻击、人为的错误配置,并可以及时进行修复。
另外,可以理解的是,本申请实施例的数据处理方法,除了应用于SDN网络框架,也可以应用于其他的配置下发的领域。
根据本申请实施例的技术方案,能够快速检查转发面设备配置是否正确以及设备状态是否正常;快速了解控制面和转发面数据配置情况;提供多种自定义的方式快速对转发面设备差异配置数据进行修复;提高网络系统环境的稳定性;提高网络系统环境运维的自动化率;快速高效的过滤出转发面设备的Underlay配置数据;解决不同业务配置数据修复时有依赖关系的问题。
另外,本申请实施例的技术方案可以和定时框架结合,做到网络系统定时巡检,自动定时修复系统异常配置;也可以和控制面下发配置数据结合,配置审计对账显示配置数据下发状态;还可以和控制面修复功能结合,可以避免对转发面设备Underlay配置进行操作,导致设备瘫痪。
基于上述数据处理方法,下面提出本申请的数据处理装置的各个实施例。
如图10所示,图10是本申请一个实施例提供的数据处理装置300的示意图,该数据处理装置300包括但不限于有审计对账单元310、第一数据获取单元320、第一数据更新单元330和数据修复单元340。
具体地,审计对账单元310被设置成获取控制面和转发面设备之间的第一差异配置数据,并根据第一差异配置数据得到第一Underlay配置数据;第一数据获取单元320被设置成获取第二Underlay配置数据,第二Underlay配置数据为转发面设备中不被控制面修复的配置数据;第一数据更新单元330被设置成根据第一Underlay配置数据对第二Underlay配置数据进行更新,得到更新后的第二Underlay配置数据;数据修复单元340被设置成根据更新后的第二Underlay配置数据修复转发面设备中的目标配置数据,目标配置数据不包括更新后的第二Underlay配置数据。
需要说明的是,上述单元的具体工作原理可以参考图2所示的方法步骤的描述,为了叙述简便,在此不再赘述。
另外,参照图10所示,在一个实施例中,图10所示的数据处理装置300还包括但不限于有第二数据获取单元350和数据删除单元360。
具体地,第二数据获取单元350被设置成获取第三Underlay配置数据,第三Underlay配置数据为转发面设备接收到控制面的删除任务之后删除失败的配置数据;数据删除单元360 被设置成从第一Underlay配置数据中删除与第三Underlay配置数据一致的配置数据。
需要说明的是,上述单元的具体工作原理可以参考图5所示的方法步骤的描述,为了叙述简便,在此不再赘述。
另外,参照图10所示,在一个实施例中,图10所示的数据处理装置300还包括但不限于有第二数据更新单元370。
具体地,第二数据更新单元370被设置成根据第一Underlay配置数据和第三Underlay配置数据得到第二差异配置数据,并根据第二差异配置数据对第三Underlay配置数据进行更新。
可以理解的是,上述的第二数据更新单元370被设置成当第三Underlay配置数据包括第一配置数据并且第二差异配置数据没有包括第一配置数据,从第三Underlay配置数据中删除第一配置数据。
需要说明的是,上述单元的具体工作原理可以参考图6所示的方法步骤的描述,为了叙述简便,在此不再赘述。
另外,关于上述的审计对账单元310,还被设置成获取控制面下发给转发面设备的历史配置数据和转发面设备的当前配置数据,并根据历史配置数据和当前配置数据得到控制面和转发面设备之间的第一差异配置数据,并根据第一差异配置数据得到第一Underlay配置数据。其次,审计对账单元310还被设置成当历史配置数据没有包括第二配置数据并且当前配置数据包括第二配置数据,将第二配置数据作为第一Underlay配置数据。
另外,关于上述的第一数据更新单元330,还被设置成根据第一Underlay配置数据和第二Underlay配置数据得到第三差异配置数据,并根据第三差异配置数据对第二Underlay配置数据进行更新,得到更新后的第二Underlay配置数据。其次,第一数据更新单元330还被设置成当第二Underlay配置数据包括第三配置数据并且第三差异配置数据没有包括第三配置数据,从第二Underlay配置数据中删除第三配置数据;另外,第一数据更新单元330还被设置成当第三差异配置数据包括第四配置数据并且第二Underlay配置数据没有包括第四配置数据,增加第四配置数据至第二Underlay配置数据。
需要说明的是,关于图9中的处理模块240,可以对应包括有图10中的审计对账单元310、第一数据获取单元320、第一数据更新单元330、数据修复单元340、第二数据获取单元350、数据删除单元360和第二数据更新单元370,或者能够实现图10中的审计对账单元310、第一数据获取单元320、第一数据更新单元330、数据修复单元340、第二数据获取单元350、数据删除单元360和第二数据更新单元370所具备的功能。
基于上述数据处理方法,下面分别提出本申请的数据处理系统和计算机可读存储介质的各个实施例。
另外,本申请的一个实施例提供了一种数据处理系统,该数据处理系统包括:存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序。
处理器和存储器可以通过总线或者其他方式连接。
需要说明的是,本实施例中的数据处理系统,可以对应为如图1所示实施例中的系统架构平台中的数据处理系统,能够构成图1所示实施例中的系统架构平台的一部分,两者属于相同的发明构思,因此两者具有相同的实现原理以及有益效果,此处不再详述。
实现上述实施例的数据处理方法所需的非暂态软件程序以及指令存储在存储器中,当被 处理器执行时,执行上述实施例的数据处理方法,例如,执行以上描述的图2中的方法步骤S100至S400、图3中的方法步骤S500、图4中的方法步骤S600、图5中的方法步骤S710至S720、图6中的方法步骤S810至S820、图7中的方法步骤S910至S920。
以上所描述的装置实施例仅仅是示意性的,其中作为分离部件说明的单元可以是或者也可以不是物理上分开的,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
此外,本申请的一个实施例还提供了一种计算机可读存储介质,该计算机可读存储介质存储有计算机可执行指令,计算机可执行指令用于执行上述的数据处理方法。例如,被上述数据处理系统实施例中的一个处理器执行,可使得上述处理器执行上述实施例中的数据处理方法,例如,执行以上描述的图2中的方法步骤S100至S400、图3中的方法步骤S500、图4中的方法步骤S600、图5中的方法步骤S710至S720、图6中的方法步骤S810至S820、图7中的方法步骤S910至S920。
本申请实施例包括:本申请实施例能够获取当前控制面和转发面设备之间的第一Underlay配置数据以及第二Underlay配置数据,并将第一Underlay配置数据和第二Underlay配置数据进行对比处理从而实现第二Underlay配置数据的更新,由于第二Underlay配置数据为转发面设备中不会被控制面修复的配置数据,因此,本申请实施例能够从转发面设备的配置数据中剔除上述更新后的第二Underlay配置数据,以得到满足修复条件的目标配置数据。根据本申请实施例的技术方案,本申请实施例能够自动识别出当前转发面设备中不需要被修复的Underlay配置数据,从而使得控制面发起修复时会自动屏蔽掉转发面设备中的更新后的第二Underlay配置数据,因此,本申请实施例不仅能够提高网络系统环境运维的自动化率,而且还能够提高网络系统环境的稳定性。
本领域普通技术人员可以理解,上文中所公开方法中的全部或某些步骤、系统可以被实施为软件、固件、硬件及其适当的组合。某些物理组件或所有物理组件可以被实施为由处理器,如中央处理器、数字信号处理器或微处理器执行的软件,或者被实施为硬件,或者被实施为集成电路,如专用集成电路。这样的软件可以分布在计算机可读介质上,计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的,术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外,本领域普通技术人员公知的是,通信介质通常包括计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据,并且可包括任何信息递送介质。
以上是对本申请的一些实施进行了具体说明,但本申请并不局限于上述实施方式,熟悉本领域的技术人员在不违背本申请范围的共享条件下还可作出种种等同的变形或替换,这些等同的变形或替换均包括在本申请权利要求所限定的范围内。

Claims (11)

  1. 一种数据处理方法,包括:
    获取控制面和转发面设备之间的第一差异配置数据,并根据所述第一差异配置数据得到第一底层承载Underlay配置数据;
    获取第二Underlay配置数据,所述第二Underlay配置数据为转发面设备中不被控制面修复的配置数据;
    根据所述第一Underlay配置数据对所述第二Underlay配置数据进行更新,得到更新后的第二Underlay配置数据;
    从转发面设备的配置数据中剔除所述更新后的第二Underlay配置数据,以得到满足修复条件的目标配置数据。
  2. 根据权利要求1所述的方法,其中,在所述根据所述第一Underlay配置数据对所述第二Underlay配置数据进行更新之前,所述方法还包括:
    获取第三Underlay配置数据,所述第三Underlay配置数据为转发面设备接收到控制面的删除任务之后删除失败的配置数据;
    从所述第一Underlay配置数据中删除与所述第三Underlay配置数据一致的配置数据。
  3. 根据权利要求2所述的方法,其中,还包括:
    根据所述第一Underlay配置数据和所述第三Underlay配置数据得到第二差异配置数据;
    根据所述第二差异配置数据对所述第三Underlay配置数据进行更新。
  4. 根据权利要求3所述的方法,其中,所述根据所述第二差异配置数据对所述第三Underlay配置数据进行更新,包括:
    当所述第三Underlay配置数据包括第一配置数据并且所述第二差异配置数据没有包括所述第一配置数据,从所述第三Underlay配置数据中删除所述第一配置数据。
  5. 根据权利要求1所述的方法,其中,所述获取控制面和转发面设备之间的第一差异配置数据,并根据所述第一差异配置数据得到第一Underlay配置数据,包括:
    获取控制面下发给转发面设备的历史配置数据和转发面设备的当前配置数据,并根据所述历史配置数据和所述当前配置数据得到控制面和转发面设备之间的第一差异配置数据,并根据所述第一差异配置数据得到第一Underlay配置数据。
  6. 根据权利要求5所述的方法,其中,所述根据所述第一差异配置数据得到第一Underlay配置数据,包括:
    当所述历史配置数据没有包括第二配置数据并且所述当前配置数据包括所述第二配置数据,将所述第二配置数据作为第一Underlay配置数据。
  7. 根据权利要求1所述的方法,其中,所述根据所述第一Underlay配置数据对所述第二Underlay配置数据进行更新,得到更新后的第二Underlay配置数据,包括:
    根据所述第一Underlay配置数据和所述第二Underlay配置数据得到第三差异配置数据;
    根据所述第三差异配置数据对所述第二Underlay配置数据进行更新,得到更新后的第二Underlay配置数据。
  8. 根据权利要求7所述的方法,其中,所述根据所述第三差异配置数据对所述第二Underlay配置数据进行更新,包括如下至少之一:
    当所述第二Underlay配置数据包括第三配置数据并且所述第三差异配置数据没有包括所述第三配置数据,从所述第二Underlay配置数据中删除所述第三配置数据;
    当所述第三差异配置数据包括第四配置数据并且所述第二Underlay配置数据没有包括所述第四配置数据,增加所述第四配置数据至所述第二Underlay配置数据。
  9. 一种数据处理装置,包括:
    审计对账单元,被设置成获取控制面和转发面设备之间的第一差异配置数据,并根据所述第一差异配置数据得到第一Underlay配置数据;
    第一数据获取单元,被设置成获取第二Underlay配置数据,所述第二Underlay配置数据为转发面设备中不被控制面修复的配置数据;
    第一数据更新单元,被设置成根据所述第一Underlay配置数据对所述第二Underlay配置数据进行更新,得到更新后的第二Underlay配置数据;
    数据修复单元,被设置成根据所述更新后的第二Underlay配置数据修复转发面设备中的目标配置数据,所述目标配置数据不包括所述更新后的第二Underlay配置数据。
  10. 一种数据处理系统,包括:存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序,其中,所述处理器执行所述计算机程序时实现如权利要求1至8中任意一项所述的数据处理方法。
  11. 一种计算机可读存储介质,存储有计算机可执行指令,其中,所述计算机可执行指令用于执行如权利要求1至8中任意一项所述的数据处理方法。
PCT/CN2021/130483 2020-11-13 2021-11-13 数据处理方法、装置、系统和计算机可读存储介质 WO2022100719A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011266973.1A CN114500276A (zh) 2020-11-13 2020-11-13 数据处理方法、装置、系统和计算机可读存储介质
CN202011266973.1 2020-11-13

Publications (1)

Publication Number Publication Date
WO2022100719A1 true WO2022100719A1 (zh) 2022-05-19

Family

ID=81491397

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/130483 WO2022100719A1 (zh) 2020-11-13 2021-11-13 数据处理方法、装置、系统和计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN114500276A (zh)
WO (1) WO2022100719A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106330477A (zh) * 2015-06-16 2017-01-11 中兴通讯股份有限公司 一种以太网业务配置方法、装置及网管
CN106992873A (zh) * 2016-01-21 2017-07-28 中兴通讯股份有限公司 保护组处理方法和装置
CN107222347A (zh) * 2017-06-09 2017-09-29 烽火通信科技股份有限公司 一种基于ptn设备的配置反刷方法
CN107360043A (zh) * 2017-08-25 2017-11-17 中国联合网络通信集团有限公司 一种在sdn中更改转发设备配置信息的方法及装置

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2015202657B2 (en) * 2011-01-27 2016-02-04 Security First Corp. Systems and Methods for Securing Data
CN103906131A (zh) * 2012-12-25 2014-07-02 华为技术有限公司 一种数据传输系统、设备及方法
KR101527786B1 (ko) * 2013-12-31 2015-06-09 쿨클라우드(주) 하이브리드 sdn 네트워크 관리 방법
CN105359483A (zh) * 2014-05-30 2016-02-24 华为技术有限公司 一种网络配置方法、装置及系统
CN104836688B (zh) * 2015-05-12 2018-11-02 深圳市泰信通信息技术有限公司 网络装置及其虚拟配置底层设备的方法
CN107241454B (zh) * 2016-03-29 2019-08-16 中兴通讯股份有限公司 一种实现地址管理的方法、装置、aaa服务器及sdn控制器
CN107733670B (zh) * 2016-08-11 2020-05-12 新华三技术有限公司 一种转发策略配置方法和装置
EP3487215B1 (en) * 2016-08-24 2021-05-12 Huawei Technologies Co., Ltd. Policy control method and network element
CN106130802B (zh) * 2016-08-30 2019-07-09 新华三技术有限公司 一种配置平滑方法及装置
CN106878061B (zh) * 2017-01-12 2019-08-13 烽火通信科技股份有限公司 一种实现数据通信设备配置同步的方法及装置
CN108449160A (zh) * 2017-02-16 2018-08-24 中兴通讯股份有限公司 报文发送方法及装置
CN110196780B (zh) * 2018-03-23 2020-06-23 腾讯科技(深圳)有限公司 确定服务器状态的方法、装置、存储介质和电子装置
CN110535771A (zh) * 2018-05-24 2019-12-03 中兴通讯股份有限公司 一种数据转发方法、网络设备和计算机可读存储介质
CN111385173B (zh) * 2018-12-28 2023-08-25 中兴通讯股份有限公司 一种报文处理方法、装置、控制面设备和计算机存储介质
CN110166299B (zh) * 2019-05-24 2022-05-10 新华三技术有限公司 Sdn控制器配置恢复方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106330477A (zh) * 2015-06-16 2017-01-11 中兴通讯股份有限公司 一种以太网业务配置方法、装置及网管
CN106992873A (zh) * 2016-01-21 2017-07-28 中兴通讯股份有限公司 保护组处理方法和装置
CN107222347A (zh) * 2017-06-09 2017-09-29 烽火通信科技股份有限公司 一种基于ptn设备的配置反刷方法
CN107360043A (zh) * 2017-08-25 2017-11-17 中国联合网络通信集团有限公司 一种在sdn中更改转发设备配置信息的方法及装置

Also Published As

Publication number Publication date
CN114500276A (zh) 2022-05-13

Similar Documents

Publication Publication Date Title
US10600028B2 (en) Automated topology change detection and policy based provisioning and remediation in information technology systems
US9712385B2 (en) Managing configurations of distributed devices
US9954747B2 (en) Systems and methods of specifying service level criteria
CN110088744B (zh) 一种数据库维护方法及其系统
CN105117263B (zh) 一种unix环境软件系统升级方法
CN111708560A (zh) 数据库高可用管理系统的自动化部署方法及装置
CN103200021A (zh) 网管系统、客户端、服务端及实现批量配置数据的方法
CN110545207B (zh) 一种同步自动化的智能dns系统及配置方法
JP2018160186A (ja) 監視プログラム、監視方法および監視装置
CN110290002B (zh) 一种更新方法、终端及电子设备
WO2022100719A1 (zh) 数据处理方法、装置、系统和计算机可读存储介质
CN117176943A (zh) 基于录像完整率与存储完整率的运维方法、系统、设备
CN110852571A (zh) 加盟商的房源管理方法、计算机可读存储介质及服务器
CN105787135A (zh) 一种用于数据库日志备份的方法与设备
CN110474800B (zh) 一种维护传输综合网管系统资源数据稳定性的方法
CN110659161B (zh) 一种基于Docker的备份数据有效性验证方法及系统
CN114691395A (zh) 一种故障处理方法、装置、电子设备及存储介质
CN108197147B (zh) 号卡数据库运维方法及装置
CN109408485B (zh) 一种分布式锁实现方法和系统
CN117075942A (zh) 基于DaemonSet控制器的节点Pod管理方法及系统
CN104598158B (zh) 系统事件处理系统及方法
CN112532660A (zh) 一种数据同步的方法、装置和网络管理系统
CN116974703B (zh) 一种kubernetes应用资源管理方法及系统
CN110471992B (zh) 一种库位信息同步方法、库位信息同步装置及服务器
CN104541478A (zh) 被管理对象版本识别

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21891239

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 18/10/2023)