Communication methods and communication devices

By sending indication information through IoT devices to indicate whether data segmentation is supported, the problem of IoT devices being unable to transmit data completely is solved, achieving efficient resource utilization and improving the success rate of data transmission.

CN123124103APending Publication Date: 2026-11-17HONOR DEVICE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510889219.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2025-05-15
Filing Date
2025-06-27
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

When IoT devices transmit data, they cannot transmit data in segments, which prevents readers from knowing the reason for the response failure, resulting in wasted resources and scheduling failures.

Method used

IoT devices send an initial indication to indicate whether data segmentation is supported. The reader adjusts its scheduling strategy based on the indication to ensure complete data transmission.

Benefits of technology

It reduces resource waste, lowers the probability of IoT device response failures, and improves the success rate of data transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123124103A_ABST
    Figure CN123124103A_ABST
Patent Text Reader

Abstract

This application discloses a communication method and a communication device, relating to the field of communication and applicable to Internet of Things (IoT) communication scenarios. The communication method includes: receiving a first message from a second device; the first message including first length information, which indicates the length of a scheduled second message; sending a second message to the second device according to the first length information, the second message including first indication information; the first indication information indicating whether the first device supports segmented data transmission, or indicating whether the first device supports segmented data transmission. This allows IoT devices to indicate whether they support segmented data transmission, reducing resource waste and lowering the probability of the first device failing to respond.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application claims priority to Chinese Patent Application No. 202510631749.4, filed on May 15, 2025, entitled "A Method and Apparatus for Information Reporting", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to a communication method and a communication device. Background Technology

[0003] In IoT communication systems, to improve the sustainability and performance of wireless communication and reduce its power consumption, low-power ambient internet of things (AIoT) technology has been introduced, including IoT devices and readers. A reader is responsible for communication between IoT devices and radio access network (RAN) equipment or between IoT devices and core network (CN) equipment. Readers can communicate with IoT devices, for example, when an IoT device sends data to a reader. Some IoT devices may not have the ability to segment data for transmission. When the data length scheduled by the reader is less than the data length required by the IoT device, the IoT device cannot send data, resulting in a response failure. The reader cannot determine the reason for the IoT device's response failure and therefore cannot improve scheduling accordingly, leading to repeated scheduling failures and wasted scheduling resources. Summary of the Invention

[0004] This application provides a communication method and a communication device for enabling IoT devices to indicate whether data segmentation is supported, thereby reducing resource waste.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0006] In a first aspect, a communication method is provided. This method can be executed by a first device, or by a component configured in the first device (such as a circuit, chip, or chip system), or by a logic module or software capable of implementing all or part of the functions of the first device. This application does not limit this approach. The following description uses the first device as an example.

[0007] The method includes: receiving a first message from a second device; the first message including first length information, the first length information being used to indicate the length of a scheduled second message; sending a second message to the second device according to the first length information, the second message including first indication information; the first indication information being used to indicate whether the first device supports segmented data transmission.

[0008] The communication method provided in this application embodiment involves a first device (e.g., an IoT device) sending a first indication message to a second device (e.g., a reader). The first indication message indicates whether the first device supports data segmentation transmission. The second device can then improve scheduling accordingly, thereby reducing resource waste and lowering the probability of the first device failing to respond.

[0009] In one possible implementation, the first indication information indicating that the first device does not support segmented data transmission means that: the second message includes fourth length information, and the fourth length information is greater than the third length information; the fourth length information is used to indicate the length of the data to be sent by the first device, and the third length information is equal to the first length information minus the length of the second message header.

[0010] In this embodiment, when the second device sends the first message again, it can increase the first length information in the first message to be greater than or equal to the length of the fourth length information plus the second message header. This allows the second device to schedule a sufficiently large second message, enabling it to send complete data without segmentation through a single second message. This avoids the situation where the second device allocates resources to schedule the first device to send data, but the first device is unable to send the second message because it cannot segment the data, thus reducing resource waste and lowering the probability of the first device failing to respond. The first length field of the second message can carry the fourth length information. This embodiment can indicate the first indication information based on the existing second message structure without adding additional fields, reducing the implementation complexity of the first device.

[0011] In one possible implementation, the first indication information indicating that the first device does not support segmented data transmission means that the second message includes a third indication information and a second length information. The third indication information indicates that there is data to be transmitted in addition to this scheduling, and the second length information is a preset value. The second length information is originally used to indicate the length of the media access control (MAC) service data unit (SDU) field in the second message, or the length of the MAC padding field, and is set to a preset value here.

[0012] In this implementation, the more data indication (MDI) field of the second message can carry the third indication information, and the first length field can carry the second length information. This implementation can indicate the first indication information based on the existing second message structure without adding additional fields, thus reducing the implementation complexity of the first device.

[0013] In one possible implementation, the first indication information indicating whether the first device supports data segmentation transmission means that: the second message includes a field carrying the first indication information; when the first indication information is a third value, it indicates that the first device does not support data segmentation transmission; when the first indication information is a fourth value, it indicates that the first device supports data segmentation transmission.

[0014] This implementation method carries the first indication information by adding a field in the second message, without affecting the functionality of the existing fields in the second message.

[0015] In one possible implementation, the first indication information is used to indicate whether the first device supports segmented data transmission and the segment type to which the data encapsulated in the second message belongs; when the first indication information is a fifth value, it indicates that the first device does not support segmented data transmission; when the first indication information is a sixth value, it indicates that the first device supports segmented data transmission and the data encapsulated in the second message is not the last segment; when the first indication information is a seventh value, it indicates that the first device supports segmented data transmission and the data encapsulated in the second message is the last segment; when the first indication information is an eighth value, it indicates that the first device supports segmented data transmission and the data encapsulated in the second message has not been segmented.

[0016] In addition to indicating the first instruction information, this implementation can further distinguish whether the data encapsulated in the second message has been segmented and whether it is the last segment.

[0017] In one possible implementation, the first indication information indicating whether the first device supports data segmentation transmission means that: the second message includes message type information, which is used to indicate the format of the second message; when the message type information is a ninth value, it indicates that the first device does not support data segmentation transmission; when the message type information is a tenth value, it indicates that the first device supports data segmentation transmission.

[0018] This implementation can indicate the first instruction information based on the existing second message structure without adding additional fields, which can reduce the implementation complexity of the first device.

[0019] In one possible implementation, the first indication information indicating whether the first device supports data segmentation transmission means that the first indication information is represented by the length of the second message; wherein, if the length of the second message is less than the length of the first length information, it indicates that the first device does not support data segmentation transmission, and if the length of the second message is greater than or equal to the length of the first length information, it indicates that the first device supports data segmentation transmission.

[0020] This implementation can indicate the first instruction information based on the existing second message structure without adding additional fields, which can reduce the implementation complexity of the first device.

[0021] In one possible implementation, if the first device does not support segmented data transmission, the second message may also include fourth length information, which indicates the length of the data to be sent by the first device.

[0022] The second device can increase the first length information in the first message to be greater than or equal to the fourth length information plus the length of the second message header when sending the first message again. This allows for scheduling a sufficiently large second message, enabling the first device to send complete data without segmentation through a single second message. This avoids situations where the second device allocates resources to schedule the first device to send data, but the first device is unable to send the second message due to the inability to segment the data, thus reducing resource waste and lowering the probability of the first device failing to respond. The first length field of the second message can carry the fourth length information, indicating the length of the data to be sent by the first device. This implementation can indicate the fourth length information based on the existing second message structure without adding an extra field, reducing the implementation complexity of the first device.

[0023] Secondly, a communication method is provided, which can be executed by a second device, or by a component configured in the second device (such as a circuit, chip, or chip system), or by a logic module or software capable of implementing all or part of the functions of the second device. This application does not limit this approach. The following description uses a second device as an example.

[0024] The method includes: sending a first message to a first device; the first message including first length information, the first length information being used to indicate the length of a scheduled second message; receiving a second message from the first device, the second message including first indication information; the first indication information being used to indicate that the first device does not support data segmentation transmission, or the first indication information being used to indicate whether the first device supports data segmentation transmission.

[0025] The embodiments of the second aspect are described with reference to the embodiments of the first aspect. The second aspect and any of its embodiments are implementations corresponding to the first aspect and any of its embodiments. The explanations, supplements and descriptions of the beneficial effects of the first aspect and any of its embodiments also apply to the second aspect and any of its embodiments, and will not be repeated here.

[0026] Thirdly, a communication method is provided, which can be executed by a first device, or by a component configured in the first device (such as a circuit, chip, or chip system), or by a logic module or software capable of implementing all or part of the functions of the first device. This application does not limit this approach. The following description uses the first device as an example.

[0027] The first device supports segmented data transmission. The method includes: receiving a first message from a second device; the first message includes first length information, which indicates the length of a scheduled second message; sending a second message to the second device according to the first length information; the second message includes a first length field and third indication information; when the data encapsulated in the second message is the first segment, the third indication information indicates that there is more data to be transmitted besides the current scheduling; the first length field is used to carry fourth length information, which indicates the length of the data to be sent by the first device; or, when the data encapsulated in the second message is any segment other than the last segment, the third indication information indicates that there is more data to be transmitted besides the current scheduling; the first length field is used to carry a preset value.

