CN101977160B - Reconfigurable method for routing protocol software components in reconfigurable route switching platform - Google Patents

Abstract

The invention relates to a reconfiguration method for routing protocol software components in a reconfigurable route switching platform, comprising the following steps: universal software component operating environment is established on the reconfigurable route switching platform; the software component operating environment communicates with a certain quantity of routing protocol software components and an operating system; a component agency is responsible for the reconfiguration control process of the routing protocol software components, communicates with a reconfigurable management platform to be responsible for receiving reconfiguring instructions of the reconfigurable management platform, and also communicated with the routing protocol software components and the software component operating environment so as to send and notify the communication addresses of different routing protocol software components to the routing protocol software components and the software component operating environment; and the component agency dynamically load and delete the routing protocol software components as well as start and stop the routing protocol software components by controlling the software component operating environment. The reconfiguration method for the routing protocol software components in the reconfigurable route switching platform provided by the invention has the advantages that the reconfiguration structure is simple, various components are supported, and the expansibility is strong.

Description

Routing Protocol Software Component Reconfiguration Method in Reconfigurable Routing and Switching Platform

(1) Technical field: The present invention relates to a method for reconfiguring routing protocol software components, in particular to a method for reconfiguring routing protocol software components in a reconfigurable routing switching platform.

(2) Background technology: The network architecture design should be change-oriented, scalable, and able to

Provide flexible services to support most existing and future businesses. The network must get rid of the endless business development constraints, be able to cluster different processing tasks and network services, and build a network architecture with features such as scalable scale, reconfigurable functions, and customizable services.

The architecture of network node equipment should conform to the principle of scalability and support the

Upgrades and functionality, performance extensions. The current network node equipment adopts dedicated software/hardware design, and its architecture is tightly coupled and lacks flexibility. The reconfigurable routing and switching platform adopts open standards and building block models. The modules are interoperable and the software is reusable. Developers can integrate software/hardware modules from different manufacturers in the switching platform to easily upgrade, expand or reorganize the switching platform. structure and services. The component technology in the reconfigurable routing and switching platform is to make the router design and development like the machinery manufacturing industry, which can be assembled with various standard and non-standard parts, or like the construction industry, it can be built with various building materials. All kinds of buildings. The goal of componentization of routing and switching systems is to conveniently and dynamically integrate functional components provided by different manufacturers, different units or individuals, and implemented on different operating systems or hardware platforms into an organism. These components are required to be interoperable. Realizing the componentization of routing and switching functions is a cutting-edge system design idea, which plays a vital role in promoting the healthy development of routing and switching equipment manufacturing and the entire network industry.

In a reconfigurable routing and switching platform composed of components, when the platform is reconfigured as needed, the components are

Basic elements and objects for row refactoring operations. We need a way to efficiently manage components and make the refactoring process simple, fast and reliable.

(3) Contents of the invention:

The technical problem to be solved by the present invention is: to overcome the defects of the prior art, to provide a simple reconstruction structure

A method for reconfiguring routing protocol software components in a reconfigurable routing switching platform that supports multiple components and has strong scalability.

Technical scheme of the present invention:

A method for reconfiguring routing protocol software components in a reconfigurable routing switching platform, in reconfigurable routing

A common software component operating environment is established on the exchange platform. The software component operating environment communicates with a certain number of routing protocol software components and the operating system. The component agent manages the routing protocol software components. The component agent is responsible for the reconfiguration control process of the routing protocol software components. The component agent communicates with the reconfigurable management platform and is responsible for receiving the reconfiguration instructions of the reconfigurable management platform. The component agent also communicates with the routing protocol software components and the software component operating environment, and issues and The communication addresses of different routing protocol software components are notified, and the component agent dynamically loads and deletes routing protocol software components, starts and closes routing protocol software components by controlling the software component operating environment.

The reconstruction control process of the routing protocol software component by the component agent is as follows:

Step a: Detect and parse the command: the component agent detects and parses the reconfiguration instruction sent by the reconfigurable management platform, and verifies the legality of the reconfiguration instruction; if it is legal, execute step b; if it is not legal, the component agent deletes the relevant analysis result , and feed back the illegal information to the reconfigurable management platform, and then execute step i;

Step b: Receive the software reconstruction description file and extract relevant information: the component agent receives the software reconstruction description file sent by the reconfigurable management platform. The software reconstruction description file contains reconstruction method information, and the component agent extracts the software reconstruction description Number information, type information and component port connection relationship information of routing protocol software components in the file;

Step c: Judging whether the components are complete, and extracting component description information: the component agent judges whether the routing protocol software components delivered by the reconfigurable management platform are complete; if not complete, perform step i; if complete, the component agent downloads the component description file, And extract resource requirement information and component ID information, and then execute step d;

Step d: Judging the situation of reconfiguration resources: the component agent judges whether the reconfiguration resources of the software component operating environment can support this reconfiguration; if not, return the information that the resources do not meet the requirements to the reconfigurable management platform, and then execute the step i; if supported, execute step e;

Step e: receiving component code: the component agent receives the routing protocol software component code issued by the reconfigurable management platform;

Step f: Deploy the component: the component agent starts the routing protocol software component in the software component operating environment according to the software reconstruction description file and the component description file;

Step g: feedback the reconstruction result: the component agent checks whether the routing protocol software component is successfully reconstructed, and feeds back the reconstruction result to the reconfigurable management platform; if not successful, execute step i; if successful, execute step h;

Step h: data switching: switching network data to the reconfigured routing protocol software component;

Step i: end.

Reconfiguration resources include storage resources and computing resources.

The software component operating environment contains component operation management interface, user control interface interface, service mapping layer and protocol message sending and receiving interface. The routing protocol software component registers the component operation management interface with the software component operating environment when it is started, and the routing protocol software component registers the component operation management interface with the software component operating environment. The control interface interface communicates with the user control interface. Through the user control interface interface, the device administrator can configure and manage the routing protocol software components in the command line interface of the device. Each routing protocol software component follows the same user control interface interface. Standard, the service mapping layer defines the communication protocol between the routing protocol software component and the software component operating environment, and the routing protocol software component accesses the operating system kernel protocol stack through the protocol message sending and receiving interface of the software component operating environment to obtain the protocol message .

The component agent includes a management interface and a component deployment management module. The component deployment management module communicates with the management interface. The component deployment management module includes a component certification program, a resource request program and a component execution program. After the program is completed, enter the component execution program. Component agent has management function, monitoring function and business composition function.

Reconstruction instructions include component authentication instructions, component query instructions, component deletion instructions and component execution instructions.

Routing protocol software components include OSPF protocol components and RIP protocol components.

The OSPF protocol component contains the interface connected with the user control interface, the interface connected with the component agent, the interface connected with the routing management component and the interface connected with the software component operating environment, and the routing management component is connected with the software component operating environment and connected with the component agent The interface of the interface and the interface connected with the routing management component are the Agent client interface.

The software component operating environment has a standard communication interface. Under the premise of following the standard communication interface, the protocol components developed by any development organization can run on the same routing and switching platform.

There are two types of communication data used in the present invention, as follows:

Type A: reconstruction messages between component agents and routing protocol software components, and between routing protocol software components; the reconstruction message is a control message, and the reconstruction message is composed of a message header and a message body, and the message header has a uniform format , which mainly includes the message type, sender ID, receiver ID, and message length.

Type B: Protocol messages and control messages between routing protocol software components and software component operating environments, and between software component operating environments and operating systems. The format of the protocol messages and control messages is traditional protocol messages and the format of traditional control messages.

The format of the message header of the reconstructed message of type A is as follows:

Version number: 4 bits, the current version is 1.

Rsvd reserved field: 4 bits, the sender must set this field to zero, and the receiver must ignore this field.

Message Type Message type: 8bit.

Its value is defined as follows:

