Communication method, apparatus and system, and storage medium and program product

Abstract

Provided in the embodiments of the present application are a communication method, apparatus and system, and a storage medium and a program product. The method comprises: a first apparatus sending a first message to a second apparatus; and the first apparatus further receiving a second message from the second apparatus, wherein the time offset between a first moment corresponding to the first message and a second moment corresponding to the second message is a first time offset, and the first time offset is associated with at least one of whether forward error correction (FEC) channel coding is used for the second message, and the message type of the second message. In the embodiment, it can be ensured, on the basis of a first time offset, that a first apparatus can receive a second message from a second apparatus; moreover, an excessively long waiting period before the first apparatus receives the second message can be avoided, thereby reducing the transmission latency.

Description

Communication methods, devices, systems, storage media and software products

[0001] This application claims priority to Chinese Patent Application No. 202510392018.9, filed with the China National Intellectual Property Administration on March 28, 2025, entitled "Communication Method, Apparatus, System, Storage Medium and Program Product", and priority to Chinese Patent Application No. 202510604165.8, filed with the China National Intellectual Property Administration on May 9, 2025, entitled "Communication Method, Apparatus, System, Storage Medium and Program Product", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to a communication method, apparatus, system, storage medium, and program product. Background Technology

[0003] With the development of communication technology, the 3rd Generation Partnership Project (3GPP) defined the Ambient Internet of Things (A-IoT) technology. A-IoT technology can be applied to logistics, warehousing, industrial manufacturing, identification, environmental monitoring, and more. A-IoT communication includes reader-to-device (R2D) communication and device-to-reader (D2R) communication. The protocol specifies that D2R communication requires 1 / 3 convolutional code (CC) for forward error correction (FEC) channel coding, but the initial value of the convolutional code register has not yet been determined. Currently, there are two solutions: tail-biting convolutional code (TBCC) and head-biting convolutional code (HBCC). However, if HBCC is used, both the transmitting and receiving ends need to preprocess the information bit sequence, introducing additional complexity. However, when using TBCC, additional processing latency occurs compared to HBCC when cyclic redundancy check (CRC) is required for information bits. Ensuring that the reader can receive information from A-IoT devices when using TBCC is a problem that needs to be solved. Summary of the Invention

[0004] This application discloses a communication method, apparatus, system, storage medium, and program product that can ensure that the reader receives information from A-IoT devices.

[0005] In a first aspect, embodiments of this application provide a communication method. This method can be applied to a first device, which may be a reader / writer or a communication module within the reader / writer, or a circuit or chip applied to the reader / writer (such as a modem chip (also known as a baseband chip), or a system-on-chip (SoC) chip or system-in-package (SIP) chip containing a modem core). Taking the application of this method to a reader / writer as an example, in this method, the reader / writer sends first information to a second device. The reader / writer also receives second information from the second device. The minimum or maximum value of the interval between the first time point corresponding to the first information and the second time point corresponding to the second information is the first time interval. The reader / writer further processes the second information to obtain third information. The first time interval is related to the bit size of the third information.

[0006] In this example, based on the first time interval, it can be ensured that the reader can receive the second information from the second device; and it can also avoid the reader waiting too long to receive the second information, thus reducing transmission latency.

[0007] Wherein, the first moment corresponding to the first information is the moment when the reader finishes sending the first information, and the second moment corresponding to the second information is the moment when the second device starts sending the second information. It is understood that the moment when the reader is ready to start receiving the second information is earlier than or equal to the moment when the second device starts sending the second information. For example, the reader may be ready to start receiving the second information after completing an uplink / downlink switch and can begin waiting for and / or receiving the second information. It is also understood that there is at least a first time interval between the moment when the second device finishes receiving the aforementioned first information and the moment when the second device starts sending the second information. Furthermore, it is understood that there is at most a first time interval between the moment when the reader finishes sending the aforementioned first information and the moment when the reader is ready to start receiving the second information.

[0008] In one possible implementation, the first time interval is also associated with one or more of the following: a chip length of the second information, a time-domain repetition factor, a CRC length for the third information, and whether the second information is subjected to FEC channel decoding.

[0009] In a first possible implementation, the first time interval is associated with the bit size of the third information, as well as with a chip length of the second information and a time-domain repetition factor.

[0010] In the second possible implementation, the first time interval is associated with the bit size of the third information and also with the bit length of the fourth information. In this implementation, the reader performs FEC channel decoding on the second information to obtain the fourth information.

[0011] In a third possible implementation, the first time interval is associated with the bit size of the third information and with the length of the CRC used for the third information. For example, the first time interval is 'a' when the length of the CRC used for the third information is 0. The first time interval is 'b' when the length of the CRC used for the third information is not 0. Here, b > a, and a and b are both positive numbers.

[0012] In one possible implementation, ba is associated with the bit size of the aforementioned third information. That is, ba is determined based on the bit size of the third information. For example, ba is associated with the bit size of the third information and also with the length of the CRC used for the third information.

[0013] In another possible implementation, ba is associated with the bit size of the third information, and also with one or more of the following: a chip length of the second information, and a time-domain repetition factor.

[0014] In another possible implementation, ba is associated with the bit size of the third information and also with the bit length of the fourth information.

[0015] In a fourth possible implementation, the first time interval is associated with the bit size of the third information, and with one or more of the chip length of the second information, the time-domain repetition factor, and the length of the CRC used for the third information.

[0016] In the fifth possible implementation, the first time interval is associated with the bit size of the third information, the bit length of the fourth information, and the length of the CRC used for the third information.

[0017] In the sixth possible implementation, the aforementioned first time interval is related to the bit size of the third information and also to whether the third information is FEC channel coded. For example, the first time interval corresponding to the second information obtained by FEC channel coding the third information is greater than the first time interval corresponding to the second information obtained without FEC channel coding. Optionally, the first time interval corresponding to the second information obtained by using TBCC when FEC channel coding the third information is greater than the time interval corresponding to the second information obtained without FEC channel coding.

[0018] In the seventh possible implementation, the first time interval is related to the bit size of the third information, as well as whether the third information is FEC channel coded, the chip length of the second information, and the time-domain repetition factor.

[0019] In the eighth possible implementation, the first time interval is related to the bit size of the third information, as well as whether the third information is FEC channel coded and the bit length of the fourth information.

[0020] In the ninth possible implementation, the aforementioned first time interval is associated with the bit size of the third information, as well as with whether the third information is FEC channel coded and the length of the CRC used for the third information.

[0021] In the tenth possible implementation, the first time interval is associated with the bit size of the third information, as well as with whether the third information is FEC channel coded, the length of the CRC used for the third information, the chip length of the second information, and the time-domain repetition factor.

[0022] In the eleventh possible implementation, the first time interval is associated with the bit size of the third information, and also with whether the third information is FEC channel coded, the length of the CRC used for the third information, and the bit length of the fourth information.

[0023] In one possible implementation, the first time interval is greater than the second time interval, which is associated with one or more of the chip length of the second information and the time-domain repetition factor. The second time interval can be understood as the time interval corresponding to the second information obtained without FEC channel coding of the third information. Alternatively, it can be understood as the time interval corresponding to the second information obtained by TBCC coding of the third information, where the CRC length of the third information is 0.

[0024] In one possible implementation, the CRC length used for the third information is greater than 0. The reader performs FEC channel decoding on the second information to obtain the fourth information, where the FEC is a tail-biting convolutional code (TBCC). The reader then verifies the fourth information based on this CRC to obtain the third information.

[0025] In one possible implementation, the second information is an uplink message following message 3 during the random access process, or the second information is a response message corresponding to the first command message, which is message 4 during the random access process. For example, the first command is read or write.

[0026] In one possible implementation, when the second information is message 1 (hereinafter Msg1) or message 3 (hereinafter Msg3) in the random access process, the first time interval corresponding to message 1 in the random access process is the same as the first time interval corresponding to message 3 in the random access process.

[0027] Secondly, embodiments of this application provide a communication method. This method can be applied to a second device, which may be an A-IoT device or a communication module within an A-IoT device, or a circuit or chip (such as a modem chip, or a SoC chip or SIP chip containing a modem core) applied to an A-IoT device. Taking the application of this method to an A-IoT device as an example, in this method, the A-IoT device receives first information from a first device. The A-IoT device encodes third information to obtain second information. The A-IoT device also sends the second information to the first device, wherein the minimum or maximum value of the interval between the first time corresponding to the first information and the second time corresponding to the second information is a first time interval; this first time interval is associated with the bit size of the aforementioned third information.

[0028] In this example, based on the first time interval, it can be ensured that the reader can receive the second information from the A-IoT device; and by preventing the reader from missing the second information, the probability of the A-IoT device successfully connecting is increased.

[0029] In one possible implementation, the first time interval is also associated with at least one of the following: a chip length of the second information, and a time-domain repetition factor.

[0030] In one possible implementation, the A-IoT device uses TBCC to encode the third information to obtain the second information.

[0031] For other implementation methods of this part, please refer to the record in the first part, which will not be repeated here.

[0032] Thirdly, this application provides a communication device that has the functions of the first aspect above. For example, the communication device includes modules, units, or means that perform the operations involved in the first aspect above. These modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0033] In one implementation, the communication device includes: a communication module for sending first information to a second device;

[0034] The communication module is also used to receive second information from the second device, wherein the minimum or maximum value of the interval between the first time corresponding to the first information and the second time corresponding to the second information is the first time interval;

[0035] The processing module is used to decode the second information to obtain the third information, wherein the first time interval is related to the bit size of the third information.

[0036] For an introduction to this part, please refer to the record in the first section, which will not be repeated here.

[0037] Fourthly, this application also provides a communication device that has the functions of the second aspect above. For example, the communication device includes modules, units, or means that perform the operations involved in the second aspect above. These modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0038] In one implementation, the communication device includes: a communication module for receiving first information from a first device;

[0039] The processing module is used to encode the third information to obtain the second information;

[0040] The communication module is further configured to send the second information to the first device, wherein the minimum or maximum value of the interval between the first time corresponding to the first information and the second time corresponding to the second information is the first time interval; the first time interval is associated with the bit size of the third information.

[0041] For details on this part, please refer to the second section; it will not be repeated here.

[0042] Fifthly, this application also provides a communication method that can be applied to a first device, which may be a reader / writer or a communication module within the reader / writer, or a circuit or chip applied to the reader / writer (such as a modem chip (also known as a baseband chip), or a system-on-a-chip or system-in-package chip containing a modem core). Taking the application of this method to a reader / writer as an example, in this method, the reader / writer sends a first message to a second device. The reader / writer also receives a second message from the second device, wherein the time offset between the first time corresponding to the first message and the second time corresponding to the second message is a first time offset; the first time offset is associated with at least one of the following: whether the second message uses forward error correction (FEC) channel coding or not, and the message type of the second message.

[0043] In a possible implementation, the first time offset is associated with both whether the second information adopts the FEC channel coding and the message type of the second message.

[0044] In a possible implementation, when the message type of the second message is a first type, and when the second message adopts the FEC channel coding, the value of the first time offset includes b; when the second message does not adopt the FEC channel coding, the value of the first time offset includes a, where a < b, and a and b are positive numbers respectively.

[0045] In a possible implementation, when the message type of the second message is a second type, the value of the first time offset includes the a.

[0046] In a possible implementation, when the value of the message type of the second message is a first value, and when the second message adopts the FEC channel coding, the value of the first time offset includes c; when the second message does not adopt the FEC channel coding, the value of the first time offset includes d, where d < c, and c and d are positive numbers respectively.

[0047] In a possible implementation, when the value of the message type of the second message is a second value, the value of the first time offset includes the d.

[0048] In a possible implementation, the first time offset is associated with whether the second message adopts the FEC channel coding.

[0049] In a possible implementation, when the second message adopts the FEC channel coding, the first time offset is e; when the second message does not adopt the FEC channel coding, the first time offset is f, where e > f, and e and f are positive numbers respectively.

[0050] In a possible implementation, the first time offset is associated with the message type of the second message.

[0051] In a possible implementation, when the message type of the second message is a third type, the value of the first time offset includes g; when the message type of the second message is a fourth type, the value of the first time offset includes h, where g < h, and g and h are positive numbers respectively.

[0052] In a possible implementation, when a value of a message type of the second message is a third value, a value of the first time offset comprises i; when the value of the message type of the second message is a fourth value, the value of the first time offset comprises j, where i < j, and both i and j are positive numbers.

[0053] In a possible implementation, a first time instant corresponding to the first message corresponds to an end time instant of a padding portion in the first message, and a second time instant corresponding to the second message is a time instant when the second apparatus starts transmitting the second message.

[0054] In a possible implementation, a first time instant corresponding to the first message corresponds to an end position of a last orthogonal frequency division multiplexing (OFDM) symbol occupied by the first message, and a second time instant corresponding to the second message is a time instant when the second apparatus starts transmitting the second message.

[0055] In a possible implementation, a first time instant corresponding to the first message corresponds to a start time instant of a padding portion in the first message, and a second time instant corresponding to the second message is a time instant when the second apparatus starts transmitting the second message.

[0056] In a possible implementation, a first time instant corresponding to the first message corresponds to an end time instant of a preamble in the first message, and a second time instant corresponding to the second message is a time instant when the second apparatus starts transmitting the second message.

[0057] In a possible implementation, the first message does not include a padding portion, a first time instant corresponding to the first message is a time instant when the first apparatus finishes transmitting the first message, and a second time instant corresponding to the second message is a time instant when the second apparatus starts transmitting the second message.

[0058] In a possible implementation, the first time offset is associated with a bit size of the second message.

[0059] In a possible implementation, the first time offset is also associated with at least one of the following: a chip length of the second message, a small frequency shift factor of the second message, and a cyclic redundancy check (CRC) length used for the second message.

[0060] In a possible implementation, the FEC is tail-biting convolutional code (TBCC).

[0061] In a sixth aspect, the present application further provides a communication method, which can be applied to a first device. The first device may be a reader / writer, or a communication module in a reader / writer, or a circuit or chip for a reader / writer (such as a modulation and demodulation chip (also referred to as a baseband chip), or a system-on-chip or system-in-package chip including a modem core). Taking the application of the method to a reader / writer as an example, in the method, the reader / writer sends a first message to a second device. The reader / writer also receives a second message from the second device, wherein the time offset between a first time corresponding to the first message and a second time corresponding to the second message is a first time offset; the first time offset includes at least a first value and a second value, and the first value is a positive number smaller than the second value.

[0062] In a possible implementation, the first value corresponds to that the second message does not adopt FEC channel coding.

[0063] In a possible implementation, when the message type of the second message is a fifth type, the first value of the first time offset includes k, and the second value of the first time offset includes m, wherein k<m, and k and m are positive numbers respectively.

[0064] In a possible implementation, when the value of the message type of the second message is a fifth value, the first value of the first time offset includes n, and the second value of the first time offset includes p, wherein n<p, and n and p are positive numbers respectively.

[0065] In a possible implementation, the first time corresponding to the first message corresponds to the end time of a padding part in the first message, and the second time corresponding to the second message is the time when the second device starts sending the second message.

[0066] In a possible implementation, the first time corresponding to the first message corresponds to the end position of the last orthogonal frequency division multiplexing (OFDM) symbol occupied by the first message, and the second time corresponding to the second message is the time when the second device starts sending the second message.

[0067] In a possible implementation, the first time corresponding to the first message corresponds to the start time of a padding part in the first message, and the second time corresponding to the second message is the time when the second device starts sending the second message.

[0068] In a possible implementation, the first time corresponding to the first message corresponds to the end time of a postamble in the first message, and the second time corresponding to the second message is the time when the second device starts sending the second message.

[0069] In a possible implementation, the first message does not include a padding part, the first time instant corresponding to the first message is a time instant when the first device finishes sending the first message, and the second time instant corresponding to the second message is a time instant when the second device starts sending the second message.

[0070] In a possible implementation, the first time offset is associated with a bit size of the second message.

[0071] In a possible implementation, the first time offset is further associated with at least one of the following: a chip length of the second message, a small frequency shift factor of the second message, and a cyclic redundancy check (CRC) length used for the second message.

[0072] In a possible implementation, the FEC is tail-biting convolutional code (TBCC).

