WO2022116009A1

WO2022116009A1 - Data transmission method and apparatus, and communication device

Info

Publication number: WO2022116009A1
Application number: PCT/CN2020/133158
Authority: WO
Inventors: 吕小强; 罗朝明
Original assignee: Oppo广东移动通信有限公司
Priority date: 2020-12-01
Filing date: 2020-12-01
Publication date: 2022-06-09
Also published as: CN116615874A

Abstract

Embodiments of the present application provide a data transmission method and apparatus, and a communication device. The method comprises: a first device sends first signaling to a second device, data carried in the first signaling being encoded in a first TLV format; wherein the first TLV format is used for determining a first TLV structure, and the first TLV structure comprises a control byte field, a tag field, and at least one of 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 apparatus, and a communication device.

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, among which, 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-mentioned TLV format is used for encoding and decoding, the efficiency of encoding and decoding is low due to the lack of some control information.

SUMMARY OF THE INVENTION

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

The data transmission method provided by the embodiment of the present application includes:

The first device sends the first signaling to the second device, and 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, where 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 second device receives the first signaling sent by the first device, and 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, where 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 by 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 the second device, where the data carried in the first signaling is encoded in a first TLV format; wherein,

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

a receiving unit, 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 communication device provided by the embodiments of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above-mentioned data transmission method.

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

Specifically, the chip includes: a processor for invoking and running a computer program from the memory, so that the device on which the chip is installed executes the above-mentioned data transmission method.

The computer-readable storage medium provided by the embodiment of the present application is used to store a computer program, and the computer program enables a 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-mentioned data transmission method.

The computer program provided by the embodiment of the present application, when it runs on the computer, causes the computer to execute the above-mentioned data transmission method.

Through the above technical solution, a new type of TLV format (ie the first TLV format) is proposed, and the TLV structure (ie the first TLV structure) determined by the new type of TLV format 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, some control information related to other fields can be described through the ControlByte field, the efficiency of encoding and decoding is improved, and a TLV structure conforming to the application is realized.

Description of drawings

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

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

2 is a schematic flowchart of a data transmission method provided by an embodiment of the present application;

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

4 is a schematic diagram 1 of the structure and composition of a data transmission device provided by an embodiment of the present application;

FIG. 5 is a second schematic diagram of the structure and composition of a data transmission device provided by an 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 accompanying drawings and in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features of the embodiments may be combined with each other in the case of no conflict. Obviously, the described embodiments are some, but not all, embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

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

In order to facilitate the 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 the device that provides resources, and the client refers to the device that accesses resources.

OCF adopts the Representational State Transfer (RESTful) architecture, and uses resources to represent IoT physical devices, as well as the functional services provided by the devices and the status of the devices. 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. The RESTful operations can be 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), and 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, and requests to operate the resources on the server. The server performs the resource operation and returns a response to the client. , the content and description information of the resource are carried in the response.

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

The transmission protocol of OCF adopts Constrained Application Protocol (CoAP) to carry resource operations. Each CRUDN operation is mapped to a CoAP request message or response message. The method operates on the resources of the server, thereby realizing the transition of the resource state.

TLV

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 triplet, 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. 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 (ie, the attribute value of the tag described by the Tag field).

The technical solutions of the embodiments of the present application propose 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 the 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 (that is, the data carried in the signaling) in the mutual signaling.

FIG. 2 is a schematic flowchart of a data transmission method provided by an 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, the second device receives the first signaling sent by the first device, and 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, where 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 request message for modifying a service (Server) state. The data carried in the first signaling is encoded in 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 in the embodiment of the present application, thereby obtaining data carried in the first signaling, and performs corresponding operations, such as attributes, according to the data 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 in the first TLV format provided by the embodiment of the present application. After receiving the response message, the client terminal 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 a first TLV structure, where 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 present application, the Tag field is used to describe the tag of the data.

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

In this 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 tag).

In one example, the content of the Tag field is 0X12, which means that the tag is temperature. The content of the Value field is 15, which represents the value of the temperature of 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. 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 the bits in the ControlByte field are the upper 3 bits in the ControlByte field. For example: Bit7-bit5 are 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 is the second part of bits.

