Communication method and communication device

Abstract

The invention provides a communication method and communication equipment. The communication method comprises: a first device receiving first data sent by a second device, the first data being data obtained by performing R2D repetition on second data; the first data is any one of the following data: R2D bit repetition of the second data, R2D chip repetition of the second data, and R2D block repetition of the second data.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and more particularly, to a communication method and a communication device. BACKGROUND

[0002] Ambient Internet of Things (A-IoT) communication adopts energy harvesting and backscatter communication technology, and has the characteristics of low power consumption and low cost. However, how to enhance the coverage capability of the A-IoT system is a technical problem to be solved. SUMMARY

[0003] The present application provides a communication method and a communication device. Each aspect of the present application is introduced below.

[0004] In a first aspect, a communication method is provided, comprising: receiving, by a first device, first data transmitted by a second device, the first data being data repeated by R2D on second data; the first data being any one of: R2D bit repetition of the second data, R2D chip repetition of the second data, and R2D block repetition of the second data.

[0005] In a second aspect, a communication method is provided, comprising: transmitting, by a second device, first data to a first device, the first data being data repeated by R2D on second data; the first data being any one of: R2D bit repetition of the second data, R2D chip repetition of the second data, and R2D block repetition of the second data.

[0006] In a third aspect, a communication device is provided, the communication device being a first device, and the communication device comprising: a first communication module configured to receive first data transmitted by a second device, the first data being data repeated by R2D on second data; the first data being any one of: R2D bit repetition of the second data, R2D chip repetition of the second data, and R2D block repetition of the second data.

[0007] In a fourth aspect, a communication device is provided, the communication device being a second device, and the communication device comprising: a first communication module configured to transmit first data to a first device, the first data being data repeated by R2D on second data; the first data being any one of: R2D bit repetition of the second data, R2D chip repetition of the second data, and R2D block repetition of the second data.

[0008] In a fifth aspect, a communication device is provided, comprising a transceiver, a memory, and a processor, the memory is configured to store a program, the processor is configured to invoke the program in the memory and control the transceiver to receive or send a signal, so that the communication device performs the method according to the first aspect or the second aspect.

[0009] In a sixth aspect, an apparatus is provided, comprising a processor configured to invoke a program from a memory, so that the apparatus performs the method according to the first aspect or the second aspect.

[0010] In a seventh aspect, a chip is provided, comprising a processor configured to invoke a program from a memory, so that a device installed with the chip performs the method according to the first aspect or the second aspect.

[0011] In an eighth aspect, a computer readable storage medium is provided, which stores a program, the program causes a computer to perform the method according to the first aspect or the second aspect.

[0012] In a ninth aspect, a computer program product is provided, comprising a program, the program causes a computer to perform the method according to the first aspect or the second aspect.

[0013] In a tenth aspect, a computer program is provided, the computer program causes a computer to perform the method according to the first aspect or the second aspect.

[0014] In the present application, the R2D is used to repeatedly transmit data, so as to improve the reliability of repeated reception of data, thereby helping to enhance the coverage of the A-IoT system transmission. BRIEF DESCRIPTION OF DRAWINGS

[0015] Figure 1 FIG. 1 is an example of a system architecture of a communication system to which embodiments of the present application can be applied.

[0016] Figure 2 FIG. 2 is an example of a system architecture of an A-IoT communication system.

[0017] Figure 3 FIG. 3 is an example of a system architecture of an A-IoT communication system.

[0018] FIG. 4(a) is an example of a system architecture of an A-IoT communication system.

[0019] FIG. 4(b) is an example of a system architecture of an A-IoT communication system.

[0020] Figure 5 FIG. 5 is an example of a system architecture of an A-IoT communication system.

[0021] Figure 6 FIG. 6 is a flowchart of an R2D generation process.

[0022] Figure 7 This is a flowchart illustrating the communication method provided in an embodiment of this application.

[0023] Figures 8(a) to 8(c) This is a schematic diagram of the R2D bit repetition generation process provided in an embodiment of this application.

[0024] Figure 9 This is a schematic diagram of the R2D chip repetition generation process provided in the embodiments of this application.

[0025] Figures 10(a) to 10(c) This is a schematic diagram of the R2D block repetition generation process provided in an embodiment of this application.

[0026] Figure 11 This is a schematic diagram of the structure of a PRDCH resource provided in an embodiment of this application.

[0027] Figure 12 This is a schematic diagram of the structure of a PRDCH resource provided in another embodiment of this application.

[0028] Figure 13 This is a schematic diagram of the structure of a PRDCH resource provided in another embodiment of this application.

[0029] Figure 14 This is a schematic diagram of the structure of a PRDCH resource provided in another embodiment of this application.

[0030] Figure 15 This is a schematic diagram of the structure of a PRDCH resource provided in another embodiment of this application.

[0031] Figure 16 This is a schematic diagram of the structure of a PRDCH resource provided in another embodiment of this application.

[0032] Figure 17 This is a schematic diagram of the structure of a PRDCH resource provided in another embodiment of this application.

[0033] Figure 18 This is a schematic diagram of the structure of a PRDCH resource provided in another embodiment of this application.

[0034] Figure 19 This is a schematic diagram of the structure for indicating the location of frequency domain resources provided in an embodiment of this application.

[0035] Figure 20 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application.

[0036] Figure 21 This is another structural schematic diagram of the communication device provided in an embodiment of this application.

[0037] Figure 22This is a schematic diagram of an apparatus to which embodiments of this application can be applied. Detailed Implementation

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

[0039] Communication system

[0040] Figure 1 This is the wireless communication system 100 used in this application embodiment. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 can provide communication coverage for a specific geographical area and can communicate with the terminal device 120 located within that coverage area. The terminal device 120 can access a network (such as a wireless network) through the network device 110.

[0041] Figure 1 An exemplary embodiment shows a network device and two terminals. Optionally, the wireless communication system 100 may include multiple network devices and each network device may include other number of terminal devices within its coverage area. This application embodiment does not limit this.

[0042] Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in this embodiment.

[0043] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as: 5th generation (5G) systems or new radio (NR), long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, etc. The technical solutions provided in this application can also be applied to future communication systems, such as 6th generation mobile communication systems, satellite communication systems, etc.

[0044] The terminal device in this application embodiment can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The terminal device in this application embodiment can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as a handheld device with wireless connectivity, vehicle-mounted device, etc. The terminal devices in the embodiments of this application can be mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, and IoT terminal devices, etc. Additionally, the terminal devices in this application can also refer to various types of A-IoT devices.

[0045] Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity, providing sidelink signaling between UEs in V2X or D2D, etc. For instance, cellular phones and cars use sidelink signals to communicate with each other. Cellular phones and smart home devices can communicate without relaying communication signals through a base station.

[0046] The network device in this application embodiment can be a device for communicating with a terminal device. This network device can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master MeNB, auxiliary SeNB, multi-mode radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. Base stations can also be mobile switching centers, devices that perform base station functions in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, network-side devices in 6G networks, and devices that perform base station functions in future communication systems. Base stations can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0047] In some embodiments, the network device can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile network device, and one or more cells can move according to the location of the mobile network device. In other examples, a helicopter or drone can be configured to be used as a device to communicate with another network device.

[0048] In some deployments, the network device in this application embodiment may refer to a CU or a DU, or the network device may include both a CU and a DU. The gNB may also include an AAU.

[0049] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

[0050] It should be understood that all or part of the functions of the communication device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform).

[0051] In recent years, the Internet of Things (IoT) has garnered significant attention in the field of wireless communication. To improve productivity and enhance quality of life, more and more "things" are expected to be interconnected. Further reducing the size, complexity, and power consumption of IoT devices could enable the deployment of hundreds of billions or even trillions of IoT devices across various applications, providing added value throughout the value chain. Currently, most IoT devices require manual battery replacement or charging, leading to high maintenance costs, serious environmental problems, and even security risks in certain scenarios (such as wireless sensors in the power and oil industries).

[0052] Automation and digitalization across various industries have opened up many new markets, requiring new Internet of Things (IoT) technologies to support battery-free devices without energy storage capabilities or energy storage devices that do not require manual replacement or charging—these are known as A-IoT devices. Compared to existing IoT devices (such as NB-IoT, LPWA, RedCap, etc.), A-IoT devices are extremely small in size and have no batteries or very limited energy storage capacity. A-IoT devices can harvest other forms of energy from the environment, such as energy from radio signals, kinetic energy, heat, light energy, and so on.

[0053] Due to their extremely small size and the fact that they lack batteries or do not require charging, A-IoT devices have very limited capabilities and complexity, and extremely low transmission power. Currently, the primary devices used in scenarios such as inventory management are radio frequency identification (RFID). However, RFID cannot access networks in unlicensed frequency bands. The NR system began researching A-IoT devices in Release 19, aiming to manage devices more effectively, improve network efficiency, and enhance security.

[0054] In one implementation, the A-IoT device may include device 1, device 2b, and device C.

[0055] Device 1: Peak power consumption is approximately 1 microwatt (μW), with energy storage capabilities, and an initial sampling frequency offset (SFO) of up to 10. X ppm (parts per million), the device does not support R2D signal amplification or D2R signal amplification; the D2R signal transmission of this device requires backscattering on an externally provided carrier.

[0056] Device 2b: Peak power consumption ≤ several hundred μW, with energy storage function, intermediate frequency (IF) envelope detector receiver or zero IF (ZIF) receiver, SFO up to 10 Y The device has R2D and / or D2R signal amplification capabilities. The D2R signal transmission of this device can be generated internally.

[0057] Device C: 1mW ≤ peak power consumption ≤ 10mW, with energy storage function, intermediate frequency (IF) envelope detector receiver or zero IF (ZIF) receiver, SFO up to 10 Y The device has R2D and / or D2R signal amplification capabilities. The D2R signal transmission of this device can be generated internally.

[0058] Assumption 10 Y The SFO value in ppm is better than any SFO value considered for device 1 in R19 (SFO value 10). Y isassumed to be better than any SFO value considered for Device 1 standardized in Rel-19).

[0059] The following is combined with Figures 2 to 5This document provides an exemplary description of an A-IoT communication system. It should be understood that the network device in the A-IoT communication system may be referred to as a reader, and this network device may be a base station with A-IoT capabilities, or any of the network devices described above in this application. The A-IoT device may be any of the terminal devices described above in this application, but this application does not limit it to any of these.

[0060] like Figure 2 As shown, the network device has Ambient IoT capabilities, enabling bidirectional communication with A-IoT devices. Specifically, the network device can send... Reader to device (R2D) The signal provides power to the A-IoT device. The A-IoT device receives R2D signals sent by the network device and sends device-to-reader (D2R) signals back to the network device. In this way, the network device performs read and write operations on the A-IoT device. The signal transmission method from the network device to the A-IoT device and the signal transmission method from the A-IoT device to the network device are different.

[0061] like Figure 3 As shown, the A-IoT communication system includes network devices, intermediate nodes, and A-IoT devices. Intermediate nodes can also be called readers. Two-way information exchange is possible between network devices and intermediate nodes, and between intermediate nodes and A-IoT devices.

[0062] Optionally, the intermediate node can be other network nodes with A-IoT capabilities, such as repeaters, integrated access and backhaul (IAB) nodes, or terminal devices, etc., and this application does not limit this. The intermediate node transmits data and / or signaling between network devices and A-IoT devices.

[0063] It should be understood that the connection and signal transmission methods between intermediate nodes and A-IoT devices are different from those of... Figure 2 The A-IoT communication system is the same across all devices. However, the signal transmission methods used by intermediate nodes to send signals to A-IoT devices and by A-IoT devices to send signals to intermediate nodes differ. Communication between intermediate nodes and network devices is transmitted via the Uu port.

[0064] As shown in Figures 4(a) and (b), the communication system includes network devices, assistant nodes, and A-IoT devices. While the network devices and A-IoT devices exchange information bidirectionally, bidirectional information exchange can also occur between the network devices and assistant nodes, and between the assistant nodes and A-IoT devices. In some implementations, the assistant nodes and network devices can communicate via the Uu interface.

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

[0066] like Figure 5 As shown, A-IoT devices and terminal devices can perform bidirectional information interaction. In one possible implementation, communication between the A-IoT device and the terminal device uses 5G NR technology or 5G sidelink technology. It should be understood that the terminal device has A-IoT capabilities.

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

[0068] In some implementation methods, the solution in this application is mainly aimed at Figure 2 and Figure 3 The A-IoT communication system in the context of A-IoT refers to the direct connection between A-IoT devices and network devices, as well as the connection between A-IoT devices and network devices through intermediate nodes.

[0069] R2D

[0070] R2D is a reader-to-device data transfer process, primarily consisting of a preamble and a physical transmission channel. The physical transmission channel, or physical reader-to-device channel (PRDCH), includes steps such as adding cyclic redundancy check (CRC), linear encoding, adding an R2D timing acquisition signal (R-TAS) and postamble, and padding. The following diagram illustrates the steps involved in R2D generation.

[0071] See Figure 6In step S601, A original information bits can be combined to form an R2D transport block. This transport block is delivered by a higher layer (such as the MAC layer) to the physical layer (L1) for processing. The R2D transport block may include: a0, a1, ..., a A-1 (i.e., information bits). A CRC checksum is appended to the original information bits for error detection at the receiving end. The appended bit sequence is denoted as: b0, b1, ..., b B-1 The total number of bits B after adding the CRC checksum is: B = A + L, where A is the number of original information bits and L is the number of CRC encoded bits.

[0072] In step S602, the data output in step S601 can be linearly encoded, and the bit sequence after linear encoding is c0, c1, ..., c 2B-1 .

[0073] In step S603, R-TAS and postcode can be added to the data output in step S602.

[0074] In step S604, the data output in step S603 may be padded to adapt to the requirements of subsequent chip and OFDM symbol mapping. It should be understood that step S604 is optional.

[0075] In step S605, the data bits output in step S604 are mapped to chips to form chip χ. R2D Then, the chip is mapped to an OFDM symbol, ready for transmission over the wireless channel.

[0076] The primary research scenario in Release 20 (R20) is the outdoor scenario. In contrast, Release 19 focuses on the indoor scenario, highlighting the need to enhance the coverage capability of A-IoT systems. In other words, how to improve the coverage capability of A-IoT systems is a key technical challenge.

[0077] To address the aforementioned issues, this application proposes a communication method that uses Relay-to-Depth (R2D) data retransmission to improve the reliability of repeated data reception, thereby enhancing the coverage of A-IoT system transmission. The following section combines... Figure 7 The embodiments of this application will be described in detail below.

