Communication apparatus and communication method

Abstract

A communication apparatus is provided with: a transmission unit that transmits, to an environmental IoT device, at least one of a first DL signal including at least one of control information and data, and a second DL signal used by the environmental IoT device in backscattering, the environmental IoT device being an environmental Internet of Things device, and the environmental IoT device being configured to transmit the first DL signal and / or the second DL signal to the environmental IoT device; the first DL signal refers to a first downlink signal; and a reception unit that receives, as an uplink signal, the second DL signal backscattered by the environmental IoT device.

Description

Technical Field

[0001] This invention relates to communication devices and communication methods in wireless communication systems. Background Technology

[0002] In NR (New Radio) (also known as "5G"), which is the successor system to LTE (Long Term Evolution), technologies are being researched to meet the requirements of high-capacity systems, high-speed data transmission, low latency, simultaneous connection of multiple terminals, low cost, and power saving (e.g., Non-Patent Literature 1).

[0003] Additionally, 3GPP (registered trademark) Release 18 is researching Ambient Internet of Things (A-IoT) (e.g., non-patent document 2). Ambient IoT aims to develop devices with extremely simple structures for low-end IoT applications that operate with minimal power consumption.

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent document 1: 3GPP TS 38.300 V17.3.0 (2022-12)

[0007] Non-patent literature 2: “New SID: Study on Ambient IoT”, RP-222685, 3GPP TSG RANMeeting #97-e, September 2022

[0008] Non-patent document 3: 3GPP TR 38.848 V0.1.0 (2023-03) Summary of the Invention

[0009] The problem that the invention aims to solve

[0010] Because devices with extremely simple structures are envisioned to support IoT environments, it is necessary to define a new type of signal that is different from the OFDM (Orthogonal Frequency Division Multiplexing) signal in existing NR.

[0011] The present invention was made in view of the above-mentioned problems, and its object is to generate signals suitable for Ambient Internet of Things (IoT) in a wireless communication system.

[0012] Methods for solving problems

[0013] According to the disclosed technology, a communication device is provided, wherein the communication device comprises: a transmitting unit that transmits to an environmental IoT (Internet of Things) device at least one of a first DL (Downlink) signal containing at least one of control information and data, and at least one of a second DL signal used by the environmental IoT device in backscattering; and a receiving unit that receives the second DL signal backscattered by the environmental IoT device as an UL (Uplink) signal.

[0014] Invention Effects

[0015] According to publicly available technology, signals suitable for Ambient Internet of Things (IoT) can be generated in wireless communication systems. Attached Figure Description

[0016] Figure 1 This is a diagram illustrating an example of the structure of a wireless communication system.

[0017] Figure 2 This is a diagram illustrating an example (1) of the topology of an embodiment of the present invention.

[0018] Figure 3 This is a diagram illustrating an example (2) of the topology of an embodiment of the present invention.

[0019] Figure 4 This is a diagram illustrating an example (3) of the topology of an embodiment of the present invention.

[0020] Figure 5 This is a diagram illustrating an example (4) of the topology of an embodiment of the present invention.

[0021] Figure 6 This is a diagram illustrating an example (5) of the topology of an embodiment of the present invention.

[0022] Figure 7 This is a diagram illustrating an example of backscatter communication according to an embodiment of the present invention.

[0023] Figure 8 This is a diagram illustrating an example (1) of communication according to an embodiment of the present invention.

[0024] Figure 9 This is a diagram illustrating an example (1) of resource allocation in an embodiment of the present invention.

[0025] Figure 10 This is a diagram illustrating an example (2) of communication according to an embodiment of the present invention.

[0026] Figure 11 This is a diagram illustrating an example (2) of resource allocation in an embodiment of the present invention.

[0027] Figure 12 This is a diagram illustrating an example (3-1) of communication according to an embodiment of the present invention.

[0028] Figure 13 This is a diagram illustrating an example (3-2) of communication according to an embodiment of the present invention.

[0029] Figure 14 This is a diagram illustrating an example (3) of resource allocation in an embodiment of the present invention.

[0030] Figure 15 This is a diagram illustrating resource allocation in intermediate nodes according to an embodiment of the present invention.

[0031] Figure 16 This is a timing diagram for illustrating example (1) of signal forwarding in an embodiment of the present invention.

[0032] Figure 17 This is a timing diagram for illustrating example (2) of signal forwarding in an embodiment of the present invention.

[0033] Figure 18 This is a timing diagram for illustrating example (3) of signal forwarding in an embodiment of the present invention.

[0034] Figure 19 This is a timing diagram for illustrating example (4) of signal forwarding in an embodiment of the present invention.

[0035] Figure 20 This is a timing diagram for illustrating example (5) of signal forwarding in an embodiment of the present invention.

[0036] Figure 21 This is a diagram illustrating an example (1) of the timing of signal forwarding according to an embodiment of the present invention.

[0037] Figure 22 This is a diagram illustrating an example (2) of the timing of signal forwarding according to an embodiment of the present invention.

[0038] Figure 23 This is a diagram illustrating an example (3) of the timing of signal forwarding according to an embodiment of the present invention.

[0039] Figure 24 This is a diagram illustrating an example (4) of the timing of signal forwarding according to an embodiment of the present invention.

[0040] Figure 25 This is a diagram illustrating an example (5) of the timing of signal forwarding according to an embodiment of the present invention.

[0041] Figure 26This is a diagram illustrating an example (6) of the timing of signal forwarding according to an embodiment of the present invention.

[0042] Figure 27 This is a diagram illustrating an example (7) of the timing of signal forwarding according to an embodiment of the present invention.

[0043] Figure 28 This is a diagram illustrating an example (8) of the timing of signal forwarding according to an embodiment of the present invention.

[0044] Figure 29 This is a diagram illustrating an example (9) of the timing of signal forwarding according to an embodiment of the present invention.

[0045] Figure 30 This is a diagram illustrating an example (10) of the timing of signal forwarding according to an embodiment of the present invention.

[0046] Figure 31 This is a diagram illustrating an example (11) of the timing of signal forwarding according to an embodiment of the present invention.

[0047] Figure 32 This is a diagram illustrating an example (12) of the timing of signal forwarding according to an embodiment of the present invention.

[0048] Figure 33 This is a diagram illustrating an example (13) of the timing of signal forwarding according to an embodiment of the present invention.

[0049] Figure 34 This is a diagram illustrating an example (14) of the timing of signal forwarding according to an embodiment of the present invention.

[0050] Figure 35 This is a diagram illustrating an example of the functional structure of a base station 10 according to an embodiment of the present invention.

[0051] Figure 36 This is a diagram illustrating an example of the functional structure of terminal 20 according to an embodiment of the present invention.

[0052] Figure 37 This is a diagram illustrating an example of the hardware structure of a base station 10 or terminal 20 according to an embodiment of the present invention.

[0053] Figure 38 This is a diagram illustrating an example of the structure of a vehicle 2001 according to an embodiment of the present invention. Detailed Implementation

[0054] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. Furthermore, the embodiments described below are merely examples, and the application of the present invention is not limited to the embodiments described below.

[0055] In the operation of the wireless communication system according to embodiments of the present invention, existing technologies are appropriately used. These existing technologies include, for example, existing LTE, but are not limited to, existing LTE. Furthermore, unless otherwise stated, the term "LTE" as used in this specification has a broad meaning that includes LTE-Advanced and subsequent methods (e.g., NR).

[0056] Furthermore, in the embodiments of the present invention described below, the terms SS (Synchronization Signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel) used in existing LTE systems are used. These are for ease of description, and the same signals and functions may also be referred to by other names. In addition, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily explicitly written as "NR-".

[0057] Furthermore, in embodiments of the present invention, the duplex mode can be TDD (Time Division Duplex), FDD (Frequency Division Duplex), or other modes (e.g., Flexible Duplex).

[0058] Furthermore, in embodiments of the present invention, the “configure” wireless parameters can be pre-configured predetermined values ​​or wireless parameters notified from the base station 10 or the terminal 20.

[0059] Figure 1This is a diagram illustrating a structural example (1) of a wireless communication system according to an embodiment of the present invention. Figure 1 As shown, the wireless communication system in this embodiment of the invention includes a base station 10 and a terminal 20. Figure 1 The image shows one base station 10 and one terminal 20, but this is just an example and there can be multiple terminals.

[0060] Base station 10 is a communication device that provides one or more cells and communicates wirelessly with terminal 20. The physical resources of the wireless signal are defined in the time and frequency domains. The time domain can be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain can be defined by the number of subcarriers or resource blocks. Base station 10 sends synchronization signals and system information to terminal 20. Synchronization signals are, for example, NR-PSS and NR-SSS. System information is transmitted, for example, via NR-PBCH, also known as broadcast information. Synchronization signals and system information can also be referred to as SSB (SS / PBCH block). Figure 1 As shown, base station 10 sends control signals or data to terminal 20 via DL (Downlink) and receives control signals or data from terminal 20 via UL (Uplink). Both base station 10 and terminal 20 are capable of beamforming for signal transmission and reception. Furthermore, both base station 10 and terminal 20 can apply MIMO (Multiple Input Multiple Output) based communication to DL or UL. Additionally, base station 10 and terminal 20 can also communicate via CA (Carrier Aggregation) based secondary cells (SCell) and primary cells (PCell). Moreover, terminal 20 can also communicate via DC (Dual Connectivity) based primary cells of base station 10 and primary / secondary cells of other base stations 10 (PSCell).

[0061] Terminal 20 is a communication device with wireless communication capabilities, such as a smartphone, mobile phone, tablet computer, wearable terminal, or M2M (Machine-to-Machine) communication module. Figure 1As shown, terminal 20 receives control signals or data from base station 10 via DL and transmits control signals or data to base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. Furthermore, terminal 20 receives various reference signals transmitted from base station 10 and performs propagation path quality measurements based on the reception results of these reference signals.

[0062] Terminal 20 is capable of carrier aggregation, which bundles multiple cells (multiple CCs (Component Carriers)) to communicate with base station 10. In carrier aggregation, one PCell (Primary cell) and one or more SCells (Secondary cells) are used. Alternatively, a PUCCH-SCell with a PUCCH can also be used.

[0063] Here, we are researching Ambient Internet of Things (e.g., non-patent literature 2). In Ambient Internet of Things, the goal is to develop devices with extremely simple structures for the lowest-end IoT applications that operate with minimal power consumption.

[0064] For example, environmental IoT can be studied for scenarios and characteristics with the following configurations.

[0065] 1) Indoor or outdoor environment.

[0066] 2) Types of base stations. For example, configurations based on macro cells, micro cells, or pico cells.

[0067] 3) Topology related to connectivity. For example, which nodes, such as base stations, UEs, relays, and repeaters, communicate with the environmental IoT devices.

[0068] 4) TDD or FDD, whether the frequency band is a licensed band or an unlicensed band.

[0069] 5) Coexistence of UEs and network devices in existing 3GPP technology frequency bands.

[0070] 6) Envision services that originate from and / or reach the device.

[0071] The configuration scenarios for the relevant use cases and the RAN design goals based on the above characteristics can at least include the following viewpoints.

[0072] 1) Power consumption

[0073] 2) Complexity

[0074] 3) Coverage area

[0075] 4) Data rate

[0076] 5) Position measurement accuracy

[0077] It is also possible to compare and study the feasibility of RAN design goals for use cases based on appropriate configuration scenarios, and clarify the envisioned required functions to be supported.

[0078] For example, the following types of devices can be envisioned for environmental IoT.

[0079] Device A does not have an energy storage device and cannot independently generate or amplify signals. It is capable of backscattering transmission.

[0080] Device B has an energy storage device and cannot generate signals independently. It can use the electrical energy transmitted and stored via backscattering to amplify the reflected signal.

[0081] Device C has an energy storage device that can independently generate signals. That is, it has an active RF component oriented towards transmission.

[0082] In addition, regarding the complexity of device A, consider the level of RFID.

[0083] For example, a network topology like the one described below can also be envisioned as an environment-oriented IoT (see Non-Patent Document 3).

[0084] Topology 1 is the structure for communication between the BS and environmental IoT devices. The environmental IoT devices communicate directly with the base station in the transmission direction. Figure 2 This is a diagram illustrating an example (1) of the topology of an embodiment of the present invention. Figure 2 An example of topology 1 is shown.

[0085] Topology 2 is a structure where the BS and environmental IoT devices communicate via an intermediate node. The environmental IoT devices communicate bidirectionally with the intermediate node configured between the base station and the environmental IoT devices. The intermediate node can be, for example, a repeater, an IAB (Integrated Access and Backhaul) node, a UE, a repeater, etc. Figure 3 This is a diagram illustrating an example (2) of the topology of an embodiment of the present invention. Figure 3 An example of topology 2 is shown.

[0086] Topology 3 includes communication between the BS and the assisting node, communication between the assisting node and the environmental IoT device, and communication between the environmental IoT device and the BS. The environmental IoT device sends data to the base station and receives data from the assisting node. Alternatively, the environmental IoT device receives data from the base station and sends it to the assisting node. The assisting node can be, for example, a repeater, an IAB node, a UE, a repeater, etc. Figure 4 This is a diagram illustrating an example (3) of the topology of an embodiment of the present invention. Figure 5 This is a diagram illustrating an example (4) of the topology of an embodiment of the present invention. Figure 4 Topology 3 shows an example of DL-assisted topology. Figure 5 Topology 3 shows an example of UL-assisted topology.

