WO2022042235A1 - 数据报文发送方法、处理方法、装置、设备及数据报文 - Google Patents

数据报文发送方法、处理方法、装置、设备及数据报文 Download PDF

Info

Publication number
WO2022042235A1
WO2022042235A1 PCT/CN2021/110451 CN2021110451W WO2022042235A1 WO 2022042235 A1 WO2022042235 A1 WO 2022042235A1 CN 2021110451 W CN2021110451 W CN 2021110451W WO 2022042235 A1 WO2022042235 A1 WO 2022042235A1
Authority
WO
WIPO (PCT)
Prior art keywords
field
data packet
data
flag bit
data message
Prior art date
Application number
PCT/CN2021/110451
Other languages
English (en)
French (fr)
Inventor
曾春亮
翟召轩
成云峰
陈钊
黄翔文
范作
杨启昌
余志刚
吴泰月
冯涛
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Publication of WO2022042235A1 publication Critical patent/WO2022042235A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • 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 communication technologies, and in particular, to a data message sending method, processing method, apparatus, device, and data message.
  • Communication protocol refers to the rules and conventions that must be followed by both entities to complete communication or services.
  • HTTP HyperText Transfer Protocol
  • Hypertext Transfer Protocol is a transport protocol for transferring hypertext from a WWW server to a local browser, which is generally used for transmission on some data channels that support IP (Internet Protocol, Internet Protocol).
  • IP Internet Protocol, Internet Protocol
  • BLE Bluetooth Low Energy, Bluetooth Low Energy
  • Embodiments of the present application provide a data message sending method, processing method, apparatus, device, and data message.
  • the technical solution is as follows:
  • an embodiment of the present application provides a method for sending a data message, the method comprising:
  • n is a positive integer
  • m is a positive integer less than or equal to the n
  • the data message including the m fields; wherein the data message further includes n flag bits, and the i-th flag bit in the n flag bits is used to indicate the data message Whether the text contains the field corresponding to the i-th flag bit in the n fields;
  • an embodiment of the present application provides a data packet processing method, the method includes:
  • the i-th flag bit in the n flag bits is used to indicate whether the data message contains the predefined n fields.
  • the field corresponding to the i-th flag bit, the n is a positive integer;
  • parse m fields included in the data packet Based on the n flag bits, parse m fields included in the data packet, where m is a positive integer less than or equal to the n.
  • an embodiment of the present application provides an apparatus for sending a data message, and the apparatus includes:
  • a field determination module configured to determine m fields included in the data message from predefined n fields, where n is a positive integer, and m is a positive integer less than or equal to the n;
  • a message generation module configured to generate the data message including the m fields; wherein, the data message further includes n flag bits, and the i-th flag bit in the n flag bits, for indicating whether the data message includes a field corresponding to the i-th flag bit in the n fields;
  • a message sending module configured to send the data message.
  • an embodiment of the present application provides a data packet processing apparatus, the apparatus includes:
  • a message receiving module for receiving data messages
  • the flag bit reading module is used to read the n flag bits included in the data message; wherein, the ith flag bit in the n flag bits is used to indicate whether the data message contains A field corresponding to the i-th flag bit in the predefined n fields, where n is a positive integer;
  • a field parsing module configured to parse m fields included in the data packet based on the n flag bits, where m is a positive integer less than or equal to the n.
  • an embodiment of the present application provides a data packet sending device, the device including a processor, a memory, and a transceiver;
  • the processor is configured to determine m fields included in the data packet from predefined n fields, where n is a positive integer, and m is a positive integer less than or equal to the n;
  • the processor is further configured to generate the data message including the m fields; wherein, the data message further includes n flag bits, and the i-th flag bit in the n flag bits , used to indicate whether the data message contains a field corresponding to the i-th flag bit in the n fields;
  • the transceiver is further configured to send the data message.
  • an embodiment of the present application provides a data packet processing device, the device includes a processor, a memory, and a transceiver;
  • the transceiver for receiving data packets
  • the processor is configured to read the n flag bits included in the data message; wherein, the i-th flag bit in the n flag bits is used to indicate whether the data message contains a pre- A field corresponding to the i-th flag bit in the defined n fields, where n is a positive integer;
  • the processor is further configured to parse m fields included in the data packet based on the n flag bits, where m is a positive integer less than or equal to the n.
  • an embodiment of the present application provides a data packet for transmission between devices, where the data packet is used to load information during data transmission between devices, and the data packet includes a predefined n number of m fields in the field, the n is a positive integer, and the m is a positive integer less than or equal to the n;
  • the data message further includes n flag bits, and the i-th flag bit in the n flag bits is used to indicate whether the data message contains the n fields and the i-th flag.
  • an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and the computer program is loaded and executed by a processor to implement the datagram described in the above aspect A method for sending a message, or implementing the method for processing a data message as described in the above aspects.
  • an embodiment of the present application provides a computer program product, where the computer program product includes computer instructions, and the computer instructions are stored in a computer-readable storage medium.
  • the processor of the computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the data packet sending method described in the above aspect, or implements the data packet described in the above aspect. text processing method.
  • FIG. 1 is a schematic diagram of an implementation environment provided by an embodiment of the present application.
  • FIG. 2 is a flowchart of a data message sending method provided by an embodiment of the present application.
  • 3 to 5 are schematic diagrams of formats of data packets provided by embodiments of the present application.
  • FIG. 6 is a flowchart of a data packet processing method provided by an embodiment of the present application.
  • FIG. 11 is a block diagram of a data message sending apparatus provided by an embodiment of the present application.
  • FIG. 12 is a block diagram of a data packet processing apparatus provided by an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a data message sending device provided by an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a data packet processing device provided by an embodiment of the present application.
  • FIG. 1 shows a schematic diagram of an implementation environment provided by an embodiment of the present application.
  • the implementation environment may include: a first device 10 , a second device 20 , and a third device 30 .
  • the first device 10 refers to a data packet sending device
  • the data packet sending device refers to a device that sends a data packet.
  • the first device 10 may be a terminal or a server, for example, the terminal may be a smart phone, a tablet computer, a PC (Personal Computer, personal computer), an intelligent multimedia device, an intelligent wearable device, etc.;
  • the server may be a server , or a server cluster composed of multiple servers, a cloud server, or an IoT (Internet of Things, Internet of Things) server.
  • the data message may be sent by an APP (Application, application program).
  • the second device 20 is a relay device, that is, the second device 20 is a device used to forward the data packet sent by the first device 10 to the third device 30 .
  • the second device 20 may be a bridge, a router, a gateway, or the like.
  • the third device 30 may be a terminal, for example, the terminal may be a smart phone, a tablet computer, a PC (Personal Computer), an intelligent multimedia device, a smart wearable device, a smart home device, an intelligent transportation device, and the like.
  • the number of the third device 30 may be one or multiple, which is not limited in this embodiment of the present application.
  • both the second device 20 and the third device 30 may be referred to as data packet processing devices, and the data packet processing device refers to a device that processes data packets.
  • the first device 10 and the third device 30 may not be able to communicate directly, and the second device 20 needs to be relayed.
  • the first device 10 sends the data packet to the second device 20, so that the second device 20 forwards the data packet to the third device 30;
  • the communication is performed directly without relaying through the second device 20 , that is, point-to-point communication can be implemented between the first device 10 and the third device 30 .
  • the first device 10 sends the data packet to the third device 30 .
  • the data packets in the embodiments of the present application may also be referred to as messages, domain network layer messages, and other names.
  • the first device 10 may simultaneously send multiple messages to the second device 20 or the third device 30, and the multiple messages form a total datagram.
  • FIG. 2 shows a flowchart of a method for sending a data packet provided by an embodiment of the present application.
  • the method may be performed by a first device, for example, the first device may be the first device 10 in the implementation environment shown in FIG. 1 .
  • the method may include the following steps (201-203).
  • Step 201 From the predefined n fields, determine m fields included in the data packet, where n is a positive integer, and m is a positive integer less than or equal to n.
  • the technicians have pre-defined n fields that can be included in the data packet.
  • the above n fields do not necessarily need to be all given in the data packet, but the necessary fields can be selected according to the transmission scenario in the data packet. given in the text.
  • the predefined n fields include: field 1, field 2, field 3 and field 4, and the fields related to transmission scenario 1 are field 2 and field 3, then the data packet includes 2 fields: Field 2 and Field 3.
  • the data packet includes 4 fields: field 1, field 2, field 3 and field 4.
  • the data packet may not include all of the predefined n fields, that is, the number of m is 0.
  • the data packet may also include at least one other field, and the other field may not be determined from the predefined n fields Yes, this application does not limit it.
  • Step 202 Generate a data packet including m fields.
  • the data message also includes n flag bits, and the i-th flag bit in the n flag bits is used to indicate whether the data message contains a field corresponding to the i-th flag bit among the n fields, i is a positive integer less than or equal to n.
  • the n flag bits correspond to the n fields one-to-one, and different fields correspond to different flag bits. Still taking the above example as an example, field 1 corresponds to flag bit 1, field 2 corresponds to flag bit 2, field 3 corresponds to flag bit 3, and field 4 corresponds to flag bit 4. Assuming that the data packet includes field 2 and field 3, the first device A data message including the above field 2 and field 3 can be generated, and the data message includes flag bit 1, flag bit 2, flag bit 3 and flag bit 4, and flag bit 1 is used to indicate that the data message does not contain field 1, Flag bit 2 is used to indicate that field 2 is included in the data message, flag bit 3 is used to indicate that field 3 is included in the data message, and flag bit 4 is used to indicate that field 4 is not included in the data message.
  • the field content of field 2 and the field content of field 3 may be in binary format.
  • the first device may first determine the value of the flag bit, and then determine the field included in the data packet according to the value of the flag bit.
  • the first device may first determine a field included in the data packet, and then determine the value of the flag bit based on the field.
  • the flag bits corresponding to the m fields are used to indicate that the data packet contains the above m fields.
  • Step 203 sending a data packet.
  • the first device may send the data packet to the second device or the third device.
  • a flag bit is set in the data message, and the flag bit is used to indicate whether the data message contains the field corresponding to the flag bit, and the flag bit is the same as the predefined field.
  • the embodiments of the present application can flexibly and dynamically assemble data packets through flag bits, thereby changing the transmission volume of the data packets, so that the data packets can be transmitted on different data channels, which enhances the transmission capacity of the data packets. Universality.
  • the length flag 31 may be represented as L
  • the destination address flag 32 may be represented as D
  • the source address flag 33 may be represented as S
  • the transaction flag 34 may be represented as T.
  • the value of the flag bit includes a first value and a second value
  • the first value is used to indicate that the field corresponding to the flag bit is not included in the data packet
  • the second value is used to indicate that the data packet contains The field corresponding to this flag bit.
  • L, S, D, and T may be in big-endian order, and the first value and the second value may each include 1 bit.
  • the first value may be 0, and the second value may be 1.
  • the length flag bit 31 is used to indicate whether a length field 311 is included in the data packet, and the length field 311 is used to indicate the length of the data packet.
  • the length of the data packet may refer to the entire length including all fields of the message header and the payload.
  • L when the value of L is 0, it indicates that there is no length field (which may be expressed as Length (length)) in the data packet, and at this time, the length of the data packet continues to the end of the total data packet.
  • the value of L When the value of L is 1, it indicates that there is a length field in the data packet, and the length of the current data packet is the length indicated by the field content of the length field.
  • the lower-level protocol is a streaming transmission protocol without data boundary such as TCP (Transmission Control Protocol)
  • TCP Transmission Control Protocol
  • the value of L is only allowed to be set to 1. If the value of L is not 1, it should be Terminate lower-level connections.
  • the length field is encoded in little-endian byte order.
  • the length field consists of 2 bytes. For example, when the length of the data packet is 1228, the length field is encoded as 0xcc0x04.
  • the destination address flag bit 32 is used to indicate whether the data packet contains a destination address field 321, and the destination address field 321 is used to indicate the destination device address of the data packet.
  • the receiving device of the data packet is the device indicated by the destination device address of the data packet; if the lower-level protocol is a datagram transmission protocol that can distinguish message boundaries , it is divided into the following two situations: 1. If the current data packet is the first message in the total data packet, the receiving device of the data packet is the device indicated by the destination device address of the data packet; 2. If the current data message is not the first message in the total datagram, the field content of the current destination address field is the same as the field content of the destination address field of the first message in the total datagram.
  • D When the value of D is 1, it indicates that there is a destination address field in the data packet. At this time, the destination device address of the data packet is given by the field content of the destination address field.
  • the destination address field is encoded in 32-bit little-endian byte order, and the destination address field includes 4 bytes.
  • the source address flag bit 33 is used to indicate whether the data packet contains a source address field 331, and the source address field 331 is used to indicate the address of the sending device of the data packet.
  • the value of S when the value of S is 0, it indicates that the source address field (which may be expressed as Source Address) does not exist in the data packet.
  • the lower-level protocol is a streaming protocol that cannot distinguish message boundaries, the content of the source address field is given by the lower-level protocol; if the lower-level protocol is a datagram transmission protocol that can distinguish message boundaries, it can be divided into the following two types Situation: 1. If the current datagram is the first message in the total datagram, the field content of the source address field is given by the lower-level protocol (for example, by DTLS (Datagram Transport Level Security) 2. If the current datagram is not the first message in the total datagram, the field content of the current source address field is the same as the field content of the source address field of the first message in the total datagram .
  • DTLS Datagram Transport Level Security
  • the source address field is encoded in 32-bit little-endian byte order, and the source address field includes 4 bytes.
  • the source address and the destination address are assigned by the cloud server or the gateway is assigned instead of the cloud server (BLE, BLE Mesh).
  • the transaction flag bit 34 is used to indicate whether a transaction field 341 is included in the data packet, and the transaction field 341 is used to indicate a transaction and to track the processing process of the transaction.
  • T when the value of T is 0, it indicates that the transaction function is not currently used, and the transaction field does not exist in the data packet. At this point, the message is neither an active transaction nor a passive transaction, and is only used for notification. The message MUST NOT be handled as a general transaction message.
  • T When the value of T is 1, it indicates that the transaction function is currently used, and there is a transaction field in the data packet.
  • the transaction field (which can be expressed as Transaction) includes 4 bytes.
  • the transaction message is sent and received through the transaction flag bit.
  • the data message includes a transaction field, it indicates that the message is a transaction message, and the message processing at this time is processed according to the transaction flow; otherwise, it is processed according to the non-transactional flow. message processing.
  • the transaction field includes 32 bits, the lower 31 bits of the 32 bits are used to represent the identifier of the transaction, and the most significant bit of the 32 bits is used to represent the operator type of the transaction.
  • the lower 31 bits include the 1st, 2nd, 3rd bytes and the lower 7 bits of the 4th byte, and the identification of the transaction may also be referred to as a transaction unique identifier (Transaction ID (Identification, identity)).
  • the MSB is the MSB of the 4th byte.
  • the highest-order bit is used to indicate an active mark or a passive mark. When the active starter of a transaction sends a message, the highest-order bit can be set to 1. At this time, the highest-order bit is used to indicate an active mark; when the passive starter of a transaction sends a message, the highest-order bit is used. Bits can be set to 0, at this time the most significant bit is used to indicate passive flag.
  • the lower 31 bits are all 0.
  • the lower 31 bits are 256, and the cloud server must avoid using 0 to 255, a total of 256 transaction fields.
  • the connection is not established for the first time, each time a new transaction is actively initiated, the lower 31 bits are automatically incremented by 1. It should be noted that 2147483647 (2 ⁇ 31-1) is an invalid identifier. When the transaction identifier increases to this value or a message with the identifier is received, the transaction should be actively cleaned up and the connection terminated.
  • the transaction field is 0x010x000x000x80.
  • the passive starter sends a transaction-related message to the active starter, flip the most significant bit, and the transaction field is 0x010x000x000x00.
  • the transmission timing of the length field, the source address field, the destination address field and the transaction field is consistent with the arrangement order of the length flag bit, the source address flag bit, the destination address flag bit and the transaction flag bit. The order can be adjusted.
  • a message is mainly composed of source address (also known as source device address, sending device address), destination address (also known as destination device address), transaction related messages, message type, message content, etc. .
  • the domain network layer is used to process and distribute the data received from the secure transport layer, and forward data packets to other devices or to the model control layer of the device for processing.
  • the device address is a 32-bit number, which is the identification of the device.
  • the device address 0 (0x00000000) indicates that no identification is specified or there is no identification.
  • the sending source refers to the device that first sent the message
  • the sending destination also called the destination device refers to the device that finally receives and processes the message.
  • Transaction refers to the process of completely processing one thing, such as “the entire reading process of reading a certain state of the device”, “the entire processing process of changing a certain state of the device to another state”, “monitoring a certain state of the device”.
  • the whole listening process of the change of the state value "the whole sending process of sending a file to the device” and so on.
  • Domain network layer messages are allowed to be combined during the transmission process.
  • the lower layer is a streaming data transmission protocol with indistinguishable message boundaries (such as TLS (Transport Layer Security). protocol)
  • the domain network layer messages will be directly combined by the lower layer
  • the lower layer is a datagram transmission protocol (such as DTLS, BLE, UDP) that can distinguish the message boundary
  • the domain network layer message is allowed to be combined but not allowed to cross the datagram boundary
  • the sender and receiver of multiple messages within the same overall datagram may be identical.
  • the embodiments of the present application can flexibly dynamically assemble data packets through flag bits, efficiently and flexibly perform network data transmission and reception, and can be dynamically extended to use in various business scenarios.
  • the sending device address and destination device address of the message are defined in the data message, which can implement point-to-point data sending and receiving, and can also support data sending and receiving through intermediate routes.
  • the embodiment of the present application clearly defines the transaction message, and the present application can extend the message through the flexible definition of the message type, which greatly improves the flexibility of the message expression.
  • the data packet further includes a first extended option field 41 and a payload 42 corresponding to the first extended option field 41 .
  • the first extended option field 41 includes 1 byte
  • the payload 42 includes 4 bytes.
  • the data format of the payload 42 is a serialized structured data format.
  • the data format of the payload is protobuf (google protocol buffer).
  • the payload can be represented as Payload.
  • Payload uses protobuf for data representation, which makes the content expression of the data message more efficient, and then flexibly assembles the message dynamically in combination with the flag bits, and uses the binary format to define the data message.
  • Embodiments of this application It can be uniformly transmitted on data channels of various bandwidths such as wifi, BLE (Bluetooth Low Energy, Bluetooth Low Energy), and the use of data packets is more flexible.
  • the payload 42 includes an extension field 411 corresponding to the first extension option field 41 , a second extension option field 43 , and an extension field 431 corresponding to the second extension option field 43 .
  • the second extension option field includes 1 byte
  • the extension field corresponding to the second extension option field includes 2 bytes
  • the extension field corresponding to the first extension option field includes 1 byte
  • the first extension option field is represented as Type
  • Payload is the extension content
  • Type indicates the Payload type
  • the message is extended by Type.
  • the second extended option field is represented as next type.
  • message expansion is performed through the content of the field of Type. After the extension content, it is followed by another extension or the payload of the higher-level message, thus enabling flexible message extension.
  • the write attribute value message of the transaction timeout (Option Transaction Timeout) can be added to the data message.
  • the field content of the first extended option field is 0x80
  • the corresponding value of the first extended option field is 0x80.
  • the field content of the extension field is 10
  • the field content of the second extension option field is 7
  • the field content of the extension field corresponding to the second extension option field is PropertiesWriteReq, which is a protocol property.
  • the first byte of the payload is the second extension option field
  • the second byte is the extension field corresponding to the first extension option field
  • the third and fourth bytes are the second extension The extension field corresponding to the option field.
  • the data packet further includes a version number field 51, and the version number field 51 is used to indicate the current version of the data packet.
  • the version number field may be represented as Ver (Version, version), and the version number fields corresponding to different versions are different, that is, the field contents of the version number fields corresponding to different versions are different.
  • Ver adopts big-endian bit order
  • the version number field includes 2 bits. For example, 00 is used to indicate that the current version of the data packet is the first version, and 01 is used to indicate that the current version of the data packet is For the second version, 10 is used to indicate that the current version of the data packet is the third version, and 11 is used to indicate that the current version of the data packet is the fourth version.
  • the fields in the data packet can be redefined and expanded into a new data packet.
  • the version number field may further include 3 bits or even more bits, which is not limited in this embodiment of the present application.
  • the data packet further includes a protocol extension field 52, and the protocol extension field 52 is used to indicate an extended function related to the data packet.
  • the protocol extension field may include 2 bits. For example, when the protocol extension field is 01, it indicates that the data in the payload is encrypted by AES (Advanced Encryption Standard).
  • AES Advanced Encryption Standard
  • the message header may include a version number field, a protocol extension field, a flag bit, and a first extension option field.
  • the message header may also include a length field, a source address field, a destination address field, and a transaction field.
  • Step 601 receiving a data message.
  • Step 602 Read n flag bits included in the data packet.
  • the ith flag bit among the n flag bits is used to indicate whether the data packet includes a field corresponding to the ith flag bit among the predefined n fields, and n is a positive integer.
  • the n flag bits correspond to the n fields one-to-one, and different fields correspond to different flag bits.
  • it is determined by the value of the flag bit whether the data packet contains a field corresponding to the flag bit.
  • the flag bit can be represented by 1 bit.
  • the value of the flag bit can be 0 or 1. When the value of the flag bit is 0, it indicates that the data packet does not contain the field corresponding to the flag bit; When the value of is 1, it indicates that the data packet contains the field corresponding to this flag bit.
  • the value of the flag bit may also be other values, which are not limited in this embodiment of the present application.
  • Step 603 Based on the n flag bits, parse m fields included in the data packet, where m is a positive integer less than or equal to n.
  • the flag bits corresponding to the m fields are used to indicate that the above m fields are included in the data packet.
  • the second device or the third device parses the field corresponding to the flag bit whose value is 1.
  • the second device may parse only some of the fields included in the data packet as required, without parsing all the fields included in the data packet.
  • a flag bit is set in the data message, and the flag bit is used to indicate whether the data message contains the field corresponding to the flag bit, and the flag bit is the same as the predefined field.
  • the embodiments of the present application can flexibly and dynamically assemble data packets through flag bits, so as to change the transmission volume of data packets, so that data packets can be transmitted on different data channels, thereby enhancing the transmission capacity of data packets. Universality.
  • the n flag bits include at least one of the following:
  • the length flag bit is used to indicate whether the data packet contains a length field, and the length field is used to indicate the length of the data packet.
  • the destination address flag bit is used to indicate whether the data packet contains a destination address field, and the destination address field is used to indicate the destination device address of the data packet.
  • the source address flag bit is used to indicate whether the data packet contains a source address field, and the source address field is used to indicate the address of the sending device of the data packet.
  • the transaction flag bit is used to indicate whether the data packet contains a transaction field, and the transaction field is used to indicate the transaction and to track the processing process of the transaction.
  • the transaction field includes 32 bits, the lower 31 bits of the 32 bits are used to represent the identifier of the transaction, and the most significant bit of the 32 bits is used to represent the operator type of the transaction.
  • the receiving device (also referred to as a data packet processing device) needs to determine whether the data packet is a data packet to be forwarded, that is, the receiving device needs to determine whether it is the second device or the third device, When the receiving device determines that the data packet is a data packet to be forwarded, the receiving device is the second device; when the receiving device determines that the data packet is not a data packet to be forwarded, the receiving device is the third device.
  • the flag bit includes the source address flag bit
  • the source address flag bit is used to indicate that the data packet does not contain a source address field
  • the address of the sending device of the data packet is determined as the source address.
  • the field content of the field is added to the datagram.
  • the forwarding process of the second device is as follows: 1. Determine the field content of the destination address field from the data message; 2. Check whether the destination device address corresponding to the field content of the destination address field can be directly connected; 3. If the destination If the device address can be directly connected, the data packet is forwarded to the third device; 4. If the destination device address cannot be directly connected, the forwarding is refused; 5.
  • the second device needs to rewrite the message header (that is, the header of the data packet), and determine the sending device address of the data packet as the field content of the source address field. 6. Send the adjusted data message to the third device.
  • message forwarding occurs at most once.
  • Message forwarding has the following provisions: the second device must be able to directly communicate with the third device, and cannot forward messages to another second device. The second device cannot forward the message back to the original connection of the message.
  • the receiving device determines whether the data packet is a data packet to be forwarded in the following manner:
  • step 3 Compare the address of the destination device with the address of the receiving device; if the address of the destination device is the same as the address of the receiving device, perform the following step 3; if the address of the destination device and the receiving device are different, perform the following step 4.
  • the address of the receiving device refers to the address of the current receiving device, that is, the address of the device that currently receives the data packet.
  • the destination device address is the address of the device that finally received the datagram.
  • the receiving device After receiving the data packet, the receiving device reads the destination address flag bit. If the value of the destination address flag bit is 0, it indicates that the data packet is not a data packet to be forwarded; if the value of the destination address flag bit is 1, it receives The device then compares the destination device address with the receiving device address. If the address of the destination device is the same as the address of the receiving device, the data packet is not a data packet to be forwarded, and the receiving device is a third device; if the address of the destination device is inconsistent with the address of the receiving device, the data packet is a data packet to be forwarded , the receiving device is the second device.
  • the data packet further includes the first extended option field and a payload corresponding to the first extended option field.
  • the processing process of the transaction message is as follows: 1. Determine whether the Type is a reserved value (the reserved value refers to the value in the model control layer); if the Type is a reserved value, the message is ignored, and the processing process ends; If Type is not a reserved value, continue with the following process. 2. Find the list of ongoing transactions on the current connection according to the transaction field. If the existing transaction (including active tag or passive tag) can be matched, it will be distributed to the existing transaction for processing, and the processing process will end; if the corresponding transaction cannot be found, the following process will continue. 3. Determine the active transaction or the passive transaction according to the transaction field.
  • Non-transactional message handling can be used for broadcast messages such as Bluetooth Beacons.
  • the data format of the payload is a serialized structured data format.
  • the payload includes an extension field corresponding to the first extension option field, a second extension option field, and an extension field corresponding to the second extension option field.
  • the data packet further includes a version number field, and the version number field is used to indicate the current version of the data packet.
  • the data packet further includes a protocol extension field, where the protocol extension field is used to indicate an extended function related to the data packet.
  • the sending device in the embodiment of the present application may also be referred to as a sender or a sender; the receiving device in the embodiment of the present application may also be referred to as a receiver or a receiver. Therefore, the sending device address may also be referred to as a sender address or a sender address, and the receiving device address may also be referred to as a receiver address or a receiver address, which is not limited in this embodiment of the present application.
  • Scenario 1 The control device (the first device) writes properties (such as turning on the light) to the sub-device (the third device) under the TCP channel. Since the control of the sub-device by the control device needs to be relayed through the gateway (the second device), Therefore, the data packet needs to include a source address field and a destination address field, and the format of the data packet is shown in Figure 7.
  • the field content of the first extended option field is 0x07
  • the field content of the payload is Set Properties Request msg (set properties request message).
  • Scenario 2 The control device (the first device) writes attributes (such as turning on the lights) to the sub-device (third device) under the Bluetooth GATT (Generic Attribute Profile) or UDP channel.
  • the datagram The message does not need to include a length field, and the format of the data message is shown in Figure 8.
  • the field content of the first extended option field is 0x07, and the field content of the payload is Set Properties Request msg (set properties request message).
  • Scenario 3 The control device (the first device) writes the attributes (such as turning on the light) point-to-point to the sub-device (third device) under the Bluetooth GATT or UDP channel.
  • the data packet does not need to include the length field and the source address field. and the destination address field, the format of the data message is shown in Figure 9.
  • the field content of the first extended option field is 0x07, and the field content of the payload is Set Properties Request msg (set properties request message).
  • Scenario 4 The cloud (the first device) sends a notification to the sub-device (the third device) through the UDP channel, such as a change of home notification.
  • the data packet does not need to include the length field, source address field, destination address field and transaction field.
  • the format of the data message is shown in Figure 10.
  • the field content of the first extended option field is 0x38, and the field content of the payload is Home Change Notify msg (home change notification).
  • an embodiment of the present application further provides a data packet for transmission between devices, where the data packet is used to load information during data transmission between devices, and the data packet includes a predefined m fields among the n fields of , where n is a positive integer, and m is a positive integer less than or equal to n.
  • the data packet further includes n flag bits, and the ith flag bit among the n flag bits is used to indicate whether the data message includes a field corresponding to the ith flag bit among the n fields.
  • the n flag bits include at least one of the following: a length flag bit, which is used to indicate whether the data packet contains a length field, and the length field is used to indicate the length of the data packet. Length; destination address flag bit, used to indicate whether the data packet contains the destination address field, the destination address field is used to indicate the destination device address of the data packet; source address flag bit, used to indicate whether the data packet contains the source address The address field, the source address field, is used to indicate the address of the sending device of the data packet; the transaction flag bit is used to indicate whether the data packet contains a transaction field, and the transaction field is used to indicate the transaction and track the processing process of the transaction.
  • a length flag bit which is used to indicate whether the data packet contains a length field, and the length field is used to indicate the length of the data packet. Length
  • destination address flag bit used to indicate whether the data packet contains the destination address field, the destination address field is used to indicate the destination device address of the data packet
  • source address flag bit used to indicate whether the data packet contains
  • the data packet further includes the first extended option field and a payload corresponding to the first extended option field.
  • the data packet further includes a protocol extension field, where the protocol extension field is used to indicate an extended function related to the data packet.
  • the data format of the payload is a serialized structured data format.
  • the payload includes an extension field corresponding to the first extension option field, a second extension option field, and an extension field corresponding to the second extension option field.
  • the data packet further includes a version number field, and the version number field is used to indicate the current version of the data packet.
  • the data packet may simultaneously include n flag bits, a first extension option field, a payload corresponding to the first extension option field, and a protocol extension field.
  • the data packet may include some or all of the above fields according to actual application requirements.
  • FIG. 11 shows a block diagram of an apparatus for sending a data message provided by an embodiment of the present application.
  • the apparatus has the function of implementing the above-mentioned method example, and the function may be implemented by hardware, or the corresponding software may be executed by the hardware. accomplish.
  • the apparatus 1100 may include: a field determination module 1110 , a message generation module 1120 and a message transmission module 1130 .
  • the field determination module 1110 is configured to determine m fields included in the data packet from predefined n fields, where n is a positive integer, and m is a positive integer less than or equal to the n.
  • a message generating module 1120 configured to generate the data message including the m fields; wherein, the data message also includes n flag bits, and the i-th flag bit in the n flag bits , which is used to indicate whether the data packet includes a field corresponding to the i-th flag bit among the n fields.
  • a message sending module 1130 configured to send the data message.
  • a flag bit is set in the data message, and the flag bit is used to indicate whether the data message contains the field corresponding to the flag bit, and the flag bit is the same as the predefined field.
  • the embodiments of the present application can flexibly and dynamically assemble data packets through flag bits, so as to change the transmission volume of data packets, so that data packets can be transmitted on different data channels, thereby enhancing the transmission capacity of data packets. Universality.
  • the n flag bits include at least one of the following:
  • a length flag bit used to indicate whether the data packet includes a length field, and the length field is used to indicate the length of the data packet;
  • a destination address flag bit used to indicate whether the data packet contains a destination address field, and the destination address field is used to indicate the destination device address of the data packet;
  • a source address flag bit used to indicate whether the data packet contains a source address field, and the source address field is used to indicate the sending device address of the data packet;
  • the transaction flag bit is used to indicate whether the data packet contains a transaction field, and the transaction field is used to indicate a transaction and to track the processing process of the transaction.
  • the transaction field includes 32 bits, the lower 31 bits of the 32 bits are used to represent the identifier of the transaction, and the most significant bit of the 32 bits is used to represent the Specifies the type of operator of the transaction.
  • the data packet further includes a first extended option field and a payload corresponding to the first extended option field.
  • the data format of the payload is a serialized structured data format.
  • the payload includes an extension field corresponding to the first extension option field, a second extension option field, and an extension field corresponding to the second extension option field.
  • the data packet further includes a protocol extension field, where the protocol extension field is used to indicate an extended function related to the data packet.
  • FIG. 12 shows a block diagram of a data packet processing apparatus provided by an embodiment of the present application.
  • the apparatus has the function of implementing the above method example, and the function may be implemented by hardware, or the corresponding software may be executed by the hardware. accomplish.
  • the apparatus 1200 may include: a message receiving module 1210 , a flag bit reading module 1220 and a field parsing module 1230 .
  • the message receiving module 1210 is used for receiving data messages.
  • the flag bit reading module 1220 is used to read the n flag bits included in the data message; wherein, the i-th flag bit in the n flag bits is used to indicate whether the data message contains It includes a field corresponding to the i-th flag bit among the predefined n fields, where n is a positive integer.
  • the field parsing module 1230 is configured to parse m fields included in the data packet based on the n flag bits, where m is a positive integer less than or equal to the n.
  • a flag bit is set in the data message, and the flag bit is used to indicate whether the data message contains the field corresponding to the flag bit, and the flag bit is the same as the predefined field.
  • the embodiments of the present application can flexibly and dynamically assemble data packets through flag bits, so as to change the transmission volume of data packets, so that data packets can be transmitted on different data channels, thereby enhancing the transmission capacity of data packets. Universality.
  • the n flag bits include at least one of the following:
  • a length flag bit used to indicate whether the data packet includes a length field, and the length field is used to indicate the length of the data packet;
  • a destination address flag bit used to indicate whether the data packet contains a destination address field, and the destination address field is used to indicate the destination device address of the data packet;
  • the transaction field includes 32 bits, the lower 31 bits of the 32 bits are used to represent the identifier of the transaction, and the most significant bit of the 32 bits is used to represent the Specifies the type of operator of the transaction.
  • the field adding module is configured to, if the data message is the data message to be forwarded, the flag bit includes the source address flag bit, and the source address flag bit is used to indicate the data message If the source address field is not included in the data packet, the sending device address of the data packet is determined as the field content of the source address field and added to the data packet.
  • the message determination module is configured to:
  • the address of the destination device is the same as the address of the receiving device, it is determined that the data packet is not the data packet to be forwarded;
  • the destination device address is different from the receiving device address, it is determined that the data packet is the to-be-forwarded data packet
  • the data format of the payload is a serialized structured data format.
  • the payload includes an extension field corresponding to the first extension option field, a second extension option field, and an extension field corresponding to the second extension option field.
  • FIG. 13 shows a schematic structural diagram of a data packet sending device 1300 provided by an embodiment of the present application.
  • the data packet sending device 1300 may include: a processor 1301 , a receiver 1302 , a transmitter 1303 , and a memory 1304 and bus 1305.
  • the processor 1301 includes one or more processing cores, and the processor 1301 executes various functional applications and information processing by running software programs and modules.
  • the receiver 1302 and the transmitter 1303 may be implemented as a communication component, which may be a communication chip.
  • the memory 1304 is connected to the processor 1301 through the bus 1305 .
  • the memory 1304 can be used to store a computer program, and the processor 1301 is used to execute the computer program, so as to implement various steps performed by the data message sending device in the above method embodiments.
  • memory 1304 may be implemented by any type or combination of volatile or non-volatile storage devices including, but not limited to, magnetic or optical disks, electrically erasable programmable Read-Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), Erasable Programmable Read-Only Memory (EPROM), Static Random Access Memory (SRAM), Read-Only Memory (Read-Only Memory, ROM), magnetic memory, flash memory, programmable read-only memory (Programmable Read Only Memory, PROM).
  • volatile or non-volatile storage devices including, but not limited to, magnetic or optical disks, electrically erasable programmable Read-Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), Erasable Programmable Read-Only Memory (EPROM), Static Random Access Memory (SRAM), Read-Only Memory (Read-Only Memory, ROM), magnetic memory, flash memory, programmable read-only memory (Programmable Read Only Memory, PROM).
  • the data message sending device includes a processor, a memory and a transceiver
  • the transceiver may include a receiver and a transmitter, the receiver is used for receiving information, and the transmitter is used for transmitting information.
  • the processor is further configured to generate the data message including the m fields; wherein, the data message further includes n flag bits, and the i-th flag bit in the n flag bits , used to indicate whether the data message contains a field corresponding to the i-th flag bit in the n fields;
  • the transceiver is further configured to send the data message.
  • the n flag bits include at least one of the following:
  • a length flag bit used to indicate whether the data packet includes a length field, and the length field is used to indicate the length of the data packet;
  • a source address flag bit used to indicate whether the data packet contains a source address field, and the source address field is used to indicate the sending device address of the data packet;
  • the transaction flag bit is used to indicate whether the data packet contains a transaction field, and the transaction field is used to indicate a transaction and to track the processing process of the transaction.
  • the transaction field includes 32 bits, the lower 31 bits of the 32 bits are used to represent the identifier of the transaction, and the most significant bit of the 32 bits is used to represent the Specifies the type of operator of the transaction.
  • the data packet further includes a first extended option field and a payload corresponding to the first extended option field.
  • the data format of the payload is a serialized structured data format.
  • the payload includes an extension field corresponding to the first extension option field, a second extension option field, and an extension field corresponding to the second extension option field.
  • the data packet further includes a protocol extension field, where the protocol extension field is used to indicate an extended function related to the data packet.
  • FIG. 14 shows a schematic structural diagram of a data packet processing device 1400 provided by an embodiment of the present application.
  • the data packet processing 1400 may include: a processor 1401, a receiver 1402, a transmitter 1403, a memory 1404, and a bus 1405.
  • the processor 1401 includes one or more processing cores, and the processor 1401 executes various functional applications and information processing by running software programs and modules.
  • the receiver 1402 and the transmitter 1403 may be implemented as a communication component, which may be a communication chip.
  • the memory 1404 is connected to the processor 1401 through the bus 1405 .
  • the memory 1404 can be used to store a computer program, and the processor 1401 is used to execute the computer program, so as to implement various steps performed by the data packet processing device in the above method embodiments.
  • memory 1404 may be implemented by any type or combination of volatile or non-volatile storage devices including, but not limited to, magnetic or optical disks, electrically erasable programmable Read-Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), Erasable Programmable Read-Only Memory (EPROM), Static Random Access Memory (SRAM), Read-Only Memory (Read-Only Memory, ROM), magnetic memory, flash memory, programmable read-only memory (Programmable Read Only Memory, PROM).
  • volatile or non-volatile storage devices including, but not limited to, magnetic or optical disks, electrically erasable programmable Read-Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), Erasable Programmable Read-Only Memory (EPROM), Static Random Access Memory (SRAM), Read-Only Memory (Read-Only Memory, ROM), magnetic memory, flash memory, programmable read-only memory (Programmable Read Only Memory, PROM).
  • the data packet processing includes a processor, a memory, and a transceiver, which may include a receiver and a transmitter, the receiver for receiving information, and the transmitter for transmitting information.
  • the transceiver for receiving data packets
  • the processor is configured to read the n flag bits included in the data message; wherein, the i-th flag bit in the n flag bits is used to indicate whether the data message contains a pre- A field corresponding to the i-th flag bit in the defined n fields, where n is a positive integer;
  • the processor is further configured to parse m fields included in the data packet based on the n flag bits, where m is a positive integer less than or equal to the n.
  • the n flag bits include at least one of the following:
  • a length flag bit used to indicate whether the data packet includes a length field, and the length field is used to indicate the length of the data packet;
  • a destination address flag bit used to indicate whether the data packet contains a destination address field, and the destination address field is used to indicate the destination device address of the data packet;
  • a source address flag bit used to indicate whether the data packet contains a source address field, and the source address field is used to indicate the sending device address of the data packet;
  • the transaction flag bit is used to indicate whether the data packet contains a transaction field, and the transaction field is used to indicate a transaction and to track the processing process of the transaction.
  • the transaction field includes 32 bits, the lower 31 bits of the 32 bits are used to represent the identifier of the transaction, and the most significant bit of the 32 bits is used to represent the Specifies the type of operator of the transaction.
  • the processor is further configured to determine whether the data packet is a data packet to be forwarded;
  • the processor is further configured to, if the data packet is the data packet to be forwarded, the flag bit includes the source address flag bit, and the source address flag bit is used to indicate the data packet If the source address field is not included in the data packet, the sending device address of the data packet is determined as the field content of the source address field and added to the data packet.
  • the processor is further configured to, in response to the data packet including the destination device address, compare the destination device address with the receiving device address;
  • the processor is further configured to determine that the data packet is not the to-be-forwarded data packet if the destination device address is the same as the receiving device address;
  • the processor is further configured to determine that the data packet is the to-be-forwarded data packet if the destination device address is different from the receiving device address;
  • the processor is further configured to, in response to that the data packet does not contain the destination device address, determine that the data packet is not the data packet to be forwarded.
  • the data packet further includes a first extended option field and a payload corresponding to the first extended option field.
  • the data format of the payload is a serialized structured data format.
  • the data packet further includes a protocol extension field, where the protocol extension field is used to indicate an extended function related to the data packet.
  • a computer-readable storage medium is also provided, and a computer program is stored in the computer-readable storage medium, and the computer program is loaded and executed by the processor of the data message sending device to realize the above-mentioned Each step in the embodiment of the method for sending a data message.
  • a computer-readable storage medium is also provided, and a computer program is stored in the computer-readable storage medium, and the computer program is loaded and executed by the processor of the data packet processing device to realize the above-mentioned Each step in the embodiment of the data packet processing method.
  • a computer program product includes computer instructions stored in a computer-readable storage medium.
  • the processor of the data message sending device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the data message sending device executes the data message sending method provided in the above aspects.
  • a computer program product includes computer instructions stored in a computer-readable storage medium.
  • the processor of the data packet processing device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the data packet processing device executes the data packet processing methods provided in the above aspects.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Communication Control (AREA)