In the embodiment of the present application, the first part of the bit in the ControlByte field is used to indicate that the purpose of the data is one of the following: general for device access, general for device control, and 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, 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) Either the transaction identification tag (ID tag) or the 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 in 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. Alternatively, 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 Tables 1-1 and 1-2 show the contents indicated by the different values of the first part of the bits (ie Bit7-bit5) in the ControlByte field, and the second part of the bits (ie Bit4) -bit0) indicates the content in the case of different values.

Table 1-1

Table 1-2

The following is an example to illustrate 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 with reference to Table 1-1 and Table 1-2 above.

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 the bits (ie Bit4-bit0) in the ControlByte field is 00100, the second part of the bits is used to indicate that the data type of the 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 the bits (ie, Bit4-bit0) in the ControlByte field is 01000, the second part of the bits is used to indicate that the data type of Value is a boolean (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 there is 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 the bits (ie Bit4-bit0) in the ControlByte field is 01010, the second part of the bits is used to indicate that the data type of Value is a floating point (float) type, and no The 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 4 bytes.

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

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

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

In an example, when the value of the second part of the bits (ie Bit4-bit0) in the ControlByte field is 11010, the second part of the bits are used to indicate that the data type of 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 the bits (ie Bit4-bit0) in the ControlByte field is 11011, the second part of the bit 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 the bit (ie Bit4-bit0) in the ControlByte field is 11100, the second part of the bit 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 the bits (ie, Bit7-bit5) in the ControlByte field is 001, the second part of the bits is used to indicate that the purpose of the data is universal for device access.

In an example, when the value of the first part of the bits (ie Bit7-bit5) in the ControlByte field is 010, the second part of the 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 the attribute, or event, or method within the service.

In an example, when the value of the first part of the bits (ie Bit7-bit5) in the ControlByte field is 100, the second part of the 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 the child element in the struct data type or array data type, the tag value (ie the value of the Tag field) is the index value, and the value value (ie the value of the Value field) is the child of the index mark. the value of the element.

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

In an example, for the general purpose of device control, referring to Table 1-2, four situations are further subdivided, and the purpose of each situation can be called device control. For the first case, the tag value (that is, the value of the Tag field) is 0x1, which represents the DeviceID tag, and the value value (that is, the value of the Value field) is the deviceID value, where deviceID is an ID that identifies 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 group 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 the 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 (ie bit7) of the byte is the Tag length identification bit, and the lower 7 bits of the byte (ie 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, where 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 this embodiment of the present application, the length and value of the Tag field may be determined through the following scheme.

Scheme 1) 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 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 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, the value of the Tag field is determined).

Scheme 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 (ie, the first byte) is 1, it means that the two bytes immediately following the byte also belong to the Tag field, and the following two words 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 is not used.

Scheme 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 the bits in the second byte; wherein, the highest bit in the first byte It 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 of a byte (ie, the first byte) is 1, it means that the use of a byte immediately following the byte also belongs to the Tag field, and the use of the first byte of bit6-bit0 and bit7-bit0 of the next byte to identify the tag value (that is, to determine the value of the Tag field).

Scheme 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, 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 Determined by the lower 7 bits of each 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 (that is, the first byte) is 1, it means that a byte (that is, the second byte) immediately following the byte also belongs to the Tag field; if the second word If the Tag length identification bit of the section is also 1, it means that the byte immediately following the byte (ie, the third byte) also belongs to the Tag field, and so on, until the Tag length identification bit of the Mth byte is 0 , 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, the following Table 3 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 followed by a byte (ie, 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, to determine the value of the Tag field) is: 00000010000001 (binary)=129 (decimal). The first half of the binary data, 0000001, corresponds to bit6-bit0 of the first byte, and the second half, 0000001, corresponds to bit6-bit0 of the second byte. The two parts are combined to identify a tag value of "129". It should be noted that if there are three bytes or more bytes, it can be deduced by analogy.

table 3

Scheme 5) The length of the Tag field is determined based on the first part in the ControlByte field, and 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: the Tag field The length of the tag field, the tag type described by the Tag field is iid tag or index tag or DeviceID tag or transaction ID tag or siid tag.

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