[0087] Topology 4 is the structure for communication between the UE and the environmental IoT devices. The environmental IoT devices communicate bidirectionally with the UE. Figure 6 This is a diagram illustrating an example (5) of the topology of an embodiment of the present invention. Figure 6 An example of topology 4 is shown.

[0088] Figure 7 This diagram illustrates an example of backscatter communication according to an embodiment of the present invention. A base station, intermediate node, auxiliary node, or other node transmits RF signals to an environmental IoT device. The environmental IoT device is activated and receives power from the RF application field of the base station, intermediate node, auxiliary node, or other node via inductive coupling. The environmental IoT device backscatters and modulates the RF signals received from the base station, intermediate node, auxiliary node, or other node by switching the reflection coefficient of its antenna, thereby transmitting information to the base station, intermediate node, auxiliary node, or other node. Figure 7 This is an example of an environmental IoT device performing ON-OFF keying and sending information. Figure 7 The area shown by the dashed line is the OFF interval.

[0089] Regarding RFID in the 860MHz-960MHz range, the reader in an RFID system is equivalent to a base station, intermediate node, or auxiliary node in an environmental IoT system. The tag is equivalent to an environmental IoT device. The RF signal from the reader to the tag is typically a sine wave with a predetermined frequency. The DL information from the reader to the tag uses ASK (Amplitude Shift Keying) modulation. Additionally, the DL information from the reader to the tag uses PIE (Pulse Interval Encoding). For UL backscattering, ASK and / or PSK (Phase Shift Keying) modulation is used. Furthermore, in UL backscattering, FMO encoding and Miller encoding are used.

[0090] Because devices with extremely simple structures are envisioned to support environmental IoT, it is necessary to define a new type of signal, different from the existing OFDM (Orthogonal Frequency Division Multiplexing) signal in NR, used in communication between base stations, intermediate nodes, auxiliary nodes, or other nodes and environmental IoT devices. Furthermore, the resource allocation between this new signal and existing NR signals is proposed in the following description.

[0091] New types of DL signals can also be defined for devices A and / or B, sent from base stations, intermediate nodes, auxiliary nodes, or other nodes as shown below, to environmental IoT devices.

[0092] DL Type A (DL type A: Downlink Type A) signal: An RF signal carrying DL control information and / or data. Imagine an environment where IoT devices decode this RF signal to obtain DL control information and / or data.

[0093] DL type B signal: An RF signal used for backscattering in environmental IoT devices. A base station, intermediate node, auxiliary node, or other node transmits a DL type B signal to the environmental IoT device. The environmental IoT device then backscatters and modulates the DL type B signal received from the base station, intermediate node, auxiliary node, or other node by switching the reflection coefficient of its own antenna, thereby transmitting information to the base station, intermediate node, auxiliary node, or other node.

[0094] DL Type C signal: The RF signal that serves as the power source for environmental IoT devices. Environmental IoT devices obtain power from the DL Type C signal. This power is used for DL ​​decoding and UL backscattering. Device B stores this power.

[0095] UL signals sent from IoT devices in the following environments to base stations, intermediate nodes, or auxiliary nodes can also be defined for devices A and / or B.

[0096] UL Type X: A backscattered signal carrying UL control information and / or data. Environmental IoT devices backscatter the aforementioned DL Type B signal.

[0097] It is also possible to define new DL signals sent from the base station, intermediate node, auxiliary node or other nodes shown below to the environmental IoT device for device C.

[0098] DL type D signal: RF signal carrying DL control information and / or data.

[0099] DL Type E Signal: An RF signal that serves as the power source for environmental IoT devices. Device C obtains power from the DL Type E signal. This power is used for DL ​​decoding and UL backscattering. Device C stores this power.

[0100] UL signals can be defined for device C from IoT devices in the following environments to base stations, intermediate nodes, or auxiliary nodes.

[0101] UL type Y signal: RF signal carrying UL control information and / or data.

[0102] Additionally, in this embodiment of the invention, the intermediate or auxiliary node can be a UE, a repeater, an IAB, or a transponder. Other nodes can be base stations, UEs, or any other type of wireless node configured within or outside the topology.

[0103] Furthermore, in embodiments of the present invention, "DL" refers to a transmission from a base station, UE, repeater, IAB, transponder, or other node to an environmental IoT device. Additionally, "UL" refers to a transmission from an environmental IoT device to a base station, UE, repeater, IAB, or transponder.

[0104] The following relationship can also be applied to DL type A signals and DL type B signals.

[0105] 1) DL type A signals and / or DL ​​type B signals can use the same signal generation method or the same waveform. DL type A signals carry DL control information and / or data. On the other hand, DL type B signals are not modulated.

[0106] 2) DL type A signals and / or DL ​​type B signals can use different signal generation methods or different waveforms.

[0107] The following relationship can also be applied to DL type A signals and DL type C signals.

[0108] 1) In addition to transmitting DL control information and / or data, DL type A signals can also be used as a power source. In this case, DL type A signals can also be a type of DL type C signal.

[0109] 2) DL type C signal can be a different type of signal independent of DL type A signal.

[0110] 2-1) DL type A signals and / or DL ​​type C signals can use the same signal generation method or the same waveform. DL type A signals carry DL control information and / or data. On the other hand, DL type C signals are not modulated.

[0111] 2-2) DL type A signals and / or DL ​​type C signals can use different signal generation methods or different waveforms.

[0112] The following relationship can also be found between DL type B signals and DL type C signals.

[0113] 1) A DL type B signal can be used as a power source. In this case, a DL type B signal can also be a type of DL type C signal.

[0114] 2) DL type C signal can be a different type of signal independent of DL type B signal.

[0115] 2-1) DL type B signals and / or DL ​​type C signals can use the same signal generation method or the same waveform.

[0116] 2-2) DL type B signals and / or DL ​​type C signals can use different signal generation methods or different waveforms.

[0117] The following relationship can also be established between DL type D signals and DL type A signals.

[0118] 1) DL type D signals and / or DL ​​type A signals can use the same modulation method and / or the same signal generation method or the same waveform.

[0119] 2) DL type D signals and / or DL ​​type A signals can use different modulation methods and / or different signal generation methods or different waveforms.

[0120] The following relationship can also be established between DL type D signals and DL type E signals.

[0121] 1) In addition to transmitting DL control information and / or data, DL type D signals can also be used as a power source. In this case, a DL type D signal can also be a type of DL type E signal.

[0122] 2) DL type D signal can be a different type of signal independent of DL type E signal.

[0123] 2-1) DL type D signals and / or DL ​​type E signals can use the same signal generation method or the same waveform. DL type D signals carry DL control information and / or data. On the other hand, DL type E signals are not modulated.

[0124] 2-2) DL type D signals and / or DL ​​type E signals can use different signal generation methods or different waveforms.

[0125] The following relationship can also be established between DL type C signals and DL type E signals.

[0126] 1) DL type C signals and / or DL ​​type E signals can use the same modulation method and / or the same signal generation method or the same waveform.

[0127] 2) DL type C signals and / or DL ​​type E signals can use different modulation methods and / or different signal generation methods or different waveforms.

[0128] The following relationship exists between DL type A, B, C, D, or E signals and existing NR signals for typical UEs.

[0129] 1) The DL physical channel or reference signal for the NR of a typical UE can be used for DL ​​type A, B, C, D or E signals.

[0130] 1A) In topologies 2A, 3A, or 4 where the environmental IoT device communicates directly with the UE, the SL (Sidelink) physical channel or reference signal for the NR typically directed to the UE can be used for DL ​​type A, B, C, D, or E signals. Considering the differences between topologies where the UE, IAB, or repeater is used as an intermediate or auxiliary node, topology 2 can be further divided into type 2A, type 2B, or type 2C, and topology 3 can be further divided into type 3A, type 3B, or type 3C.

[0131] 2) DL type A, B, C or D signals can be different kinds of signals that are independent of the DL physical channel or reference signal of the NR facing the normal UE.

[0132] 2-1) DL type A, B, C or D signals can use the same modulation scheme and / or the same signal generation scheme or the same waveform as the DL physical channel or reference signal of the NR for a typical UE.

[0133] 2-2) DL type A, B, C or D signals may use different modulation schemes and / or different signal generation schemes or different waveforms than the DL physical channel or reference signal of the NR for the usual UE.

[0134] 2A) In topologies 2A, 3A, or 4 where the environmental IoT device communicates directly with the UE, the DL type A, B, C, or D signal can be a different kind of signal independent of the SL physical channel or reference signal of the NR facing the typical UE.

[0135] 2A-1) DL type A, B, C or D signals can use the same modulation scheme and / or the same signal generation scheme or the same waveform as the SL physical channel or reference signal of the NR for a typical UE.

[0136] 2A-2) In DL type A, B, C or D signals, different modulation schemes and / or different signal generation schemes or different waveforms may be used compared to the SL physical channel or reference signal of the NR for the typical UE.

[0137] Furthermore, in embodiments of the present invention, the UE can typically be a non-RedCap (Reduced Cap) terminal and / or a RedCap terminal, or a UE other than an environmental IoT device. Additionally, the DL physical channel or reference signal for NR for a typical UE can be PDCCH, PDSCH, PBCH, SS, reference signal, etc. Furthermore, the SL physical channel or reference signal for NR for a typical UE can be PSCCH, PSSCH, PSFCH, PSBCH, S-PSS, S-SSS, etc. Moreover, the DL, UL, or SL physical channel or reference signal for NR can be extended to 6G DL, UL, or SL physical channel or reference signal.

[0138] The following relationship can exist between UL type Y signals and existing NR signals for typical UEs.

[0139] 1) The UL physical channel and / or reference signal of the NR for a typical UE can be used as a UL type Y signal.

[0140] 1A) In topologies 2A, 3A, or 4 where the environmental IoT device communicates directly with the UE, the SL physical channel or reference signal of the NR facing the typical UE can be used as a UL type Y signal.

[0141] 2) UL type Y signal can be a different kind of signal that is independent of the UL physical channel or reference signal of the NR facing the usual UE.

[0142] 2-1) UL type Y signals can use the same modulation scheme and / or the same signal generation scheme or the same waveform as the UL physical channel or reference signal of the NR for a typical UE.

[0143] 2-2) DL type Y signals can use different modulation schemes and / or different signal generation schemes or different waveforms than the UL physical channel or reference signal of the NR for a typical UE.

[0144] 2A) In topologies 2A, 3A, or 4 where the environmental IoT device communicates directly with the UE, the UL type Y signal can be a different kind of signal independent of the SL physical channel or reference signal of the NR facing the typical UE.

[0145] 2A-1) UL type Y signals can use the same modulation scheme and / or the same signal generation scheme or the same waveform as the SL physical channel or reference signal of the NR for a typical UE.

[0146] 2A-2) DL type Y signals can use different modulation schemes and / or different signal generation schemes or different waveforms than the SL physical channel or reference signal of the NR for a typical UE.

[0147] In addition, in embodiments of the present invention, the UL physical channel or reference signal for the NR of a typical UE can also be PUCCH, PUSCH, or a reference signal.

[0148] Action 1) The following describes the resource allocation of DL type A, B, C, D and / or E signals and UL type X and / or Y signals as defined above.

[0149] When using DL type A signals and / or DL ​​type B signals in an IoT device in a certain environment, resources can be allocated as shown in 1)-5) below.

[0150] 1) DL type A signals and / or DL ​​type B signals are transmitted and received in different time domain resources.

[0151] 2) DL type A signals and / or DL ​​type B signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0152] 3) DL type A signals and / or DL ​​type B signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0153] 4) DL type A signals and / or DL ​​type B signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0154] 5) DL type A signals and / or DL ​​type B signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0155] When using DL type A signals and / or DL ​​type C signals in an IoT device in a certain environment, resources can be allocated as shown in 1)-5) below.

[0156] 1) DL type A signals and / or DL ​​type C signals are transmitted and received in different time domain resources.

[0157] 2) DL type A signals and / or DL ​​type C signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0158] 3) DL type A signals and / or DL ​​type C signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0159] 4) DL type A signals and / or DL ​​type C signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0160] 5) DL type A signals and / or DL ​​type C signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0161] When using DL type B signals and / or DL ​​type C signals in an IoT device in a certain environment, resources can be allocated as shown in 1)-5) below.

[0162] 1) DL type B signals and / or DL ​​type C signals are transmitted and received in different time domain resources.

[0163] 2) DL type B signals and / or DL ​​type C signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0164] 3) DL type B signals and / or DL ​​type C signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0165] 4) DL type B signals and / or DL ​​type C signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0166] 5) DL type B signals and / or DL ​​type C signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0167] When using DL type A signals and / or UL type X signals in an IoT device in a certain environment, resources can be allocated as shown in 1)-5) below.

[0168] 1) DL type A signals and / or UL type X signals are transmitted and received in different time domain resources.