[0078] Figure 7 This is a schematic flowchart illustrating the communication method provided in an embodiment of this application. Figure 7 The communication method shown is introduced from the perspective of communication between the first device and the second device. Figure 7The first and second devices in the communication link can be two communication devices at opposite ends of the link. The first device can be the receiver of the communication link, and the second device can be the transmitter. For example, the first device could be... Figure 2 or Figure 3 In the context of A-IoT devices, the second device could be, for example, the upper... Figure 2 or Figure 3 The network device in the middle. In other implementations, the second device can also be, for example, the upper network device. Figure 2 or Figure 3 The intermediate node in the process can be a repeater, IAB, terminal equipment, or other devices.

[0079] See Figure 7 In step S710, the first device receives first data sent by the second device. The first data is data obtained by repeating the second data using R2D. That is, the first data can be obtained by repeating the second data using R2D. The second data can be bit data (such as information bit data or coded bit data), chip data, or data blocks (such as bit blocks, coded blocks, or modulation symbol blocks, etc.). This application does not impose specific limitations on this.

[0080] This application does not impose specific restrictions on the repetition mechanism of the second data in R2D repetition. For example, the R2D repetition can be R2D bit repetition (also known as bit-level R2D repetition); or R2D repetition can be R2D chip repetition (also known as chip-level R2D repetition); or R2D repetition can be R2D block repetition (also known as block-level R2D repetition).

[0081] Accordingly, the first data is any of the following: R2D bit repetition of the second data, R2D chip repetition of the second data, or R2D block repetition of the second data.

[0082] In some implementations, R2D bit repetition can refer to the repetition N of bit data transmitted in R2D. r Next, N r It is a natural number. R2D bit repetition includes R2D information bit repetition or R2D encoded bit repetition. R2D information bit repetition can refer to the repetition N of the original bit information transmitted in R2D. r R2D encoded bit repetition can refer to the encoding of information bits transmitted in R2D and repeating them N times. r The following is an illustrative description of the R2D bit repetition generation process with reference to the accompanying drawings.

[0083] As shown in Figure 8(a), a process for generating R2D information bit repetition includes steps S801 to S807.

[0084] In step S801, A original information bits (a0, a1, ..., a...) are... A-1 Each bit in ) is repeated N times r After this, the bit sequence is obtained: r0, r1, ..., r R-1 If the number of repetitions of the R2D information bits is 2, such as a0 repeated twice as a0,a0.

[0085] In step S802, the R bits output in step S801 can be used to form an R2D transmission block. A CRC checksum is appended after the R bits for error detection at the receiving end.

[0086] In step S803, channel coding can be performed on the data output in step S802.

[0087] In step S804, the data output in step S803 can be linearly encoded.

[0088] In step S805, R-TAS and / or postcode and / or auxiliary signals can be added to the data output in step S804. The R-TAS mainly comprises two parts: the first part is a start-indicator part, used to indicate the start of R2D transmission, for example, this start-indicator part can be an 8-bit sequence "11001000". The second part is a clock acquisition part, used to provide R2D clock synchronization messages to terminal devices (such as A-IoT devices), for example, the clock acquisition part can be a 4-bit sequence "1010". Auxiliary signals can include one or more of the following: m-sequences, golay sequences, walsh sequences, CRC codewords, D2R preambles, D2R introcodes, or D2R postcodes, R2D preambles, R2D introcodes, or R2D postcodes, or specific codewords.

[0089] In step S806, the data output in step S805 may be padded to adapt to the requirements of subsequent chip and OFDM symbol mapping. It should be understood that step S806 is optional.

[0090] In step S807, the data output in step S806 is mapped to a chip (forming a χ). R2D (and OFDM symbols. It should be understood that the data output in step S807 can be transmitted over a wireless channel.)

[0091] As shown in Figure 8(b), another process for generating R2D information bit repetition includes steps S811 to S817.

[0092] In step S811, A original information bits (a0, a1, ..., a...) are... A-1 These can be combined into an R2D transport block, with a CRC checksum appended after A bits for error detection at the receiving end.

[0093] In step S812, each bit output in step S811 is repeated N times. r After this, the bit sequence is obtained: r0, r1, ..., r R-1 .

[0094] In step S813, channel coding can be performed on the data output in step S812.

[0095] In step S814, the data output in step S813 can be linearly encoded.

[0096] In step S815, R-TAS and / or postcode and / or auxiliary signals may be added to the data output in step S814.

[0097] In step S816, the data output in step S815 may be padded to adapt to the requirements of subsequent chip and OFDM symbol mapping. It should be understood that step S816 is optional.

[0098] In step S817, the data output in step S816 is mapped to a chip (forming a χ). R2D (and OFDM symbols. It should be understood that the data output in step S817 can be transmitted over a wireless channel.)

[0099] As shown in Figure 8(c), a process for generating R2D encoded bit repetition includes steps S821 to S827.

[0100] In step S821, A original information bits (a0, a1, ..., a...) are... A-1 These can be combined into an R2D transport block, with a CRC checksum appended after A bits for error detection at the receiving end.

[0101] In step S822, channel coding can be performed on the data output in step S821.

[0102] In step S823, each bit output in step S822 is repeated N times. r After this, the bit sequence is obtained: r0, r1, ..., r R-1 .

[0103] In step S824, the data output in step S823 can be linearly encoded.

[0104] In step S825, R-TAS and / or postcode and / or auxiliary signals may be added to the data output in step S824.

[0105] In step S826, the data output in step S825 may be padded to adapt to the requirements of subsequent chip and OFDM symbol mapping. It should be understood that step S826 is optional.

[0106] In step S827, the data output in step S826 is mapped to a chip (forming a χ). R2D (and OFDM symbols. It should be understood that the data output in step S827 can be transmitted over a wireless channel.)

[0107] It should be understood that the above Figures 8(a) to 8(c) The order of steps in the example is for illustrative purposes only; the order of these steps can be interchanged. For example, adding CRC can occur after channel coding. The bit repetition step can occur at any step before adding R-TAS and the postcode. Of course, Figures 8(a) to 8(c) The example process does not exclude the possibility of adding or removing other steps in the R2D generation process.

[0108] In some implementations, R2D chip repetition can refer to repeatedly mapping each bit to a modulation chip. For example, R2D chip repetition can mean that after the information bits transmitted in R2D are encoded, each modulation chip after on-off keying (OOK) modulation is repeated N times. r The following is an illustrative description of the process for generating repeated R2D chips, with reference to the accompanying drawings.

[0109] See Figure 9 A process for generating repeated R2D chips includes steps S901 to S905.

[0110] In step S901, A original information bits can be combined to form an R2D transport block, which may include: a0, a1, ..., a A-1 (i.e., information bits). A CRC checksum is appended to the original information bits for error detection at the receiving end. The appended bit sequence is denoted as: b0, b1, ..., b B-1 The total number of bits B after adding the CRC checksum is: B = A + L, where A is the number of original information bits and L is the number of CRC encoded bits.

[0111] In step S902, the data output in step S901 can be linearly encoded.

[0112] In step S903, R-TAS and / or postcode and / or auxiliary signals may be added to the data output in step S902.

[0113] In step S904, the data output in step S903 may be padded to adapt to the requirements of subsequent chip and OFDM symbol mapping. It should be understood that step S904 is optional.

[0114] In step S905, the data bits output in step S904 are repeatedly mapped to chips to form multiple chips χ. R2D Then, the chip is mapped to an OFDM symbol, ready for transmission over the wireless channel.

[0115] In some implementations, R2D block repetition can refer to the repetition N of block data transmitted in R2D. r Here, R is a natural number. R2D block repetition includes R2D information bit block repetition, R2D coded bit block repetition, or R2D modulation symbol block repetition. R2D information bit block repetition can refer to the repetition N of the information bit block transmitted in R2D. r Then it undergoes encoding and modulation. R2D encoded bit block repetition can refer to repeating the encoded bit block of information transmitted in R2D N times. r The modulation is performed again. R2D modulation symbol block repetition can refer to repeating the encoded and modulated information bit block of R2D transmission N times. r The following is an illustrative description of the R2D bit repetition generation process with reference to the accompanying drawings.

[0116] As shown in Figure 10(a), a process for generating repeated R2D information bit blocks includes steps S1001 to S1007.

[0117] In step S1001, A original information bits (a0, a1, ..., a...) are... A-1 The R2D transport block composed of N repeats r After this, the bit sequence is obtained: r0, r1, ..., r R-1 If the number of repetitions of the R2D information bit block is 2, such as a0, a1, ..., a A-1 Repeated twice, a0, a1, ..., a A-1 ,a0,a1,…,a A-1 .

[0118] In step S1002, the R bits output in step S1001 are used to form an R2D transmission block, and a CRC checksum is appended to the R2D transmission block for error detection at the receiving end.

[0119] In step S1003, channel coding can be performed on the data output in step S1002.

[0120] In step S1004, the data output in step S1003 can be linearly encoded.

[0121] In step S1005, R-TAS and / or postcode and / or auxiliary signals may be added to the data output in step S1004.

[0122] In step S1006, the data output in step S1005 may be padded to adapt to the requirements of subsequent chip and OFDM symbol mapping. It should be understood that step S1006 is optional.

[0123] In step S1007, the data output in step S1006 is mapped to a chip (forming a χ). R2D (and OFDM symbols. It should be understood that the data output in step S1007 can be transmitted over a wireless channel.)

[0124] As shown in Figure 10(b), another process for generating repeated R2D information bit blocks includes steps S1011 to S1017.

[0125] In step S1011, A original information bits (a0, a1, ..., a...) are... A-1 These can be combined into an R2D transport block, with a CRC checksum appended after A bits for error detection at the receiving end.

[0126] In step S1012, the R2D transfer block output in step S1011 is repeated N times. r After this, the bit sequence is obtained: r0, r1, ..., r R-1 .

[0127] In step S1013, channel coding can be performed on the data output in step S1012.

[0128] In step S1014, the data output in step S1013 can be linearly encoded.

[0129] In step S1015, R-TAS and / or postcode and / or auxiliary signals may be added to the data output in step S1014.

[0130] In step S1016, the data output in step S1015 may be padded to adapt to the requirements of subsequent chip and OFDM symbol mapping. It should be understood that step S1016 is optional.

[0131] In step S1017, the data output in step S1016 is mapped to a chip (forming a χ). R2D (and OFDM symbols. It should be understood that the data output in step S1017 can be transmitted over a wireless channel.)

[0132] As shown in Figure 10(c), a process for generating R2D encoded bit block repetition includes steps S1021 to S1027.

[0133] In step S1021, A original information bits (a0, a1, ..., a...) are... A-1 These can be combined into an R2D transport block, and a CRC checksum can be appended to the R2D transport block for error detection at the receiving end.

[0134] In step S1022, channel coding can be performed on the data output in step S1021.

[0135] In step S1023, the R2D transfer block output in step S1022 is repeated N times. r After this, the bit sequence is obtained: r0, r1, ..., r R-1 .

[0136] In step S1024, the data output in step S1023 can be linearly encoded.

[0137] In step S1025, R-TAS and / or postcode and / or auxiliary signals may be added to the data output in step S1024.

[0138] In step S1026, the data output in step S1025 may be padded to adapt to the requirements of subsequent chip and OFDM symbol mapping. It should be understood that step S1026 is optional.

[0139] In step S1027, the data output in step S1026 is mapped to a chip (forming a χ). R2D (and OFDM symbols. It should be understood that the data output in step S1027 can be transmitted over a wireless channel.)

[0140] It should be understood that the above Figures 10(a) to 10(c) The order of steps in the example is for illustrative purposes only; the order of these steps can be interchanged. For example, adding CRC can occur after channel coding. The R2D block repetition step can occur at any step before adding R-TAS and post-code, or it can occur after adding R-TAS and post-code. For example, the modulation symbol block after OFDM symbol mapping can be repeated Nr times. Of course, Figures 10(a) to 10(c)The example process does not exclude the possibility of adding or removing other steps in the R2D generation process.

[0141] The above mainly describes the R2D repeat mechanism in detail. The following is an exemplary description of the R2D repeat data transmission mechanism.

[0142] In some implementations, the first data is carried on one or more PRDCH resources. That is, R2D repeating transmissions can be transmitted in one PRDCH resource or in N PRDCHs, where N is an integer greater than 1.

[0143] In some implementations, the number of PRDCH resources can be the same as or different from the number of times the R2D duplicate data is repeated (Nr) (i.e., the number of times the second data is repeated in R2D).

[0144] In some implementations, one or more auxiliary signals may be inserted between the first data on the PRDCH resource. In other words, the first data on the PRDCH resource may be divided into multiple data portions by auxiliary signals and / or preambles (such as R-TAS) and / or postambles. These multiple data portions may be referred to as R2D data or data blocks (or R2D data blocks), such as... Figure 11 or Figure 12 As shown. The auxiliary signal can be one or more of the following: m-sequence, golay sequence, walsh sequence, CRC codeword, D2R preamble, D2R mid-preamble or D2R postamble, R2D preamble, R2D mid-preamble or R2D postamble, or a specific codeword.

[0145] In some implementations, the number of auxiliary signals inserted on the PRDCH resource is configured by a second device, or determined based on a method predefined by the protocol.

[0146] In some implementations, if the number of auxiliary signals is determined based on a predefined method in the protocol, the number of auxiliary signals may be associated with one or more of the following: the number of repetitions of the second data; the length of the first data between adjacent auxiliary signals, and / or between the first auxiliary signal and the preamble, and / or between the last auxiliary signal and the postamble; the first data; and the data length of the second data.

[0147] For example, the number of auxiliary signals can be the number of repetitions of the second data minus 1 (i.e., Nr-1).

[0148] For example, the first device can calculate the number of auxiliary signals based on the length of the R2D data block between adjacent auxiliary signals, between the first auxiliary signal (i.e., the first auxiliary signal among multiple auxiliary signals on the PRDCH resource) and the preamble (e.g., R-TAS), and between the last auxiliary signal (i.e., the last auxiliary signal among multiple auxiliary signals on the PRDCH resource) and the postamble (e.g., R2D postamble).

[0149] It should be noted that, in this embodiment, the R2D data block between two adjacent auxiliary signals is a part of the first data. The data length of the R2D data block may be the same as or different from the data length of the second data.

[0150] For example, the first device may determine the number of auxiliary signals based on the length of the first data and / or the second data.