(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 present 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) is of variable length, so the length can be determined in a variable-length manner. In an optional manner, the terminator of a struct or an array may be used to identify the end position of a struct or a struct, so that the length of the Length field is determined according to the end position.

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

(4) Value field

In this 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 solutions of the embodiments of the present application provide a novel TLV structure (that is, the first TLV structure). In an example, the following Table 4 provides the overall structure of the first TLV structure, where the length of the ControlByte field is It is 1 byte (byte), the length of the Tag field is 0 to 8 bytes, the length of the Length field is 0 to 8 bytes, and the length of the Value field is variable according to the content.

ControlByteControlByte	TagTag	LengthLength	ValueValue
1byte1byte	0-8bytes0-8bytes	0-8bytes0-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 (that is, the data carried in the signaling) in the mutual signaling, thereby improving the encoding and decoding efficiency.

FIG. 4 is a schematic structural diagram 1 of a data transmission apparatus provided by an embodiment of the present application, which is applied to a first device. As shown in FIG. 4 , the data transmission apparatus includes:

The sending unit 401 is 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, where the first TLV structure includes a control byte ControlByte field, a tag 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 the bit in the ControlByte field is used to indicate that the purpose of the data is one of the following: general for device access, general for device control, and 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 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 first part of the bits in the ControlByte field are 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 in the Value field.

In an optional manner, 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.

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 word. The second byte and the third byte after the section, and the value of the Tag field is determined by all bits in the second byte and all bits in the third byte; wherein, all 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 word. 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 the bits in the second byte; wherein, the first byte The highest bit 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 word. The second byte after the section, 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 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 value of the field is determined by the lower 7 bits of each 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, and 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, 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 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.

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 of the ControlByte field is used to indicate the length of the Value field of the basic data type; or, the second part of 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 above-mentioned 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 second schematic structural diagram of a data transmission apparatus provided by an embodiment of the present application, which is applied to a second device. As shown in FIG. 5 , the data transmission apparatus includes:

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

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

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;

FIG. 6 is a schematic structural diagram of a communication device 600 provided by 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 processing The processor 610, the processor 610 may call and run a computer program from the memory to implement the method in the embodiments of the present application.

Optionally, as shown in FIG. 6 , the communication device 600 may further include a memory 620 . The processor 610 may call and run a computer program from the memory 620 to implement the methods in the embodiments of the present application.

The memory 620 may be a separate 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, may send information or data to other devices, or receive other devices Information or data sent by a device.

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

Optionally, the communication device 600 may specifically be the network device in this embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method in 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 embodiments 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 embodiments of the present application, for the sake of brevity. , and 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 this embodiment of the present application.

Optionally, as shown in FIG. 7 , the chip 700 may further include a memory 720 . The processor 710 may call and run a computer program from the memory 720 to implement the methods in the embodiments of the present application.

The memory 720 may be a separate device independent of the processor 710 , or may be integrated in the processor 710 .

Optionally, the chip 700 may further include an input interface 730 . The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may acquire information or data sent by other devices or chips.

Optionally, the chip 700 may further include an output interface 740 . The processor 710 can control the output interface 740 to communicate with other devices or chips, and 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 each method of the embodiment of the present application, which is not repeated here for brevity.

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 each method of the embodiments of the present application. For brevity, here No longer.

It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.

It should be understood that the processor in this 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 method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software. The above-mentioned processor can 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 Programming logic devices, discrete gate or transistor logic devices, discrete hardware components. The methods, steps, and logic block diagrams disclosed in the embodiments of this application can 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 conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. 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 this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. 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 electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. Volatile memory may 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, 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 link 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 memory is an example but not a limitative description, 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) and so on. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

Embodiments of the present application further provide a computer-readable storage medium for storing a computer program.

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 each method 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 each method of the embodiments of the present application. , and are not repeated here for brevity.

Embodiments of the present application also provide a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. 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 each method of the embodiments of the present application, For brevity, details are not repeated here.

The embodiments of the present application also provide a computer program.

