Communication method, apparatus, communication device, storage medium, and computer program product

Abstract

This application relates to a communication method, apparatus, communication device, storage medium, and computer program product. The method includes: an IoT terminal device receiving a first message sent by a reader; and, based on the instruction of the first message, sending a second message to the reader; the second message is sent by the IoT terminal device in a multiple access manner, including time division multiple access and / or frequency division multiple access; the reader can combine the terminal capabilities of multiple devices and the actual channel state, and by sending the first message to the devices, allocate random access resources to multiple devices, avoiding frequency conflicts between resources used by multiple devices, improving the effectiveness of resource allocation, and enhancing the transmission efficiency and reliability of the system.

Description

Technical Field

[0001] This application relates to the field of wireless communication and terminal technology, and in particular to a communication method, apparatus, communication device, storage medium, and computer program product. Background Technology

[0002] Passive IoT is a promising low-power IoT technology. Technologies such as wireless power supply and backscatter communication can reduce the reliance of passive IoT devices on batteries, providing a technological foundation for the development of new battery-free IoT devices. 3GPP defines a new paradigm for the form and access process of Ambient IoT terminal devices. In Ambient IoT systems, passive IoT devices place new demands on the transmission mechanisms and scheduling methods of wireless communication networks.

[0003] In traditional 3GPP Release 19 Ambient IoT systems, it is necessary to determine TDMA and FDMA for D2R transmission of passive IoT devices to enable multiple access for multiple devices. While TDMA schemes for random access procedures have been extensively discussed, data transmission and scheduling schemes for FDMA lack in-depth research. Because passive IoT devices have relatively weak functionality and lack the ability to autonomously transmit electromagnetic waves, they can only send data via backscattered waves, making cellular FDMA schemes unsuitable. Therefore, how to achieve effective resource allocation and instruction for terminal devices and readers during FDMA processes is a pressing issue that needs to be addressed. Summary of the Invention

[0004] This application provides a communication method, apparatus, communication device, storage medium, and computer program product that can realize frequency division multiple access transmission between terminal devices and readers, improve data transmission efficiency, and enhance the effectiveness of readers in allocating frequency domain resources to each terminal device.

[0005] A communication method applied to an Internet of Things (IoT) terminal device, the method comprising:

[0006] Receive the first message sent by the reader / writer;

[0007] Based on the instruction of the first message, a second message is sent to the reader / writer; the second message is sent by the IoT terminal device in a multiple access mode, the multiple access mode including time division multiple access and / or frequency division multiple access.

[0008] In one embodiment, the first message is an R2D transmission, which includes one or more of a timing acquisition signal (TAS), R2D transmission data, control information, and a postamble; the second message is a D2R transmission, which includes one or more of a timing acquisition signal, D2R transmission data, control information, a midamble, and a postamble.

[0009] In one embodiment, the timing acquisition signal is a preamble, and the R2D transmission data is carried on a PRDCH.

[0010] In one embodiment, the timing acquisition signal at least characterizes the start of R2D and / or D2R transmission of the message to which the timing acquisition signal is located in the time domain, and the timing acquisition signal is used for clock synchronization, determining the chip duration of subsequent transmissions, sampling frequency offset (SFO) estimation, carrier frequency offset (CFO) estimation, channel estimation, and interference estimation, or one or more of these.

[0011] In one embodiment, the control information includes at least one of the scheduling information for the R2D transmission and the scheduling information for the D2R transmission corresponding to the R2D transmission. The scheduling information for the D2R transmission includes at least one of the following: time-domain and / or frequency-domain resources, class modulation and coding scheme (MCS) information, chip duration, information bit duration, frequency offset factor, device-related ID, repetition, D2R preamble related indication information, and D2R midamble related indication information.

[0012] In one embodiment, the method further includes:

[0013] Clock calibration is performed on the R2D transmission to obtain one or more of the following: the estimated sampling frequency offset, the estimated carrier frequency offset, the maximum frequency shift range supported by the device, and the NR band or frequency range supported by the device.

[0014] In one embodiment, the method further includes:

[0015] In D2R transmission, the capability information of the IoT terminal device is sent to the reader / writer. The capability information includes device power information, device type, estimated sampling frequency offset, estimated carrier frequency offset, maximum frequency offset range supported by the device, and one or more of the NR bands or frequency ranges supported by the device.

[0016] In one embodiment, the method further includes:

[0017] Based on the scheduling information of the D2R transmission corresponding to the R2D transmission contained in the control information of the R2D transmission, the access resource of frequency division multiple access indicated by the reader is obtained, and D2R data / D2R transmission is sent to the reader on the access resource of frequency division multiple access indicated by the reader.

[0018] In one embodiment, the IoT terminal device determines the implementation method of frequency division multiple access in at least one of the following ways:

[0019] The implementation method of frequency division multiple access is determined in a predefined or pre-configured manner, and / or based on the type of the IoT terminal device, and / or the multiple access mode indication corresponding to the IoT terminal device;

[0020] Based on control information in different formats and / or the content of control information, determine the frequency division multiple access implementation method of the IoT terminal device;

[0021] Based on the device type indicated by the different formats of control information and / or the content of the control information, the frequency division multiple access implementation mode of the IoT terminal device is determined.

[0022] In one embodiment, the method further includes:

[0023] When the D2R transmission of the IoT terminal device is achieved by backscattering on an externally provided carrier, frequency division multiple access is achieved through a small frequency offset of the carrier; or...

[0024] When the D2R transmission of the IoT terminal device is generated internally by the device, frequency division multiple access is achieved through a small frequency offset of the carrier and / or a spectrum shifting mechanism for the generated waveform.

[0025] In one embodiment, the method further includes:

[0026] When the IoT terminal device is device 1 and / or device 2a, frequency division multiple access is achieved through a small frequency offset of the backscattered carrier; or,

[0027] When the device type of the IoT terminal device is device2b, frequency division multiple access is achieved through a small frequency offset of the carrier and / or a spectrum shifting mechanism for generating waveforms.

[0028] In one embodiment, the first message is used to indicate time-domain resource allocation and / or frequency-domain resource allocation during D2R transmission.

[0029] In one embodiment, the data in the first message used to indicate time-domain resource allocation and / or frequency-domain resource allocation includes at least control information, which is one or more of physical layer control information, MAC CE, and higher-layer signaling.

[0030] In one embodiment, the first message includes at least one field, multiple fields, a code point in a field, multiple code points in a field, a string, and one or more methods in the corresponding bit mapping table to indicate one or more of the following: frequency domain resource location, frequency domain resource offset, and length of continuously allocated frequency domain resources.

[0031] In one embodiment, when the IoT terminal device determines the frequency domain resource location based on the first message, the content of the first message includes at least any of the following:

[0032] The resource unit number N1 and / or the size Ru of a single frequency domain resource unit;

[0033] The starting resource unit number Nstart, the frequency domain offset Nsf from the starting frequency, and / or the size Ru of a single frequency domain resource unit;

[0034] The frequency domain offset Nsf from the starting frequency, the size Ru of a single frequency domain resource unit, and the starting frequency Fstart, which at least supports the frequency of the carrier CW;

[0035] Frequency offset factor Rsf, or related information about the frequency offset factor;

[0036] Information bit duration Tb or information bit rate 1 / Tb;

[0037] The length indication information of the amble transmitted by D2R must contain at least one of the preamble, midamble, and postamble.

[0038] Carrier frequency Fcw;

[0039] Chip duration Tc or chip rate 1 / Tc;

[0040] Transmission bandwidth;

[0041] Baseband bandwidth (BW).

[0042] In one embodiment, the frequency offset factor related indication information includes one or more of the following: D2R frequency offset factor calculation parameter n, frequency offset factor calculation rule, frequency offset factor calculation type, and maximum value of D2R frequency offset factor.

[0043] In one embodiment, when the IoT terminal device determines the length of continuous frequency domain resources based on the first message, the content of the first message includes at least any of the following:

[0044] The number of continuous frequency domain units, NBW;

[0045] Indicates the duration Tb of the information bit or the information bit rate 1 / Tb;

[0046] The length indication information of the amble transmitted by D2R includes at least one of preamble, midamble, and postamble.

[0047] Indicates the chip duration Tc or chip rate 1 / Tc;

[0048] Indicates the transmission bandwidth and / or baseband bandwidth BW';

[0049] Indicates the block size TBS and / or the duration T of the D2R message.

[0050] In one embodiment, the first message indicates one or more of the following through at least one of the following methods: a field, multiple fields, a code point in a field, multiple code points in a field, an indicator, multiple indicators, a string, and a corresponding bit mapping table: D2R frequency offset factor Rsf, D2R frequency offset factor calculation parameter n, frequency offset factor calculation rule, frequency offset factor calculation type, and maximum value of D2R frequency offset factor.

[0051] In one embodiment, the first message indicates the row index value m of the frequency offset factor allocation table via a frequency offset factor indicator field or one or more code points in the field.

[0052] In one embodiment, the definition of each row in the frequency offset factor allocation table includes one or more of the following: frequency offset factor Rsf, frequency offset factor calculation parameter n, frequency offset factor calculation rule, frequency offset factor calculation type, maximum value of D2R frequency offset factor, D2R application scenario or message type, and parameters, wherein the parameters include one or more of the continuously allocated frequency domain resources NBW, Tb or information bit rate, Tc or chip rate, transmission bandwidth, baseband bandwidth, and R2D and D2R time domain unit ratios.

[0053] In one embodiment, the capability information indicates one or more of the following: the sampling frequency offset estimate, the carrier frequency offset estimate, the maximum frequency offset range supported by the device, and the NR band or frequency range supported by the device, through one or more fields, one or more code points in one field, one or more code points in one field, or a string and a corresponding bit mapping table.

[0054] In one embodiment, the sampled frequency offset estimate indicates a quantized value or an index value, the carrier frequency offset estimate indicates a quantized value or an index value, and the maximum frequency offset range supported by the device indicates a quantized value or an index value for the frequency offset magnitude.

[0055] In one embodiment, the capability information indicates the index value m of the IoT terminal device in the capability information index table through one field, or multiple fields, or one code point in one field, or multiple code points in one field, or a string and a corresponding bit mapping table. The row definition content of the capability information index table includes one or more of the following: SFO estimate, CFO estimate, maximum frequency offset range supported by the device, and NR bands or frequency ranges supported by the device.

[0056] In one embodiment, the method further includes:

[0057] The device receives R2D transmissions from a reader / writer. The R2D transmission is one or more of the following: a paging signal, a subsequent paging signal, an R2D transmission that triggers random access, and an R2D transmission that triggers terminal capability reporting. The R2D transmission includes a terminal capability query request.

[0058] Receive the R2D transmission, perform clock synchronization based on the TAS signal in the R2D transmission, and obtain the device's power information, SFO estimate, CFO estimate, and one or more of the maximum frequency shift range supported by the device;

[0059] Send a D2R transmission to the reader / writer, wherein the D2R transmission is the capability information reported by the IoT terminal device.

[0060] A communication method applied to a reader / writer, the method comprising:

[0061] Send a first message to one or more IoT terminal devices, the first message being used to indicate the resources for multiple access of the IoT terminal devices;

[0062] Receive multiple second messages sent by multiple IoT terminal devices in a multiple access manner, wherein the multiple access manner includes time division multiple access and / or frequency division multiple access.

[0063] In one embodiment, the method further includes:

[0064] Receive D2R transmission sent by the IoT terminal device, obtain timing acquisition signal from the D2R transmission, perform one or more of the SFO, CFO estimation and clock calibration operations, and obtain one or more of the SFO estimate, CFO estimate and clock correction result of the IoT terminal device.

[0065] Resource allocation for frequency division multiple access is performed on the IoT terminal device to obtain the first message.

[0066] In one embodiment, the D2R transmission is capability information reported by the IoT terminal device; the capability information includes at least one of chip length, maximum frequency offset factor, maximum repetition count, device power information, SFO estimate, CFO estimate, maximum frequency shift range supported by the device, and NR band or frequency range supported by the device.

[0067] In one embodiment, the reader / writer uses the first message to indicate frequency domain resources to multiple IoT terminal devices, and / or, frequency shift factor, and / or, frequency shift factor-related parameters, to ensure that no frequency domain resource conflict occurs on the same time domain resources.

[0068] In one embodiment, the frequency domain resource conflict includes at least one of the following:

[0069] The frequency domain resources of the IoT terminal device overlap with the frequency domain resources of other IoT terminal devices.

[0070] The frequency domain resources of the D2R transmission sent by the IoT terminal device based on the instruction of the first message overlap with the frequency domain resources of the D2R transmission sent by other IoT terminal devices based on the instruction of the first message.

[0071] The frequency domain resources used by the IoT terminal device to transmit D2R transmissions generate harmonic interference with the frequency domain resources used by other IoT terminal devices to transmit D2R transmissions.

[0072] In one embodiment, the frequency domain resources of the D2R transmission include the main lobe frequency band after frequency shifting by the IoT terminal device based on the frequency shift factor or frequency shift factor-related parameters.

[0073] In one embodiment, the harmonic interference is the frequency band of the third harmonic of the D2R transmission sent by the IoT terminal device based on the instruction of the first message, which overlaps with the main lobe frequency band of the D2R transmission sent by other IoT terminal devices based on the instruction of the first message.

[0074] In one embodiment, the first message is an R2D transmission, which includes one or more of timing acquisition signals, R2D transmission data, control information, and postamble; the second message is a D2R transmission, which includes one or more of timing acquisition signals, D2R transmission data, control information, midamble, and postamble.

[0075] In one embodiment, the timing acquisition signal is a preamble, and the R2D transmission data is carried on the PRDCH.

[0076] In one embodiment, the timing acquisition signal at least characterizes the start of R2D and / or D2R transmission of the message to which the timing acquisition signal is located in the time domain, and the timing acquisition signal is used for clock synchronization, determining the chip duration of subsequent transmissions, SFO estimation, CFO estimation, channel estimation, and interference estimation, or one or more of these.