0x00 Reserved Reserved

0x01 AssociationSetup Start link building

0x02 AssociationTeardown Teardown link

0x03 Config Config

0x04 Query Query

0x05 Event Notification Event Notification

0x06 PacketRedirect Packet Redirection

0x07 - 0x0E Reserved Reserved

0x0F Heartbeat Heartbeat

0x11 AssociationSetupRepsonse Start link establishment response

0x12 Reserved Reserved

0x13 ConfigRepsonse ConfigRepsonse

0x14 Query- Query response

Length: The length of the message.

Source ID: Source artifact ID.

Destination ID: target component ID0.

Correlator: Correlation factor.

Purpose of Correlator: Request message and Response message must have the same correlator value. Message segmentation: the first 32 bits are the same, but the last 32 bits are different. Different messages for the same transaction, ex

The 32 bits are the same, but the last 32 bits are different. The difference from message segmentation is that AT=1. In other cases, the correlator can be 0.

ACK (acknowledgment flag, 4bit): ACK is used to indicate whether the component needs to reply.

ACK can be set to the following values:

NoACK (0b00): Indicates that the destination component does not need to send any response message.

SuccessACK (0b01): Indicates that a response message must be returned only when the sent message has been successfully processed. The so-called success means that all operations in the same message are all successful.

FailureACK (0b10): Indicates that only when the sent message fails to be processed, a response message must be returned.

AlwaysACK (0b11): Indicates that the destination component must send a response message to the source component.

Pri (priority flag, 4bit): The control protocol defines 8 different priorities (0-7); the higher the priority value, the more important the content of the protocol message.

Revd: Reserved field, filled with 0.

Beneficial effects of the present invention:

1. The present invention adopts component agents to control the reconfiguration process of routing protocol software components, and is also provided with a software component operating environment. The component agents communicate with the reconfigurable management platform, are responsible for receiving reconfiguration instructions from the reconfigurable management platform, and send The routing protocol software component and the software component operating environment issue and notify the communication addresses of different routing protocol software components. Therefore, the component management efficiency of the present invention is high, and the steps of the reconfiguration process are simple, fast and reliable.

(4) Description of drawings:

Figure 1 is a schematic diagram of the control relationship among the reconfigurable management platform, component agent, software component operating environment, and routing protocol software components;

Fig. 2 is the interface schematic diagram of OSPF protocol component;

Fig. 3 is a schematic diagram of the message header format of the reconstruction message of the communication data type A used in the present invention;

Fig. 4 is a schematic diagram of the structure of the common header of the standard communication message of the service mapping layer.

(5) Specific implementation methods:

Embodiment 1: Refer to Figure 1 to Figure 4. In the figure, the routing protocol software in the reconfigurable routing switching platform

The software component reconfiguration method is as follows: establish a common software component operating environment on the reconfigurable routing exchange platform, the software component operating environment communicates with a certain number of routing protocol software components and operating systems, the component agent manages the routing protocol software components, and the components The agent is responsible for the reconfiguration control process of the routing protocol software components. The component agent communicates with the reconfigurable management platform and is responsible for receiving the reconfiguration instructions from the reconfigurable management platform. The component agent also communicates with the routing protocol software components and the software component operating environment to send Routing protocol software components and software component operating environments issue and notify the communication addresses of different routing protocol software components, and the component agent dynamically loads and deletes routing protocol software components, starts and closes routing protocol software components by controlling the software component operating environment.

The reconstruction control process of the routing protocol software component by the component agent is as follows:

Step a: Detect and parse the command: the component agent detects and parses the reconfiguration instruction sent by the reconfigurable management platform, and verifies the legality of the reconfiguration instruction; if it is legal, execute step b; if it is not legal, the component agent deletes the relevant analysis result , and feed back the illegal information to the reconfigurable management platform, and then execute step i;