[0028] The communication method provided in this application embodiment, when the first device supports segmented data transmission, can also include fourth length information in the second message, so that the second device knows the total length of the data to be sent by the first device, thereby achieving precise scheduling. The fourth length information can be indicated based on the existing second message structure without adding an extra field, reducing the implementation complexity of the first device. Alternatively, when the data encapsulated in the second message consists of segments other than the last segment, since the end of the second message is entirely MAC SDU fields and does not include a MAC padding field, the first length field does not need to carry the second length information, i.e., it does not need to indicate the length of the MAC SDU field or the length of the MAC padding field. In this case, the first length field carries a preset value (e.g., 0), which simplifies the information carried by the first length field and reduces the implementation complexity of the first device.

[0029] Fourthly, a communication method is provided, which can be executed by a second device, or by a component configured in the second device (such as a circuit, chip, or chip system), or by a logic module or software capable of implementing all or part of the functions of the second device. This application does not limit this. The following description uses a second device as an example.

[0030] The method includes: sending a first message to a first device; the first message includes first length information, which is used to indicate the length of a scheduled second message; the first device supports segmented data transmission; receiving a second message from the first device; the second message includes a first length field and third indication information; when the data encapsulated in the second message is the first segment, the third indication information indicates that there is data to be transmitted in addition to the current scheduling; the first length field is used to carry fourth length information, which is used to indicate the length of the data to be transmitted by the first device; or, when the data encapsulated in the second message is any segment other than the last segment, the third indication information indicates that there is data to be transmitted in addition to the current scheduling; the first length field is used to carry a preset value.

[0031] The fourth aspect is the implementation corresponding to the third aspect. The explanations, supplements, and descriptions of the beneficial effects of the first aspect also apply to the fourth aspect, and will not be repeated here.

[0032] Fifthly, a communication method is provided, which can be executed by a third device, or by a component (such as a circuit, chip, or chip system) configured in the third device, or by a logic module or software capable of implementing all or part of the functions of the third device. This application does not limit this. The following description uses a third device as an example.

[0033] The method includes: sending a fourth message to a second device, the fourth message including first data; receiving a third message from the second device, the third message including fourth indication information, or the third message including second data and fourth indication information, the second data being feedback data of the first data, the fourth indication information being used to indicate the number of times the second device sends the first data to the first device, and the fourth indication information being used to narrow the value range of the decryption parameter.

[0034] The communication method provided in this application embodiment involves a second device sending a fourth indication information to a third device. The fourth indication information is used to indicate the number of times N that the second device sends the first data to the first device. The third device narrows the range of values ​​for the decryption parameters based on the number of times N that the first data is sent, thereby reducing the decryption time.

[0035] In one possible implementation, the method further includes: determining N decryption parameters [x, x+N-1] based on the fourth instruction information, where x is the initial value of the decryption parameter and N is the number of times the second device sends the first data to the first device; and using the N decryption parameters as input parameters to decrypt the second data to obtain the original plaintext data.

[0036] The third device only needs to attempt linear-level (at most N times) decryption, which greatly reduces the number of decryption attempts and speeds up the decryption process compared to the exponential-level (2^32 possibilities for 32-bit decryption parameters) decryption in existing technologies.

[0037] Sixthly, a communication method is provided, which may be executed by a second device, or by a component configured in the second device (such as a circuit, chip, or chip system), or by a logic module or software capable of implementing all or part of the functions of the second device. This application does not limit this. The following description uses a second device as an example.

[0038] The method includes: sending a first message to a first device, the first message including first data; receiving a second message from the first device, the second message including second data, the second data being feedback data of the first data; sending a third message to a third device, the third message including fourth indication information, or the third message including the second data and the fourth indication information, the fourth indication information being used to indicate the number of times the second device sends the first data to the first device, the fourth indication information being used to narrow the value range of the decryption parameter.

[0039] The implementation of the sixth aspect and any of its embodiments, as well as the explanations, supplements and descriptions of the beneficial effects of the fifth aspect and any of its embodiments, also apply to the sixth aspect and any of its embodiments, and will not be repeated here.

[0040] In a seventh aspect, a communication device is provided, comprising a communication module. The communication module is configured to receive a first message from a second device; the first message includes first length information used to indicate the length of a scheduled second message; and to send a second message to the second device according to the first length information, the second message including first indication information used to indicate whether the first device supports segmented data transmission.

[0041] The embodiments of the seventh aspect are described with reference to the embodiments of the first aspect. The seventh aspect and any of its embodiments are implementations corresponding to the first aspect and any of its embodiments. The explanations, supplements and descriptions of the beneficial effects of the first aspect and any of its embodiments also apply to the seventh aspect and any of its embodiments, and will not be repeated here.

[0042] Eighthly, a communication device is provided, comprising a communication module. The communication module is configured to send a first message to a first device; the first message includes first length information, the first length information being used to indicate the length of a scheduled second message; and to receive a second message from the first device, the second message including first indication information; the first indication information being used to indicate that the first device does not support data segmentation transmission, or the first indication information being used to indicate whether the first device supports data segmentation transmission.

[0043] The embodiments of the eighth aspect are described with reference to the embodiments of the first aspect. The eighth aspect and any of its embodiments are implementations corresponding to the first aspect and any of its embodiments. The explanations, supplements and descriptions of the beneficial effects of the first aspect and any of its embodiments also apply to the eighth aspect and any of its embodiments, and will not be repeated here.

[0044] A ninth aspect provides a communication device comprising a communication module. The communication module is configured to receive a first message from a second device; the first message includes first length information indicating the length of a scheduled second message; and to send a second message to the second device according to the first length information; the second message includes a first length field and third indication information; when the data encapsulated in the second message is the first segment, the third indication information indicates that there is data to be transmitted in addition to the current scheduling; the first length field is configured to carry fourth length information indicating the length of data to be transmitted by the first device; or, when the data encapsulated in the second message is any segment other than the last segment, the third indication information indicates that there is data to be transmitted in addition to the current scheduling; the first length field is configured to carry a preset value.

[0045] The embodiments of the ninth aspect are described with reference to the embodiments of the third aspect. The ninth aspect and any of its embodiments are implementations corresponding to the third aspect and any of its embodiments. The explanations, supplements, and descriptions of beneficial effects of the third aspect and any of its embodiments also apply to the ninth aspect and any of its embodiments, and will not be repeated here.

[0046] In a tenth aspect, a communication device is provided, comprising a communication module. The communication module is configured to send a first message to a first device; the first message includes first length information indicating the length of a scheduled second message; the first device supports segmented data transmission; and the first device receives a second message from the first device; the second message includes a first length field and third indication information; when the data encapsulated in the second message is the first segment, the third indication information indicates that there is data to be transmitted in addition to the current scheduling; the first length field carries fourth length information indicating the length of data to be transmitted by the first device; or, when the data encapsulated in the second message is any segment other than the last segment, the third indication information indicates that there is data to be transmitted in addition to the current scheduling; the first length field carries a preset value.

[0047] The embodiments of the tenth aspect are described with reference to the embodiments of the third aspect. The tenth aspect and any of its embodiments are implementations corresponding to the third aspect and any of its embodiments. The explanations, supplements and descriptions of beneficial effects of the third aspect and any of its embodiments also apply to the tenth aspect and any of its embodiments, and will not be repeated here.

[0048] Eleventhly, a communication device is provided, comprising a communication module and a processing module. The communication module is used to send a fourth message to a second device, the fourth message including first data. It also receives a third message from the second device, the third message including fourth indication information, or the third message including second data and fourth indication information, where the second data is feedback data of the first data, and the fourth indication information is used to indicate the number of times the second device sends the first data to the first device, and the fourth indication information is used to narrow the value range of the decryption parameters.

[0049] In one possible design, the processing module is used to determine N decryption parameters [x, x+N-1] based on the fourth instruction information, where x is the initial value of the decryption parameter and N is the number of times the second device sends the first data to the first device; the N decryption parameters are used as input parameters to decrypt the second data to obtain the original plaintext data.

[0050] The eleventh aspect and any of its embodiments are implementations corresponding to the fifth aspect and any of its embodiments. The explanations, supplements and descriptions of the beneficial effects of the fifth aspect and any of its embodiments also apply to the eleventh aspect and any of its embodiments, and will not be repeated here.

[0051] In a twelfth aspect, a communication device is provided, comprising a communication module. The communication module is configured to send a first message to a first device, the first message including first data; receive a second message from the first device, the second message including second data, the second data being feedback data of the first data; and send a third message to a third device, the third message including fourth indication information, or the third message including the second data and the fourth indication information, the fourth indication information being used to indicate the number of times the second device sends the first data to the first device, and the fourth indication information being used to narrow the value range of the decryption parameter.

[0052] The twelfth aspect and any of its embodiments are implementations corresponding to the fifth aspect and any of its embodiments. The explanations, supplements and descriptions of the beneficial effects of the fifth aspect and any of its embodiments also apply to the twelfth aspect and any of its embodiments, and will not be repeated here.

[0053] In a thirteenth aspect, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the methods of the first aspect, the third aspect, and any implementation thereof described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0054] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0055] In another implementation, the communication device is a chip configured in a network device. When the communication device is a chip configured in a network device, the communication interface can be an input / output interface.

