CN102902542B - Virtual interface configuration method and device - Google Patents

Abstract

A method for configuring a virtual interface, comprising the steps of: obtaining basic parameters of messages delivered by a virtual interface; assigning the basic parameters of the messages to the corresponding basic parameter variables in the header object structure of the predefined general interface; pointing to The pointer of the virtual interface of the message is added as a linked list node in the linked list structure in the data object structure in the predefined general interface; obtain the data object verification structure containing the verification code of the linked list structure of the message; obtain the pre-defined The general parameters of the defined general interface, the general parameters of the predefined general interface, the header object structure containing the basic parameters of the message, the linked list structure containing the message, and the data object verification structure containing the message are combined to form a transfer The virtual interface for the message. In addition, a virtual interface configuration device is provided. The above virtual interface configuration method and device reduce a lot of repeated code data, save storage space, and are easy to operate.

Description

Virtual interface configuration method and device

technical field

The invention relates to computer technology, in particular to a virtual interface configuration method and device.

Background technique

With the development of computer technology, the functions of consumer electronic products are becoming more and more abundant, which greatly meets the needs of people. The underlying design of traditional consumer electronics products is generally based on software layers of various code architectures, and the interfaces between modules between different software layers are mainly implemented in the form of functions. The processing of different functional services has different control parameters and data formats that need to be transmitted. It is necessary to implement communication between the upper and lower layers and between modules through different function interfaces. Different function interfaces are implemented through a large number of different codes.

However, many function interfaces have only a few differences in parameters, but use a large number of different codes to maintain, need to store a large amount of code data, occupy storage space, and need to call different interfaces for communication between different modules. cumbersome.

Contents of the invention

Based on this, it is necessary to provide a virtual interface configuration method that can save storage space and is easy to operate, aiming at the problem of occupying a large amount of storage space and calling different interfaces is cumbersome.

A virtual interface configuration method, comprising the following steps:

Obtain the basic parameters of the message passed by the virtual interface;

assigning the basic parameters of the message to the basic parameter variables corresponding to the message in the header object structure in the predefined general interface;

Adding the pointer to the virtual interface of the message as a linked list node in the linked list structure in the data object structure in the predefined common interface;

Obtain a data object verification structure of the verification code of the linked list structure containing the message;

Obtain the general parameters of the predefined general interface, combine the general parameters of the predefined general interface, the header object structure containing the basic parameters of the message, the linked list structure containing the message and the data object verification structure containing the message Combining constitutes a virtual interface for passing said messages.

In one of the embodiments, before the step of obtaining the type identification of the message delivered by the virtual interface, the steps include:

Predefined common interface;

The steps of the predefined common interface include:

Predefine the common parameters of the common interface, the common parameters include header object variable, data object pointer and data object verification pointer;

The header object structure of the predefined common interface;

Predefining the data object structure of the general interface, the data object structure includes a linked list structure, and the linked list structure includes linked list nodes;

The data object verification structure of the general interface is predefined, and the data object verification structure stores the verification code of the linked list structure.

In one of the embodiments, the basic parameter variables of the message include a message type identification variable, a message length variable, and a data object check length variable.

In one of the embodiments, after the step of obtaining the basic parameters of the message delivered by the virtual interface, it further includes:

Detecting whether the data length of the message transmitted by the virtual interface is 0, if yes, the message is a control message; if not, the message is a control plus data message.

In one of the embodiments, the check code is a cyclic redundancy check code.

A virtual interface configuration device, comprising:

The obtaining module is used to obtain the basic parameters of the message passed by the virtual interface;

An assignment module, configured to assign the basic parameters of the message to the basic parameter variables corresponding to the message in the header object structure in the predefined general interface;

Adding a module for adding the pointer to the virtual interface of the message as a linked list node in the linked list structure in the data object structure in the predefined general interface;

A verification acquisition module, configured to obtain a data object verification structure containing a verification code of a linked list structure of the message;

The combination module is used to obtain the general parameters of the predefined general interface, and combine the general parameters of the predefined general interface, the head object structure containing the basic parameters of the message, the linked list structure containing the message and the The data object check structure is combined to form a virtual interface for passing the message.