Step b: Receive the software reconstruction description file and extract relevant information: the component agent receives the software reconstruction description file sent by the reconfigurable management platform. The software reconstruction description file contains reconstruction method information, and the component agent extracts the software reconstruction description Number information, type information and component port connection relationship information of routing protocol software components in the file;

Step c: Judging whether the components are complete, and extracting component description information: the component agent judges whether the routing protocol software components delivered by the reconfigurable management platform are complete; if not complete, perform step i; if complete, the component agent downloads the component description file, And extract resource requirement information and component ID information, and then execute step d;

Step d: Judging the situation of reconfiguration resources: the component agent judges whether the reconfiguration resources of the software component operating environment can support this reconfiguration; if not, return the information that the resources do not meet the requirements to the reconfigurable management platform, and then execute the step i; if supported, execute step e;

Step e: receiving component code: the component agent receives the routing protocol software component code issued by the reconfigurable management platform;

Step f: Deploy the component: the component agent starts the routing protocol software component in the software component operating environment according to the software reconstruction description file and the component description file;

Step g: feedback the reconstruction result: the component agent checks whether the routing protocol software component is successfully reconstructed, and feeds back the reconstruction result to the reconfigurable management platform; if not successful, execute step i; if successful, execute step h;

Step h: data switching: switching network data to the reconfigured routing protocol software component;

Step i: end.

Reconfiguration resources include storage resources and computing resources.

The software component operation environment contains component operation management interface, user control interface interface, service mapping layer and protocol message sending and receiving interface. When starting, the routing protocol software component registers the component operation management interface with the software component operation environment, and the component agent can use the component operation The management interface manages the routing protocol software components. The routing protocol software components communicate with the user control interface through the user control interface interface. Through the user control interface interface, the device administrator can perform corresponding operations on the routing protocol software components in the command line interface of the device. Configuration and management, each routing protocol software component follows the same user control interface interface standard, the communication protocol between the routing protocol software component and the software component operating environment is defined in the service mapping layer, and the routing protocol software component passes through the protocol of the software component operating environment The message sending and receiving interface accesses the operating system kernel protocol stack to obtain protocol messages.

The component agent includes a management interface and a component deployment management module. The component deployment management module communicates with the management interface. The component deployment management module includes a component certification program, a resource request program and a component execution program. After the program is completed, enter the component execution program. Component agent has management function, monitoring function and business composition function.

Reconstruction instructions include component authentication instructions, component query instructions, component deletion instructions and component execution instructions.

Routing protocol software components include OSPF protocol components and RIP protocol components.

The OSPF protocol component contains the interface connected with the user control interface, the interface connected with the component agent, the interface connected with the routing management component and the interface connected with the software component operating environment, and the routing management component is connected with the software component operating environment and connected with the component agent The interface of the interface and the interface connected with the routing management component are the Agent client interface.

The interface connected with the user control interface is described as follows:

Interface method: use the connection-based streaming socket for IPv4 domain in the Socket API interface.

Interface function: When the daemon process of the OSPF protocol component starts running, it provides a channel for the network administrator to configure, intervene, and view the operating status of OSPF through commands.

When the OSPF protocol component runs as a process, during module initialization, the component establishes a tcp connection with the user control interface through the socket, and monitors all commands from the port. When listening to a command, OSPF receives the command by reading the thread, and then the protocol process searches the command tree according to the received command string, thereby executing the corresponding function, thereby completing the configuration of the OSPF protocol and the management of the running status.

The interface connected with component proxy is described as follows:

Interface mode: use the Agent client to establish communication with the component agent, and use the message format customized by the Agent client in the communication.

Interface function: when the component is initialized, a registration message is sent to the component agent through this interface. After the component agent receives the registration message, it sends a message to the current component through this interface, so that it knows the address of the component it will communicate with. The component agent can send the configuration file to the component through this interface, and order the component to read the configuration file. At the same time, the component agent can also close the component through this interface.

The interface connected with the routing management component is described as follows:

Interface mode: use the Agent client to establish communication with the routing management component, and use the message format customized by the service mapping layer in the communication.

