Time-sensitive network configuration management system and method

[0052] The embodiments of the present invention will be easily understood by those skilled in the

[0053] The drawings are intended to be illustrative only, rather than illustrative, not to be understood, in order to better illustrate embodiments of the invention, and other components of the present invention will be omitted. Enlarge or shrink does not represent the size of the actual product; some well-known structures and descriptions thereof may be understood in the drawings in the drawings.

[0054] The same or similar components in the drawings of the embodiments correspond to the same or similar components; in the description of the present invention, it is to be understood that if there is a term "upper", "lower", "left", "right" , "Before", "Post", etc. The direction or position is based on the orientation or positional relationship shown in the drawings, is merely described in order to facilitate the description of the present invention, not indicating or implies that the device or component must be Has a specific orientation, constructed and operated in a particular direction, thus describing the use of positional relationships is for exemplary description, and is not to be understood that the limitation of the invention will be, and those of ordinary skill in the art can be based on specific The situation is understood to understand the specific meaning of the above terms.

[0055] See Figure 1 ~ 3 The present invention proposes a NETCONF protocol network architecture, such as figure 1 As shown, the network architecture consists of two parts of the network management client and multiple network management servers. Each TSN switch is installed with a network management server, and the TSN stream is transmitted between each TSN switch. The network management client is configured by the user, RPC (Remote Process Call) Message Processor, Session Communication Layer Composition, MDNS (Multicast Domain Name System) module, the network management server consists of a session communication layer, an RPC message processor, an operation manager, a managed object module, and an MDNS module.

[0056] In the network management client, the RPC message processor and session communication layer form a NetConf client, while the MDNS module and the MDNS module in the network management server are used for the network management client to obtain port IP of the network management server. The client configures the specified device; the session communication layer, the RPC message processor, the operation manager, and the managed object module in the network management server form a NETCONF server.

[0057] In a local area network, the MDNS module in the NMS client is sent to MDNS messages between the MDNS modules in the network management server, and the NMS client automatically obtains the port IP address of the network management server. The network management client's session communication layer implements an SSH (Security Housing Protocol) client, the network management server session communication layer implements an SSH server, used for authentication of user identity and encryption of data, ensuring security in data transfer.

[0058] The user first selects a specific device in the user configuration interface, establishes the SSH secure connection, then configures the TSN parameter, the RPC request information is sent to the NETCONF server side in the form of an XML file, the server side obtains the RPC request attribute, RPC request Attributes include message numbers, operation types, configuration status, operation object 4, which subsequently generates the corresponding operational command, and finally perform the operation command to implement remote configuration of the device.

[0059] Time-sensitive network configuration management system design includes:

[0060] MDNS Protocol Module: The NMS client MDNS protocol module is used to request a service to the entire LAN, and the network management server registers the IP address of the device into the MDNS module. When the MDNS protocol in the network management server is the same as the former supplied to the LAN announcement The MDNS module in the network management client automatically obtains the IP address of the network management server.

[0061] User Configuration Interface: Responsible for interacting with the user, showing the system information to the user, and provides the network management operation interface, the user configuration interface is based on the user's operation, the operational request is created, and passed to the RPC message processor, waiting for the response of the network management server returned. The message is presented to the user.

[0062] Tube Client RPC Message Processor: Responsible for handling the RPC message of the network management client, complete the following two functions: (1) Generate an RPC request message. It is responsible for receiving an operation request, encapsulating the RPC request message, and sends a session communication layer in the format of the XML file. (2) Analyze the RPC response message. The RPC message processor waits to receive the RPC response message, then verify the format of the RPC response message, parses the results of the configuration operation, passed to the user configuration interface display.

[0063] NMS client session communication layer: Responsible for establishing a connection with the network management server, completing the transmission of management information. When the message processor has an RPC request message, the session communication layer encapsulates it to request packets, sent to the network management server side; then wait for the response message of the agent to extract the RPC response message, pass to the RPC message processor.

[0064] NMS server session communication layer: When the network management server starts, the session communication layer opens a listening thread, waiting for the request message sent by the network management client, decrypt the RPC request message, and passed to the RPC message processor; then wait RPC The response message of the message processor is encrypted into the network management client.