[0073] In a seventh aspect, embodiments of the present application provide a communication method. The method can be applied to a second device, where the second device may be an A-IoT device or a communication module in an A-IoT device, or applied to a circuit or a chip (such as a modem chip, an SoC chip including a modem core, or an SIP chip) of an A-IoT device. For example, when the method is applied to an A-IoT device, in the method, the A-IoT device receives a first message from a first device. The A-IoT device further sends the second message to the first device, where a time offset between a first time instant corresponding to first information and a second time instant corresponding to second information is a first time offset; and the first time offset is associated with at least one of whether the second message uses forward error correction (FEC) channel coding or not, and a message type of the second message.

[0074] In a possible implementation, the first time offset is associated with both whether the second information uses the FEC channel coding or not and the message type of the second message.

[0075] In a possible implementation, when the message type of the second message is a first type, and when the second message uses the FEC channel coding, a value of the first time offset includes b; when the second message does not use the FEC channel coding, the value of the first time offset includes a, where a < b, and a and b are positive numbers respectively.

[0076] In a possible implementation, when the message type of the second message is a second type, the value of the first time offset includes the a.

[0077] In a possible implementation, when the value of the message type of the second message is a first value and the second message adopts the FEC channel coding, the value of the first time offset comprises c; when the second message does not adopt the FEC channel coding, the value of the first time offset comprises d, where d < c, and c and d are positive numbers respectively.

[0078] In a possible implementation, when the value of the message type of the second message is a second value, the value of the first time offset comprises said d.

[0079] In a possible implementation, the first time offset is associated with whether the second message adopts the FEC channel coding or not.

[0080] In a possible implementation, when the second message adopts the FEC channel coding, the first time offset is e; when the second message does not adopt the FEC channel coding, the first time offset is f, where e > f, and e and f are positive numbers respectively.

[0081] In a possible implementation, the first time offset is associated with the message type of the second message.

[0082] In a possible implementation, when the message type of the second message is a third type, the value of the first time offset comprises g; when the message type of the second message is a fourth type, the value of the first time offset comprises h, where g < h, and g and h are positive numbers respectively.

[0083] In a possible implementation, when the value of the message type of the second message is a third value, the value of the first time offset comprises i; when the value of the message type of the second message is a fourth value, the value of the first time offset comprises j, where i < j, and i and j are positive numbers respectively.

[0084] In a possible implementation, the first time instant corresponding to the first message corresponds to the end time instant of the padding part in the first message, and the second time instant corresponding to the second message is the time instant when the second device starts transmitting the second message.

[0085] In a possible implementation, the first time instant corresponding to the first message corresponds to the end position of the last Orthogonal Frequency Division Multiplexing (OFDM) symbol occupied by the first message, and the second time instant corresponding to the second message is the time instant when the second device starts transmitting the second message.

[0086] In a possible implementation, the first time instant corresponding to the first message corresponds to a start time instant of a padding part in the first message, and the second time instant corresponding to the second message is a time instant at which the second apparatus starts to transmit the second message.

[0087] In a possible implementation, the first time instant corresponding to the first message corresponds to an end time instant of a postamble in the first message, and the second time instant corresponding to the second message is a time instant at which the second apparatus starts to transmit the second message.

[0088] In a possible implementation, the first message does not include a padding part, the first time instant corresponding to the first message is a time instant at which the first apparatus finishes transmitting the first message, and the second time instant corresponding to the second message is a time instant at which the second apparatus starts to transmit the second message.

[0089] In a possible implementation, the first time offset is associated with a bit size of the second message.

[0090] In a possible implementation, the first time offset is further associated with at least one of the following: a chip length of the second message, a small frequency shift factor of the second message, and a cyclic redundancy check (CRC) length used for the second message.

[0091] In a possible implementation, the FEC is tail-biting convolutional code (TBCC).

[0092] In an eighth aspect, embodiments of the present application provide a communication method. The method can be applied to a second apparatus, which may be an A-IoT device or a communication module in an A-IoT device, or a circuit or chip (such as a modem chip, or a SoC chip or SIP chip including a modem core) applied to an A-IoT device. Taking the application of the method to an A-IoT device as an example, in the method, the A-IoT device receives a first message from a first apparatus. The A-IoT device also transmits the second message to the first apparatus, where a time offset between a first time instant corresponding to first information and a second time instant corresponding to second information is a first time offset; the first time offset includes at least a first value and a second value, and the first value is a positive number less than the second value.

[0093] In a possible implementation, the first value corresponds to a case where the second message does not adopt FEC channel coding.

[0094] In a possible implementation, when the message type of the second message is a fifth type, the first value of the first time offset includes k, and the second value of the first time offset includes m, where k < m, and k and m are positive numbers respectively.

[0095] In a possible implementation, when the value of the message type of the second message is a fifth value, a first value of the first time offset comprises n, and a second value of the first time offset comprises p, where n < p, and n and p are positive numbers respectively.

[0096] In a possible implementation, a first time instant corresponding to the first message corresponds to an end time instant of a padding part in the first message, and a second time instant corresponding to the second message is a time instant when the second device starts sending the second message.

[0097] In a possible implementation, a first time instant corresponding to the first message corresponds to an end position of a last orthogonal frequency division multiplexing (OFDM) symbol occupied by the first message, and a second time instant corresponding to the second message is a time instant when the second device starts sending the second message.

[0098] In a possible implementation, a first time instant corresponding to the first message corresponds to a start time instant of a padding part in the first message, and a second time instant corresponding to the second message is a time instant when the second device starts sending the second message.

[0099] In a possible implementation, a first time instant corresponding to the first message corresponds to an end time instant of a postamble in the first message, and a second time instant corresponding to the second message is a time instant when the second device starts sending the second message.

[0100] In a possible implementation, the first message does not comprise a padding part, a first time instant corresponding to the first message is a time instant when the first device finishes sending the first message, and a second time instant corresponding to the second message is a time instant when the second device starts sending the second message.

[0101] In a possible implementation, the first time offset is associated with a bit size of the second message.

[0102] In a possible implementation, the first time offset is further associated with at least one of the following: a chip length of the second message, a small frequency shift factor of the second message, and a cyclic redundancy check (CRC) length used for the second message.

[0103] In a possible implementation, the FEC is tail-biting convolutional code (TBCC).

[0104] Ninthly, this application provides a communication device that has the functions of the fifth aspect above. For example, the communication device includes modules, units, or means that perform the operations involved in the fifth aspect above. These modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0105] In one implementation, the communication device includes: a communication module for sending a first message to a second device;

[0106] The communication module is further configured to receive a second message from the second device, wherein the time offset between the first time corresponding to the first message and the second time corresponding to the second message is a first time offset; the first time offset is associated with at least one of the following: whether the second message uses forward error correction (FEC) channel coding or not, and the message type of the second message.

[0107] For details on this section, please refer to the fifth section; it will not be repeated here.

[0108] In a tenth aspect, this application provides a communication device that has the functions of the sixth aspect described above. For example, the communication device includes modules, units, or means that perform the operations involved in the sixth aspect. These modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0109] In one implementation, the communication device includes: a communication module for sending a first message to a second device;

[0110] The communication module is further configured to receive a second message from the second device, wherein the time offset between the first time corresponding to the first message and the second time corresponding to the second message is a first time offset; the first time offset includes at least a first value and a second value, wherein the first value is a positive number less than the second value.

[0111] For a detailed explanation of this section, please refer to the sixth section; it will not be repeated here.

[0112] Eleventhly, this application also provides a communication device that has the functions of the seventh aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the seventh aspect above. These modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0113] In one implementation, the communication device includes: a communication module for receiving a first message from a first device;

[0114] The communication module is further configured to send a second message to the first device, wherein the time offset between the first time corresponding to the first message and the second time corresponding to the second message is a first time offset; the first time offset is associated with at least one of the following: whether the second message uses forward error correction (FEC) channel coding or not, and the message type of the second message.

[0115] For a detailed explanation of this section, please refer to section seven; it will not be repeated here.

[0116] In a twelfth aspect, this application also provides a communication device that has the functions of the eighth aspect above. For example, the communication device includes modules, units, or means that perform the operations involved in the eighth aspect above. These modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0117] In one implementation, the communication device includes: a communication module for receiving a first message from a first device;

[0118] The communication module is further configured to send a second message to the first device, wherein the time offset between the first time corresponding to the first message and the second time corresponding to the second message is a first time offset; the first time offset includes at least a first value and a second value, wherein the first value is a positive number less than the second value.

[0119] For a detailed explanation of this section, please refer to section eight; it will not be repeated here.

[0120] In a thirteenth aspect, this application also provides a communication system, which includes a communication device as provided in any possible embodiment of the third aspect and a communication device as provided in any possible embodiment of the fourth aspect, or a communication device as provided in any possible embodiment of the ninth aspect and a communication device as provided in any possible embodiment of the eleventh aspect, or a communication device as provided in any possible embodiment of the tenth aspect and a communication device as provided in any possible embodiment of the twelfth aspect.

[0121] In a fourteenth aspect, this application provides a communication device including a processor, the processor being configured to execute a computer program or computer-executable instructions stored in a memory, and / or to cause the device to perform a method provided in any of the possible embodiments of the first, fifth, and sixth aspects via logic circuitry.

[0122] One possible implementation also includes memory. Alternatively, the memory and processor can be integrated together.

[0123] One possible implementation also includes an interface circuit.

[0124] In one possible implementation, the device is a chip or chip system.

[0125] In a fifteenth aspect, this application provides a communication device including a processor, the processor being configured to execute a computer program or computer-executable instructions stored in a memory, and / or to cause the device to perform a method provided in any of the possible embodiments of the second, seventh, and eighth aspects via logic circuitry.

[0126] One possible implementation also includes memory. Alternatively, the memory and processor can be integrated together.

[0127] One possible implementation also includes an interface circuit.

[0128] In one possible implementation, the device is a chip or chip system.

[0129] In a sixteenth aspect, this application also provides a communication system, which includes a communication device as provided in any possible embodiment of the fourteenth aspect and a communication device as provided in any possible embodiment of the fifteenth aspect.

[0130] In a seventeenth aspect, this application provides a computer-readable storage medium storing a computer program that is executed by a processor to implement the method provided in any of the possible embodiments of the first, second, fifth to eighth aspects.

[0131] In an eighteenth aspect, this application provides a computer program product that, when run on a computer, causes the computer to perform a method provided by any of the possible implementations of the first, second, fifth to eighth aspects.

[0132] It is understood that the apparatus described in the third aspect, the apparatus described in the fourth aspect, the methods described in the fifth to eighth aspects, the apparatus described in the ninth to twelfth aspects, the system described in the thirteenth aspect, the apparatus described in the fourteenth aspect, the apparatus described in the fifteenth aspect, the system described in the sixteenth aspect, the computer storage medium described in the seventeenth aspect, or the computer program product described in the eighteenth aspect are all used to execute the methods provided in the first or second aspect. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here. Attached Figure Description

[0133] The accompanying drawings used in the embodiments of this application are described below.

[0134] Figure 1 is a schematic diagram of the architecture of the communication system 1000 used in the embodiments of this application;

[0135] Figure 2 is a schematic diagram of radio frequency identification communication;

[0136] Figure 3 is a schematic diagram of the structure of A-IoT device 1;

[0137] Figures 4a-4e are schematic diagrams of the network topology provided in the embodiments of this application;

[0138] Figure 5a is a schematic diagram of random access in an A-IoT system;

[0139] Figure 5b is a schematic diagram of a contention-based random access process for an A-IoT device;

[0140] Figure 6a is a schematic diagram of the time-domain waveform using a small frequency shift;

[0141] Figure 6b is a schematic diagram of the signal spectrum;

[0142] Figures 7a and 7b are schematic diagrams of convolutional code encoders;

[0143] Figure 8 is a schematic diagram of the tail-biting convolutional code;

[0144] Figure 9 is a schematic diagram of the biting head convolutional code;

[0145] Figure 10 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0146] Figure 11 is a schematic diagram of a data processing embodiment provided in this application;

[0147] Figure 12 is a schematic diagram of a first time interval provided in an embodiment of this application;

[0148] Figure 13 is a communication schematic diagram provided in an embodiment of this application;

[0149] Figure 14 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0150] Figures 15a, 15b, 16a, 16b, 16c, and 16d are schematic diagrams of the first time offset provided in the embodiments of this application;

[0151] Figure 17 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0152] Figures 18 and 19 are schematic diagrams of the communication device provided in the embodiments of this application;

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

[0154] The technical solutions provided in this application can be applied to various communication systems, such as 5G (5th generation mobile communication technology), future evolution systems, or multiple communication convergence systems, as well as existing communication systems. The application scenarios of the technical solutions provided in this application can include various scenarios, such as machine-to-machine (M2M), macro-micro communication, enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (uRLLC), and massive machine-type communication (mMTC). These scenarios may include, but are not limited to, communication scenarios between terminal devices, communication scenarios between network devices, and communication scenarios between network devices and terminal devices. Among these, network devices include access network devices and core network devices.

[0155] Figure 1 is a schematic diagram of the architecture of a communication system 1000 provided in an embodiment of this application. As shown in Figure 1, the communication system 1000 includes a radio access network (RAN) 100, wherein the RAN 100 includes at least one RAN node (110a and 110b in Figure 1, collectively referred to as 110), and may also include at least one terminal (120a-120j in Figure 1, collectively referred to as 120). The RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1). The terminal 120 is wirelessly connected to the RAN node 110. Terminals and RAN nodes can be interconnected via wired or wireless means. The communication system 1000 may also include a core network 200. The RAN node 110 is connected to the core network 200 via wireless or wired means. The core network equipment in core network 200 and the RAN node 110 in RAN 100 can be independent and different physical devices, or they can be the same physical device that integrates the logical functions of the core network equipment and the logical functions of the RAN node. Communication system 1000 may also include Internet 300.

[0156] RAN100 can be an evolved universal terrestrial radio access (E-UTRA) system, a new radio (NR) system, or a future radio access system as defined in the 3rd generation partnership project (3GPP), or it can be a WiFi system. RAN100 can also include two or more of the above-mentioned different radio access systems. RAN100 can also be an open RAN (O-RAN).

[0157] RAN nodes, also known as radio access network devices, RAN entities, or access nodes, are used to help terminals access communication systems wirelessly. In one application scenario, an RAN node can be a base station, an evolved NodeB (eNodeB), a transmission and reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. RAN nodes can be macro base stations (as shown in Figure 1, 110a), micro base stations or indoor stations (as shown in Figure 1, 110b), relay nodes, or donor nodes.

[0158] In another application scenario, multiple RAN nodes can collaborate to help terminals achieve wireless access, with different RAN nodes implementing different functions of the base station. For example, a RAN node can be a central unit (CU), a distributed unit (DU), or a radio unit (RU). Here, the CU performs the functions of the base station's Radio Resource Control (RRC) and Packet Data Convergence Protocol (PDCP), and can also perform the functions of the Service Data Adaptation Protocol (SDAP). The DU performs the functions of the base station's Radio Link Control (RANC) and Medium Access Control (MAC) layers, and can also perform some or all of the physical layer functions. For specific descriptions of these protocol layers, refer to the relevant 3GPP technical specifications. The RU can be used to implement radio frequency signal transmission and reception. The CU and DU can be two independent RAN nodes or integrated into the same RAN node, such as within a baseband unit (BBU). The RU can be included in radio frequency equipment, such as in a remote radio unit (RRU) or an active antenna unit (AAU). The CU can be further divided into two types of RAN nodes: CU-control plane and CU-user plane.

[0159] In different systems, RAN nodes may have different names. For example, in an O-RAN system, a CU can be called an open CU (O-CU), a DU can be called an open DU (O-DU), and an RU can be called an open RU (O-RU). The RAN nodes in the embodiments of this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. For example, a RAN node can be a server loaded with the corresponding software modules. The embodiments of this application do not limit the specific technology or device form used in the RAN nodes. For ease of description, a base station is used as an example of a RAN node in the following description.

[0160] A terminal is a device with wireless transceiver capabilities, capable of sending signals to or receiving signals from a base station. Terminals can also be called terminal equipment, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technology or device form used in the terminal.

[0161] Base stations and terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the base stations and terminals.

[0162] The roles of base stations and terminals can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile base station. For terminals 120j that access the wireless access network 100 through 120i, terminal 120i is a base station; however, for base station 110a, 120i is a terminal, meaning that 110a and 120i communicate via a wireless air interface protocol. Of course, 110a and 120i can also communicate via a base station-to-base station interface protocol. In this case, relative to 110a, 120i is also a base station. Therefore, both base stations and terminals can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be called communication devices with base station functions, and 120a-120j in Figure 1 can be called communication devices with terminal functions.