[0151] For example, if the length of the first data or the second data is within a first threshold range, the number of auxiliary signals is a first quantity; if the length of the first data or the second data is within a second threshold range, the number of auxiliary signals is a second quantity. The first threshold range and the second threshold range are different, and the first quantity and the second quantity are different. For example, the first threshold range can be smaller than the second threshold range, and the first quantity can be smaller than the second quantity; that is, the longer the length of the first data or the second data, the more auxiliary signals are generated. The first threshold range, the second threshold range, the first quantity, and the second quantity can all be set according to requirements, and this application does not impose specific limitations on them.

[0152] In some implementations, the data lengths of multiple R2D data blocks can be the same or different between adjacent auxiliary signals, between the first auxiliary signal (i.e., the first auxiliary signal among multiple auxiliary signals on the PRDCH resource) and a preamble (such as R-TAS), and between the last auxiliary signal (i.e., the last auxiliary signal among multiple auxiliary signals on the PRDCH resource) and a postamble (such as R2D postamble). To reduce the complexity of the first device receiving R2D data, the data lengths of multiple R2D data blocks on the PRDCH resource can be set to be the same.

[0153] In some implementations, the data length of R2D data between adjacent auxiliary signals, between the first auxiliary signal and the preamble, and between the last auxiliary signal and the postamble is configured by the second device or determined based on a method predefined by the protocol.

[0154] For example, the R2D data length between adjacent auxiliary signals, between the first auxiliary signal and the preamble, and between the last auxiliary signal and the postamble is configured by the second device, and the R2D data length between adjacent auxiliary signals, between the first auxiliary signal and the preamble, and between the last auxiliary signal and the postamble is the same.

[0155] For example, if the second device is configured with the R2D data length of S, and the R2D data length between the last auxiliary signal and the postcode is less than S, then the R2D data between the last auxiliary signal and the postcode can be supplemented so that the R2D data length between the last auxiliary signal and the postcode is equal to S.

[0156] In other words, the first data on the PRDCH resource includes a first R2D data block and a second R2D data block. If the length of the second R2D data block is shorter than the length of the first R2D data block, then the length of the second R2D data block can be supplemented to make the length of the second R2D data block equal to the length of the first R2D data block; the second R2D data block is the last R2D data block on the PRDCH resource. In some implementations, the first data on the PRDCH resource can be divided into multiple R2D data blocks by auxiliary signals and / or preambles (such as R-TAS) and / or postambles, and these multiple R2D data blocks include the aforementioned first R2D data block and second R2D data block.

[0157] For example, see Figure 11 If the length of the R2D data block between the first auxiliary signal and the preamble (such as R-TAS), and between subsequent adjacent auxiliary signals, is L, and if the length of the R2D data block between the last auxiliary signal and the postamble (R2D postamble) is less than L, the second device can make its length equal to L by using padding bits. Of course, if it is not necessary to keep the lengths of multiple R2D data blocks consistent, this padding bit operation can be omitted.

[0158] In some implementations, the auxiliary signal may have multiple lengths or only one length. The length of the auxiliary signal may be configured by a second device or determined based on a pre-defined protocol.

[0159] In some implementations, the length of the auxiliary signal can be a default length predefined by the protocol.

[0160] In some implementations, the length of the auxiliary signal is a variety of lengths predefined by the protocol, and the length of the auxiliary signal is associated with one or more of the following: the data size or length of the first data; the size or length of the second data; the data type of the first data; the data type of the second data (also known as the data information type or data message type); the number of repetitions of the second data; the number of auxiliary signals; and the length of the R2D data block between adjacent auxiliary signals.

[0161] For example, if the transport block size (TBS) of the first or second data is between [L1, L2], the length of the auxiliary signal is S1; if the TBS is between [L2, L3], the length of the auxiliary signal is S2. The transport block size of the first or second data can also be referred to as the data size or length of the first or second data.

[0162] For example, if the number of repetitions of the second data is Nr1, then the length of the auxiliary signal is S1; if the number of repetitions of the second data is Nr2, then the length of the auxiliary signal is S2.

[0163] For example, there are one or more R2D data blocks between adjacent auxiliary signals. If the length of the R2D data block is in the range of [L1, L2], then the length of the auxiliary signal is S1; if the length of the R2D data block is in the range of [L2, L3], then the length of the auxiliary signal is S2.

[0164] For example, if the number of auxiliary signals is R1, then the length of the auxiliary signal is S1; if the number of auxiliary signals is R2, then the length of the auxiliary signal is S2.

[0165] In some implementations, the data type of the first data / second data is any of the following: synchronization information, paging message, Msg2, Msg4, access timing trigger message, R2D upper layer data transmission message, R2D control information (scheduling information for resources used to schedule R2D duplicate data), and scheduling information (other scheduling information not used to schedule R2D duplicate data).

[0166] For example, if the data type of the first or second data is synchronization information, the length of the auxiliary signal (such as CRC codeword) is S1; if the data type of the first or second data is A-IoT paging message, the length of the auxiliary signal is S2.

[0167] It should be noted that this application does not impose specific restrictions on the setting values ​​of the parameters appearing in the above examples. For example, the values ​​of parameters such as Nr1, Nr2, S1, S2, R1, R2, and L1 to L3 can be set according to requirements.

[0168] It should be noted that the length of the auxiliary signal can also be determined based on a combination of multiple parameters. For example, if the length of the first or second data is within the range [L1, L2] and the number of auxiliary signals is R1, then the length of the auxiliary signal is S1; if the length of the first or second data is within the range [L2, L3] and the number of auxiliary signals is R2, then the length of the auxiliary signal is S2. It should be understood that the length of the auxiliary signal can also be determined based on combinations of more or fewer parameters, which will not be elaborated upon here.

[0169] In some implementations, the auxiliary signal can be linearly encoded.

[0170] In some implementations, the first data is carried on multiple PRDCH resources. This first data can be transmitted independently over the network across these multiple PRDCHs, and each PRDCH can choose the optimal transmission path, improving transmission robustness. Even if a PRDCH cannot be correctly received by the first device, the R2D transmission data can still be correctly decoded through other PRDCHs, further improving transmission reliability.

[0171] In some implementations, the first data is carried on N PRDCH resources, where N may be the same as or different from the number of repetitions of the second data.

[0172] In some implementations, the first data on each of the N PRDCH resources may have the same or different data lengths.

[0173] As an example, the length of the first data on N PRDCHs is the same, for example, the first data is R2D bit repetition data or R2D chip repetition data (this type of first data is transmitted in multiple PRDCHs in a way similar to the way the first data is sent in packets).

[0174] In some implementations, if the data length of the first data on the PRDCH resources in the N PRDCH resources is different, the data length of the first data on each of the N PRDCH resources can be set to be the same, thereby reducing the complexity of the first device's reception.

[0175] For example, if the data length of the first data on the last PRDCH resource among N PRDCH resources is less than the data length of the first data on other PRDCH resources, then the data length of the first data on the last PRDCH resource is padded so that the data length of the first data on each PRDCH resource is the same.

[0176] For example, the first data can be divided into N transmission blocks and transmitted in N PRDCHs. If the length / size of the first data cannot be divided into N transmission blocks, then the minimum number of bits / codewords that make the data size divisible by N are padded after the first data. The length or size of the aforementioned transmission blocks can be configured by the second device or determined based on a predefined definition.

[0177] For example, if the length of the first data that can be carried in each PRDCH is S, and N is the minimum value that can be used to transmit the first data completely, and the length of the first data in the last PRDCH is less than S, then the last padding bits of the first data in the last PRDCH will make its length S. It should be understood that the value of S is indicated by the second device or is predetermined by the protocol.

[0178] The scheme in this application makes the transmission length of the first data on each of the multiple PRDCHs the same, thereby reducing the complexity of the first device receiving R2D transmissions.

[0179] In some implementations, the length of the first data on N PRDCHs is the same. For example, if the first data is repeated R2D block data, and each repeated block of the second data is transmitted in a separate PRDCH, then the number of PRDCH resources N is the same as the number of repetitions Nr of the second data. Figure 13 As shown, taking Nr equal to 3 as an example, the duplicate block of the second data is transmitted in a separate PRDCH. The value of N is Nr by default, or it is indicated by the second device.

[0180] In some implementations, for cases where the first data is repeated R2D block data, if the data length of the first data on the PRDCH resources in the N PRDCH resources is different, the data length of the first data on each PRDCH resource in the N PRDCH resources can be set to be the same, thereby reducing the complexity of the first device receiving the data.

[0181] For example, the length of the first data in each PRDCH is S, and N is the minimum value that can be used to transmit the first data completely. If the length of the first data in the last PRDCH is less than S, then padding bits are added to the end of the first data in the last PRDCH to make its length S. Here, S may be the same as or different from the length of the block repeating data in the second data. (This is similar to how the length of data transmitted in each PRDCH is fixed; for example, S is predetermined by the protocol or indicated by the second device, but it may not be the same as the length of the block repeating data).

[0182] In some implementations, the frequency domain resources of the N PRDCHs are related; for example, the frequency domain resources of the N PRDCHs are the same, or the frequency domain resources of the N PRDCHs are different.

[0183] In other implementations, the data rates of the multiple PRDCH resources are the same or different; and / or, the modulation schemes and modulation parameters of the multiple PRDCH resources are the same or different; and / or, the auxiliary signals inserted on the multiple PRDCH resources are the same or different.

[0184] For example, N PRDCHs have the same modulation scheme and modulation parameters, such as all N PRDCHs using OOK-4 modulation, and the m value of OOK-4 modulation is the same.

[0185] In some implementations, the preamble / intermule / postamble of the N PRDCHs may be the same or different.

[0186] It should be understood that if all parameters for N PRDCHs are identical, the configuration of related parameters can be reduced, thereby reducing signaling overhead. Furthermore, it reduces the configuration information required for the first device to receive and decode, lowering the complexity of signal processing for the first device. Using different parameters to transmit PRDCHs allows for parameter adjustment based on different channel conditions, providing greater flexibility to adapt to varying channel states.

[0187] In some implementations, the time-domain resource information of the PRDCH resource includes one or more of the following: the start time of the time-domain resource, the end time of the time-domain resource, the duration of the time-domain resource, the offset of the time-domain resource, and the period of the time-domain resource.

[0188] In some implementations, the starting offset reference point of the time domain resource of the first data is the end or start time of the time domain resource of the first information, and the first information is used to schedule the time domain resource of the first data; or, the starting offset reference point is the end or start time of the time domain resource of the previous R2D transmission received by the first device; or, the starting offset reference point is the end or start time of the time domain resource of the previous D2R transmission sent by the first device; or the starting offset reference point is the end or start time of the time domain resource of a certain type of R2D / D2R transmission.

[0189] In some implementations, the first data is carried on multiple PRDCH resources, which include N PRDCH resources, where N is an integer greater than 1;

[0190] The starting offset reference point of the time-domain resource of the first PRDCH resource is the end or start time of the time-domain resource of the first information, and the starting offset reference point of the time-domain resource of the (n+1)th PRDCH resource is the end or start time of the time-domain resource of the nth PRDCH resource. The first information is used to schedule the time-domain resource of the first data, where N>n>1. It should be noted that the first information in this application can be control information (such as R2D control information), R2D scheduling information, or resource configuration information (such as R2D resource configuration information).

[0191] See Figure 15 Taking an R2D repetition count of 4 as an example, the R2D control information can be used to indicate four offsets: Toffset0, Toffset1, Toffset2, and Toffset3. The values ​​of Toffset0, Toffset1, Toffset2, and Toffset3 can be the same or different. Alternatively, the R2D control information can be used to indicate the Toffset value, where Toffset0, Toffset1, Toffset2, and Toffset3 are all the same, representing Toffset. It should be understood that Toffset0, Toffset1, Toffset2, and Toffset3 in this application can also be represented as offset 1, offset 2, offset 3, and offset 4.

[0192] In some implementations, for cases where PRDCHs are contiguous in the time domain, R2D control information can be used to indicate the start / end offset of the time domain resources for the (1+n1×a)th PRDCH. Here, 'a' is an integer greater than 1, 0 ≤ n1 ≤ N1, and n1 is an integer, representing the number of contiguous PRDCHs in the time domain. 'N1' is an integer greater than or equal to 1. 'a' and 'N1' can be indicated by the second device or predefined by the protocol. Specifically, the time domain resources from the (1+n1×a)th PRDCH to the (n1+1)×ath PRDCH are contiguous, such as... Figure 16 As shown.

[0193] In some implementations, the reference point for the start / end offset of the time-domain resource of the n1×a+1th PRDCH can be the start / end position of the time-domain resource of the R2D control information, or it can be the start / end position of the time-domain resource of the n1×ath PRDCH. For example... Figure 16 As shown, a is 2, and the reference point for the start offset of the third PRDCH time domain resource is the end position of the second PRDCH time domain resource.

[0194] In some implementations, the first data is carried on multiple PRDCH resources, including a first PRDCH resource and a second PRDCH resource. The first information on the first PRDCH resource is used to indicate the starting offset of the temporal resource of the second PRDCH resource, and the first information is used to schedule the temporal resource of the first data. The first PRDCH resource is located before the second PRDCH resource in the temporal domain.