[0065] NMS server-side RPC message processor: Responsible for handling the RPC message of the network management server, completes the following two functions: (1) Resolving the RPC request message passed from the session communication layer. First verify the format of the RPC request message, when the format is correct, extract the parameters of the configuration operation, passed to the Operator Manager. (2) Generate an RPC response message. It waits for the configuration operation result of the receiving operation manager, and packages it to the RPC response message to the session communication layer.

[0066] Operation Manager: Responsible for completing two functions: (1) The operational parameters transmitted by the RPC message processor are responsible for generating a command to generate a configuration operation and call the method provided by the managed object module. (2) Return the configuration operation result passed by the managed object module to the RPC message processor.

[0067] Tube Object Module: Responsible for the storage and processing of managed information for network devices. It consists of several management object modules, each managing the configuration information of a data model information packet, and is responsible for completing the actual processing operation of management information. The management object processor provides the operation manager with an interface to access management information. This interface is responsible for receiving the configuration command of the Operator Manager and calls the managed object module to perform the operation of the management information.

[0068] The time-sensitive network configuration management process includes two major parts. First, the network management client automatically acquires the network management server IP address in a local area; then use the device IP configuration specified by the device IP acquired, such as figure 2 As shown, the specific steps are as follows:

[0069] Step 1: The network management server registers the following information to MDNS: Provide SSH service, the IP address is 192.168.0.1, the port is 22;

[0070] Step 2: The network management client lays a request to his own MDNS service to find SSH services;

[0071] Step 3: The network management server is consistent with the service provided by the network management client, and the network management server sends its own IP address 192.168.0.1 and port number 22 to the network management client. Thus, the network management client gets the IP address of the NMS server, and the network management client can configure a particular network management server;

[0072] Step 4: The network management client establishes an SSH connection in a session communication layer with the IP address in step 3 in step 3;

[0073] Step 5: The RPC message processor in the network management client encapsulates the user requests to an RPC operation request. The RPC operation request is an XML file data request, which converts the YANG file in the TSN standard into an XML framework, and user Configure parameters combine to convert to actual XML files;

[0074] Step 6: Encrypt the RPC operation request on the session communication layer, the session communication layer implements an SSH client, combined with the network management server-side session communication layer, establishes a safety tunnel for information transmission and user identity. ;

[0075] Step 7: The network management server side session communication layer decrypts the RPC operation request;

[0076] Step 8: The RPC operation processor is responsible for resolving the RPC request, and its RPC message analysis process is like image 3 As shown, the RPC request message is verified with the XML Schema file of RFC4741. If the NetConf is consistent, the RPC element part in the document is parsed, and the message-id, namespace name, and namespace content in the RPC element are performed. And save. Then take the internal operation type to pass to the Operator Manager. The RPC element request attribute includes: an operation type and an operation object. The type of operation includes several types such as , , , and , the operation object represents the management object of the configuration operation;

[0077] Step 9: Operation Manager generates a configuration operation command according to the extracted configuration operation parameters; the NetConf protocol defines 9 basic operations, each of which is different, generates different operational commands;

[0078] Step 10: Call the managed object module to configure the device by the operation manager;

[0079] Step 11: Returns the configuration operation result to the operation manager;

[0080] Step 12: Operation Manager sends the configuration operation result to the RPC operating processor;

[0081] Step 13: If the operation manager successfully calls the managed object module execution command, the RPC message processor returns the correct RPC-Reply packet. The RPC Operator Manager then performs the returned response packet package package, and then sends it to the session communication layer. If the error is checked or the manager error is checked on a part, it is unified to be encapsulated into an error handling message, and sends it to the session communication layer;

[0082] Step 14: Session Communication Layer Encryption Package RPC-Reply Response Packet;

[0083] Step 15: The session communication layer of the network management client decrypts the extracting the RPC-Reply response message and presents the interface.

[0084] Not, the above embodiments are intended to illustrate the technical solutions of the present invention, not limiting, although the present invention will be described in detail, and those skilled in the art will appreciate that the technical solutions of the present invention can be carried out. Modify or equivalent replacement, without departing from the purposes and scope of the invention, it should be included in the scope of the invention.