[0163] Communication between base stations and terminals, between base stations, and between terminals can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can be conducted using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.

[0164] In the embodiments of this application, the functions of the base station can be executed by modules (such as chips) within the base station, or by a control subsystem that includes base station functions. This control subsystem, including base station functions, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal can be executed by modules (such as chips or modems) within the terminal, or by a device that includes terminal functions.

[0165] In this application, the base station sends downlink signals or downlink information to the terminal, with the downlink information carried on the downlink channel; the terminal sends uplink signals or uplink information to the base station, with the uplink information carried on the uplink channel. To communicate with the base station, the terminal needs to establish a radio connection on a cell controlled by the base station. The cell with which the terminal has established a radio connection is called the terminal's serving cell. When the terminal communicates with this serving cell, it is also susceptible to interference from signals from neighboring cells.

[0166] With the increasing prevalence of 5G NR machine-type communication (MTC) and Internet of Things (IoT) communication, the number of connected IoT devices is growing daily. Therefore, the industry's demand for reduced cost and power consumption in IoT devices is becoming increasingly strong. During the 4G era, the 3rd Generation Partnership Project (3GPP) introduced narrowband IoT (NB-IoT) systems. However, NB-IoT terminals still require external power (batteries) and have the ability to generate local high-frequency carrier waves, thus limiting their power consumption to milliwatts. However, with the evolution and development of 5G IoT, the need for lower-power terminals in 5G networks is growing, and radio frequency identification (RFID) technology provides a good technical reference for low power consumption, supporting microwatt-level power consumption. RFID terminals (tags) use low-precision, low-power mid-to-low frequency ring oscillators or receive downlink signals without a local oscillator. When the tag is working, the energy and carrier wave for communication are supplied by the reader, and communication is based on reflected carrier waves. Figure 2 shows a schematic diagram of radio frequency identification communication. Curve 1 represents the carrier wave sent by the reader, and curve 2 represents the tag modulating and reflecting the carrier wave sent by the reader for transmission.

[0167] Given the low power consumption advantage of RFID communication technology, 5G A-IoT technology has emerged. To meet ultra-low power consumption requirements, terminals in A-IoT also use low-precision, low-power mid-to-low frequency ring oscillators or receivers without a local oscillator to receive downlink signals. This receiving method further reduces the power consumption of downlink reception. However, for such low-power receiving methods, only amplitude detection, such as envelope detection, can be performed because a low-precision ring oscillator alone cannot guarantee accurate demodulation of signal phase information.

[0168] Existing RFID terminals are low in cost and design complexity, but suffer from poor coverage and limited applicability. During the research of 5G A-IoT, coverage enhancement designs also encounter some challenges.

[0169] A-IoT technology can be applied to logistics, warehousing, industrial manufacturing, identity recognition, environmental monitoring, and more.

[0170] I. A-IoT:

[0171] Passive IoT technology refers to IoT without a "source," where "source" refers to a power source. Currently, the most common and mature passive IoT technology is Radio Frequency Identification (RFID), which uses radio frequency to read and write data to recording media (electronic tags or RFID cards). The basic principle of RFID is to use backscattering to complete energy conversion and communication. An RFID system generally includes a reader and an RFID tag. The reader transmits electromagnetic waves of a certain frequency through an antenna; when the RFID tag enters the working range of the transmitting antenna, it is activated by an induced current, and then transmits its stored information through its internal antenna; the transmission process involves load modulation of the received electromagnetic waves. The reader's antenna receives the carrier signal from the RFID tag and transmits it back to the reader.

[0172] Traditional RFID has several drawbacks, such as short transmission distance and a limited reading range of only a few meters. It typically requires handheld scanning, leading to labor-intensive and time-consuming operations. Furthermore, the lack of interference management solutions results in severe interference and capacity issues between RFID readers, especially in densely deployed scenarios, making it difficult for RFID to support seamless, large-scale networks.

[0173] Therefore, A-IoT was proposed to support backscatter communication technology in cellular systems.

[0174] A-IoT, also known as passive IoT, offers lower power consumption and lower cost compared to NB-IoT within the 3GPP standard framework. In non-3GPP frameworks, A-IoT targets the market demand for RFID, providing comparable and even more advantageous technical solutions.

[0175] The demand for A-IoT stems from addressing scenarios not covered by current 3GPP technologies, such as the following three scenarios:

[0176] 1) Under extreme environmental conditions, such as high pressure, extremely high / low temperature, and humid environments.

[0177] 2) Scenarios such as ultra-low complexity, very small device size / shape factor (e.g., thickness in millimeters), maintenance-free (e.g., traditional batteries that do not require device replacement) and longer life cycle.

[0178] 3) Device scenarios where traditional battery-powered devices are not applicable.

[0179] A-IoT can provide Internet of Things (IoT) services and features characteristics such as battery-free operation, low power consumption, low complexity, low cost, small size, and long lifespan. Compared to traditional IoT technologies, an A-IoT system includes A-IoT devices and readers. For example, a reader can also be called an interrogator. For example, an A-IoT device can also be called an A-IoT terminal, A-IoT, or a device with A-IoT functionality identified by a tag.

[0180] A-IoT devices are powered by energy harvesting, allowing them to operate without batteries or with limited energy storage (i.e., using capacitors). They can communicate with other devices without traditional power sources or avoid human intervention for charging or replacement. A-IoT devices can harvest energy from radio waves or, in specific use cases, from any other form of energy. For example, in some scenarios, A-IoT devices can harvest energy from radio waves, which may originate from 5G New Radio (NR) network entities or UEs. In other scenarios, A-IoT devices can harvest energy from solar energy, light, motion / vibration, heat, pressure, or any other source.

[0181] II. Device types of A-IoT devices:

[0182] In one possible example, an A-IoT device can have the following two characteristics:

[0183] A-IoT device 1 has a peak power consumption of approximately 1 microwatt (μW), energy storage capability, a sampling clock frequency offset (SFO) as high as 10 x ppm, and no signal amplification capability. Here, ppm represents parts per million. Device-to-reader (D2R) transmission of A-IoT device 1 is based on backscatter transmission using an externally provided carrier frequency. D2R refers to the transmission process from the A-IoT device to the reader (such as a network device or terminal device), which is described in detail below.

[0184] Figure 3 shows a schematic diagram of the structure of A-IoT device 1, which includes the following modules:

[0185] (1) Antenna: Radio frequency (RF) energy reception and receiver / transmitter can be shared or separated.

[0186] (2) Matching network: Matches the impedance between the antenna and other parts (including the RF energy harvester and receiver-related modules).

[0187] (3) RF energy harvester: including rectifier, which converts radio frequency signals (AC) into DC.

[0188] (4) Energy storage (e.g., capacitor): Storing collected energy from an RF energy receiver.

[0189] (5) Power Management Unit (PMU): Manages the energy stored from the energy harvester and provides energy to the active modules that need energy supply.

[0190] (6) Digital baseband logic (BB logics): including functional modules such as encoder, decoder, controller, etc.

[0191] (7) Memory: Includes two types of memory: 1) Non-volatile memory, such as electrically erasable programmable read-only memory (EEPROM), and permanent storage devices such as IDs. 2) Registers that temporarily store information, which can only store information when there is sufficient energy in the energy storage.

[0192] (8) Clock generator: provides clock signals.

[0193] (9) Receiving related modules:

[0194] RF band-pass filter (BPF): Improves frequency selectivity.

[0195] RF envelope detector: Converts RF signals to baseband.

[0196] Baseband low-pass filter (BB LPF): Filters out harmonics and high-frequency components, improving the signal quality input to the comparator.

[0197] Comparator: determines whether the input signal is high or low (level).

[0198] (10) Sending related modules:

[0199] Backscatter modulator: Switches the impedance to modulate the backscatter signal using the transmit signal from the baseband logic.

[0200] A-IoT device 2 has a peak power consumption of several hundred microwatts, energy storage capabilities, a SFO of up to 10X ppm, and signal amplification capabilities. Furthermore, based on the source of the carrier frequency used for transmission, A-IoT device 2 can be divided into A-IoT device 2a and A-IoT device 2b. Specifically, A-IoT device 2a's D2R transmission is based on backscatter transmission using an externally provided carrier frequency, while A-IoT device 2b's D2R transmission is based on a carrier frequency generated internally within the device.

[0201] This application mainly relates to A-IoT devices 1.

[0202] In another possible example, an A-IoT device can have the following three characteristics:

[0203] A-IoT device A: No energy storage, no independent signal generation / amplification, such as backscattering.

[0204] A-IoT device B: It has energy storage but does not generate independent signals, such as backscattering. The stored energy can be used to amplify the feedback signal.

[0205] A-IoT device C: It has energy storage and independent signal generation, such as the transmission of active radio frequency components.

[0206] III. Network Topology of A-IoT:

[0207] 3GPP defines several A-IoT topologies, as shown in Figures 4a-4e.

[0208] Network Topology 1: Interaction between Network Devices and A-IoT Devices

[0209] Please refer to Figure 4a, which is a schematic diagram of a topology provided in an embodiment of this application. In Figure 4a, the A-IoT device and the network device communicate bidirectionally. The network device can send a reader-to-device (R2D) signal to the A-IoT device; the A-IoT device receives the R2D signal sent from the network device; optionally, the A-IoT device sends a corresponding response signal to the network device (this response signal can be a backscattered signal). Correspondingly, the A-IoT device can send a D2R signal to the network device; the network device receives the D2R signal from the A-IoT device; optionally, the network device sends a corresponding response signal to the A-IoT device.

[0210] It should be noted that, in Figure 4a, the transmission from the network device to the A-IoT device can be referred to as "R2D" transmission, and the transmission from the A-IoT device to the network device can be referred to as "D2R" transmission. Optionally, in Figure 4a, the reader / writer can be a network device.

[0211] In some possible implementations, a network device is a device with wireless transceiver capabilities. In some implementations, the network device may be responsible for air interface-side radio resource management (RRM), quality of service (QoS) management, data compression and encryption, and data transmission and reception.

[0212] In some possible implementations, network devices may include base stations (BS) in a communication system or devices deployed in a radio access network (RAN) to provide wireless communication functions; that is, network devices may include devices in the RAN. For example, devices in the RAN may include evolved node B (eNB or eNodeB) in an LTE communication system, next-generation evolved node B (ng-eNB) in an NR communication system, next-generation node B (gNB) in an NR communication system, master node (MN) in a dual-connectivity architecture, secondary node (SN) in a dual-connectivity architecture, etc., without specific limitations.

[0213] In some possible implementations, network devices may include devices in the core network (CN). For example, devices in the CN may include access and mobility management functions (AMF), user plane functions (UPF), session management functions (SMF), etc.

[0214] In some possible implementations, network devices can also be access points (APs) in Wireless Local Area Networks (WLANs), relay stations, communication devices in future evolved PLMN networks, and communication devices in Non-Terrestrial Networks (NTNs).

[0215] In some possible implementations, the network device may include means for providing wireless communication capabilities to terminal devices, such as a chip system, a chip, or a chip module. For example, the chip system may include a chip, or it may include other discrete devices.

[0216] In some possible implementations, network devices can communicate with Internet Protocol (IP) networks, such as the Internet, private IP networks, or other data networks.

[0217] In some possible implementations, the network device may include a single node to perform the functions of the aforementioned base station, or it may include two or more independent nodes to perform the functions of the aforementioned base station. For example, the network device includes centralized units (CUs) and distributed units (DUs), such as gNB-CU and gNB-DU.

[0218] In some possible implementations, the network device can be any of the multiple sites that perform coherent joint transmission (CJT) with the terminal device, or other sites outside of the multiple sites, or other network devices that communicate with the terminal device, without any specific restrictions.

[0219] In some possible implementations, the network device can have mobility characteristics; for example, the network device can be a mobile device. Optionally, the network device can be a satellite or a balloon station. For example, the satellite can be a low Earth orbit (LEO) satellite, a medium Earth orbit (MEO) satellite, a geostationary Earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device can also be a base station located on land, water, or other similar locations.

[0220] In some possible implementations, network devices can provide services to a cell, and terminal devices within that cell can communicate with the network devices via transmission resources (such as spectrum resources). This cell can be a macro cell, small cell, metro cell, micro cell, pico cell, or femto cell, etc.

[0221] In some possible implementations, the network device described in the embodiments of this application may be a chip, chip module, device, unit, etc., and there are no specific limitations on it.

[0222] Network Topology 2: Network devices interact with A-IoT devices through intermediate nodes:

[0223] Please refer to Figure 4b, which is a schematic diagram of another topology provided in an embodiment of this application. In Figure 4b, since the network device and the A-IoT device cannot communicate directly, the intermediate node can relay the communication between the network device and the A-IoT device. In Figure 4b, the transmission from the intermediate node to the A-IoT device can be called "R2D" transmission, and the transmission from the A-IoT device to the intermediate node can be called "D2R" transmission. In Figure 4b, optionally, the reader / writer can refer to the intermediate node.

[0224] Specifically, the network device sends R2D data to the intermediate node. The intermediate node then assembles the R2D data into an R2D signal and sends it directly to the A-IoT device, or processes the R2D data to assemble an R2D signal before sending it to the A-IoT device. The R2D data can be the data portion of the R2D signal. Correspondingly, the A-IoT device receives the R2D signal. Optionally, the A-IoT device sends a corresponding response signal to the intermediate node (this response signal can be a backscattered signal). Optionally, the intermediate node forwards the response signal to the network device, or processes the response signal before sending it to the network device. The network device and the intermediate node can communicate via the Uu interface. The A-IoT device sends a D2R signal to the intermediate node. The intermediate node then forwards the D2R data from the signal to the network device, or processes the D2R data before sending it to the network device. Correspondingly, the network device receives the D2R data, which can be the data portion of the D2R signal. Optionally, the network device sends a corresponding response signal to the intermediate node. Alternatively, the intermediate node forwards the response signal to the A-IoT device, or processes the response signal before sending it to the A-IoT device. The network device and the intermediate node can communicate via a Uu interface.

[0225] In some possible implementations, an intermediate node is a device with wireless transceiver capabilities. For example, an intermediate node could be a terminal device. For example, intermediate nodes can be eNBs, eNodeBs, gNodeBs, gNBs, multi-transmission receiving points (M-TRPs), base stations in subsequent evolution systems, access nodes in WLAN systems, mobile phones, terminals, remote UEs, relay UEs, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), tablets, computers with wireless transceiver capabilities, virtual reality (VR) devices, augmented reality (AR) devices, wireless devices in industrial control, wireless devices in autonomous driving, wireless devices in remote medical care, wireless devices in smart grids, wireless devices in transportation safety, wireless devices in smart cities, and wireless devices in smart homes. Wireless devices in the home, in-vehicle devices, wearable devices, or terminal devices in future public land mobile networks (PLMNs), etc.

[0226] For a detailed description of the network equipment, please refer to Figure 4a; it will not be repeated here.

[0227] Network Topology 3: Interaction between network devices and auxiliary nodes, A-IoT devices:

[0228] “Network Topology 3” is divided into R2D-assisted network topology and D2R-assisted network topology.

[0229] Please refer to Figure 4c. The topology in Figure 4c can be called an R2D-assisted network topology, which is another topology diagram provided in the embodiments of this application. In the R2D-assisted network topology, network devices cannot directly send R2D signals to A-IoT devices, while A-IoT devices can directly send D2R signals to network devices and receive R2D signals from the auxiliary node. Optionally, for R2D, the reader / writer can be an auxiliary node; for D2R, the reader / writer can be a network device.

[0230] Specifically, the network device sends R2D data to the auxiliary node; then, the auxiliary node can either assemble the R2D data into an R2D signal and directly forward it to the A-IoT device, or process the R2D data to assemble an R2D signal before sending it to the A-IoT device. The R2D data can be the data portion of the R2D signal. Correspondingly, the A-IoT device receives the R2D signal from the auxiliary node. The A-IoT device can also directly send D2R signals to the network device. The network device and the auxiliary node can communicate via the Uu interface.

[0231] In Figure 4c, the transmission from the auxiliary node to the A-IoT device can be called "R2D" transmission, and the transmission from the A-IoT device to the network device can be called "D2R" transmission.

[0232] Please refer to Figure 4d. The topology in Figure 4d can be called a D2R-assisted network topology, which is another topology diagram provided in the embodiments of this application. In the D2R-assisted network topology, A-IoT devices cannot directly send D2R signals to network devices, but A-IoT devices can receive R2D signals from network devices and then send D2R signals to the auxiliary node. Optionally, for R2D, the reader / writer can be a network device; for D2R, the reader / writer can be an auxiliary node.