Optionally, the computer program can be applied to the network device in the embodiments of the present application, and when the computer program runs on the computer, the computer executes the corresponding processes implemented by the network device in the various methods of the embodiments of the present application, for the sake of brevity. , and will not be repeated here.

Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiments of the present application, and when the computer program is run on the computer, the mobile terminal/terminal device implements the various methods of the computer program in the embodiments of the present application. The corresponding process, for the sake of brevity, will not be repeated here.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example 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 performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus 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 may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may 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 achieve the purpose of the solution in this embodiment.

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

The functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution, and the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to 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 media that can store program codes .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. should be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

A data transmission method, the method comprising:

The first device sends the first signaling to the second device, and 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, where the first TLV structure includes a control byte ControlByte field, a tag 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 the 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, and general 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 the Tag.
The method of 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 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 4 to 6, wherein the first part of the bits in the ControlByte field are 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 further used to indicate: the terminator of the container data type.
The method according to any one of claims 8 to 10, wherein the second part of the bits in the ControlByte field are 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 a first byte, and if the value of the highest bit in the first byte is a 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.
The method according to claim 12 or 13, wherein the Tag field occupies at least a first byte, and if the value of the highest bit in the first byte is a second value, it means that the Tag field also Occupies the second byte and the third byte after the first byte, and the value of the Tag field passes through all bits in the second byte and all bits in the third byte The bit is determined; 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 a first byte, and if the value of the highest bit in the first byte is a second value, it means that the Tag field 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 the 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 a first byte, and if the value of the highest bit in the first byte is a second value, it means that the Tag field 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, 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 from 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, and the first part in the ControlByte field is used to indicate the description of the Tag, 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 of claim 19 or 20, wherein the length of the Length field is determined based on a second part of the ControlByte field, the second part of the ControlByte field being 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 of claim 22, wherein the length of the Value field is determined based on the second portion of the ControlByte field,

The second part of the ControlByte field is used to indicate the length of the Value field of the basic data type; or, the second part of 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, and 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, where the first TLV structure includes a control byte ControlByte field, a tag 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 the 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, and general 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 the Tag.
The method of 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 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 28 to 30, wherein the first part of the bits in the ControlByte field are 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 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 32, wherein the second part of bits in the ControlByte field is further used to indicate: the terminator of the container data type.
The method according to any one of claims 32 to 34, wherein the second part of the bits in the ControlByte field are 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 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 a first byte, and if the value of the highest bit in the first byte is a 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.
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 also Occupies the second byte and the third byte after the first byte, and the value of the Tag field passes through all bits in the second byte and all bits in the third byte The bit is determined; 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 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 the 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 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, 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 from 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, and the first part in the ControlByte field is used to indicate the description of the Tag, 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 of claim 43 or 44, wherein the length of the Length field is determined based on a second part of the ControlByte field, the second part of the ControlByte field being 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 of claim 46, wherein the length of the Value field is determined based on the second portion of the ControlByte field,

The second part of the ControlByte field is used to indicate the length of the Value field of the basic data type; or, the second part of 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 apparatus, applied to a first device, the apparatus comprising:

a sending unit, configured to send a 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, where the first TLV structure includes a control byte ControlByte field, a tag Tag field, and at least one of the following: a Length field and a Value field.
The apparatus according to claim 49, wherein the length of the ControlByte field is N1 bytes, and the value of N1 is a positive integer.
The apparatus according to claim 50, wherein the value of N1 is 1.
The apparatus according to claim 51, wherein the first part of the 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, and general for device control.
The apparatus according to claim 52, wherein the first part of the bits in the ControlByte field is further used to indicate the description of the Tag.
The apparatus of 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 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 apparatus according to any one of claims 52 to 54, wherein the first part of the bits in the ControlByte field are the upper 3 bits in the ControlByte field.
The apparatus 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 apparatus according to claim 56, 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 56, wherein the second part of bits in the ControlByte field is further used to indicate: the terminator of the container data type.
The apparatus according to any one of claims 56 to 58, wherein the second part of the bits in the ControlByte field are the lower 5 bits in the ControlByte field.
The apparatus 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 apparatus according to claim 60 or 61, wherein the Tag field occupies a first byte, and if the value of the highest bit in the first byte is a 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.
The apparatus according to claim 60 or 61, wherein the Tag field occupies at least a first byte, and if the highest bit in the first byte is a second value, it means that the Tag field still has a second value. Occupies the second byte and the third byte after the first byte, and the value of the Tag field passes through all bits in the second byte and all bits in the third byte The bit is determined; wherein, the highest bit in the first byte is the Tag length identification bit.
The apparatus according to claim 60 or 61, wherein the Tag field occupies at least a first byte, and if the highest bit in the first byte is a second value, it means that the Tag field still has a second value. 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 the bits in the second byte; wherein, The highest bit in the first byte is the Tag length identification bit.
The apparatus according to claim 60 or 61, wherein the Tag field occupies at least a first byte, and if the highest bit in the first byte is a second value, it means that the Tag field still has a second value. 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, 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 from the first byte to the Mth byte.
The apparatus according to claim 60 or 61, wherein the length of the Tag field is determined based on a first part in the ControlByte field, and the first part in the ControlByte field is used to indicate the description of the Tag, 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 apparatus 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 of claim 67 or 68, wherein the length of the Length field is determined based on a second part of the ControlByte field, the second part of the ControlByte field being used to indicate the length of the Length field.
The apparatus 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 of claim 70, wherein the length of the Value field is determined based on the second portion of the ControlByte field,