[0056] In a fourteenth aspect, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the methods of the second, fourth, and sixth aspects and any implementation thereof described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0057] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0058] In another implementation, the communication device is a chip configured in a terminal device. When the communication device is a chip configured in a terminal device, the communication interface can be an input / output interface.

[0059] In a fifteenth aspect, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the methods of the fifth aspect and any implementation thereof. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0060] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0061] In another implementation, the communication device is a chip configured in a network device. When the communication device is a chip configured in a network device, the communication interface can be an input / output interface.

[0062] In a sixteenth aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the method of any possible implementation of the first to sixth aspects described above.

[0063] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0064] In a seventeenth aspect, a communication device is provided, including a processor and a memory. The processor is configured to read instructions stored in the memory, receive signals via a receiver, and transmit signals via a transmitter to execute the methods in any of the possible implementations of the first to sixth aspects described above.

[0065] Optionally, the processor may be one or more, and the memory may be one or more.

[0066] Eighteenthly, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions), which, when the computer program is run, causes a computer to perform the method in any of the possible implementations of the first to sixth aspects described above.

[0067] In a nineteenth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the methods of any of the possible implementations of the first to sixth aspects described above.

[0068] In a twentieth aspect, embodiments of this application provide a chip system including one or more processors for calling and executing instructions stored in a memory, causing the methods in any of the possible implementations of the first to sixth aspects to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0069] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0070] In a twenty-first aspect, a communication system is provided, including the aforementioned communication devices, such as a first device, a second device, and a third device. Optionally, the communication system may further include other devices that communicate with the first device, the second device, and the third device.

[0071] The technical effects of aspects thirteen through twenty-one refer to the technical effects of aspect one and any of its embodiments, aspect three and any of its embodiments, and aspect five and any of its embodiments, and will not be repeated here. Attached Figure Description

[0072] Figure 1 This application provides an embodiment of an Internet of Things (IoT) communication system architecture diagram.

[0073] Figure 2 A schematic diagram of the structure of a UE provided in an embodiment of this application;

[0074] Figure 3 This is a schematic diagram of the structure of a RAN device provided in an embodiment of this application;

[0075] Figure 4 A schematic diagram of the structure of a core network device provided in an embodiment of this application;

[0076] Figure 5 This is a schematic diagram of the structure of an Internet of Things (IoT) device provided in an embodiment of this application;

[0077] Figure 6 A flowchart illustrating a communication method provided in an embodiment of this application;

[0078] Figure 7 This is a schematic diagram of the structure of a second message provided in an embodiment of this application;

[0079] Figure 8 A schematic diagram illustrating another communication method provided in an embodiment of this application;

[0080] Figure 9 This is a schematic diagram of another structure of the second message provided in an embodiment of this application;

[0081] Figure 10 This is a schematic diagram of another structure of the second message provided in an embodiment of this application;

[0082] Figure 11 This is a schematic diagram of another structure of the second message provided in an embodiment of this application;

[0083] Figure 12 This is a schematic diagram of another structure of the second message provided in an embodiment of this application;

[0084] Figure 13 A schematic diagram illustrating another communication method provided in an embodiment of this application;

[0085] Figure 14 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0086] Figure 15This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0087] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0088] First, some concepts involved in this application will be described.

[0089] The terms "first" and "second" used in the embodiments of this application are only used to distinguish features of the same type and should not be construed as indicating relative importance, quantity, order, etc.

[0090] The terms "exemplary" or "for example" used in the embodiments of this application are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0091] Figure 1 This is a schematic diagram of the architecture of an Internet of Things (IoT) communication system provided in an embodiment of this application. The IoT communication system 100 includes an IoT device 101, a reader 102, and a core network device (or core network element) 103. The main functions of each device are described in detail below.

[0092] IoT device 101 can be an AIoT device. AIoT devices operate by collecting and utilizing various energy sources in the environment (including but not limited to radio waves, light energy, kinetic energy, and heat energy), improving the sustainability and performance of wireless communication and reducing its power consumption. AIoT devices can be applied in various scenarios, such as smart buildings, asset tracking, agriculture, and smart homes. Specifically, AIoT devices can be smart switches, smart locks, smart meters, sensor-based devices for monitoring machine status and environmental conditions, building automation and control equipment, and tagging devices. In these scenarios, the communication needs of AIoT devices are generally simple, perhaps involving simple asset information reporting or sending minimal sensor data. The environmental energy collected by AIoT devices typically only generates a small amount of electricity, requiring AIoT devices to be simpler and more energy-efficient.

[0093] The reader 102 can be a user equipment (UE) 1021, a radio access network (RAN) device 1022, an integrated access and backhaul (IAB) node, a relay node, a repeater, an AIoT reader / writer, an AIoT reader / writer device, a tag reader / writer device, or any other device with relay capabilities. The reader 102 can use wireless communication to read and write to the IoT device 101, thereby achieving target identification and data exchange. Taking the IoT device 101 as a tag device as an example, the reader 102 provides energy to the tag device by sending an excitation signal and transmits commands. The tag device sends a response to the reader 102 through a reflected signal. In this way, the reader 102 can identify the tag device's identification information and perform read and write operations on the tag device. The core network device 103 can be an access management function (AMF) network element or an AIoT function (AIOTF) network element. The AIOTF network element manages the reader 102 and IoT device 101, providing AIoT services such as: reader 102 selection or reselection, reader 102 subscription data query, IoT device 101 context management, IoT device 101 subscription data query, and IoT device 101 registration management. The AIOTF network element can select RAN device 1022 as the AIOTF reader (corresponding to topology 1), or select UE 1021 as the AIOTF reader (corresponding to topology 2), and send the selected UE list to the RAN device. The AMF network element is used to forward AIoT data.

[0094] UE 1021 may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities; it may also include subscriber units, cellular phones, smartphones, wireless data cards, personal digital assistant (PDA) computers, tablet computers, wireless modems, handheld devices, laptop computers, cordless phones or wireless local loop (WLL) stations, machine type communication (MTC) terminals, mobile stations (MS), terminal devices, or relay user equipment, etc.

[0095] RAN equipment 1022 may include various types of base stations, such as macro base stations, micro base stations (also known as "small stations"), relay stations, access points, and distributed unit-control units (DU-CUs). Additionally, these base stations can also be radio controllers in cloud radio access network (CRAN) scenarios, or network equipment in relay stations, access points, vehicle-mounted devices, wearable devices, or future public land mobile network (PLMN) networks. RAN equipment 1022 may also include broadband network gateways (BNGs), aggregation switches, and non-3GPP access equipment.

[0096] RAN device 1022 is used for functions such as radio resource management, uplink and downlink data classification, quality of service (QoS) management, data compression and encryption, signaling processing with control plane network elements, and data forwarding with user plane function network elements on the air interface side. This application embodiment does not limit the specific form and structure of RAN device 1022. For example, in systems employing different radio access technologies, the name of the RAN device 1022 with base station functions may differ. For example, a base station can be an evolved universal terrestrial radio access network (E-UTRAN) device in LTE, such as an evolved NodeB (eNB or e-NodeB), or a next-generation radio access network (NG-RAN) device (such as a gNB) in a 5G system.

[0097] Figure 2 This is a schematic diagram of the structure of a UE provided in an embodiment of this application. Taking UE 1021 as a mobile phone as an example, UE 1021 may include components such as: radio frequency (RF) circuit 210, memory 220, other input devices 230, display screen 240, sensor 250, audio circuit 260, I / O subsystem 270, processor 280, and power supply 290. Those skilled in the art will understand that the structure shown in the figure does not constitute a limitation on UE 1021, and may include more or fewer components than shown, or combine some components, or split some components, or have different component arrangements. Those skilled in the art will understand that display screen 240 belongs to the user interface (UI), and display screen 240 may include display panel 241 and touch panel 242. Although not shown, UE 1021 may also include functional modules or devices such as a camera and Bluetooth module, which will not be described in detail here.

[0098] Furthermore, the processor 280 is connected to the RF circuit 210, memory 220, audio circuit 260, I / O subsystem 270, and power supply 290. The I / O subsystem 270 is connected to other input devices 230, display screen 240, and sensor 250. The RF circuit 210 can be used to receive and transmit signals during information transmission or calls; specifically, after receiving downlink information from network devices, it sends it to the processor 280 for processing. The memory 220 can be used to store software programs and modules. The processor 280 executes various functional applications and data processing of the UE 1021 by running the software programs and modules stored in the memory 220, such as executing the methods involved in the embodiments of this application.

[0099] Other input devices 230 can be used to receive input digital or character information, and generate keyboard signal input related to user settings and function control of UE 1021. Display screen 240 can be used to display information input by the user or information provided to the user, as well as various menus of UE 1021, and can also accept user input. Sensor 250 can be a light sensor, motion sensor, or other sensor. Audio circuit 260 provides an audio interface between the user and UE 1021. I / O subsystem 270 is used to control external input / output devices, which may include other device input controllers, sensor controllers, and display controllers. Processor 280 is the control center, connecting various parts of UE 1021 through various interfaces and lines. It executes various functions of UE 1021 and processes data by running or executing software programs and / or modules stored in memory 220, and by calling data stored in memory 220. Power supply 290 (e.g., a battery) is used to power the above components. The power supply can be logically connected to processor 280 through a power management system, thereby managing charging, discharging, and power consumption.

