CN116615874A - Data transmission method and device and communication equipment - Google Patents

Abstract

An embodiment of the present application provides a data transmission method and device, and a communication device. The method includes: the first device sends a first signaling to the second device, and the data carried in the first signaling is encoded using a first TLV format ; Wherein, the first TLV format is used to determine the first TLV structure, and the first TLV structure includes a ControlByte field, a Tag field, and at least one of the following: a Length field, and a Value field.

Description

A data transmission method and device, and communication equipment technical field

The embodiments of the present application relate to the field of mobile communication technologies, and in particular to a data transmission method and device, and communication equipment.

Background technique

The data transmitted between the client and the server is encoded and decoded in TLV format. The current TLV format indicates that the TLV structure includes a tag (Tag) field, a length (Length) field and a value (Value) field. A basic data element includes the above three fields, where the Tag field is used to describe the label of the data, the Length field is used to describe the length of the Value field, and the Value field is used to describe the Value of the data (that is, the attribute of the tag described by the Tag field value). When the above TLV format is used for encoding and decoding, due to the lack of some control information, the encoding and decoding efficiency is low.

Contents of the invention

Embodiments of the present application provide a data transmission method and device, and communication equipment.

The data transmission method provided in the embodiment of this application includes:

The first device sends first signaling to the second device, where the data carried in the first signaling is encoded in a first TLV format; wherein,

The first TLV format is used to determine a first TLV structure, and the first TLV structure includes a control byte (ControlByte) field, a Tag field, and at least one of the following: a Length field and a Value field.

The data transmission method provided in the embodiment of this application includes:

The second device receives the first signaling sent by the first device, where the data carried in the first signaling is encoded in a first TLV format; wherein,

The first TLV format is used to determine a first TLV structure, and the first TLV structure includes a ControlByte field, a Tag field, and at least one of the following: a Length field and a Value field.

The data transmission device provided in the embodiment of the present application is applied to the first device, and the device includes:

A sending unit, configured to send a first signaling to a second device, where the data carried in the first signaling is encoded in a first TLV format; wherein,

The first TLV format is used to determine a first TLV structure, and the first TLV structure includes a ControlByte field, a Tag field, and at least one of the following: a Length field and a Value field.

The data transmission device provided in the embodiment of the present application is applied to the second device, and the device includes:

The receiving unit is configured to receive the first signaling sent by the first device, where the data carried in the first signaling is encoded in the first TLV format; wherein,

The first TLV format is used to determine a first TLV structure, and the first TLV structure includes a ControlByte field, a Tag field, and at least one of the following: a Length field and a Value field.

The communication device provided in the embodiment of the present application includes a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory to execute the above data transmission method.

The chip provided in the embodiment of the present application is used to implement the above data transmission method.

Specifically, the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the above-mentioned data transmission method.

The computer-readable storage medium provided by the embodiment of the present application is used for storing a computer program, and the computer program causes the computer to execute the above-mentioned data transmission method.

The computer program product provided by the embodiments of the present application includes computer program instructions, and the computer program instructions cause a computer to execute the above data transmission method.

The computer program provided by the embodiment of the present application, when running on a computer, enables the computer to execute the above-mentioned data transmission method.

Through the above technical scheme, a novel TLV format (i.e. the first TLV format) is proposed, and the TLV structure determined by the novel TLV format (i.e. the first TLV structure) includes a control byte (ControlByte) field, a Tag field , and at least one of the following: Length field, Value field. Since the first TLV structure has a ControlByte field, the ControlByte field can be used to describe some control information related to other fields, which improves the efficiency of encoding and decoding, and realizes a TLV structure suitable for applications.

Description of drawings

The drawings described here are used to provide a further understanding of the application and constitute a part of the application. The schematic embodiments and descriptions of the application are used to explain the application and do not constitute an improper limitation to the application. In the attached picture:

FIG. 1 is an optional communication architecture diagram provided by an embodiment of the present application;

FIG. 2 is a schematic flow diagram of a data transmission method provided in an embodiment of the present application;

FIG. 3 is a schematic diagram of the interaction between the client and the server provided by the embodiment of the present application;

FIG. 4 is a first schematic diagram of the structure and composition of the data transmission device provided by the embodiment of the present application;

FIG. 5 is a second schematic diagram of the structure and composition of the data transmission device provided by the embodiment of the present application;

FIG. 6 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a chip according to an embodiment of the present application.

Detailed ways

Hereinafter, the present application will be described in detail with reference to the drawings and embodiments. It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other. Apparently, the described embodiments are some of the embodiments of the present application, but not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the scope of protection of this application.

It should be noted that the terms "first" and "second" in the description and claims of the present application and the above drawings are used to distinguish similar objects, but not necessarily used to describe a specific sequence or sequence.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the related technologies involved in the embodiments of the present application are described below.

communication architecture

The Open Connectivity Foundation (OCF) defines a client and a server. The server refers to a device that provides resources, and the client refers to a device that accesses resources.

OCF adopts the Representational State Transfer (RESTful) architecture, and uses resources to describe physical devices of the Internet of Things, as well as information such as functional services provided by devices and device status. The device that provides resources is the server, and the device that accesses resources is the client. end. The client and server defined in OCF are logical functional entities, and a device can be a client, a server, or both a client and a server.

The business interaction between the client and the server is realized by performing RESTful operations on resources. RESTful operations can be create-read-update-delete-notify (Create-Retrieve-Update-Delete-Notify, CRUDN) operations. Obviously, CRUDN The operation can be any one or more of the following operations: create (Create), read (Retrieve), update (Update), delete (Delete), notify (Notify). The client is the initiator of the RESTful operation, and the server is the responder of the RESTful operation. The client sends a resource operation request to the server, requesting to operate on the resource on the server, and the server executes the resource operation and returns a response to the client. , the response carries the content and description information of the resource.

Figure 1 is an optional communication architecture diagram provided by the embodiment of the present application. The description of resources is a resource model layer, and each resource corresponds to a specific uniform resource identifier (Uniform Resource Identifier, URI), which can be accessed through URI to access this resource, and each resource has a corresponding interface that supports Restful operations. It is the transmission protocol layer that transmits resource content and description information. By mapping the resource operation to a specific transmission protocol, the Restful operation of each resource is transformed into a physical message that is transmitted between devices, providing means for the interconnection and intercommunication between devices.

OCF’s transport protocol adopts Constrained Application Protocol (CoAP) to carry resource operations. Each CRUDN operation is mapped to a CoAP request message or response message. The client can pass GET, POST, and DELETE in CoAP. The method operates on the resource on the server side, so as to realize the conversion of the resource state.

TLVs

