Communication method, Internet of Things device, storage medium and program product

Abstract

The invention provides a communication method, an Internet of Things device, a storage medium and a program product. The communication method comprises the following steps: receiving time domain control information sent by network side equipment, wherein the time domain control information comprises at least one of timeline information, time domain resource information, time interval information and time sequence scheduling information; and performing D2R transmission with the network side device at the first time based on the time domain control information, the D2R transmission comprising at least one transmission of PDRCH, D2R control signal, synchronization signal and reference signal.

Description

Technical Field

[0001] This disclosure relates to the field of communications, and in particular to a communication method, an Internet of Things (IoT) device, a storage medium, and a program product. Background Technology

[0002] Ambient IoT can perform waveform modulation and transmission without relying on batteries by obtaining energy from the environment or radio frequency signals.

[0003] During the transmission process of IoT devices, their transmission timing needs to be designed to ensure sufficient basic transmission and processing latency. This prevents excessively frequent control commands from overwhelming the IoT devices or excessively frequent responses from the IoT devices from preventing the base station from performing proper demodulation, leading to information transmission errors and impacting transmission performance. Since environmental IoT is more similar to RFID (Radio Frequency Identification), the design scheme for environmental IoT will follow the design principles of RFID. Summary of the Invention

[0004] The inventors noted that, considering the low power consumption, low cost, and low complexity of IoT devices, environmental IoT systems require the design of dedicated transmission methods and formats to enable base station-side scheduling of IoT devices, allowing them to acquire transmission resources and command information to complete the transmission process. Currently, the 3GPP (3rd Generation Partnership Project) organization has not yet designed any timing or timeline.

[0005] Accordingly, this disclosure provides a communication method that can design the timeline of IoT devices during transmission.

[0006] In a first aspect of this disclosure, a communication method is provided for an Internet of Things (IoT) device, comprising: receiving time-domain control information sent by a network-side device, wherein the time-domain control information includes at least one of timeline information, time-domain resource information, time interval information, and timing scheduling information; and, based on the time-domain control information, performing IoT device-to-network-side device (D2R) transmission with the network-side device at a first time, wherein the D2R transmission includes the transmission of at least one of a physical layer transport channel (PDRCH), a D2R control signal, a synchronization signal, and a reference signal on the D2R link.

[0007] In some embodiments, the first time includes at least one of the following: the maximum time interval T from the last time granularity of the previous network-side device to the end of the R2D transmission to the IoT device to the first time granularity of the D2R transmission.R2D_max The minimum time interval T from the last time granularity of the previous R2D transmission to the first time granularity of the D2R transmission. R2D_min The time interval T from the last time granularity of the previous R2D transmission to the first time granularity of the D2R transmission. R2D The minimum time interval T from the last time granularity of the previous D2R transmission to the first time granularity of the D2R transmission. D2R_D2R_min The maximum time interval T from the last time granularity of the previous D2R transmission to the first time granularity of the D2R transmission. D2R_D2R_max The time interval T from the last time granularity of the previous D2R transmission to the first time granularity of the D2R transmission. D2R_D2R The maximum time interval T from the first time granularity of carrier CW transmission to the first time granularity of the D2R transmission. CW_D2R_max The minimum time interval T from the first time granularity of carrier CW transmission to the first time granularity of D2R transmission. CW_D2R_min The time interval T from the first time granularity of carrier CW transmission to the first time granularity of D2R transmission. CW_D2R .

[0008] In some embodiments, the first time is predefined, preconfigured, higher-level configured, or indicated by the physical layer.

[0009] In some embodiments, the maximum time interval T R2D_max Includes one or more values; in the maximum time interval T R2D_max In the case of multiple values, at least one of the following is included: configuring or indicating the multiple values ​​according to the bandwidth of D2R or R2D transmission; configuring or indicating the multiple values ​​according to the subcarrier spacing; or directly configuring or indicating the multiple values.

[0010] In some embodiments, the minimum time interval T R2D_min Includes one or more values; in the minimum time interval T R2D_min In the case of multiple values, at least one of the following is included: configuring or indicating the multiple values ​​according to the bandwidth of D2R or R2D transmission; configuring or indicating the multiple values ​​according to the subcarrier spacing; or directly configuring or indicating the multiple values.

[0011] In some embodiments, the time interval T R2D Includes one or more values; in the time interval T R2DIn the case of multiple values, at least one of the following is included: configuring or indicating the multiple values ​​according to the bandwidth of D2R or R2D transmission; configuring or indicating the multiple values ​​according to the subcarrier spacing; or directly configuring or indicating the multiple values.

[0012] In some embodiments, the minimum time interval T D2R_D2R_min Includes one or more values; in the minimum time interval T D2R_D2R_min In the case of multiple values, at least one of the following is included: configuring or indicating the multiple values ​​according to the bandwidth of D2R or R2D transmission; configuring or indicating the multiple values ​​according to the subcarrier spacing; or directly configuring or indicating the multiple values.

[0013] In some embodiments, the maximum time interval T D2R_D2R_max Includes one or more values; in the maximum time interval T D2R_D2R_max In the case of multiple values, at least one of the following is included: configuring or indicating the multiple values ​​according to the bandwidth of D2R or R2D transmission; configuring or indicating the multiple values ​​according to the subcarrier spacing; or directly configuring or indicating the multiple values.

[0014] In some embodiments, the time interval T D2R_D2R Includes one or more values; in the time interval T D2R_D2R In the case of multiple values, at least one of the following is included: configuring or indicating the multiple values ​​according to the bandwidth of D2R or R2D transmission; configuring or indicating the multiple values ​​according to the subcarrier spacing; or directly configuring or indicating the multiple values.

[0015] In some embodiments, the maximum time interval T CW_D2R_max Includes one or more values; in the maximum time interval T CW_D2R_max In the case of multiple values, at least one of the following is included: configuring or indicating the multiple values ​​according to the bandwidth of D2R or R2D transmission; configuring or indicating the multiple values ​​according to the subcarrier spacing; or directly configuring or indicating the multiple values.

[0016] In some embodiments, the minimum time interval T CW_D2R_min Includes one or more values; in the minimum time interval T CW_D2R_min In the case of multiple values, at least one of the following is included: configuring or indicating the multiple values ​​according to the bandwidth of D2R or R2D transmission; configuring or indicating the multiple values ​​according to the subcarrier spacing; or directly configuring or indicating the multiple values.

[0017] In some embodiments, the time interval T CW_D2R Includes one or more values; in the time interval TCW_D2R In the case of multiple values, at least one of the following is included: configuring or indicating the multiple values ​​according to the bandwidth of D2R or R2D transmission; configuring or indicating the multiple values ​​according to the subcarrier spacing; or directly configuring or indicating the multiple values.

[0018] In some embodiments, the higher-layer configuration or physical layer indication includes at least one of the following: higher-layer configuration or physical layer indication is performed directly by the network side; configuration is performed by the network side based on information reported by the IoT device; when the first higher-layer enable parameter is disabled, the first time is configured or indicated by the network side; when the first higher-layer enable parameter is enabled, the first time is configured or indicated by the network side based on information reported by the IoT device; when the second higher-layer enable parameter is disabled, the first time remains unchanged through network predefined or preconfigured means; when the second higher-layer enable parameter is enabled, the first time information is allowed to be modified; when the third higher-layer enable parameter is disabled, the first time is not configured; when the third higher-layer enable parameter is enabled, the first time information is allowed to be configured or indicated.

[0019] In some embodiments, direct high-level configuration or physical layer instruction from the network side includes at least one of the following: configuration based on proximity measurements from the network side; configuration based on predefined or pre-configured results from the network side; and configuration based on T data reported by the network side for previous D2R transmissions of the IoT device. R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R Configure at least one of them; configure the measurement results of other IoT devices through the network side.

[0020] In some embodiments, the direct high-layer configuration or physical layer indication by the network side further includes: configuring a time offset; obtaining a first raw time based on the network side's close-range measurement results, obtaining the first time based on the first raw time and the time offset, and configuring it; or, obtaining a second raw time based on the network side's predefined or pre-configured results, obtaining the first time based on the second raw time and the time offset, and configuring it; or, based on the T data reported by the network side for previous D2R transmissions of the IoT device... R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R TCW_D2R_max T CW_D2R_min T CW_D2R At least one of the following methods is used to obtain a third original time, and based on the third original time and the time offset, the first time is obtained and configured; or, based on the measurement results of other IoT devices by the network side, a fourth original time is obtained, and based on the fourth original time and the time offset, the first time is obtained and configured.

[0021] In some embodiments, the direct high-layer configuration or physical layer indication by the network side further includes: configuring a time coefficient; obtaining a first raw time based on the network side's close-range measurement results, obtaining the first time based on the first raw time and the time coefficient, and configuring it; or, obtaining a second raw time based on the network side's predefined or pre-configured results, obtaining the first time based on the second raw time and the time coefficient, and configuring it; or, based on the T data reported by the network side for previous D2R transmissions of the IoT device... R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R At least one of the following methods is used to obtain a third raw time, and based on the third raw time and the time coefficient, the first time is obtained and configured; or, based on the measurement results of other IoT devices by the network side, a fourth raw time is obtained, and based on the fourth raw time and the time coefficient, the first time is obtained and configured.

[0022] In some embodiments, the configuration by the network side based on the information reported by the IoT device includes at least one of the following: the IoT device based on the previous or earlier T R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R At least one of them is reported so that the network side can configure it; other IoT devices report according to T. R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2RAt least one of them is reported so that the network side can configure it; the IoT device reports its own T R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R The network side configures itself based on the reported capability information of at least one of the IoT devices; the IoT device reports its own type information so that the network side can configure itself based on the reported type information.

[0023] In some embodiments, the configuration by the network side based on the information reported by the IoT device further includes: configuring a time offset; and configuring the time offset based on the T reported by the IoT device. R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R At least one of them, to obtain a fifth original time, and based on the fifth original time and the time offset, to obtain the first time and configure it; or, based on the T reported by other IoT devices. R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R At least one of the following, a sixth original time is obtained, and based on the sixth original time and the time offset, the first time is obtained and configured; or, the T reported by the IoT device. R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R Based on the capability information of at least one of the following, a seventh original time is obtained, and based on the seventh original time and the time offset, a first time is obtained and configured; or, based on the type information reported by the IoT device, an eighth original time is obtained, and based on the eighth original time and the time offset, a first time is obtained and configured.

[0024] In some embodiments, the configuration by the network side based on the information reported by the IoT device further includes: configuring a time coefficient; and configuring the time coefficient based on the T reported by the IoT device. R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R At least one of them, to obtain a fifth original time, and based on the fifth original time and the time coefficient, to obtain the first time and configure it; or, based on T reported by other IoT devices. R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R At least one of the following, a sixth original time is obtained, and based on the sixth original time and the time coefficient, the first time is obtained and configured; or, the T reported by the IoT device. R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R Based on the capability information of at least one of the following, a seventh original time is obtained, and based on the seventh original time and the time coefficient, a first time is obtained and configured; or, based on the type information reported by the IoT device, an eighth original time is obtained, and based on the eighth original time and the time coefficient, a first time is obtained and configured.

[0025] In some embodiments, the higher-level configuration or physical layer indication method includes at least one of the following: configuration via the Media Access Control (MAC) layer or a new layer without physical layer indication; indication via the physical layer without MAC layer or new layer configuration; configuration via the MAC layer or a new layer, and indication via the physical layer.

[0026] In some embodiments, when the configuration is performed through the MAC layer or a new layer and the physical layer provides indication, it includes at least one of the following: the MAC layer configures a portion of first time parameters, and the physical layer indicates a portion of the first time parameters; the MAC layer configures enable information for the first time parameters, and the physical layer indicates the first time parameter information corresponding to the enable information based on the enable information of the first time parameters.

[0027] In some embodiments, the maximum time interval T R2D_max It includes at least one of the following: timing advance (TA) information or transmission delay information, carrier wait time information, R2D transmission processing delay information, transmission preparation time information, and modulation time information; wherein, the carrier wait time information includes at least one of R2D carrier wait time information and D2R carrier wait time information, the R2D carrier wait time information includes at least one of charging time information and carrier arrival time information, and the D2R carrier wait time information includes at least one of charging time information and carrier arrival time information.

[0028] In some embodiments, the maximum time interval T R2D_max The composition includes at least one of the following: TA information or transmission delay information; TA information or transmission delay information + R2D transmission processing delay information; TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information; TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information + carrier waiting time information; TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information + carrier waiting time information + modulation time information; TA information or transmission delay information + transmission preparation time information; TA information or transmission delay information + transmission preparation time information + carrier waiting time information; TA information or transmission delay information + transmission preparation time information + carrier waiting time information + modulation time information; TA information or transmission delay information + carrier waiting time information; TA information or transmission delay information + carrier waiting time information + modulation time information.

[0029] In some embodiments, the minimum time interval T R2D_min It includes at least one of the following: TA information or transmission delay information, carrier wait time information, R2D transmission processing delay information, transmission preparation time information, D2R carrier wait time information, and modulation time information; wherein, the carrier wait time information includes at least one of R2D carrier wait time information and D2R carrier wait time information, the R2D carrier wait time information includes at least one of charging time information and carrier arrival time information, and the D2R carrier wait time information includes at least one of charging time information and carrier arrival time information.

[0030] In some embodiments, the minimum time interval T R2D_minThe composition includes at least one of the following: TA information or transmission delay information; TA information or transmission delay information + R2D transmission processing delay information; TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information; TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information + carrier waiting time information; TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information + carrier waiting time information + modulation time information; TA information or transmission delay information + transmission preparation time information; TA information or transmission delay information + transmission preparation time information + carrier waiting time information; TA information or transmission delay information + transmission preparation time information + carrier waiting time information + modulation time information; TA information or transmission delay information + carrier waiting time information; TA information or transmission delay information + carrier waiting time information + modulation time information.

[0031] In some embodiments, the time interval T R2D It includes at least one of the following: TA information or transmission delay information, carrier wait time information, R2D transmission processing delay information, transmission preparation time information, and modulation time information; wherein, the carrier wait time information includes at least one of R2D carrier wait time information and D2R carrier wait time information, the R2D carrier wait time information includes at least one of charging time information and carrier arrival time information, and the D2R carrier wait time information includes at least one of charging time information and carrier arrival time information.

[0032] In some embodiments, the time interval T R2D The composition includes at least one of the following: TA information or transmission delay information; TA information or transmission delay information + R2D transmission processing delay information; TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information; TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information + carrier waiting time information; TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information + carrier waiting time information + modulation time information; TA information or transmission delay information + transmission preparation time information; TA information or transmission delay information + transmission preparation time information + carrier waiting time information; TA information or transmission delay information + transmission preparation time information + carrier waiting time information + modulation time information; TA information or transmission delay information + carrier waiting time information; TA information or transmission delay information + carrier waiting time information + modulation time information.

[0033] In some embodiments, the minimum time interval T D2R_D2R_minIncludes at least one of the following: transmission interval time information or transmission preparation time information, carrier wait time information, and modulation time information.

[0034] In some embodiments, the minimum time interval T D2R_D2R_min The composition includes at least one of the following: transmission interval time information or transmission preparation time information; transmission interval time information or transmission preparation time information + carrier waiting time information; transmission interval time information or transmission preparation time information + carrier waiting time information + modulation time information.

[0035] In some embodiments, the maximum time interval T D2R_D2R_max Includes at least one of the following: transmission interval time information or transmission preparation time information, carrier wait time information, and modulation time information.

[0036] In some embodiments, the maximum time interval T D2R_D2R_max The composition includes at least one of the following: transmission interval time information or transmission preparation time information; transmission interval time information or transmission preparation time information + carrier waiting time information; transmission interval time information or transmission preparation time information + carrier waiting time information + modulation time information.

[0037] In some embodiments, the time interval T D2R_D2R Includes at least one of the following: transmission interval time information or transmission preparation time information, carrier wait time information, and modulation time information.

[0038] In some embodiments, the time interval T D2R_D2R The composition includes at least one of the following: transmission interval time information or transmission preparation time information; transmission interval time information or transmission preparation time information + carrier waiting time information; transmission interval time information or transmission preparation time information + carrier waiting time information + modulation time information.

[0039] In some embodiments, the maximum time interval T CW_D2R_max Includes at least one of the following: time advance information relative to R2D transmission, charging time information before R2D transmission, time advance information relative to D2R transmission, and charging time information before D2R transmission.

[0040] In some embodiments, the maximum time interval T CW_D2R_maxThe composition includes at least one of the following: time advance information relative to R2D transmission; time advance information relative to R2D transmission + charging time information before R2D transmission; time advance information relative to D2R transmission; time advance information relative to D2R transmission + charging time information before D2R transmission.

