Wireless communication method and communication device

Abstract

The invention provides a wireless communication method and a communication device, and the method comprises the steps that a first device sends a first request to a second device on a first transmission resource, and the first request is used for requesting a broadcast message; through the method provided by the invention, the power consumption and time delay of acquiring the broadcast message by the first equipment can be reduced.

Description

Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a wireless communication method and communication device. Background Technology

[0002] In some scenarios, a second device sends periodic broadcast messages to a first device. The first device can synchronize and acquire time-frequency resources based on these broadcast messages to maintain normal information transmission and reception. If the first device misses receiving a periodic broadcast message, it needs to continuously monitor it, which leads to higher power consumption and increased latency. Summary of the Invention

[0003] This application provides a wireless communication method and a communication device, and the various aspects involved in this application will be described below.

[0004] In a first aspect, a wireless communication method is provided, comprising: a first device sending a first request to a second device on a first transmission resource, the first request being used to request a broadcast message.

[0005] In a second aspect, a wireless communication method is provided, comprising: a second device receiving a first request sent by a first device on a first transmission resource, the first request being used to request a broadcast message.

[0006] Thirdly, a communication device is provided, comprising a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, and the processor is used to invoke and run the computer programs in the memory, causing the communication device to perform some or all of the steps in the method of the first aspect.

[0007] Fourthly, a communication device is provided, comprising a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, and the processor is used to invoke and run the computer programs in the memory, causing the communication device to perform some or all of the steps in the method of the second aspect.

[0008] Fifthly, embodiments of this application provide a communication system that includes the first device and / or the second device described above. In another possible design, the system may further include other devices that interact with the first device or the second device as provided in the embodiments of this application.

[0009] In a sixth aspect, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a communication device (e.g., a terminal device or a network device) to perform some or all of the steps in the methods described above.

[0010] In a seventh aspect, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a communication device (e.g., a terminal device or a network device) to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.

[0011] Eighthly, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0012] In this embodiment of the application, the first device sends a first request to the second device on the first transmission resource to request the second device to send a broadcast message, which can reduce the power consumption and latency of the first device in obtaining the broadcast message. Attached Figure Description

[0013] Figure 1 This is the wireless communication system 100 used in the embodiments of this application.

[0014] Figure 2 An example diagram illustrating the working principle of an ambient internet of things (A-IoT) device is shown.

[0015] Figures 3 to 7 This is a schematic diagram illustrating the application scenario of the embodiments of this application.

[0016] Figure 8 A schematic diagram of the method 800 provided in this application is shown.

[0017] Figure 9 An example diagram is shown illustrating how a first device, according to an embodiment of this application, determines the time-domain location of a first transmission resource based on the time-domain location of a first signal.

[0018] Figure 10 An example diagram is shown illustrating how a first device, according to first information, determines the frequency domain location of a first transmission resource based on first information, as provided in an embodiment of this application.

[0019] Figure 11 This illustration shows an example diagram of a first device, according to an embodiment of this application, determining the temporal location of a first transmission resource based on reader-to-device (R2D) control information and / or R2D data sent by a second device to another first device.

[0020] Figure 12 This is a schematic diagram of a communication device according to an embodiment of this application.

[0021] Figure 13 This is a schematic diagram of a communication device according to an embodiment of this application.

[0022] Figure 14 This is a schematic structural diagram of a communication device according to an embodiment of this application. Detailed Implementation

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

[0024] Communication system architecture

[0025] Figure 1 This is the wireless communication system 100 used in the embodiments of this application. 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 may provide communication coverage for a specific geographical area and may communicate with the terminal device 120 located within that coverage area.

[0026] 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.

[0027] 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.

[0028] 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.

[0029] 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, self-driving, remote medical surgery, smart grids, transportation safety, smart cities, and smart homes, etc. Optionally, the UE can act as a base station. For example, the UE can act as a scheduling entity, providing sidelink signals between UEs in V2X or D2D, etc. For example, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices communicate without relaying communication signals through a base station.

[0030] 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.

[0031] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0032] 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.

[0033] 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.

[0034] 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).

[0035] Ambient Internet of Things (A-IoT)

[0036] A-IoT communication employs energy harvesting and backscatter communication technologies. An A-IoT device refers to an Internet of Things (IoT) device powered by various environmental energy sources, such as radio frequency energy, light energy, solar energy, thermal energy, and mechanical energy. Such IoT devices may have no energy storage capacity or very limited energy storage capacity (e.g., using capacitors with a capacity of tens of microfarads (µF)). Compared to existing IoT devices, A-IoT devices offer numerous advantages, including no need for conventional batteries, no maintenance, small size, low complexity and low cost, and long lifespan. In this scenario, the terminal device 120 mentioned earlier can be referred to as a "zero-power device" or an "A-IoT device."

[0037] Figure 2 An example diagram illustrating the working principle of A-IoT devices is shown. Figure 2 As shown, the environmental Internet of Things (IoT) may include network device 210 and A-IoT device 220. Network device 210 may, for example, be... Figure 1 Network device 110. A-IoT device 220, for example, can Figure 1 The terminal device 120 is used in the network device 210 to send a wireless power signal to the A-IoT device 220. The A-IoT device 220 is used to send a backscatter signal to the network device 210, or the A-IoT device 220 is used to generate a carrier signal, modulate the carrier signal and send it to the network device 210.

[0038] In some embodiments, the A-IoT device 220 may include an energy harvesting module 221 and a backscatter communication module 222. In some cases, the A-IoT device 220 may also include a low-power computing module 223. The low-power computing module 223 can be used to provide computing functions for the A-IoT device 220, such as data processing. In other cases, the A-IoT device 220 may also include a sensor module 224 for collecting external information (e.g., ambient temperature, ambient humidity, etc.). In still other cases, the A-IoT device 220 may also include a storage module for storing information (e.g., external information collected by the aforementioned sensors, or such as item identification).

[0039] The energy harvesting module 221 described above is used to harvest energy. In some implementations, energy can be harvested via a power supply signal sent by other devices or via the external environment. The power supply signal can be a "radio frequency (RF) signal" sent by the network device 210; therefore, the energy harvesting module described above can be a "radio frequency (RF) power harvesting module."

[0040] Low-power IoT based on cellular networks

[0041] The cellular Internet of Things (IoT) is booming. For example, the 3rd Generation Partnership Project (3GPP) has standardized IoT technologies such as Narrow Band Internet of Things (NB-IoT), Machine Type Communications (MTC), and Reduced Capability (RedCaP). However, many IoT communication needs in various scenarios cannot be met by existing technologies. These include harsh communication environments (high temperature, low temperature, high humidity, high pressure, high radiation, or high-speed movement), extremely small terminal form factors, and extremely low costs. Therefore, to cover these unmet IoT communication needs, ultra-low cost, extremely small size, and battery-free / maintenance-free IoT devices also need to be developed within cellular networks. Environmental IoT can precisely meet this requirement.

[0042] Based on the discussion of A-IoT application scenarios in the 3GPP system architecture (SA)1, A-IoT can be used in at least the following four scenarios: (1) Object recognition, such as logistics, production line product management, and supply chain management. (2) Environmental monitoring, such as monitoring of temperature, humidity, and harmful gases in the working environment and natural environment. (3) Positioning, such as indoor positioning, smart object finding, and production line item positioning. (4) Smart control, such as smart control of various electrical appliances in smart homes (turning on and off air conditioners, adjusting temperature), and smart control of various facilities in agricultural greenhouses (automatic irrigation, fertilization).

[0043] For example, A-IoT devices can be used in inventory management scenarios.

[0044] In some implementations, such as Figure 3 As shown, the reader is a network device 210 with A-IoT capabilities. The A-IoT device 220 is directly connected to the network device 210 and can directly receive and send carrier signals from the network device 210, and send or backscatter corresponding data or signals to the network device 210.

[0045] In some implementations, such as Figure 4 As shown, the reader is an intermediate node with A-IoT capabilities, meaning that communication between the A-IoT device 220 and the network device 210 can be achieved through the intermediate node 230. The intermediate node can be a terminal device, a base station device, an integrated access and backhaul (IAB) node, or a repeater. Communication between the network device 210 and the intermediate node 230 is transmitted via the Uu port.

[0046] In some implementations, the reader is an auxiliary node with A-IoT capabilities. For example... Figure 5 As shown, during the downlink process, A-IoT device 220 receives signals from auxiliary node 230 and transmits the signals to network device 210. For example... Figure 6 As shown, during the uplink process, A-IoT device 220 receives signals from network device 210 and sends the signals to auxiliary node 230. The auxiliary node can be a terminal device, base station device, IAB node, or repeater. Communication between network device 210 and auxiliary node 230 is transmitted via Uu port.

[0047] In some implementations, such as Figure 7As shown, the reader is a terminal device with A-IoT capabilities, or the reader is a normal terminal device, and the A-IoT device 220 is directly connected to the terminal device 210.

[0048] The following is a brief introduction to the terminology used in this application.

[0049] I. Types of A-IoT Devices: In some implementations, A-IoT devices can operate without batteries, although they can also be equipped with batteries. Based on their power source and usage, A-IoT devices can be categorized into passive A-IoT devices, semi-passive A-IoT devices, and active A-IoT devices.

[0050] Passive A-IoT devices do not require an internal battery. When the A-IoT device is near a network device (such as a reader), it falls within the near-field range of the network device's antenna radiation. Therefore, the A-IoT device's antenna generates an induced current through electromagnetic induction, which drives the device's low-power chip circuitry. This enables demodulation of reader-to-device (R2D) link signals and modulation of device-to-reader (D2R) signals. For backscatter links, the A-IoT device uses backscattering for signal transmission. It can be seen that passive A-IoT devices do not require an internal battery for either R2D or D2R links, making them truly zero-power terminal devices. Because passive A-IoT devices do not require a battery, their RF and baseband circuits are very simple, eliminating the need for components such as low-noise amplifiers, power amplifiers, crystal oscillators, and analog-to-digital converters. Therefore, they offer numerous advantages such as small size, light weight, low cost, and long lifespan.

[0051] Semi-passive A-IoT devices do not have built-in batteries, but they can harvest radio wave energy using RF energy harvesting modules, or solar / photovoltaic / thermal / kinetic energy harvesting modules, storing the harvested energy in an energy storage unit (such as a capacitor). The energy storage unit then powers the low-power chip circuitry of the A-IoT device, enabling demodulation of R2D link signals and modulation of backscatter links. For backscatter links, the A-IoT device uses backscattering for signal transmission. It can be seen that semi-passive A-IoT devices do not require built-in batteries for either R2D or D2R links. Although they use energy stored in capacitors, the energy originates from the radio wave energy harvested by the energy harvesting module, making them truly zero-power terminal devices. Semi-passive A-IoT devices inherit many advantages of passive A-IoT devices, resulting in small size, light weight, low price, and long lifespan.

[0052] Active A-IoT devices can have built-in batteries (conventional batteries such as dry cell batteries, rechargeable lithium batteries, etc.). The battery powers the low-power chip circuitry of the A-IoT device, enabling demodulation of R2D link signals and modulation of backward link signals. Therefore, the zero power consumption of active A-IoT devices is primarily due to the fact that D2R link signal transmission does not require the terminal's own power, but instead uses backscattering. Although active A-IoT devices use batteries, their power consumption is extremely low due to ultra-low power communication technology, thus significantly extending battery life compared to existing technologies. The built-in battery powering the chip in active A-IoT devices increases the tag's read / write distance and improves communication reliability. Therefore, active A-IoT devices are applicable in scenarios with relatively high requirements for communication distance and read latency.

[0053] Optionally, A-IoT devices include the following types: device 1, device 2a / 2b, and device c.

[0054] 1. Device 1: This device was standardized in Rel-19. It lacks batteries and energy storage capabilities and has an extremely simple structure, achieving a clock synchronization accuracy of 10^5 ppm. Due to the extremely low synchronization capability of A-IoT devices, in the Rel-19 research, A-IoT devices require R2D signals to provide a synchronization clock when transmitting signals, i.e., DO-DTT (Device-originated by device-terminated trigger) and DT (Device-terminated) services. Before performing D2R transmission, A-IoT devices receive the corresponding R2D information and obtain synchronization information. In other words, A-IoT devices do not have the ability to spontaneously send signals.

[0055] 2. Device 2a / 2b: Peak power not exceeding several hundred μW, with energy storage capability, equipped with an intermediate frequency (IF) envelope detector receiver or a zero intermediate frequency (ZIF) receiver, with a maximum initial sampling frequency offset (SFO) of 10. Y ppm; the device has internal R2D and / or D2R amplification functions, and its D2R transmission is generated autonomously by the device itself. Compared to device1, device 2a / 2b can support higher precision clocks and can support device-originated autonomous (DO-A) service requirements.