[0233] Specifically, network devices can send R2D signals to A-IoT devices. Correspondingly, after receiving the R2D signal from the network device, the A-IoT device can optionally send a D2R signal to the auxiliary node. The auxiliary node then forwards the D2R data from the D2R signal to the network device, or processes the D2R data in the D2R signal before sending it to the network device. The D2R data can be the data portion of the D2R signal. The network device and the auxiliary node can communicate via the Uu interface.

[0234] In Figure 4d, the transmission from the network device to the A-IoT device can be called "R2D" transmission, and the transmission from the A-IoT device to the auxiliary node can be called "D2R" transmission.

[0235] In some possible implementations, an auxiliary node is a device with wireless transceiver capabilities. For example, an auxiliary node can be an eNB, eNodeB, gNodeB, gNB, M-TRP, a base station in a subsequent evolution system, an access node in a WLAN system, a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, a VR terminal, an AR terminal, a wireless terminal in industrial control, a vehicle terminal, a wireless terminal in autonomous driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a wearable terminal, etc.

[0236] Network Topology 4: Interaction between Terminal Devices and A-IoT Devices

[0237] Please refer to Figure 4e, which is a schematic diagram of another topology provided in an embodiment of this application. In Figure 4e, the A-IoT device and the terminal device communicate directly in both directions. The reader / writer can refer to the terminal device.

[0238] Specifically, the terminal device sends an R2D signal to the A-IoT device, and the A-IoT device receives the R2D signal sent by the terminal device. Optionally, the A-IoT device sends a corresponding response signal to the terminal device. Correspondingly, the A-IoT device sends a D2R signal to the terminal device; the terminal device receives the D2R signal sent by the A-IoT device, and optionally, the terminal device sends a corresponding response signal to the A-IoT device (this response signal can be a backscattered signal).

[0239] The terminal device in this application is a device with wireless transceiver capabilities, and may be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, remote station, remote terminal, mobile device, wireless communication device, UE agent, or UE device, etc. The terminal device can be fixed or mobile. It should be noted that the terminal device can support at least one wireless communication technology, such as Long Term Evolution (LTE) or New Radio (NR). For example, terminal devices can be mobile phones, tablets, desktop computers, laptops, all-in-one computers, in-vehicle terminals, virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, wearable devices, terminal devices in future mobile communication networks, or terminal devices in future evolved public land mobile networks (PLMNs), etc. In some embodiments of this application, the terminal device may also be a device with transceiver functions, such as a chip system. The chip system may include a chip, and may also include other discrete components.

[0240] In the above description, "direct" means that the signal transmission does not pass through auxiliary nodes or intermediate nodes. However, in actual transmission, it may need to pass through other devices, such as routers in the communication link.

[0241] In summary, in this embodiment, the A-IoT system may include network nodes and A-IoT devices. The network node may be one of the network devices, intermediate nodes, or auxiliary nodes shown in Figures 4a to 4e. The intermediate or auxiliary node serves as a relay for transmission between the network device and the A-IoT device.

[0242] IV. D2R / R2D Transmission:

[0243] In this embodiment, the communication between the reader / writer and the A-IoT device is referred to as R2D, which can also be called R2D transmission, R2D communication, R2D signal transmission, or R2D information transmission. Optionally, the R2D signal can also be called the A-IoT R2D signal, and the data portion therein can be called R2D data or A-IoT R2D data. This embodiment does not impose any limitations on this.

[0244] Communication between A-IoT devices and readers is referred to as D2R, or D2R transmission, D2R communication, D2R signal transmission, or D2R information transmission. Optionally, the D2R signal can be called an A-IoT D2R signal, and the data portion can be called D2R data or A-IoT D2R data; this application does not limit the specific terminology used in the embodiments.

[0245] Optionally, the signal transmission between the reader and the A-IoT device can be D2R and / or R2D for any of the above network topologies, and this application does not impose any restrictions.

[0246] For the network topology shown in Figure 4a, R2D signal transmission refers to the network device directly sending R2D signals to the A-IoT device, and the A-IoT device directly receiving R2D signals from the network device. D2R signal transmission refers to the A-IoT device directly sending D2R signals to the network device, and the network device directly receiving D2R signals from the A-IoT device.

[0247] For the network topology shown in Figure 4b, R2D signal transmission refers to the network device sending R2D data to the intermediate node, the intermediate node assembling the R2D data into an R2D signal and sending it to the A-IoT device, and the A-IoT device receiving the R2D signal from the intermediate node. D2R signal transmission refers to the A-IoT device sending a D2R signal to the intermediate node, the intermediate node forwarding the D2R data in the D2R signal to the network device, and the network device receiving the D2R data from the intermediate node.

[0248] For the network topology shown in Figure 4c, R2D signal transmission refers to the network device sending R2D data to the auxiliary node, the auxiliary node assembling the R2D data into an R2D signal and sending it to the A-IoT device, and the A-IoT device receiving the R2D signal from the auxiliary node. D2R signal transmission refers to the A-IoT device sending a D2R signal to the network device, and the network device receiving the D2R signal from the A-IoT device.

[0249] For the network topology shown in Figure 4d, R2D signal transmission refers to the network device directly sending R2D signals to the A-IoT device, and the A-IoT device directly receiving R2D signals from the network device. D2R signal transmission refers to the A-IoT device sending D2R signals to the auxiliary node, the auxiliary node forwarding the D2R data in the D2R signal to the network device, and the network device receiving the D2R data from the auxiliary node.

[0250] For the network topology shown in Figure 4e, R2D signal transmission refers to the terminal device directly sending R2D signals to the A-IoT device, and the A-IoT device directly receiving R2D signals from the terminal device. D2R signal transmission refers to the A-IoT device directly sending D2R signals to the terminal device, and the terminal device directly receiving D2R signals from the A-IoT device.

[0251] In the above description, "direct" means that the signal transmission does not pass through auxiliary nodes or intermediate nodes. However, in actual transmission, it may need to pass through other devices, such as routers in the communication link.

[0252] For example, both A-IoT devices and readers can be implemented based on cellular network infrastructure. In other words, both A-IoT devices and readers can be devices within a cellular network. For instance, an A-IoT device can be implemented by a terminal within a cellular network, such as an ultra-low power, ultra-low complexity IoT terminal. The functionality of a reader can be implemented by network devices, such as base stations. Non-contact data communication can be performed between the network device and the terminal, thereby reading information from the terminal and / or writing information that needs to be stored into the terminal.

[0253] A-IoT technology can be used to implement one or more of the following functions: inventory management, location tracking, sensing, and commands. Command functions can be understood as implementing write or lock processes. In terms of application scope, A-IoT technology can be applied to scenarios such as logistics, warehousing, industrial manufacturing, identity recognition, or environmental monitoring.

[0254] The 3GPP plenary meeting defined an extremely low-power, extremely low-complexity Internet of Things (IoT) technology. It can be understood as an extension of radio frequency identification (RFID) technology in 3GPP. Although it shares some principles with RFID, such as similar inventory management processes, it introduces more value scenarios in 3GPP.

[0255] The inventory management process involves using readers to connect A-IoT devices within the coverage area. Once connected, each device needs to send its unique identifier (which the network can recognize, such as the electronic product code (EPC) in RFID) to the reader.

[0256] Positioning is the process of using location signals to pinpoint the location of A-IoT devices.

[0257] Sensing involves A-IoT devices reporting sensor data to the base station, such as temperature data.

[0258] The command can be some operation instructions, such as write and lock. The write process is that the BS sends a downlink command and data, instructing the A-IoT device to write the data into its own storage area. The lock process is that a downlink command is sent to instruct the A-IoT device to lock the location at a specified address in the storage area, and the contents of that storage area cannot be modified and / or read.

[0259] Random access:

[0260] Random access in A-IoT technology is a necessary process for establishing a wireless link between A-IoT devices and readers. Through this random access process, A-IoT devices establish uplink synchronization with readers and obtain uplink resources. There are two random access methods: contention-based and non-contention-based.

[0261] Contention-based random access:

[0262] Figure 5a illustrates random access in an A-IoT system. Random access in A-IoT technology mainly includes the following signaling:

[0263] R2D mainly includes paging, R2D trigger message, and message 2 (Msg2);

[0264] D2R mainly includes message 1 (Msg1) and message 3 (Msg3);

[0265] Control information can be carried in paging, R2D trigger messages, and Msg2.

[0266] A paging message is sent only once per paging cycle. The paging message carries the device ID to be paging and scheduling information. The first paging message sent is called the initial paging message.

[0267] R2D trigger messages are used to indicate Msg1 resources to A-IoT devices and are sent multiple times during a single inventory cycle. R2D trigger messages can also be called QueryRep-like messages or paging messages. If called QueryRep-like messages, their main difference from paging messages lies in the Media Access Control (MAC) header. If called paging messages, their difference from paging messages is that they do not carry a device identifier.

[0268] Figure 5b illustrates a contention-based random access procedure for an A-IoT device. This procedure includes the following steps:

[0269] S500. The reader sends message 0 (Msg0) (i.e., paging) to trigger the target A-IoT device to initiate random access.

[0270] S501. The A-IoT device sends Msg1 to the reader, where Msg1 carries a random identifier (random ID) generated by the A-IoT device.

[0271] S502. The reader sends a Physical Reader Device Channel (PRDCH) containing Msg2 as a response to the received Msg1 from the A-IoT device. Msg2 may contain the random ID from Msg1.

[0272] Msg2 is used for contention resolution, that is, when an A-IoT device receives Msg2 containing its own random ID, the A-IoT device considers the contention resolution successful.

[0273] PRDCH can carry one or more A-IoT devices, Msg2.

[0274] The S503.A-IoT device sends Msg3 to the reader, carrying upper-layer data (including device identifier and / or other upper-layer data).

[0275] The scheduling information for Msg3 is indicated by Msg2.

[0276] The following explains the terms that may be involved in the embodiments of this application:

[0277] 1. Chip: The time unit for D2R and R2D transmission is a chip, which is one level. For on-off keying (OOK) modulation (both D2R and R2D support OOK), the level refers to the duration of a high level or a low level.

[0278] 2. M: The length of a chip in R2D is equal to 1 / M of the length of an orthogonal frequency division multiplexing (OFDM) symbol, where M is a positive integer. The larger M is, the larger the bandwidth occupied by the R2D signal in the frequency domain.

[0279] 3. D2R Chip Length: The D2R chip length is affected by the time-domain repetition factor R. Frequency division multiple access (FDMA) requires small frequency shift (SFS) for implementation. Specifically, as shown in Figure 6a, which is a schematic diagram of the time-domain waveform using small frequency shift, let the bit before line code encoding be denoted as the information bit, and its length be denoted as the information bit length (which can be denoted as Tb). Then, the length of each chip after line code encoding and SFS is denoted as the D2R chip length (as shown in Figure 6a), and D2R chip length = Tb / (2×R).

[0280] 4. Time-domain repetition factor R: It can be understood that when R>1, relative to R=1, the frequency domain position of the signal corresponding to R>1 will shift or move ±R / T. b For example, as shown in Figure 6a, assuming information bit #1 is 0110, T b =266.66 microseconds (μs); when R=1, the signal #1 after Manchester encoding and SFS of information bit #1 can be 10010110, and the chip length of signal #1 is 133.33μs; when R=4, the signal #2 after Manchester encoding and SFS of information bit #1 can be 1010101001010101 01010101 10101010, and the chip length of signal #2 is 33.33μs.

[0281] Taking time interval #1 as an example, when R=1, the first bit 0 of information bit #1 is encoded as 10, and 10 is transmitted once in time interval #1. When R=4, the first bit 0 of information bit #1 is encoded as 10101010, that is, 10 is transmitted four times in time interval #1. Compared to R=1, R=4 is equivalent to shortening the chip length of R=1 to 1 / 4 and transmitting it four times. It can be understood that the above examples using R=1 and R=4 illustrate the time-domain characteristics of different values ​​of R. R can also take any other possible value, and its time-domain characteristics are similar to those of R=1 and R=4. These are for reference and understanding and are not limited to any specific value.

[0282] The following section continues with R=1 and R=4 as examples to introduce the frequency domain characteristics of different values ​​of R.

[0283] Assuming R=1, the effective bandwidth of signal #1 is 15 kilohertz (kHz). For example, the spectrum of signal #1 is shown in the left figure of Figure 6b (the horizontal axis is frequency (f) in kHz, and the vertical axis is power in decibels milliwatts (dBm)). The effective bandwidth of signal #1 can include single-sideband #1 and single-sideband #2. The effective bandwidth range of single-sideband #1 is -7.5kHz to 0kHz, and the effective bandwidth range of single-sideband #2 is 0kHz to 7.5kHz.

[0284] When R=4, the frequency domain position of signal #2 will shift or move ±4 / T relative to R=1. b For example, the spectrum of signal #2 is shown in the right figure of Figure 6b (horizontal axis is frequency in kHz; vertical axis is power in dBm). The effective bandwidth of signals #1 and #2 is the same, both being 15kHz. The effective bandwidth of signal #2 can include single-sideband #3 and single-sideband #4. The frequency domain position of single-sideband #3 is offset by -7.5kHz relative to single-sideband #1, that is, the effective bandwidth range of single-sideband #3 is -15kHz to (-7.5)kHz; similarly, the frequency domain position of single-sideband #4 is offset by +7.5kHz relative to single-sideband #2, that is, the effective bandwidth range of single-sideband #4 is 7.5kHz to 15kHz. It can be understood that the above uses R=1 and R=4 as examples to introduce the frequency domain characteristics of different values ​​of R. R can also take any other possible value, and its frequency domain characteristics are similar to those of R=1 and R=4. This can be used for reference and understanding without limitation.

[0285] In the embodiments of this application, the time-domain repetition factor can also be referred to as the small frequency shift factor.

[0286] 5. Forward Error Correction Channel Coding: The current standard has determined to use convolutional codes, and forward error correction channel coding is performed after CRC attachment. Figure 7a shows a schematic diagram of a convolutional code encoder with a code rate of 1 / 3. Convolutional codes convert the input bit sequence (c0,…,c…) into a single bit sequence. K-1 The input bit c of the FEC channel is multiplied modulo-2 by one or more generator polynomials, and the results are then output in parallel to form the encoded sequence. The convolutional code encoder used in the current AIoT device 1 is shown in Figure 7a. In Figure 7a, the convolutional code encoder includes 6 shift registers (represented by "D" in Figure 7a) and 12 XOR gates (represented by ⊕ in Figure 7a). The registers are used to store bit values, and the XOR gates are used to perform XOR operations. The generator polynomial can be in octal form [133, 171, 165]. Referring to Figure 7b, the input bit c of the FEC channel coding... k After entering the convolutional encoder, the output based on encoding branch 1, encoding branch 2, and encoding branch 3 is... That is, 1 bit input corresponds to 3 bits output. The input bit sequence (c0,…,c…) K-1 The output bits after convolutional coding are Furthermore, no sub-block interleaving is performed after convolutional encoding.

[0287] 6. Tail-biting convolutional code: As shown in Figure 8, the initial values ​​of the registers of the convolutional code encoder are the last 6 bits of the input bit sequence, i.e., s. i =C K-i-1 ,i=0,1,…,5, where s0,s1,…s5 represent the encoder's shift registers, and K is the length of the bit sequence to be encoded. The initial and final states of the shift registers are the same.

[0288] 7. Bit-head convolutional code: The initial values ​​of the registers of the convolutional code encoder are the first 6 bits of the input bit sequence, i.e., s. i =C i Let i = 0, 1, ..., 5. Here, K is the length of the bit sequence to be encoded. Furthermore, if a bit-biting convolutional code is used, as shown in Figure 9, the first 6 bits of the input bit sequence need to be shifted to the end, i.e., from c0, c1, c2, c3, c4, c5, ..., c K Change to c6,…,c K-1 c0, c1, c2, c3, c4, c5. The initial and final states of the shift registers are the same.

[0289] 8. Cyclic Redundancy Check (CRC)

[0290] CRC is used for error detection. The CRC check bits are performed using the entire D2R block. The bits are a0, a1, ..., a1. A-1Bits in a D2R block are represented by p0, p1, ..., p L-1 This represents the parity bits, where A is the payload size and L is the number of parity bits. The least significant bit a0 maps to the most significant bit of the D2R block.