[0077] In one embodiment, the control information includes at least one of the scheduling information for the R2D transmission and the scheduling information for the D2R transmission corresponding to the R2D transmission. The scheduling information for the D2R transmission includes at least one of the following: time-domain and / or frequency-domain resources, MCS-like information, chip duration, information bit duration, frequency offset factor, device-related ID, repetition, D2R preamble related indication information, and D2R midamble related indication information.

[0078] In one embodiment, the method further includes:

[0079] In the first message, based on control information in different formats and / or the content of the control information, the implementation mode of the frequency division multiple access of the IoT terminal device is indicated; and / or,

[0080] In the first message, based on different formats of control information and / or the content of the control information, the device type is indicated, and the frequency division multiple access implementation method of the IoT terminal device is indicated.

[0081] A communication device for use in Internet of Things (IoT) terminal devices, the device comprising:

[0082] The first receiving module is used to receive the first message sent by the reader / writer;

[0083] The first sending module is configured to send a second message to the reader based on the indication of the first message; the second message is sent by the IoT terminal device in a multiple access mode, the multiple access mode including time division multiple access and / or frequency division multiple access.

[0084] A communication device for use in a reader / writer, the device comprising:

[0085] The second sending module is used to send a first message to one or more IoT terminal devices, wherein the first message is used to indicate the resources for multiple access of the IoT terminal devices;

[0086] The second receiving module is used to receive multiple second messages sent by multiple IoT terminal devices in a multiple access manner, wherein the multiple access manner includes time division multiple access and / or frequency division multiple access.

[0087] A communication device includes: a transmitter and a receiver;

[0088] The transmitter is used to receive the first message sent by the reader / writer;

[0089] The receiver is configured to send a second message to the reader based on the indication of the first message; the second message is sent by the IoT terminal device in a multiple access mode, the multiple access mode including time division multiple access and / or frequency division multiple access.

[0090] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method in the embodiments of this application.

[0091] A computer program product includes a computer program that, when executed by a processor, implements the steps of the method described in the embodiments of this application.

[0092] The aforementioned communication method, apparatus, communication device, storage medium, and computer program product, wherein the method includes: an IoT terminal device receiving a first message sent by a reader; and sending a second message to the reader based on the instruction of the first message; the second message being sent by the IoT terminal device in a multiple access mode, including time division multiple access and / or frequency division multiple access; the reader can combine the terminal capabilities of multiple devices and the actual channel status, and allocate random access resources to multiple devices by sending the first message to the devices, thereby avoiding frequency conflicts between resources used by multiple devices, improving the effectiveness of resource allocation, and improving the transmission efficiency and reliability of the system. Attached Figure Description

[0093] Figure 1 This is a diagram illustrating the application environment of a communication method in one embodiment;

[0094] Figure 2 This is a flowchart illustrating a communication method in one embodiment;

[0095] Figure 3 This is a flowchart illustrating the signal transmission steps in one embodiment;

[0096] Figure 4 This is a flowchart illustrating the communication method in another embodiment;

[0097] Figure 5 Here is a signaling diagram of the communication method in another embodiment;

[0098] Figure 6This is a structural block diagram of a communication device in one embodiment;

[0099] Figure 7 This is a structural block diagram of a communication device in one embodiment;

[0100] Figure 8 This is an internal structural diagram of a communication device in one embodiment. Detailed Implementation

[0101] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0102] Figure 1 This is a schematic diagram illustrating an application scenario of a communication method provided in an embodiment of this application. For example... Figure 1 As shown, this scenario includes an IoT terminal device 100 and a reader / writer 200. The IoT terminal device 100 and the reader / writer 200 transmit data via a network.

[0103] Among them, the IoT terminal device 100 can be a terminal IoT device in passive IoT or a terminal device in ambient IoT, that is, an ambient IoT terminal device; the reader can be a reader IoT device in passive IoT.

[0104] Because passive IoT devices have relatively weak functionality, especially Device1 with energy less than 1uW, they lack the ability to autonomously emit electromagnetic waves and can only transmit data via backscattered waves. Therefore, the traditional cellular FDMA (Frequency Division Multiple Access) scheme is no longer applicable. Issues such as the frequency shifting implementation method for devices, reader resource allocation and indication, device time and frequency resource determination, and frequency conflict avoidance among multiple devices still urgently need to be addressed in the FDMA process.

[0105] Based on the aforementioned traditional technologies, this application provides a communication method, specifically a data transmission method for multiple passive IoT devices accessing the network via Frequency Division Multiple Access (FDMA). This method includes a device-side frequency domain resource determination method and a reader-side resource scheduling mechanism. It supports passive IoT devices in frequency shifting based on codeword repetition or mixing, and supports repetition count and frequency offset calculation methods under different line codes. It also supports devices reporting maximum frequency offset based on frequency offset estimation and their own capabilities. The reader can indicate FDMA resources by sending messages to the passive IoT devices, avoiding frequency domain conflicts between multiple passive IoT devices, reducing frequency resource collisions, and improving system transmission efficiency and reliability.

[0106] It should be noted that the beneficial effects or technical problems solved by the embodiments of this application are not limited to this one, but may also be other implicit or related problems. For details, please refer to the description of the embodiments below.

[0107] Before introducing specific embodiments of the present invention, the technical terms involved in the present invention will be explained:

[0108] Device: Passive IoT terminal device; Paging: Paging message; Trigger: Trigger message; ID: Identification code, identifier; D2R: IoT device to reader; R2D: Reader to IoT device; FDMA: Frequency Division Multiple Access; MSG (Message): Messages for random access in Ambient IoT, including MSG1, MSG2, and MSG3; TAS (Timing acquisition signal): Timing acquisition signal; MCS: Modulation and coding scheme; CP (Cyclic Prefix): Cyclic prefix.

[0109] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0110] In one embodiment, such as Figure 2 As shown, a communication method is provided, which is applied to Figure 1 Taking IoT terminal devices as an example, the explanation includes the following steps:

[0111] Step 202: Receive the first message sent by the reader / writer.

[0112] Specifically, an environmental IoT system may include a reader and multiple IoT terminal devices. The reader communicates with the multiple IoT terminal devices; a first message is used to indicate the multiple access method by which the multiple IoT terminal devices send messages to the reader. In one example, the reader sends a first message to one or more IoT terminal devices; optionally, the IoT terminal device may be referred to as an environmental IoT terminal device.

[0113] Step 204: Based on the instruction of the first message, send the second message to the reader / writer.

[0114] The second message is sent by the IoT terminal device in a multiple access manner, including time division multiple access and / or frequency division multiple access. Time division multiple access means that multiple IoT terminal devices send the second message to the reader in different time slots. Frequency division multiple access means that multiple IoT terminal devices send multiple second messages to the reader based on the different frequency bandwidths allocated to them.

[0115] Specifically, the IoT terminal device can receive a first message sent by the reader and, based on the resources allocated to the IoT terminal device by the reader in the first message, send a second message to the reader in the form of time division multiple access and / or frequency division multiple access; the second message can be D2R transmission, or it can be D2R transmission data, etc.

[0116] In the above communication method, the IoT terminal device can receive a first message sent by the reader; and based on the instruction of the first message, send a second message to the reader; the second message is sent by the IoT terminal device in a multiple access mode, including time division multiple access and / or frequency division multiple access; the reader can combine the terminal capabilities of multiple devices and the actual channel status, and allocate random access resources to multiple devices by sending the first message to the devices, thereby avoiding frequency conflicts between the resources used by multiple devices, improving the effectiveness of resource allocation and improving the transmission efficiency and reliability of the system.

[0117] In one embodiment, the first message is an R2D transmission, which includes one or more of the following: timing acquisition signal TAS, R2D transmission data, control information, and postamble; the second message is a D2R transmission, which includes one or more of the following: timing acquisition signal, D2R transmission data, control information, midamble, and postamble.

[0118] Specifically, the reader sends a first message to the IoT terminal device, which can be an R2D transmission. Correspondingly, the R2D transmission message can carry one or more of the following information: Time-Series Acquisition Signal (TAS), R2D transmission data, control information, and a postamble. The TAS can be a continuous signal and / or a discrete signal acquired sequentially in the time dimension. The R2D transmission data can be data transmitted from the reader to the IoT terminal device. The postamble can be a specific sequence located at the end of the data frame. The D2R transmission can represent a message sent from the IoT terminal device to the reader. The D2R transmission data represents data transmitted from the IoT terminal device to the reader. The midamble represents the area between the preamble and the postamble.

[0119] In this embodiment, the content carried in the first message and the second message can include a variety of contents to ensure message diversity.

[0120] In one embodiment, the timing acquisition signal is a preamble, and the R2D transmission data is carried on the PRDCH. The preamble can be a known sequence located at the very beginning of the data frame.

[0121] In one embodiment, the timing acquisition signal is at least a time-domain characterizing the start of R2D and / or D2R transmission of the message to which the timing acquisition signal is located. The timing acquisition signal is used for clock synchronization, determining the chip duration of subsequent transmissions, sampling frequency offset (SFO) estimation, carrier frequency offset (CFO) estimation, channel estimation, and interference estimation, or one or more of these.

[0122] Specifically, the timing acquisition signal in the first message can characterize the start of R2D transmission of the first message in the time domain; the timing acquisition signal in the second message can characterize the start of D2R transmission of the second message in the time domain. Optionally, the timing acquisition signal can be used to perform one or more of sampling frequency offset (SFO) estimation, carrier frequency offset (CFO) estimation, channel estimation, and interference estimation to obtain one or more of the following: acquisition frequency offset estimate, carrier frequency offset estimate, channel estimation result, and interference estimation result.

[0123] In this embodiment, by carrying timing acquisition signals in both the first and second messages, the start of the time domain can be accurately characterized, ensuring the reliability of data transmission.

[0124] In one embodiment, the control information includes at least one of the scheduling information for R2D transmission and the scheduling information for D2R transmission corresponding to the R2D transmission. The scheduling information for D2R transmission includes at least one of the following: time-domain and / or frequency-domain resources, class modulation and coding scheme (MCS) information, chip duration, information bit duration, frequency offset factor, device-related ID, repetition, D2R preamble related indication information, and D2R midamble related indication information.

[0125] Specifically, the control information may include scheduling information for R2D transmission, or the control information may include scheduling information for D2R transmission corresponding to R2D transmission; wherein, the D2R transmission corresponding to R2D transmission may be a signal sent from the device to the reader after the reader sends data to the device.

[0126] Optionally, the scheduling information for R2D transmission may include at least one of the following: time-domain and / or frequency-domain resources, class modulation and coding scheme (MCS) information, chip duration, information bit duration, frequency offset factor, device-related ID, repetition, R2D preamble related indication information, and R2D midamble related indication information.

[0127] In this embodiment, scheduling information is described in multiple forms to accurately indicate resource allocation, further avoiding the risk of resource conflicts and enabling frequency division multiple access for multiple IoT terminal devices.

[0128] In one embodiment, the method further includes:

[0129] Clock calibration is performed on R2D transmission to obtain one or more of the following: sampling frequency offset estimate, carrier frequency offset estimate, maximum frequency shift range supported by the device, and NR band or frequency range supported by the device.

[0130] Specifically, the sampling frequency offset can be a deviation value caused by the frequency difference between the sampling clocks of the transmitting end and the receiving end; the IoT terminal device can perform clock calibration processing on the received R2D transmission to obtain one or more of the following: the estimated carrier frequency offset of the IoT terminal device, the maximum frequency shift range supported by the device, the NR frequency band supported by the device, or the frequency range supported by the device.

[0131] In this embodiment, by accurately estimating various parameters of the device, the accuracy of signal demodulation can be improved, the influence of signal noise can be suppressed, and a reliable communication foundation can be provided for subsequent communication between the device and the reader.

[0132] In one embodiment, the method further includes:

[0133] In D2R transmission, the capability information of the IoT terminal device is sent to the reader. The capability information includes device power information, device type, estimated sampling frequency offset, estimated carrier frequency offset, maximum frequency offset range supported by the device, and one or more of the NR bands or frequency ranges supported by the device.

[0134] Specifically, the capability information of the IoT terminal device can be the capability information that the IoT terminal device can use to communicate with other devices, such as readers and writers; the device power information can be the current real-time power of the IoT terminal device or the maximum power that the device can store; the device type can include any one of device 1, device2a, and device 2b; the NR band or frequency range supported by the device can be the NR band supported by the device or the frequency range supported by the device.

[0135] In this embodiment, accurate reporting of terminal device capability information is achieved, which assists the reader in allocating resources among multiple terminals and improves the effectiveness of resource allocation.

[0136] In one embodiment, the method further includes:

[0137] Based on the scheduling information of the D2R transmission corresponding to the R2D transmission contained in the control information of the R2D transmission, obtain the frequency division multiple access resource indicated by the reader, and send D2R data / D2R transmission to the reader on the frequency division multiple access resource indicated by the reader.

[0138] Specifically, when an IoT terminal device receives an R2D transmission sent by a reader, it can obtain the control information carried in the R2D transmission and, based on the scheduling information of the D2R transmission corresponding to the R2D transmission contained in the control information, obtain the frequency division multiple access resources allocated to the IoT terminal device by the reader. That is, the reader uses the scheduling information in the control information contained in the R2D transmission to indicate the frequency division multiple access resources to the IoT terminal device. In this way, the IoT terminal device can send D2R data to the reader or send D2R transmissions to the reader on the access resources allocated to the IoT terminal device by the reader.

[0139] In this embodiment, D2R data / signals are sent to the reader / writer based on the resources indicated by the reader / writer, ensuring accurate transmission based on the reader / writer's instructions and further improving the effectiveness of resource allocation.

[0140] In one embodiment, the IoT terminal device determines the implementation method of frequency division multiple access in at least one of the following ways:

[0141] The implementation method of frequency division multiple access is determined in a predefined or pre-configured manner, and / or based on the type of IoT terminal device and / or the multiple access mode indication corresponding to the IoT terminal device;