[0056] 3. Device C: Equipped with energy storage capability, featuring an IF envelope detector receiver or a ZIF receiver, with an initial SFO of up to 10. Y ppm; the device has internal R2D and / or D2R amplification capabilities. Compared to device1, device 2a / 2b can support higher precision clocks and can meet DO-A service requirements.

[0057] In some scenarios, a second device sends periodic broadcast messages to a first device. The first device can obtain transmission information related to R2D control information, as well as information related to R2D and D2R transmissions, based on these periodic broadcast messages, enabling it to send and receive information normally. However, in some cases, the first device may miss receiving periodic broadcast messages, for example, when its battery is depleted, causing it to enter a prolonged sleep state. On the one hand, if the first device continues to monitor periodic broadcast messages under such circumstances, its power consumption will be too high. On the other hand, if the missed periodic broadcast messages update information such as the reception period and time-frequency resources, but the first device still monitors the periodic broadcast messages based on the previous information, it will take a long time for the first device to resynchronize with the second device, and the prolonged monitoring of R2D messages will also result in high power consumption. Therefore, embodiments of this application provide a wireless communication method to reduce the power consumption and latency of the first device.

[0058] For ease of description, the following description uses the example of an A-IoT device accessing a reader / writer, but it should be understood that this should not limit this application.

[0059] Figure 8 A schematic diagram of the method 800 provided in this application is shown.

[0060] In method 800, the first device is an A-IoT device. This application embodiment does not limit the type of the first device. As an example, the first device is an active device (e.g., device 2a / 2b, or device c), meaning the first device supports a high-precision clock and can support the DO-A service requirements; or, the first device is another device type with higher complexity and clock precision.

[0061] In method 800, the second device is a reader / writer with A-IoT capabilities. This application embodiment does not limit the type of the second device; as an example, the second device may be a network device, a terminal device, an IAB (Internet Application Blocks) device, or a relay device.

[0062] S810, the first device sends a first request on the first transmission resource, and correspondingly, the second device receives the first request on the first transmission resource.

[0063] The first request is used to request the second device to send a broadcast message.

[0064] To distinguish it from periodic broadcast messages, this application embodiment refers to the broadcast message sent by the second device to the first device based on the first request as an on-demand (OD) broadcast message. However, it should be understood that this should not limit this application, and this application embodiment does not exclude the possibility of using other names for OD broadcast messages.

[0065] This application does not limit the specific implementation method of the first device determining the first transmission resource. As one possible implementation, the first device determines the first transmission resource based on one or more of the following: a pre-configured time-domain location, a pre-configured frequency-domain location, DO-A transmission resources, and other D2R resources corresponding to the first device.

[0066] The first possible implementation: The first device determines the time domain location of the first transmission resource based on the pre-configured time domain location.

[0067] In one possible scenario, the first device determines the time-domain location of the first transmission resource based on the time-domain location of the first signal sent by the second device.

[0068] The embodiments of this application do not limit the first signal. As one possible implementation, the first signal is a synchronization signal, or the first signal is a CFO calibration signal, or the first signal is an R2D preamble signal, or the first signal is other messages (i.e., R2D signals) sent by the second device to the first device.

[0069] In one possible implementation, the synchronization signal / CFO calibration signal can be any of the following: a sequence-based modulated signal or an unmodulated waveform signal.

[0070] For example, the protocol predefines the synchronization signal / CFO calibration signal as a sequence-based modulation signal, and based on this, the waveform of the synchronization signal / CFO calibration signal is an OFDM waveform. The synchronization signal / CFO calibration signal can be, for example, the longest linear feedback shift register sequence (m-sequence), or a Gold sequence, or a Golay sequence, or a Walsh sequence.

[0071] For example, the protocol predefines the waveform of the synchronization signal / CFO calibration signal as an unmodulated sine wave. For instance, the waveform of the synchronization signal / CFO calibration signal may be a single-tone unmodulated waveform or a multi-tone unmodulated waveform.

[0072] In this embodiment, the first signal is a short-period synchronization signal or a CFO calibration signal. After receiving / monitoring the first signal, the first device can determine the first transmission resource and send a first request in the first transmission resource to obtain the OD broadcast message. This method reduces the power consumption and latency of the first device in obtaining the OD broadcast message.

[0073] This application does not limit the specific implementation method of the first device determining the time domain position of the first transmission resource based on the time domain position of the first signal sent by the second device. Several possible implementation methods are given below.

[0074] Implementation Method 1: The time domain location of the first transmission resource is determined based on the time domain location of the first signal and the pre-configured time domain resources.

[0075] Specifically, the first device determines the time-domain position of the first transmission resource based on a reference point of the time-domain position of the first transmission resource and pre-configured time-domain resources, wherein the reference point of the time-domain position of the first transmission resource is the time-domain position of the first signal.

[0076] As one possible implementation, the pre-configured time-domain resources include one or more of the following: the offset of the start position of the time domain, the offset of the end position of the time domain, and the size of the time-domain resources requested in the first request (or, the duration of the first request).

[0077] This application does not limit the specific implementation of the first device determining the time domain position of the first transmission resource based on the time domain position of the first signal and the pre-configured time domain resources. The following is an exemplary description.

[0078] Example 1: The pre-configured time-domain resources include the offset of the time-domain start position and the duration of the first request.

[0079] For example, the first device can determine the time-domain start position of the first transmission resource by using the time-domain position of the first signal as a reference point and the offset of the time-domain start position. Furthermore, the first device can determine the time-domain end position of the first transmission resource by the duration of the first request.

[0080] Example 2: The pre-configured time-domain resources include the offset of the time-domain end position and the duration of the first request.

[0081] For example, the first device can determine the time domain end position of the first transmission resource by using the time domain position of the first signal as a reference point and the offset of the time domain end position. Furthermore, the first device can determine the time domain start position of the first transmission resource by the duration of the first request.

[0082] This application does not limit the specific implementation method by which the first device determines the reference point for the time domain location of the pre-configured time domain resources and / or the first transmission resources. As one possible implementation, the first device determines the reference point for the time domain location of the pre-configured time domain resources and / or the first transmission resources based on predefined information and / or instructions from the second device.

[0083] In one possible implementation, the second device indicates a reference point for the time-domain location of the pre-configured time-domain resources and / or the first transmission resources via one or more of the following messages: periodic broadcast messages, A-IoT paging messages, and access trigger messages.

[0084] For example, the first device caches information #A in periodic broadcast messages and determines a reference point for the time domain location of pre-configured time domain resources and / or the first transmission resource based on information #A.

[0085] Specifically, the periodic broadcast message includes information #A and information #B. The update cycle of information #A is longer than that of information #B. In other words, information #A includes a stable portion of the periodic broadcast message that will not be updated for a long period of time. Therefore, the first device can cache information #A in the periodic broadcast message for later retrieval, thereby reducing the power consumption caused by the first device frequently monitoring information #A. Information #B includes a frequently updated portion of the periodic broadcast message. This portion of the message updates more frequently. Therefore, the first device needs to continuously monitor information #B to avoid missing the reception of information #B, which would lead to a decrease in communication performance.

[0086] This application does not limit the specific implementation of the first device determining the time-domain position of the first signal as the reference point for the time-domain position of the first transmission resource. As one possible implementation, the reference point for the time-domain position of the first transmission resource can be any one of the following: the start position of the first signal in the time domain, the end position of the first signal in the time domain, the time when the second device sends the first signal, or the time when the first device receives / monitors the first signal.

[0087] Implementation Method 2: The starting position of the time domain of the first transmission resource is obtained after the time domain position of the first signal (e.g., denoted as n) and a first time period (e.g., denoted as T1). In other words, the starting position of the time domain of the first transmission resource is the time domain position of the first signal (i.e., n) after the first time period (i.e., T1).

[0088] Figure 9 An example diagram is shown illustrating how a first device, according to an embodiment of this application, determines the time-domain start position of a first transmission resource based on the time-domain position of a first signal.

[0089] See Figure 9 After the first device receives / monitors the first signal, the first device sends the first request at n+T1.

[0090] The embodiments of this application do not limit the time-domain position of the first signal. For example, the time-domain position of the first signal is the start position of the first signal in the time domain; or, the time-domain position of the first signal is the end position of the first signal in the time domain; or, the time-domain position of the first signal is the time when the second device sends the first signal; or, the time-domain position of the first signal is the time when the first device receives / monitors the first signal.

[0091] The embodiments of this application do not limit the unit of the first time period. One possible implementation is that the unit of the first time period is an absolute time unit, such as seconds, milliseconds, microseconds, or nanoseconds. Another possible implementation is that the unit of the first time period is a time unit defined in NR / LTE, such as a frame, subframe, time slot, or orthogonal frequency division multiplexing (OFDM) symbol. Yet another possible implementation is that the unit of the first time period is a time unit defined in A-IoT. For example, the unit of the first time period is an integer multiple of the chip duration under a specific subcarrier spacing (SCS) and a specific OOK-4 modulation parameter (e.g., M). For example, the unit of the first time period is the duration of L chips with M=4 when the SCS is 15kHz.

[0092] This application does not limit the method for determining the first time period (i.e., T1). As one possible implementation, the first device determines the value of T1 based on one or more of the following: the device type of the first device, the SFO of the first device, and the time delay of the first device in processing the first signal.

[0093] The following is an example illustration.

[0094] Example 1: The first device determines the value of T1 based on the type of the first device.

[0095] For example, the relationship between the type of the first device and the value of T1 is predefined in the protocol, as shown in Table 1.

[0096] Table 1

[0097] Type of the first device The value of T1 device 2b t1 device c t2

[0098] Referring to Table 1, when the device type of the first device is device 2b, the first device determines the value of T1 to be t1 based on the device type of the first device and the predefined information; when the device type of the first device is device c, the first device determines the value of T1 to be t2 based on the device type of the first device and the predefined information.

[0099] Example 2: The first device determines the value of T1 based on the first device's SFO. For example, T1 is greater than and / or equal to the first time-domain offset (e.g., denoted as T). SFO1 The value of ), where the first time domain offset is the time domain offset caused by the SFO of the first device.

[0100] Example 3: The first device determines the value of T1 based on the time delay of processing the first signal. For example, T1 is greater than and / or equal to the time delay of processing the first signal (e.g., denoted as T). process1 The value of ).

[0101] Example 4: The first device determines the value of T1 based on the SFO of the first device and the time delay of the first device in processing the first signal.

[0102] For example, the value of T1 satisfies formula (1):

[0103] T1 = T SFO1 +T process1 (1)

[0104] Among them, T SFO1 For the first time-domain offset, T process1 The time delay for the first device to process the first signal.

[0105] This application embodiment relates to T SFO1 and T process1 The unit is not limited, T SFO1 and T process1 The units can be referred to in the aforementioned explanation of the units for the first time period, and will not be repeated here.

[0106] As described above, the first device can consider various factors when determining the first time period, making the communication process more efficient. For example, considering the SFO caused by the low precision of the first device, the first device determines the first time period based on the SFO, which can reduce the probability that the first device cannot send or receive messages normally due to the SFO.

[0107] This application does not limit the implementation method of the first device determining the first time period (i.e., T1). As one possible implementation, the first device determines the first time period based on predefined information and / or instructions from the second device.

[0108] Several possible implementation methods are given below.

[0109] Implementation method 1: The first device determines the value of T1 based on predefined information.

[0110] For example, the protocol predefines T1 to a fixed value, such as 0.25 μs.

[0111] In another example, the protocol predefines X candidate values, and the first device determines one of the X candidate values ​​as the value of T1, where X is an integer greater than and / or equal to 1.

[0112] In another example, the protocol predefines X candidate values, and the first device determines the value of T1 based on the device type of the first device and the X candidate values.

[0113] For example, X = 3, and the X candidate values ​​are T. 1a T 1b and T 1c Furthermore, the protocol predefines X candidate values ​​associated with the device type of the first device, T 1a Associated with device 1, T 1b Associated with device 2b, T 1c Associated with device c; based on this, when the device type of the first device is device 1, the first device determines that the value of T1 is T. 1a When the device type of the first device is device 2b, the first device determines that the value of T1 is T. 1b When the device type of the first device is device c, the first device determines that the value of T1 is T. 1c .

[0114] Implementation method 2: The first device determines the value of T1 according to the instructions of the second device.

[0115] This application does not limit the specific implementation of the value of the second device indicating T1. As one possible implementation, the second device configures the value of T1 for the first device through periodic broadcast messages. For example, the first device caches information #A in the periodic broadcast messages and determines the value of T1 based on information #A.

[0116] In some possible scenarios, implementation method one and implementation method two can be used in combination, that is, the first device determines the value of T1 based on predefined information and the instruction of the second device.

[0117] For example, the protocol predefines X candidate values, and the second device indicates that Y candidate values ​​among the X candidate values ​​can be used as values ​​for T1, where Y is an integer greater than and / or equal to 1 and less than and / or equal to X.