[0291] The cyclic generator polynomial used to calculate the parity bits is:

[0292] When L=16, g is used CRC16 (D)=[D 16 +D 12 +D 5 +1]

[0293] When L=6, use g CRC6 (D)=[D 6 +D 5 +1]

[0294] Encoding is performed systematically, meaning that the remainder of the following polynomials in GF(2) divided by the corresponding CRC generator polynomial is equal to 0: a0D A+L-1 +a1D A+L-2 +…+a A-1 D L +p0D L-1 +p1D L-2 +…+p L-2 D 1 +p L-1

[0295] Then, p0, p1, ..., p L-1 Append to the D2R block, and if A > 24, set L to 16 bits; otherwise, set L to 6 bits.

[0296] The bits appended by the CRC are represented as b0, b1, ..., b B-1 Where B = A + L. And b k =a k for k = 0, 1, 2, ..., A-1 b k =p k-A for k = A, A+1, ..., A+L-1.

[0297] The process of adding CRC:

[0298] a) Let a0, a1, a2, a3, ..., a A-1 This represents the input bit sequence of the CRC to be appended, p0, p1, p2, p3, ..., p L-1 This represents the parity bit, where A is the size of the input sequence and L is the number of parity bits.

[0299] b) The output bit sequence is: a0, a1, a2, a3, ..., a A-1 ,p0,p1,p2,p3,…,p L-1 .

[0300] c) Taking CRC16 as an example, let the CRC generator polynomial used be D. 16 +D 12 +D 5 +1 = 10001000000100001.

[0301] d) First, a0, a1, a2, a3, ..., a A-1 Adding 16 zeros at the end gives a0, a1, a2, a3, ..., a A-1 ,0,…,0.

[0302] e) Then, a0, a1, a2, a3, ..., a A-1 Perform modulo-2 division on 0, ..., 0 and 10001000000100001, and take the lower 16 bits of the remainder.

[0303] f) Specifically, let A = 32, a0, a1, a2, a3, ..., a A-1 The result is [1,1,1,0,1,1,1,1,1,1,0,0,1,1,0,1,1,0,1,1,0,1,1,1,0,1,0,1,0,1,0,1,0,1,0,1]. The resulting check bit sequence is [1,0,1,1,1,0,0,1,0,1,1,0,1,0,0,0].

[0304] The architecture of the embodiments of this application has been described above. The methods of the embodiments of this application will be described in detail below.

[0305] Referring to Figure 10, a flowchart illustrating a communication method provided in an embodiment of this application is shown. Optionally, this method can be applied to the aforementioned communication system, such as the communication system shown in Figure 1. The communication method shown in Figure 10 may include steps 1001-1003. Steps 1001-1003 are as follows:

[0306] 1001. The first device sends first information to the second device. Accordingly, the second device receives the first information.

[0307] For example, the first device is a reader / writer. The second device is an A-IoT device (such as a device). Optionally, the first information can be an R2D trigger message, Msg2, or Msg4, etc. For a description of this part, please refer to the description of the embodiments shown in FIG5a and FIG5b above, and the description of the embodiment shown in FIG13, which will not be repeated here.

[0308] 1002. The second device encodes the third information to obtain the second information.

[0309] For example, the third information can be unencoded information. For instance, the third information could be the initial input D2R information. The second information is the encoded information. For instance, the second information could be a signal carried by the physical device-to-reader channel (PDRCH).

[0310] In one possible implementation, as shown in Figure 11, the second device adds a CRC to the third information. Optionally, the second device also performs FEC processing on the third information with the added CRC. For example, the second device performs TBCC processing on the third information with the added CRC. The second device also encodes the result of the FEC processing (such as line coding) and performs SFS processing on the encoded result. The second device further modulates the result of the SFS processing to obtain the aforementioned second information.

[0311] Understandably, the second device can also perform HBCC processing on the third information with added CRC, and this solution does not restrict this.

[0312] It is understandable that step 1002 can be executed after step 1001, before step 1001, or simultaneously, and this solution does not impose any restrictions on this.

[0313] Optionally, the first information may be the R2D trigger message in the aforementioned random access procedure, and the second information may be Msg1 in the random access procedure. Alternatively, the first information may be Msg2 in the random access procedure, and the second information may be Msg3 in the random access procedure. Alternatively, the first information may be Msg4, and the second information may be an uplink message following message 3 (Msg3) in the random access procedure, or the second information may be a response message (such as Msg5) corresponding to the first command message (such as Msg4). The first command may be read or write, etc.

[0314] 1003. The second device sends the aforementioned second information to the first device. The minimum or maximum value of the interval between the first time point corresponding to the first information and the second time point corresponding to the second information is the first time interval. This first time interval is related to the bit size of the aforementioned third information. Accordingly, the first device receives the second information.

[0315] The minimum or maximum value of the interval between the first time point corresponding to the first information and the second time point corresponding to the second information is the first time interval. That is, the minimum value of the interval between the first time point corresponding to the first information and the second time point corresponding to the second information is the first time interval. Alternatively, the maximum value of the interval between the first time point corresponding to the first information and the second time point corresponding to the second information is the first time interval.

[0316] Here, the first moment corresponding to the first information can be understood as the moment when the first device finishes sending the first information. The first device finishing sending the first information means that it has completed the action of sending the first information. The second moment corresponding to the second information can be understood as the moment when the second device starts sending the second information. As shown in Figure 12, the moment when the first device finishes sending the first information is t1, and the moment when the second device starts sending the second information is t2. The minimum interval between the two is the first time interval.

[0317] Understandably, the time when the first device is ready to start receiving the second information is earlier than or equal to the time when the second device starts sending the second information. This readiness of the first device to start receiving the second information could be, for example, by completing an uplink / downlink handover and beginning to wait for and / or receive the second information. For instance, as shown in Figure 12, the first device is prepared before the second device begins sending the second information, such as at time t3.

[0318] It is also understandable that there is at least a first time interval between the moment when the second device finishes receiving the first information and the moment when the second device starts sending the second information. Here, the second device finishing receiving the first information means that the second device has completed the action of receiving the first information.

[0319] It is also understandable that the time interval between the moment when the first device finishes sending the first information and the moment when the first device is ready to start receiving the second information is at most a first time interval.

[0320] Based on this example, it can be ensured that the first device can receive the second information from the second device; and it can avoid the first device waiting too long to receive the second information, thus reducing transmission latency.

[0321] The first time interval mentioned above is related to the bit size of the third information mentioned above. It can be understood that the first time interval is determined based on the bit size of the third information.

[0322] The following section introduces several ways to implement the first time interval.

[0323] In a first possible implementation, the first time interval is associated with the bit size of the third information, and also with one or more of the following: a chip length of the aforementioned second information, and a time-domain repetition factor. For example, the... Where 'a' is the first time interval used when the CRC length of the third information is 0. Alternatively, the first time interval = bit size of the third information × (chip length of the second information × time-domain repetition factor) + a. Another example: the first time interval = bit size of the third information × 2 × (chip length of the second information × time-domain repetition factor) + a. This scheme does not specifically limit this calculation method. Of course, the calculation of the first time interval can also be based on other designs, etc., and this scheme does not restrict this.

[0324] In a second possible implementation, the first time interval is associated with both the bit size of the third information and the bit length of the fourth information. Specifically, the second device adds a CRC checksum to the third information and performs FEC channel coding on the CRC-encoded third information to obtain the fourth information. The second device then performs SFS processing on the fourth information to obtain the aforementioned second information. For example, the first time interval = bit size of the third information × bit length of the fourth information + a. Wherein, the bit length of the fourth information = 2 × (one chip length of the second information × time-domain repetition factor).

[0325] In a third possible implementation, the first time interval is associated with the bit size of the third information and the length of the CRC used for that third information. For example, the first time interval is 'a' when the length of the CRC used for the third information is 0. The first time interval is 'b' when the length of the CRC used for the third information is not 0. Here, b > a, where a and b are both positive numbers. That is, the first time interval when the length of the CRC used for the third information is not 0 is greater than the first time interval when the length of the CRC used for the third information is 0. It can be understood that when the length of the CRC used for the third information is 0, that is, no CRC is added to the third information.

[0326] In one possible implementation, ba is associated with the bit size of the aforementioned third information. That is, ba is determined based on the bit size of the third information. For example, ba is associated with the bit size of the third information and also with the length of the CRC used for the third information.

[0327] In another possible implementation, ba is associated with the bit size of the third information, and also with one or more of the following: a chip length of the second information, and a time-domain repetition factor. For a description of this part, please refer to the foregoing records, which will not be repeated here.

[0328] In another possible implementation, ba is associated with the bit size of the third information and also with the bit length of the fourth information. For a description of this part, please refer to the above description; it will not be repeated here.

[0329] In a fourth possible implementation, the first time interval is associated with the bit size of the third information, and with one or more of the chip length of the second information and the time-domain repetition factor, as well as with the length of the CRC used for the third information. For a description of this part, please refer to the above description; it will not be repeated here.

[0330] In the fifth possible implementation, the aforementioned first time interval is associated with the bit size of the third information, the bit length of the fourth information, and the length of the CRC used for the third information. For a description of this part, please refer to the above description; it will not be repeated here.

[0331] In the sixth possible implementation, the aforementioned first time interval is related to the bit size of the third information and also to whether FEC channel coding is performed on the third information. For example, the first time interval corresponding to the second information obtained by FEC channel coding of the third information is greater than the first time interval corresponding to the second information obtained without FEC channel coding. Optionally, the first time interval corresponding to the second information obtained by using TBCC when FEC channel coding the third information is greater than the time interval corresponding to the second information obtained without FEC channel coding. It is understood that if the second device does not perform FEC channel coding on the third information or during the processing of the third information, no additional processing delay will occur during the process of the second device processing the third information to obtain the second information. Specifically, the time interval corresponding to the second information obtained without FEC channel coding is equal to the time interval corresponding to the second information obtained by using HBCC when FEC channel coding the third information.

[0332] In the seventh possible implementation, the first time interval is related to the bit size of the third information, as well as whether the third information is FEC channel coded, the chip length of the second information, and the time-domain repetition factor.

[0333] In the eighth possible implementation, the first time interval is related to the bit size of the third information, as well as whether the third information is FEC channel coded and the bit length of the fourth information.

[0334] In the ninth possible implementation, the aforementioned first time interval is associated with the bit size of the third information, as well as with whether the third information is FEC channel coded and the length of the CRC used for the third information.

[0335] In the tenth possible implementation, the first time interval is associated with the bit size of the third information, as well as with whether the third information is FEC channel coded, the length of the CRC used for the third information, the chip length of the second information, and the time-domain repetition factor.

[0336] In the eleventh possible implementation, the first time interval is associated with the bit size of the third information, and also with whether the third information is FEC channel coded, the length of the CRC used for the third information, and the bit length of the fourth information.

[0337] In one possible implementation, the first time interval is greater than the second time interval, and the second time interval is associated with one or more of the chip length of the second information and the time-domain repetition factor. The second time interval can be understood as the time interval corresponding to the second information obtained without FEC channel coding of the third information. Alternatively, it can be understood as the time interval corresponding to the second information obtained by TBCC coding of the third information, where the CRC length of the third information is 0. For a description of the second time interval, please refer to the above description of the first time interval; it will not be repeated here.

[0338] In one possible implementation, the CRC length of the third information is greater than 0. The second device adds a CRC to the third information and performs FEC channel coding on the CRC-encoded third information to obtain the fourth information, where the FEC is TBCC. The second device also performs SFS and other processing on the fourth information to obtain the aforementioned second information.

[0339] In one possible implementation, the first device further processes the second information to obtain the aforementioned third information. For example, the first device decodes the second information to obtain fourth information. The first device then performs FEC channel decoding and other processing on the fourth information according to TBCC to obtain the aforementioned third information.

[0340] In this embodiment, a first device sends first information to a second device. The second device encodes third information to obtain second information. The second device then sends the second information back to the first device. The minimum or maximum value of the interval between the first time corresponding to the first information and the second time corresponding to the second information is the first time interval. This first time interval is related to the bit size of the third information. In this example, based on this first time interval, it can be ensured that the first device can receive the second information from the second device, avoiding the first device missing the second information and increasing the probability of successful access for the second device; moreover, it can avoid the first device waiting too long to receive the second information, reducing transmission latency.

[0341] The method provided in this application will be described below with reference to several embodiments.

[0342] Example 1:

[0343] As shown in Figure 13, during the random access process, the A-IoT device sends Msg1 (as shown in the second information in the embodiment of Figure 10) and Msg3 (as shown in the second information in the embodiment of Figure 10) to the reader. Msg1 does not have a CRC checksum, and its corresponding first time interval T is set to... R2D,1 The interval is 13.8µs. A CRC checksum is added to Msg3, and the typical length of Msg3 (the length before CRC) can be set to 496 bits, i.e., K = 496. Assuming the chip length of D2R and R are 0.69µs and 1 respectively, then the first time interval T corresponding to Msg3 is... R2D,2 It can be represented as:

[0344] For example, after successfully receiving Msg3, the reader sends message 4 (Msg4), which carries command information including operation instructions such as "read" and "write". After successfully receiving Msg4, the A-IoT device sends message 5 (Msg5). If Msg4 carries a "read" instruction, then Msg5 contains the information that the A-IoT device needs to upload to the reader after reading it; if Msg4 carries a "write" instruction, then the A-IoT device will write the relevant content carried in Msg4 into its memory and return message Msg5 to the reader. This Msg5 is used as feedback, informing the reader that the "write" instruction has been successfully completed.

[0345] Understandably, in this example, the calculation method for the first time interval corresponding to Msg5 sent by the A-IoT device to the reader can be found in the calculation method for the first time interval corresponding to Msg3, and will not be repeated here.

[0346] In other words, in this example, the first time interval is associated with the length of the CRC. The first time interval when the CRC length is not 0 is greater than the first time interval when the CRC length is 0.

[0347] In another possible implementation, the first time interval T corresponding to Msg3 mentioned above... R2D,2 It can be represented as: T R2D,2 =T R2D,1 +K×ChipLength·R=13.8+496×0.69μs=356.0μs.

[0348] It is understandable that the calculation method for the first time interval corresponding to Msg5 can be found in the calculation method for the first time interval corresponding to Msg3, and will not be repeated here.

[0349] In another possible implementation, the first time interval T corresponding to Msg3 mentioned above... R2D,2 It can be represented as: T R2D,2 =T R2D,1 +K×2·ChipLength·R=13.8+2×496×0.69μs=698.3μs.

[0350] It is understandable that the calculation method for the first time interval corresponding to Msg5 can be found in the calculation method for the first time interval corresponding to Msg3, and will not be repeated here.

[0351] It should be noted that the above are just a few examples. The calculation method for the first time interval can also be based on other simple variations and designs. This solution does not limit this.

[0352] Example 2:

[0353] As shown in Figure 13, during the random access process, the A-IoT device sends Msg1 and Msg3 to the reader. Msg1 is not appended with a CRC checksum, while Msg3 is appended with a CRC checksum. It is assumed that the first time interval corresponding to Msg1 and Msg3 sent by the A-IoT device during the random access process is the same, both being T. R2D,1 That is, 13.8us, etc.

[0354] For example, during data transmission after the random access process, the A-IoT device sends Msg5 to the reader. Msg5 is appended with a CRC checksum, and its typical length (length before CRC) can be set to 800 bits, i.e., K = 800. Assuming the chip length and R of the D2R are 0.69µs and 1 respectively, then the first time interval T corresponding to Msg5... R2D，3 It can be represented as:

[0355] In another possible implementation, the first time interval T corresponding to Msg5 R2D,3 It can be represented as: T R2D,3 =T R2D,1 +K×ChipLength·R=13.8+800×0.69μs×1=565.8μs.

[0356] In yet another possible implementation, the first time interval T corresponding to Msg5 R2D,3 It can be represented as: T R2D,3 =T R2D,1+K×2·ChipLength·R=13.8+2×800×0.69μs×1=1117.8μs.

[0357] In other words, in this example, the first time interval of the D2R messages in the data transmission process after the random access procedure is greater than the first time interval of the D2R messages in the random access procedure. Furthermore, the first time interval of each D2R message in the random access procedure is the same.

[0358] It should be noted that the above are just a few examples. The calculation method for the first time interval can also be based on other simple variations and designs. This solution does not limit this.

