[go: up one dir, main page]

WO2022116009A1 - Procédé et appareil de transmission de données, et dispositif de communication - Google Patents

Procédé et appareil de transmission de données, et dispositif de communication Download PDF

Info

Publication number
WO2022116009A1
WO2022116009A1 PCT/CN2020/133158 CN2020133158W WO2022116009A1 WO 2022116009 A1 WO2022116009 A1 WO 2022116009A1 CN 2020133158 W CN2020133158 W CN 2020133158W WO 2022116009 A1 WO2022116009 A1 WO 2022116009A1
Authority
WO
WIPO (PCT)
Prior art keywords
field
tag
byte
value
length
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2020/133158
Other languages
English (en)
Chinese (zh)
Inventor
吕小强
罗朝明
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to PCT/CN2020/133158 priority Critical patent/WO2022116009A1/fr
Priority to CN202080105087.2A priority patent/CN116615874B/zh
Publication of WO2022116009A1 publication Critical patent/WO2022116009A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • 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.
  • 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).
  • the efficiency of encoding and decoding is low due to the lack of some control information.
  • Embodiments of the present application provide a data transmission method and apparatus, and a communication device.
  • 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.
  • ControlByte ControlByte
  • Tag Tag
  • Value Value
  • 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;
  • 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 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;
  • 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 communication device includes 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 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.
  • 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.
  • 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.
  • FIG. 1 is an optional communication architecture diagram provided by an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a data transmission method provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of interaction between a client and a server provided by an embodiment of the present application.
  • FIG. 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.
  • the Open Connectivity Foundation defines a client and a server.
  • the server refers to the device that provides resources
  • 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.
  • CRUDN 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
  • 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 Uniform Resource Identifier
  • 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.
  • CoAP Constrained Application Protocol
  • 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 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).
  • BER Basic Encoding Rule
  • a basic data element includes a tlv triplet, namely Tag-Length-Value.
  • 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
  • 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.
  • the first device is a client
  • the second device is a server.
  • the first signaling is a resource operation request message.
  • 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.
  • the server 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.
  • the first device is a server
  • 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.
  • 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.
  • the first TLV structure includes a ControlByte field and a Tag field.
  • the first TLV structure includes a ControlByte field, a Tag field and a Value field.
  • the first TLV structure includes a ControlByte field, a Tag field, a Length field and a Value field.
  • 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.
  • 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.
  • 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.
  • the Value field is used to describe the Value of the data (that is, the attribute value corresponding to the tag).
  • 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.
  • the length of the ControlByte field is N1 bytes, and the value of N1 is a positive integer.
  • the value of N1 is 1, that is, the length of the ControlByte field is 1 byte.
  • 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
  • the second part is used to determine the related control information of the Value field.
  • the first part of the bits in the ControlByte field are the upper 3 bits in the ControlByte field.
  • 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.
  • Bit4-bit0 is the second part of bits.
  • 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.
  • 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).
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • the value of Bit5-bit7 is 000 .
  • the second part of the bit is used to indicate the terminator of the array, and the value of Bit5-bit7 is 000 .
  • unsigned integer type signed integer type
  • Boolean type floating point type
  • byte type 0 .
  • String types are reference types.
  • Structure types and array types are container data types.
  • the second part of the bits is used to indicate that the purpose of the data is universal for device access.
  • 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
  • the length of the Tag field is 1 byte.
  • the tag value (that is, the value of the Tag field) is the iid value
  • the value value (that is, the value of the Value field) is the attribute value corresponding to idd.
  • iid is the unique identifier of the attribute, or event, or method within the service.
  • 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.
  • 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
  • the value value ie the value of the Value field
  • the second part of the bits is used to indicate that the purpose of the data is common for device control.
  • 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.
  • 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.
  • the transaction ID is a group of associated The identifier of the signaling flow.
  • 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.
  • siid is a The ID of the service instance.
  • 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.
  • siid is a The ID of the service instance.
  • the length of the Tag field is N2 bytes, and N2 is a positive integer.
  • 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.
  • 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.
  • 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.
  • the Tag field can occupy one or more bytes.
  • the length and value of the Tag field may be determined through the following scheme.
  • 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.
  • 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).
  • 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.
  • the second value is 1.
  • the value of the Tag length identification bit in a byte ie, the first byte
  • 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.
  • the second value is 1.
  • the value of the Tag length identification bit of a byte ie, the first byte
  • 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.
  • the second value is 1 and the first value is 0.
  • the Tag length identification bit of a byte that is, the first byte
  • Use bit6-bit0 of each byte to identify the tag value (that is, to determine the value of the Tag field).
  • the Tag field occupies the first byte and the second byte.
  • 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
  • the Tag length identification bit of the second byte is 0, representing The second byte is the last byte occupied by the Tag field.
  • the first half of the binary data, 0000001 corresponds to bit6-bit0 of the first byte
  • 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.
  • 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.
  • the length of the Tag field can be determined directly according to the first part (ie, the tagControl part) in the ControlByte field.
  • 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.
  • the length of the Length field is N3 bytes, and N3 is a positive integer.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the length of the Value field is N4 bytes, and the value of N4 is a positive integer.
  • 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).
  • 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.
  • ControlByte Tag Length Value 1byte 0-8bytes 0-8bytes lengthen
  • 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.
  • the length of the ControlByte field is N1 bytes, and the value of N1 is a positive integer.
  • the value of N1 is 1.
  • 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.
  • the first part of bits in the ControlByte field is also used to indicate the description of the Tag.
  • the description of the Tag is used to determine at least one of the following
  • the tag type described by the Tag field is iid tag or index tag or DeviceID tag or transaction ID tag or siid tag.
  • the first part of the bits in the ControlByte field are the upper 3 bits in the ControlByte field.
  • the second part of bits in the ControlByte field is used to indicate the data type of the Value described in the Value field.
  • 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 second part of bits in the ControlByte field is also used to indicate: the terminator of the container data type.
  • the second part of bits in the ControlByte field is the lower 5 bits in the ControlByte field.
  • the length of the Tag field is N2 bytes, and N2 is a positive integer.
  • the value of N2 is greater than or equal to 0 and less than or equal to 8.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the length of the Length field is N3 bytes, and N3 is a positive integer.
  • the value of N3 is greater than or equal to 0 and less than or equal to 8.
  • 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 length of the Value field is N4 bytes, and the value of N4 is a positive integer.
  • 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 Tag field is used to describe the tag of the data
  • the Length field is used to describe the length of the Value field
  • the Value field is used to describe the Value of the data.
  • 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;
  • 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 length of the ControlByte field is N1 bytes, and the value of N1 is a positive integer.
  • the value of N1 is 1.
  • 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.
  • the first part of bits in the ControlByte field is also used to indicate the description of the Tag.
  • the description of the Tag is used to determine at least one of the following:
  • the tag type described by the Tag field is iid tag or index tag or DeviceID tag or transaction ID tag or siid tag.
  • the first part of the bits in the ControlByte field are the upper 3 bits in the ControlByte field.
  • the second part of bits in the ControlByte field is used to indicate the data type of the Value described in the Value field.
  • 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 second part of bits in the ControlByte field is also used to indicate: the terminator of the container data type.
  • the second part of bits in the ControlByte field is the lower 5 bits in the ControlByte field.
  • the length of the Tag field is N2 bytes, and N2 is a positive integer.
  • the value of N2 is greater than or equal to 0 and less than or equal to 8.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the length of the Length field is N3 bytes, and N3 is a positive integer.
  • the value of N3 is greater than or equal to 0 and less than or equal to 8.
  • 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 length of the Value field is N4 bytes, and the value of N4 is a positive integer.
  • 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 Tag field is used to describe the tag of the data
  • the Length field is used to describe the length of the Value field
  • the Value field is used to describe the Value of the data.
  • 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.
  • 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 .
  • 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.
  • 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.
  • 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. .
  • 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.
  • 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 .
  • 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.
  • 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.
  • 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.
  • 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.
  • the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application.
  • the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application.
  • 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.
  • the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • 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.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • 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.
  • 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.
  • 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.
  • RAM Static RAM
  • DRAM Dynamic RAM
  • SDRAM Synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • synchronous link dynamic random access memory Synchlink DRAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • 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.
  • 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.
  • 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 .