[0195] For example, R2D control information can be in the same PRDCH as R2D repeating data. The R2D control information can be used to indicate the start / end offset of the temporal resources in the next PRDCH. Taking an R2D repeating data repetition count of 3 as an example, [the following text is incomplete and requires further context: "participating..."] Figure 17 The first R2D control message (R2D control message #0) indicates the time-domain resource start offset of the first PRDCH (PRDCH #0), the second R2D control message (R2D control message #1) indicates the time-domain resource start offset of the second PRDCH (PRDCH #1), the third R2D control message (R2D control message #3) indicates the time-domain resource start offset of the third PRDCH (PRDCH #2), and so on. The R2D repetitive data indicated by the current R2D control message is transmitted in the next PRDCH following the current R2D control message.

[0196] It should be understood that transmitting R2D control information and R2D repetitive data in a single PRDCH can reduce latency and improve resource utilization. The R2D repetitive data scheduled by the R2D control information can avoid the first device not having enough time to solve the scheduling information in the next PRDCH transmission, thus ensuring the reliability of transmission.

[0197] In some implementations, N PRDCHs can be sent on consecutive time-domain resources, such as... Figure 18 As shown, the time-domain resources received by the first device are continuous across N PRDCHs, with no time gap. R2D control information can be used to indicate the starting position offset of the first PRDCH.

[0198] In some implementations, the first information is carried in higher-layer signaling or physical-layer signaling.

[0199] In some implementations, the frequency domain resource information of the PRDCH resource includes one or more of the following: small frequency shift parameter, frequency shift amount, frequency band location, bandwidth size, guard band size, center frequency, frequency domain resource start position, frequency domain resource end position, frequency domain resource channel number, and frequency domain reference point.

[0200] In some implementations, the frequency domain resource location of the first data is determined based on frequency domain resource information.

[0201] For example, the second device can indicate the center frequency or the frequency domain offset at the start / end of the frequency domain resource. This offset can be the absolute value of the offset, or it can indicate the smallest frequency domain unit / granularity of the offset and the number of units in that smallest granularity. For example, if the smallest frequency shift unit is 180kHz, the second device can indicate the number of frequency shift units, X. This allows the location of the frequency domain resource for the first data to be determined.

[0202] For example, the second device can indicate the channel number / index / ID. For instance, the protocol may pre-define or the second device may instruct / configure the frequency domain reference point of the channel, the protocol may pre-define or the second device may instruct / configure the starting position / center frequency of the first channel, and the channel bandwidth, such as... Figure 19 As shown. The second device can indicate the channel number / index / ID, while the first device can determine the frequency domain resources (such as one or more channel resources) for R2D repetitive data.

[0203] In some implementations, for the case where R2D repetitive data is transmitted in a PRDCH, the second device can indicate / configure information related to frequency domain resources.

[0204] For example, the second device indicates / configures the center frequency location of the frequency domain resource, the transmission bandwidth of the frequency domain resource, and / or the guard band size. The second device indicates the absolute location of the center frequency point, such as 400MHz; or it indicates the offset of the center frequency point from a frequency domain reference point, which can be the start (lowest point) / end (highest point) / center frequency point of the frequency domain resource in the indication / configuration information or other R2D messages.

[0205] For example, the second device indicates / configures the starting position of frequency domain resources, and / or, transmission bandwidth, and / or, guard band size.

[0206] For example, the second device indicates / configures the start and end positions of frequency domain resources, and / or the guard band size.

[0207] In some implementations, the second device indicates the start / end position of the frequency domain resource. This can be an absolute position indicating the start / end position, such as 400MHz; or it can be an offset of the start / end position from a frequency domain reference point. The frequency domain reference point can be the start (lowest point) / end (highest point) / center frequency of the frequency domain resource indicated by the configuration information or other R2D messages.

[0208] In some implementations, the protocol can predefine information related to frequency domain resources. For example, the protocol can predefine the frequency shift amount, and / or frequency band location, and / or bandwidth size, and / or guard band size, and / or center frequency, and / or start / end position of the frequency domain resources for R2D repetitive data, etc. Furthermore, the protocol can predefine that the reference point for the frequency shift amount is the frequency domain resource of the indication / configuration information or other R2D messages, etc.

[0209] In some implementations, when the first data is transmitted in N PRDCHs, the frequency domain resource locations and sizes of the N PRDCHs are the same. For the specific determination method, please refer to the example above for transmitting duplicate data in N PRDCHs, which will not be repeated here.

[0210] Of course, the frequency domain resource locations of the N PRDCHs can also be different. R2D repetitive data is transmitted at different frequency domain locations, utilizing frequency domain diversity gain, which can improve the performance against interference and fading in outdoor scenarios, enhance the coverage capability of edge users, and improve the reliability of transmission.

[0211] For example, the second device may indicate / configure the absolute frequency domain position of the frequency domain resource center frequency and / or the start / end position of the frequency domain resource for each PRDCH, and / or the PRDCH transmission bandwidth size, and / or the PRDCH guard band size.

[0212] For example, the second device may respectively indicate / configure the center frequency of the frequency domain resources of each PRDCH and / or the offset of the start / end position of the frequency domain resources from the frequency domain position of the R2D control information, and / or the PRDCH transmission bandwidth size, and / or the guard band size of the PRDCH.

[0213] For example, the offset of the frequency domain resource center frequency and / or the start / end position of the frequency domain resource of the first PRDCH from the frequency domain position of the R2D control information, as indicated / configured by the second device, and the offset of the frequency domain resource center frequency and / or the start / end position of the frequency domain resource of the nth PRDCH from the frequency domain position of the (n-1)th PRDCH, where N≥n≥2, and / or the PRDCH transmission bandwidth size, and / or the PRDCH guard band size.

[0214] In some implementations, the bandwidth and / or guard band size of the N PRDCHs can be the same or different. The case where the bandwidth and / or guard band size of the N PRDCHs are different can be indicated by R2D control information.

[0215] In some implementations, R2D control information and R2D duplicate data can be transmitted on different PRDCHs or on the same PRDCH. This application does not impose specific limitations on this.

[0216] The R2D control information in the above implementation can also be replaced with first information or other R2D information. The other R2D information can be at least one of the following: synchronization information, paging message, Msg2, Msg4, access timing trigger message, R2D upper layer data transmission message, and scheduling information.

[0217] In some implementations, the first device receives second information sent by the second device, the second information indicating the number of repetitions of the second data. It should be understood that the second information may be the same as or different from the first information mentioned above.

[0218] In some implementations, the number of repetitions of the second data is determined based on one or more of the following information reported by the first device: R2D signal power related information; path loss measurement related information; D2R signal power related information.

[0219] As an example, the signal power-related information of R2D can be the RSRP-related information of R2D. For instance, if the number of repetitions supported by R2D (i.e., the number of repetitions of the second data) is {2, 4, 8}, and the RSRP is between [thrs1, thrs2], then the second device uses R2D repetition with a repetition count of 2; if the RSRP is between [thrs3, thrs4], then the second device uses R2D repetition with a repetition count of 4; and if the RSRP is between [thrs5, thrs6], then the second device uses R2D repetition with a repetition count of 8. Here, [thrs5, thrs6] represents the smallest or weakest information value, and [thrs1, thrs2] represents the largest or strongest information value.

[0220] As another example, the second device determines the number of repetitions of the second data based on the power information of the D2R signal. For example, if the power of the D2R signal received by the second device is between [thrs1, thrs2], the second device determines to use R2D repetition with a repetition number of Q, where Q is set according to requirements.

[0221] In some other implementations, the number of repetitions of the second data is determined based on one or more of the following information:

[0222] The time interval T during which the second device did not receive a D2R message from the first device; the current number of repetitions of the second data; and the number of transmissions of the first data.

[0223] As an example, if the second device does not receive a D2R message from the first device within time T, the second device will use R2D retransmission and determine the number of repetitions. The value of T can be indicated / configured by the second device or predefined by the protocol.

[0224] For example, if the second device does not receive a D2R message from the first device within time T, the second device will use R2D repeated transmission and use the minimum number of repetitions.

[0225] For example, if the second device sends R2D repeat data (i.e., the current number of repeats) and does not receive a D2R message from the first device within time T, the second device increases the number of repeats and retransmits the R2D repeat data. Specifically, if the supported number of repeats for R2D is {2, 4, 6, 8}, and the second device sends an R2D repeat transmission with 2 repeats but does not receive a D2R message from the first device within time T, the second device retransmits the R2D message with 4 repeats. This process continues, allowing the second device to gradually increase the number of repeats to send R2D repeat messages.

[0226] As another example, if the second device sends X (i.e., the number of times the first data is transmitted) R2D duplicate data and does not receive a D2R message from the first device, then the second device will use R2D duplicate transmission and determine the number of duplicates. The value of X can be indicated / configured by the second device or predefined by the protocol.

[0227] For example, if the second device sends X R2D transmissions but does not receive a D2R message from the first device, the second device will use R2D repeated transmissions with the minimum number of repetitions.

[0228] To facilitate understanding, the communication method of this application is described in more detail below with examples. It should be noted that the embodiments below are merely to help those skilled in the art understand the embodiments of this application, and are not intended to limit the embodiments of this application to the specific values ​​or scenarios illustrated. Those skilled in the art can obviously make various equivalent modifications or changes based on the specific examples given, and such modifications or changes also fall within the scope of the embodiments of this application. It should be noted that in the following examples, the first device is denoted as "device"; the second device is denoted as "reader"; the first data includes one or more R2D data, or the first data includes one or more data blocks; the R2D repetition number is denoted as Nr, which can refer to the number of repetitions of the second data, or it can refer to the number of R2D data or data blocks included in the first data; and the first information is R2D control information, as illustrated in the example.

[0229] R2D repeated transmissions are transmitted within a PRDCH.

[0230] 1. R2D bit repetition or R2D chip repetition is transmitted in a PRDCH.

[0231] like Figure 11 As shown, auxiliary signals such as midamble, CRC, specific sequences, and specific codewords are inserted into the PRDCH carrying R2D repetition.

[0232] The number of auxiliary signals inserted is M. The number of auxiliary signals can be indicated to the device by the reader, or determined according to predefined rules (i.e., a method pre-defined by the protocol).

[0233] The case is determined by predefined rules, for example, M is the same as (Nr-1). For another example, the device can calculate the value of M based on the length L of the R2D data between adjacent auxiliary signals.

[0234] The R2D data length between the first auxiliary signal and the preamble (such as R-TAS), as well as between subsequent adjacent auxiliary signals, is L. If the R2D data length between the last auxiliary signal and the R2D postamble is less than L, the reader can make its length equal to L by padding bits, or no other operation is performed.

[0235] The auxiliary signal can have multiple lengths or only one length. When the auxiliary signal has multiple lengths, the length can be the same in each R2D repetition, but the length can be different in different R2D repetitions. Conversely, the length can also be the same in different R2D repetitions, meaning the auxiliary signal has only one length. The length of the auxiliary signal is indicated to the device by the reader or determined according to predefined rules.

[0236] For example, according to predefined rules, if the TBS range of the first or second data is between [L1, L2], the length of the auxiliary signal is S1; if the TBS range is between [L2, L3], the length of the auxiliary signal is S2. This application does not impose specific restrictions on the size of S1 and S2, which can be set according to requirements. The values ​​of L1 to L3 can also be set according to requirements.

[0237] For example, if the number of R2D repetitions is Nr1, then the length of the auxiliary signal is S1; if the number of R2D repetitions is Nr2, then the length of the auxiliary signal is S2. The values ​​of Nr1 and Nr2 can be set according to requirements.

[0238] Optionally, the auxiliary signal can be an m-sequence / Golay sequence / Walsh sequence, etc.

[0239] Optionally, the auxiliary signal can be linearly coded.

[0240] 2. R2D blocks are repeatedly transmitted within a single PRDCH.

[0241] like Figure 12 As shown, auxiliary signals such as midamble, CRC codewords, specific sequences, and clock calibration signals are inserted between repeated R2D data blocks. In other words, auxiliary signals are inserted between two consecutively repeated data blocks, specifically between the end of one data block and the beginning of the next.

[0242] In this application, the device can distinguish R2D data or data blocks based on auxiliary signals. For example, if the device cannot accurately receive a certain repeated part of the R2D for some reason, the device can correctly decode the other parts of the data information based on the distinguished R2D data or data blocks. In addition, because the repetition causes the R2D transmission data to be too long, and the local clock accuracy of the A-IoT device is low, sampling frequency offset (SFO) and carrier frequency offset (CFO) will occur. Inserting auxiliary signals into the PRDCH can help the device calibrate the SFO and CFO, further improving the accuracy of transmission.

[0243] In some implementations, auxiliary signals are inserted between repeating data blocks. These auxiliary signals can be R2D / D2R preambles, midambles, or postambles. For example, the auxiliary signal can be an existing R2D preamble (such as R-TAS), R2D midamble, or D2R preamble or midamble as defined in R19. Alternatively, the auxiliary signal can be a newly defined R2D preamble sequence, such as an m-sequence, Golay sequence, or Walsh sequence.

[0244] The length of the auxiliary signal is related to the data length of the data block. For example, if the data length / size of the data block is in the range [S1, S2], then the length of the auxiliary signal is L1; if the data length / size of the data block is in the range [S2, S3], then the length of the auxiliary signal is L2.

[0245] The type / length of the auxiliary signal is related to the type of message repeated in R2D. In some implementations, the data repeated in R2D can be one or more of the following: synchronization information / A-IoT message / Msg2 (i.e., Random ID response message) / Msg4 / Access Occasion Trigger message / R2D Upper Layer Data Transfer message / scheduling information / etc. (The above-mentioned message types for repeated R2D are applicable to any R2D transmission in this invention).

[0246] In some implementations, CRC codewords (a type of auxiliary signal) can be inserted between repeated data blocks. The CRC codewords can be determined according to the CRC generation method in NR / LTE.

[0247] For example, the length of the CRC codeword is related to the data length of the data block and the message type. For instance, if the data length of the data block is in the range [S1, S2], the CRC codeword length is L1; if the data length of the data block is in the range [S2, S3], the CRC codeword length is L2. As another example, if the message type repeated in the data block is synchronization information, the CRC codeword length is L1; or if the message type repeated in the data block is A-IoT paging message, the CRC codeword length is L2.

[0248] As mentioned earlier, specific sequences can be inserted between repeating data blocks. These sequences can be m-sequences, Golay sequences, Walsh sequences, etc. The length of the specific sequence is related to the data length of the data block and the message type. This will not be elaborated further based on the above information.

[0249] R2D repeated transmissions are transmitted in N PRDCHs.

[0250] It should be understood that R2D repeated data can be transmitted independently over the network among N PRDCHs, and each PRDCH can choose the optimal transmission path, thus improving transmission robustness. Even if a PRDCH cannot be correctly received by the device, the R2D repeated data can still be correctly decoded through other PRDCHs, further improving transmission reliability.

[0251] 1. The data lengths of the R2D duplicate data on N PRDCHs are either the same or different.

[0252] In some implementations, the R2D repeating data on N PRDCHs has the same data length. R2D repeating can be R2D bit repeating or R2D chip repeating (this type of repeating is transmitted in multiple PRDCHs in a similar way to R2D transmission by packetizing).

[0253] For example, R2D repeated data (i.e., the first data mentioned above) is divided into N transport blocks and transmitted in N PRDCHs. If the length / size of the R2D repeated data cannot be divided into N transport blocks, then the minimum number of bits / codewords that make the data size divisible by N are padded after the R2D repeated data. The value of N is indicated to the device by the reader or is predetermined by the protocol.

[0254] For example, if the length of the R2D repeating data in each PRDCH is S, and N is the minimum value that can transmit all the R2D repeating data, and the length of the R2D repeating data in the last PRDCH is less than S, then bits can be padded at the end of the data to make the length of the repeating data that does not meet S S. The values ​​of N and S are indicated to the device by the reader, or are predetermined by the protocol.

[0255] In this application, by keeping the length of repeated R2D data transmission on multiple PRDCHs the same, it helps to reduce the complexity of device receiving R2D transmissions.

[0256] In some other implementations, the transmitted data length of R2D repeating data on N PRDCHs is the same, and R2D repeating can be the case of R2D block repeating.

[0257] For example, if each repeated transport block is transmitted in a separate PRDCH, then N and Nr are the same. Figure 13 As shown, taking an example where the number of repetitions Nr equals 3, each repeated transport block is transmitted in a separate PRDCH. The value of N is Nr by default, or it can be indicated by the network device.

[0258] For example, the length of repeated data in each PRDCH is S, and N is the minimum value that can transmit an R2D repetition. If the data length in the last PRDCH is less than S, bits are padded at the end of the data to make its length S. S may be the same as or different from a repeated data block. (This is similar to the fact that the data length transmitted in each PRDCH is fixed, for example, it is predetermined by the protocol, but it may not be the same as the length of the repeated data block).

[0259] Associations among N PRDCHs

[0260] In some implementations, the frequency domain resources of the N PRDCHs are the same, but their time domain resources are different. Alternatively, the frequency domain resources of the N PRDCHs are different, and their time domain resources are also different.

[0261] In some implementations, the data rates of the N PRDCHs may be the same or different, and / or the modulation schemes and modulation parameters of the N PRDCHs may be the same or different. For example, all N PRDCHs may use OOK-4 modulation, and the m value of OOK-4 modulation may be the same.

[0262] In some implementations, the preamble / intermule / postamble of the N PRDCHs may be the same or different.

[0263] It should be understood that if all parameters for N PRDCHs are identical, the configuration of related parameters can be reduced, thereby reducing signaling overhead. Furthermore, it reduces the configuration information required for the first device to receive and decode, lowering the complexity of signal processing for the first device. Using different parameters to transmit PRDCHs allows for parameter adjustment based on different channel conditions, providing greater flexibility to adapt to varying channel states.

[0264] Determining R2D Repeated Transfer Resources

[0265] 1. Determining the temporal resources of R2D repetitive data.

[0266] In some implementations, the information related to the time-domain resources repeated in R2D includes at least one of the following: the start position of the time-domain resource, the end position of the time-domain resource, the duration of the time-domain resource, the offset of the time-domain resource (which may be a start offset or an end offset), and the period of the time-domain resource (i.e., the time-domain resource may be periodic).

[0267] In some implementations, R2D control information can be used to configure / indicate information related to time-domain resources. The device receives R2D control information from the reader and determines a first time-domain resource based on the R2D control information. This first time-domain resource is used to receive the transmission of R2D repetitions. The R2D control information may include information related to time-domain resources.

[0268] In some implementations, R2D control information can be carried by higher-layer signaling, such as MAC CE, or by physical layer signaling.

[0269] In some implementations, R2D control information and R2D repeating data can be transmitted on different PRDCHs or on the same PRDCH.

[0270] In some implementations, the unit of time-domain resources can be a time unit (such as the time unit of NR). For example, the time unit can be a frame, subframe, time slot, or symbol of a certain subcarrier spacing (SCS); it can also be an absolute time unit, such as seconds, milliseconds, microseconds, etc.; it can also be the chip duration of R2D / D2R; or it can be other defined time units.

[0271] In this application, the offset reference points of the temporal domain resources of R2D repeating data include a start offset reference point and an end offset reference point.

[0272] For cases where R2D repeating data (i.e., the first data) is transmitted in one or more PRDCHs, for example, the start offset reference point of the time domain resource of the R2D repeating data is the end / start position of the time domain resource of the R2D control information, or the end / start position of the time domain resource of the previous R2D transmission received by the device, or the end / start position of the time domain resource of the previous D2R transmission sent by the device.

[0273] For example, the end offset reference point of the R2D repetition time domain resource is the end / start position of the time domain resource of the R2D control information, or the end / start position of the time domain resource of the previous R2D transmission received by the device, or the end / start position of the time domain resource of the previous D2R transmission sent by the device.

[0274] In some implementations, for the case where R2D duplicate data is transmitted across N PRDCHs, see [link to relevant documentation]. Figure 14 The R2D control information is used to indicate the offset from the start position of each PRDCH to the end position of the R2D control information.

[0275] In other implementations, for the case where R2D repetitive data is transmitted across N PRDCHs, the start / end offset reference point of the temporal resource of the first PRDCH is the start / end position of the temporal resource of the R2D control information. The start / end offset reference point of the (n+1)th PRDCH temporal resource is the start / end position of the nth PRDCH temporal resource, where N ≥ n ≥ 1, and n is an integer.

[0276] See Figure 15Taking an R2D repetition count of 4 as an example, the R2D control information can be used to indicate Toffset0, Toffset1, Toffset2, and Toffset3 respectively. The values ​​of Toffset0, Toffset1, Toffset2, and Toffset3 can be the same or different. Alternatively, the R2D control information can be used to indicate the Toffset value, where Toffset0, Toffset1, Toffset2, and Toffset3 all have the same value: Toffset.

[0277] In some implementations, for cases where PRDCHs are contiguous in the time domain, R2D control information can be used to indicate the start / end offset of the time domain resources for the (1+n1×a)th PRDCH. Here, 'a' is an integer greater than 1, 0 ≤ n1 ≤ N1, and n1 is an integer, representing the number of contiguous PRDCHs in the time domain. 'N1' is an integer greater than or equal to 1. 'a' and 'N1' can be indicated by the second device or predefined by the protocol. Specifically, the time domain resources from the (1+n1×a)th PRDCH to the (n1+1)×ath PRDCH are contiguous, such as... Figure 16 As shown.

[0278] In some implementations, the reference point for the start / end offset of the time-domain resource of the n1×a+1th PRDCH can be the start / end position of the time-domain resource of the R2D control information, or it can be the start / end position of the time-domain resource of the n1×ath PRDCH. For example... Figure 16 As shown, a is 2, and the reference point for the start offset of the third PRDCH time domain resource is the end position of the second PRDCH time domain resource.

[0279] In some implementations, R2D control information can reside in the same PRDCH as the R2D repeating data. The R2D control information can be used to indicate the start / end offset of the temporal resources in the next PRDCH. Taking an R2D repeating data repetition count of 3 as an example, [the following text is incomplete and requires further context]. Figure 17 The first R2D control message indicates the time-domain resource start offset of the first PRDCH, the second R2D control message indicates the time-domain resource start offset of the second PRDCH, and so on. The R2D repetitive data indicated by the current R2D control message is transmitted in the next PRDCH following the current R2D control message.

[0280] It should be understood that transmitting R2D control information and R2D repetitive data in a single PRDCH can reduce latency and improve resource utilization. The R2D repetitive data scheduled by R2D control information can avoid the device not having enough time to resolve the scheduling information in the next PRDCH transmission, thus ensuring the reliability of transmission.

[0281] In some implementations, N PRDCHs can be sent on consecutive time-domain resources, such as... Figure 18 As shown, the device receives N PRDCHs with continuous time-domain resources, without any time gap. R2D control information can be used to indicate the starting position offset of the first PRDCH.

[0282] In this application, a time-domain offset (Toffset) is configured in the PRDCH transmission to provide a time-domain interval, thereby preventing the device from losing power due to excessively long PRDCH transmission and long device reception time. The time interval between PRDCH transmissions can be used by the device for charging, ensuring that the device has continuous power during reception and preventing the device from failing to receive correctly due to power loss.

[0283] The offset value in this application can be determined based on the capacitance information, power information, or charging information reported by the device.

[0284] In some implementations, time-domain resource-related information can be predefined by the protocol. Alternatively, some time-domain resource-related information can be predefined by the protocol, while others can be indicated to the device by the reader.

[0285] For example, the protocol predetermines that the start offset and / or duration of N PRDCH transmissions are the same, and the corresponding values ​​are indicated to the device by the reader.

[0286] 2. Determining the frequency domain resources of R2D repetitive data.

[0287] In some implementations, the information related to frequency domain resources includes at least one of the following: small frequency shift parameter, frequency shift amount, frequency band location, bandwidth size, guard band size, center frequency, start / end location of frequency domain resources, channel number / index / ID, etc.

[0288] In some implementations, the information related to frequency domain resources can be predefined by the protocol, or the information related to frequency domain resources can be indicated / configured by the reader, or part of the information related to frequency domain resources can be predefined by the protocol and part can be indicated / configured by the reader to the device.

[0289] In some implementations, R2D control information can be carried by higher-layer signaling, such as MAC CE, or by physical layer signaling.

[0290] In some implementations, frequency domain resource-related information can be predefined by the protocol. For example, the frequency domain resources of R2D repeating data are the same as those of R2D control information, where R2D control information can be used to indicate the frequency domain resources of R2D repeating data and / or the number of repetitions of R2D repeating data.

[0291] For example, R2D repeating data may have the same frequency domain location as other specific R2D messages. For example, other specific R2D messages may include one or more of the following: R2D synchronization information / A-IoT paging message / Msg2 (Random ID response message) / Msg4 / Access Occasion Trigger message / R2D Upper Layer Data Transfer message / Scheduling information / etc.

[0292] For example, R2D repetitive data is transmitted in N PRDCHs, and the frequency domain resource locations of the N PRDCHs may be the same or different.

[0293] In some implementations, the unit of frequency domain resources can be a frequency domain unit (such as the frequency domain unit defined in NR), for example, a resource block (RB); it can also be an absolute frequency domain unit, such as Hz, kHz, MHz, etc.; or it can be other defined frequency domain units.

[0294] In some implementations, the reader can indicate the frequency offset of the center frequency or the start / end of the frequency domain resource. This offset can be the absolute value, or it can indicate the smallest frequency domain unit / granularity of the offset and the number of units in that smallest granularity. For example, if the smallest frequency shift unit is 180kHz, the reader can indicate the number of frequency shift units, X.

[0295] In other implementations, the channel number / index / identifier (ID) is indicated. For example, the protocol pre-defines or the reader instructs / configures the frequency domain reference point for the channel, the protocol pre-defines or the reader instructs / configures the starting position / center frequency of the first channel, and the channel bandwidth, such as... Figure 19 As shown. The Reader can indicate the channel number / index / ID, while the device can determine the frequency domain resources (such as one or more channel resources) for R2D repetitive data.

[0296] In some implementations, for the case where R2D repetitive data is transmitted in a PRDCH, the reader can indicate / configure information related to frequency domain resources.

[0297] For example, the reader indicates / configures the center frequency location of the frequency domain resource, its transmission bandwidth, and / or guard band size. The reader indicates the absolute location of the center frequency, such as 400MHz; or it indicates the offset of the center frequency location from a frequency domain reference point, which can be the start (lowest point) / end (highest point) / center frequency of the frequency domain resource in the indication / configuration information or other R2D messages. In some implementations, the other R2D messages can be any of the following: synchronization information, paging messages, Msg2, Msg4, access timing trigger messages, R2D upper-layer data transmission messages, and scheduling information.

[0298] For example, the reader indicates / configures the starting position of frequency domain resources, and / or the transmission bandwidth, and / or the guard band size.

[0299] For example, the reader indicates / configures the start and end positions of frequency domain resources, and / or the guard band size.

[0300] In some implementations, the reader indicates the start / end position of the frequency domain resource. This can be an absolute position indicating the start / end position, such as 400MHz; or it can be an offset of the start / end position from a frequency domain reference point. The frequency domain reference point can be the start (lowest point) / end (highest point) / center frequency of the frequency domain resource indicating / configuration information or other R2D messages.

[0301] In some implementations, the protocol can predefine information related to frequency domain resources. For example, the protocol can predefine the frequency shift amount, and / or frequency band location, and / or bandwidth size, and / or guard band size, and / or center frequency, and / or start / end position of the frequency domain resources for R2D repetitive data, etc. Furthermore, the protocol can predefine that the reference point for the frequency shift amount is the frequency domain resource of the indication / configuration information or other R2D messages, etc.

[0302] In some implementations, for the case where R2D repeating data (i.e., the first data) is transmitted in N PRDCHs, the frequency domain resource locations and sizes of the N PRDCHs are the same. For the specific determination method, please refer to the example above for the transmission of repeating data in N PRDCHs, which will not be repeated here.

[0303] Of course, the frequency domain resource locations of the N PRDCHs can also be different. R2D repetitive data is transmitted at different frequency domain locations, utilizing frequency domain diversity gain, which can improve the performance against interference and fading in outdoor scenarios, enhance the coverage capability of edge users, and improve the reliability of transmission.

[0304] For example, the reader can indicate / configure the absolute frequency domain position of the frequency domain resource center point and / or the start / end position of the frequency domain resource for each PRDCH, and / or the PRDCH transmission bandwidth size, and / or the PRDCH guard band size.

[0305] For example, the reader can instruct / configure the center frequency of the frequency domain resources of each PRDCH and / or the offset of the start / end position of the frequency domain resources from the frequency domain position of the R2D control information, and / or the PRDCH transmission bandwidth size, and / or the guard band size of the PRDCH.

[0306] For example, the offset between the center frequency point and / or the start / end position of the frequency domain resource of the first PRDCH and the frequency domain position of the R2D control information, as indicated / configured by the reader, and the offset between the center frequency point and / or the start / end position of the frequency domain resource of the nth PRDCH and the frequency domain position of the (n-1)th PRDCH, where N≥n≥2, and / or the PRDCH transmission bandwidth, and / or the guard band size of the PRDCH.

[0307] In some implementations, the bandwidth and / or guard band size of the N PRDCHs can be the same or different. The case where the bandwidth and / or guard band size of the N PRDCHs are different can be indicated by R2D control information.

[0308] In some implementations, R2D control information and R2D duplicate data can be transmitted on different PRDCHs or on the same PRDCH. This application does not impose specific limitations on this.

[0309] Determine the number of repetitions for R2D duplicate data

[0310] In some implementations, the reader instructs / configures the device, the device receives second information from the reader, and determines the number of repetitions of the R2D transmission based on the second information.

[0311] In some implementations, the reader determines the number of repetitions of R2D repeated data based on certain information reported by the device and instructs the device accordingly. For example, the device reports information related to the RSRP of certain signals based on measurements; another example is the device reporting information related to path loss measurements, and so on.

[0312] In some implementations, the Reader can increase or decrease the number of repetitions in R2D duplicate data based on the information reported by the device.

[0313] For example, based on the RSRP-related information of a certain transmission / signal reported by the device, when the RSRP-related information value is higher than a certain threshold, the reader reduces the number of repetitions; when the RSRP-related information value is lower than a certain threshold, the number of repetitions is increased.

[0314] For example, R2D repetition supports a repetition count of {2, 4, 8}. If RSRP is between [thrs1, thrs2], the reader uses R2D repetition with a repetition count of 2; if RSRP is between [thrs3, thrs4], the reader uses R2D repetition with a repetition count of 4; and if RSRP is between [thrs5, thrs6], the reader uses R2D repetition with a repetition count of 8. Here, [thrs5, thrs6] represents the smallest or weakest information value, and [thrs1, thrs2] represents the largest or strongest information value.

[0315] In some implementations, the Reader determines the number of repetitions for R2D repeating data based on the D2R signal sent by the device. For example, the Reader determines the number of repetitions based on the power information of the D2R signal. If the power of the D2R signal received by the Reader is between [thrs1, thrs2], the Reader uses R2D repetition with a repetition count of Q, where Q is set according to requirements.

[0316] Among them, D2R signals can refer to reference signals covering the coverage area of ​​the communication system, random ID messages such as Msg1 in CBRA, upper layer data transfer messages, or other types of D2R messages / signals.

[0317] In some implementations, the Reader determines the number of repetitions for R2D based on predefined rules.

[0318] As an example, if the reader does not receive a D2R message from the device within time T, the reader will use R2D retransmission and determine the number of repetitions. The value of T can be indicated / configured by the reader or predefined by the protocol.

[0319] For example, if the reader does not receive a D2R message from the device within time T, the reader will use R2D retransmission with the minimum number of repetitions.

[0320] For example, if the reader sends R2D duplicate data and does not receive a D2R message from the device within a time T, the reader increases the number of repetitions and retransmits the R2D duplicate data. Specifically, if the supported number of repetitions for R2D is {2, 4, 6, 8}, and the reader sends an R2D duplicate transmission with 2 repetitions but does not receive a D2R message from the device within a time T, the reader retransmits the R2D message with 4 repetitions. This process continues, allowing the reader to gradually increase the number of repetitions to send R2D duplicate messages.

[0321] As another example, if the reader sends X R2D transmissions and does not receive a D2R message from the device, the reader will perform R2D retransmission and determine the number of repetitions. The value of X can be indicated / configured by the reader or predefined by the protocol.

[0322] For example, if the reader sends X R2D transmissions but does not receive a D2R message from the device, the reader will use R2D retransmission with the minimum number of repetitions.

[0323] For example, if the reader sends an R2D repeat but does not receive a D2R message from the device, the reader will increase the number of repeats and resend the R2D repeat data. Specifically, if the supported number of repeats for R2D is {2, 4, 6, 8}, and the reader sends an R2D repeat with 2 repeats but does not receive a D2R message from the device, the reader will resend the R2D message with 4 repeats. And so on, the reader can gradually increase the number of repeats when sending R2D repeat messages.

[0324] This application configures / instructs the R2D repeating transmission resources through the reader, so that the device does not need to blindly detect R2D transmissions and can directly receive R2D transmissions on the corresponding resources, thereby reducing the power consumption of the device listening to R2D and improving the reliability of transmission.

[0325] The R2D repetitive transmission scheme proposed in this application enhances the signal-to-noise ratio of R2D transmission and utilizes time diversity gain to improve the reliability of successful data reception, thereby enhancing the transmission coverage.

[0326] The method embodiments of this application have been described in detail above with reference to the accompanying drawings. The apparatus embodiments of this application will now be described in detail below with reference to the accompanying drawings. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the foregoing method embodiments.

[0327] Figure 20 This is a schematic diagram of the structure of a communication device provided in one embodiment of this application. Figure 20 The communication device 2000 shown can be the first device mentioned above. The communication device 2000 may include a first communication module 2010. The first communication module 2010 is used to receive first data sent by the second device, the first data being data obtained by repeating second data using R2D; the first data is any one of the following: R2D bit repetition of the second data, R2D chip repetition of the second data, or R2D block repetition of the second data.

[0328] In some implementations, the R2D bit repetition is any of the following: R2D information bit repetition, R2D encoding bit repetition.

[0329] In some implementations, the R2D block repetition is any of the following: R2D information bit block repetition, R2D encoded bit block repetition, or R2D modulation symbol block repetition.

[0330] In some implementations, the first data is carried on one or more PRDCH resources.

[0331] In some implementations, one or more auxiliary signals are inserted between the first data.

[0332] In some implementations, the number of auxiliary signals inserted on the PRDCH resource is configured by the second device, or determined based on a method predefined by the protocol.

[0333] In some implementations, the number of auxiliary signals is determined based on a pre-defined method in the protocol, and the number of auxiliary signals is associated with one or more of the following: the number of repetitions of the second data; the length of the first data between two adjacent auxiliary signals; the data length of the first data; and the data length of the second data.

[0334] In some implementations, the data length of the R2D data between adjacent auxiliary signals, and / or between the first auxiliary signal and the preamble, and / or between the last auxiliary signal and the postamble, is configured by the second device or determined based on a method predefined by the protocol.

[0335] In some implementations, the first data on the PRDCH resource includes a first R2D data block and a second R2D data block. If the length of the second R2D data block is less than the length of the first R2D data block, then the length of the second R2D data block is supplemented so that the length of the second R2D data block is equal to the length of the first R2D data block; the second R2D data block is the last R2D data block on the PRDCH resource.

[0336] In some implementations, the PRDCH resource includes a plurality of auxiliary signals, the plurality of auxiliary signals having one or more lengths.

[0337] In some implementations, the length of the auxiliary signal is predetermined by the protocol and is associated with one or more of the following: the data size or length of the first data; the size or length of the second data; the data type of the first data; the data type of the second data; the number of repetitions of the second data; the number of auxiliary signals; and the length of the R2D data block between adjacent auxiliary signals, and / or between the first auxiliary signal and the preamble, and / or between the last auxiliary signal and the postamble.

[0338] In some implementations, the data type of the first data is any of the following: synchronization information, paging message, Msg2, Msg4, access timing trigger message, R2D upper layer data transmission message, and scheduling information.

[0339] In some implementations, the first data is carried on multiple PRDCH resources, and the data length of the first data on each of the multiple PRDCH resources may be the same or different.

[0340] In some implementations, the first data is carried on multiple PRDCH resources, and the number of multiple PRDCH resources is the same as or different from the number of repetitions of the second data.

[0341] In some implementations, if the data length of the first data on the last PRDCH resource among a plurality of PRDCH resources is less than the data length of the first data on other PRDCH resources, then the data length of the first data on the last PRDCH resource is filled in so that the data length of the first data on each PRDCH resource is the same.

[0342] In some implementations, the frequency domain resources of the multiple PRDCH resources are the same or different.

[0343] In some implementations, the data rates of the multiple PRDCH resources are the same or different; and / or, the modulation schemes and modulation parameters of the multiple PRDCH resources are the same or different; and / or, the auxiliary signals inserted on the multiple PRDCH resources are the same or different.

[0344] In some implementations, the time-domain resource information of the PRDCH resource includes one or more of the following: the start time of the time-domain resource, the end time of the time-domain resource, the duration of the time-domain resource, the offset of the time-domain resource, and the period of the time-domain resource.

[0345] In some implementations, the starting offset reference point of the time domain resource of the first data is the end or start time of the time domain resource of the first information, and the first information is used to schedule the time domain resource of the first data; or, the starting offset reference point is the end or start time of the time domain resource of the previous R2D transmission received by the first device; or, the starting offset reference point is the end or start time of the time domain resource of the previous D2R transmission sent by the first device.

[0346] In some implementations, the first data is carried on multiple PRDCH resources, which include N PRDCH resources, where N is an integer greater than 1; the start offset reference point of the time domain resource of the first PRDCH resource is the end or start time of the time domain resource of the first information, and the start offset reference point of the time domain resource of the (n+1)th PRDCH resource is the end or start time of the time domain resource of the nth PRDCH resource, wherein the first information is used to schedule the time domain resource of the first data, and N>n>1.

[0347] In some implementations, the first data is carried on multiple PRDCH resources, including a first PRDCH resource and a second PRDCH resource. First information on the first PRDCH resource is used to indicate the starting offset of the temporal resource of the second PRDCH resource. The first information is used to schedule the temporal resource of the first data. The first PRDCH resource is located before the second PRDCH resource in the temporal domain.

[0348] In some implementations, the first information is carried in higher-layer signaling or physical-layer signaling.

[0349] In some implementations, the frequency domain resource information of the PRDCH resource includes one or more of the following: small frequency shift parameter, frequency shift amount, frequency band position, bandwidth size, guard band size, center frequency point, frequency domain resource start position, frequency domain resource end position, frequency domain resource channel number, and frequency domain reference point.

[0350] In some implementations, the frequency domain resource location of the first data is determined based on the frequency domain resource information.

[0351] In some implementations, the communication device 2000 further includes a second communication module 2020 for receiving second information sent by the second device, the second information being used to indicate the number of repetitions of the second data.

[0352] In some implementations, the number of repetitions of the second data is determined based on one or more of the following information reported by the first device: R2D signal power related information; path loss measurement related information; D2R signal power related information.

[0353] In some implementations, the number of repetitions of the second data is determined based on one or more of the following: the time interval during which the second device has not received a D2R message from the first device; the current number of repetitions of the second data; and the number of times the first data has been transmitted.

[0354] In some implementations, the first device is an environmental Internet of Things (A-IoT) terminal device.

[0355] In some implementations, the second device is a network device; or an intermediate node, through which the first device communicates with the network device.

[0356] Figure 21 This is a schematic diagram of the structure of a communication device provided in another embodiment of this application. Figure 21 The communication device 2100 shown can be the second device mentioned above. The communication device 2100 may include a first communication module 2110. The first communication module 2110 is used to send first data to the first device, the first data being data obtained by repeating second data using R2D; the first data is any one of the following: R2D bit repetition of the second data, R2D chip repetition of the second data, or R2D block repetition of the second data.

[0357] In some implementations, the R2D bit repetition is any of the following: R2D information bit repetition, R2D encoding bit repetition.

[0358] In some implementations, the R2D block repetition is any of the following: R2D information bit block repetition, R2D encoded bit block repetition, or R2D modulation symbol block repetition.

[0359] In some implementations, the first data is carried on one or more PRDCH resources.

[0360] In some implementations, one or more auxiliary signals are inserted between the first data.

[0361] In some implementations, the number of auxiliary signals inserted on the PRDCH resource is configured by the second device, or determined based on a method predefined by the protocol.

[0362] In some implementations, the number of auxiliary signals is determined based on a pre-defined method in the protocol, and the number of auxiliary signals is associated with one or more of the following: the number of repetitions of the second data; the length of the first data between two adjacent auxiliary signals; the data length of the first data; and the data length of the second data.

[0363] In some implementations, the data length of the R2D data between adjacent auxiliary signals, and / or between the first auxiliary signal and the preamble, and / or between the last auxiliary signal and the postamble, is configured by the second device or determined based on a method predefined by the protocol.

[0364] In some implementations, the first data on the PRDCH resource includes a first R2D data block and a second R2D data block. If the length of the second R2D data block is less than the length of the first R2D data block, then the length of the second R2D data block is supplemented so that the length of the second R2D data block is equal to the length of the first R2D data block; the second R2D data block is the last R2D data block on the PRDCH resource.

[0365] In some implementations, the PRDCH resource includes a plurality of auxiliary signals, the plurality of auxiliary signals having one or more lengths.

[0366] In some implementations, the length of the auxiliary signal is predetermined by the protocol and is associated with one or more of the following: the data size or length of the first data; the size or length of the second data; the data type of the first data; the data type of the second data; the number of repetitions of the second data; the number of auxiliary signals; and the length of the R2D data block between adjacent auxiliary signals, and / or between the first auxiliary signal and the preamble, and / or between the last auxiliary signal and the postamble.

[0367] In some implementations, the data type of the first data is any of the following: synchronization information, paging message, Msg2, Msg4, access timing trigger message, R2D upper layer data transmission message, and scheduling information.

[0368] In some implementations, the first data is carried on multiple PRDCH resources, and the data length of the first data on each of the multiple PRDCH resources may be the same or different.

[0369] In some implementations, the first data is carried on multiple PRDCH resources, and the number of multiple PRDCH resources is the same as or different from the number of repetitions of the second data.

[0370] In some implementations, if the data length of the first data on the last PRDCH resource among a plurality of PRDCH resources is less than the data length of the first data on other PRDCH resources, then the data length of the first data on the last PRDCH resource is filled in so that the data length of the first data on each PRDCH resource is the same.

[0371] In some implementations, the frequency domain resources of the multiple PRDCH resources are the same or different.

[0372] In some implementations, the data rates of the multiple PRDCH resources are the same or different; and / or, the modulation schemes and modulation parameters of the multiple PRDCH resources are the same or different; and / or, the auxiliary signals inserted on the multiple PRDCH resources are the same or different.

[0373] In some implementations, the time-domain resource information of the PRDCH resource includes one or more of the following: the start time of the time-domain resource, the end time of the time-domain resource, the duration of the time-domain resource, the offset of the time-domain resource, and the period of the time-domain resource.

[0374] In some implementations, the starting offset reference point of the time domain resource of the first data is the end or start time of the time domain resource of the first information, and the first information is used to schedule the time domain resource of the first data; or, the starting offset reference point is the end or start time of the time domain resource of the previous R2D transmission received by the first device; or, the starting offset reference point is the end or start time of the time domain resource of the previous D2R transmission sent by the first device.

[0375] In some implementations, the first data is carried on multiple PRDCH resources, which include N PRDCH resources, where N is an integer greater than 1; the start offset reference point of the time domain resource of the first PRDCH resource is the end or start time of the time domain resource of the first information, and the start offset reference point of the time domain resource of the (n+1)th PRDCH resource is the end or start time of the time domain resource of the nth PRDCH resource, wherein the first information is used to schedule the time domain resource of the first data, and N>n>1.

[0376] In some implementations, the first data is carried on multiple PRDCH resources, including a first PRDCH resource and a second PRDCH resource. First information on the first PRDCH resource is used to indicate the starting offset of the temporal resource of the second PRDCH resource. The first information is used to schedule the temporal resource of the first data. The first PRDCH resource is located before the second PRDCH resource in the temporal domain.

[0377] In some implementations, the first information is carried in higher-layer signaling or physical-layer signaling.

[0378] In some implementations, the frequency domain resource information of the PRDCH resource includes one or more of the following: small frequency shift parameter, frequency shift amount, frequency band position, bandwidth size, guard band size, center frequency point, frequency domain resource start position, frequency domain resource end position, frequency domain resource channel number, and frequency domain reference point.

[0379] In some implementations, the frequency domain resource location of the first data is determined based on the frequency domain resource information.

[0380] In some implementations, the communication device 2100 further includes a second communication module 2120, used to send second information to the first device, the second information being used to indicate the number of repetitions of the second data.

[0381] In some implementations, the number of repetitions of the second data is determined based on one or more of the following information reported by the first device: R2D signal power related information; path loss measurement related information; D2R signal power related information.

[0382] In some implementations, the number of repetitions of the second data is determined based on one or more of the following: the time interval during which the second device has not received a D2R message from the first device; the current number of repetitions of the second data; and the number of times the first data has been transmitted.

[0383] In some implementations, the first device is an environmental Internet of Things (A-IoT) terminal device.

[0384] In some implementations, the second device is a network device; or an intermediate node, through which the first device communicates with the network device.

[0385] Figure 22 This is a schematic structural diagram of a communication device applicable to embodiments of this application. Figure 22 The dashed lines indicate that the unit or module is optional. The device 2200 can be used to implement the methods described in the above method embodiments. The device 2200 can be a chip, a terminal device, or a network device.

[0386] Apparatus 2200 may include one or more processors 2210. The processor 2210 may support apparatus 2200 in implementing the methods described in the preceding method embodiments. The processor 2210 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, 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, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0387] The apparatus 2200 may further include one or more memories 2220. The memories 2220 store a program that can be executed by the processor 2210, causing the processor 2210 to perform the methods described in the preceding method embodiments. The memories 2220 may be independent of the processor 2210 or integrated within the processor 2210.