[0118] See Table 2, X=4, which is the protocol predefined table 2.

[0119] Table 2

[0120] Candidate value sequence number / index Candidate values 0 <![CDATA[T 1a ]]> 1 <![CDATA[T 1b ]]> 2 <![CDATA[T 1c ]]> 3 <![CDATA[T 1d ]]>

[0121] For example, if Y = 1, the second device indicates one candidate value (e.g., T).1a For example, if Y = 2, the second device indicates two candidate values ​​(e.g., T). 1a and T 1b ) is the value of T1.

[0122] The embodiments of this application do not limit the specific implementation of the second device indicating Y candidate values.

[0123] In one example, the second device uses N bits to indicate the indices of Y candidate values, for example, N=2, where "00" represents the candidate value with indices 0 (i.e., T). 1a "01" represents the candidate value with index 1 (i.e., T). 1b "10" represents the candidate value with index 2 (i.e., T). 1c "11" represents the candidate value with index 3 (i.e., T). 1d ).

[0124] In another example, the second device directly indicates the specific value of the candidate value. For instance, the second device indicates that the value of T1 is T. 1a .

[0125] The second possible implementation: The first device determines the frequency domain location of the first transmission resource based on the pre-configured frequency domain location.

[0126] In the first possible scenario, the first device determines the frequency domain location of the first transmission resource based on the first information.

[0127] As one possible implementation, the first information includes one or more of the following: the bandwidth of the channel, the start position of the frequency domain location, the end position of the frequency domain location, the size of the guard band, the frequency domain offset of the frequency domain location, the center frequency point, and the index / identifier of the channel / band.

[0128] This application does not limit the specific implementation method of the first device determining the first information. As one possible implementation, the first device determines the first information based on predefined information and / or instructions from the second device.

[0129] This application does not limit the specific implementation of the second device indicating the first information. As one possible implementation, the first information may be carried in one or more of the following ways: A-IoT paging message, access trigger message, R2D control information, periodic broadcast message, synchronization signal, or CFO calibration signal.

[0130] For example, the first device caches information #A in periodic broadcast messages and determines the first information based on information #A.

[0131] The embodiments of this application do not limit the name of the first information. For example, the first information may also be called anchored frequency domain position information, or the first information may also be called fixed frequency domain position information.

[0132] This application does not limit the specific implementation method of the first device determining the frequency domain location of the first transmission resource based on the first information. Several possible implementation methods are given below.

[0133] Implementation Method 1: The first device determines the frequency domain location of the first transmission resource according to the first information pre-defined in the protocol.

[0134] For example, the protocol predefines the start and end positions of the frequency domain location. Based on this, the first device can determine the frequency domain location of the first transmission resource according to the start and end positions of the frequency domain location.

[0135] For example, the protocol predefines the start position of the frequency domain location and the size of the channel bandwidth. Based on this, the first device can determine the start position of the frequency domain of the first transmission resource according to the start position of the frequency domain location, and the first device can determine the end position of the frequency domain of the first transmission resource according to the size of the channel bandwidth.

[0136] Method 2: The first device determines the frequency domain location of the first transmission resource based on the first information indicated by the second device.

[0137] For example, the second device indicates the start and end positions of the frequency domain location. Based on this, the first device can determine the frequency domain location of the first transmission resource according to the start and end positions of the frequency domain location.

[0138] For example, the second device indicates the start position of the frequency domain location and the size of the channel bandwidth. Based on this, the first device can determine the start position of the frequency domain of the first transmission resource according to the start position of the frequency domain location, and the first device can determine the end position of the frequency domain of the first transmission resource according to the size of the channel bandwidth.

[0139] Implementation Method 3: The first device determines the frequency domain location of the first transmission resource based on the first information pre-defined in the protocol and indicated by the second device.

[0140] In one possible scenario, the protocol predefines M candidate channels, and the second device indicates one of the M candidate channels as the frequency domain location of the first transmission resource, where M is an integer greater than and / or equal to 1.

[0141] For example, M=3, and the protocol predefines M candidate channels, such as candidate channel #1, candidate channel #2, and candidate channel #3. The second device indicates the index of one of the M candidate channels (e.g., candidate channel #1). Based on this, the first device can determine the frequency domain location of the first transmission resource as channel #1.

[0142] The following combination Figure 10 A complete example is given of a first device determining the frequency domain location of a first transmission resource based on first information.

[0143] Figure 10 An example diagram is shown illustrating how a first device, according to first information, determines the frequency domain location of a first transmission resource based on first information, as provided in an embodiment of this application.

[0144] Example 1, see Figure 10 The first piece of information indicates the frequency domain offset and the bandwidth of the channel.

[0145] Step 1: The first device determines the frequency domain reference point based on predefined information and / or instructions from the second device.

[0146] Step 2: The first device determines the frequency domain offset and the bandwidth of the channel based on the first information.

[0147] The first device can determine the starting position of channel #0 based on the frequency domain offset and the frequency domain reference point. Furthermore, the first device can determine the frequency domain range occupied by channel #0 based on the bandwidth of the channel, that is, the first device can determine the ending position of channel #0.

[0148] Step 3: The first device determines that channel #0 is the frequency domain location of the first transmission resource, and based on this, the first device sends a first request on channel #0.

[0149] This application uses a step-by-step approach to describe the scheme in many places, which will be explained uniformly here. The step-by-step approach is only for ease of description and does not limit this application. In some possible implementations, based on actual application requirements, different steps can be combined into one step, or one step can be broken down into multiple steps. In some possible implementations, the execution order between steps can be adjusted based on actual application requirements.

[0150] Example 2: See Figure 10 The first piece of information indicates the starting position of the frequency domain location and the bandwidth of the channel.

[0151] Step 1: The first device determines M candidate channels based on predefined information and / or instructions from the second device, where M is an integer greater than and / or equal to 1.

[0152] For example, M = 4, and the M candidate channels are denoted as channel #0, channel #1, channel #2, and channel #3.

[0153] Step 2: The first device determines the starting position of the M candidate channels and the bandwidth of each of the M candidate channels based on the first information.

