Communication method and device

Abstract

The present application provides a communication method and a device. A first device sends a first data portion of first data to a second device; the second device sends a data amount of the first data portion and / or storage position information of the first data to the first device; and the first device sends a second data portion of the first data to the second device, wherein a starting position of the second data portion in the first data is determined on the basis of the data amount of the first data portion and the storage position information of the first data. The first device does not need to store one or more of storage position information of data to be transmitted (i.e., the first data) and / or a data amount of part of data having been transmitted (i.e., the first data portion), the second device informs the first device of the information, and the first device can determine, on the basis of the information, a starting position of a remaining data portion to be transmitted (i.e., the second data portion), thereby saving the storage overhead of the first device, and improving the continuity of data transmission.

Description

A communication method and apparatus

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202410952170.3, filed on July 15, 2024, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0004] The Internet of Things (IoT) technology has been introduced into wireless communication systems. In IoT, tags can act as terminal devices, base stations as readers, and tags can communicate with readers. Tags are passive or semi-active devices, and typical applications include logistics, warehousing, industrial manufacturing, identification, and environmental monitoring.

[0005] Given the small size of the tags and the limited amount of electricity they can store, their transmission and storage capabilities are both limited. Therefore, improving the transmission performance of the tags is an issue that needs to be considered. Summary of the Invention

[0006] This application provides a communication method and apparatus for improving the transmission performance of tags.

[0007] Firstly, this application provides a communication method, which can be executed by a first device, or by other devices including the functions of the first device, or by a chip system (which can also be replaced by a chip) or other functional module, wherein the chip system or functional module is capable of implementing the functions of the first device, and the chip system or functional module is, for example, disposed in the first device. The first device may be a tag, a device, or a terminal device. Taking the execution of the method by the first device as an example: the first device sends a first message, the first message including a first portion of data in first data; the first device receives first information, the first information including the data volume of the first portion of data and / or the storage location information of the first data; the first device sends a second message, the second message including a second portion of data in the first data, wherein the starting position of the second portion of data in the first data is determined based on the data volume of the first portion of data and the storage location information of the first data.

[0008] In this implementation, the first device does not need to store one or more of the storage location information of the data to be transmitted (e.g., the first data) and / or the amount of data of the partially transmitted data (e.g., the first part of the data). The second device informs the first device of this information, and the first device can determine the starting position of the remaining data to be transmitted (e.g., the second part of the data) based on this information. This can save the storage overhead of the first device and improve the continuous transmission of data.

[0009] In one possible implementation, the first device may also store the data volume of the first portion of data or the storage location information of the first data. For example, the first device stores the data volume of the first portion of data, and the first information includes the storage location information of the first data. As another example, the first device stores the storage location information of the first data, and the first information includes the data volume of the first portion of data.

[0010] In one possible implementation, the storage location information of the first data is included in the downlink command.

[0011] In one possible implementation, before sending the first message, the first device may also receive a downlink command, the downlink command including storage location information of the first data; in addition, the first message includes the downlink command.

[0012] In this implementation, during data transmission, the second device sends a downlink command to the first device again. The first device does not need to save the downlink command, thus saving storage overhead. In one possible implementation, the first device may also send a third message to the second device. This third message indicates that: the first portion of data is not the last segmentation, or the first data transmission is incomplete, or the first portion of data is undelivered data, or there is first data to be transmitted, or the first portion of data is a part of the first data, and requests continued data transmission. For example, the third message is included in the first message. Another example is sending the third message after sending the first message and before receiving the first message.

[0013] In this implementation, the first device can know whether the first data has been transmitted successfully and inform the second device of the transmission status so that the second device can take appropriate action based on the status.

[0014] In one possible implementation, the first device receives second information before receiving the first information, the second information being used to indicate triggering random access. Further optionally, the first device sends identification information for contention resolution and the third information to the second device.

[0015] In this implementation, the first device can transmit the first data during two or more random access processes.

[0016] In one possible implementation, the third information includes a first identifier, which is used to identify the first device.

[0017] In this implementation, the first identifier can be associated with the first device for segmented transmission, and the first identifier can implicitly indicate that the first part of the data is not the last part of the data, or that the first data has not been completely transmitted.

[0018] In one possible implementation, the first device may also send a fourth message to the second device, the fourth message indicating that: the first portion of data is the last segmentation, or the first data has been transmitted completely, or the second portion of data is data that can be delivered, or the first data is data that can be delivered. For example, the second message includes the fourth message.

[0019] In one possible implementation, after sending the first message and before sending the second message, the first device may also receive second information, which is used to trigger random access; the first device does not respond to the second information. For example, the second information may be QueryRep signaling or Query signaling.

[0020] In this implementation, before the first data transmission is completed, the first device, upon receiving a QueryRep signaling or a Query signaling, will not initiate the next random access, thus avoiding disruption by other situations and maintaining the state of transmitting the first data.

[0021] In one possible implementation, the first device may instruct the second device on the time to transmit the second portion of data. For example, the first device may instruct the second device on the time to transmit the second portion of data while or after transmitting the first portion of data. For instance, the first device may instruct the second device on a first time, indicating that transmission of the second portion of data will begin at that first time. As another example, the first device may instruct the second device on a first duration, indicating that transmission of the second portion of data will begin after a first duration following a certain time (e.g., the time the instruction was received, or the time the first portion of data was received).

[0022] In one possible implementation, the first device receives an instruction from the second device indicating the time for transmitting the second portion of data. For example, the first device receives the instruction from the second device indicating the time for transmitting the second portion of data after transmitting the first portion of data. This instruction can be received before the first device receives the first information; it can also be received while receiving the first information; or it can be received after receiving the first information. For example, if the first device receives the second time instruction from the second device, it indicates that transmission of the second portion of data will begin at that second time. As another example, if the first device receives the second duration instruction from the second device, it indicates that transmission of the second portion of data will begin after a second duration following a certain time (e.g., the time the instruction was received, or the time the first portion of data was transmitted).

[0023] In one possible implementation, the first duration or the second duration may also indicate the charging duration, the sleep duration, the maximum sleep duration, the minimum sleep duration, the resume waiting time, the minimum segmented waiting time, or the maximum segmented waiting time, etc.

[0024] In one possible implementation, the first device may also receive one or more of the following information: a first identifier, which identifies the first device; and the amount of data in the transport block.

[0025] In one possible implementation, the first message further includes a first identifier for identifying the first device; and / or, the second message further includes a first identifier for identifying the first device.

[0026] In this implementation, when the first device transmits the first part of data and / or the second part of data, it carries a first identifier. The second device can determine which device sent the data through the first identifier, which can then facilitate the second device or the core network equipment to reassemble the first part of data and the second part of data.

[0027] Secondly, this application provides a communication method that can be executed by a second device, or by other devices including the functions of the second device, or by a chip system (which can also be replaced by a chip) or other functional module, which can realize the functions of the second device, and is, for example, disposed in the second device. The second device can be a reader, a network device, or a terminal device. Taking the execution of the method by the second device as an example: the second device receives a first message from a first device, the first message including a first portion of data in first data; the second device sends first information to the first device, the first information indicating the data volume of the first portion of data and / or the storage location information of the first data; the second device receives a second message from the first device, the second message including a second portion of data in the first data, the starting position of the second portion of data in the first data being determined based on the data volume of the first portion of data and the storage location information of the first data.

[0028] In this implementation, the first device does not need to store one or more of the storage location information of the data to be transmitted (e.g., the first data) and / or the amount of data of the partially transmitted data (e.g., the first part of the data). The second device informs the first device of this information, and the first device can determine the starting position of the remaining data to be transmitted (e.g., the second part of the data) based on this information, thereby improving the continuous transmission of data.

[0029] In one possible implementation, the storage location information of the first data is included in the downlink command.

[0030] In one possible implementation, before receiving the first message, the second device may also send a downlink command, the downlink command including the storage location information of the first data; in addition, the first message includes the downlink command.

[0031] In this implementation, during data transmission, the second device sends a downlink command to the first device again. The first device does not need to save the downlink command, which can save the storage overhead of the first device.

[0032] In one possible implementation, the second device can determine that the amount of data in the first portion of the data is less than the amount of data in the first data.

[0033] In this implementation, the second device can determine whether the first data has been completely transmitted based on the amount of data in the first part of the data. If it is determined that the first data has not been completely transmitted, the second device can send first information to the first device in order to transmit some of the remaining data.

[0034] In one possible implementation, the second device may also receive third information from the first device; the third information indicates that: the first portion of data is not the last segmentation, or the first data has not been fully transmitted, or the first portion of data is undelivered data, or there is first data to be transmitted, or the first portion of data is part of the first data, and requests continued data transmission. For example, the third information is included in the first message. As another example, after receiving the first message from the first device, and before sending the first information to the first device, the second device receives the third information from the first device.

[0035] In one possible implementation, the second device may send the first information to the first device based on the third information.

[0036] In this implementation, the first device informs the second device whether the first data transmission is complete. If it is determined that the first data transmission is incomplete, the second device can send a first message to the first device to transmit some of the remaining data. By having the first device inform the second device whether the first data transmission is complete, the processing complexity of the second device can be simplified.

[0037] In one possible implementation, the second device sends a second message before sending the first message, the second message indicating the triggering of random access. Further optionally, the second device receives identification information from the first device for contention resolution and the third message.

[0038] In this implementation, the first device can transmit the first data during two or more random access processes.

[0039] In one possible implementation, the third information includes a first identifier, which is used to identify the first device.

[0040] In this implementation, the first identifier can be associated with the first device for segmented transmission, and the first identifier can implicitly indicate that the first part of the data is not the last part of the data, or that the first data has not been completely transmitted.

[0041] In one possible implementation, the second device may also receive fifth information from the core network equipment, the fifth information being used to instruct continued data transmission.

[0042] In one possible implementation, the second device may send the first information to the first device based on the fifth information.

[0043] In this implementation, the second device determines whether to send the first information to the first device based on the instructions from the core network, which simplifies the processing complexity of the second device.

[0044] In one possible implementation, the second device may also send the first part of the data and / or the second part of the data to the core network equipment. For example, the second device may send the first part of the data and the second part of the data in the same message or different messages. As another example, the second device may reassemble / merge the first part of the data and the second part of the data before sending them to the core network equipment.

[0045] In this implementation, the second device sends the first part of the data to the core network device. On the one hand, the core network device can determine whether the first data has been transmitted completely based on the first part of the data, and then instruct the second device to continue transmission or complete transmission. On the other hand, sending the first part of the data and the second part of the data to the core network device can enable the core network device to implement one or more services based on the first part of the data and the second part of the data.

[0046] In one possible implementation, the second device may also receive fourth information from the first device, the fourth information indicating that: the first portion of data is the last segmentation, or the first data has been transmitted completely, or the second portion of data is data that can be submitted, or the first data is data that can be submitted. For example, the second message includes the fourth information.

[0047] In one possible implementation, the second device may receive an indication from the first device of the time for transmitting the second portion of data. For example, the second device receives a first time indication from the first device, indicating that transmission of the second portion of data will begin at the first time. As another example, the second device receives a first duration indication from the first device, indicating that transmission of the second portion of data will begin after a first duration following a certain time (e.g., the time the indication information is received, or the time the first portion of data is received).

[0048] In another possible implementation, the second device may instruct the first device on the time to send the second portion of data. For example, after the second device receives the first portion of data, it may instruct the first device on the time to send the second portion of data. This instruction can be given before the second device sends the first information, while the second device is sending the first information, or after the second device has sent the first information.

[0049] For example, the second device instructs the first device to a second time, indicating that the transmission of the second portion of data will begin at the second time. As another example, the second device instructs the first device to a second duration, indicating that the transmission of the second portion of data will begin after a second duration following a certain time (e.g., the time the instruction was received, or the time the first portion of data was transmitted).

[0050] In one possible implementation, the first duration or the second duration may also indicate the charging duration, the sleep duration, the maximum sleep duration, the minimum sleep duration, the resume waiting time, the minimum segmented waiting time, or the maximum segmented waiting time, etc.

[0051] In one possible implementation, the second device may also send one or more of the following information to the first device: a first identifier, which identifies the first device; and the amount of data in the transport block.

[0052] In one possible implementation, the first message further includes a first identifier for identifying the first device; and / or, the second message further includes a first identifier for identifying the first device.

[0053] In this implementation, when the first device transmits the first part of data and / or the second part of data, it carries a first identifier. The second device can determine which device sent the data through the first identifier, which can then facilitate the second device or the core network equipment to reassemble the first part of data and the second part of data.

[0054] Thirdly, this application provides a communication method that can be executed by a core network device, or by other devices including the functions of a core network device, or by a chip system (which can also be replaced by a chip) or other functional module, wherein the chip system or functional module is capable of implementing the functions of the core network device, and such chip system or functional module is, for example, disposed within the core network device. Taking the execution of this method by a core network device as an example: the core network device sends fifth information to a second device, the fifth information being used to indicate continued data transmission.

[0055] In one possible implementation, the core network device may further receive a first portion of the first data from the second device, and based on the first portion of the data, send fifth information to the second device. For example, the core network device determines that the amount of the first portion of the data is less than the amount of the first data, and thus determines to send the fifth information to the second device. As another example, the core network device determines that the content of the first portion of the data is not the complete content of the first data, and thus determines to send the fifth information to the second device.

[0056] In one possible implementation, the core network device receives a first portion of data from the first data and / or a second portion of data from the first data from the second device.

[0057] Fourthly, this application provides a communication method that can be executed by a first device, or by another device including the functions of the first device, or by a chip system (which can also be replaced by a chip) or other functional module, wherein the chip system or functional module is capable of implementing the functions of the first device, and the chip system or functional module is, for example, disposed in the first device. The first device may be a tag, a device, or a terminal device. Taking the execution of the method by the first device as an example: the first device sends a first message, the first message including a first portion of data in first data; the first device receives indication information, the indication information being used to indicate / trigger an access opportunity; the first device sends identification information for contention resolution to a second device; the first device receives indication information from the second device indicating successful contention resolution; the first device sends a second message to the second device, the second message including a second portion of data in the first data, the starting position of the second portion of data in the first data being determined based on the data volume of the first portion of data and the storage location information of the first data.

[0058] In this implementation, the first device performs segmented data transmission during multiple connections (connection refers to the first device connecting to the second device).

[0059] In one possible implementation, after receiving indication information for indicating / triggering an access opportunity, the first device receives first information from the second device, the first information including the amount of data in the first part of the data and / or the storage location information of the first data.

[0060] In this implementation, the first device does not need to store one or more of the storage location information of the data to be transmitted (e.g., the first data) and / or the amount of data of the partially transmitted data (e.g., the first part of the data). The second device informs the first device of this information, and the first device can determine the starting position of the remaining data to be transmitted (e.g., the second part of the data) based on this information. This can save the storage overhead of the first device and improve the continuous transmission of data.

[0061] In one possible implementation, the first device may also store the data volume of the first portion of data and / or the storage location information of the first data. For example, the first device stores the data volume of the first portion of data, and the first information includes the storage location information of the first data. As another example, the first device stores the storage location information of the first data, and the first information includes the data volume of the first portion of data.

[0062] In one possible implementation, the first device sends indication information to the second device, the indication information indicating that the first data transmission has not been completed. For example, the indication information includes a first identifier used to identify the first device. For example, the indication information and the identifier information for contention resolution are in the same message. For example, the first device sends the indication information after sending the identifier information for contention resolution.

[0063] In this implementation, the first identifier can be associated with the first device for segmented transmission, and the first identifier can implicitly indicate that the first data has not been transmitted in complete.

[0064] In one possible implementation, the second message includes indication information indicating whether the data being transmitted is part of or not all of the first data. For example, the indication information includes a first identifier that identifies the first device. In this implementation, the first identifier can be associated with the first device for segmented transmission, and the first identifier can implicitly indicate continued data transmission.

[0065] In one possible implementation, the first device may also receive one or more of the following information: a first identifier, which identifies the first device; and the amount of data in the transport block.