[0388] The device 2200 may also include a transceiver 2230. The processor 2210 can communicate with other devices or chips via the transceiver 2230. For example, the processor 2210 can send and receive data with other devices or chips via the transceiver 2230.

[0389] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to the communication device provided in this application, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.

[0390] This application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in this application embodiment, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.

[0391] This application also provides a computer program. This computer program can be applied to the communication device provided in this application, and causes the computer to execute the methods performed by the communication device in various embodiments of this application.

[0392] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0393] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0394] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0395] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0396] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0397] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0398] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0399] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

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

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

[0402] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0403] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0404] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: The first device receives first data sent by the second device, wherein the first data is data that is repeated by R2D on the second data; The first data is any one of the following: The R2D bits of the second data are repeated, the R2D chips of the second data are repeated, and the R2D blocks of the second data are repeated.

2. The method according to claim 1, characterized in that, The R2D bit repetition is any of the following: R2D information bit repetition, R2D encoding bit repetition.

3. The method according to claim 1, characterized in that, The R2D block repeats in any of the following ways: R2D information bit block repetition, R2D encoded bit block repetition, R2D modulation symbol block repetition.

4. The method according to any one of claims 1-3, characterized in that, The first data is carried on one or more PRDCH resources.

5. The method according to claim 4, characterized in that, One or more auxiliary signals are inserted between the first data.