[0154] Specifically, the first device determines the starting position of M candidate channels (e.g., the starting position of channel #0) based on the starting position of the frequency domain position indicated by the first information. Further, the first device determines the bandwidth of each of the M candidate channels based on the bandwidth of the channel indicated by the first information. Based on this, the first device can determine the frequency domain position corresponding to each of the M candidate channels.

[0155] Step 3: The first device determines the frequency domain location of one of the M candidate channels as the first transmission resource based on predefined information and / or the instructions of the second device.

[0156] For example, the second device indicates that channel #1 is the frequency domain location of the first transmission resource, and based on this, the first device sends a first request on channel #1.

[0157] This application does not limit the specific implementation of the second device indicating the frequency domain location of one of the M candidate channels as the first transmission resource. As one possible implementation, the second device indicates the index of one of the M candidate channels.

[0158] In the second possible scenario, the first device determines the frequency domain location of the first transmission resource based on the frequency domain location of the received R2D message.

[0159] This application embodiment does not limit the R2D messages received by the first device. As one possible implementation, the R2D messages received by the first device include one of the following: A-IoT paging message, access trigger message, R2D control information, periodic broadcast message, synchronization signal, and CFO calibration signal.

[0160] This application does not limit the specific implementation method of the first device determining the frequency domain location of the first transmission resource based on the frequency domain location of the received R2D message. Several possible implementation methods are given below.

[0161] Implementation Method 1: The frequency domain position of the first transmission resource is the same as the frequency domain position of the R2D message already received by the first device.

[0162] As an example, the first device caches information #A in periodic broadcast messages and determines the frequency domain location of the first transmission resource based on information #A.

[0163] For example, information #A indicates the frequency domain location of the A-IoT paging message. Based on this, the first device sends a first request at the frequency domain location of the A-IoT paging message according to information #A.

[0164] For example, information #A indicates the frequency domain location of the access trigger message. Based on this, the first device sends a first request at the frequency domain location of the access trigger message according to information #A.

[0165] As an example, the first device sends a first request at the frequency domain location of the synchronization signal.

[0166] Implementation Method 2: The first device determines the frequency domain position of the first transmission resource based on the frequency domain position of the received R2D message and the pre-configured frequency domain resources.

[0167] Specifically, the first device determines the frequency domain position of the first transmission resource based on a reference point of the frequency domain position of the first transmission resource and a pre-configured additional frequency domain resource, wherein the reference point of the frequency domain position of the first transmission resource is the frequency domain position of the R2D message already received by the first device.

[0168] The pre-configured frequency domain resources include one or more of the following: the offset of the frequency domain start position, the offset of the frequency domain end position, and the size of the first requested frequency domain resources (or, the size of the channel bandwidth).

[0169] This application does not limit the specific implementation of how the first device determines the frequency domain position of the first transmission resource based on the frequency domain position of the R2D message received by the first device and the pre-configured frequency domain resources. The following is an exemplary description.

[0170] Example 1: Pre-configured frequency domain resources include the offset of the frequency domain start position and the size of the channel bandwidth.

[0171] For example, the first device can determine the frequency domain start position of the first transmission resource by using the frequency domain position of the R2D message received by the first device as a reference point and the offset of the frequency domain start position. Furthermore, the first device can determine the frequency domain end position of the first transmission resource by the size of the channel bandwidth.

[0172] Example 2: Pre-configured frequency domain resources include the offset of the frequency domain end position and the size of the channel bandwidth.

[0173] For example, the first device can determine the frequency domain end position of the first transmission resource by using the frequency domain position of the R2D message received by the first device as a reference point and the offset of the frequency domain end position. Furthermore, the first device can determine the frequency domain start position of the first transmission resource by the size of the channel bandwidth.

[0174] This application does not limit the specific implementation method by which the first device determines the reference point for the frequency domain position of the pre-configured frequency domain resources and / or the first transmission resources. As one possible implementation, the first device determines the reference point for the frequency domain position of the pre-configured frequency domain resources and / or the first transmission resources based on predefined information and / or instructions from the second device.

[0175] In one possible implementation, the second device indicates a reference point for the frequency domain location of the pre-configured frequency domain resources and / or the first transmission resources via one or more of the following messages: A-IoT paging message, access trigger message, R2D control information, periodic broadcast message, synchronization signal, and CFO calibration signal.

[0176] For example, the first device caches information #A in periodic broadcast messages and determines a reference point for the frequency domain location of pre-configured frequency domain resources and / or the first transmission resource based on information #A.

[0177] This application does not limit the specific implementation of the reference point for the first device to determine the frequency domain position of the first transmission resource based on the frequency domain position of the R2D messages received by the first device. As one possible implementation, the reference point for the frequency domain position of the first transmission resource may be any one of the following: the lowest point of the frequency domain position of the R2D messages received by the first device, the highest point of the frequency domain position of the R2D messages received by the first device, or the center frequency point of the frequency domain position of the R2D messages received by the first device.

[0178] In the third possible scenario, the first device determines the frequency domain location of the first transmission resource based on the frequency domain location of the first signal sent by the second device.

[0179] The embodiments of this application do not limit the first signal. As one possible implementation, the first signal is a synchronization signal, or the first signal is a CFO calibration signal, or the first signal is another message sent by the second device to the first device (i.e., an R2D signal).

[0180] This application does not limit the method for determining the frequency domain position of the first signal. As one possible implementation, the frequency domain position of the first signal is determined by the second device, and / or the frequency domain position of the first signal is predefined by the protocol.

[0181] This application does not limit the specific implementation of the first device determining the frequency domain position of the first transmission resource based on the frequency domain position of the first signal. Several possible solutions are given below.

[0182] Option 1: The first device determines that the frequency domain location of the first transmission resource is the same as the frequency domain location of the first signal based on predefined information. Based on this, the first device receives / monitors the first signal and determines the frequency domain location of the first signal. Further, the first device determines the frequency domain location for sending the first request based on the frequency domain location of the first signal.

[0183] Option 2: The first device determines the frequency domain position of the first transmission resource based on predefined information by using the frequency domain position of the first signal as a reference point (or starting position) and passing through a first frequency domain offset. Based on this, the first device receives / monitors the first signal and determines the frequency domain position of the first signal. Further, the first device determines the frequency domain position of the first transmission resource based on the frequency domain position of the first signal and the first frequency domain offset.

[0184] The embodiments of this application do not limit the reference point and the first frequency domain offset determined by the first device.

[0185] As one possible implementation, the reference point is one or more of the following: the highest point of the frequency domain position of the first signal, the lowest point of the frequency domain position of the first signal, the starting position of the frequency domain position of the first signal, the ending position of the frequency domain position of the first signal, the center frequency point of the frequency domain position of the first signal, and the middle position of the frequency domain position of the first signal.

[0186] As one possible implementation, the first frequency domain offset refers to one or more of the following: the offset of the lowest point of the frequency domain position of the first transmission resource from the reference point, the offset of the highest point of the frequency domain position of the first transmission resource from the reference point, the offset of the starting position of the frequency domain position of the first transmission resource from the reference point, the offset of the ending position of the frequency domain position of the first transmission resource from the reference point, the offset of the center frequency point of the frequency domain position of the first transmission resource from the reference point, and the offset of the middle position of the frequency domain position of the first transmission resource from the reference point.

[0187] This application does not limit the specific method by which the first device determines the first frequency domain offset. As one possible implementation, the first device determines the first frequency domain offset based on predefined information and / or configuration information sent by the second device.

[0188] This application does not limit the specific implementation of the second device indicating the first frequency domain offset. As one possible implementation, the second device indicates the absolute value of the offset. As another possible implementation, the second device indicates the smallest frequency domain unit (or smallest granularity) of the offset and the number of the smallest frequency domain units of the offset. For example, the smallest frequency domain unit is 180kHz or a frequency domain unit defined in NR (resource block (RB), physical resource block (PRB), etc.) or a newly defined frequency domain unit. The number N of the smallest frequency domain units of the offset indicated by the second device is an integer greater than and / or equal to 1.

[0189] The following is a complete example of Scheme 2.

[0190] Step 1: The first device determines the frequency domain position of the first transmission resource based on the predefined information by taking the frequency domain position of the first signal as the reference point and passing through the first frequency domain offset.

[0191] Step 2: The first device determines the first frequency domain offset based on the configuration information of the second device.

[0192] For example, the configuration information of the second device includes one or more of the following: first frequency domain offset, guard band size, channel bandwidth size, and transmission bandwidth size.

[0193] For example, the first frequency domain offset is the offset of the lowest point of the frequency domain position of the first transmission resource from the lowest point of the frequency domain position of the first signal.

[0194] Among them, the size of the guard band, the bandwidth of the channel, and the transmission bandwidth satisfy the formula (2):

[0195] Channel bandwidth = guard band size + transmission bandwidth size (2)

[0196] Step 3: The first device receives / monitors the first signal and determines the lowest point of the frequency domain position of the first signal.

[0197] Step 4: The first device determines the lowest point of the frequency domain position of the first transmission resource based on the lowest point of the frequency domain position of the first signal and the first frequency domain offset. Further, the first device determines the frequency domain position of the first transmission resource based on the lowest point of the frequency domain position of the first transmission resource and the bandwidth of the channel.

[0198] Option 3: The first device determines, according to the instructions of the second device, that the frequency domain location of the first transmission resource is the same as the frequency domain location of the first signal. Based on this, the first device receives / monitors the first signal and determines the frequency domain location of the first signal. Furthermore, the first device sends a first request at the frequency domain location of the first signal.

[0199] Option 4: The first device determines the frequency domain position of the first transmission resource based on the instruction of the second device by using the frequency domain position of the first signal as the starting position and passing through a first frequency domain offset. Based on this, the first device receives / monitors the first signal and determines the frequency domain position of the first signal. Further, the first device determines the frequency domain position of the first transmission resource based on the frequency domain position of the first signal and the first frequency domain offset.

[0200] The embodiments of this application do not limit the specific implementation of the second device indicating the first frequency domain offset.

[0201] As one possible implementation, method 800 further includes: a first device receiving / monitoring a first signal on a first frequency domain resource. Based on this, the first device is able to determine the first transmission resource according to the time domain location and / or frequency domain location of the first signal.

[0202] In one possible scenario, the first frequency domain resource is a specific frequency domain location, such as the frequency domain location indicated by the first information or the frequency domain location of the R2D message received by the first device.

[0203] Another possible scenario is that the first frequency domain resource is frequency domain range #1. Here, frequency domain range #1 indicates a frequency domain range used to transmit the first signal, or frequency domain range #1 is a channel.

[0204] Specifically, the communication system supports the second device transmitting a first signal on any one of G channels, where G is an integer greater than and / or equal to 1. Since the first device cannot determine the channel on which the second device transmits the first signal, monitoring / receiving the first signal on all G channels would cause excessive power consumption for the first device. Therefore, the first device determines a frequency domain range #1 and monitors the first signal on the channel indicated by frequency domain range #1.

[0205] This application does not limit the specific implementation of the first device determining the frequency domain range #1. As one possible implementation, the first device determines the frequency domain range #1 based on predefined information and / or instructions from the second device.

[0206] As an example, the second device indicates the channel index corresponding to frequency range #1.

[0207] For example, G=4, the communication system supports the second device transmitting a first signal on any one of the G channels (e.g., denoted as channel #1, channel #2, channel #3, and channel #4). The second device indicates a channel corresponding to frequency range #1 (e.g., channel #1), meaning the second device transmits the first signal on channel #1. Based on this, the first device monitors channel #1. Compared to the first device monitoring all G channels used to transmit the first signal, this method reduces the frequency range of the first device monitoring the first signal.

[0208] This application does not limit the specific implementation of the second device indicating frequency range #1. As one possible implementation, the second device indicates frequency range #1 through any of the following messages: A-IoT paging message, access trigger message, R2D control information, periodic broadcast message, synchronization signal, and CFO calibration signal.

[0209] For example, the first device buffers information #A from periodic broadcast messages, and the first device can determine the channel where frequency range #1 is located based on information #A. As an example, information #A indicates that the channel where frequency range #1 is located is channel #2.

[0210] The first device receives / monitors the first signal on the first frequency domain resource to determine the first transmission resource. In this way, the frequency domain range of the first device monitoring the first signal can be reduced, thereby reducing the power consumption and latency caused by the first device monitoring the first signal.

[0211] The third possible implementation: The first device determines the time-domain location and / or frequency-domain location of the first transmission resource based on the resources of the DO-A transmission.

[0212] The resources for DO-A transmission refer to one or more of the following: the resources of the first DO-A transmission of the first device, and the resources of other DO-A transmissions of the first device.

[0213] In this embodiment, the other DO-A transmission resources of the first device refer to the DO-A transmission resources other than the first DO-A transmission resources of the first device. This embodiment does not exclude other methods of distinguishing the first DO-A transmission resources of the first device from other DO-A transmission resources.

[0214] The resources used for DO-A transmission are used to transmit one or more of the following: Message 1 (Msg1) corresponding to the DO-A service, the scheduling request message of the DO-A service, and the data of the DO-A service.

[0215] In this embodiment of the application, the first device uses DO-A transmission resources to send the first request. On the one hand, it is not necessary to configure new resources for the first device to send the first request, thereby reducing the overhead of R2D resources; on the other hand, this method can reduce the signaling overhead of configuring the first transmission resources.

[0216] In some possible implementations, the first device uses the resources of the first DO-A transmission to send the first request, thereby reducing the duration of the first device's monitoring in the time domain and thus reducing communication latency.

[0217] This application does not limit the specific content of the resources for DO-A transmission. As one possible implementation, the resources for DO-A transmission include time-domain resources and / or frequency-domain resources.

[0218] One possible implementation is that the time-domain resources of DO-A transmission include one or more of the following: the number of resources in the time domain, the start position of the time-domain resources, the duration of the time-domain resources, the end position of the time-domain resources, and the period of DO-A transmission.

[0219] For example, the time-domain resources of DO-A transmission include the start position and the end position of the time-domain resources. Based on this, the first device can determine the time-domain position of the first transmission resource according to the start position and the end position of the time-domain resources.

[0220] For example, the time-domain resources of DO-A transmission include the start position and duration of the time-domain resources. Based on this, the first device can determine the end position of the time-domain resources according to the start position and duration of the time-domain resources, and further, the first device can determine the time-domain position of the first transmission resource according to the start position and end position of the time-domain resources.

[0221] One possible implementation is that the frequency domain resources of DO-A transmission include one or more of the following: the number of resources in the frequency domain, the size of the channel bandwidth, the start position of the frequency domain resources, the end position of the frequency domain resources, the size of the guard band, the frequency offset, and the center frequency.

[0222] For example, the frequency domain resources of DO-A transmission include the start position and the end position of the frequency domain resources. Based on this, the first device can determine the frequency domain position of the first transmission resource according to the start position and the end position of the frequency domain resources.

[0223] For example, the frequency domain resources of DO-A transmission include the start position and frequency offset of the frequency domain resources. Based on this, the first device can determine the end position of the frequency domain resources according to the start position and frequency offset of the frequency domain resources. Furthermore, the first device can determine the frequency domain position of the first transmission resource according to the start position and end position of the frequency domain resources.

[0224] This application does not limit the specific implementation method of the first device determining the resources for DO-A transmission in the embodiments. As one possible implementation, the first device determines the resources for DO-A transmission based on predefined information and / or instructions from the second device.

[0225] One possible implementation is that the second device configures the DO-A transmission resources through one or more of the following messages: periodic broadcast messages, A-IoT paging messages, and access trigger messages.

[0226] For example, the first device caches information #A in periodic broadcast messages and determines the resources for DO-A transmission based on information #A.

[0227] In some possible implementations, the second device needs to determine the priority of the first request when processing the first request. Several possible implementations are given below.

[0228] Implementation method 1, method 800 includes: a first device sending a first request using DO-A transmission resources, wherein the first request includes priority information #1, and the priority information #1 is used by a second device to determine the priority of the first request.

[0229] This application does not limit the specific implementation of the first device indicating the priority of the first request in the embodiments. As one possible implementation, the first device uses L bits to indicate the priority of the first request, that is, the priority information #1 includes L bits, where L is an integer greater than and / or equal to 1.

[0230] This application does not limit the specific implementation of the first device using L bits to indicate the priority of the first request. As one possible implementation, the larger the value indicated by the L bits, the higher the priority of the first request; for example, a bit value of "000" indicates a lower priority than a bit value of "001". As another possible implementation, the smaller the value indicated by the L bits, the higher the priority of the first request; for example, a bit value of "000" indicates a higher priority than a bit value of "001".

[0231] For example, if L=3, the first device uses L bits to indicate the priority of the first request, and the larger the value indicated by L bits, the higher the priority of the first request. When priority information #1 is "000", it indicates that the priority of the first request is low, and when priority information #1 is "001", it indicates that the priority of the first request is high.

[0232] In this embodiment, high priority and low priority are relative concepts. A low priority for the first request means that the first request has a low priority relative to the DO-A service of the first device; in other words, the first request has a lower priority than the DO-A service of the first device. A high priority for the first request means that the first request has a high priority relative to the DO-A service of the first device; in other words, the first request has a higher priority than the DO-A service of the first device. The DO-A service refers to one or more of the following transmitted by the first device: message 1 corresponding to the DO-A service, a scheduling request message for the DO-A service, and data for the DO-A service.

[0233] In the second implementation method, the priority of the first request is predefined in the protocol, and the second device can determine the priority of the first request based on the predefined information.

[0234] This application does not limit the specific implementation of the priority of the first request predefined in the protocol embodiments. As one possible implementation, the protocol predefines the priorities of different types of uplink transmissions / D2R transmissions.

[0235] As an example, the protocol predefines Table 3, which indicates the priority of different types of uplink transmissions.

[0236] Table 3

[0237] Serial Number / Index Uplink transmission 0 First Request 1 Message 1 corresponding to DO-A service 2 DO-A service scheduling request message 3 Data from DO-A services

[0238] For example, the larger the predefined sequence number in the protocol, the higher the priority of the corresponding uplink transmission. Based on this, the first request has the lowest priority, and the data in the DO-A service has the highest priority.

[0239] For example, the smaller the predefined sequence number in the protocol, the higher the priority of the corresponding uplink transmission. Based on this, the first request has the highest priority, and the data in DO-A services has the lowest priority.

[0240] In the third implementation method, the second device determines the priority of the first request and instructs the first device accordingly.

[0241] Specifically, the second device determines the priority of different types of uplink transmissions, and further, the second device indicates the priority of the first request to the first device.

[0242] This application does not limit the specific implementation method of the second device determining the priority of different types of uplink transmissions. As one possible implementation, the second device determines the priority of different types of uplink transmissions based on predefined information, or the second device determines the priority of different types of uplink transmissions itself.

[0243] The embodiments of this application do not limit the specific implementation method of the second device indicating the priority of the first request to the first device.

[0244] In one possible implementation, the second device indicates to the first device that the priority number of the first request is 0, the priority number of message 1 corresponding to the DO-A service is 1, the priority number of the scheduling request message of the DO-A service is 2, and the priority number of the data of the DO-A service is 3. Wherein, the larger the priority number, the higher the priority of the corresponding uplink transmission; or, the smaller the priority number, the higher the priority of the corresponding uplink transmission.

[0245] The embodiments of this application provide various implementation methods that enable the second device to determine the priority of the first request. When the first request has a high priority, the second device can choose to process the first request first and send an OD broadcast message to the first device, thereby reducing the latency of the first device. When the first request has a low priority, the second device processes the DO-A service before processing the first request, ensuring the normal operation of the DO-A service while configuring the OD broadcast message for the first device.

[0246] The fourth possible implementation: The first device determines the time-domain location and / or frequency-domain location of the first transmission resource based on the D2R resources corresponding to other first devices.

[0247] As one possible implementation, method 800 includes: a first device receiving / monitoring R2D control information and / or R2D data sent by a second device to another first device; the first device determining, based on the R2D control information and / or R2D data sent by the second device to the other first device, the D2R resources configured by the second device for the other first device. Further, the first device uses the D2R resources corresponding to the other first device to send a first request.

[0248] In one possible scenario, the first device receives / monitors the R2D information sent by the second device to other first devices as shown in Table 4.

[0249] Table 4

[0250]

[0251] Another possible scenario is that R2D control information is used to schedule R2D transmissions corresponding to other first devices. As one possible implementation, the R2D transmissions corresponding to other first devices are used to transmit one or more of the following information: A-IoT paging messages from other first devices, access trigger messages from other first devices, and periodic broadcast messages.

[0252] R2D data includes one or more of the following: A-IoT paging messages from other first devices, access trigger messages from other first devices, and periodic broadcast messages.

[0253] In this embodiment, after receiving / monitoring R2D control information and / or R2D data, the first device obtains the D2R resources configured by the second device for other first devices. The first device occupies the D2R resources of other first devices to send a first request. This method reduces the power consumption and latency of the first device in obtaining the first transmission resources.

[0254] The following combination Figure 11 Please provide a detailed explanation.

[0255] Figure 11 An example diagram is shown illustrating how a first device, according to an embodiment of this application, determines the temporal location of a first transmission resource based on R2D control information and / or R2D data sent by a second device to another first device.

[0256] See Figure 11 The time domain position of the first transmission resource is obtained after a second time period (e.g., T2) starting from the time domain position of the R2D control information and / or R2D data (e.g., denoted as m). In other words, after the first device receives / monitors the R2D control information and / or R2D data sent by the second device to other first devices, the first device sends the first request at m+T2.

[0257] The embodiments of this application do not limit the method for determining the time-domain position of R2D control information and / or R2D data. For example, the time-domain position of R2D control information and / or R2D data is the start position of R2D control information and / or R2D data in the time domain; or, the time-domain position of R2D control information and / or R2D data is the end position of R2D control information and / or R2D data in the time domain; or, the time-domain position of R2D control information and / or R2D data is the moment when the second device sends R2D control information and / or R2D data; or, the time-domain position of R2D control information and / or R2D data is the moment when the first device receives / monitors R2D control information and / or R2D data.

[0258] The embodiments of this application do not limit the unit of the second time period. The unit of the second time period can be referred to the aforementioned explanation of the unit of the first time period, and will not be repeated here.

[0259] This application does not limit the method for determining the second time period (i.e., T2). As one possible implementation, the first device determines the value of T2 based on one or more of the following: the device type of the first device, the SFO of the first device, and the time delay of the first device in processing R2D control information and / or R2D data of other first devices.

[0260] The following is an example illustration.

[0261] Example 1: The first device determines the value of T2 based on the type of the first device.

[0262] For example, the relationship between the type of the first device and the value of T2 is predefined in the protocol, as shown in Table 5.

[0263] Table 5

[0264] Type of the first device The value of T2 device 2b t1 device c t2

[0265] Referring to Table 5, when the device type of the first device is device 2b, the first device determines the value of T2 to be t1 based on the device type of the first device and the predefined information; when the device type of the first device is device c, the first device determines the value of T2 to be t2 based on the device type of the first device and the predefined information.

[0266] Example 2: The first device determines the value of T2 based on the first device's SFO. For example, T2 is greater than and / or equal to the second time-domain offset (e.g., denoted as T). SFO2 The value of ), where the second time-domain offset is the time-domain offset caused by the SFO of the first device.

[0267] Example 3: The first device determines the value of T2 based on the time delay of the first device in processing the R2D control information and / or R2D data of other first devices. For example, T2 is greater than and / or equal to the time delay of the first device in processing the R2D control information and / or R2D data of other first devices (e.g., denoted as T). process2 The value of ).

[0268] Example 4: The first device determines the value of T2 based on the first device's SFO and the time delay of the first device in processing the R2D control information and / or R2D data of other first devices.

[0269] For example, the value of T2 satisfies formula (3):

[0270] T2 = T SFO2 +T process2 (3)

[0271] Among them, T SFO2 For the second time-domain offset, T process2 The time delay for the first device to process R2D control information and / or R2D data of other first devices.

[0272] This application embodiment relates to T SFO2 and T process2 The unit is not limited, T SFO2 and T process2 The units can be referred to in the aforementioned explanation of the units for the first time period, and will not be repeated here.

[0273] As described above, the first device can consider various factors when determining the second time period, making the communication process more efficient. For example, considering the SFO caused by the low precision of the first device, the first device determines the second time period based on the SFO, which can reduce the probability that the first device cannot send or receive messages normally due to the SFO.

[0274] This application does not limit the implementation method of the first device determining the second time period (i.e., T2). As one possible implementation, the first device determines the second time period based on predefined information and / or instructions from the second device.

[0275] The specific implementation method of the first device determining the second time period based on predefined information and / or instructions from the second device can be referred to the aforementioned description of the first device determining the first time period, and will not be repeated here.

[0276] The embodiments of this application do not limit the specific implementation of the first device determining the frequency domain location of the first transmission resource based on the R2D control information and / or R2D data sent by the second device to other first devices.

[0277] As one possible implementation, R2D control information and / or R2D data indicate one or more of the following: the number of resources in the frequency domain, the size of the channel bandwidth, the start position of the frequency domain resources, the end position of the frequency domain resources, the size of the guard band, the frequency domain offset, and the center frequency.

[0278] For example, R2D control information and / or R2D data indicate the start and end positions of the frequency domain resources. Based on this, the first device can determine the frequency domain position of the first transmission resource according to the start and end positions of the frequency domain resources.

[0279] For example, R2D control information and / or R2D data indicate the start position and frequency offset of the frequency domain resource. Based on this, the first device can determine the end position of the frequency domain resource according to the start position and frequency offset of the frequency domain resource, and further, the first device can determine the frequency domain position of the first transmission resource according to the start position and end position of the frequency domain resource.

[0280] In some possible implementations, the second device needs to determine the priority of the first request when processing the first request. Several possible implementations are given below.

[0281] Implementation method 1, method 800 includes: a first device occupies the D2R resources corresponding to other first devices to send a first request, wherein the first request includes priority information #2, and the priority information #2 is used by the second device to determine the priority of the first request.

[0282] This application does not limit the specific implementation of the first device indicating the priority of the first request in the embodiments. As one possible implementation, the first device uses P bits to indicate the priority of the first request, that is, priority information #2 includes P bits, where P is an integer greater than and / or equal to 1.

[0283] This application does not limit the specific implementation of the first device using P bits to indicate the priority of the first request. As one possible implementation, the larger the value indicated by the P bits, the higher the priority of the first request; for example, a bit value of "000" indicates a lower priority than a bit value of "001". As another possible implementation, the smaller the value indicated by the P bits, the higher the priority of the first request; for example, a bit value of "000" indicates a higher priority than a bit value of "001".

[0284] For example, if P=3, the first device uses P bits to indicate the priority of the first request, and the larger the value indicated by the P bits, the higher the priority of the first request. When priority information #2 is "000", it indicates that the priority of the first request is low, and when priority information #2 is "001", it indicates that the priority of the first request is high.

[0285] In this embodiment, high priority and low priority are relative concepts. A low priority for the first request means that the first request has a lower priority relative to the D2R information of other first devices; in other words, the first request has a lower priority than the D2R information of other first devices. A high priority for the first request means that the first request has a higher priority relative to the D2R information of other first devices; in other words, the first request has a higher priority than the D2R information of other first devices.

[0286] In the second implementation method, the priority of the first request is predefined in the protocol, and the second device can determine the priority of the first request based on the predefined information.

[0287] This application does not limit the specific implementation of the priority of the first request predefined in the protocol embodiments. As one possible implementation, the protocol predefines the priorities of different types of uplink transmissions / D2R transmissions.

[0288] As an example, the protocol predefines Table 6, which indicates the priority of different types of uplink transmissions.

[0289] Table 6

[0290] Serial Number / Index Uplink transmission 0 First Request 1 D2R information from other first devices

[0291] For example, the larger the predefined sequence number in the protocol, the higher the priority of the corresponding uplink transmission. Based on this, the priority of the first request is lower than the D2R information of other first devices.

[0292] For example, the smaller the predefined sequence number in the protocol, the higher the priority of the corresponding uplink transmission. Based on this, the first request has a higher priority than other D2R information from the first device.

[0293] In the third implementation method, the second device determines the priority of the first request and instructs the first device accordingly.

[0294] Specifically, the second device determines the priority of different types of uplink transmissions, and further, the second device indicates the priority of the first request to the first device.

[0295] This application does not limit the specific implementation method of the second device determining the priority of different types of uplink transmissions. As one possible implementation, the second device determines the priority of different types of uplink transmissions based on predefined information, or the second device determines the priority of different types of uplink transmissions itself.

[0296] The embodiments of this application do not limit the specific implementation method of the second device indicating the priority of the first request to the first device.

[0297] In one possible implementation, the second device indicates to the first device that the priority number of the first request is 0, and the priority number of the D2R information of other first devices is 1. The higher the priority number, the higher the priority of the corresponding uplink transmission; conversely, the lower the priority number, the higher the priority of the corresponding uplink transmission.

[0298] The embodiments of this application provide various implementation methods that enable the second device to determine the priority of the first request. When the first request has a high priority, the second device can choose to process the first request first and send an OD broadcast message to the first device, thereby reducing the latency of the first device. When the first request has a low priority, the second device processes the D2R information of other first devices before processing the first request, ensuring normal communication of other first devices while configuring the OD broadcast message for the first device.

[0299] Among the possible implementations, the fourth possible implementation is applicable to the case where the first device loses synchronization.

[0300] In some possible implementations, the above four possible implementations (i.e., the first to the fourth possible implementations) can be used in combination.

[0301] This application does not limit the size of the time-domain resource of the first transmission resource. Several possible implementation methods are given below.

[0302] (1) The first device determines the size of the time domain resource of the first transmission resource according to the predefined information.

[0303] One possible implementation is that the protocol predefines one or more of the following: the message size of the first request, the encoding method of the first request, and the modulation method of the first request. Based on this, the first device determines the size of the time-domain resource of the first transmission resource according to the predefined information.

[0304] Another possible implementation is that the protocol predefines the duration of the time-domain resource requested in the first request (e.g., denoted as Td), based on which the first device determines the size of the time-domain resource of the first transmission resource according to Td.

[0305] The embodiments of this application do not limit the unit of Td. The unit of Td can be referred to the above description of the unit of the first time period, which will not be repeated here.

[0306] (2) The first device determines the size of the first transmission resource according to the instructions of the second device.

[0307] In one possible implementation, the second device indicates one or more of the following: the size of the first requested information, the encoding method of the first request, and the modulation method of the first request. Based on this, the first device determines the size of the time-domain resource of the first transmission resource according to the instructions of the second device.

[0308] In another possible implementation, the second device indicates the duration (i.e., Td) of the time-domain resource requested by the first device, and based on this, the first device determines the size of the time-domain resource of the first transmission resource according to Td.

[0309] This application does not limit the specific implementation of the second device indicating Td. As one possible implementation, the second device indicates Td through any of the following information: A-IoT paging message, access trigger message, R2D control information, periodic broadcast message, synchronization signal, or CFO calibration signal.

[0310] For example, the first device caches information #A in periodic broadcast messages and determines Td based on information #A.

[0311] (3) The first device determines the size of the first transmission resource based on the predefined information and the instructions of the second device.

[0312] One possible implementation involves the protocol predefining the size of the first request's information, and the second device indicating the encoding and modulation schemes of the first request. Based on this, the first device determines the size of the time-domain resources of the first transmission resource according to the predefined information and the instructions from the second device.

[0313] This application does not limit the specific content of the first request in its embodiments. As one possible implementation, the first request may include one or more of the following: message type information, specific sequence information, information of the first device, information of the second device, and priority information.

[0314] (1) Message type information is used to indicate that the information in the D2R transmission is a first request.

[0315] This application does not limit the specific indication method of message type information in its embodiments. As one possible implementation, message type information is indicated using R bits, where R is an integer greater than and / or equal to 1.

[0316] For example, R=1, the bit value "1" indicates that the message type in the D2R transmission is a first request. As another example, R=2, the bit value is a specific value indicating that the message type in the D2R transmission is a first request.

[0317] In some possible implementations, message type information is carried in physical layer signaling or higher layer signaling.

[0318] In some possible implementations, message type information is also used to characterize the priority of the first request. For example, a bit value of "1" indicates that the information in the D2R transmission is the first request, and the priority of the first request is higher than the DO-A service of the first device or other D2R information of the first device.

[0319] In some possible implementations, message type information is also used to characterize the priority of the first request. For example, a bit value of "1" indicates that the information in the D2R transmission is the first request, and the first transmission resource is a dedicated resource for the first request, meaning that the first transmission resource cannot be used to transmit DO-A services of the first device or D2R information of other first devices.

[0320] (2) Specific sequence information is used to request OD broadcast messages. As one possible implementation, the specific sequence information is an m-sequence of length S, or a Golay sequence, or a Walsh sequence, or a Gold sequence, or a sequence information predefined by the protocol. Wherein, S is an integer greater than and / or equal to 1.

[0321] For example, specific sequence information distinguishes the m-sequence from Rel-19 in terms of length and / or content.

[0322] For example, the protocol predefines specific sequence information as "10101010".

[0323] (3) The information of the first device is used to identify the first device.

[0324] One possible implementation is that the information of the first device is determined based on the identification information of the first device and / or the RN16 corresponding to the first device.

[0325] For example, the information of the first device is part or all of the ID information / electronic product code (EPC) that comes with the first device from the factory.

[0326] For example, the information of the first device is RN16 sent by the first device in Msg1.

[0327] (4) The information of the second device is used to identify the second device.

[0328] One possible implementation is that the information of the second device is determined based on the random bits corresponding to the second device and / or the cell identifier corresponding to the second device.

[0329] For example, the information of the second device is bit information of length Z randomly generated by the second device, where Z is an integer greater than and / or equal to 1.

[0330] For example, the information of the second device is the same as the cell identifier corresponding to the second device.

[0331] The details regarding priority information can be found in the previous description and will not be repeated here.

[0332] This application does not limit the encoding method of the first request in its embodiments. As one possible implementation, the encoding method of the first request may be one or more of the following: forward error correction (FEC) encoding, cyclic redundancy check (CRC) encoding.

[0333] This application does not limit the specific implementation of the first device determining the encoding method of the first request in the embodiments. As one possible implementation, the first device determines the encoding method of the first request based on predefined information and / or instructions from the second device.

[0334] One possible implementation involves the protocol predefining one or more of the following: the coderate of the FEC encoding, the length of the CRC attachment, and the generator formula for the CRC attachment. Based on this, the first device can determine the encoding method of the first request according to the predefined information.

[0335] In another possible implementation, the second device indicates one or more of the following: the FEC encoding rate, the length of the CRC appendix, and the generator formula for the CRC appendix. Based on this, the first device can determine the encoding method of the first request according to the instructions of the second device.

[0336] This application does not limit the specific implementation of the encoding method for the second device to indicate the first request in the embodiments. As one possible implementation, the second device indicates the encoding method for the first request through any of the following information: A-IoT paging message, access trigger message, R2D control information, periodic broadcast message, synchronization signal, CFO calibration signal.

[0337] For example, the first device caches information #A in periodic broadcast messages and determines the encoding method of the first request based on information #A.

[0338] Another possible implementation is that the first device determines the encoding method of the first request based on predefined rules.

[0339] For example, the first device determines the encoding method of the first request based on cache information #1, wherein cache information #1 may be, for example, the encoding method of historical D2R information cached by the first device, or cache information #1 may be, for example, the encoding method of historical R2D information cached by the first device.

[0340] This application does not limit the modulation method of the first request in its embodiments. As one possible implementation, the modulation method of the first request is one or more of the following: on-off keying (OOK) modulation, binary phase-shift keying (BPSK) modulation, minimum shift keying (MSK) modulation, and differential binary phase-shift keying (DBPSK) modulation.

[0341] This application does not limit the specific implementation of the first device determining the modulation scheme of the first request. As one possible implementation, the first device determines the modulation scheme of the first request based on predefined information and / or instructions from the second device.

[0342] One possible implementation is that the protocol predefines one or more of the following: modulation scheme (e.g., OOK modulation), modulation order, information bits, and mapping of the modulated codewords. Based on this, the first device can determine the modulation scheme of the first request according to the predefined information.

[0343] In another possible implementation, the second device indicates one or more of the following: modulation scheme, modulation order, information bits, and mapping of the modulated codewords. Based on this, the first device can determine the modulation scheme requested in the first request according to the instructions of the second device.

[0344] This application does not limit the specific implementation of the modulation scheme indicated by the second device for the first request in the embodiments. As one possible implementation, the second device indicates the modulation scheme of the first request through any of the following information: A-IoT paging message, access trigger message, R2D control information, periodic broadcast message, synchronization signal, CFO calibration signal.

[0345] For example, the first device caches information #A in periodic broadcast messages and determines the modulation scheme of the first request based on information #A.

[0346] Another possible implementation is that the first device determines the modulation scheme of the first request based on predefined rules.

[0347] For example, the first device determines the modulation scheme of the first request based on cache information #2, wherein cache information #2 may be, for example, the modulation scheme of historical D2R information cached by the first device, or cache information #2 may be, for example, the modulation scheme of historical R2D information cached by the first device.

[0348] This application does not limit the specific content included in the OD broadcast message. As one possible implementation, the OD broadcast message includes one or more of the following: the cell identifier corresponding to the second device, the information of the second device, the information of the first device, the resource information of Msg1, the relevant information of L1 R2D control information, the D2R resource information for DO-A transmission, the power control information, the relevant information of R2D signal, and the relevant information of R2D transmission mechanism.

[0349] (1) The resource information of Msg1 includes one or more of the following: the number of resources of Msg1 in the time domain, information related to the time domain resources of Msg1, the number of resources of Msg1 in the frequency domain, and information related to the frequency domain resources of Msg1.

[0350] The information related to Msg1 time-domain resources includes one or more of the following: the start position of the time-domain resource, the duration of the time-domain resource, the end position of the time-domain resource, and the transmission period of Msg1.

[0351] The Msg1 frequency domain resource-related information includes one or more of the following: channel bandwidth, start position of frequency domain resource, end position of frequency domain resource, guard band size, frequency offset, center frequency point, etc.

[0352] (2) Information related to L1 R2D control information, such as chip duration of L1 R2D control information and information related to L1 R2D control resources.

[0353] (3) D2R resource information used for DO-A transmission includes time-domain resources and / or frequency-domain resources.

[0354] Among them, the D2R time-domain resources of DO-A include one or more of the following: the number of resources in the time domain, the start position of the time-domain resources, the duration of the time-domain resources, the end position of the time-domain resources, the period of D2R transmission, etc.

[0355] Among them, the D2R frequency domain resources of DO-A include one or more of the following: the number of resources in the frequency domain, the size of the channel bandwidth, the start position of the frequency domain resources, the end position of the frequency domain resources, the size of the guard band, the frequency domain offset, the center frequency point, etc.

[0356] (4) Power control information, such as R2D transmission power or D2R target transmission power.

[0357] (5) Relevant information of R2D signal includes one or more of the following: the format of synchronization signal, the period of synchronization signal, the period format of CFO calibration signal, information related to transmission mechanism, etc.

[0358] (6) Information related to the transmission mechanism of R2D transmission, such as the FEC bit rate, number of repeated transmissions, modulation method, encoding method, etc.

[0359] This application does not limit the information included in the OD broadcast message. As one possible implementation, the information included in the OD broadcast message is part or all of the same as the information carried by the periodic broadcast message.

[0360] In summary, the first device can receive R2D control information based on the OD broadcast message, or it can receive relevant R2D data based on the OD broadcast message, or it can obtain updated synchronization information in a timely manner based on the OD broadcast message. This improves the communication performance of the first device while reducing the power consumption and latency of the first device receiving broadcast messages.

[0361] The above text combined Figures 1 to 11 The method embodiments of this application are described in detail below, in conjunction with... Figures 12 to 14 The present application provides a detailed description of the apparatus embodiments. 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 found in the foregoing method embodiments.

[0362] Figure 12 This is a schematic diagram of a communication device according to an embodiment of this application. Figure 12 The communication device 1200 shown is the first device, and the communication device 1200 includes a transmitting unit 1210.

[0363] The sending unit 1210 is configured to send a first request to the second device on the first transmission resource, wherein the first request is used to request a broadcast message.

[0364] In some implementations, the first transmission resource is determined based on one or more of the following: a pre-configured time-domain location, a pre-configured frequency-domain location, DO-A transmission resources, and D2R resources corresponding to other first devices.

[0365] In some implementations, the temporal location of the first transmission resource is determined based on the temporal location of the first signal sent by the second device.

[0366] In some implementations, the time-domain position of the first transmission resource is obtained by taking the time-domain position of the first signal as the starting position and then passing through a first time period.

[0367] In some implementations, the first time period is determined based on one or more of the following: the sampling frequency offset SFO of the first device, the time delay of the first device in processing the first signal, and the device type of the first device.

[0368] In some implementations, the first time period is based on the protocol agreement, and / or the first time period is configured by the second device.

[0369] In some implementations, the frequency domain location of the first transmission resource is determined based on one or more of the following: fixed frequency domain location information, and the frequency domain location of the received R2D message.

[0370] In some implementations, the frequency domain location of the first transmission resource is determined based on the frequency domain location of the first signal transmitted by the second device.

[0371] In some implementations, the frequency domain position of the first transmission resource is the frequency domain position of the first signal, or the frequency domain position of the first transmission resource is obtained by taking the frequency domain position of the first signal as the starting position and passing through the first frequency domain offset.

[0372] In some implementations, the first frequency domain offset is determined based on predefined information and / or configuration information sent by the second device.

[0373] In some implementations, the first signal includes a synchronization signal and / or a CFO calibration signal.

[0374] In some implementations, the time-domain location and / or frequency-domain location of the first transmission resource is determined based on the resources of the DO-A transmission.

[0375] In some implementations, the time-domain location of the first transmission resource is the time-domain location of the DO-A transmission, and / or, the frequency-domain location of the first transmission resource is the frequency-domain location of the DO-A transmission.

[0376] In some implementations, the resources of a DO-A transmission are the resources of the first DO-A transmission of the first device, and / or the resources of other DO-A transmissions.

[0377] In some implementations, the resources for DO-A transmission are configured based on one or more of the following messages: periodic broadcast messages, paging messages from the first device, and access trigger messages.

[0378] In some implementations, the resources used for DO-A transmissions are used to transmit one or more of the following: message 1 corresponding to the DO-A service, scheduling request message for the DO-A service, and data for the DO-A service.

[0379] In some implementations, the time-domain location and / or frequency-domain location of the first transmission resource is determined based on the D2R resources corresponding to other first devices.

[0380] In some implementations, the communication device 1200 further includes a receiving unit that monitors and / or receives R2D control information and / or R2D data sent by the second device to other first devices; the sending unit 1210 uses the D2R resources corresponding to the other first devices to send a first request.

[0381] In some implementations, the D2R resources corresponding to other first devices are determined after a second time period, starting with the resources of R2D control information and / or R2D data.

[0382] In some implementations, the second time period is determined based on one or more of the following: the sampling frequency offset SFO of the first device, the delay of the first device in processing R2D control information and / or R2D data of other first devices, and the device type of the first device.

[0383] In some implementations, the second time period is based on a protocol agreement, and / or the second time period is configured by the second device.

[0384] In some implementations, the first request carries priority information, which is used to determine the priority of the first request.

[0385] In some implementations, the first request may also carry one or more of the following: message type information, which indicates that the first request is for requesting a broadcast message; specific sequence information, which is for requesting a broadcast message; information of the first device; and information of the second device.

[0386] In some implementations, the size of the time-domain resource corresponding to the first transmission resource is determined based on one or more of the following: the message size corresponding to the first request, the encoding parameters corresponding to the first request, and the modulation parameters corresponding to the first request.

[0387] In some implementations, the size of the time-domain resource corresponding to the first transmission resource is determined based on predefined information and / or configuration information sent by the second device.

[0388] In some implementations, the encoding method for the first request includes FEC encoding and / or CRC encoding.

[0389] In some implementations, the modulation method of the first request includes one of the following: OOK modulation, BPSK modulation, MSK modulation, or DBPSK modulation.

[0390] Figure 13 This is a schematic diagram of a communication device according to an embodiment of this application. Figure 13 The communication device 1300 shown is a second device, and the communication device 1300 includes a receiving unit 1310.

[0391] The receiving unit 1310 is configured to receive a first request sent by the first device on the first transmission resource, wherein the first request is used to request a broadcast message.

[0392] In some implementations, the first transmission resource is determined based on one or more of the following: a pre-configured time-domain location, a pre-configured frequency-domain location, DO-A transmission resources, and D2R resources corresponding to other first devices.

[0393] In some implementations, the temporal location of the first transmission resource is determined based on the temporal location of the first signal sent by the second device.

[0394] In some implementations, the time-domain position of the first transmission resource is obtained by taking the time-domain position of the first signal as the starting position and then passing through a first time period.

[0395] In some implementations, the first time period is determined based on one or more of the following: the sampling frequency offset SFO of the first device, the time delay of the first device in processing the first signal, and the device type of the first device.

[0396] In some implementations, the first time period is based on the protocol agreement, and / or the first time period is configured by the second device.

[0397] In some implementations, the frequency domain location of the first transmission resource is determined based on one or more of the following: fixed frequency domain location information, and the frequency domain location of the received R2D message.

[0398] In some implementations, the frequency domain location of the first transmission resource is determined based on the frequency domain location of the first signal transmitted by the second device.

[0399] In some implementations, the frequency domain position of the first transmission resource is the frequency domain position of the first signal, or the frequency domain position of the first transmission resource is obtained by taking the frequency domain position of the first signal as the starting position and passing through the first frequency domain offset.

[0400] In some implementations, the first frequency domain offset is determined based on predefined information and / or configuration information sent by the second device.

[0401] In some implementations, the first signal includes a synchronization signal and / or a CFO calibration signal.

[0402] In some implementations, the time-domain location and / or frequency-domain location of the first transmission resource is determined based on the resources of the DO-A transmission.

[0403] In some implementations, the time-domain location of the first transmission resource is the time-domain location of the DO-A transmission, and / or, the frequency-domain location of the first transmission resource is the frequency-domain location of the DO-A transmission.

[0404] In some implementations, the resources of a DO-A transmission are the resources of the first DO-A transmission of the first device, and / or the resources of other DO-A transmissions.

[0405] In some implementations, the resources for DO-A transmission are configured based on one or more of the following messages: periodic broadcast messages, paging messages from the first device, and access trigger messages.

[0406] In some implementations, the resources used for DO-A transmissions are used to transmit one or more of the following: message 1 corresponding to the DO-A service, scheduling request message for the DO-A service, and data for the DO-A service.

[0407] In some implementations, the time-domain location and / or frequency-domain location of the first transmission resource is determined based on the D2R resources corresponding to other first devices.

[0408] In some implementations, the communication device 1300 further includes a transmitting unit that transmits R2D control information and / or R2D data to other first devices.

[0409] In some implementations, the D2R resources corresponding to other first devices are determined after a second time period, starting with the resources of R2D control information and / or R2D data.

[0410] In some implementations, the second time period is determined based on one or more of the following: the sampling frequency offset SFO of the first device, the delay of the first device in processing R2D control information and / or R2D data of other first devices, and the device type of the first device.

[0411] In some implementations, the second time period is based on a protocol agreement, and / or the second time period is configured by the second device.

[0412] In some implementations, the first request carries priority information, which is used to determine the priority of the first request.

[0413] In some implementations, the first request may also carry one or more of the following: message type information, which indicates that the first request is for requesting a broadcast message; specific sequence information, which is for requesting a broadcast message; information of the first device; and information of the second device.

[0414] In some implementations, the size of the time-domain resource corresponding to the first transmission resource is determined based on one or more of the following: the message size corresponding to the first request, the encoding parameters corresponding to the first request, and the modulation parameters corresponding to the first request.

[0415] In some implementations, the size of the time-domain resource corresponding to the first transmission resource is determined based on predefined information and / or configuration information sent by the second device.

[0416] In some implementations, the encoding method for the first request includes FEC encoding and / or CRC encoding.

[0417] In some implementations, the modulation method of the first request includes one of the following: OOK modulation, BPSK modulation, MSK modulation, or DBPSK modulation.

[0418] In an optional embodiment, the transmitting unit 1210 may be a transceiver 1430. The communication device 1200 may also include a processor 1410 and / or a memory 1420, specifically as follows: Figure 14 As shown.

[0419] In an optional embodiment, the receiving unit 1310 may be a transceiver 1430. The communication device 1300 may also include a processor 1410 and / or a memory 1420, specifically as follows: Figure 14 As shown.

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

[0421] Apparatus 1400 may include one or more processors 1410. The processor 1410 may support apparatus 1400 in implementing the methods described in the preceding method embodiments. The processor 1410 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.

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

[0423] The device 1400 may also include a transceiver 1430. The processor 1410 can communicate with other devices or chips via the transceiver 1430. For example, the processor 1410 can send and receive data with other devices or chips via the transceiver 1430.

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

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

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

[0427] 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.

[0428] 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.

[0429] 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.

[0430] 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.

[0431] 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 pre-specified in the protocol.

[0432] 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.

[0433] 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.

[0434] 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.

[0435] 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.

[0436] 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.

[0437] 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.

[0438] 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.

[0439] 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 method for wireless communication, characterized in that, include: The first device sends a first request to the second device on the first transmission resource, the first request being used to request a broadcast message.

2. The method as described in claim 1, characterized in that, The first transmission resource is determined based on one or more of the following: Pre-configured time-domain location; Pre-configured frequency domain location; Resources for automatically initiating DO-A service transmissions by the device; Other first devices correspond to device-to-reader (D2R) resources.

3. The method as described in claim 2, characterized in that, The time-domain location of the first transmission resource is determined based on the pre-configured time-domain location, including: the time-domain location of the first transmission resource is determined based on the time-domain location of the first signal sent by the second device.

4. The method as described in claim 3, characterized in that, The time-domain position of the first transmission resource is obtained after a first time period, starting from the time-domain position of the first signal.

5. The method as described in claim 4, characterized in that, The first time period is determined based on one or more of the following: The sampling frequency offset of the first device is SFO; The time delay of the first device in processing the first signal; The device type of the first device.

6. The method as described in claim 4 or 5, characterized in that, The first time period is based on the agreement, and / or the first time period is configured by the second device.

7. The method according to any one of claims 2-6, characterized in that, The frequency domain location of the first transmission resource is determined based on the pre-configured frequency domain location, including: The frequency domain location of the first transmission resource is determined based on one or more of the following: Fixed frequency domain location information; The frequency domain location of the received R2D message.

8. The method according to any one of claims 2-6, characterized in that, The frequency domain position of the first transmission resource is determined based on the pre-configured frequency domain position, including: the frequency domain position of the first transmission resource is determined based on the frequency domain position of the first signal sent by the second device.

9. The method as described in claim 8, characterized in that, The frequency domain location of the first transmission resource is the frequency domain location of the first signal, or The frequency domain position of the first transmission resource is obtained by taking the frequency domain position of the first signal as the starting position and passing through the first frequency domain offset.

10. The method as described in claim 9, characterized in that, The first frequency domain offset is determined based on predefined information and / or configuration information sent by the second device.

11. The method according to any one of claims 3-6, 8-10, characterized in that, The first signal includes a synchronization signal and / or a CFO calibration signal.

12. The method as described in claim 2, characterized in that, The time-domain location and / or frequency-domain location of the first transmission resource are determined based on the resources of the DO-A transmission.

13. The method as described in claim 12, characterized in that, The time-domain location of the first transmission resource is the time-domain location of the DO-A transmission, and / or The frequency domain location of the first transmission resource is the frequency domain location of the DO-A transmission.

14. The method as described in claim 12 or 13, characterized in that, The resources of the DO-A transmission are the resources of the first DO-A transmission of the first device, and / or the resources of other DO-A transmissions.

15. The method according to any one of claims 12-14, characterized in that, The resources for the DO-A transmission are configured based on one or more of the following messages: periodic broadcast messages, paging messages from the first device, and access trigger messages.

16. The method according to any one of claims 12-15, characterized in that, The resources used for DO-A transmission are used to transmit one or more of the following: message 1 corresponding to DO-A service, scheduling request message for DO-A service, and data of DO-A service.

17. The method as described in claim 2, characterized in that, The time-domain location and / or frequency-domain location of the first transmission resource are determined based on the D2R resources corresponding to the other first devices.

18. The method as described in claim 17, characterized in that, The first device sends a first request to the second device on the first transmission resource, including: The first device monitors and / or receives R2D control information and / or R2D data sent by the second device to the other first devices; The first device uses the D2R resources corresponding to the other first devices to send the first request.

19. The method as described in claim 18, characterized in that, The D2R resources corresponding to the other first devices are determined after a second time period, starting with the resources of the R2D control information and / or R2D data.

20. The method as described in claim 19, characterized in that, The second time period is determined based on one or more of the following: The SFO of the first device; The delay in the first device processing the R2D control information and / or R2D data of the other first devices; The device type of the first device.

21. The method as described in claim 19 or 20, characterized in that, The second time period is based on the agreement and / or the second time period is configured by the second device.

22. The method according to any one of claims 12-21, characterized in that, The first request carries priority information, which is used to determine the priority of the first request.

23. The method according to any one of claims 1-22, characterized in that, The first request also carries one or more of the following: Message type information, wherein the message type information is used to indicate the message type of the first request; Specific sequence information, which is used to request the broadcast message; Information about the first device; Information about the second device.

24. The method according to any one of claims 1-23, characterized in that, The size of the time-domain resource corresponding to the first transmission resource is determined based on one or more of the following: The message size corresponding to the first request; The encoding parameters corresponding to the first request; The modulation parameters corresponding to the first request.

25. The method according to any one of claims 1-24, characterized in that, The size of the time-domain resource corresponding to the first transmission resource is determined based on predefined information and / or the configuration information sent by the second device.

26. The method according to any one of claims 1-25, characterized in that, The encoding method of the first request includes forward error correction (FEC) encoding and / or cyclic redundancy check (CRC) encoding.

27. The method according to any one of claims 1-26, characterized in that, The modulation method requested in the first request includes one of the following: On-Off Keying (OOK) modulation, Binary Phase Shift Keying (BPSK) modulation, Minimum Frequency Shift Keying (MSK) modulation, and Differential Binary Phase Shift Keying (DBPSK) modulation.

28. A method for wireless communication, characterized in that, include: The second device receives a first request sent by the first device on the first transmission resource, the first request being used to request a broadcast message.

29. The method as described in claim 28, characterized in that, The first transmission resource is determined based on one or more of the following: Pre-configured time-domain location; Pre-configured frequency domain location; Resources transmitted via DO-A; Other D2R resources corresponding to the first device.

30. The method as described in claim 29, characterized in that, The time-domain location of the first transmission resource is determined based on the pre-configured time-domain location, including: the time-domain location of the first transmission resource is determined based on the time-domain location of the first signal sent by the second device.

31. The method as described in claim 30, characterized in that, The time-domain position of the first transmission resource is obtained after a first time period, starting from the time-domain position of the first signal.

32. The method as described in claim 31, characterized in that, The first time period is determined based on one or more of the following: The SFO of the first device; The time delay of the first device in processing the first signal; The device type of the first device.

33. The method as described in claim 31 or 32, characterized in that, The first time period is based on the agreement, and / or the first time period is configured by the second device.

34. The method according to any one of claims 29-33, characterized in that, The frequency domain location of the first transmission resource is determined based on the pre-configured frequency domain location, including: The frequency domain location of the first transmission resource is determined based on one or more of the following: Fixed frequency domain location information; The frequency domain location of the received R2D message.

35. The method according to any one of claims 29-33, characterized in that, The frequency domain position of the first transmission resource is determined based on the pre-configured frequency domain position, including: the frequency domain position of the first transmission resource is determined based on the frequency domain position of the first signal sent by the second device.

36. The method as described in claim 35, characterized in that, The frequency domain location of the first transmission resource is the frequency domain location of the first signal, or The frequency domain position of the first transmission resource is obtained by taking the frequency domain position of the first signal as the starting position and passing through the first frequency domain offset.

37. The method as described in claim 36, characterized in that, The first frequency domain offset is determined based on predefined information and / or configuration information sent by the second device.

38. The method according to any one of claims 30-33, 35-37, characterized in that, The first signal includes a synchronization signal and / or a CFO calibration signal.

39. The method as described in claim 29, characterized in that, The time-domain location and / or frequency-domain location of the first transmission resource are determined based on the resources of the DO-A transmission.

40. The method as described in claim 39, characterized in that, The time-domain location of the first transmission resource is the time-domain location of the DO-A transmission, and / or The frequency domain location of the first transmission resource is the frequency domain location of the DO-A transmission.

41. The method as described in claim 39 or 40, characterized in that, The resources of the DO-A transmission are the resources of the first DO-A transmission of the first device, and / or the resources of other DO-A transmissions.

42. The method according to any one of claims 39-41, characterized in that, The resources for the DO-A transmission are configured based on one or more of the following messages: periodic broadcast messages, paging messages from the first device, and access trigger messages.

43. The method according to any one of claims 39-42, characterized in that, The resources used for DO-A transmission are used to transmit one or more of the following: message 1 corresponding to DO-A service, scheduling request message for DO-A service, and data of DO-A service.

44. The method as described in claim 29, characterized in that, The time-domain location and / or frequency-domain location of the first transmission resource are determined based on the D2R resources corresponding to the other first devices.

45. The method as described in claim 44, characterized in that, The method further includes: The second device sends R2D control information and / or R2D data to the other first device.

46. ​​The method as described in claim 45, characterized in that, The D2R resources corresponding to the other first devices are determined after a second time period, starting with the resources of the R2D control information and / or R2D data.

47. The method as described in claim 46, characterized in that, The second time period is determined based on one or more of the following: The SFO of the first device; The delay in the first device processing the R2D control information and / or R2D data of the other first devices; The device type of the first device.

48. The method as described in claim 46 or 47, characterized in that, The second time period is based on the agreement and / or the second time period is configured by the second device.

49. The method according to any one of claims 39-48, characterized in that, The first request carries priority information, which is used to determine the priority of the first request.

50. The method according to any one of claims 28-49, characterized in that, The first request also carries one or more of the following: Message type information, wherein the message type information is used to indicate the message type of the first request; Specific sequence information, which is used to request the broadcast message; Information about the first device; Information about the second device.

51. The method according to any one of claims 28-50, characterized in that, The size of the time-domain resource corresponding to the first transmission resource is determined based on one or more of the following: The message size corresponding to the first request; The encoding parameters corresponding to the first request; The modulation parameters corresponding to the first request.

52. The method according to any one of claims 28-51, characterized in that, The size of the time-domain resource corresponding to the first transmission resource is determined based on predefined information and / or the configuration information sent by the second device.

53. The method according to any one of claims 28-52, characterized in that, The encoding method of the first request includes FEC encoding and / or CRC encoding.

54. The method according to any one of claims 28-53, characterized in that, The modulation method requested in the first request includes one of the following: OOK modulation, BPSK modulation, MSK modulation, and DBPSK modulation.

55. A communication device, characterized in that, The communication device is a first device, comprising: The sending unit is configured to send a first request to the second device on the first transmission resource, wherein the first request is used to request a broadcast message.

56. The communication device as claimed in claim 55, characterized in that, The first transmission resource is determined based on one or more of the following: Pre-configured time-domain location; Pre-configured frequency domain location; Resources transmitted via DO-A; Other D2R resources corresponding to the first device.

57. The communication device as claimed in claim 56, characterized in that, The time-domain location of the first transmission resource is determined based on the pre-configured time-domain location, including: the time-domain location of the first transmission resource is determined based on the time-domain location of the first signal sent by the second device.

58. The communication device as claimed in claim 57, characterized in that, The time-domain position of the first transmission resource is obtained after a first time period, starting from the time-domain position of the first signal.

59. The communication device as claimed in claim 58, characterized in that, The first time period is determined based on one or more of the following: The SFO of the first device; The time delay of the first device in processing the first signal; The device type of the first device.

60. The communication device as described in claim 58 or 59, characterized in that, The first time period is based on the agreement, and / or the first time period is configured by the second device.

61. The communication device according to any one of claims 56-60, characterized in that, The frequency domain location of the first transmission resource is determined based on the pre-configured frequency domain location, including: The frequency domain location of the first transmission resource is determined based on one or more of the following: Fixed frequency domain location information; The frequency domain location of the received R2D message.

62. The communication device according to any one of claims 56-60, characterized in that, The frequency domain position of the first transmission resource is determined based on the pre-configured frequency domain position, including: the frequency domain position of the first transmission resource is determined based on the frequency domain position of the first signal sent by the second device.

63. The communication device as claimed in claim 62, characterized in that, The frequency domain location of the first transmission resource is the frequency domain location of the first signal, or The frequency domain position of the first transmission resource is obtained by taking the frequency domain position of the first signal as the starting position and passing through the first frequency domain offset.

64. The communication device as claimed in claim 63, characterized in that, The first frequency domain offset is determined based on predefined information and / or configuration information sent by the second device.

65. The communication device according to any one of claims 57-60, 62-64, characterized in that, The first signal includes a synchronization signal and / or a CFO calibration signal.

66. The communication device as claimed in claim 56, characterized in that, The time-domain location and / or frequency-domain location of the first transmission resource are determined based on the resources of the DO-A transmission.

67. The communication device as claimed in claim 66, characterized in that, The time-domain location of the first transmission resource is the time-domain location of the DO-A transmission, and / or The frequency domain location of the first transmission resource is the frequency domain location of the DO-A transmission.

68. The communication device as claimed in claim 66 or 67, characterized in that, The resources of the DO-A transmission are the resources of the first DO-A transmission of the first device, and / or the resources of other DO-A transmissions.

69. The communication device as claimed in any one of claims 66-68, characterized in that, The resources for the DO-A transmission are configured based on one or more of the following messages: periodic broadcast messages, paging messages from the first device, and access trigger messages.

70. The communication device as described in any one of claims 66-69, characterized in that, The resources used for DO-A transmission are used to transmit one or more of the following: message 1 corresponding to DO-A service, scheduling request message for DO-A service, and data of DO-A service.

71. The communication device as claimed in claim 56, characterized in that, The time-domain location and / or frequency-domain location of the first transmission resource are determined based on the D2R resources corresponding to the other first devices.

72. The communication device as claimed in claim 71, characterized in that, The communication device further includes: The receiving unit is used to monitor and / or receive R2D control information and / or R2D data sent by the second device to the other first device; The sending unit uses the D2R resources corresponding to the other first device to send the first request.

73. The communication device as claimed in claim 72, characterized in that, The D2R resources corresponding to the other first devices are determined after a second time period, starting with the resources of the R2D control information and / or R2D data.

74. The communication device as claimed in claim 73, characterized in that, The second time period is determined based on one or more of the following: The SFO of the first device; The delay in the first device processing the R2D control information and / or R2D data of the other first devices; The device type of the first device.

75. The communication device as claimed in claim 73 or 74, characterized in that, The second time period is based on the agreement and / or the second time period is configured by the second device.

76. The communication device according to any one of claims 66-75, characterized in that, The first request carries priority information, which is used to determine the priority of the first request.

77. The communication device as described in any one of claims 55-76, characterized in that, The first request also carries one or more of the following: Message type information, wherein the message type information is used to indicate the message type of the first request; Specific sequence information, which is used to request the broadcast message; Information about the first device; Information about the second device.

78. The communication device as described in any one of claims 55-77, characterized in that, The size of the time-domain resource corresponding to the first transmission resource is determined based on one or more of the following: The message size corresponding to the first request; The encoding parameters corresponding to the first request; The modulation parameters corresponding to the first request.

79. The communication device as described in any one of claims 55-78, characterized in that, The size of the time-domain resource corresponding to the first transmission resource is determined based on predefined information and / or the configuration information sent by the second device.

80. The communication device according to any one of claims 55-79, characterized in that, The encoding method of the first request includes FEC encoding and / or CRC encoding.

81. The communication device according to any one of claims 55-80, characterized in that, The modulation method requested in the first request includes one of the following: OOK modulation, BPSK modulation, MSK modulation, and DBPSK modulation.

82. A communication device, characterized in that, The communication device is a second device, comprising: The receiving unit is configured to receive a first request sent by a first device on a first transmission resource, wherein the first request is used to request a broadcast message.

83. The communication device as claimed in claim 82, characterized in that, The first transmission resource is determined based on one or more of the following: Pre-configured time-domain location; Pre-configured frequency domain location; Resources transmitted via DO-A; Other D2R resources corresponding to the first device.

84. The communication device as claimed in claim 83, characterized in that, The time-domain location of the first transmission resource is determined based on the pre-configured time-domain location, including: the time-domain location of the first transmission resource is determined based on the time-domain location of the first signal sent by the second device.

85. The communication device as claimed in claim 84, characterized in that, The time-domain position of the first transmission resource is obtained after a first time period, starting from the time-domain position of the first signal.

86. The communication device as claimed in claim 85, characterized in that, The first time period is determined based on one or more of the following: The SFO of the first device; The time delay of the first device in processing the first signal; The device type of the first device.

87. The communication device as described in claim 85 or 86, characterized in that, The first time period is based on the agreement, and / or the first time period is configured by the second device.

88. The communication device as claimed in any one of claims 83-87, characterized in that, The frequency domain location of the first transmission resource is determined based on the pre-configured frequency domain location, including: The frequency domain location of the first transmission resource is determined based on one or more of the following: Fixed frequency domain location information; The frequency domain location of the received R2D message.

89. The communication device as described in any one of claims 83-87, characterized in that, The frequency domain position of the first transmission resource is determined based on the pre-configured frequency domain position, including: the frequency domain position of the first transmission resource is determined based on the frequency domain position of the first signal sent by the second device.

90. The communication device as claimed in claim 89, characterized in that, The frequency domain location of the first transmission resource is the frequency domain location of the first signal, or The frequency domain position of the first transmission resource is obtained by taking the frequency domain position of the first signal as the starting position and passing through the first frequency domain offset.

91. The communication device as claimed in claim 90, characterized in that, The first frequency domain offset is determined based on predefined information and / or configuration information sent by the second device.

92. The communication device as described in any one of claims 84-87, 88-91, characterized in that, The first signal includes a synchronization signal and / or a CFO calibration signal.

93. The communication device as claimed in claim 83, characterized in that, The time-domain location and / or frequency-domain location of the first transmission resource are determined based on the resources of the DO-A transmission.

94. The communication device as claimed in claim 93, characterized in that, The time-domain location of the first transmission resource is the time-domain location of the DO-A transmission, and / or The frequency domain location of the first transmission resource is the frequency domain location of the DO-A transmission.

95. The communication device as described in claim 93 or 94, characterized in that, The resources of the DO-A transmission are the resources of the first DO-A transmission of the first device, and / or the resources of other DO-A transmissions.

96. The communication device as described in any one of claims 93-95, characterized in that, The resources for the DO-A transmission are configured based on one or more of the following messages: periodic broadcast messages, paging messages from the first device, and access trigger messages.

97. The communication device as described in any one of claims 93-96, characterized in that, The resources used for DO-A transmission are used to transmit one or more of the following: message 1 corresponding to DO-A service, scheduling request message for DO-A service, and data of DO-A service.

98. The communication device as claimed in claim 83, characterized in that, The time-domain location and / or frequency-domain location of the first transmission resource are determined based on the D2R resources corresponding to the other first devices.

99. The communication device as claimed in claim 44, characterized in that, The communication device further includes: The transmitting unit is used to transmit R2D control information and / or R2D data to the other first devices.

100. The communication device as claimed in claim 99, characterized in that, The D2R resources corresponding to the other first devices are determined after a second time period, starting with the resources of the R2D control information and / or R2D data.

101. The communication device as claimed in claim 100, characterized in that, The second time period is determined based on one or more of the following: The sampling frequency offset of the first device is SFO; The delay in the first device processing the R2D control information and / or R2D data of the other first devices; The device type of the first device.

102. The communication device as claimed in claim 100 or 101, characterized in that, The second time period is based on the agreement and / or the second time period is configured by the second device.

103. The communication device as described in any one of claims 93-102, characterized in that, The first request carries priority information, which is used to determine the priority of the first request.

104. The communication device according to any one of claims 82-103, characterized in that, The first request also carries one or more of the following: Message type information, wherein the message type information is used to indicate the message type of the first request; Specific sequence information, which is used to request the broadcast message; Information about the first device; Information about the second device.

105. The communication device as described in any one of claims 82-104, characterized in that, The size of the time-domain resource corresponding to the first transmission resource is determined based on one or more of the following: The message size corresponding to the first request; The encoding parameters corresponding to the first request; The modulation parameters corresponding to the first request.

106. The communication device as described in any one of claims 82-105, characterized in that, The size of the time-domain resource corresponding to the first transmission resource is determined based on predefined information and / or the configuration information sent by the second device.

107. The communication device as described in any one of claims 82-106, characterized in that, The encoding method of the first request includes FEC encoding and / or CRC encoding.

108. The communication device as claimed in any one of claims 82-107, characterized in that, The modulation method requested in the first request includes one of the following: OOK modulation, BPSK modulation, MSK modulation, and DBPSK modulation.

109. A communication device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor calls and runs the program in the memory and controls the transceiver to receive or send signals, so as to cause the communication device to perform the method as described in any one of claims 1-27; or to cause the communication device to perform the method as described in any one of claims 28-54.

110. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the device to perform the method as claimed in any one of claims 1-27; or to cause the device to perform the method as claimed in any one of claims 28-54.

111. A chip, characterized in that, Includes a processor for calling a program from memory to cause a device having the chip mounted to perform the method as claimed in any one of claims 1-27; or, to cause a device having the chip mounted to perform the method as claimed in any one of claims 28-54.

112. 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-27; or, the program causes a computer to perform the method as described in any one of claims 28-54.

113. A computer program product, characterized in that, The method includes a program that causes a computer to perform the method as described in any one of claims 1-27; or, the program causes a computer to perform the method as described in any one of claims 28-54.

114. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1-27; or, the computer program causes the computer to perform the method as described in any one of claims 28-54.

Images