[0359] Referring to Figure 14, another communication method provided in this application embodiment is illustrated. Optionally, this method can be applied to the aforementioned communication system, such as the communication system shown in Figure 1. The communication method shown in Figure 14 may include steps 1401-1403. Steps 1401-1403 are as follows:

[0360] 1401. The first device sends a first message to the second device. Accordingly, the second device receives the first message.

[0361] For example, the first device is a reader / writer. The second device is an A-IoT device. For a description of this part, please refer to the description of step 1001 in the embodiment shown in FIG10 above, which will not be repeated here.

[0362] 1402. The second device encodes the third message to obtain the second message.

[0363] For example, the third message can be the initial input D2R message. The second message is the encoded message. For a description of this part, please refer to the description of step 1002 in the embodiment shown in Figure 10 above, which will not be repeated here.

[0364] 1403. The second device sends the aforementioned second message to the first device. The time offset between the first time corresponding to the first message and the second time corresponding to the second message is called the first time offset. This first time offset is associated with at least one of the following: whether the second message uses FEC channel coding or not, and the message type of the second message. Accordingly, the first device receives the second message.

[0365] The aforementioned time offset (Toffset) can also be referred to as an interval (gap), time interval, etc. Correspondingly, the first time offset can also be referred to as the first time interval, etc.

[0366] In one possible implementation, the unit of time offset can be absolute time, such as microseconds (µs). In another possible implementation, the unit of time offset can be relative time, such as Tb. Tb represents the length of each information bit. This information bit can be a bit before or after FEC channel coding.

[0367] The aforementioned message types can be, for example, messages in contention-based random access (CBRA) or contention-free random access (CFRA). Of course, other message types are also possible, and this scheme does not impose any restrictions on them.

[0368] The following is an introduction to messages in CBRA:

[0369] QueyRep messages can also be called R2D trigger messages or Access Occasion Trigger messages.

[0370] Msg1 can also be referred to as Message 1 of the contention-based random access procedure, or a random ID message.

[0371] Msg2 can also be called Message 2 of the contention-based random access procedure, or random ID response message.

[0372] Msg3 can also be referred to as: D2R message for message 2 scheduling based on contention-based random access procedure, or D2R Upper Layer Data Transfer message.

[0373] Msg4 can also be called the R2D message following the contention-based random access procedure, or the R2D Upper Layer Data Transfer message.

[0374] Msg5 can also be referred to as the D2R message following a contention-based random access procedure, or the D2R Upper Layer Data Transfer message.

[0375] The following is an introduction to messages in CFRA:

[0376] A paging message may also be referred to as a QueryRep (QueyRep) message, an R2D trigger message, or an Access Occasion Trigger message.

[0377] A D2R message for scheduling a paging message may also be referred to as a paging message-triggered D2R message, a query repetition message-triggered D2R message, an R2D trigger message-triggered D2R message, or an access opportunity trigger message-triggered D2R message, or

[0378] An R2D message after a contention-free access-based random process may also be referred to as an R2D Upper Layer Data Transfer message.

[0379] A D2R message after a contention-free access-based random process may also be referred to as a D2R Upper Layer Data Transfer message, or a D2R message scheduled by an R2D message after a contention-free access-based random process.

[0380] In a possible implementation, the first time offset is associated with both whether the second message adopts FEC channel coding or not and the message type of the second message.

[0381] For example, when the message type of the second message is a first type: when the second message adopts the FEC channel coding, the value of the first time offset includes b; when the second message does not adopt the FEC channel coding, the value of the first time offset includes a, where a < b, and a and b are positive numbers respectively. Further, when the message type of the second message is a second type, the value of the first time offset includes a.

[0382] For example, the first type of the aforementioned second message is a D2R message corresponding to the R2D message after the random access procedure in CBRA. The first time offset between the R2D message after the random access procedure and the corresponding D2R message is: when the second message does not adopt the FEC channel coding, a is 30us; when the second message adopts the FEC channel coding, b is 1500us. For another example, the second type of the aforementioned second message is Msg1 in CBRA. The first time offset between Paging or QueryRep and Msg1 is: when the second message does not adopt the FEC channel coding, the value is 30us; when the second message adopts the FEC channel coding, the value is 60us. Alternatively, the first time offset between Paging or QueryRep and Msg1 is 30us regardless of whether the second message adopts the FEC channel coding or not.

[0383] For another example, the first type of the aforementioned second message is a D2R message corresponding to the R2D message after the random access procedure in CFRA. For the relevant introduction, reference can be made to the related records of the D2R message corresponding to the R2D message after the random access procedure in the aforementioned CBRA, which will not be repeated herein.

[0384] Alternatively, when the value of the message type of the second message is a first value: when the second message adopts the FEC channel coding, the value of the first time offset includes c; when the second message does not adopt the FEC channel coding, the value of the first time offset includes d. Wherein, d < c, and c and d are positive numbers respectively. Further, when the value of the message type of the second message is a second value, the value of the first time offset includes d. For example, when the message type of the second message is Msg1, the aforementioned value is 001. When the message type of the second message is Msg3, the aforementioned value is 010. When the message type of the second message is a D2R upper-layer data transmission message after the random access procedure in CBRA or CFRA, the aforementioned value is 100, etc.

[0385] In another possible implementation, the first time offset is associated with whether the second message adopts FEC channel coding or not.

[0386] Exemplarily, when the second message adopts the FEC channel coding, the first time offset is e; when the second message does not adopt the FEC channel coding, the first time offset is f. Wherein, e > f, and e and f are positive numbers respectively. That is, the time offset when the second message does not adopt the FEC channel coding is smaller than the time offset when the second message adopts the FEC channel coding.

[0387] For example, for a first time offset between an R2D message and a corresponding D2R message after a random access procedure in CBRA: when the second message does not adopt the FEC channel coding, the value of the first time offset is 30us; when the second message adopts the FEC channel coding, the value of the first time offset is 1500us. For another example, for a first time offset between an R2D message and a corresponding D2R after a random access procedure in CFRA: when the second message does not adopt the FEC channel coding, the value of the first time offset is 30us; when the second message adopts the FEC channel coding, the value of the first time offset is 1500us.

[0388] In another possible implementation, the first time offset is associated with a message type of the second message.

[0389] Exemplarily, when the message type of the second message is a third type, the value of the first time offset comprises g. When the message type of the second message is a fourth type, the value of the first time offset comprises h. Wherein, g < h, and g and h are positive numbers respectively.

[0390] Exemplarily, the message type of the above second message is a message in CBRA. For example, a first time offset between Paging or QueryRep and Msg1 is 30us. For another example, a first time offset between Msg2 and Msg3 is 30us. For another example, a first time offset between an R2D message after a CBRA random access procedure and a corresponding D2R is 1500us.

[0391] For another example, the message type of the above second message is a message in CFRA. For example, a first time offset between an R2D message after a CFRA random access procedure and a corresponding D2R message is 1500us.

[0392] Alternatively, when the value of the message type of the second message is a third value, the value of the first time offset comprises i. When the value of the message type of the second message is a fourth value, the value of the first time offset comprises j. Wherein, i < j, and i and j are positive numbers respectively. For the introduction of this part, reference may be made to the foregoing description, which will not be repeated herein.

[0393] In a possible implementation, the first time instant corresponding to the first message corresponds to the end time instant of a padding part in the first message, as shown in FIG. 15a. That is, the first time instant corresponding to the first message is the same as the time instant corresponding to the end position of a last padding chip. The second time instant corresponding to the second message is a time instant when a second apparatus starts sending the second message.

[0394] It should be noted that this example is described using the padding portion of the first message, but it can also be other parts of the first message or replaced with other descriptions, etc. This solution does not restrict this.

[0395] For example, the first time corresponding to the first message corresponds to the end position of the last orthogonal frequency division multiplexing (OFDM) symbol occupied by the first message, as shown in Figure 15a. The second time corresponding to the second message is the time when the second device starts sending the second message.

[0396] In another possible implementation, the first time corresponding to the first message corresponds to the start time of the padding portion in the first message, as shown in Figure 15b. That is, the first time corresponding to the first message is the same as the time corresponding to the start position of the first padding chip. The second time corresponding to the second message is the time when the second device begins to transmit the second message.

[0397] In another possible implementation, the first message does not include a padding portion, and the first time corresponding to the first message is the time when the first device finishes sending the first message. The second time corresponding to the second message is the time when the second device starts sending the second message.

[0398] In another possible implementation, the first time point corresponding to the first message corresponds to the end time of the postamble in the first message. The second time point corresponding to the second message is the time when the second device begins sending the second message.

[0399] For example, the first time offset includes several types, such as Toffset1, Toffset3, Toffset4, and Toffset5. Toffset1 and Toffset3 are defined in contention-based random access (CBRA). For an introduction to contention-based random access, please refer to the descriptions in Figures 5a and 5b above, which will not be repeated here. Referring to Figures 5a, 16a, and 16b, Toffset1 represents the time offset between a paging message (the initial paging message in Figure 5a) or a query repetition message (the R2D trigger message in Figure 5a) and the corresponding Msg1. Referring to Figures 5a and 16c, Toffset3 represents the time offset between Msg2 and the corresponding Msg3. Toffset4 and Toffset5 are defined in contention-free random access (CFRA). As shown in Figure 16d, the first R2D message (paging in Figure 16d) can also be a queryrep message or an R2D trigger message, etc. The first message in Figure 16d carries the device ID and / or any other upper-layer message. The second and third messages in Figure 16d are analogous to Msg4 and Msg5 in CBRA. Here, Toffset4 represents the time offset between the paging message and the first message, as shown in Figure 16d; it can also be called Toffset3. Toffset5 represents the time offset between the second and third messages, as shown in Figure 16d; it can also be called Toffset4.

[0400] Based on this example, it can be ensured that the first device can receive the second message from the second device; and the first device can avoid waiting too long to receive the second message, thus reducing transmission latency.

[0401] In one possible implementation, the first time offset is also associated with the bit size of the second message. This can be understood as the first time offset being determined based on the bit size of the second message.

[0402] In one possible implementation, the first time offset is also associated with at least one of the following: a chip length of the second message, a small frequency shift factor of the second message, and a cyclic redundancy check (CRC) length for the second message.

[0403] For details on this part, please refer to the description of step 1003 in the embodiment shown in Figure 10 above, which will not be repeated here.

[0404] It is understood that the message in this example can be equivalent to the relevant information in the embodiment shown in Figure 10 above, and this solution does not limit it.

[0405] In this example, based on the first time offset, it can be ensured that the first device can receive the second message from the second device, avoiding the first device missing the second message and increasing the probability of the second device successfully accessing the network; moreover, it can avoid the first device waiting too long to receive the second message, thus reducing transmission latency.

[0406] For example, referring to Figure 17, another communication method provided by an embodiment of this application is shown. Optionally, this method can be applied to the aforementioned communication system, such as the communication system shown in Figure 1. The communication method shown in Figure 17 may include steps 1701-1703. Steps 1701-1703 are as follows:

[0407] 1701. The first device sends a first message to the second device. Accordingly, the second device receives the first message.

[0408] For details on this part, please refer to the description of step 1001 in the embodiment shown in Figure 10 above, which will not be repeated here.

[0409] Optionally, it also includes 1702, whereby the second device encodes the third message to obtain the second message.

[0410] For details on this part, please refer to the description of step 1002 in the embodiment shown in Figure 10 above, which will not be repeated here.

[0411] 1703. The second device sends the aforementioned second message to the first device. The time offset between the first time corresponding to the first message and the second time corresponding to the second message is called the first time offset. This first time offset includes at least a first value and a second value, where the first value is a positive number less than the second value. Accordingly, the first device receives the second message.

[0412] For an introduction to the first time offset, please refer to the relevant description of the embodiment shown in Figure 14, which will not be repeated here.

[0413] The first value corresponds to the second message not using FEC channel coding. This can be understood as the first value being associated with the second message not using FEC channel coding. In other words, the first value corresponds to the case where the second message does not use FEC channel coding. Alternatively, it can be understood that the first value should not be applied to the scenario where the second message uses FEC channel coding. That is, the first value applies to the scenario where the second message does not use FEC channel coding.

[0414] The second value can correspond to (or be associated with) the second message not using FEC channel coding. Alternatively, the second value can correspond to (or be associated with) the second message using FEC channel coding. This scheme does not impose any limitations on the second value.

[0415] In one possible implementation, the first time corresponding to the first message corresponds to the end time of the padding portion in the first message, as shown in Figure 15a. The second time corresponding to the second message is the time when the second device begins sending the second message.

[0416] In another possible implementation, the first time corresponding to the first message corresponds to the end position of the last OFDM symbol occupied by the first message, as shown in Figure 15a. The second time corresponding to the second message is the time when the second device starts sending the second message.

[0417] In another possible implementation, the first time corresponding to the first message corresponds to the start time of the padding portion in the first message, as shown in Figure 15b. The second time corresponding to the second message is the time when the second device begins sending the second message.

[0418] In another possible implementation, the first message does not include a padding portion, and the first time corresponding to the first message is the time when the first device finishes sending the first message. That is, the first time corresponding to the first message corresponds to the end time of the postcode in the first message. The second time corresponding to the second message is the time when the second device starts sending the second message.

[0419] For details on this part, please refer to the relevant descriptions in the embodiment shown in Figure 14, which will not be repeated here.

[0420] Example 1: The start time of the first time offset corresponds to the end time of the padding portion in the R2D message, as shown in Figure 15a. The first value corresponds to the scenario where the device does not use FEC channel coding in the corresponding D2R message, and the second value corresponds to the scenario where the device uses FEC channel coding in the corresponding D2R message.

[0421] Example 2: The first value of the first time offset Toffset corresponds to the start time of Toffset being the end time of the padding portion in the R2D message, as shown in Figure 15a, and corresponds to the scenario where the device does not use FEC channel coding in the corresponding D2R message. The second value of the first time offset Toffset corresponds to the start time of Toffset being the start time of the padding portion in the R2D message, as shown in Figure 15b, and corresponds to the scenario where the device does not use FEC channel coding in the corresponding D2R message.

[0422] Example 3: The first value of the first time offset Toffset corresponds to the start time of Toffset being the start time of the padding portion in the R2D message, as shown in Figure 15b, and corresponds to the scenario where the device does not use FEC channel coding in the corresponding D2R message. The second value of the first time offset Toffset corresponds to the start time of Toffset being the start time of the padding portion in the R2D message, as shown in Figure 15b, and corresponds to the scenario where the device uses FEC channel coding in the corresponding D2R message.

[0423] Example 4: The first value of the first time offset Toffset corresponds to the start time of Toffset being the start time of the padding portion in the R2D message, as shown in Figure 15b, and corresponds to the scenario where the device does not use FEC channel coding in the corresponding D2R message. The second value of the first time offset Toffset corresponds to the start time of Toffset being the end time of the padding portion in the R2D message, as shown in Figure 15a, and corresponds to the scenario where the device uses FEC channel coding in the corresponding D2R message.

[0424] Example 5: The first time offset corresponds to a set of values, which may contain one or more candidate values. These candidate values ​​may correspond to either a scenario where the device does not use FEC channel coding in the D2R message corresponding to the first time offset, or a scenario where the device uses FEC channel coding in the D2R message corresponding to the first time offset. For example, the first time offset may include both the values ​​corresponding to the scenario where FEC channel coding is not used in the D2R message and the values ​​corresponding to the scenario where FEC channel coding is used in the D2R message.

[0425] Example 6: The first time offset corresponds to a set of values, and the smallest one or more values ​​in the set of values ​​correspond to the scenario where the device does not use FEC channel coding in the D2R message corresponding to the first time offset.

[0426] Example 7: The first time offset corresponds to multiple value sets. The value set Tset1 corresponds to the scenario where the device does not use FEC channel coding in the D2R message corresponding to the first time offset. The number of elements in Tset1 can be equal to 1 or greater than 1. The value set Tset2 corresponds to the scenario where the device uses FEC channel coding in the D2R message corresponding to the first time offset. The number of elements in Tset2 can be equal to 1 or greater than 1. The minimum value in Tset1 is less than or equal to the minimum value in Tset2.

[0427] Example 8: The first time offset corresponds to multiple value sets. The value set Tset1 corresponds to the scenario where the device does not use FEC channel coding in the D2R message corresponding to the first time offset. The number of elements in Tset1 can be equal to 1 or greater than 1. The value set Tset2 corresponds to the scenario where the device uses FEC channel coding in the D2R message corresponding to the first time offset. The number of elements in Tset2 can be equal to 1 or greater than 1. The start time corresponding to each candidate value in Tset1 and Tset2 corresponds to the end time of the padding portion in the corresponding R2D message, or both correspond to the end time of the padding portion in the corresponding R2D message. The maximum value in Tset1 is less than or equal to the minimum value in Tset2.

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