The data transmitted between the client and the server is encoded and decoded in TLV format. TLV is a type of Basic Encoding Rule (BER) encoding and complies with the ASN1 standard. The full name of TLV is: Tag (tag)-Length (length)-Value (value). In the field of IS-IS data communication, a basic data element includes a tlv ternary array, namely Tag-Length-Value. It can also be understood that a basic data element includes three fields, namely Tag field, Length field and Value field. Wherein, the Tag field is used to describe the tag of the data, the Length field is used to describe the length of the Value field, and the Value field is used to describe the Value of the data (that is, the attribute value of the tag described by the Tag field).

The technical solution of the embodiment of this application proposes a TLV format that matches a specific transmission protocol, which is called the first TLV format. It should be noted that the description of the first TLV format can also be replaced by other methods, such as TLV format , or CTLV format, etc. The client and the server can use the first TLV format to encode and decode the content of the payload (ie, the data carried in the signaling) in the signaling interacted with each other.

Fig. 2 is a schematic flow chart of the data transmission method provided by the embodiment of the present application. As shown in Fig. 2, the data transmission method includes the following steps:

Step 201: The first device sends the first signaling to the second device, and the second device receives the first signaling sent by the first device, and the data carried in the first signaling is encoded using the first TLV format; wherein, The first TLV format is used to determine a first TLV structure, and the first TLV structure includes a ControlByte field, a Tag field, and at least one of the following: a Length field and a Value field.

In an optional manner of the present application, referring to FIG. 3 , the first device is a client, and the second device is a server. The first signaling is a resource operation request message. Here, the resource operation request message may be, for example, a service (Server) state modification request message. The data carried in the first signaling is encoded using the first TLV format provided by the embodiment of the present application. After receiving the resource operation request message, the server decodes the first signaling according to the first TLV format provided by the embodiment of this application, thereby obtaining the data carried in the first signaling, and performs corresponding operations according to the data, such as attribute Change operation.

In another optional manner of the present application, referring to FIG. 3 , the first device is a server, and the second device is a client. The first signaling is a response message. The data carried in the response message is encoded using the first TLV format provided by the embodiment of the present application. After receiving the response message, the client decodes the first signaling according to the first TLV format provided by the embodiment of the present application, so as to obtain the data carried in the first signaling.

The first TLV format in this embodiment of the present application is used to determine the first TLV structure, and the first TLV structure includes a ControlByte field, a Tag field, and at least one of the following: a Length field and a Value field.

In an optional manner, the first TLV structure includes a ControlByte field and a Tag field.

In an optional manner, the first TLV structure includes a ControlByte field, a Tag field and a Value field.

In an optional manner, the first TLV structure includes a ControlByte field, a Tag field, a Length field, and a Value field.

In this embodiment of the present application, the ControlByte field is used to describe the control information of other fields, for example, the control information of the Tag field and/or the control information of the Value field. Wherein, the control information of the Tag field includes the description of the Tag. The control information of the Value field includes the data type of the Value, and optionally, the length of the Length field and/or the length of the Value field.

In this embodiment of the application, the Tag field is used to describe a tag of data.

In this embodiment of the present application, the Length field is used to describe the length of the Value field.

In the embodiment of the present application, the Value field is used to describe the Value of the data (that is, the attribute value corresponding to the label).

In an example, the content of the Tag field is 0X12, which means the tag is temperature. The content of the Value field is 15, which means that the value of the temperature is 15 degrees (15 degrees).

Each field in the above scheme is described in detail below.

(1) ControlByte field

In the embodiment of the present application, the length of the ControlByte field is N1 bytes, and the value of N1 is a positive integer. In an optional manner, the value of N1 is 1, that is, the length of the ControlByte field is 1 byte.

In this embodiment of the present application, the ControlByte field includes two parts, namely a first part and a second part, wherein the first part may also be called a tagControl part, and the second part may also be called an elementType part. Wherein, the first part is used to determine the related control information of the Tag field, and the second part is used to determine the related control information of the Value field.

In an optional manner, the first part of bits in the ControlByte field is the upper 3 bits in the ControlByte field. For example: Bit7-bit5 is the first part of bits. The second part of bits in the ControlByte field is the lower 5 bits in the ControlByte field. For example, Bit4-bit0 are the second part of bits.

In this embodiment of the present application, the first part of bits in the ControlByte field is used to indicate that the use of the data is one of the following: general for device access, general for device control, general for device control. Further, the first part of bits in the ControlByte field is also used to indicate the description of the Tag. Here, the description of the Tag is used to determine at least one of the following: the length of the Tag field, and the tag type described by the Tag field is an attribute identification tag (iid tag) or an index tag (index tag) or a device identification tag (DeviceID tag) Or a transaction identification tag (ID tag) or a service identification tag (siid tag).

It should be noted that, the tag type described by the Tag field is, for example: the tag type described by the Tag field is an attribute identification tag (iid tag) or an index tag (index tag).

In this embodiment of the present application, the second part of bits in the ControlByte field is used to indicate the data type of the Value described by the Value field. Further, the second part of bits in the ControlByte field is also used to indicate at least one of the following: the length of the Length field, and the length of the Value field. Or, the second part of bits in the ControlByte field is also used to indicate: the terminator of the container data type.

In an example, the following Table 1-1 and Table 1-2 give the content indicated by the different values of the first part of bits (ie Bit7-bit5) in the ControlByte field, and the second part of bits (ie Bit4 The content indicated under different values of -bit0).

Table 1-1

Table 1-2

The following describes how the first part of bits (ie, Bit7-bit5) and the second part of bits (ie, Bit4-bit0) in the ControlByte field perform information indication in combination with the above-mentioned Table 1-1 and Table 1-2.

In an example, when the value of the second part of bits (ie Bit4-bit0) in the ControlByte field is 00000, the second part of bits is used to indicate that the data type of Value is an 8-bit unsigned integer (uint8) , and there is no Length field (it can also be understood that the length of the Length field is 0 bytes), and the length of the Value field is 1 byte.

In an example, when the value of the second part of bits (ie, Bit4-bit0) in the ControlByte field is 00100, the second part of bits is used to indicate that the data type of Value is an 8-bit signed integer (int8) , and there is no Length field (it can also be understood that the length of the Length field is 0 bytes), and the length of the Value field is 1 byte.

In an example, when the value of the second part of bits (ie Bit4-bit0) in the ControlByte field is 01000, the second part of bits is used to indicate that the data type of Value is a boolean type, and the data The value of is false (false), and there is no Length field (it can also be understood that the length of the Length field is 0 bytes) and no Value field (it can also be understood that the length of the Value field is 0 bytes).

In an example, when the value of the second part of bits (that is, Bit4-bit0) in the ControlByte field is 01010, the second part of bits is used to indicate that the data type of Value is a floating point (float) type, and there is no The Length field (it can also be understood as the length of the Length field is 0 bytes), and the length of the Value field is 4 bytes.