[0100] Figure 3This is a schematic diagram of a RAN device provided in an embodiment of this application. Taking RAN device 1022 as a base station as an example, RAN device 1022 may include an indoor baseband unit (BBU) 301 and a remote radio unit (RRU) 302. The RRU 302 is connected to the antenna system (i.e., antenna) 303. BBU 301 and RRU 302 can be disassembled and used as needed. BBU 301 may include a processor 3011, a memory 3012, and a bus system 3013. The processor 3011 and memory 3012 of BBU 301 are interconnected through the bus system 3013. The bus system may be a peripheral component interconnection standard bus or an extended industrial standard structure bus, etc. The bus may be divided into address bus, data bus, control bus, etc. For ease of illustration, only one line is used to represent it in the figure, but this does not mean that there is only one bus or one type of bus. RRU 302 may include RF circuitry 3021, which is interconnected with BBU 301 via optical fiber and with antenna 303 via coaxial cable. Processor 3011 executes various functional applications and data processing of RAN device 1022 by running computer instructions stored in memory 3012, such as the methods described in the embodiments of this application.

[0101] Figure 4This is a schematic diagram of the structure of a core network device (e.g., an AIOTF network element, an AMF network element) provided for embodiments of this application. Taking core network device 103 as an example, the core network device 103 may include at least one processor 401, a communication line 402, a memory 403, and at least one communication interface 404. The processor 401 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of programs according to the present application. The communication line 402 may include a path for transmitting information between the above components. The communication interface 404, using any transceiver-like device, is used to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), etc. The memory 403 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory may exist independently and be connected to the processor via communication line 402. The memory may also be integrated with the processor. The memory 403 is used to store computer execution instructions (which may be referred to as application code) for executing the scheme of this application, and its execution is controlled by the processor 401. The processor 401 is used to execute computer execution instructions stored in the memory 403, thereby performing the methods involved in the embodiments of this application.

[0102] Figure 5This is a schematic diagram of the structure of an Internet of Things (IoT) device provided in an embodiment of this application. Taking IoT device 101 as a tag device as an example, IoT device 101 may include a processing module 501, a communication module 502, and an energy harvesting module 503. The processing module 501 is used for data preprocessing and controlling the IoT device 101 to go into sleep mode or power on. The communication module 502 is used for communication via backscatter or a simplified radio frequency protocol. The energy harvesting module 503 is used to convert environmental energy such as radio frequency, light energy, heat energy, and kinetic energy into electrical energy to power the processing module 501 and the communication module 502.

[0103] The AIoT services performed by the reader include inventory and command services. Inventory is a fundamental service used to discover or identify IoT devices within the reader's coverage area. Command services include read, write, disable, and enable services. The read service is used to read information from IoT devices. The write service is used to write information to IoT devices. The disable service instructs IoT devices to permanently or temporarily disable their ability to transmit radio frequencies. The enable service enables temporarily disabled IoT devices. For example, when the IoT device is a sensor, the reader can acquire sensor data through the read service.

[0104] Figure 6 This is a flowchart illustrating a communication method provided in an embodiment of this application. The method 600 includes: S601, a first message being sent from a second device to a first device; S602, a second message being sent from the first device to the second device.

[0105] For example, in this embodiment, the first device is an IoT device, the second device is a reader, the first message is a reader-to-device (R2D) message, and the second message is a device-to-reader (D2R) message. In the inventory service, the R2D message triggers the IoT device to report inventory results, and the D2R message includes the inventory results of the IoT device, such as the IoT device identifier. In the command service, the R2D message includes a command request to trigger the command service, and the D2R message includes a command response to indicate the result of the IoT device executing the command service. For example, for the read service, the result refers to the data returned by the IoT device. For the write service, the result indicates whether the write service was successful. For the de-enable service, the result indicates whether the IoT device was successfully de-enabled. For the enable service, the result indicates whether the IoT device was successfully enabled.

[0106] Figure 7This is a schematic diagram illustrating the structure of a second message provided in an embodiment of this application. The second message can be a Media Access Control (MAC) Protocol Data Unit (PDU). The second message 700 includes a More Data Indication (MDI) field, a First Length field, and a Media Access Control (MAC) Service Data Unit (SDU) field. Optionally, the second message may also include a Message Type field and a MAC Padding field. The naming of these fields is not limited in this embodiment.

[0107] The message type field indicates the structure of the second message. For example, a message type of 1 indicates that the second message is a higher-level data transmission resource request message, which includes an MDI field and a first length field; a message type of 2 indicates that the second message is a higher-level data transmission message, which includes an MDI field, a first length field, a MAC SDU field, and a MAC padding field. The MAC SDU is the higher-level data encapsulated in the second message. The first length field carries the second length information, which indicates the length of the MAC SDU field, or the length of the MAC padding field. The MDI field occupies 1 bit and carries the third indication information, which indicates whether there is any data to be transmitted besides this scheduling. The MAC padding field is used to fill in invalid data to achieve resource alignment.

[0108] The first message includes first length information, which indicates the length of the second message to be scheduled, or the length of the scheduled transport block, or the length of the scheduled MAC PDU. Third length information can be obtained implicitly or explicitly from the first length information. The third length information is equal to the first length information minus the length of the second message header. The third length information represents the maximum length of data (MAC SDU) that the first device can send in this scheduling.

[0109] For example, assuming the first length information is the transport block size (TBS), subtracting the MAC header length from the first length information yields the third length information. For example, in... Figure 7 In a MAC header, the message type field, the MDI field, and the first length field are included. The length of the MAC header is equal to the sum of the lengths of the message type field, the MDI field, and the first length field. When the MAC PDU does not have a MAC padding field, the third length information is equal to the length of the MAC SDU field; when the MAC PDU has a MAC padding field, the third length information is equal to the length of the MAC SDU field plus the length of the MAC padding field.

[0110] When the third indication information is the first value (e.g., true or 1), it indicates that there is more data to be transmitted besides this scheduling. For example, the data encapsulated in the second message (MAC SDU) is not the last segment, and more second messages need to be transmitted to transmit the remaining segments. In this case, there is no MAC padding field at the end of the second message. When the third indication information is the second value (e.g., false or 0), it indicates that there is no data to be transmitted besides this scheduling. For example, the data encapsulated in the second message is the last segment or has not been segmented. In this case, if the length of the MAC SDU field is less than the third length information, the IoT device adds a MAC padding field with invalid data to the end of the second message, so that the length of the MAC SDU field plus the length of the MAC padding field equals the third length information, and the length of the entire second message equals the first length information, to achieve resource alignment.

[0111] Some IoT devices may not have the capability to transmit data in segments. When the data length (TBS) scheduled by the reader is less than the data length the IoT device needs to send, the IoT device cannot send data, resulting in a response failure. The reader cannot determine the reason for the IoT device's response failure and therefore cannot improve scheduling accordingly, such as increasing the scheduled data length, leading to repeated scheduling failures and wasting scheduling resources. In view of this, embodiments of this application provide a communication method in which a first device (e.g., an IoT device) sends first indication information to a second device (e.g., a reader). The first indication information indicates whether the first device supports data segmentation transmission. The second device can then improve scheduling accordingly, thereby reducing resource waste and lowering the probability of the first device's response failure.

[0112] Figure 8 This is a schematic diagram of another communication method provided in an embodiment of this application. Figure 8 The first device in the process can be Figure 1 The term "Internet of Things (IoT) device" can also refer to the components within an IoT device (such as processors, chips, or chip systems). Figure 8 The second device in the process can be Figure 1 The term "reader" can also refer to the devices within a reader (such as a processor, chip, or chip system). For example... Figure 8 As shown, the communication method 800 includes the following steps S801-S803:

[0113] S801, the second device sends the first message to the first device.

[0114] Accordingly, the first device receives a first message from the second device. The first message includes first length information, which indicates the length of the scheduled second message, i.e., the length of the scheduled MAC PDU. The second message is a media access control (MAC) service data unit (SDU) encapsulated with a MAC header (e.g., ...). Figure 7 The MAC PDU contains a message type field, an MDI field, and a first length field (the message type field is optional). The length unit in this embodiment can be bits or bytes. The first message can schedule a single second message or multiple consecutive second messages.

[0115] It should be noted that the first length information can be directly represented by the length of the second message (MAC PDU) (e.g., the transport block size (TBS)), or it can be calculated by the length of the scheduled data (MAC SDU), or it can be calculated by other lengths related to the length of the MAC PDU.

[0116] S802, the first device sends a second message to the second device based on the first length information.

[0117] Accordingly, the second device receives the first message from the first device.

[0118] The first device determines the third length information based on the first length information. The third length information is equal to the first length information minus the length of the second message header. The third length information is the maximum length of data (MAC SDU) that the first device can send in this scheduling. The length of the data to be sent by the first device is less than or equal to the third length information. Subsequently, the first device can compare the length of the data to be sent with the third length information to determine whether a single second message can completely transmit the data to be sent. The data to be sent by the first device refers to the higher-layer response data generated after the first device receives a disk storage request or command request from the second device, or it can refer to the data cached by the first device's MAC layer.