[0429] The methods of the embodiments of this application have been described in detail above, and the apparatus of the embodiments of this application is provided below. It is understood that the division of multiple units or modules in the various apparatus embodiments of this application is only a logical division based on function and is not intended to limit the specific structure of the apparatus. In specific implementations, some functional modules may be subdivided into more smaller functional modules, and some functional modules may be combined into a single functional module. However, regardless of whether these functional modules are subdivided or combined, the general flow executed by the apparatus is the same. For example, some apparatuses include a receiving unit and a transmitting unit. In some designs, the transmitting unit and the receiving unit can also be integrated into a communication unit, which can implement the functions implemented by the receiving unit and the transmitting unit. Typically, each unit corresponds to its own program code (or program instructions). When the program code corresponding to each unit runs on the processor, it causes the unit to be controlled by the processing unit to execute the corresponding flow and thus achieve the corresponding function.

[0430] This application also provides an apparatus for implementing any of the above methods. For example, a communication apparatus is provided that includes a module (or means) for implementing the steps performed by the first apparatus in any of the above methods.

[0431] For example, referring to FIG18, which is a schematic diagram of a communication device provided in an embodiment of this application, the communication device is used to implement the aforementioned communication method, such as the means performed by the first device in the communication method shown in FIG10.

[0432] As shown in Figure 18, the device may include a communication module 1801 and a processing module 1802, as detailed below:

[0433] Communication module 1801 is used to send first information to the second device;

[0434] The communication module 1801 is further configured to receive second information from the second device, wherein the minimum or maximum value of the interval between the first time corresponding to the first information and the second time corresponding to the second information is the first time interval;

[0435] The processing module 1802 is used to process the second information to obtain the third information, wherein the first time interval is associated with the bit size of the third information.

[0436] In one possible implementation, the first moment corresponding to the first information is the moment when the communication device finishes sending the first information, and the second moment corresponding to the second information is the moment when the second device starts sending the second information.

[0437] In one possible implementation, the first time interval is also associated with at least one of the following: a chip length of the second information, a time-domain repetition factor, a cyclic redundancy check (CRC) length for the third information, and whether forward error correction (FEC) channel decoding is performed on the second information.

[0438] In one possible implementation, the first time interval is greater than the second time interval, which is associated with one or more of the chip length of the second information and the time-domain repetition factor.

[0439] In one possible implementation, the CRC length of the third information is greater than 0. The processing module 1802 is used to perform FEC channel decoding on the second information to obtain the fourth information, wherein the FEC is a tail-biting convolutional code TBCC; and to verify the fourth information based on the CRC to obtain the third information.

[0440] In one possible implementation, the second information is an uplink message following message 3 during the random access process, or the second information is a response message corresponding to the first command message, where the first command message is message 4 during the random access process.

[0441] In one possible implementation, when the length of the CRC is 0, the first time interval is a; when the length of the CRC is not 0, the first time interval is b, where b > a, and a and b are both positive numbers.

[0442] In one possible implementation, ba is associated with the bit size of the third information.

[0443] In one possible implementation, the association of ba with the bit size of the third information includes: the association of ba with the bit size of the third information and with the length of the CRC used for the third information.

[0444] In one possible implementation, the ba is also associated with at least one of the following: a chip length of the second information, and a time-domain repetition factor.

[0445] In one possible implementation, when the second information is message 1 or message 3 in the random access process, the first time interval corresponding to message 1 in the random access process is the same as the first time interval corresponding to message 3 in the random access process.

[0446] For a description of each of the above modules, please refer to the description in the foregoing embodiments, which will not be repeated here.

[0447] For example, as shown in FIG18, the communication device is used to implement the aforementioned communication method, such as the means performed by the second device in the communication method shown in FIG10.

[0448] As shown in Figure 18, the device may include a communication module 1801 and a processing module 1802, as detailed below:

[0449] Communication module 1801 is used to receive first information from the first device;

[0450] Processing module 1802 is used to encode the third information to obtain the second information;

[0451] The communication module 1801 is further configured to send the second information to the first device, wherein the minimum or maximum value of the interval between the first time corresponding to the first information and the second time corresponding to the second information is a first time interval; the first time interval is associated with the bit size of the third information.

[0452] In one possible implementation, the first moment corresponding to the first information is the moment when the first device finishes sending the first information, and the second moment corresponding to the second information is the moment when the second device starts sending the second information.

[0453] In one possible implementation, the first time interval is also associated with at least one of the following: a chip length of the second information, a time-domain repetition factor, a CRC length for the third information, and whether the third information is FEC channel coded.

[0454] In one possible implementation, the first time interval is greater than the second time interval, which is associated with one or more of the chip length of the second information and the time-domain repetition factor.

[0455] In one possible implementation, the processing module 1802 is further configured to perform FEC channel coding on the third information to obtain the second information, wherein the FEC is TBCC.

[0456] In one possible implementation, the second information is an uplink message following message 3 during the random access process, or the second information is a response message corresponding to the first command message, where the first command message is message 4 during the random access process.

[0457] In one possible implementation, when the length of the CRC is 0, the first time interval is a; when the length of the CRC is not 0, the first time interval is b, where b > a, and a and b are both positive numbers.

[0458] In one possible implementation, ba is associated with the bit size of the third information.

[0459] In one possible implementation, the association of ba with the bit size of the third information includes: the association of ba with the bit size of the third information and with the length of the CRC used for the third information.

[0460] In one possible implementation, the ba is also associated with at least one of the following: a chip length of the second information, and a time-domain repetition factor.

[0461] In one possible implementation, when the second information is message 1 or message 3 in the random access process, the first time interval corresponding to message 1 in the random access process is the same as the first time interval corresponding to message 3 in the random access process.

[0462] For a description of each of the above modules, please refer to the description in the foregoing embodiments, which will not be repeated here.

[0463] For another example, referring to FIG. 19, it is a schematic structural diagram of a communication apparatus provided by an embodiment of the present application. The communication apparatus is configured to implement the foregoing communication method, for example, the means performed by the first apparatus in the communication method shown in FIG. 14.

[0464] As shown in FIG. 19, the apparatus may include a communication module 1901, which is specifically described as follows:

[0465] The communication module 1901 is configured to send a first message to a second apparatus;

[0466] The communication module 1901 is further configured to receive a second message from the second apparatus, where a time offset between a first time corresponding to the first message and a second time corresponding to the second message is a first time offset; the first time offset is associated with at least one of whether the second message adopts forward error correction (FEC) channel coding or not, and a message type of the second message.

[0467] In a possible implementation, the first time offset is associated with both whether the second information adopts the FEC channel coding or not and the message type of the second message.

[0468] In a possible implementation, when the message type of the second message is a first type and the second message adopts the FEC channel coding, a value of the first time offset includes b; when the second message does not adopt the FEC channel coding, the value of the first time offset includes a, where a < b, and a and b are positive numbers respectively.

[0469] In a possible implementation, when the message type of the second message is a second type, the value of the first time offset includes a.

[0470] In a possible implementation, when a value of the message type of the second message is a first value and the second message adopts the FEC channel coding, a value of the first time offset includes c; when the second message does not adopt the FEC channel coding, the value of the first time offset includes d, where d < c, and c and d are positive numbers respectively.

[0471] In a possible implementation, when the value of the message type of the second message is a second value, the value of the first time offset includes d.

[0472] In a possible implementation, the first time offset is associated with whether the second message adopts the FEC channel coding or not.

[0473] In a possible implementation, when the second message adopts the FEC channel coding, the first time offset is e; when the second message does not adopt the FEC channel coding, the first time offset is f, where e>f, and e and f are positive numbers respectively.

[0474] In a possible implementation, the first time offset is associated with the message type of the second message.

[0475] In a possible implementation, when the message type of the second message is a third type, the value of the first time offset includes g, and when the message type of the second message is a fourth type, the value of the first time offset includes h, where g<h, and g and h are positive numbers respectively.

[0476] In a possible implementation, when the value of the message type of the second message is a third value, the value of the first time offset includes i, and when the value of the message type of the second message is a fourth value, the value of the first time offset includes j, where i<j, and i and j are positive numbers respectively.

[0477] In a possible implementation, the first time instant corresponding to the first message corresponds to the end time instant of the padding portion in the first message, and the second time instant corresponding to the second message is the time instant when the second apparatus starts to transmit the second message.

[0478] In a possible implementation, the first time instant corresponding to the first message corresponds to the end position of the last orthogonal frequency division multiplexing (OFDM) symbol occupied by the first message, and the second time instant corresponding to the second message is the time instant when the second apparatus starts to transmit the second message.

[0479] In a possible implementation, the first time instant corresponding to the first message corresponds to the start time instant of the padding portion in the first message, and the second time instant corresponding to the second message is the time instant when the second apparatus starts to transmit the second message.

[0480] In a possible implementation, the first time instant corresponding to the first message corresponds to the end time instant of the postamble in the first message, and the second time instant corresponding to the second message is the time instant when the second apparatus starts to transmit the second message.

[0481] In a possible implementation, the first message does not include a padding portion, the first time instant corresponding to the first message is the time instant when the first apparatus finishes transmitting the first message, and the second time instant corresponding to the second message is the time instant when the second apparatus starts to transmit the second message.

[0482] In a possible implementation, the first time offset is associated with the bit size of the second message.

[0483] In a possible implementation, the first time offset is further associated with at least one of the following: a chip length of the second message, a small frequency shift factor of the second message, and a cyclic redundancy check (CRC) length used for the second message.

[0484] In a possible implementation, the FEC channel coding is tail-biting convolutional code (TBCC).

[0485] For the description of the foregoing modules, reference may be made to the records of the foregoing embodiments, and details are not described herein again.

[0486] For another example, referring to Figure 19, it is a schematic structural diagram of a communication apparatus provided by an embodiment of the present application. The communication apparatus is configured to implement the foregoing communication method, for example, the means performed by the first apparatus in the communication method shown in Figure 17.

[0487] As shown in Figure 19, the apparatus may include a communication module 1901, which is specifically described as follows:

[0488] The communication module 1901 is configured to send a first message to a second apparatus;

[0489] The communication module 1901 is further configured to receive a second message from the second apparatus, where a time offset between a first time corresponding to the first message and a second time corresponding to the second message is a first time offset; the first time offset includes at least a first value and a second value, and the first value is a positive number smaller than the second value.

[0490] In a possible implementation, the first value corresponds to a case where the second message does not adopt FEC channel coding.

[0491] In a possible implementation, when the message type of the second message is a fifth type, the first value of the first time offset includes k, and the second value of the first time offset includes m, where k < m, and k and m are positive numbers respectively.

[0492] In a possible implementation, when the value of the message type of the second message is a fifth value, the first value of the first time offset includes n, and the second value of the first time offset includes p, where n < p, and n and p are positive numbers respectively.

[0493] For other implementations of this part, reference may be made to the foregoing records, and details are not described herein again.

[0494] For the description of the foregoing modules, reference may be made to the records of the foregoing embodiments, and details are not described herein again.

[0495] For another example, with reference to FIG. 19, it is a schematic structural diagram of a communication apparatus provided in an embodiment of the present application. The communication apparatus is configured to implement the foregoing communication method, for example, the means performed by a second apparatus in the communication method shown in FIG. 14.

[0496] As shown in FIG. 19, the apparatus may include a communication module 1901, which is specifically described as follows:

[0497] The communication module 1901 is configured to receive a first message from a first apparatus;

[0498] The communication module 1901 is further configured to send a second message to the first apparatus, wherein a time offset between a first time corresponding to the first message and a second time corresponding to the second message is a first time offset; the first time offset is associated with at least one of whether the second message uses forward error correction (FEC) channel coding or not, and a message type of the second message.

[0499] In a possible implementation, the first time offset is associated with both whether the second message uses the FEC channel coding or not and the message type of the second message.

[0500] In a possible implementation, when the message type of the second message is a first type, and the second message uses the FEC channel coding, the value of the first time offset comprises b; when the second message does not use the FEC channel coding, the value of the first time offset comprises a, wherein a < b, and a and b are positive numbers respectively.

[0501] In a possible implementation, when the message type of the second message is a second type, the value of the first time offset comprises the a.

[0502] In a possible implementation, when the value of the message type of the second message is a first value, and the second message uses the FEC channel coding, the value of the first time offset comprises c; when the second message does not use the FEC channel coding, the value of the first time offset comprises d, wherein d < c, and c and d are positive numbers respectively.

[0503] In a possible implementation, when the value of the message type of the second message is a second value, the value of the first time offset comprises the d.

[0504] In a possible implementation, the first time offset is associated with whether the second message uses the FEC channel coding or not.

[0505] In a possible implementation, when the second message adopts the FEC channel coding, the first time offset is e; when the second message does not adopt the FEC channel coding, the first time offset is f, wherein e > f, and e and f are positive numbers respectively.

[0506] In a possible implementation, the first time offset is associated with the message type of the second message.

[0507] In a possible implementation, when the message type of the second message is a third type, the value of the first time offset includes g, and when the message type of the second message is a fourth type, the value of the first time offset includes h, wherein g < h, and g and h are positive numbers respectively.

[0508] In a possible implementation, when the value of the message type of the second message is a third value, the value of the first time offset includes i, and when the value of the message type of the second message is a fourth value, the value of the first time offset includes j, wherein i < j, and i and j are positive numbers respectively.

[0509] The first time corresponding to the first message corresponds to the end time of the padding part in the first message, and the second time corresponding to the second message is the time when the second device starts sending the second message.

[0510] In a possible implementation, the first time corresponding to the first message corresponds to the end position of the last Orthogonal Frequency Division Multiplexing (OFDM) symbol occupied by the first message, and the second time corresponding to the second message is the time when the second device starts sending the second message.

[0511] In a possible implementation, the first time corresponding to the first message corresponds to the start time of the padding part in the first message, and the second time corresponding to the second message is the time when the second device starts sending the second message.

[0512] In a possible implementation, the first time corresponding to the first message corresponds to the end time of the postamble in the first message, and the second time corresponding to the second message is the time when the second device starts sending the second message.

[0513] In a possible implementation, the first message does not include a padding part, the first time corresponding to the first message is the time when the first device finishes sending the first message, and the second time corresponding to the second message is the time when the second device starts sending the second message.

[0514] In one possible implementation, the first time offset is associated with the bit size of the second message.

[0515] In one possible implementation, the first time offset is further associated with at least one of the following: a chip length of the second message, a small frequency shift factor of the second message, and a cyclic redundancy check (CRC) length used for the second message.

[0516] In one possible implementation, the FEC channel coding is tail-biting convolutional code (TBCC).

[0517] For the introduction of each of the foregoing modules, reference may be made to the description of the foregoing embodiments, and details are not described herein again.

[0518] For another example, referring to FIG. 19, it is a schematic structural diagram of a communication apparatus provided by an embodiment of the present application. The communication apparatus is configured to implement the foregoing communication method, for example, the measures performed by a second apparatus in the communication method shown in FIG. 17.

[0519] As shown in FIG. 19, the apparatus may include a communication module 1901, which is specifically described as follows:

[0520] The communication module 1901 is configured to receive a first message from a first apparatus;

[0521] The communication module 1901 is further configured to send a second message to the first apparatus, where a time offset between a first time corresponding to the first message and a second time corresponding to the second message is a first time offset; the first time offset includes at least a first value and a second value, and the first value is a positive number less than the second value.

[0522] In one possible implementation, the first value corresponds to a case where the second message does not adopt FEC channel coding.

[0523] In one possible implementation, when a message type of the second message is a fifth type, the first value of the first time offset includes k, and the second value of the first time offset includes m, where k < m, and k and m are each positive numbers.

[0524] In one possible implementation, when a value of the message type of the second message is a fifth value, the first value of the first time offset includes n, and the second value of the first time offset includes p, where n < p, and n and p are each positive numbers.

[0525] For other implementations of this part, reference may be made to the foregoing description, and details are not described herein again.

[0526] For the introduction of each of the foregoing modules, reference may be made to the description of the foregoing embodiments, and details are not described herein again.

