WO2022156354A1

WO2022156354A1 - Version configuration method, apparatus, device, system, and storage medium

Info

Publication number: WO2022156354A1
Application number: PCT/CN2021/133217
Authority: WO
Inventors: 陈宁涛
Original assignee: 中兴通讯股份有限公司
Priority date: 2021-01-21
Filing date: 2021-11-25
Publication date: 2022-07-28
Also published as: CN112399452B; CN112399452A

Abstract

Embodiments of the present application relate to the communication field and disclose a version configuration method, an apparatus, a device, a system, and a storage medium. The version configuration method of the present application comprises: converting a user request into a corresponding service type identification code according to a pre-defined service type set by means of utilizing an orchestrator; then generating a first communication protocol to communicate with a controller according to an orchestrator identification code identifying the orchestrator itself, a controller identification code identifying the controller, and a determined service type identification code; and sending a configuration command to the controller on the basis of the generated first communication protocol, thereby allowing the controller, upon receiving the configuration command sent by the orchestrator, to be able to control a network element device to be configured to autonomously acquire corresponding configuration information from a configuration information management center and perform version configuration.

Description

Version configuration method, device, device, system and storage medium

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is based on the Chinese patent application with the application number "202110079406.3" and the application date is January 21, 2021, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby incorporated by reference. Application.

technical field

The embodiments of the present application relate to the field of communications, and in particular, to a version configuration method, apparatus, device, system, and storage medium.

Background technique

With the widespread application of 5G, higher and higher requirements are placed on the bearer network. In addition to the requirements for large bandwidth, large connections, and low latency, operators have put forward requirements for more refinement, intelligence, and automation. In order to meet these requirements, various network element devices in the bearer network, such as routers, switches, and transmission nodes involved in the optical transport network (OTN), need to be continuously updated according to user needs.

However, the current version configuration when updating the version of the network element device, because the configuration information of different versions is pre-stored locally in the network element device, which is limited by the local storage space, so that more versions cannot be stored. configuration information. Meanwhile, the version configuration currently performed when the version update is performed on the network element device requires manual intervention to select appropriate configuration information from the local storage space for version configuration, which seriously affects the configuration efficiency.

SUMMARY OF THE INVENTION

An embodiment of the present application provides a version configuration method, which is applied to an orchestrator in a version configuration system, where the version configuration system further includes a controller, a configuration information management center, and a network element device to be configured, and the version configuration method includes :

receiving user requirements, and determining a service type identification code corresponding to the user requirement according to a predefined service type set, where the service type set includes the corresponding relationship between each user requirement and each service type identification code;

obtain the identifier of the orchestrator and the identifier of the controller of the controller;

generating a first communication protocol for communicating with the controller according to the orchestrator identification code, the controller identification code and the service type identification code;

Based on the first communication protocol, a configuration command is delivered to the controller for the controller to control the to-be-configured network element device to obtain configuration information from the configuration information management center to perform version configuration.

Embodiments of the present application further provide a version configuration method, which is applied to a controller in a version configuration system, where the version configuration system further includes an orchestrator, a configuration information management center, and a network element device to be configured, and the version configuration method includes :

receiving a configuration command issued by the scheduler through a first communication protocol, where the first communication protocol carries a service type identification code corresponding to a user requirement;

Extract the service type identification code from the first communication protocol, and determine the version identification code of the configuration information required for version configuration of the to-be-configured network element device according to the service type identification code;

Obtain the controller identification code and the configuration information management center identification code of the configuration information management center;

generating a second communication protocol for communicating with the configuration information management center according to the controller identification code, the configuration information management center identification code and the version identification code;

Based on the second communication protocol, a configuration information search command is issued to the configuration information management center for the configuration information management center to determine whether configuration information matching the version identifier is stored.

An embodiment of the present application further provides a version configuration method, which is applied to a configuration information management center in a version configuration system, where the version configuration system further includes an orchestrator, a controller, and a network element device to be configured, and the version configuration method includes :

receiving a configuration information search command issued by the controller through a second communication protocol, where the second communication protocol carries a version identification code of configuration information required for version configuration of the to-be-configured network element device;

Extract the version identification code from the second communication protocol, and traverse the locally stored configuration information according to the version identification code;

If the configuration information matching the version identification code is traversed, the configuration information management center stores the configuration information matching the version identification code as a search result;

If the configuration information matching the version identification code is not traversed, the configuration information management center that does not store the configuration information matching the version identification code is used as the search result;

Based on the second communication protocol, the search result is fed back to the controller, so that the controller can respond to the orchestrator for a configuration failure, or control the to-be-configured network element device to manage from the configuration information The configuration information matching the version identification code is obtained in the center for version configuration.

Embodiments of the present application further provide a version configuration method, which is applied to a network element device to be configured in a version configuration system, where the version configuration system further includes an orchestrator, a controller, and a configuration information management center, and the version configuration method includes :

receiving a configuration command issued by the controller through a third communication protocol, where the third communication protocol carries a version identification code of configuration information required for version configuration;

extracting the version identifier from the third communication protocol;

Obtain the configuration information management center identification code of the configuration information management center that stores the configuration information matching the version identification code;

generating a fourth communication protocol for communicating with the configuration information management center according to the configuration information management center identification code and the version identification code;

Based on the fourth communication protocol, issue a configuration information acquisition command to the configuration information management center for the configuration information management center to feed back configuration information matching the version identifier based on the fourth communication protocol;

receiving the configuration information that matches the version identification code fed back by the configuration information management center through the fourth communication protocol;

The version configuration is performed according to the configuration information.

The embodiment of the present application also provides a version configuration device, including:

a determining module, configured to receive user requirements, and determine a service type identification code corresponding to the user requirement according to a predefined service type set, where the service type set includes the corresponding relationship between each user requirement and each service type identification code;

an acquisition module, used to acquire the identifier of the scheduler and the identifier of the controller of the controller;

a generating module, configured to generate a first communication protocol for communicating with the controller according to the sequencer identification code, the controller identification code and the service type identification code;

A sending module, configured to issue a configuration command to the controller based on the first communication protocol, for the controller to control the to-be-configured network element device to obtain configuration information from the configuration information management center for version configuration .

a receiving module, configured to receive a configuration command issued by the scheduler through a first communication protocol, where the first communication protocol carries a service type identification code corresponding to a user requirement;

a determining module, configured to extract the service type identification code from the first communication protocol, and determine the version identification code of the configuration information required for version configuration of the network element device to be configured according to the service type identification code ;

an acquisition module for acquiring the controller identification code and the configuration information management center identification code of the configuration information management center;

a generating module, configured to generate a second communication protocol for communicating with the configuration information management center according to the controller identification code, the configuration information management center identification code and the version identification code;

A sending module, configured to issue a configuration information search command to the configuration information management center based on the second communication protocol, so that the configuration information management center determines whether configuration information matching the version identification code is stored.

A receiving module, configured to receive a configuration information search command issued by the controller through a second communication protocol, where the second communication protocol carries a version identification of the configuration information required for version configuration of the to-be-configured network element device code;

A search module, configured to extract the version identification code from the second communication protocol, and traverse the locally stored configuration information according to the version identification code; if the configuration information matching the version identification code is traversed, Then the configuration information management center stores the configuration information matching the version identification code as the search result; if the configuration information matching the version identification code is not traversed, the configuration information management center does not store the configuration information matching the version identification code. The configuration information matched by the version identifier is used as the search result;

A sending module, configured to feed back the search result to the controller based on the second communication protocol, so that the controller can respond to the orchestrator for configuration failure, or control the to-be-configured network element device from The configuration information management center obtains configuration information matching the version identification code to perform version configuration.

a receiving module, configured to receive a configuration command issued by the controller through a third communication protocol, where the third communication protocol carries a version identification code of configuration information required for version configuration;

an extraction module for extracting the version identification code from the third communication protocol;

an acquisition module for acquiring the configuration information management center identification code of the configuration information management center that stores the configuration information matching the version identification code;

a generating module for generating a fourth communication protocol for communicating with the configuration information management center according to the configuration information management center identification code and the version identification code;

A sending module, configured to issue a configuration information acquisition command to the configuration information management center based on the fourth communication protocol, for the configuration information management center to feed back a configuration information matching the version identification code based on the fourth communication protocol. configuration information;

a receiving module, further configured to receive the configuration information that matches the version identification code fed back by the configuration information management center through the fourth communication protocol;

A configuration module, configured to perform version configuration according to the configuration information.

a memory communicatively coupled to the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute a version configuration as described above as applied to the orchestrator The method, or the version configuration method applied to the controller, or the configuration management method applied to the configuration management center, or the version configuration method applied to the network element device to be configured.

The embodiment of the present application also provides a version configuration system, including: an orchestrator, a controller, a configuration information management center, and a network element device to be configured;

the orchestrator, configured to execute the above-mentioned version configuration method applied to the orchestrator;

the controller, configured to execute the above-mentioned version configuration method applied to the controller;

The configuration information management center is used to execute the above-mentioned version configuration method applied to the configuration information management center;

The to-be-configured network element device is configured to execute the above-mentioned version configuration method applied to the to-be-configured network element device.