[0142] Based on control information in different formats and / or the content of control information, determine the frequency division multiple access implementation method of IoT terminal devices;

[0143] Based on the device type indicated by different formats of control information and / or the content of control information, determine the frequency division multiple access implementation method of IoT terminal devices.

[0144] Specifically, the predefined or preconfigured method can be a method that the reader / writer predefines or configures for the IoT terminal device; the type of IoT terminal device can be a device type, such as any one of device 1, device2a, and device 2b; the multiple access mode indication corresponding to the IoT terminal device can be the multiple access mode that the IoT terminal device determines.

[0145] Control information in different formats can be represented by one or more fields or one or more code points in the fields indicating the control information format, or it can be control information scrambled with different information, or it can be control information with CRC appended with different lengths and / or contents; the content of control information in different formats can be the content of control information represented by one or more fields or one or more code points in the fields; after receiving the first message sent by the reader, the terminal device can determine the corresponding frequency division multiple access implementation method based on the control information carried in the first message and / or the content of the control information.

[0146] Optionally, different formats can be multiple formats such as one or more fields, one or more code points in a field, etc. For example, control information and / or the content of control information can indicate the device type of the terminal device. The terminal device can determine the device type based on the device type indicated by the control information and / or the content of the control information in different formats, and determine the frequency division multiple access implementation method corresponding to the device type. The specific implementation method of frequency division multiple access based on the device type will be described in detail in subsequent embodiments, and will not be repeated here.

[0147] In this embodiment, the terminal can determine the implementation method of frequency division multiple access in a variety of ways, which is more flexible, applicable to a variety of different scenarios, and can achieve more comprehensive service support capabilities.

[0148] In one embodiment, the communication method further includes:

[0149] When the D2R transmission of an IoT terminal device is achieved by backscattering on an externally provided carrier, frequency division multiple access is achieved through a small frequency offset of the carrier; or, when the D2R transmission of an IoT terminal device is generated internally by the device, frequency division multiple access is achieved through a small frequency offset of the carrier and / or a spectrum shifting mechanism of the generated waveform.

[0150] Specifically, the terminal device can determine the implementation method of its own D2R transmission and, based on the implementation method of the D2R transmission, determine the implementation method of the frequency division multiple access (FDMA) of the IoT device. For example, when the terminal device determines that the D2R transmission of the device is implemented by backscattering on an externally provided carrier, then the terminal device can determine that FDMA is implemented by a small frequency offset of the carrier.

[0151] Optionally, when the terminal device determines that the D2R transmission of the device is generated internally, it can be determined that the frequency division multiple access method of the device can be any one of the following: small frequency offset of the carrier or spectrum shifting mechanism of the generated waveform. The specific implementation method of frequency division multiple access can be determined based on the actual application scenario.

[0152] In this embodiment, the specific method for implementing frequency division multiple access in IoT terminal devices is quickly determined through the device's D2R transmission method.

[0153] In one embodiment, the method further includes:

[0154] When the IoT terminal device is device 1 and / or device 2a, frequency division multiple access is achieved by a small frequency offset of the backscattered carrier; or, when the IoT terminal device is device 2b, frequency division multiple access is achieved by a small frequency offset of the carrier and / or a spectrum shifting mechanism for generating waveforms.

[0155] Specifically, IoT terminal devices can exist in different device types. Thus, an IoT terminal device can obtain its own device type and, based on this type, determine the method for implementing frequency division multiple access (FDMA). In one example, when the device type is device1, and / or device2a, the IoT terminal device can determine that FDMA is implemented using a small frequency offset of the backscattered carrier. That is, the method for implementing FDMA is determined to be a small frequency offset of the backscattered carrier; in other words, D2R transmission of the IoT terminal device can be achieved through backscattering.

[0156] In another example, when the device type is device2b, the IoT terminal device can determine its frequency division multiple access (FDMA) implementation method based on the small frequency offset of the carrier and the spectrum shifting mechanism of the generated waveform. For example, the IoT terminal device can determine one or more of the small frequency offset of the carrier and the spectrum shifting mechanism of the generated waveform as its FDMA implementation method. In other words, when the device type is device2b, the D2R transmission of the IoT terminal device can be implemented internally within the device.

[0157] In this embodiment, the specific method for implementing frequency division multiple access in IoT terminal devices is accurately and efficiently determined by the device type.

[0158] In one embodiment, the first message is used to indicate the time-domain resource allocation and / or frequency-domain resource allocation during D2R transmission.

[0159] Specifically, the reader can send a first message to one or more IoT terminal devices. The first message is used to instruct the IoT terminal device on the resources used by the IoT terminal device when sending data to the reader, i.e. when the IoT terminal device performs D2R (Device to Reader) transmission. For example, it can instruct the time domain resource allocation, frequency domain resource allocation, or time-frequency domain resource allocation when performing D2R transmission.

[0160] In this implementation, the reader accurately instructs the IoT terminal device on relevant data regarding time-domain and / or frequency-domain resource allocation through the first message, thereby improving the reliability of information transmission.

[0161] In one embodiment, the data in the first message used to indicate time-domain resource allocation and / or frequency-domain resource allocation includes at least control information, which is one or more of physical layer control information, MAC CE, and higher-layer signaling.

[0162] Specifically, the first message may include at least control information. The data / fields / parts in the first message used to instruct the IoT terminal device on time-domain resource allocation and / or frequency-domain resource allocation may include at least control information. That is, the reader / writer can instruct on time-domain resource allocation and / or frequency-domain resource allocation at least through the control information in the first message.

[0163] Optionally, the control information in the first message can be one or more of the following: physical layer control information, MAC CE (Media Access Control Control Element), and higher-layer signaling (RRC signaling).

[0164] In this embodiment, the control information in the first message is described in multiple ways, and the control information in the first message can be used to instruct the IoT terminal device on resource allocation, ensuring the diversity of the transmission form of the control information and the flexible configuration in the first message.

[0165] In one embodiment, the first message includes at least one of the following: a field, multiple fields, a code point in a field, multiple code points in a field, a string, and a corresponding bit mapping table, indicating one or more of the following: frequency domain resource location, frequency domain resource offset, and length of continuously allocated frequency domain resources.

[0166] Specifically, the first message may include a field indicating one or more of the following: frequency domain resource location, frequency domain resource offset, and length of continuously allocated frequency domain resources; or, the first message may include multiple fields, each indicating one or more of the following: frequency domain resource location, frequency domain resource offset, and length of continuously allocated frequency domain resources; or, the first message may include at least one code point in one field, indicating one or more of the following: frequency domain resource location, frequency domain resource offset, and length of continuously allocated frequency domain resources; or, the first message may use multiple code points in one field to indicate one or more of the following: frequency domain resource location, frequency domain resource offset, and length of continuously allocated frequency domain resources. Alternatively, the first message may use a string and a corresponding bit mapping table to indicate the above information respectively; optionally, the first message may also use a field and a code point in that field to jointly indicate the above information, wherein the fields may be the same or different fields, and the specific methods of joint indication cannot be exhaustively listed, but are all within the protection scope of this embodiment.

[0167] Optionally, the first message may include a field carrying information that may include one or more of the following: timing acquisition signal (TAS), R2D transmission data, control information, and postamble code. Thus, the field in the first message can be used to indicate one or more of the following: frequency domain resource location, frequency domain resource offset, and length of continuously allocated frequency domain resources.

[0168] Optionally, the first message may include multiple fields, each carrying information including one or more of the following: timing acquisition signal (TAS), R2D transmission data, control information, and postamble code. Thus, the multiple fields in the first message can be used to indicate one or more of the following: frequency domain resource location, frequency domain resource offset, and length of continuously allocated frequency domain resources. Correspondingly, the representation of a single code point in a field within the first message, and multiple code points in a field, is similar and will not be elaborated further here.

[0169] In this embodiment, the first message can carry a variety of information in multiple ways, further enhancing the flexibility of the way the information is carried in the first message and the diversity of the information carried.

[0170] In one embodiment, when the IoT terminal device determines the location of frequency domain resources based on the first message, the content of the first message includes at least any of the following:

[0171] Optionally, the resource unit number N1 and / or the size Ru of a single frequency domain resource unit;

[0172] Ru can be the size of a single frequency domain resource unit. The frequency domain resource location is determined based on the resource unit number N1 and / or the size Ru of a single frequency domain resource unit. The frequency domain resource location can be the actual frequency location F1, where F1 = N1 * Ru.

[0173] Optionally, the starting resource unit number Nstart, the frequency domain offset Nsf from the starting frequency, and / or the size Ru of a single frequency domain resource unit;

[0174] The starting resource unit number NStart and the frequency offset Nsf from the starting frequency are indicated. The starting frequency Fstart can be indicated by the starting resource unit number, and the starting frequency can be the frequency of the carrier CW. Correspondingly, the frequency domain resource position F1 = Nsf*Ru + Nstart*Ru.

[0175] Optionally, the frequency domain offset Nsf from the starting frequency, the size Ru of a single frequency domain resource unit, and the starting frequency Fstart, the starting frequency being at least the frequency that supports the carrier CW;

[0176] Frequency offset is indicated by the frequency domain offset Nsf from the starting frequency: Fsf = Nsf * Ru, the starting frequency Fstart supports at least the frequency of carrier CW; frequency domain resource location F1 = Nsf * Ru + Fstart.

[0177] Optionally, frequency offset factor Rsf, or frequency offset factor related indication information;

[0178] The frequency offset factor related indication information includes one or more of the following: D2R frequency offset factor calculation parameter n, frequency offset factor calculation rule, frequency offset factor calculation type, and maximum value of D2R frequency offset factor.

[0179] Optionally, the information bit duration Tb or the information bit rate 1 / Tb;

[0180] Specifically, the frequency domain offset Fsf of the distance CW is determined based on the information bit duration Tb and the frequency offset factor Rsf; or, the frequency domain offset Fsf of the distance CW is determined based on the information bit rate 1 / Tb and the frequency offset factor Rsf; Fsf = ±Rsf / Tb. Thus, the frequency domain resource location F1 = Fsf + Fcw, where Fcw is the carrier frequency, and Fcw = Ncw * Ru;

[0181] Optionally, the length indication information of the amble transmitted by D2R includes at least one of preamble, midamble, and postamble; wherein, preamble can be a preamble signal or preamble code, midamble can be an intermediate code, and postamble can be a postsynchronization code.

[0182] Optionally, the carrier frequency is Fcw; where the frequency domain resource location is F1 = Fsf + Fcw, and Fsf is the frequency domain offset Fsf from CW.

[0183] Optionally, the chip duration Tc or the chip rate 1 / Tc;

[0184] Specifically, the frequency domain offset from CW is Fsf = ±Rsf / (2*Tc); correspondingly, the frequency domain resource location is F1 = Fsf + Fcw.

[0185] Optionally, the transmission bandwidth and / or baseband bandwidth BW.

[0186] Specifically, Fsf = ±Rsf*BW / 4, so the frequency domain resource location F1 = Fsf + Fcw, where Fcw = Ncw*Ru is the carrier frequency and Ru is the size of a single frequency domain resource unit.

[0187] In this embodiment, the reader can allocate random access resources in various ways, and the device can determine the location of frequency domain resources in various ways, further improving the flexibility of message configuration.

[0188] In one embodiment, the frequency offset factor related indication information includes one or more of the following: D2R frequency offset factor calculation parameter n, frequency offset factor calculation rule, frequency offset factor calculation type, and maximum value of D2R frequency offset factor.

[0189] In one embodiment, when the IoT terminal device determines the length of the continuous frequency domain resource based on the first message, the content of the first message includes at least any of the following:

[0190] The number of continuous frequency domain units, NBW;

[0191] Specifically, the first message can directly indicate the number of consecutive frequency domain units NBW, and the length of consecutive frequency domain resources (the length of consecutively allocated frequency domain resources) FBW=NBW*Ru, where Ru can be the size of a single frequency domain resource unit.

[0192] Indicates the duration Tb of the information bit or the information bit rate 1 / Tb;

[0193] Specifically, the first message can indicate the duration Tb of the baseband information bit, or it can indicate the information bit rate Tb, and the continuous frequency domain resource length (the length of the continuously allocated frequency domain resources) FBW=4 / Tb.

[0194] The length indication information of the amble transmitted in D2R includes at least one of the preamble, midamble, and postamble; where the preamble can be a preamble signal or preamble code, the midamble can be an intermediate code, and the postamble can be a postsynchronization code.

[0195] Indicates the chip duration Tc or chip rate 1 / Tc;

[0196] Specifically, the first message can indicate the chip duration Tc or chip rate 1 / Tc, and the continuous frequency domain resource length (the length of continuously allocated frequency domain resources) FBW=2 / Tc.

[0197] Indicates the transmission bandwidth and / or baseband bandwidth BW';

[0198] Specifically, the continuous frequency domain resource length (the length of continuously allocated frequency domain resources) FBW = BW' / 2.

[0199] Indicates the block size TBS and / or the duration T of the D2R message.

[0200] Specifically, the continuous frequency domain resource length (the length of continuously allocated frequency domain resources) FBW = TBS / T / 2.

[0201] In this embodiment, the reader can allocate random access resources in various ways, and the device can determine the length of continuous frequency domain resources in various ways, further improving the flexibility of message configuration.

[0202] In one embodiment, the first message indicates one or more of the following through at least one of the following methods: a field, multiple fields, a code point in a field, multiple code points in a field, an indicator, multiple indicators, a string, and a corresponding bit mapping table: D2R frequency offset factor Rsf, D2R frequency offset factor calculation parameter n, frequency offset factor calculation rule, frequency offset factor calculation type, and maximum value of D2R frequency offset factor.