Interface function: The reconfigurable routing switching platform provides services such as interfaces and routing information for each routing protocol through the routing management component. At the same time, it collects the routing information of each protocol to generate a unified routing table and sends it to each hardware forwarding component. The OSPF component communicates with the routing management component in the form of sending and receiving messages through the Agent client, and submits the obtained routing information; the routing management component provides the OSPF component with the interface information of the system and the redistributed routing information through the Agent client.

The interface connected with the software component operating environment is described as follows:

Interface method: use the connection-based streaming socket for IPv4 domain in the Socket API interface.

Interface function: SCRE is between the operating system and protocol components; it acts as a bottom shield for the operating system. In this way, the connection between the OSPF protocol component and the operating system is carried out through SCRE, and there is no need to care about which operating system is used. This interface mainly realizes the connection between the OSPF protocol component and the TCP/IP protocol stack of the operating system to receive and send data packets, and provides memory and timer management during the operation of the protocol module.

The software component operating environment has a standard communication interface. Under the premise of following the standard communication interface, the protocol components developed by any development organization can run on the same routing and switching platform.

There are two types of communication data used in the present invention, as follows:

Type A: reconstruction messages between component agents and routing protocol software components, and between routing protocol software components; the reconstruction message is a control message, and the reconstruction message is composed of a message header and a message body, and the message header has a uniform format , which mainly includes the message type, sender ID, receiver ID, and message length.

Type B: Protocol messages and control messages between routing protocol software components and software component operating environments, and between software component operating environments and operating systems. The format of the protocol messages and control messages is traditional protocol messages and the format of traditional control messages.

The format of the message header of the reconstructed message of type A is as follows:

Version number: 4 bits, the current version is 1.

Rsvd reserved field: 4 bits, the sender must set this field to zero, and the receiver must ignore this field.

Message Type Message type: 8bit.

Its value is defined as follows:

0x00 Reserved Reserved

0x01 AssociationSetup Start link building

0x02 AssociationTeardown Teardown link

0x03 Config Config

0x04 Query Query

0x05 Event Notification Event Notification

0x06 PacketRedirect Packet Redirection

0x07 - 0x0E Reserved Reserved

0x0F Heartbeat Heartbeat

0x11 AssociationSetupRepsonse Start link establishment response

0x12 Reserved Reserved

0x13 ConfigRepsonse ConfigRepsonse

0x14 Query- Query response

Length: The length of the message.

Source ID: Source artifact ID.

Destination ID: target component ID0.

Correlator: Correlation factor.

Purpose of Correlator: Request message and Response message must have the same correlator value. Message segmentation: the first 32 bits are the same, but the last 32 bits are different. Different messages for the same transaction, ex

The 32 bits are the same, but the last 32 bits are different. The difference from message segmentation is that AT=1. In other cases, the correlator can be 0.

ACK (acknowledgment flag, 4bit): ACK is used to indicate whether the component needs to reply.

ACK can be set to the following values:

NoACK (0b00): Indicates that the destination component does not need to send any response message.

SuccessACK (0b01): Indicates that a response message must be returned only when the sent message has been successfully processed. The so-called success means that all operations in the same message are all successful.

FailureACK (0b10): Indicates that only when the sent message fails to be processed, a response message must be returned.

AlwaysACK (0b11): Indicates that the destination component must send a response message to the source component.

Pri (priority flag, 4bit): The control protocol defines 8 different priorities (0-7); the higher the priority value, the more important the content of the protocol message.

Revd: Reserved field, filled with 0.

The definition and related functions of the component operation management interface are introduced as follows:

Component operation management interface data structure description

Typedef struct {

Int (*component_init)( char *workdir, struct sockaddr_in *container);

Int (*component_stop)();

Int (*component_restart)();

Int (*component_poll)();

Int (*component_writeconfig)(char *conffile);

Int (*component_readconfig)(char *conffile);

Int (*component_showrun)(char *strbuff, int maxlen, int *runlen);

Int (*component_readstatistics)(struct NCI_statistics_info *info);

Int (*component_vendorinfo)(char *strbuff,int maxlen,int *runlen);

}NCI_Component_Admin_Interface;

