WO2011116583A1

WO2011116583A1 - Method and apparatus for implementing management of multi-protocol communication components

Info

Publication number: WO2011116583A1
Application number: PCT/CN2010/076178
Authority: WO
Inventors: 康海涛; 边海蓉; 高歌
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-03-26
Filing date: 2010-08-20
Publication date: 2011-09-29
Also published as: CN101820361A; CN101820361B

Abstract

Disclosed are a method and an apparatus for implementing the management of multi-protocol communication components, wherein the method relates to a service application layer and communication lower layer of a communication device, and includes: adding a protocol adaptation layer between the service application layer and the communication lower layer; when the communication device needs to provide support for a protocol stack, recording the communication type of the protocol stack in a configuration file via the protocol adaptation layer, compiling the protocol stack into a dynamic-link library and downloading the dynamic-link library to the conmmunication device to form one or more communication components, and enabling the communication components. The present invention enables the stability and the flexibility of the system to be improved dramatically without increasing the cost of the system on the basis of the original devices, and thus has good application prospect and value in use.

Description

Method and device for realizing management of multi-protocol communication component

Technical field

The present invention relates to a point-to-multipoint communication device in which communication components capture a plurality of communication protocols, and more particularly to a method and apparatus for implementing management of a multi-protocol communication component in such a communication device.

Background technique

When constructing a device system for a multipoint communication and communication component with multiple communication protocols, the following scenario is often encountered: For a management component at a core location (for example, a wavelength division monitoring channel management system) It may be attached to subcomponents (boards) with a variety of communication protocols, and the management component will have to implement all the protocols to support the various subcomponents that may appear in the system. This may have the following three problems:

(1) For some new boards that appear in the future, the types of communication protocols that are not supported by the current management components may be used, so that the addition of new boards will bring about the reconstruction of the entire management component version.

(2) In order to support a board with a new communication protocol, each project upgrade requires an upgrade of the entire management software in the operating system, which increases the upgrade risk and system downtime.

When a new type of communication protocol needs to be added to the system, it is often necessary to upgrade the entire system. The complexity is high and the time is too long (including download time and flash time), which causes long interruption of all services.

(3) If only one or a few types of communication protocol boards are used in the system, the management component must also load all types of communication protocol stacks, create corresponding send and receive tasks, send and receive queues, and Resources such as semaphores cause waste of communication port resources.

In some application scenarios, only one or several types of boards can be used. If the remaining communication components cannot be uninstalled and continue to perform idle tasks, they will consume a lot of CPU resources.

In summary, it can be seen that the management components in the existing monitoring equipment fail to implement dynamic management of the protocol stack of the lower board, which will result in extremely high system setup and maintenance costs, which is not conducive to system upgrade, and will This causes serious waste of resources such as CPU/RAM/FLASH in the device. Summary of the invention

The technical problem to be solved by the present invention is to provide a method and apparatus for implementing management of a multi-protocol communication component, which can implement effective dynamic management of a multi-protocol communication component.

In order to solve the above technical problem, the present invention provides a method for implementing management of a multi-protocol communication component, which relates to a service application layer and a communication underlayer of a communication device, and the method includes:

Add a protocol adaptation layer between the business application layer and the communication underlayer;

When the communication device is to provide support for the protocol stack, the communication layer of the protocol stack is recorded in a configuration file by the protocol adaptation layer, and the protocol stack is compiled into a dynamic link library and downloaded to the communication device to form one or more communications. Component, and enable communication components.

The method also includes:

When the communication device is initialized at power-on, the communication device is normally operated by creating a corresponding communication task and its sending and receiving queue for the communication component existing in the configuration file through the protocol adaptation layer.

The method also includes:

During the normal operation of the communication device, the protocol adaptation layer interacts with the service application layer and the communication port under the communication layer through the sending and receiving queues to implement message distribution and/or protocol learning and dynamic port loading or unloading of the protocol stack.

Implementing message distribution includes:

The service application layer transmits the received message message to the protocol adaptation layer through the message receiving queue of the sending and receiving queue;

The protocol adaptation layer determines the communication type of the corresponding communication component in the configuration file according to the destination address to which the message message is sent, and places the basic element information of the communication into the message header provided for the message message, and is provided with a report. The message message of the header is placed in the message sending queue of the corresponding communication task;

The bottom layer of the communication fills in the message message, the source address and the destination address in the message sending queue to the corresponding entry parameters of the corresponding driver transceiver function, and realizes the coupling with the corresponding interface of the corresponding communication task.

Implementing protocol learning includes:

After the protocol adaptation layer receives the message from the message receiving queue, it will add the newly added header. The type information is recorded in the configuration file and stored as a new communication type.

Implementing dynamic loading or unloading of the protocol stack includes:

The protocol adaptation layer adds or deletes the communication type in the configuration file, and loads or unloads the corresponding communication task and its sending and receiving queue after the communication device is powered on again.

Before the protocol adaptation layer records the communication type of the protocol stack in the configuration file, the foregoing method further includes:

The protocol adaptation layer creates a configuration file according to the configuration of the communication device. In addition to the communication type of the protocol stack currently supported by the communication device, the configuration file also records the message structure information of the communication type; the protocol currently supported by the communication device The stack is compiled into a dynamic link library.

In order to solve the above technical problem, the present invention provides an apparatus for implementing management of a multi-protocol communication component, including a service application layer management module and an underlying communication module, and a protocol is further included between the service application layer management module and the communication module. With modules, where:

The service application layer management module is configured to: transmit the received message message to the protocol adaptation module; the protocol adaptation module is configured to: at least record the communication type of the protocol stack in a configuration file, and compile the protocol stack into a dynamic Linking library downloads, forming one or more communication components, and enabling communication components; at least, distributing received message messages according to communication types recorded in the configuration file when the device is in normal operation;

The communication module is configured to: deliver the message that is distributed by the protocol adaptation module to the corresponding communication component.

The protocol adaptation module includes a protocol loading unit, a message distribution unit, and a storage unit, where: the protocol loading unit is configured to: record the communication type of the supported protocol stack into a configuration file saved in the storage unit, and initialize the device on the device. Creating a corresponding communication task and a sending and receiving queue for the communication component existing in the configuration file, and interacting with the service application layer management module and the communication module respectively in the normal operation of the device through the sending and receiving queue;

The storage unit is set to: save the configuration file;

The message distribution unit is set to: according to the message message received from the message receiving queue of the sending and receiving queue The destination address to be sent determines the communication type of the corresponding communication component in the configuration file, and the basic element information of the communication is placed in the message header provided for the message message, and the message message with the message header is placed. The corresponding communication task is sent in the message queue.

The protocol adaptation module includes a protocol learning unit, where:

The protocol learning unit is configured to: after receiving the message message from the message receiving queue, record the format information of the newly added message header in the configuration file in the storage unit, and save it as a new communication type; the protocol loading unit also sets To: Add or delete the communication type in the configuration file, and load or unload the corresponding communication task and its sending and receiving queue after the device is powered on again.

Compared with the prior art, the management component uses the plug-and-play, dynamic learning and dynamic loading methods for the communication component, which can greatly reduce the risk of system upgrade and the interruption time of the service, and support the new component. More quickly and quickly; In addition, if only a few types of sub-components are configured in the system, this way of dynamically loading according to the communication type can greatly reduce the communication port overhead, which is especially true in embedded systems where resources are particularly tight. important. The method and device of the invention can greatly improve the stability and flexibility of the system without increasing the system cost on the basis of the original equipment, so it has a good application prospect and use value.

BRIEF abstract

1 is a structural block diagram of an embodiment of a multi-protocol communication component management apparatus according to the present invention; FIG. 2 is a structural block diagram of an embodiment of the protocol adaptation module shown in FIG.