In an example, when the value of the second part of bits (ie, Bit4-bit0) in the ControlByte field is 10000, the second part of bits is used to indicate that the data type of Value is bytes, and Length The length of the field is 1 byte, and the Value field is of variable length.

In an example, when the value of the second part of bits (that is, Bit4-bit0) in the ControlByte field is 10100, the second part of bits is used to indicate that the data type of Value is a string type, and Length The length of the field is 1 byte, and the Value field is of variable length.

In an example, when the value of the second part of bits (ie Bit4-bit0) in the ControlByte field is 11001, the second part of bits is used to indicate that the data type of Value is a structure (struct) type, and Length Field and Value fields are variable length.

In an example, when the value of the second part of bits (ie, Bit4-bit0) in the ControlByte field is 11010, the second part of bits is used to indicate that the data type of the Value is an array type, and the Length field and Value fields are variable length.

In an example, when the value of the second part of bits (that is, Bit4-bit0) in the ControlByte field is 11011, the second part of bits is used to indicate the terminator of the struct, and the value of Bit5-bit7 is 000 .

In an example, when the value of the second part of bits (that is, Bit4-bit0) in the ControlByte field is 11100, the second part of bits is used to indicate the terminator of the array, and the value of Bit5-bit7 is 000 .

It should be noted that the above-mentioned unsigned integer type, signed integer type, Boolean type, floating point type, and byte type belong to basic data types. String types are reference types. Structure types and array types are container data types.

In an example, when the value of the first part of bits (that is, Bit7-bit5) in the ControlByte field is 001, the second part of bits is used to indicate that the purpose of the data is general for device access.

In an example, when the value of the first part of bits (ie Bit7-bit5) in the ControlByte field is 010, the second part of bits is used to indicate that the purpose of the data is for device control, and the tag described in the Tag field The type is iid tag, and the length of the Tag field is 1 byte. In this case, the tag value (that is, the value of the Tag field) is the iid value, and the value value (that is, the value of the Value field) is the attribute value corresponding to idd. Here, iid is the unique identifier of an attribute, event, or method within the service.

In an example, when the value of the first part of bits (namely Bit7-bit5) in the ControlByte field is 100, the second part of bits is used to indicate that the purpose of the data is for device control, and the tag described in the Tag field The type is index tag, and the length of the Tag field is 1 byte. In this case, index is used to mark subelements of struct data type or array data type, the tag value (that is, the value of the Tag field) is the index value, and the value value (that is, the value of the Value field) is the subelement of the index tag The value of the element.

In an example, when the value of the first part of bits (that is, Bit7-bit5) in the ControlByte field is 110, the second part of bits is used to indicate that the purpose of the data is general purpose for device control.

In one example, for general equipment control, referring to Table 1-2, four situations are further subdivided, and the use of each situation can be called equipment control. For the first case, the tag value (i.e. the value of the Tag field) is 0x1, representing the DeviceID tag, and the value value (i.e. the value of the Value field) is the deviceID value, where deviceID is the ID identifying a device. For the second case, the tag value (that is, the value of the Tag field) is 0x2, which represents the transaction ID tag, and the value value (that is, the value of the Value field) is the transaction ID value. Here, the transaction ID is a set of associated The identifier of the signaling flow. For the third case, the tag value (that is, the value of the Tag field) is 0x3, which represents the siid tag, and the value value (that is, the value of the Value field) is a siid value with a length of 1 byte. Here, siid is a The ID of the service instance. For the fourth case, the tag value (that is, the value of the Tag field) is 0x4, which represents the siid tag, and the value value (that is, the value of the Value field) is a siid value with a length of 2 bytes. Here, siid is a The ID of the service instance.

(2) Tag field

In the embodiment of the present application, the length of the Tag field is N2 bytes, and N2 is a positive integer. In an optional manner, the value of N2 is greater than or equal to 0 and less than or equal to 8, that is, the length of the Tag field is 0-8 bytes.

In an example, the structure of the byte occupied by the Tag field is shown in Table 2-1 below, where the highest bit (bit7) of the byte is the Tag length identification bit, and the lower 7 bits of the byte (bit6- bit0) is used to identify the Tag value.

table 2-1

In another example, the structure of the byte occupied by the Tag field is shown in Table 2-2 below, wherein all bits (ie, bit7-bit0) of the byte are used to identify the Tag value.

Table 2-2

The Tag field can occupy one or more bytes. In the embodiment of the present application, the length and value of the Tag field can be determined through the following solutions.

Solution 1) The Tag field occupies the first byte, if the value of the highest bit in the first byte is the first value, it means that the Tag field only occupies the first byte, and the The value of the Tag field is determined by the lower 7 bits in the first byte; wherein, the highest bit in the first byte is a Tag length identification bit.

In an optional manner, the first value is 0. Specifically, when the value of the Tag length identification bit in a byte is 0, Bit6-bit0 is used to identify the tag value (that is, to determine the value of the Tag field).

Solution 2) The Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field also occupies the first byte after the first byte. Two bytes and a third byte, and the value of the Tag field is determined by all bits in the second byte and all bits in the third byte; wherein, the first word The highest bit in the section is the Tag length identification bit.

In an optional manner, the second value is 1. Specifically, when the value of the Tag length identification bit in a byte (that is, the first byte) is 1, it means that the two bytes following the byte also belong to the Tag field, and the following two characters are used All bits of the section are used to identify the tag value (that is, to determine the value of the Tag field). It should be noted that bit6-bit0 in the first byte are not used.

Solution 3) The Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field also occupies the first byte after the first byte. Two bytes, and the value of the Tag field is determined by the lower 7 bits in the first byte and all bits in the second byte; wherein, the highest bit in the first byte Identifies the length of the Tag.

In an optional manner, the second value is 1. Specifically, when the value of the Tag length identification bit of a byte (that is, the first byte) is 1, it means that the byte following the byte also belongs to the Tag field, and the value of the first byte is used bit6-bit0 and bit7-bit0 of the next byte to identify the tag value (that is, to determine the value of the Tag field).

Solution 4) The Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field also occupies the first byte after the first byte. Two bytes, if the value of the highest bit of the second byte is the second value, it means that the Tag field also occupies the third byte after the second byte, and so on until the The value of the highest bit in the Mth byte occupied by the Tag field is the first value, and the Mth byte is taken as the last byte occupied by the Tag field, and M is a positive integer; the value of the Tag field It is determined by the lower 7 bits in each byte of the first byte to the Mth byte.

In an optional manner, the second value is 1, and the first value is 0. Specifically, when the Tag length identification bit of a byte (i.e. the first byte) is 1, it means that a byte immediately following the byte (i.e. the second byte) also belongs to the Tag field; if the second word If the Tag length flag of the section is also 1, it means that the byte following the byte (i.e. the third byte) also belongs to the Tag field, and so on until the Tag length flag of the Mth byte is 0 , then the Mth byte is the last byte occupied by the Tag field. Use bit6-bit0 of each byte to identify the tag value (that is, to determine the value of the Tag field).

