WO2016090957A1

WO2016090957A1 - Decoding method and apparatus, and computer storage medium

Info

Publication number: WO2016090957A1
Application number: PCT/CN2015/087642
Authority: WO
Inventors: 许艳芳
Original assignee: 深圳市中兴微电子技术有限公司
Priority date: 2014-12-12
Filing date: 2015-08-20
Publication date: 2016-06-16
Also published as: CN105740292B; CN105740292A

Abstract

Disclosed is a decoding method. The method comprises: extracting protocol related information from a standard protocol file, and storing the protocol related information into a database by using a corresponding data structure format; and decoding a to-be-decoded code stream according to the information stored in the database. Also disclosed are a decoding apparatus and a computer storage medium.

Description

Decoding method, device and computer storage medium

Technical field

The present invention relates to a codec technology in the field of communication protocols, and in particular, to a decoding method, apparatus, and computer storage medium.

Background technique

With the rapid development of the communication industry technology, the communication protocol is also constantly updated, and the application protocol needs to be updated accordingly. At present, most of the processing of standard protocol documents is to convert standard protocol documents into C, C++ and other languages through manual translation, and by manual decoding, not only a lot of manpower and time is wasted, but also error-prone. Therefore, many manufacturers analyze the standard protocol documents according to their own needs, establish their own codec system, in order to realize the automatic codec of the standard protocol documents related to themselves; when the standard protocol documents are upgraded, through the established codec system By directly reading the standard protocol document, the codec library can be upgraded, which greatly improves the efficiency of the codec.

At present, the description languages of protocols such as Abstract Syntax Notation (ASN) and China Smart Logistic Network (CSN) have mature codec systems, which can be easily obtained from such Extract information from the protocol document. However, some protocol documents describe the protocol information in the form of a table, such as the 24008x series of protocol documents. Since they do not have a unified syntax and a fixed format, it brings a lot of difficulties to automatically extract such protocol information.

Summary of the invention

In view of this, the main purpose of the embodiments of the present invention is to provide a decoding method, an apparatus, and a computer storage medium, which can automatically decode and improve protocol documents described in a tabular form. Decoding efficiency.

To achieve the above objective, the technical solution of the embodiment of the present invention is implemented as follows:

An embodiment of the present invention provides a decoding method, where the method includes:

Extracting protocol-related information from the standard protocol document, and saving the protocol-related information to the database in a corresponding data structure format;

The code stream to be decoded is decoded based on the information stored in the database.

In the foregoing solution, the protocol related information includes at least: message description information, cell description information, and enumeration description information.

In the above solution, the protocol-related information is extracted from the standard protocol document, and the protocol-related information is saved in the database in a corresponding data structure format, including:

Setting a first storage format, where the first storage format includes a message description table storage format, a cell description table storage format, an enumeration description table storage format, and an array type storage format;

Reading the standard protocol document, and extracting message description information, cell description information, and enumeration description information from the protocol document;

And based on the first storage format, storing the message description information, the cell description information, and the enumeration description information in a corresponding storage format into a database.

In the above solution, the decoding, according to the information stored in the database, the code stream to be decoded, includes:

After receiving the code stream to be decoded, obtaining relevant parameters required for decoding from the code stream;

Determining a message name corresponding to the code stream according to the relevant parameters required for decoding;

Obtaining, by using the message name as a key, a message node corresponding to the message name, cyclically parsing the child node under the message, and obtaining a format attribute value of the child node, if the format attribute value of the child node is an optional item Then, jump to the optional decoding process, otherwise enter the mandatory decoding process until the end of the code stream or the end of the node, the current message decoding ends.

In the foregoing solution, the optional decoding process includes:

First, the optional start node is obtained. Each time the option is decoded, starting from the optional start node, the option tag value actually obtained by the current code stream is matched with the standard optional tag value in the database, if it matches Successfully, get the current node, call the required decoding interface to decode.