3 is a flow chart of an embodiment of a method for managing a multi-protocol communication component according to the present invention.

Preferred embodiment of the invention

The technical solutions of the present invention are described in detail below with reference to the accompanying drawings and preferred embodiments. The following examples are intended to illustrate and explain the present invention and are not intended to limit the invention.

For an idealized multi-protocol communication component management device (such as an application for a communication monitoring Equipment), its service level can completely ignore the details of each protocol used by the underlying layer, and only need to call the corresponding sending and receiving interfaces to perform the sending and receiving of the message. The details of shielding the underlying communication can reduce the coupling of the system, thereby increasing the modularity of the system. In fact, for a new protocol type of board application, it can be achieved by simply modifying the configuration file and downloading a new protocol stack module. In this regard, if it is implemented by the "plug and play" technology, for example, the management device is regarded as a host, and all the service boards are regarded as a type of plug-and-play peripheral, thereby facilitating the hooking and unloading.

The invention utilizes "plug and play" technology to realize dynamic management of communication protocols. Here, various communication modules can be easily hooked up to the system like a peripheral to support multiple communication protocols.

The invention provides a structure for implementing an embodiment of a multi-protocol communication component management device, which adds a layer of "protocol adaptation module" middleware between the service application layer management module and the underlying communication module, as shown in FIG. :

The service application layer management module is configured to exchange the received message message (that is, the message body) to the protocol adaptation module by interacting with the protocol adaptation module through the message sending and receiving queue;

For the business application layer management module, the details of the underlying communication protocol are transparent at this level. It does not need to know what the header format of each communication type is, and only handles the body part of the message. It needs to communicate with the protocol adaptation module through the sending and receiving queues. Regardless of which type of board the message is sent to, the message is first transmitted to the protocol adaptation module through the message receiving queue for processing.

The protocol adaptation module is used as a core part of the plug-and-play communication protocol, and is used for interacting with the upper layer service application layer management module and the lower layer communication port through the sending and receiving queues, thereby realizing message distribution, protocol learning, and dynamic loading of the communication protocol;

The creation or deletion of communication tasks and their transceiver queues is dynamically adjusted by the protocol adaptation module. The communication module is configured to, in response to the transceiving task, couple the message content, the source address, and the destination address in the message queue from the protocol adaptation module to an interface corresponding to the corresponding transceiving task.

The communication module fills in the message content, source address, and destination address to the corresponding driver transceiver function. On the corresponding entry parameters, an interface coupling corresponding to the corresponding transceiving task is implemented.

The destination address here refers to the communication address of each board in the system. These communication addresses are also virtual addresses. To each different physical medium, it needs to be translated into the actual physical address by address resolution, that is, address adaptation. .

The protocol adaptation module shown in FIG. 1 further includes a protocol loading unit, a protocol learning unit, a message distribution unit, and a storage unit, as shown in FIG. 2, where:

a protocol loading unit, configured to record a type of a board communication (ie, a communication protocol type) used in the communication device in a configuration file or a database, and save the data in the storage unit; when in use, load the corresponding communication component into the Running in RAM;

The protocol loading unit reads the contents of the configuration file or database when the system is powered on, and creates corresponding communication tasks and sending and receiving queues only for the communication types existing in the configuration file or the database. In this way, when the system needs to support the board of the new communication type, you can add a new protocol by modifying the configuration file or database (modified through the network management or directly modifying). After the power is turned on, the corresponding communication task and sending and receiving queue will be loaded. Resources, while communication protocols not configured in the system are silent and are not enabled.

The protocol learning unit is configured to: after receiving the message message from the message receiving queue, record the format information of the newly added message header in a configuration file or a database stored in the storage unit;

For different types of boards, there are differences in the format of the communication protocol. The interactive packet includes the packet header and the packet body. The main difference between the different types of boards is the format of the packet header, and the packet body is the packet content transmitted through the message queue of the service application layer management module. The protocol learning unit puts the format information of the newly added message header in the configuration file or database, which means that a new communication protocol is learned, which is used for the message distribution unit to perform the >3⁄4 header adaptation processing. In this way, the message distribution unit reads the format information of the packet header after power-on, and combines the packet header and the packet body to form a new packet for transmission.