The second part of the ControlByte field is used to indicate the length of the Value field of the basic data type; or, the second part of the ControlByte field is used to indicate the terminator of the container data type.
The apparatus 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 apparatus, applied to a second device, the apparatus comprising:

a receiving unit, 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, where the first TLV structure includes a control byte ControlByte field, a tag Tag field, and at least one of the following: a Length field and a Value field.
The apparatus 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 of claim 74, wherein the value of N1 is 1.
The apparatus according to claim 75, wherein 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, and general for device control.
The apparatus according to claim 76, wherein the first part of the bits in the ControlByte field is further used to indicate the description of the Tag.
The apparatus of 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 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 apparatus according to any one of claims 76 to 78, wherein the first part of the bits in the ControlByte field are the upper 3 bits in the ControlByte field.
The apparatus 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 apparatus 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 further used to indicate: the terminator of the container data type.
The apparatus according to any one of claims 80 to 82, wherein the second part of the bits in the ControlByte field are the lower 5 bits in the ControlByte field.
The apparatus 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 of claim 84, wherein the value of N2 is greater than or equal to 0 and less than or equal to 8.
The apparatus according to claim 84 or 85, wherein the Tag field occupies a first byte, and if the value of the highest bit in the first byte is a 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.
The device according to claim 84 or 85, wherein the Tag field occupies at least a first byte, and if the highest bit in the first byte is a second value, it means that the Tag field still has a second value. Occupies the second byte and the third byte after the first byte, and the value of the Tag field passes through all bits in the second byte and all bits in the third byte The bit is determined; wherein, the highest bit in the first byte is the Tag length identification bit.
The apparatus according to claim 84 or 85, wherein the Tag field occupies at least a first byte, and if the highest bit in the first byte is a second value, it means that the Tag field still has a second value. 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 the 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 a first byte, and if the highest bit in the first byte is a second value, it means that the Tag field still has a second value. 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, 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 from the first byte to the Mth byte.
The apparatus according to claim 84 or 85, wherein the length of the Tag field is determined based on the first part in the ControlByte field, and the first part in the ControlByte field is used to indicate the description of the Tag, 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 apparatus 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 of claim 91 or 92, wherein the length of the Length field is determined based on a second part of the ControlByte field, the second part of the ControlByte field being used to indicate the length of the Length field.
The apparatus 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 of the ControlByte field is used to indicate the length of the Value field of the basic data type; or, the second part of the ControlByte field is used to indicate the terminator of the container data type.
The apparatus 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 call and run the computer program stored in the memory, and execute the computer program according to any one of claims 1 to 24. , or the method of any one of claims 25 to 48.
A chip, comprising: a processor for invoking and running 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 The method of any of the above.
A computer-readable storage medium for storing a computer program that causes a computer to perform the method of any one of claims 1 to 24, or the method of any one of claims 25 to 48 .
A computer program product comprising computer program instructions that cause a computer to perform the method of any one of claims 1 to 24, or the method of any one of claims 25 to 48.
A computer program that causes a computer to perform the method of any one of claims 1 to 24, or the method of any one of claims 25 to 48.