Embodiments of the present application further provide a computer-readable storage medium storing a computer program. When the computer program is executed by the processor, the above-mentioned version configuration method applied to the orchestrator is implemented, or the version configuration method applied to the controller, or the configuration management method applied to the configuration management center, or applied to the network to be configured. Metadevice version configuration method.

Description of drawings

One or more embodiments are exemplified by the pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments.

1 is a schematic structural diagram of a version configuration system provided by a first embodiment of the present application;

2 is a flowchart of a version configuration method applied to an orchestrator provided by a second embodiment of the present application;

3 is a flowchart of a version configuration method applied to a controller provided by a third embodiment of the present application;

4 is a flowchart of a version configuration method applied to a configuration information management center provided by the fourth embodiment of the present application;

5 is a flowchart of a version configuration method applied to a to-be-configured network element device provided by a fifth embodiment of the present application;

FIG. 6 is a schematic structural diagram of a version configuration device deployed in an orchestrator according to a sixth embodiment of the present application;

7 is a schematic structural diagram of a version configuration device deployed in a controller provided by a seventh embodiment of the present application;

8 is a schematic structural diagram of a version configuration device deployed in a configuration information management center provided by an eighth embodiment of the present application;

9 is a schematic structural diagram of a version configuration apparatus deployed on a network element device to be configured provided by the ninth embodiment of the present application;

FIG. 10 is a schematic structural diagram of a version configuration device provided by a tenth embodiment of the present application.

Detailed ways

In order to make the objectives, technical solutions and advantages of the embodiments of the present application more clear, each embodiment of the present application will be described in detail below with reference to the accompanying drawings. However, those of ordinary skill in the art can understand that, in each embodiment of the present application, many technical details are provided for the reader to better understand the present application. However, even without these technical details and various changes and modifications based on the following embodiments, the technical solutions claimed in the present application can be realized. The following divisions of the various embodiments are for the convenience of description, and should not constitute any limitation on the specific implementation of the present application, and the various embodiments may be combined with each other and referred to each other on the premise of not contradicting each other.

The version configuration method, device, device, system and storage medium proposed in the present application convert user requirements into corresponding service type identification codes according to a predefined set of service types by using an orchestrator, and then identify codes according to the orchestrator's own orchestrator. code, as well as the controller identification code that identifies the controller and the identified service type identification code, generate a first communication protocol for communicating with the controller, and issue a configuration command to the controller based on the generated first communication protocol, so that After receiving the configuration command issued by the orchestrator, the controller can control the network element device to be configured to independently obtain the corresponding configuration information from the configuration information management center to perform version configuration. Because in the entire version configuration process, only the interaction between the orchestrator, the controller, the configuration information management center and the network element to be configured can accurately locate the configuration information required for the version configuration, without manual intervention at all, so that both In order to improve the configuration efficiency, it can avoid human errors caused by manual intervention.

In addition, because in the version configuration solution provided in this application, the configuration information required for version configuration of the network element device to be configured is separately stored in the configuration information management center, that is, the configuration information corresponding to different versions does not need to be pre-stored in the configuration information management center. In each network element device to be configured, only one copy of the configuration information of the same version needs to be stored in the configuration information management center, thereby reducing the manpower to deploy different versions of the configuration information in each network element device to be configured in advance. It can also facilitate the later operation and maintenance personnel to update and maintain the configuration information of each version. At the same time, by storing the configuration information separately in the configuration information management center, the version configuration of the network element device to be configured is free from the limitation of the local storage space of the network element device to be configured, so that more versions of the configuration of the network element device to be configured can be realized. , so as to better meet the needs of various users.

The first embodiment of the present application relates to a version configuration system, including an orchestrator, a controller, a configuration information management center, and a network element device to be configured.

Among them, the orchestrator is mainly used to convert user requirements into service requirements that can be identified by the controller. In this embodiment, it is specifically a service type identification code that identifies the uniqueness of the service type, and is based on the orchestrator identification code that identifies the uniqueness of the orchestrator. , a controller identification code that identifies the uniqueness of the controller, and the converted service type identification code to generate a first communication protocol for communicating with the controller, and then issue a configuration command to the controller based on the generated first communication protocol.

The controller is mainly used to generate and communicate with the configuration information management center based on the service type identification code carried in the first communication protocol with the scheduler, its own controller identification code, and the obtained identification code of the configuration information management center the second communication protocol, and then communicate with the configuration information management center based on the second communication protocol.

In this embodiment, the controller also determines, based on the search result fed back by the configuration information management center through the second communication protocol, whether to inform the scheduler that the configuration fails this time based on the first communication protocol, or whether to inform the orchestrator based on the identification code of the controller and the network element to be configured. The device's network element identification code and the version identification code determined based on the service type identification code generate a third communication protocol for communicating with the to-be-configured network element device, and communicate with the to-be-configured network element device based on the third communication protocol.

The configuration information management center is mainly used to traverse the locally stored configuration information based on the version identification code carried in the second communication protocol with the controller, and then determine whether the configuration information matching the version identification code is stored locally, and The controller is informed of the traversal result via the second communication protocol.

In this embodiment, the configuration information management center will further locate the corresponding configuration information based on the version identification code carried in the fourth communication protocol when receiving the configuration information acquisition command issued by the network element device to be configured based on the fourth communication protocol, The obtained configuration information is fed back to the network element device to be configured through the fourth communication protocol.

The network element device to be configured is mainly used for the configuration information management center identification code based on the version identification code carried in the third communication protocol with the controller and the configuration information management center that stores the configuration information corresponding to the version identification code, A fourth communication protocol for communicating with the configuration information management center is generated, that is, the configuration information corresponding to the version identification code is acquired from the configuration information management center based on the fourth communication protocol.

In addition, it is worth mentioning that, in practical applications, there may be multiple network element devices to be configured.

Correspondingly, in order to facilitate version configuration of network element devices to be configured in different areas and different clusters, there may also be multiple configuration information management centers that store configuration information required for version configuration of network element devices to be configured. Similarly, there may also be multiple controllers that directly communicate with the network element device to be configured.

Understandably, in practical applications, the number of configuration information management centers and controllers may be determined according to the area or cluster where the network element device to be configured is located.

For example, if there are currently three NE clusters A, B and C to be configured, three controllers and three configuration information management centers can be set in the version configuration system, that is, each NE cluster to be configured corresponds to one controller and a configuration information management center.

For another example, when there are three clusters of network element devices to be configured, A, B, and C, there are 50 network element devices to be configured in cluster A, 100 network element devices to be configured in cluster B, and 10 network element devices in cluster C. The network element device to be configured, the version configuration system can have three controllers and three configuration information management centers, that is, each network element device cluster to be configured corresponds to one controller and one configuration information management center, or two A controller and two configuration information management centers, and one controller and one configuration information management center correspond to cluster A and cluster C, and the other controller and configuration information management center correspond to cluster B independently.

It should be understood that the above examples are only examples listed for better understanding of the technical solutions of the present embodiment, and are not used as the only limitation on the present embodiment. In practical applications, those skilled in the art can set the number of controllers and configuration information management centers as required.

In addition, it is worth mentioning that, in order to make the version configuration system provided in this embodiment with disaster tolerance, the orchestrator, controller, and controller corresponding to each to-be-configured network element device cluster or each to-be-configured network element device There are at least two configuration information management centers, that is, there will be a master orchestrator, a slave orchestrator, a master controller, a slave controller, a master configuration information management center, and a slave configuration information management center in the version configuration system. center. At the same time, based on the preset logic, only the main orchestrator, the main controller and the main configuration information management center are started under normal circumstances, and when any one of them is abnormal, the function responsible for the abnormal device will be switched to the corresponding slave device. , so as to ensure the normal operation of the version configuration system.

In addition, it can be understood that in practical applications, the configuration information management center is essentially a database that stores configuration information of various network element devices to be configured, such as system version configuration information, function version configuration information, and patch version configuration information.

The network element device to be configured may be a router, a switch, or a transmission node involved in an optical transport network (OTN).

For ease of understanding and description, this embodiment takes an orchestrator, a controller, a configuration information management center, and a network element device to be configured, specifically a router, as an example, and with reference to FIG. The version configuration process is described in detail.

For the orchestrator:

When a user submits a user requirement to the orchestrator, that is, when the orchestrator receives the user requirement, it converts the user's original request into a service request and sends it to the corresponding controller.

Understandably, the above-mentioned original request is the received user demand.

Accordingly, the original request is converted into a service request and sent to the corresponding controller, specifically:

(1) Determine the service type identifier corresponding to the user requirement according to a predefined service type set.

In this embodiment, the service type set includes correspondences between various user requirements and various service type identification codes.

It is understandable that in practical applications, the pre-defined service type set includes not only user requirements and service type identification codes, but also the service types corresponding to the service type identification codes. The defined service type set analyzes the received user requirements to determine the service type corresponding to the current user requirement, and then finds the service type identification code identifying the current service type.

Regarding the above-mentioned business type set, the specific form can be shown in Table 1:

Table 1 Set of business types

用户需求User needs	业务类型business type	业务类型识别码business type identifier
用户需求1User needs 1	业务类型1 business type 1	123123
用户需求2User needs 2	业务类型2 business type 2	234234
......	......	......