Taking the Tag field occupying two bytes as an example, Table 3 below shows that the Tag field occupies the first byte and the second byte. Among them, the Tag length identification bit of the first byte is 1, which means that the first byte is followed by a byte (that is, the second byte) also belongs to the Tag field, and the Tag length identification bit of the second byte is 0, representing The second byte is the last byte occupied by the Tag field. Using bit6-bit0 of the first byte and bit6-bit0 of the second byte to identify the tag value (that is, determine the value of the Tag field) is: 00000010000001 (binary)=129 (decimal). Among them, the first half of the binary data 0000001 corresponds to bit6-bit0 of the first byte, and the second half of 0000001 corresponds to bit6-bit0 of the second byte. After the two parts are combined, a tag value is "129". It should be noted that if there are three or more bytes, the same can be done.

table 3

Scheme 5) The length of the Tag field is determined based on the first part in the ControlByte field, the first part in the ControlByte field is used to indicate the description of the Tag, and the description of the Tag is used to determine at least one of the following: Tag field length, and the tag type described in the Tag field is iid tag or index tag or DeviceID tag or transaction ID tag or siid tag.

For scheme five), the length of the Tag field can be determined directly according to the first part (namely the tagControl part) in the ControlByte field. Specifically, the indication content corresponding to the value of the first part in the ControlByte field can be determined with reference to the content shown in the above Table 1-1.

(3) Length field

In the embodiment of the present application, the length of the Length field is N3 bytes, and N3 is a positive integer. In an optional manner, the value of N3 is greater than or equal to 0 and less than or equal to 8, that is, the length of the Length field is 0-8 bytes.

In this embodiment of the application, for some data types (such as basic data types), the length of the Length field is determined based on the second part in the ControlByte field, and the second part in the ControlByte field is used to indicate the Length field length.

It should be noted that the Length field of container data types (such as struct type and array type) has a variable length, so a variable length method can be used to determine its length. In an optional manner, the terminator of the struct or array may be used to identify the end position of a struct or struct, so as to determine the length of the Length field according to the end position.

It should be noted that the basic data types are, for example, unsigned integer (uint), signed integer (nit), and floating point (float) shown in Table 2-1. The container data type is, for example, the structure (struct) type and array (array) type shown in Table 2-1.

(4) Value field

In the embodiment of the present application, the length of the Value field is N4 bytes, and the value of N4 is a positive integer.

In this embodiment of the present application, the length of the Value field is determined based on the second part in the ControlByte field, and the second part in the ControlByte field is used to indicate the length of the Value field of the basic data type; or, the ControlByte The second part of the field is used to indicate the terminator of the container data type.

The above technical solution of the embodiment of the present application provides a new type of TLV structure (i.e. the first TLV structure). In one example, the following table 4 shows the overall structure of the first TLV structure, wherein the length of the ControlByte field The length of the Tag field is 0 to 8 bytes, the length of the Length field is 0 to 8 bytes, and the value field has a variable length according to the content.

ControlByte tag Length value 1byte 0-8bytes 0-8bytes lengthen

Table 4

The client and the server can use the first TLV format in the above solution to encode and decode the content of the payload (ie, the data carried in the signaling) in the signaling interacted with each other, thereby improving the efficiency of encoding and decoding.

Fig. 4 is a schematic diagram of the structure and composition of the data transmission device provided by the embodiment of the present application. It is applied to the first device. As shown in Fig. 4, the data transmission device includes:

A sending unit 401, configured to send a first signaling to a second device, where the data carried in the first signaling is encoded using a first TLV format; wherein,

The first TLV format is used to determine a first TLV structure, and the first TLV structure includes a ControlByte field, a Tag field, and at least one of the following: a Length field, and a Value field.

In an optional manner, the length of the ControlByte field is N1 bytes, and the value of N1 is a positive integer.

In an optional manner, the value of N1 is 1.

In an optional manner, the first part of bits in the ControlByte field is used to indicate that the usage of the data is one of the following: general for device access, general for device control, general for device control.

In an optional manner, the first part of bits in the ControlByte field is also used to indicate the description of the Tag.

In an optional manner, the description of the Tag is used to determine at least one of the following

The length of the Tag field;

The tag type described in the Tag field is iid tag or index tag or DeviceID tag or transaction ID tag or siid tag.

In an optional manner, the first part of bits in the ControlByte field is the upper 3 bits in the ControlByte field.

In an optional manner, the second part of bits in the ControlByte field is used to indicate the data type of the Value described by the Value field.

In an optional manner, the second part of bits in the ControlByte field is also used to indicate at least one of the following: the length of the Length field, and the length of the Value field.

In an optional manner, the second part of bits in the ControlByte field is also used to indicate: the terminator of the container data type.

In an optional manner, the second part of bits in the ControlByte field is the lower 5 bits in the ControlByte field.

In an optional manner, the length of the Tag field is N2 bytes, and N2 is a positive integer.

In an optional manner, the value of N2 is greater than or equal to 0 and less than or equal to 8.

In an optional manner, the Tag field occupies the first byte, and if the value of the highest bit in the first byte is the first value, it means that the Tag field only occupies the first byte , and the value of the Tag field is determined by the lower 7 bits in the first byte; wherein, the highest bit in the first byte is the Tag length identification bit.

In an optional manner, the Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field also occupies the first byte The second byte and the third byte after the section, and the value of the Tag field is determined by all the bits in the second byte and all the bits in the third byte; wherein, The highest bit in the first byte is the Tag length identification bit.

In an optional manner, the Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field also occupies the first byte The second byte after the section, and the value of the Tag field is determined by the lower 7 bits in the first byte and all bits in the second byte; wherein, the first byte The highest bit in is the Tag length identification bit.

In an optional manner, the Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field also occupies the first byte The second byte after the second byte, if the highest bit of the second byte is the second value, it means that the Tag field also occupies the third byte after the second byte, and so on , until the value of the highest bit in the Mth byte occupied by the Tag field is the first value, the Mth byte is taken as the last byte occupied by the Tag field, and M is a positive integer; the Tag The value of the field is determined by the lower 7 bits in each byte of the first byte to the Mth byte.

In an optional manner, the length of the Tag field is determined based on the first part in the ControlByte field, the first part in the ControlByte field is used to indicate the description of the Tag, and the description of the Tag is used to determine at least one of the following 1: The length of the Tag field, and the tag type described by the Tag field is iid tag or index tag or DeviceID tag or transaction ID tag or siid tag.

In an optional manner, the length of the Length field is N3 bytes, and N3 is a positive integer.

In an optional manner, the value of N3 is greater than or equal to 0 and less than or equal to 8.

In an optional manner, the length of the Length field is determined based on a second part in the ControlByte field, and the second part in the ControlByte field is used to indicate the length of the Length field.