[0066] In one possible implementation, the first message further includes a first identifier for identifying the first device; and / or, the second message further includes a first identifier for identifying the first device.

[0067] In this implementation, when the first device transmits the first part of data and / or the second part of data, it carries a first identifier. The second device can determine which device sent the data through the first identifier, which can then facilitate the second device or the core network equipment to reassemble the first part of data and the second part of data.

[0068] Fifthly, this application provides a communication method that can be executed by a second device, or by other devices including the functions of the second device, or by a chip system (which can also be replaced by a chip) or other functional module, which is capable of implementing the functions of the second device, and which is, for example, disposed in the second device. The second device can be a reader, a network device, or a terminal device. Taking the execution of the method by the second device as an example: the second device receives a first message from a first device, the first message including a first portion of data in first data; the second device sends indication information to the first device, the indication information being used to indicate / trigger an access opportunity; the second device sends indication information of successful contention resolution to the first device; the second device receives a second message from the first device, the second message including a second portion of data in the first data, the starting position of the second portion of data in the first data being determined based on the data volume of the first portion of data and the storage location information of the first data.

[0069] In this implementation, the first device performs segmented data transmission during multiple connections (connection refers to the first device connecting to the second device).

[0070] In one possible implementation, after sending indication information to the first device to indicate / trigger an access opportunity, the second device sends first information to the first device, the first information including the data volume of the first part of the data and / or the storage location information of the first data.

[0071] In this implementation, the first device does not need to store one or more of the storage location information of the data to be transmitted (e.g., the first data) and / or the amount of data of the partially transmitted data (e.g., the first part of the data). The second device informs the first device of this information, and the first device can determine the starting position of the remaining data to be transmitted (e.g., the second part of the data) based on this information. This can save the storage overhead of the first device and improve the continuous transmission of data.

[0072] In one possible implementation, the second device receives indication information from the first device, the indication information indicating that the first data transmission has not been completed. For example, the indication information includes a first identifier used to identify the first device. For example, the indication information and the identifier information for contention resolution are in the same message. For example, the second device receives the indication information after receiving the identifier information for contention resolution.

[0073] In this implementation, the first identifier can be associated with the first device for segmented transmission, and the first identifier can implicitly indicate that the first data has not been transmitted in complete.

[0074] In one possible implementation, the second message includes indication information indicating whether the transmitted data is a portion of the first data or not the complete first data. For example, the indication information includes a first identifier to identify the first device. In this implementation, the first identifier can be associated with the first device for segmented transmission, and the first identifier can implicitly indicate continued data transmission.

[0075] In one possible implementation, the first device may also receive one or more of the following information: a first identifier, which identifies the first device; and the amount of data in the transport block.

[0076] In one possible implementation, the first message further includes a first identifier for identifying the first device; and / or, the second message further includes a first identifier for identifying the first device.

[0077] In this implementation, when the first device transmits the first part of data and / or the second part of data, it carries a first identifier. The second device can determine which device sent the data through the first identifier, which can then facilitate the second device or the core network equipment to reassemble the first part of data and the second part of data.

[0078] Sixthly, this application provides a communication method that can be executed by a core network device, or by other devices including the functions of a core network device, or by a chip system (which can also be replaced by a chip) or other functional module, which is capable of implementing the functions of the core network device, and which is, for example, disposed in the core network device. Taking the execution of the method by a core network device as an example: the core network device receives a first data amount from a second device, the first data amount being the maximum data amount suggested or allowed by the second device for the first device to transmit data each time, or the maximum data amount allowed for each device to transmit data each time.

[0079] In one possible implementation, the core network device sends a first downlink command to the first device via forwarding from the second device, wherein the storage area information in the first downlink command is related to the first data volume.

[0080] The core network equipment can determine how many bits or bytes to divide the entire application layer (or non-access layer) data into for segmented transmission based on the first data volume.

[0081] In one possible implementation, the first data volume and coverage level and / or modulation and coding scheme (MCS) configuration parameters are related.

[0082] In a seventh aspect, a communication device is provided, which can be the first device described in the preceding aspects. The communication device possesses the functions of the first device. The communication device is, for example, a functional module of the first device, such as a baseband device or a chip system. Alternatively, the communication device can be the second device described in the preceding aspects. The communication device possesses the functions of the second device. The communication device is, for example, a functional module of the second device, such as a baseband device or a chip system. Alternatively, the communication device can be the core network equipment described in the preceding aspects. The communication device possesses the functions of the core network equipment. The communication device is, for example, a functional module of the core network equipment, such as a baseband device or a chip system.

[0083] In one optional implementation, the communication device includes a baseband device and a radio frequency device. In another optional implementation, the communication device includes a processing unit (sometimes also called a processing module) and a transceiver unit (sometimes also called a transceiver module). The transceiver unit is capable of transmitting and receiving functions. When the transceiver unit performs the transmitting function, it can be called a transmitting unit (sometimes also called a transmitting module), and when the transceiver unit performs the receiving function, it can be called a receiving unit (sometimes also called a receiving module). The transmitting unit and the receiving unit can be the same functional module, which is called the transceiver unit and can perform both transmitting and receiving functions; or, the transmitting unit and the receiving unit can be different functional modules, and the transceiver unit is a collective term for these functional modules.

[0084] In one possible implementation, the communication device further includes a storage unit (sometimes also called a storage module), and the processing unit is configured to couple with the storage unit and execute programs or instructions in the storage unit to enable the communication device to perform the functions of the first device described in the foregoing aspects, or to perform the functions of the second device described in the foregoing aspects, or to perform the functions of the core network equipment described in the foregoing aspects.

[0085] Eighthly, a communication device is provided, including an interface circuit and a processor, and optionally, a memory. The memory stores a computer program. The processor is coupled to the memory and the interface circuit. When the processor reads the computer program or instructions, it causes the communication device to execute the method performed by the first device in the above-described aspects, or the method performed by the second device in the above-described aspects, or the method performed by the core network device in the above-described aspects. For example, the interface circuit is used to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device. The processor, through logic circuits or executable code instructions, implements the method performed by the first device in the above-described aspects, or the method performed by the second device in the above-described aspects, or the method performed by the core network device in the above-described aspects.

[0086] In one possible implementation, the communication device is a chip or a chip system. The chip system may consist of chips or may include chips and other discrete components.

[0087] In a ninth aspect, a communication device is provided, including a processor, and optionally, a memory; the processor and the memory are coupled; the memory is used to store computer programs or instructions; the processor is used to execute part or all of the computer programs or instructions in the memory, and when the part or all of the computer programs or instructions are executed, to implement the function of a first device in the above aspects, or to implement the function of a second device in the above aspects, or to implement the function of a core network device in the above aspects.

[0088] In one possible implementation, the apparatus may further include a transceiver for transmitting signals processed by the processor or receiving signals input to the processor. The transceiver may perform transmission or reception actions performed by the first apparatus in each aspect, or by the second apparatus in each aspect, or by the core network equipment in each aspect.

[0089] In one possible implementation, the processing unit in the seventh aspect can be implemented by the processor, the storage unit in the seventh aspect can be implemented by the memory, and the transceiver unit in the seventh aspect can be implemented by the transceiver.

[0090] In one possible implementation, the communication device is a chip or a chip system. The chip system may consist of chips or may include chips and other discrete components.

[0091] In a tenth aspect, a computer-readable storage medium is provided for storing a computer program or instructions that, when executed, cause the methods of the foregoing aspects to be implemented.

[0092] Eleventhly, a chip is provided, comprising a processor, which, when executing a computer program or instructions, implements the methods in any possible implementation of any of the first to sixth aspects. Optionally, the chip may further include a memory, which may be composed of chips or may include chips and other discrete devices. The memory is used to store computer programs or instructions.

[0093] In a twelfth aspect, a circuit is provided for performing the methods in any possible implementation of any of the first to sixth aspects described above. The circuit may include a chip circuit. Optionally, the circuit may also be coupled to a memory.

[0094] In a thirteenth aspect, a computer program product containing instructions is provided that, when run on a computer, enables the methods in the foregoing aspects to be implemented.

[0095] In a fourteenth aspect, a communication system is provided, comprising at least two of the first device, the second device, and core network equipment described in the foregoing aspects. For example, the first device and the second device may be implemented using the communication devices described in the seventh, eighth, or ninth aspects. Attached Figure Description

[0096] Figure 1a is a schematic diagram of the structure of a network device provided in an embodiment of this application;

[0097] Figure 1b is a schematic diagram of an O-RAN communication system applicable to an embodiment of this application;

[0098] Figures 2a, 2b, 2c, and 2d are schematic diagrams of a communication system applicable to an embodiment of this application;

[0099] Figures 3, 4, 5, 6, 9, 10, and 11 are schematic flowcharts of a communication method provided in an embodiment of this application.

[0100] Figures 7 and 8 are schematic diagrams of data transmission provided in an embodiment of this application;

[0101] Figure 12 is a schematic diagram of a communication device structure provided in an embodiment of this application;

[0102] Figure 13 is a schematic diagram of a communication device structure provided in an embodiment of this application. Detailed Implementation

[0103] The technical solution of this application can be applied to various wireless communication systems, including but not limited to the fourth generation (4G) system (also known as the long term evolution (LTE) system), the fifth generation (5G) system (also known as the new radio (NR) system), or future mobile communication systems, etc., without any specific limitations.

[0104] Furthermore, the technical solutions provided in this application can be applied to device-to-device (D2D) scenarios, such as NR-D2D scenarios, or to vehicle-to-everything (V2X) communication scenarios, such as NR-V2X scenarios. For example, they can be used in fields such as intelligent driving, assisted driving, or intelligent connected vehicles. As another example, the technical solutions provided in this application can also be applied to factory manufacturing scenarios.

[0105] Furthermore, the technical solutions provided in this application can be applied to scenarios including but not limited to: terrestrial cellular communication, non-terrestrial network (NTN), satellite communication, high altitude platform station (HAPS) communication, integrated access and backhaul (IAB) communication, and reconfigurable intelligent surface (RIS) communication.

[0106] In this embodiment, the network device can be a device in a wireless network, and can also be called a network apparatus or a wireless access network device. For example, the network device can be a radio access network (RAN) node that connects a terminal device to a wireless network, and can also be called an access network device. The network device includes, but is not limited to: base station, evolved NodeB (eNodeB), transmission reception point (TRP), next-generation NodeB (gNB) in a 5th generation (5G) mobile communication system, access network device in an open radio access network (O-RAN), next-generation base station in a 6th generation (6G) mobile communication system, base station in a future mobile communication system, or access node in a wireless fidelity (WiFi) system; or it can be a module or unit that performs part of the functions of a base station, such as a central unit (CU), a distributed unit (DU), a central unit control plane (CU-CP) module, or a central unit user plane (CU-UP) module. Network equipment can be macro base stations, micro base stations, indoor stations, relay nodes, or donor nodes, etc. This application does not limit the specific technology or form of the network equipment.

[0107] In some implementations, network devices can include centralized units (CUs) and distributed units (DUs). This includes RAN devices at CU and DU nodes that separate the protocol layers of the gNB in ​​the NR system. Some protocol layer functions are centrally controlled by the CU, while the remaining partial or complete protocol layer functions are distributed across the DUs, which are then centrally controlled by the CU. Furthermore, the CU can be divided into a control plane (CU-CP) and a user plane (CU-UP). The CU-CP handles control plane functions, primarily including radio resource control (RRC) and the corresponding packet data convergence protocol (PDCP) (i.e., control plane part of PDCP, PDCP-C). The CU-UP handles user plane functions, primarily including the service data adaptation protocol (SDAP) and the corresponding user plane PDCP (i.e., user plane part of PDCP, PDCP-U). The CU-CP and CU-UP are connected via an E1 interface. CU-CP represents the gNB connecting to the core network via the next-generation (NG) interface and to the DU via the F1 interface control plane (i.e., F1-C). CU-UP connects to the DU via the F1 interface user plane (i.e., F1-U). Another possible implementation is that PDCP-C is also located in CU-UP.

[0108] It is understood that CU (including CU-CP or CU-UP) or DU may have different names in different systems, but those skilled in the art will understand their meaning. For example, in an open radio access network (O-RAN or ORAN) system, CU can also be called an open CU (open CU, O-CU), DU can also be called an open DU (open DU, O-DU), CU-CP can also be called O-CU-CP, and CU-UP can also be called O-CU-UP. For ease of description, this application uses CU, CU-CP, CU-UP, and DU as examples. Network devices may also include active antenna units (AAUs). CU implements some of the functions of the gNB, and DU implements some of the functions of the gNB. For example, CU is responsible for handling non-real-time protocols and services, implementing the functions of the RRC layer. DU is responsible for handling physical layer protocols and real-time services, implementing the functions of the radio link control (RLC) layer, media access control (MAC) layer, and physical (PHY) layer. In some deployments, the CU can also be divided into a centralized unit control plane (CU-CP) node and a centralized unit user plane (CU-UP) node. The CU-CP is responsible for control plane functions, while the CU-UP is responsible for user plane functions.

[0109] The terminal device involved in the embodiments of this application can be a wireless terminal device capable of receiving network device scheduling and instruction information. The terminal device can be referred to as a terminal device, or it can also be called user equipment (UE), terminal, mobile station (MS), mobile terminal (MT), etc. The terminal device can be a device that includes wireless communication functions (providing voice / data connectivity to the user). For example, a handheld device with wireless connectivity, or an in-vehicle device, in-vehicle module, etc. Currently, examples of terminal devices include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in vehicle-to-everything (V2X) communication, wireless terminals in vehicle-to-everything (V2X) communication, intelligent vehicles, in-vehicle infotainment systems (or onboard transmitters) (T-boxes), machine-to-machine / machine-type communications (M2M / MTC) terminal devices, and the Internet of Things (IoT). IoT (Internet of Things) terminal devices, etc. For example, terminal devices can be in-vehicle equipment, vehicle equipment, in-vehicle modules, vehicles, on-board units (OBU), roadside units (RSU), T-boxes, chips or systems on chips (SOC), etc. The aforementioned chips or SOCs can be installed in vehicles, OBUs, RSUs or T-boxes.Terminal devices can also be V2X devices, such as smart cars, digital cars, unmanned cars, driverless cars, pilotless cars, autonomous cars, pure electric vehicles (EVs), hybrid electric vehicles (HEVs), range-extended electric vehicles (REEVs), plug-in hybrid electric vehicles (PHEVs), new energy vehicles, and roadside units (RSUs). Terminal devices can also be devices used in device-to-device (D2D) communication, such as electricity meters and water meters.

[0110] Furthermore, in this embodiment, the terminal device can also be an ambient internet of things (A-IoT) device. A-IoT is an important component of future information technology development, and its main technical feature is connecting objects to networks through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection. The A-IoT terminal device can be implemented by a terminal in a cellular network, such as an extremely low-power, extremely low-complexity IoT terminal. Non-contact data communication can be performed between the network device and the A-IoT terminal device, thereby reading information from the A-IoT terminal device and / or writing information that needs to be stored into the A-IoT terminal device.

[0111] An RFID system, composed of network devices (which can be viewed as readers in radio frequency identification (RFID) technology) and passive / semi-passive / active A-IoT terminal devices, can perform tasks such as inventory management, positioning, sensing, and command execution. Typical application scenarios include logistics, warehousing, industrial manufacturing, identification, and environmental monitoring. For example, passive A-IoT terminal devices can also be referred to as passive Internet of Things (IoT) devices.

[0112] Terminal devices can include passive terminal devices, semi-passive terminal devices, and active terminal devices. Passive terminal devices require an excitation signal from the network device; some energy is used for internal processing such as encoding / decoding and modulation / demodulation. This excitation signal can also serve as a carrier wave for reflecting uplink information from the terminal device. Semi-passive terminal devices contain a battery, and internal processing such as encoding / decoding and modulation / demodulation can be performed using the battery, but they still require the network device to send an excitation signal as a reflected carrier. Active terminal devices contain a battery and perform encoding / decoding and modulation / demodulation. Active terminal devices include a radio transmitter and can actively send data to other devices.