Abstract

本申请实施例提供了一种数据报文发送方法、处理方法、装置、设备及数据报文，涉及通信技术领域。所述方法包括：从预定义的n个字段中，确定数据报文中包括的m个字段，n为正整数，且m为小于等于n的正整数；生成包括m个字段的数据报文；其中，数据报文中还包括n个标志位，n个标志位中的第i个标志位，用于指示数据报文中是否包含n个字段中的与第i个标志位对应的字段；发送数据报文。本申请实施例增强了数据报文的通用性。

Description

数据报文发送方法、处理方法、装置、设备及数据报文
本申请要求于2020年08月31日提交的申请号为202010901599.1、发明名称为“数据报文发送方法、处理方法、装置、设备及数据报文”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，特别涉及一种数据报文发送方法、处理方法、装置、设备及数据报文。
背景技术
通信协议是指双方实体完成通信或服务所必须遵循的规则和约定。
在相关技术中，不同业务使用不同的通信协议。例如，HTTP(HyperText Transfer Protocol，超文本传输协议)是用于从WWW服务器传输超文本到本地浏览器的传输协议，其一般用于在一些支持IP(Internet Protocol，互联网协议)的数据通道上传输数据，在一些低带宽如BLE(Bluetooth Low Energy，低功耗蓝牙)数据通道上就不适用了。
发明内容
本申请实施例提供一种数据报文发送方法、处理方法、装置、设备及数据报文。所述技术方案如下：
一方面，本申请实施例提供一种数据报文发送方法，所述方法包括：
从预定义的n个字段中，确定数据报文中包括的m个字段，所述n为正整数，且所述m为小于等于所述n的正整数；
生成包括所述m个字段的所述数据报文；其中，所述数据报文中还包括n个标志位，所述n个标志位中的第i个标志位，用于指示所述数据报文中是否包含所述n个字段中的与所述第i个标志位对应的字段；
发送所述数据报文。
另一方面，本申请实施例提供一种数据报文处理方法，所述方法包括：
接收数据报文；
读取所述数据报文中包括的n个标志位；其中，所述n个标志位中的第i个标志位，用于指示所述数据报文中是否包含预定义的n个字段中的与所述第i个标志位对应的字段，所述n为正整数；
基于所述n个标志位，解析所述数据报文中包括的m个字段，所述m为小于等于所述n的正整数。
另一方面，本申请实施例提供一种数据报文发送装置，所述装置包括：
字段确定模块，用于从预定义的n个字段中，确定数据报文中包括的m个字段，所述n为正整数，且所述m为小于等于所述n的正整数；
报文生成模块，用于生成包括所述m个字段的所述数据报文；其中，所述数据报文中还包括n个标志位，所述n个标志位中的第i个标志位，用于指示所述数据报文中是否包含所述n个字段中的与所述第i个标志位对应的字段；
报文发送模块，用于发送所述数据报文。
另一方面，本申请实施例提供一种数据报文处理装置，所述装置包括：
报文接收模块，用于接收数据报文；
标志位读取模块，用于读取所述数据报文中包括的n个标志位；其中，所述n个标志位中的第i个标志位，用于指示所述数据报文中是否包含预定义的n个字段中的与所述第i个标志位对应的字段，所述n为正整数；
字段解析模块，用于基于所述n个标志位，解析所述数据报文中包括的m个字段，所述m为小于等于所述n的正整数。
又一方面，本申请实施例提供一种数据报文发送设备，所述设备包括处理器、存储器和收发器；
所述处理器，用于从预定义的n个字段中，确定数据报文中包括的m个字段，所述n为正整数，且所述m为小于等于所述n的正整数；
所述处理器，还用于生成包括所述m个字段的所述数据报文；其中，所述数据报文中还包括n个标志位，所述n个标志位中的第i个标志位，用于指示所述数据报文中是否包含所述n个字段中的与所述第i个标志位对应的字段；
所述收发器，还用于发送所述数据报文。
又一方面，本申请实施例提供一种数据报文处理设备，所述设备包括处理器、存储器和收发器；
所述收发器，用于接收数据报文；
所述处理器，用于读取所述数据报文中包括的n个标志位；其中，所述n个标志位中的第i个标志位，用于指示所述数据报文中是否包含预定义的n个字段中的与所述第i个标志位对应的字段，所述n为正整数；
所述处理器，还用于基于所述n个标志位，解析所述数据报文中包括的m个字段，所述m为小于等于所述n的正整数。
又一方面，本申请实施例提供一种用于设备间传输的数据报文，所述数据报文用于在设备间进行数据传输时装载信息，所述数据报文中包括预定义的n个字段中的m个字段，所述n为正整数，且所述m为小于等于所述n的正整数；
所述数据报文还包括n个标志位，所述n个标志位中的第i个标志位，用于指示所述数据报文中是否包含所述n个字段中的与所述第i个标志位对应的字段。
又一方面，本申请实施例提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，所述计算机程序由处理器加载并执行以实现如上述方面所述的数据报文发送方法，或实现如上述方面所述的数据报文处理方法。
又一方面，本申请实施例提供一种计算机程序产品，该计算机程序产品包括计算机指令，该计算机指令存储在计算机可读存储介质中。计算机设备的处理器从计算机可读存储介质读取该计算机指令，处理器执行该计算机指令，使得该计算机设备执行上述方面所述的数据报文发送方法，或实现如上述方面所述的数据报文处理方法。
附图说明
图1是本申请一个实施例提供的实施环境的示意图；
图2是本申请一个实施例提供的数据报文发送方法的流程图；
图3至图5是本申请实施例提供的数据报文的格式示意图；
图6是本申请一个实施例提供的数据报文处理方法的流程图；
图7至图10是本申请实施例提供的数据报文的格式示意图；
图11是本申请一个实施例提供的数据报文发送装置的框图；
图12是本申请一个实施例提供的数据报文处理装置的框图；
图13是本申请一个实施例提供的数据报文发送设备的结构示意图；
图14是本申请一个实施例提供的数据报文处理设备的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作进一步地详细描述。
请参考图1，其示出了本申请一个实施例提供的实施环境的示意图，该实施环境可以包括：第一设备10、第二设备20和第三设备30。
在本申请实施例中，第一设备10是指数据报文发送设备，数据报文发送设备是指发送数据报文的设备。示例性地，第一设备10可以是终端或服务器，例如，终端可以是智能手机、平板电脑、PC(Personal Computer，个人计算机)、智能多媒体设备、智能可穿戴设备等；服务器可以是一台服务器，也可以是由多台服务器组成的服务器集群，也可以是云服务器，还可以是IoT(Internet of Things，物联网)服务器。当然，在可能的实现方式中，数据报文可以由APP(Application，应用程序)发送。
在本申请实施例中，第二设备20是中转设备，也即，第二设备20是用于将第一设备10发送的数据报文转发至第三设备30的设备。示例性地，第二设备20可以是网桥、路由、网关等。
示例性地，第三设备30可以是终端，例如，终端可以是智能手机、平板电脑、PC(Personal Computer，个人计算机)、智能多媒体设备、智能可穿戴设备、智能家居设备、智能交通设备等。第三设备30的数量可以是一个，也可以是多个，本申请实施例对此不作限定。
需要说明的是，第二设备20和第三设备30都可以称之为数据报文处理设备，数据报文处理设备是指对数据报文进行处理的设备。
在可能的实现方式中，第一设备10和第三设备30之间可能不能直接进行通信，需要第二设备20进行中转。此时，第一设备10将数据报文发送给第二设备20，以使得第二设备20将该数据报文转发给第三设备30；或者，第一设备10和第三设备30之间可以直接进行通信，不用通过第二设备20进行中转，也即，第一设备10和第三设备30之间可以实现点对点通信。此时，第一设备10将数据报文发送给第三设备30。
在可能的实现方式中，本申请实施例中的数据报文还可以称之为消息、域网络层消息等其他名称。第一设备10会同时向第二设备20或第三设备30发送多个消息，该多个消息形成了总数据报。
下面，将结合几个示例性实施例，对本申请技术方案进行介绍说明。
请参考图2，其示出了本申请一个实施例提供的数据报文发送方法的流程图。该方法可以由第一设备执行，例如第一设备可以是图1所示实施环境中的第一设备10。该方法可以包括如下几个步骤(201～203)。
步骤201，从预定义的n个字段中，确定数据报文中包括的m个字段，n为正整数，且m为小于等于n的正整数。
可以理解的，技术人员预先定义好数据报文中可以包括的n个字段，上述n个字段并不一定需要全部在数据报文中给出，而是可以根据传输场景选择必要的字段在数据报文中给出。例如，在可能的实现方式中，假设预定义的n个字段包括：字段1、字段2、字段3和字段4，与传输场景1相关的字段为字段2和字段3，则数据报文中包括2个字段：字段2和字段3。又例如，与传输场景2相关的字段为字段1、字段2、字段3和字段4，则数据报文中包括4个字段：字段1、字段2、字段3和字段4。又例如，数据报文中可以不包括预定义的n个字段中的全部字段，也即m的数量为0。
在一些实施例中，数据报文中除了包括从预定义的n个字段中确定的m个字段之外，还可能包括至少一个其他字段，该其他字段可以不是从预定义的n个字段中确定的，本申请对此不作限定。
步骤202，生成包括m个字段的数据报文。
其中，数据报文中还包括n个标志位，n个标志位中的第i个标志位，用于指示数据报文中是否包含n个字段中的与该第i个标志位对应的字段，i为小于等于n的正整数。
n个标志位与n个字段一一对应，不同的字段对应有不同的标志位。仍然以上述示例为例，字段1对应标志位1、字段2对应标志位2、字段3对应标志位3、字段4对应标志位4，假设数据报文中包括字段2和字段3，第一设备可以生成包括上述字段2和字段3的数据报文，数据报文中包括标志位1、标志位2、标志位3和标志位4，标志位1用于指示数据报文 中不包含字段1，标志位2用于指示数据报文中包含字段2，标志位3用于指示数据报文中包含字段3，标志位4用于指示数据报文中不包含字段4。字段2的字段内容和字段3的字段内容可以为二进制格式。
在可能的实现方式中，通过标志位的值来确定数据报文中是否包含与该标志位对应的字段。标志位可以用1位比特表示，示例性地，标志位的值可以为0或1，当标志位的值为0时，表明数据报文中不包含与该标志位对应的字段；当标志位的值为1时，表明数据报文中包含与该标志位对应的字段。当然，在其它可能的实现方式中，标志位的值还可以是其它值，本申请实施例对此不作限定。
在一个示例中，第一设备可以先确定标志位的值，再根据标志位的值确定数据报文中包括的字段。
在另一个示例中，第一设备可以先确定数据报文中包括的字段，再基于此确定标志位的值。
在本申请实施例中，与m个字段对应的标志位，用于指示数据报文中包含上述m个字段。
步骤203，发送数据报文。
当第一设备生成数据报文后，第一设备可以向第二设备或第三设备发送数据报文。
综上所述，本申请实施例提供的技术方案中，通过在数据报文中设置标志位，标志位用于指示数据报文中是否包含该标志位对应的字段，标志位与预定义的字段相对应，本申请实施例可以通过标志位对数据报文进行灵活地动态组装，从而改变数据报文的传输量，使得数据报文可以在不同的数据通道上进行传输，增强了数据报文的通用性。
在示意性实施例中，如图3所示，n个标志位包括以下至少一项：长度标志位31、目的地址标志位32、源地址标志位33、事务标志位34。
示例性地，长度标志位31可以表示为L，目的地址标志位32可以表示为D，源地址标志位33可以表示为S，事务标志位34可以表示为T。
在可能的实现方式中，标志位的值包括第一数值和第二数值，第一数值用于指示数据报文中不包含该标志位对应的字段，第二数值用于指示数据报文中包含该标志位对应的字段。L、S、D、T可以采用大端位序，第一数值和第二数值可以分别包括1位比特，例如，第一数值可以为0，第二数值可以为1。
长度标志位31，用于指示数据报文中是否包含长度字段311，长度字段311用于指示数据报文的长度。
数据报文的长度可以是指包括消息头的所有字段及Payload的整体长度。
示例性地，当L的值为0时，表明数据报文中不存在长度字段(可以表示为Length(长度))，此时，数据报文的长度持续至总数据报结尾。例如，当更底层协议是UDP(User Datagram Protocol，用户数据报协议)等有数据边界的协议时，L＝0意味着总数据报的剩余部分内容均为当前数据报文的内容。
当L的值为1时，表明数据报文中存在长度字段，当前数据报文的长度为长度字段的字段内容指示的长度。示例性地，当更底层协议是TCP(Transmission Control Protocol，传输控制协议)等无数据边界的流式传输协议时，L的值只允许被设置为1，若L的值不为1，则应当终止更底层连接。
在可能的实现方式中，长度字段编码采用小端字节序。长度字段包括2个字节。例如，数据报文的长度为1228时，长度字段编码为0xcc0x04。
目的地址标志位32，用于指示数据报文中是否包含目的地址字段321，目的地址字段321用于指示数据报文的目的地设备地址。
示例性地，当D的值为0时，表明数据报文中不存在目的地址字段(可以表示为Destination Address(目的地址))。若更底层协议为无法区分消息边界的流式传输协议，则数据报文的接收设备即为数据报文的目的地设备地址指示的设备；若更底层协议为可以区分消息边界的数 据报传输协议，则分为以下两种情形：1、若当前数据报文是总数据报内的第一条消息，则数据报文的接收设备即为数据报文的目的地设备地址指示的设备；2、若当前数据报文不是总数据报内的第一条消息，则当前目的地址字段的字段内容与总数据报内的第一条消息的目的地址字段的字段内容相同。
当D的值为1时，表明数据报文中存在目的地址字段，此时，数据报文的目的地设备地址由目的地址字段的字段内容给出。
示例性地，在同一个总数据报内出现多条消息时，从第2条消息开始，D取值必须为0，否则包含D＝1的消息在内的剩余数据被忽略。
在可能的实现方式中，目的地址字段按照32位小端字节序编码，目的地址字段包括4个字节。
源地址标志位33，用于指示数据报文中是否包含源地址字段331，源地址字段331用于指示数据报文的发送设备地址。
示例性地，当S的值为0时，表明数据报文中不存在源地址字段(可以表示为Source Address(源地址))。若更底层协议为无法区分消息边界的流式传输协议，源地址字段的字段内容由更底层协议给出；若更底层协议为可以区分消息边界的数据报传输协议，则可以分为以下两种情形：1、若当前数据报文是总数据报内的第一条消息，则源地址字段的字段内容由更底层协议给出(例如，由DTLS(Datagram Transport Level Security，数据报安全传输协议)的证书给出)；2、若当前数据报文不是总数据报内的第一条消息，则当前源地址字段的字段内容与总数据报内的第一条消息的源地址字段的字段内容相同。
当S的值为1时，表明数据报文中存在源地址字段，此时，数据报文的发送设备地址由源地址字段的字段内容给出。
示例性地，在同一个总数据报内出现多条消息时，从第2条消息开始，S取值必须为0。否则，包含S＝1的消息在内的剩余数据被忽略。
在可能的实现方式中，源地址字段按照32位小端字节序编码，源地址字段包括4个字节。
需要说明的是，在同一个网络内，一般不会出现不同设备使用同一个地址的情况。在可能的实现方式中，源地址和目的地址由云服务器分配或网关代替云服务器(BLE、BLE Mesh)分配。
事务标志位34，用于指示数据报文中是否包含事务字段341，事务字段341用于指示事务以及用于跟踪事务的处理过程。
示例性地，当T的值为0时，表明当前不使用事务功能，数据报文中不存在事务字段。此时，消息既不是主动事务，也不是被动事务，仅用于通知。消息必须不按照一般事务消息来处理。
当T的值为1时，表明当前使用事务功能，数据报文中存在事务字段。
在可能的实现方式中，事务字段(可以表示为Transaction(事务))包括4个字节。
在本申请实施例中，通过事务标志位实现事务消息的收发，当数据报文中包括事务字段时，表明该消息是事务消息，此时的消息处理按照事务的流程进行处理；否则按照非事务消息处理。
在可能的实现方式中，事务字段包括32位比特，32位比特中的低31位比特用于表示事务的标识，32位比特中的最高位比特用于表示事务的操作方类型。
示例性地，低31位比特包括第1、2、3字节以及第4个字节的低7位，事务的标识也可以称之为事务唯一标识符(Transaction ID(Identification，身份))。最高位比特为第4个字节的最高位。最高位比特用于表示主动标记或被动标记，事务的主动开始方发送消息时，最高位比特可以设置为1，此时最高位比特用于表示主动标记；事务的被动开始方发送消息时，最高位比特可以设置为0，此时最高位比特用于表示被动标记。
除了与云服务器建立的连接外，底层首次建立连接时，低31位比特全为0。与云服务器 建立的连接，需要预留256个事务字段，用于处理隐式功能，因此，首次建立连接时，低31位比特为256，云服务器必须避免使用0～255共256个事务字段。当不是首次建立连接时，每主动发起新的事务，低31位比特自增1。需要说明的是，2147483647(2^31-1)为无效标识，事务的标识增长到该值或收到标识为该值的消息时，应主动清理事务并终止连接。
当主动开始方发起一个事务时，若使用标识为0x00000001，则事务字段为0x010x000x000x80。当被动开始方向主动开始方发送事务相关消息时，翻转最高位比特，事务字段为0x010x000x000x00。
在可能的实现方式中，长度字段、源地址字段、目的地址字段和事务字段的传输时序与长度标志位、源地址标志位、目的地址标志位和事务标志位的排列顺序一致，上述标志位的顺序是可以调整的。
可以理解的，一条消息主要由源地址(也可以称之为来源设备地址、发送设备地址)、目的地址(也可以称之为目的地设备地址)、事务相关消息、消息类型、消息内容等组成。域网络层用于将从安全传输层收到的数据进行处理和分发，将数据报文转发至其它设备或者交给本设备的模型控制层处理。设备地址是一个32位的数，是设备的身份标识，设备地址0(0x00000000)表示不指定身份标识或没有身份标识。发送来源是指首个发出消息的设备，发送目的地(也可以称之为目的地设备)是指最终接收并处理消息的设备。事务指完整处理一件事情的这个过程，例如“读取设备的某个状态的整个读取过程”、“将设备的某个状态更改为另外一个状态的整个处理过程”、“监听设备某个状态值的变化的整个监听过程”、“向设备发送一个文件的整个发送过程”等等。
域网络层消息在传输过程中允许被拼合，根据更底层协议类型，有如下两种拼合的情况：更底层为不可区分消息边界的流式数据传输协议(如TLS(Transport Layer Security，安全传输层协议))，域网络层消息将被更底层直接拼合；更底层为可区分消息边界的数据报传输协议(如DTLS、BLE、UDP)，域网络层消息允许拼合但不允许跨越数据报边界，此时一个总数据报内可能存在多个域网络层消息。在可能的实现过程中，在同一个总数据报内的多个消息的发送者与接收者可能完全相同。
本申请实施例通过标志位，可以灵活地对数据报文进行动态组装，高效和灵活的进行网络数据收发，并能动态的扩展到各个业务场景中使用。数据报文中定义了消息的发送设备地址和目的地设备地址，可以实现点对点数据收发，也可以支持通过中间路由进行数据收发。
本申请实施例对事务消息进行了明确的定义，本申请可以通过消息类型的灵活定义对消息进行扩展，大大提高了消息表达的灵活性。
在示意性实施例中，如图4所示，数据报文中还包括第一扩展选项字段41和第一扩展选项字段41对应的有效载荷42。
在可能的实现方式中，第一扩展选项字段41包括1个字节，有效载荷42包括4个字节。
在可能的实现方式中，有效载荷42的数据格式为序列化结构数据格式。
示例性地，有效载荷的数据格式为protobuf(google protocol buffer，谷歌协议缓冲)。有效载荷可以表示为Payload，Payload使用protobuf进行数据表示，使得数据报文的内容表达效率更高，再结合标志位灵活地对消息进行动态组装，以及使用二进制格式定义数据报文，本申请实施例可以在wifi、BLE(Bluetooth Low Energy，低功耗蓝牙)等各种带宽的数据通道上统一传输，数据报文的使用更加灵活。
在可能的实现方式中，有效载荷42中包括第一扩展选项字段41对应的扩展字段411、第二扩展选项字段43以及第二扩展选项字段43对应的扩展字段431。
在可能的实现方式中，第二扩展选项字段包括1个字节，第二扩展选项字段对应的扩展字段包括2个字节，第一扩展选项字段对应的扩展字段包括1个字节。
在可能的实现方式中，第一扩展选项字段表示为Type，Payload为扩展内容，Type指示Payload类型，消息通过Type进行扩展。第二扩展选项字段表示为next type。本申请实施例 通过Type的字段内容进行消息扩展。在扩展内容之后，再跟另一个扩展或更高层消息的有效载荷，从而实现灵活的消息扩展。
在可能的实现方式中，在数据报文中可以添加事务超时时间(Option Transaction Timeout)的写入属性值消息，此时，第一扩展选项字段的字段内容为0x80，第一扩展选项字段对应的扩展字段的字段内容为10，第二扩展选项字段的字段内容为7，第二扩展选项字段对应的扩展字段的字段内容为PropertiesWriteReq，PropertiesWriteReq为一种协议属性。
在可能的实现方式中，有效载荷的第一个字节是第二扩展选项字段、第二个字节是第一扩展选项字段对应的扩展字段，第三和第四个字节是第二扩展选项字段对应的扩展字段。
通过消息扩展，可以灵活地进行业务扩展，本申请实施例特别适合于IoT场景的通讯。
在示意性实施例中，如图5所示，数据报文还包括版本号字段51，版本号字段51用于指示数据报文的当前版本。
示例性地，版本号字段可以表示为Ver(Version，版本)，不同版本对应的版本号字段不同，也即不同版本对应的版本号字段的字段内容不同。
在可能的实现方式中，Ver采用大端位序，版本号字段包括2位比特，例如，00用于指示数据报文的当前版本为第一版本，01用于指示数据报文的当前版本为第二版本，10用于指示数据报文的当前版本为第三版本，11用于指示数据报文的当前版本为第四版本。当当前版本升级时，数据报文中的字段可以重新定义，扩展为一份新的数据报文。
当然，在可能的实现方式中，版本号字段还可以包括3位甚至更多位比特，本申请实施例对此不作限定。
在示意性实施例中，如图5所示，数据报文还包括协议扩展字段52，协议扩展字段52用于指示与数据报文相关的扩展功能。
协议扩展字段可以包括2位比特。例如，当协议扩展字段为01时，表明Payload中的数据为AES(Advanced Encryption Standard，高级加密标准)加密。
消息头可以包括版本号字段、协议扩展字段、标志位、第一扩展选项字段。当然，在可能的实现方式中，消息头还可以包括长度字段、源地址字段、目的地址字段和事务字段。
请参考图6，其示出了本申请一个实施例提供的数据报文处理方法的流程图。该方法可以由第二设备或第三设备执行，例如第二设备可以是图1所示实施环境中的第二设备20，第三设备可以是图1所示实施环境中的第三设备30。该方法可以包括如下几个子步骤(601～603)：
步骤601，接收数据报文。
步骤602，读取数据报文中包括的n个标志位。
其中，n个标志位中的第i个标志位，用于指示数据报文中是否包含预定义的n个字段中的与该第i个标志位对应的字段，n为正整数。
n个标志位与n个字段一一对应，不同的字段对应有不同的标志位。在可能的实现方式中，通过标志位的值来确定数据报文中是否包含与该标志位对应的字段。标志位可以用1位比特表示，示例性地，标志位的值可以为0或1，当标志位的值为0时，表明数据报文中不包含与该标志位对应的字段；当标志位的值为1时，表明数据报文中包含与该标志位对应的字段。当然，在其它可能的实现方式中，标志位的值还可以是其它值，本申请实施例对此不作限定。
步骤603，基于n个标志位，解析数据报文中包括的m个字段，m为小于等于n的正整数。
与m个字段对应的标志位，用于指示数据报文中包含上述m个字段。示例性地，第二设备或第三设备解析值为1的标志位对应的字段。
当然，在可能的实现方式中，第二设备可以根据需要仅解析数据报文中包括的部分字段，而不必解析数据报文中包括的所有字段。
综上所述，本申请实施例提供的技术方案中，通过在数据报文中设置标志位，标志位用于指示数据报文中是否包含该标志位对应的字段，标志位与预定义的字段相对应，本申请实施例可以通过标志位对数据报文进行灵活地动态组装，从而改变数据报文的传输量，使得数据报文可以在不同的数据通道上进行传输，增强了数据报文的通用性。
在示意性实施例中，n个标志位包括以下至少一项：
长度标志位，用于指示数据报文中是否包含长度字段，长度字段用于指示数据报文的长度。
目的地址标志位，用于指示数据报文中是否包含目的地址字段，目的地址字段用于指示数据报文的目的地设备地址。
源地址标志位，用于指示数据报文中是否包含源地址字段，源地址字段用于指示数据报文的发送设备地址。
事务标志位，用于指示数据报文中是否包含事务字段，事务字段用于指示事务以及用于跟踪事务的处理过程。
在可能的实现方式中，事务字段包括32位比特，32位比特中的低31位比特用于表示事务的标识，32位比特中的最高位比特用于表示事务的操作方类型。
在示意性实施例中，接收设备(也可以称之为数据报文处理设备)需要确定数据报文是否为待转发数据报文，也即接收设备需要确定自己是第二设备还是第三设备，当接收设备确定数据报文是待转发数据报文时，接收设备为第二设备；当接收设备确定数据报文不是待转发数据报文时，接收设备为第三设备。
若数据报文是待转发数据报文，标志位包括源地址标志位，且源地址标志位用于指示数据报文中不包含源地址字段，则将数据报文的发送设备地址确定为源地址字段的字段内容添加至数据报文中。
通过源地址字段和目的地址字段可以实现点对点数据收发，也可以实现消息路由转发，消息转发可以通过网桥进行消息转发。第二设备转发的过程如下：1、从数据报文中确定目的地址字段的字段内容；2、检查该目的地址字段的字段内容对应的目的地设备地址是否可以直接连通；3、若该目的地设备地址可以直接连通，则将该数据报文转发给第三设备；4、若该目的地设备地址不可以直接连通，则拒绝转发；5、若数据报文中包括的源地址标志位用于指示该数据报文中不包含源地址字段，则第二设备需要重写消息头(即，数据报文的报头)，将数据报文的发送设备地址确定为源地址字段的字段内容添加至数据报文中；6、将调整后的数据报文发送给第三设备。
在可能的实现方式中，消息转发最多进行一次。消息转发有如下规定：第二设备必须能够直接与第三设备相连通，不能转发消息到另一第二设备。第二设备不能将消息转发回收到消息的原连接上。
在可能的实现方式中，接收设备通过如下方式确定数据报文是否为待转发数据报文：
1、确定数据报文中是否包含目的地设备地址；若数据报文中包含目的地设备地址，则执行下述步骤2；若数据报文中不包含目的地设备地址，则执行下述步骤3。
2、将目的地设备地址与接收设备地址进行对比；若目的地设备地址与接收设备地址相同，则执行下述步骤3；若目的地设备地址与接收设备地址不同，则执行下述步骤4。
接收设备地址是指当前接收设备的地址，也即，当前接收到数据报文的设备的地址。目的地设备地址是最终接收数据报文的设备的地址。
3、确定数据报文不是待转发数据报文。
4、确定数据报文是待转发数据报文。
接收设备接收到数据报文后，读取目的地址标志位，若目的地址标志位的值为0，则表明数据报文不是待转发数据报文；若目的地址标志位的值为1，则接收设备再将目的地设备地址与接收设备地址进行对比。若目的地设备地址与接收设备地址一致，则数据报文不是待 转发数据报文，接收设备是第三设备；若目的地设备地址与接收设备地址不一致，则数据报文是待转发数据报文，接收设备是第二设备。
在示意性实施例中，数据报文中还包括第一扩展选项字段和第一扩展选项字段对应的有效载荷。
可以理解的，第一扩展选项字段可以表示为Type。示例性的，事务消息的处理过程如下：1、确定Type是否为预留值(预留值指的是模型控制层中的值)；若Type是预留值，则忽略消息，处理过程结束；若Type不是预留值，则继续下述流程。2、根据事务字段查找当前连接上正在进行的事务列表。若能够匹配到已存在的事务(包括主动标记或被动标记)，则分发至目前已存在的事务进行处理，处理过程结束；若无法找到对应事务，则继续下述流程。3、根据事务字段判断主动事务或被动事务，对于被动事务，应答错误(code＝ESRCH(线程不存在))，处理过程结束；对于主动事务，则继续流程。4、根据事务字段判断是否被标记为已结束，若事务被标记为已结束，则应答(code＝EFINISHED(Error Finished，完成结束))，处理过程结束；若事务未被标记为已结束，则继续下述流程。5、将消息交给模型控制层处理。
非事务消息处理可以被用于蓝牙Beacon等广播消息。
在示意性实施例中，有效载荷的数据格式为序列化结构数据格式。
在示意性实施例中，有效载荷中包括第一扩展选项字段对应的扩展字段、第二扩展选项字段以及第二扩展选项字段对应的扩展字段。
在示意性实施例中，数据报文还包括版本号字段，版本号字段用于指示数据报文的当前版本。
在示意性实施例中，数据报文还包括协议扩展字段，协议扩展字段用于指示与数据报文相关的扩展功能。
有关数据报文的介绍说明可参见上文实施例，此处不再赘述。
需要说明的是，本申请实施例中的发送设备也可以称之为发送方或发送者；本申请实施例中的接收设备也可以称之为接收方或接收者。因此，发送设备地址也可以称之为发送方地址或发送者地址，接收设备地址也可以称之为接收方地址或接收者地址，本申请实施例对此不作限定。
下面，通过几个应用场景对本申请实施例进行介绍说明。
场景1：控制设备(第一设备)在TCP通道下对子设备(第三设备)写属性(例如开灯)的操作，由于控制设备对子设备的控制需要通过网关(第二设备)中转，所以数据报文中需要包括源地址字段和目的地址字段，数据报文的格式如图7所示。第一扩展选项字段的字段内容为0x07，有效载荷的字段内容为Set Properties Request msg(设置属性请求消息)。
场景2：控制设备(第一设备)在蓝牙GATT(Generic Attribute Profile，通用属性配置文件)或UDP通道下对子设备(第三设备)写属性(如开灯)的操作，此时的数据报文不需要包括长度字段，数据报文的格式如图8所示。第一扩展选项字段的字段内容为0x07，有效载荷的字段内容为Set Properties Request msg(设置属性请求消息)。
场景3：控制设备(第一设备)在蓝牙GATT或UDP通道下点对点对子设备(第三设备)写属性(如开灯)的操作，此时数据报文不需要包括长度字段、源地址字段和目的地址字段，数据报文的格式如图9所示。第一扩展选项字段的字段内容为0x07，有效载荷的字段内容为Set Properties Request msg(设置属性请求消息)。
场景4：云端(第一设备)通过UDP通道向子设备(第三设备)下发通知，如更换家庭通知，此时数据报文不需要包括长度字段、源地址字段、目的地址字段和事务字段，数据报文的格式如图10所示。第一扩展选项字段的字段内容为0x38，有效载荷的字段内容为Home Change Notify msg(更换家庭通知)。
在示意性实施例中，本申请实施例还提供了一种用于设备间传输的数据报文，该数据报文用于在设备间进行数据传输时装载信息，该数据报文中包括预定义的n个字段中的m个字 段，n为正整数，且m为小于等于n的正整数。
数据报文还包括n个标志位，n个标志位中的第i个标志位，用于指示数据报文中是否包含n个字段中的与第i个标志位对应的字段。
结合参考图3至图5，在可能的实现方式中，n个标志位包括以下至少一项：长度标志位，用于指示数据报文中是否包含长度字段，长度字段用于指示数据报文的长度；目的地址标志位，用于指示数据报文中是否包含目的地址字段，目的地址字段用于指示数据报文的目的地设备地址；源地址标志位，用于指示数据报文中是否包含源地址字段，源地址字段用于指示数据报文的发送设备地址；事务标志位，用于指示数据报文中是否包含事务字段，事务字段用于指示事务以及用于跟踪事务的处理过程。
在可能的实现方式中，数据报文中还包括第一扩展选项字段和第一扩展选项字段对应的有效载荷。
在可能的实现方式中，数据报文还包括协议扩展字段，协议扩展字段用于指示与数据报文相关的扩展功能。在可能的实现方式中，有效载荷的数据格式为序列化结构数据格式。
在可能的实现方式中，有效载荷中包括第一扩展选项字段对应的扩展字段、第二扩展选项字段以及第二扩展选项字段对应的扩展字段。
在可能的实现方式中，数据报文中还包括版本号字段，版本号字段用于指示数据报文的当前版本。
需要说明的是，在可能的实现方式中，数据报文中可以同时包括n个标志位、第一扩展选项字段、第一扩展选项字段对应的有效载荷、协议扩展字段。当然，数据报文可以根据实际应用的需要包括上面的部分或全部字段。
有关数据报文的相关介绍说明可参见上文实施例，此处不再赘述。
下述为本申请装置实施例，可以用于执行本申请方法实施例。对于本申请装置实施例中未披露的细节，请参照本申请方法实施例。
请参考图11，其示出了本申请一个实施例提供的数据报文发送装置的框图，该装置具有实现上述方法示例的功能，所述功能可以由硬件实现，也可以由硬件执行相应的软件实现。该装置1100可以包括：字段确定模块1110、报文生成模块1120和报文发送模块1130。
字段确定模块1110，用于从预定义的n个字段中，确定数据报文中包括的m个字段，所述n为正整数，且所述m为小于等于所述n的正整数。
报文生成模块1120，用于生成包括所述m个字段的所述数据报文；其中，所述数据报文中还包括n个标志位，所述n个标志位中的第i个标志位，用于指示所述数据报文中是否包含所述n个字段中的与所述第i个标志位对应的字段。
报文发送模块1130，用于发送所述数据报文。
综上所述，本申请实施例提供的技术方案中，通过在数据报文中设置标志位，标志位用于指示数据报文中是否包含该标志位对应的字段，标志位与预定义的字段相对应，本申请实施例可以通过标志位对数据报文进行灵活地动态组装，从而改变数据报文的传输量，使得数据报文可以在不同的数据通道上进行传输，增强了数据报文的通用性。
在示意性实施例中，所述n个标志位包括以下至少一项：
长度标志位，用于指示所述数据报文中是否包含长度字段，所述长度字段用于指示所述数据报文的长度；
目的地址标志位，用于指示所述数据报文中是否包含目的地址字段，所述目的地址字段用于指示所述数据报文的目的地设备地址；
源地址标志位，用于指示所述数据报文中是否包含源地址字段，所述源地址字段用于指示所述数据报文的发送设备地址；
事务标志位，用于指示所述数据报文中是否包含事务字段，所述事务字段用于指示事务以及用于跟踪所述事务的处理过程。
在示意性实施例中，所述事务字段包括32位比特，所述32位比特中的低31位比特用于表示所述事务的标识，所述32位比特中的最高位比特用于表示所述事务的操作方类型。
在示意性实施例中，所述数据报文中还包括第一扩展选项字段和所述第一扩展选项字段对应的有效载荷。
在示意性实施例中，所述有效载荷的数据格式为序列化结构数据格式。
在示意性实施例中，所述有效载荷中包括所述第一扩展选项字段对应的扩展字段、第二扩展选项字段以及所述第二扩展选项字段对应的扩展字段。
在示意性实施例中，所述数据报文还包括协议扩展字段，所述协议扩展字段用于指示与所述数据报文相关的扩展功能。
请参考图12，其示出了本申请一个实施例提供的数据报文处理装置的框图，该装置具有实现上述方法示例的功能，所述功能可以由硬件实现，也可以由硬件执行相应的软件实现。该装置1200可以包括：报文接收模块1210、标志位读取模块1220和字段解析模块1230。
报文接收模块1210，用于接收数据报文。
标志位读取模块1220，用于读取所述数据报文中包括的n个标志位；其中，所述n个标志位中的第i个标志位，用于指示所述数据报文中是否包含预定义的n个字段中的与所述第i个标志位对应的字段，所述n为正整数。
字段解析模块1230，用于基于所述n个标志位，解析所述数据报文中包括的m个字段，所述m为小于等于所述n的正整数。
综上所述，本申请实施例提供的技术方案中，通过在数据报文中设置标志位，标志位用于指示数据报文中是否包含该标志位对应的字段，标志位与预定义的字段相对应，本申请实施例可以通过标志位对数据报文进行灵活地动态组装，从而改变数据报文的传输量，使得数据报文可以在不同的数据通道上进行传输，增强了数据报文的通用性。
在示意性实施例中，所述n个标志位包括以下至少一项：
长度标志位，用于指示所述数据报文中是否包含长度字段，所述长度字段用于指示所述数据报文的长度；
目的地址标志位，用于指示所述数据报文中是否包含目的地址字段，所述目的地址字段用于指示所述数据报文的目的地设备地址；
源地址标志位，用于指示所述数据报文中是否包含源地址字段，所述源地址字段用于指示所述数据报文的发送设备地址；
事务标志位，用于指示所述数据报文中是否包含事务字段，所述事务字段用于指示事务以及用于跟踪所述事务的处理过程。
在示意性实施例中，所述事务字段包括32位比特，所述32位比特中的低31位比特用于表示所述事务的标识，所述32位比特中的最高位比特用于表示所述事务的操作方类型。
在示意性实施例中，所述装置1200，还包括：报文确定模块和字段添加模块(图中未示出)。
所述报文确定模块，用于确定所述数据报文是否为待转发数据报文；
所述字段添加模块，用于若所述数据报文是所述待转发数据报文，所述标志位包括所述源地址标志位，且所述源地址标志位用于指示所述数据报文中不包含所述源地址字段，则将所述数据报文的发送设备地址确定为所述源地址字段的字段内容添加至所述数据报文中。
在示意性实施例中，所述报文确定模块，用于：
响应于所述数据报文中包含所述目的地设备地址，将所述目的地设备地址与接收设备地址进行对比；
若所述目的地设备地址与所述接收设备地址相同，则确定所述数据报文不是所述待转发数据报文；
若所述目的地设备地址与所述接收设备地址不同，则确定所述数据报文是所述待转发数 据报文；
响应于所述数据报文中不包含所述目的地设备地址，确定所述数据报文不是所述待转发数据报文。
在示意性实施例中，所述数据报文中还包括第一扩展选项字段和所述第一扩展选项字段对应的有效载荷。
在示意性实施例中，所述有效载荷的数据格式为序列化结构数据格式。
在示意性实施例中，所述有效载荷中包括所述第一扩展选项字段对应的扩展字段、第二扩展选项字段以及所述第二扩展选项字段对应的扩展字段。
在示意性实施例中，所述数据报文还包括协议扩展字段，所述协议扩展字段用于指示与所述数据报文相关的扩展功能。
需要说明的是，上述实施例提供的装置在实现其功能时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将设备的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的装置与方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
请参考图13，其示出了本申请一个实施例提供的数据报文发送设备1300的结构示意图，该数据报文发送设备1300可以包括：处理器1301、接收器1302、发射器1303、存储器1304和总线1305。
处理器1301包括一个或者一个以上处理核心，处理器1301通过运行软件程序以及模块，从而执行各种功能应用以及信息处理。
接收器1302和发射器1303可以实现为一个通信组件，该通信组件可以是一块通信芯片。
存储器1304通过总线1305与处理器1301相连。
存储器1304可用于存储计算机程序，处理器1301用于执行该计算机程序，以实现上述方法实施例中的数据报文发送设备执行的各个步骤。
此外，存储器1304可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，易失性或非易失性存储设备包括但不限于：磁盘或光盘，电可擦除可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)，可擦除可编程只读存储器(Erasable Programmable Read-Only Memory，EPROM)，静态随时存取存储器(Static Random Access Memory，SRAM)，只读存储器(Read-Only Memory，ROM)，磁存储器，快闪存储器，可编程只读存储器(Programmable Read Only Memory，PROM)。
在示意性实施例中，所述数据报文发送设备包括处理器、存储器和收发器，该收发器可以包括接收器和发射器，接收器用于接收信息，发射器用于发送信息。
所述处理器，用于从预定义的n个字段中，确定数据报文中包括的m个字段，所述n为正整数，且所述m为小于等于所述n的正整数；
所述处理器，还用于生成包括所述m个字段的所述数据报文；其中，所述数据报文中还包括n个标志位，所述n个标志位中的第i个标志位，用于指示所述数据报文中是否包含所述n个字段中的与所述第i个标志位对应的字段；
所述收发器，还用于发送所述数据报文。
在示意性实施例中，所述n个标志位包括以下至少一项：
长度标志位，用于指示所述数据报文中是否包含长度字段，所述长度字段用于指示所述数据报文的长度；
目的地址标志位，用于指示所述数据报文中是否包含目的地址字段，所述目的地址字段用于指示所述数据报文的目的地设备地址；
源地址标志位，用于指示所述数据报文中是否包含源地址字段，所述源地址字段用于指示所述数据报文的发送设备地址；
事务标志位，用于指示所述数据报文中是否包含事务字段，所述事务字段用于指示事务以及用于跟踪所述事务的处理过程。
在示意性实施例中，所述事务字段包括32位比特，所述32位比特中的低31位比特用于表示所述事务的标识，所述32位比特中的最高位比特用于表示所述事务的操作方类型。
在示意性实施例中，所述数据报文中还包括第一扩展选项字段和所述第一扩展选项字段对应的有效载荷。
在示意性实施例中，所述有效载荷的数据格式为序列化结构数据格式。
在示意性实施例中，所述有效载荷中包括所述第一扩展选项字段对应的扩展字段、第二扩展选项字段以及所述第二扩展选项字段对应的扩展字段。
在示意性实施例中，所述数据报文还包括协议扩展字段，所述协议扩展字段用于指示与所述数据报文相关的扩展功能。
请参考图14，其示出了本申请一个实施例提供的数据报文处理设备1400的结构示意图，该数据报文处理1400可以包括：处理器1401、接收器1402、发射器1403、存储器1404和总线1405。
处理器1401包括一个或者一个以上处理核心，处理器1401通过运行软件程序以及模块，从而执行各种功能应用以及信息处理。
接收器1402和发射器1403可以实现为一个通信组件，该通信组件可以是一块通信芯片。
存储器1404通过总线1405与处理器1401相连。
存储器1404可用于存储计算机程序，处理器1401用于执行该计算机程序，以实现上述方法实施例中的数据报文处理设备执行的各个步骤。
此外，存储器1404可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，易失性或非易失性存储设备包括但不限于：磁盘或光盘，电可擦除可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)，可擦除可编程只读存储器(Erasable Programmable Read-Only Memory，EPROM)，静态随时存取存储器(Static Random Access Memory，SRAM)，只读存储器(Read-Only Memory，ROM)，磁存储器，快闪存储器，可编程只读存储器(Programmable Read Only Memory，PROM)。
在示意性实施例中，所述数据报文处理包括处理器、存储器和收发器，该收发器可以包括接收器和发射器，接收器用于接收信息，发射器用于发送信息。
所述收发器，用于接收数据报文；
所述处理器，用于读取所述数据报文中包括的n个标志位；其中，所述n个标志位中的第i个标志位，用于指示所述数据报文中是否包含预定义的n个字段中的与所述第i个标志位对应的字段，所述n为正整数；
所述处理器，还用于基于所述n个标志位，解析所述数据报文中包括的m个字段，所述m为小于等于所述n的正整数。
在示意性实施例中，所述n个标志位包括以下至少一项：
长度标志位，用于指示所述数据报文中是否包含长度字段，所述长度字段用于指示所述数据报文的长度；
目的地址标志位，用于指示所述数据报文中是否包含目的地址字段，所述目的地址字段用于指示所述数据报文的目的地设备地址；
源地址标志位，用于指示所述数据报文中是否包含源地址字段，所述源地址字段用于指示所述数据报文的发送设备地址；
事务标志位，用于指示所述数据报文中是否包含事务字段，所述事务字段用于指示事务以及用于跟踪所述事务的处理过程。
在示意性实施例中，所述事务字段包括32位比特，所述32位比特中的低31位比特用于表示所述事务的标识，所述32位比特中的最高位比特用于表示所述事务的操作方类型。
在示意性实施例中，所述处理器，还用于确定所述数据报文是否为待转发数据报文；
所述处理器，还用于若所述数据报文是所述待转发数据报文，所述标志位包括所述源地址标志位，且所述源地址标志位用于指示所述数据报文中不包含所述源地址字段，则将所述数据报文的发送设备地址确定为所述源地址字段的字段内容添加至所述数据报文中。
在示意性实施例中，所述处理器，还用于响应于所述数据报文中包含所述目的地设备地址，将所述目的地设备地址与接收设备地址进行对比；
所述处理器，还用于若所述目的地设备地址与所述接收设备地址相同，则确定所述数据报文不是所述待转发数据报文；
所述处理器，还用于若所述目的地设备地址与所述接收设备地址不同，则确定所述数据报文是所述待转发数据报文；
所述处理器，还用于响应于所述数据报文中不包含所述目的地设备地址，确定所述数据报文不是所述待转发数据报文。
在示意性实施例中，所述数据报文中还包括第一扩展选项字段和所述第一扩展选项字段对应的有效载荷。
在示意性实施例中，所述有效载荷的数据格式为序列化结构数据格式。
在示意性实施例中，所述有效载荷中包括所述第一扩展选项字段对应的扩展字段、第二扩展选项字段以及所述第二扩展选项字段对应的扩展字段。
在示意性实施例中，所述数据报文还包括协议扩展字段，所述协议扩展字段用于指示与所述数据报文相关的扩展功能。
在示例性实施例中，还提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，所述计算机程序由数据报文发送设备的处理器加载并执行以实现上述数据报文发送方法实施例中的各个步骤。
在示例性实施例中，还提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，所述计算机程序由数据报文处理设备的处理器加载并执行以实现上述数据报文处理方法实施例中的各个步骤。
在示例性实施例中，提供了一种计算机程序产品，该计算机程序产品包括计算机指令，该计算机指令存储在计算机可读存储介质中。数据报文发送设备的处理器从计算机可读存储介质读取该计算机指令，处理器执行该计算机指令，使得该数据报文发送设备执行上述方面中提供的数据报文发送方法。
在示例性实施例中，提供了一种计算机程序产品，该计算机程序产品包括计算机指令，该计算机指令存储在计算机可读存储介质中。数据报文处理设备的处理器从计算机可读存储介质读取该计算机指令，处理器执行该计算机指令，使得该数据报文处理设备执行上述方面中提供的数据报文处理方法。
应当理解的是，在本文中提及的“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。“多个”是指两个或两个以上。在本文中提及的“小于等于”可以理解为小于或等于。
以上所述仅为本申请的示例性实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (24)

  1. 一种数据报文发送方法，其特征在于，所述方法包括：
    从预定义的n个字段中，确定数据报文中包括的m个字段，所述n为正整数，且所述m为小于等于所述n的正整数；
    生成包括所述m个字段的所述数据报文；其中，所述数据报文中还包括n个标志位，所述n个标志位中的第i个标志位，用于指示所述数据报文中是否包含所述n个字段中的与所述第i个标志位对应的字段；
    发送所述数据报文。
  2. 根据权利要求1所述的方法，其特征在于，所述n个标志位包括以下至少一项：
    长度标志位，用于指示所述数据报文中是否包含长度字段，所述长度字段用于指示所述数据报文的长度；
    目的地址标志位，用于指示所述数据报文中是否包含目的地址字段，所述目的地址字段用于指示所述数据报文的目的地设备地址；
    源地址标志位，用于指示所述数据报文中是否包含源地址字段，所述源地址字段用于指示所述数据报文的发送设备地址；
    事务标志位，用于指示所述数据报文中是否包含事务字段，所述事务字段用于指示事务以及用于跟踪所述事务的处理过程。
  3. 根据权利要求2所述的方法，其特征在于，所述事务字段包括32位比特，所述32位比特中的低31位比特用于表示所述事务的标识，所述32位比特中的最高位比特用于表示所述事务的操作方类型。
  4. 根据权利要求1所述的方法，其特征在于，所述数据报文中还包括第一扩展选项字段和所述第一扩展选项字段对应的有效载荷。
  5. 根据权利要求4所述的方法，其特征在于，所述有效载荷的数据格式为序列化结构数据格式。
  6. 根据权利要求4所述的方法，其特征在于，所述有效载荷中包括所述第一扩展选项字段对应的扩展字段、第二扩展选项字段以及所述第二扩展选项字段对应的扩展字段。
  7. 根据权利要求1至6任一项所述的方法，其特征在于，所述数据报文还包括协议扩展字段，所述协议扩展字段用于指示与所述数据报文相关的扩展功能。
  8. 一种数据报文处理方法，其特征在于，所述方法包括：
    接收数据报文；
    读取所述数据报文中包括的n个标志位；其中，所述n个标志位中的第i个标志位，用于指示所述数据报文中是否包含预定义的n个字段中的与所述第i个标志位对应的字段，所述n为正整数；
    基于所述n个标志位，解析所述数据报文中包括的m个字段，所述m为小于等于所述n的正整数。
  9. 根据权利要求8所述的方法，其特征在于，所述n个标志位包括以下至少一项：
    长度标志位，用于指示所述数据报文中是否包含长度字段，所述长度字段用于指示所述数据报文的长度；
    目的地址标志位，用于指示所述数据报文中是否包含目的地址字段，所述目的地址字段用于指示所述数据报文的目的地设备地址；
    源地址标志位，用于指示所述数据报文中是否包含源地址字段，所述源地址字段用于指示所述数据报文的发送设备地址；
    事务标志位，用于指示所述数据报文中是否包含事务字段，所述事务字段用于指示事务以及用于跟踪所述事务的处理过程。
  10. 根据权利要求9所述的方法，其特征在于，所述事务字段包括32位比特，所述32位比特中的低31位比特用于表示所述事务的标识，所述32位比特中的最高位比特用于表示所述事务的操作方类型。
  11. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    确定所述数据报文是否为待转发数据报文；
    若所述数据报文是所述待转发数据报文，所述标志位包括所述源地址标志位，且所述源地址标志位用于指示所述数据报文中不包含所述源地址字段，则将所述数据报文的发送设备地址确定为所述源地址字段的字段内容添加至所述数据报文中。
  12. 根据权利要求11所述的方法，其特征在于，所述确定所述数据报文是否为待转发数据报文，包括：
    响应于所述数据报文中包含所述目的地设备地址，将所述目的地设备地址与接收设备地址进行对比；
    若所述目的地设备地址与所述接收设备地址相同，则确定所述数据报文不是所述待转发数据报文；
    若所述目的地设备地址与所述接收设备地址不同，则确定所述数据报文是所述待转发数据报文；
    响应于所述数据报文中不包含所述目的地设备地址，确定所述数据报文不是所述待转发数据报文。
  13. 根据权利要求8所述的方法，其特征在于，所述数据报文中还包括第一扩展选项字段和所述第一扩展选项字段对应的有效载荷。
  14. 根据权利要求13所述的方法，其特征在于，所述有效载荷的数据格式为序列化结构数据格式。
  15. 根据权利要求13所述的方法，其特征在于，所述有效载荷中包括所述第一扩展选项字段对应的扩展字段、第二扩展选项字段以及所述第二扩展选项字段对应的扩展字段。
  16. 根据权利要求8至15任一项所述的方法，其特征在于，所述数据报文还包括协议扩展字段，所述协议扩展字段用于指示与所述数据报文相关的扩展功能。
  17. 一种数据报文发送装置，其特征在于，所述装置包括：
    字段确定模块，用于从预定义的n个字段中，确定数据报文中包括的m个字段，所述n为正整数，且所述m为小于等于所述n的正整数；
    报文生成模块，用于生成包括所述m个字段的所述数据报文；其中，所述数据报文中还包括n个标志位，所述n个标志位中的第i个标志位，用于指示所述数据报文中是否包含所述n个字段中的与所述第i个标志位对应的字段；
    报文发送模块，用于发送所述数据报文。
  18. 一种数据报文处理装置，其特征在于，所述装置包括：
    报文接收模块，用于接收数据报文；
    标志位读取模块，用于读取所述数据报文中包括的n个标志位；其中，所述n个标志位中的第i个标志位，用于指示所述数据报文中是否包含预定义的n个字段中的与所述第i个标志位对应的字段，所述n为正整数；
    字段解析模块，用于基于所述n个标志位，解析所述数据报文中包括的m个字段，所述m为小于等于所述n的正整数。
  19. 一种数据报文发送设备，其特征在于，所述设备包括处理器、存储器和收发器；
    所述处理器，用于从预定义的n个字段中，确定数据报文中包括的m个字段，所述n为正整数，且所述m为小于等于所述n的正整数；
    所述处理器，还用于生成包括所述m个字段的所述数据报文；其中，所述数据报文中还包括n个标志位，所述n个标志位中的第i个标志位，用于指示所述数据报文中是否包含所 述n个字段中的与所述第i个标志位对应的字段；
    所述收发器，还用于发送所述数据报文。
  20. 一种数据报文处理设备，其特征在于，所述设备包括处理器、存储器和收发器；
    所述收发器，用于接收数据报文；
    所述处理器，用于读取所述数据报文中包括的n个标志位；其中，所述n个标志位中的第i个标志位，用于指示所述数据报文中是否包含预定义的n个字段中的与所述第i个标志位对应的字段，所述n为正整数；
    所述处理器，还用于基于所述n个标志位，解析所述数据报文中包括的m个字段，所述m为小于等于所述n的正整数。
  21. 一种用于设备间传输的数据报文，其特征在于，所述数据报文用于在设备间进行数据传输时装载信息，所述数据报文中包括预定义的n个字段中的m个字段，所述n为正整数，且所述m为小于等于所述n的正整数；
    所述数据报文还包括n个标志位，所述n个标志位中的第i个标志位，用于指示所述数据报文中是否包含所述n个字段中的与所述第i个标志位对应的字段。
  22. 根据权利要求21所述的数据报文，其特征在于，所述n个标志位包括以下至少一项：所述长度标志位，用于指示所述数据报文中是否包含长度字段，所述长度字段用于指示所述数据报文的长度；所述目的地址标志位，用于指示所述数据报文中是否包含目的地址字段，所述目的地址字段用于指示所述数据报文的目的地设备地址；所述源地址标志位，用于指示所述数据报文中是否包含源地址字段，所述源地址字段用于指示所述数据报文的发送设备地址；所述事务标志位，用于指示所述数据报文中是否包含事务字段，所述事务字段用于指示事务以及用于跟踪所述事务的处理过程；
    和/或，
    所述数据报文中还包括第一扩展选项字段和所述第一扩展选项字段对应的有效载荷；
    和/或，
    所述数据报文还包括协议扩展字段，所述协议扩展字段用于指示与所述数据报文相关的扩展功能；
    和/或，
    所述数据报文还包括版本号字段，所述版本号字段用于指示所述数据报文的当前版本。
  23. 根据权利要求22所述的数据报文，其特征在于，
    所述有效载荷的数据格式为序列化结构数据格式；
    和/或，
    所述有效载荷中包括所述第一扩展选项字段对应的扩展字段、第二扩展选项字段以及所述第二扩展选项字段对应的扩展字段。
  24. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机程序，所述计算机程序由处理器加载并执行以实现如权利要求1至7任一项所述的数据报文发送方法，或者实现如权利要求8至16任一项所述的数据报文处理方法。