In addition, it is worth mentioning that, in practical applications, in addition to a user requirement corresponding to a service type, and then corresponding to a service type identification code, that is, the situation given in Table 1, there may also be a user requirement corresponding to multiple service types. , which in turn corresponds to multiple service type identification codes, and a user requirement corresponds to one service type identification code but corresponds to multiple service types.

For example, the current router is running the version corresponding to the 4G service. When the user needs to apply for the 5G service, the version search will be triggered in this case, and the version will be updated when the version can be searched. In this case, the user requirement is the 5G service application. The service type identification code corresponding to the 5G service can be set in advance, and the service type identification code that identifies the 5G service may have multiple service types, which can be understood as service functions. Such as segment routing (SR), network remote sensing technology (Telemetry), Bier multicast, FlexE, etc.

For another example, the current router is running the version corresponding to the 5G service, but the user needs a new 5G function, which is not supported by the current router. Assuming that the information configuration management center has a patch version that supports this function, it can be loaded by the above method. In this patch version, the service type identification code of the new service type of the 5G function can be found through the user requirement.

It should be understood that the above examples are only examples listed for better understanding of the technical solutions of the present embodiment, and are not used as the only limitation on the present embodiment.

(2) Obtain the identifier of the scheduler and the controller identifier of the controller.

The organizer identification code mentioned in this embodiment is identification information that can identify the uniqueness of the organizer.

Correspondingly, the controller identification code is identification information that can identify the uniqueness of the controller.

Understandably, in practical applications, the above-mentioned sequencer identification code for identifying the uniqueness of the sequencer and the controller identification code for identifying the uniqueness of the controller may be pre-allocated by technicians according to preset rules. , or it can be the identifier information allocated by the manufacturer when the orchestrator and controller are prepared and shipped from the factory, or it can be the unique identifier assigned to each orchestrator and controller of the access network according to the pre-compiled script. identification information.

(3) Generating a first communication protocol for communicating with the controller according to the orchestrator identification code, the controller identification code and the service type identification code.

It should be noted that the communication connections established between the functional entities in the version configuration system in this embodiment are still based on existing protocols such as Transmission Control Protocol (TCP, Transmission Control Protocol)/Internet Protocol (IP, Internet Protocol). However, the communication protocol required for communication between the functional entities in this embodiment essentially indicates what information is specifically carried in the communication protocol.

Therefore, the above-mentioned first communication protocol is essentially to express the communication protocol generated based on the above-mentioned three kinds of identification codes, and issue a configuration command to the controller, in order to transmit the above-mentioned three kinds of identification codes to the control receiving the configuration command. The device takes the above three identification codes as the header file of the first communication protocol, and uses the configuration command as the specific action instruction for transmission.

The relationship between the orchestrator ID, the controller ID, and the service type ID can be identified in the following format: <organizer ID, controller ID, service type ID>.

(4) Based on the first communication protocol, a configuration command is delivered to the controller, so that the controller can control the to-be-configured network element device to obtain configuration information from the configuration information management center to perform version configuration.

In addition, it is worth mentioning that in practical applications, in order to avoid responding to illegal and invalid user requirements, the module responsible for interacting with users in the orchestrator can be called a demand input module. , you can first check the validity of user requirements.

Correspondingly, if it is determined that the current user demand is legitimate, it is actually received for subsequent processing, that is, only the legitimate user demand will be received by the arranger; otherwise, the current user demand is directly rejected.

Regarding the above-mentioned legality check, it specifically refers to whether the request format, the adopted protocol, etc. of the original request carrying the user requirements meet the preset requirements of the orchestrator. That is, if it is satisfied, it is considered that the current user requirement is legal, otherwise, it is illegal.

In this embodiment, since the orchestrator converts user requirements into service requirements that can be identified by the controller, that is, when determining the service type identifier corresponding to the user requirement, it is based on a pre-defined service type set, so in order to avoid centralized service types Undefined user requirements are analyzed and processed, thereby increasing the resource occupancy of the orchestrator. After it is determined that the received user requirement is legitimate, and before determining the service type identification code corresponding to the user requirement according to the predefined service type set, it can be further judged whether the user requirement is a valid requirement.

Specifically, in practical applications, to determine the validity of the user requirements, it can be determined whether the user requirements are valid requirements according to preset logical analysis rules.

Correspondingly, if it is determined through judgment that the user requirement is a valid requirement, the above-mentioned operation of determining the service type identification code corresponding to the user requirement according to the predefined service type set is performed.

Regarding the above-mentioned logic analysis rules, it may be to define a pre-defined business type as a valid business type or an invalid business type; When judging, as long as the business type corresponding to the current user requirement is not in the logic analysis rules, the current user requirement is considered to be an invalid requirement, otherwise, it is an effective requirement.

In addition, in practical applications, the above-mentioned operation of validity detection can be regarded as being implemented by another functional module inside the orchestrator, for example, the module that performs validity detection is called a requirement analysis module.

In this embodiment, the function of finally determining the service type identifier corresponding to the user requirement according to the predefined service type set can also be regarded as being implemented by another functional module inside the orchestrator, such as a service type module.

Based on the above description, it can be seen that when the user demand reaches the orchestrator, the internal demand input module will first check the validity, and when it is legal, the internal demand analysis module will conduct validity analysis, and when it is valid, the internal business type model will be used. According to the predefined service type set, the service type identification code corresponding to the user requirement is determined.

It should be understood that the division of the above functional modules is only an example enumerated for better understanding of the technical solutions of the present embodiment, and is not regarded as the only limitation of the present embodiment.

For the controller:

The controller sends a configuration information adaptation request to the configuration information management center according to the service request sent by the orchestrator, and then sends a configuration command to the router to be configured when there is matching configuration information in the configuration information management center. When there is no matching configuration information in the management center, the orchestrator is notified that the configuration request for this version fails.

It is understandable that the service request mentioned above is essentially the service type identification code corresponding to the user requirement carried by the scheduler through the first communication protocol.

Correspondingly, the version configuration process executed in the controller is as follows:

(1) Receive a configuration command sent by the orchestrator through the first communication protocol.

It can be known from the above description of the scheduler that the first communication protocol carries a service type identification code corresponding to a user requirement, that is, a service type ID.

(2) Extract the service type identification code from the first communication protocol, and determine the version identification code of the configuration information required for version configuration of the to-be-configured network element device according to the service type identification code.

In this embodiment, since the relationship between the user requirements and the service type identification code is predetermined, the configuration information of the version corresponding to the user requirements and the service type identification code is also predetermined. To quickly locate the configuration information of the corresponding version, this embodiment also allocates a corresponding version identification code to the configuration information.

Further, after the service type identification code is extracted from the first communication protocol, the corresponding relationship between the service type identification code and the version identification code is defined according to a preset, so that the network element equipment to be configured can be quickly determined. The version identifier of the configuration information required for version configuration.

(3) Obtain the controller identification code and the configuration information management center identification code of the configuration information management center.

The controller identification code mentioned in this embodiment is identification information that can identify the uniqueness of the controller.

Correspondingly, the configuration information management center identification code is identification information capable of identifying the uniqueness of the configuration information management center.

Understandably, in practical applications, the above-mentioned controller identification code for identifying the uniqueness of the controller, and the configuration information management center identification code for identifying the uniqueness of the configuration information management center, may be the technical personnel according to preset rules. , pre-allocated, it can also be the identification information allocated by the manufacturer when the controller is prepared and shipped from the factory, configured according to preset rules when the configuration information management center is built, or it can be based on pre-compiled scripts. The unique identification information assigned by the controller entering the network and the configuration information management center to identify its uniqueness.

(4) Generate a second communication protocol for communicating with the configuration information management center according to the controller identification code, the configuration information management center identification code and the version identification code.

Because the communication connections established between the functional entities in the version configuration system in this embodiment are still based on the implementation of existing protocols such as Transmission Control Protocol (TCP)/Internet Protocol (IP) , and the communication protocol required for communication between the functional entities in this embodiment is essentially to indicate what information is specifically carried in the communication protocol.

Therefore, the above-mentioned second communication protocol is essentially to express the communication protocol generated based on the above-mentioned three kinds of identification codes, and issue a configuration information search command to the configuration information management center, in order to transmit the above-mentioned three kinds of identification codes to the receiving The configuration information management center of the configuration information search command takes the above three identification codes as the header file of the second communication protocol, and uses the configuration information search command as a specific action instruction for transmission.

The relationship between the controller identification code, the configuration information management center identification code and the version identification code can be identified in the following format: <controller ID, configuration information management center ID, version ID>.

(5) Based on the second communication protocol, issue a configuration information search command to the configuration information management center for the configuration information management center to determine whether configuration information matching the version identifier is stored.

(6) Receive the search result fed back by the configuration management center through the second communication protocol.

Correspondingly, if the search result is that the configuration information management center does not store the configuration information matching the version identifier, then based on the first communication protocol, a response of configuration failure is made to the orchestrator; If the search result is that the configuration information management center stores configuration information matching the version identification code, the network element identification code of the to-be-configured network element device is acquired.

It is understandable that the network element identification code of the network element device to be configured in this embodiment is identification information that can identify the uniqueness of the network element device.