[0113] In one implementation, terminal devices in A-IoT can be divided into three categories:

[0114] One type of device (which can be referred to as Device 1): ~1μW peak power consumption; the device has neither downlink (DL) amplification nor uplink (UL) amplification; the device's UL transmission is backscattered on an externally provided carrier. Optionally, this type of device has energy storage. Optionally, this type of device is similar to a passive A-IoT terminal.

[0115] Another type of device (which may be referred to as device 2a): Peak power consumption ≤ several hundred μW; the device has DL amplification and / or UL amplification functions. The device's UL transmission is backscattered on an externally provided carrier. Optionally, this type of device has energy storage. Optionally, this type of device is similar to a semi-passive A-IoT terminal.

[0116] Another type of device (which can be referred to as device 2b) is similar to an active A-IoT terminal: ≤ several hundred μW peak power consumption, with DL amplification and / or UL amplification functions. The UL transmission of the device is generated internally. Optionally, this type of device has energy storage. Optionally, this type of device is similar to an active A-IoT terminal.

[0117] In addition, the network devices involved in the embodiments of this application may be referred to as readers (or readers-writers), radio access network (RAN) devices, open radio access network (O-RAN) devices or any component node in O-RAN, a node B (gNB) that continues to evolve from a transmission reception point, a transmission reception point (TRP), an evolved node B (eNB), a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., home evolved NodeB, or home Node B, HNB), a base band unit (BBU), or a wireless fidelity (Wi-Fi) access point (AP), etc.

[0118] Figure 1a illustrates an exemplary structural diagram of a network device according to an embodiment of this application. As shown in Figure 1a, the network device may include a centralized unit (CU) node, a distributed unit (DU) node, or a RAN device including both CU and DU nodes. The RAN device including CU and DU nodes separates the protocol layers of the eNB in ​​a long term evolution (LTE) system. Some protocol layer functions are centrally controlled by the CU, while the remaining partial or complete protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0119] In some examples, the CU is a logical node carrying the radio resource control (RRC) layer, service data adaptation protocol (SDAP) layer, packet data convergence protocol (PDCP) layer, and other control functions of the access network equipment. The CU connects to network nodes such as the core network through interfaces, which can be interfaces such as E2 interfaces. Optionally, the CU may have some core network functions. The CU (e.g., PDCP layer and higher layers) connects to the DU (e.g., RLC layer and lower layers) through interfaces, which can be interfaces such as F1 interfaces. In some examples, these interfaces (e.g., F1 interfaces) can provide control plane (C-Plane) and user plane (U-Plane) functions (e.g., interface management, system information management, UE context management, RRC message transmission, etc.). F1AP is the application protocol of the F1 interface, defining the F1 signaling procedures in some examples. The F1 interface supports control plane F1-C and user plane F1-U.

[0120] In some examples, the CU can be split into CU-CP (control unit-control plane) and CU-UP (control unit-user plane). CU-CP is a logical node carrying the RRC layer and PDCP-C (control plane part of PDCP) layer, used to implement the CU's control plane functions. CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be access and mobility function (AMF) network elements, such as the access and mobility management function (AMF) in a 5G system. AMF network elements are responsible for mobility management in the mobile network, such as terminal device location updates, terminal device registration with the network, and terminal device handover. CU-UP is a logical node carrying the SDAP layer and PDCP-U (user plane part of PDCP) layer, used to implement the CU's user plane functions. CU-UP can interact with network elements in the core network used to implement user plane functions. These network elements in the core network, such as the UPF (user plane function) in a 5G system, are responsible for data forwarding and receiving in terminal devices. The above configuration of CU and DU is just an example; you can also configure the functions of CU and DU as needed.

[0121] In some examples, the DU is a logical node that carries the radio link control (RLC) layer, medium access control (MAC) layer, higher physical layer (Higher PHY) layer, and other functions. In some examples, the DU can control at least one radio unit (RU). The DU connects to the RU through interfaces, which can be fronthaul interfaces.

[0122] In some examples, the RU is a logical node that carries both lower physical layer (PHY) and radio frequency (RF) processing. In other examples, the RU can be a 3GPP transmission reception point (TRP), a remote radio head (RRH), or other similar entities.

[0123] The DU and RU can be co-located or not. The DU and RU exchange control plane and user plane information via a lower-layer split-control, user, and synchronization (LLS-CUS) interface through a fronthaul link. LLS-CUS may include LLS-C and LLS-U interfaces that provide the control plane (C-Plane) and user plane (U-Plane), respectively. In some examples, the control plane (C-Plane) refers to real-time control between the DU and RU. The DU and RU exchange management information via an LLS-M interface on the fronthaul link; the management plane (M-Plane) refers to non-real-time management operations between the DU and RU.

[0124] DU and RU can cooperate to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DU and RU can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the PHY layer, and an RU can be configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer can include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer can include another portion of the physical layer's functions that are closer to the mid-RF side.

[0125] In some examples, network devices also include RAN intelligent controllers (RICs). RICs include near-real-time RICs (near-RT RICs) and non-real-time RICs (non-RT RICs).

[0126] Optionally, near real-time RIC and non-real-time RIC can be set up as separate network elements, or they can be part of other devices. For example, near real-time RIC can be set up in network devices, while non-real-time RIC can be set up in operation administration and maintenance (OAM) network elements, cloud servers, core network devices, or other network devices.

[0127] Optionally, the network device can be a single RAN node or include multiple RAN nodes, such as CU and DU. The CU and / or DU can also have one or more AI modules configured. In some examples, the CU can also be split into CU-CP and CU-UP. One or more AI models are configured in the CU-CP and / or CU-UP.

[0128] Figure 1b illustrates an example diagram of an O-RAN system, which may include components other than those shown in the figure. As shown, access network equipment (e.g., an eNB, gNB, or next-generation access network equipment) communicates with the core network (CN) via a backhaul link and with user equipment (UE) via an air interface.

[0129] To facilitate understanding of the embodiments of this application, the communication system shown in Figures 2a to 2d will be used as an example to describe in detail the communication system applicable to the embodiments of this application. This communication system includes at least a first device and a second device. The first device can be understood as a tag, and the second device can be understood as a reader, but this application does not specifically limit this.

[0130] Figures 2a, 2b, and 2c below illustrate a communication system applicable to the embodiments of this application, with the first device as a terminal device and the second device as a network device as examples. Figure 2d illustrates a communication system applicable to the embodiments of this application, with both the first device and the second device as terminal devices as examples.

[0131] As shown in Figure 2a, network devices can communicate bidirectionally with terminal devices. Specifically, the network device can send excitation signals to the terminal device via the forward link to provide power. The terminal device receives the excitation signals sent by the network device and sends reflected signals back to the network device via the reverse link. In this way, the network device can identify the terminal device's ID and perform read and write operations on the terminal device. Uplink and downlink data / signaling exist between the network device and the terminal device.

[0132] As shown in Figure 2b, the communication system includes network devices, intermediate nodes, and terminal devices. Two-way information exchange is possible between the network devices and intermediate nodes, and between the intermediate nodes and terminal devices. Specifically, the network devices can send RFID-related signaling to the intermediate nodes via the fronthaul downlink. The intermediate nodes receive this RFID-related signaling and, based on it, send an excitation signal to the terminal devices via the fronthaul link. The terminal devices send reflected signals via the reverse link; correspondingly, the intermediate nodes can receive these reflected signals from the terminal devices via the reverse link and send them back to the network devices. Furthermore, the network devices and intermediate nodes can exchange other signaling on the fronthaul uplink and fronthaul downlink, such as resource configuration signaling, which will not be detailed here.

[0133] Optionally, the intermediate node can be a repeater, an integrated access and backhaul (IAB) node, or a UE, etc., and this application does not limit this. The intermediate node transmits data and / or signaling between network devices and terminal devices.

[0134] As shown in Figure 2c, the communication system includes network devices, assisting nodes, and terminal devices. While the network devices and terminal devices exchange information bidirectionally, the network devices can also exchange information bidirectionally with the assisting nodes, and the assisting nodes can also exchange information bidirectionally with the terminal devices. For example, the terminal device sends RFID-related signaling to the network device and also to the assisting node. The assisting node then sends the RFID-related signaling back to the network device to assist the terminal device in sending signals and enhance the network device's reception. The same logic applies when the network device sends RFID-related signaling to the terminal device, which will not be elaborated further. In some implementations, the assisting node and the network device can communicate via the Uu interface.

[0135] Optionally, the auxiliary node can be a repeater, IAB, UE, or other device; this application does not limit this. The terminal device sends data / signaling to the network device and receives data / signaling from the auxiliary node; or the network device sends data / signaling to the terminal device and receives data / signaling from the auxiliary node.

[0136] Optionally, the network devices in Figures 2a, 2b and 2c may be base stations or any of the network devices involved in this application as described above, and the terminal devices may be A-IoT terminal devices or any of the terminal devices involved in this application as described above, but this application does not limit them.

[0137] As shown in Figure 2d, terminal device 1 and terminal device 2 can perform bidirectional information interaction. In one possible implementation, the communication between terminal device 1 and terminal device 2 adopts 5G NR technology or 5G sidelink technology.

[0138] Optionally, terminal device 1 in Figure 2d above can be a UE, and terminal device 2 can be an A-IoT terminal device. Alternatively, terminal device 2 can be a UE, and terminal device 1 can be an A-IoT terminal device. Terminal device 1 and terminal device 2 can also be any of the terminal devices involved in this application described above, but this application does not limit them.

[0139] It should be understood that the number of network devices, terminal devices, intermediate nodes, and auxiliary nodes in the above communication system example may be more or less, and this application does not limit this.

[0140] It is worth noting that the first device and the second device can be implemented in multiple ways.

[0141] As another example, the first device and the second device are different terminal devices. Accordingly, the communication link between the first device and the second device can be a communication link between terminal devices, such as a side link.

[0142] As another example, the first device can be called an (Environmental Internet of Things) device (which can be an implementation example of a terminal device), and the second device can be called a reader. Accordingly, the communication link between the first device and the second device can include a device-to-reader (DR or D2R) link and a reader-to-device (RD or R2D) link.

[0143] In the NR system, the RLC layer includes three transmission modes: unacknowledged mode (UM), acknowledged mode (AM), and transparent mode (TM). For UM and AM, the input size of the scheduler at the terminal device's MAC layer is limited. If the amount of data the terminal device needs to transmit exceeds the scheduler's input size, the data must be segmented and reassembled at the RLC layer. For RLC layer segmentation, the terminal device needs to buffer the data to be transmitted, save and record in real-time the sequence number of the next data to be sent, corresponding to the Protocol Data Unit (PDU), until the data transmission is complete.

[0144] For terminal devices such as tags / devices, scenarios requiring segmented transmission often involve low power consumption (e.g., peak power consumption of only 1μW or a few hundred μW). However, tags / devices have limited caching capabilities, lacking sufficient capacity to cache data to be transmitted, and even their ability to store information related to the data to be transmitted is limited. For example, tags / devices cannot, or cannot for extended periods, retain the storage location of the data to be transmitted within the tag / device, nor can they, or cannot, retain the position of already transmitted data within the data to be transmitted. This affects the continuity of data transmission. Therefore, this application provides several methods to address these issues and improve the transmission performance of tags / devices.

[0145] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0146] It is understood that this application does not specifically limit the structure of the execution subject of the method provided in the embodiments of this application. The following description takes the interaction between the first device and the second device as an example. The first device may be a terminal device or a tag, etc., and the first device may also be a chip or module in the terminal device or tag, etc.; the second device may be a network device or a terminal device or a tag, etc., and the first device may also be a chip or module in the network device or a terminal device or a tag, etc.

[0147] The following explanations of some terms or concepts used in the embodiments of this application are provided to facilitate understanding by those skilled in the art.

[0148] The Query signal, also known as access round indication or access round trigger, is not specifically named. This signaling can be used to trigger / indicate at least one access opportunity. For example, it can directly or indirectly indicate the total number of access opportunities, or it can be used to trigger the first access opportunity.

[0149] QueyRep, also known as access occasion indication or access occasion trigger, is a signaling term without specific name restrictions. It can be used to trigger / indicate the next access occasion, or it can be understood as indicating / associating with the boundary of an access occasion; the boundary can be a start or an end.

[0150] The aforementioned access opportunity can also be described as an access timing, access time slot, etc. Each access opportunity may allow the first device to send at least one of the following: access request, identification information for contention resolution, data, etc.

[0151] Paging can be used to instruct an AIoT device to connect to a reader, for example:

[0152] When the reader is a base station / access network device, Paging can be used to indicate that the device is accessing the network.

[0153] When the reader is a terminal device, Paging can be used to instruct the device to connect to the terminal device. Optionally, the device can connect to the network through the terminal device.

[0154] Paging can also be used to trigger / instruct a device to send uplink data, or to trigger / instruct / request a device to perform a first service, wherein the first service may include at least one of the following: paging service, inventory service, command service (such as read, write, deactivate, lock, etc.), positioning service, and sensing service.

[0155] Paging, also known as trigger message / indication, initial trigger message / indication, downlink trigger message / indication, initial downlink trigger message / indication, selection message, etc., is not subject to specific name restrictions and can be triggered by core network elements (such as AMF, or AIoTMF (ambient IoT management function), AIoTF (ambient IoT function)).

[0156] The first device sends identification information for contention resolution to the second device. This identification information is used for contention resolution or to distinguish different terminal devices during random access / contention resolution. The identification information for contention resolution can be a random number (RN), also known as a random access identifier or random ID. For example, RN16; however, the bitbook may not impose any restrictions.

[0157] The second device sends an acknowledgment (ACK) message to the first device, indicating successful contention resolution. Optionally, the ACK may include identification information used for contention resolution to associate the device. The first device can compare the identification information carried in the ACK with the identification information sent by the first device itself; if they match, the contention resolution is considered successful. The ACK message can also be called an access ID response message.

[0158] In one possible implementation, the message that connects the first device to the second device or to the network is called message 1, or AIOT message 1. For example, a message carrying identification information for contention resolution is called message 1, or AIOT message 1.

[0159] In one possible implementation, the message sent by the second device to the first device to confirm successful access is called message 2, or AIOT message 2. For example, the ACK message indicating successful contention resolution is called message 2, or AIOT message 2.

[0160] In one possible implementation, after the first device connects to the second device or to the network, the data-carrying message sent is called message 3, or AIoT message 3. For example, message 3 carries the device ID.

[0161] In this application, "downlink" can also be replaced with "R2D (reader-to-device)" or "RD"; "uplink" can be replaced with "D2R (device-to-reader)" or "DR". For example, the transmission from the second device to the first device is a downlink transmission, and the transmission from the first device to the second device is an uplink transmission.

[0162] "Segmented transmission" refers to data to be transmitted not being transmitted all at once, but rather divided into at least two transmissions, each transmitting a portion of the data. "Segmented" can also be replaced with "partial," "discontinuous," or "incomplete," etc. For example, in this application, the data to be transmitted is first data. First, the first portion of the first data is transmitted, followed by the second portion. Optionally, if the first data is not fully transmitted when the second portion is transmitted, then the third portion is transmitted.

[0163] In this application, "data" can be replaced with data packets, protocol data units (PDUs), messages, signaling, etc.

[0164] In this application, "electronic product code (EPC)" and "device identity (device ID)" are interchangeable. Alternatively, EPC can be a type of device ID or a part of the device identity.

[0165] To better illustrate the embodiments of this application, the methods provided by the embodiments of this application are described below with reference to the accompanying drawings. Unless otherwise specified below, the steps indicated by dashed lines in the accompanying drawings corresponding to the various embodiments of this application are optional steps. It should be noted that the technical details of the multiple embodiments provided in this application can be referenced to each other, each embodiment described below can exist independently, and multiple embodiments can also be combined with each other as an embodiment in the absence of logical errors.

[0166] Example 1:

[0167] Figure 3 is a flowchart illustrating a communication method provided in an embodiment of this application, including the following steps:

[0168] Step 301: The first device sends a first message, the first message including a first portion of the first data.

[0169] Correspondingly, the second device receives the first message.

[0170] Optionally, the first data can be data from a single service, where a single service can be understood as a service triggered by a paging message. For example, a single service might be an inventory check, a command service (such as a read / write service), etc. Of course, it's also possible for the first data to include data from multiple services. For example, the first data could include data from an inventory check (such as device identification information) and data from a command service (such as a read command response message or the data read). Furthermore, the data from a single service can be complete data or partial data. For example, partial data from an inventory check might be partial device identification information, or partial data from a read service might be partial read data. When the first data includes data from multiple services, the data from these multiple services can be complete data from multiple services, partial data from multiple services, or it can include complete data from one or more services and partial data from another one or more services.

[0171] Before sending the first portion of data, the first device accesses the second device or the network. The first device may perform random access to the second device, which can be contention-free random access (CFRA) or contention-based random access (CBRA). Alternatively, the first device may not perform random access and may access the second device or the network via mobile terminated (MT). For example, the second device may send a paging message to the first device, skipping random access and directly triggering the first device to send data. Optionally, the paging message may include query signaling.

[0172] Optionally, the first device generates the first message before sending the first message.

[0173] Step 302: The second device sends the first information, and correspondingly, the first device receives the first information.

[0174] The first information includes the amount of data in the first part of the data and / or the storage location information of the first data.

[0175] In one possible implementation, the first device may store the data volume of the first part of the data, or the end position of the first part of the data within the first data, or the start position of the second part of the data within the first data. The first information in step 302 may include the storage location information of the first data, and optionally, may also include the data volume of the first part of the data.

[0176] In one possible implementation, the first device may store the storage location information of the first data. The first information in step 302 may include the amount of the first portion of data, and optionally, it may also include the storage location information of the first data.

[0177] The amount of data in the first part can be represented by one or more bits. For example, 1 bit can indicate a maximum of two different amounts of data, and 5 bits can indicate a maximum of 64 different amounts of data. For example, the unit of data can be a byte or a bit.

[0178] The amount of data in the first part of the first information (i.e., the amount of data that has been transmitted in the first data) can be replaced with any of the following:

[0179] The data volume of the untransmitted (or yet to be transmitted) data in the first data set, or the data volume of the second data set (this applies when the second data set is the last segment of the first data set), or the position information of the second data set (e.g., the starting position of the second data set within the first data set; the starting position can be a start bit / start byte / start field, etc.), or the position information of the first data set (e.g., the ending position of the first data set within the first data set; the ending position can be an end bit / end byte / end field, etc.), or the segment position, or the breakpoint position. Optionally, the data position information can be indicated by one or more bits, such as 6 bits, 7 bits, etc. The position information of the first or second data set can be understood as index information.

[0180] The storage location information of the first data can refer to the starting position (e.g., the Kth field / byte / bit, where K is an integer greater than or equal to 0) and / or ending position (e.g., the starting position is the Kth field / byte / bit, and the ending position is the Hth field / byte / bit, where H > K) of the first data in a certain storage area (e.g., User Memory or EPC Memory).

[0181] The first part of the data can contain M bits / bytes / fields, where M is an integer greater than or equal to 1.

[0182] For example, using bytes as the unit, L bits can be used to indicate position information with a length not exceeding 2^L bytes. For instance, 7 bits indicate 2^7 = 128 bytes or a data amount not exceeding 128 bytes. Here, 0000000 indicates the position information is the end position of the first byte (or the next bit after that position) or the amount of data already transmitted is 1 byte; 0000001 indicates the position information is the end position of the second byte (or the next bit after that position) or the amount of data already transmitted is 2 bytes; and 1111111 indicates the position information is the end position of the 128th byte (or the next bit after that position) or the amount of data already transmitted is 128 bytes.

[0183] For example, using fields (each field is 16 bits long) as the unit, a length of no more than 2^(L+1) bytes can be indicated using L bits.

[0184] The method of indicating or storing location information is similar to the location information of the data mentioned above.

[0185] Optionally, the storage location information may also include storage area location information, such as indicating 2^M storage areas using M bits. For example, 2 bits can indicate 2^2 = 4 storage areas, where 00 indicates the device ID storage area / EPC storage area / identity storage area, 01 indicates the user (custom) storage area, and 10 and 01 indicate the reserved storage area.

[0186] In one possible implementation, if the second device sends storage location information of the first data to the first device, the storage location information of the first data can be carried in downlink data, a NAS message, or a command. For example, downlink data may include a command that includes the storage location information of the first data. For example, a NAS message may include a command that includes the storage location information of the first data.

[0187] In one possible implementation, the downlink data, NAS message, or command may originate from a second core network device. For example, the core network device sends downlink data, NAS messages, or commands to the second device, and the second device receives the downlink data, NAS messages, or commands from the core network device and then sends them to the first device.

[0188] Additionally, the first piece of information can be a message, a field / element within a message, or multiple fields / elements within a message. The aforementioned "downlink data, or NAS message, or command" can be a portion of the first piece of information, or it can be two separate segments within a message, distinct from the first piece of information.

[0189] Optionally, the second device generates the first information before sending the first information.

[0190] Step 303: The first device sends a second message, which includes a second portion of the data from the first data.

[0191] Correspondingly, the second device receives the second message.

[0192] The first device can determine the starting position (or start position) of the second part of the data within the first data, and select data for transmission starting from that starting position. The starting position of the second part of the data within the first data is either the ending position of the first part of the data within the first data, or the position following the ending position. In other words, the position of the first part of the data (e.g., the ending position) and the position of the second part of the data within the first data (e.g., the start position) are continuous, adjacent, or without interval.

[0193] The following is an example of determining the starting position of the second part of the data within the first part of the data:

[0194] For example, the starting position of the second part of data within the first data is determined based on the data volume of the first part of data and the storage location information of the first data. The first device can determine the starting position of the second part of data within the first data based on the data volume of the first part of data. For example, if the starting position of the first data is the Kth field / byte / bit in the user storage area, and the data volume of the first part of data is M bits / byte / field, then the starting position of the second part of data is the M+K+1th field / byte / bit in the user storage area. For example, if K = 100 bytes and M = 50 bytes, then the starting position of the second part of data is the 151st byte in the user storage area.

[0195] For example, the starting position of the second part of the data within the first data is determined based on the amount of untransmitted data in the first data and the storage location information of the first data. For example, if the ending position of the first data is the Hth field / byte / bit in the user storage area, and the amount of untransmitted data is F bits / byte / field, then the starting position of the second part of the data is the H-F+1th field / byte / bit in the user storage area. For example, if H = 200 bytes and F = 30 bytes, then the starting position of the second part of the data is the 171st byte in the user storage area.

[0196] Optionally, if the first device does not receive the first information or does not receive the first information for a period of time (i.e., step 302 is not executed), the first device may stop transmitting the first data (i.e., step 303 is not executed). Alternatively, the first device may stop transmitting the first data after the battery is depleted or the battery level is below a threshold.

[0197] Optionally, the first device generates the second message before sending the second message.

[0198] In this embodiment, the first device does not need to store one or more of the storage location information of the data to be transmitted (e.g., the first data) and / or the amount of data of the partially transmitted data (e.g., the first part of the data). The second device informs the first device of this information. Based on this information, the first device can determine the starting position of the remaining data to be transmitted (e.g., the second part of the data), which can save the storage overhead of the first device and improve the continuous transmission of data.

[0199] The following provides further details about this embodiment:

[0200] (1) Conditions for triggering data segmentation transmission.

[0201] In one possible implementation, the first device transmits data based on the schedule of the second device. For example, before the first device sends the first data to the second device, the second device indicates the transport block size (TBS) to the first device. If the first device determines that the TBS is less than the data size of the carrier message of the first data, then the first data needs to be transmitted in segments. The first device sends a first portion of the first data to the second device, for example, the data size of the carrier message of the first portion of the data is the TBS.

[0202] The data-bearing message includes the data, for example, the data is first data or first part of data; wherein, the data may be a MAC service data unit (SDU), or a non-access stratum (NAS) PDU, or application layer data, etc.; further optionally, the data-bearing message may also include at least one of the following: message header, frame header (e.g., preamble), postamble, cyclic redundancy check (CRC) sequence, etc.

[0203] In another possible implementation, the first device's current battery level, remaining capacitor capacity, or stored energy is insufficient to transmit the first data, and only a portion of the first data (e.g., the first part of the data) can be transmitted. In one implementation, if the battery level is below a threshold, only a portion of the first data can be transmitted. This threshold can be specified by the protocol or sent by the second device to the first device, such as through a paging message, a query message, a downlink data indication, or an indication message carried in the MAC CE or MAC header; it is not limited.

[0204] In one possible implementation, the first device sends indication information to the second device, which indicates low battery / segmentation request. This indication information could be sent, for example, on RN16. For example, the first device sends the indication information to the second device before sending a first message. For example, the first device sends the indication information to the second device during random access. For example, the indication information can be sent when sending contention resolution identification information, or it can be sent in other steps. Optionally, the indication information may include contention resolution identification information.

[0205] (2) Data transmission path.

[0206] After receiving the first portion of data (e.g., in step 301), the second device can process or use the first portion of data itself. For example, the first device is a terminal device, the second device is also a terminal device, and the first data is sidelink data. Alternatively, after receiving the first portion of data, the second device can send the first portion of data to the core network device.

[0207] Similarly, after receiving the second part of the data (e.g., step 303), the second device can process or use the second part of the data itself, or it can send the second part of the data to the core network device.

[0208] When the second device sends the first and second parts of data to the core network equipment, it can send the first and second parts of data in different messages or in the same message. For example, after receiving the first part of data, the second device can first buffer it. After receiving the second part of data, it can reassemble or merge the first and second parts of data and send the reassembled or merged data to the core network equipment. The second device can identify that the first and second parts of data come from the same device without parsing their specific content.

[0209] (3) The second part of the data is not the last part of the first data. After the first device sends the second part of the data, it sends the third part of the first data.

[0210] If the second part of the data sent in step 303 is not the last segmentation of the first data, then the first data transmission is not complete after step 303. Optionally, the following process may also be included if the first data transmission is not complete after step 303:

[0211] The second device sends at least one of the following to the first device: the amount of data already transmitted (i.e., the sum of the amounts of the first and second parts of data), and the storage location information of the first data. Accordingly, the first device receives this information. This process is similar to step 302 and can be referenced interchangeably. The amount of data already transmitted can be replaced with any of the following: the amount of data not transmitted (or to be transmitted) in the first data, or the amount of data in the third part of data (this applies when the third part of data is the last segment of the first data), or the location information of the third part of data (e.g., the starting position of the third part of data in the first data, which could be a start bit / start byte / start field, etc.), or the location information of the second part of data (e.g., the ending position of the second part of data in the first data, which could be an end bit / end byte / end field, etc.).

[0212] The first device sends the third portion of the first data to the second device, and the second device receives the third portion of the data accordingly. The starting position of the third portion of the data in the first data is determined based on the amount of data already transmitted (either informed by the second device to the first device, or determined by the first device based on the amounts of the first and second portions of the data). This process is similar to step 303 and can be referred to accordingly.

[0213] (4) During the data segmentation transmission process, the first device does not perform random access.

[0214] In one possible implementation, after the first data transmission is completed, the second device may send an indication message to the first device that the first data transmission has been completed.

[0215] For example, the information could be a Query signaling message. In this case, the second device would not send a Query signaling message to the first device before the first data transmission is complete; after the first data transmission is complete, the second device would send a Query signaling message to the first device to initiate the next random access.

[0216] For example, the indication information can be a 1-bit indication. For instance, when 1 bit is 0, it indicates that the first data transmission is complete; when 1 bit is 1, it indicates that the first data transmission is not complete.

[0217] For example, if the second device does not send the amount of data transmitted and / or the storage location information of the first data (similar to the first information in step 302) to the first device after the first data transmission is completed, the first device can consider the first data transmission to be complete.

[0218] In another possible implementation, the second device triggers random access to the first device regardless of whether the first data transmission is complete. The first device can determine for itself whether the first data transmission is complete; if the first data transmission is incomplete, the first device does not initiate a new random access. Figure 4 illustrates this scenario. Compared to Figure 3, Figure 4 shows the second device triggering random access to the first device after the first device has sent the first portion of data (e.g., step 301).

[0219] Figure 4 shows a flowchart illustrating a possible communication method.

[0220] Optionally, step 401: The first device performs random access to the second device.

[0221] Before sending the first portion of data, the first device accesses the second device or the network. The first device may perform random access to the second device; this random access can be a non-contention-based random access (CFRA) or a contention-based random access (CBRA). Alternatively, the first device may not perform random access and may access the second device or the network via a mobile called (MT) method. For example, the second device may send a paging message to the first device, skipping random access and directly triggering the first device to send data. Optionally, the paging message may include query signaling.

[0222] Step 402: The first device sends a first message to the second device, the first message including a first portion of the first data.

[0223] Correspondingly, the second device receives the first message from the first device.

[0224] For details of the first message in step 402, please refer to the details of the first message in step 301.

[0225] Step 403: The second device sends second information to the first device, the second information being used to trigger random access (or trigger access opportunity).

[0226] Correspondingly, the first device receives the second information.