[0203] Specifically, the first message can exist in various formats, such as fields, indicators, code points in fields, strings, and bit mapping tables corresponding to those strings. The first message can indicate one or more of the following in various formats: D2R frequency offset factor Rsf, D2R frequency offset factor calculation parameter n, frequency offset factor calculation rule, frequency offset factor calculation type, and maximum value of D2R frequency offset factor. For example, the above information can be indicated by a single field, a code point in a field, or multiple code points in a field. The format of code points in fields is similar to that of indicators and will not be described in detail here. Optionally, the first message can also jointly indicate the above information by a single field and a code point in a field. The fields can be the same or different fields. The specific methods of joint indication cannot be exhaustively listed, but all are within the protection scope of this embodiment.

[0204] In this embodiment, the first message used to indicate resource allocation can include multiple formats, further improving the flexibility of capability information configuration, ensuring the reliability of information transmission, and realizing the effective allocation of random access resources.

[0205] In one embodiment, the first message indicates the row index value m of the frequency offset factor allocation table via a frequency offset factor indicator field or one or more code points in the field.

[0206] Specifically, the first message indicates the row index value m of the frequency offset factor allocation table through a frequency offset factor indicator field, or through a code point in a frequency offset factor indicator field, or through multiple code points in a frequency offset factor indicator field.

[0207] In one embodiment, the definition of each row in the frequency offset factor allocation table includes one or more of the following: frequency offset factor Rsf, frequency offset factor calculation parameter n, frequency offset factor calculation rule, frequency offset factor calculation type, maximum value of D2R frequency offset factor, D2R application scenario or message type, and parameters, including one or more of the continuously allocated frequency domain resources NBW, Tb or information bit rate, Tc or chip rate, transmission bandwidth, baseband bandwidth, and R2D and D2R time domain unit ratios.

[0208] Specifically, the D2R application scenario or message type and parameters include the D2R application scenario, or the D2R message type, or parameters; the parameters include one or more of the following: continuously allocated frequency domain resources NBW, Tb, information bit rate, Tc, chip rate, transmission bandwidth, baseband bandwidth, R2D time domain unit ratio, and D2R time domain unit ratio.

[0209] In this embodiment, by defining multiple types of data in the frequency offset factor allocation table, data diversity is ensured, message transmission efficiency is improved, and data transmission costs are reduced.

[0210] In one embodiment, capability information indicates one or more of the following for the IoT terminal device: sampling frequency offset estimate, carrier frequency offset estimate, maximum frequency offset range supported by the device, and NR bands or frequency ranges supported by the device, through one or more fields, one or more fields, one code point in one field, one or more code points in one field, or a string and a corresponding bit mapping table.

[0211] Specifically, the capability information can be the capabilities of an IoT terminal device. This capability information may include a single field indicating one or more of the following: the estimated sampling frequency offset, the estimated carrier frequency offset, the maximum frequency offset range supported by the device, and the NR bands or frequency ranges supported by the device. Alternatively, the capability information may include multiple fields, with one or more of these fields indicating the aforementioned information. Alternatively, the capability information may also indicate the aforementioned information through a single code point in a field, or through multiple code points in a field, respectively indicating the aforementioned information, for example, respectively indicating one or more of the estimated sampling frequency offset, the estimated carrier frequency offset, the maximum frequency offset range supported by the device, and the NR bands or frequency ranges supported by the device. Optionally, the capability information can also be jointly indicated by a single field and a code point within that field. These fields can be the same or different fields; the specific methods of joint indication are not exhaustive, but all are within the scope of this embodiment.

[0212] In this embodiment, the capability information can include multiple formats, further enhancing the flexibility of capability information configuration, ensuring the reliability of information transmission, and realizing the effective allocation of random access resources.

[0213] In one embodiment, the sampled frequency offset estimate indicates a quantized value or an index value, the carrier frequency offset estimate indicates a quantized value or an index value, and the maximum frequency offset range supported by the device indicates a quantized value or an index value for the frequency offset magnitude.

[0214] Specifically, the sampling frequency offset estimate supports an index value, which can be an index in a pre-configured table containing a field for the sampling frequency offset estimate; the carrier frequency offset estimate supports an index value, which can be an index in a pre-configured table containing a field for the carrier frequency offset estimate; the index value can be represented in binary, for example, the index value can include 00, 01, 10, 11, where each index value is configured with a corresponding estimate and a maximum frequency offset range.

[0215] In one embodiment, capability information indicates the index value m of the IoT terminal device in the capability information index table through one or more fields, or one code point in one field, or multiple code points in one field, or a string and a corresponding bit mapping table. The row definition content of the capability information index table includes SFO estimate, CFO estimate, maximum frequency offset range supported by the device, and one or more of the NR bands or frequency ranges supported by the device.

[0216] In this embodiment, the capability information can include multiple formats, further enhancing the flexibility of capability information configuration, ensuring the reliability of information transmission, and realizing the effective allocation of random access resources.

[0217] In one embodiment, such as Figure 3 As shown, the communication method also includes:

[0218] Step 302: Receive the R2D transmission from the reader / writer.

[0219] Among them, R2D transmission is one or more of the following: paging signal, subsequent paging signal, R2D transmission that triggers random access, and R2D transmission that triggers terminal capability reporting; R2D transmission includes terminal capability query request.

[0220] Specifically, the reader can send R2D transmissions to IoT terminal devices, such as one or more of the following: transmitting paging signals, subsequent paging signals, triggering random access R2D transmissions, and triggering terminal capability reporting R2D transmissions to IoT terminal devices.

[0221] Step 304: Receive R2D transmission, perform clock synchronization based on TAS signal in R2D transmission, and obtain device power information, SFO estimate, CFO estimate, and one or more of the maximum frequency shift range supported by the device.

[0222] Specifically, the terminal device can receive the R2D transmission sent by the reader and perform clock synchronization based on the TAS signal carried in the R2D transmission to obtain the power information, SFO estimate, CFO estimate, and one or more of the maximum frequency shift range supported by the device.

[0223] Step 306: Send D2R transmission to the reader / writer.

[0224] Among them, D2R transmission is the capability information reported by IoT terminal devices.

[0225] Specifically, after determining its own capability information, the terminal device can report the capability information of the IoT device to the reader via D2R transmission.

[0226] In this embodiment, through communication between the reader and the tag, the tag can report capability information to the reader in a timely manner, which helps the reader allocate resources for multiple access to multiple tags, ensuring that resources between devices do not conflict and improving the effectiveness of resource allocation.

[0227] Optionally, the first message jointly indicates the resource allocation of the first and second information sets in the frequency domain through a frequency domain resource allocation field, wherein the frequency domain resource allocation field includes a frequency domain resource indication value (RIV); the indication content includes at least one of the following:

[0228] Case 1: The relationship between RIV and the frequency domain starting resource unit Nstart and the length of the continuously allocated frequency domain resource block NBW is indexed to the mapping table through RIV; or, the relationship between RIV and the frequency offset Nsf of the frequency domain resource distance from the reference frequency point and the length of the continuously allocated frequency domain resource block NBW is indexed to the mapping table through RIV, for example, it could be Table 1-1;

[0229] Table 1-1

[0230]

[0231] Table 1-1 represents the mapping relationship between RIV and Nstart (or Nsf) and NBW. For example, S11 indicated by RIV can be indexed to the values ​​N1 and N1' of Nstart (or Nsf).

[0232] Case 2: The relationship between RIV and the frequency domain start frequency Fstart and the size of the continuously allocated frequency domain resources FBW is indexed into the mapping table through RIV; or, the relationship between RIV and the frequency offset Fsf from the reference frequency position and the size of the continuously allocated frequency domain resources FBW is indexed into the mapping table through RIV.

[0233] Specifically, the relationship between RIV and the frequency domain start frequency Fstart or the frequency offset Fsf from the reference frequency position and the continuously allocated frequency domain resource size FBW is indexed to a mapping table through RIV, such as Table 1-2:

[0234] Table 1-2

[0235]

[0236] Case 3: The relationship between RIV and frequency offset factor Rsf and parameter X is indexed to the mapping table through RIV; where X is one or more of the continuously allocated frequency domain resources NBW, Tb or information bit rate, Tc or chip rate, transmission bandwidth, and baseband bandwidth.

[0237] Specifically, the relationship between RIV, frequency offset factor Rsf, and parameter X is indexed into a mapping table via RIV, where X is one or more of the continuously allocated frequency domain resources NBW, Tb or bit rate, Tc or chip rate, transmission bandwidth, and baseband bandwidth, as shown in Table 1-3 for example:

[0238] Table 1-3

[0239]

[0240] Case 4: The D2R frequency domain resource allocation field value *m* is indicated by a frequency domain resource allocation field, along with the index of the (m+1)th row of the resource allocation table. The indexed row is defined to include one or more of the following: continuously allocated frequency domain resource NBW, Tb or information bit rate, Tc or chip rate, transmission bandwidth, baseband bandwidth, and D2R message type. Bandwidth may include transmission bandwidth and / or baseband bandwidth. The resource allocation table may be as shown in Tables 1-4 below.

[0241] Table 1-4

[0242]

[0243] In one embodiment, the first message indicates frequency domain resources through a bitmap table and a bitmap string. The bitmap string is NB bits in size, with each bit corresponding to a frequency domain resource unit. These frequency domain resource units are arranged in ascending order of frequency domain. Each frequency domain resource unit supports one or more of subbands, subcarriers, and frequency domain resource blocks, with NB representing the maximum number of corresponding resources. The bitmap table for the D2R transmission PDRCH frequency domain resources can be as shown in Tables 1-5.

[0244] Table 1-5

[0245]

[0246] Frequency domain resources are indicated by bitmap strings.

[0247] The bitmap string can be up to NB bits in size, with each bit corresponding to a frequency domain resource unit (FROM). FROMs are indexed in ascending frequency order, starting from the lowest frequency. The mapping order of FROM blocks in the mapping table is: from MSB -> LSB to subband 0 -> frequency domain resource NB-1. FROMs support one or more of subbands, subcarriers, and frequency domain resource blocks, with NB representing the maximum number of corresponding resources.

[0248] In one example, the minimum number of frequency domain resource units is S1, and the maximum number is S2. Continuous and non-contiguous resource configurations are supported, and the configuration method can be specified via a set of bitmap strings. If the corresponding bit value in the bitmap string is 1, the frequency domain resource allocated to the UE is located on that frequency domain resource unit. Specifically, if the frequency domain resource is the minimum resource allocation unit, it is allocated to the UE; otherwise, if the corresponding bit value in the bitmap string is 0, the frequency domain resource unit is not allocated to the UE. In another example, the frequency domain resource is configured as a certain number of resource units or one of the values ​​of a set of resource unit configuration indices. When configuring S1>S2, different resource sizes at the beginning and end are supported.

[0249] In one embodiment, the first message indicates the frequency offset factor via a bitmap string; the bitmap string is N bits in size, with each bit corresponding to a frequency offset factor; each set of frequency offset factors is configured with the value of each element in a pre-configured, pre-defined, or Reader-indicated manner, where N is the maximum number of elements in a set of frequency offset factors. Optionally, the first message can indicate the frequency offset factor via control information in the first message, for example, via a bitmap string.

[0250] Specifically, the first message can indicate the frequency offset factor via a bitmap string; for example, the bitmap string is N bits in size, with each bit corresponding to a frequency offset factor. Frequency domain resources are indexed in ascending order of size, starting with the smallest value. A set of frequency offset factors {Rsf1, …, RsfN} is configured with the value of each element through pre-configuration, pre-definition, or Reader indication, where N is the maximum number of elements in the set of frequency offset factors. The corresponding bitmap table for the D2R transmission PDRCH frequency domain resources can be as shown in Table 1-6:

[0251] Table 1-6

[0252]

[0253] In one embodiment, the first message is used to indicate a joint set of time-frequency resources. The time-domain resources include at least one of the following: frame, subframe, time slot, sub-time slot, time unit, Tb duration, chip duration, R2D symbol, and time-domain resource index. The frequency-domain resources include at least one of the following: subband, subcarrier, resource block, resource unit, frequency offset factor, and frequency-domain resource index. The time-domain resources are arranged in ascending order of time, and the frequency-domain resources are arranged in ascending order of frequency.

[0254] Specifically, the first message can be used to indicate the joint time-frequency domain resource CORESET, for example, it can include a set of time-domain resources and a set of frequency-domain resources; wherein the elements of the time-domain resource set support frames, subframes, time slots, sub-time slots, time units, Tb durations, chip durations, R2D symbols, or one of the time-domain resource indices determined by Embodiment 1; wherein the elements of the time-frequency domain resource set support subbands, subcarriers, resource blocks, resource units, frequency offset factors, or one of the time-domain resource indices determined by other embodiments (the indices of time-domain resources will be described in detail in the following embodiments, and will not be repeated here). Frequency-domain resources are indexed in ascending order of frequency, starting from the lowest frequency. Time-domain resources are indexed in ascending order of time, starting from the smallest time.

[0255] Optionally, the joint resource set in the time and frequency domains is indicated by a bitmap string, where each bit corresponds to a joint resource consisting of one frequency domain resource and one time domain resource. That is, the bitmap string is Nf*Nt bits in size, and each bit corresponds to a resource consisting of one frequency domain resource and one time domain resource. This bit mapping table can be as shown in Tables 1-7 below:

[0256] Table 1-7

[0257]

[0258] The specific content of Table 1-7 may be the CORESET bitmap of the time-frequency domain resource of the PDRCH in D2R transmission.

[0259] Optionally, the joint resource set in the time and frequency domains is indicated by a resource mapping table and an index. Each row of the resource mapping table is defined to include at least one of the following: time-domain resources, frequency-domain resources, frequency offset factor, repetition count, mapping type, and parameters. These parameters include continuously allocated frequency-domain resources (NBW), Tb or information bit rate, Tc or chip rate, transmission bandwidth, baseband bandwidth, R2D and D2R time-domain unit ratio, and one or more application scenarios or message types. The resource mapping table can be a D2R transmission PDRCH time-frequency domain resource CORESET mapping table, specifically as shown in Tables 1-8.

[0260] Table 1-8

[0261]