In the above solution, the required decoding process includes:

If the length information is included in the message format attribute value, the length information is first decoded, and then the length information is compared with the standard length information, and if the length information is within the standard length range, The decoding is continued, otherwise, the current decoding process is ended; if the length information is not included in the message format attribute value, the length information does not need to be decoded; until the decoding length is 0, the current message decoding ends.

An embodiment of the present invention further provides a decoding apparatus, where the decoding apparatus includes an extraction module and a decoding module, where

The extracting module is configured to extract protocol related information from a standard protocol document, and save the protocol related information to a database in a corresponding data structure format;

The decoding module is configured to decode a code stream to be decoded based on information stored in the database.

In the above solution, the extraction module includes a setting submodule, a reading submodule, and a storage submodule; wherein

The setting submodule is configured to preset a first storage format, where the first storage format includes a message description table storage format, a cell description table storage format, an enumeration description table storage format, and an array type storage format;

The reading submodule configured to read the standard protocol document from the protocol document Extracting message description information, cell description information, and enumeration description information;

The storage submodule is configured to store the message description information, the cell description information, and the enumeration description information in a corresponding storage format into a database based on the first storage format.

In the above solution, the decoding module includes an obtaining submodule, a determining submodule, and a processing submodule; wherein

The acquiring submodule is configured to: after receiving the code stream to be decoded, obtain relevant parameters required for decoding from the code stream;

The determining submodule is configured to determine a message name corresponding to the code stream according to the relevant parameters required for decoding;

The processing submodule is configured to acquire a message node corresponding to the message name by using the message name as a key, loop through the child nodes under the message, and obtain a format attribute value of the child node, if the child If the format attribute value of the node is optional, it will jump to the optional decoding process, otherwise it will enter the mandatory decoding process until the end of the code stream or the end of the node, and the current message decoding ends.

In the foregoing solution, the optional decoding process includes:

First, the optional start node is obtained. Each time the option is decoded, starting from the optional start node, the option tag value actually obtained by the current code stream is matched with the standard optional tag value in the database, if the matching is successful. Get the current node and call the required decoding interface to decode.

In the above solution, the required decoding process includes:

If the length information is included in the message format attribute value, the length information is first decoded, and then the length information is compared with the standard length information, and if the length information is within the standard length range, Continue to decode, otherwise, the current decoding process is ended; if the message format attribute value does not include the length information, the length information does not need to be decoded; Until the decoding length is 0, the current message decoding ends.

The embodiment of the invention further provides a computer storage medium, wherein the computer storage medium stores a computer program, and the computer program is used to execute the decoding method described above.

The decoding method, device and computer storage medium provided by the embodiments of the present invention extract protocol related information from a standard protocol document, and save the protocol related information in a database in a corresponding data structure format; based on the information stored in the database The code stream to be decoded is decoded. In this way, automatic decoding of the protocol document described in the form of a table can be realized, and the problem that the protocol described in the tabular form cannot be automatically decoded can be solved. In addition, the decoding efficiency of the protocol document described in the form of a table is also improved, and the efficiency of maintenance and upgrade of the decoding library can be improved. Furthermore, the method according to an embodiment of the invention is particularly suitable for decoding a protocol document described in tabular form, such as a network layer protocol document.

DRAWINGS

1 is a schematic flowchart of a decoding method according to an embodiment of the present invention;

2 is a schematic diagram of a storage format of a message description table according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of a storage format of a cell description table according to an embodiment of the present disclosure;

4 is a schematic diagram of a storage format of an enumeration description according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of an array storage format according to an embodiment of the present invention;

FIG. 6 is a schematic structural diagram of a decoding apparatus according to an embodiment of the present invention.

detailed description

The invention will be described in detail with reference to the accompanying drawings, and the accompanying drawings are only for the purpose of illustration.

FIG. 1 is a schematic flowchart of a decoding method according to an embodiment of the present invention. As shown in FIG. 1 , the method mainly includes the following steps:

Step 101: Extract protocol related information from a standard protocol document, and save the protocol related information into a database in a corresponding data structure format.

Here, the standard protocol document mainly refers to a document that describes the contents of the protocol in a tabular form, such as the 24008x series protocol.

Preferably, the protocol related information at least includes: message description information, cell description information, and enumeration description information.

Preferably, the protocol-related information is extracted from the standard protocol document, and the protocol-related information is saved in the database in a corresponding data structure format, including:

And based on the first storage format, the message description information, the cell description information, and the enumeration description information are respectively stored in a database in a corresponding storage format.

Here, the message description information may be stored in a message description table, and the cell description information may be stored in a cell description table, and the enumeration description information may be saved in an enumeration description table. The message description table may be stored in a database, a cell description table, an enumeration description table, and an array type storage format, which may be stored in another database. Of course, the message description table, the cell description table, the enumeration description table, and the array type storage format can also be stored in the same database.

FIG. 2 is a schematic diagram of a storage format of a message description table according to an embodiment of the present invention. The message description table storage format is specifically:

With the message name as the key value, the cell description below the message is taken as a child node.

Among them, each cell attribute includes: an option tag value (IEI), a cell name (Name), Category, Presence, Length, and the corresponding chapter number.

Obviously, in Figure 2, the message with the message name <IMSI_DETACH_INDICATION> contains 5 cells.

FIG. 3 is a schematic diagram of a storage format of a cell description table according to an embodiment of the present invention. The cell description table storage format is specifically:

The chapter number is used as the first level key value, and the byte is used as the second level key value, and the cells in each byte are used as child nodes.

Among them, each cell attribute includes: Name, Length (Len), Type (bArry), Enumeration Flag (bEnum), and Reference Member Name (Member).

The storage format of the enumeration description table provided by the embodiment of the present invention is as shown in FIG. 4, and the enumeration description table storage format is specifically:

The chapter number is used as the first level key value, and the cell name is used as the second level key value, and each enumeration value is used as a child node;

Among them, each enumeration value attribute includes: enumeration value (Val), enumeration description (Caption).

Wherein, the enumeration value is expressed in decimal.

The array type storage format provided by the embodiment of the present invention is as shown in FIG. 5, and the array type storage format is specifically:

The structure name is used as the key value, and the structure cell is used as the child node.

The array attribute includes: a cell name (Name), a cell length (Len), a cell type (Mem Type), and an enumeration flag bit (bEnum).

Among them, the cell type is divided into a general type, a length type, and a dependent length type. Specifically, MemType=0 indicates a general type, MemType=1 indicates a length type, and MemType=2 indicates a dependent length type.

In an embodiment, the algorithm for extracting the message description table mainly includes the following steps:

Get the message name;

Searching in the database with the message name + message content as a key, and determining a message description table of the message;

The information in the message description table is read in the cells of the row.

In an embodiment, reading the information in the message description table according to the cells of the row may include:

When the chapter number is read, it indicates that the current member has finished reading and continues to read the next member until the reading of the first table ends.

Taking four tables in the 24008 protocol document as an example, the four tables are specifically: "Table 10.2/3GPP TS 24.008: Message types for Mobility Management", "Table 10.3/3GPP TS 24.008: Message types for Call Control And call related SS messages", "Table 10.4/3GPP TS 24.008: Message types for GPRS mobility management", "Table 10.4a/3GPP TS 24.008: Message types for GPRS session management", the value of the 10th column of each row can be taken as a message Name, and then look up the message name + message content as the key, the first table from the found location is the message description table of the message, and then read the information in the message description table according to the cell of the row, when read In the chapter number, it indicates that this member has finished reading and continues to read the next member until the reading of the first table ends.

In an embodiment, the algorithm flow for extracting the cell description table may include:

When the chapter number is used as the search condition, the chapter number found is the directory, and the chapter is found to obtain the first table of the chapter; the information in the first table is sequentially read in units of cells.

The first table is a cell description table of the current member.

Specifically, when the first keyword (octet) is read, it indicates that the cell reading of the current byte ends, and the cell of the next byte is continuously read until the reading of the first table ends.

It should be noted that the number of columns of the current byte represents the number of cells of the current byte, if any If you merge, merge them in a small number of columns and save them in an array.

In an embodiment, the algorithm flow for extracting the enumerated cell value and the enumeration description information may include:

The chapter number is used as the search condition, and when the chapter number found is the directory (ie "title"), the chapter is found;

Obtaining a second table of the chapter; wherein the second table is an enumeration description table of the current IE;

The information in the second table is sequentially read in units of cells.

Specifically, the information in the second table is sequentially read in units of cells, including:

The second table is read according to the cell, and when the second keyword "(OCTET" is read, the cell name of the current member is obtained; wherein the character preceding the keyword is the cell name.

After reading the word string of ‘0’ or ‘1’, it is converted to decimal;

Reads a string that is not ‘0’ or ‘1’. If the cell does not have a newline, the description information of the current enumeration value is saved in the array;

The next cell continues to be read until the second table reading ends.

Step 102: Decode a code stream to be decoded based on information stored in the database.

In an embodiment, the decoding of the code stream to be decoded based on the information stored in the database may include:

The related parameters required for decoding include: Protocol Discriminator (PD) information, and message type (MsgType) information.

In an embodiment, the obtaining the relevant parameters required for decoding from the code stream may include:

Obtaining PD information by using the first byte of the code stream;

Based on the PD information, it is determined that one of the second and third bytes in the code stream is MsgType information.

Specifically, the determining, according to the required parameters related to the decoding, a message name corresponding to the code stream, including:

Determining, according to the PD information, a global mapping table corresponding to the PD information;

Determining, according to the MsgType information, a message name corresponding to the code stream from the global mapping table.

Here, the global mapping table refers to a mapping from MsgType to a message name.

Here, in the database, different global mapping tables are set for each type of PD.

The optional decoding process includes:

First, the optional start node is obtained. Each time the option is decoded, starting from the optional start node, the option tag value (IEI value) actually obtained by the current code stream is matched with the standard optional tag value in the database. If the match is successful, the current node is obtained, and the required decoding interface is decoded.

Here, the IEI value actually obtained by the code stream is matched with the standard IEI value in the database, and if the actual IEI value is within the standard IEI value range, the matching is successful.

The required decoding process includes:

In other words, if the current message format is "L", the length must be decoded first, and then The length of the decoding is judged. If the comparison is successful, the following cell continues to be decoded, otherwise the return fails until the decoding length is 0, and the current message decoding ends.

For example, when the format is "TLV" or "LV", the length of one byte must be decoded first; when the format is "TLV-E" or "LV-E", the length of two bytes must be decoded first. .

In order to better understand the decoding method of the present invention, the embodiment provides a method for extracting protocol-related information from a layer three standard protocol document and saving the data in an abstracted data structure format to the database, the method mainly includes The following steps:

Step 201: Open a word document about the layer three standard protocol, open a macro environment based on the word document, and extract detailed information in the word document by using a VBS language in the macro environment.

Here, the VBS language is an abbreviation of Visual Basic Script.

Here, you can open the macro environment with the "ALT+F11" shortcut.

Here, the layer three standard protocol may be the 24008 protocol.

Step 202: Find a message description table according to the message type definition table, and read the message description information.

In this embodiment, step 202 specifically includes the following steps:

Step 202a: Cycle through the message type definition table and read the first information in the last cell (Cell) of each row;

The information in the last cell of each row is a message name defined by the message type definition table, that is, the first information is a message name.