[0227] After receiving the second information, the first device may choose not to respond (or not to process, or not to respond (or not to process) for a period of time, or discard the second information. Alternatively, the first device may choose not to receive the second information.

[0228] For example, the second information could be a QueryRep signaling or a Query signaling. In the prior art, the first device initiates the next random access after receiving the QueryRep signaling or the Query signaling. However, in this embodiment, the first device does not initiate the next random access after receiving the QueryRep signaling or the Query signaling.

[0229] Step 403 may occur only once or may be executed multiple times. The first device will not perform random access before the first data has been transmitted.

[0230] Step 404: The second device sends first information to the first device, the first information including the amount of the first part of data and / or the storage location information of the first data.

[0231] Correspondingly, the first device receives the first information from the second device.

[0232] For details of the first information in step 404, please refer to the details of the first information in step 302.

[0233] Step 405: The first device sends a second message to the second device, the second message including the second part of the first data.

[0234] Correspondingly, the second device receives the second message.

[0235] For details of the second message in step 405, please refer to the details of the second message in step 303.

[0236] Optionally, if the second device sends a second message to the first device after the first device has finished transmitting the first data, the first device can respond to the second message. That is, before the first data transmission is completed, the first device must maintain the state of transmitting the first data and not be disturbed by other situations.

[0237] Optionally, if the first device receives a Paging message after sending the first part of the first data, the first device can respond to the Paging message and initiate the next random access.

[0238] (5) First identifier.

[0239] The first device may or may not be capable of storing the first identifier. The following description applies to the first device that is capable of storing the first identifier.

[0240] In step 301 (or step 402) above, the first device sends a first message to the second device, the first message including a first portion of the first data. Optionally, the first message may also include a first identifier, which identifies the first device. The second device can use the first identifier to determine which device sent the data, for example, to facilitate data reassembly of the first and second portions of the data by the second device or core network equipment. Additionally, optionally, the first device saves the first identifier after sending the first message (the first portion of the data).

[0241] In step 302 (or step 404) above, the first device receives first information from the second device. The first information includes the data volume of the first portion of data and / or the storage location information of the first data. Optionally, the first information may also include a first identifier, which identifies the first device. For example, when the second device sends a message / information / signaling to a device, it carries the identifier corresponding to that device in the message / information / signaling, thus distinguishing multiple devices. After receiving the message / information / signaling, the device (e.g., the first device) can compare the identifier carried therein with its own identifier; if they are the same, it determines that the message / information / signaling was sent to itself; if they are different, it determines that the message / information / signaling was not sent to itself and no further processing is required. For example, when the second device communicates with multiple devices, it can carry the identifier of the device in the message / information / signaling when sending messages / information / signaling to different devices, although it is possible that the corresponding identifier is not carried. For example, if the second device communicates with only one device (such as the first device), when the second device sends a message / information / signaling to this device, it does not need to carry the device's identifier in the message / information / signaling, although it is not excluded that the corresponding identifier may be carried.

[0242] It should be noted that this application embodiment does not limit the first identifier to be carried in the first information of step 302 (or step 404) only if the first identifier is carried in the first message of step 301 (or step 402). That is to say, regardless of whether the first identifier is carried in the first message of step 301 (or step 402), the first identifier may or may not be carried in the first information of step 302 (or step 404).

[0243] In step 303 (or step 405) above, the first device sends a second message to the second device, the second message including a second portion of the first data. Optionally, the second message may also include a first identifier, which identifies the first device. The second device can use the first identifier to determine which device sent the data, for example, to facilitate data reassembly of the first and second portions of the data by the second device or core network equipment. Additionally, optionally, if the first data transmission is not complete after the first device sends the second portion of the data, the first device saves the first identifier. This can also be understood as the first device saving the first identifier after sending a portion of the first data.

[0244] It should be noted that this application embodiment does not limit the first identifier to be carried in the second message of step 303 (or step 405) only if the first identifier is carried in the first message of step 301 (or step 402) and / or the first information of step 302 (or step 404). That is to say, regardless of whether the first identifier is carried in the first message of step 301 (or step 402), and regardless of whether the first identifier is carried in the first information of step 302 (or step 404), the second message of step 303 (or step 405) may or may not carry the first identifier.

[0245] In another possible implementation, the first identifier can be associated with multiple first devices, meaning that the first identifiers corresponding to multiple first devices are the same. The first identifier can indicate a packet or a class of devices. The second device sends the same first identifier to multiple first devices, which may trigger segmented transmission among the multiple first devices. Different transmission resources can be allocated to the multiple first devices using time division or frequency division.

[0246] The first identifier can be any combination of one or more of the following: identification information used for contention resolution (e.g., a random number RN16, where the name and number of bits of RN16 are not limited), a temporary ID, an access stratum (AS) ID, the electronic product code (EPC) of the first device, a portion of the EPC of the first device, the device identity (device ID) of the first device, or a portion of the device identity of the first device. Alternatively, the first identifier can be information other than any of the above. Optionally, the first identifier is less than or equal to 16 bits.

[0247] The methods for determining the first identifier include, but are not limited to, the following (the numbers in the following methods are for ease of description only and do not reflect the importance or priority of the method):

[0248] Method 1: The first identifier can be generated by the first device.

[0249] For example, the first device may randomly generate the first identifier. For example, the first device may generate the first identifier based on the transmission resources of the first data. As another example, the first device may generate the first identifier based on identifier information used for contention resolution. For example, the first identifier may be obtained by adding other information after the identifier information used for contention resolution; or by adding other information before the identifier information used for contention resolution; or by adding other information both before and after the identifier information used for contention resolution; or by performing some kind of computational processing on the identifier information used for contention resolution to obtain the first identifier.

[0250] The first device can generate a first identifier during random access, either before or after random access. This random access can be performed on the second device for the transmission of first data, or it can be performed for the transmission of other data before the transmission of the first data. The first device can also generate the first identifier during data transmission, for example, during the transmission of the first data (in this case, the first message in step 301 (or step 402) cannot carry the first identifier, but the second message in step 303 (or step 405) can). Another example is generating the first identifier during the transmission of other data before the transmission of the first data.

[0251] Method 2: The first identifier can be pre-configured to the first device before leaving the factory, or generated by a device other than the second device (e.g., core network equipment, application network element, or operation administration maintenance (OAM) function) after leaving the factory and sent (directly or forwarded through other devices) to the first device. The core network equipment, application network element, or OAM can determine the first identifier based on device-related prior information, including but not limited to: the number of devices, the estimated time of the first service, etc.

[0252] Method 3: The first identifier can be generated by the second device and sent (directly or forwarded through other devices / equipment) to the first device.

[0253] For example, the second device may randomly generate the first identifier. For example, the second device may generate the first identifier based on the transmission resources of the first data. As another example, the second device may generate the first identifier based on identifier information from the first device used for contention resolution.

[0254] The second device can generate the first identifier during the random access process, either before or after the random access. This random access can be a process where the first device performs random access to the second device for the transmission of first data, or it can be a process where random access is performed before the transmission of first data for the transmission of other data. The second device can also generate the first identifier during data transmission.

[0255] The first device performs random access to the second device, and the second device may send a first identifier to the first device during the random access process. This random access can be performed on the second device for the transmission of first data, or it can be performed on the second device for the transmission of other data before the transmission of the first data.

[0256] The second device may also send the first identifier to the first device during data transmission. For example, the second device may send the first identifier to the first device before transmitting the first data, while the first device is transmitting other data to the second device. Another example is that the second device may send the first identifier to the first device during the transmission of the first data. For instance, the first identifier may be carried in step 302 (or step 404), or the second device may send the first identifier to the first device after step 301 (or step 402) and before step 302 (or step 404) (in this case, the first identifier cannot be carried in the first message of step 301 (or step 402), but it can be carried in the second message of step 303 (or step 405), or the second device may send the first identifier to the first device after step 302 (or step 404) and before step 303 (or step 405).

[0257] Figure 5 illustrates a communication process in which a second device sends a first identifier to a first device:

[0258] Step 501: The second device triggers an access opportunity to the first device.

[0259] For example, the second device sends a Paging message and / or Query signaling and / or QueryRep signaling to the first device, triggering an access opportunity through this signaling. In an O-RAN architecture, a CU may send Paging to the second device, and the second device then executes step 501.

[0260] Step 502: The first device sends identification information for contention resolution to the second device. For example, RN16.

[0261] Step 503: The second device sends an acknowledgment (ACK) message to the first device.

[0262] One approach is for the second device to send a first identifier to the first device at the same time as sending an ACK to the first device.

[0263] Another approach is that the second device sends a first identifier to the first device after sending an ACK to the first device.

[0264] Another approach is that the second device sends a first identifier to the first device before sending an ACK to the first device.

[0265] In the O-RAN architecture, the RIC sends device-related prior information to the CU. The CU or DU determines the first identifier based on this prior information, which includes, but is not limited to, the number of devices and the estimated time of the first service. Additionally, the RIC can know the device's capacity or power consumption and can prioritize triggering the resumption of data transmission from devices with lower capacity or power consumption.

[0266] Further optionally, step 301 or step 402 is performed: the first device sends a first message to the second device, the first message including a first part of data, and optionally also including a first identifier.

[0267] In the embodiments of this application, after the first device obtains the first identifier, it can carry the first identifier when transmitting data, or it can be used for other purposes. This application does not limit this.

[0268] (6) The first device indicates to the second device whether the first data transmission is complete.

[0269] In one possible implementation, before the first data transmission is complete, the first device may send an indication message to the second device to inform the second device that the first data transmission is not complete.

[0270] In one possible implementation, when the first data transmission is complete, the first device may send an indication message to the second device to inform the second device that the first data transmission has been completed.

[0271] For example, this indication information can be indicated by 1 bit or multiple bits. Taking 1 bit as an example, when 1 bit is 0, it indicates that the first data transmission is complete, and when 1 bit is 1, it indicates that the first data transmission is not complete.

[0272] For example, the indication information includes a first identifier, which is used to identify the first device. The first identifier may also implicitly indicate that the first data has not been transmitted in complete. In other words, the first identifier can be associated with the first device for segmented transmission.

[0273] For example, the indication information may include a first identifier and an additional 1 bit or more bits.

[0274] For example, if the first data is divided into multiple segments, the indication information can include a segment index indicating the segment number of the currently transmitted data. For instance, if the default is 2 segments, a number of 0 or 1 indicates that this data is the first segment of the first data (implicitly indicating segmented transmission, the first data has not been fully transmitted), while a number of 1 or 2 indicates that this data is the second segment of the first data (implicitly indicating segmented transmission, the first data has been fully transmitted).

[0275] For ease of description, when this indication information is used to indicate that the first data has not been transmitted completely, this indication information is referred to as the third information.

[0276] For example, the first device sends a third message, and correspondingly, the second device receives the third message, which is used to indicate that: the first data has not been completely transmitted, or the first part of the data (or the transmitted data) is not the last segment of the first data, or there is first data to be transmitted, the first part of the data (or the transmitted data) is part of the first data (or incomplete data, or segmented data), or the first part of the data (the transmitted data) is data that is not to be submitted (or not allowed to be submitted, or does not need to be submitted, or cannot be submitted), or requests to continue transmitting data.

[0277] In this context, "submission" can be understood as sending data to core network devices, access network devices, or submitting it to a higher protocol layer, such as the MAC layer submitting it to the NAS layer, AIoT NAS layer, or application layer. "Can be submitted" can be understood as having obtained complete initial data and being able to submit it; "cannot be submitted" (or not allowed to be submitted, or not required to be submitted) can be understood as the initial data being incomplete and not yet ready for submission.

[0278] The timing of the first device sending third information to the second device includes, but is not limited to, any of the following examples (the numbers in the following examples are for ease of description only and do not represent the priority or importance of the examples):

[0279] Example 1: The third information is included in the first message (e.g., step 301 or step 402). That is, when the first device sends the first part of the first data to the second device, it informs the second device that the first data transmission is not complete.

[0280] Example 2: After the first device sends the first message (e.g., step 301 or step 402) and before the first device receives the first information (i.e., step 302 or step 404), the first device sends the third information. That is, after sending the first part of the first data, the first device informs the second device that the first data transmission is not complete.

[0281] Example 3: Before the first device sends the first message (e.g., step 301 or step 402), the first device sends a third message. This can be understood as the first device knowing or predicting the amount of data that can be sent before sending the first data. If the amount of data that can be sent is less than the amount of the first data, then the first data cannot be sent completely. For example, before sending the first message, the second device sends a TBS to the first device. The TBS is used by the first device to determine the amount of data to be sent. For example, if the TBS is less than the amount of data carrying the first data message, then the first data needs to be transmitted in segments. The first device sends the first part of the first data to the second device. For example, the amount of data carrying the first part of the first data message is the TBS. Another example is that the first device can predict the amount of data that the current remaining battery power allows to be sent based on historical data. The first device's battery power is insufficient to send all the first data.

[0282] For ease of description, when this indication information is used to indicate that the first data transmission has been completed, this indication information is referred to as the fourth information.

[0283] For example, the first device sends a fourth message, and correspondingly, the second device receives the fourth message, which indicates that: the first data transmission is complete, or the second part of the data is the last segmentation of the first data, or there is no first data to be transmitted, or the transmitted data is all of the first data, or the transmitted data is the complete first data, or the transmitted data is data to be submitted (or allowed to be submitted, or required to be submitted, or able to be submitted), or the second part of the data is data to be submitted (or allowed to be submitted, or required to be submitted, or able to be submitted), or the first data is data to be submitted (or allowed to be submitted, or required to be submitted, or able to be submitted). This indication information can be sent to the second device in the same message as the last part of the data. For example, if the second part of the data is the last segmentation of the first data, the first device sends a second message to the second device (e.g., step 303 or step 405), the second message including the second part of the first data and the indication information.

[0284] Optionally, the second message may include an indication message indicating that the second part of the data is a continuation of a previous transmission. A continuation indicates that the data being sent is a portion of a previously transmitted data set, and that the data being sent this time is not new data triggered by a new service. For example, this indication message can be indicated by 1 bit or more bits. Using 1 bit as an example, when 1 bit is 0, it indicates that the second part of the data is a continuation of a previous transmission; when 1 bit is 1, it indicates that the data being transmitted this time is not a continuation of a previous transmission. For example, the indication message may include a first identifier, which identifies the first device. The first identifier may also implicitly indicate a continuation of the transmission; that is, the first identifier can be associated with the first device for segmented transmission. Another example is that the indication message may include a first identifier and an additional 1 bit or more bits.

[0285] (7) First time / first duration.

[0286] In one possible implementation, the first device may instruct the second device on the time to send the second portion of data. For example, the first device may instruct the second device on the time to send the second portion of data when or after the first device sends the first portion of data to the second device (e.g., step 301 or step 402). For example, the first device may instruct the second device on a first time, indicating that the transmission of the second portion of data will begin at the first time. Another example is that the first device may instruct the second device on a first duration, indicating that the transmission of the second portion of data will begin after a first duration following a certain time (e.g., the time when the instruction information is received, or the time when the first portion of data is received). Alternatively, after the first duration, the second device may send a first message to the first device (e.g., step 302 or step 404), or after the first duration, the second device may instruct the first device to continue transmitting data.

[0287] In another possible implementation, the second device may indicate to the first device the time to send the second portion of data. For example, after the second device receives the first portion of data (e.g., step 301 or step 402), the second device may indicate to the first device the time to send the second portion of data. This indication can be given to the first device before sending the first information; it can also be given while the second device is sending the first information; or it can be given to the first device after sending the first information.

[0288] For example, the second device instructs the first device to a second time, indicating that the transmission of the second portion of data will begin at the second time. As another example, the second device instructs the first device to a second duration, indicating that the transmission of the second portion of data will begin after a second duration following a certain time (e.g., the time the instruction was received, or the time the first portion of data was transmitted). Alternatively, after the second duration, the second device may send a first message to the first device (e.g., step 302 or step 404), or after the second duration, the second device may instruct the first device to continue transmitting data.

[0289] Optionally, the first duration or the second duration may also indicate the charging duration, the sleep duration, the maximum sleep duration, the minimum sleep duration, the resume waiting time, the minimum segmented waiting time, or the maximum segmented waiting time, etc.

[0290] In one implementation, the first device may start timing after sending the first portion of data, or after receiving a downlink acknowledgment message (e.g., to confirm successful reception of the first portion of data) after sending the first portion of data; before the timing exceeds a first duration or a second duration, no messages are sent and / or received; after the timing exceeds the first duration or the second duration, messages can be sent and / or received. One timing method is to start a timer.

[0291] Optionally, during the timing period (e.g., during timer operation), the first device may enter sleep mode or conserve energy to reduce power consumption or recharge. Alternatively, during the time interval between transmitting the first portion of data and transmitting the second portion of data, the first device may recharge or not monitor other messages.

[0292] (8) The second device instructs the first device to continue transmitting data.

[0293] Step 302 (or step 404) above describes the first information as including the data volume of the first portion of data and / or the storage location information of the first data. The first information can be carried in downlink signaling / messages, for example, the downlink signaling / messages are Paging signaling / messages, MAC signaling / messages, or other downlink signaling / messages. The content included in the first information can implicitly indicate continued data transmission.

[0294] For example, the second device sends an indication message to the first device, which instructs the first device to continue transmitting data. This indication message can be carried in the same message as the first message; or, the indication message can be sent to the first device before the first message; or, the indication message can be sent to the second device after the first message. This indication message can be carried in downlink signaling / messages, such as Paging signaling / messages, MAC signaling / messages, or other downlink signaling / messages. For example, the indication message includes one or more bits to indicate whether to continue transmitting data. Taking 1 bit as an example, for instance, when the 1st bit is 1, it indicates to continue transmitting data; when the 1st bit is 0, it indicates not to continue transmitting data. For another example, the indication message includes the first identifier described above. For yet another example, the indication message includes the identifier of the first service (the first data was triggered by the first service).

[0295] In one possible scenario, if the first device can save the resume state, it will not be necessary to send this indication message to indicate whether to continue data transmission. If the first device cannot save the resume state, it can send this indication message to indicate whether to continue data transmission.

[0296] In one possible implementation, the second device sends a Paging message to the first device. The Paging message includes the first information and the indication information. In current technology, the Paging message does not include indication information on whether to continue data transmission. Upon receiving the Paging message, the first device may discard the previous service and initiate a new service. However, in this example, the Paging message includes indication information on whether to continue data transmission. Upon receiving the Paging message, the first device can determine whether to continue data transmission based on this indication information, and thus transmit the second part of the data.

[0297] (9) Triggering conditions for the second device to send the first information to the first device.

[0298] In step 302 (or step 404) above, the second device sends first information to the first device. This first information includes the amount of data in the first portion of the data and / or the storage location information of the first data. Additionally, this first information may implicitly indicate that the first data transmission is incomplete. Examples of the second device determining to send the first information to the first device include, but are not limited to, the following:

[0299] Example 1: The second device can determine to send the first information to the first device based on the amount of data in the first part of the data and the amount of data in the first data.

[0300] For example, when the second device determines that the amount of data in the first part of the data is less than the amount of data in the first data, the second device may send the first information to the second device. The amount of data in the first data may be provided by the first device to the second device, or it may be provided by the core network equipment to the second device. For example, the first device may send the amount of data in the first data to the second device when sending identification information for contention resolution. Of course, the amount of data in the first data may also be carried in other existing messages, or it may be sent in a separate message.

[0301] Furthermore, the determination by the first device of whether the amount of data in the first part of the data is less than the amount of data in the first data may not be used to determine whether to send the first information to the first device, or may have other uses, which are not limited in this application.

[0302] Example 2: The second device may send the first information to the first device based on the third information.

[0303] The above describes how the third information can be used to indicate that the first part of the data is not the last segment of the first data, or that the first data has not been fully transmitted, or that there is first data to be transmitted. After receiving the third information, the second device can send the first information to the first device based on the third information.

[0304] Furthermore, the function of the third information is not limited to this. After receiving the third information, the second device may not use it to determine whether to send the first information to the first device.

[0305] Example 3: The second device can send the first information to the first device based on the instructions of the core network.

[0306] For example, the core network device sends a fifth message to the second device, and correspondingly, the second device receives the fifth message from the core network device, which is used to indicate continued data transmission. The second device can then send the first message to the first device based on the fifth message.

[0307] Furthermore, the function of the fifth information is not limited to this. After receiving the fifth information, the second device may not use it to determine whether to send the first information to the first device.

[0308] The core network equipment determines the methods for sending the fifth information to the second device, including but not limited to the following:

[0309] Method 1: After receiving the first part of the data (e.g., step 301 or step 402), the second device may send the first part of the data to the core network device. The core network device may determine whether to send the fifth information to the second device based on the amount or content of the first part of the data. This method is described below as shown in Figure 6.

[0310] Figure 6 shows a flowchart of a communication method.

[0311] Optionally, step 601: The first device is randomly connected to the second device.

[0312] Step 602a: The first device sends a first message to the second device, the first message including a first part of the first data.

[0313] Correspondingly, the second device receives the first message from the first device.

[0314] For further details regarding the first message, please refer to the description in step 301; it will not be elaborated upon here.

[0315] Step 602b: The first device sends the first part of the first data to the core network equipment.

[0316] Accordingly, the core network equipment receives this first part of the data.

[0317] Optionally, in step 602b, in addition to sending the first part of the data in the first message to the core network device, the first device may also send some or all of the information in the first message other than the first part of the data to the core network device.

[0318] Optionally, the second device can transmit the first part of the data.

[0319] Step 603: The core network device sends the fifth message to the second device, which is used to indicate that transmission should continue.

[0320] Correspondingly, the second device receives the fifth message.

[0321] For example, after receiving the first portion of data, the core network device can determine the amount of data in the first portion and then, based on the amount of data in the first portion and the amount of data in the first data, determine whether to send the fifth information to the second device. For example, if the amount of data in the first portion is less than the amount of data in the first data, the core network device sends the fifth information to the second device. For example, if the amount of data in the first portion is not less than the amount of data in the first data, the core network device does not need to send the fifth information to the second device, or it can send a data transmission completion indication to the second device.

[0322] For example, after receiving the first part of the data, the core network device can determine the content of the first part of the data, and then, based on the content of the first part of the data, determine whether to send the fifth information to the second device. For example, the core network device can determine, based on the content of the first part of the data, that the first part of the data is only a part of the first data, not the entire content, and then determine to send the fifth information to the second device.

[0323] For example, the second device also sends a sixth message to the core network equipment, which indicates that data transmission has not been completed. Based on this sixth message, the core network equipment sends the fifth message to the second device.

[0324] Step 604: The second device sends the first information to the first device. Correspondingly, the first device receives the first information.

[0325] For further details regarding the first message, please refer to the description in step 302; it will not be elaborated upon here.

[0326] Step 605a: The first device sends a second message to the second device, the second message including a second portion of the first data. Correspondingly, the second device receives the second message.

[0327] For further details regarding the second message, please refer to the description in step 605a; it will not be elaborated upon here.

[0328] Optionally, the second device may transmit the second portion of data.

[0329] Step 605b: The second device sends the second part of the first data to the core network device, and the core network device receives the second part of the data accordingly.

[0330] Optionally, in step 605b, in addition to sending the second part of the data in the second message to the core network device, the first device may also send some or all of the information in the second message other than the second part of the data to the core network device.

[0331] Optionally, in step 606: the core network device sends an indication message to the second device, which indicates that the data transmission is complete.

[0332] Accordingly, the second device receives the instruction information.

[0333] After determining that data transmission is complete, the core network device may send an indication message to the second device to indicate that the data transmission is complete. Upon receiving this indication message from the core network device, the second device determines that the data transmission is complete. Alternatively, the core network device may not send an indication message to the second device after determining that the data transmission is complete, and the second device may also consider the data transmission complete if it does not receive a downlink command from the core network device for an extended period.

[0334] Optionally, step 607: the second device triggers an access opportunity to the first device.

[0335] After confirming that the data transmission is complete, the second device can trigger an access opportunity to the first device and initiate the next random access.

[0336] Method 2: The second device can send a sixth message to the core network equipment, the sixth message indicating that the first data transmission has not been completed. After receiving the sixth message, the core network equipment can send a fifth message to the second device.

[0337] In one example, the first device sends third information to the second device, indicating that: the first portion of data is not the last segment of the first data, or the first data has not been fully transmitted, or there is first data to be transmitted. Based on this third information, the second device can determine that the first data has not been fully transmitted and then send sixth information to the core network equipment. This sixth information can be a reused version of the third information or it can be generated by the second device itself.

[0338] In another example, the second device can determine whether the first data transmission is complete based on the amount or content of the first data portion. If it is determined that the amount of the first data portion is less than the amount of the first data, then a sixth message is sent to the core network device.

[0339] For example, after receiving the first part of the data, the second device can determine the amount of data in the first part, and then, based on the amount of data in the first part and the amount of data in the first data, determine whether to send the sixth information to the core network device. For example, if the amount of data in the first part is less than the amount of data in the first data, the second device sends the sixth information to the core network device.

[0340] For example, after receiving the first part of the data, the second device can determine the content of the first part of the data, and then, based on the content of the first part of the data, determine whether to send the sixth information to the core network equipment. For example, the second device can determine, based on the content of the first part of the data, that the first part of the data is only a part of the first data, not the entire content, and then determine to send the sixth information to the core network equipment.

[0341] Method 3: The second device sends the amount of the first data to the core network device. The core network device can determine whether to send the fifth information to the second device based on the amount of the first part of the data and the amount of the first data. For example, if the amount of the first part of the data is less than the amount of the first data, the core network device sends the fifth information to the second device. For example, if the amount of the first part of the data is not less than the amount of the first data, the core network device does not need to send the fifth information to the second device, or it can send a data transmission completion indication to the second device.

[0342] Method 4: The core network device can obtain the data size TBS of the transport block scheduled by the second device to the first device. For example, the TBS can be provided to the core network device by the second device, or it can be determined by the core network device. The data size of each data transmission by the first device is less than or equal to the TBS, that is, the data size of the first part of the first data is less than or equal to the TBS. The core network device can determine whether to send the fifth information to the second device based on the TBS and the data size of the first data. For example, if the TBS is less than the data size of the first data, the core network device sends the fifth information to the second device.

[0343] In one possible implementation, after receiving the first part of the data (e.g., step 301 or step 402), the second device can send an indication of received data to the core network device. The core network device determines that the TBS is less than the amount of the first data, and then the core network device can send the fifth information to the second device.

[0344] Based on methods 1-4 described above, after receiving the first part of the data (e.g., step 301 or step 402), the second device receives the fifth information from the core network device. In another possible implementation, the second device may receive the fifth information from the core network device after receiving the first part of the data (e.g., step 301 or step 402). In this case, it can be seen that the core network device authorizes the second device to determine whether to continue transmitting data without consulting the core network device. The second device may use Example 1 or Example 2 described above, or other methods, to determine whether to send the first information to the first device.

[0345] (10) The second device instructs the first device to perform the first service.

[0346] In this application embodiment, the service that triggers the transmission of first data is referred to as the first service. The first service may include a single service or multiple services. The first service may include one or more of the following: inventory service, command service (such as read, write, deactivate, lock, etc.), positioning service, sensing service, etc.

[0347] Based on the triggering of the first service, the first device sends a first part of the first data to the second device (e.g., step 301 or step 402). For example, before the first device sends the first part of the data to the second device, the second device instructs the first service to the first device, such as instructing the first service to the first device in a Paging message.

[0348] Before sending the second part of the data, the second device may again indicate the first service to the first device. For example, after receiving the first part of the data (e.g., in step 301 or step 402), the second device sends indication information to the first device, which indicates the first service. For example, when the first service is an inventory service, the indication information indicates the device ID. As another example, when the first service is a command service, the indication information indicates read, write, deactivate, or lock commands.

[0349] For example, the second device may send the indication information to the first device when sending the first information (e.g., step 302 or step 404) (this may be in a different data segment of the same message). For example, the second device may send the indication information to the first device after receiving the first message (e.g., step 301 or step 402) and before sending the first information (e.g., step 302 or step 404). As another example, the second device may send the indication information to the first device after sending the first information (e.g., step 302 or step 404) and before receiving the second message (e.g., step 303 or step 405).

[0350] During data transmission, the second device can instruct the first device to perform the first service again, eliminating the need for the first device to remember the service and reducing storage overhead. Of course, if the first device can store the first service, the second device does not need to instruct it again.

[0351] (11) The second device indicates the amount of data TBS in the transmission block to the first device.

[0352] The amount of data sent from the first device to the second device can be determined by the first device itself, or it can be determined based on the scheduling of the second device. For example, the second device indicates the data size (TBS) of a transport block to the first device. After knowing the TBS, the first device can send the data of the TBS, or send data smaller than the TBS.

[0353] The following is an example of the first device transmitting data based on the scheduling of the second device:

[0354] Before the first device sends the first data to the second device, the second device indicates a first TBS to the first device, and the data size of the bearer message for the first part of the data is the first TBS. The bearer message for the first part of the data includes the first part of the data, which may be a MAC SDU, a NAS PDU, or application layer data; further optionally, the bearer message for the first part of the data may also include at least one of the following: a message header, a frame header (e.g., a preamble), a postamble, a CRC sequence, etc. The second device may indicate the first TBS to the first device during random access, or it may indicate the first TBS to the first device after random access and before data transmission.

[0355] Before the first device sends the second part of the data to the second device, the second device instructs the first device to a second TBS, wherein the data size of the message carrying the second part of the data is the second TBS or less than the second TBS.

[0356] The second device may indicate the second TBS to the first device when it sends the first message (e.g., step 302 or step 404). Alternatively, the second device may indicate the second TBS to the first device after receiving the first message (e.g., step 301 or step 402) but before sending the first message (e.g., step 302 or step 404). Or, the second device may indicate the second TBS to the first device after sending the first message (e.g., step 302 or step 404) but before receiving the second message (e.g., step 303 or step 405).

[0357] When the second device indicates a TBS (e.g., the first TBS or the second TBS) to the first device, the indication can be explicit, for example, the second device sends indication information to the first device, which is used to indicate the TBS; or it can be implicit, for example, the TBS is associated with the physical layer sequence or frame structure, or preamble, etc., and the second device can indicate a TBS by sending the physical layer sequence or frame structure, or preamble, etc. to the first device.

[0358] Figure 7 illustrates a data transmission diagram. In the disk storage operation, the data to be transmitted is the device ID (optionally, the device ID is stored in the memory bank). The first device first obtains the device ID, uses it as the NASSDU, and encapsulates the device ID using a NAS header (optionally, the NAS header is stored in a register). The encapsulated whole is considered as the first data. Before transmitting the first data, the second device sends the first TBS to the first device.

[0359] When the first device sends the first data portion, it can encode the first data portion by adding a CRC sequence and perform MAC layer encapsulation, etc. (Optionally, the CRC sequence and MAC header are stored in a buffer). The data size of the message carried by the first data portion sent by the first device is the first TBS. In the example of Figure 7, the sum of the data size of the first data portion (i.e., MAC SDU1) and the MAC header is the first TBS.

[0360] After receiving the first part of the data, the second device can determine the second TBS based on the data volume of the first data and the data volume of the first part of the data. For example, if the data volume of the first data = (first TBS - MAC header data volume) + (second TBS - MAC header data volume), then the second TBS = first data volume - first TBS - 2 * MAC header data volume.

[0361] The second device can also send a second TBS to the first device. After receiving the second TBS, the first device can send the second part of the data to the second device based on the second TBS. Similarly, when sending the second part of the data, the first device can encode the second part of the data, add a CRC sequence, and perform MAC layer encapsulation, etc. The data volume of the message carried by the second part of the data is the second TBS. In the example of Figure 7, the sum of the data volume of the second part of the data (i.e., MAC SDU2) and the MAC header is the second TBS.

[0362] The amount of data in the first data acquired by the second device may be accurate or inaccurate. If the amount of data in the first data is accurate, then the amount of data in the second TBS corresponds exactly to the amount of data in the second part of the data; if the amount of data in the first data is inaccurate, then the amount of data in the message carried by the second TBS and the second part of the data may deviate slightly.

[0363] Referring to the example in Figure 7, it can be concluded that the data to be transmitted (e.g., device ID, command service data, or NAS PDU) and the NAS header, as a whole, are considered as the first data. The first part of the data is a portion of the NAS header and the data to be transmitted; the second part of the data is another portion of the data to be transmitted.

[0364] In another possible implementation, the second part of the data may include another portion of the data to be transmitted and a NAS header. The content of the NAS header in the second part of the data may be the same as or not exactly the same as the content of the NAS header in the first part of the data.

[0365] In another possible implementation, the data to be transmitted, the NAS header, and the MAC header are the first data.

[0366] In another possible implementation, the data to be transmitted (without a NAS header) is the first data, the first part of the data is a portion of the first data, and the second part of the data is another portion of the first data.

[0367] Here, the MAC layer refers to the protocol layer of the AS, and the NAS layer refers to the protocol layer of the non-access layer. There are no restrictions on their names. For example, the MAC layer can be replaced with the AS layer of AIoT, and the NAS layer can also be replaced with the application layer or the NAS layer of AIoT, etc.

[0368] Figure 8 below illustrates a data transmission diagram. In command operations (e.g., read / write), the first device can determine the storage location of the data to be transmitted based on the received downlink command, and retrieve the data to be transmitted from that storage location (optionally, the data to be transmitted is stored in a memory bank).

[0369] Before transmitting the first data, the second device sends a first TBS to the first device. When sending the first data portion, the first device can perform operations such as NAS layer encapsulation, encoding and adding a CRC sequence, and MAC layer encapsulation on the first data portion (optionally, the CRC sequence and MAC header are stored in a buffer). The data size of the message carried by the first data portion sent by the first device is the first TBS. In the example of Figure 8, the sum of the data sizes of the first data portion, the NAS header, and the MAC header is the first TBS.

[0370] After receiving the first part of the data, the second device can determine the second TBS based on the data volume of the first data and the data volume of the first part of the data. For example, if the data volume of the first data = (first TBS - MAC header data volume - NAS header data volume) + (second TBS - MAC header data volume - NAS header data volume), then the second TBS = first data volume - first TBS - 2 * MAC header data volume - 2 * NAS header data volume.

[0371] The second device can also send a second TBS to the first device. After receiving the second TBS, the first device can send the second part of the data to the second device based on the second TBS. Similarly, when sending the second part of the data, the first device can perform operations such as NAS layer encapsulation, encoding and adding a CRC sequence, and MAC layer encapsulation on the second part of the data. The data volume of the message carried by the second part of the data is the second TBS. In the example of Figure 8, the sum of the data volumes of the second part of the data, the NAS header, and the MAC header is the second TBS.

[0372] (12) Safety parameters.

[0373] For example, security parameters include, but are not limited to: freshness, randomness, keys, prior information, and Media Access Control (MAC) address. Security parameters can be used in security processes, such as preventing replay attacks and authentication.

[0374] In one implementation, the second device indicates safety parameters to the first device.

[0375] For example, the second device may indicate security parameters to the first device before the first device sends the first portion of data, for instance, during random access or the sending of paging messages. For example, the enemy device may indicate security parameters to the first device before step 301 or before step 402.

[0376] As another example, the second device may also indicate security parameters to the first device during the data transmission process of the first device. For example, the second device indicates security parameters to the first device before the first device transmits the second portion of data (e.g., step 303 or step 405). For example, the second device indicates security parameters to the first device when transmitting the first information (e.g., step 302 or step 404), or the second device indicates security parameters to the first device before or after transmitting the first information.

[0377] In another implementation, the first device generates the safety parameters itself. The generation process is not limited.

[0378] The first device can store safety parameters. This storage can be temporary, such as for one day or one week, or it can be permanent.

[0379] The first device can perform security protection on the transmitted data (e.g., a first part of data and / or a second part of data) according to security parameters. For example, security protection includes, but is not limited to, one or more of encryption protection, integrity protection, and privacy protection. For instance, when transmitting the first part of data (e.g., step 301 or 402), the first device uses security parameters to perform security protection on the first part or data. As another example, when transmitting the second part of data (e.g., step 303 or 405), the first device uses security parameters to perform security protection on the second part or data.

[0380] The first device can use the same security parameters (without needing to inform each other of the security parameters again) or different security parameters when sending the first part of data and the second part of data.

[0381] (13) First state, second state.

[0382] In one possible implementation, the first device may be configured with a first state, which refers to a state where data transmission is incomplete. The first state may be referred to as a continuation state, a segmentation state, or a data transmission incomplete state, etc., and the name of the first state is not limited. The first device may enter the first state after sending the first portion of data (e.g., step 301 or step 402).

[0383] Optionally, the first device can also be configured with a second state, which refers to a state where data transmission is complete or new data transmission has not yet begun. The second state can be called a non-resumption state, a paging state, a data transmission completion state, etc., and the name of the second state is not limited. The first device can be in the second state before step 301 or step 402. If the second part of the data is the last segment of the first data, then after the first device sends the second part of the data, the first data transmission is complete, and the first device can deactivate / release the first state or enter the second state.

[0384] The first device may have flag bits set for the first state and / or the second state. For example, the flag bit occupies 1 bit. When 1 bit is 0, it indicates that the first device has entered the first state; when 1 bit is 1, it indicates that it has entered the second state.

[0385] The first state can be associated with a first identifier. For example, after the first device has sent a portion of the first data, it saves the first identifier. That is, before the first data is completely sent, the first device saves the first identifier each time it sends a portion of the first data, using the first identifier to indicate that the first data transmission is not complete.

[0386] (14) The third state.

[0387] In one possible implementation, the first device can be configured to a third state, which is an energy-saving state. This third state can be referred to as a hibernation state, sleep state, semi-sleep state, energy-saving state, low-power state, etc., and the name of the third state is not limited. The first device can enter the third state after sending a first portion of data to the second device (e.g., step 301 or step 402). Alternatively, the first device can enter the third state after sending the first portion of data and receiving feedback information from the second device (e.g., an acknowledgment message (such as ACK), QueryRep signaling, or a time slot end indication). In the third state, the behavior of the first device can be one or more of the following:

[0388] It does not monitor downlink messages / signaling / information / data; it does not respond to downlink messages / signaling / information / data; it does not send uplink messages / signaling / information / data; it monitors some downlink messages / signaling / information / data (such as paging or wake-up signals); it responds to some downlink messages / signaling / information / data (such as paging or wake-up signals).

[0389] By entering the third state, energy can be saved from the first device.

[0390] The duration of the third state can be measured in absolute time (milliseconds / seconds / minutes, etc.) or relative time, such as frames, subframes, time slots, sub-time slots, the number of received signaling, etc.

[0391] The duration can be specified in the agreement.

[0392] The duration can be determined by the first device. For example, the first device can determine the duration based on its own energy (e.g., capacitance value, remaining power). The first device can also inform the second device of the duration it has determined. For example, during data transmission, random access, or other processes, it can inform the second device of the duration. For example, the duration can be sent to the second device along with the data, or it can be sent to the second device in other uplink messages.

[0393] The duration can be determined by the second device. For example, the first device can send its energy information (which can be energy / capacitance values, etc., the specific form is not limited, and its function is to measure the amount of energy currently or subsequently available to the first device) to the second device, and the second device determines the duration based on the energy information of the first device. The first device can send the energy information to the second device during random access, for example, when the first device sends identification information for contention resolution; or when the first device sends uplink data to the second device. The first device can also send the energy information to the second device in other processes. The second device can also inform the first device of its own determined duration. For example, it can inform the first device during data transmission or random access, or it can inform the first device in other processes.

[0394] This duration can be determined by the core network equipment. For example, the first device sends its energy information to the second device, which then sends the first device's energy information to the core network equipment. The core network equipment determines the duration based on the first device's energy information, sends the duration to the second device, and the second device then sends the duration back to the first device.

[0395] In one possible implementation, the second device sends a first message to the first device (e.g., step 302 or step 404), and subsequently does not receive a response from the first device (e.g., the second part of the data is not received). The second device can then send the first message again, i.e., repeatedly send the first message to the first device. Another possible implementation where the second device does not receive a response is that the first device is in a sleep state and has not detected the first message.

[0396] Example 2:

[0397] As shown in Figure 4 above, the first device performs segmented transmission in a single connection (a connection refers to the first device connecting to the second device). Example 2 illustrates an example of the first device performing segmented transmission in multiple connections. Details (1)-(3) and (5)-(14) described in Example 1 are applicable to Example 2.

[0398] Figure 9 illustrates a flowchart of a communication method, including the following steps:

[0399] Optionally, step 901: The first device randomly connects to the second device.

[0400] Before sending the first portion of data, the first device accesses the second device or the network. The first device may perform random access to the second device; this random access can be a non-contention-based random access (CFRA) or a contention-based random access (CBRA). Alternatively, the first device may not perform random access and may access the second device or the network via a mobile called (MT) method. For example, the second device may send a paging message to the first device, skipping random access and directly triggering the first device to send data. Optionally, the paging message may include query signaling.

[0401] Step 902: The first device sends a first message to the second device, the first message including the first part of the first data.

[0402] Correspondingly, the second device receives the first message.

[0403] Step 902 can be referred to the description of step 301 in Embodiment 1, and will not be repeated in detail here.

[0404] Step 903: The second device sends an indication message to the first device, which is used to indicate / trigger an access opportunity.

[0405] The instruction information may include one or more of the following: Paging signaling, or Query signaling, or Query Rep signaling.

[0406] Step 904: The first device sends identification information for contention resolution to the second device.

[0407] Optionally, in step 905: the second device sends an ACK message to the first device. Optionally, the ACK message carries the identification information of the contention resolution.

[0408] Accordingly, the first device received the ACK message. The contention was successfully resolved by the first device.

[0409] Optionally, step 906: the second device sends first information to the first device, the first information including the amount of data in the first part of the data and / or the storage location information of the first data.

[0410] Step 906 can be referred to the description of step 302 in Example 1, and will not be repeated in detail here.

[0411] If the first device can save the storage location information of the first data and the amount of the first part of the data (or the end position, segment position, or breakpoint position of the first part of the data in the first data), there is no need for the second device to inform the first device of this information.

[0412] Steps 906 and 905 may be in the same message or in different messages.

[0413] Optionally, after step 903 and before step 906, the first device sends an indication message to the second device, indicating whether the first data transmission is complete or incomplete. This indication message may be the one sent by the first device to the second device as described in detail (6) above, indicating whether the data transmission is complete or incomplete; or it may be a different indication message than the one described in detail (6).

[0414] For example, this indication information can be indicated by 1 bit or multiple bits. Taking 1 bit as an example, when 1 bit is 0, it indicates that the first data transmission is not complete; when 1 bit is 1, it indicates that the first data transmission is complete.

[0415] For example, the indication information includes a first identifier. This first identifier can be used to identify the first device. The first identifier can also implicitly indicate that the first data transmission is incomplete; that is, the first identifier can be associated with the first device for segmented transmission.

[0416] For example, the indication information may include a first identifier and an additional 1 bit or more bits.

[0417] For example, if the first data is divided into multiple segments, the indication information can include a segment index indicating the segment number of the currently transmitted data. For instance, if the default is 2 segments, a number of 0 or 1 indicates that this data is the first segment of the first data (implicitly indicating segmented transmission, the first data has not been fully transmitted), while a number of 1 or 2 indicates that this data is the second segment of the first data (implicitly indicating segmented transmission, the first data has been fully transmitted).

[0418] When this indication information is used to indicate that the first data transmission has not been completed, the meaning of this indication information can be replaced as follows:

[0419] The first part of the data (or the data that has been transmitted) is not the last segment of the first data, or there is first data to be transmitted, or the first part of the data (or the data that has been transmitted) is part of the first data (or incomplete data, or segmented data), or the first part of the data (the data that has been transmitted) is data that is not submitted (or not allowed to be submitted, or does not need to be submitted), or the data transmitted in the previous transmission (or the data transmitted in the previous communication connection established by random access) is not the last segment of the first data, or the data transmitted in the current communication connection established by random access is a continuation of the data transmitted in the previous communication connection established by random access, or the data to be transmitted next is a continuation of the data transmitted in the previous communication connection established by random access.

[0420] Figure 9 shows a flowchart of the communication method, illustrating several scenarios in which the first device sends the indication information to the second device (the numbers in the following scenarios are for descriptive purposes only and do not represent the priority or importance of the scenarios). Figure 9 also uses an example where the indication information includes a first identifier.

[0421] In case (1), the instruction information is sent in step 904 (shown as an example of the first identifier in Figure 9). That is, the first device sends the instruction information when it sends the identifier information for contention resolution to the second device.

[0422] In case (2), after step 904 and before step 905, the first device sends the instruction information to the second device (the first identifier is shown as an example in Figure 9).

[0423] In case (3), after step 905 and before step 906, the first device sends the instruction information to the second device (the first identifier is shown as an example in Figure 9).

[0424] Step 907: The first device sends a second message to the second device, the second message including the second part of the first data.

[0425] Correspondingly, the second device receives the second message.

[0426] Step 907 can be referenced from step 303.

[0427] Optionally, in step 908: the second device sends indication information or downlink data to the first device, the indication information being used to indicate / trigger an access opportunity.

[0428] The instruction information may include one or more of the following: Paging signaling, or Query signaling, or Query Rep signaling.

[0429] Figure 9 above illustrates that the first device can be informed that the first data transmission is not complete before resuming data transmission (e.g., sending a second portion of data). In the following example, the first device informs the second device that the data is resuming transmission when sending the second portion of data to the second device.

[0430] Figure 10 shows a flowchart illustrating a communication method.

[0431] Optionally, step 1001: The first device randomly connects to the second device.

[0432] Step 1002: The first device sends a first message to the second device, the first message including the first part of the first data.

[0433] Correspondingly, the second device receives the first message.

[0434] For details of the first message in step 1001, please refer to the details of the first message in step 301.

[0435] Step 1003: The second device sends an indication message to the first device, which is used to indicate / trigger an access opportunity.

[0436] Steps 1001 to 1003 can be referred to steps 901 to 903, and will not be described in detail here.

[0437] Step 1004: The first device sends identification information for contention resolution to the second device.

[0438] Optionally, in step 1005: the second device sends an ACK message to the first device. Optionally, the ACK message carries the identification information of the contention resolution.

[0439] Accordingly, the first device receives the ACK message.

[0440] Step 1006: The first device sends the second part of the first data and the instruction information to the second device. Accordingly, the second device receives this information.

[0441] This indication information is used to associate the first data. This indication information can be the indication sent by the first device to the second device as described in detail (6) above, indicating that data transmission is complete; or it can be another indication information different from the indication sent in detail (6) to indicate that data transmission is complete. This indication information can be the indication sent by the first device to the second device as described in detail (6) above, indicating that the second part of the data is continuation data; or it can be another indication information different from the indication sent in detail (6) to indicate that the second part of the data is continuation data.

[0442] For example, this indication information can be indicated by 1 bit or multiple bits. Taking 1 bit as an example, when 1 bit is 0, it indicates that the data transmitted this time is part of the first data, or is not all of the first data; when 1 bit is 1, it indicates that the data transmitted this time is complete data, or is not part of the data.

[0443] For example, the indication information may include a first identifier. This first identifier can be used to identify the first device. The first identifier may also implicitly indicate that the data being transmitted is part of first data. That is, the first identifier can be associated with the first device for segmented transmission.

[0444] For example, the indication information includes a first identifier and an additional 1 bit.

[0445] For example, if the first data is divided into multiple segments, the indication information can include a segment index indicating the segment number of the currently transmitted data. For instance, if the default is 2 segments, a number of 0 or 1 indicates that this data is the first segment of the first data (implicitly indicating segmented transmission, the first data has not been fully transmitted), while a number of 1 or 2 indicates that this data is the second segment of the first data (implicitly indicating segmented transmission, the first data has been fully transmitted).

[0446] Optionally, in step 1007: the second device sends indication information or downlink data to the first device, the indication information being used to indicate / trigger an access opportunity.

[0447] The instruction information may include one or more of the following: Paging signaling, or Query signaling, or Query Rep signaling.

[0448] In the example of Figure 10, the first device can save the storage location information of the first data and the data volume of the first part of the data (or the end position or segment position of the first part of the data in the first data) without the second device informing the first device.

[0449] Example 3:

[0450] The following example illustrates how segmented transmission can be triggered by core network devices or upper layers. For instance, a downlink (DL) command might instruct the transmission of a specific portion of data.

[0451] Figure 11 shows a flowchart of a communication method.

[0452] Optionally, step 1101: The second device sends the data volume (which may be referred to as the suggested data volume) to the core network equipment.

[0453] Here, "data volume" can be understood as: the maximum amount of data that the second device suggests or allows the first device to transmit each time, or the maximum amount of data that each device can transmit each time. Optionally, this data volume can determine how many bits or bytes the core network will divide the entire application layer (or non-access layer) data into for segmented transmission.

[0454] The amount of data may be related to the coverage level and / or modulation and coding scheme (MCS) configuration parameters.

[0455] Optionally, step 1102: The first device randomly connects to the second device.

[0456] The order of steps 1101 and 1102 is not restricted.

[0457] Before sending the first portion of data, the first device accesses the second device or the network. The first device may perform random access to the second device, which can be contention-free random access (CFRA) or contention-based random access (CBRA). Alternatively, the first device may not perform random access and may access the second device or the network via mobile terminated (MT). For example, the second device may send a paging message to the first device, skipping random access and directly triggering the first device to send data. Optionally, the paging message may include query signaling.

[0458] Step 1103a: The core network device sends the first downlink command (DL command) to the second device.

[0459] In addition to carrying command instructions (such as read, write, etc.), the downlink command may also carry information about the first storage area. This information about the first storage area is related to segmented transmission (i.e., the amount of data suggested by the second device). The core network equipment can determine whether to perform segmented transmission, and how many segments to transmit, and thus determine the information about the first storage area carried in the downlink command.

[0460] The core network device can determine the information of the first storage area based on the data volume suggested in step 1101. For example, the data volume in the first storage area is less than or equal to the data volume suggested in step 1101.

[0461] Step 1103b: The second device sends a first downlink command (DL command) to the first device.

[0462] The second device can be the one that transmits the first downlink command (DL command).

[0463] Step 1104a: The first device sends the first part of the first data to the second device.

[0464] The starting position of the first part of the data is the starting position of the first storage area, and the ending position of the first part of the data is the ending position of the first storage area.

[0465] Step 1104b: The second device sends the first part of the first data to the core network equipment.

[0466] Optionally, the second device can transmit the first part of the data.

[0467] Step 1105a: The core network equipment sends a second downlink command (DL command) to the second device.

[0468] Step 1105b: The second device sends a second downlink command (DL command) to the first device.

[0469] In addition to carrying command instructions (such as read, write, etc.), the second downlink command can also carry information about the second storage area. This information about the second storage area is related to segmented transmission. The positions of the first and second storage areas are consecutive; for example, the start position of the second storage area is the end position of the first storage area, which ensures the continuity of data transmission.

[0470] Step 1106a: The first device sends the second part of the first data to the second device.

[0471] The starting position of the second part of the data is the starting position of the second storage area, and the ending position of the second part of the data is the ending position of the second storage area.

[0472] Step 1106b: The second device sends the second part of the first data to the core network equipment.

[0473] Optionally, the second device may transmit the second portion of data.

[0474] If the first data is transmitted in two segments, the first data transmission is completed after step 1106b. If the first data is transmitted in three segments or more, a process similar to steps 1105a, 1105b, 1106a, and 1106b can be repeated after step 1106b until the data transmission is complete.

[0475] Optionally, in step 1107: the core network device sends an indication message to the second device, which is used to indicate that the data transmission is complete.

[0476] Accordingly, the second device receives the instruction information.

[0477] After receiving the indication information from the core network device, the second device can determine that the data transmission is complete; or, if the core network device does not send the indication information to the second device, and the second device does not receive a downlink command from the core network device within a set time period, it can also be considered that the data transmission is complete.

[0478] Optionally, in step 1108: the second device sends an indication message to the first device, which is used to indicate / trigger an access opportunity.

[0479] The instruction information may include one or more of the following: Paging signaling, or Query signaling, or Query Rep signaling.

[0480] It is understood that, in order to achieve the functions in the above embodiments, the first device, the second device, and the core network equipment include hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0481] Figures 12 and 13 are schematic diagrams of possible communication devices provided in embodiments of this application. These communication devices can be used to implement the functions of the first device, the second device, or the core network equipment in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.

[0482] As shown in Figure 12, the communication device 1200 includes a processing unit 1210 and a transceiver unit 1220.

[0483] For example, the communication device 1200 is used to implement the functions of the first device, the second device, or the core network device in the method embodiments shown in Figures 3 to 11. The transceiver unit 1220 can perform the receiving and transmitting actions performed by the first device, the second device, or the core network device in the method embodiments. The processing unit 1210 can perform other actions besides the transmitting and receiving actions performed by the first device, the second device, or the core network device in the method embodiments.

[0484] For example, when the communication device 1200 is used to implement the function of the first device in the method embodiment shown in FIG3, the transceiver unit 1220 is used to send a first portion of data in the first data, receive the data volume of the first portion of data and / or the storage location information of the first data, and send a second portion of data in the first data. The processing unit 1210 is used to determine the start position of the second data based on the data volume of the first portion of data and the storage location information of the first data.

[0485] For example, when the communication device 1200 is used to implement the function of the second device in the method embodiment shown in FIG3, the transceiver unit 1220 is used to receive a first portion of data in the first data, the amount of data to be sent in the first portion of data and / or the storage location information of the first data, and to receive a second portion of data in the first data. The processing unit 1210 is used to determine the amount of data in the first portion of data.

[0486] A more detailed description of the processing unit 1210 and the transceiver unit 1220 can be obtained directly from the relevant descriptions in the method embodiments shown in Figures 3 to 11, and will not be repeated here. The processing unit 1210 can be implemented by a processor, and the transceiver unit 1220 can be implemented by a transceiver.

[0487] It should be understood that the division of units in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, all units in the device can be implemented entirely through software calls from processing elements; all units can be implemented entirely in hardware; or some units can be implemented through software calls from processing elements, and others in hardware. For example, each unit can be a separate processing element, or it can be integrated into a chip within the device. Alternatively, it can be stored as a program in memory, called and executed by a processing element of the device. Moreover, these units can be fully or partially integrated together, or implemented independently. The processing unit here can also be called a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, the operations of the above methods or the various units can be implemented through integrated logic circuits in the processor element or through software calls from processing elements.

[0488] In one example, a unit in any of the above devices can be one or more integrated circuits configured to implement the methods described above, such as: one or more application-specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these forms of integrated circuits. As another example, when a unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a processor, such as a general-purpose central processing unit (CPU), or other processor capable of calling programs. Furthermore, these units can be integrated together to implement a system-on-a-chip (SOC).

[0489] The receiving unit described above is an interface circuit of this device, used to receive signals from other devices. For example, when the device is implemented as a chip, this unit is an interface circuit for the chip to receive signals from other chips or devices. The transmitting unit described above is an interface circuit of this device, used to transmit signals to other devices. For example, when the device is implemented as a chip, this unit is an interface circuit for the chip to transmit signals to other chips or devices.

[0490] As shown in Figure 13, the communication device 1300 includes a processor 1310 and an interface circuit 1320. The processor 1310 and the interface circuit 1320 are coupled to each other. It is understood that the interface circuit 1320 can be a transceiver or an input / output interface. Optionally, the communication device 1300 may also include a memory 1330 for storing instructions executed by the processor 1310, or storing input data required for the processor 1310 to execute instructions, or storing data generated after the processor 1310 executes instructions. Sometimes, the interface circuit 1320 can also be understood as part of the processor 1310, in which case the communication device 1300 includes the processor 1310.

[0491] When the communication device 1300 is used to implement the methods shown in Figures 3 to 11, the processor 1310 is used to implement the functions of the processing unit 1210, and the interface circuit 1320 is used to implement the functions of the transceiver unit 1220.

[0492] When the aforementioned communication device is a chip applied to a terminal device, the terminal device chip implements the functions of the terminal device in the above method embodiments. The terminal device chip receives information from a network device, which can be understood as the information being first received by other modules (such as an RF module or antenna) in the terminal device, and then sent to the terminal device chip by these modules. The terminal device chip sends information to a network device, which can be understood as the information being first sent to other modules (such as an RF module or antenna) in the terminal device, and then sent to the network device by these modules.

[0493] When the aforementioned communication device is a chip applied to a network device, the network device chip implements the functions of the network device in the above method embodiments. The network device chip receives information from the terminal device, which can be understood as the information being first received by other modules (such as radio frequency modules or antennas) in the network device, and then sent to the network device chip by these modules. The network device chip sends information to the terminal device, which can be understood as the information being sent down to other modules (such as radio frequency modules or antennas) in the network device, and then sent to the terminal device by these modules. Here, the network device module can be the baseband chip of the network device, or a DU (Digital Unit) or other modules. The DU here can be a DU under the Open Radio Access Network (O-RAN) architecture.

[0494] In this application, entity A sends information to entity B, either directly or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be network devices or terminal devices, or modules within network devices or terminal devices. The sending and receiving of information can be between network devices and terminal devices, between two network devices (e.g., CU and DU), or between different modules within a single device (e.g., a terminal device chip and other modules within the terminal device, or a network device chip and other modules within the network device).

[0495] It is understood that the processor in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0496] This application also provides a computer-readable storage medium storing a computer program that, when executed by a computer, enables the computer to perform the aforementioned communication method. Alternatively, the computer program includes instructions for implementing the aforementioned communication method.