[0262] Optionally, the joint resource set in the time and frequency domain indicates at least an index in the joint resource set in the time and frequency domain through one or more fields, or one code point in one field, or multiple code points in one field, wherein the index corresponds to a time domain resource and / or a frequency domain resource.

[0263] In one example, the first message may also indicate one or more of the following through one or more fields, one code point in one field, multiple code points in one field, one indicator, or multiple indicators: D2R frequency offset factor Rsf, D2R frequency offset factor calculation parameter n, frequency offset factor calculation rule, frequency offset factor calculation type, and maximum value of D2R frequency offset factor:

[0264] Optionally, the frequency offset factor value Rsf can be directly indicated; or, the frequency offset factor can be indirectly derived by the device according to a pre-configured or predefined calculation method or determined by the device implementation by indicating one or more of the calculation parameters n, frequency offset factor calculation rules or types, and the maximum value of the D2R frequency offset factor.

[0265] Specifically, the calculation rule for Rsf is indicated by a 1-bit indicator or a code point in higher-layer signaling. When the first value is indicated, the device uses the first calculation rule, Rsf = 2. n , n = 0,1,…; otherwise, when the second value is indicated, the device uses the second calculation rule, Rsf = 2n, n = 0,1,… and the frequency offset factor calculation parameter n is indicated by an indicator or a code point of higher-layer signaling.

[0266] Table 2-1 can be the frequency offset factor calculation rules and parameters corresponding to the frequency offset factor:

[0267] Table 2-1

[0268]

[0269] The maximum frequency offset factor, Rsf_max, is indicated by an indicator or a code point in higher-layer signaling. When the frequency offset factor Rsf calculated by the device is greater than Rsf_max, the device uses Rsf_max as the frequency offset factor. Table 2-2 shows the frequency offset factor calculation rules and the maximum frequency offset factor corresponding to the code point.

[0270] Table 2-2

[0271]

[0272] In one example, the first message may also provide an index of row m+1 of the frequency offset factor allocation table via a frequency offset factor indicator field or one or more code points in the field indicating the index value m. The indexed row defines one or more of the following: frequency offset factor Rsf, frequency offset factor calculation parameter n, frequency offset factor calculation rule or type, maximum D2R frequency offset factor, and D2R application scenario or message type. A row definition in the frequency offset factor index table 2-3 must contain at least one of the following column information from either table 2-3 or table 2-4:

[0273] Table 2-3

[0274]

[0275] Table 2-4

[0276]

[0277] The indicated row index number corresponds to the time-frequency domain information in the resource mapping table. Here, X represents one or more of the continuously allocated frequency domain resources NBW, Tb or bit rate, Tc or chip rate, transmission bandwidth, baseband bandwidth, R2D and D2R time domain unit ratio, application scenario, or message type.

[0278] In one embodiment, the first message may provide an index of row (m+1) and column (n+1) of a frequency offset factor allocation table via a frequency offset factor indicator field or a set of code points in the field indicating index values ​​(m, n). The indexed row defines one or more of the following: frequency offset factor Rsf, frequency offset factor calculation parameter n, frequency offset factor calculation rule or type, maximum D2R frequency offset factor, and D2R application scenario or message type.

[0279] One or more sets of frequency offset factors can be defined through pre-definition, pre-configuration, or device implementation. For example, the i-th set of frequency offset factors might be {Rsf i1, Rsf i2, ..., Rsf iN}. The indexing method for each set is associated with different D2R message types, application scenarios, or set index numbers. A single row of the frequency offset factor index table must contain at least one of the following column information: for example, it could be Table 2-5, where the frequency offset factor is calculated using indicator information:

[0280] Table 2-5

[0281]

[0282] You can also directly specify the frequency offset factor or frequency offset factor index, such as the frequency offset factor information index table in Table 2-6:

[0283] Table 2-6

[0284]

[0285] In one embodiment, a device frequency offset capability reporting process may be included:

[0286] This information, indicated by one or more fields or one or more code points within a field, is used to indicate the device's frequency offset capability. It includes one or more of the following: SFO estimate, CFO estimate, and maximum transmit frequency offset. The SFO or CFO estimate can be a quantized value or an index value; the maximum transmit frequency offset can be a quantized value or an index value indicating the frequency offset size. For example, it could be the frequency offset capability corresponding to the codepoint described in Table 2-7.

[0287] Table 2-7

[0288]

[0289] Optionally, an index to row m+1 of the allocation table is also provided, indicating the frequency offset capability index value m via a frequency offset capability field or one of its code points. The indexed row defines one or more of the following: SFO estimate, CFO estimate, maximum transmission frequency offset. Each row definition in resource allocation table 2-8 must contain at least one of the following information:

[0290] Table 2-8

[0291]

[0292] In one embodiment, such as Figure 4 As shown, a communication method is provided, which is applied to Figure 1 Taking the reader 200 as an example, the explanation includes the following steps:

[0293] Step 402: Send a first message to one or more IoT terminal devices.

[0294] The first message is used to indicate the resources for multiple access of IoT terminal devices.

[0295] Specifically, the reader can indicate non-conflicting random access resources to multiple IoT terminal devices, and send a first message to one or more IoT terminal devices. By reading the first message, the reader can indicate to the multiple IoT terminal devices the multiple access resources used by the IoT terminal device during the random access process.

[0296] Step 404: Receive multiple second messages sent by multiple IoT terminal devices in a multiple address manner.

[0297] Multiple access methods include time division multiple access (TDMA) and / or frequency division multiple access (FDMA).

[0298] Specifically, after receiving the first message from the reader, each IoT terminal device, based on the instruction of the first message, sends a second message to the reader using multiple access methods. The IoT terminal devices can send the second message to the reader using time-division multiple access (TDMA), frequency-division multiple access (FDMA), etc. Alternatively, some IoT terminal devices can send the message using TDMA while others send it using FDMA. Based on this, the reader can receive multiple second messages sent by multiple IoT terminal devices using various multiple access methods.

[0299] In this embodiment, the IoT terminal device can receive a first message sent by the reader; and based on the instruction of the first message, send a second message to the reader; the second message is sent by the IoT terminal device in a multiple access mode, including time division multiple access and / or frequency division multiple access; the reader can combine the terminal capabilities of multiple devices and the actual channel status, and allocate random access resources to multiple devices by sending the first message to the devices, thereby avoiding frequency conflicts between the resources used by multiple devices, improving the effectiveness of resource allocation and improving the transmission efficiency and reliability of the system.

[0300] In one embodiment, the method further includes:

[0301] Receive D2R transmissions from IoT terminal devices, acquire timing acquisition signals from the D2R transmissions, perform one or more operations among SFO, CFO estimation, and clock calibration, and obtain one or more of the SFO estimate, CFO estimate, and clock correction results from the IoT terminal devices; allocate resources for frequency division multiple access for the IoT terminal devices, and obtain the first message.

[0302] Specifically, the reader can receive D2R transmissions from one or more IoT terminal devices. These D2R transmissions include at least timing acquisition signals. Based on these transmissions, the reader can perform one or more operations, such as SFO (Signal Frequency Offset), CFO (Card Frequency Offset), and clock calibration, to obtain one or more of the following: carrier frequency offset estimate, sampling frequency offset estimate, and clock correction result. Based on these estimates, the reader allocates resources for frequency division multiple access (FDMA) to one or more IoT terminal devices, obtaining random access resources allocated to each device, and subsequently receiving the first message corresponding to each IoT terminal device. Thus, the reader can send the first message to one or more IoT terminal devices.

[0303] In this embodiment, IoT terminal devices can report their capabilities to the reader, assisting the reader in resource allocation and further improving the efficiency of the reader in allocating resources to various IoT terminal devices, thereby enhancing the effectiveness of resource allocation.

[0304] In one embodiment, D2R transmission is capability information reported by the IoT terminal device; the capability information includes at least one of chip length, maximum frequency offset factor, maximum repetition count, device power information, SFO estimate, CFO estimate, maximum frequency shift range supported by the device, and NR band or frequency range supported by the device.

[0305] Specifically, capability information can be the capabilities of an IoT terminal device. Capability information can include a field that indicates one or more of the following: the estimated sampling frequency offset, the estimated carrier frequency offset, the maximum frequency offset range supported by the device, and the NR bands or frequency ranges supported by the device. Alternatively, capability information can include multiple fields, with one or more of these fields indicating the aforementioned information. Or, capability information can also indicate the aforementioned information through a code point in a field, or through multiple code points in a field, for example, respectively indicating one or more of the following: the estimated sampling frequency offset, the estimated carrier frequency offset, the maximum frequency offset range supported by the device, and the NR bands or frequency ranges supported by the device.

[0306] In this embodiment, the capability information can include multiple formats, further enhancing the flexibility of capability information configuration, ensuring the reliability of information transmission, and realizing the effective allocation of random access resources.

[0307] In one embodiment, the reader indicates frequency domain resources, frequency shift factor, and frequency shift factor-related parameters to multiple IoT terminal devices through a first message, so as to ensure that no frequency domain resource conflict occurs on the same time domain resources.

[0308] Specifically, the reader sends a first message to multiple IoT devices to indicate the resources used by each IoT terminal device for random access. On the same time domain resources, the frequency domain resources indicated by the reader to multiple IoT terminal devices through the first message, and or, the frequency shift factor, and or, the frequency shift factor-related parameters, do not cause frequency domain conflicts.

[0309] In this embodiment, the reader can combine the terminal capabilities of multiple devices and the actual channel status, and allocate random access resources to multiple devices by sending a first message to the devices. This avoids frequency conflicts between the resources used by multiple devices, improves the effectiveness of resource allocation, and enhances the transmission efficiency and reliability of the system.

[0310] In one embodiment, frequency domain resource conflict includes at least one of the following:

[0311] The frequency domain resources of IoT terminal devices overlap with those of other IoT terminal devices.

[0312] The frequency domain resources of D2R transmission sent by IoT terminal devices based on the instruction of the first message overlap with the frequency domain resources of D2R transmission sent by other IoT terminal devices based on the instruction of the first message.

[0313] The frequency domain resources used by IoT terminal devices to transmit D2R data can cause harmonic interference with the frequency domain resources used by other IoT terminal devices to transmit D2R data.

[0314] This embodiment specifies in detail the various situations in which frequency domain resources may conflict, thus avoiding various situations in which IoT terminal devices may conflict.

[0315] In one embodiment, the frequency domain resources of D2R transmission include the main lobe frequency band after frequency shifting by the IoT terminal device based on the frequency shift factor or frequency shift factor-related parameters.

[0316] In one embodiment, the harmonic interference is the frequency band of the third harmonic of the D2R transmission sent by the IoT terminal device based on the instruction of the first message, which overlaps with the main lobe frequency band of the D2R transmission sent by other IoT terminal devices based on the instruction of the first message.

[0317] This embodiment specifies various scenarios of harmonic interference, which can further improve the reliability of communication between the reader and the terminal device, suppress resonance risks, and further ensure communication quality.

[0318] In one embodiment, the first message is an R2D transmission, which includes one or more of timing acquisition signals, R2D transmission data, control information, and postamble; the second message is a D2R transmission, which includes one or more of timing acquisition signals, D2R transmission data, control information, midamble, and postamble.

[0319] Specifically, the reader sends a first message to the IoT terminal device, which can be an R2D transmission. Correspondingly, the R2D transmission message can carry one or more of the following information: Time-Series Acquisition Signal (TAS), R2D transmission data, control information, and a postamble. The TAS can be a continuous signal and / or a discrete signal acquired sequentially in the time dimension. The R2D transmission data can be data transmitted from the reader to the IoT terminal device. The postamble can be a specific sequence located at the end of the data frame. The D2R transmission can represent a message sent from the IoT terminal device to the reader. The D2R transmission data represents data transmitted from the IoT terminal device to the reader. The midamble represents the area between the preamble and the postamble.

[0320] In this embodiment, the content carried in the first message and the second message can include a variety of contents to ensure message diversity.

[0321] In one embodiment, the timing acquisition signal is a preamble, and the R2D transmission data is carried on the PRDCH. The preamble can be a known sequence located at the very beginning of the data frame.

[0322] In one embodiment, the timing acquisition signal at least characterizes the start of R2D and / or D2R transmission of the message to which the timing acquisition signal is located in the time domain, and the timing acquisition signal is used for clock synchronization, determining the chip duration of subsequent transmissions, SFO estimation, CFO estimation, channel estimation, interference estimation and one or more of these.

[0323] Specifically, the timing acquisition signal in the first message can characterize the start of R2D transmission of the first message in the time domain; the timing acquisition signal in the second message can characterize the start of D2R transmission of the second message in the time domain. Optionally, the timing acquisition signal can be used to perform one or more of sampling frequency offset (SFO) estimation, carrier frequency offset (CFO) estimation, channel estimation, and interference estimation to obtain one or more of the following: acquisition frequency offset estimate, carrier frequency offset estimate, channel estimation result, and interference estimation result.

[0324] In this embodiment, by carrying timing acquisition signals in both the first and second messages, the start of the time domain can be accurately characterized, ensuring the reliability of data transmission.

[0325] In one embodiment, the control information includes at least one of the scheduling information for R2D transmission and the scheduling information for D2R transmission corresponding to R2D transmission. The scheduling information for D2R transmission includes at least one of the following: time domain and / or frequency domain resources, MCS-like information, chip duration, information bit duration, frequency offset factor, device-related ID, repetition, D2R preamble related indication information, and D2R midamble related indication information.

[0326] Specifically, the control information may include scheduling information for R2D transmission, or the control information may include scheduling information for D2R transmission corresponding to R2D transmission; wherein, the D2R transmission corresponding to R2D transmission may be a signal sent from the device to the reader after the reader sends data to the device.

[0327] Optionally, the scheduling information for R2D transmission may include at least one of the following: time-domain and / or frequency-domain resources, class modulation and coding scheme (MCS) information, chip duration, information bit duration, frequency offset factor, device-related ID, repetition, R2D preamble related indication information, and R2D midamble related indication information.