In an optional manner, the length of the Value field is N4 bytes, and the value of N4 is a positive integer.

In an optional manner, the length of the Value field is determined based on the second part in the ControlByte field,

The second part in the ControlByte field is used to indicate the length of the Value field of the basic data type; or, the second part in the ControlByte field is used to indicate the terminator of the container data type.

In an optional manner, the Tag field is used to describe the tag of the data, the Length field is used to describe the length of the Value field, and the Value field is used to describe the Value of the data.

Those skilled in the art should understand that the relevant description of the data transmission apparatus in the embodiment of the present application can be understood with reference to the relevant description of the data transmission method in the embodiment of the present application.

Fig. 5 is a schematic diagram of the second structural composition of the data transmission device provided by the embodiment of the present application, which is applied to the second device. As shown in Fig. 5, the data transmission device includes:

The receiving unit 501 is configured to receive the first signaling sent by the first device, where the data carried in the first signaling is encoded in the first TLV format; wherein,

The first TLV format is used to determine a first TLV structure, and the first TLV structure includes a ControlByte field, a Tag field, and at least one of the following: a Length field, and a Value field.

In an optional manner, the length of the ControlByte field is N1 bytes, and the value of N1 is a positive integer.

In an optional manner, the value of N1 is 1.

In an optional manner, the first part of bits in the ControlByte field is used to indicate that the usage of the data is one of the following: general for device access, general for device control, general for device control.

In an optional manner, the first part of bits in the ControlByte field is also used to indicate the description of the Tag.

In an optional manner, the description of the Tag is used to determine at least one of the following:

The length of the Tag field;

The tag type described in the Tag field is iid tag or index tag or DeviceID tag or transaction ID tag or siid tag.

In an optional manner, the first part of bits in the ControlByte field is the upper 3 bits in the ControlByte field.

In an optional manner, the second part of bits in the ControlByte field is used to indicate the data type of the Value described by the Value field.

In an optional manner, the second part of bits in the ControlByte field is also used to indicate at least one of the following: the length of the Length field, and the length of the Value field.

In an optional manner, the second part of bits in the ControlByte field is also used to indicate: the terminator of the container data type.

In an optional manner, the second part of bits in the ControlByte field is the lower 5 bits in the ControlByte field.

In an optional manner, the length of the Tag field is N2 bytes, and N2 is a positive integer.

In an optional manner, the value of N2 is greater than or equal to 0 and less than or equal to 8.

In an optional manner, the Tag field occupies the first byte, and if the value of the highest bit in the first byte is the first value, it means that the Tag field only occupies the first byte , and the value of the Tag field is determined by the lower 7 bits in the first byte; wherein, the highest bit in the first byte is the Tag length identification bit.

In an optional manner, the Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field also occupies the first byte The second byte and the third byte after the section, and the value of the Tag field is determined by all the bits in the second byte and all the bits in the third byte; wherein, The highest bit in the first byte is the Tag length identification bit.

In an optional manner, the Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field also occupies the first byte The second byte after the section, and the value of the Tag field is determined by the lower 7 bits in the first byte and all bits in the second byte; wherein, the first byte The highest bit in is the Tag length identification bit.

In an optional manner, the Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field also occupies the first byte The second byte after the second byte, if the highest bit of the second byte is the second value, it means that the Tag field also occupies the third byte after the second byte, and so on , until the value of the highest bit in the Mth byte occupied by the Tag field is the first value, the Mth byte is taken as the last byte occupied by the Tag field, and M is a positive integer; the Tag The value of the field is determined by the lower 7 bits in each byte of the first byte to the Mth byte.

In an optional manner, the length of the Tag field is determined based on the first part in the ControlByte field, the first part in the ControlByte field is used to indicate the description of the Tag, and the description of the Tag is used to determine at least one of the following One: The length of the Tag field, and the tag type described in the Tag field is iid tag or index tag or DeviceID tag or transaction ID tag or siid tag.

In an optional manner, the length of the Length field is N3 bytes, and N3 is a positive integer.

In an optional manner, the value of N3 is greater than or equal to 0 and less than or equal to 8.

In an optional manner, the length of the Length field is determined based on a second part in the ControlByte field, and the second part in the ControlByte field is used to indicate the length of the Length field.

In an optional manner, the length of the Value field is N4 bytes, and the value of N4 is a positive integer.

In an optional manner, the length of the Value field is determined based on the second part in the ControlByte field,

The second part in the ControlByte field is used to indicate the length of the Value field of the basic data type; or, the second part in the ControlByte field is used to indicate the terminator of the container data type.

In an optional manner, the Tag field is used to describe the tag of the data, the Length field is used to describe the length of the Value field, and the Value field is used to describe the Value of the data.

Those skilled in the art should understand that the relevant description of the data transmission apparatus in the embodiment of the present application can be understood with reference to the relevant description of the data transmission method in the embodiment of the present application.

FIG. 6 is a schematic structural diagram of a communication device 600 provided in an embodiment of the present application. The communication device may be a first device or a second device, wherein the first device may be a client or a server, and the second device may be a server or a client. The communication device 600 shown in FIG. 6 includes a processing The processor 610, and the processor 610 can invoke and run a computer program from the memory, so as to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 6 , the communication device 600 may further include a memory 620 . Wherein, the processor 610 can invoke and run a computer program from the memory 620, so as to implement the method in the embodiment of the present application.

Wherein, the memory 620 may be an independent device independent of the processor 610 , or may be integrated in the processor 610 .

Optionally, as shown in FIG. 6, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, to send information or data to other devices, or receive other Information or data sent by the device.

Wherein, the transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include antennas, and the number of antennas may be one or more.

Optionally, the communication device 600 may specifically be the network device of the embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, details are not repeated here. .

Optionally, the communication device 600 may specifically be the mobile terminal/terminal device of the embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, for the sake of brevity , which will not be repeated here.

FIG. 7 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 700 shown in FIG. 7 includes a processor 710, and the processor 710 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 7 , the chip 700 may further include a memory 720 . Wherein, the processor 710 can invoke and run a computer program from the memory 720, so as to implement the method in the embodiment of the present application.

Wherein, the memory 720 may be an independent device independent of the processor 710 , or may be integrated in the processor 710 .

Optionally, the chip 700 may also include an input interface 730 . Wherein, the processor 710 may control the input interface 730 to communicate with other devices or chips, specifically, may obtain information or data sent by other devices or chips.

Optionally, the chip 700 may also include an output interface 740 . Wherein, the processor 710 can control the output interface 740 to communicate with other devices or chips, specifically, can output information or data to other devices or chips.

Optionally, the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in the methods of the embodiment of the present application. For the sake of brevity, details are not repeated here.

Optionally, the chip can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiments of the present application. For the sake of brevity, here No longer.

It should be understood that the chip mentioned in the embodiment of the present application may also be called a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip.