Landscapes

  • Communication Control (AREA)

Abstract

Selon des modes de réalisation, la présente invention concerne un procédé et un appareil de transmission de données, et un dispositif de communication. Le procédé comprend les étapes suivantes : un premier dispositif envoie de la première signalisation à un deuxième dispositif, des données transportées dans la première signalisation étant encodées selon un premier format TLV ; le premier format TLV étant utilisé pour déterminer une première structure TLV, et la première structure TLV comprenant un champ d'octet de commande, un champ d'étiquette, et un champ de longueur et/ou un champ de valeur.
PCT/CN2020/133158 2020-12-01 2020-12-01 Procédé et appareil de transmission de données, et dispositif de communication Ceased WO2022116009A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2020/133158 WO2022116009A1 (fr) 2020-12-01 2020-12-01 Procédé et appareil de transmission de données, et dispositif de communication
CN202080105087.2A CN116615874B (zh) 2020-12-01 2020-12-01 一种数据传输方法及装置、通信设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/133158 WO2022116009A1 (fr) 2020-12-01 2020-12-01 Procédé et appareil de transmission de données, et dispositif de communication

Publications (1)

Publication Number Publication Date
WO2022116009A1 true WO2022116009A1 (fr) 2022-06-09

Family

ID=81852864

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/133158 Ceased WO2022116009A1 (fr) 2020-12-01 2020-12-01 Procédé et appareil de transmission de données, et dispositif de communication

Country Status (2)