[0328] In this embodiment, scheduling information is described in multiple forms to accurately indicate resource allocation, further avoiding the risk of resource conflicts and enabling frequency division multiple access for multiple IoT terminal devices.

[0329] In one embodiment, the communication method further includes:

[0330] In the first message, the implementation mode of frequency division multiple access of the IoT terminal device is indicated based on control information in different formats and / or the content of control information; and / or, in the first message, the device type is indicated based on control information in different formats and / or the content of control information, indicating the implementation mode of frequency division multiple access of the IoT terminal device.

[0331] The predefined or preconfigured method can be a method that the reader / writer predefines or configures for the IoT terminal device; the type of IoT terminal device can be a device type, such as any one of device 1, device2a, and device 2b; the multiple access mode indication corresponding to the IoT terminal device can be the multiple access mode that the IoT terminal device determines.

[0332] Control information in different formats can be represented by one or more fields or one or more code points in the fields indicating the control information format, or it can be control information scrambled with different information, or it can be control information with CRC appended with different lengths and / or contents; the content of control information in different formats can be the content of control information represented by one or more fields or one or more code points in the fields; after receiving the first message sent by the reader, the terminal device can determine the corresponding frequency division multiple access implementation method based on the control information carried in the first message and / or the content of the control information.

[0333] Optionally, different formats can include one or more fields, one or more code points in the fields, etc. The control information and / or the content of the control information can indicate the device type of the terminal device. The terminal device can determine the device type based on the device type indicated by the control information and / or the content of the control information in different formats, and determine the frequency division multiple access implementation method corresponding to the device type. The specific implementation method of frequency division multiple access based on the device type will be described in detail in subsequent embodiments, and will not be repeated here.

[0334] In this embodiment, the reader can configure the frequency division multiple access implementation for the tag in a variety of ways, which is more flexible, applicable to a variety of different scenarios, and can achieve more comprehensive business support capabilities.

[0335] The following describes in detail the communication process between a passive IoT device and a Reader using an embodiment. The process can be carried by physical layer control information and / or MAC CE and / or higher layer (RRC) signaling, through control information indicating relevant information of R2D and D2R transmissions.

[0336] In one embodiment, during R2D transmission, the first message, along with / the control information within the first message, indicates the specific process of time-domain resource allocation for D2R transmission:

[0337] Optionally, the first time unit offset, first time unit length, second time unit start point, second time unit length, D2R mapping type, D2R repetition type and number can be indicated by one or more fields or one or more code points in a field, including the following cases:

[0338] Case 1: First time unit offset K2, start and length indicator SLIV, D2R mapping type, D2R repeat type and number of times.

[0339] Specifically, the starting position of the time resource can be calculated as Tstart = Tref + K2 * T1 + S * T2, and the length of the time resource is Tlength = L * T2; the relationship between SLIV and the starting point S and length L of the second time unit is mapped to Table 3-1 through the SLIV index:

[0340] Table 3-1

[0341]

[0342] Case 2: First time unit offset K2, second time unit start position S and allocation length L, D2R mapping type, D2R repetition type and number; specifically, the start position of the time resource can be calculated as Tstart=Tref+K2*T1+S*T2, and the time resource length is Tlength=L*T2.

[0343] Case 3: First time unit offset K2, second time unit start position S and allocation length L, D2R mapping type, D2R repetition type and number; specifically, the time resource start position can be calculated as Tstart=Tref+K2*T1+S*T2, and the time resource length is Tlength=L*T1.

[0344] Case 4: First time unit offset K2, first time unit allocation length L, D2R mapping type, D2R repetition type and number; specifically, the start position of the time resource can be calculated as Tstart=Tref+K2*T1, and the length of the time resource is Tlength=L*T1.

[0345] Case 5: Second time unit start position S, second time unit allocation length L, D2R mapping type, D2R repetition type and number; specifically, the time resource start position can be calculated as Tstart=Tref+S*T2, and the time resource length is Tlength=L*T2.

[0346] Where Tref is a reference time point used to determine the location of time-domain resources, which can be the end of the transmission of the first message or the end of the last second message; T1 is the time length of a single first time unit; and T2 is the time length of a single second time unit.

[0347] Optionally, the first message may indicate the D2R time resource allocation field value m via a time-domain resource allocation field, providing an index to the (m+1)th row of the resource allocation table. The indexed row defines one or more of the following: time unit offset K2, start and length indicators SLIV, start time unit S and allocation length L, and D2R mapping type. The determination of the resource allocation table involves one or more of the following:

[0348] Scenario 1: The resource allocation table can be selected in conjunction with the CP length. For example, it can include the default PDRCH time-domain resource allocation table 3-2 for normal CPs and the default D2R transmission PDRCH time-domain resource allocation table 3-3 for extended CPs.

[0349] Table 3-2

[0350]

[0351] Table 3-3

[0352]

[0353] Scenario 2: The resource allocation table can be selected in conjunction with the M value of R2D. For example, it can include the default D2R transmission PDRCH time-domain resource allocation table 3-4 and the definition table of the j value 3-5:

[0354] Table 3-4

[0355]

[0356] Table 3-5

[0357]

[0358] Case 3: The resource allocation table only contains the offset K2 of the first time unit and the length L of the first time unit, as shown in Table 3-6:

[0359] Table 3-6

[0360]

[0361] Case 4: The resource allocation table only contains the offset S of the second time unit and the length L of the second time unit.

[0362] Case 5: The resource allocation table contains only the offset K for the first time unit and the start length indicator symbol SLIV.

[0363] Case 6: One or more rows in the resource allocation table contain multiple time resource indication information, such as those shown in Tables 3-7 and 3-8:

[0364] Table 3-7

[0365]

[0366] Table 3-8

[0367]

[0368] The harmonic calculation process involved in this embodiment is described with reference to one example:

[0369] The baseband chip rate of the first device is B1, the SFO size is O1, and the frequency shift factor is R1. The baseband chip rate of the second device is B2, the SFO size is O2, and the frequency shift factor is R2. The frequency band is defined as the range from the first frequency to the second frequency, and is calculated as follows:

[0370] The main lobe frequency band range of the first and second devices can be calculated using the following formula:

[0371] (Ri*Bi)*(1-Oi) - Bi / 2*(1+Oi) ~ (Ri*Bi)*(1+Oi) + (1+Oi)*Bi / 2;

[0372] The frequency band range of the third harmonic can be calculated using the following formula:

[0373] 3*(Ri*Bi)*(1-Oi) - Bi / 2*(1+Oi) ~ 3*(Ri*Bi)*(1+Oi)+ (1+Oi)*Bi / 2;

[0374] Where i=1 represents the first device and i=2 represents the second device; the condition for frequency domain resource conflict between the first device and the second device is that any of the following conditions are met:

[0375] Case 1: The first frequency of the main lobe of the second device < the second frequency of the third harmonic of the first device < the second frequency of the main lobe of the second device;

[0376] Case 2: The first frequency of the main lobe of the second device is less than the first frequency of the third harmonic of the first device, which is less than the second frequency of the main lobe of the second device.

[0377] Case 3: The first frequency of the main lobe of the first device < the second frequency of the third harmonic of the second device < the second frequency of the main lobe of the first device;

[0378] Case 4: The first frequency of the main lobe of the first device is less than the first frequency of the third harmonic of the second device, which is less than the second frequency of the main lobe of the first device.

[0379] Optionally, for D2R transmissions between multiple devices with the same baseband chip rate, such as MSG1 of a first and second device in random access, the above conditions are simplified to:

[0380] 3R1(1-O1) / (1+O1)-1 <R2<3R1(1+O1) / (1-O1)-1;

[0381] 3R1 <R2< (3R1+1)(1+O1) / (1-O1);

[0382] Among them, R1 and R2 can be interchanged.

[0383] In one embodiment, since the time-domain estimation occurs within two CP intervals of the OFDM symbol period, the CFO will cause a phase difference between the first and last sampling points within the OFDM symbol period. After symbol synchronization, assuming the channel effect is negligible, the terminal device can multiply the signals from the first and last sampling points of the period and obtain the CFO estimate based on the phase angle. Correspondingly, the SFO estimation correction method of the device and the reader can be selected from any of the following methods based on the device's capabilities:

[0384] Method 1: Correction before FFT. If the receiver uses VCO, adjust the ADC sampling clock according to the TAS signal; otherwise, use interpolation to adjust the sampled data by adding or subtracting SFO in units of sampling clock. The clock is generated by a fixed crystal oscillator.

[0385] Method 2 involves correcting after FFT by using pilot information to estimate the phase rotation caused by the sampling frequency offset, and then compensating for each sample value.

[0386] The following describes the process of the above communication method in detail with reference to a specific example of random access triggered by a paging signal, including a reader / writer and a device, which can be an environmental IoT terminal device, such as... Figure 5 As shown:

[0387] Step 1: The reader transmits a paging signal to the device, i.e., R2D transmission of the paging signal; specifically, the reader carries the indication information of the random access process in the paging or trigger, and configures the corresponding time and frequency resource pool and control information for this inventory process.

[0388] Step 2: The device receives and decodes the R2D frame structure, and estimates the SFO, CFO and frequency shift range. Specifically, after receiving the Paging signal, the device decodes it to obtain the TAS signal, estimates the SFO and CFO, and estimates the maximum frequency offset range to obtain the sampled frequency offset estimate, the carrier frequency offset estimate, and the maximum frequency offset range.

[0389] Step 3: The device transmits the MSG1 signal via D2R, that is, the device reports its own multiple access capability information; specifically, the device randomly selects a resource access in the random access resource pool and sends an MSG1 message to report its own multiple access capability information, including SFO estimate, CFO estimate, and maximum frequency offset.

[0390] Step 4: The reader receives and decodes the D2R frame structure, and performs SFO, CFO and time calibration; specifically, the reader receives MSG1, decodes it to obtain the TAS signal, and performs SFO, CFO estimation and time calibration.

[0391] Step 5: The reader allocates resources for the device to access frequency division multiple access. Specifically, the reader combines the frequency offset capability reported by the device, chip length, frequency offset factor, repetition count, and the reader's CFO and SFO estimates, and uses a resource allocation mechanism to reduce resource conflicts to allocate frequencies for each device to access frequency division multiple access.

[0392] Step 6: The reader transmits the MSG2 signal via R2D, which directly or indirectly indicates the frequency offset or subband configuration; specifically, the reader sends the MSG2 signal to the device to provide resources for frequency division multiple access by directly or indirectly indicating the frequency offset factor or subband configuration.

[0393] Step 7: The device receives and decodes the R2D frame structure to obtain the access resources indicated by the control information; specifically, after receiving the MSG2 signal, the device decodes the resources indicated by the control information.

[0394] Step 8: The device repeats the codeword with the corresponding frequency offset according to the indication information of the access resource; specifically, the device obtains the frequency offset factor Rsf according to the indication information, and repeats each Manchester codeword Rsf times within the time length of the corresponding information bit by frequency conversion method.

[0395] Step 9: The device transmits MSG3 on the indicated time-frequency resource. That is, the device transmits the MSG3 signal via D2R and transmits data on the indicated time-domain resource.

[0396] The communication method provided in this embodiment is a method for frequency division multiple access (FDMA) transmission of D2R signals between a passive IoT device and a Reader. Specifically, the device reports its own FDMA capability, estimates the sampling frequency offset and carrier frequency offset by decoding the received R2D signal, and calculates the frequency shift range on the device side. The Reader designs a frequency resource allocation method based on the frequency shift capability of the FDMA reported by the device. The device implements a small frequency shift FDMA method for the backscattered waveform based on scheduling control information, including two implementation methods: frequency conversion method and frequency mixing method.

[0397] Specifically, the device reports its own frequency division multiple access (FDMA) capability to assist the Reader in allocating random access resources and improve the effectiveness of resource allocation; the Reader, in combination with the device's capabilities and the actual channel conditions, allocates random access resources to multiple devices, reducing frequency conflicts between devices and improving transmission reliability; the device performs small frequency shifts based on scheduling information to solve the frequency shifting problem of passive IoT based on backscatter waveforms, enabling multiple passive IoT devices to access the network via FDMA and improving transmission efficiency.

[0398] It should be understood that, although Figure 1-5The steps in the flowchart are shown sequentially as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order in which these steps are executed, and they can be performed in other orders. Figure 1-5 At least some of the steps in the process may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but may be executed at different times. The execution order of these steps or stages is not necessarily sequential, but may be executed in turn or alternately with other steps or at least some of the steps or stages in other steps.

[0399] In one embodiment, such as Figure 6 As shown, a communication device 600 is provided for use in Internet of Things (IoT) terminal devices, comprising:

[0400] The first receiving module 602 is used to receive the first message sent by the reader / writer;

[0401] The first sending module 604 is used to send a second message to the reader based on the instruction of the first message; the second message is sent by the IoT terminal device in a multiple access mode, including time division multiple access and / or frequency division multiple access.

[0402] In one embodiment, the first message is an R2D transmission, which includes one or more of a timing acquisition signal (TAS), R2D transmission data, control information, and a postamble; the second message is a D2R transmission, which includes one or more of a timing acquisition signal, D2R transmission data, control information, a midamble, and a postamble.

[0403] In one embodiment, the timing acquisition signal is a preamble, and the R2D transmission data is carried on the PRDCH.

[0404] In one embodiment, the timing acquisition signal at least characterizes the start of R2D and / or D2R transmission of the message to which the timing acquisition signal is located in the time domain, and the timing acquisition signal is used for clock synchronization, determining the chip duration of subsequent transmissions, sampling frequency offset (SFO) estimation, carrier frequency offset (CFO) estimation, channel estimation, and interference estimation, or one or more of these.

[0405] In one embodiment, the control information includes at least one of the scheduling information for the R2D transmission and the scheduling information for the D2R transmission corresponding to the R2D transmission. The scheduling information for the D2R transmission includes at least one of the following: time-domain and / or frequency-domain resources, class modulation and coding scheme (MCS) information, chip duration, information bit duration, frequency offset factor, device-related ID, repetition, D2R preamble related indication information, and D2R midamble related indication information.