PCT/CN2021/110451 2020-08-31 2021-08-04 数据报文发送方法、处理方法、装置、设备及数据报文 WO2022042235A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010901599.1 2020-08-31
CN202010901599.1A CN114125940A (zh) 2020-08-31 2020-08-31 数据报文发送方法、处理方法、装置、设备及数据报文

Publications (1)

Publication Number Publication Date
WO2022042235A1 true WO2022042235A1 (zh) 2022-03-03

Family

ID=80352634

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/110451 WO2022042235A1 (zh) 2020-08-31 2021-08-04 数据报文发送方法、处理方法、装置、设备及数据报文

Country Status (2)

Country Link
CN (1) CN114125940A (zh)
WO (1) WO2022042235A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114629972B (zh) * 2022-03-21 2024-03-22 中国科学院计算机网络信息中心 一种数据报文的处理方法及装置
CN114925386B (zh) * 2022-07-15 2022-10-25 飞腾信息技术有限公司 数据处理方法、计算机设备、数据处理系统及存储介质
CN116016752A (zh) * 2022-12-29 2023-04-25 联想(北京)有限公司 控制方法及电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150281050A1 (en) * 2014-03-31 2015-10-01 Alcatel-Lucent Usa Inc. Method for Adjacency Status Synchronization in Label Distribution Protocol
CN107707565A (zh) * 2017-11-07 2018-02-16 盛科网络（苏州）有限公司 一种udf报文解析芯片
CN108282461A (zh) * 2017-12-22 2018-07-13 中国电子科技集团公司第三十研究所 一种支持生物特征的eap协议改进方法
CN111740908A (zh) * 2019-03-25 2020-10-02 华为技术有限公司 通信方法及相关设备

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6473425B1 (en) * 1997-10-02 2002-10-29 Sun Microsystems, Inc. Mechanism for dispatching packets via a telecommunications network
CN102111233B (zh) * 2009-12-28 2014-03-26 华为软件技术有限公司 一种fec数据的处理方法及系统
CN104038450B (zh) * 2013-03-04 2017-09-19 华为技术有限公司 基于pcie总线的报文传输方法与装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150281050A1 (en) * 2014-03-31 2015-10-01 Alcatel-Lucent Usa Inc. Method for Adjacency Status Synchronization in Label Distribution Protocol
CN107707565A (zh) * 2017-11-07 2018-02-16 盛科网络（苏州）有限公司 一种udf报文解析芯片
CN108282461A (zh) * 2017-12-22 2018-07-13 中国电子科技集团公司第三十研究所 一种支持生物特征的eap协议改进方法
CN111740908A (zh) * 2019-03-25 2020-10-02 华为技术有限公司 通信方法及相关设备