The callback function in the component operation management interface data structure is introduced as follows:

component_init: notify the protocol component initialization, where workdir specifies the working directory where the protocol component runs, and container gives the access address of the service mapping layer;

component_stop: notify the protocol component to stop running and exit;

component_restart: notify the protocol component to restart to the state before initialization;

component_poll: detect whether the protocol component is active;

component_writeconfig: notify the protocol component to write the configuration information into the conffile;

component_readconfig: notify the protocol component to load configuration information in conffile;

component_showrun: notify the protocol component to display the current running configuration status information, strbuff gives the buffer of the running configuration status information, maxlen indicates the maximum length of the buffer, and runlen returns the length of the actual running configuration status information;

component_readstatistics: Read the operating status statistics of protocol components, including: memory usage, CPU usage, routing table usage, message sending and receiving, etc.;

component_vendorinfo: notify the protocol component to display the vendor information of the protocol component, strbuff gives the buffer for storing the vendor information, maxlen indicates the maximum length of the buffer, and runlen returns the actual length of the vendor information.

There is a command structure in the user control interface interface library used by the routing protocol software component to maintain the command list of the entire protocol component. Each protocol component maintains its own command vector, called cmdvec. A command vector consists of a sequence of command nodes. Command nodes in turn may install corresponding command elements.

The command node data structure is shown in the table:

structure member describe Node_type node type Prompt prompt information function corresponding function Cmd_vector command vector

The Cmd_vector of a command node in turn includes a list of command elements installed into that node. The command element data structure is shown in the table:

structure member describe String command string function command element corresponding function Daemon The daemon to which the command element belongs ... ...

When the routing protocol software component establishes the configuration command of this protocol, it first initializes top_level_vector: cmdvec. The command node is then installed in the vector using the install_node() function. And utilize the install_element() function to install commands in specific nodes.

During the operation of the reconfigurable protocol components, the VTY of the routing and switching platform continuously queries user input. Once the user enters the command tree of this protocol component through the command tree path on the VTY interface, any command input by the user will read the input command string from the user interface, and then use the The associated command handler executes the command. The command processing function first verifies whether the command data structure filled in cmdvec matches the user input command. If the command is valid, select the corresponding command element from the command node, execute the command, and return the result to the VTY terminal.

The service mapping layer defines the routing exchange platform's own communication protocol - "component routing and interface access" protocol, which handles the communication between the service mapping layer and components. Each component is the client, and the service mapping layer is the server.

The service mapping layer communicates with the routing protocol software components through standard TCP/IP Socket. During the communication, the routing protocol software component acts as the client of both communication parties, and the service mapping layer acts as the server of both communication parties, monitoring the communication connection between the routing protocol software component and the service mapping layer on the designated Socket port. After the routing protocol software component and the Socket communication connection of the service mapping layer are established, information can be exchanged based on the standard communication message format. All data fields in the standard communication message header follow the network byte order, and the key data fields of the standard message header are described as follows:

l Message length: 16-bit integer, which defines the byte length of all service mapping layer messages including standard message headers;

l Protocol ID: 8-bit integer, which defines the protocol ID of the service mapping layer communication message, currently defined as 0xFF;

l Protocol version: 8-bit integer, which defines the protocol version number of the service mapping layer communication message, currently positioned as 0x01;

l Interface command word: 16-bit integer, defining the interface command type contained in the subsequent command data field;

l Command data field: variable length data field, the specific command data is determined by the interface command word 80;

The content (main interface functions and functions) contained in the command data field is listed as follows:

serial number name Function 1 NCI_INTERFACE_ADD Router Adds Interface Advertisement 2 NCI_INTERFACE_DELETE Router Interface Deletion Advertisement 3 NCI_INTERFACE_ADDRESS_ADD interface address increase notification 4 NCI_INTERFACE_ADDRESS_DELETE Interface Address Deletion Notification 5 NCI_INTERFACE_UP interface state availability notification 6 NCI_INTERFACE_DOWN interface state unavailable notification 7 NCI_IPV4_ROUTE_ADD Added route advertisement command for IPv4 route redistribution 8 NCI_IPV4_ROUTE_DELETE IPv4 route redistribution cancel route advertisement command 9 NCI_IPV6_ROUTE_ADD New route advertisement command for IPv6 route redistribution 10 NCI_IPV6_ROUTE_DELETE IPv6 route redistribution delete existing route advertisement command 11 NCI_REDISTRIBUTE_ADD Route redistribution status setting notification command 12 NCI_REDISTRIBUTE_DELETE Route redistribution status deletion notification command 13 NCI_REDISTRIBUTE_DEFAULT_ADD Default route redistribution new notice 14 NCI_REDISTRIBUTE_DEFAULT_DELETE Default route redistribution delete notice 15 NCI_IPV4_NEXTHOP_LOOKUP Next hop status query command 16 NCI_IPV6_NEXTHOP_LOOKUP IPv6 next hop status query command 17 NCI_IPV4_IMPORT_LOOKUP Routing status query command 18 NCI_IPV6_IMPORT_LOOKUP IPv6 routing status query command 19 NCI_MPLS_ENABLE MPLS Protocol Enabling Notification 20 NCI_MPLS_DISABLE MPLS Protocol Closing Notification twenty one NCI_MPLS_LABLE_ADD MPLS protocol adds label entry notification twenty two NCI_MPLS_LABLE_DEL MPLS Protocol Deletion Label Entry Notification twenty three NCI_VRF_NEW Create a new VRF advertisement twenty four NCI_VRF_DEL Delete a VRF advertisement 25 NCI_VRF_RT_ADD Added route advertisement command in a VRF 26 NCI_VRF_RT_DEL Delete route advertisement command in a VRF

The main interface functions of the protocol message sending and receiving interface are defined as follows:

serial number name Function 1 NCI_Socket Create NCI_Socket 2 NCI_Accept Accept connection requests to the socket 3 NCI_Bind Bind a socket to a local address 4 NCI_Connect Connect a socket to a remote host 5 NCI_Getsockname Get the address of the specified socket 6 NCI_Select Determine the status of the Socket, waiting for I/O operations 7 NCI_Recv Receive data from a connected or bound socket 8 NCI_Recvfrom Receive UDP packets and save the source address 9 NCI_Send Send data to the connected socket 10 NCI_Sendto Send data to UDP socket 11 NCI_Listen Put a socket into listening state 12 NCI_Closesocket close existing socket

Claims (8)