[0406] In one embodiment, the device further includes:

[0407] The first calibration module is used to perform clock calibration on the R2D transmission to obtain one or more of the following: the estimated sampling frequency offset, the estimated carrier frequency offset, the maximum frequency shift range supported by the device, and the NR band or frequency range supported by the device.

[0408] In one embodiment, the device further includes:

[0409] The third transmitting module is used in D2R transmission to send the capability information of the IoT terminal device to the reader. The capability information includes device power information, device type, estimated sampling frequency offset, estimated carrier frequency offset, maximum frequency offset range supported by the device, and one or more of the NR bands or frequency ranges supported by the device.

[0410] In one embodiment, the device further includes:

[0411] The first acquisition module acquires the frequency division multiple access resource indicated by the reader based on the scheduling information of the D2R transmission corresponding to the R2D transmission contained in the control information in the R2D transmission, and sends D2R data / D2R transmission to the reader on the frequency division multiple access resource indicated by the reader.

[0412] In one embodiment, the IoT terminal device determines the implementation method of frequency division multiple access in at least one of the following ways:

[0413] The implementation method of frequency division multiple access is determined in a predefined or pre-configured manner, and / or based on the type of the IoT terminal device, and / or the multiple access mode indication corresponding to the IoT terminal device;

[0414] Based on control information in different formats and / or the content of control information, determine the frequency division multiple access implementation method of the IoT terminal device;

[0415] Based on the device type indicated by the different formats of control information and / or the content of the control information, the frequency division multiple access implementation mode of the IoT terminal device is determined.

[0416] In one embodiment, the device further includes:

[0417] The first processing module implements frequency division multiple access by a small frequency offset of the carrier when the D2R transmission of the IoT terminal device is achieved by backscattering on an externally provided carrier; or, when the D2R transmission of the IoT terminal device is generated internally by the device, it implements frequency division multiple access by a small frequency offset of the carrier and / or a spectrum shifting mechanism for the generated waveform.

[0418] In one embodiment, the device further includes:

[0419] The second processing module implements frequency division multiple access (FDMA) by a small frequency offset of the backscattered carrier when the device type of the IoT terminal device is device 1 and / or device 2a; or, when the device type of the IoT terminal device is device 2b, it implements FDMA by a small frequency offset of the carrier and / or a spectrum shifting mechanism for generating waveforms.

[0420] In one embodiment, the first message is used to indicate time-domain resource allocation and / or frequency-domain resource allocation during D2R transmission.

[0421] In one embodiment, the data in the first message used to indicate time-domain resource allocation and / or frequency-domain resource allocation includes at least control information, which is one or more of physical layer control information, MAC CE, and higher-layer signaling.

[0422] In one embodiment, the first message includes at least one of the following: a field, multiple fields, a code point in a field, multiple code points in a field, a string, and a corresponding bit mapping table, indicating one or more of the following: frequency domain resource location, frequency domain resource offset, and length of continuously allocated frequency domain resources.

[0423] In one embodiment, when the IoT terminal device determines the frequency domain resource location based on the first message, the content of the first message includes at least any of the following:

[0424] The resource unit number N1 and / or the size Ru of a single frequency domain resource unit;

[0425] The starting resource unit number Nstart, the frequency domain offset Nsf from the starting frequency, and / or the size Ru of a single frequency domain resource unit;

[0426] The frequency domain offset Nsf from the starting frequency, the size Ru of a single frequency domain resource unit, and the starting frequency Fstart, which at least supports the frequency of the carrier CW;

[0427] Frequency offset factor Rsf, or related information about the frequency offset factor;

[0428] Information bit duration Tb or information bit rate 1 / Tb;

[0429] The length indication information of the amble transmitted by D2R must contain at least one of the preamble, midamble, and postamble.

[0430] Carrier frequency Fcw;

[0431] Chip duration Tc or chip rate 1 / Tc;

[0432] Transmission bandwidth;

[0433] Baseband bandwidth (BW).

[0434] In one embodiment, the frequency offset factor related indication information includes one or more of the following: D2R frequency offset factor calculation parameter n, frequency offset factor calculation rule, frequency offset factor calculation type, and maximum value of D2R frequency offset factor.

[0435] In one embodiment, when the IoT terminal device determines the length of continuous frequency domain resources based on the first message, the content of the first message includes at least any of the following:

[0436] The number of continuous frequency domain units, NBW;

[0437] Indicates the duration Tb of the information bit or the information bit rate 1 / Tb;

[0438] The length indication information of the amble transmitted by D2R includes at least one of preamble, midamble, and postamble.

[0439] Indicates the chip duration Tc or chip rate 1 / Tc;

[0440] Indicates the transmission bandwidth and / or baseband bandwidth BW';

[0441] Indicates the block size TBS and / or the duration T of the D2R message.

[0442] In one embodiment, the first message indicates one or more of the following through at least one of the following methods: a field, multiple fields, a code point in a field, multiple code points in a field, an indicator, multiple indicators, a string, and a corresponding bit mapping table: D2R frequency offset factor Rsf, D2R frequency offset factor calculation parameter n, frequency offset factor calculation rule, frequency offset factor calculation type, and maximum value of D2R frequency offset factor.

[0443] In one embodiment, the first message indicates the row index value m of the frequency offset factor allocation table via a frequency offset factor indicator field or one or more code points in the field.

[0444] In one embodiment, the definition of each row in the frequency offset factor allocation table includes one or more of the following: frequency offset factor Rsf, frequency offset factor calculation parameter n, frequency offset factor calculation rule, frequency offset factor calculation type, maximum value of D2R frequency offset factor, D2R application scenario or message type, and parameters, wherein the parameters include one or more of the continuously allocated frequency domain resources NBW, Tb or information bit rate, Tc or chip rate, transmission bandwidth, baseband bandwidth, and R2D and D2R time domain unit ratios.

[0445] In one embodiment, the capability information indicates one or more of the following: the sampling frequency offset estimate, the carrier frequency offset estimate, the maximum frequency offset range supported by the device, and the NR band or frequency range supported by the device, through one or more fields, one or more code points in one field, one or more code points in one field, or a string and a corresponding bit mapping table.

[0446] In one embodiment, the sampled frequency offset estimate indicates a quantized value or an index value, the carrier frequency offset estimate indicates a quantized value or an index value, and the maximum frequency offset range supported by the device indicates a quantized value or an index value for the frequency offset magnitude.

[0447] In one embodiment, the capability information indicates the index value m of the IoT terminal device in the capability information index table through one field, or multiple fields, or one code point in one field, or multiple code points in one field, or a string and a corresponding bit mapping table. The row definition content of the capability information index table includes one or more of the following: SFO estimate, CFO estimate, maximum frequency offset range supported by the device, and NR bands or frequency ranges supported by the device.

[0448] In one embodiment, the device further includes:

[0449] The third receiving module receives R2D transmissions from the reader / writer. The R2D transmission is one or more of the following: paging signal, subsequent paging signal, R2D transmission triggering random access, and R2D transmission triggering terminal capability reporting. The R2D transmission includes a terminal capability query request.

[0450] The fourth receiving module receives the R2D transmission, performs clock synchronization based on the TAS signal in the R2D transmission, and obtains the device's power information, SFO estimate, CFO estimate, and one or more of the maximum frequency shift range supported by the device.

[0451] The fourth sending module sends D2R transmissions to the reader / writer, wherein the D2R transmissions are capability information reported by the IoT terminal device.

[0452] In one embodiment, such as Figure 7 As shown, a communication device 700 is provided for use in a reader / writer, comprising:

[0453] The second sending module 702 is used to send a first message to one or more IoT terminal devices, the first message being used to indicate the resources for multiple access of the IoT terminal devices;

[0454] The second receiving module 704 is used to receive multiple second messages sent by multiple IoT terminal devices in a multiple access mode, including time division multiple access and / or frequency division multiple access.

[0455] In one embodiment, the device further includes:

[0456] The fifth receiving module is used to receive the D2R transmission sent by the IoT terminal device, obtain timing acquisition signals from the D2R transmission, perform one or more operations of SFO, CFO estimation and clock calibration, and obtain one or more of the SFO estimate, CFO estimate and clock correction result of the IoT terminal device.

[0457] The first allocation module is used to allocate resources for frequency division multiple access for the IoT terminal device and obtain the first message.

[0458] In one embodiment, the D2R transmission is capability information reported by the IoT terminal device; the capability information includes at least one of chip length, maximum frequency offset factor, maximum repetition count, device power information, SFO estimate, CFO estimate, maximum frequency shift range supported by the device, and NR band or frequency range supported by the device.

[0459] In one embodiment, the reader / writer uses the first message to indicate frequency domain resources to multiple IoT terminal devices, and / or, frequency shift factor, and / or, frequency shift factor-related parameters, to ensure that no frequency domain resource conflict occurs on the same time domain resources.

[0460] In one embodiment, the frequency domain resource conflict includes at least one of the following:

[0461] The frequency domain resources of the IoT terminal device overlap with the frequency domain resources of other IoT terminal devices.

[0462] The frequency domain resources of the D2R transmission sent by the IoT terminal device based on the instruction of the first message overlap with the frequency domain resources of the D2R transmission sent by other IoT terminal devices based on the instruction of the first message.

[0463] The frequency domain resources used by the IoT terminal device to transmit D2R transmissions generate harmonic interference with the frequency domain resources used by other IoT terminal devices to transmit D2R transmissions.

[0464] In one embodiment, the frequency domain resources of the D2R transmission include the main lobe frequency band after frequency shifting by the IoT terminal device based on the frequency shift factor or frequency shift factor-related parameters.

[0465] In one embodiment, the harmonic interference is the frequency band of the third harmonic of the D2R transmission sent by the IoT terminal device based on the instruction of the first message, which overlaps with the main lobe frequency band of the D2R transmission sent by other IoT terminal devices based on the instruction of the first message.

[0466] In one embodiment, the first message is an R2D transmission, which includes one or more of timing acquisition signals, R2D transmission data, control information, and postamble; the second message is a D2R transmission, which includes one or more of timing acquisition signals, D2R transmission data, control information, midamble, and postamble.

[0467] In one embodiment, the timing acquisition signal is a preamble, and the R2D transmission data is carried on the PRDCH.

[0468] In one embodiment, the timing acquisition signal at least characterizes the start of R2D and / or D2R transmission of the message to which the timing acquisition signal is located in the time domain, and the timing acquisition signal is used for clock synchronization, determining the chip duration of subsequent transmissions, SFO estimation, CFO estimation, channel estimation, and interference estimation, or one or more of these.

[0469] In one embodiment, the control information includes at least one of the scheduling information for the R2D transmission and the scheduling information for the D2R transmission corresponding to the R2D transmission. The scheduling information for the D2R transmission includes at least one of the following: time-domain and / or frequency-domain resources, MCS-like information, chip duration, information bit duration, frequency offset factor, device-related ID, repetition, D2R preamble related indication information, and D2R midamble related indication information.

[0470] In one embodiment, the device further includes:

[0471] The third processing module is used to indicate the frequency division multiple access implementation mode of the IoT terminal device based on control information of different formats and / or the content of control information in the first message; and / or, based on the device type indicated in the first message, to indicate the frequency division multiple access implementation mode of the IoT terminal device.

[0472] Specific limitations regarding the communication device can be found in the limitations regarding the communication method above, and will not be repeated here. Each module in the aforementioned communication device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in hardware or independently of the processor in the computer device, or stored in software in the memory of the computer device, so that the processor can call and execute the operations corresponding to each module.

[0473] In one embodiment, a communication device is provided, see [link to previous document]. Figure 8 . Figure 8 This is a schematic diagram of the structure of the terminal device provided in an embodiment of the present invention. Figure 8 The terminal device 800 shown includes at least one processor 801, a memory 802, at least one network interface 804, and a user interface 803. The various components in the terminal device 800 are coupled together via a bus system 805. It is understood that the bus system 805 is used to implement communication between these components. In addition to a data bus, the bus system 805 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in… Figure 8 Various buses are labeled as bus system 805. Additionally, this embodiment of the invention includes a transceiver 806, which may consist of multiple elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium.

[0474] The user interface 803 may include a display, keyboard, or clicking device (e.g., mouse, trackball, touchpad, or touchscreen).

[0475] It is understood that the memory 802 in the embodiments of the present invention can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 802 of the systems and methods described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.

[0476] In some implementations, memory 802 stores elements such as executable modules or data structures, or subsets thereof, or extended sets thereof: operating system 8021 and application programs 8022.

[0477] The operating system 8021 includes various system programs, such as the framework layer, core library layer, and driver layer, used to implement various basic business functions and handle hardware-based tasks. The application program 8022 includes various applications, such as a media player and a browser, used to implement various application functions. The program implementing the method of this embodiment can be included in the application program 8022.

[0478] In this embodiment of the invention, by calling the program or instructions stored in the memory 802, specifically the program or instructions stored in the application program 8022, the transmitter is used to receive a first message sent by the reader / writer; the receiver is used to send a second message to the reader / writer based on the indication of the first message; the second message is sent by the IoT terminal device in a multiple access mode, including time division multiple access and / or frequency division multiple access.

[0479] The methods disclosed in the above embodiments of the present invention, in part or in all of them, can also be applied to processor 801, implemented by processor 801, or implemented by processor 801 in conjunction with other components (e.g., transceivers). Processor 801 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above methods can be completed by the integrated logic circuit of the hardware in processor 801 or by instructions in the form of software. The processor 801 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present invention can be directly manifested as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory 802, and processor 801 reads the information in memory 802 and, in conjunction with its hardware, completes the steps of the above method.

[0480] It is understood that the embodiments described in this invention can be implemented using hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in this application, or combinations thereof.

[0481] For software implementation, the technology described in the embodiments of the present invention can be implemented by modules (e.g., procedures, functions, etc.) that perform the functions described in the embodiments of the present invention. The software code can be stored in memory and executed by processor 801. The memory can be implemented in processor 801 or external to processor 801.