[0041] In some embodiments, the minimum time interval T CW_D2R_min Includes at least one of the following: time advance information relative to R2D transmission, charging time information before R2D transmission, time advance information relative to D2R transmission, and charging time information before D2R transmission.

[0042] In some embodiments, the minimum time interval TCW_D2R_min is composed of at least one of the following: time advance information relative to R2D transmission; time advance information relative to R2D transmission + charging time information before R2D transmission; time advance information relative to D2R transmission; and time advance information relative to D2R transmission + charging time information before D2R transmission.

[0043] In some embodiments, the time interval T CW_D2R Includes at least one of the following: time advance information relative to R2D transmission, charging time information before R2D transmission, time advance information relative to D2R transmission, and charging time information before D2R transmission.

[0044] In some embodiments, the time interval T CW_D2R The composition includes at least one of the following: time advance information relative to R2D transmission; time advance information relative to R2D transmission + charging time information before R2D transmission; time advance information relative to D2R transmission; time advance information relative to D2R transmission + charging time information before D2R transmission.

[0045] In some embodiments, at least one of the TA information or transmission delay information, the processing delay information of the R2D transmission, the transmission preparation time information, the carrier waiting time information, the modulation time information, and the transmission interval time information is pre-configured, pre-defined, higher-layer configured, or indicated by the physical layer.

[0046] In some embodiments, when the TA information or transmission delay information is predefined or preconfigured, the TA information or transmission delay information includes one or more values; when the TA information or transmission delay information is configured by a higher layer or indicated by a physical layer, the TA information or transmission delay information includes at least one of the following: directly configured by a higher layer or directly indicated by a physical layer; reported by the IoT device, and configured by the network side based on the reported information; when the fourth higher layer enable parameter is disabled, the TA information or transmission delay information is configured or indicated by the network side; when the fourth higher layer enable parameter is enabled, the TA information or transmission delay information is reported by the IoT device so that the network side can configure or indicate it; when the fifth higher layer enable parameter is disabled, the TA information or transmission delay information remains unchanged through network definition or configuration; when the fifth higher layer enable parameter is enabled, the TA information or transmission delay information is allowed to be modified.

[0047] In some embodiments, the direct configuration by the higher layer or direct indication by the physical layer includes at least one of the following: configuration based on near-field measurement results from the network side; configuration based on predefined or pre-configured results from the network side; configuration based on results reported by the network side regarding previous D2R transmissions of the IoT device; configuration based on measurement results from the network side regarding other IoT devices; and configuration based on results reported by the network side regarding user equipment.

[0048] In some embodiments, the direct configuration by a higher layer or direct indication by a physical layer further includes: configuring a time offset; configuring based on near-field measurement results from the network side to obtain a ninth original time, and obtaining and configuring a first time based on the ninth original time and the time offset; or configuring based on predefined or pre-configured results from the network side to obtain a tenth original time, and obtaining and configuring a first time based on the tenth original time and the time offset; or configuring based on the results of previous D2R transmissions reported by the network side to the IoT device to obtain an eleventh original time, and obtaining and configuring a first time based on the eleventh original time and the time offset; or configuring based on measurement results from the network side to other IoT devices to obtain a twelfth original time, and obtaining and configuring a first time based on the twelfth original time and the time offset; or configuring based on the results of reports from the network side to user equipment to obtain a thirteenth original time, and obtaining and configuring a first time based on the thirteenth original time and the time offset.

[0049] In some embodiments, the direct configuration by the higher layer or direct indication by the physical layer further includes: configuring a time coefficient; configuring based on near-field measurement results from the network side to obtain a ninth original time, and obtaining and configuring a first time based on the ninth original time and the time coefficient; or configuring based on predefined or pre-configured results from the network side to obtain a tenth original time, and obtaining and configuring a first time based on the tenth original time and the time coefficient; or configuring based on the results of previous D2R transmissions reported by the network side to the IoT device to obtain an eleventh original time, and obtaining and configuring a first time based on the eleventh original time and the time coefficient; or configuring based on measurement results from the network side to other IoT devices to obtain a twelfth original time, and obtaining and configuring a first time based on the twelfth original time and the time coefficient; or configuring based on the reporting results from the network side to the user equipment to obtain a thirteenth original time, and obtaining and configuring a first time based on the thirteenth original time and the time coefficient.

[0050] In some embodiments, the reporting by the IoT device and the configuration by the network side based on the reported information includes at least one of the following: the IoT device reports TA information or transmission delay information based on the last or previous D2R transmission, so that the network side can configure it based on the reported information; other IoT devices report TA information or transmission delay information, so that the network side can configure the IoT devices; the IoT device reports its own TA information or transmission delay information capability information, so that the network side can configure it based on the reported capability information; the IoT device reports its own type information, so that the network side can configure it based on the reported type information.

[0051] In some embodiments, when the processing latency information of the R2D transmission is predefined or preconfigured, the processing latency information of the R2D transmission includes one or more values; when the processing latency information of the R2D transmission is configured by a higher layer or indicated by a physical layer, the processing latency information of the R2D transmission includes at least one of the following: directly configured by a higher layer or directly indicated by a physical layer; reported by the IoT device, and configured by the network side based on the reported information; when the sixth higher layer enable parameter is disabled, the processing latency of the R2D transmission is processed by the network side. Configuration or indication; when the sixth layer enable parameter is enabled, the processing latency of R2D transmission is reported by the IoT device, and the network side configures or indicates it; when the seventh layer enable parameter is disabled, the processing latency of R2D transmission remains unchanged through network predefinition or preconfiguration; when the seventh layer enable parameter is enabled, the processing latency of R2D transmission can be modified; when the eighth layer enable parameter is disabled, no configuration of R2D transmission latency is performed; when the eighth layer enable parameter is enabled, R2D transmission latency is configured.

[0052] In some embodiments, the reporting via IoT devices and the configuration by the network side based on the reported information include at least one of the following: the IoT devices report based on previous R2D processing latency so that the network side can configure based on the reported information; other IoT devices report their own R2D processing latency so that the network side can configure based on the reported information; the IoT devices report their own R2D processing latency capability information so that the network side can configure based on the reported capability information; and the IoT devices report their own type information so that the network side can configure based on the reported type information.

[0053] In some embodiments, when the transmission preparation time information is predefined or preconfigured, the transmission preparation time information includes one or more values; when the transmission preparation time information is a higher-layer configuration or physical layer indication, the transmission preparation time information includes at least one of the following: directly configured by a higher layer or directly indicated by a physical layer; reported by the IoT device so that the network side can configure according to the reported information; reported transmission preparation time capability information by the IoT device so that the network side can configure the transmission preparation time according to the reported capability information; reported its own type information by the IoT device so that the network side can configure according to the reported type information.

[0054] In some embodiments, when the ninth layer enable parameter is disabled, the transmission preparation time information is configured or indicated by the network side; when the ninth layer enable parameter is enabled, the transmission preparation time information is reported by the IoT-side device so that the network side can configure or indicate it; when the tenth layer enable parameter is disabled, the transmission preparation time information remains unchanged through network predefined or preconfigured methods; when the tenth layer enable parameter is enabled, the transmission preparation time information is allowed to be modified; when the eleventh layer enable parameter is disabled, the transmission preparation time information is not configured; when the eleventh layer enable parameter is enabled, the transmission preparation time information is configured.

[0055] In some embodiments, when the modulation time information is predefined or preconfigured, the modulation time information includes one or more values; when the modulation time information is a higher-layer configuration or physical layer indication, the modulation time information includes at least one of the following: reported by the IoT device and configured by the network side based on the reported information; when the twelfth higher-layer enable parameter is disabled, the modulation time information is not configured; when the twelfth higher-layer enable parameter is enabled, the modulation time information is configured.

[0056] In some embodiments, the reporting via the IoT device and the configuration by the network side based on the reported information includes at least one of the following: the IoT device reporting its own modulation method, and the network side configuring it based on the reported modulation method; the IoT device reporting its own capability information value, and the network side configuring it based on the reported capability information value; the IoT device reporting its own type information, and the network side configuring it based on the reported type information.

[0057] In some embodiments, when the carrier latency information is predefined or preconfigured, the carrier latency information includes one or more values; when the carrier latency information is a higher-layer configuration or physical layer indication, the carrier latency information includes at least one of the following: configuring or indicating the maximum carrier latency information of the IoT device; configuring the corresponding carrier latency information by the network side through the IoT device reporting its own charging time or charging capability information; configuring the network side according to the reported type information through the IoT device reporting its own type information; when the thirteenth higher-layer enable parameter is disabled, the carrier latency remains unchanged through network predefinition or preconfiguration; when the thirteenth higher-layer enable parameter is enabled, the carrier latency is allowed to be modified; when the fourteenth higher-layer enable parameter is disabled, the carrier latency is not configured; when the fourteenth higher-layer enable parameter is enabled, the carrier latency is configured.

[0058] In some embodiments, when the transmission interval is predefined or preconfigured, the transmission interval includes one or more values; when the transmission interval is configured by a higher layer or indicated by a physical layer, the transmission interval includes at least one of the following: configured directly by a higher layer or indicated directly by a physical layer; or configured by the network side based on the reported information reported by the IoT device.

[0059] In some embodiments, the configuration by the network side based on the reported information, achieved through the reporting by the IoT device, includes at least one of the following: the IoT device reports based on previous transmission interval information, and the network side configures itself based on the reported transmission interval information; other IoT devices report their own transmission interval information, and the network side configures itself based on the reported transmission interval information; the IoT device reports transmission interval capability information, and the network side configures the transmission preparation time based on the reported capability information; the IoT device reports its own type information, and the network side configures itself based on the reported type information.

[0060] In some embodiments, when the fifteenth higher-layer enable parameter is disabled, the transmission interval information is configured or indicated by the network side; when the fifteenth higher-layer enable parameter is enabled, the transmission interval information is reported by the IoT device and configured or indicated by the network side; when the sixteenth higher-layer enable parameter is disabled, the transmission interval information remains unchanged through network predefined or preconfigured methods; when the sixteenth higher-layer enable parameter is enabled, the transmission interval information is allowed to be modified; when the seventeenth higher-layer enable parameter is disabled, the transmission interval is not configured; when the seventeenth higher-layer enable parameter is enabled, the transmission interval is configured.

[0061] In some embodiments, when the timing advance information relative to R2D transmission is predefined or preconfigured, the timing advance information relative to R2D transmission includes one or more values; when the timing advance information relative to R2D transmission is configured by a higher layer or indicated by a physical layer, the timing advance information relative to R2D transmission includes at least one of the following: configuring or indicating the maximum timing advance information relative to R2D transmission for the IoT device; configuring the timing advance information relative to R2D transmission by the network side through the IoT device reporting its own charging time or charging capability information; configuring the IoT device relative to R2D transmission based on the reported type information through the IoT device reporting its own type information; when the eighteenth higher layer enable parameter is disabled, the timing advance information relative to R2D transmission remains unchanged through network predefinition or preconfiguration; when the eighteenth higher layer enable parameter is enabled, the timing advance information relative to R2D transmission is allowed to be modified; when the nineteenth higher layer enable parameter is disabled, the timing advance information relative to R2D transmission is not configured; when the nineteenth higher layer enable parameter is enabled, the timing advance information relative to R2D transmission is configured.

[0062] In some embodiments, when the charging time information before R2D transmission is predefined or preconfigured, the charging time information before R2D transmission includes one or more values; when the charging time information before R2D transmission is configured by a higher layer or indicated by a physical layer, the charging time information before R2D transmission includes at least one of the following: configuring or indicating the maximum charging time information before R2D transmission for the IoT device; configuring the corresponding charging time information before R2D transmission by the network side through the IoT device reporting its own charging time or charging capability information; configuring the IoT device by the network side based on the reported type information through the IoT device reporting its own type information; and disabling the 20th higher layer enable parameter. The charging time information before R2D transmission is configured or indicated by the network side; when the 20th layer enable parameter is enabled, the charging time information before R2D transmission is reported by the IoT device and configured or indicated by the network side; when the 21st layer enable parameter is disabled, the charging time information before R2D transmission remains unchanged through network predefinition or preconfiguration; when the 21st layer enable parameter is enabled, the charging time information before R2D transmission can be modified; when the 22nd layer enable parameter is disabled, the charging time information before R2D transmission is not configured; when the 22nd layer enable parameter is enabled, the charging time information before R2D transmission is configured.

[0063] In some embodiments, when the timing advance information relative to D2R transmission is predefined or preconfigured, the timing advance information relative to D2R transmission includes one or more values; when the timing advance information relative to D2R transmission is a higher-layer configuration or physical layer indication, the timing advance information relative to D2R transmission includes at least one of the following: configuring or indicating the maximum carrier wait time information of the IoT device; configuring the corresponding timing advance information relative to D2R transmission by the network side through the IoT device reporting its own charging time or charging capability information; configuring the IoT device according to the reported type information through the network side; when the twenty-third higher-layer enable parameter is disabled, the timing advance information relative to D2R transmission remains unchanged through network predefinition or preconfiguration; when the twenty-third higher-layer enable parameter is enabled, the timing advance information relative to D2R transmission is allowed to be modified; when the twenty-fourth higher-layer enable parameter is disabled, the timing advance information relative to D2R transmission is not configured; when the twenty-fourth higher-layer enable parameter is enabled, the timing advance information relative to D2R transmission is configured.

[0064] In some embodiments, when the charging time information before D2R transmission is predefined or preconfigured, the charging time information before D2R transmission includes one or more values; when the charging time information before D2R transmission is a higher-layer configuration or physical layer indication, the charging time information before D2R transmission includes at least one of the following: configuring or indicating the maximum charging time information before D2R transmission for the IoT device; configuring the charging time information before D2R transmission by the network side through the IoT device reporting its own charging time or charging capability information; configuring the charging time information before D2R transmission by the network side based on the reported type information through the IoT device reporting its own type information; and disabling the twenty-fifth higher-layer enable parameter. The charging time information before D2R transmission is configured or indicated by the network side; when the 25th layer enable parameter is enabled, the charging time information before D2R transmission is reported by the IoT device and configured or indicated by the network side; when the 26th layer enable parameter is disabled, the charging time information before D2R transmission remains unchanged through network predefinition or preconfiguration; when the 26th layer enable parameter is enabled, the charging time information before D2R transmission can be modified; when the 27th layer enable parameter is disabled, the charging time information before D2R transmission is not configured; when the 27th layer enable parameter is enabled, the charging time information before D2R transmission is configured.

[0065] In some embodiments, the time granularity information includes at least one of the following: the time granularity information is a fixed value; the time granularity information is not greater than a first threshold or not less than a second threshold; the time granularity information is within a specified time granularity range; the time granularity information is a bit, a transport block, an orthogonal frequency division multiplexing (OFDM) symbol, an on / off keying OOK chip, an OFDM time slot, a microsecond, a sampling point, a PRDCH chip, a PRDCH symbol, a PRDCH time slot, a PRDCH sampling point, a physical layer channel PDRCH chip on a D2R link, a PDRCH symbol, a PDRCH time slot, a PDRCH sampling point, an R2D chip, an R2D symbol, an R2D time slot, an R2D sampling point, a D2R chip, a D2R symbol, a D2R time slot, and a D2R sampling point.

[0066] In some embodiments, the configuration or indication method further includes at least one of the following: each parameter in the configuration or indication method is configured individually, uniformly configured within an environmental IoT resource set, an environmental IoT media access control element, or an environmental IoT control command; the configuration or indication method is configured in the form of a resource set, with the network side configuring or indicating the resource set identifier to be selected, so as to select the resource set corresponding to the resource set identifier for configuration from multiple resource sets.

[0067] In a second aspect of this disclosure, an Internet of Things (IoT) device is provided, comprising: a memory; and a processor coupled to the memory, the processor being configured to execute instructions stored in the memory to implement the method as described in any of the above embodiments.

[0068] In a third aspect of this disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions that, when executed by a processor, implement the method as described in any of the above embodiments.

[0069] In a fourth aspect of this disclosure, a computer program product is provided, including computer instructions, wherein the computer instructions, when executed by a processor, implement the method as described in any of the above embodiments.

[0070] Other features and advantages of this disclosure will become clear from the following detailed description of exemplary embodiments with reference to the accompanying drawings. Attached Figure Description

[0071] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0072] Figure 1 This is a flowchart illustrating a communication method according to an embodiment of the present disclosure;

[0073] Figure 2 This is a schematic diagram of the structure of an Internet of Things (IoT) terminal according to an embodiment of this disclosure;

[0074] Figure 3 This is a schematic diagram of a timeline configuration according to an embodiment of the present disclosure;

[0075] Figure 4 A schematic diagram of a timeline configuration for another embodiment of this disclosure;

[0076] Figure 5 This is a schematic diagram of the timeline configuration for yet another embodiment of this disclosure;