[0119] Then, the first device determines the information included in the second message based on whether the first device supports segmented data transmission, the third length information, and the fourth length information. The fourth length information refers to the length of the data to be sent by the first device.

[0120] When the fourth length information (the length of the data to be sent by the first device) is less than or equal to the third length information (the maximum length of data that the first device can send in this scheduling), regardless of whether the first device supports data segmentation, a single second message can completely transmit the data to be sent by the first device without involving data segmentation. In this case, the format of the second message can be referenced... Figure 7 As shown, it will not be elaborated further here.

[0121] The second message includes a first indication message when at least one of the following conditions is met: the first device does not support segmented data transmission; the fourth length information (the length of the data to be transmitted by the first device) is greater than the third length information (the maximum length of data that the first device can transmit in this scheduling); the second device allows the first device to send the first indication message; or the first device has sufficient energy to send the first indication message. The first indication message indicates that the first device does not support segmented transmission of the data to be transmitted (MAC SDU or NAS PDU), or it indicates whether the first device supports segmented data transmission. The fourth length information can be M times the third length information, or it can be M times the length of a unit of data, where M is a positive integer.

[0122] The specific instruction method for the first instruction information may include at least one of the following implementation methods:

[0123] In one implementation, the first indication information indicating that the first device does not support segmented data transmission means that the second message includes fourth length information, and the fourth length information is greater than the third length information. That is, the length of the data to be sent by the first device is greater than the maximum length of data that the first device can send in this scheduled transmission. In this case, the second device can increase the first length information in the first message to be greater than or equal to the fourth length information plus the length of the second message header when sending the first message next time. This allows for scheduling a sufficiently large second message, enabling the first device to send complete data without segmentation through a single second message. This avoids situations where the second device allocates resources to schedule the first device to send data, but the first device is unable to send the second message due to the inability to segment the data, thus reducing resource waste and lowering the probability of the first device failing to respond.

[0124] It should be noted that the fourth length information can be represented directly by the length of the MAC SDU to be transmitted, or by the length of the second message or other lengths related to the length of the MAC SDU. The first device can deduce the length of the scheduled data (MAC SDU) by using the length of the second message or other lengths.

[0125] For example, it is possible to Figure 7The first length field of the second message 700 shown carries fourth length information. This implementation can indicate the first indication information based on the existing second message structure without adding an additional field, thus reducing the implementation complexity of the first device.

[0126] For example, Figure 9 This is a schematic diagram illustrating another structure of the second message provided in an embodiment of this application. It can also be seen in... Figure 9 The second message 900 shown carries fourth length information in the newly added second length field. The position of the second length field is not limited in this embodiment. Figure 9 Other domain references Figure 7 The description will not be repeated here. This implementation does not require modification of the meaning of the first length field.

[0127] For example, Figure 10 This is a schematic diagram illustrating another structure of the second message provided in an embodiment of this application. Because the length of the second message is too short to encapsulate data (MAC SDU), therefore... Figure 10 As shown in A or B, the second message 1000 can be removed. Figure 7 or Figure 9 The MAC SDU field in the middle is used to save the overhead of the second message 1000. This can be done... Figure 10 The first length field shown in Figure A carries the fourth length information (refer to...). Figure 7 (Description), or, can be Figure 10 The second length field shown in B carries fourth length information (refer to...). Figure 9 describe).

[0128] In another implementation, the first indication information indicating that the first device does not support segmented data transmission means that the second message includes the second indication information, which indicates the transmission resources requested by the first device, such as time-frequency resources, for transmitting the data to be sent by the first device. The purpose of the second indication information is that since the first device does not support segmented data transmission, the transmission resources currently allocated by the second device to the first device are insufficient, preventing the first device from transmitting data. Therefore, the second device needs to allocate more transmission resources, effectively increasing the TBS (Transmission Block Size). This avoids a situation where the second device allocates resources to schedule the first device to send data, but the first device is unable to send the second message due to the inability to segment the data, thus reducing resource waste and lowering the probability of the first device failing to respond. Optionally, the second message may also include fourth length information.

[0129] For example, Figure 7 The first length field of the second message 700 shown can carry the second indication information; or, Figure 9The first length field of the second message 900 shown can carry second indication information, and the second length field can carry fourth length information; or, Figure 9 The second length field of the second message 900 shown can carry the second indication information, and the first length field can carry the fourth length information; or, other fields added to the second message can carry the second indication information.

[0130] In another implementation, the first indication information indicating that the first device does not support segmented data transmission means that the second message includes a third indication information and a second length information. The third indication information indicates that there is data to be transmitted in addition to the current schedule, and the second length information is a preset value (e.g., 0). Specifically, the third indication information indicates whether there is data to be transmitted in addition to the current schedule, and the second length information indicates the length of the MAC SDU field, or the length of the MAC padding field. Optionally, the second message may also include a fourth length information.

[0131] For example, Figure 7 The MDI field of the second message 700 shown can carry third indication information, and the first length field can carry second length information. For example, when the first length field indicates the length of the MAC SDU field: the MDI field is a first value (e.g., true or 1), indicating that there is data to be transmitted in addition to this scheduling; the first length field is 0, indicating that there is no data to be transmitted in this scheduling; thus indicating that the first device does not support segmented data transmission. This implementation can indicate the first indication information based on the existing second message structure without adding additional fields, which can reduce the implementation complexity of the first device.

[0132] Optional, such as Figure 9 As shown, the second message 900 may also include a second length field, which can carry fourth length information. For details on the technical effects, please refer to... Figure 9 The description will not be repeated here.

[0133] In another implementation, the first indication information indicating whether the first device supports segmented data transmission means that the second message includes a field carrying the first indication information (e.g., a segment indication field). Optionally, the field carrying the first indication information may occupy one bit. This implementation carries the first indication information by adding a field to the second message, without affecting the functionality of existing fields in the second message.

[0134] When the first indication information is a third value (e.g., false or 0), it indicates that the first device does not support data segmentation transmission. Optionally, the second message may include fourth length information, and the first length field may carry this fourth length information. When the first indication information is a fourth value (e.g., true or 1), it indicates that the first device supports data segmentation transmission. In this case, the first length field of the second message may carry second length information.

[0135] For example, Figure 11 This is a schematic diagram illustrating another structure of a second message provided in an embodiment of this application. The second message 1100 includes an extended field, which is used to carry first indication information. Other fields in the second message 1100 are referenced... Figure 7 The description will not be repeated here. The embodiments of this application do not limit the location of the extended field; for example, the extended field may be located before or after the MDI field.

[0136] In another implementation, the first indication information can be used not only to indicate whether the first device supports segmented data transmission, but also to indicate the segment type of the data encapsulated in the second message. That is, the first indication information is used to indicate whether the first device supports segmented data transmission, and the segment type of the data encapsulated in the second message. The segment type of the data encapsulated in the second message can include: last segment, not the last segment, not segmented, etc. The first indication information can occupy two bits, thus having four values ​​(e.g., 0 to 3). For example, the first indication information can be... Figure 11 The extended field and MDI field shown are combined to carry the data.

[0137] When the first indication information is the fifth value (e.g., 0), it indicates that the first device does not support segmented data transmission. In this case, the second message may include fourth length information, and the first length field can carry the fourth length information. The fourth length information is described above and will not be repeated here.

[0138] When the first indication information is the sixth value (e.g., 1), it indicates that the first device supports segmented data transmission, and the data encapsulated in the second message is not the last segment. Optionally, since the second message ends entirely with MAC SDU fields and will not include MAC padding fields, the second message may not include the first length field used to carry the second length information, in order to save resources for transmitting more data.

[0139] When the first indication information is the seventh value (e.g., 2), it indicates that the first device supports segmented data transmission, and the data encapsulated in the second message is the last segment. Optionally, since the second message may include a MAC padding field, the second message may include a first length field, which carries second length information. The second length information is described above and will not be repeated here.

[0140] When the first indication information is the eighth value (e.g., 3), it indicates that the first device supports segmented data transmission, and the data encapsulated in the second message has not been segmented. Optionally, since the second message may include a MAC padding field, the second message may include a first length field, which carries second length information. The second length information is described above and will not be repeated here. This implementation, in addition to indicating the first indication information, can further distinguish whether the data encapsulated in the second message has been segmented and whether it is the last segment.

[0141] In another implementation, the first indication information indicating whether the first device supports segmented data transmission means that the second message includes message type information, which indicates the format of the second message. When the message type information is a ninth value (e.g., 0), it indicates that the first device does not support segmented data transmission; optionally, the second message may include fourth length information, which is described above and will not be repeated here. When the message type information is a tenth value (e.g., 1), it indicates that the first device supports segmented data transmission. This implementation can indicate the first indication information based on the existing second message structure without adding additional fields, thus reducing the implementation complexity of the first device.

[0142] For example, Figure 12 This is a schematic diagram illustrating another structure of a second message provided in an embodiment of this application. The second message 1200 includes a message type field, a first length field, and a MAC padding field. The message type field carries message type information. The first length field is optional. When the message type field is a ninth value (e.g., 0), it indicates that the first device does not support segmented data transmission. In this case, the structure of the second message is as follows... Figure 12 As shown, the second message 1200 may include a first length field, which can carry fourth length information. When the message type field is the tenth value (e.g., 1), it indicates that the first device supports segmented data transmission. In this case, the structure of the second message is as follows: Figure 7 As shown, it will not be elaborated further here.