[0482] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps in the embodiments of this application.

[0483] This application also provides a computer program product containing instructions that, when run on a computer, cause the computer to execute the steps in this application.

[0484] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0485] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0486] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A communication method, characterized in that, The method, applied to Internet of Things (IoT) terminal devices, includes: Receive the first message sent by the reader / writer; Based on the instruction of the first message, a second message is sent to the reader / writer; the second message is sent by the IoT terminal device in a multiple access mode, the multiple access mode including time division multiple access and / or frequency division multiple access.

2. The method according to claim 1, characterized in that, The first message is an R2D transmission, which includes one or more of the following: timing acquisition signal (TAS), R2D transmission data, control information, and postamble. The second message is a D2R transmission, which includes one or more of the following: timing acquisition signal, D2R transmission data, control information, midamble, and postamble.

3. The method according to claim 2, characterized in that, The timing acquisition signal is a preamble, and the R2D transmission data is carried on the PRDCH.

4. The method according to claim 2, characterized in that, The control information includes at least one of the scheduling information for the R2D transmission and the scheduling information for the D2R transmission corresponding to the R2D transmission. The scheduling information for the D2R transmission includes at least one of the following: time-domain and / or frequency-domain resources, class modulation and coding scheme (MCS) information, chip duration, information bit duration, frequency offset factor, device-related ID, repetition, D2R preamble related indication information, and D2R midamble related indication information.

5. The method according to claim 2, characterized in that, The method further includes: Clock calibration is performed on the R2D transmission to obtain one or more of the following: the estimated sampling frequency offset, the estimated carrier frequency offset, the maximum frequency shift range supported by the device, and the NR band or frequency range supported by the device.

6. The method according to claim 2, characterized in that, The method further includes: In D2R transmission, the capability information of the IoT terminal device is sent to the reader / writer. The capability information includes device power information, device type, estimated sampling frequency offset, estimated carrier frequency offset, maximum frequency offset range supported by the device, and one or more of the NR bands or frequency ranges supported by the device.

7. The method according to claim 2, characterized in that, The method further includes: Based on the scheduling information of the D2R transmission corresponding to the R2D transmission contained in the control information of the R2D transmission, the access resource of frequency division multiple access indicated by the reader is obtained, and D2R data / D2R transmission is sent to the reader on the access resource of frequency division multiple access indicated by the reader.

8. The method according to claim 1, characterized in that, The IoT terminal device determines the implementation method of frequency division multiple access, including at least one of the following: The implementation method of frequency division multiple access is determined in a predefined or pre-configured manner, and / or based on the type of the IoT terminal device, and / or the multiple access mode indication corresponding to the IoT terminal device; Based on control information in different formats and / or the content of control information, determine the frequency division multiple access implementation method of the IoT terminal device; Based on the device type indicated by the different formats of control information and / or the content of the control information, the frequency division multiple access implementation mode of the IoT terminal device is determined.

9. The method according to claim 8, characterized in that, The method further includes: When the D2R transmission of the IoT terminal device is achieved by backscattering on an externally provided carrier, frequency division multiple access is achieved through a small frequency offset of the carrier; or... When the D2R transmission of the IoT terminal device is generated internally by the device, frequency division multiple access is achieved through a small frequency offset of the carrier and / or a spectrum shifting mechanism for the generated waveform.

10. The method according to claim 8, characterized in that, The method further includes: When the IoT terminal device is device 1 and / or device 2a, frequency division multiple access is achieved through a small frequency offset of the backscattered carrier; or, When the device type of the IoT terminal device is device2b, frequency division multiple access is achieved through a small frequency offset of the carrier and / or a spectrum shifting mechanism for generating waveforms.

11. The method according to claim 2, characterized in that, The first message is used to indicate the time-domain resource allocation and / or frequency-domain resource allocation during D2R transmission.

12. The method according to claim 2, characterized in that, The data in the first message used to indicate time-domain resource allocation and / or frequency-domain resource allocation includes at least control information, which is one or more of physical layer control information, MAC CE, and higher-layer signaling.

13. The method according to claim 11, characterized in that, The first message includes at least one of the following methods: a field, multiple fields, a code point in a field, multiple code points in a field, a string, and a corresponding bit mapping table, indicating one or more of the following: frequency domain resource location, frequency domain resource offset, and length of continuously allocated frequency domain resources.

14. The method according to claim 13, characterized in that, When the IoT terminal device determines the frequency domain resource location based on the first message, the content of the first message includes at least any of the following: The resource unit number N1 and / or the size Ru of a single frequency domain resource unit; The starting resource unit number Nstart, the frequency domain offset Nsf from the starting frequency, and / or the size Ru of a single frequency domain resource unit; The frequency domain offset Nsf from the starting frequency, the size Ru of a single frequency domain resource unit, and the starting frequency Fstart, which at least supports the frequency of the carrier CW; Frequency offset factor Rsf, or related information about the frequency offset factor; Information bit duration Tb or information bit rate 1 / Tb; The length indication information of the amble transmitted by D2R must contain at least one of the preamble, midamble, and postamble. Carrier frequency Fcw; Chip duration Tc or chip rate 1 / Tc; Transmission bandwidth and / or baseband bandwidth rate (BW).

15. The method according to claim 14, characterized in that, The frequency offset factor related indication information includes one or more of the following: D2R frequency offset factor calculation parameter n, frequency offset factor calculation rule, frequency offset factor calculation type, and maximum value of D2R frequency offset factor.

16. The method according to claim 13, characterized in that, When the IoT terminal device determines the length of continuous frequency domain resources based on the first message, the content of the first message includes at least any one of the following: The number of continuous frequency domain units, NBW; Indicates the duration Tb of the information bit or the information bit rate 1 / Tb; The length indication information of the amble transmitted by D2R includes at least one of preamble, midamble, and postamble. Indicates the chip duration Tc or chip rate 1 / Tc; Indicates the transmission bandwidth and / or baseband bandwidth BW'; Indicates the block size TBS and / or the duration T of the D2R message.

17. The method according to claim 11, characterized in that, The first message indicates one or more of the following through at least one of the following methods: a field, multiple fields, a code point in a field, multiple code points in a field, an indicator, multiple indicators, a string, and a corresponding bit mapping table: D2R frequency offset factor Rsf, D2R frequency offset factor calculation parameter n, frequency offset factor calculation rule, frequency offset factor calculation type, and maximum value of D2R frequency offset factor.

18. The method according to claim 11, characterized in that, The first message indicates the row index value m of the frequency offset factor allocation table through a frequency offset factor indicator field or one or more code points in the field.

19. The method according to claim 18, characterized in that, Each row in the frequency offset factor allocation table is defined to include one or more of the following: frequency offset factor Rsf, frequency offset factor calculation parameter n, frequency offset factor calculation rule, frequency offset factor calculation type, maximum value of D2R frequency offset factor, D2R application scenario or message type, and parameters, including one or more of the continuously allocated frequency domain resources NBW, Tb or information bit rate, Tc or chip rate, transmission bandwidth, baseband bandwidth, and the ratio of R2D and D2R time domain units.

20. The method according to claim 6, characterized in that, The capability information indicates one or more of the following: the sampling frequency offset estimate, the carrier frequency offset estimate, the maximum frequency offset range supported by the device, and the NR band or frequency range supported by the device, through one or more fields, one or more fields, one code point in one field, one or more code points in one field, or a string and a corresponding bit mapping table.

21. The method according to claim 20, characterized in that, The sampling frequency offset estimate is a quantized value or an index value; the carrier frequency offset estimate is a quantized value or an index value; and the maximum frequency offset range supported by the device is a quantized value or an index value indicating the frequency offset size.

22. The method according to claim 6, characterized in that, The capability information indicates the index value m of the IoT terminal device in the capability information index table through one or more fields, one code point in one field, multiple code points in one field, or a string and a corresponding bit mapping table. The row definition content of the capability information index table includes one or more of the following: SFO estimate, CFO estimate, maximum frequency offset range supported by the device, and NR bands or frequency ranges supported by the device.

23. The method according to claim 1, characterized in that, The method further includes: The device receives R2D transmissions from a reader / writer. The R2D transmission is one or more of the following: a paging signal, a subsequent paging signal, an R2D transmission that triggers random access, and an R2D transmission that triggers terminal capability reporting. The R2D transmission includes a terminal capability query request. Receive the R2D transmission, perform clock synchronization based on the TAS signal in the R2D transmission, and obtain the device's power information, SFO estimate, CFO estimate, and one or more of the maximum frequency shift range supported by the device; Send a D2R transmission to the reader / writer, wherein the D2R transmission is the capability information reported by the IoT terminal device.

24. The method according to claim 2, characterized in that, The timing acquisition signal at least characterizes the start of R2D and / or D2R transmission of the message to which the timing acquisition signal is located in the time domain. The timing acquisition signal is used for clock synchronization, determining the chip duration of subsequent transmissions, sampling frequency offset (SFO) estimation, carrier frequency offset (CFO) estimation, channel estimation, and interference estimation, or one or more of these.

25. A communication method, characterized in that, Applied to a reader / writer, the method includes: Send a first message to one or more IoT terminal devices, the first message being used to indicate the resources for multiple access of the IoT terminal devices; Receive multiple second messages sent by multiple IoT terminal devices in a multiple access manner, wherein the multiple access manner includes time division multiple access and / or frequency division multiple access.

26. The method according to claim 25, characterized in that, The method further includes: Receive D2R transmission sent by the IoT terminal device, obtain timing acquisition signal from the D2R transmission, perform one or more of the SFO, CFO estimation and clock calibration operations, and obtain one or more of the SFO estimate, CFO estimate and clock correction result of the IoT terminal device. Resource allocation for frequency division multiple access is performed on the IoT terminal device to obtain the first message.

27. The method according to claim 26, characterized in that, The D2R transmission is the capability information reported by the IoT terminal device; the capability information includes at least one of the following: chip length, maximum frequency offset factor, maximum repetition count, device power information, SFO estimate, CFO estimate, maximum frequency shift range supported by the device, and NR band or frequency range supported by the device.

28. The method according to claim 25, characterized in that, The reader / writer uses the first message to indicate frequency domain resources to multiple IoT terminal devices, and / or frequency shift factor, and / or frequency shift factor related parameters, to ensure that no frequency domain resource conflict occurs on the same time domain resources.

29. The method according to claim 28, characterized in that, The frequency domain resource conflict includes at least one of the following situations: The frequency domain resources of the IoT terminal device overlap with the frequency domain resources of other IoT terminal devices. The frequency domain resources of the D2R transmission sent by the IoT terminal device based on the instruction of the first message overlap with the frequency domain resources of the D2R transmission sent by other IoT terminal devices based on the instruction of the first message. The frequency domain resources used by the IoT terminal device to transmit D2R transmissions generate harmonic interference with the frequency domain resources used by other IoT terminal devices to transmit D2R transmissions.

30. The method according to claim 29, characterized in that, The frequency domain resources of the D2R transmission include the main lobe frequency band after frequency shifting by the IoT terminal device based on the frequency shift factor or frequency shift factor-related parameters.

31. The method according to claim 29, characterized in that, The harmonic interference refers to the frequency band of the third harmonic of the D2R transmission sent by the IoT terminal device based on the instruction of the first message, which overlaps with the main lobe frequency band of the D2R transmission sent by other IoT terminal devices based on the instruction of the first message.

32. The method according to claim 25, characterized in that, The first message is an R2D transmission, which includes one or more of timing acquisition signals, R2D transmission data, control information, and postamble; the second message is a D2R transmission, which includes one or more of timing acquisition signals, D2R transmission data, control information, midamble, and postamble.

33. The method according to claim 32, characterized in that, The timing acquisition signal is a preamble, and the R2D transmission data is carried on the PRDCH.

34. The method according to claim 32, characterized in that, The timing acquisition signal at least characterizes the start of R2D and / or D2R transmission of the message to which the timing acquisition signal is located in the time domain. The timing acquisition signal is used for clock synchronization, determining the chip duration of subsequent transmissions, SFO estimation, CFO estimation, channel estimation, and interference estimation, or one or more of these.

35. The method according to claim 32, characterized in that, The control information includes at least one of the scheduling information for the R2D transmission and the scheduling information for the D2R transmission corresponding to the R2D transmission. The scheduling information for the D2R transmission includes at least one of the following: time-domain and / or frequency-domain resources, MCS-like information, chip duration, information bit duration, frequency offset factor, device-related ID, repetition, D2R preamble related indication information, and D2R midamble related indication information.

36. The method according to claim 25, characterized in that, The method further includes: In the first message, based on control information in different formats and / or the content of the control information, the implementation mode of the frequency division multiple access of the IoT terminal device is indicated; and / or, In the first message, based on different formats of control information and / or the content of the control information, the device type is indicated, and the frequency division multiple access implementation method of the IoT terminal device is indicated.

37. A communication device, characterized in that, The device is applied to Internet of Things (IoT) terminal devices and includes: The first receiving module is used to receive the first message sent by the reader / writer; The first sending module is configured to send a second message to the reader based on the indication of the first message; the second message is sent by the IoT terminal device in a multiple access mode, the multiple access mode including time division multiple access and / or frequency division multiple access.

38. A communication device, characterized in that, Applied to a reader / writer, the device includes: The second sending module is used to send a first message to one or more IoT terminal devices, wherein the first message is used to indicate the resources for multiple access of the IoT terminal devices; The second receiving module is used to receive multiple second messages sent by multiple IoT terminal devices in a multiple access manner, wherein the multiple access manner includes time division multiple access and / or frequency division multiple access.

39. A communication device, characterized in that, include: Transmitter and receiver; The transmitter is used to receive the first message sent by the reader / writer; The receiver is configured to send a second message to the reader / writer based on the indication of the first message; The second message is sent by the IoT terminal device in a multiple access manner, including time division multiple access and / or frequency division multiple access.

40. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 36.

41. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 36.

Images