6. The method according to claim 4 or 5, characterized in that, The number of auxiliary signals inserted on the PRDCH resource is configured by the second device, or determined based on a method predefined by the protocol.

7. The method according to claim 6, characterized in that, The number of auxiliary signals is determined based on a pre-defined method in the protocol, and the number of auxiliary signals is associated with one or more of the following: The number of repetitions in the second data; The length of the first data between two adjacent auxiliary signals; The data length of the first data; The length of the second data.

8. The method according to any one of claims 5-7, characterized in that, The data length of the R2D data between adjacent auxiliary signals, and / or between the first auxiliary signal and the preamble, and / or between the last auxiliary signal and the postamble, is configured by the second device, or determined in a manner predefined by the protocol.

9. The method according to any one of claims 5-8, characterized in that, The first data on the PRDCH resource includes a first R2D data block and a second R2D data block. If the length of the second R2D data block is less than the length of the first R2D data block, then the length of the second R2D data block is supplemented so that the length of the second R2D data block is equal to the length of the first R2D data block. The second R2D data block is the last R2D data block on the PRDCH resource.

10. The method according to any one of claims 5-9, characterized in that, The PRDCH resource includes a plurality of auxiliary signals, and the plurality of auxiliary signals have one or more lengths.

11. The method according to claim 10, characterized in that, The length of the auxiliary signal is predefined by the protocol, and the length of the auxiliary signal is associated with one or more of the following: The data size or length of the first data; The size or length of the second data; The data type of the first data; The data type of the second data; The number of repetitions in the second data; The number of auxiliary signals; The length of the R2D data block between adjacent auxiliary signals, and / or between the first auxiliary signal and the preamble, and / or between the last auxiliary signal and the postamble.