In one of the embodiments, it also includes:

Predefined modules for predefining common interfaces;

The predefined modules include:

The general parameter definition unit is used to predefine the general parameters of the general interface, and the general parameters include header object variables, data object pointers and data object verification pointers;

The header object definition unit is used to predefine the header object structure of the common interface;

The data object structure definition unit is used to predefine the data object structure of the general interface, the data object structure includes a linked list structure, and the linked list structure includes linked list nodes;

The verification structure definition unit is used to predefine the data object verification structure of the general interface, and the data object verification structure stores the verification code of the linked list structure.

In one of the embodiments, the basic parameter variables of the message include a message type identification variable, a message length variable, and a data object check length variable.

In one of the embodiments, it also includes:

The detection module is used to detect whether the data length of the message transmitted by the virtual interface is 0, if yes, the message is a control message; if not, the message is a control plus data message.

In one of the embodiments, the check code is a cyclic redundancy check code.

The above virtual interface configuration method and device, by assigning the basic parameters of the obtained message to the message basic parameter variable in the general interface, and adding the pointer of the virtual interface corresponding to the message, a virtual interface is formed, and different messages correspond to The virtual interface only needs to modify some variable values without redesigning the interface, which reduces a lot of repeated code data, saves storage space, and is easy to operate.

Description of drawings

Fig. 1 is a schematic flow diagram of a virtual interface configuration method in an embodiment;

Fig. 2 is a specific schematic flow diagram of a predefined general interface in an embodiment;

Fig. 3 is a schematic diagram of member encapsulation structure in an embodiment;

Fig. 4 is a schematic diagram of a message format in an embodiment;

5 is a schematic diagram of a virtual interface configuration method applicable to message transmission between different structural layers;

Fig. 6 is a schematic diagram of message delivery between the platform layer and the middleware layer;

Figure 7 is a schematic diagram of the system structure;

FIG. 8 is a schematic diagram of the internal structure of a virtual interface configuration device in an embodiment;

Fig. 9 is a schematic diagram of the internal structure of a virtual interface configuration device in another embodiment;

Fig. 10 is a schematic diagram of the internal structure of a predefined module in an embodiment.

detailed description

The technical solution of the virtual interface configuration method and device will be described in detail below in conjunction with specific embodiments and accompanying drawings, so as to make it more clear.

As shown in Figure 1, in one embodiment, a kind of virtual interface configuration method comprises the following steps:

Step S110, acquiring the basic parameters of the message transmitted by the virtual interface.

Specifically, when a new virtual interface is added due to business logic, the basic parameters of the message transmitted by the virtual interface are obtained first. Basic parameters include type identification, message length, message grouping, data object parity length, etc. The type identifier includes a main type identifier and a subtype identifier, and can be represented by 1 byte in hexadecimal notation. For example, the main type may be a playback class, and the subtypes may be playback control, playback pause, playback stop, or playback fast-forward.

After step S110, detect whether the data length of message is 0, if so, then this message is a control message; Different messages are processed differently. Specifically, the transmitted message may only include control bits, but not data content, then the message is a control message, and only need to parse the control message to complete the corresponding control operation during application; the transmitted message may also include data content at the same time and control bits, the message is a control plus data message, which needs to enter the message processing flow during application, such as message parsing, message grouping, or message forwarding.

Step S120, assigning the basic parameters of the message to the basic parameter variables corresponding to the message in the header object structure in the predefined common interface.

Specifically, a common interface is firstly defined in advance. As shown in Figure 2, the steps of predefining a common interface include:

Step S210, predefine general parameters of the general interface, the general parameters include header object variables, data object pointers and data object verification pointers.

Specifically, the general parameters of the general interface are defined in a data structure, as described below:

Among them, the typedefHeader object is the definition header object variable, the typedef* data object is the definition data object pointer, and the typedef* data verification object is the definition data object verification pointer.

Step S220, predefine the header object structure of the common interface.

Specifically, the header object structure of the general interface includes several message basic parameter variables, and the message basic parameter variables mainly include a message type identification variable, a message length variable, and a data object check length variable. Further, the basic parameter variable of the message may also include whether the message is grouped, the number of groups, etc., but is not limited thereto.