The message distribution unit is configured to distribute the message transmitted from the service application layer management module through the message receiving queue to different communication tasks. In the communication type in the configuration file, the basic element information of the communication is placed in the message header provided for the message message according to the communication type, and the message message with the message header is placed in the corresponding communication task. The queue to be sent to the communication module in the message sending queue.

The basic element information for a communication system includes the source address, the destination address, and the length of the message.

A storage unit that is used to save the configuration file.

FIG. 3 shows a flow of an embodiment of the method for managing a multi-protocol communication component of the present invention, including the following steps:

110: Create a configuration file according to the configuration of the communication device, and record at least the communication communication type currently supported by the device in the configuration file;

In addition, other information such as the message structure of the current protocol of the device is also recorded in the configuration file.

120: Compiling a communication protocol stack currently supported by the device into a dynamic link library;

130: When the device is required to provide support for the new protocol stack, the modified configuration file and the recompiled dynamic link library are downloaded to the device to form a new component;

140: Make the new components of the protocol stack effective;

Many operating systems provide an interface for dynamic link library management, which allows dynamic loading of the corresponding library files without rebooting the system. For example, dlopen/dlsym/dlclose in the Linux system implements the function of opening, using, and uninstalling the dynamic link library, thereby completing the online upgrade without interrupting the service.

150: Create corresponding queues and communication tasks, and the system enters normal operation.

Once the corresponding queue and communication tasks have been created for the new component, the new protocol is supported and the system is up and running.

Here, step 110 is a supplement to step 140 to prevent the system from being restored to the initial state after restarting (ie, the state of the new component is not added), and the configuration file must be modified each time a new component is added/unloaded.

Step 120 is to implement the stripping of the communication module and the operating system and the application, so that each pass When the letter module is upgraded, it is not necessary to update the entire Bin file (mega-capacity level), but only the dynamic link library (kilobyte level) part of the communication module protocol stack; and the application (in the business application layer management module) ) Some versions are well controlled.

Step 140 is an important step of the present invention. After upgrading the configuration file and the dynamic link library, the required dynamic link library components can be loaded or unloaded directly from the command line.

The above method of the present invention is simple and easy to implement in the specific implementation, and is mainly embodied in three links: adding an adaptation layer between the service application layer management module and the underlying communication module, that is, reducing the service and communication module through the protocol adaptation module Degree of coupling between;

The protocol stack of the communication module is separated from the device system and compiled into a dynamic link library to facilitate the upgrade;

By reserving the upgrade interface in the protocol adaptation module and the communication module, the purpose of supporting the new communication module can be achieved by simple symbol table replacement.

While the preferred embodiments of the present invention have been disclosed for purposes of illustration, those skilled in the art will recognize that various modifications, additions and substitutions are possible, and the scope of the invention should not be limited to the embodiments described above.

One of ordinary skill in the art will appreciate that all or a portion of the steps above may be accomplished by a program to instruct the associated hardware, such as a read-only memory, a magnetic disk, or an optical disk. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the above embodiment may be implemented in the form of hardware or in the form of a software function module. The invention is not limited to any specific form of combination of hardware and software.

Industrial applicability

Compared with the prior art, the management component uses the plug-and-play, dynamic learning and dynamic loading methods for the communication component, which can greatly reduce the risk of system upgrade and the interruption time of the service, and support the new component. Faster and faster; in addition, if only a few are configured in the system Sub-components of the type, which can dynamically reduce the communication port overhead according to the way the communication type is dynamically loaded, which is particularly important in embedded systems where resources are particularly tight. The method and device of the invention can greatly improve the stability and flexibility of the system without increasing the system cost on the basis of the original equipment, so it has a good application prospect and use value.

Claims

Claim