[0169] 2) DL type A signals and / or UL type X signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0170] 3) DL type A signals and / or UL type X signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0171] 4) DL type A signals and / or UL type X signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0172] 5) DL type A signals and / or UL type X signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0173] When using DL type C signals and / or UL type X signals in an IoT device in a certain environment, resources can be allocated as shown in 1)-5) below.

[0174] 1) DL type C signals and / or UL type X signals are transmitted and received in different time domain resources.

[0175] 2) DL type C signals and / or UL type X signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0176] 3) DL type C signals and / or UL type X signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0177] 4) DL type C signals and / or UL type X signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0178] 5) DL type C signals and / or UL type X signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0179] When using DL type D signals and / or DL ​​type E signals in an IoT device in a certain environment, resources can be allocated as shown in 1)-5) below.

[0180] 1) DL type D signals and / or DL ​​type E signals are transmitted and received in different time domain resources.

[0181] 2) DL type D signals and / or DL ​​type E signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0182] 3) DL type D signals and / or DL ​​type E signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0183] 4) DL type D signals and / or DL ​​type E signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0184] 5) DL type D signals and / or DL ​​type E signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0185] When using DL type D signals and / or UL type Y signals in an IoT device in a certain environment, resources can be allocated as shown in 1)-5) below.

[0186] 1) DL type D signals and / or UL type Y signals are transmitted and received in different time domain resources.

[0187] 2) DL type D signals and / or UL type Y signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0188] 3) DL type D signals and / or UL type Y signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0189] 4) DL type D signals and / or UL type Y signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0190] 5) DL type D signals and / or UL type Y signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0191] When using DL type E signals and / or UL type Y signals in an IoT device in a certain environment, resources can be allocated as shown in 1)-5) below.

[0192] 1) DL type E signals and / or UL type Y signals are transmitted and received in different time domain resources.

[0193] 2) DL type E signals and / or UL type Y signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0194] 3) DL type E signals and / or UL type Y signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0195] 4) DL type E signals and / or UL type Y signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0196] 5) DL type E signals and / or UL type Y signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0197] When using DL type B signals and / or UL type X signals in an IoT device in a certain environment, resources can be allocated as shown in 1)-5) below.

[0198] 1) DL type B signals and / or UL type X signals are transmitted and received in different time domain resources.

[0199] 2) DL type B signals and / or UL type X signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0200] 3) DL type B signals and / or UL type X signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0201] 4) DL type B signals and / or UL type X signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0202] 5) DL type B signals and / or UL type X signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0203] The DL type A, B, C, D or E signals of a certain environmental IoT device and the DL type A, B, C, D or E signals of other environmental IoT devices can be allocated resources as shown in 1)-5) below.

[0204] 1) DL type A, B, C, D or E signals are transmitted and received in different time domain resources.

[0205] 2) DL type A, B, C, D or E signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0206] 3) DL type A, B, C, D or E signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0207] 4) DL type A, B, C, D or E signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0208] 5) DL type A, B, C, D or E signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0209] Resources can be allocated between the DL type A, B, C, D or E signals of a certain environmental IoT device and the UL type X or Y signals of other environmental IoT devices as shown in 1)-5) below.

[0210] 1) DL type A, B, C, D or E signals and UL type X or Y signals are transmitted and received in different time domain resources.

[0211] 2) DL type A, B, C, D or E signals and UL type X or Y signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0212] 3) DL type A, B, C, D or E signals and UL type X or Y signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0213] 4) DL type A, B, C, D or E signals and UL type X or Y signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0214] 5) DL type A, B, C, D or E signals and UL type X or Y signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0215] The UL type X or Y signal of a certain environmental IoT device and the UL type X or Y signal of other environmental IoT devices can be allocated resources as shown in 1)-5) below.

[0216] 1) UL type X or Y signals are transmitted and received in different time domain resources.

[0217] 2) UL type X or Y signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0218] 3) UL type X or Y signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0219] 4) UL type X or Y signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0220] 5) UL type X or Y signals are transmitted and received in the same time domain resources, the same frequency domain resources, and different code domain resources.

[0221] In addition, the aforementioned DL type A, B, C, D, or E signals can be either cell-wide or group-wide. Cell-wide refers to targeting all environmental IoT devices within a specific cell, while group-wide refers to targeting a specific group of environmental IoT devices.

[0222] Furthermore, in embodiments of the present invention, time-domain resources can be symbols, time slots, subframes, frames, or other units of time defined in the specification. Additionally, in embodiments of the present invention, frequency-domain resources can also be units of frequency bands, CC, BWP, RB, subcarriers, or other frequencies defined in the specification.

[0223] In addition, in embodiments of the present invention, the airspace resources can be airspace resources defined by airspace filters, QCL (Quasi co-location) of reference RS, beams, TCI (Transmission Configuration Indicator) status, ports, panels, TRP (Transmission and Reception Point) or other terms.

[0224] In addition, in embodiments of the present invention, the code domain resource may be an orthogonal code, orthogonal cover code, CS (Cyclic shift), quasi-orthogonal code, Gold sequence, M sequence, Zadoff-chu sequence, or other code domain resources defined by other terms.

[0225] Action 2-1) The following describes the resource allocation for DL ​​type A, B, C, D and / or E signals, UL type X and / or Y signals, and NR signals for a typical UE, as defined above.

[0226] Figure 8 This is a diagram illustrating an example (1) of communication according to an embodiment of the present invention. Figure 8 The diagram shows Topology 1, which enables direct bidirectional communication between an environmental IoT device and a base station. It envisions a scenario where the base station communicates with a typical UE. Resources can be allocated for DL ​​type A, B, C, D, or E signals sent from the base station to the environmental IoT device and NR DL signals sent from the base station to the typical UE, as shown in 1)-5) below.

[0227] 1) DL type A, B, C, D or E signals and NR DL signals are transmitted and received in different time domain resources.

[0228] 2) DL type A, B, C, D or E signals are transmitted and received in the same time domain resources but different frequency domain resources as NR DL signals.

[0229] 3) DL type A, B, C, D or E signals and NR DL signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0230] 4) DL type A, B, C, D or E signals and NR DL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0231] 5) DL type A, B, C, D or E signals and NR DL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0232] Resources can be allocated for UL type X or Y signals sent from environmental IoT devices to the base station and UL signals for NRs sent from the typical UE to the base station, as shown in 1)-5) below.

[0233] 1) UL type X or Y signals and NR UL signals are transmitted and received in different time domain resources.

[0234] 2) UL type X or Y signals and NR type UL signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0235] 3) UL type X or Y signals and NR UL signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0236] 4) UL type X or Y signals and NR type UL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0237] 5) UL type X or Y signals and NR type UL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0238] Resources can be allocated to DL type A, B, C, D or E signals sent from the base station to the environmental IoT device and UL signals of NR sent from the UE to the base station, as shown in 1)-5) below.

[0239] 1) DL type A, B, C, D or E signals and NR UL signals are transmitted and received in different time domain resources.

[0240] 2) DL type A, B, C, D or E signals and NR UL signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0241] 3) DL type A, B, C, D or E signals and NR UL signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0242] 4) DL type A, B, C, D or E signals and NR UL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0243] 5) DL type A, B, C, D or E signals and NR UL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0244] Resources can also be allocated as shown in 1)-5) below for UL type X or Y signals sent from environmental IoT devices to the base station and NR DL signals sent from the base station to the usual UE.

[0245] 1) UL type X or Y signals and NR type DL signals are transmitted and received in different time domain resources.

[0246] 2) UL type X or Y signals and NR type DL signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0247] 3) UL type X or Y signals and NR type DL signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0248] 4) UL type X or Y signals and NR type DL signals are transmitted and received in the same time domain resources and the same frequency domain resources, but in different spatial domain resources.

[0249] 5) UL type X or Y signals and NR type DL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0250] In addition, different options can be applied to in-band and out-of-band scenarios.

[0251] The resource allocation of signals from environmental IoT devices and typical UE signals can be determined as shown in 1) or 2) below.

[0252] 1) It can also be determined based on the base station implementation without notifying the UE.

[0253] 2) Time-domain, frequency-domain, spatial-domain, and / or code-domain resources for transmitting and receiving signals for environmental IoT devices can be communicated to the typical UE.

[0254] Figure 9 This is a diagram illustrating an example (1) of resource allocation according to an embodiment of the present invention. Figure 8In such an environment, such as Figure 9 As shown, the DL or UL channels or signals of the UE and the signals of the environmental IoT devices can typically be TDM (Time Division Multiplexing) or FDM (Frequency Division Multiplexing).

[0255] As in TDM Example 1, time-domain resources can be separated, and frequency-domain resources can partially overlap. As in TDM Example 2, time-domain resources can be adjacent, and frequency-domain resources can completely overlap.

[0256] As in FDM Example 1, time-domain resources can partially overlap, while frequency-domain resources can be separated. As in FDM Example 2, time-domain resources can partially overlap, while frequency-domain resources can be adjacent.

[0257] Action 2-2) Figure 10 This is a diagram illustrating an example (2) of communication according to an embodiment of the present invention. Figure 10 The diagram shows topology 2A, which describes bidirectional communication between a UE and an environmental IoT device between a base station and a device, assuming the base station and the UE are communicating. Resources can be allocated for DL ​​type A, B, C, D, or E signals sent from the UE to the environmental IoT device and NR DL signals sent from the base station to the UE, as shown in 1)-5) below.

[0258] 1) DL type A, B, C, D or E signals and NR DL signals are transmitted and received in different time domain resources.

[0259] 2) DL type A, B, C, D or E signals are transmitted and received in the same time domain resources but different frequency domain resources as NR DL signals.

[0260] 3) DL type A, B, C, D or E signals and NR DL signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0261] 4) DL type A, B, C, D or E signals and NR DL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0262] 5) DL type A, B, C, D or E signals and NR DL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0263] Resources can be allocated for DL ​​type A, B, C, D or E signals sent from the UE to the environmental IoT device and UL signals of NR sent from the UE to the base station, as shown in 1)-5) below.

[0264] 1) DL type A, B, C, D or E signals and NR UL signals are transmitted and received in different time domain resources.

[0265] 2) DL type A, B, C, D or E signals and NR UL signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0266] 3) DL type A, B, C, D or E signals and NR UL signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0267] 4) DL type A, B, C, D or E signals and NR UL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0268] 5) DL type A, B, C, D or E signals and NR UL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0269] Resources can be allocated for UL type X or Y signals sent from the environmental IoT device to the UE and NR DL signals sent from the base station to the UE, as shown in 1)-5) below.

[0270] 1) UL type X or Y signals and NR type DL signals are transmitted and received in different time domain resources.

[0271] 2) UL type X or Y signals and NR type DL signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0272] 3) UL type X or Y signals and NR type DL signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0273] 4) UL type X or Y signals and NR type DL signals are transmitted and received in the same time domain resources and the same frequency domain resources, but in different spatial domain resources.

[0274] 5) UL type X or Y signals and NR type DL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0275] Resources can be allocated for UL type X or Y signals sent from the environmental IoT device to the UE and UL signals for NR sent from the UE to the base station, as shown in 1)-5) below.

[0276] 1) UL type X or Y signals and NR UL signals are transmitted and received in different time domain resources.

[0277] 2) UL type X or Y signals and NR type UL signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0278] 3) UL type X or Y signals and NR UL signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0279] 4) UL type X or Y signals and NR type UL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0280] 5) UL type X or Y signals and NR type UL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0281] In addition, different options can be applied to in-band and out-of-band scenarios.

[0282] The above options can also be determined based on the UE's capabilities.

[0283] The time-domain, frequency-domain, spatial-domain, and / or code-domain resources for transmitting and receiving signals for environmental IoT devices can be notified to the UE between the device and the base station.

[0284] Figure 11 This is a diagram illustrating an example (2) of resource allocation according to an embodiment of the present invention. Figure 10 In such an environment, such as Figure 11 As shown, the signals between the UE and the base station and between the UE and the environmental IoT devices can be TDM or FDM.

[0285] As in TDM Example 1, time-domain resources can be separated, and frequency-domain resources can partially overlap. As in TDM Example 2, time-domain resources can be adjacent, and frequency-domain resources can completely overlap.

[0286] As in FDM Example 1, time-domain resources can partially overlap, while frequency-domain resources can be separated. As in FDM Example 2, time-domain resources can partially overlap, while frequency-domain resources can be adjacent.

[0287] Action 2-2A) Figure 12 This is a diagram illustrating an example (3-1) of communication according to an embodiment of the present invention. Figure 12 The diagram shows topology 2A for bidirectional communication between a base station and a UE and an ambient IoT device, assuming the base station communicates with the UE and the UE communicates with other regular UEs. Resources can be allocated for DL ​​type A, B, C, D, or E signals sent from the UE to the ambient IoT device and NR SL signals received by the UE from regular UEs, as shown in 1)-5) below.

[0288] 1) DL type A, B, C, D or E signals and NR SL signals are transmitted and received in different time domain resources.