Step 202b: Perform a search by using the message name + message content acquired in step 202a as a key, determine the first table under the keyword as a message description table of the message, and cyclically read the cell in units of cells. The contents of the first table are described until the current message description table is read.

Here, the message description table is composed of a plurality of members, wherein each member occupies one or more rows of the table.

In this embodiment, the content in the first table is cyclically read in units of cells, and when the cell containing the chapter number is read, it indicates that the current member has finished reading. In addition, if it is a member of multiple lines, it needs to be merged and saved to the defined variables.

For example, taking the 24008 protocol document as an example, when the cell contains "10." or "9.", it indicates that the current member has finished reading. That is to say, conditions can be added specifically according to the chapters in the protocol document.

Step 202c: Loop two steps of step 202a and step 202b until the messages in all message type definition tables are read.

Step 203: Save the message description information read in step 202 into a variable, and store the variable information in a database.

In this embodiment, the variable information includes: an option tag value (IEI value), a name, a type, a chapter number, a length, and a format.

Among them, the format mainly includes the following: T, TV, V, TLV, LV, LV-E, TLV-E.

In this embodiment, the variable information is saved in the database, including:

The message name is the key value, and the node content under the key value corresponds to the variable information.

Step 204: Read cell description information of each member.

In this embodiment, the cell description information of the member may be read by the following steps:

Step 204a: Cycle through the chapter number information.

Here, when step 202 reads the message description message, the chapter information of each member is uniformly saved into an array, and the chapter number information in the array is obtained cyclically.

Step 204b: The chapter number is a keyword, and the searched keyword is "title" information, and the first table below the keyword is searched, and the first table is determined as the cell description table of the current member.

Step 204c: Find a cell description table of the current member, and obtain a width of a bit.

Here, the obtaining the width of the bit bit includes: first obtaining the width of the cell description table of the current member, and dividing the width of the cell description table of the current member by 8, thereby obtaining the width of the bit, where The width of the bit can be expressed as "len".

Step 204d): cyclically reading the first table in units of cells, and after reading the first keyword, indicating that the current byte cell reading ends.

Here, the first keyword may be "Octet".

Here, by dividing the width of each cell by the width of the bit, it is obtained that the current cell occupies several bits.

Step 204e: Looping step 204d until the reading of the first table ends.

Step 204f: Save the read cell description information into the structure variable array.

Here, the structure mainly includes: a cell name, a cell length, a cell type, whether to include enumeration description information, and an array structure.

The cell type mainly includes a general type, an array type, an extended type, and an infinite extended type.

Step 205: Save the cell description information read in step 204 to the database.

In this embodiment, the chapter number is a key value, each byte is a child node, and each cell description information is saved as a child node content in a database.

Step 206: Read enumeration description information of each member, and store the enumeration description information in a database.

In this embodiment, the enumeration description information can be read by the following steps:

Step 206a: cyclically obtain chapter number information in the array, the chapter number is a search keyword, and the searched keyword is "title" information, and the second table below the keyword is searched, and the cell is read in units of cells. After reading the second table, after reading the second keyword, the character in front of it is the cell name, continue to read the next cell, and read 0' or 1' to save until it reads non-zero' or Non-1', convert the previously saved binary stream to a decimal integer, then read the next unit The cell, if not empty, is the description of the current enumeration value until the second table is read.

Here, the second keyword is "(OCTET".

Step 206b: cyclically read the structure array, and save the chapter name as a key value, the cell name as a member name, and each enumeration value of the cell as a child node to be saved in the database.

Step 207: Store the preset array in the database.

In this embodiment, the structure name is used as the key value, and the structure cell is a child node, and the preset array information is saved in the database.

In this embodiment, the database may be an Extensible Markup Language (XML) file.

The above embodiments are merely a preferred embodiment of the present invention. It should be noted that the message description information, the cell description information, and the enumeration information are read from the protocol document, and the message description information, the cell description information, and the enumeration information are stored in a database, The preset array information is stored in the database; there is no order.