The header object structure can be defined as follows, but not limited to:

Step S230, predefine the data object structure of the general interface, the data object structure includes a linked list structure, and the linked list structure includes linked list nodes.

Specifically, the data object structure of the general interface includes a linked list structure, and each linked list node in the linked list structure is a structure pointer, and the structure pointer points to a data structure, which represents a parameter of a virtual interface. For example, if the virtual interface has 3 parameters, then there are 3 corresponding structure pointers in the linked list structure. The number of linked list nodes in the linked list structure varies with different messages. In this way, the message delivery of different functional interfaces can be completed.

The following definitions may be used, but are not limited to:

Among them, the member encapsulation structure is a link structure, and several data structure pointers related to the message are stored in the linked list structure. As shown in FIG. 3 , the member encapsulation structure includes the address of data structure 1 to the address of data structure N.

Step S240, predefine the data object verification structure of the common interface, and the data object verification structure stores the verification code of the linked list structure.

Specifically, the data object verification structure of the general interface can be defined as follows, but is not limited thereto.

Wherein, the data verification member is a verification code and a message group used to store the link structure of the data object. The check code can be a cyclic redundancy check code.

The general interface is predefined, and the format of the message transmitted through the general interface includes header data, data content and verification data, as shown in Table 1.

Table 1

header data data check data

As shown in FIG. 4 , header data includes main message type, sub-message type, message length, message check control, control bit 1 to control bit N; data includes data 1 to N.

Step S130, adding the pointer to the virtual interface of the message as a linked list node in the linked list structure in the data object structure in the predefined common interface.

Specifically, the pointer to the virtual interface of the message is added to the linked list structure in the data object structure of the general interface in the form of a linked list node, and the linked list node becomes a structure pointer pointing to the virtual interface.

Step S140, acquiring a data object verification structure including the verification code of the linked list structure of the message.

Specifically, the check code of the linked list structure including the message is recalculated, and stored in the data object check structure.

Step S150, obtain the general parameters of the predefined general interface, and combine the general parameters of the predefined general interface, the header object structure containing the basic parameters of the message, the linked list structure containing the message, and the data object containing the message The check structures are combined to form a virtual interface for passing the message.

Specifically, the basic parameter of the message is assigned to the basic parameter variable of the message defined in the general interface, and after adding the linked list node in the linked list structure, a virtual interface for transmitting the message is formed.

The above virtual interface configuration method, by assigning the basic parameters of the obtained message to the message basic parameter variable in the general interface, and adding the pointer of the virtual interface corresponding to the message, constitutes a virtual interface, and the virtual interface corresponding to different messages Only need to modify part of the variable value, no need to redesign the interface, reduce a lot of repeated code data, save storage space, and easy to operate.

The above virtual interface configuration method can be applied to message transmission between different structural layers, as shown in Figure 5, specifically including:

Step S310, obtaining a request from the second structural layer to transmit the first structural layer message to the third structural layer, the first structural layer and the second structural layer are adjacent, and the second structural layer is adjacent to the third structural layer.

Specifically, for example, the first structural layer is a MiddleWare (middleware) layer, the second structural layer is a platform layer, and the third structural layer is a driver layer. The platform layer gets the middleware layer messages. The middleware layer message includes MiddleWare layer header data (MiddleWare layer Header), MiddleWare layer data and MiddleWare layer verification data.

In step S320, the first structural layer message is assembled between the header data of the second structural layer and the data of the second structural layer to form a second structural layer message.

Specifically, as shown in Figure 6, the platform layer adds the MiddleWare layer message to the platform layer Header (header object structure) and platform layer data. Platform layer messages include platform layer Header, MiddleWare layer messages, platform layer data and platform layer verification data.

Step S330, sending the second structural layer message to the third structural layer.

For example, sending platform layer messages to the driver layer.

In the above virtual interface configuration method, when the second structural layer transmits messages to the first structural layer, taking the platform layer and MiddleWare layer as an example, the message of the platform layer includes platform layer header data, data and verification data, and the platform layer transfers the platform layer After the message is sent to the MiddleWare layer, the MiddleWare layer parses the message of the platform layer according to the message format of the MiddleWare layer after receiving the message.