Similarly, in practical applications, the above-mentioned network element identification code used to identify the uniqueness of the network element equipment to be configured may be pre-allocated by technicians according to preset rules, or may be prepared by the network element equipment to be configured. When the factory is finished, the identification information assigned by the manufacturer may also be identification information assigned to each network element device to be configured on the access network to identify its uniqueness according to a pre-compiled script.

(7) Generate a third communication protocol for communicating with the to-be-configured network element device according to the controller identification code, the network element identification code and the version identification code.

Therefore, the above-mentioned third communication protocol is essentially to express the communication protocol generated based on the above-mentioned three identification codes, and issue a configuration command to the network element device to be configured, that is, the to-be-configured router in FIG. The identification code is transmitted to the router to be configured that receives the configuration command, that is, the above three identification codes are used as the header file of the third communication protocol, and the configuration command is used as the specific action instruction of the transmission.

The relationship between the controller identification code, the network element identification code and the version identification code may be identified in the following format: <controller ID, network element ID, version ID>.

(8) Based on the third communication protocol, issue a configuration command to the to-be-configured network element device for the to-be-configured network element device to obtain the configuration information corresponding to the version identifier from the configuration information management center for version configuration.

In addition, it is worth mentioning that in practical applications, in order to avoid responding to illegal and invalid business requirements (the business type corresponding to the business type identifier), the module in the controller responsible for interacting with the orchestrator can be called For the service type input module, when monitoring the arrival of the configuration command issued by the orchestrator through the first communication protocol, it can firstly check the validity of the service type corresponding to the service type identification code carried in the first communication protocol.

Correspondingly, if it is determined that the service type is legal through the inspection, it is actually received for subsequent processing, that is, only the legal service type will be received by the controller; otherwise, it is directly rejected.

In this embodiment, in order to ensure that the incoming service type is both legal and valid. After determining that the service type is legal, before generating the second communication protocol for communicating with the configuration information management center according to the controller identification code, the configuration information management center identification code and the version identification code, further Determine whether the business type is valid.

Specifically, in practical applications, the judgment of the validity of the service type can also be judged according to the preset logical analysis rules.

Correspondingly, if it is determined by judging that the service type is valid, then the above-mentioned generation of the second information that communicates with the configuration information management center according to the controller identification code, the configuration information management center identification code and the version identification code is performed. The operation of the communication protocol.

The judgment of the legality and validity of the execution of the controller is similar to the judgment of the validity and validity of the execution of the orchestrator, and will not be repeated here.

In addition, those skilled in the art can set the rules based on which the controller judges legality and validity, which is not limited in this embodiment.

For the configuration information management center, it is mainly used to save all configurable versions of the to-be-configured network element devices, such as the router to be configured in FIG. 1 , and the configuration information corresponding to these versions.

At the same time, the configuration information management center supports the functions of adding, deleting, and modifying the configuration information of each version, and supports the configuration information search requirements of the controller and the download requirements of the configuration information of the network element devices to be configured.

In addition, in order to facilitate the configuration information management center to search for the configuration information corresponding to the version identification code required by the controller, and to facilitate the network element device to be configured to obtain the configuration information corresponding to the version identification code from the configuration information management center, the configuration information The versions stored in the management center and the configuration information corresponding to these versions are stored in a manner agreed upon with the controller and the network element device to be configured.

In order to facilitate the understanding of the configuration information management center, the operations performed during the version configuration process are described below:

(1) Receive a configuration information search command sent by the controller through a second communication protocol, where the second communication protocol carries a version identification code of configuration information required for version configuration of the network element device to be configured.

(2) Extract the version identification code from the second communication protocol, traverse the locally stored configuration information according to the version identification code, and generate a search result according to the traversal result.

For example, if the configuration information matching the version identification code is traversed, the configuration information management center stores the configuration information matching the version identification code as a search result.

Correspondingly, if the configuration information matching the version identification code is not traversed, the configuration information management center that does not store the configuration information matching the version identification code is used as the search result.

(3) Feeding back the search result to the controller based on the second communication protocol, so that the controller can respond to the orchestrator for a configuration failure, or control the network element device to be configured from the The configuration information management center obtains configuration information matching the version identification code for version configuration.

In this embodiment, if the feedback search result is that the configuration information management center stores configuration information that matches the version identifier, the controller will control the to-be-configured network element device to delete the configuration information from the configuration information management center. Obtain configuration information matching the version identifier to perform version configuration; otherwise, the controller will respond to the orchestrator that the configuration fails.

(4) Receive a configuration information acquisition command issued by the to-be-configured network element device through a fourth communication protocol, where the fourth communication protocol carries the version of the configuration information required for version configuration of the to-be-configured network element device Identifier.

It should be noted that the fourth communication protocol mentioned in this embodiment is specifically configured by the network element device to be configured, according to the configuration information management center identification code of the configuration information management center that stores the configuration information to be obtained and the configuration information to be obtained. The version identifier corresponding to the configuration information is generated.

Similar to the first, second, and third communication protocols mentioned above, the format is: <configuration information management center ID, version ID>.

(5) Based on the fourth communication protocol, the configuration information matching the version identification code is fed back to the to-be-configured network element device for the to-be-configured network element device to perform version configuration.

For the to-be-configured network element device, this embodiment specifically refers to the to-be-configured router in FIG. 1 :

When the router to be configured receives the configuration command sent by the controller through the third communication protocol, the configuration information is downloaded by interacting with the configuration information management center, and the configuration of this version is completed according to the downloaded configuration information.

(1) Receive a configuration command issued by the controller through a third communication protocol, where the third communication protocol carries a version identification code of configuration information required for version configuration.

(2) Extracting the version identification code from the third communication protocol.

(3) Obtain the configuration information management center identification code of the configuration information management center that stores the configuration information matching the version identification code.

(4) Generate a fourth communication protocol for communicating with the configuration information management center according to the configuration information management center identification code and the version identification code.

(5) Based on the fourth communication protocol, issue a configuration information acquisition command to the configuration information management center for the configuration information management center to feed back configuration information matching the version identifier based on the fourth communication protocol .

(6) Receive the configuration information that matches the version identifier and is fed back by the configuration information management center through the fourth communication protocol.

(7) Perform version configuration according to the configuration information.

It is understandable that, in practical applications, in order to avoid repeated configuration of the same version, before executing (7), the current version information currently running can be obtained first; then, it is determined whether the current version information is consistent with the version information. .

Correspondingly, if they are inconsistent, the operation of performing version configuration according to the configuration information is performed; otherwise, based on the third communication protocol, feedback is made to the controller that version configuration is not required.

(8) Based on the third communication protocol, a configuration result, such as configuration failure or configuration success, is fed back to the controller.

In addition, it can be seen from FIG. 1 that when the network element device to be configured is a router, the router includes a main control board and several line cards.

Therefore, when the network element device to be configured is a router, the version configuration process of the router is as follows:

First, the configuration information that matches the version identification code fed back by the configuration information management center through the fourth communication protocol is saved in the main control board.

Then, the main control board acquires the line card identification code of each of the line cards, and then generates the first communication with the corresponding line card according to the version identification code and each of the line card identification codes. five communication protocols, and based on the fifth communication protocol with each of the line cards, the configuration information is delivered to each of the line cards for each of the line cards to perform according to the configuration information version configuration.

It can be seen from the above description that the fifth communication protocol followed between the main control board and the line card is specifically the relationship between the version ID and the line card ID, so it can be specifically expressed in the form of <version ID, line card ID>.

In addition, it is worth mentioning that, due to the limitation of router chip resources, in practical applications, versions of different sizes and complexity can usually be made in advance according to different business types, and stored in the configuration information management center. The controller searches for the configuration information of the adaptable version from the configuration information management center according to the service type ID obtained from the orchestrator. However, when actually searching, multiple versions may be found. In this case, each searched version can be scored. The scoring principle is based on the version usage and service matching degree. The version with higher matching degree is closer to the user's needs, that is, it is finally fed back to the router. The required configuration information is the closest to the user's needs.

In addition, in practical applications, in order to make the version configuration more in line with the actual use requirements, the orchestrator, controller, configuration information management center, and network element devices to be configured in the version configuration system are all provided with a feedback mechanism. If a rejection occurs in one link, the entire version configuration process will be terminated, the operation will be canceled, and finally the orchestrator will conduct arbitration and reply to the user.

In addition, regarding the first, second, third, fourth and fifth mentioned above, the communication protocol itself is not limited, but is only used to distinguish the communication protocols followed when different functional entities communicate.

Thus, the version configuration process of the single orchestrator, the single controller, the single configuration information management center, and the single version configuration system of the single network element device to be configured is completed.

Based on the above description, the process of version configuration for a single orchestrator, multiple controllers, multiple configuration information management centers, and multiple version configuration systems for network element devices to be configured is described:

The orchestrator issues commands to the controller clusters under its jurisdiction according to user requirements, and each controller issues a configuration information search command to the corresponding configuration information management center according to the to-be-configured network element device cluster under its jurisdiction, and searches for each to-be-configured device cluster. The network element device issues a configuration command, and each network element device to be configured downloads configuration information from the configuration information management center designated by the controller.

Further, considering the disaster recovery requirements of the network, a load sharing relationship or an active/standby relationship may be established between multiple controllers and between multiple configuration information management centers. The multiple network element devices to be configured are generally independent and parallel, and are controlled by the controller as a whole.