[0077] Figure 6 This is a schematic diagram of the timeline configuration for yet another embodiment of this disclosure;

[0078] Figure 7 This is a schematic diagram of the timeline configuration for yet another embodiment of this disclosure;

[0079] Figure 8 This is a schematic diagram of the timeline configuration for yet another embodiment of this disclosure;

[0080] Figure 9 This is a schematic diagram of the timeline configuration for yet another embodiment of this disclosure;

[0081] Figure 10 This is a schematic diagram of the timeline configuration for yet another embodiment of this disclosure;

[0082] Figure 11 This is a schematic diagram of the timeline configuration for yet another embodiment of this disclosure;

[0083] Figure 12 This is a schematic diagram of the timeline configuration for yet another embodiment of this disclosure;

[0084] Figure 13 This is a schematic diagram of the timeline configuration for yet another embodiment of this disclosure. Detailed Implementation

[0085] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0086] Unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of this disclosure.

[0087] At the same time, it should be understood that, for ease of description, the dimensions of the various parts shown in the accompanying drawings are not drawn according to actual scale.

[0088] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0089] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0090] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0091] Figure 1 This is a flowchart illustrating a communication method according to an embodiment of the present disclosure. In some embodiments, the following communication method is performed by an Internet of Things (IoT) device, including steps 11-12.

[0092] Step 11: Receive time domain control information sent by the network-side device.

[0093] It should be noted that time-domain control information includes at least one of timeline information, time-domain resource information, time interval information, and timing scheduling information.

[0094] In step 12, based on time-domain control information, D2R (device-to-reader) transmission is performed with the network-side device at the first time.

[0095] It should be noted that D2R transmission includes the transmission of at least one of the following: PDRCH (Physical Device to Reader Channel, physical layer transmission channel on the D2R link), D2R control signals, synchronization signals, and reference signals.

[0096] In some embodiments, the first time includes at least one of the following:

[0097] 1) The maximum time interval T from the last time granularity of the previous R2D (reader to device, network-side device to IoT device) transmission to the first time granularity of the D2R transmission. R2D_max ;

[0098] 2) The minimum time interval T from the last time granularity of the previous R2D transmission to the first time granularity of the D2R transmission. R2D_min ;

[0099] 3) The time interval T from the last time granularity of the previous R2D transmission to the first time granularity of the D2R transmission. R2D ;

[0100] 4) The minimum time interval T from the last time granularity of the previous D2R transmission to the first time granularity of the D2R transmission. D2R_D2R_min ;

[0101] 5) The maximum time interval T from the last time granularity of the previous D2R transmission to the first time granularity of the D2R transmission. D2R_D2R_max ;

[0102] 6) The time interval T from the last time granularity of the previous D2R transmission to the first time granularity of the D2R transmission. D2R_D2R ;

[0103] 7) The maximum time interval T from the first time granularity of carrier CW transmission to the first time granularity of D2R transmission. CW_D2R_max ;

[0104] 8) The minimum time interval T from the first time granularity of carrier CW transmission to the first time granularity of D2R transmission. CW_D2R_min ;

[0105] 9) The time interval T from the first time granularity of carrier CW transmission to the first time granularity of D2R transmission. CW_D2R .

[0106] In some embodiments, the first time is predefined, preconfigured, higher-level configured, or indicated by the physical layer.

[0107] For example, the T mentioned above R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R At least one of them is predefined, preconfigured, high-level configured, or physical layer indicated.

[0108] In some embodiments, the maximum time interval T R2D_max Includes at least one of the following:

[0109] 1) A value.

[0110] For example, T R2D_max It is a positive integer, and its value ranges from 200μs to 300μs.

[0111] 2) Multiple values. For example, the multiple values ​​include at least one of the following:

[0112] 2.1) Configure or indicate multiple values ​​based on the bandwidth of D2R or R2D transmission.

[0113] For example, the bandwidth value for 180kHz is 200μs to 300μs, and the bandwidth value for 360kHz is 100μs to 150μs.

[0114] 2.2) Configure or indicate multiple values ​​based on the subcarrier spacing.

[0115] For example, the subcarrier spacing value at 15 kHz is 200 μs to 300 μs, and the subcarrier spacing band at 30 kHz is T. R2D_max The value is 100μs~150μs.

[0116] 2.3) Directly configure or indicate multiple values.

[0117] For example, multiple T R2D_max The values ​​were all set between 200 μs and 300 μs.

[0118] In some embodiments, the minimum time interval T R2D_min Includes at least one of the following:

[0119] 1) A value.

[0120] For example, T R2D_min It is a positive integer, and its value ranges from 200μs to 300μs.

[0121] 2) Multiple values. For example, the multiple values ​​include at least one of the following:

[0122] 2.1) Configure or indicate multiple values ​​based on the bandwidth of D2R or R2D transmission.

[0123] For example, the bandwidth value for 180kHz is 200μs to 300μs, and the bandwidth value for 360kHz is 100μs to 150μs.

[0124] 2.2) Configure or indicate multiple values ​​based on the subcarrier spacing.

[0125] For example, the subcarrier spacing value at 15 kHz is 200 μs to 300 μs, and the subcarrier spacing band at 30 kHz is T. R2D_min The value is 100μs~150μs.

[0126] 2.3) Directly configure or indicate multiple values.

[0127] For example, T R2D_min It is a positive integer. Multiple T R2D_min The values ​​were all set between 200 μs and 300 μs.

[0128] In some embodiments, time interval T R2D Includes at least one of the following:

[0129] 1) A value.

[0130] For example, T R2D It is a positive integer, and its value ranges from 200μs to 300μs.

[0131] 2) Multiple values. For example, the multiple values ​​include at least one of the following:

[0132] 2.1) Configure or indicate multiple values ​​based on the bandwidth of D2R or R2D transmission.

[0133] For example, the bandwidth value for 180kHz is 200μs to 300μs, and the bandwidth value for 360kHz is 100μs to 150μs.

[0134] 2.2) Configure or indicate multiple values ​​based on the subcarrier spacing.

[0135] For example, the subcarrier spacing value at 15 kHz is 200 μs to 300 μs, and the subcarrier spacing band at 30 kHz is T. R2D The value is 100μs~150μs.

[0136] 2.3) Directly configure or indicate multiple values.

[0137] For example, T R2D It is a positive integer. Multiple T R2D The values ​​were all set between 200 μs and 300 μs.

[0138] In some embodiments, the minimum time interval T D2R_D2R_min Includes at least one of the following:

[0139] 1) A value.

[0140] For example, T D2R_D2R_min It is a positive integer, and its value ranges from 100μs to 200μs.

[0141] 2) Multiple values. For example, the multiple values ​​include at least one of the following:

[0142] 2.1) Configure or indicate multiple values ​​based on the bandwidth of D2R or R2D transmission.

[0143] For example, the bandwidth value for 180kHz is 100μs to 200μs, and the bandwidth value for 360kHz is 50μs to 100μs.

[0144] 2.2) Configure or indicate multiple values ​​based on the subcarrier spacing.

[0145] For example, the subcarrier spacing value at 15 kHz is 100 μs to 200 μs, and the subcarrier spacing band at 30 kHz is T. D2R_D2R_min The duration is 50μs to 100μs.

[0146] 2.3) Directly configure or indicate multiple values.

[0147] For example, T D2R_D2R_min It is a positive integer. Multiple T D2R_D2R_min The values ​​were all set between 100 μs and 200 μs.

[0148] In some embodiments, the maximum time interval T D2R_D2R_max Includes at least one of the following:

[0149] 1) A value

[0150] For example, T D2R_D2R_max It is a positive integer, and its value ranges from 100μs to 200μs.

[0151] 2) Multiple values. For example, the multiple values ​​include at least one of the following:

[0152] 2.1) Configure or indicate multiple values ​​based on the bandwidth of D2R or R2D transmission.

[0153] For example, the bandwidth value for 180kHz is 100μs to 200μs, and the bandwidth value for 360kHz is 50μs to 100μs.

[0154] 2.2) Configure or indicate multiple values ​​based on the subcarrier spacing.

[0155] For example, the subcarrier spacing value at 15 kHz is 100 μs to 200 μs, and the subcarrier spacing band at 30 kHz is T. D2R_D2R_max The value is 50μs to 100μs.

[0156] 2.3) Directly configure or indicate multiple values.

[0157] For example, T D2R_D2R_max The value is a positive integer. Multiple T's D2R_D2R_max The values ​​were all set between 100 μs and 200 μs.

[0158] In some embodiments, time interval T D2R_D2R Includes at least one of the following:

[0159] 1) A value.

[0160] For example, T D2R_D2R It is a positive integer, and its value ranges from 100μs to 200μs.

[0161] 2) Multiple values. For example, the multiple values ​​include at least one of the following:

[0162] 2.1) Configure or indicate multiple values ​​based on the bandwidth of D2R or R2D transmission;

[0163] For example, the bandwidth value for 180kHz is 100μs to 200μs, and the bandwidth value for 360kHz is 50μs to 100μs.

[0164] 2.2) Configure or indicate multiple values ​​based on the subcarrier spacing.

[0165] For example, the subcarrier spacing value at 15 kHz is 100 μs to 200 μs, and the subcarrier spacing band at 30 kHz is T. D2R_D2R The value is 50μs to 100μs.

[0166] 2.3) Configure or indicate multiple values.

[0167] For example, T D2R_D2R It is a positive integer. Multiple TD2R_D2R values ​​are all set between 100μs and 200μs.

[0168] In some embodiments, the maximum time interval T CW_D2R_max Includes at least one of the following:

[0169] 1) A value.

[0170] For example, T CW_D2R_max It is a positive integer, and its value ranges from 0s to 10s.

[0171] 2) Multiple values. For example, the multiple values ​​include at least one of the following:

[0172] 2.1) Configure or indicate multiple values ​​based on the bandwidth of D2R or R2D transmission;

[0173] For example, the bandwidth value for 180kHz is 0s to 10s, and the bandwidth value for 360kHz is 0s to 5s.

[0174] 2.2) Configure or indicate multiple values ​​based on the subcarrier spacing.

[0175] For example, the subcarrier spacing for 15kHz is 0s to 10s, and the subcarrier spacing for 30kHz is 0s to 5s.

[0176] 2.3) Directly configure or indicate multiple values.

[0177] For example, T CW_D2R_max It is a positive integer. Multiple T CW_D2R_max The values ​​are all set between 0s and 10s.

[0178] In some embodiments, the minimum time interval T CW_D2R_min Includes at least one of the following:

[0179] 1) A value.

[0180] For example, T CW_D2R_min It is a positive integer, and its value ranges from 0s to 10s.

[0181] 2) Multiple values. For example, the multiple values ​​include at least one of the following:

[0182] 2.1) Configure or indicate multiple values ​​based on the bandwidth of D2R or R2D transmission;

[0183] For example, the bandwidth value for 180kHz is 0s to 10s, and the bandwidth value for 360kHz is 0s to 5s.

[0184] 2.2) Configure or indicate multiple values ​​based on the subcarrier spacing;

[0185] For example, the subcarrier spacing value for 15kHz is 0s to 10s, and the subcarrier spacing band for 30kHz is T. CW_D2R_min The duration is 0s to 5s.

[0186] 2.3) Directly configure or indicate multiple values.

[0187] For example, T CW_D2R_min It is a positive integer. Multiple T CW_D2R_min The values ​​are all set between 0s and 10s.

[0188] In some embodiments, time interval T CW_D2R Includes at least one of the following:

[0189] 1) A value.

[0190] For example, T CW_D2R It is a positive integer, and its value ranges from 0s to 10s.

[0191] 2) Multiple values. For example, the multiple values ​​include at least one of the following:

[0192] 2.1) Configure or indicate multiple values ​​based on the bandwidth of D2R or R2D transmission.

[0193] For example, the bandwidth value for 180kHz is 0s to 10s, and the bandwidth value for 360kHz is 0s to 5s.

[0194] 2.2) Configure or indicate multiple values ​​based on the subcarrier spacing.

[0195] For example, the subcarrier spacing value of 15kHz is between 0s and 10s, and the subcarrier spacing band of 30kHz is T. CW_D2R The duration is 0s to 5s.

[0196] 2.3) Directly configure or indicate multiple values.

[0197] For example, T CW_D2RIt is a positive integer. Multiple T CW_D2R The values ​​are all set between 0s and 10s.

[0198] In some embodiments, the higher-level configuration or physical layer indication includes at least one of the following 1)-5):

[0199] 1) Higher-layer configuration or physical layer instructions are made directly from the network side. For example, this includes at least one of the following: 1.1)-1.6).

[0200] 1.1) Configure based on the short-range measurement results from the network side.

[0201] 1.2) Configure according to the results of predefined or preconfigured network side.

[0202] 1.3) Based on the T data reported by the network side regarding previous D2R transmissions of IoT devices. R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R Configure at least one of them.

[0203] 1.4) Configure the measurement results of other IoT devices through the network side, wherein the other IoT devices are close to the IoT device or are in the same group.

[0204] 1.5) Configure the time offset. Based on the results of 1.1)-1.4), calculate the time offset, obtain the new first time information and configure it. The calculation method may be the result of 1.1)-1.4) + time offset, or the result of 1.1)-1.4) - time offset.

[0205] 1.6) Configure the time factor. Based on the results of 1.1)-1.4), perform time factor calculation to obtain new first time information and configure it. The calculation method may be the result of 1.1)-1.4) * time factor.

[0206] 2) The configuration is performed by the network side based on the information reported by the IoT devices. For example, it includes at least one of the following: 2.1)-2.6).

[0207] 2.1) IoT devices based on the last or previous T R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max TCW_D2R_min T CW_D2R At least one of them is reported so that the network side can make configurations.

[0208] 2.2) Other IoT devices according to T R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R At least one of the IoT devices must be reported so that the network side can configure it. Other IoT devices are located close to this IoT device or belong to the same group.

[0209] 2.3) IoT devices report their own T R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R The network side needs to obtain at least one of the capability information so that it can configure itself based on the reported capability information.

[0210] For example, 2.3) above includes at least one of the following.

[0211] 2.3.1) The reported capability information is whether the corresponding first-time parameter configuration is supported.

[0212] 2.3.2) The reported capability information is the configurable threshold information for the corresponding time parameter, for example, for T R2D_max Information may correspond to different T values ​​depending on the capabilities of different IoT devices. R2D_max Value, here you report your own ability's T. R2D_max value.

[0213] 2.3.3) The reported capability information consists of multiple configurable thresholds for corresponding time parameters. The network side selects one of these thresholds for configuration based on the reported capability information.

[0214] 2.4) IoT devices report their own type information so that the network side can configure them according to the reported type information.

[0215] For example, 2.4 above includes at least one of the following.

[0216] 2.4.1) Predefined or pre-configured T for different types of IoT devices on the network side R2D_max T R2D_min TR2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R At least one piece of information is configured according to the reported type of information.

[0217] 2.4.2) Network-side predefined or pre-configured T R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R The system selects one of the following for configuration based on at least one of the multiple pieces of information and the reported category information:

[0218] 2.5) Configure the time offset. Based on the results of 2.1)-2.4), calculate the time offset, obtain the new first time information and configure it. The calculation method may be the result of 2.1)-2.4) + time offset, or the result of 2.1)-2.4) - time offset.

[0219] 2.6) Configure the time factor. Based on the results of 2.1)-2.4), perform time factor calculation to obtain new first time information and configure it. The calculation method may be the result of 2.1)-2.4) * time factor.

[0220] 3) Add a first high-layer enabling parameter. When the first high-layer enabling parameter is disabled, the network side will configure or instruct it immediately; when the first high-layer enabling parameter is enabled, the network side will configure or instruct it immediately based on the information reported by the IoT device.

[0221] 4) Add a second high-level enabling parameter. When the second high-level enabling parameter is disabled, it will not be changed immediately through network predefined or preconfiguration; when the second high-level enabling parameter is enabled, the information can be modified immediately.

[0222] 5) Add a third high-level enabling parameter. When the third high-level enabling parameter is disabled, no configuration will be performed immediately; when the third high-level enabling parameter is enabled, configuration or indication will be allowed immediately.

[0223] In some embodiments, the manner in which a higher-level configuration or physical layer indicates a configuration includes at least one of the following:

[0224] 1) Configuration is performed through the MAC (Media Access Control) layer or a new layer, without requiring physical layer instructions.

[0225] 2) Instructions are given through the physical layer, without the need for configuration of the MAC layer or a new layer.

[0226] 3) Configuration is performed through the MAC layer or a new layer, with instructions provided by the physical layer.

[0227] For example, 3) above includes at least one of the following:

[0228] 3.1) The MAC layer configures a portion of the first-time parameters, and the physical layer indicates a portion of the first-time parameters.