It should be understood that the processor in the embodiment of the present application may be an integrated circuit chip, which has a signal processing capability. In the implementation process, each step of the above-mentioned method embodiments may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software. The above-mentioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Program logic devices, discrete gate or transistor logic devices, discrete hardware components. Various methods, steps, and logic block diagrams disclosed in the embodiments of the present application may be implemented or executed. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Wherein, the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electronically programmable Erase Programmable Read-Only Memory (Electrically EPROM, EEPROM) or Flash. The volatile memory can be Random Access Memory (RAM), which acts as an external cache. By way of illustration and not limitation, many forms of RAM are available such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (Synchlink DRAM, SLDRAM ) and direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but not be limited to, these and any other suitable types of memory.

It should be understood that the above-mentioned memory is illustrative but not restrictive. For example, the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is, the memory in the embodiments of the present application is intended to include, but not be limited to, these and any other suitable types of memory.

The embodiment of the present application also provides a computer-readable storage medium for storing computer programs.

Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the methods of the embodiments of the present application. For brevity, here No longer.

Optionally, the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiments of the present application , for the sake of brevity, it is not repeated here.

The embodiment of the present application also provides a computer program product, including computer program instructions.

Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, the Let me repeat.

Optionally, the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the methods of the embodiments of the present application, For the sake of brevity, details are not repeated here.

The embodiment of the present application also provides a computer program.

Optionally, the computer program can be applied to the network device in the embodiment of the present application. When the computer program is run on the computer, the computer executes the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity , which will not be repeated here.

Optionally, the computer program can be applied to the mobile terminal/terminal device in the embodiment of the present application. When the computer program is run on the computer, the computer executes each method in the embodiment of the present application to be implemented by the mobile terminal/terminal device For the sake of brevity, the corresponding process will not be repeated here.

Those skilled in the art can appreciate that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.

If the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other various media that can store program codes. .

The above is only a specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application. Should be covered within the protection scope of this application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims (101)