In addition, in practical applications, when the version configuration of the network element device to be configured is performed, in order to achieve service protection, the network element device to be configured for the version configuration may be isolated.

For example, when the controller determines that the configuration information management center stores matching configuration information, that is, when the version configuration of the network element device to be configured can be performed, after issuing a configuration command to the network element device to be configured, the controller can further make the entire network element device to be configured. Meta-devices are isolated, and the topology is recalculated for service convergence. After the version configuration is completed, the controller releases the isolated network element devices to be configured, and recalculates the topology to perform service convergence.

For another example, when the controller determines that matching configuration information is stored in the configuration information management center, that is, when the version configuration of the network element device to be configured can be performed, after issuing a configuration command to the network element device to be configured, the controller can further make only the configuration information to be configured. The units in the NE device that need to be version-configured are isolated, and service convergence is performed again. After the version configuration is completed, the controller releases the internally isolated units of the network element device to be configured, and performs service convergence again.

It should be understood that the above examples are only examples listed for better understanding of the technical solutions of the present embodiment, and are not used as the only limitation on the present embodiment. In practical applications, what method is used to protect the service of the network element equipment to be configured that needs to be versioned? Specifically, according to the principle of minimal service impact, the method of isolating only the units that need to be versioned is generally preferred. When this method cannot meet the service requirements, select the method of isolating the entire NE to be configured.

In addition, it is worth mentioning that no matter which method is selected, since it involves the switching of the traffic path, it is necessary to switch the services and traffic to be configured to the backup device and backup link to achieve the purpose of service protection. After the version configuration is complete, switch services and traffic to the new unit to support user needs.

Therefore, the version configuration system provided by this embodiment converts user requirements into corresponding service type identification codes according to a predefined service type set by using an orchestrator, and then identifies the Based on the controller identification code of the controller and the determined service type identification code, a first communication protocol for communicating with the controller is generated, and based on the generated first communication protocol, a configuration command is issued to the controller, so that the controller receives a configuration command. After the configuration command issued by the orchestrator, the network element device to be configured can be controlled to independently obtain the corresponding configuration information from the configuration information management center to perform version configuration. Because in the entire version configuration process, only the interaction between the orchestrator, the controller, the configuration information management center and the network element to be configured can accurately locate the configuration information required for the version configuration, without manual intervention at all, so that both In order to improve the configuration efficiency, it can avoid human errors caused by manual intervention.

In addition, in the version configuration system provided by this application, the configuration information required for version configuration of the network element device to be configured is separately stored in the configuration information management center, that is, the configuration information corresponding to different versions does not need to be pre-stored in the configuration information management center. In each network element device to be configured, only one copy of the configuration information of the same version needs to be stored in the configuration information management center, thereby reducing the manpower to deploy different versions of the configuration information in each network element device to be configured in advance. It can also facilitate the later operation and maintenance personnel to update and maintain the configuration information of each version. At the same time, by storing the configuration information separately in the configuration information management center, the version configuration of the network element device to be configured is free from the limitation of the local storage space of the network element device to be configured, so that more versions of the configuration of the network element device to be configured can be realized. , so as to better meet the needs of various users.

The second embodiment of the present application relates to a version configuration method, which is applied to an orchestrator in a version configuration system, where the version configuration system further includes a controller, a configuration information management center, and a network element device to be configured.

Understandably, in practical applications, the configuration information management center is essentially a database that stores configuration information of various network element devices to be configured, such as system version configuration information, function version configuration information, and patch version configuration information.

Correspondingly, the network element device to be configured may be a router, a switch, or a transmission node involved in an optical transport network (OTN).

In order to facilitate the understanding of the version configuration method provided by this embodiment, the following description is made with reference to the flowchart shown in FIG. 2 :

Step 201: Receive a user requirement, and determine a service type identifier corresponding to the user requirement according to a predefined service type set.

Wherein, in this embodiment, the service type set includes the corresponding relationship between each user requirement and each service type identification code.

Correspondingly, if it is determined that the current user demand is legitimate, it is actually received for subsequent processing, that is, only the legitimate user demand will be received by the orchestrator; otherwise, the orchestrator directly rejects the user requirement.

Further, since the orchestrator converts user requirements into service requirements that can be identified by the controller, that is, when determining the service type identification code corresponding to the user requirements, it is based on a predefined service type set, so in order to avoid no definition of the service type set. analysis and processing of user requirements, which in turn increases the resource usage of the orchestrator. After it is determined that the received user requirement is legitimate, and before determining the service type identification code corresponding to the user requirement according to the predefined service type set, it can be further judged whether the user requirement is a valid requirement.

In addition, in practical applications, the above-mentioned operation of validity detection can be regarded as implemented by another functional module inside the orchestrator, for example, the module that performs validity detection is called a requirement analysis module.

Step 202: Obtain the identifier of the orchestrator and the identifier of the controller of the controller.

Step 203: Generate a first communication protocol for communicating with the controller according to the orchestrator identification code, the controller identification code, and the service type identification code.

Step 204: Based on the first communication protocol, issue a configuration command to the controller for the controller to control the to-be-configured network element device to obtain configuration information from the configuration information management center to perform version configuration.

It is not difficult to find from the above description that the version configuration method provided in this embodiment uses an orchestrator to convert user requirements into corresponding service type identifiers according to a pre-defined service type set, and then identifies the orchestrator's own scheduler identifier according to the identifier. , and the controller identification code that identifies the controller and the identified service type identification code, generates a first communication protocol that communicates with the controller, and issues a configuration command to the controller based on the generated first communication protocol, so that the control After receiving the configuration command issued by the orchestrator, the controller can control the network element device to be configured to independently obtain the corresponding configuration information from the configuration information management center to perform version configuration. Because in the entire version configuration process, only the interaction between the orchestrator, the controller, the configuration information management center and the network element to be configured can accurately locate the configuration information required for the version configuration, without manual intervention at all, so that both In order to improve the configuration efficiency, it can avoid human errors caused by manual intervention.

In addition, it is not difficult to find that the orchestrator, controller, configuration information management center and to-be-configured network element device mentioned in this embodiment are respectively different from the orchestrator, controller, configuration information management center and to-be-configured network element device involved in the first embodiment. The configuration corresponds to the network element equipment, that is, this embodiment can be implemented in cooperation with the first embodiment. Therefore, the related technical details mentioned in the first embodiment are still valid in this embodiment, and are not repeated here in order to reduce repetition. Correspondingly, the relevant technical details mentioned in this embodiment can also be applied in the first embodiment.

The third embodiment of the present application relates to a version configuration method, which is applied to a controller in a version configuration system, where the version configuration system further includes an orchestrator, a configuration information management center, and a network element device to be configured.

In order to facilitate the understanding of the version configuration method provided by this embodiment, the following description is made with reference to the flowchart shown in FIG. 3 :

Step 301: Receive a configuration command issued by the orchestrator through a first communication protocol, where the first communication protocol carries a service type identification code corresponding to a user requirement.

Step 302: Extract the service type identification code from the first communication protocol, and determine the version identification code of the configuration information required for version configuration of the network element device to be configured according to the service type identification code.

Step 303: Obtain the controller identification code and the configuration information management center identification code of the configuration information management center.

Step 304: Generate a second communication protocol for communicating with the configuration information management center according to the controller identification code, the configuration information management center identification code, and the version identification code.

Step 305 , based on the second communication protocol, issue a configuration information search command to the configuration information management center for the configuration information management center to determine whether configuration information matching the version identifier is stored.

Step 306: Receive the search result fed back by the configuration management center through the second communication protocol.

Step 307: Determine whether the search result is that the configuration information management center stores configuration information matching the version identification code.

In this embodiment, if the search result is that the configuration information management center stores configuration information matching the version identification code, step 308 is performed; otherwise, step 311 is performed.

Step 308: Obtain the network element identification code of the to-be-configured network element device.

Step 309: Generate a third communication protocol for communicating with the to-be-configured network element device according to the controller identification code, the network element identification code, and the version identification code.

Step 310: Based on the third communication protocol, issue a configuration command to the to-be-configured network element device for the to-be-configured network element device to obtain the configuration information corresponding to the version identification code from the configuration information management center. version configuration.

Step 311, based on the first communication protocol, make a configuration failure response to the orchestrator.

Therefore, in the version configuration method provided by this embodiment, the controller sends a configuration information adaptation request to the configuration information management center according to the service request sent by the orchestrator, and then when there is matching configuration information in the configuration information management center, It sends a configuration command to the router to be configured, and when there is no matching configuration information in the configuration information management center, it notifies the orchestrator that the configuration request of this version fails. Because in the entire version configuration process, only the interaction between the orchestrator, the controller, the configuration information management center and the network element to be configured can accurately locate the configuration information required for the version configuration, without manual intervention at all, so that both In order to improve the configuration efficiency, it can avoid human errors caused by manual intervention.