[0229] 3.2) The MAC layer configures the enable information of the first time parameter, and the physical layer indicates the corresponding first time parameter information based on the enable information of the first time parameter.

[0230] In some embodiments, the maximum time interval T R2D_max Include at least one of the following: 1)-5)

[0231] 1) TA (timing advance) information or transmission delay information is used to express the transmission delay from the IoT device to the network-side device. For example, it can be the maximum TA information or the maximum transmission delay information.

[0232] 2) Carrier wait time information, for example, including at least one of the following 2.1)-2.2):

[0233] 2.1) R2D carrier wait time information, used to express the time interval affected by carrier CW between the arrival of R2D at the IoT device and the IoT device's readiness to decode the R2D transmission. For example, the maximum R2D carrier wait time information may include at least one of the following parameters:

[0234] 2.1.1) Charging time information, used to express the charging time of the IoT device or the waiting time required for charging.

[0235] 2.1.2) Carrier arrival time information, used to express the time from when R2D arrives at the IoT device to when carrier CW successfully arrives at the IoT device.

[0236] 2.2) D2R carrier wait time information, used to express the time interval affected by the CW carrier from the time the IoT device finishes decoding or preparing to transmit to the time interval when it is ready to transmit or modulate in D2R. For example, the maximum D2R carrier wait time information may include at least one of the following parameters:

[0237] 2.2.1) Charging time information, used to express the charging time of the IoT device or the waiting time required for charging.

[0238] 2.2.2) Carrier arrival time information, used to express the waiting time from when the IoT device finishes decoding or is ready to send to when the CW carrier successfully arrives at the IoT device.

[0239] 3) R2D transmission processing delay information, used to express the processing time that the IoT device can decode the R2D transmission sent by the network-side device, for example, the maximum processing time.

[0240] 4) Send preparation time information, which is used to express the time interval between when the IoT device finishes decoding and when it is ready to send the next D2R transmission. For example, it is the maximum send preparation time information.

[0241] 5) Modulation time information, used to express the time information required for the IoT device to perform modulation and coding, for example, the maximum modulation and coding time.

[0242] In some embodiments, the maximum time interval T R2D_max The composition includes at least one of the following:

[0243] 1) TA information or transmission delay information;

[0244] 2) TA information or transmission delay information + R2D transmission processing delay information;

[0245] 3) TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information;

[0246] 4) TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information + carrier wait time information;

[0247] 5) TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information + carrier wait time information + modulation time information;

[0248] 6) TA information or transmission delay information + transmission preparation time information;

[0249] 7) TA information or transmission delay information + transmission preparation time information + carrier wait time information;

[0250] 8) TA information or transmission delay information + transmission preparation time information + carrier wait time information + modulation time information;

[0251] 9) TA information or transmission delay information + carrier wait time information;

[0252] 10) TA information or transmission delay information + carrier wait time information + modulation time information.

[0253] In some embodiments, the minimum time interval T R2D_min Include at least one of the following: 1)-6)

[0254] 1) TA information or transmission delay information, used to express the transmission delay from the IoT device to the network-side device, for example, minimum TA information or minimum transmission delay information.

[0255] 2) Carrier wait time information, including, for example, at least one of the following: 2.1)-2.2)

[0256] 2.1) R2D carrier wait time information, used to express the time interval affected by carrier CW between the arrival of R2D at the IoT device and the IoT device's readiness to decode the R2D transmission. For example, the maximum R2D carrier wait time information may include at least one of the following parameters:

[0257] 2.1.1) Charging time information, used to express the charging time of the IoT device or the waiting time required for charging;

[0258] 2.1.2) Carrier arrival time information, used to express the time from when R2D arrives at the IoT device to when carrier CW successfully arrives at the IoT device.

[0259] 2.2) D2R carrier wait time information, used to express the time interval affected by carrier CW from the time the IoT device finishes decoding or preparing to transmit to the time interval when it is ready to transmit or modulate in D2R. For example, the maximum D2R carrier wait time information may include at least one of the following parameters:

[0260] 2.2.1) Charging time information, used to express the charging time of the IoT device or the waiting time required for charging;

[0261] 2.2.2) Carrier arrival time information, used to express the waiting time from when the IoT device finishes decoding or preparing to send to when the carrier CW successfully arrives at the IoT device.

[0262] 3) R2D transmission processing delay information, used to express the processing time for the IoT device to decode the R2D transmission sent by the network-side device, for example, the minimum processing time.

[0263] 4) Send preparation time information, which is used to express the time interval between when the IoT device finishes decoding and when it is ready to send the next D2R transmission. For example, it is the minimum send preparation time information.

[0264] 5) D2R carrier wait time information, used to express the time interval from when the IoT device finishes decoding or is ready to send to when the D2R transmission carrier CW arrives. For example, it is the minimum D2R carrier wait time information.

[0265] 6) Modulation time information, used to express the time information required for the IoT device to perform modulation and coding, for example, the minimum modulation and coding time.

[0266] In some embodiments, the minimum time interval T R2D_min The composition includes at least one of the following:

[0267] 1) TA information or transmission delay information;

[0268] 2) TA information or transmission delay information + R2D transmission processing delay information;

[0269] 3) TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information;

[0270] 4) TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information + carrier wait time information;

[0271] 5) TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information + carrier wait time information + modulation time information;

[0272] 6) TA information or transmission delay information + transmission preparation time information;

[0273] 7) TA information or transmission delay information + transmission preparation time information + carrier wait time information;

[0274] 8) TA information or transmission delay information + transmission preparation time information + carrier wait time information + modulation time information;

[0275] 9) TA information or transmission delay information + carrier wait time information;

[0276] 10) TA information or transmission delay information + carrier wait time information + modulation time information.

[0277] In some embodiments, time interval T R2D Includes at least one of the following: 1)-5)

[0278] 1) TA information or transmission delay information is used to express the transmission delay from the IoT device to the network-side device.

[0279] 2) Carrier wait time information, including, for example, at least one of the following: 2.1)-2.2)

[0280] 2.1) R2D carrier wait time information, used to express the time interval affected by carrier CW between the arrival of R2D at the IoT device and the IoT device's readiness to decode the R2D transmission; may include at least one of the following parameters:

[0281] 2.1.1) Charging time information, used to express the charging time of the IoT device or the waiting time required for charging;

[0282] 2.1.2) Carrier arrival time information, used to express the time from when R2D arrives at the IoT device to when carrier CW successfully arrives at the IoT device.

[0283] 2.2) D2R carrier wait time information, used to express the time interval affected by carrier CW between the completion of decoding or transmission preparation by the IoT device and the preparation for D2R transmission or modulation, may include at least one of the following parameters:

[0284] 2.2.1) Charging time information, used to express the charging time of the IoT device or the waiting time required for charging;

[0285] 2.2.2) Carrier arrival time information, used to express the waiting time from when the IoT device finishes decoding or preparing to send to when the carrier CW successfully arrives at the IoT device.

[0286] 3) R2D transmission processing delay information, which is used to express the processing time for the IoT device to decode the R2D transmission sent by the network-side device.

[0287] 4) Send preparation time information, which is used to express the time interval between when the IoT device finishes decoding and when it is ready to send the next D2R transmission.

[0288] 5) Modulation timing information, used to express the timing information required for the IoT device to perform modulation and coding.

[0289] In some embodiments, time interval T R2D The composition includes at least one of the following:

[0290] 1) TA information or transmission delay information;

[0291] 2) TA information or transmission delay information + R2D transmission processing delay information;

[0292] 3) TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information;

[0293] 4) TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information + carrier wait time information;

[0294] 5) TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information + carrier wait time information + modulation time information;

[0295] 6) TA information or transmission delay information + transmission preparation time information;

[0296] 7) TA information or transmission delay information + transmission preparation time information + carrier wait time information;

[0297] 8) TA information or transmission delay information + transmission preparation time information + carrier wait time information + modulation time information;

[0298] 9) TA information or transmission delay information + carrier wait time information;

[0299] 10) TA information or transmission delay information + carrier wait time information + modulation time information.

[0300] In some embodiments, the minimum time interval T D2R_D2R_min Include at least one of the following: 1)-3)

[0301] 1) Transmission interval time information or transmission preparation time information, used to express the waiting time from the completion of one D2R transmission to the start of the next D2R transmission on the IoT device, for example, the minimum waiting time.

[0302] 2) Carrier wait time information, used to express the time interval from when the IoT device is ready to send to when the carrier CW carrying D2R transmission arrives, for example, the minimum carrier wait time information.

[0303] 3) Modulation time information, which is used to express the processing time required for the IoT device to perform modulation and coding, for example, the minimum modulation time information.

[0304] In some embodiments, the minimum time interval T D2R_D2R_min The composition includes at least one of the following:

[0305] 1) Transmission interval time information or transmission preparation time information;

[0306] 2) Transmission interval time information or transmission preparation time information + carrier wait time information;

[0307] 3) Transmission interval time information or transmission preparation time information + carrier waiting time information + modulation time information.

[0308] In some embodiments, the maximum time interval T D2R_D2R_max Include at least one of the following: 1)-3)

[0309] 1) Transmission interval time information or transmission preparation time information, used to express the waiting time from the completion of one D2R transmission to the start of the next D2R transmission on the IoT device, for example, the maximum waiting time.

[0310] 2) Carrier wait time information, used to express the time interval from when the IoT device is ready to send to when the carrier CW carrying D2R transmission arrives, for example, the maximum carrier wait time information.

[0311] 3) Modulation time information, which is used to express the processing time required for the IoT device to perform modulation and coding, for example, the maximum modulation time information.

[0312] In some embodiments, the maximum time interval T D2R_D2R_max The composition includes at least one of the following:

[0313] 1) Transmission interval time information or transmission preparation time information;

[0314] 2) Transmission interval time information or transmission preparation time information + carrier wait time information;

[0315] 3) Transmission interval time information or transmission preparation time information + carrier waiting time information + modulation time information.

[0316] In some embodiments, time interval T D2R_D2R Include at least one of the following: 1)-3)

[0317] 1) Transmission interval time information or transmission preparation time information, used to express the waiting time from the completion of one D2R transmission to the start of the next D2R transmission on the IoT device.

[0318] 2) Carrier wait time information, which is used to express the time interval from when the IoT device is ready to send to when the carrier CW carrying D2R transmission arrives.

[0319] 3) Modulation time information, which is used to express the processing time required for the IoT device to perform modulation and coding.

[0320] In some embodiments, time interval T D2R_D2R The composition includes at least one of the following:

[0321] 1) Transmission interval time information or transmission preparation time information;

[0322] 2) Transmission interval time information or transmission preparation time information + carrier wait time information;

[0323] 3) Transmission interval time information or transmission preparation time information + carrier waiting time information + modulation time information.

[0324] In some embodiments, the maximum time interval T CW_D2R_max Include at least one of the following: 1)-4)

[0325] 1) Time advance information relative to R2D transmission, for example, maximum time advance information.

[0326] 2) Charging time information before R2D transmission, for example, maximum charging time information.

[0327] 3) Time advance information relative to D2R transmission, for example, maximum time advance information.

[0328] 4) Charging time information before D2R transmission, for example, maximum charging time information.

[0329] In some embodiments, the maximum time interval T CW_D2R_max The composition includes at least one of the following:

[0330] 1) Timing advance information relative to R2D transmission;

[0331] 2) Time advance information relative to R2D transmission + charging time information before R2D transmission;

[0332] 3) Timing advance information relative to D2R transmission;

[0333] 4) Time advance information relative to D2R transmission + charging time information before D2R transmission.

[0334] In some embodiments, the minimum time interval T CW_D2R_min Include at least one of the following: 1)-4)

[0335] 1) The timing advance information relative to R2D transmission, for example, the minimum timing advance information.

[0336] 2) Charging time information before R2D transmission, for example, minimum charging time information.

[0337] 3) Time advance information relative to D2R transmission, for example, minimum time advance information.

[0338] 4) Charging time information before D2R transmission, for example, minimum charging time information.

[0339] In some embodiments, the minimum time interval TCW_D2R_min is composed of at least one of the following:

[0340] 1) Timing advance information relative to R2D transmission;

[0341] 2) Time advance information relative to R2D transmission + charging time information before R2D transmission;

[0342] 3) Timing advance information relative to D2R transmission;

[0343] 4) Time advance information relative to D2R transmission + charging time information before D2R transmission.

[0344] In some embodiments, time interval T CW_D2R Includes at least one of the following:

[0345] 1) Timing advance information relative to R2D transmission.

[0346] 2) Charging time information before R2D transmission.

[0347] 3) Timing advance information relative to D2R transmission.

[0348] 4) Charging time information before D2R transmission.

[0349] In some embodiments, time interval T CW_D2R The composition includes at least one of the following:

[0350] 1) Timing advance information relative to R2D transmission;

[0351] 2) Time advance information relative to R2D transmission + charging time information before R2D transmission;

[0352] 3) Timing advance information relative to D2R transmission;

[0353] 4) Time advance information relative to D2R transmission + charging time information before D2R transmission.

[0354] In some embodiments, at least one of the following is pre-configured, predefined, higher-layer configured, or physical-layer indicated: TA information or transmission delay information, R2D transmission processing delay information, transmission preparation time information, carrier wait time information, modulation time information, and transmission interval time information, including at least one of the following schemes.

[0355] 1) TA information or transmission delay information

[0356] 1.1) For predefined or preconfigured

[0357] 1.1.1) Only one value, which is a positive integer, for example, 0 to 200 μs.

[0358] 1.1.2) Define multiple values, which are positive integers, for example, all in the range of 0 to 200 μs.

[0359] 1.2) For high-level configurations or physical layer indications, including at least one of the following:

[0360] 1.2.1) Directly configured by a higher layer or directly indicated by the physical layer, including at least one of the following:

[0361] a) Configure based on short-range measurement results from the network side;

[0362] b) Configure according to the predefined or preconfigured results on the network side;

[0363] c) Configure based on the network side's previous D2R transmission reports from IoT devices;

[0364] d) Configure based on the measurement results of other IoT devices on the network side. Other IoT devices may be close to this IoT device or belong to the same group.

[0365] e) Configure the user equipment based on the network side's reporting results to the user equipment, where the user equipment is relatively close to the target IoT device;

[0366] f) Configure the time offset. Based on the results of a) to e), calculate the time offset, obtain the new first time information and configure it. The calculation method may be the result of a) to e) + time offset, or the result of a) to e) - time offset.

[0367] g) Configure the time factor. Based on the results of a) to e), perform the time factor calculation to obtain new first time information and configure it. The calculation method may be the result of a) to e) * the time factor.

[0368] 1.2.2) Reporting is made through IoT devices, and the network side configures itself based on the reported information, including at least one of the following:

[0369] a) IoT devices report TA information or transmission delay information from the last or previous D2R transmission so that the network side can configure itself based on the reported information;

[0370] b) Other IoT devices report TA information or transmission delay information so that the network side can configure the IoT devices. Other IoT devices may be close to the IoT device or be in the same group.

[0371] c) The ability of IoT devices to report their own TA information or transmission latency information, so that the network side can configure itself based on the reported capability information, including at least one of the following:

[0372] i. The reported capability information is the threshold information of TA information or transmission delay information. For example, different IoT device capabilities may correspond to different TA information or transmission delay information values. Here, the TA information or transmission delay information value belonging to its own capability is reported.

[0373] ii. The reported capability information consists of multiple configurable thresholds for corresponding time parameters. The network side selects one of these thresholds for configuration based on the reported capability information.

[0374] d) IoT devices report their type information so that the network side can configure itself based on the reported type information, including at least one of the following:

[0375] i. The network side predefines or preconfigures TA information or transmission latency information for different types of IoT devices, and configures it according to the reported type information.

[0376] ii. The network side predefines or preconfigures various types of TA information or transmission delay information, and selects one of them for configuration based on the reported type of information.

[0377] e) Based on a) to d) above, configure the time offset, perform time offset calculation, obtain new TA information or transmission delay information and configure it. The calculation method may be the result of a) to d) + time offset, or the result of a) to d) - time offset.

[0378] f) Based on a) to d) above, configure the time coefficient factor, perform time coefficient calculation, obtain new TA information or transmission delay information and configure it. The calculation method may be the result of a) to d) * time coefficient.

[0379] 1.2.3) Add a fourth layer enabling parameter. When the fourth layer enabling parameter is disabled, TA information or transmission delay information is configured or indicated by the network side. When the fourth layer enabling parameter is enabled, TA information or transmission delay information is reported by the IoT device so that the network side can configure or indicate it.

[0380] 1.2.4) Add a fifth layer enabling parameter. When the fifth layer enabling parameter is disabled, TA information or transmission delay information will no longer change through network definition or configuration. When the fifth layer enabling parameter is enabled, TA information or transmission delay information can be modified.