1. A routing protocol software component reconfiguration method in a reconfigurable routing exchange platform is characterized in that: a general software component operating environment is set up on the reconfigurable routing exchange platform, the software component operating environment and a certain number of routing The protocol software component communicates with the operating system, and the component agent manages the routing protocol software component. The component agent is responsible for the reconfiguration control process of the routing protocol software component. The component agent communicates with the reconfigurable management platform and is responsible for receiving the reconfiguration instructions of the reconfigurable management platform. , the component agent also communicates with the routing protocol software components and the software component operating environment, issues and notifies the communication addresses of different routing protocol software components to the routing protocol software components and the software component operating environment, and the component agent dynamically loads the software components by controlling the software component operating environment and delete the routing protocol software component, start and close the routing protocol software component; the reconstruction control process of the routing protocol software component by the component agent is as follows: Step a: Detect and parse the command: the component agent detects and parses the reconfiguration instruction sent by the reconfigurable management platform, and verifies the legality of the reconfiguration instruction; if it is legal, execute step b; if it is not legal, the component agent deletes the relevant analysis result , and feed back the illegal information to the reconfigurable management platform, and then execute step i; Step b: Receive the software reconstruction description file and extract relevant information: the component agent receives the software reconstruction description file sent by the reconfigurable management platform. The software reconstruction description file contains reconstruction method information, and the component agent extracts the software reconstruction description Number information, type information and component port connection relationship information of routing protocol software components in the file; Step c: Judging whether the components are complete, and extracting component description information: the component agent judges whether the routing protocol software components delivered by the reconfigurable management platform are complete; if not complete, perform step i; if complete, the component agent downloads the component description file, And extract resource requirement information and component ID information, and then execute step d; Step d: Judging the situation of reconfiguration resources: the component agent judges whether the reconfiguration resources of the software component operating environment can support this reconfiguration; if not, return the information that the resources do not meet the requirements to the reconfigurable management platform, and then execute the step i; if supported, execute step e; Step e: receiving component code: the component agent receives the routing protocol software component code issued by the reconfigurable management platform; Step f: Deploy the component: the component agent starts the routing protocol software component in the software component operating environment according to the software reconstruction description file and the component description file; Step g: feedback the reconstruction result: the component agent checks whether the routing protocol software component is successfully reconstructed, and feeds back the reconstruction result to the reconfigurable management platform; if not successful, execute step i; if successful, execute step h; Step h: data switching: switching network data to the reconfigured routing protocol software component; Step i: end. 2. The method for reconfiguring routing protocol software components in the reconfigurable routing and switching platform according to claim 1, wherein the reconfiguring resources include storage resources and computing resources. 3. the routing protocol software component reconfiguration method in the reconfigurable routing switching platform according to claim 1 is characterized in that: the component operation management interface, the user control interface interface, and the service mapping layer are contained in the software component operating environment and protocol message sending and receiving interface, the routing protocol software component registers the component operation management interface with the software component operating environment when starting, the component agent can use the component operation management interface to manage the routing protocol software component, and the routing protocol software component through the user control interface interface Communicate with the user control interface. Through the user control interface interface, the device administrator can configure and manage the routing protocol software components in the command line interface of the device. Each routing protocol software component follows the same user control interface interface standard, and the service The mapping layer defines the communication protocol between the routing protocol software component and the software component operating environment. The routing protocol software component accesses the operating system kernel protocol stack through the protocol packet sending and receiving interface of the software component operating environment to obtain protocol packets. 4. the routing protocol software component reconfiguration method in the reconfigurable routing exchange platform according to claim 1 is characterized in that: the component agent contains a management interface and a component deployment management module, and the component deployment management module communicates with the management interface , the component deployment management module includes a component certification program, a resource request program and a component execution program, after the component certification program is completed, it enters the resource request program, and after the resource request program is completed, it enters the component execution program. 5. The routing protocol software component reconfiguration method in the reconfigurable routing exchange platform according to claim 1, characterized in that: said reconfiguration instruction includes component authentication instruction, query component instruction, component deletion instruction and component execution instruction . 6. The method for reconfiguring routing protocol software components in the reconfigurable routing switching platform according to claim 1, characterized in that: said routing protocol software components include OSPF protocol components and RIP protocol components. 7. the routing protocol software component reconfiguration method in the reconfigurable routing exchange platform according to claim 6 is characterized in that: the OSPF protocol component contains the interface connected with the user control interface, the interface connected with the component agent, The interface connected with the routing management component and the interface connected with the software component operating environment, the routing management component is connected with the software component operating environment, the interface connected with the component agent and the interface connected with the routing management component is the Agent client interface. 8. The routing protocol software component reconfiguration method in the reconfigurable routing exchange platform according to claim 1 is characterized in that: the reconfiguration between the component agent and the routing protocol software component, between each routing protocol software component The reconstructed message is a control message, and the reconstructed message is composed of a message header and a message body. The message header has a unified format, and the message header includes the type of the message, the sender's identifier, the receiver's identifier, and the message length; the routing protocol software component and software The formats of protocol messages and control messages between component operating environments and between software component operating environments and operating systems are traditional protocol messages and traditional control message formats.

Images