Country Link
CN (1) CN116615874B (fr)
WO (1) WO2022116009A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117873539A (zh) * 2023-12-28 2024-04-12 四川赛狄信息技术股份公司 基于MicroBlaze的FPGA在线升级方法、系统及介质
CN119212056A (zh) * 2024-11-25 2024-12-27 上海铌锣智能科技有限公司 一种温度检测方法、装置、设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101179580A (zh) * 2007-12-12 2008-05-14 北京北方烽火科技有限公司 一种用于实现WiMAX系统消息编解码的方法
CN102090001A (zh) * 2008-10-30 2011-06-08 华为技术有限公司 基于以太网的光网络终端管理和控制接口
CN102739505A (zh) * 2011-04-06 2012-10-17 中兴通讯股份有限公司 数据中心网络中对虚拟通道的流量控制方法及系统
US20130077626A1 (en) * 2011-09-23 2013-03-28 Avaya Inc. Separation of edge and routing/control information for multicast over shortest path bridging
CN110086763A (zh) * 2013-06-25 2019-08-02 谷歌有限责任公司 结构网络

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102333288B (zh) * 2011-05-31 2014-02-19 华为软件技术有限公司 控制终端应用程序运行的方法和终端
US9338071B2 (en) * 2014-10-08 2016-05-10 Google Inc. Locale profile for a fabric network
CN111447243B (zh) * 2014-11-04 2022-07-15 三星电子株式会社 发送装置和接收装置及其信号处理方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101179580A (zh) * 2007-12-12 2008-05-14 北京北方烽火科技有限公司 一种用于实现WiMAX系统消息编解码的方法
CN102090001A (zh) * 2008-10-30 2011-06-08 华为技术有限公司 基于以太网的光网络终端管理和控制接口
CN102739505A (zh) * 2011-04-06 2012-10-17 中兴通讯股份有限公司 数据中心网络中对虚拟通道的流量控制方法及系统
US20130077626A1 (en) * 2011-09-23 2013-03-28 Avaya Inc. Separation of edge and routing/control information for multicast over shortest path bridging
CN110086763A (zh) * 2013-06-25 2019-08-02 谷歌有限责任公司 结构网络

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117873539A (zh) * 2023-12-28 2024-04-12 四川赛狄信息技术股份公司 基于MicroBlaze的FPGA在线升级方法、系统及介质
CN119212056A (zh) * 2024-11-25 2024-12-27 上海铌锣智能科技有限公司 一种温度检测方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN116615874B (zh) 2024-08-23
CN116615874A (zh) 2023-08-18

Similar Documents

Publication Publication Date Title
CN111352889B (zh) 一种基于mctp协议的设备管理方法、设备、装置和介质
CN110740481B (zh) 基于服务质量的数据处理方法、设备和计算机存储介质
WO2021057326A1 (fr) Procédé de codage de données, procédé de décodage de données, procédé de codage et de décodage de données, dispositif et support de stockage
WO2022042235A1 (fr) Procédé et appareil d'émission de paquets de données, procédé et appareil de traitement de paquets de données, dispositif, et paquet de données
CN116204487A (zh) 远程数据访问方法及装置
WO2022116009A1 (fr) Procédé et appareil de transmission de données, et dispositif de communication
WO2019174191A1 (fr) Procédé et appareil d'initialisation de données de rapport, dispositif informatique et support d'informations
US20220365895A1 (en) Pcie-based data transmission method and apparatus
WO2024207483A1 (fr) Procédé de communication, dispositif électronique et support de stockage
TWI645698B (zh) 資料發送裝置、資料接收裝置及其方法
CN106790201B (zh) 一种传输数据的方法和装置
WO2024197874A1 (fr) Procédé de configuration de mesure de détection, dispositif électronique et support de stockage
WO2020221033A1 (fr) Procédé de gestion de dispositif de stockage à distance au moyen d'un dispositif de gestion
WO2024160146A1 (fr) Procédé de négociation de capacité de dispositif et dispositif associé
WO2019144619A1 (fr) Procédé et système de communication rpc, et dispositif
WO2018202151A1 (fr) Procédé et dispositif de communication
WO2023050045A1 (fr) Procédé, appareil, et système de transmission de données
WO2024187385A1 (fr) Procédé de communication, dispositif électronique et support de stockage
CN115968543B (zh) 资源映射方法、装置、设备及存储介质
CN117730623A (zh) 通信方法及电子设备、存储介质
CN113630300B (zh) 用于报文传输的方法和节点
CN110727391A (zh) 交易数据存储方法及装置、区块链系统、介质和电子设备
CN115348277A (zh) 一种多层消息机制分布式集群通信管理方法及系统
CN115473944A (zh) 一种数据传输方法、装置、存储介质及电子装置
CN112565088B (zh) 消息处理方法、系统、装置和网络设备

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202080105087.2

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20963857

Country of ref document: EP

Kind code of ref document: A1