Also Published As

Publication number Publication date
CN114125940A (zh) 2022-03-01

Similar Documents

Publication Publication Date Title
WO2022042235A1 (zh) 数据报文发送方法、处理方法、装置、设备及数据报文
WO2021000827A1 (zh) 数据传输链路建立方法、装置以及计算机可读存储介质
US9462089B1 (en) Communication channels
CN110022264B (zh) 控制网络拥塞的方法、接入设备和计算机可读存储介质
US20050216727A1 (en) Communication stack for network communication and routing
KR20070053367A (ko) 패킷 플로우에 따라 세션 서비스를 적용하는 시스템 및방법
TW201713093A (zh) 應用於伺服器負載均衡中的連接建立方法及裝置
US10880369B2 (en) Session persistence method, device, and storage medium
CN110505244B (zh) 远程隧道访问技术网关以及服务器
WO2021083284A1 (zh) 一种负载均衡方法、装置、介质和设备
WO2017148419A1 (zh) 数据传输方法及服务器
CN110417632B (zh) 一种网络通信方法、系统及服务器
US20190253393A1 (en) Multi-access interface for internet protocol security
WO2023103367A1 (zh) 数据传输方法及相关设备
CN114586326A (zh) 用于对媒体服务进行网络辅助的方法、核心网络节点、无线装置和无线电接入网络节点
CN105141603A (zh) 通信数据传输方法及系统
US8650313B2 (en) Endpoint discriminator in network transport protocol startup packets
US20200137153A1 (en) Method for establishing peer to peer service session over infrastructure link
WO2022100199A1 (zh) 数据传输方法、装置、介质、电子设备及网络接入设备
CN110771117B (zh) 一种采用面向id的网络的会话层通信
WO2021031092A1 (zh) 报文处理方法及网络设备
TW200807988A (en) Configuring a host device by way of MMP
KR102025375B1 (ko) 데이터 분산 서비스를 위한 장치 및 방법, 데이터 분산 서비스 시스템
CN112953953B (zh) 通讯协议设计方法、终端及计算机存储介质
WO2021232920A1 (zh) 数据传输方法、电子设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21860075

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21860075

Country of ref document: EP

Kind code of ref document: A1