12. The method according to claim 11, characterized in that, The data type of the first data is any of the following: synchronization information, paging message, Msg2, Msg4, access timing trigger message, R2D upper layer data transmission message, and scheduling information.

13. The method according to claim 4, characterized in that, The first data is carried on multiple PRDCH resources, and the data length of the first data on each of the multiple PRDCH resources may be the same or different.

14. The method according to any one of claims 4-13, characterized in that, The first data is carried on multiple PRDCH resources, and the number of multiple PRDCH resources is the same as or different from the number of repetitions of the second data.

15. The method according to claim 13 or 14, characterized in that, If the data length of the first data on the last PRDCH resource among the multiple PRDCH resources is less than the data length of the first data on other PRDCH resources, then the data length of the first data on the last PRDCH resource is filled in so that the data length of the first data on each PRDCH resource is the same.

16. The method according to any one of claims 13-15, characterized in that, The frequency domain resources of the multiple PRDCH resources may be the same or different.

17. The method according to any one of claims 13-16, characterized in that, The data rates of the multiple PRDCH resources are the same or different; and / or, The modulation schemes and modulation parameters of the multiple PRDCH resources are the same or different; and / or, The auxiliary signals inserted on multiple PRDCH resources may be the same or different.

18. The method according to any one of claims 4-17, characterized in that, The time-domain resource information of the PRDCH resource includes one or more of the following: The start time of the time-domain resource, the end time of the time-domain resource, the duration of the time-domain resource, the offset of the time-domain resource, and the period of the time-domain resource.

19. The method according to any one of claims 4-18, characterized in that, The starting offset reference point of the temporal domain resource of the first data is the end or start time of the temporal domain resource of the first information, and the first information is used to schedule the temporal domain resource of the first data; or, The starting offset reference point is the end or start time of the time-domain resource of the previous R2D transmission received by the first device; or, The starting offset reference point is the end or start time of the time domain resource of the previous D2R transmission sent by the first device.

20. The method according to any one of claims 4-18, characterized in that, The first data is carried on multiple PRDCH resources, and the multiple PRDCH resources include N PRDCH resources, where N is an integer greater than 1; The starting offset reference point of the time domain resource of the first PRDCH resource is the end or start time of the time domain resource of the first information, and the starting offset reference point of the time domain resource of the (n+1)th PRDCH resource is the end or start time of the time domain resource of the nth PRDCH resource. The first information is used to schedule the time domain resource of the first data, where N>n>1.

21. The method according to any one of claims 4-18, characterized in that, The first data is carried on multiple PRDCH resources, including a first PRDCH resource and a second PRDCH resource. The first information on the first PRDCH resource is used to indicate the starting offset of the temporal resource of the second PRDCH resource. The first information is used to schedule the temporal resource of the first data. The first PRDCH resource is located before the second PRDCH resource in the temporal domain.

22. The method according to claims 19-21, characterized in that, The first information is carried in higher-layer signaling or physical-layer signaling.

23. The method according to any one of claims 4-17, characterized in that, The frequency domain resource information of the PRDCH resource includes one or more of the following: Small frequency shift parameters, frequency shift amount, frequency band position, bandwidth size, guard band size, center frequency, frequency domain resource start position, frequency domain resource end position, frequency domain resource channel number, and frequency domain reference point.

24. The method according to claim 23, characterized in that, The frequency domain resource location of the first data is determined based on the frequency domain resource information.

25. The method according to any one of claims 1-24, characterized in that, The method further includes: The first device receives second information sent by the second device, the second information being used to indicate the number of repetitions of the second data.

26. The method according to claim 25, characterized in that, The number of duplicates of the second data is determined based on one or more of the following information reported by the first device: Information related to the signal power of R2D; Information related to path loss measurement; Information related to the signal power of D2R.

27. The method according to any one of claims 1-24, characterized in that, The number of repetitions in the second data is determined based on one or more of the following information: The time interval during which the second device did not receive a D2R message from the first device; The current number of repetitions of the second data; The number of times the first data was transmitted.

28. The method according to any one of claims 1-27, characterized in that, The first device is an environmental Internet of Things (A-IoT) terminal device.

29. The method according to any one of claims 1-28, characterized in that, The second device is: Network equipment; or Intermediate node, through which the first device communicates with network devices.

30. A communication method, characterized in that, include: The second device sends first data to the first device, the first data being data obtained by performing R2D repetition on the second data; The first data is any one of the following: The R2D bits of the second data are repeated, the R2D chips of the second data are repeated, and the R2D blocks of the second data are repeated.

31. The method according to claim 30, characterized in that, The R2D bit repetition is any of the following: R2D information bit repetition, R2D encoding bit repetition.

32. The method according to claim 30, characterized in that, The R2D block repeats in any of the following ways: R2D information bit block repetition, R2D encoded bit block repetition, R2D modulation symbol block repetition.

33. The method according to any one of claims 30-32, characterized in that, The first data is carried on one or more PRDCH resources.

34. The method according to claim 33, characterized in that, One or more auxiliary signals are inserted between the first data.

35. The method according to claim 33 or 34, characterized in that, The number of auxiliary signals inserted on the PRDCH resource is configured by the second device, or determined based on a method predefined by the protocol.

36. The method according to claim 35, characterized in that, The number of auxiliary signals is determined based on a pre-defined method in the protocol, and the number of auxiliary signals is associated with one or more of the following: The number of repetitions in the second data; The length of the first data between two adjacent auxiliary signals; The data length of the first data; The length of the second data.

37. The method according to any one of claims 34-36, characterized in that, The data length of the R2D data between adjacent auxiliary signals, and / or between the first auxiliary signal and the preamble, and / or between the last auxiliary signal and the postamble, is configured by the second device, or determined in a manner predefined by the protocol.

38. The method according to any one of claims 34-37, characterized in that, The first data on the PRDCH resource includes a first R2D data block and a second R2D data block. If the length of the second R2D data block is less than the length of the first R2D data block, then the length of the second R2D data block is supplemented so that the length of the second R2D data block is equal to the length of the first R2D data block. The second R2D data block is the last R2D data block on the PRDCH resource.

39. The method according to any one of claims 34-38, characterized in that, The PRDCH resource includes a plurality of auxiliary signals, and the plurality of auxiliary signals have one or more lengths.

40. The method according to claim 39, characterized in that, The length of the auxiliary signal is predefined by the protocol, and the length of the auxiliary signal is associated with one or more of the following: The data size or length of the first data; The size or length of the second data; The data type of the first data; The data type of the second data; The number of repetitions in the second data; The number of auxiliary signals; The length of the R2D data block between adjacent auxiliary signals, and / or between the first auxiliary signal and the preamble, and / or between the last auxiliary signal and the postamble.

41. The method according to claim 40, characterized in that, The data type of the first data is any of the following: synchronization information, paging message, Msg2, Msg4, access timing trigger message, R2D upper layer data transmission message, and scheduling information.

42. The method according to claim 33, characterized in that, The first data is carried on multiple PRDCH resources, and the data length of the first data on each of the multiple PRDCH resources may be the same or different.

43. The method according to any one of claims 33-42, characterized in that, The first data is carried on multiple PRDCH resources, and the number of multiple PRDCH resources is the same as or different from the number of repetitions of the second data.

44. The method according to claim 42 or 43, characterized in that, If the data length of the first data on the last PRDCH resource among the multiple PRDCH resources is less than the data length of the first data on other PRDCH resources, then the data length of the first data on the last PRDCH resource is filled in so that the data length of the first data on each PRDCH resource is the same.

45. The method according to any one of claims 42-44, characterized in that, The frequency domain resources of the multiple PRDCH resources may be the same or different.

46. ​​The method according to any one of claims 42-45, characterized in that, The data rates of the multiple PRDCH resources are the same or different; and / or, The modulation schemes and modulation parameters of the multiple PRDCH resources are the same or different; and / or, The auxiliary signals inserted on multiple PRDCH resources may be the same or different.

47. The method according to any one of claims 33-46, characterized in that, The time-domain resource information of the PRDCH resource includes one or more of the following: The start time of the time-domain resource, the end time of the time-domain resource, the duration of the time-domain resource, the offset of the time-domain resource, and the period of the time-domain resource.

48. The method according to any one of claims 33-47, characterized in that, The starting offset reference point of the temporal domain resource of the first data is the end or start time of the temporal domain resource of the first information, and the first information is used to schedule the temporal domain resource of the first data; or, The starting offset reference point is the end or start time of the time-domain resource of the previous R2D transmission received by the first device; or, The starting offset reference point is the end or start time of the time domain resource of the previous D2R transmission sent by the first device.

49. The method according to any one of claims 33-47, characterized in that, The first data is carried on multiple PRDCH resources, and the multiple PRDCH resources include N PRDCH resources, where N is an integer greater than 1; The starting offset reference point of the time domain resource of the first PRDCH resource is the end or start time of the time domain resource of the first information, and the starting offset reference point of the time domain resource of the (n+1)th PRDCH resource is the end or start time of the time domain resource of the nth PRDCH resource. The first information is used to schedule the time domain resource of the first data, where N>n>1.

50. The method according to any one of claims 33-47, characterized in that, The first data is carried on multiple PRDCH resources, including a first PRDCH resource and a second PRDCH resource. The first information on the first PRDCH resource is used to indicate the starting offset of the temporal resource of the second PRDCH resource. The first information is used to schedule the temporal resource of the first data. The first PRDCH resource is located before the second PRDCH resource in the temporal domain.

51. The method according to claims 48-50, characterized in that, The first information is carried in higher-layer signaling or physical-layer signaling.

52. The method according to any one of claims 33-46, characterized in that, The frequency domain resource information of the PRDCH resource includes one or more of the following: Small frequency shift parameters, frequency shift amount, frequency band position, bandwidth size, guard band size, center frequency, frequency domain resource start position, frequency domain resource end position, frequency domain resource channel number, and frequency domain reference point.

53. The method according to claim 52, characterized in that, The frequency domain resource location of the first data is determined based on the frequency domain resource information.

54. The method according to any one of claims 30-53, characterized in that, The method further includes: The second device sends a second message to the first device, the second message indicating the number of repetitions of the second data.