[0497] This application also provides a chip including a processor. When the processor executes a computer program or instructions, it implements the communication method provided above. Optionally, the chip may further include a memory. The chip may be composed of a single chip or may include chips and other discrete devices. The memory is used to store computer programs or instructions.

[0498] The application also provides a circuit for performing the communication method described above. This circuit may include a chip circuit. Optionally, the circuit may also be coupled to a memory.

[0499] This application also provides a computer program product, including: computer program code, which, when run on a computer, enables the computer to execute the communication method provided above.

[0500] This application also provides a communication system, which includes at least two of a first device, a second device, and a core network device that perform the above-described communication method.

[0501] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, compact disc read-only memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a base station or terminal. Of course, the processor and storage medium can also exist as discrete components in the base station or terminal.

[0502] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a first control plane network element, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer program or instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0503] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0504] In this application embodiment, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A or B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. Expressions such as "at least one of the following" or "one or more of them" refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b and / or c, or one or more of a, b and / or c, means: a, b, c, a and b, a and c, b and c, or a and b and c. Each of a, b, and c can be single or multiple.

[0505] The ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority, or importance of the multiple objects. Furthermore, such names do not indicate differences in the content, sending / receiving end, sending order, size, application scenario, priority, or importance of the two pieces of information. Additionally, the numbering of steps in the various embodiments described in this application is only to distinguish different steps and is not used to limit the order of steps.