[0289] 2) DL type A, B, C, D or E signals and NR type SL signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0290] 3) DL type A, B, C, D or E signals and NR SL signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0291] 4) DL type A, B, C, D or E signals and NR SL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0292] 5) DL type A, B, C, D or E signals and NR SL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0293] Resources can be allocated to DL type A, B, C, D or E signals sent from the UE to the ambient IoT device and SL signals of NR sent by the UE to the usual UE, as shown in 1)-5) below.

[0294] 1) DL type A, B, C, D or E signals and NR SL signals are transmitted and received in different time domain resources.

[0295] 2) DL type A, B, C, D or E signals and NR type SL signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0296] 3) DL type A, B, C, D or E signals and NR SL signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0297] 4) DL type A, B, C, D or E signals and NR SL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0298] 5) DL type A, B, C, D or E signals and NR SL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0299] Resources can be allocated for UL type X or Y signals sent from the environmental IoT device to the UE and SL signals of NR received by the UE from the UE as shown in 1)-5) below.

[0300] 1) UL type X or Y signals and NR type SL signals are transmitted and received in different time domain resources.

[0301] 2) UL type X or Y signals and NR type SL signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0302] 3) UL type X or Y signals and NR type SL signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0303] 4) UL type X or Y signals and NR type SL signals are transmitted and received in the same time domain resources and the same frequency domain resources, but in different spatial domain resources.

[0304] 5) UL type X or Y signals and NR type SL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0305] Resources can be allocated for UL type X or Y signals sent from the environmental IoT device to the UE and NR SL signals sent by the UE to the regular UE, as shown in 1)-5) below.

[0306] 1) UL type X or Y signals and NR type SL signals are transmitted and received in different time domain resources.

[0307] 2) UL type X or Y signals and NR type SL signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0308] 3) UL type X or Y signals and NR type SL signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0309] 4) UL type X or Y signals and NR type SL signals are transmitted and received in the same time domain resources and the same frequency domain resources, but in different spatial domain resources.

[0310] 5) UL type X or Y signals and NR type SL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0311] In addition, different options can be applied to in-band and out-of-band scenarios.

[0312] The above options can also be determined based on the UE's capabilities.

[0313] The time-domain, frequency-domain, spatial-domain, and / or code-domain resources for transmitting and receiving signals for environmental IoT devices can be notified to the UE between the device and the base station. Furthermore, the time-domain, frequency-domain, spatial-domain, and / or code-domain resources for transmitting and receiving signals for environmental IoT devices can be notified to the regular UE.

[0314] Actions 2-3) Figure 13This is a diagram illustrating an example (3-2) of communication according to an embodiment of the present invention. Figure 13 The diagram illustrates topology 2B, which describes bidirectional communication between an IAB node and an environmental IoT device, oriented towards a base station and a device. It envisions a scenario where the base station communicates with the IAB node, and the IAB node communicates with other typical UEs. Resources can be allocated for DL ​​type A, B, C, D, or E signals sent from the IAB-DU (Distributed Unit) to the environmental IoT device, and for NR DL signals sent from the IAB-DU to the typical UE, as shown in 1)-5) below.

[0315] 1) DL type A, B, C, D or E signals and NR DL signals are transmitted and received in different time domain resources.

[0316] 2) DL type A, B, C, D or E signals are transmitted and received in the same time domain resources but different frequency domain resources as NR DL signals.

[0317] 3) DL type A, B, C, D or E signals and NR DL signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0318] 4) DL type A, B, C, D or E signals and NR DL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0319] 5) DL type A, B, C, D or E signals and NR DL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0320] Resources can be allocated for DL ​​type A, B, C, D or E signals sent from the IAB-DU to the environmental IoT device, as well as for UL signals of NR that the UE typically sends to the IAB-DU, as shown in 1)-5) below.

[0321] 1) DL type A, B, C, D or E signals and NR UL signals are transmitted and received in different time domain resources.

[0322] 2) DL type A, B, C, D or E signals and NR UL signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0323] 3) DL type A, B, C, D or E signals and NR UL signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0324] 4) DL type A, B, C, D or E signals and NR UL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0325] 5) DL type A, B, C, D or E signals and NR UL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0326] Resources can be allocated to the UL type X or Y signals sent from the environmental IoT device to the IAB-DU and the DL signals of the NR sent from the IAB-DU to the typical UE, as shown in 1)-5) below.

[0327] 1) UL type X or Y signals and NR type DL signals are transmitted and received in different time domain resources.

[0328] 2) UL type X or Y signals and NR type DL signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0329] 3) UL type X or Y signals and NR type DL signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0330] 4) UL type X or Y signals and NR type DL signals are transmitted and received in the same time domain resources and the same frequency domain resources, but in different spatial domain resources.

[0331] 5) UL type X or Y signals and NR type DL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0332] Resources can be allocated to UL type X or Y signals sent from environmental IoT devices to the IAB-DU and UL signals of NRs typically sent by the UE to the IAB-DU, as shown in 1)-5) below.

[0333] 1) UL type X or Y signals and NR UL signals are transmitted and received in different time domain resources.

[0334] 2) UL type X or Y signals and NR type UL signals are transmitted and received in the same time domain resources but different frequency domain resources.

[0335] 3) UL type X or Y signals and NR UL signals are transmitted and received in the same time domain resources but different frequency domain resources and different spatial domain resources.

[0336] 4) UL type X or Y signals and NR type UL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different spatial domain resources.

[0337] 5) UL type X or Y signals and NR type UL signals are transmitted and received in the same time domain resources and the same frequency domain resources but different code domain resources.

[0338] In addition, different options can be applied to in-band and out-of-band scenarios.

[0339] The options mentioned above can be determined based on the capabilities of the IAB node.

[0340] The time-domain, frequency-domain, spatial-domain, and / or code-domain resources for transmitting and receiving signals for environmental IoT devices can be notified to the UE between the device and the base station.

[0341] The resource allocation of signals from environmental IoT devices and typical UE signals can be determined as shown in 1) or 2) below.

[0342] 1) This can be determined based on the implementation of the IAB node.

[0343] 2) The time domain, frequency domain, spatial domain and / or code domain resources used for transmitting and receiving signals for environmental IoT devices can be notified to the IAB node.

[0344] Figure 14 This is a diagram illustrating an example (3) of resource allocation according to an embodiment of the present invention. Figure 13 In such an environment, such as Figure 14 As shown, the signals between the IAB-DU and the typical UE, as well as the signals between the IAB-DU and the environmental IoT devices, can be TDM or FDM.

[0345] As in TDM Example 1, time-domain resources can be separated, and frequency-domain resources can partially overlap. As in TDM Example 2, time-domain resources can be adjacent, and frequency-domain resources can completely overlap.

[0346] As in FDM Example 1, time-domain resources can partially overlap, while frequency-domain resources can be separated. As in FDM Example 2, time-domain resources can partially overlap, while frequency-domain resources can be adjacent.

[0347] Additionally, the IAB-MT can be used to transmit and receive signals from IoT devices in the environment. In this case, the IAB-MT can act as a UE to perform action 2-2).

[0348] Furthermore, in topology 2C, where the network controlled repeater (NCR) facilitates bidirectional communication between environmental IoT devices and base stations, the NCR amplifies and forwards RF signals, so the expected changes to the NCR operation are minimal. Typically, the UE expects the same operation as in operation 2-1).

[0349] In topology 3A where the IoT device receives and sends data from the UE to the base station or from the base station to the UE, the signal in the base station can be the same as in action 2-1), and the signal in the UE can be the same as in action 2-2) or action 2-2A).

[0350] In topology 3B, where environmental IoT devices receive signals from IAB nodes and send them to base stations or receive signals from base stations and send them to IAB nodes, the signals in the base station can be the same as in action 2-1), and the signals in the IAB nodes can be the same as in action 2-3).

[0351] In topology 3C where environmental IoT devices receive from NCR and transmit to the base station or receive from the base station and transmit to NCR, the NCR action changes little.

[0352] In topology 4, where environmental IoT devices and UEs communicate bidirectionally, either action 2-2) or action 2-2A can be used. From the perspective of resource reuse, topology 4 is similar to topology 2A.

[0353] Action 3) The following describes the time domain resources, frequency domain resources, spatial domain resources and / or code domain resources used by signals for environmental IoT devices.

[0354] You can also specify the time-domain resources used for transmitting and receiving signals by environmental IoT devices, as shown in the following options.

[0355] Option 1) Notify the index of subframes, time slots, symbols, and / or other time units defined in the specification.

[0356] Option 2) Notify the index and period of subframes, time slots, symbols, and / or other time units defined in the specification. Time-domain resources are periodically configured.

[0357] Option 3) The notification begins at the time specified in subframes, time slots, symbols, and / or other units of time as defined in the specification, and lasts for the duration specified in the number of subframes, time slots, symbols, and / or other units of time as defined in the specification.

[0358] Option 4) The notification starts at the time of notification in terms of subframes, time slots, symbols, and / or other unit times defined in the specification, and the duration and period of notification in terms of the number of subframes, time slots, symbols, and / or other unit times defined in the specification. Time-domain resources are set periodically.

[0359] Option 5) can be combined with time slot format notifications. For example, in addition to D, U, or F, a new type X can be introduced. When other unit times defined in the time slot, symbol, and / or specification are notified as "X", it can be interpreted that the time domain resource is being used for environmental IoT devices.

[0360] Option 6 (IAB only) can be combined with notifications of hard H, soft S, and unavailable NA from IAB-DU. For example, in addition to H, S, and NA, a new type X can also be imported. When a time slot, symbol, and / or other unit time defined in the specification is notified as "X", it can be interpreted that the time domain resource is being used for environmental IoT devices.

[0361] You can also specify the frequency domain resources used for transmitting and receiving signals by environmental IoT devices, as shown in the following options.

[0362] Option 1) can notify frequency domain resources. It can be determined that the notified frequency domain resources will always be used for environmental IoT devices. Furthermore, notification can also be performed as follows.

[0363] 1) It can notify the index of RB, subcarrier and / or other frequency units defined in the specification.

[0364] 2) The starting position and length of the frequency domain resource can also be notified, wherein the starting position of the frequency domain resource is notified as the RB, subcarrier and / or other frequency unit defined in the specification at the beginning of the frequency domain resource, and the length of the frequency domain resource is notified as the number of RB, subcarrier and / or other frequency unit defined in the specification.

[0365] 3) It can notify the frequency band, CC, or BWP set for the transmission and reception of signals for environmental IoT devices.

[0366] 4) (IAB only) Notifications can be combined with notifications of IAB-DU's hard H, software S, and unavailable NA. For example, in addition to H, S, and NA, new types X can also be imported. When a frequency domain resource is notified as "X", it can be interpreted as the frequency domain resource being used for environmental IoT devices.

[0367] Option 2) Notify of frequency-domain resources. It can be determined that the frequency-domain resource is used for environmental IoT devices within the time-domain resource. The notification of frequency-domain resources can be the same as Option 1). The notification of time-domain resources can be the same as Options 1)-6) above.

[0368] You can also notify the spatial area resources used by environmental IoT devices for transmitting and receiving signals, as shown in the following options.

[0369] Option 1) can notify the use of a spatial resource. It can be determined that this spatial resource is always used for environmental IoT devices at any frequency. This can be a beam, the QCL of a reference RS, TCI, spatially relevant information, a port, a panel, a TRP, or an index of another spatial filter defined in the specification.

[0370] Option 2) can notify the spatiotemporal domain resources. It can be decided that the spatiotemporal domain resource will be used for environmental IoT devices within the spatiotemporal domain resource. The notification of the spatiotemporal domain resource can be similar to Option 1). The notification of the spatiotemporal domain resource can be the same as Options 1)-6) above.

[0371] Option 3) can notify the time-frequency spatial domain resources. It can be determined that the spatial domain resource is used for environmental IoT devices within the time-domain resource and / or the frequency-domain resource. Notification of spatial domain resources can be similar to option 1). Notification of time-domain resources can be the same as options 1)-6) above. Notification of frequency-domain resources can be the same as options 1) and / or 2) above.

[0372] You can also specify the code domain resources used by environmental IoT devices for transmitting and receiving signals, as shown in the following options.

[0373] Option 1) can notify code domain resources. It can be determined that resources for this code domain are always used for environmental IoT devices at any frequency. It can also notify code domain resources defined by orthogonal codes, OCC, CS, pseudo-orthogonal codes, Gold sequences, M sequences, Zadoff-chu sequences, or other terms.

[0374] Option 2) can notify the time code domain resource. It can be determined that the code domain resource is used for environmental IoT devices within the time domain resource. The notification of the code domain resource can be the same as in Option 1). The notification of the time domain resource can be the same as in Options 1)-6) above.

[0375] Option 3) can notify the time-frequency code domain resource. It can be determined that the code domain resource is used for environmental IoT devices in the time domain resource and / or the frequency domain resource. The notification of the code domain resource can be the same as option 1). The notification of the time domain resource can be the same as options 1)-6) above. The notification of the frequency domain resource can be the same as options 1) and / or 2) above.