In addition, the above virtual interface configuration method can also be applied to configure the interface between the LinuxKernel layer and the platform layer, the interface between the platform layer and the MiddleWare layer, and the interface between the MiddleWare layer and the application layer.

As shown in Figure 7, the LinuxKernel layer is used to provide driver services for Linux system components, and this layer involves various hardware drivers.

The platform layer includes providing OS-related components and providing C/C++ libraries to support the upper layer (middleware layer). Including customizable C/C++ library, standard core C library and operating environment, such as virtual machine. The platform layer has a hardware abstraction layer interface (interface A) and a development language adaptation interface (interface B). The hardware abstraction layer interface provides various hardware-related interfaces to complete the message communication between the platform layer and different hardware interfaces. The development language adaptation interface is used to complete the conversion between high-level language and local language, so that high-level language can use local language, such as JNI, and embed NativeC/C++ in Java code.

The MiddleWare layer is used to provide the APIApplicationProgrammingInterface (application programming interface) framework of the core application services of the system, and handle different business logics. Users can develop their own service applications in this layer and provide interface C. The MiddleWare layer also provides a variety of service functions, such as data sharing services, instant messaging services, and so on.

The application layer includes the initial application of the system and the application developed by the user.

As shown in FIG. 8 , in one embodiment, a virtual interface configuration device includes an acquisition module 110 , an assignment module 120 , an addition module 130 , a verification acquisition module 140 and a combination module 150 . in:

The obtaining module 110 is used for obtaining the basic parameters of the message in the API. Specifically, when a new virtual interface is added due to business logic, the basic parameters of the message transmitted by the virtual interface are obtained first. Basic parameters include type identification, message length, message grouping, data object parity length, etc. The type identifier includes a main type identifier and a subtype identifier, and can be represented by 1 byte in hexadecimal notation. For example, the main type may be a playback class, and the subtypes may be playback control, playback pause, playback stop, or playback fast-forward.

The assignment module 120 is configured to assign the basic parameters of the message to the basic parameter variables corresponding to the message in the header object structure in the predefined common interface.

The adding module 130 is used for adding the pointer pointing to the virtual interface of the message as a linked list node in the linked list structure in the data object structure in the predefined common interface. Specifically, the pointer to the virtual interface of the message is added to the linked list structure in the data object structure of the general interface in the form of a linked list node, and the linked list node becomes a structure pointer pointing to the virtual interface.

The verification obtaining module 140 is configured to obtain a data object verification structure including a verification code of the linked list structure of the message. Specifically, the check code of the linked list structure including the message is recalculated, and stored in the data object check structure.

The combination module 150 is used to obtain the general parameters of the predefined general interface, and combine the general parameters of the predefined general interface, the head object structure containing the basic parameters of the message, the linked list structure containing the message and the The data object verification structure is combined to form a virtual interface for passing the message.

Specifically, the basic parameter of the message is assigned to the basic parameter variable of the message defined in the general interface, and after adding the linked list node in the linked list structure, a virtual interface for transmitting the message is formed.

The above-mentioned virtual interface configuration device forms a virtual interface by assigning the basic parameters of the obtained message to the basic parameter variable of the message in the general interface, and adding the pointer of the virtual interface corresponding to the message, and the virtual interface corresponding to different messages Only need to modify part of the variable value, no need to redesign the interface, reduce a lot of repeated code data, save storage space, and easy to operate.

As shown in Figure 9, in one embodiment, the above-mentioned virtual interface configuration device, in addition to including the acquisition module 110, the assignment module 120, the addition module 130, the verification acquisition module 140 and the combination module 150, also includes a predefined module 160 and a verification module Module 170. in:

The predefinition module 160 is used to predefine common interfaces.

As shown in FIG. 10 , in one embodiment, the predefined module 160 includes a general parameter definition unit 161 , a header object definition unit 163 , a data object structure definition unit 165 and a check structure definition unit 167 . in:

The general parameter definition unit 161 is used to predefine the general parameters of the general interface, and the general parameters include header object variables, data object pointers and data object verification pointers.