[0143] In another implementation, the first indication information indicating whether the first device supports data segmentation transmission means that the first indication information is represented by the length of the second message. If the length of the second message is less than the first length information or TBS, it indicates that the first device does not support data segmentation transmission. If the length of the second message is greater than or equal to the first length information or TBS, it indicates that the first device supports data segmentation transmission. The structure of the second message can be referred to... Figure 7The description of the first instruction is omitted here. This implementation can indicate the first instruction information based on the existing second message structure without adding additional fields, which can reduce the implementation complexity of the first device. Optionally, the second message may include fourth length information, and the first length field can carry the fourth length information. The fourth length information is described above and will not be repeated here.

[0144] Furthermore, if the first device supports segmented data transmission, the second message may also include fourth length information so that the second device knows the length of the data to be sent by the first device, thereby achieving precise scheduling. The fourth length information is described above and will not be repeated here.

[0145] For example, Figure 7 The MDI field of the second message 700 shown carries third indication information, and the first length field carries fourth length information or second length information.

[0146] When the data encapsulated in the second message (i.e., the MAC SDU field) is the first segment, the third indication information is the first value (e.g., true or 1), indicating that there is more data to be transmitted besides this scheduling. At this time, since the end of the second message is entirely MACSDU fields and does not include MAC padding fields, the first length field does not need to carry the second length information, that is, it does not need to indicate the length of the MAC SDU field or the length of the MAC padding field. The first length field can be used to carry the fourth length information.

[0147] When the data encapsulated in the second message is the last segment or is unsegmented, the third indication information is a second value (e.g., false or 0), indicating that no data needs to be transmitted except for this scheduling. In this case, since the second message may include a MAC padding field, the first length field can carry the second length information to indicate the length of the MAC SDU field, or the length of the MAC padding field.

[0148] When the data encapsulated in the second message consists of segments other than the first and last segments, the third indication information is a first value (e.g., true or 1), indicating that there is more data to be transmitted besides this schedule. In this case, the first length field can carry the second length information to indicate the length of the MAC SDU field, or the length of the MAC padding field.

[0149] If the first device supports segmented data transmission, the second message can also include fourth length information so that the second device knows the total length of the data to be sent by the first device, thereby achieving precise scheduling. The fourth length information can be indicated based on the existing second message structure without adding extra fields, which reduces the implementation complexity of the first device.

[0150] In addition, if the first device supports data segmentation for transmission, the information carried by the first length field can be simplified, reducing the implementation complexity of the first device.

[0151] For example, Figure 7 The MDI field of the second message 700 shown carries third indication information, and the first length field carries second length information or a preset value (e.g., 0).

[0152] When the data encapsulated in the second message is the last segment or is unsegmented, the third indication information is a second value (e.g., false or 0), indicating that no data needs to be transmitted except for this scheduling. In this case, since the second message may include a MAC padding field, the first length field can carry the second length information to indicate the length of the MAC SDU field, or the length of the MAC padding field.

[0153] When the data encapsulated in the second message consists of segments other than the last segment, the third indication information is a first value (e.g., true or 1), indicating that there is more data to be transmitted besides this scheduling. Since the end of the second message is entirely a MACSDU field and does not include a MAC padding field, the first length field does not need to carry the second length information, i.e., it does not need to indicate the length of the MAC SDU field or the length of the MAC padding field. In this case, the first length field carries a preset value (e.g., 0), which simplifies the information carried by the first length field and reduces the implementation complexity of the first device.

[0154] S803. In response to the first indication information, the second device sends scheduling information to the first device, or sends re-access indication information to the first device, or sends failure indication information to the first device.

[0155] Accordingly, the first device receives scheduling information, or re-access indication information, or failure indication information from the second device. The scheduling information, re-access indication information, and failure indication information can be carried in the first message. The scheduling information (or resource information) is used to schedule the transmission resources of the second message, such as time-frequency resources, first length information (which can be TBS), etc. The re-access indication information is used to trigger a re-paging. The failure indication information is used to trigger inventory.

[0156] If the first indication information indicates that the first device does not support data segmentation transmission: the second device sends scheduling information to the first device, wherein the first length information is greater than or equal to the fourth length information; or, the second device sends re-access indication information to the first device; or, the second device sends failure indication information to the first device.

[0157] When the first instruction information indicates that the first device supports data segmentation transmission: the second device sends scheduling information to the first device, and the second device can make its own decision on the first length information, for example, keeping it the same as the previous first length information.

[0158] The communication method provided in this application embodiment involves a first device (e.g., an IoT device) sending a first indication message to a second device (e.g., a reader). The first indication message indicates whether the first device supports data segmentation transmission. The second device can then improve scheduling accordingly, thereby reducing resource waste and lowering the probability of the first device failing to respond.

[0159] In addition, in IoT communication systems, encryption / decryption or integrity protection operations are performed between the primary device and the core network device to protect the security and integrity of data transmission. For example, the NAS layer uses the Advanced Encryption Standard (AES) Counter Mode (AES-CTR), NEA0, and 128-NEA2 for encryption, and 128-NIA2 for integrity protection. Taking AES-CTR encryption as an example, the keystream for this encryption method is obtained as follows: a random initialization vector (IV) is generated, and the count value (COUNT), initialization vector (IV), logical channel identifier (bearID), and uplink / downlink direction information are combined and input into the AES encryption function for encryption to obtain the keystream. Encryption process: Each block of plaintext data is XORed with the keystream at the corresponding position to obtain the ciphertext. Decryption process: XORing the ciphertext with the keystream at the corresponding position recovers the original plaintext data.

[0160] During decryption, the receiving end may fail to decrypt directly, leading to service transmission failure. Alternatively, it may require traversing all possible values ​​of the parameter for decryption, which is time-consuming. To address this, this application provides a communication method that determines the range of parameter values ​​required for decryption based on the number of data transmissions, thereby reducing decryption time and ensuring successful decryption.

[0161] Figure 13 This is a schematic diagram of another communication method provided in an embodiment of this application. Figure 13 The first device in the process can be Figure 1 The term "Internet of Things (IoT) device" can also refer to the components within an IoT device (such as processors, chips, or chip systems). Figure 13 The second device in the process can be Figure 1 The term "reader" can also refer to the devices within a reader (such as processors, chips, or chip systems). Figure 13 The third device in the middle can be Figure 1The core network equipment (such as AMF network elements, AIOTF network elements) can also refer to devices within the core network equipment (such as processors, chips, or chip systems). Figure 13 As shown, the communication method 1300 includes the following steps S1301-S1305:

[0162] S1301, The third device sends a fourth message to the second device.

[0163] Accordingly, the second device receives a fourth message from the third device. This fourth message includes the first data. The first data can be a non-access stratum protocol data unit (NAS PDU) or a container. A NAS PDU can be, for example, an authentication request, a session establishment command, or an AIoT inventory request or command request. The container information can encapsulate AIoT-specific commands, such as an inventory command for querying a device list.

[0164] S1302, The second device sends the first message to the first device.

[0165] Accordingly, the first device receives a first message from the second device. The first message includes first data. To ensure that the first device can correctly receive the first message and can send feedback information about the first message, the second device will send multiple first messages to the first device until it receives a second message from the first device.

[0166] S1303, The first device sends a second message to the second device.

[0167] Accordingly, the second device receives a second message from the first device. This second message includes second data. The second data is a NAS PDU or a container. The second data can be feedback data from the first message.

[0168] S1304, The second device sends a third message to the third device.

[0169] Accordingly, the third device receives a third message from the second device. The third message includes fourth indication information, or the third message includes second data and fourth indication information. That is, the fourth indication information can be sent in the same third message as the second data, or it can be sent in different third messages. The fourth indication information is used to indicate the number N of times the second device sends the first data to the first device, where N is a positive integer greater than 0. For example, if the second device sends the first data 3 times, then N is recorded as 3. Alternatively, the fourth indication information is used to indicate the number N of times the first data is sent and feedback data (second data) is received. For example, if the second device sends the first data 3 times and receives the second data 1 time, then N is recorded as 1; if the second device sends the first data 3 times and receives the second data 2 times, then N is recorded as 2.

[0170] S1305, The third device decrypts the second data according to the fourth instruction information.

[0171] The third device determines N decryption parameters [x, x+N-1] based on the fourth instruction information, where x is the initial value of the decryption parameter and N is the fourth instruction information. The third device uses the N decryption parameters as input parameters to decrypt the second data to obtain the original plaintext data. The third device only needs to attempt linear-level (at most N times) decryption, which greatly reduces the number of decryption attempts and speeds up the decryption process compared to the exponential-level (2^32 possibilities for 32-bit decryption parameters) decryption in existing technologies.

[0172] For example, taking AES-CTR decryption, the third device determines the range of N count values ​​(COUNT) as [x, x+N-1] based on the fourth instruction information, where x is the initial value of the count value (COUNT), and the decryption parameter is the count value. The initialization vector (IV), logical channel identifier (bear ID), and uplink / downlink instruction information (direction) are combined with the N count values ​​(COUNT) respectively, and input as input parameters to the AES encryption function to obtain N key streams. Each of the N key streams is then XORed with the second data to decrypt the original plaintext data. One of these key streams will be able to decrypt the original plaintext data. The third device only needs to attempt linear-level (at most N times) decryption, which significantly reduces the number of decryption attempts and speeds up the decryption process compared to the exponential-level (2^32 possibilities for a 32-bit count value (COUNT)) decryption in existing technologies.