[0376] The time, frequency, spatial and / or code domain resources of a certain type of signal can have a predefined or pre-set relationship with the time, frequency, spatial and / or code domain resources of other types of signals.

[0377] For example, the time, frequency, spatial, and / or code domain resources of a certain type of signal can be implicitly derived from the time, frequency, spatial, and / or code domain resources of other types of signals. A certain type of signal can also be a signal of the type defined in action 1) above.

[0378] For example, the resources used for receiving frequency, space, and / or code domain can be the same as those used for transmitting.

[0379] For example, the time-domain resource used for receiving can be the time-domain resource used for transmitting X units of time later. The unit of time can be a millisecond, a time slot, a symbol, or a unit of time other than these.

[0380] The following describes the actions of the UE or IAB related to the time, frequency, spatial and / or code domain resources used by signals from environmentally oriented IoT devices that overlap with existing signals.

[0381] Action 4) To notify the UE of the time, frequency, spatial and / or code domain resources for transmitting and receiving signals for the environmental IoT device, the following actions may be taken.

[0382] Option 1) The UE may be envisioned as having time, frequency, spatial and / or code domain resources for DL ​​and / or UL channels and / or signals that are notified to be used for NR transmission and reception between the UE and the base station that do not overlap with resources that are notified to be used for environmental IoT devices.

[0383] Option 2) can be determined as follows: the time, frequency, space and / or code domain resources used for environmental IoT devices cannot be used for DL ​​and / or UL channels and / or signals of NR transmitted and received between the UE and the base station.

[0384] Option 3) The UE may perform priority ordering on DL and / or UL channels and / or signals of NR transmitted and received between the UE and the base station that overlap with the time, frequency, spatial and / or code domain resources notified for use with environmental IoT devices.

[0385] Option 4) can also be envisioned as follows: when the time, frequency and / or code domain resources notified for use by environmental IoT devices overlap with the time, frequency and / or code domain resources notified for use by DL and / or UL channels and / or signals for NR transmission and reception between the UE and the base station, different spatial domain resources are notified for each resource.

[0386] In addition, the above options can be applied to any of the UEs that typically act as intermediate or auxiliary nodes in topology 2A / 3A / 4.

[0387] Furthermore, in topology 2B / 3B, the time, frequency, spatial and / or code domain resources for transmitting and receiving signals between the IAB-DU and the environmental IoT devices can also be operated as follows.

[0388] Option 1) IAB-DU can be envisioned as having time, frequency, spatial and / or code domain resources notified for transmission and reception between IAB-DU and a typical UE that do not overlap with resources notified for transmission and reception between IAB-DU and ambient IoT devices.

[0389] Option 2) can be determined as follows: the time, frequency, space and / or code domain resources used for transmission and reception between the IAB-DU and the environmental IoT device cannot be used for signals transmitted and received between the IAB-DU and the normal UE.

[0390] Option 3) The IAB-DU can prioritize signals transmitted and received between the IAB-DU and the typical UE that overlap with the time, frequency, spatial and / or code domain resources notified for transmission and reception between the IAB-DU and the environmental IoT device.

[0391] Option 4) The IAB-DU can decide whether to prioritize transmitting and receiving with the usual UE or with the environmental IoT devices.

[0392] Option 5) Where the time, frequency and / or code domain resources notified for transmission and reception between the IAB-DU and the normal UE overlap with the time, frequency and / or code domain resources notified for transmission and reception between the IAB-DU and the environmental IoT device, it is conceivable that the respective resources are notified of different spatial domain resources.

[0393] Action 4A) describes the actions of the UE or IAB in terms of time, frequency, spatial and / or code domain resources used in signals for IoT devices in environments that overlap with existing SL signals.

[0394] In topologies 2A / 3A / 4, the following actions can be taken to notify the UE of the time, frequency, spatial, and / or code domain resources used for transmitting and receiving signals from IoT devices in the environment:

[0395] Option 1) The UE may envision that the time, frequency, spatial and / or code domain resources of the SL channel and / or reference signals for NR transmission and reception between the UE and the base station do not overlap with the time, frequency, spatial and / or code domain resources of the UE for use with environmental IoT devices.

[0396] Option 2) can determine that time, frequency, spatial and / or code domain resources for environmental IoT devices cannot be used for the transmission and reception of SL channels and / or reference signals for NR between the UE and a normal sidelink UE.

[0397] Option 3) The UE can prioritize SL channels and / or reference signals of NRs transmitted and received between the UE and a normal sidelink UE that overlap with the time, frequency, spatial and / or code domain resources of the notified environmental IoT devices.

[0398] Option 4) When the time, frequency and / or code domain resources for the transmission and reception of SL channels and / or reference signals for NR between the UE and the usual sidelink UE overlap with the time, frequency and / or code domain resources for the transmission and reception of signals for the environmental IoT device by the UE, it is conceivable that the respective resources are notified of different spatial domain resources.

[0399] The following describes the actions of the UE or IAB when it has the ability to select resources from time, frequency, spatial and / or code domain resources of signals that are notified to be used for environmental IoT devices.

[0400] Action 5) Figure 15 This is a diagram illustrating resource allocation in an intermediate node according to an embodiment of the present invention. In topology 2A / 3A / 4, the time, frequency, spatial, and / or code domain resources for transmitting and receiving signals between the UE and the environmental IoT device may also be operated as follows.

[0401] Option 1) The base station can have complete control over the UE's actions. For example... Figure 15 As shown in Option 1, the UE can use the time, frequency, spatial and / or code domain resources notified to the base station to communicate with environmental IoT devices.

[0402] Option 2) The time, frequency, spatial, and / or code domain resources notified to the base station can be considered as candidate resources. For example... Figure 15 As shown, the UE can have the ability to determine the time, frequency, spatial and / or code domain resources actually used for transmission and reception between the UE and the IoT devices in the environment from the candidate resources.

[0403] Furthermore, in topology 2B / 3B, the time, frequency, spatial and / or code domain resources for transmitting and receiving signals between the IAB-DU and the environmental IoT devices can also be operated as follows.

[0404] Option 1) The base station can fully control the IAB-DU's actions. For example... Figure 15 As shown in Option 1, the IAB-DU can use the time, frequency, space and / or code domain resources notified to the base station to communicate with environmental IoT devices.

[0405] Option 2) The time, frequency, spatial, and / or code domain resources notified to the base station can be considered as candidate resources. For example... Figure 15 As shown, the IAB-DU can determine the actual time, frequency, spatial and / or code domain resources used in the transmission and reception between the IAB-DU and environmental IoT devices from the candidate resources.

[0406] The following describes, in addition to the time, frequency, spatial and / or code domain resources of the signals used for environmental IoT devices, other information notified to the UEs in topologies 2A / 3A / 4 or the IAB nodes in topologies 2B / 3B.

[0407] Action 6) For the UE in topology 2A / 3A / 4 or the IAB in topology 2B / 3B, the action can be performed as shown in 1)-6).

[0408] 1) For the time, frequency, spatial and / or code domain resources of signals transmitted and received between the UE or IAB node and the ambient IoT device, the UE or IAB node may be notified whether the resources are used for transmission to the ambient IoT device or for reception from the ambient IoT device.

[0409] 2) For the time, frequency, spatial, and / or code domain resources notified for transmitting signals from the UE or IAB node to the environmental IoT devices, the UE or IAB node can specify which type of signal transmission the resource is used for. For example, the signal type can be any one of the DL type A, DL type B, DL type C, DL type D, and DL type E signals mentioned above. Different types of signals can use different modulation schemes and / or different waveforms. DL type B, DL type C, and / or DL ​​type E signals may not be modulated.

[0410] 3) Regarding the time, frequency, spatial, and / or code domain resources notified for receiving signals from the environmental IoT device to the UE or IAB node, the UE or IAB node can be notified of which type of signal the resource is used for. For example, the signal type could be either a UL type X signal or a UL type Y signal as described above. Different types of signals can use different modulation schemes and / or different waveforms.

[0411] 4) Regarding the time, frequency, spatial, and / or code domain resources for transmitting and receiving signals between the UE or IAB node and the environmental IoT device, the UE or IAB node can notify the type of the target environmental IoT device. For example, the type of environmental IoT device can be device A, device B, or device C as described above. Different types of environmental IoT devices can use different modulation methods and / or different waveforms.

[0412] 5) For the time, frequency, spatial and / or code domain resources of signals to be transmitted and received between the UE or IAB node and the IoT devices in the environment, the UE or IAB node may directly notify the modulation method and / or waveform.

[0413] 6) For the time, frequency, spatial, and / or code domain resources notified for the transmission and reception of signals between the UE or IAB node and the environmental IoT device, the UE or IAB node may notify the identifier of the target environmental IoT device. The identifier, device type, modulation scheme, and waveform used by the environmental IoT device may be separately notified to the UE or IAB node.

[0414] The following describes the general process of signal forwarding between the base station and environmental IoT devices in topology 2A / 3A or IAB nodes in topology 2B / 3B.

[0415] Action 7) DL forwarding from the base station to the environmental IoT device can be performed as follows.

[0416] Figure 16 This is a timing diagram illustrating example (1) of signal forwarding in an embodiment of the present invention. In step S11, the UE or IAB node receives DL information from the BS to be forwarded to the target environmental IoT device. The DL information contains an identifier of the target environmental IoT device. Based on this identifier, the UE or IAB node identifies that the DL information is forwarded to the target environmental IoT device. The identifier of the environmental IoT device can be an identifier in the PHY layer, an existing higher layer, or a new higher layer, such as an identifier in a higher layer with routing capabilities. For example, for the IAB node, the identifier can be an identifier in the BAP (Backhaul Adaptation Protocol) layer with routing capabilities.

[0417] In step S12, the UE or IAB node obtains notifications of time, frequency, spatial, and / or code domain resources from the DL information. The UE or IAB node uses these time, frequency, spatial, and / or code domain resources for forwarding the DL information. The UE or IAB node can obtain the device type, modulation scheme, and / or waveform from the DL information. Alternatively, the UE or IAB node can notify in advance of the association between the device type, modulation scheme, and / or waveform and the device identifier. The UE or IAB node can determine the device type, modulation scheme, and / or waveform based on the device identifier and its association.

[0418] In step S13, the UE or IAB node forwards the DL information to the environmental IoT device.

[0419] Figure 17This is a timing diagram illustrating example (2) of signal forwarding in an embodiment of the present invention. In step S21, the UE or IAB node receives DL information from the BS to be forwarded to the target environmental IoT device. The DL information contains an identifier of the target environmental IoT device. Based on this identifier, the UE or IAB node identifies that the DL information is forwarded to the target environmental IoT device. The identifier of the environmental IoT device can be an identifier in the PHY layer, an existing higher layer, or a new higher layer, such as an identifier in a higher layer with routing capabilities. For example, for the IAB node, the identifier can be an identifier in the BAP layer with routing capabilities.

[0420] In step S22, the UE or IAB node obtains prior notification of candidate time, frequency, spatial, and / or code domain resources from the BS. The UE or IAB node autonomously selects the time, frequency, spatial, and / or code domain resources from these candidate resources for forwarding DL information. The UE or IAB node can obtain the device type, modulation scheme, and / or waveform from the DL information. Alternatively, the UE or IAB node can provide prior notification of the association between the device type, modulation scheme, and / or waveform and the device identifier. The UE or IAB node can determine the device type, modulation scheme, and / or waveform based on the device identifier and the association relationship.

[0421] In step S23, the UE or IAB node forwards the DL information to the environmental IoT device.

[0422] Figure 18 This is a timing diagram illustrating example (3) of signal forwarding in an embodiment of the present invention. In step S31, the UE or IAB node receives notifications of time, frequency, spatial, and / or code domain resources from the BS. The UE or IAB node uses these time, frequency, spatial, and / or code domain resources to receive UL signals from environmental IoT devices.

[0423] When the environmental IoT device is of type A or type B, the UE or IAB node uses the time, frequency, spatial and / or code domain resources of the notification to send the DL type B signal and uses the time, frequency, spatial and / or code domain resources of the notification to receive the backscattered UL signal from the environmental IoT device.

[0424] The UE or IAB node can be notified of the device type, modulation scheme, and / or waveform to receive the UL signal. Alternatively, the UE or IAB node can be notified of the identifier of the target environmental IoT device to receive the UL signal. The UE or IAB node can be notified in advance of the association between the device type, modulation scheme, and / or waveform and the device identifier. The UE or IAB node can determine the device type, modulation scheme, and / or waveform based on the device identifier and the association.

[0425] In step S32, the UE or IAB node receives UL information from the environmental IoT device. In step S33, the UE or IAB node forwards the UL information to the BS.

[0426] Figure 19 This is a timing diagram illustrating example (4) of signal forwarding in an embodiment of the present invention. In step S41, the UE or IAB node receives a request from the BS to "receive a UL signal from an environmental IoT device". The UE or IAB node receives prior notification of time, frequency, spatial and / or code domain resources from the BS. In step S42, the UE or IAB node autonomously selects from the notified time, frequency, spatial and / or code domain resources the time, frequency, spatial and / or code domain resources for receiving the UL signal from the environmental IoT device.