In order to better understand the decoding method of the present invention, this embodiment provides a specific process for automatic decoding, including:

Step 301: After receiving the code stream, obtain PD information and message type (MsgType) information from the code stream, and determine a message name corresponding to the code stream according to the PD information and the MsgType information.

In an embodiment, the determining, according to the PD information and the MsgType information, a message name corresponding to the code stream, including:

The first byte of the code stream contains PD information, and the second or third byte of the code stream contains MsgType information.

Step 302: Search the message start node in the “Message Description Table” with the message name as a key, find a message description table, and cyclically read each IE child node in the message description table.

Here, the message description table is part of the database.

Step 303: Step 302: When the IE sub-node is read, the message format, the message length information, and the member chapter number are obtained. If the message format includes the length information, the length information is decoded first, and then the length information is Comparing with the standard length information, if the length information is within the standard length range, the decoding is continued; otherwise, the current decoding process is ended;

In this embodiment, if the length information is not included in the message format, the length information does not need to be decoded.

Wherein, the standard length range is pre-stored in a database.

Step 304: Using the obtained member chapter number as a key, find the corresponding chapter under the element (Element) node and the chapter under the enumeration (Enum) node from the "cell description table", and read the member chapter in a loop. Each node below the number.

Here, the "cell description table" is a part of a database, and the "cell description table" stores a cell description table, an enumeration description table, and an array of structures.

It should be noted that the “message description table” and the “cell description table” may exist as independent databases or may be located in the same database.

When decoding the node in step 304, first, the current node type is determined, and then different decoding is performed according to the node type. That is to say, different types of nodes correspond to different decoding interfaces.

Here, the node type may be a general type, or a general extension type, or a wireless extension type, or an array type.

Step 305: When the node type is a general type, it may be directly decoded according to the length of the node. If the description value needs to be enumerated, the enumeration description value is obtained from the cell description table according to the currently decoded value.

Step 306: When the node is of the general extension type, it decodes the extension bit of one bit. If it is 0, it returns to step 304. If it is 1, it needs to jump out the same byte as the current byte number. For example, octet3 needs to jump out of octet3a. , octet3b...., etc., until jumping to byte octet4, repeating back to step 304.

Step 307: When the node is of the wireless extension type, it decodes a bit extension bit. If it is 0, it decodes in the current byte cycle; if it is 1, it jumps out the same byte as the current byte number.

Step 308: When the node is an array type, the structure name is used as a key, and the corresponding node below the array is found, and the node is cyclically read.

Here, there are three types of nodes that are cyclically read in step 308: a general type, a length type, and a dependent length type; wherein, for a general type, it can be directly decoded according to the length; for a length type, it is decoded according to the length and saved to the length variable, To facilitate the use of the following nodes; for the dependent length type, the decoding is performed according to the decoded length until the end of the code stream.

Step 309: Repeat the above 8 steps until the current message node is empty or the code stream is empty, and it is judged that the decoding ends.

Based on the message description table storage format, the cell description table storage format, the enumeration description storage format, and the array storage format described above, the present invention also proposes a decoding apparatus.

FIG. 6 is a schematic structural diagram of a decoding apparatus according to an embodiment of the present invention. As shown in FIG. 6, the decoding apparatus includes an extraction module 61 and a decoding module 62.

The extracting module 61 is configured to extract protocol related information from a standard protocol document, and save the protocol related information into a database in a corresponding data structure format;

The decoding module 62 is configured to decode a code stream to be decoded based on information stored in the database.

Preferably, the protocol related information at least includes: message description information, cell description information, Enumerate the description information.

In a specific embodiment, the extraction module 61 includes a setting submodule 611, a reading submodule 612, and a storage submodule 613;

The setting sub-module 611 is configured to preset a first storage format, where the first storage format includes a message description table storage format, a cell description table storage format, an enumeration description table storage format, and an array type storage format. ;