[0173] The communication method provided in this application embodiment involves a second device sending a fourth indication information to a third device. The fourth indication information is used to indicate the number of times N that the second device sends the first data to the first device. The third device narrows the range of values ​​for the decryption parameters based on the number of times N that the first data is sent, thereby reducing the decryption time.

[0174] Figure 14This is a schematic diagram of a communication device provided in an embodiment of this application. The communication device 1400 may include a communication module 1410. The communication module 1410 can implement corresponding communication functions, which can be internal communication functions of the communication device 1400 or communication functions between the communication device 1400 and other devices. Optionally, the communication module 1410 may also be referred to as a communication interface or a transceiver module. Optionally, the communication device 1400 further includes a processing module 1420. The processing module 1420 can implement corresponding processing functions.

[0175] Optionally, the communication device 1400 further includes a storage module 1430, which can be used to store instructions and / or data; the processing module 1420 can read the instructions and / or data in the storage module 1430 so that the communication device 1400 can implement the aforementioned method embodiment.

[0176] In one possible design, the communication device 1400 may correspond to the first device in the above method embodiments, or a component (such as a circuit, chip, or chip system) configured in the first device. The communication device 1400 may be used to perform the steps or processes performed by the first device in any of the above method embodiments.

[0177] For example, the communication module 1410 is used to receive a first message from a second device; the first message includes first length information, which is used to indicate the length of a scheduled second message; and sends a second message to the second device according to the first length information, the second message including first indication information; the first indication information is used to indicate whether the first device supports segmented data transmission.

[0178] In one possible implementation, the first indication information indicating that the first device does not support segmented data transmission means that: the second message includes fourth length information, and the fourth length information is greater than the third length information; the fourth length information is used to indicate the length of the data to be sent by the first device, and the third length information is equal to the first length information minus the length of the second message header.

[0179] In one possible implementation, the first indication information indicating that the first device does not support data segmentation transmission means that the second message includes a third indication information and a second length information. The third indication information indicates that there is data to be transmitted in addition to this scheduling, and the second length information is a preset value.

[0180] In one possible implementation, the first indication information indicating whether the first device supports data segmentation transmission means that: the second message includes a field carrying the first indication information; when the first indication information is a third value, it indicates that the first device does not support data segmentation transmission; when the first indication information is a fourth value, it indicates that the first device supports data segmentation transmission.

[0181] In one possible implementation, the first indication information is used to indicate whether the first device supports segmented data transmission and the segment type to which the data encapsulated in the second message belongs; when the first indication information is a fifth value, it indicates that the first device does not support segmented data transmission; when the first indication information is a sixth value, it indicates that the first device supports segmented data transmission and the data encapsulated in the second message is not the last segment; when the first indication information is a seventh value, it indicates that the first device supports segmented data transmission and the data encapsulated in the second message is the last segment; when the first indication information is an eighth value, it indicates that the first device supports segmented data transmission and the data encapsulated in the second message has not been segmented.

[0182] In one possible implementation, the first indication information indicating whether the first device supports data segmentation transmission means that: the second message includes message type information, which is used to indicate the format of the second message; when the message type information is a ninth value, it indicates that the first device does not support data segmentation transmission; when the message type information is a tenth value, it indicates that the first device supports data segmentation transmission.

[0183] In one possible implementation, the first indication information indicating whether the first device supports data segmentation transmission means that the first indication information is represented by the length of the second message; wherein, if the length of the second message is less than the length of the first length information, it indicates that the first device does not support data segmentation transmission, and if the length of the second message is greater than or equal to the length of the first length information, it indicates that the first device supports data segmentation transmission.

[0184] In one possible implementation, if the first device does not support segmented data transmission, the second message may also include fourth length information, which indicates the length of the data to be sent by the first device.

[0185] In one possible design, the communication device 1400 may correspond to the second device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the second device. The communication device 1400 may be used to perform the steps or processes performed by the second device in any of the above method embodiments.

[0186] For example, the communication module 1410 is used to send a first message to a first device; the first message includes first length information, which is used to indicate the length of a scheduled second message; receive a second message from the first device, which includes first indication information; the first indication information is used to indicate that the first device does not support data segmentation transmission, or the first indication information is used to indicate whether the first device supports data segmentation transmission.

[0187] In one possible design, the communication device 1400 may correspond to the first device in the above method embodiments, or a component (such as a circuit, chip, or chip system) configured in the first device. The communication device 1400 may be used to perform the steps or processes performed by the first device in any of the above method embodiments.

[0188] For example, the communication module 1410 is used to receive a first message from a second device; the first message includes first length information, which is used to indicate the length of a scheduled second message; the second message is sent to the second device according to the first length information; the second message includes a first length field and third indication information; when the data encapsulated in the second message is the first segment, the third indication information indicates that there is more data to be transmitted in addition to this scheduling; the first length field is used to carry fourth length information, which is used to indicate the length of the data to be sent by the first device; or, when the data encapsulated in the second message is any segment other than the last segment, the third indication information indicates that there is more data to be transmitted in addition to this scheduling; the first length field is used to carry a preset value.

[0189] In one possible design, the communication device 1400 may correspond to the second device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the second device. The communication device 1400 may be used to perform the steps or processes performed by the second device in any of the above method embodiments.

[0190] For example, the communication module 1410 is used to send a first message to a first device; the first message includes first length information, which is used to indicate the length of a scheduled second message; the first device supports segmented data transmission; receiving a second message from the first device; the second message includes a first length field and third indication information; when the data encapsulated in the second message is the first segment, the third indication information indicates that there is more data to be transmitted besides this scheduling; the first length field is used to carry fourth length information, which is used to indicate the length of the data to be sent by the first device; or, when the data encapsulated in the second message is any segment other than the last segment, the third indication information indicates that there is more data to be transmitted besides this scheduling; the first length field is used to carry a preset value.

[0191] In one possible design, the communication device 1400 may correspond to the third device in the above method embodiments, or a component (such as a circuit, chip, or chip system) configured in the third device. The communication device 1400 may be used to perform the steps or processes performed by the third device in any of the above method embodiments.

[0192] For example, the communication module 1410 is used to send a fourth message to the second device, the fourth message including first data; receive a third message from the second device, the third message including fourth indication information, or the third message including second data and fourth indication information, the second data being feedback data of the first data, the fourth indication information being used to indicate the number of times the second device sends the first data to the first device, and the fourth indication information being used to narrow the value range of the decryption parameter.

[0193] In one possible design, the processing module 1420 is used to determine N decryption parameters [x, x+N-1] based on the fourth instruction information, where x is the initial value of the decryption parameter and N is the number of times the second device sends the first data to the first device; and uses the N decryption parameters as input parameters to decrypt the second data to obtain the original plaintext data.

[0194] In one possible design, the communication device 1400 may correspond to the second device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the second device. The communication device 1400 may be used to perform the steps or processes performed by the second device in any of the above method embodiments.

[0195] For example, the communication module 1410 is used to send a first message to a first device, the first message including first data; receive a second message from the first device, the second message including second data, the second data being feedback data of the first data; send a third message to a third device, the third message including fourth indication information, or the third message including the second data and the fourth indication information, the fourth indication information being used to indicate the number of times the second device sends the first data to the first device, the fourth indication information being used to narrow the value range of the decryption parameter.

[0196] Figure 15 This is a schematic diagram of another communication device provided in an embodiment of this application. The communication device 1500 may be a chip, chip system, or processor, etc., implementing the above-described method, such as a first device, a second device, or a third device. The communication device 1500 can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.

[0197] like Figure 15 As shown, the communication device 1500 may include one or more processors 1510, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 1510 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device 1500 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0198] In an alternative design, the processor 1510 may also store instructions and / or data, which can be executed by the processor 1510 to cause the communication device 1500 to perform the methods described in the above method embodiments.

[0199] In another alternative design, the communication device 1500 may include a communication interface 1520 for implementing receiving and transmitting functions. For example, the communication interface 1520 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0200] Optionally, the communication device 1500 may include one or more memories 1530, which may store instructions that can be executed on the processor 1510, causing the communication device 1500 to perform the methods described in the above method embodiments. Optionally, the memories 1530 may also store data. Optionally, the processor 1510 may also store instructions and / or data. The processor 1510 and the memories 1530 may be provided separately or integrated together.

[0201] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0202] In one implementation, the communication device 1500 may correspond to the first device in the above method embodiments and may be used to execute the various steps and / or processes executed by the first device in the above method embodiments. The processor 1510 may be used to execute instructions stored in the memory 1530, and when the processor 1510 executes the instructions stored in the memory, the processor 1510 is used to execute the various steps and / or processes of the above method embodiments corresponding to the first device.

[0203] In another implementation, the communication device 1500 may correspond to the second device in the above method embodiments and may be used to execute the various steps and / or processes executed by the second device in the above method embodiments. The processor 1510 may be used to execute instructions stored in the memory 1530, and when the processor 1510 executes the instructions stored in the memory, the processor 1510 is used to execute the various steps and / or processes of the above method embodiments corresponding to the second device.