In addition, in the version configuration method provided in this embodiment, the configuration information required for version configuration of the network element device to be configured is separately stored in the configuration information management center, that is, the configuration information corresponding to different versions does not need to be pre-stored in each version. In the network element device to be configured, only one copy of the configuration information of the same version needs to be stored in the configuration information management center, which can not only reduce the manpower to deploy different versions of the configuration information in each network element device to be configured in advance, but also It can facilitate the later operation and maintenance personnel to update and maintain the configuration information of each version. At the same time, by storing the configuration information separately in the configuration information management center, the version configuration of the network element device to be configured is free from the limitation of the local storage space of the network element device to be configured, so that more versions of the configuration of the network element device to be configured can be realized. , so as to better meet the needs of various users.

Therefore, after receiving the configuration command issued by the scheduler based on the first communication protocol, the controller locally firstly judges the legality and validity of the service type corresponding to the service type identification code carried in the first communication protocol, so that The version configuration process is more reasonable.

The fourth embodiment of the present application relates to a version configuration method.

Step 401: Receive a configuration information search command issued by the controller through a second communication protocol, where the second communication protocol carries a version identification code of configuration information required for version configuration of the to-be-configured network element device.

Step 402: Extract the version identification code from the second communication protocol, traverse the locally stored configuration information according to the version identification code, and generate a search result according to the traversal result.

Step 403, based on the second communication protocol, feed back the search result to the controller, so that the controller can respond to the orchestrator for configuration failure, or control the to-be-configured network element device from the The configuration information management center obtains configuration information matching the version identification code for version configuration.

Step 404: Receive a configuration information acquisition command issued by the to-be-configured network element device through a fourth communication protocol, where the fourth communication protocol carries the version of the configuration information required for version configuration of the to-be-configured network element device Identifier.

Step 405 , based on the fourth communication protocol, feedback configuration information matching the version identification code to the network element device to be configured, so that the network element device to be configured performs version configuration.

Therefore, in the version configuration method provided in this embodiment, the configuration information required for version configuration of the network element device to be configured is separately stored in the configuration information management center, that is, the configuration information corresponding to different versions does not need to be pre-stored in each to-be-configured device. In configuring network element devices, only one copy of the configuration information of the same version needs to be stored in the configuration information management center, which not only reduces the manpower required to deploy different versions of configuration information on each network element device to be configured in advance, but also facilitates The later operation and maintenance personnel update and maintain the configuration information of each version. At the same time, by storing the configuration information separately in the configuration information management center, the version configuration of the network element device to be configured is free from the limitation of the local storage space of the network element device to be configured, so that more versions of the configuration of the network element device to be configured can be realized. , so as to better meet the needs of various users.

The fifth embodiment of the present application relates to a version configuration method.

Step 501: Receive a configuration command issued by the controller through a third communication protocol, where the third communication protocol carries a version identification code of configuration information required for version configuration.

Step 502: Extract the version identification code from the third communication protocol.

Step 503: Obtain the configuration information management center identification code of the configuration information management center that stores the configuration information matching the version identification code.

Step 504: Generate a fourth communication protocol for communicating with the configuration information management center according to the configuration information management center identification code and the version identification code.

Step 505, based on the fourth communication protocol, issue a configuration information acquisition command to the configuration information management center for the configuration information management center to feed back configuration information matching the version identifier based on the fourth communication protocol .

Step 506: Receive configuration information that matches the version identifier and is fed back by the configuration information management center through the fourth communication protocol.

Step 507: Perform version configuration according to the configuration information.

In this embodiment, in order to avoid repeated configuration of the same version, before step 507 is executed, the current version information currently running may be obtained first; then, it is determined whether the current version information is consistent with the version information.

In addition, in order to enable the orchestrator to know the current version configuration, after the network element device to be configured performs version configuration according to the configuration information, it can feed back the configuration result to the controller based on the third communication protocol, such as successful configuration or configuration failure, and then The controller is caused to inform the orchestrator of the feedback result based on the first communication protocol.

In addition, in practical applications, the network element device to be configured may be a router.

Understandably, in general, a router includes a main control board and several line cards.

Correspondingly, after receiving the configuration information that matches the version identification code fed back by the configuration information management center through the fourth communication protocol, the configuration information will be saved to the main control board; The main control board obtains the line card identification code of each of the line cards, and generates a fifth communication protocol for communicating with the corresponding line card according to the version identification code and each of the line card identification codes, And based on the fifth communication protocol with each of the line cards, the configuration information is delivered to each of the line cards for each of the line cards to perform version configuration according to the configuration information.

Therefore, the version configuration method provided by this embodiment converts user requirements into corresponding service type identification codes according to a predefined service type set by using an orchestrator, and then identifies the Based on the controller identification code of the controller and the determined service type identification code, a first communication protocol for communicating with the controller is generated, and based on the generated first communication protocol, a configuration command is issued to the controller, so that the controller receives a configuration command. After the configuration command issued by the orchestrator, the network element device to be configured can be controlled to independently obtain the corresponding configuration information from the configuration information management center to perform version configuration. Because in the entire version configuration process, only the interaction between the orchestrator, the controller, the configuration information management center and the network element to be configured can accurately locate the configuration information required for the version configuration, without manual intervention at all, so that both In order to improve the configuration efficiency, it can avoid human errors caused by manual intervention.

In addition, the configuration information required for version configuration of the network element device to be configured is stored separately in the configuration information management center, that is, the configuration information corresponding to different versions does not need to be pre-stored in each network element device to be configured. Only one copy of the configuration information of different versions needs to be stored in the configuration information management center, which not only reduces the manpower required to deploy different versions of configuration information on each NE to be configured in advance, but also facilitates the later operation and maintenance personnel to compare different versions of the configuration information. The update and maintenance of the configuration information. At the same time, by storing the configuration information separately in the configuration information management center, the version configuration of the network element device to be configured is free from the limitation of the local storage space of the network element device to be configured, so that more versions of the configuration of the network element device to be configured can be realized. , so as to better meet the needs of various users.

In addition, it should be understood that the division of steps of the various methods above is only for the purpose of describing clearly, and can be combined into one step or split into some steps during implementation, and decomposed into multiple steps, as long as the same logical relationship is included, all Within the protection scope of this patent; adding insignificant modifications to the algorithm or process or introducing insignificant designs, but not changing the core design of the algorithm and process are all within the protection scope of this patent.

The sixth embodiment of the present application relates to a version configuration apparatus, as shown in FIG. 6 , including: a determination module 601 , an acquisition module 602 , a generation module 603 , and a transmission module 604 .

The determining module 601 is configured to receive user requirements, and determine a service type identification code corresponding to the user requirement according to a predefined service type set, where the service type set includes the corresponding relationship between each user requirement and each service type identification code Obtaining module 602 is used to obtain the sequencer identification code and the controller identification code of the controller; Generation module 603 is used to obtain the sequencer identification code, the controller identification code and the service type identification code according to the sequencer identification code , generating a first communication protocol for communicating with the controller; the sending module 604 is configured to, based on the first communication protocol, issue a configuration command to the controller for the controller to control the network to be configured The meta-device obtains configuration information from the configuration information management center to perform version configuration.

In addition, in another example, the version configuration apparatus further includes a requirement input module.

In this embodiment, the requirement input module is configured to check the validity of the user requirement submitted by the user before the determination module 601 performs the above operation.

Correspondingly, if the user requirement is valid, the trigger determination module 601 is executed to perform the above operation; otherwise, the user requirement is rejected.

In addition, in another example, the version configuration apparatus further includes a requirement analysis module.

In this embodiment, the demand analysis module is used to determine whether the user demand is a valid demand according to a preset logic analysis rule after the demand input module determines that the user demand is valid and before the determination module 601 performs the above operation.

Correspondingly, if the user requirement is a valid requirement, the notification determination module 601 performs an operation of determining the service type identification code corresponding to the user requirement according to a predefined service type set.

It is not difficult to find that this embodiment is a device embodiment corresponding to the second embodiment, and this embodiment can be implemented in cooperation with the second embodiment. The related technical details mentioned in the second embodiment are still valid in this embodiment, and are not repeated here in order to reduce repetition. Correspondingly, the related technical details mentioned in this embodiment can also be applied in the second embodiment.

The seventh embodiment of the present application relates to a version configuration apparatus, as shown in FIG. 7 , including: a receiving module 701 , a determining module 702 , an obtaining module 703 , a generating module 704 and a sending module 705 .

The receiving module 701 is configured to receive a configuration command issued by the orchestrator through a first communication protocol, and the first communication protocol carries the service type identification code corresponding to the user's requirement; the determining module 702 is configured to obtain a configuration command from the The service type identification code is extracted from the first communication protocol, and the version identification code of the configuration information required for version configuration of the network element device to be configured is determined according to the service type identification code; the obtaining module 703 is used for obtaining The controller identification code and the configuration information management center identification code of the configuration information management center; the generating module 704 is configured to generate and match the controller identification code, the configuration information management center identification code and the version identification code according to the The second communication protocol for the configuration information management center to communicate; the sending module 705 is configured to issue a configuration information search command to the configuration information management center based on the second communication protocol, for the configuration information management center to determine Whether configuration information matching the version identifier is stored.

In addition, in another example, the receiving module 701 is further configured to receive the search result fed back by the configuration management center through the second communication protocol.