[0381] 2) Processing delay information for R2D transmission

[0382] 2.1) For predefined or preconfigured

[0383] 2.1.1) Only one value, which is a positive integer, for example, 0 to 100 μs.

[0384] 2.1.2) Define multiple values, including at least one of the following:

[0385] a) Configure or indicate the processing delay values ​​for multiple R2D transmissions based on the bandwidth of the R2D transmission, for example, 0 to 100 μs for 180 kHz bandwidth and 0 to 50 μs for 360 kHz bandwidth.

[0386] b) Configure or indicate the processing delay values ​​for multiple R2D transmissions based on the subcarrier spacing, for example, the subcarrier spacing value for 15KHz is 0 to 100μs, and the processing delay value for R2D transmission with a subcarrier spacing of 30KHz is 0 to 50μs.

[0387] c) are positive integers, all within the range of 0 to 100 μs.

[0388] 2.2) For high-level configurations or physical layer indications, including at least one of the following:

[0389] 2.2.1) Directly configured by the upper layer or directly indicated by the physical layer.

[0390] For example, configuration can be performed based on predefined or pre-configured results from the network side.

[0391] 2.2.2) Reporting is made via IoT devices, and the network side configures itself based on the reported information. For example, this includes at least one of the following:

[0392] a) IoT devices report based on the previous R2D processing latency so that the network side can configure itself based on the reported information.

[0393] b) Other IoT devices report their R2D processing latency so that the network side can configure itself based on the reported information. These other IoT devices must be devices with the same capabilities or of the same type as the current IoT device.

[0394] c) IoT devices report their R2D processing latency capabilities so that the network can configure itself based on the reported capabilities. This includes at least one of the following:

[0395] i. The reported capability information is the threshold information for R2D processing latency. For example, different IoT device capabilities may correspond to different TA information or transmission latency information values. Here, the TA information or transmission latency information value belonging to its own capability is reported.

[0396] ii. The reported capability information consists of multiple corresponding configurable thresholds for R2D processing latency. The network side selects one of these thresholds for configuration based on the reported capability information.

[0397] d) IoT devices report their type information so that the network can configure itself based on this information. This includes at least one of the following:

[0398] i. The network side predefines or preconfigures R2D processing latency information for different types of IoT devices, and configures it according to the reported type information;

[0399] ii. The network side predefines or preconfigures various types of TA information or transmission delay information, and selects one of them for configuration based on the reported type of information.

[0400] 2.2.3) Add a sixth layer enabling parameter. When the sixth layer enabling parameter is disabled, the processing latency of R2D transmission is configured or indicated by the network side; when the sixth layer enabling parameter is enabled, the processing latency of R2D transmission is reported by the IoT device, and the network side configures or indicates it.

[0401] 2.2.4) A new seventh layer enabling parameter is added. When the seventh layer enabling parameter is disabled, the processing latency of R2D transmission will not change through network predefinition or preconfiguration; when the seventh layer enabling parameter is enabled, the processing latency of R2D transmission can be modified.

[0402] 2.2.5) Add an eighth layer enable parameter. When the eighth layer enable parameter is disabled, R2D transmission delay is not configured; when the eighth layer enable parameter is enabled, R2D transmission delay is configured.

[0403] 3) Send preparation time information

[0404] 3.1) For predefined or preconfigured

[0405] 3.1.1) Only one value, which is a positive integer, for example, 0 to 50 μs.

[0406] 3.1.2) Define multiple values, including at least one of the following:

[0407] a) Configure or indicate multiple transmit preparation time information based on the bandwidth of R2D or D2R transmission, for example, the value is 0 to 50 μs for 180 kHz bandwidth and 0 to 25 μs for 360 kHz bandwidth.

[0408] b) Configure or indicate multiple transmission preparation time information according to the subcarrier spacing, for example, the subcarrier spacing value of 15KHz is between 0 and 50μs, and the processing delay value of R2D transmission of 30HKz subcarrier spacing is between 0 and 25μs.

[0409] c) are positive integers, all within the range of 0 to 100 μs.

[0410] 3.2) For high-level configurations or physical layer indications, including at least one of the following:

[0411] 3.2.1 It can be configured directly by the upper layer or indicated directly by the physical layer.

[0412] For example, configuration can be performed based on predefined or pre-configured results from the network side.

[0413] 3.2.2 Reporting is performed via IoT devices so that the network side can configure itself based on the reported information, including at least one of the following:

[0414] a) IoT devices report based on previous transmission preparation time information, and the network side configures itself based on this reported information;

[0415] b) Other IoT devices report their own transmission preparation time information, and the network side configures the IoT device based on this reported information. Other IoT devices have the same capabilities or belong to the same category as this IoT device.

[0416] 3.2.3 Report transmission preparation time capability information through IoT devices so that the network side can configure the transmission preparation time based on the reported capability information, including at least one of the following:

[0417] a) The IoT device reports a transmission preparation time capability information value, and the network side configures accordingly. For example, different transmission preparation time values ​​may be predefined, and the configuration is based on the reported capability information;

[0418] b) The IoT device reports multiple capability information values ​​for transmission preparation time, and the network side selects one of them for configuration based on the capability information.

[0419] 3.2.4 The IoT device reports its own type information so that the network side can configure itself based on the reported type information.

[0420] a) The network side predefines or preconfigures transmission preparation time information for different types of IoT devices, and configures it according to the reported type information;

[0421] b) The network side predefines or preconfigures various transmission preparation time information and selects one of them for configuration based on the reported type of information.

[0422] 3.3) Add a new ninth layer enabling parameter. When the ninth layer enabling parameter is disabled, the preparation time information is sent for configuration or indication via the network side; when the ninth layer enabling parameter is enabled, the preparation time information is reported by the IoT device so that the network side can configure or indicate it.

[0423] 3.4) Add a new tenth layer enabling parameter. When the tenth layer enabling parameter is disabled, the transmission preparation time information will not change through network predefined or preconfigured methods; when the tenth layer enabling parameter is enabled, the transmission preparation time information can be modified.

[0424] 3.5) Add an eleventh layer enable parameter. When the eleventh layer enable parameter is disabled, no transmission preparation time information is configured; when the eleventh layer enable parameter is enabled, transmission preparation time information is configured.

[0425] 4) Modulation time information

[0426] 4.1) For predefined or preconfigured

[0427] 4.1.1) is a single value, which varies depending on the modulation method. For example, it is 0–10 μs for OOK (on-off keying), 0–20 μs for BPSK (Binary Phase Shift Keying), and 0–20 μs for BFSK (Binary Frequency Shift Keying).

[0428] 4.1.2)2. Assign multiple values, for example, assign three values, corresponding to OOK, BPSK or BFSK.

[0429] 4.2) For high-level configurations or physical layer indications, including at least one of the following:

[0430] 4.2.1) Reporting is made through IoT devices, and the network side configures itself based on the reported information, including at least one of the following:

[0431] a) The IoT device reports its modulation scheme, and the network side configures it based on the reported modulation scheme.

[0432] b) The IoT device reports its own capability information value, and the network side configures it based on the reported capability information value, including at least one of the following:

[0433] i. An IoT device reports a capability information value, and the network side uses this capability information to determine the possible modulation method of the IoT device and configure it accordingly;

[0434] ii. The IoT device reports multiple capability information values, and the network side selects one of them for configuration based on the capability information.

[0435] c) The IoT device reports its own type information, and the network side configures itself based on the reported type information.

[0436] i. The network side determines the modulation method that the IoT device may adopt based on the reported type information and configures it accordingly;

[0437] ii. The network side predefines or preconfigures various modulation methods that IoT devices of different types may adopt, and selects one of them for configuration based on the reported type information.

[0438] 4.2.2) Add a twelfth layer enable parameter. When the twelfth layer enable parameter is disabled, modulation timing information is not configured; when the twelfth layer enable parameter is enabled, modulation timing information is configured.

[0439] 5) Carrier wait time information

[0440] 5.1) For predefined or preconfigured

[0441] 5.1.1) is a single value, configured to be 0–100 μs.

[0442] 5.1.2) represents multiple values, all configured within the range of 0–100 μs, including at least one of the following:

[0443] a) Differentiate between R2D carrier latency and D2R carrier latency, and configure them separately;

[0444] b) Distinguish T R2D_max T R2D_min ;

[0445] c) Differentiate the types of IoT devices and configure them accordingly;

[0446] d) Differentiate the capabilities of IoT devices and configure them accordingly.

[0447] 5.2) For high-level configurations or physical layer indications, including at least one of the following:

[0448] 5.2.1) Configure or indicate the maximum carrier wait time information for IoT devices;

[0449] 5.2.2) The IoT device reports its charging time or charging capacity information, and the network side configures the corresponding carrier waiting time information, including at least one of the following:

[0450] a) Predefine or preconfigure carrier waiting time information under different charging times or charging capabilities, and configure it based on the information reported by the IoT device;

[0451] b) Predefine or preconfigure multiple carrier wait time information values, and select one of the values ​​for configuration based on the reported charging time or charging capacity information.

[0452] 5.2.3) The IoT device reports its own category information, and the network side configures itself based on the reported category information, including at least one of the following:

[0453] a) Predefine or preconfigure carrier wait time information for different types of IoT devices, and configure it based on the information reported by the IoT devices;

[0454] b) Predefine or preconfigure multiple carrier wait time information values, and select one of the values ​​for configuration based on the reported IoT device type information.

[0455] 5.2.4) Add a new thirteenth layer enable parameter. When the thirteenth layer enable parameter is disabled, the carrier latency will no longer change through network predefinition or preconfiguration; when the thirteenth layer enable parameter is enabled, the carrier latency can be modified.

[0456] 5.2.5) Add a fourteenth layer enable parameter. When the fourteenth layer enable parameter is disabled, the carrier wait time is not configured; when the fourteenth layer enable parameter is enabled, the carrier wait time is configured.

[0457] 6) Transmission interval time

[0458] 6.1) For predefined or preconfigured

[0459] 6.1.1) Only one value, which is a positive integer, for example, 0 to 100 μs.

[0460] 6.1.2) Define multiple values, including at least one of the following:

[0461] a) Configure or indicate multiple transmission interval time information according to the bandwidth of D2R transmission, for example, the value of 180KHz bandwidth is 0~100μs, and the value of 360KHz bandwidth is 0~50μs.

[0462] b) Configure or indicate multiple transmission interval time information according to the subcarrier spacing, for example, the subcarrier spacing value of 15KHz is 0 to 100μs, and the processing delay value of R2D transmission of 30KHz subcarrier spacing is 0 to 50μs.

[0463] c) are positive integers, all within the range of 0 to 100 μs.

[0464] 6.2) For high-level configurations or physical layer indications, including at least one of the following:

[0465] 6.2.1) Direct configuration at the higher level or direct indication at the physical layer.

[0466] For example, configuration can be performed based on predefined or pre-configured results from the network side.

[0467] 6.2.2) The network side will configure itself based on the information reported by the IoT device, including at least one of the following:

[0468] a) IoT devices report based on previous transmission interval information, and the network side configures itself based on the reported transmission interval information;

[0469] b) Other IoT devices report their own transmission interval information, and the network side configures the network based on the reported transmission interval information. Other IoT devices have the same capability or the same type as this IoT device.

[0470] c) The IoT device reports transmission interval capability information, and the network side configures the transmission preparation time based on the reported capability information, including at least one of the following:

[0471] i. An IoT device reports a transmission interval time capability value, and the network side configures itself based on this capability information. For example, different transmission interval time values ​​may be predefined, and configuration is performed based on the reported capability information;

[0472] ii. The IoT device reports multiple transmission interval time capability information values, and the network side selects one of them for configuration based on the capability information.

[0473] d) IoT devices report their own type information, and the network side configures itself based on the reported type information, including at least one of the following:

[0474] i. The network side predefines or preconfigures transmission interval time information for different types of IoT devices, and configures it according to the reported type information;

[0475] ii. The network side predefines or preconfigures various transmission interval time information and selects one of them for configuration based on the reported type of information.

[0476] 6.3) Add a new 15th layer enabling parameter. When the 15th layer enabling parameter is disabled, the transmission interval time information is configured or indicated by the network side; when the 15th layer enabling parameter is enabled, the transmission interval time information is reported by the IoT device and configured or indicated by the network side.

[0477] 6.4) Add a new sixteenth layer enabling parameter. When the sixteenth layer enabling parameter is disabled, the transmission interval time information will not change through network predefined or preconfigured methods; when the sixteenth layer enabling parameter is enabled, the transmission interval time information can be modified.

[0478] 6.5) Added a new seventeenth layer enable parameter. When the seventeenth layer enable parameter is disabled, the transmission interval time is not configured; when the seventeenth layer enable parameter is enabled, the transmission interval time is configured.

[0479] 7) Timing advance information relative to R2D transmission

[0480] 7.1) For predefined or preconfigured

[0481] 7.1.1) is a single value, configured to be 0–100 μs;

[0482] 7.1.2) has multiple values, all configured in the range of 0 to 100 μs.

[0483] 7.2) For high-level configurations or physical layer indications, including at least one of the following:

[0484] 7.2.1) Configure or indicate the maximum time lead information of IoT devices relative to R2D transmission;

[0485] 7.2.2) The IoT device reports its charging time or charging capacity information, and the network side configures the time lead information relative to R2D transmission, including at least one of the following:

[0486] a) Predefine or preconfigure the time advance information relative to R2D transmission under different charging times or charging capabilities, and configure it based on the information reported by the IoT device;

[0487] b) Predefine or preconfigure multiple time advance information values ​​relative to R2D transmission, and select one of the values ​​for configuration based on the reported charging time or charging capacity information.

[0488] 7.2.3) The IoT device reports its own type information, and the network side configures itself based on the reported type information, including at least one of the following:

[0489] a) Predefine or preconfigure the time advance information relative to R2D transmission for different types of IoT devices, and configure it according to the information reported by the IoT device;

[0490] b) Predefine or preconfigure multiple time advance information relative to R2D transmission, and select one of the values ​​for configuration based on the reported IoT device type information.

[0491] 7.2.4) Add an 18th layer enabling parameter. When the 18th layer enabling parameter is disabled, the timing advance information relative to R2D transmission will not change through network predefinition or preconfiguration; when the 18th layer enabling parameter is enabled, the timing advance information relative to R2D transmission can be modified.

[0492] 7.2.5) Add a new nineteenth layer enable parameter. When the nineteenth layer enable parameter is disabled, the timing advance information relative to R2D transmission is not configured; when the nineteenth layer enable parameter is enabled, the timing advance information relative to R2D transmission is configured.

[0493] 8) Charging time information before R2D transmission

[0494] 8.1) For predefined or preconfigured

[0495] 8.1.1) is a single value, configured to be 0 to 100 μs.

[0496] 8.1.2) contains multiple values, all configured in the range of 0–100 μs, including at least one of the following:

[0497] a) Differentiate the types of IoT devices and configure them accordingly;

[0498] b) Differentiate the capabilities of IoT devices and configure them separately.

[0499] 8.2) For high-level configurations or physical layer indications, include at least one of the following:

[0500] 8.2.1) Configure or indicate the maximum charging time information before the maximum R2D transmission of IoT devices.

[0501] 8.2.2) The IoT device reports its own charging time or charging capacity information, and the network side configures the corresponding charging time information before R2D transmission, including at least one of the following:

[0502] a) Predefine or preconfigure charging time information before R2D transmission under different charging times or charging capabilities, and configure it based on the information reported by the IoT device;

[0503] b) Predefine or preconfigure multiple charging time information before R2D transmission, and select one value for configuration based on the reported charging time or charging capacity information.

[0504] 8.2.3) The IoT device reports its own type information, and the network side configures itself based on the reported type information, including at least one of the following:

[0505] a) Predefine or preconfigure charging time information before R2D transmission for different types of IoT devices, and configure it according to the information reported by the IoT devices;

[0506] b) Predefine or preconfigure multiple charging time information before R2D transmission, and select one of the values ​​for configuration based on the reported IoT device type information.

[0507] 8.2.4) Add a new 20th layer enabling parameter. When the 20th layer enabling parameter is disabled, the charging time information before R2D transmission is configured or indicated by the network side; when the 20th layer enabling parameter is enabled, the charging time information before R2D transmission is reported by the IoT device and configured or indicated by the network side.

[0508] 8.2.5) Added a new 21st high-layer enabling parameter. When the 21st high-layer enabling parameter is disabled, the charging time information before R2D transmission will no longer change through network predefinition or preconfiguration; when the 21st high-layer enabling parameter is enabled, the charging time information before R2D transmission can be modified.

[0509] 8.2.6) Added a 22nd high-layer enable parameter. When the 22nd high-layer enable parameter is disabled, the charging time information before R2D transmission is not configured; when the 22nd high-layer enable parameter is enabled, the charging time information before R2D transmission is configured.