Claims

1. A communication method characterized by comprising: Applied to a first device, comprising: sending a first message, the first message comprising a first part of data in first data; receiving first information, the first information comprising a data amount of the first part of data and / or storage location information of the first data; sending a second message, the second message comprising a second part of data in the first data, a start position of the second part of data in the first data being determined based on the data amount of the first part of data and the storage location information of the first data.

2. The method of claim 1, wherein, The data amount of the first part of data is the byte length of the first part of data.

3. The method of claim 2, wherein, In the case that the first information comprises the data amount of the first part of data, the length of the first information is 7 bits.

4. The method according to any one of claims 1 to 3, characterized in that, Further comprising: receiving a transport block data amount TBS, the TBS being used by the first device to determine a data amount of transmitted data; in the case that the transport block data amount is less than a data amount of a bearer message of the first data, sending a first part of data in the first data.

5. The method of claim 4, wherein, The bearer message comprises: a medium access control service data unit, or a non-access stratum protocol data unit.

6. The method according to any one of claims 1 to 5, wherein, Before sending the first message, further comprising: receiving downlink data, the downlink data comprising the storage location information of the first data.

7. The method according to any one of claims 1 to 6, wherein Further comprising: sending third information, the third information being used to indicate that the first data is not transmitted completely, or the first part of data is not the last part of data in the first data, or the first part of data is non-deliverable data, or there is first data to be transmitted, or the first part of data is part of the first data, and requesting to continue transmitting data.