55. The method according to claim 54, characterized in that, The number of duplicates of the second data is determined based on one or more of the following information reported by the first device: Information related to the signal power of R2D; Information related to path loss measurement; Information related to the signal power of D2R.

56. The method according to any one of claims 30-53, characterized in that, The number of repetitions in the second data is determined based on one or more of the following information: The time interval during which the second device did not receive a D2R message from the first device; The current number of repetitions of the second data; The number of times the first data was transmitted.

57. The method according to any one of claims 30-56, characterized in that, The first device is an environmental Internet of Things (A-IoT) terminal device.

58. The method according to any one of claims 30-57, characterized in that, The second device is: Network equipment; or Intermediate node, through which the first device communicates with network devices.

59. A communication device, characterized in that, The communication device is a first device, and the communication device includes: The first communication module is used to receive first data sent by the second device, wherein the first data is data that is repeated by R2D on the second data; The first data is any one of the following: The R2D bits of the second data are repeated, the R2D chips of the second data are repeated, and the R2D blocks of the second data are repeated.

60. The communication device according to claim 59, characterized in that, The R2D bit repetition is any of the following: R2D information bit repetition, R2D encoding bit repetition.

61. The communication device according to claim 59, characterized in that, The R2D block repeats in any of the following ways: R2D information bit block repetition, R2D encoded bit block repetition, R2D modulation symbol block repetition.

62. The communication device according to any one of claims 59-61, characterized in that, The first data is carried on one or more PRDCH resources.

63. The communication device according to claim 62, characterized in that, One or more auxiliary signals are inserted between the first data.

64. The communication device according to claim 62 or 63, characterized in that, The number of auxiliary signals inserted on the PRDCH resource is configured by the second device, or determined based on a method predefined by the protocol.

65. The communication device according to claim 64, characterized in that, The number of auxiliary signals is determined based on a pre-defined method in the protocol, and the number of auxiliary signals is associated with one or more of the following: The number of repetitions in the second data; The length of the first data between two adjacent auxiliary signals; The data length of the first data; The length of the second data.

66. The communication device according to any one of claims 63-65, characterized in that, The data length of the R2D data between adjacent auxiliary signals, and / or between the first auxiliary signal and the preamble, and / or between the last auxiliary signal and the postamble, is configured by the second device, or determined in a manner predefined by the protocol.

67. The communication device according to any one of claims 63-66, characterized in that, The first data on the PRDCH resource includes a first R2D data block and a second R2D data block. If the length of the second R2D data block is less than the length of the first R2D data block, then the length of the second R2D data block is supplemented so that the length of the second R2D data block is equal to the length of the first R2D data block. The second R2D data block is the last R2D data block on the PRDCH resource.

68. The communication device according to any one of claims 63-67, characterized in that, The PRDCH resource includes a plurality of auxiliary signals, and the plurality of auxiliary signals have one or more lengths.

69. The communication device according to claim 68, characterized in that, The length of the auxiliary signal is predefined by the protocol, and the length of the auxiliary signal is associated with one or more of the following: The data size or length of the first data; The size or length of the second data; The data type of the first data; The data type of the second data; The number of repetitions in the second data; The number of auxiliary signals; The length of the R2D data block between adjacent auxiliary signals, and / or between the first auxiliary signal and the preamble, and / or between the last auxiliary signal and the postamble.

70. The communication device according to claim 69, characterized in that, The data type of the first data is any of the following: synchronization information, paging message, Msg2, Msg4, access timing trigger message, R2D upper layer data transmission message, and scheduling information.

71. The communication device according to claim 62, characterized in that, The first data is carried on multiple PRDCH resources, and the data length of the first data on each of the multiple PRDCH resources may be the same or different.

72. The communication device according to any one of claims 62-71, characterized in that, The first data is carried on multiple PRDCH resources, and the number of multiple PRDCH resources is the same as or different from the number of repetitions of the second data.

73. The communication device according to claim 71 or 72, characterized in that, If the data length of the first data on the last PRDCH resource among the multiple PRDCH resources is less than the data length of the first data on other PRDCH resources, then the data length of the first data on the last PRDCH resource is filled in so that the data length of the first data on each PRDCH resource is the same.

74. The communication device according to any one of claims 71-73, characterized in that, The frequency domain resources of the multiple PRDCH resources may be the same or different.

75. The communication device according to any one of claims 71-74, characterized in that, The data rates of the multiple PRDCH resources are the same or different; and / or, The modulation schemes and modulation parameters of the multiple PRDCH resources are the same or different; and / or, The auxiliary signals inserted on multiple PRDCH resources may be the same or different.

76. The communication device according to any one of claims 62-75, characterized in that, The time-domain resource information of the PRDCH resource includes one or more of the following: The start time of the time-domain resource, the end time of the time-domain resource, the duration of the time-domain resource, the offset of the time-domain resource, and the period of the time-domain resource.

77. The communication device according to any one of claims 62-76, characterized in that, The starting offset reference point of the temporal domain resource of the first data is the end or start time of the temporal domain resource of the first information, and the first information is used to schedule the temporal domain resource of the first data; or, The starting offset reference point is the end or start time of the time-domain resource of the previous R2D transmission received by the first device; or, The starting offset reference point is the end or start time of the time domain resource of the previous D2R transmission sent by the first device.

78. The communication device according to any one of claims 62-76, characterized in that, The first data is carried on multiple PRDCH resources, and the multiple PRDCH resources include N PRDCH resources, where N is an integer greater than 1; The starting offset reference point of the time domain resource of the first PRDCH resource is the end or start time of the time domain resource of the first information, and the starting offset reference point of the time domain resource of the (n+1)th PRDCH resource is the end or start time of the time domain resource of the nth PRDCH resource. The first information is used to schedule the time domain resource of the first data, where N>n>1.

79. The communication device according to any one of claims 62-76, characterized in that, The first data is carried on multiple PRDCH resources, including a first PRDCH resource and a second PRDCH resource. The first information on the first PRDCH resource is used to indicate the starting offset of the temporal resource of the second PRDCH resource. The first information is used to schedule the temporal resource of the first data. The first PRDCH resource is located before the second PRDCH resource in the temporal domain.

80. The communication device according to claims 77-79, characterized in that, The first information is carried in higher-layer signaling or physical-layer signaling.

81. The communication device according to any one of claims 62-75, characterized in that, The frequency domain resource information of the PRDCH resource includes one or more of the following: Small frequency shift parameters, frequency shift amount, frequency band position, bandwidth size, guard band size, center frequency, frequency domain resource start position, frequency domain resource end position, frequency domain resource channel number, and frequency domain reference point.

82. The communication device according to claim 81, characterized in that, The frequency domain resource location of the first data is determined based on the frequency domain resource information.

83. The communication device according to any one of claims 59-82, characterized in that, The communication device also includes: The second communication module is used to receive second information sent by the second device, the second information being used to indicate the number of repetitions of the second data.

84. The communication device according to claim 83, characterized in that, The number of duplicates of the second data is determined based on one or more of the following information reported by the first device: Information related to the signal power of R2D; Information related to path loss measurement; Information related to the signal power of D2R.

85. The communication device according to any one of claims 59-82, characterized in that, The number of repetitions in the second data is determined based on one or more of the following information: The time interval during which the second device did not receive a D2R message from the first device; The current number of repetitions of the second data; The number of times the first data was transmitted.

86. The communication device according to any one of claims 59-85, characterized in that, The first device is an environmental Internet of Things (A-IoT) terminal device.

87. The communication device according to any one of claims 59-86, characterized in that, The second device is: Network equipment; or Intermediate node, through which the first device communicates with network devices.

88. A communication device, characterized in that, The communication device is a second device, and the communication device includes: The first communication module is used to send first data to the first device, wherein the first data is data that is repeated by R2D on the second data; The first data is any one of the following: The R2D bits of the second data are repeated, the R2D chips of the second data are repeated, and the R2D blocks of the second data are repeated.

89. The communication device according to claim 88, characterized in that, The R2D bit repetition is any of the following: R2D information bit repetition, R2D encoding bit repetition.

90. The communication device according to claim 88, characterized in that, The R2D block repeats in any of the following ways: R2D information bit block repetition, R2D encoded bit block repetition, R2D modulation symbol block repetition.

91. The communication device according to any one of claims 88-90, characterized in that, The first data is carried on one or more PRDCH resources.

92. The communication device according to claim 91, characterized in that, One or more auxiliary signals are inserted between the first data.

93. The communication device according to claim 91 or 92, characterized in that, The number of auxiliary signals inserted on the PRDCH resource is configured by the second device, or determined based on a method predefined by the protocol.

94. The communication device according to claim 93, characterized in that, The number of auxiliary signals is determined based on a pre-defined method in the protocol, and the number of auxiliary signals is associated with one or more of the following: The number of repetitions in the second data; The length of the first data between two adjacent auxiliary signals; The data length of the first data; The length of the second data.

95. The communication device according to any one of claims 92-94, characterized in that, The data length of the R2D data between adjacent auxiliary signals, and / or between the first auxiliary signal and the preamble, and / or between the last auxiliary signal and the postamble, is configured by the second device, or determined in a manner predefined by the protocol.

96. The communication device according to any one of claims 92-95, characterized in that, The first data on the PRDCH resource includes a first R2D data block and a second R2D data block. If the length of the second R2D data block is less than the length of the first R2D data block, then the length of the second R2D data block is supplemented so that the length of the second R2D data block is equal to the length of the first R2D data block. The second R2D data block is the last R2D data block on the PRDCH resource.

97. The communication device according to any one of claims 92-96, characterized in that, The PRDCH resource includes a plurality of auxiliary signals, and the plurality of auxiliary signals have one or more lengths.

98. The communication device according to claim 97, characterized in that, The length of the auxiliary signal is predefined by the protocol, and the length of the auxiliary signal is associated with one or more of the following: The data size or length of the first data; The size or length of the second data; The data type of the first data; The data type of the second data; The number of repetitions in the second data; The number of auxiliary signals; The length of the R2D data block between adjacent auxiliary signals, and / or between the first auxiliary signal and the preamble, and / or between the last auxiliary signal and the postamble.

99. The communication device according to claim 98, characterized in that, The data type of the first data is any of the following: synchronization information, paging message, Msg2, Msg4, access timing trigger message, R2D upper layer data transmission message, and scheduling information.

100. The communication device according to claim 91, characterized in that, The first data is carried on multiple PRDCH resources, and the data length of the first data on each of the multiple PRDCH resources may be the same or different.

101. The communication device according to any one of claims 91-100, characterized in that, The first data is carried on multiple PRDCH resources, and the number of multiple PRDCH resources is the same as or different from the number of repetitions of the second data.

102. The communication device according to claim 100 or 101, characterized in that, If the data length of the first data on the last PRDCH resource among the multiple PRDCH resources is less than the data length of the first data on other PRDCH resources, then the data length of the first data on the last PRDCH resource is filled in so that the data length of the first data on each PRDCH resource is the same.

103. The communication device according to any one of claims 100-102, characterized in that, The frequency domain resources of the multiple PRDCH resources may be the same or different.

104. The communication device according to any one of claims 100-103, characterized in that, The data rates of the multiple PRDCH resources are the same or different; and / or, The modulation schemes and modulation parameters of the multiple PRDCH resources are the same or different; and / or, The auxiliary signals inserted on multiple PRDCH resources may be the same or different.

105. The communication device according to any one of claims 91-104, characterized in that, The time-domain resource information of the PRDCH resource includes one or more of the following: The start time of the time-domain resource, the end time of the time-domain resource, the duration of the time-domain resource, the offset of the time-domain resource, and the period of the time-domain resource.

106. The communication device according to any one of claims 91-105, characterized in that, The starting offset reference point of the temporal domain resource of the first data is the end or start time of the temporal domain resource of the first information, and the first information is used to schedule the temporal domain resource of the first data; or, The starting offset reference point is the end or start time of the time-domain resource of the previous R2D transmission received by the first device; or, The starting offset reference point is the end or start time of the time domain resource of the previous D2R transmission sent by the first device.

107. The communication device according to any one of claims 91-105, characterized in that, The first data is carried on multiple PRDCH resources, and the multiple PRDCH resources include N PRDCH resources, where N is an integer greater than 1; The starting offset reference point of the time domain resource of the first PRDCH resource is the end or start time of the time domain resource of the first information, and the starting offset reference point of the time domain resource of the (n+1)th PRDCH resource is the end or start time of the time domain resource of the nth PRDCH resource. The first information is used to schedule the time domain resource of the first data, where N>n>1.

108. The communication device according to any one of claims 91-105, characterized in that, The first data is carried on multiple PRDCH resources, including a first PRDCH resource and a second PRDCH resource. The first information on the first PRDCH resource is used to indicate the starting offset of the temporal resource of the second PRDCH resource. The first information is used to schedule the temporal resource of the first data. The first PRDCH resource is located before the second PRDCH resource in the temporal domain.

109. The communication device according to claims 106-108, characterized in that, The first information is carried in higher-layer signaling or physical-layer signaling.

110. The communication device according to any one of claims 91-104, characterized in that, The frequency domain resource information of the PRDCH resource includes one or more of the following: Small frequency shift parameters, frequency shift amount, frequency band position, bandwidth size, guard band size, center frequency, frequency domain resource start position, frequency domain resource end position, frequency domain resource channel number, and frequency domain reference point.

111. The communication device according to claim 110, characterized in that, The frequency domain resource location of the first data is determined based on the frequency domain resource information.

112. The communication device according to any one of claims 88-111, characterized in that, The communication device also includes: The second communication module is used to send second information to the first device, the second information being used to indicate the number of repetitions of the second data.

113. The communication device according to claim 112, characterized in that, The number of duplicates of the second data is determined based on one or more of the following information reported by the first device: Information related to the signal power of R2D; Information related to path loss measurement; Information related to the signal power of D2R.

114. The communication device according to any one of claims 88-111, characterized in that, The number of repetitions in the second data is determined based on one or more of the following information: The time interval during which the second device did not receive a D2R message from the first device; The current number of repetitions of the second data; The number of times the first data was transmitted.

115. The communication device according to any one of claims 88-114, characterized in that, The first device is an environmental Internet of Things (A-IoT) terminal device.

116. The communication device according to any one of claims 88-115, characterized in that, The second device is: Network equipment; or Intermediate node, through which the first device communicates with network devices.

117. A communication device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the communication device performs the method as described in any one of claims 1 to 58.

118. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the apparatus to perform the method as described in any one of claims 1 to 58.

119. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 58.

120. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1 to 58.

121. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1 to 58.

122. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1 to 58.

Images