A data transmission method, the method comprising: The first device sends first signaling to the second device, where the data carried in the first signaling is encoded in a first TLV format; wherein, The first TLV format is used to determine a first TLV structure, and the first TLV structure includes a ControlByte field, a Tag field, and at least one of the following: a Length field, and a Value field. The method according to claim 1, wherein the length of the ControlByte field is N1 bytes, and the value of N1 is a positive integer. The method according to claim 2, wherein the value of N1 is 1. The method according to claim 3, wherein the first part of bits in the ControlByte field is used to indicate that the use of the data is one of the following: general use for device access, general use for device control, and general use for device control. The method according to claim 4, wherein the first part of bits in the ControlByte field is also used to indicate the description of Tag. The method according to claim 5, wherein the description of the Tag is used to determine at least one of the following: The length of the Tag field; The tag type described in the Tag field is an attribute identification tag iid tag or an index tag index tag or a device identification tag DeviceID tag or a transaction identification tag ID tag or a service identification tag siid tag. The method according to any one of claims 4 to 6, wherein the first part of bits in the ControlByte field is the upper 3 bits in the ControlByte field. The method according to any one of claims 3 to 7, wherein the second part of bits in the ControlByte field is used to indicate the data type of the Value described by the Value field. The method according to claim 8, wherein the second part of bits in the ControlByte field is further used to indicate at least one of the following: the length of the Length field, and the length of the Value field. The method according to claim 8, wherein the second part of bits in the ControlByte field is also used to indicate: a terminator of the container data type. The method according to any one of claims 8 to 10, wherein the second part of bits in the ControlByte field is the lower 5 bits in the ControlByte field. The method according to any one of claims 1 to 11, wherein the length of the Tag field is N2 bytes, and N2 is a positive integer. The method according to claim 12, wherein the value of N2 is greater than or equal to 0 and less than or equal to 8. The method according to claim 12 or 13, wherein the Tag field occupies the first byte, and if the value of the highest bit in the first byte is the first value, it means that the Tag field only occupies The first byte, and the value of the Tag field is determined by the lower 7 bits in the first byte; wherein, the highest bit in the first byte is a Tag length identification bit. The method according to claim 12 or 13, wherein the Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field is also Occupies the second byte and the third byte after the first byte, and the value of the Tag field passes through all the bits in the second byte and all the bits in the third byte bit determination; wherein, the highest bit in the first byte is the Tag length identification bit. The method according to claim 12 or 13, wherein the Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field is also Occupies the second byte after the first byte, and the value of the Tag field is determined by the lower 7 bits in the first byte and all bits in the second byte; wherein, The highest bit in the first byte is the Tag length identification bit. The method according to claim 12 or 13, wherein the Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field is also Occupies the second byte after the first byte, if the value of the highest bit of the second byte is the second value, it means that the Tag field also occupies the third byte after the second byte byte, and so on, until the value of the highest bit in the Mth byte occupied by the Tag field is the first value, and the Mth byte is taken as the last byte occupied by the Tag field, and M is A positive integer; the value of the Tag field is determined by the lower 7 bits of each byte in the first byte to the Mth byte. The method according to claim 12 or 13, wherein the length of the Tag field is determined based on the first part in the ControlByte field, the first part in the ControlByte field is used to indicate the description of the Tag, and the description of the Tag It is used to determine at least one of the following: the length of the Tag field, and the tag type described by the Tag field is an attribute identification tag iid tag or an index tag index tag or a device identification tag DeviceID tag or a transaction identification tag ID tag or a service identification tag siid tag. The method according to any one of claims 1 to 18, wherein the length of the Length field is N3 bytes, and N3 is a positive integer. The method according to claim 19, wherein the value of N3 is greater than or equal to 0 and less than or equal to 8. The method according to claim 19 or 20, wherein the length of the Length field is determined based on the second part in the ControlByte field, and the second part in the ControlByte field is used to indicate the length of the Length field. The method according to any one of claims 1 to 21, wherein the length of the Value field is N4 bytes, and the value of N4 is a positive integer. The method according to claim 22, wherein the length of the Value field is determined based on the second part in the ControlByte field, The second part in the ControlByte field is used to indicate the length of the Value field of the basic data type; or, the second part in the ControlByte field is used to indicate the terminator of the container data type. The method according to any one of claims 1 to 23, wherein the Tag field is used to describe the tag of the data, the Length field is used to describe the length of the Value field, and the Value field is used to describe the Value of the data . A data transmission method, the method comprising: The second device receives the first signaling sent by the first device, where the data carried in the first signaling is encoded in a first TLV format; wherein, The first TLV format is used to determine a first TLV structure, and the first TLV structure includes a ControlByte field, a Tag field, and at least one of the following: a Length field, and a Value field. The method according to claim 25, wherein the length of the ControlByte field is N1 bytes, and the value of N1 is a positive integer. The method according to claim 26, wherein the value of N1 is 1. The method according to claim 27, wherein the first part of bits in the ControlByte field is used to indicate that the use of the data is one of the following: general use for device access, general use for device control, and general use for device control. The method according to claim 28, wherein the first part of bits in the ControlByte field is also used to indicate the description of Tag. The method according to claim 29, wherein the description of the Tag is used to determine at least one of the following: The length of the Tag field; The tag type described in the Tag field is an attribute identification tag iid tag or an index tag index tag or a device identification tag DeviceID tag or a transaction identification tag ID tag or a service identification tag siid tag. The method according to any one of claims 28 to 30, wherein the first part of bits in the ControlByte field is the upper 3 bits in the ControlByte field. The method according to any one of claims 27 to 31, wherein the second part of bits in the ControlByte field is used to indicate the data type of the Value described by the Value field. The method according to claim 32, wherein the second part of bits in the ControlByte field is also used to indicate at least one of the following: the length of the Length field and the length of the Value field. The method according to claim 32, wherein the second part of bits in the ControlByte field is also used to indicate: a terminator of the container data type. The method according to any one of claims 32 to 34, wherein the second part of bits in the ControlByte field is the lower 5 bits in the ControlByte field. The method according to any one of claims 25 to 35, wherein the length of the Tag field is N2 bytes, and N2 is a positive integer. The method according to claim 36, wherein the value of said N2 is greater than or equal to 0 and less than or equal to 8. The method according to claim 36 or 37, wherein the Tag field occupies the first byte, and if the value of the highest bit in the first byte is the first value, it means that the Tag field only occupies The first byte, and the value of the Tag field is determined by the lower 7 bits in the first byte; wherein, the highest bit in the first byte is a Tag length identification bit. The method according to claim 36 or 37, wherein the Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field is also Occupies the second byte and the third byte after the first byte, and the value of the Tag field passes through all the bits in the second byte and all the bits in the third byte bit determination; wherein, the highest bit in the first byte is the Tag length identification bit. The method according to claim 36 or 37, wherein the Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field is also Occupies the second byte after the first byte, and the value of the Tag field is determined by the lower 7 bits in the first byte and all bits in the second byte; wherein, The highest bit in the first byte is the Tag length identification bit. The method according to claim 36 or 37, wherein the Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field is also Occupies the second byte after the first byte, if the value of the highest bit of the second byte is the second value, it means that the Tag field also occupies the third byte after the second byte byte, and so on, until the value of the highest bit in the Mth byte occupied by the Tag field is the first value, and the Mth byte is taken as the last byte occupied by the Tag field, and M is A positive integer; the value of the Tag field is determined by the lower 7 bits of each byte in the first byte to the Mth byte. The method according to claim 36 or 37, wherein the length of the Tag field is determined based on the first part in the ControlByte field, the first part in the ControlByte field is used to indicate the description of the Tag, and the description of the Tag It is used to determine at least one of the following: the length of the Tag field, and the tag type described by the Tag field is an attribute identification tag iid tag or an index tag index tag or a device identification tag DeviceID tag or a transaction identification tag ID tag or a service identification tag siid tag. The method according to any one of claims 25 to 42, wherein the length of the Length field is N3 bytes, and N3 is a positive integer. The method according to claim 43, wherein the value of N3 is greater than or equal to 0 and less than or equal to 8. The method according to claim 43 or 44, wherein the length of the Length field is determined based on the second part in the ControlByte field, and the second part in the ControlByte field is used to indicate the length of the Length field. The method according to any one of claims 25 to 45, wherein the length of the Value field is N4 bytes, and the value of N4 is a positive integer. The method according to claim 46, wherein the length of the Value field is determined based on the second part in the ControlByte field, The second part in the ControlByte field is used to indicate the length of the Value field of the basic data type; or, the second part in the ControlByte field is used to indicate the terminator of the container data type. The method according to any one of claims 25 to 47, wherein the Tag field is used to describe the tag of the data, the Length field is used to describe the length of the Value field, and the Value field is used to describe the Value of the data . A data transmission device applied to a first device, the device comprising: A sending unit, configured to send a first signaling to a second device, where the data carried in the first signaling is encoded in a first TLV format; wherein, The first TLV format is used to determine a first TLV structure, and the first TLV structure includes a ControlByte field, a Tag field, and at least one of the following: a Length field, and a Value field. The device according to claim 49, wherein the length of the ControlByte field is N1 bytes, and the value of N1 is a positive integer. The device according to claim 50, wherein the value of N1 is 1. The apparatus according to claim 51, wherein the first part of bits in the ControlByte field is used to indicate that the use of the data is one of the following: general use for device access, general use for device control, and general use for device control. The device according to claim 52, wherein the first part of bits in the ControlByte field is also used to indicate the description of Tag. The device according to claim 53, wherein the description of the Tag is used to determine at least one of the following: The length of the Tag field; The tag type described in the Tag field is an attribute identification tag iid tag or an index tag index tag or a device identification tag DeviceID tag or a transaction identification tag ID tag or a service identification tag siid tag. The apparatus according to any one of claims 52 to 54, wherein the first part of bits in the ControlByte field is the upper 3 bits in the ControlByte field. The device according to any one of claims 51 to 55, wherein the second part of bits in the ControlByte field is used to indicate the data type of the Value described by the Value field. The device according to claim 56, wherein the second part of bits in the ControlByte field is also used to indicate at least one of the following: the length of the Length field, the length of the Value field. The device according to claim 56, wherein the second part of bits in the ControlByte field is also used to indicate: a terminator of the container data type. The apparatus according to any one of claims 56 to 58, wherein the second part of bits in the ControlByte field is the lower 5 bits in the ControlByte field. The device according to any one of claims 49 to 59, wherein the length of the Tag field is N2 bytes, and N2 is a positive integer. The device according to claim 60, wherein the value of N2 is greater than or equal to 0 and less than or equal to 8. The device according to claim 60 or 61, wherein the Tag field occupies the first byte, and if the value of the highest bit in the first byte is the first value, it means that the Tag field only occupies The first byte, and the value of the Tag field is determined by the lower 7 bits in the first byte; wherein, the highest bit in the first byte is a Tag length identification bit. The device according to claim 60 or 61, wherein the Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field is also Occupies the second byte and the third byte after the first byte, and the value of the Tag field passes all the bits in the second byte and all the bits in the third byte bit determination; wherein, the highest bit in the first byte is the Tag length identification bit. The device according to claim 60 or 61, wherein the Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field is also Occupies the second byte after the first byte, and the value of the Tag field is determined by the lower 7 bits in the first byte and all bits in the second byte; wherein, The highest bit in the first byte is the Tag length identification bit. The device according to claim 60 or 61, wherein the Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field is also Occupies the second byte after the first byte, if the value of the highest bit of the second byte is the second value, it means that the Tag field also occupies the third byte after the second byte byte, and so on, until the value of the highest bit in the Mth byte occupied by the Tag field is the first value, and the Mth byte is taken as the last byte occupied by the Tag field, and M is A positive integer; the value of the Tag field is determined by the lower 7 bits of each byte in the first byte to the Mth byte. The device according to claim 60 or 61, wherein the length of the Tag field is determined based on the first part in the ControlByte field, the first part in the ControlByte field is used to indicate the description of the Tag, and the description of the Tag It is used to determine at least one of the following: the length of the Tag field, and the tag type described by the Tag field is an attribute identification tag iid tag or an index tag index tag or a device identification tag DeviceID tag or a transaction identification tag ID tag or a service identification tag siid tag. The device according to any one of claims 49 to 66, wherein the length of the Length field is N3 bytes, and N3 is a positive integer. The device according to claim 67, wherein the value of N3 is greater than or equal to 0 and less than or equal to 8. The apparatus according to claim 67 or 68, wherein the length of the Length field is determined based on a second part in the ControlByte field, and the second part in the ControlByte field is used to indicate the length of the Length field. The device according to any one of claims 49 to 69, wherein the length of the Value field is N4 bytes, and the value of N4 is a positive integer. The apparatus according to claim 70, wherein the length of the Value field is determined based on the second part in the ControlByte field, The second part in the ControlByte field is used to indicate the length of the Value field of the basic data type; or, the second part in the ControlByte field is used to indicate the terminator of the container data type. The device according to any one of claims 49 to 71, wherein the Tag field is used to describe the tag of the data, the Length field is used to describe the length of the Value field, and the Value field is used to describe the Value of the data . A data transmission device applied to a second device, the device comprising: The receiving unit is configured to receive the first signaling sent by the first device, where the data carried in the first signaling is encoded in the first TLV format; wherein, The first TLV format is used to determine a first TLV structure, and the first TLV structure includes a ControlByte field, a Tag field, and at least one of the following: a Length field, and a Value field. The device according to claim 73, wherein the length of the ControlByte field is N1 bytes, and the value of N1 is a positive integer. The apparatus according to claim 74, wherein the value of N1 is 1. The device according to claim 75, wherein the first part of bits in the ControlByte field is used to indicate that the use of the data is one of the following: general for device access, general for device control, general for device control. The device according to claim 76, wherein the first part of bits in the ControlByte field is also used to indicate the description of Tag. The apparatus according to claim 77, wherein the description of the Tag is used to determine at least one of the following: The length of the Tag field; The tag type described in the Tag field is an attribute identification tag iid tag or an index tag index tag or a device identification tag DeviceID tag or a transaction identification tag ID tag or a service identification tag siid tag. The apparatus according to any one of claims 76 to 78, wherein the first part of bits in the ControlByte field is the upper 3 bits in the ControlByte field. The device according to any one of claims 75 to 79, wherein the second part of bits in the ControlByte field is used to indicate the data type of the Value described by the Value field. The device according to claim 80, wherein the second part of bits in the ControlByte field is further used to indicate at least one of the following: the length of the Length field, and the length of the Value field. The apparatus according to claim 80, wherein the second part of bits in the ControlByte field is also used to indicate: a terminator of the container data type. The apparatus according to any one of claims 80 to 82, wherein the second part of bits in the ControlByte field is the lower 5 bits in the ControlByte field. The device according to any one of claims 73 to 83, wherein the length of the Tag field is N2 bytes, and N2 is a positive integer. The device according to claim 84, wherein the value of N2 is greater than or equal to 0 and less than or equal to 8. The device according to claim 84 or 85, wherein the Tag field occupies the first byte, and if the value of the highest bit in the first byte is the first value, it means that the Tag field only occupies The first byte, and the value of the Tag field is determined by the lower 7 bits in the first byte; wherein, the highest bit in the first byte is a Tag length identification bit. The device according to claim 84 or 85, wherein the Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field is also Occupies the second byte and the third byte after the first byte, and the value of the Tag field passes through all the bits in the second byte and all the bits in the third byte bit determination; wherein, the highest bit in the first byte is the Tag length identification bit. The device according to claim 84 or 85, wherein the Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field is also Occupies the second byte after the first byte, and the value of the Tag field is determined by the lower 7 bits in the first byte and all bits in the second byte; wherein, The highest bit in the first byte is the Tag length identification bit. The device according to claim 84 or 85, wherein the Tag field occupies at least the first byte, and if the value of the highest bit in the first byte is the second value, it means that the Tag field is also Occupies the second byte after the first byte, if the value of the highest bit of the second byte is the second value, it means that the Tag field also occupies the third byte after the second byte byte, and so on, until the value of the highest bit in the Mth byte occupied by the Tag field is the first value, and the Mth byte is taken as the last byte occupied by the Tag field, and M is A positive integer; the value of the Tag field is determined by the lower 7 bits of each byte in the first byte to the Mth byte. The device according to claim 84 or 85, wherein the length of the Tag field is determined based on the first part in the ControlByte field, the first part in the ControlByte field is used to indicate the description of the Tag, and the description of the Tag It is used to determine at least one of the following: the length of the Tag field, and the tag type described by the Tag field is an attribute identification tag iid tag or an index tag index tag or a device identification tag DeviceID tag or a transaction identification tag ID tag or a service identification tag siid tag. The device according to any one of claims 73 to 90, wherein the length of the Length field is N3 bytes, and N3 is a positive integer. The device according to claim 91, wherein the value of N3 is greater than or equal to 0 and less than or equal to 8. The apparatus according to claim 91 or 92, wherein the length of the Length field is determined based on a second part in the ControlByte field, and the second part in the ControlByte field is used to indicate the length of the Length field. The device according to any one of claims 73 to 93, wherein the length of the Value field is N4 bytes, and the value of N4 is a positive integer. The apparatus of claim 94, wherein the length of the Value field is determined based on the second part in the ControlByte field, The second part in the ControlByte field is used to indicate the length of the Value field of the basic data type; or, the second part in the ControlByte field is used to indicate the terminator of the container data type. The device according to any one of claims 73 to 95, wherein the Tag field is used to describe the tag of the data, the Length field is used to describe the length of the Value field, and the Value field is used to describe the Value of the data . A communication device, comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to invoke and run the computer program stored in the memory, and execute the computer program described in any one of claims 1 to 24 , or a method as claimed in any one of claims 25 to 48. A chip, comprising: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 1 to 24, or claims 25 to 48 any one of the methods described. A computer-readable storage medium for storing a computer program, the computer program causing a computer to execute the method according to any one of claims 1 to 24, or the method according to any one of claims 25 to 48 . A computer program product comprising computer program instructions for causing a computer to execute the method according to any one of claims 1 to 24, or the method according to any one of claims 25 to 48. A computer program that causes a computer to execute the method according to any one of claims 1 to 24, or the method according to any one of claims 25 to 48.