1. A method for implementing management of a multi-protocol communication component, the method comprising:

Adding a protocol adaptation layer between the service application layer and the communication bottom layer of the communication device; when the communication device is to provide support for the protocol stack, the communication type of the protocol stack is recorded by the protocol adaptation layer In the configuration file, the protocol stack is compiled into a dynamic link library and downloaded to the communication device to form one or more communication components, and the communication component is enabled.

2. The method of claim 1 further comprising:

The communication device creates a corresponding communication task and a transceiver queue for the communication component existing in the configuration file by the protocol adaptation layer during power-on initialization, and the communication device operates normally.

3. The method of claim 2, further comprising:

During normal operation of the communication device, the protocol adaptation layer interacts with the service application layer and the communication port of the communication bottom layer through the transceiver queue to implement message distribution and/or protocol learning and protocol stack. Dynamically load or unload.

The method according to claim 3, wherein the implementing the message distribution comprises: transmitting, by the service application layer, the received message message to the protocol adaptation layer by using a message receiving queue of the sending and receiving queue;

Determining, by the protocol adaptation layer, the communication type of the corresponding communication component in the configuration file according to the destination address to which the message message is sent, and placing the basic element information of the communication into the message provided for the message In the header, the message message with the message header is placed in the message sending queue of the corresponding communication task;

The communication bottom layer fills the message message, the source address and the destination address in the message sending queue to the corresponding entry parameters of the corresponding driver transceiver function, and implements coupling with the corresponding interface of the corresponding communication task.

5. The method according to claim 4, wherein implementing the protocol learning comprises: the protocol adaptation layer, after receiving the message from the message receiving queue, adding format information of the newly added packet header It is recorded in the configuration file and saved as a new communication type.

6. The method of claim 4, wherein dynamic loading or unloading of the protocol stack is implemented Includes:

The method according to any one of claims 1 to 6, before the protocol adaptation layer records the communication type of the protocol stack in the configuration file, the method further includes:

The protocol adaptation layer creates the configuration file according to the configuration of the communication device, and records the communication type report in addition to the communication type of the protocol stack currently supported by the communication device in the configuration file. The structure information; compiling the protocol stack currently supported by the communication device into a dynamic link library.

8. An apparatus for implementing management of a multi-protocol communication component, comprising: a service application layer management module and an underlying communication module, wherein the device further includes a protocol between the service application layer management module and the communication module With modules, where:

The service application layer management module is configured to: transmit the received message message to the protocol adaptation module;

The protocol adaptation module is configured to: record a communication type of the protocol stack in a configuration file, and compile the protocol stack into a dynamic link library download to form one or more communication components, and enable the communication component And distributing the received text message according to the communication type described in the configuration file when the device is in normal operation;

9. The apparatus according to claim 8, wherein the protocol adaptation module comprises a protocol loading unit, a message distribution unit, and a storage unit,

The protocol loading unit is configured to: record a communication type of the supported protocol stack into the configuration file saved in the storage unit, and create a communication component existing in the configuration file when the device is powered on and initialized Corresponding communication tasks and their sending and receiving queues, respectively, interacting with the service application layer management module and the communication module in the normal operation of the device through the sending and receiving queues; the storage unit is configured to: save the configuration file;

The message distribution unit is configured to: receive according to a message receiving queue from the sending and receiving queue Determining, by the destination address to which the message message is sent, the communication type of the corresponding communication component in the configuration file, and placing the basic element information of the communication into the message header provided for the message message, and The message message of the packet header is placed in the message sending queue of the corresponding communication task.

10. The apparatus of claim 9, wherein the protocol adaptation module comprises a protocol learning unit,

The protocol learning unit is configured to: after receiving the message message from the message receiving queue, record format information of the newly added message header in a configuration file in the storage unit, as a new communication Type save;

The protocol loading unit is further configured to: add or delete the communication type in the configuration file, and load or unload the corresponding communication task and its sending and receiving queue after the device is powered on again.