The reading sub-module 612 is configured to read the standard protocol document, and extract message description information, cell description information, and enumeration description information from the protocol document;

The storage submodule 613 is configured to store the message description information, the cell description information, and the enumeration description information into a database in a corresponding storage format based on the first storage format.

In a specific embodiment, the decoding module 62 includes an obtaining submodule 621, a determining submodule 622, and a processing submodule 623;

The acquiring sub-module 621 is configured to: after receiving the code stream to be decoded, obtain relevant parameters required for decoding from the code stream;

The determining sub-module 622 is configured to determine a message name corresponding to the code stream according to the relevant parameters required for decoding;

The processing sub-module 623 is configured to acquire, by using the message name as a key, a message node corresponding to the message name, loop through the child nodes under the message, and obtain a format attribute value of the child node, if If the format attribute value of the child node is optional, it jumps to the optional decoding process, otherwise it enters the mandatory decoding process until the end of the code stream or the end of the node, and the current message decoding ends.

The optional decoding process includes:

First, the optional start node is obtained, and each time the option is decoded, starting from the optional start node, the option tag value actually obtained through the current code stream is selected from the standard in the database. The item tag value is matched. If the match is successful, the current node is obtained, and the required decoding interface is decoded.

The required decoding process includes:

It will be understood by those skilled in the art that the implementation functions of the units in the decoding apparatus shown in FIG. 6 can be understood by referring to the related description of the foregoing decoding method.

In an actual application, the extraction module 61 and the decoding module 62 may be a central processing unit (CPU), a microprocessor (MPU, a Micro Processor Unit), a digital signal processor (DSP, Digital) in a terminal to which the decoding device belongs. Signal Processor) or Field Programmable Gate Array (FPGA) implementation.

The embodiment of the invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the foregoing decoding method.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, such as: multiple units or components may be combined, or Can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, or direct coupling, or communication connection of the components shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical, mechanical or other forms. of.

The units described above as separate components may or may not be physically separated. The components displayed as the unit may be, or may not be, physical units, that is, may be located in one place, or may be distributed to multiple network units; some or all of the units may be selected according to actual needs to implement the solution of the embodiment. purpose.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may be separately used as one unit, or two or more units may be integrated into one unit; The unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to the program instructions. The foregoing program may be stored in a computer readable storage medium, and the program is executed when executed. The foregoing storage device includes the following steps: The foregoing storage medium includes: a removable storage device, a read-only memory (ROM), a magnetic disk, or an optical disk, and the like, which can store program codes.

Alternatively, the above-described integrated unit of the present invention may be stored in a computer readable storage medium if it is implemented in the form of a software function module and sold or used as a standalone product. Based on such understanding, the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions. A computer device (which may be a personal computer, server, or network device, etc.) is caused to perform all or part of the methods described in various embodiments of the present invention. The foregoing storage medium includes various media that can store program codes, such as a mobile storage device, a ROM, a magnetic disk, or an optical disk.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and scope of the invention are intended to be included within the scope of the invention.

Industrial applicability

In the embodiment of the present invention, protocol related information is extracted from a standard protocol document, and the association is The related information is saved in the database in the corresponding data structure format; the code stream to be decoded is decoded based on the information stored in the database; thus, automatic decoding of the protocol document described in a tabular form can be realized, and the table format is solved. The described protocol cannot achieve the problem of automated decoding.

Claims

A decoding method, the method comprising:

Extracting protocol-related information from the standard protocol document, and saving the protocol-related information to the database in a corresponding data structure format;

The code stream to be decoded is decoded based on the information stored in the database.
The method according to claim 1, wherein the protocol related information comprises at least: message description information, cell description information, and enumeration description information.
The method of claim 2, wherein the extracting the protocol-related information from the standard protocol document and saving the protocol-related information to the database in a corresponding data structure format comprises:

Setting a first storage format, where the first storage format includes a message description table storage format, a cell description table storage format, an enumeration description table storage format, and an array type storage format;

Reading the standard protocol document, and extracting message description information, cell description information, and enumeration description information from the protocol document;

And based on the first storage format, storing the message description information, the cell description information, and the enumeration description information in a corresponding storage format into a database.
The method of claim 2, wherein the decoding of the code stream to be decoded based on information stored by the database comprises:

After receiving the code stream to be decoded, obtaining relevant parameters required for decoding from the code stream;

Determining a message name corresponding to the code stream according to the relevant parameters required for decoding;

Obtaining, by using the message name as a key, a message node corresponding to the message name, cyclically parsing the child node under the message, and obtaining a format attribute value of the child node, if the format attribute value of the child node is an optional item Then, jump to the optional decoding process, otherwise enter the mandatory decoding process until the end of the code stream or the end of the node, the current message decoding ends.
The method of claim 4, wherein the optional decoding process comprises:

First, the optional start node is obtained. Each time the option is decoded, starting from the optional start node, the option tag value actually obtained by the current code stream is matched with the standard optional tag value in the database, if it matches Successfully, get the current node, call the required decoding interface to decode.
The method of claim 4, wherein the mandatory decoding process comprises:

If the length information is included in the message format attribute value, the length information is first decoded, and then the length information is compared with the standard length information, and if the length information is within the standard length range, The decoding is continued, otherwise, the current decoding process is ended; if the length information is not included in the message format attribute value, the length information does not need to be decoded; until the decoding length is 0, the current message decoding ends.
A decoding device, the decoding device comprising an extraction module and a decoding module; wherein

The extracting module is configured to extract protocol related information from a standard protocol document, and save the protocol related information to a database in a corresponding data structure format;

The decoding module is configured to decode a code stream to be decoded based on information stored in the database.
The decoding apparatus according to claim 7, wherein the protocol related information at least includes message description information, cell description information, and enumeration description information.
The decoding device according to claim 7, wherein the extraction module comprises a setting submodule, a reading submodule, and a storage submodule; wherein

The setting submodule is configured to preset a first storage format, where the first storage format includes a message description table storage format, a cell description table storage format, an enumeration description table storage format, and an array type storage format;

The reading submodule is configured to read the standard protocol document, and extract message description information, cell description information, and enumeration description information from the protocol document;

The storage submodule is configured to store the message description information, the cell description information, and the enumeration description information in a corresponding storage format into a database based on the first storage format.
The decoding device according to claim 7, wherein the decoding module comprises an acquisition submodule, a determination submodule, and a processing submodule; wherein

The acquiring submodule is configured to: after receiving the code stream to be decoded, obtain relevant parameters required for decoding from the code stream;

The determining submodule is configured to determine a message name corresponding to the code stream according to the relevant parameters required for decoding;

The processing submodule is configured to acquire a message node corresponding to the message name by using the message name as a key, loop through the child nodes under the message, and obtain a format attribute value of the child node, if the child If the format attribute value of the node is optional, it will jump to the optional decoding process, otherwise it will enter the mandatory decoding process until the end of the code stream or the end of the node, and the current message decoding ends.
The decoding device according to claim 10, wherein the optional decoding process comprises:

First, the optional start node is obtained. Each time the option is decoded, starting from the optional start node, the option tag value actually obtained by the current code stream is matched with the standard optional tag value in the database, if the matching is successful. Get the current node and call the required decoding interface to decode.
The decoding apparatus according to claim 10, wherein the required decoding process comprises:

If the length information is included in the message format attribute value, the length information is first decoded, and then the length information is compared with the standard length information, and if the length information is within the standard length range, Continue decoding, otherwise, end the current decoding process; If the length information is not included in the message format attribute value, the length information does not need to be decoded; until the decoding length is 0, the current message decoding ends.
A computer storage medium having stored therein computer executable instructions for performing the method of any one of claims 1 to 6.