[0527] It should be understood that the division of modules in the above devices is only 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, modules in a communication device can be implemented by a processor calling software; for example, a communication device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of each module in the device. The processor can be, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the modules in the device can be implemented as hardware circuits. The functionality of some or all units can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), and the functionality of some or all of the above units is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD), such as a field-programmable gate array (FPGA), which can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the above units. All modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0528] Referring to FIG20, a hardware structure diagram of another communication device provided in an embodiment of this application is shown. The communication device 2000 shown in FIG20 includes one or more processors 2001 (a processor is illustrated in the figure).

[0529] Processor 2001 is a circuit with signal processing capabilities. In one implementation, processor 2001 can be a circuit with instruction read and execute capabilities, such as a central processing unit (CPU), microprocessor, graphics processing unit (GPU) (which can be understood as a type of microprocessor), or digital signal processor (DSP). In another implementation, processor 2001 can achieve certain functions through the logical relationships of hardware circuits. These logical relationships of hardware circuits are fixed or reconfigurable. For example, processor 2001 can be a hardware circuit implemented as an ASIC or a programmable logic device (PLD), such as an FPGA. In reconfigurable hardware circuits, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the processor loading instructions to achieve the functions of some or all of the above modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as a type of ASIC, such as a neural network processing unit (NPU), tensor processing unit (TPU), or deep learning processing unit (DPU). The processor 2001 is used to execute related programs to implement the functions required by the units in the communication device of the present application embodiment, or to execute the communication method of the method embodiment of the present application.

[0530] Optionally, the communication device 2000 may also include a memory (e.g., memory 2003, memory 2004, memory 2005) (shown as dashed lines in the figure). This memory is used to store instructions executed by the processor 2001, or to store input data required by the processor 2001 to execute instructions, or to store data generated after the processor 2001 executes instructions.

[0531] Optionally, the memory may be located within the one or more processors (e.g., memory 2003), or outside the one or more processors (e.g., memory 2004, memory 2005), or may include a storage portion located within the one or more processors and a storage portion located outside the one or more processors.

[0532] In this embodiment, the memory (e.g., memory 2003, memory 2004, memory 2005) may include, but is not limited to, cache, read-only memory (ROM), random access memory (RAM), synchronous dynamic random access memory (SDRAM), hard disk drive (HDD) or solid-state drive (SSD), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), etc. Memory is any other medium capable of carrying or storing desired program code having an instruction or data structure form and accessible by a computer, but is not limited thereto. The memory in this embodiment may also be a circuit or any other device capable of implementing storage functions for storing computer programs or instructions, and / or data.

[0533] Optionally, the communication device 2000 may also include a communication interface 2002 (shown as a dashed line in the figure). The processor 2001 and the communication interface 2002 are coupled to each other. The communication interface 2002 may be a transceiver or interface circuit, bus, module, or other type of communication interface.

[0534] The memory can store programs. When the program stored in the memory is executed by the processor 2001, the processor 2001 and the communication interface 2002 are used to execute the various steps of the communication method of the embodiments of this application.

[0535] As can be seen, each module in the above device can be one or more processors (or processing circuits) configured to implement the above methods, such as: CPU, GPU, NPU, TPU, DPU, microprocessor, DSP, ASIC, FPGA, or a combination of at least two of these processor forms or a portion of the processing circuits in these processors.

[0536] Furthermore, the modules in the above devices can be integrated in whole or in part, or they can be implemented independently. In one implementation, these modules are integrated together as a system-on-a-chip (SOC). The SOC may include at least one processor for implementing any of the above methods or for implementing the functions of the modules of the device. The at least one processor may be of different types, such as CPU and FPGA, CPU and artificial intelligence processor, CPU and GPU, etc.

[0537] It should be noted that although the device 2000 shown in Figure 20 only illustrates the memory, processor, and communication interface, those skilled in the art should understand that in specific implementations, device 2000 may also include other devices necessary for normal operation. Furthermore, depending on specific needs, those skilled in the art should understand that device 2000 may also include hardware devices for implementing other additional functions. Moreover, those skilled in the art should understand that device 2000 may only include the devices necessary for implementing the embodiments of this application, and not necessarily all the devices shown in Figure 20.

[0538] This application also provides a computer-readable storage medium storing instructions that, when executed on a computer or processor, cause the computer or processor to perform one or more steps of any of the above methods.

[0539] This application also provides a computer program product containing instructions. When the computer program product is run on a computer or processor, it causes the computer or processor to perform one or more steps of any of the methods described above.

[0540] It is understood that in this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information to indicate A, it can be understood that the instruction information carries A, directly indicates A, or indirectly indicates A. In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementation, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index, or indirectly indicating the information to be instructed by indicating other information, wherein there is an association between the other information and the information to be instructed. It is also possible to indicate only a part of the information to be instructed, while the other parts of the information to be instructed are known or agreed upon in advance. For example, the instruction of specific information can also be achieved by using the arrangement order of various information in advance (e.g., as specified by a protocol), thereby reducing the instruction overhead to a certain extent. The information to be instructed can be sent as a whole or divided into multiple sub-information to be sent separately, and the sending period and / or sending time of these sub-information can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device.

[0541] It should be understood that in the description of this application, unless otherwise stated, " / " indicates that the objects before and after it are in an "or" relationship. For example, A / B can represent A or B; where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Additionally, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" do not necessarily imply difference. In this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being better or more advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

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

[0543] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0544] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in or transmitted through a computer-readable storage medium. The computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be read-only memory (ROM), random access memory (RAM), or magnetic media, such as floppy disks, hard disks, magnetic tapes, magnetic disks, or optical media, such as digital versatile discs (DVDs), or semiconductor media, such as solid-state disks (SSDs).

[0545] The above description is merely a specific implementation of the embodiments of this application, but the protection scope of the embodiments of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the embodiments of this application should be covered within the protection scope of the embodiments of this application. Therefore, the protection scope of the embodiments of this application should be determined by the protection scope of the claims.

Claims

1. A communication method applied to a first device, characterized in that, The method comprises: sending a first message to a second apparatus; receiving a second message from the second apparatus, wherein the time offset between a first time instant corresponding to the first message and a second time instant corresponding to the second message is a first time offset; the first time offset is associated with at least one of whether the second message adopts forward error correction (FEC) channel coding or not and a message type of the second message.

2. The method according to claim 1, characterized in that, the step that the first time offset is associated with at least one of whether the second message adopts the FEC channel coding or not and the message type of the second message comprises: the first time offset is associated with both whether the second message adopts the FEC channel coding or not and the message type of the second message.

3. The method according to claim 2, characterized in that, when the message type of the second message is a first type, and when the second message adopts the FEC channel coding, the value of the first time offset comprises b, when the second message does not adopt the FEC channel coding, the value of the first time offset comprises a, wherein a < b, and both a and b are positive numbers.

4. The method according to claim 3, characterized in that, when the message type of the second message is a second type, the value of the first time offset comprises a.

5. The method according to claim 2, characterized in that, when the value of the message type of the second message is a first value, and when the second message adopts the FEC channel coding, the value of the first time offset comprises c, when the second message does not adopt the FEC channel coding, the value of the first time offset comprises d, wherein d < c, and both c and d are positive numbers.

6. The method according to claim 5, characterized in that, when the value of the message type of the second message is a second value, the value of the first time offset comprises d.

7. The method according to claim 1, characterized in that, the step that the first time offset is associated with at least one of whether the second message adopts the FEC channel coding or not and the message type of the second message comprises: the first time offset is associated with whether the second message adopts the FEC channel coding or not.

8. The method according to claim 7, wherein when the second message uses the FEC channel coding, the first time offset is e; when the second message does not use the FEC channel coding, the first time offset is f, wherein, e > f, and both e and f are positive numbers.

9. The method according to claim 1, characterized in that, the step that the first time offset is associated with at least one of whether the second message adopts the FEC channel coding or not and the message type of the second message comprises: the first time offset is associated with the message type of the second message.

10. The method according to claim 9, characterized in that, when the message type of the second message is a third type, the value of the first time offset comprises g, when the message type of the second message is a fourth type, the value of the first time offset comprises h, wherein g < h, and both g and h are positive numbers.

11. The method according to claim 9, characterized in that, when the value of the message type of the second message is a third value, the value of the first time offset comprises i, when the value of the message type of the second message is a fourth value, the value of the first time offset comprises j, wherein i < j, and both i and j are positive numbers.

12. A communication method applied to a first device, characterized in that, The method comprises: sending a first message to a second apparatus; receiving a second message from the second apparatus, wherein the time offset between a first time instant corresponding to the first message and a second time instant corresponding to the second message is a first time offset; the first time offset comprises at least a first value and a second value, and the first value is a positive number less than the second value.

13. The method according to claim 12, characterized in that, the first value corresponds to that the second message does not adopt FEC channel coding.

14. The method according to claim 12 or 13, characterized in that, when the message type of the second message is a fifth type, the first value of the first time offset comprises k, and the second value of the first time offset comprises m, wherein k<m, and k and m are positive numbers respectively.

15. The method according to claim 12 or 13, characterized in that, when the value of the message type of the second message is a fifth value, the first value of the first time offset comprises n, and the second value of the first time offset comprises p, wherein n<p, and n and p are positive numbers respectively.

16. The method according to any one of claims 1 to 15, characterized in that, the first time instant corresponding to the first message corresponds to an end time instant of a padding part in the first message, and the second time instant corresponding to the second message is a time instant when the second apparatus starts transmitting the second message.

17. The method according to any one of claims 1 to 15, characterized in that, the first time instant corresponding to the first message corresponds to an end position of the last Orthogonal Frequency Division Multiplexing (OFDM) symbol occupied by the first message, and the second time instant corresponding to the second message is a time instant when the second apparatus starts transmitting the second message.

18. The method according to any one of claims 1 to 15, characterized in that, the first time instant corresponding to the first message corresponds to a start time instant of a padding part in the first message, and the second time instant corresponding to the second message is a time instant when the second apparatus starts transmitting the second message.

19. The method according to any one of claims 1 to 15, characterized in that, the first time instant corresponding to the first message corresponds to an end time instant of a postamble in the first message, and the second time instant corresponding to the second message is a time instant when the second apparatus starts transmitting the second message.

20. The method according to any one of claims 1 to 15, characterized in that, the first message does not comprise a padding part, the first time instant corresponding to the first message is a time instant when the first apparatus finishes transmitting the first message, and the second time instant corresponding to the second message is a time instant when the second apparatus starts transmitting the second message.

21. The method according to any one of claims 1 to 12, 14 to 20, characterized in that, the first time offset is associated with the bit size of the second message.

22. The method according to any one of claims 1 to 12, 14 to 21, characterized in that, the first time offset is further associated with at least one of the following: a chip length of the second message, a small frequency shift factor of the second message, and a cyclic redundancy check (CRC) length used for the second message.

23. The method according to any one of claims 1 to 12, 14 to 22, characterized in that, the FEC channel coding is tail-biting convolutional code (TBCC).

24. A communication method applied to a second device, characterized in that, the method comprises: receiving a first message from a first apparatus; transmitting a second message to the first apparatus, wherein the time offset between a first time instant corresponding to the first message and a second time instant corresponding to the second message is a first time offset; the first time offset is associated with at least one of whether the second message adopts Forward Error Correction (FEC) channel coding and the message type of the second message.

25. The method according to claim 24, characterized in that, that the first time offset is associated with at least one of whether the second message adopts the FEC channel coding and the message type of the second message comprises: the first time offset is associated with both whether the second information adopts the FEC channel coding and the message type of the second message.

26. The method according to claim 25, characterized in that, When the message type of the second message is the first type, and when the second message adopts the FEC channel coding, the value of the first time offset includes b, when the second message does not adopt the FEC channel coding, the value of the first time offset includes a, wherein a < b, and a and b are positive numbers respectively.

27. The method according to claim 26, characterized in that, When the message type of the second message is the second type, the value of the first time offset includes a.

28. The method according to claim 25, characterized in that, When the value of the message type of the second message is a first value, and when the second message adopts the FEC channel coding, the value of the first time offset includes c, when the second message does not adopt the FEC channel coding, the value of the first time offset includes d, wherein d < c, and c and d are positive numbers respectively.

29. The method according to claim 28, characterized in that, When the value of the message type of the second message is a second value, the value of the first time offset includes d.

30. The method according to claim 24, characterized in that, that the first time offset is associated with at least one of whether the second message adopts the FEC channel coding and the message type of the second message comprises: the first time offset is associated with whether the second message adopts the FEC channel coding.

31. The method according to claim 30, wherein when the second message uses the FEC channel coding, the first time offset is e; when the second message does not use the FEC channel coding, the first time offset is f, wherein, e > f, and e and f are positive numbers respectively.

32. The method according to claim 24, characterized in that, that the first time offset is associated with at least one of whether the second message adopts the FEC channel coding and the message type of the second message comprises: the first time offset is associated with the message type of the second message.

33. The method according to claim 32, characterized in that, When the message type of the second message is a third type, the value of the first time offset includes g, When the message type of the second message is a fourth type, the value of the first time offset includes h, wherein g < h, and g and h are positive numbers respectively.

34. The method according to claim 32, characterized in that, When the value of the message type of the second message is a third value, the value of the first time offset includes i, When the value of the message type of the second message is a fourth value, the value of the first time offset includes j, wherein i < j, and i and j are positive numbers respectively.

35. A communication method applied to a second device, characterized in that, The method comprises: receiving a first message from a first device; transmitting a second message to the first device, wherein a time offset between a first time corresponding to the first message and a second time corresponding to the second message is the first time offset; the first time offset comprises at least a first numerical value and a second numerical value, and the first numerical value is a positive number smaller than the second numerical value.

36. The method according to claim 35, characterized in that, the first numerical value corresponds to that the second message does not adopt FEC channel coding.

37. The method according to claim 35 or 36, characterized in that, When the message type of the second message is a fifth type, the first numerical value of the first time offset comprises k, and the second numerical value of the first time offset comprises m, wherein k < m, and k and m are positive numbers respectively.

38. The method according to claim 35 or 36, characterized in that, When the value of the message type of the second message is a fifth value, the first numerical value of the first time offset comprises n, and the second numerical value of the first time offset comprises p, wherein n < p, and n and p are positive numbers respectively.

39. The method according to any one of claims 24 to 38, characterized in that, The first time corresponding to the first message corresponds to the end time of the padding portion in the first message, and the second time corresponding to the second message is the time when the second device starts sending the second message.

40. The method according to any one of claims 24 to 38, characterized in that, The first time corresponding to the first message corresponds to the end position of the last orthogonal frequency division multiplexing (OFDM) symbol occupied by the first message, and the second time corresponding to the second message is the time when the second device starts sending the second message.

41. The method according to any one of claims 24 to 38, characterized in that, The first time corresponding to the first message corresponds to the start time of the padding portion in the first message, and the second time corresponding to the second message is the time when the second device starts sending the second message.

42. The method according to any one of claims 24 to 38, characterized in that, The first time corresponding to the first message corresponds to the end time of the postcode in the first message, and the second time corresponding to the second message is the time when the second device starts sending the second message.

43. The method according to any one of claims 24 to 38, characterized in that, The first message does not include a padding portion, the first time corresponding to the first message is the time when the first device finishes sending the first message, and the second time corresponding to the second message is the time when the second device starts sending the second message.

44. The method according to any one of claims 24 to 35, 37 to 43, characterized in that, The first time offset is associated with the bit size of the second message.

45. The method according to any one of claims 24 to 35, 37 to 44, characterized in that, The first time offset is also associated with at least one of the following: a chip length of the second message, a small frequency shift factor of the second message, and the cyclic redundancy check (CRC) length of the second message.

46. ​​The method according to any one of claims 24 to 35, 37 to 45, characterized in that, The FEC channel is coded as a tail-biting convolutional code (TBCC).

47. A communication device, characterized in that, Includes modules for implementing the method as described in any one of claims 1-46.

48. A communication device, characterized in that, The apparatus includes a processor and a memory for storing program code, and the processor for calling the program code to perform the method as described in any one of claims 1-23.

49. A communication device, characterized in that, The apparatus includes a processor and a memory for storing program code, and the processor for calling the program code to perform the method as described in any one of claims 24-46.

50. A communication system, characterized in that, Includes the apparatus as described in claim 48 and the apparatus as described in claim 49.

51. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, the method as described in any one of claims 1-46 is performed.

52. A computer program product, characterized in that, The computer program product includes relevant program instructions, which, when executed, cause the method as described in any one of claims 1-46 to be implemented.

Images