[0510] 9) Timing advance information relative to D2R transmission

[0511] 9.1) is for predefined or preconfigured

[0512] 9.1.1) is a single value, configured to be 0–100 μs;

[0513] 9.1.2) has multiple values, all configured in the range of 0 to 100 μs.

[0514] 9.2) For high-level configurations or physical layer indications, include at least one of the following:

[0515] 9.2.1) Configure or indicate the maximum carrier wait time information for IoT devices.

[0516] 9.2.2) The IoT device reports its charging time or charging capacity information, and the network side configures the corresponding time advance information relative to D2R transmission, including at least one of the following:

[0517] a) Predefine or preconfigure the time advance information relative to D2R transmission under different charging times or charging capabilities, and configure it based on the information reported by the IoT device;

[0518] b) Predefine or preconfigure multiple time advance information relative to D2R transmission, and select one of the values ​​for configuration based on the reported charging time or charging capacity information.

[0519] 9.2.3) The IoT device reports its own type information, and the network side configures itself based on the reported type information, including at least one of the following:

[0520] a) Predefine or preconfigure the time advance information relative to D2R transmission for different types of IoT devices, and configure it based on the information reported by the IoT devices;

[0521] b) Predefine or preconfigure multiple time advance information relative to D2R transmission, and select one of the values ​​for configuration based on the reported IoT device type information.

[0522] 9.2.4) Added a new 23rd layer enabling parameter. When the 23rd layer enabling parameter is disabled, the timing advance information relative to D2R transmission will not change through network predefinition or preconfiguration; when the 23rd layer enabling parameter is enabled, the timing advance information relative to D2R transmission can be modified.

[0523] 9.2.5) Added a new 24th layer enable parameter. When the 24th layer enable parameter is disabled, the timing advance information relative to D2R transmission is not configured; when the 24th layer enable parameter is enabled, the timing advance information relative to D2R transmission is configured.

[0524] 10) Charging time information before D2R transmission

[0525] 10.1) refers to predefined or preconfigured...

[0526] 10.1.1) is a single value, configured to be 0 to 100 μs.

[0527] 10.1.2) represents multiple values, all configured in the range of 0–100 μs, including at least one of the following:

[0528] a) Differentiate the types of IoT devices and configure them accordingly;

[0529] b) Differentiate the capabilities of IoT devices and configure them separately.

[0530] 10.2) For high-level configurations or physical layer indications, include at least one of the following:

[0531] 10.2.1) Configure or indicate the maximum D2R transmission charging time information for IoT devices.

[0532] 10.2.2) The IoT device reports its own charging time or charging capacity information, and the network side configures the charging time information before D2R transmission, including at least one of the following:

[0533] a) Predefine or preconfigure charging time information before D2R transmission under different charging times or charging capabilities, and configure it based on the information reported by the IoT device;

[0534] b) Predefine or preconfigure multiple charging time information before D2R transmission, and select one of the values ​​for configuration based on the reported charging time or charging capacity information.

[0535] 10.2.3) The IoT device reports its own type information, and the network side configures itself based on the reported type information, including at least one of the following:

[0536] a) Predefine or preconfigure charging time information before D2R transmission for different types of IoT devices, and configure it according to the information reported by the IoT devices;

[0537] b) Predefine or preconfigure multiple charging time information before D2R transmission, and select one of the values ​​for configuration based on the reported IoT device type information.

[0538] 10.2.4) Added a new 25th layer enabling parameter. When the 25th layer enabling parameter is disabled, the charging time information before D2R transmission is configured or indicated by the network side; when the 25th layer enabling parameter is enabled, the charging time information before D2R transmission is reported by the IoT device and configured or indicated by the network side.

[0539] 10.2.5) Added a new 26th high-layer enabling parameter. When the 26th high-layer enabling parameter is disabled, the charging time information before D2R transmission will no longer change through network predefined or preconfigured methods; when the 26th high-layer enabling parameter is enabled, the charging time information before D2R transmission can be modified.

[0540] 10.2.6) Added a new 27th high-layer enabling parameter. When the 27th high-layer enabling parameter is disabled, the charging time information before D2R transmission is not configured; when the 27th high-layer enabling parameter is enabled, the charging time information before D2R transmission is configured.

[0541] In some embodiments, the time granularity information includes at least one of the following:

[0542] a) The time granularity information is a fixed value, for example, X time granularities;

[0543] b) The time granularity information is not greater than the first threshold or not less than the second threshold, for example, not more than or not less than X time granularities;

[0544] c) The time granularity information is within a specified time granularity range, for example, between X time granularities * 0.9 and X time granularities * 1.1;

[0545] d) The time granularity information is at least one of the following: bit, transport block, OFDM (Orthogonal Frequency Division Multiplexing) symbol, OOK chip, OFDM time slot, microsecond, sampling point, PRDCH chip, PRDCH symbol, PRDCH time slot, PRDCH sampling point, PDRCH chip, PDRCH symbol, PDRCH time slot, PDRCH sampling point, R2D chip, R2D symbol, R2D time slot, R2D sampling point, D2R chip, D2R symbol, D2R time slot, and D2R sampling point.

[0546] In some embodiments, the above configuration or indication methods further include at least one of the following:

[0547] a) Configured separately, or uniformly configured within the environmental IoT resource set, the environmental IoT media access control element, or the environmental IoT control command;

[0548] b) Configured in the form of resource sets, the network side configures or indicates the resource set identifier to be selected, so that the resource set corresponding to the resource set identifier can be selected from multiple resource sets for configuration.

[0549] In the communication method provided in the above embodiments of this disclosure, time-domain control information sent by a network-side device is received, wherein the time-domain control information includes at least one of timeline information, time-domain resource information, time interval information, and timing scheduling information; based on the time-domain control information, D2R transmission is performed with the network-side device at a first time, wherein the D2R transmission includes at least one of PDRCH, D2R control signal, synchronization signal, and reference signal transmission. By designing the timeline of the IoT device during the transmission process accordingly, the communication problem of passive IoT is effectively solved.

[0550] Figure 2 This is a schematic diagram of the structure of an Internet of Things (IoT) terminal according to an embodiment of this disclosure.

[0551] like Figure 2 As shown, the IoT terminal 20 can be represented in the form of a general computing device. The IoT terminal 20 includes a memory 21, a processor 22, and a bus 23 connecting different system components.

[0552] The memory 21 may include, for example, system memory, non-volatile storage media, etc. System memory may store, for example, an operating system, application programs, a boot loader, and other programs. System memory may include volatile storage media, such as random access memory (RAM) and / or cache memory. Non-volatile storage media may store, for example, instructions for a corresponding embodiment of at least one communication method being executed. Non-volatile storage media include, but are not limited to, disk storage, optical storage, flash memory, etc.

[0553] Processor 22 can be implemented using a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic devices, discrete hardware components such as discrete gates or transistors. Accordingly, each module, such as the acquisition module, calculation module, and adjustment module, can be implemented by executing instructions in the central processing unit (CPU) running memory to perform the corresponding steps, or by implementing dedicated circuitry to perform the corresponding steps.

[0554] For example, processor 22 is configured as a memory-based instruction execution implementation such as Figure 1 The method involved in any of the embodiments.

[0555] Bus 23 can use any of the various bus architectures. For example, bus architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MCA) bus, and the Peripheral Component Interconnect (PCI) bus.

[0556] The interfaces 24, 25, and 26 of the IoT terminal 20, as well as the memory 21 and processor 22, can be connected via bus 23. Input / output interface 24 provides a connection interface for input / output devices such as displays, mice, and keyboards. Network interface 25 provides a connection interface for various networked devices. Storage interface 26 provides a connection interface for external storage devices such as floppy disks, USB flash drives, and SD cards.

[0557] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus, and computer program products according to embodiments of this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations thereof, can be implemented by computer-readable program instructions.

[0558] These computer-readable program instructions are provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable device to produce a machine, such that execution of the instructions by the processor produces means for implementing the functions specified in one or more boxes of the flowchart and / or block diagram.

[0559] These computer-readable program instructions may also be stored in a computer-readable storage medium. These instructions cause a computer to work in a particular manner to produce an article of manufacture, including instructions that implement the functions specified in one or more boxes in a flowchart and / or block diagram.

[0560] This disclosure may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects.

[0561] This disclosure also provides a computer-readable storage medium storing computer instructions that, when executed by a processor, implement... Figure 1 The method involved in any of the embodiments.

[0562] This disclosure also provides a computer program product, including computer instructions, wherein the computer instructions, when executed by a processor, implement as follows: Figure 1 The method involved in any of the embodiments.

[0563] The following specific examples illustrate this disclosure. It should be noted that "device" in this document refers to an Internet of Things (IoT) device.

[0564] Example 1:

[0565] The time interval T from the last time granularity of the previous R2D transmission to the first time granularity of this D2R transmission R2D ,like Figure 3 As shown.

[0566] like Figure 3 As shown, starting from the last moment after the R2D transmission ends, the next D2R transmission for that R2D transmission can begin at either the earliest or latest possible moment. The time interval between the earliest D2R transmission and the start moment is considered to be T. R2D_min The time interval between the latest D2R transmission time and the start time is considered to be T. R2D_max， The start time of the D2R transmission will be located at [T R2D_min T R2D_max Between ] . This scheme is generally used in scenarios where an R2D control signal is sent, and its control signal triggers a D2R transmission.

[0567] Example 2:

[0568] The time interval T from the last time granularity of the previous R2D transmission to the first time granularity of this D2R transmission R2D ,like Figure 4 As shown.

[0569] like Figure 4As shown, starting from the last moment of the R2D transmission, compared to Example 1, the earliest and latest two possible moments are no longer defined, but T is directly configured or indicated. R2D The value is used to inform the device of the theoretically accurate time to send a D2R transmission, thus avoiding too frequent collisions when multiple devices are transmitting simultaneously. This scheme is generally used in scenarios where a D2R transmission is triggered by a control signal sent after an R2D control signal is sent.

[0570] Example 3:

[0571] The time interval T from the last time granularity of the previous D2R transmission to the first time granularity of this D2R transmission D2R_D2R ,like Figure 5 As shown.

[0572] like Figure 5 As shown, starting from the last moment of the D2R transmission, the next D2R transmission can begin at either the earliest or latest possible moment. The time interval between the earliest D2R transmission and the start moment is considered to be T. D2R_D2R_min The time interval between the latest D2R transmission time and the start time is considered to be T. D2R_D2R_max， The start time of the D2R transmission will be located at [T D2R_D2R_min T D2R_D2R_max This scheme is generally used when, after an R2D transmission, the decoding of the R2D takes a long time and a response cannot be made within the predetermined time range. Therefore, multiple D2R transmissions are sent to indicate that the device is still processing and a delayed response will be made.

[0573] Example 4:

[0574] The time interval T from the last time granularity of the previous D2R transmission to the first time granularity of this D2R transmission D2R_D2R ,like Figure 6 As shown.

[0575] like Figure 6 As shown, starting from the last moment of the D2R transmission, compared to Embodiment 3, instead of defining the earliest and latest possible moments, the system directly configures or indicates the precise time theoretically required between two D2R transmissions. This informs the device of the precise moment when sending D2R transmission 2, avoiding frequent collisions caused by delayed responses from multiple devices. This scheme is generally used when, after an R2D transmission, decoding the R2D requires a long time and a response cannot be made within the predetermined time range. Therefore, multiple D2R transmissions are sent to indicate that the device is still processing and will respond with a delay.

[0576] Example 5:

[0577] The time interval information T from the first time granularity sent at the start of CW to the first time granularity of this D2R transmission. CW_D2R ,like Figure 7 As shown.

[0578] like Figure 7 As shown, this time interval is primarily used to consider how far in advance CW should be transmitted before D2R. Therefore, if the start time is still taken as the end time of CW, it would require D2R transmission to occur within a certain time after CW transmission is completed. This is unreasonable because the ideal situation is that D2R transmission should begin immediately after CW completes device charging. Therefore, the time between CW and D2R transmission should be kept as short as possible to ensure the continuity of D2R transmission. However, if it is too short, the base station will transmit CW for an extended period, resulting in energy waste and potential interference. Therefore, this indicator is designed.

[0579] The time interval between the earliest D2R transmission and the start of CW is considered to be T. CW_D2R_min The time interval between the latest D2R transmission time and the start time of CW is considered to be T. CW_D2R_max， The time interval between CW and R2D will be located in [T CW_D2R_min T CW_D2R_max ]between.

[0580] Example 6:

[0581] The time interval information T from the first time granularity sent at the start of CW to the first time granularity of this D2R transmission. CW_D2R ,like Figure 8 As shown.

[0582] like Figure 8 As shown, this time interval is primarily used to consider how far in advance CW should be transmitted before D2R. Therefore, if the start time is still taken as the end time of CW, it would require D2R transmission to occur within a certain time after CW transmission is completed. This is unreasonable because the ideal situation is that D2R transmission should begin immediately after CW completes device charging. Therefore, the time between CW and D2R transmission should be kept as short as possible to ensure the continuity of D2R transmission. However, if it is too short, the base station will transmit CW for an extended period, resulting in energy waste and potential interference. Therefore, this indicator is designed.

[0583] Unlike Embodiment 5, Embodiment 6 does not define the earliest and latest transmission times. Instead, it configures or indicates an accurate value on the network side to ensure that the CW carrier arrives at the device side as on time as possible. This approach is more efficient but requires more accurate and complex signaling interactions.

[0584] Example 7:

[0585] T R2D Possible components such as Figure 9 As shown.

[0586] like Figure 9 As shown, T R2D It may consist of five parts. The first and foremost element is transmission delay, which is an objective reality and is also known as T. R2D The main components of the delay are: This delay may be predefined or preconfigured, or it may be configured separately based on the device's capabilities or measurement results to meet the accuracy of personalized transmission and avoid excessive transmission delay. After experiencing the transmission delay, the R2D transmission is received by the device. At this point, there may be a device processing delay for decoding the R2D data. However, it may not be defined or configured separately, but rather considered in the transmission preparation delay, i.e., this part of the delay is not considered separately. The third part is the D2R preparation delay, which is mainly the time that must be waited between receiving the information and sending the corresponding R2D transmission, including R2D command parsing and preparing the corresponding information based on the next D2R transmission. If there is no carrier waiting delay, it may also include modulation processing time. The fourth part is the carrier waiting delay, used in scenarios where the CW carrier has not yet been transmitted, or the device is in a charging state, resulting in waiting for CW. This delay may be included in the D2R transmission preparation delay and not defined separately, or it may be configured separately. The fifth part is the modulation time, which mainly depends on the fourth part. If the fourth part is not defined separately, the fifth part will not be defined separately either, but will be included entirely within the preparation time; if the fourth part is defined or configured separately, then the latency of the fifth part will also need to be defined or configured separately.

[0587] Example 8:

[0588] T D2R_D2R Composition such as Figure 10 As shown.

[0589] like Figure 10 As shown, T D2R_D2R The configuration does not involve the transmission delay and processing delay of R2D, so it only includes the transmission preparation delay, carrier waiting delay, and modulation delay. If the carrier can arrive early or on time, separate configuration may not be required.

[0590] Example 9:

[0591] T CW_D2R Composition such as Figure 11 As shown.

[0592] like Figure 11 As shown, to define the time advance relative to D2R transmission, the time advance information of the CW carrier relative to R2D transmission can be calculated. Thus, if it is necessary to calculate the advance time required for CW relative to the target D2R transmission, this can be obtained from T... CW_D2R Then, by using the time length of R2D and T R2D The value is used to obtain the time advance relative to D2R transmission. The calculation method is: time advance relative to R2D transmission + duration of R2D + T R2D Once this time information is obtained, it can be ensured that D2R transmission does not need to wait too long for the CW carrier, or transmission can be carried out directly.

[0593] Example 10:

[0594] T CW_D2R Composition such as Figure 12 As shown.

[0595] like Figure 12 As shown, to define the time advance relative to D2R transmission, the time advance information of the CW carrier when it is received on the device side relative to R2D transmission can be calculated. Thus, if it is necessary to calculate the advance time required for CW relative to the target D2R transmission, this can be obtained from T... CW_D2R Then, by using the time length of R2D and T R2D The value is used to obtain the time advance relative to D2R transmission. Considering that receiving R2D transmissions may require advance charging to activate the device, the calculation method is: time advance relative to R2D transmission + R2D duration + transmission preparation time, or time advance relative to D2R transmission + R2D charging time + R2D duration + transmission preparation time. Having this time information ensures that D2R transmission does not need to wait too long for the CW carrier, or that transmission can proceed directly.

[0596] Example 11:

[0597] T CW_D2R Composition such as Figure 13 As shown.

[0598] like Figure 13 As shown, to define the time advance relative to D2R transmission, the time advance information of the CW carrier relative to D2R transmission can be calculated. Considering that D2R transmission may require advance charging to activate the device, the calculation method is: the time advance relative to D2R transmission, or the time advance relative to D2R transmission + R2D charging time. Having this time information ensures that D2R transmission does not need to wait too long for the CW carrier, or that transmission can proceed directly.

[0599] In some embodiments, the functional units described above may be implemented as general-purpose processors, programmable logic controllers (PLCs), digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof for performing the functions described herein.

[0600] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0601] The description in this disclosure is provided for illustrative and descriptive purposes only and is not intended to be exhaustive or to limit the disclosure to its forms. Many modifications and variations will be apparent to those skilled in the art. The embodiments were chosen and described in order to better illustrate the principles and practical application of this disclosure and to enable those skilled in the art to understand this disclosure and to design various embodiments with various modifications suitable for a particular purpose.