[0427] When the environmental IoT device is of type A or type B, the UE or IAB node uses the selected time, frequency, spatial and / or code domain resources to transmit DL type B signals and uses the selected time, frequency, spatial and / or code domain resources to receive backscattered UL signals from the environmental IoT device.

[0428] The request may include the device type, modulation scheme, and / or waveform for receiving UL signals. Alternatively, the request may include an identifier of the target environmental IoT device for receiving UL signals. The UE or IAB node may notify in advance of the association between the device type, modulation scheme, and / or waveform and the device identifier. The UE or IAB node may determine the device type, modulation scheme, and / or waveform based on the device identifier and the association.

[0429] In step S43, the UE or IAB node receives UL information from the environmental IoT device. In step S44, the UE or IAB node forwards the UL information to the BS.

[0430] Figure 20 This is a timing diagram illustrating example (5) of signal forwarding in an embodiment of the present invention. In step S51, the UE or IAB node receives a request from the environmental IoT device to "receive a UL signal from the environmental IoT device". The UE or IAB node receives prior notification of time, frequency, spatial and / or code domain resources from the BS. In step S52, the UE or IAB node autonomously selects from the notified time, frequency, spatial and / or code domain resources the time, frequency, spatial and / or code domain resources for receiving the UL signal from the environmental IoT device.

[0431] When the environmental IoT device is of type A or type B, the UE or IAB node uses the selected time, frequency, spatial and / or code domain resources to transmit DL type B signals and uses the selected time, frequency, spatial and / or code domain resources to receive backscattered UL signals from the environmental IoT device.

[0432] The request may include the device type, modulation scheme, and / or waveform for receiving UL signals. Alternatively, the request may include an identifier of the target environmental IoT device for receiving UL signals. The UE or IAB node may notify in advance of the association between the device type, modulation scheme, and / or waveform and the device identifier. The UE or IAB node may determine the device type, modulation scheme, and / or waveform based on the device identifier and its association.

[0433] In step S53, the UE or IAB node receives UL information from the environmental IoT device. In step S54, the UE or IAB node forwards the UL information to the BS.

[0434] The following describes the information contained in DL type A signals and / or DL ​​type D signals sent from BS, UE, or IAB nodes to environmental IoT devices.

[0435] Action 8) The DL type A signal and / or DL ​​type D signal sent by the BS, UE or IAB node to the environmental IoT device may include the following information.

[0436] 1) Identifier for environmental IoT devices. This identifier identifies the target environmental IoT device.

[0437] 2) DL information format identifier. Identifies the type of DL information contained. This identifier can identify the number of bits, the fields included, the number of bits for each field, and the interpretation of each field in the DL information.

[0438] 3) Notifications sent from the BS, UE, or IAB node to the environmental IoT device, and subsequently sent via DL.

[0439] 4) Control information sent from the BS, UE, or IAB node to the environmental IoT device for subsequent DL transmissions. This control information may also include a format identifier identifying the type of DL information contained. This format identifier may identify the number of bits, the fields included, the number of bits for each field, and the interpretation of each field in the DL information. This control information may include the allocation of time, frequency, spatial, and / or code domain resources for subsequent DL transmissions. This control information may include the modulation scheme, waveform, and encoding scheme.

[0440] 5) Requests sent from environmental IoT devices to BS, UE, or IAB nodes, and subsequently sent by UL.

[0441] 6) Control information transmitted from environmental IoT devices to BS, UE, or IAB nodes for subsequent UL transmissions. This control information may also include a format identifier identifying the type of UL information being transmitted. This format identifier may identify the number of bits, the fields included, the number of bits for each field, and the interpretation of each field in the UL information. This control information may include the allocation of time, frequency, spatial, and / or code domain resources for subsequent UL transmissions. This control information may include the modulation scheme, waveform, and encoding scheme.

[0442] 7) CRC.

[0443] The following explains how environmental IoT devices obtain the start and / or end times of DL signals sent from BS, UE, or IAB nodes to environmental IoT devices, and how environmental IoT devices obtain the start and / or end times of UL signals sent from environmental IoT devices to BS, UE, or IAB nodes.

[0444] Action 9) The start time of the DL transmission from the BS, UE, or IAB node to the environmental IoT device can be determined as follows.

[0445] Option 1) Figure 21 This is a diagram illustrating an example (1) of the timing of signal forwarding according to an embodiment of the present invention. Figure 21 As shown, the start time of DL transmission from the BS, UE, or IAB node to the environmental IoT device can be notified via a pre-signal sent from the BS, UE, or IAB node. The pre-signal can be a DL type A signal or a DL type D signal carrying control information for DL ​​transmission.

[0446] Option 2) Figure 22 This is a diagram illustrating an example (2) of the timing for signal forwarding according to an embodiment of the present invention. The association between the pre-processing DL signal sent from the BS, UE, or IAB node to the environmental IoT device and the DL transmission from the BS, UE, or IAB node to the environmental IoT device can be defined or pre-set in advance. For example, as... Figure 22 As shown, the offset between the pre-amplifier DL signal and the DL transmission can also be defined or preset in advance. For example, the offset can be zero. The pre-amplifier DL signal can be a DL type A signal or a DL type D signal carrying control information for DL ​​transmission.

[0447] Option 3) Figure 23This is a diagram illustrating an example (3) of signal forwarding timing according to an embodiment of the present invention. The association between the pre-processing DL signal sent from the BS, UE, or IAB node to the environmental IoT device and the DL transmission from the BS, UE, or IAB node to the environmental IoT device can be defined or pre-set in advance. For example, as... Figure 23 As shown, the offset between the pre-set DL signal and the DL transmission can also be defined or preset in advance. For example, the offset can be zero. The pre-set DL signal can be a predefined sequence indicating the start of the DL transmission.

[0448] In addition, the end time of DL transmission from the BS, UE, or IAB node to the environmental IoT device can be determined as follows.

[0449] Option 1) Figure 24 This is a diagram illustrating an example (4) of the timing of signal forwarding according to an embodiment of the present invention. Figure 24 As shown, the duration of DL transmission from the BS, UE, or IAB node to the environmental IoT device can be explicitly notified via a pre-signal sent from the BS, UE, or IAB node. The pre-signal can be either a DL type A signal or a DL type D signal carrying control information for DL ​​transmission.

[0450] Option 2) Figure 25 This is a diagram illustrating an example (5) of the timing for signal forwarding according to an embodiment of the present invention. Figure 25 As shown, the duration of DL transmission can be predefined or pre-set.

[0451] Option 3) Figure 26 This is a diagram illustrating an example (6) of the timing of signal forwarding according to an embodiment of the present invention. Figure 26 As shown, a predefined sequence can also be sent at the end of the DL transmission to indicate the end of the DL transmission.

[0452] Action 10) The start time of UL transmission from the environmental IoT device to the BS, UE or IAB node can be determined as follows.

[0453] Option 1) Figure 27 This is a diagram illustrating an example (7) of the timing of signal forwarding according to an embodiment of the present invention. Figure 27 As shown, the start time of UL transmission from the environmental IoT device to the BS, UE, or IAB node can be notified via a pre-signal sent from the BS, UE, or IAB node to the environmental IoT device. The pre-signal can be a DL type A signal or a DL type D signal carrying control information transmitted by the UL.

[0454] Option 2) Figure 28This is a diagram illustrating an example (8) of signal forwarding timing according to an embodiment of the present invention. The association between the pre-transmission DL signal sent from the BS, UE, or IAB node to the environmental IoT device and the UL transmission sent from the environmental IoT device to the BS, UE, or IAB node can be defined or pre-set in advance. For example, as... Figure 28 As shown, the offset between the pre-amplifier DL signal and the UL transmission can also be defined or preset in advance. For example, the offset can be zero. The pre-amplifier DL signal can be a DL type A signal or a DL type D signal carrying control information transmitted by the UL. In addition, the pre-amplifier DL signal can also be a predefined sequence.

[0455] Option 3) allows setting a time window. Within this time window, the environmental IoT device can determine the start time for UL transmission.

[0456] Figure 29 This is a diagram illustrating an example (9) of the signal forwarding timing according to an embodiment of the present invention. Figure 30 This is a diagram illustrating an example (10) of the signal forwarding timing according to an embodiment of the present invention. Figure 31 This is a diagram illustrating an example (11) of the signal forwarding timing according to an embodiment of the present invention.

[0457] like Figure 29 As shown, the start time of the time window can be defined as the minimum offset between the pre-transmission DL signal sent from the BS, UE, or IAB node to the environmental IoT device and the UL transmission. The end time of the time window can be defined as the maximum offset between the pre-transmission DL signal sent from the BS, UE, or IAB node to the environmental IoT device and the UL transmission. The pre-transmission DL signal can be a DL type A signal or a DL type D signal carrying control information transmitted by the UL. Furthermore, the pre-transmission DL signal can also be a predefined sequence.

[0458] like Figure 30 As shown, when UL transmission begins from a predefined UL sequence sent from an environmental IoT device to a BS, UE, or IAB node, the BS, UE, or IAB node can also receive the sequence and recognize the start of UL transmission.

[0459] like Figure 31 As shown, when UL transmission begins after a predefined or pre-set offset following the transmission of a predefined UL sequence from the IoT device in the environment to the BS, UE, or IAB node, the BS, UE, or IAB node can receive the sequence and recognize the start of UL transmission.

[0460] In addition, the end time of DL transmission from the BS, UE, or IAB node to the environmental IoT device can be determined as follows.

[0461] Option 1) Figure 32 This is a diagram illustrating an example (12) of the timing of signal forwarding according to an embodiment of the present invention. Figure 32 As shown, the duration of UL transmission from the BS, UE, or IAB node to the environmental IoT device can be explicitly notified via a pre-signal sent from the BS, UE, or IAB node. The pre-signal can be a DL type A signal or a DL type D signal carrying control information for DL ​​transmission.

[0462] Option 2) Figure 33 This is a diagram illustrating an example (13) of the timing of signal forwarding according to an embodiment of the present invention. Figure 33 As shown, the duration of UL transmission can be predefined or pre-set.

[0463] Option 3) Figure 34 This is a diagram illustrating an example (14) of the timing of signal forwarding according to an embodiment of the present invention. Figure 34 As shown, a predefined sequence can also be sent at the end of the UL transmission to indicate the end of the UL transmission.

[0464] The capabilities of UE or IAB nodes can be defined as shown below.

[0465] 1) Does it support sending to and / or receiving from environmental IoT devices?

[0466] 2) Does it support the device types of IoT devices in the target environment (device A, device B, and device C mentioned above)?

[0467] 3) Whether it supports modulation methods for transmitting to and / or receiving from environmental IoT devices.

[0468] 4) Whether it supports waveforms sent to and / or received from environmental IoT devices.

[0469] 5) Whether it supports encoding methods for sending to and / or receiving from environmental IoT devices.

[0470] The capabilities of IoT devices in the environment can also be defined as shown below.

[0471] 1) Does it support the device types of environmental IoT devices (Device A, Device B, Device C mentioned above)?

[0472] 2) Whether it supports modulation methods for transmitting to and / or receiving from environmental IoT devices.

[0473] 3) Whether waveforms for sending to and / or receiving from environmental IoT devices are supported.

[0474] 4) Whether it supports encoding methods for sending to and / or receiving from environmental IoT devices.

[0475] The embodiments of the present invention can also be applied only to situations where the corresponding capabilities are supported by UE, IAB or environmental IoT devices and / or activated by corresponding high-level parameters.

[0476] Through the above embodiments, the base station, UE, or IAB node can send DL signals to the environmental IoT device and receive UL signals from the environmental IoT device.

[0477] That is, in wireless communication systems, signals suitable for Ambient Internet of Things (IoT) can be generated.

[0478] (Device structure)

[0479] Next, an example of the functional structure of the base station 10 and terminal 20 performing the processes and actions described above will be explained. The base station 10 and terminal 20 include the functions implemented in the above embodiments. However, the base station 10 and terminal 20 may each have only a portion of the functions described in the embodiments.

[0480] <Base Station 10>

[0481] Figure 35 This is a diagram illustrating an example of the functional structure of base station 10 in an embodiment of the present invention. For example... Figure 35 As shown, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130 and a control unit 140. Figure 35 The functional structure shown is only one example. As long as the actions involved in the embodiments of the present invention can be performed, the functional distinctions and names of the functional parts can be arbitrary.

[0482] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 and wirelessly transmitting the signal. Furthermore, the transmitting unit 110 transmits inter-network node messages to other network nodes. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 and obtaining, for example, higher-level information from the received signals. Furthermore, the transmitting unit 110 has the function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, etc., to the terminal 20. Furthermore, the receiving unit 120 receives inter-network node messages from other network nodes.

[0483] The setting unit 130 stores preset setting information and various setting information sent to the terminal 20. The content of the setting information includes, for example, information related to communication with IoT devices in the environment.

[0484] The control unit 140 performs control to implement the functions described in the embodiment. Additionally, as described in the embodiment, the control unit 140 performs control related to communication with the environmental IoT device. Alternatively, the signal transmission-related functions of the control unit 140 may be included in the transmitting unit 110, and the signal reception-related functions of the control unit 140 may be included in the receiving unit 120.

[0485] Terminal 20