[0204] In another implementation, the communication device 1500 may correspond to the third device in the above method embodiments and may be used to execute the various steps and / or processes executed by the third device in the above method embodiments. The processor 1510 may be used to execute instructions stored in the memory 1530, and when the processor 1510 executes the instructions stored in the memory, the processor 1510 is used to execute the various steps and / or processes of the above method embodiments corresponding to the third device.

[0205] It should be understood that the aforementioned processor can be one or more chips. For example, the processor can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0206] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0207] According to the method provided in the embodiments of this application, this application also provides a processor, including: an input circuit, an output circuit, and a processing circuit. The processing circuit is used to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the method described in the embodiments of this application.

[0208] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0209] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0210] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0211] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned first device, second device, and third device.

[0212] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the first device, the second device, and the third device in any of the foregoing method embodiments.

[0213] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code, which, when run on a computer, causes the computer to execute the various steps or processes performed by the first device, second device, and third device in any of the foregoing method embodiments.

[0214] The computer-readable storage medium may be the aforementioned volatile memory or non-volatile memory, or it may include both volatile memory and non-volatile memory.

[0215] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0216] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated.

[0217] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0218] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0219] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A communication method characterized by comprising: Applied to a first device, the method includes: Receive a first message from a second device; the first message includes first length information, which is used to indicate the length of the scheduled second message; A second message is sent to the second device based on the first length information. The second message includes first indication information. The first indication information is used to indicate that the first device does not support data segmentation transmission, or the first indication information is used to indicate whether the first device supports data segmentation transmission.

2. The method of claim 1, wherein, The first indication information indicates that the first device does not support data segmentation transmission, which means: The second message includes fourth length information, and the fourth length information is greater than the third length information; the fourth length information is used to indicate the length of the data to be sent by the first device, and the third length information is equal to the first length information minus the length of the second message header.

3. The method according to claim 1, characterized in that, The first indication information indicates that the first device does not support data segmentation transmission, which means: The second message includes a third indication information and a second length information. The third indication information indicates that there is data to be transmitted in addition to this scheduling, and the second length information is a preset value.

4. The method according to claim 1, characterized in that, The first indication information indicates whether the first device supports data segmentation transmission, meaning: The second message includes a field carrying the first indication information. When the first indication information is a third value, it indicates that the first device does not support data segmentation transmission; when the first indication information is a fourth value, it indicates that the first device supports data segmentation transmission.

5. The method according to claim 1, characterized in that, The first indication information is used to indicate whether the first device supports data segmentation transmission, and the segmentation type to which the data encapsulated in the second message belongs; When the first indication information is the fifth value, it indicates that the first device does not support data segmentation transmission; When the first indication information is the sixth value, it indicates that the first device supports data segmentation transmission, and the data encapsulated in the second message is not the last segment; When the first indication information is the seventh value, it indicates that the first device supports data segmentation transmission, and the data encapsulated in the second message is the last segment; When the first indication information is the eighth value, it indicates that the first device supports data segmentation transmission, and the data encapsulated in the second message has not been segmented.

6. The method according to claim 1, characterized in that, The first indication information indicates whether the first device supports data segmentation transmission, meaning: The second message includes message type information, which indicates the format of the second message; When the message type information is the ninth value, it indicates that the first device does not support data segmentation transmission; When the message type information is the tenth value, it indicates that the first device supports data segmentation transmission.

7. The method according to claim 1, characterized in that, The first indication information indicates whether the first device supports data segmentation transmission, meaning: The first indication information is represented by the length of the second message; wherein, if the length of the second message is less than the length information of the first message, it indicates that the first device does not support data segmentation transmission, and if the length of the second message is greater than or equal to the length information of the first message, it indicates that the first device supports data segmentation transmission.

8. The method according to any one of claims 1, 3-7, characterized in that, If the first device does not support data segmentation transmission, the second message also includes fourth length information, which is used to indicate the length of the data to be sent by the first device.

9. A communication method, characterized in that, Applied to a second device, the method includes: Send a first message to the first device; the first message includes first length information, which is used to indicate the length of the scheduled second message; A second message is received from the first device, the second message including first indication information; the first indication information is used to indicate that the first device does not support data segmentation transmission, or the first indication information is used to indicate whether the first device supports data segmentation transmission.

10. The method according to claim 9, characterized in that, The first indication information indicates that the first device does not support data segmentation transmission, which means: The second message includes fourth length information, and the fourth length information is greater than the third length information; the fourth length information is used to indicate the length of the data to be sent by the first device, and the third length information is equal to the first length information minus the length of the second message header.

11. The method according to claim 9, characterized in that, The first indication information indicates that the first device does not support data segmentation transmission, which means: The second message includes a third indication information and a second length information. The third indication information indicates that there is data to be transmitted in addition to this scheduling, and the second length information is a preset value.

12. The method according to claim 9, characterized in that, The first indication information indicates whether the first device supports data segmentation transmission, meaning: The second message includes a field carrying the first indication information. When the first indication information is a third value, it indicates that the first device does not support data segmentation transmission; when the first indication information is a fourth value, it indicates that the first device supports data segmentation transmission.

13. The method according to claim 9, characterized in that, The first indication information is used to indicate whether the first device supports data segmentation transmission, and the segmentation type to which the data encapsulated in the second message belongs; When the first indication information is the fifth value, it indicates that the first device does not support data segmentation transmission; When the first indication information is the sixth value, it indicates that the first device supports data segmentation transmission, and the data encapsulated in the second message is not the last segment; When the first indication information is the seventh value, it indicates that the first device supports data segmentation transmission, and the data encapsulated in the second message is the last segment; When the first indication information is the eighth value, it indicates that the first device supports data segmentation transmission, and the data encapsulated in the second message has not been segmented.

14. The method according to claim 9, characterized in that, The first indication information indicates whether the first device supports data segmentation transmission, meaning: The second message includes message type information, which indicates the format of the second message; When the message type information is the ninth value, it indicates that the first device does not support data segmentation transmission; When the message type information is the tenth value, it indicates that the first device supports data segmentation transmission.

15. The method according to claim 9, characterized in that, The first indication information indicates whether the first device supports data segmentation transmission, meaning: The first indication information is represented by the length of the second message; wherein, if the length of the second message is less than the length of the first message, it indicates that the first device does not support data segmentation transmission, and if the length of the second message is greater than or equal to the length of the first message, it indicates that the first device supports data segmentation transmission.

16. The method according to any one of claims 9, 11-15, characterized in that, If the first device does not support data segmentation transmission, the second message also includes fourth length information, which is used to indicate the length of the data to be sent by the first device.

17. A communication method, characterized in that, Applied to a first device, the first device supporting segmented data transmission, the method includes: Receive a first message from a second device; the first message includes first length information, which is used to indicate the length of the scheduled second message; A second message is sent to the second device based on the first length information; the second message includes a first length field and third indication information. When the data encapsulated in the second message is the first segment, the third indication information indicates that there is data to be transmitted in addition to this scheduling; the first length field is used to carry the fourth length information, which is used to indicate the length of the data to be sent by the first device; or, When the data encapsulated in the second message is any segment other than the last segment, the third indication information indicates that there is data to be transmitted in addition to this scheduling; the first length field is used to carry a preset value.

18. A communication method, characterized in that, Applied to a second device, the method includes: A first message is sent to a first device; the first message includes first length information, which is used to indicate the length of a scheduled second message; the first device supports data segmentation for transmission. Receive a second message from the first device; the second message includes a first length field and third indication information; When the data encapsulated in the second message is the first segment, the third indication information indicates that there is data to be transmitted in addition to this scheduling; the first length field is used to carry the fourth length information, which is used to indicate the length of the data to be sent by the first device; or, When the data encapsulated in the second message is any segment other than the last segment, the third indication information indicates that there is data to be transmitted in addition to this scheduling; the first length field is used to carry a preset value.

19. A communication method, characterized in that, Applied to a third device, the method includes: Send a fourth message to the second device, the fourth message including the first data; Receive a third message from the second device, the third message including fourth indication information, or the third message including second data and fourth indication information, the second data being feedback data of the first data, and the fourth indication information being used to indicate the number of times the second device sends the first data to the first device.

20. The method according to claim 19, characterized in that, Also includes: Based on the fourth indication information, N decryption parameters [x, x+N-1] are determined, where x is the initial value of the decryption parameter and N is the number of times the second device sends the first data to the first device; The N decryption parameters are used as input parameters to decrypt the second data to obtain the original plaintext data.

21. A communication method, characterized in that, Applied to a second device, the method includes: Send a first message to the first device, the first message including first data; Receive a second message from the first device, the second message including second data, the second data being feedback data of the first data; A third message is sent to a third device, the third message including a fourth indication information, or the third message including the second data and the fourth indication information, the fourth indication information being used to indicate the number of times the second device sends the first data to the first device, the fourth indication information being used to narrow the value range of the decryption parameter.

22. A communication device, characterized in that, The device includes a processor and a memory, wherein the memory stores instructions, and when the processor executes the instructions, the communication device performs the method as described in any one of claims 1-21.

23. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, they cause the computer to perform the method as described in any one of claims 1-21.