Specifically, the general parameters of the general interface are defined in a data structure, as described below:

Among them, the typedefHeader object is the definition header object variable, the typedef* data object is the definition data object pointer, and the typedef* data verification object is the definition data object verification pointer.

The header object definition unit 163 is used to predefine the header object structure of the common interface.

Specifically, the header object structure of the general interface includes several message basic parameter variables, and the message basic parameter variables mainly include a message type identification variable, a message length variable, and a data object check length variable. Further, the basic parameter variable of the message may also include whether the message is grouped, the number of groups, etc., but is not limited thereto.

The header object structure can be defined as follows, but not limited to:

The data object structure definition unit 165 is used to predefine the data object structure of the general interface, the data object structure includes a linked list structure, and the linked list structure includes linked list nodes.

Specifically, the data object structure of the general interface includes a linked list structure, and each linked list node in the linked list structure is a structure pointer, and the structure pointer points to a data structure, which represents a parameter of a virtual interface. For example, if the virtual interface has 3 parameters, then there are 3 corresponding structure pointers in the linked list structure. The number of linked list nodes in the linked list structure varies with different messages. In this way, the message delivery of different functional interfaces can be completed.

The following definitions may be used, but are not limited to:

Among them, the member encapsulation structure is a link structure, and several data structure pointers related to the message are stored in the linked list structure. As shown in FIG. 3 , the member encapsulation structure includes addresses of data structures 1 to N.

The verification structure definition unit 167 is used to predefine the data object verification structure of the general interface, and the data object verification structure stores the verification code of the linked list structure.

Specifically, the data object verification structure of the general interface can be defined as follows, but is not limited thereto.

Wherein, the data verification member is a verification code and a message group used to store the link structure of the data object. The check code can be a cyclic redundancy check code.

The general interface is predefined, and the format of the message transmitted through the general interface includes header data, data content and verification data, as shown in Table 1.

As shown in Figure 4, header data includes main message type, sub-message type, message length, message check control, control bit 1 to control bit N; data content includes data 1 to N.

The detection module 170 is used to detect whether the data length of the message in the API is 0, if so, the message is a control message; if not, the message is a message with data content, that is, a control plus data message; In specific applications, different processing may be performed for different messages. Specifically, the message may only include control bits, but not data content, then the message is a control message, and it is only necessary to parse the control message during application to complete the corresponding control operation; the message may also include data content at the same time and control bits, the message is a control plus data message, which needs to enter the message processing flow during application, such as message parsing, message grouping, or message forwarding.

The above virtual interface configuration device can be applied to message transmission between different structural layers, and the specific process is:

The acquiring module 110 acquires a request from the second structural layer to transmit the first structural layer message to the third structural layer, the first structural layer and the second structural layer are adjacent, and the second structural layer is adjacent to the third structural layer.

Specifically, for example, the first structural layer is a MiddleWare (middleware) layer, the second structural layer is a platform layer, and the third structural layer is a driver layer. The platform layer gets the middleware layer messages. The middleware layer message includes the middle layer header data (MiddleWare layer Header), MiddleWare layer data and MiddleWare layer verification data.

The assignment module 120 assigns the basic parameters of the message at the first structure layer to the basic parameter variables corresponding to the messages in the head object structure of the second structure layer.

The adding module 130 adds the pointer to the first structure layer message as a linked list node in the linked list structure in the data object structure of the second structure layer interface.

The combining module 150 is configured to add the first structure layer message between the header data of the second structure layer and the data of the second structure layer to assemble the second structure layer message.

Specifically, as shown in Figure 6, the platform layer adds the MiddleWare layer message to the platform layer Header (header object structure) and platform layer data. Platform layer messages include platform layer Header, MiddleWare layer messages, platform layer data and platform layer verification data.

The above virtual interface configuration device further includes a transmission module, configured to send the second structural layer message to the third structural layer.

For example, sending platform layer messages to the driver layer.

In the above-mentioned virtual interface configuration device, when the second structural layer transmits a message to the first structural layer, taking the platform layer and MiddleWare layer as an example, the message of the platform layer includes platform layer header data, data and verification data, and the platform layer transfers the platform layer After the message is sent to the MiddleWare layer, the MiddleWare layer parses the message of the platform layer according to the message format of the MiddleWare layer after receiving the message.