[0486] Figure 36 This is a diagram illustrating an example of the functional structure of terminal 20 in an embodiment of the present invention. For example... Figure 36 As shown, the terminal 20 includes a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. Figure 36 The functional structure shown is only one example. As long as the actions involved in the embodiments of the present invention can be performed, the functional distinctions and names of the functional parts can be arbitrary.

[0487] The transmitting unit 210 generates a transmission signal based on the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and obtains higher-layer signals from the received physical layer signals. Furthermore, the receiving unit 220 has the function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, etc., transmitted from the base station 10. For example, as D2D communication, the transmitting unit 210 transmits PSCCH (Physical Sidelink Control Channel), PSSCH (Physical Sidelink Shared Channel), PSDCH (Physical Sidelink Discovery Channel), PSBCH (Physical Sidelink Broadcast Channel), etc., to other terminals 20, and the receiving unit 220 receives PSCCH, PSSCH, PSDCH, or PSBCH from other terminals 20.

[0488] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. In addition, the setting unit 230 also stores pre-set setting information. The content of the setting information includes, for example, information related to communication with IoT devices in the environment.

[0489] The control unit 240 performs control to implement the functions described in the embodiment. Additionally, as described in the embodiment, the control unit 240 performs control related to communication with the environmental IoT device. Alternatively, the signal transmission-related functions of the control unit 240 may be included in the transmitting unit 210, and the signal reception-related functions of the control unit 240 may be included in the receiving unit 220.

[0490] (Hardware structure)

[0491] The block diagrams used in the description of the above embodiments ( Figure 35 and Figure 36 The diagram illustrates blocks organized by function. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Furthermore, there are no particular limitations on the implementation method of each functional block. That is, each functional block can be implemented using a single device that is physically or logically combined, or by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. Functional blocks can also be implemented by combining software within the aforementioned single or multiple devices.

[0492] The functions include judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, the functional block (component) that enables transmission is called the transmitting unit or transmitter. In short, as mentioned above, there are no particular limitations on the implementation method.

[0493] For example, in one embodiment of this disclosure, the base station 10, terminal 20, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 37 This is a diagram illustrating an example of the hardware structure of a base station 10 and a terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 may also be configured as a computer device that physically includes a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

[0494] Additionally, in the following description, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware structure of base station 10 and terminal 20 can be configured to include one or more of the devices shown in the figures, or it can be configured to not include any of them.

[0495] The functions of base station 10 and terminal 20 are implemented by reading predetermined software (program) into hardware such as processor 1001 and storage device 1002, so that processor 1001 performs calculations and controls the communication of communication device 1004 or controls at least one of reading and writing data in storage device 1002 and auxiliary storage device 1003.

[0496] The processor 1001 controls the computer as a whole by instructing the operating system to operate. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, the control unit 140 and control unit 240 described above can also be implemented using the processor 1001.

[0497] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage devices 1003 and communication devices 1004, and performs various processes accordingly. As a program, a program is used that causes the computer to perform at least a portion of the actions described in the above embodiments. For example, Figure 35 The control unit 140 of the base station 10 shown can also be implemented by a control program stored in the storage device 1002 and operated in the processor 1001. And, for example, Figure 36 The control unit 240 of the terminal 20 shown can also be implemented by a control program stored in the storage device 1002 and operated in the processor 1001. Although it has been described that the various processes described above are executed by one processor 1001, the various processes described above can also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 can also be implemented by more than one chip. In addition, the program can also be sent from the network via a telecommunications line.

[0498] Storage device 1002 is a computer-readable recording medium, and may be composed of at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. Storage device 1002 may also be referred to as a register, cache, main memory (main storage device), etc. Storage device 1002 can store programs (program code), software modules, etc., that are executable for implementing the communication method according to one embodiment of this disclosure.

[0499] The auxiliary storage device 1003 is a computer-readable recording medium, such as at least one of the following: CD-ROM (CompactDisc ROM) or other optical discs, hard disks, floppy disks, magneto-optical discs (e.g., compact discs, digital multifunction discs, Blu-ray discs, smart cards, flash memory (e.g., cards, sticks, key drives), floppy disks, magnetic stripes, etc. The aforementioned storage medium may, for example, be a database, server, or other suitable media that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0500] The communication device 1004 is hardware (transceiver) used for communication between computers via at least one of a wired network and a wireless network. It may also be referred to as a network device, network controller, network interface card (NIC), communication module, etc. The communication device 1004 may, for example, be configured to include a high-frequency switch, duplexer, filter, frequency synthesizer, etc., to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, transceiver antennas, amplifiers, transceiver units, transmission path interfaces, etc., can also be implemented using the communication device 1004. The transceiver unit may also be physically or logically separated into a transmitting unit and a receiving unit.

[0501] Input device 1005 is an input device that accepts input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, LED, etc.). Alternatively, input device 1005 and output device 1006 can also be integrated (e.g., a touch panel).

[0502] Furthermore, the processor 1001 and storage device 1002, among other devices, are connected via a bus 1007 for communicating information. The bus 1007 can be a single bus or can be composed of different buses between devices.

[0503] Furthermore, the base station 10 and the terminal 20 can be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or a FPGA (Field Programmable Gate Array), and can also use this hardware to implement part or all of the functional blocks. For example, the processor 1001 can also be implemented using at least one of these hardware components.

[0504] Figure 38 An example of the structure of vehicle 2001 is shown. For example... Figure 38 As shown, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a gearshift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021-2029, an information service unit 2012, and a communication module 2013. The various forms / implementations described in this disclosure can also be applied to communication devices mounted on the vehicle 2001, for example, to the communication module 2013.

[0505] The drive unit 2002 may be composed, for example, an engine, a motor, or a hybrid power system of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a steering wheel) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

[0506] The electronic control unit 2010 consists of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (I / O port) 2033. Signals from various sensors 2021 to 2029 of the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 can also be referred to as an ECU (Electronic Control Unit).

[0507] The signals from various sensors 2021 to 2029 include current signals from current sensor 2021 that monitors motor current, speed signals of the front or rear wheels obtained by speed sensor 2022, air pressure signals of the front or rear wheels obtained by air pressure sensor 2023, vehicle speed signals obtained by vehicle speed sensor 2024, acceleration signals obtained by acceleration sensor 2025, accelerator pedal input signals obtained by accelerator pedal sensor 2029, brake pedal input signals obtained by brake pedal sensor 2026, gear lever operation signals obtained by gear lever sensor 2027, and detection signals obtained by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0508] The Information Service Unit 2012 comprises various devices such as a car navigation system, audio system, speakers, television, and radio, used to provide (output) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The Information Service Unit 2012 uses information obtained from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001. The Information Service Unit 2012 may include input devices that accept input from external sources (such as keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.), and may also include output devices that perform output to external sources (such as displays, speakers, LED lights, touch panels, etc.).

[0509] The Driver Assistance System 2030 comprises various devices used to prevent accidents or reduce driver workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning devices (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyroscope systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. Furthermore, the Driver Assistance System 2030 transmits and receives various information via the communication module 2013 to achieve driver assistance or autonomous driving functions.

[0510] The communication module 2013 can communicate with the microprocessor 2031 and the components of the vehicle 2001 via the communication port. For example, the communication module 2013 can send and receive data with the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gear shift lever 2006, front wheel 2007, rear wheel 2008, axle 2009, microprocessor 2031 in the electronic control unit 2010, memory (ROM, RAM) 2032, and sensors 2021 to 29 in the vehicle 2001 via the communication port 2033.

[0511] The communication module 2013, controlled by the microprocessor 2031 of the electronic control unit 2010, is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information with external devices via wireless communication. The communication module 2013 can be located inside or outside the electronic control unit 2010. External devices can be, for example, base stations, mobile stations, etc.

[0512] The communication module 2013 can also wirelessly transmit at least one of the signals input to the electronic control unit 2010 from the various sensors 2021-2028 described above, the information obtained based on those signals, and the information obtained via the information service unit 2012 based on input from an external source (user) to an external device. The electronic control unit 2010, the various sensors 2021-2028, and the information service unit 2012 can also be referred to as input units that receive input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the aforementioned inputs.

[0513] The communication module 2013 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) sent from external devices and displays it on the information service unit 2012 of the vehicle 2001. The information service unit 2012 can also be referred to as an output unit (for example, an output unit that outputs information to devices such as displays and speakers based on the PDSCH received by the communication module 2013 (or data / information decoded from the PDSCH)). Furthermore, the communication module 2013 stores the various information received from external devices in a memory 2032 available to the microprocessor 2031. The microprocessor 2031 can also control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gearshift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., of the vehicle 2001 based on the information stored in the memory 2032.

[0514] (Summary of implementation methods)

[0515] As described above, according to an embodiment of the present invention, a communication device is provided, wherein the communication device comprises: a transmitting unit that transmits to an environmental IoT (Internet of Things) device at least one of a first DL (Downlink) signal containing at least one of control information and data, and at least one of a second DL signal used by the environmental IoT device in backscattering; and a receiving unit that receives the second DL signal backscattered by the environmental IoT device as a UL (Uplink) signal.

[0516] Through the above structure, base stations, UEs, or IAB nodes can send DL signals to environmental IoT devices and receive UL signals from environmental IoT devices. That is, signals suitable for environmental IoT (Ambient Internet of Things) can be generated in the wireless communication system.

[0517] The transmitting unit can also send a third DL signal, which serves as a power source, to the environmental IoT device. Through this structure, the base station, UE, or IAB node can send DL signals to the environmental IoT device and receive UL signals from the environmental IoT device.

[0518] The transmitting unit can also apply different waveforms to the first DL signal and the second DL signal. Through this structure, the base station, UE, or IAB node can transmit DL signals to environmental IoT devices and receive UL signals from environmental IoT devices.

[0519] The transmitting unit may also transmit the first DL signal to the environmental IoT device in a manner that serves as a power source. Through this structure, the base station, UE, or IAB node can transmit DL signals to the environmental IoT device and receive UL signals from the environmental IoT device.

[0520] The transmitting unit may also transmit the second DL signal to the environmental IoT device in a manner that serves as a power source. Through this structure, the base station, UE, or IAB node can transmit DL signals to the environmental IoT device and receive UL signals from the environmental IoT device.

[0521] In addition, according to an embodiment of the present invention, a communication method is provided, wherein a communication device performs the following steps: sending to an environmental IoT (Internet of Things) device a first DL (Downlink) signal containing at least one of control information and data, and at least one of a second DL signal used by the environmental IoT device in backscattering; receiving the second DL signal backscattered by the environmental IoT device as a UL (Uplink) signal.

[0522] Through the above structure, base stations, UEs, or IAB nodes can send DL signals to environmental IoT devices and receive UL signals from environmental IoT devices. That is, signals suitable for environmental IoT (Ambient Internet of Things) can be generated in the wireless communication system.

[0523] (Supplement to the implementation method)

[0524] The embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments. Those skilled in the art should understand various modifications, alterations, substitutions, and replacements. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these values ​​are merely examples, and any appropriate values ​​may be used. The distinctions between items in the above description are not essential to the present invention. Items described in two or more items may be combined as needed, and items described in one item may be applied to items described in another item (as long as there is no contradiction). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical components. Multiple functional units may be operated by a single physical component, or a single functional unit may be operated by multiple physical components. Regarding the processing described in the embodiments, the order of processing may be interchanged unless there is a contradiction. For ease of explanation, a functional block diagram is used to illustrate the base station 10 and terminal 20, but such a device may also be implemented by hardware, software, or a combination thereof. The software operating according to the embodiments of the present invention via the processor of the base station 10 and the software operating according to the embodiments of the present invention via the processor of the terminal 20 may also be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server and other suitable storage media, respectively.

[0525] Furthermore, the notification of information is not limited to the forms / implementations described in this disclosure, and other methods may also be used. For example, the notification of information may be implemented through physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. In addition, RRC signaling may also be referred to as an RRC message, for example, it may be an RRC connection setup message, an RRC connection reconfiguration message, etc.

[0526] The various forms / implementations described in this disclosure can also be applied to systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The system may include at least one of 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), other suitable systems, and next-generation systems based on, modified, created, or defined by these systems. Furthermore, multiple systems may be combined (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.).

[0527] The processing procedures, timing, and flow of the various forms / implementations described in this specification may be rearranged in order, provided there is no contradiction. For example, the elements of various steps are indicated using an illustrative order for the methods described in this disclosure, but are not limited to the specific order indicated.

[0528] In this specification, certain actions performed by base station 10 may sometimes also be performed by its upper node, depending on the circumstances. In a network consisting of one or more network nodes having base station 10, it is obvious that various actions performed to communicate with terminal 20 can be performed by at least one of base station 10 and other network nodes besides base station 10 (e.g., considering MME or S-GW, but not limited to these). The above example illustrates the case where there is one other network node besides base station 10, but other network nodes can also be a combination of multiple other network nodes (e.g., MME and S-GW).

[0529] The information or signals described in this disclosure can be output from a higher (or lower) layer to a lower (or higher) layer. They can also be input or output via multiple network nodes.