Claims

1. A communication method applied to Internet of Things (IoT) devices, comprising: Receive time-domain control information sent by a network-side device, wherein the time-domain control information includes at least one of timeline information, time-domain resource information, time interval information, and timing scheduling information; Based on the time-domain control information, IoT device-to-network device (D2R) transmission is performed with the network-side device at the first time, wherein the D2R transmission includes the transmission of at least one of the physical layer transmission channel PDRCH, D2R control signal, synchronization signal and reference signal on the D2R link.

2. The communication method according to claim 1, wherein, The first time includes at least one of the following: The maximum time interval T from the last time granularity of the previous network-side device's R2D transmission to the end of the IoT device's R2D transmission to the first time granularity of the D2R transmission. R2D_max The minimum time interval T from the last time granularity of the previous R2D transmission to the first time granularity of the D2R transmission. R2D_min The time interval T from the last time granularity of the previous R2D transmission to the first time granularity of the D2R transmission. R2D The minimum time interval T from the last time granularity of the previous D2R transmission to the first time granularity of the D2R transmission. D2R_D2R_min The maximum time interval T from the last time granularity of the previous D2R transmission to the first time granularity of the D2R transmission. D2R_D2R_max The time interval T from the last time granularity of the previous D2R transmission to the first time granularity of the D2R transmission. D2R_D2R The maximum time interval T from the first time granularity of carrier CW transmission to the first time granularity of the D2R transmission. CW_D2R_max The minimum time interval T from the first time granularity of carrier CW transmission to the first time granularity of D2R transmission. CW_D2R_min The time interval T from the first time granularity of carrier CW transmission to the first time granularity of D2R transmission. CW_D2R .

3. The communication method according to claim 2, wherein, The first time is predefined, preconfigured, high-level configured, or indicated by the physical layer.

4. The communication method according to claim 3, wherein, The maximum time interval T R2D_max Includes one or more values; In the maximum time interval T R2D_max In the case of multiple values, the multiple values ​​are determined by at least one of the following: The bandwidth configuration or indication of the multiple values ​​are based on D2R or R2D transmission; The multiple values ​​are configured or indicated according to the subcarrier spacing; The multiple values ​​can be configured or indicated directly.

5. The communication method according to claim 3, wherein, The minimum time interval T R2D_min Includes one or more values; In the minimum time interval T R2D_min In the case of multiple values, the multiple values ​​are determined by at least one of the following: The bandwidth configuration or indication of the multiple values ​​are based on D2R or R2D transmission; The multiple values ​​are configured or indicated according to the subcarrier spacing; The multiple values ​​can be configured or indicated directly.

6. The communication method according to claim 3, wherein, The time interval T R2D Includes one or more values; In the time interval T R2D In the case of multiple values, the multiple values ​​are determined by at least one of the following: The bandwidth configuration or indication of the multiple values ​​are based on D2R or R2D transmission; The multiple values ​​are configured or indicated according to the subcarrier spacing; The multiple values ​​can be configured or indicated directly.

7. The communication method according to claim 3, wherein, The minimum time interval T D2R_D2R_min Includes one or more values; In the minimum time interval T D2R_D2R_min In the case of multiple values, the multiple values ​​are determined by at least one of the following: The bandwidth configuration or indication of the multiple values ​​are based on D2R or R2D transmission; The multiple values ​​are configured or indicated according to the subcarrier spacing; The multiple values ​​can be configured or indicated directly.

8. The communication method according to claim 3, wherein, The maximum time interval T D2R_D2R_max Includes one or more values; In the maximum time interval T D2R_D2R_max In the case of multiple values, the multiple values ​​are determined by at least one of the following: The bandwidth configuration or indication of the multiple values ​​are based on D2R or R2D transmission; The multiple values ​​are configured or indicated according to the subcarrier spacing; The multiple values ​​can be configured or indicated directly.

9. The communication method according to claim 3, wherein, The time interval T D2R_D2R Includes one or more values; In the time interval T D2R_D2R In the case of multiple values, the multiple values ​​are determined by at least one of the following: The bandwidth configuration or indication of the multiple values ​​are based on D2R or R2D transmission; The multiple values ​​are configured or indicated according to the subcarrier spacing; The multiple values ​​can be configured or indicated directly.

10. The communication method according to claim 3, wherein, The maximum time interval T CW_D2R_max Includes one or more values; In the maximum time interval T CW_D2R_max In the case of multiple values, the multiple values ​​are determined by at least one of the following: The bandwidth configuration or indication of the multiple values ​​are based on D2R or R2D transmission; The multiple values ​​are configured or indicated according to the subcarrier spacing; The multiple values ​​can be configured or indicated directly.

11. The communication method according to claim 3, wherein, The minimum time interval T CW_D2R_min Includes one or more values; In the minimum time interval T CW_D2R_min In the case of multiple values, the multiple values ​​are determined by at least one of the following: The bandwidth configuration or indication of the multiple values ​​are based on D2R or R2D transmission; The multiple values ​​are configured or indicated according to the subcarrier spacing; The multiple values ​​can be configured or indicated directly.

12. The communication method according to claim 3, wherein, The time interval T CW_D2R Includes one or more values; In the time interval T CW_D2R In the case of multiple values, the multiple values ​​are determined by at least one of the following: The bandwidth configuration or indication of the multiple values ​​are based on D2R or R2D transmission; The multiple values ​​are configured or indicated according to the subcarrier spacing; The multiple values ​​can be configured or indicated directly.

13. The communication method according to claim 3, wherein, The higher-level configuration or physical layer indication includes at least one of the following: High-level configuration or physical layer instructions can be directly performed from the network side. The configuration is performed by the network side based on the information reported by the IoT devices; When the first high-layer enabling parameter is disabled, the first time is configured or indicated by the network side; when the first high-layer enabling parameter is enabled, the first time is configured or indicated by the network side based on the information reported by the IoT device. When the second high-level enabling parameter is disabled, the first time will not be changed through network predefined or preconfiguration. With the second high-level enabling parameter enabled, the first-time information can be modified; When the third high-level enabling parameter is disabled, no configuration is performed immediately; when the third high-level enabling parameter is enabled, configuration or indication is allowed immediately.

14. The communication method according to claim 13, wherein, High-level configuration or physical layer instructions directly performed from the network side include at least one of the following: Configure based on short-range measurement results from the network side; Configure according to the predefined or preconfigured results on the network side; According to the T reported by the network side for the previous D2R transmissions of the IoT device R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R Configure at least one of them; Configure the measurement results of other IoT devices through the network side.

15. The communication method according to claim 14, wherein, The direct high-level configuration or physical layer instruction from the network side also includes: Configure time offset; Based on the close-range measurement results from the network side, a first raw time is obtained. Based on the first raw time and the time offset, the first time is obtained and configured. Alternatively, based on the results of predefined or preconfigured information on the network side, a second original time can be obtained, and the first time can be obtained and configured based on the second original time and the time offset. Alternatively, based on the T data reported by the network side regarding previous D2R transmissions of IoT devices. R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R At least one of them, a third original time is obtained, and the first time is obtained and configured based on the third original time and the time offset; Alternatively, based on the network side's measurement results of other IoT devices, a fourth raw time can be obtained, and based on the fourth raw time and the time offset, the first time can be obtained and configured.

16. The communication method according to claim 14, wherein, The direct high-level configuration or physical layer instruction from the network side also includes: Configure time coefficients; Based on the close-range measurement results from the network side, a first raw time is obtained. Based on the first raw time and the time coefficient, the first time is obtained and configured. Alternatively, based on the results of predefined or preconfigured information on the network side, a second original time is obtained, and based on the second original time and the time coefficient, the first time is obtained and configured. Alternatively, based on the T data reported by the network side regarding previous D2R transmissions of IoT devices. R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R At least one of them, a third original time is obtained, and the first time is obtained and configured based on the third original time and the time coefficient; Alternatively, based on the measurement results of other IoT devices by the network side, a fourth raw time can be obtained, and the first time can be obtained and configured based on the fourth raw time and the time coefficient.

17. The communication method according to claim 13, wherein, The configuration by the network side based on the information reported by the IoT devices includes at least one of the following: The IoT device is based on the previous or earlier T R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R At least one of them must be reported so that the network side can make the configuration; Other IoT devices according to T R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R At least one of them must be reported so that the network side can make the configuration; The IoT device reports its own T R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R The network side needs to provide at least one of the capability information so that it can configure itself based on the reported capability information. The IoT device reports its own type information so that the network side can configure itself based on the reported type information.

18. The communication method according to claim 17, wherein, The configuration by the network side based on the information reported by the IoT devices also includes: Configure time offset; According to the T reported by the IoT device R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R At least one of them, to obtain a fifth original time, and based on the fifth original time and the time offset, to obtain the first time and configure it; Alternatively, based on T reported by other IoT devices R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R At least one of them, a sixth original time is obtained, and based on the sixth original time and the time offset, the first time is obtained and configured; Or, the T reported by the IoT device R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R Based on the capability information of at least one of them, a seventh original time is obtained, and based on the seventh original time and the time offset, the first time is obtained and configured. Alternatively, based on the type information reported by the IoT device, an eighth original time is obtained, and based on the eighth original time and the time offset, the first time is obtained and configured.

19. The communication method according to claim 17, wherein, The configuration by the network side based on the information reported by the IoT devices also includes: Configure time coefficients; According to the T reported by the IoT device R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R At least one of them, a fifth original time is obtained, and based on the fifth original time and the time coefficient, the first time is obtained and configured; Alternatively, based on T reported by other IoT devices R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R At least one of them, to obtain a sixth original time, and based on the sixth original time and the time coefficient, to obtain the first time and configure it; Or, the T reported by the IoT device R2D_max T R2D_min T R2D T D2R_D2R_min T D2R_D2R_max T D2R_D2R T CW_D2R_max T CW_D2R_min T CW_D2R Based on the capability information of at least one of them, a seventh original time is obtained, and based on the seventh original time and the time coefficient, the first time is obtained and configured. Alternatively, based on the type information reported by the IoT device, an eighth original time is obtained, and based on the eighth original time and the time coefficient, the first time is obtained and configured.

20. The communication method according to claim 3, wherein, The manner in which the higher-level configuration or physical layer indication is made includes at least one of the following: Configuring via the Media Access Control (MAC) layer or a new layer does not require physical layer instructions; Instructions are given through the physical layer, eliminating the need for configuration of the MAC layer or any new layers. Configuration is performed through the MAC layer or a new layer, with instructions provided by the physical layer.

21. The communication method according to claim 20, wherein, In the case where the configuration is performed via the MAC layer or a new layer, and the physical layer provides instructions, at least one of the following is included: The MAC layer configures some of the first-time parameters, and the physical layer indicates some of the first-time parameters; The MAC layer configures the enable information of the first time parameter, and the physical layer indicates the corresponding first time parameter information based on the enable information of the first time parameter.

22. The communication method according to claim 2, wherein, The maximum time interval T R2D_max Includes at least one of the following: timing advance (TA) information or transmission delay information, carrier wait time information, R2D transmission processing delay information, transmission preparation time information, and modulation time information; The carrier waiting time information includes at least one of R2D carrier waiting time information and D2R carrier waiting time information. The R2D carrier waiting time information includes at least one of charging time information and carrier arrival time information. The D2R carrier waiting time information includes at least one of charging time information and carrier arrival time information.

23. The communication method according to claim 22, wherein, The maximum time interval T R2D_max The composition includes at least one of the following: TA information or transmission delay information; TA information or transmission delay information + R2D transmission processing delay information; TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information; TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information + carrier wait time information; TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information + carrier wait time information + modulation time information; TA information or transmission delay information + transmission preparation time information; TA information or transmission delay information + transmission preparation time information + carrier wait time information; TA information or transmission delay information + transmission preparation time information + carrier wait time information + modulation time information; TA information or transmission delay information + carrier wait time information; TA information or transmission delay information + carrier wait time information + modulation time information.

24. The communication method according to claim 2, wherein, The minimum time interval T R2D_min Includes at least one of the following: TA information or transmission delay information, carrier wait time information, R2D transmission processing delay information, transmission preparation time information, D2R carrier wait time information and modulation time information; The carrier waiting time information includes at least one of R2D carrier waiting time information and D2R carrier waiting time information. The R2D carrier waiting time information includes at least one of charging time information and carrier arrival time information. The D2R carrier waiting time information includes at least one of charging time information and carrier arrival time information.

25. The communication method according to claim 24, wherein, The minimum time interval T R2D_min The composition includes at least one of the following: TA information or transmission delay information; TA information or transmission delay information + R2D transmission processing delay information; TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information; TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information + carrier wait time information; TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information + carrier wait time information + modulation time information; TA information or transmission delay information + transmission preparation time information; TA information or transmission delay information + transmission preparation time information + carrier wait time information; TA information or transmission delay information + transmission preparation time information + carrier wait time information + modulation time information; TA information or transmission delay information + carrier wait time information; TA information or transmission delay information + carrier wait time information + modulation time information.

26. The communication method according to claim 2, wherein, The time interval T R2D Includes at least one of the following: TA information or transmission delay information, carrier wait time information, R2D transmission processing delay information, transmission preparation time information, and modulation time information; The carrier waiting time information includes at least one of R2D carrier waiting time information and D2R carrier waiting time information. The R2D carrier waiting time information includes at least one of charging time information and carrier arrival time information. The D2R carrier waiting time information includes at least one of charging time information and carrier arrival time information.

27. The communication method according to claim 26, wherein, The time interval T R2D The composition includes at least one of the following: TA information or transmission delay information; TA information or transmission delay information + R2D transmission processing delay information; TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information; TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information + carrier wait time information; TA information or transmission delay information + R2D transmission processing delay information + transmission preparation time information + carrier wait time information + modulation time information; TA information or transmission delay information + transmission preparation time information; TA information or transmission delay information + transmission preparation time information + carrier wait time information; TA information or transmission delay information + transmission preparation time information + carrier wait time information + modulation time information; TA information or transmission delay information + carrier wait time information; TA information or transmission delay information + carrier wait time information + modulation time information.

28. The communication method according to claim 2, wherein, The minimum time interval T D2R_D2R_min Includes at least one of the following: transmission interval time information or transmission preparation time information, carrier wait time information, and modulation time information.

29. The communication method according to claim 28, wherein, The minimum time interval T D2R_D2R_min The composition includes at least one of the following: Transmission interval information or transmission preparation time information; Transmission interval time information or transmission preparation time information + carrier wait time information; Transmission interval time information or transmission preparation time information + carrier wait time information + modulation time information.

30. The communication method according to claim 2, wherein, The maximum time interval T D2R_D2R_max Includes at least one of the following: transmission interval time information or transmission preparation time information, carrier wait time information, and modulation time information.

31. The communication method according to claim 30, wherein, The maximum time interval T D2R_D2R_max The composition includes at least one of the following: Transmission interval information or transmission preparation time information; Transmission interval time information or transmission preparation time information + carrier wait time information; Transmission interval time information or transmission preparation time information + carrier wait time information + modulation time information.

32. The communication method according to claim 2, wherein, The time interval T D2R_D2R Includes at least one of the following: transmission interval time information or transmission preparation time information, carrier wait time information, and modulation time information.

33. The communication method according to claim 32, wherein, The time interval T D2R_D2R The composition includes at least one of the following: Transmission interval information or transmission preparation time information; Transmission interval time information or transmission preparation time information + carrier wait time information; Transmission interval time information or transmission preparation time information + carrier wait time information + modulation time information.

34. The communication method according to claim 2, wherein, The maximum time interval T CW_D2R_max Includes at least one of the following: time advance information relative to R2D transmission, charging time information before R2D transmission, time advance information relative to D2R transmission, and charging time information before D2R transmission.