The above-mentioned embodiments only express several implementation modes of the present invention, and the description thereof is relatively specific and detailed, but should not be construed as limiting the patent scope of the present invention. It should be pointed out that those skilled in the art can make several modifications and improvements without departing from the concept of the present invention, and these all belong to the protection scope of the present invention. Therefore, the protection scope of the patent for the present invention should be based on the appended claims.

Claims (10)

1. A virtual interface configuration method, comprising the following steps: Obtain the basic parameters of the message transmitted by the virtual interface, the format of the message includes header data, data content and check data; assigning the basic parameters of the message to the basic parameter variables corresponding to the message in the header object structure in the predefined general interface; Adding the pointer to the virtual interface of the message as a linked list node in the linked list structure in the data object structure in the predefined common interface; Obtain a data object verification structure of the verification code of the linked list structure containing the message; Obtain the general parameters of the predefined general interface, verify the general parameters of the predefined general interface, the header object structure containing the basic parameters of the message, the linked list structure containing the message, and the linked list structure containing the message The code's data object check structure is combined to form a virtual interface for delivering the message. 2. The virtual interface configuration method according to claim 1, characterized in that, before the step of obtaining the basic parameters of the message delivered by the virtual interface, the steps include: Predefined common interface; The steps of the predefined common interface include: Predefine the common parameters of the common interface, the common parameters include header object variable, data object pointer and data object verification pointer; The header object structure of the predefined common interface; Predefining the data object structure of the general interface, the data object structure includes a linked list structure, and the linked list structure includes linked list nodes; The data object verification structure of the general interface is predefined, and the data object verification structure stores the verification code of the linked list structure. 3. The virtual interface configuration method according to claim 1, wherein the basic parameter variables of the message include a message type identification variable, a message length variable, and a data object check length variable. 4. The virtual interface configuration method according to claim 1, wherein after the step of obtaining the basic parameters of the message delivered by the virtual interface, further comprising: Detecting whether the data length of the message transmitted by the virtual interface is 0, if yes, the message is a control message; if not, the message is a control plus data message. 5. The virtual interface configuration method according to claim 1, wherein the check code is a cyclic redundancy check code. 6. A virtual interface configuration device, comprising: The obtaining module is used to obtain the basic parameters of the message delivered by the virtual interface, and the format of the message includes header data, data content and verification data; An assignment module, configured to assign the basic parameters of the message to the basic parameter variables corresponding to the message in the header object structure in the predefined general interface; Adding a module for adding the pointer to the virtual interface of the message as a linked list node in the linked list structure in the data object structure in the predefined general interface; A verification acquisition module, configured to obtain a data object verification structure containing a verification code of a linked list structure of the message; The combination module is used to obtain the general parameters of the predefined general interface, and combine the general parameters of the predefined general interface, the head object structure containing the basic parameters of the message, the linked list structure containing the message and the The data object verification structure of the verification code of the linked list structure is combined to form a virtual interface for transmitting the message. 7. The virtual interface configuration device according to claim 6, further comprising: Predefined modules for predefining common interfaces; The predefined modules include: The general parameter definition unit is used to predefine the general parameters of the general interface, and the general parameters include header object variables, data object pointers and data object verification pointers; The header object definition unit is used to predefine the header object structure of the common interface; The data object structure definition unit is used to predefine the data object structure of the general interface, the data object structure includes a linked list structure, and the linked list structure includes linked list nodes; The verification structure definition unit is used to predefine the data object verification structure of the general interface, and the data object verification structure stores the verification code of the linked list structure. 8. The virtual interface configuration device according to claim 6, wherein the basic parameter variables of the message include a message type identification variable, a message length variable, and a data object check length variable. 9. The virtual interface configuration device according to claim 6, further comprising: The detection module is used to detect whether the data length of the message transmitted by the virtual interface is 0, if yes, the message is a control message; if not, the message is a control plus data message. 10. The virtual interface configuration device according to claim 6, wherein the check code is a cyclic redundancy check code.