8. The method of claim 7, wherein, The field length of the third information is 1 bit.

9. The method of claim 8, wherein, The value of the 1 bit is 1.

10. The method according to any one of claims 7 to 9, characterized in that, The third information is contained in the first message; or, After sending the first message, before receiving the first information, the third information is sent.

11. The method of claim 10, wherein, Before receiving the first information, further comprising: receiving second information, the second information being used to indicate triggering random access.

12. The method according to any one of claims 7 to 11, characterized in that, The third information comprises a first identifier, the first identifier being used to identify the first device.

13. The method of any one of claims 1-12, wherein, Further comprising: sending fourth information, the fourth information being used to indicate that the first data has been transmitted completely, or there is no first data to be transmitted, or the second part of data is the last part of data in the first data, or the second part of data is deliverable data, or the first data is deliverable data.

14. The method of claim 13, wherein, The length of the fourth information is 1 bit.

15. The method of claim 14, wherein, The value of the 1 bit is 0.

16. The method according to any one of claims 13 to 15, wherein, The second message comprises the fourth information.

17. The method of claim 1, wherein, Further comprising: saving the data amount of the first part of data or the storage location information of the first data.

18. The method of claim 1 or 17, wherein, The storage location information of the first data is contained in a downlink command.

19. The method of any one of claims 1-10, wherein, After sending the first message, before sending the second message, further comprising: receiving second information, the second information being used to trigger random access; not responding to the second information.

20. A method of communication, comprising: Applied to a second device, comprising: receiving a first message from a first device, the first message comprising a first part of data in first data; sending first information to the first device, the first information being used for indicating a data amount of the first part of data and / or storage location information of the first data; receiving a second message from the first device, the second message comprising a second part of data in the first data, a starting position of the second part of data in the first data being determined based on the data amount of the first part of data and the storage location information of the first data.

21. The method of claim 20, wherein, The data amount of the first part of data is a byte length of the first part of data.

22. The method of claim 21, wherein, In a case where the first information comprises the data amount of the first part of data, a length of the first information is 7 bits.

23. The method of any one of claims 20-22, wherein, Further comprising: receiving a data amount TBS of a transport block, the TBS being used for the first device to determine a data amount of transmitted data; in a case where the data amount of the transport block is less than a data amount of a bearer message of the first data, sending a first part of data in the first data.

24. The method of claim 23, wherein, The bearer message comprises a medium access control service data unit or a non-access stratum protocol data unit.

25. The method of any one of claims 20-24, wherein, The storage location information of the first data is contained in a downlink command.

26. The method of any one of claims 20-25, wherein, Before receiving the first message, further comprising: sending downlink data, the downlink data comprising the storage location information of the first data.

27. The method of any one of claims 20-26, wherein, Further comprising: determining that the data amount of the first part of data is less than a data amount of the first data.

28. The method of any one of claims 20-26, wherein, Further comprising: receiving third information from the first device, the third information being used for indicating that the first data is not transmitted completely, or the first part of data is not a last part of data in the first data, or the first part of data is non-deliverable data, or there is first data to be transmitted, or the first part of data is part of the first data.

29. The method of claim 28, wherein, A field length of the third information is 1 bit.

30. The method of claim 29, wherein, The 1 bit is valued as 1.

31. The method of claim 30, wherein, The third information is contained in the first message; or After receiving the first message from the first device, before sending the first information to the first device, receiving third information from the first device.

32. The method of claim 31, wherein, Before sending the first information to the first device, further comprising: sending second information, the second information being used for indicating triggering random access.

33. The method of any one of claims 28-32, wherein, The sending the first information to the first device comprises: based on the third information, sending the first information to the first device.

34. The method of any one of claims 28-33, wherein, The third information comprises a first identifier, the first identifier being used for identifying the first device.

35. The method of any one of claims 20-34, wherein, Further comprising: receiving fifth information from a core network device, the fifth information being used for indicating continuing to transmit data.

36. The method of claim 35, wherein, The sending the first information to the first device comprises: based on the fifth information, sending the first information to the first device.

37. The method of any one of claims 20-36, wherein, Further comprising: sending the first part of data and / or the second part of data to the core network device.

38. The method of any one of claims 20-37, wherein, Further comprising: receiving fourth information, the fourth information being used for indicating that the first data is transmitted completely, or there is no first data to be transmitted, or the second part of data is a last part of data in the first data, or the second part of data is deliverable data, or the first data is deliverable data.

39. The method of claim 38, wherein, A length of the fourth information is 1 bit.

40. The method of claim 39, wherein, The 1 bit is valued as 0.

41. The method of any one of claims 38-40, wherein, The second message comprises the fourth information.

42. A communications device, characterized by comprising means for performing the method of any of claims 1-19, or means for performing the method of any of claims 20-41.

43. A communications device, characterized by comprising a processor coupled to a memory; the memory for storing computer programs or instructions; the processor for executing part or all of the computer programs or instructions in the memory, when the part or all of the computer programs or instructions are executed, for implementing the method of any of claims 1-19, or for implementing the method of any of claims 20-41.

44. A chip system, characterized by comprising a processor coupled to a memory; the memory for storing computer programs or instructions; the processor for executing part or all of the computer programs or instructions in the memory, when the part or all of the computer programs or instructions are executed, for implementing the method of any of claims 1-19, or for implementing the method of any of claims 20-41.

45. A computer-readable storage medium, comprising: the storage medium has stored therein computer programs or instructions, when the computer programs or instructions are executed by the communication device, for implementing the method of any of claims 1-19, or for implementing the method of any of claims 20-41.

46. A computer program product, characterised in that, the computer program product comprises computer instructions, when the computer instructions are run on a computer, for causing the method of any of claims 1-19 to be implemented, or for causing the method of any of claims 20-41 to be implemented.

Images