35. The communication method according to claim 34, wherein, The maximum time interval T CW_D2R_max The composition includes at least one of the following: The time advance information relative to R2D transmission; The time lead information relative to R2D transmission + the charging time information before R2D transmission; Time advance information relative to D2R transmission; Information on the time lead time relative to D2R transmission + charging time information before D2R transmission.

36. The communication method according to claim 2, wherein, The minimum time interval T CW_D2R_min Includes at least one of the following: time advance information relative to R2D transmission, charging time information before R2D transmission, time advance information relative to D2R transmission, and charging time information before D2R transmission.

37. The communication method according to claim 36, wherein, The minimum time interval TCW_D2R_min is composed in a manner that includes at least one of the following: The time advance information relative to R2D transmission; The time lead information relative to R2D transmission + the charging time information before R2D transmission; Time advance information relative to D2R transmission; Information on the time lead time relative to D2R transmission + charging time information before D2R transmission.

38. The communication method according to claim 2, wherein, The time interval T CW_D2R Includes at least one of the following: time advance information relative to R2D transmission, charging time information before R2D transmission, time advance information relative to D2R transmission, and charging time information before D2R transmission.

39. The communication method according to claim 38, wherein, The time interval T CW_D2R The composition includes at least one of the following: The time advance information relative to R2D transmission; The time lead information relative to R2D transmission + the charging time information before R2D transmission; Time advance information relative to D2R transmission; Information on the time lead time relative to D2R transmission + charging time information before D2R transmission.

40. The communication method according to any one of claims 22-39, wherein, At least one of the following is pre-configured, pre-defined, higher-layer configured, or physically layer indicated: the TA information or transmission delay information, the R2D transmission processing delay information, the transmission preparation time information, the carrier waiting time information, the modulation time information, and the transmission interval time information.

41. The communication method according to claim 40, wherein, When the TA information or transmission delay information is predefined or preconfigured, the TA information or transmission delay information includes one or more values; When the TA information or transmission delay information is a higher-layer configuration or physical layer indication, the TA information or transmission delay information is determined by at least one of the following: It can be configured directly by the upper layer or indicated directly by the physical layer. The information is reported through the IoT device, and the network side configures the system based on the reported information. When the fourth layer enable parameter is disabled, the TA information or transmission delay information is configured or indicated by the network side. When the fourth layer enable parameter is enabled, the TA information or transmission delay information is reported by the IoT device so that the network side can configure or indicate it. When the fifth layer enable parameter is disabled, the TA information or transmission delay information will not change through network definition or configuration. When the fifth layer enable parameter is enabled, the TA information or transmission delay information can be modified.

42. The communication method according to claim 41, wherein, The direct configuration by the higher layer or direct indication by the physical layer includes at least one of the following: Configure based on short-range measurement results from the network side; Configure according to the predefined or preconfigured results on the network side; Configure the network based on the results of previous D2R transmissions reported by the IoT device. Configure based on the network side's measurement results of other IoT devices; Configure based on the network side's reporting results to user devices.

43. The communication method according to claim 42, wherein, The direct configuration by the higher layer or direct indication by the physical layer also includes: Configure time offset; Based on the network-side close-range measurement results, a ninth original time is obtained. Based on the ninth original time and the time offset, the first time is obtained and configured. Alternatively, the tenth original time can be obtained by configuring according to the predefined or preconfigured results on the network side, and the first time can be obtained and configured based on the tenth original time and the time offset. Alternatively, the network side can configure the eleventh original time based on the results of previous D2R transmissions reported by the IoT device, and then obtain the first time based on the eleventh original time and the time offset, and configure it accordingly. Alternatively, the twelfth original time can be obtained by configuring the network side based on the measurement results of other IoT devices, and the first time can be obtained and configured based on the twelfth original time and the time offset. Alternatively, the network can configure the system based on the results reported to the user equipment to obtain the thirteenth original time. Based on the thirteenth original time and the time offset, the first time can be obtained and configured.

44. The communication method according to claim 42, wherein, The direct configuration by the higher layer or direct indication by the physical layer also includes: Configure time coefficients; Based on the network-side close-range measurement results, a ninth original time is obtained. Based on the ninth original time and the time coefficient, the first time is obtained and configured. Alternatively, the tenth original time can be obtained by configuring according to the predefined or preconfigured results on the network side, and the first time can be obtained and configured based on the tenth original time and the time coefficient. Alternatively, the network side can configure the eleventh original time based on the results of previous D2R transmissions reported by the IoT device, and then obtain and configure the first time based on the eleventh original time and the time coefficient. Alternatively, the twelfth original time can be obtained by configuring the network side based on the measurement results of other IoT devices, and the first time can be obtained and configured based on the twelfth original time and the time coefficient. Alternatively, the network side can configure the thirteenth original time based on the reported results of the user equipment, and then obtain the first time based on the thirteenth original time and the time coefficient, and configure it accordingly.

45. The communication method according to claim 41, wherein, The reporting via the IoT device, and the configuration by the network side based on the reported information, includes at least one of the following: The IoT device reports the TA information or transmission delay information from the previous or previous D2R transmission so that the network side can configure itself based on the reported information. Other IoT devices report TA information or transmission latency information so that the network side can configure the IoT devices. The IoT device's ability to report its own TA information or transmission latency information is used to configure the network side based on the reported capability information; IoT devices report their type information so that the network side can configure them based on the reported type information.

46. ​​The communication method according to claim 40, wherein, When the processing delay information of the R2D transmission is predefined or preconfigured, the processing delay information of the R2D transmission includes one or more values; When the processing latency information of the R2D transmission is a higher-layer configuration or a physical layer indication, the processing latency information of the R2D transmission is determined by at least one of the following: It can be configured directly by the upper layer or indicated directly by the physical layer. The information is reported through the IoT device, and the network side configures the system based on the reported information. When the sixth layer enable parameter is disabled, the processing latency of R2D transmission is configured or indicated by the network side; when the sixth layer enable parameter is enabled, the processing latency of R2D transmission is reported by the IoT device and configured or indicated by the network side. When the enabling parameter of the seventh layer is disabled, the processing latency of R2D transmission no longer changes through network predefinition or preconfiguration. When the seventh high-layer enable parameter is enabled, the processing latency of R2D transmission can be modified; When the eighth layer enable parameter is disabled, R2D transmission delay is not configured; when the eighth layer enable parameter is enabled, R2D transmission delay is configured.

47. The communication method according to claim 46, wherein, The reporting via IoT devices, and the configuration of the network side based on the reported information, includes at least one of the following: The IoT device reports based on the previous R2D processing delay, so that the network side can configure itself based on the reported information; Other IoT devices report their R2D processing latency so that the network side can configure itself based on the reported information; The IoT device reports its R2D processing latency capability information so that the network side can configure itself based on the reported capability information; The IoT device reports its own type information so that the network side can configure itself based on the reported type information.

48. The communication method according to claim 40, wherein, When the transmission preparation time information is predefined or preconfigured, the transmission preparation time information includes one or more values; When the transmission preparation time information is a higher-layer configuration or a physical layer indication, the transmission preparation time information is determined by at least one of the following: It can be configured directly by the upper layer or indicated directly by the physical layer. The information is reported through the IoT device so that the network side can configure itself based on the reported information. The IoT device reports its transmission preparation time capability information so that the network side can configure the transmission preparation time based on the reported capability information. The IoT device reports its own species information so that the network side can configure itself based on the reported species information.

49. The communication method according to claim 48, further comprising: When the ninth high-layer enable parameter is disabled, the transmission preparation time information is configured or indicated by the network side. When the ninth high-layer enabling parameter is enabled, the transmission preparation time information is reported by the IoT side device so that the network side can configure or instruct it. When the enabling parameter of the tenth layer is disabled, the transmission preparation time information will not change through network predefinition or preconfiguration. When the tenth layer enable parameter is enabled, the transmission preparation time information can be modified; If the eleventh layer enable parameter is disabled, the transmission preparation time information is not configured; if the eleventh layer enable parameter is enabled, the transmission preparation time information is configured.

50. The communication method according to claim 40, wherein, When the modulation time information is predefined or preconfigured, the modulation time information includes one or more values; When the modulation timing information is a higher-layer configuration or a physical layer indication, the modulation timing information is determined by at least one of the following: The information is reported through the IoT device, and the network side configures the system based on the reported information. When the twelfth layer enable parameter is deactivated, the modulation timing information is not configured; when the twelfth layer enable parameter is enabled, the modulation timing information is configured.

51. The communication method according to claim 50, wherein, The reporting via the IoT device, and the configuration by the network side based on the reported information, includes at least one of the following: The IoT device reports its modulation scheme, and the network side configures it based on the reported modulation scheme. The IoT device reports its own capability information values, and the network side configures the device based on the reported capability information values. The IoT device reports its own type information, and the network side configures itself based on the reported type information.

52. The communication method according to claim 40, wherein, When the carrier wait time information is predefined or preconfigured, the carrier wait time information includes one or more values; When the carrier latency information is a higher-layer configuration or a physical layer indication, the carrier latency information is determined by at least one of the following: Configure or indicate the maximum carrier latency information of the IoT device; The IoT device reports its charging time or charging capacity information, and the network side configures the corresponding carrier waiting time information. The IoT device reports its own type information, and the network side configures itself based on the reported type information. When the 13th layer enable parameter is disabled, the carrier latency remains unchanged through network predefined or preconfigured methods; when the 13th layer enable parameter is enabled, the carrier latency can be modified. When the fourteenth high-layer enable parameter is disabled, the carrier wait time is not configured; When the fourteenth high-layer enable parameter is enabled, the carrier wait time is configured.

53. The communication method according to claim 40, wherein, When the transmission interval is predefined or preconfigured, the transmission interval includes one or more values; When the transmission interval is configured by a higher layer or indicated by a physical layer, the transmission interval includes at least one of the following: Through direct configuration at the higher level or direct instruction at the physical layer; The information is reported by the IoT device, and the network side configures the device based on the reported information.

54. The communication method according to claim 53, wherein, The configuration by the network side based on the reported information, which is reported through the IoT device, includes at least one of the following: The IoT device reports based on the previous transmission interval information, and the network side configures itself based on the reported transmission interval information. Other IoT devices report their own transmission interval information, and the network side configures the network based on the reported transmission interval information. The IoT device reports transmission interval time capability information, and the network side configures the transmission preparation time based on the reported capability information; The IoT device reports its own type information, and the network side configures itself based on the reported type information.

55. The communication method according to claim 53, wherein, When the fifteenth layer enable parameter is disabled, the transmission interval time information is configured or indicated by the network side; when the fifteenth layer enable parameter is enabled, the transmission interval time information is reported by the IoT device and configured or indicated by the network side. When the sixteenth high-layer enable parameter is disabled, the transmission interval time information remains unchanged through network predefined or preconfigured methods. When the sixteenth high-layer enable parameter is enabled, the transmission interval time information can be modified; When the seventeenth high-level enable parameter is disabled, the transmission interval time is not configured; When the seventeenth high-layer enable parameter is enabled, the transmission interval time is configured.

56. The communication method according to claim 40, wherein, When the time advance information relative to R2D transmission is predefined or preconfigured, the time advance information relative to R2D transmission includes one or more values; When the timing advance information relative to R2D transmission is a higher-layer configuration or a physical layer indication, the timing advance information relative to R2D transmission is determined by at least one of the following: Configure or indicate the maximum time advance information relative to R2D transmission for the IoT device; The IoT device reports its own charging time or charging capacity information, and the network side configures the time advance information relative to R2D transmission. The IoT device reports its own type information, and the network side configures itself based on the reported type information. When the 18th layer enable parameter is disabled, the timing advance information relative to R2D transmission remains unchanged through network predefined or preconfigured methods; when the 18th layer enable parameter is enabled, the timing advance information relative to R2D transmission can be modified. When the nineteenth high-layer enable parameter is disabled, the timing advance information relative to R2D transmission is not configured; when the nineteenth high-layer enable parameter is enabled, the timing advance information relative to R2D transmission is configured.

57. The communication method according to claim 40, wherein, If the charging time information before the R2D transmission is predefined or preconfigured, the charging time information before the R2D transmission includes one or more values; When the charging time information before the R2D transmission is a higher-layer configuration or a physical layer indication, the charging time information before the R2D transmission is determined by at least one of the following: Configure or indicate the maximum charging time information before the maximum R2D transmission of the IoT device; The IoT device reports its own charging time or charging capacity information, and the network side configures the corresponding charging time information before R2D transmission. The IoT device reports its own type information, and the network side configures itself based on the reported type information. When the 20th layer enable parameter is disabled, the charging time information before R2D transmission is configured or indicated by the network side; when the 20th layer enable parameter is enabled, the charging time information before R2D transmission is reported by the IoT device and configured or indicated by the network side. When the 21st high-layer enable parameter is disabled, the charging time information before R2D transmission remains unchanged through network predefinition or preconfiguration; when the 21st high-layer enable parameter is enabled, the charging time information before R2D transmission can be modified. When the 22nd high-layer enable parameter is disabled, the charging time information before the R2D transmission is not configured; when the 22nd high-layer enable parameter is enabled, the charging time information before the R2D transmission is configured.

58. The communication method according to claim 40, wherein, When the timing advance information relative to D2R transmission is predefined or preconfigured, the timing advance information relative to D2R transmission includes one or more values; When the timing advance information relative to D2R transmission is configured by a higher layer or indicated by a physical layer, the timing advance information relative to D2R transmission includes at least one of the following: Configure or indicate the maximum carrier latency information of the IoT device; The IoT device reports its charging time or charging capacity information, and the network side configures the corresponding time advance information relative to D2R transmission. The IoT device reports its own type information, and the network side configures itself based on the reported type information. When the 23rd high-layer enabling parameter is disabled, the timing advance information relative to D2R transmission will not change through network predefined or preconfigured methods. When the 23rd high-layer enable parameter is enabled, the timing advance information relative to D2R transmission can be modified; When the 24th high-layer enable parameter is disabled, the timing advance information relative to D2R transmission is not configured. When the 24th high-layer enable parameter is enabled, the timing advance information relative to the D2R transmission is configured.

59. The communication method according to claim 40, wherein, If the charging time information before the D2R transmission is predefined or preconfigured, the charging time information before the D2R transmission includes one or more values; When the charging time information before the D2R transmission is a higher-layer configuration or a physical layer indication, the charging time information before the D2R transmission includes at least one of the following: Configure or indicate the charging time information before the maximum D2R transmission of the IoT device; The IoT device reports its own charging time or charging capacity information, and the network side configures the charging time information before D2R transmission. The IoT device reports its own type information, and the network side configures itself based on the reported type information. When the 25th layer enable parameter is disabled, the charging time information before D2R transmission is configured or indicated by the network side; when the 25th layer enable parameter is enabled, the charging time information before D2R transmission is reported by the IoT device and configured or indicated by the network side. When the twenty-sixth high-level enabling parameter is disabled, the charging time information before D2R transmission will no longer change through network predefinition or preconfiguration. When the twenty-sixth high-layer enabling parameter is enabled, the charging time information before D2R transmission can be modified; When the 27th high-layer enable parameter is disabled, the charging time information before the D2R transmission is not configured; when the 27th high-layer enable parameter is enabled, the charging time information before the D2R transmission is configured.

60. The communication method according to any one of claims 2-38, wherein, The time granularity information includes at least one of the following: The time granularity information is a fixed value; The time granularity information is not greater than the first threshold or not less than the second threshold; The time granularity information is within a specified time granularity range; The time granularity information is at least one of the following: bit, transport block, orthogonal frequency division multiplexing (OFDM) symbol, on / off keying OOK chip, OFDM time slot, microsecond, sampling point, PRDCH chip, PRDCH symbol, PRDCH time slot, PRDCH sampling point, physical layer channel PDRCH chip, PDRCH symbol, PDRCH time slot, PDRCH sampling point on a D2R link, R2D chip, R2D symbol, R2D time slot, R2D sampling point, D2R chip, D2R symbol, D2R time slot, and D2R sampling point.

61. The communication method according to any one of claims 2-38, wherein, The configuration or indication method also includes at least one of the following: Each parameter in the configuration or indication method is configured individually, and uniformly configured within the environmental IoT resource set, the environmental IoT media access control element, or the environmental IoT control command. The configuration or indication method is configured in the form of resource sets. The network side configures or indicates the resource set identifier to be selected, so as to select the resource set corresponding to the resource set identifier from multiple resource sets for configuration.

62. An Internet of Things (IoT) device, comprising: Memory; A processor, coupled to a memory, configured to implement the method as described in any one of claims 1-60 based on memory-stored instruction execution.

63. A computer-readable storage medium, wherein, A computer-readable storage medium stores computer instructions that, when executed by a processor, implement the method as described in any one of claims 1-60.

64. A computer program product comprising computer instructions, wherein the computer instructions, when executed by a processor, implement the method as described in any one of claims 1-60.

Images