[0530] Input or output information can be stored in a specific location (e.g., memory) or managed using a management table. Input or output information can be overwritten, updated, or appended. Output information can also be deleted. Input information can also be sent to other devices.

[0531] The determination in this disclosure can be made by a value represented by 1 bit (0 or 1), by a Boolean value (Boolean: true or false), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value).

[0532] Software, whether called software, firmware, middleware, microcode, hardware description language, or by other names, should be broadly interpreted as referring to commands, command sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0533] In addition, software, commands, and information can also be sent and received via transmission media. For example, when software is sent from a webpage, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of transmission media.

[0534] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, the data, commands, instructions, information, signals, bits, symbols, chips, etc., that may be involved in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination of these.

[0535] Furthermore, the terms used in this disclosure and those necessary for understanding this disclosure may be replaced with terms that have the same or similar meanings. For example, at least one of the channel and symbol may also be a signal (signaling). Additionally, a signal may also be a message. Furthermore, a component carrier (CC) may also be referred to as carrier frequency, cell, frequency carrier, etc.

[0536] The terms “system” and “network” as used in this disclosure are used interchangeably.

[0537] Furthermore, the information, parameters, etc., described in this disclosure may be represented using absolute values, relative values ​​to predetermined values, or other corresponding information. For example, wireless resources may also be indicated using indexes.

[0538] The names used for the above parameters are non-limiting in any respect. Furthermore, the formulas, etc., using these parameters sometimes differ from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by all appropriate names, therefore the various names assigned to these channels and information elements are non-limiting in any respect.

[0539] In this disclosure, the terms "base station (BS)," "wireless base station," "base station device," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" are used interchangeably. Sometimes, terms such as macro cell, small cell, femtocell, and picocell are also used to refer to base stations.

[0540] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, its coverage area can be divided into several smaller areas, each of which can provide communication services through a base station subsystem (e.g., a small indoor base station RRH: Remote Radio Head). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

[0541] In this disclosure, the base station sending information to the terminal can also be replaced by the base station instructing the terminal on information-based control / actions.

[0542] In this disclosure, the terms "Mobile Station (MS)," "User Terminal (user terminal)," "User Equipment (UE)," and "Terminal" can be used interchangeably.

[0543] For mobile stations, those skilled in the art sometimes also use the following terms: subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handheld device, user agent, mobile client, client, or some other appropriate terms.

[0544] At least one of the base station and the mobile station can also be referred to as a transmitting device, a receiving device, a communication device, etc. Furthermore, at least one of the base station and the mobile station can also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to an object capable of movement, with arbitrary speed. This also includes situations where the mobile body is stationary. Examples of mobile bodies include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, shovel cars, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, rear cars, rickshaws, ships and other watercraft, airplanes, rockets, artificial satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted on them. Additionally, the mobile body can also be a mobile body that moves autonomously based on operating commands. This can be a means of transportation (such as a car, airplane, etc.), a mobile entity that moves unmanned (such as a drone, self-driving car, etc.), or a robot (humanized or unmanned). Furthermore, at least one of the base station and mobile station may also include devices that do not necessarily move during communication. For example, at least one of the base station and mobile station may be an IoT (Internet of Things) device such as a sensor.

[0545] Furthermore, the base station in this disclosure can also be replaced by a user terminal. For example, the communication between the base station and the user terminal can be replaced by communication between multiple terminals 20 (e.g., D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.), and various forms / implementations of this disclosure can also be applied. In this case, the terminal 20 can also be configured to have the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be replaced with terms corresponding to inter-terminal communication (e.g., "side"). For example, uplink channel, downlink channel, etc., can also be replaced with side channel.

[0546] Similarly, the user terminal in this disclosure can also be replaced by a base station. In this case, the base station can also be configured to have the functions of the aforementioned user terminal.

[0547] The terms "determining" and "determining" as used in this disclosure sometimes encompass a variety of actions. For example, "determining" or "determining" may include actions such as judging, calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or other data structure), and ascertaining, which are considered as actions of "determining" or "determining." Furthermore, "determining" or "determining" may include actions such as receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, and accessing (e.g., accessing data in memory), which are considered as actions of "determining" or "determining." Additionally, "determining" or "determining" may include actions such as resolving, selecting, choosing, establishing, and comparing, which are considered as actions of "determining" or "determining." That is, "judgment" and "decision" can include matters that are considered as having been "judged" or "decided". In addition, "judgment (decision)" can also be replaced by "assuming", "expecting", "considering", etc.

[0548] The terms “connected,” “coupled,” or any variations thereof are intended to indicate any direct or indirect connection or combination between two or more elements, including cases where there is one or more intermediate elements between the two elements that are “connected” or “coupled.” The combination or connection between elements can be physical, logical, or a combination of these. For example, “access” can be used instead of “connected.” In the context of this disclosure, it can be understood that two elements are “connected” or “coupled” to each other using at least one of one or more wires, cables, and printed electrical connections, and, as some non-limiting and non-inclusive examples, using electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, and light (including both visible and invisible regions) to “connect” or “couple” to each other.

[0549] The reference signal can be simply called RS (Reference Signal), or, depending on the standard applied, pilot.

[0550] As used in this disclosure, the word "based on" does not mean "based on only" unless otherwise expressly stated. In other words, the word "based on" means both "based on only" and "based on at least".

[0551] Any reference to elements using the designations "first," "second," etc., as used in this disclosure does not necessarily limit the number or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to a first element and a second element does not imply that only two elements can be used, or that in any form the first element must precede the second element.

[0552] Alternatively, the "unit" in the structure of the above devices can be replaced with "section", "circuit", "equipment", etc.

[0553] When the terms "include," "including," and their variations are used in this disclosure, these terms, like the term "comprising," imply inclusion. Furthermore, the term "or" as used in this disclosure does not refer to XOR.

[0554] A radio frame can consist of one or more frames in the time domain. In the time domain, one or more frames can be called subframes. A subframe can also consist of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology).

[0555] A parameter set can be communication parameters applied to at least one of the transmission and reception of a signal or channel. For example, a parameter set can represent at least one of the following: Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transceiver in the frequency domain, and specific windowing processing performed by the transceiver in the time domain.

[0556] In the time domain, a time slot can be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A time slot can be a time unit based on a set of parameters.

[0557] A time slot can contain multiple mini-time slots. Each mini-time slot can consist of one or more symbols in the time domain. Furthermore, a mini-time slot can also be called a sub-time slot. A mini-time slot can consist of fewer symbols than a time slot. PDSCH (or PUSCH) transmitted in time units larger than mini-time slots can be called PDSCH (or PUSCH) mapping type (type) A. PDSCH (or PUSCH) transmitted using mini-time slots can be called PDSCH (or PUSCH) mapping type (type) B.

[0558] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can each be referred to by other corresponding names.

[0559] For example, a subframe can be called a Transmission Time Interval (TTI), multiple consecutive subframes can also be called a TTI, and a time slot or a mini-time slot can also be called a TTI. That is, at least one of a subframe and a TTI can be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI can also be called a time slot, mini-time slot, etc., instead of a subframe.

[0560] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules the allocation of radio resources (bandwidth, transmit power, etc., available to each terminal 20) in units of TTI. However, the definition of TTI is not limited to this.

[0561] The Time Interval (TTI) can be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., or it can be a processing unit such as scheduling or link adaptation. Furthermore, when a TTI is given, the actual time interval (e.g., the number of symbols) that the transmission block, code block, codeword, etc., are mapped to can be shorter than that TTI.

[0562] In addition, when one time slot or one mini time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini time slot) can also be the minimum time unit for scheduling. Furthermore, the number of time slots (mini time slots) constituting the minimum time unit for scheduling can also be controlled.

[0563] A TTI with a duration of 1ms can also be called a normal TTI (TTI in LTE Rel.8-12), a long TTI, a normal subframe, a long subframe, or a time slot. A TTI shorter than a normal TTI can also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini time slot, a sub-time slot, or a time slot.

[0564] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) can be understood as a TTI with a duration of more than 1ms, and a short TTI (e.g., a shortened TTI, etc.) can be understood as a TTI with a duration of less than a long TTI but more than 1ms.

[0565] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can contain one or more consecutive subcarriers. The number of subcarriers contained in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers contained in an RB can also be determined based on the parameter set.

[0566] Furthermore, the temporal domain of an RB can contain one or more symbols, which can be a single time slot, a single mini-time slot, a single subframe, or the length of a single TTI. A single TTI, a single subframe, etc., can each be composed of one or more resource blocks.

[0567] In addition, one or more RBs can also be called Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0568] Furthermore, a resource block can consist of one or more resource elements (REs). For example, one RE can be a radio resource area consisting of one subcarrier and one symbol.

[0569] The Bandwidth Part (BWP) (also known as partial bandwidth, etc.) can also represent a subset of contiguous common resource blocks (RBs) used for a certain parameter set in a certain carrier. Here, common RBs can be determined by indexing RBs based on a common reference point of that carrier. PRBs can be defined and numbered within a BWP.

[0570] A BWP can include a UL BWP and a DL BWP. One or more BWPs can be set for a UE within a single carrier.

[0571] At least one of the configured BWPs can be active, and it is not necessary to assume that the UE will transmit or receive predetermined signals / channels outside of the active BWP. In addition, the terms "cell" and "carrier" in this disclosure can be replaced by "BWP".

[0572] The structures of radio frames, subframes, time slots, mini-time slots, and symbols described above are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained in a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other structures can be varied in many ways.

[0573] In this disclosure, for example, in cases where articles are added through translation, such as in English (e.g., a, an, and the), this disclosure also includes cases where the noun following these articles is in a plural form.

[0574] In this disclosure, the phrase "A and B are different" can mean "A and B are not the same." Additionally, this phrase can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0575] The various forms / implementations described in this disclosure can be used individually, in combination, or switched between each other during execution. Furthermore, the notification of predetermined information (e.g., a "It is X" notification) is not limited to being explicit, but can also be implicit (e.g., not notifying the predetermined information).

[0576] The present disclosure has been described in detail above, but it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the present disclosure is for illustrative purposes only and is not intended to be limiting.

[0577] Label Explanation

[0578] 10 base stations

[0579] 110 Dispatch Department

[0580] 120 Receiving Department

[0581] 130 Setting Department

[0582] 140 Control Department

[0583] 20 terminals

[0584] 210 Sending Department

[0585] 220 Receiving Department

[0586] 230 Setting Department

[0587] 240 Control Department

[0588] 30-core network

[0589] 1001 processor

[0590] 1002 Storage device

[0591] 1003 Auxiliary storage device

[0592] 1004 Communication device

[0593] 1005 Input Device

[0594] 1006 Output Device

[0595] Vehicle 2001

[0596] 2002 Drive Unit

[0597] 2003 Steering Unit

[0598] 2004 Accelerator Pedal

[0599] 2005 Brake Pedal

[0600] 2006 gearshift lever

[0601] 2007 front wheel

[0602] 2008 rear wheel

[0603] 2009 axle

[0604] 2010 Electronic Control Department

[0605] 2012 Information Service Department

[0606] 2013 Communication Module

[0607] 2021 Current Sensor

[0608] 2022 Speed ​​Sensor

[0609] 2023 Barometric Pressure Sensor

[0610] 2024 vehicle speed sensor

[0611] 2025 Accelerometer

[0612] 2026 Brake Pedal Sensor

[0613] 2027 Gearshift sensor

[0614] 2028 Object Detection Sensor

[0615] 2029 Accelerator Pedal Sensor

[0616] 2030 Driver Assistance Systems Department

[0617] 2031 microprocessor

[0618] 2032 Memory (ROM, RAM)

[0619] 2033 Communication Port (IO Port)

Claims

1. A communication device, wherein, The communication device has: The transmitting unit transmits to an environmental IoT device at least one of a first DL signal containing at least one of control information and data, and at least one of a second DL signal used by the environmental IoT device in backscattering, wherein the environmental IoT device refers to an environmental Internet of Things device, and the first DL signal refers to a first downlink signal; and The receiving unit receives the second DL signal backscattered by the IoT device in the environment, and uses it as the UL signal, i.e., the uplink signal.

2. The communication device according to claim 1, wherein, The transmitting unit sends a third DL signal, which becomes a power source, to the environmental IoT device.

3. The communication device according to claim 1, wherein, The transmitting unit applies different waveforms to the first DL signal and the second DL signal.

4. The communication device according to claim 1, wherein, The transmitting unit sends the first DL signal to the environmental IoT device in a manner that serves as a power source.

5. The communication device according to claim 1, wherein, The transmitting unit sends the second DL signal to the environmental IoT device in a manner that serves as a power source.

6. A communication method, wherein, The following steps are performed by the communication device: Sending at least one of a first DL signal containing at least one of control information and data, and at least one of a second DL signal used by the environmental IoT device in backscattering, wherein the environmental IoT device refers to an environmental Internet of Things device, and the first DL signal refers to a first downlink signal; and sending at least one of the following to an environmental IoT device: a first DL signal containing at least one of control information and data; and sending at least one of the following to an environmental IoT device: a first downlink signal; The second DL signal, after being backscattered by the IoT device in the environment, is received as the UL signal, i.e., the uplink signal.

Images