Correspondingly, if the search result is that the configuration information management center does not store the configuration information matching the version identifier, then based on the first communication protocol, a response of configuration failure is made to the orchestrator; If the search result is that the configuration information management center stores configuration information that matches the version identification code, the acquisition module 703 is notified to obtain the network element identification code of the to-be-configured network element device; the generation module 704 is further configured to The controller identification code, the network element identification code and the version identification code are used to generate a third communication protocol for communicating with the to-be-configured network element device; the sending module 705 is further configured to, based on the third communication protocol, A configuration command is issued to the to-be-configured network element device, so that the to-be-configured network element device obtains configuration information corresponding to the version identification code from the configuration information management center to perform version configuration.

In addition, in another example, the version configuration apparatus further includes a service type input module.

In this embodiment, the service type input module is configured to perform constraint checking on the validity of the service type corresponding to the service type identification code carried in the first communication protocol.

Correspondingly, if the service type is legal, the receiving module 701 is triggered to perform the operation of receiving the configuration command issued by the orchestrator through the first communication protocol; otherwise, the receiving module 701 is triggered to perform the operation based on the first communication protocol. , and make a response operation that the service type is illegal to the orchestrator.

In addition, in another example, the version configuration apparatus further includes a service type analysis module.

In this embodiment, the service type analysis module is configured to judge whether the service type is a valid service type according to a preset logic analysis rule.

Correspondingly, if the service type is a valid service type, the trigger generation module 704 executes the process of generating the configuration information corresponding to the configuration information according to the controller identification code, the configuration information management center identification code and the version identification code. The management center communicates the operation of the second communication protocol.

It is not difficult to find that this embodiment is a device embodiment corresponding to the third embodiment, and this embodiment can be implemented in cooperation with the third embodiment. The related technical details mentioned in the third embodiment are still valid in this embodiment, and are not repeated here in order to reduce repetition. Correspondingly, the relevant technical details mentioned in this embodiment can also be applied in the third embodiment.

The eighth embodiment of the present application relates to a version configuration apparatus, as shown in FIG. 8 , including: a receiving module 801 , a searching module 802 and a sending module 803 .

The receiving module 801 is configured to receive a configuration information search command issued by the controller through a second communication protocol, where the second communication protocol carries configuration information required for version configuration of the network element device to be configured The version identification code; the search module 802 is used to extract the version identification code from the second communication protocol, and traverse the locally stored configuration information according to the version identification code; If the configuration information matching the version identification code is stored in the configuration information management center as a search result; if no configuration information matching the version identification code is found, the configuration information matching the version identification code is not found. The information management center does not store the configuration information matching the version identification code as the search result; the sending module 803 is configured to feed back the search result to the controller based on the second communication protocol for the control The controller makes a configuration failure response to the orchestrator, or controls the to-be-configured network element device to obtain configuration information matching the version identifier from the configuration information management center to perform version configuration.

In addition, in another example, the receiving module 801 is further configured to receive a configuration information acquisition command issued by the to-be-configured network element device through a fourth communication protocol, where the fourth communication protocol carries information about the to-be-configured network element device. The version identification code of the configuration information required by the element device to perform version configuration; the sending module 803 is further configured to feed back the configuration information matching the version identification code to the network element device to be configured based on the fourth communication protocol, The version configuration is performed on the network element device to be configured.

It is not difficult to find that this embodiment is a device embodiment corresponding to the fourth embodiment, and this embodiment can be implemented in cooperation with the fourth embodiment. The related technical details mentioned in the fourth embodiment are still valid in this embodiment, and are not repeated here in order to reduce repetition. Correspondingly, the related technical details mentioned in this embodiment can also be applied in the fourth embodiment.

The ninth embodiment of the present application relates to a version configuration apparatus, as shown in FIG.

The receiving module 901 is configured to receive a configuration command issued by the controller through a third communication protocol, where the third communication protocol carries the version identification code of the configuration information required for version configuration; the extracting module 902 is configured to use to extract the version identification code from the third communication protocol; an acquisition module 903 is used to obtain the configuration information management center identification code of the configuration information management center that stores the configuration information matching the version identification code; The generating module 904 is used for generating the fourth communication protocol for communicating with the configuration information management center according to the configuration information management center identification code and the version identification code; the sending module 905 is used for based on the fourth communication protocol, and issue a configuration information acquisition command to the configuration information management center for the configuration information management center to feed back configuration information matching the version identification code based on the fourth communication protocol; the receiving module 901 is further configured to receive The configuration information matching the version identification code fed back by the configuration information management center through the fourth communication protocol; the configuration module 906 is configured to perform version configuration according to the configuration information.

In addition, in another example, the receiving module 901 is further configured to feed back a configuration result to the controller based on the third communication protocol, for example, the configuration succeeds or the configuration fails.

In addition, in another example, the version configuration apparatus further includes a configuration information detection module.

In this embodiment, the obtaining module 903 is configured to obtain the current version information currently running.

A configuration information detection module, configured to determine whether the current version information is consistent with the version information.

Correspondingly, if it is inconsistent, the triggering configuration module 906 is executed to perform the operation of performing version configuration according to the configuration information; otherwise, the triggering receiving module 901 is executed based on the third communication protocol, to the controller that no version configuration is required. feedback action.

In addition, in another example, the network element device to be configured is a router, and the router includes a main control board and several line cards.

Correspondingly, after receiving the configuration information that matches the version identification code fed back by the configuration information management center through the fourth communication protocol, the receiving module 901 also executes saving the configuration information to the main control board. operation.

Correspondingly, when the configuration module 906 performs version configuration according to the configuration information, it is specifically:

the main control board obtains the line card identification code of each of the line cards;

The main control board generates a fifth communication protocol for communicating with the corresponding line card according to the version identification code and each of the line card identification codes;

The main control board issues the configuration information to each of the line cards based on the fifth communication protocol with each of the line cards, for each of the line cards to perform operations according to the configuration information. version configuration.

It is not difficult to find that this embodiment is a device embodiment corresponding to the fifth embodiment, and this embodiment can be implemented in cooperation with the fifth embodiment. The relevant technical details mentioned in the fifth embodiment are still valid in this embodiment, and are not repeated here in order to reduce repetition. Correspondingly, the related technical details mentioned in this embodiment can also be applied to the fifth embodiment.

It is worth mentioning that all the modules involved in this embodiment are logical modules. In practical applications, a logical unit may be a physical unit, a part of a physical unit, or multiple physical units. A composite implementation of the unit. In addition, in order to highlight the innovative part of the present application, this embodiment does not introduce units that are not closely related to solving the technical problem raised by the present application, but this does not mean that there are no other units in this embodiment.

The tenth embodiment of the present application relates to a version configuration device, as shown in FIG. 10 , comprising: at least one processor 1001 ; and a memory 1002 communicatively connected to the at least one processor 1001 ; wherein the memory 1002 stores a Instructions executed by the at least one processor 1001, the instructions are executed by the at least one processor 1001, so that the at least one processor 1001 can execute the version configuration method described in the above method embodiments.

It should be noted that, in practical applications, the version configuration device mentioned in this embodiment may be any one of an orchestrator, a controller, a configuration information management center, and a network element device to be configured.

Therefore, the processor 1001 in the above-mentioned version configuration device can execute the version configuration method described in the above method embodiment, specifically:

When the version configuration device is an orchestrator, the internal processor 1001 executes the version configuration method applied to the orchestrator, that is, the version configuration method described in the second embodiment above.

Correspondingly, when the version configuration device is a controller, the internal processor 1001 executes the version configuration method applied to the controller, that is, the version configuration method described in the third embodiment above.

Correspondingly, when the version configuration device is the configuration information management center, the internal processor 1001 executes the version configuration method applied to the configuration information management center, that is, the version configuration method described in the fourth embodiment.

Correspondingly, when the version configuration device is the network element device to be configured, the internal processor 1001 executes the version configuration method applied to the network element device to be configured, that is, the version configuration method described in the fifth embodiment.

In addition, it can be understood that in practical applications, the memory 1002 and the processor 1001 are connected by a bus, and the bus may include any number of interconnected buses and bridges. The bus connects one or more processors 1001 and various circuits of the memory 1002 connected. The bus may also connect together various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides the interface between the bus and the transceiver. A transceiver may be a single element or multiple elements, such as multiple receivers and transmitters, providing a means for communicating with various other devices over a transmission medium. The data processed by the processor 1001 is transmitted on the wireless medium through the antenna, and further, the antenna also receives the data and transmits the data to the processor 1001 .

The processor 1001 is responsible for managing the bus and general processing, and may also provide various functions including timing, peripheral interface, voltage regulation, power management, and other control functions. And the memory 1002 may be used to store data used by the processor 1001 when performing operations.

The eleventh embodiment of the present application relates to a computer-readable storage medium storing a computer program. When the computer program is executed by the processor, the version configuration method described in the above method embodiment is implemented.

Similarly, in practical applications, the version configuration device mentioned in this embodiment may be any one of an orchestrator, a controller, a configuration information management center, and a network element device to be configured.

Therefore, in practical applications, the computer storage medium mentioned in this embodiment refers to a computer-readable storage medium suitable for the above-mentioned four versions of the configuration device.

Correspondingly, when the above-mentioned computer program is executed by the processor, the version configuration method described in the above method embodiment is realized, specifically:

When the version configuration device is an orchestrator, when the computer program deployed in the orchestrator is executed by the internal processor, what is specifically implemented is the version configuration method applied to the orchestrator, that is, the version described in the second embodiment above. configuration method.

Correspondingly, when the version configuration device is a controller, when the computer program deployed in the controller is executed by the internal processor, what is specifically implemented is the version configuration method applied to the controller, that is, the above third embodiment. Describes the version configuration method.

Correspondingly, when the version configuration device is the configuration information management center, when the computer program deployed in the configuration information management center is executed by the internal processor, what is specifically implemented is the version configuration method applied to the configuration information management center, that is, The version configuration method described in the fourth embodiment above.

Correspondingly, when the version configuration device is the to-be-configured network element device, when the computer program deployed in the to-be-configured network element device is executed by the internal processor, the version configuration applied to the to-be-configured network element device is specifically implemented. method, that is, the version configuration method described in the fifth embodiment.

That is, those skilled in the art can understand that all or part of the steps in the method for implementing the above embodiments can be completed by instructing the relevant hardware through a program, and the program is stored in a storage medium and includes several instructions to make a device ( It may be a single chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes .

Those of ordinary skill in the art can understand that the above-mentioned embodiments are specific embodiments for realizing the present application, and in practical applications, various changes in form and details can be made without departing from the spirit and the spirit of the present application. scope.

Claims

A version configuration method is applied to an orchestrator in a version configuration system, wherein the version configuration system further includes a controller, a configuration information management center and a network element device to be configured, and the version configuration method includes:

Receive user requirements, and determine a service type identification code corresponding to the user requirement according to a predefined service type set, where the service type set includes the corresponding relationship between each user requirement and each service type identification code;

obtain the identifier of the orchestrator and the identifier of the controller of the controller;

generating a first communication protocol for communicating with the controller according to the orchestrator identification code, the controller identification code and the service type identification code;

Based on the first communication protocol, a configuration command is delivered to the controller for the controller to control the to-be-configured network element device to obtain configuration information from the configuration information management center to perform version configuration.
The method according to claim 1, wherein, before the receiving user requirements, the method further comprises:

Check the validity of the user requirements;

If the user requirement is legal, the step of receiving the user requirement is performed;

Otherwise, the user requirement is rejected.
The method according to claim 2, wherein, before determining the service type identification code corresponding to the user requirement according to the predefined service type set, the method further comprises:

Judging whether the user requirement is an effective requirement according to a preset logic analysis rule;

If the user requirement is a valid requirement, the step of determining the service type identification code corresponding to the user requirement according to the predefined service type set is performed.
A version configuration method is applied to a controller in a version configuration system, wherein the version configuration system further includes an orchestrator, a configuration information management center, and a network element device to be configured, and the version configuration method includes:

receiving a configuration command issued by the scheduler through a first communication protocol, where the first communication protocol carries a service type identification code corresponding to a user requirement;

Extract the service type identification code from the first communication protocol, and determine the version identification code of the configuration information required for version configuration of the to-be-configured network element device according to the service type identification code;

Obtain the controller identification code and the configuration information management center identification code of the configuration information management center;

generating a second communication protocol for communicating with the configuration information management center according to the controller identification code, the configuration information management center identification code and the version identification code;

Based on the second communication protocol, a configuration information search command is issued to the configuration information management center for the configuration information management center to determine whether configuration information matching the version identifier is stored.
The method according to claim 4, wherein after the configuration information search command is issued to the configuration information management center based on the second communication protocol, the method further comprises:

receiving the search result fed back by the configuration management center through the second communication protocol;

If the search result is that the configuration information management center does not store the configuration information matching the version identifier, making a configuration failure response to the orchestrator based on the first communication protocol;

If the search result is that the configuration information management center stores configuration information matching the version identification code, acquiring the network element identification code of the to-be-configured network element device;

generating a third communication protocol for communicating with the to-be-configured network element device according to the controller identification code, the network element identification code and the version identification code;

Based on the third communication protocol, a configuration command is delivered to the to-be-configured network element device for the to-be-configured network element device to obtain configuration information corresponding to the version identifier from the configuration information management center for version configuration.
The method according to any one of claims 4 to 5, wherein before the receiving the configuration command issued by the orchestrator through the first communication protocol, the method further comprises:

Carrying out a constraint check on the validity of the service type corresponding to the service type identification code carried in the first communication protocol;

If the service type is legal, the step of receiving the configuration command sent by the orchestrator through the first communication protocol is performed;

Otherwise, based on the first communication protocol, a response is made to the orchestrator that the service type is invalid.
The method according to claim 6, wherein in said generating the second communication with the configuration information management center according to the controller identification code, the configuration information management center identification code and the version identification code Before the communication protocol, the method further includes:

According to preset logic analysis rules, determine whether the business type is a valid business type;

If so, the step of generating a second communication protocol for communicating with the configuration information management center according to the controller identification code, the configuration information management center identification code and the version identification code is performed.
A version configuration method is applied to a configuration information management center in a version configuration system, wherein the version configuration system further includes an orchestrator, a controller and a network element device to be configured, and the version configuration method includes:

receiving a configuration information search command issued by the controller through a second communication protocol, where the second communication protocol carries a version identification code of configuration information required for version configuration of the to-be-configured network element device;

Extract the version identification code from the second communication protocol, and traverse the locally stored configuration information according to the version identification code;

If the configuration information matching the version identification code is traversed, the configuration information management center stores the configuration information matching the version identification code as a search result;

If the configuration information matching the version identification code is not traversed, the configuration information management center that does not store the configuration information matching the version identification code is used as the search result;

Based on the second communication protocol, the search result is fed back to the controller, so that the controller can respond to the orchestrator for a configuration failure, or control the to-be-configured network element device to manage from the configuration information The configuration information matching the version identification code is obtained in the center for version configuration.
The method according to claim 8, wherein after the feedback of the search result to the controller based on the second communication protocol, the method further comprises:

receiving a configuration information acquisition command issued by the to-be-configured network element device through a fourth communication protocol, where the fourth communication protocol carries a version identification code of configuration information required for version configuration of the to-be-configured network element device;

Based on the fourth communication protocol, the configuration information matching the version identifier is fed back to the to-be-configured network element device for the to-be-configured network element device to perform version configuration.
A version configuration method is applied to a network element device to be configured in a version configuration system, the version configuration system further includes an orchestrator, a controller and a configuration information management center, and the version configuration method includes:

receiving a configuration command issued by the controller through a third communication protocol, where the third communication protocol carries a version identification code of configuration information required for version configuration;

extracting the version identifier from the third communication protocol;

Obtain the configuration information management center identification code of the configuration information management center that stores the configuration information matching the version identification code;

generating a fourth communication protocol for communicating with the configuration information management center according to the configuration information management center identification code and the version identification code;

Based on the fourth communication protocol, issue a configuration information acquisition command to the configuration information management center for the configuration information management center to feed back configuration information matching the version identifier based on the fourth communication protocol;

receiving the configuration information that matches the version identification code fed back by the configuration information management center through the fourth communication protocol;

The version configuration is performed according to the configuration information.
The method according to claim 10, wherein after the version configuration is performed according to the configuration information, the method further comprises:

Based on the third communication protocol, the configuration result is fed back to the controller.
The method according to any one of claims 10 to 11, wherein before the version configuration is performed according to the configuration information, the method further comprises:

Get the current version information that is currently running;

Determine whether the current version information is consistent with the version information;

If it is inconsistent, execute the step of performing version configuration according to the configuration information;

Otherwise, based on the third communication protocol, feedback is made to the controller that version configuration is not required.
The method according to any one of claims 10 to 12, wherein the network element device to be configured is a router, and the router includes a main control board and several line cards;

After receiving the configuration information that matches the version identification code fed back by the configuration information management center through the fourth communication protocol, the method further includes:

saving the configuration information to the main control board;

The performing version configuration according to the configuration information includes:

the main control board obtains the line card identification code of each of the line cards;

The main control board generates a fifth communication protocol for communicating with the corresponding line card according to the version identification code and each of the line card identification codes;

The main control board issues the configuration information to each of the line cards based on the fifth communication protocol with each of the line cards, for each of the line cards to perform operations according to the configuration information. version configuration.
A version configures the device, including:

at least one processor; and,

a memory communicatively coupled to the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform any one of claims 1 to 3 The version configuration method, or the version configuration method described in any one of claims 4 to 7, or the version configuration method described in any one of 8 and 9, or the version configuration method described in any one of 10 to 13.
A version configuration system, the version configuration system includes: an orchestrator, a controller, a configuration information management center, and a network element device to be configured;

the orchestrator, configured to execute the version configuration method according to any one of claims 1 to 3;

The controller is configured to execute the version configuration method according to any one of claims 4 to 7;

The configuration information management center is used to execute the version configuration method according to any one of claims 8 and 9;

The to-be-configured network element device is used to execute the version configuration method according to any one of claims 10 to 13.
A computer-readable storage medium storing a computer program, when the computer program is executed by a processor, the version configuration method described in any one of claims 1 to 3, or the version described in any one of claims 4 to 7 is realized The configuration method, or the version configuration method described in any one of 8 and 9, or the version configuration method described in any one of 10 to 13.