Wireless communication apparatus and communication method

Abstract

To appropriately determine parameters for resource selection within a resource pool in a communication system including A-IoT.SOLUTION: A wireless communication apparatus that communicates with a device having lower complexity than an NB-IoT device includes a receiving unit that receives resource pool information from a network indicating a resource pool for R2D transmission / D2R reception / CW transmission with the device, and a control unit that determines parameters for selecting resources for the R2D transmission / D2R reception / CW transmission within the resource pool.SELECTED DRAWING: Figure 51

Description

[Technical Field]

[0001] The present disclosure relates to a wireless communication device and a communication method. [Background technology]

[0002] For NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies are being considered that meet the requirements of a large-capacity system, high-speed data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, and low power consumption (see, for example, Non-Patent Document 1).

[0003] Furthermore, Release 18 (Rel-18) of 3GPP (registered trademark) is considering Ambient Internet of Things (A-IoT) (see, for example, Non-Patent Document 2). Ambient IoT targets devices with extremely simple configurations for low-end IoT applications that operate with extremely low power consumption. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 38.300 V17.3.0 (2022-12) [Non-patent document 2] “Revised SID on Ambient IoT”, RP-232404, 3GPP TSG RAN Meeting #101, September 2023 [Non-patent document 3] 3GPP TR 38.848 V1.0.0 (2023-09) [Non-patent document 4] 3GPP TS 36.211 V16.8.0 (2023-09) [Non-patent document 5] “Study on solutions for Ambient IoT (Internet of Things) in NR”, RP-234058, 3GPP TSG RAN Meeting #102, December 2023 Summary of the Invention

[0005] In A-IoT from Rel-19 onwards, a configuration called "Topology 2" may be used in which an A-IoT device communicates with a base station via an intermediate UE (also called an "intermediate node" or "int.UE (intermediate UE)") (see Section 4.2.1.2 of Non-Patent Document 3). In this Topology 2, the intermediate UE performs transmission (TX) and reception (RX) operations between the A-IoT device and the base station.

[0006] In this topology 2, if the network attempts to dynamically allocate resources for transmission and reception of intermediate UEs, a large signaling overhead will occur. Therefore, in order to reduce this overhead, the network can provide resource pool information to the intermediate UEs in advance, allowing the intermediate UEs to autonomously determine the resources for each transmission and reception in topology 2.

[0007] However, there are still unresolved issues regarding the determination of parameters for resource selection within a resource pool, and further study is required.

[0008] One aspect of the present disclosure contributes to providing a wireless communication device and a communication method that can appropriately determine parameters for resource selection within a resource pool in a communication system including A-IoT.

[0009] A wireless communication device according to one embodiment of the present disclosure is a wireless communication device that communicates with a device of lower complexity than an NB-IoT (Narrow Band Internet of Things) device, and includes: a receiving unit that receives, from a network, resource pool information indicating a resource pool for R2D (reader to device) transmission / D2R (device to reader) reception / CW (Carrier Wave) transmission between the device; and a control unit that determines parameters for selecting resources for the R2D transmission / D2R reception / CW transmission within the resource pool. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure. [Figure 2] FIG. 1 is a diagram illustrating Topology 1. [Figure 3] FIG. 10 is a diagram illustrating Topology 2. [Figure 4] FIG. 10 is a diagram illustrating topology 3 in DL support. [Figure 5] FIG. 10 is a diagram illustrating Topology 3 in UL support. [Figure 6] FIG. 10 is a diagram illustrating Topology 4. [Figure 7] FIG. 1 is a diagram illustrating backscatter transmission. [Figure 8] 1A and 1B are diagrams illustrating examples of candidate topologies for CW / R2D / D2R transmission in Topology 1. [Figure 9] FIG. 10 is a diagram illustrating an example of a candidate topology for CW / R2D / D2R transmission in topology 2. [Figure 10] FIG. 10 is a diagram illustrating an example of the DT case in topology 1. [Figure 11] FIG. 1 is a diagram illustrating an example of the DO-DTT case in topology 1. [Figure 12] FIG. 10 is a diagram illustrating an example of the DT case in topology 2. [Figure 13] FIG. 10 is a diagram illustrating an example of the DO-DTT case in topology 2. [Figure 14] FIG. 1 is a diagram illustrating an example of cooperation between LTE and NR. [Figure 15] FIG. 10 is a diagram illustrating an example of power sharing. [Figure 16] FIG. 10 illustrates an example of periodic generation of a resource pool. [Figure 17] FIG. 1 illustrates an example of resource pools that are contiguous in the time domain and in the frequency domain. [Figure 18] FIG. 1 illustrates an example of resource pools that are contiguous in the time domain but not in the frequency domain. [Figure 19] FIG. 10 illustrates an example of resource pools that are discontinuous in the time domain but contiguous in the frequency domain. [Figure 20] FIG. 1 illustrates an example of resource pools that are discontinuous in the time domain and discontinuous in the frequency domain. [Figure 21] FIG. 10 is a diagram for explaining the length of a bitmap. [Figure 22] FIG. 10 is a diagram for explaining the length of a bitmap. [Figure 23] FIG. 10 is a diagram for explaining the length of a bitmap. [Figure 24] FIG. 10 is a diagram showing an example of overlap in the DT case. [Figure 25] FIG. 10 is a diagram showing an example of overlap in the case of DO-DTT. [Figure 26] FIG. 25 is a diagram showing an example in which method b-1-1 is applied to the case shown in FIG. 24. [Figure 27] FIG. 25 is a diagram showing an example in which method b-1-2 is applied to the case shown in FIG. 24. [Figure 28] FIG. 25 is a diagram showing an example in which method b-1-3 is applied to the case shown in FIG. 24. [Figure 29] FIG. 10 is a diagram showing an example of overlap in the DT case. [Figure 30] FIG. 10 is a diagram showing an example of overlap in the case of DO-DTT. [Figure 31]FIG. 30 is a diagram showing an example in which method b-2-1 is applied to the case shown in FIG. 29. [Figure 32] FIG. 30 is a diagram showing an example in which method b-2-2 is applied to the case shown in FIG. 29. [Figure 33] FIG. 10 is a diagram illustrating an example of simultaneous transmission, Case 1. [Figure 34] FIG. 10 is a diagram illustrating an example of simultaneous transmission, Case 2. [Figure 35] FIG. 10 is a diagram illustrating an example of simultaneous transmission, Case 3. [Figure 36] FIG. 10 is a diagram illustrating an example of simultaneous transmission, Case 4. [Figure 37] FIG. 10 is a diagram showing an example in which Case 1, Option 1 of b-4-3 is applied. [Figure 38] FIG. 10 is a diagram showing an example in which case 1 and option 2 of b-4-3 are applied. [Figure 39] This is a diagram showing an example in which case 1, option 3 of b-4-3 is applied. [Figure 40] FIG. 10 is a diagram showing an example of overlap in b-5. [Figure 41] FIG. 10 is a diagram illustrating an example of overlap processing of b-5-1. [Figure 42] FIG. 10 is a diagram showing an example of overlap processing of a variation of b-5-1. [Figure 43] FIG. 10 is a diagram illustrating an example of overlap processing of b-5-2. [Figure 44] FIG. 10 is a diagram showing an example of overlap in b-6. [Figure 45] FIG. 10 is a diagram illustrating an example of overlap processing of b-6-1. [Figure 46] FIG. 10 is a diagram illustrating an example of overlap processing of b-6-2. [Figure 47] FIG. 10 is a diagram showing an example of overlap processing of variation 2 of b-6-2. [Figure 48] FIG. 10 is a diagram showing an example of overlap in b-7. [Figure 49] FIG. 10 is a diagram illustrating an example of overlap processing of b-7-1. [Figure 50]FIG. 10 is a diagram illustrating an example of overlap processing of b-7-2. [Figure 51] FIG. 2 is a block diagram illustrating an example of a configuration of a base station according to an embodiment of the present disclosure. [Figure 52] FIG. 1 is a block diagram illustrating an example of a configuration of a device according to an embodiment of the present disclosure. [Figure 53] FIG. 2 is a diagram illustrating an example of a hardware configuration of a base station and a device according to an embodiment of the present disclosure. [Figure 54] 1 is a diagram illustrating an example of a configuration of a vehicle according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, an embodiment according to one aspect of the present disclosure will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present disclosure is applied is not limited to the following embodiment.

[0012] In operation of the wireless communication system according to the embodiment of the present disclosure, existing technologies are used as appropriate. The existing technologies are, for example, existing LTE or NR, but are not limited to existing LTE or NR. Furthermore, the term "LTE" as used in this specification has a broad meaning including LTE-Advanced and systems beyond LTE-Advanced, unless otherwise specified.

[0013] Furthermore, in the embodiments of the present disclosure described below, terms used in existing LTE, such as 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), are used. This is for convenience of description, and similar signals, functions, etc. may be referred to by other names. Furthermore, the above-mentioned 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 designated as "NR-".

[0014] Furthermore, in the embodiments of the present disclosure, the duplex method may be a time division duplex (TDD) method, a frequency division duplex (FDD) method, or another method (for example, flexible duplex, etc.).

[0015] Furthermore, in the embodiments of the present disclosure, "configuring" radio parameters, etc. may mean that predetermined values ​​are pre-configured, or that radio parameters notified from a base station, device, terminal, etc. are set.

[0016] (Embodiment) <Wireless communication system> FIG. 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure. As illustrated in FIG. 1, the wireless communication system 1 includes a base station 10 and a device 20. While FIG. 1 illustrates one base station 10 and one device 20, this is merely an example, and multiple base stations and devices may exist. A base station may also be referred to as a BS (Base Station), gNB, or the like. The device 20 may be considered a form of terminal (UE: User Equipment) and may be an ambient IoT device, which is a device with lower complexity than an NB-IoT (Narrow Band Internet of Things) device. The ambient IoT device may also be referred to as an ambient IoT terminal, ambient IoT UE, or the like.

[0017] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the device 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols. The frequency domain may be defined by the number of subcarriers or the number of resource blocks (RBs).

[0018] The base station 10 transmits DL signals such as control information, setting information, and data to the device 20 via DL (Downlink). The base station 10 receives UL signals such as control information, information related to the processing capability of the device 20 (device capability (information) or A-IoT capability (information); for example, capability, device capability, A-IoT capability, A-IoT device capability, etc.), and data from the device 20 via UP (Uplink).

[0019] Channels used for transmitting DL signals include, for example, data channels and control channels. For example, the data channel may include a physical downlink shared channel (PDSCH), and the control channel may include a physical downlink control channel (PDCCH). For example, the base station 10 transmits control information to the device 20 using the PDCCH, and transmits DL data signals using the PDSCH. Note that the PDSCH is an example of a downlink shared channel or a data channel, and the PDCCH is an example of a downlink control channel. The PDCCH may be interpreted as downlink control information (DCI), control information, etc. transmitted in the PDCCH.

[0020] As will be described later, the wireless communication system may include intermediate nodes, assisting nodes, and / or terminals (UEs) (see <Device Types and Topologies> below). Note that, hereinafter, "and / or" may be written simply as " / ".

[0021] The device 20 is a communication device equipped with a wireless communication function, and may be an ambient IoT device (e.g., a sensor, etc.) as described above. Hereinafter, the ambient IoT device will also be referred to as an A-IoT UE.

[0022] The device 20 receives DL signals such as control signals, setting information, and data from the base station 10 via DL, and transmits UL signals such as control signals, capability information of the device 20, and data to the base station 10 via UL.

[0023] Channels used for transmitting UL signals include, for example, data channels and control channels. For example, the data channel may include a Physical Uplink Shared Channel (PUSCH), and the control channel may include a Physical Uplink Control Channel (PUCCH). For example, device 20 transmits control information using the PUCCH and transmits UL data signals using the PUSCH. Note that the PUSCH is an example of an uplink shared channel or a data channel, and the PUCCH is an example of an uplink control channel. Note that the PUSCH or PUCCH may be interpreted as uplink control information (UCI), control information, etc. transmitted in the PUSCH or PUCCH.

[0024] <Ambient IoT> Rel-18 approved the study of ambient IoT (see, for example, Non-Patent Document 2), which is even lower-end than the existing NB-IoT (see, for example, Section 10 of Non-Patent Document 4). Ambient IoT targets ultra-low power consumption and ultra-low complexity devices.

[0025] Ambient IoT may consider, for example, the following deployment scenarios and characteristics for relevant use cases: Indoor or outdoor environment Base station type, e.g., macro / micro / pico cell-based deployment The connectivity topology, e.g., which nodes (e.g., base stations, terminals (UE), relays, and repeaters) communicate with the ambient IoT devices - Duplexing method: TDD or FDD, frequency band: licensed or unlicensed Coexistence with UE and network equipment in frequency bands for existing 3GPP technologies - Traffic assumptions for outgoing / incoming traffic from the device

[0026] Based on the above deployment scenarios and characteristics, for example, the following RAN design targets can be formulated: ·Power consumption Complexity ·coverage Data rate Positioning accuracy

[0027] Based on deployment scenarios appropriate for the relevant use cases, compare and evaluate the feasibility of meeting design targets and identify supporting features.

[0028] <Device type and topology> Based on the results of the study items, TR 38.848 (Non-Patent Document 3) was approved. TR 38.848 considers the following categories of ambient IoT devices: Device A: Device A has no power (energy) storage, no independent signal generation and amplification functions, and performs backscattering transmission. Device B: Device B has power storage, does not have the capability of independent signal generation, and performs backscatter transmission. Device B uses the stored power to amplify the reflected signal. Device C: Device C has power storage, is capable of independent signal generation, and has active RF (radio frequency) components for transmission.

[0029] The complexity of device A is assumed to be about the same as that of RFID (radio frequency identification).

[0030] TR 38.848 defines the following topologies 1 to 4 in an ambient IoT network.

[0031] Figure 2 is a diagram illustrating Topology 1. As shown in Figure 2, Topology 1 is a configuration in which a base station (BS) and an ambient IoT device communicate with each other. The ambient IoT device communicates directly with the base station in both directions.

[0032] Figure 3 is a diagram illustrating Topology 2. As shown in Figure 3, Topology 2 is a configuration in which a base station and an ambient IoT device communicate via an intermediate node. The ambient IoT device performs bidirectional communication with the intermediate node located between the base station and the ambient IoT device. The intermediate node may be, for example, a relay, an integrated access and backhaul (IAB) node, a UE, a repeater, etc.

[0033] Figure 4 is a diagram illustrating Topology 3 in DL assistance. As shown in Figure 4, Topology 3 is a configuration including communication between a base station and an assisting node, communication between the assisting node and an ambient IoT device, and communication between the ambient IoT device and a base station.

[0034] The support node supports DL communication. For example, as shown in Figure 4, the support node receives DL signals from the base station and transmits the received DL signals to the ambient IoT device. For UL communication, the ambient IoT device transmits UL signals directly to the base station.

[0035] Figure 5 is a diagram illustrating Topology 3 in UL support. As shown in Figure 5, Topology 3 is a configuration including communication between a base station and a support node, communication between a support node and an ambient IoT device, and communication between an ambient IoT device and a base station.

[0036] The support node supports UL communication. For example, as shown in Figure 5, the support node receives UL signals from the ambient IoT device and transmits the received UL signals to the base station. For DL ​​communication, the ambient IoT device receives DL signals directly from the base station.

[0037] The supporting nodes shown in Figures 4 and 5 may be, for example, relays, IAB nodes, UEs, repeaters, etc.

[0038] Figure 6 is a diagram illustrating Topology 4. Topology 4 is a configuration in which a UE and an ambient IoT device communicate with each other. The ambient IoT device performs bidirectional communication with the UE. Communication related to Topology 4 may be considered as sidelink (SL) communication.

[0039] In the above topologies 1 to 4, the ambient IoT device may be provided with a carrier wave from another node inside or outside the topology (see Section 4.2.1 of Non-Patent Document 3).

[0040] The wireless communication system 1 (wireless communication network) may include a base station, a support node, an intermediate node, and / or a terminal (UE of Topology 4) in addition to the device 20. In this specification, the base station, the support node, the intermediate node, and the terminal may be read as a network or a (network) node. Also, an A-IoT device may be simply referred to as A-IoT.

[0041] <Backscatter transmission> Base stations, intermediate nodes, support nodes, and other nodes transmit RF signals to ambient IoT devices, which are activated and obtain power from the RF operating fields from the base stations, intermediate nodes, support nodes, and other nodes via inductive coupling.

[0042] The ambient IoT device backscatters and modulates the RF signals received from the base station, intermediate node, support node, and other nodes by switching the reflection coefficient of the device's antenna, and transmits information to the base station, intermediate node, support node, and other nodes.

[0043] FIG. 7 is a diagram illustrating backscatter transmission. FIG. 7 shows an example in which an ambient IoT device performs ON-OFF keying and transmits information. The dashed line area in FIG. 7 indicates an OFF section, which may correspond to the information (bit) "0." A sine wave signal may correspond to the information "1."

[0044] <Rel-19 SID> The Rel-19 SID (Study Item Description) examined solutions necessary and feasible for A-IoT (see Section 4.1 of Non-Patent Document 5). The examined solutions include, for example, determining which functions, procedures, etc. are necessary and which functions, procedures, etc. are not.

[0045] Additionally, for the DL and UL of A-IoT, several issues will be discussed under the leadership of RAN 1. One of the issues to be discussed is the scheduling and timing relationship between DL and UL in A-IoT. In discussing the scheduling and timing relationship, the following 1. traffic flow, 2. device assumptions, and 3. topology can be considered.

[0046] 1. Traffic Flow The following DT and DO-DTT are being considered as traffic flows for A-IoT.

[0047] DT (device terminated) As for traffic, there is transmission (DL) to the A-IoT UE, but there is no transmission (UL) from the A-IoT UE. In other words, there is information to be transmitted to the A-IoT UE, but there is no information to be transmitted from the A-IoT UE. DT corresponds to a command type, for example, in which there is an instruction such as a command to the A-IoT UE.

[0048] ·DO-DTT(device originated - device terminated triggered) Traffic includes triggers from the network (NW) and transmissions (UL) from the A-IoT UE. In other words, traffic includes information transmitted from the A-IoT UE. DO-DTT corresponds to, for example, a sensor information report type in which the A-IoT UE transmits sensor information collected by the A-IoT UE.

[0049] In this disclosure, transmitting information corresponds to transmitting a signal containing information or transmitting a signal. In this disclosure, transmitting to a certain device X corresponds to transmitting a signal (or information) to device X. In addition, transmitting from a certain device X and transmitting by a certain device X correspond to device X transmitting a signal (or information). In addition, receiving from a certain device X corresponds to receiving a signal (or information) transmitted by device X. In addition, receiving by a certain device X corresponds to device X receiving a signal (or information).

[0050] 2. Device Prerequisites For A-IoT UE, the following TX (transmission) and FR (frequency range) 1-FDD are assumed:

[0051] ·TX TX can be unamplified backscatter UL transmission, amplified backscatter UL transmission, or amplified general UL transmission.

[0052] FR1-FDD FR1-FDD is applied to the A-IoT UE, that is, the A-IoT UE can switch carrier frequencies between DL carriers and UL carriers. However, the present disclosure is not limited to FR1-FDD and may be applied to TDD, FR2, or FR3.

[0053] The frequency bands of each FR are, for example, as follows: FR1: 410MHz~7.125GHz FR2: 24.25GHz~52.6GHz FR3: 7.125GHz~24.25GHz

[0054] FR1 may use a sub-carrier spacing (SCS) of 15 kHz, 30 kHz, or 60 kHz, and may use a bandwidth (BW) of 5 to 100 MHz. FR2 is a higher frequency than FR1, and may use an SCS of 60 kHz or 120 kHz (240 kHz may be included), and may use a bandwidth (BW) of 50 to 400 MHz.

[0055] 3. Topology Among the topologies shown in FIGS. 2 to 6, attention is focused on Topology 1 and Topology 2.

[0056] In Topology 1, UL and / or DL ​​communication is performed between a base station and an A-IoT UE without passing through an intermediate node. Note that the base station in the case of Topology 1 may correspond to a microcell.

[0057] In Topology 2, communication is performed between a base station and an A-IoT UE via an intermediate node. The A-IoT UE performs bidirectional communication with the intermediate node located between the base station and the A-IoT UE. Note that the base station in Topology 2 may correspond to a macrocell. The Topology 2 case may also be applied to indoor cases. Hereinafter, the intermediate node will also be referred to as intermediate UE, int.UE (intermediate UE), etc.

[0058] <Device Type> Three device types are defined for A-IoT devices: Device 1, Device 2a, and Device 2b.

[0059] Device 1 (may also be referred to as Type 1) Device 1 is a device type that consumes a peak power of 1 μW or less. Device 1 has an energy storage and an initial sampling frequency offset (SFO) of up to Z ppm (parts per million), where Z is 10 to the power of x (x is an integer greater than or equal to 0). Device 1 does not have any amplification in either DL or UL. UL transmission in Device 1 is performed by backscattering an externally provided carrier wave (CW), i.e., an unmodulated wave.

[0060] Device 2a (also referred to as Type 2a) The device 2a is a device type that consumes a peak power of several hundred μW. The device 2a has an energy storage and an initial sampling frequency offset of up to Z [ppm] (Z is 10 to the power x (x is an integer equal to or greater than 0)). The device 2a also performs DL and / or UL amplification. The UL transmission in the device 2a is performed by backscattering in a CW provided from an external device.

[0061] Device 2b (also called Type 2b) Device 2b is a device type that consumes a peak power of several hundred μW. Device 2b has energy storage and an initial sampling frequency offset of up to Z [ppm] (Z is 10 to the power x (x is an integer equal to or greater than 0)). DL and / or UL amplification is performed in device 2b. UL transmission in device 2b is performed internally within device 2b. In other words, UL transmission in device 2b does not need to be performed by backscattering in CW provided from an external source.

[0062] <Candidate Topology> Next, we describe candidate topologies for CW / R2D / D2R transmission.

[0063] Fig. 8 is a diagram showing examples of candidate topologies for CW / R2D / D2R transmission in Topology 1. Fig. 8 shows Topology 1A, Topology 1B, Topology 1C, Topology 1D, and Topology 1E as examples of candidate topologies.

[0064] As shown in Figure 8, in topologies 1A to 1E, CW / R2D communication signals (sometimes referred to as "R2D" in Figure 8 and below) / D2R communication signals (sometimes referred to as "D2R" in Figure 8 and below) can be sent and received to A-IoT devices.

[0065] In this embodiment, DL and R2D (reader to device) may be interchangeable, and UL and D2R (device to reader) may be interchangeable, where reader corresponds to BS and / or intermediate UE, and device corresponds to A-IoT device.

[0066] In Topology 1A, the node (first BS) that transmits the CW is different from the node (second BS) that receives the D2R communication signal transmitted by the A-IoT device via backscattering, and the node that transmits the CW is the same as the node that transmits the R2D communication signal. Also, the node that transmits the R2D communication signal is different from the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering. In other words, the R in R2D is different from the R in D2R.

[0067] In Topology 1B, the node (BS) that transmits the CW, the node that transmits the R2D communication signal, and the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering are the same.

[0068] In Topology 1C, the node transmitting the CW (CW node) is different from the node transmitting the R2D communication signal (BS). Also, in Topology 1C, the node transmitting the CW is different from the node receiving the D2R communication signal transmitted by the A-IoT device via backscattering (BS). Also, in Topology 1C, the node transmitting the R2D communication signal is the same as the node receiving the D2R communication signal transmitted by the A-IoT device via backscattering (BS). In other words, the R in R2D and the R in D2R are the same. Note that the CW node may be a BS, (intermediate) UE, IAB node, NCR (network-controlled repeater) node, relay node, or other type of node.

[0069] In Topology 1D, the node (BS) that transmits the R2D communication signal is the same as the node that receives the D2R communication signal generated and transmitted by the A-IoT device. That is, R in R2D is the same as R in D2R.

[0070] In Topology 1E, the node (first BS) that transmits the R2D communication signal is different from the node (second BS) that receives the D2R communication signal generated and transmitted by the A-IoT device. In other words, R in R2D is different from R in D2R.

[0071] Fig. 9 is a diagram showing examples of candidate topologies for CW / R2D / D2R transmission in Topology 2. Fig. 9 shows Topology 2A, Topology 2B, Topology 2C, Topology 2D, and Topology 2E as examples of candidate topologies.

[0072] As shown in Figure 9, in topologies 2A to 2E, CW / R2D communication signals (denoted as "R2D" in Figure 9) / D2R communication signals (denoted as "D2R" in Figure 9) can be sent and received to A-IoT devices.

[0073] In Topology 2A, the node transmitting the CW (first intermediate UE) is different from the node receiving the D2R communication signal transmitted by the A-IoT device via backscattering (second intermediate UE), and the node transmitting the CW is the same as the node transmitting the R2D communication signal. Also, the node transmitting the R2D communication signal is different from the node receiving the D2R communication signal transmitted by the A-IoT device via backscattering. In other words, the R in R2D is different from the R in D2R.

[0074] In Topology 2B, the node that transmits the CW (intermediate UE), the node that transmits the R2D communication signal, and the node that receives the D2R communication signal transmitted by the A-IoT device via backscattering are the same.

[0075] In Topology 2C, the node transmitting the CW (CW node) is different from the node transmitting the R2D communication signal (intermediate UE). Also, in Topology 1C, the node transmitting the CW is different from the node receiving the D2R communication signal transmitted by the A-IoT device via backscattering (BS). Also, in Topology 1C, the node transmitting the R2D communication signal is the same as the node receiving the D2R communication signal transmitted by the A-IoT device via backscattering. In other words, the R in R2D and the R in D2R are the same. Note that the CW node may be a BS / (intermediate) UE / IAB node / NCR node / relay node / other type of node.

[0076] In Topology 2D, the node (intermediate UE) that transmits the R2D communication signal is the same as the node that receives the D2R communication signal generated and transmitted by the A-IoT device, i.e., R in R2D is the same as R in D2R.

[0077] In Topology 2E, the node (first intermediate UE) that transmits the R2D communication signal is different from the node (second intermediate UE) that receives the D2R communication signal generated and transmitted by the A-IoT device. That is, R in R2D is different from R in D2R.

[0078] The signal design for A-IoT UE may be common between the above-mentioned Topology 1 and Topology 2.

[0079] Next, examples of communication flows for each combination of topology and traffic will be described. Below, the following combinations of topology and traffic will be described: DT in Topology 1, DO-DTT in Topology 1, DT in Topology 2, and DO-DTT in Topology 2.

[0080] Figure 10 is a diagram showing an example of the DT case in Topology 1. Figure 10 shows the flow of signals between the base station (gNB) and the A-IoT UE. Note that since this is the DT case in Topology 1, there is information transmission from the base station to the A-IoT UE, but there is no information transmission from the A-IoT UE to the base station.

[0081] In the case of DT in Topology 1, a communication flow consisting of the following two steps is assumed. Note that step 1 starts, for example, when a packet arrives at the base station. Step 1: The A-IoT UE wakes up. Step 2: The A-IoT UE receives information from the base station. In other words, the base station transmits information to the A-IoT UE.

[0082] Note that step 1 and step 2 may be performed together, for example, by the same signal.

[0083] In step 1, the A-IoT UE may wake up in response to a signal transmitted from a base station. The signal transmitted from the base station may be referred to as a carrier waveform. Here, the signal transmitted from the base station may correspond to an energy source that supplies energy to the A-IoT UE. Note that in this embodiment, the carrier waveform may be replaced with a carrier wave.

[0084] Also, in step 1, the A-IoT UE may wake up in response to a signal other than the carrier waveform signal transmitted from the base station (e.g., a radio frequency signal (RF) signal). Here, the signal other than the carrier waveform signal transmitted from the base station may correspond to an energy source that supplies energy to the A-IoT UE. Alternatively, in step 1, the A-IoT UE may wake up in response to a signal other than the base station (e.g., a radio frequency signal (RF) signal). Here, the signal other than the base station may correspond to an energy source that supplies energy to the A-IoT UE.

[0085] In step 1, the signal received by the A-IoT UE may be an example of a signal requesting a wake-up.

[0086] In the above-described steps 1 and 2, when a signal is transmitted from the base station, the transmission method of the signal transmitted from the base station may be any one of the following methods 1a to 1c.

[0087] (1a) A signal transmitted from a base station may be broadcast to one or more arbitrary A-IoT UEs. In this case, there is no need to distinguish whether the destination of the transmission from the base station is a UE or a UE group including one or more UEs. In other words, an A-IoT UE (e.g., A-IoT UE #1) that receives a signal does not need to detect whether the received signal is addressed to A-IoT UE #1 or to a group to which A-IoT UE #1 belongs.

[0088] (1b) A signal transmitted from a base station may be multicast to a group including one or more A-IoT UEs. In this case, a certain A-IoT UE (e.g., A-IoT UE #1) detects whether the received signal is transmitted to the group to which A-IoT UE #1 belongs. For example, A-IoT UE #1 detects whether the signal is transmitted to the group to which A-IoT UE #1 belongs based on information included in the signal (e.g., a cyclic redundancy check (CRC)) and / or resources used for the signal (e.g., at least one of time, frequency, and code).

[0089] (1c) A signal transmitted from a base station is unicast to a single A-IoT UE. In this case, a certain A-IoT UE (e.g., A-IoT UE#1) detects whether a received signal is transmitted to A-IoT UE#1. For example, A-IoT UE#1 detects whether a signal is transmitted to A-IoT UE#1 based on information included in the signal (e.g., a cyclic redundancy check (CRC)) and / or resources used for the signal (e.g., at least one of time, frequency, and code).

[0090] In addition, the A-IoT UE may notify a capability indicating whether or not it supports reception of at least one of the transmissions 1a to 1c described above.

[0091] Note that the method of transmitting signals from the base station may differ between the above-mentioned step 1 and step 2. For example, in step 1, the signal for waking up the A-IoT UE may be broadcast to one or more arbitrary A-IoT UEs as in 1a, and in step 2, the signal for transmitting information to the A-IoT UE may be multicast as in 1b or unicast as in 1c.

[0092] Note that the above-mentioned steps 1 and 2 may be consecutive in time, or there may be an interval between steps 1 and 2. For example, the signal for waking up and the signal containing information to be transmitted to the A-IoT may be consecutive in time.

[0093] In step 1 and / or step 2 of the above example, the base station may transmit to the A-IoT multiple times, or may transmit individually to each of two or more A-IoTs.

[0094] <DO-DTT case in Topology 1> Figure 11 is a diagram showing an example of Topology 1 and the DO-DTT case. Figure 11 shows the signal flow between the base station (gNB) and the A-IoT UE. Note that because this is the DO-DTT case in Topology 1, there is information transmission from the base station to the A-IoT UE and information transmission from the A-IoT UE to the base station.

[0095] In the case of DO-DTT in Topology 1, a communication flow consisting of the following three steps is assumed. Note that step 1 starts, for example, when a packet arrives at the base station. Step 1: The A-IoT UE wakes up. Step 2: The A-IoT UE receives information from the base station. In other words, the base station transmits information to the A-IoT UE. Step 3: The A-IoT UE transmits a signal to the base station. In other words, the base station receives a signal from the A-IoT UE.

[0096] Note that steps 1 and 2 may be performed together, for example, using the same signal. The signal in step 2 may be a carrier waveform signal.

[0097] In step 1, the A-IoT UE may wake up in response to a signal transmitted from a base station. The signal transmitted from the base station may be referred to as a carrier waveform. Here, the signal transmitted from the base station may correspond to an energy source that supplies energy to the A-IoT UE.

[0098] Also, in step 1, the A-IoT UE may wake up in response to a signal other than the carrier waveform signal transmitted from the base station (e.g., a radio frequency signal (RF) signal). Here, the signal other than the carrier waveform signal transmitted from the base station may correspond to an energy source that supplies energy to the A-IoT UE. Alternatively, in step 1, the A-IoT UE may wake up in response to a signal other than the base station (e.g., a radio frequency signal (RF) signal). Here, the signal other than the base station may correspond to an energy source that supplies energy to the A-IoT UE.

[0099] In step 1, the signal received by the A-IoT UE may be an example of a signal requesting a wake-up.

[0100] In the above-described steps 1 and 2, when a signal is transmitted from the base station, the signal transmitted from the base station may be one of the following 2a to 2c.

[0101] (2a) A signal transmitted from a base station may be broadcast to one or more arbitrary A-IoT UEs. In this case, there is no need to distinguish whether the destination of the transmission from the base station is a UE or a UE group including one or more UEs. In other words, an A-IoT UE (e.g., A-IoT UE #1) that receives a signal does not need to detect whether the received signal is addressed to A-IoT UE #1 or to a group to which A-IoT UE #1 belongs.

[0102] (2b) A signal transmitted from a base station may be multicast to a group including one or more A-IoT UEs. In this case, a certain A-IoT UE (e.g., A-IoT UE #1) detects whether the received signal is transmitted to the group to which A-IoT UE #1 belongs. For example, A-IoT UE #1 detects whether the signal is transmitted to the group to which A-IoT UE #1 belongs based on information included in the signal (e.g., a cyclic redundancy check (CRC)) and / or resources used for the signal (e.g., at least one of time, frequency, and code).

[0103] (2c) A signal transmitted from a base station is unicast to a single A-IoT UE. In this case, a certain A-IoT UE (e.g., A-IoT UE#1) detects whether a received signal is transmitted to A-IoT UE#1. For example, A-IoT UE#1 detects whether a signal is transmitted to A-IoT UE#1 based on information included in the signal (e.g., a cyclic redundancy check (CRC)) and / or resources used for the signal (e.g., at least one of time, frequency, and code).

[0104] In addition, the A-IoT UE may notify a capability indicating whether or not it supports reception of at least one of the transmissions 2a to 2c described above.

[0105] Note that the method of transmitting signals from the base station may differ between the above-mentioned step 1 and step 2. For example, in step 1, the signal for waking up the A-IoT UE may be broadcast to one or more arbitrary A-IoT UEs as in 2a, and in step 2, the signal for transmitting information to the A-IoT UE may be multicast as in 2b or unicast as in 2c.

[0106] Note that the above-mentioned steps 1 and 2 may be consecutive in time, or there may be an interval between steps 1 and 2. For example, the signal for waking up and the signal containing information to be transmitted to the A-IoT may be consecutive in time.

[0107] In the above-mentioned step 3, the signal transmission method when transmitting a signal from the A-IoT UE to the base station may be either 2d or 2e below.

[0108] (2d) The transmission in step 3 may be a backscattered UL transmission. In this case, timing adjustment (e.g., timing advance) between DL reception and UL transmission may or may not be applied. Also, power adjustment (e.g., power amplifier) ​​may or may not be applied. Also, transmit timing adjustment may or may not be applied.

[0109] (2e) The transmission in step 3 may be a non-backscattered UL transmission. The non-backscattered UL transmission may be a general UL transmission. For example, a UL channel (e.g., PUCCH, PUSCH, PRACH, etc.) and / or a UL reference signal (e.g., SRS (Sounding Reference Signal), sequence-based signal, etc.) is generated and transmitted. In this case, timing adjustment between DL reception and UL transmission may or may not be applied. Also, power adjustment may be applied.

[0110] In the above example (e.g., FIG. 11), a single transmission from the base station to the A-IoT UE and a single transmission from the A-IoT UE to the base station are shown, but the present disclosure is not limited to this. For example, multiple transmissions from the base station to the A-IoT UE may be followed by a single transmission from the A-IoT UE to the base station. In this case, a single transmission from the A-IoT UE to the base station may include responses to the multiple transmissions from the base station to the A-IoT UE.

[0111] Figure 12 is a diagram showing an example of the DT case in Topology 2. Figure 12 shows the signal flow between the base station (gNB), int.UE (intermediate UE), and A-IoT UE. Note that since this is the DT case in Topology 2, there is information transmission to the A-IoT UE, but there is no information transmission from the A-IoT UE.

[0112] In the case of DT in Topology 2, a communication flow consisting of the following four steps is assumed. Note that step 0 starts, for example, when a packet arrives at the base station. Step 0: The int.UE receives a trigger from the base station to send a signal to the A-IoT UE, and sends the signal to the A-IoT UE based on the trigger. Step 0 includes an operation of the base station sending a trigger to the int.UE. Step 1: The A-IoT UE wakes up. Step 2: The A-IoT UE receives information from the int.UE. In other words, the int.UE sends information to the A-IoT UE. Step X: The UE transmits a signal to the base station.

[0113] Note that step 1 and step 2 may be performed together, for example, by the same signal.

[0114] Of these four steps, steps 0 to 2 may be executed in this order. Step X is not limited to being executed after step 2. The timing at which step X is executed will be described later. In step 0, the signal received by the int.UE may be referred to as signal X. In step 1, the signal received by the A-IoT UE (signal transmitted by the int.UE) may be referred to as signal Y. In step 2, the signal received by the A-IoT UE may be referred to as signal Z. In step X, the signal transmitted by the int.UE may be referred to as signal R.

[0115] Note that step 0 may be performed without receiving a trigger to transmit a signal to the A-IoT UE. For example, the int.UE transmits a signal to the A-IoT UE without receiving a trigger. Illustratively, the int.UE transmits a signal to the A-IoT UE periodically or at predetermined resources.

[0116] In step 1, the A-IoT UE may wake up by a signal transmitted from the int.UE. The signal transmitted from the int.UE may be referred to as a carrier waveform. Here, the signal transmitted from the int.UE may correspond to an energy source that supplies energy to the A-IoT UE.

[0117] Also, in step 1, the A-IoT UE may wake up due to a signal other than the carrier waveform signal transmitted from the int.UE (e.g., an RF signal (radio frequency signal)). Here, the signal other than the carrier waveform signal transmitted from the int.UE may correspond to an energy source that supplies energy to the A-IoT UE. Alternatively, in step 1, the A-IoT UE may wake up due to a signal other than the int.UE (e.g., an RF signal (radio frequency signal)). Here, the signal other than the carrier waveform signal transmitted from the int.UE may correspond to an energy source that supplies energy to the A-IoT UE.

[0118] In step 1, the signal received by the A-IoT UE may be an example of a signal requesting a wake-up.

[0119] In the above-described steps 1 and 2, when a signal is transmitted from the int.UE, the transmission method of the signal transmitted from the int.UE may be any one of the following methods 3a to 3c.

[0120] (3a) A signal transmitted from an int.UE may be broadcast to one or more arbitrary A-IoT UEs. In this case, there is no need to distinguish whether the destination of the transmission from the int.UE is a UE or a UE group including one or more UEs. In other words, an A-IoT UE (e.g., A-IoT UE #1) that receives a signal does not need to detect whether the received signal is addressed to A-IoT UE #1 or to a group to which A-IoT UE #1 belongs.

[0121] (3b) A signal transmitted from an int.UE may be multicast to a group including one or more A-IoT UEs. In this case, an A-IoT UE (e.g., A-IoT UE#1) detects whether the received signal is transmitted to the group to which A-IoT UE#1 belongs. For example, A-IoT UE#1 detects whether the signal is transmitted to the group to which A-IoT UE#1 belongs based on information included in the signal (e.g., a cyclic redundancy check (CRC)) and / or resources used for the signal (e.g., at least one of time, frequency, and code).

[0122] (3c) Signals transmitted from an int.UE are unicast to a single A-IoT UE. In this case, a certain A-IoT UE (e.g., A-IoT UE#1) detects whether a received signal was transmitted to A-IoT UE#1. For example, A-IoT UE#1 detects whether a signal was transmitted to A-IoT UE#1 based on information included in the signal (e.g., a cyclic redundancy check (CRC)) and / or resources used for the signal (e.g., at least one of time, frequency, and code).

[0123] In addition, the A-IoT UE may notify a capability indicating whether or not it supports reception of at least one of the transmissions 3a to 3c described above.

[0124] Note that the method of transmitting signals from the int.UE may differ between the above-mentioned step 1 and step 2. For example, in step 1, the signal for waking up the A-IoT UE may be broadcast to one or more arbitrary A-IoT UEs as in 3a, and in step 2, the signal for transmitting information to the A-IoT UE may be multicast as in 3b or unicast as in 3c.

[0125] Note that the above-mentioned steps 1 and 2 may be consecutive in time, or there may be an interval between steps 1 and 2. For example, the signal for waking up and the signal containing information to be transmitted to the A-IoT may be consecutive in time.

[0126] The timing at which step X is executed may be any one of the following 3d to 3f.

[0127] (3d) Step X is performed before step 2. That is, the int.UE sends a signal to the base station before the A-IoT UE receives the information. In other words, the int.UE sends a signal to the base station before the int.UE sends information to the A-IoT UE. In this case, the signal sent to the base station may include a report indicating that the trigger was successfully received.

[0128] (3e) Step X is executed after step 2. That is, the int.UE transmits a signal to the base station after the A-IoT UE receives information. In other words, the int.UE transmits a signal to the base station after the int.UE transmits information to the A-IoT UE. In this case, the signal transmitted to the base station includes a report indicating whether the transmission to the A-IoT UE was completed or failed. Note that whether the transmission to the A-IoT UE was completed or failed may correspond to whether the int.UE was able to perform the transmission or was unable to perform it. Note that the signal transmitted to the base station in this case may include a report indicating that the trigger was successfully received.

[0129] (3f) Step X is executed before step 0. That is, the int.UE transmits a signal to the base station before the int.UE receives a trigger from the base station. In this case, the signal transmitted to the base station includes information on the type of request from the int.UE. The information on the type of request may be information related to a transmission request from the int.UE to the A-IoT UE (e.g., a transmission resource request).

[0130] Note that step X may be performed at multiple times. For example, the above-mentioned 3f and 3d or 3e may be applied. In this case, the information included in the signal transmitted by the int.UE to the base station at each timing may differ for each timing. When the above-mentioned 3f and 3d are applied, the int.UE transmits a signal to the base station before receiving a trigger from the base station, and transmits a signal to the base station before the A-IoT UE receives information.

[0131] The timing of step X may be specified in advance, or may be set or instructed by the base station. The instruction on the timing of step X may be included in a trigger transmitted from the base station.

[0132] The int.UE may notify the int.UE of a capability indicating when step X, in which the int.UE transmits a signal to the base station, can be performed. For example, the int.UE may notify the int.UE of a capability indicating whether step X can be performed before step 2, whether step X can be performed after step 2, or whether step X can be performed before step 0. The base station may instruct the int.UE on the timing of step X based on the notified capability.

[0133] <DO-DTT case in Topology 2> Figure 13 is a diagram showing an example of the DO-DTT case in Topology 2. Figure 13 shows the signal flow between the base station (gNB), int.UE, and A-IoT UE. Note that because this is the DO-DTT case in Topology 2, there is information transmission to the A-IoT UE and information transmission from the A-IoT UE.

[0134] In the case of DO-DTT in Topology 2, the communication flow is assumed to have the following five steps. Note that step 0 starts, for example, when a packet arrives at the base station. Step 0: The int.UE receives a trigger from the base station to send a signal to the A-IoT UE, and sends the signal to the A-IoT UE based on the trigger. Step 0 includes an operation of the base station sending a trigger to the int.UE. Step 1: The A-IoT UE wakes up. Step 2: The A-IoT UE receives information from the int.UE. In other words, the int.UE sends information to the A-IoT UE. Step 3: The A-IoT UE transmits a signal to the base station. In other words, the base station receives a signal from the A-IoT UE. Step X: The UE transmits a signal to the base station.

[0135] Note that steps 1 and 2 may be performed together, for example, using the same signal. The signal in step 2 may be a carrier waveform signal.

[0136] Of these five steps, steps 0 to 3 may be executed in this order. Step X is not limited to being executed after step 3. The timing at which step X is executed will be described later. In step 0, the signal received by the int.UE may be referred to as signal X. In step 1, the signal received by the A-IoT UE (signal transmitted by the int.UE) may be referred to as signal Y. In step 2, the signal received by the A-IoT UE may be referred to as signal Z. In step X, the signal transmitted by the int.UE may be referred to as signal R.

[0137] Note that step 0 may be performed without receiving a trigger to transmit a signal to the A-IoT UE. For example, the int.UE transmits a signal to the A-IoT UE without receiving a trigger. Illustratively, the int.UE transmits a signal to the A-IoT UE periodically or at predetermined resources.

[0138] In step 1, the A-IoT UE may wake up by a signal transmitted from the int.UE. The signal transmitted from the int.UE may be referred to as a carrier waveform. Here, the signal transmitted from the int.UE may correspond to an energy source that supplies energy to the A-IoT UE.

[0139] Also, in step 1, the A-IoT UE may wake up due to a signal other than the carrier waveform signal transmitted from the int.UE (e.g., an RF signal (radio frequency signal)). Here, the signal other than the carrier waveform signal transmitted from the int.UE may correspond to an energy source that supplies energy to the A-IoT UE. Alternatively, in step 1, the A-IoT UE may wake up due to a signal other than the int.UE (e.g., an RF signal (radio frequency signal)). Here, the signal other than the int.UE may correspond to an energy source that supplies energy to the A-IoT UE.

[0140] In step 1, the signal received by the A-IoT UE may be an example of a signal requesting a wake-up.

[0141] In the above-described steps 1 and 2, when a signal is transmitted from the int.UE, the transmission method of the signal transmitted from the int.UE may be any one of the following methods 4a to 4c.

[0142] (4a) A signal transmitted from an int.UE may be broadcast to one or more arbitrary A-IoT UEs. In this case, there is no need to distinguish whether the destination of the transmission from the int.UE is a UE or a UE group including one or more UEs. In other words, an A-IoT UE (e.g., A-IoT UE #1) that receives a signal does not need to detect whether the received signal is addressed to A-IoT UE #1 or to a group to which A-IoT UE #1 belongs.

[0143] (4b) Signals transmitted from an int.UE may be multicast to a group including one or more A-IoT UEs. In this case, a certain A-IoT UE (e.g., A-IoT UE#1) detects whether the received signal is transmitted to the group to which A-IoT UE#1 belongs. For example, A-IoT UE#1 detects whether the signal is transmitted to the group to which A-IoT UE#1 belongs based on information included in the signal (e.g., a cyclic redundancy check (CRC)) and / or resources used for the signal (e.g., at least one of time, frequency, and code).

[0144] (4c) Signals transmitted from an int.UE are unicast to a single A-IoT UE. In this case, a certain A-IoT UE (e.g., A-IoT UE#1) detects whether a received signal was transmitted to A-IoT UE#1. For example, A-IoT UE#1 detects whether a signal was transmitted to A-IoT UE#1 based on information included in the signal (e.g., a cyclic redundancy check (CRC)) and / or resources used for the signal (e.g., at least one of time, frequency, and code).

[0145] In addition, the A-IoT UE may notify a capability indicating whether or not it supports reception of at least one of the transmissions 4a to 4c described above.

[0146] Note that the method of transmitting signals from the int.UE may differ between the above-mentioned step 1 and step 2. For example, in step 1, the signal for waking up the A-IoT UE may be broadcast to one or more arbitrary A-IoT UEs as in 4a, and in step 2, the signal for transmitting information to the A-IoT UE may be multicast as in 4b or unicast as in 4c.

[0147] Note that the above-mentioned steps 1 and 2 may be consecutive in time, or there may be an interval between steps 1 and 2. For example, the signal for waking up and the signal containing information to be transmitted to the A-IoT may be consecutive in time.

[0148] In step 3, the destination int.UE to which the A-IoT UE transmits a signal (for example, the int.UE that receives the signal transmitted by the A-IoT UE) may be the same as or different from the source int.UE that transmitted information to the A-IoT UE in step 2.

[0149] The timing at which step X is executed may be any one of 4d to 4g below.

[0150] (4d) Step X is performed before step 2. That is, the int.UE sends a signal to the base station before the A-IoT UE receives the information. In other words, the int.UE sends a signal to the base station before the int.UE sends information to the A-IoT UE. In this case, the signal sent to the base station may include a report indicating that the trigger was successfully received.

[0151] (4e) Step X is executed after step 2. That is, the int.UE transmits a signal to the base station after the A-IoT UE receives information. In other words, the int.UE transmits a signal to the base station after the int.UE transmits information to the A-IoT UE. In this case, the signal transmitted to the base station includes a report indicating whether the transmission to the A-IoT UE was completed or failed. Note that here, whether the transmission to the A-IoT UE was completed or failed may correspond to whether the int.UE was able to perform the transmission or was unable to perform it. Note that the signal transmitted to the base station in this case may include a report indicating that the trigger was successfully received.

[0152] (4f) Step X is performed after step 3. That is, the int.UE transmits a signal to the base station after the A-IoT UE transmits information. In other words, the int.UE transmits a signal to the base station after the int.UE receives information from the A-IoT UE. In this case, the signal transmitted to the base station may include a report indicating whether transmission to the A-IoT UE is complete or failed, and / or a report indicating whether reception from the A-IoT UE is complete or failed. In addition, the signal transmitted to the base station may include a report indicating successful reception of the trigger.

[0153] (4g) Step X is executed before step 0. That is, the int.UE transmits a signal to the base station before the int.UE receives a trigger from the base station. In this case, the signal transmitted to the base station includes information on the type of request from the int.UE. The information on the type of request may be information related to a transmission request from the int.UE to the A-IoT UE (e.g., a transmission resource request).

[0154] Note that step X may be performed at multiple times. For example, at least one of 4g and 4d, 4e, and 4f described above may be applied. In this case, the information included in the signal transmitted by the int.UE to the base station at each timing may differ for each timing. When 4g and 4d described above are applied, the int.UE transmits a signal to the base station before receiving a trigger from the base station, and transmits a signal to the base station before the A-IoT UE receives information.

[0155] The timing of step X may be specified in advance, or may be set or instructed by the base station. The instruction on the timing of step X may be included in a trigger transmitted from the base station.

[0156] The int.UE may notify the int.UE of a capability indicating when step X, in which the int.UE transmits a signal to the base station, can be performed. For example, the int.UE may notify the int.UE of a capability indicating whether step X can be performed before step 2, whether step X can be performed after step 2, or whether step X can be performed before step 0. The base station may instruct the int.UE on the timing of step X based on the notified capability.

[0157] In step 3 above, the signal transmission method when transmitting a signal from the A-IoT UE to the int.UE may be either 4h or 4k as follows.

[0158] (4h) The transmission in step 3 may be a backscattered UL transmission. In this case, timing adjustment (e.g., timing advance) between DL reception and UL transmission may or may not be applied. Also, power adjustment (e.g., power amplifier) ​​may or may not be applied. Also, transmit timing adjustment may or may not be applied.

[0159] (4k) The transmission in step 3 may be a UL transmission that is not backscattering. A UL transmission that is not backscattering may be a general UL transmission. For example, a UL channel (e.g., PUCCH, PUSCH, PRACH, etc.) and / or a UL reference signal (e.g., SRS (Sounding Reference Signal), sequence-based signal, etc.) is generated and transmitted. In this case, timing adjustment between DL reception and UL transmission may or may not be applied. Also, power adjustment may be applied.

[0160] In addition, in the above-described example (e.g., FIG. 13), the transmissions from the base station to the int.UE, from the int.UE to the A-IoT UE, from the A-IoT UE to the int.UE, and from the int.UE to the base station are each shown as being once, but the present disclosure is not limited thereto. The number of these transmissions may be different from each other.

[0161] In addition, in the above-described embodiments, "wake-up" may mean preparing to receive a signal from the base station and / or the int.UE, or may mean starting to monitor a signal from the base station and / or the int.UE.

[0162] <Simultaneous Transmission and Power Sharing in NR> Here, an example of the possibility of simultaneous transmission and power sharing in NR will be described.

[0163] FIG. 14 is a diagram showing an example of cooperation between LTE and NR. In FIG. 14, an example in which a UE of NR cooperates between an eNB of LTE and a gNB of NR is shown. In the example of FIG. 14, the UE of NR switches the transmission destination of UL transmission between the eNB of LTE and the gNB of NR.

[0164] For E-UTRA NR Dual Connectivity (EN-DC) as shown in Figure 14, when a UE simultaneously transmits UL signals on different carriers, there is a concern about IMD, which may affect DL reception depending on the band combination. Therefore, Release 15 (Rel-15) supports EN-DC single UL transmission, which can avoid simultaneous UL transmission between LTE and NR.

[0165] In this case, the UE may report, as its capability, whether it supports single UL transmission for each possible combination of EN-DC band combinations, or whether it supports simultaneous UL transmission for each possible combination of EN-DC band combinations.

[0166] Fig. 15 is a diagram showing an example of power sharing. Fig. 15 shows the maximum power P NR and the maximum LTE power P LTE 10 shows a power state #1 obtained by adding the above and a power state #2 obtained after power sharing has been performed on the state #1.

[0167] For example, the maximum power P of NR NR and the maximum power of LTE, P LTE and the total maximum power P total are set / defined individually.

[0168] In this setting / definition, P NR +P LTE >P total and if the UE supports dynamic power sharing, the UE shall total For example, as shown in state #2 of FIG. 15, the UE drops the NR transmission power so that the total transmission power does not exceed P totalThe NR transmission power is dropped so as not to exceed

[0169] In this setting / definition, P NR +P LTE >P total If the UE does not support dynamic power sharing, the UE does not transmit for NR in a slot where UL transmission is allocated for LTE, i.e., in this case, LTE and NR are time division multiplexed (TDM).

[0170] <Resource pool> In the case of Topology 2, if the network dynamically schedules each R2D transmission / D2R reception / CW transmission of the int.UE using a dynamic grant, a large signaling overhead will be generated.

[0171] Therefore, a possible method is for a network (NW) such as a base station to provide resource pool information indicating a resource pool for R2D transmission, D2R reception, and CW transmission to an int.UE, and for the int.UE to autonomously determine resources for R2D transmission, D2R reception, and CW transmission within the resource pool. This method can reduce overhead compared to scheduling using dynamic grants.

[0172] This section describes how to provide resource pool information to the int.UE. The following description assumes that the resource pool for R2D transmission / D2R reception / CW transmission is provided to the int.UE.

[0173] A resource pool is a collection of time and / or frequency resources. The following description assumes that an int.UE can perform R2D transmission / D2R reception / CW transmission on time domain and / or frequency domain resources in the resource pool. The following description also assumes that an int.UE autonomously determines time domain and / or frequency domain resources for each R2D transmission / D2R reception / CW transmission in the resource pool.

[0174] RRC / MAC CE / DCI can be used to instruct the int.UE to configure / update / activate / deactivate etc.

[0175] 0. Common or individual resource pools The network may provide the int.UE with a common or separate resource pool for R2D / D2R / CW as needed.

[0176] 1. Cyclically occurring resource pools The int.UE uses a resource pool that occurs periodically, which may be defined in the specification or wireless communication system, or may be dictated by the network. Fig. 16 is a diagram showing an example of periodic generation of resource pools. In the generation example shown in Fig. 16, the horizontal axis represents the time axis and the vertical axis represents the frequency axis. In this generation example, there are eight consecutive resource pools in the time domain and two consecutive resource pools in the frequency domain, and they are generated periodically every one period. The period may be expressed using N frames / subframes / seconds / milliseconds / slots / OFDM symbols / chips.

[0177] As a result, the terminal can autonomously determine the resources for R2D transmission, D2R reception, and CW transmission according to the cycle.

[0178] 2. Resource granularity within a resource pool The granularity of resources within a resource pool is explained below.

[0179] The granularity in the time domain can be a frame, subframe, second, millisecond, slot, OFDM symbol, chip, or a group of the above. For example, the int.UE is provided with a set of slots / OFDM symbols etc. that can be used for R2D transmission, D2R reception, and CW transmission.

[0180] The granularity of the frequency band can be RB, subcarrier, or a group of the above. For example, an int.UE is provided with a set of RBs / subcarriers that can be used for R2D transmission, D2R reception, and CW transmission.

[0181] As a result, the terminal can select an appropriate granularity from the above granularities.

[0182] 3. Contiguous or non-contiguous resource pools Whether the resource pools within a period are contiguous or non-contiguous in the time domain or the frequency domain is described below.

[0183] The resource pool may or may not be contiguous in the time domain. The resource pool may or may not be contiguous in the frequency domain.

[0184] Here, the granularity of resources is the same as in 2 above in both the time domain and the frequency domain.

[0185] Fig. 17 is a diagram showing an example of resource pools that are contiguous in the time domain and in the frequency domain. Fig. 18 is a diagram showing an example of resource pools that are contiguous in the time domain but not in the frequency domain. Fig. 19 is a diagram showing an example of resource pools that are not contiguous in the time domain but in the frequency domain. Fig. 20 is a diagram showing an example of resource pools that are not contiguous in the time domain and not in the frequency domain.

[0186] As a result, the resource pools may or may not be contiguous, which increases the degree of freedom in setting the resource pools.

[0187] 4. Specifying consecutive resource pool information This section explains how to represent a resource pool that has continuous resources in the time domain / frequency domain.

[0188] The network instructs the int.UE to: Time domain start resource Number of resources in the time domain Frequency domain starting resources Number of frequency domain resources

[0189] In this way, resource pool information indicating a resource pool having consecutive resources includes a starting resource from which the consecutive resources start, and the number of consecutive resources from the starting resource.

[0190] 5. Specifying non-contiguous resource pool information This section explains how to represent a resource pool that has resources that are not contiguous in the time domain / frequency domain.

[0191] The network provides the int.UE with a bitmap indicating the resource pool, where each bit in the bitmap corresponds to the following: The bits indicate whether the time / frequency / time-frequency resources are available for R2D transmission / D2R reception / CW transmission. Each bit corresponds to one time resource. Each bit corresponds to one frequency resource. Each bit corresponds to one time-frequency resource.

[0192] In this way, resource pool information indicating a resource pool having non-contiguous resources includes information indicating whether each resource is available for R2D transmission / D2R reception / CW transmission.

[0193] Regarding the length of the bitmap, let N be the number of time domain resources included in one period, as shown in Figure 21. And let M be the number of frequency domain resources in the BWP designated for DL ​​BWP / UL BWP or R2D / D2R / CW, as shown in Figure 22. In this case, the length of the bitmap is N x M, as shown in Figure 23.

[0194] Another example of how to represent a resource pool is to determine a reference pattern. For example, in the example of Fig. 18, the eight consecutive patterns from the left end of the time domain may be the reference pattern, and these reference patterns may be the second and fourth patterns from the bottom end of the frequency domain. For example, in the example of Fig. 20, the second and fourth patterns from the bottom end of the frequency domain may be the reference patterns, and these may be the first, fourth, ninth, etc. patterns counting from the left end of the time domain.

[0195] 6. Variations / extensions of resource instructions We will now describe variations / extensions (1) to (4) for increasing the flexibility of indicating available resources for R2D transmission / D2R reception / CW transmission.

[0196] (1) An int.UE may be provided with multiple resource pools, i.e., the int.UE may receive and use information related to multiple resource pools. int.UE does not assume that multiple resource pools contain resources that overlap in time and / or frequency. Alternatively, multiple resource pools may contain resources that overlap in time and / or frequency.

[0197] (2) The activation / deactivation of the resource pool may be indicated to the int.UE, i.e., the int.UE may receive information regarding the activation / deactivation of the resource pool and use the resource pool based on the information.

[0198] (3) The int.UE may be indicated with "flexible" time / frequency / time-frequency resources. In the case of "flexible" resources, the int.UE follows further instructions / rules to decide whether the resources are available for R2D transmission / D2R reception / CW transmission. - For example, the int.UE may be dynamically instructed via MAC CE / DCI whether "flexible" resources are available for R2D transmission / D2R reception / CW transmission. - For example, the int.UE determines that "flexible" resources are available for R2D transmission / D2R reception / CW transmission if they do not overlap with R2D transmission / D2R reception / CW transmission.

[0199] The "bitmap" in point 5 above is replaced with "a set of instructions." - the int.UE is provided with the following set of instructions: Each instruction corresponds to one time resource. Each instruction corresponds to one frequency resource. Each instruction corresponds to one time-frequency resource. The indication indicates whether the time / frequency / time-frequency resource is available for R2D transmission / D2R reception / CW transmission, unavailable, or "flexible."

[0200] (4) int.UE can provide the following information related to the resource pool / resources within the resource pool: Transmit power Spatial domain information (beam) Encoding method / rate ·Waveform Modulation method / number of orders

[0201] 7. Resource Overlap For a resource in the resource pool, if that resource overlaps with a given DL reception / UL transmission, the int.UE will not use that resource for R2D transmission / D2R reception / CW transmission.

[0202] The predetermined DL reception / UL transmission may be any DL channel / signal, any UL channel / signal, or a DL reception / UL transmission of a particular type of DL channel / signal, UL channel / signal.

[0203] Examples of the specific types of DL channels / signals and UL channels / signals include cell-specific channels / signals / SSB / CSI-RS / PDCCH / SIB 1 / SIB x / CORESET#0 / PDCCH / PDSCH / SRS / PUCCH / PUSCH / PRACH in any CSS.

[0204] <Terminology> Here, we will explain the terms used in relation to the A-IoT mentioned above.

[0205] A-IoT device or device: a device included in an A-IoT system, having any of the multiple device types as described above.

[0206] Reader: D2R receiver The leader may be either a BS or a UE. The leader UE may be called an int.UE (intermediate UE). The R2D transmitter and D2R receiver may be the same node or different nodes.

[0207] ·R2D: Abbreviation for Reader-to-Device Link. PRDCH: Physical R2D channel. D2R: Abbreviation for Device-to-Reader Link. PDRCH: Physical D2R channel.

[0208] ·DT traffic: Abbreviation for Device Terminated traffic. DT traffic is, for example, traffic that sends commands from a reader to a device and terminates at the device.

[0209] DO-DTT traffic: Device Originated-Device Terminated Trigger DO-DTT traffic is, for example, "inventory" traffic.

[0210] Timing acquisition signal / preamble / midamble / postamble / synchronization signal can be replaced with each other.

[0211] <Overlap> In an A-IoT communication system that includes ambient IoT devices, multiple communications, including those in the A-IoT communication system, may overlap with each other. The assumptions regarding this overlap are as follows:

[0212] ·int.UE can be replaced by a CW node. The overlap may be in time but not in frequency. The overlap may be time-overlapping and frequency-overlapping. "Overlap" may include transmission (Tx) / reception (Rx) in the same time unit (e.g. slot) even if there is no actual timing overlap. "Overlap" may include transmissions (Tx) / receptions (Rx) that do not overlap in time but do not have a sufficient gap between them. "Overlap" may include cases where there is no actual frequency overlap but where there is transmission (Tx) / reception (Rx) in the same frequency range / band. "Overlap" may include transmit (Tx) / receive (Rx) that do not overlap in frequency but do not have sufficient guard bands between them.

[0213] Note that transmit (Tx) / receive (Rx) overlap may mean the following: Overlap between Uu / SL transmission (Tx) and A-IoT transmission (Tx) Overlap between Uu / SL transmission (Tx) and A-IoT reception (Rx) Overlap between Uu / SL reception (Rx) and A-IoT transmission (Tx) Overlap between Uu / SL reception (Rx) and A-IoT reception (Rx)

[0214] <Consideration 1> As mentioned above, overlapping may occur in the transmission (Tx) / reception (Rx) of multiple communications in the int.UE. Resource overlap may also occur when a resource pool for R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx) is provided to the int.UE and the int.UE autonomously selects resources within the pool.

[0215] For example, it is possible that an R2D / D2R / CW resource in a resource pool is selected by an int.UE and the selected resource overlaps with a DL / UL / SL resource.

[0216] Further study is required on how int.UE should handle cases where resources in the resource pool overlap.

[0217] Therefore, in this embodiment, we will explain a method for appropriately processing resources to eliminate overlap when overlap occurs in resources within a resource pool in a communication system including A-IoT (Proposal 1 and Proposal 2).

[0218] <Consideration 2> Further consideration is also required as to whether the following parameters related to resource selection for R2D / D2R / CW in the int.UE should be determined by the int.UE itself or provided by the network. R2D / D2R / CW repetition factor CW waveforms (i.e., single tone / single tone with frequency hopping / multi-tone) The gap between two tones in the case of a multi-tone CW waveform The gap between two frequency hops when the CW waveform is a single tone with frequency hopping

[0219] Therefore, in this embodiment, a method will be described in which an A-IoT device appropriately determines parameters for resource selection for R2D / D2R / CW (Proposal 3).

[0220] In this embodiment, "time resource" and "time domain resource" may be interchangeable. In addition, in this embodiment, "frequency", "frequency resource", and "frequency domain resource" may be interchangeable. Similarly, in this embodiment, "code", "code resource", and "code domain resource" may be interchangeable. In addition, in this embodiment, "signal monitoring" may be interchangeable with "signal reception".

[0221] In addition, in this embodiment, "R2D," "R2D signal," "R2D message," and "R2D message type" may be interchangeable. In addition, in this embodiment, "D2R," "D2R signal," "D2R message," and "D2R message type" may be interchangeable.

[0222] The items described in the following proposals may be combined as appropriate as long as no contradictions arise.

[0223] In the following suggestions, the options may be combined as appropriate.

[0224] In the proposals below, different options may be applied on a case-by-case basis.

[0225] In the following proposal, the indication / configuration may be carried by physical (PHY) layer control information or higher layer payload (e.g., MAC (Medium Access Control) layer control information, Msg0 (paging), Msg2 (RAR (Random Access Response)), Msg4, unicast data, etc.).

[0226] In the following proposal, the display on R2D may have the same meaning as above.

[0227] In the following proposal, the indication / configuration may be transmitted by the PRDCH or R2D timing acquisition signal (preamble / midamble / postamble) / synchronization signal.

[0228] In the following proposal, a slot may be a time interval of 1 ms (ie, one slot in OFDM) or a slot in slotted ALOHA, or any other time domain unit consisting of one or more symbols.

[0229] In the following proposal, a symbol may be one OFDM symbol, M chips for OOK, or one modulation symbol for PSF / FSK.

[0230] In the following proposals, different alternatives / options may apply to R2D and D2R.

[0231] In the suggestions below, different alternatives / options may apply depending on the device type.

[0232] In the following proposals, different alternatives / options may apply to different connection topologies.

[0233] In the following proposal, different alternatives / options may be applied to different R2D / D2R channels (PRDCH: PHY channel for R2D control, PDRCH: PHY channel for D2R control).

[0234] In the following proposal, different alternatives / options may apply for different R2D / D2R information / formats / commands (R2D data, R2D control, R2D system information, R2D information triggering contention-based access, D2R data, D2R control, D2R ACK / NACK response, D2R response in contention-based access (Msg1 / Msg3)).

[0235] In the following, "CW / R2D / D2R transmission" may also be referred to as communication in a wireless communication system including an A-IoT device, communication of an A-IoT device, communication with an A-IoT device, communication involving an A-IoT device, etc.

[0236] In the following, notifications may be carried in the physical (PHY) layer / MAC layer / Radio Resource Control (RRC) layer / a new layer defined for A-IoT.

[0237] <Prerequisites for Proposal 1> The premise of Proposal 1 is as follows: · The int.UE is provided with a resource pool for R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx). ·int.UE selects resources for R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx) within the resource pool.

[0238] <Proposal 1> In Proposal 1, when overlap occurs in resources within the resource pool, the int.UE selects resources as follows (a) to (c).

[0239] (a) If a resource in the resource pool overlaps with a resource for DL ​​reception (Rx) / UL transmission (Tx) / SL reception (Rx) / SL transmission (Tx), the int.UE will not select that resource for R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx).

[0240] (a-1) If a resource in the resource pool partially overlaps with a resource for DL ​​reception (Rx) / UL transmission (Tx) / SL reception (Rx) / SL transmission (Tx), the int.UE handles the resource as follows (Option 1) or (Option 2).

[0241] (Option 1) The int.UE may select its resources for R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx).

[0242] (Option 2) int.UE does not select the resource for R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx).

[0243] The "partial overlap" includes the following cases: - Partially overlapping in time and fully overlapping / partially overlapping / non-overlapping in frequency - Completely overlapping in time and partially overlapping in frequency

[0244] (a-2) If a resource in the resource pool is used for R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx) with repetition, and one or more of the repetitions overlap with resources for DL ​​reception (Rx) / UL transmission (Tx) / SL reception (Rx) / SL transmission (Tx), the int.UE handles the resource as follows (Option 1) or (Option 2).

[0245] (Option 1) The int.UE may select its resources for R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx).

[0246] (Option 2) int.UE does not select the resource for R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx).

[0247] (a-3) If a resource in the resource pool is used for CW transmission (Tx) of a multi-tone waveform and one of the multiple tones of the CW transmission (Tx) overlaps with a resource for DL ​​reception (Rx), UL transmission (Tx), SL reception (Rx), or SL transmission (Tx), the int.UE handles the resource as follows (Option 1) or (Option 2).

[0248] (Option 1) The int.UE may select its resources for CW transmission (Tx).

[0249] (Option 2) int.UE does not select that resource for CW transmission (Tx).

[0250] Note that a "multi-tone waveform" refers to a waveform that has multiple unmodulated single tones, each at a different frequency point.

[0251] (b) If a resource in the resource pool overlaps with a resource for DL ​​reception (Rx), UL transmission (Tx), SL reception (Rx), or SL transmission (Tx), the int.UE performs transmission-related processing as follows (b-1) to (b-7).

[0252] (b-1) When a resource in the resource pool is selected by the int.UE for R2D transmission (Tx) / D2R reception (Rx) and the selected resource overlaps with a resource for DL ​​reception (Rx) / UL transmission (Tx), the int.UE performs the transmission-related processing as follows (b-1-1) to (b-1-5). (b-1-1) Simultaneous transmission is performed. The transmission power of each may be determined based on the priority. (b-1-2) Transmit one and not transmit the other. For example, execute R2D transmission (Tx) and do not execute UL transmission (Tx) that overlaps with that transmission. For example, execute UL transmission (Tx) and do not execute R2D transmission (Tx) that overlaps with that transmission. (b-1-3) Multiplexing overlapping transmissions, selecting resources for the multiplexed transmission, and executing the transmission. (b-1-4) Depending on the situation, either b-1-1, b-1-2, or b-1-3 above will be applied. (b-1-5) Execute transmission when processing time requirements are met.

[0253] (b-2) When a resource in the resource pool is selected by the int.UE for R2D transmission (Tx) / D2R reception (Rx) and the selected resource overlaps with a resource for SL reception (Rx) / SL transmission (Tx), the int.UE performs resource processing as follows (b-2-1) to (b-2-4). (b-2-1) Simultaneous transmission is performed. The transmission power of each may be determined based on the priority. (b-2-2) Transmit one and not the other. For example, execute R2D transmission (Tx) and do not execute SL transmission (Tx) that overlaps with that transmission. For example, execute SL transmission (Tx) and do not execute R2D transmission (Tx) that overlaps with that transmission. (b-2-3) Depending on the situation, either b-2-1 or b-2-2 above will be applied. (b-2-4) Execute transmission when processing time requirements are met.

[0254] (b-3) When a resource in the resource pool is selected by the int.UE for R2D transmission (Tx) / D2R reception (Rx), and the selected resource overlaps with a resource for DL ​​reception (Rx) / UL transmission (Tx) / SL reception (Rx) / SL transmission (Tx), the int.UE may handle these resource processes together.

[0255] (b-4) When a resource in the resource pool is selected by the int.UE for R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx), and the selected resource overlaps with resources such as DL reception (Rx) / UL transmission (Tx) / SL reception (Rx) / SL transmission (Tx) (other than b-1 to b-3 above), the int.UE performs resource processing as follows (b-4-1) to (b-4-3). (b-4-1) int. UE / CW node reports whether it supports or can support simultaneous transmission. (b-4-2) If the int.UE / CW node does not support simultaneous transmission, it performs priority processing. It may perform the prioritized transmission and skip the other transmission. (b-4-3) If the int.UE / CW node supports simultaneous transmission, perform dynamic power sharing among multiple transmissions.

[0256] (b-5) When a resource in the resource pool is selected by the int.UE for R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx), and the selected resource partially overlaps with resources such as DL reception (Rx) / UL transmission (Tx) / SL reception (Rx) / SL transmission (Tx), the int.UE performs resource processing as follows (b-5-1) to (b-5-2). (b-5-1) int. UE performs overlap processing operations only on resources in the overlapping portion. (b-5-2)int.UE performs the same overlap processing operation for the entire transmission / reception resource.

[0257] (b-6) When a resource in the resource pool is selected by the int.UE for repetition of R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx), and at least one of the repetitions overlaps with other resources for DL ​​reception (Rx) / UL transmission (Tx) / SL reception (Rx) / SL transmission (Tx), the int.UE performs resource processing as follows (b-6-1) to (b-6-2). (b-6-1) int. UE performs overlap processing operations only on resources of repetition of the overlap portion. (b-6-2) int.UE performs the same overlap processing operation for all repetition resources.

[0258] (b-7) When a resource in the resource pool is selected by the int.UE for CW transmission (Tx) having a multi-tone waveform, and at least one resource of the selected multiple tones overlaps with other resources such as DL reception (Rx), UL transmission (Tx), SL reception (Rx), and SL transmission (Tx), the int.UE performs resource processing as follows (b-7-1) to (b-7-2). (b-7-1) int. The UE performs overlap processing operations only on resources of overlapping tones. (b-7-2) int. UE performs the same overlap processing operation on all tone resources.

[0259] Below, (b-1) to (b-7) and (b-1-1) to (b-7-2) will be explained in order.

[0260] (b-1) When a resource in the resource pool is selected by the int.UE for R2D transmission (Tx) / D2R reception (Rx) and the selected resource overlaps with a resource for DL ​​reception (Rx) / UL transmission (Tx), the int.UE performs the transmission-related processing as follows (b-1-1) to (b-1-5).

[0261] For example, in Topology 2, when an int.UE transmits as an int.UE, other transmissions may occur at the int.UE, and the transmission as the int.UE and the other transmissions may overlap in time.

[0262] Here, the other transmission is a transmission independent of the operation as an int.UE. Hereinafter, the transmission independent of the operation as an int.UE may be referred to as an independent transmission (independent TX).

[0263] For example, in the case of b-1, the independent transmission includes the UL transmission as a UE. Hereinafter, the uplink transmission as a UE, which is independent of the operation as an int.UE, may be referred to as an independent UL or an independent UL transmission.

[0264] Here, for the above-mentioned overlap, the following two overlaps, overlap #A and overlap #B, are considered. Overlap #A: Independent UL and overlap with transmission from int.UE to A-IoT Overlap #B: Overlap between an independent UL and a UL for reporting communication between the int.UE and the A-IoT (e.g., transmission of signal R)

[0265] In addition, during overlap #A, transmission from int.UE to A-IoT includes transmission of at least one of the following signals: A signal to wake up the A-IoT UE and / or a carrier waveform provided to the A-IoT for backscattering (e.g., signal Y) Signal for transmitting information to A-IoT UE (e.g., signal Z) Note that signal Z may not contain information and may be a signal for backscatter transmission.

[0266] Figure 24 is a diagram showing an example of overlap in the case of DT. Similar to Figure 12, Figure 24 shows the signal flow between the base station (gNB), int.UE, and A-IoT UE. Note that since this is the case of DT in Topology 2, there is information transmission to the A-IoT UE, but there is no information transmission from the A-IoT UE.

[0267] Figure 24 shows an example where an independent UL and transmission from an int.UE to an A-IoT overlap. Figure 24 also shows an example where an independent UL and a UL for reporting communication between an int.UE and an A-IoT overlap.

[0268] Figure 25 is a diagram showing an example of overlap in the case of DO-DTT. Similar to Figure 13, Figure 25 shows the signal flow between the base station (gNB), int.UE, and A-IoT UE. Note that since this is the case of DO-DTT in Topology 2, there is information transmission to the A-IoT UE and information transmission from the A-IoT UE.

[0269] Figure 25 shows an example where an independent UL and transmission from an int.UE to an A-IoT overlap. Figure 25 also shows an example where an independent UL and a UL for reporting communication between an int.UE and an A-IoT overlap.

[0270] 24 and 25 show an example in which an independent UL and a UL for reporting communication between an int.UE and an A-IoT are executed to the same base station, but the present disclosure is not limited to this. For example, the destination of the independent UL and the destination of the UL for reporting communication between an int.UE and an A-IoT may be different base stations.

[0271] Note that in b-1 of this embodiment, overlap is not limited to overlap of actual timing. For example, in this embodiment, overlap may not be overlap of actual timing, but may include multiple transmissions in the same time unit (for example, any one of a slot, a certain time interval, and a switching period). For example, taking overlap #A as an example, if an independent UL and a transmission from int.UE to A-IoT are instructed / configured to be performed in the same slot, it may be determined that the independent UL and the transmission from int.UE to A-IoT overlap. Furthermore, overlap may mean overlap at least in the time domain.

[0272] In topology 2, when an overlap of transmissions related to the operation of the int.UE occurs in the int.UE, the int.UE handles the overlap.

[0273] Specific response modes will be described below. Note that each of the modes described below may be applied to each overlap type (e.g., overlap #A and #B). Also, among the mechanisms of the modes described below, the applied mechanism may differ between overlap types. Also, among the mechanisms of the modes described below, the applied mechanism may be applied based on the capability of the int.UE.

[0274] (b-1-1) Simultaneous transmission is performed. The transmission power of each may be determined based on the priority (hereinafter, method b-1-1).

[0275] In method b-1-1, overlapping transmissions are performed simultaneously. Note that in method b-1-1, transmission power may be allocated between overlapping transmissions. For example, a power allocation priority may be set. Higher transmission power may be allocated to transmissions with higher priority.

[0276] Figure 26 is a diagram showing an example in which method b-1-1 is applied to the case shown in Figure 24. Similar to Figure 24, Figure 26 shows the flow of signals between the base station (gNB), int.UE, and A-IoT UE. Note that since this is a DT case in Topology 2, there is information transmission to the A-IoT UE, but there is no information transmission from the A-IoT UE.

[0277] Figure 26 shows an example in which an overlapping independent UL and a transmission from an int.UE to an A-IoT are transmitted simultaneously. Figure 26 also shows an example in which an overlapping independent UL and a UL for reporting communication between an int.UE and an A-IoT are transmitted simultaneously.

[0278] Transmission power may be allocated based on the priority between overlapping transmissions. For example, transmission power may be allocated based on at least one of the following priorities: In the following description, "a" > "b" indicates that a has a higher priority than b:

[0279] For example, transmission power may be allocated based on the priority of the channel type and signal type of overlapping transmissions. For example, the priority may be set as follows: "PRACH / PUCCH" > "Signal Y / Signal Z" > "PUSCH (e.g., DG (dynamic grant) PUSCH and / or CG (configured grant) PUSCH)."

[0280] For example, transmit power may be allocated based on the priority of overlapping transmission traffic flows, such as "signal Y / signal Z for DO-DTT" > "UL" > "signal Y / signal Z for DT."

[0281] Transmission power may be allocated based on the priority of the instruction / setting. For example, the priority may be set as follows: "UL with a relatively high priority instruction" > "signal Y / signal Z with a relatively low priority instruction." Note that the priority may be indicated in signal X (a signal from the base station to the int. UE).

[0282] The transmission power may be allocated based on the priority of the transmission timing. For example, the priority may be set as follows: "transmission with a relatively early start of transmission" > "transmission with a relatively late start of transmission."

[0283] Transmission power may be allocated based on the priority of the scheduling timing. For example, the priority may be set as follows: "transmission corresponding to relatively later scheduling" > "transmission corresponding to relatively earlier scheduling."

[0284] Priorities may be set based on numerology and / or subcarrier spacing (SCS), and transmission power may be allocated based on the set priorities. For example, when the numerology and / or SCS are changed, priorities may be set based on whether the numerology and / or SCS have changed.

[0285] For example, for a certain transmission, priority is set depending on whether the SCS of the transmission has changed from the SCS of the transmission immediately preceding the transmission. For example, the priority of a certain transmission X whose SCS has not changed from the SCS of the transmission immediately preceding the transmission X is higher than the priority of a certain transmission X whose SCS has changed from the SCS of the transmission immediately preceding the transmission X. Note that the previous transmission may refer to, for example, the immediately preceding or most recent transmission. Alternatively, the SCS of the previous transmission may be replaced with the SCS currently being applied after being set or notified. The same applies hereinafter.

[0286] For example, in a case where transmission X (e.g., an independent UL) and transmission Y (e.g., a transmission from an int.UE to an A-IoT) overlap, if the SCS of transmission X has not changed from the SCS of the transmission previous to transmission X, and the SCS of transmission Y has changed from the SCS of the transmission previous to transmission Y, the priority of transmission X is higher than the priority of transmission Y. Here, "transmission previous to transmission X" corresponds to, for example, an independent UL previous to the independent UL corresponding to transmission X, or a transmission from an int.UE to an A-IoT, and "transmission previous to transmission Y" corresponds to, for example, an independent UL previous to the transmission from an int.UE to an A-IoT corresponding to transmission Y, or a transmission from an int.UE to an A-IoT. Note that if there is no change in the SCS in both transmission X and transmission Y, the priorities in terms of SCS may be the same. Also, if there is a change in the SCS in both transmission X and transmission Y, the priorities in terms of SCS may be the same.

[0287] For example, in a certain transmission, priority is set depending on whether the numerology of the transmission has changed from the numerology of the transmission immediately preceding the transmission. For example, if the numerology of a certain transmission X has not changed from the numerology of the transmission immediately preceding the transmission X, the priority of the transmission X is higher than the priority of a certain transmission X if the numerology of the transmission X has not changed from the numerology of the transmission immediately preceding the transmission X. Note that the numerology of the previous transmission may be replaced by the numerology that has been set or notified and is currently being applied. The same applies below.

[0288] For example, in a case where transmission X and transmission Y overlap, if the numerology of transmission X has not changed from the numerology of the transmission preceding transmission X, and the numerology of transmission Y has changed from the numerology of the transmission preceding transmission Y, transmission X has a higher priority than transmission Y. Note that if there is no change in numerology in both transmission X and transmission Y, the priorities from the perspective of numerology may be the same. Also, if there is a change in numerology in both transmission X and transmission Y, the priorities from the perspective of numerology may be the same.

[0289] For example, the priority may be set based on the waveform. For example, when the waveform used during transmission is changed by selecting a waveform from among multiple candidate waveforms, the priority may be set based on the waveform. For example, candidate waveforms include DFT-S-OFDM (Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing) waveforms, etc. Alternatively, modulation methods such as OOK (On-Off-Keying) may be included. The same applies hereinafter.

[0290] For example, a priority is set for a transmission depending on whether the waveform of that transmission has been changed from the waveform of the transmission immediately preceding that transmission. For example, if the waveform of a transmission X has not been changed from the waveform of the transmission immediately preceding that transmission, the priority of that transmission X is higher than the priority of a transmission X if the waveform of that transmission X has been changed from the waveform of the transmission immediately preceding that transmission.

[0291] For example, in a case where transmission X and transmission Y overlap, if the waveform of transmission X has not changed from the waveform of the transmission immediately preceding transmission X, and the waveform of transmission Y has changed from the waveform of the transmission immediately preceding transmission Y, the priority of transmission X is higher than the priority of transmission Y. Note that if there is no change in waveform in both transmission X and transmission Y, the priorities from the viewpoint of waveform may be the same. Also, if there is a change in waveform in both transmission X and transmission Y, the priorities from the viewpoint of waveform may be the same. Note that the waveform of the previous transmission may be replaced with the waveform that has been set or notified and is currently being applied. The same applies below.

[0292] For example, the priority may be set based on the frequency. For example, when the frequency (for example, BWP or band) is changed, the priority may be set based on whether or not the frequency has changed.

[0293] For example, a priority may be set for a transmission depending on whether the frequency of the transmission has changed from the frequency of the transmission immediately preceding it. For example, if the frequency of a transmission X has not changed from the frequency of the transmission immediately preceding it, the priority of the transmission X is higher than the priority of the transmission X if the frequency of the transmission X has changed from the frequency of the transmission immediately preceding it.

[0294] For example, in a case where transmission X and transmission Y overlap, if the frequency of transmission X has not been changed from the frequency of the transmission previous to transmission X, and the frequency of transmission Y has been changed from the frequency of the transmission previous to transmission Y, the priority of transmission X is higher than the priority of transmission Y. Note that if there is no change in frequency in both transmission X and transmission Y, the priorities in terms of frequency may be the same. Also, if there is a change in frequency in both transmission X and transmission Y, the priorities in terms of frequency may be the same. Note that the frequency of the previous transmission may be replaced with a frequency that has been set or notified and is currently being applied. The same applies hereinafter.

[0295] The A-IoT may be introduced within a guard band or in a standalone band. In other words, the A-IoT frequency may be provided within a guard band or in a standalone band.

[0296] The priority of the signal R may be the same as the priority of the corresponding signal Y / signal Z.

[0297] If an independent UL or transmission from int.UE to A-IoT or signal R consists of multiple transmissions, the priority may be set to the highest priority among the priorities of the multiple transmissions.

[0298] In the method b-1-1 described above, when the operations related to the two overlapping communications are executable, the operations related to the two overlapping communications can be executed appropriately.

[0299] (b-1-2) Transmit one and not transmit the other. For example, perform R2D transmission (Tx) and not perform UL transmission (Tx) that overlaps with that transmission. For example, perform UL transmission (Tx) and not perform R2D transmission (Tx) that overlaps with that transmission (hereinafter referred to as method b-1-2).

[0300] The transmissions to be performed and / or dropped may be determined based on a priority among the overlapping transmissions, for example, based on at least one of the following priorities:

[0301] Figure 27 is a diagram showing an example in which method b-1-2 is applied to the case shown in Figure 24. Similar to Figure 24, Figure 27 shows the signal flow between the base station (gNB), int.UE, and A-IoT UE. Note that since this is a DT case in Topology 2, there is information transmission to the A-IoT UE, but there is no information transmission from the A-IoT UE.

[0302] In the example of Figure 27, of the independent ULs that overlapped in Figure 24 and the transmission from int.UE to A-IoT, the independent UL is executed and the transmission from int.UE to A-IoT is dropped. Also, in the example of Figure 27, of the independent ULs that overlapped in Figure 24 and the UL for reporting communication between int.UE and A-IoT, the UL for reporting communication between int.UE and A-IoT is executed and the independent UL is dropped.

[0303] For example, transmissions to be performed and / or transmissions to be dropped may be determined based on the channel type of overlapping transmissions and the priority of signal types. For example, the priority may be set as follows: "PRACH / PUCCH" > "Signal Y / Signal Z" > "PUSCH (e.g., DG PUSCH and / or CG PUSCH)."

[0304] For example, transmissions to be performed and / or dropped may be determined based on the priority of the traffic flow of overlapping transmissions. Illustratively, the priority may be set as follows: "Signal Y / Signal Z for DO-DTT" > "UL" > "Signal Y / Signal Z for DT."

[0305] Based on the priority of the instruction / setting, the transmission to be performed and / or the transmission to be dropped may be determined. For example, the priority may be set as "UL with relatively high priority instruction" > "signal Y / signal Z with relatively low priority instruction." Note that the priority may be indicated in signal X (signal from the base station to the int. UE).

[0306] A transmission to be performed and / or a transmission to be dropped may be determined based on the priority of the transmission timing. For example, the priority may be set as "a transmission that starts transmission relatively early" > "a transmission that starts transmission relatively late."

[0307] Based on the priority of the scheduling timing, the transmissions to be performed and / or the transmissions to be dropped may be determined. For example, the priority may be set as follows: "transmissions corresponding to relatively later scheduling" > "transmissions corresponding to relatively earlier scheduling."

[0308] Priorities may be set based on numerology and / or subcarrier spacing (SCS), and transmissions to be performed and / or dropped may be determined based on the set priorities. For example, when the numerology and / or SCS are changed, priorities may be set based on whether the numerology and / or SCS are changed.

[0309] For example, a priority is set for a transmission depending on whether the SCS of the transmission has changed from the SCS of the transmission immediately preceding the transmission. For example, the priority of a transmission X whose SCS has not changed from the SCS of the transmission immediately preceding the transmission X is higher than the priority of a transmission X whose SCS has changed from the SCS of the transmission immediately preceding the transmission X.

[0310] For example, in a case where transmission X (e.g., an independent UL) and transmission Y (e.g., a transmission from an int.UE to an A-IoT) overlap, if the SCS of transmission X has not changed from the SCS of the transmission previous to transmission X, and the SCS of transmission Y has changed from the SCS of the transmission previous to transmission Y, the priority of transmission X is higher than the priority of transmission Y. Here, "transmission previous to transmission X" corresponds to, for example, an independent UL previous to the independent UL corresponding to transmission X, or a transmission from an int.UE to an A-IoT, and "transmission previous to transmission Y" corresponds to, for example, an independent UL previous to the transmission from an int.UE to an A-IoT corresponding to transmission Y, or a transmission from an int.UE to an A-IoT. Note that if there is no change in the SCS in both transmission X and transmission Y, the priorities in terms of SCS may be the same. Also, if there is a change in the SCS in both transmission X and transmission Y, the priorities in terms of SCS may be the same.

[0311] For example, a priority is set for a transmission depending on whether the numerology of the transmission has changed from the numerology of the transmission preceding the transmission. For example, the priority of a transmission X whose numerology has not changed from the numerology of the transmission preceding the transmission X is higher than the priority of a transmission X whose numerology has not changed from the numerology of the transmission preceding the transmission X.

[0312] For example, in a case where transmission X and transmission Y overlap, if the numerology of transmission X has not changed from the numerology of the transmission preceding transmission X, and the numerology of transmission Y has changed from the numerology of the transmission preceding transmission Y, transmission X has a higher priority than transmission Y. Note that if there is no change in numerology in both transmission X and transmission Y, the priorities from the perspective of numerology may be the same. Also, if there is a change in numerology in both transmission X and transmission Y, the priorities from the perspective of numerology may be the same.

[0313] For example, the priority may be set based on the waveform. For example, when the waveform used during transmission is changed by selecting a waveform from among multiple candidate waveforms, the priority may be set based on the waveform. For example, candidate waveforms include DFT-S-OFDM waveforms.

[0314] For example, a priority is set for a transmission depending on whether the waveform of that transmission has been changed from the waveform of the transmission immediately preceding that transmission. For example, if the waveform of a transmission X has not been changed from the waveform of the transmission immediately preceding that transmission, the priority of that transmission X is higher than the priority of a transmission X if the waveform of that transmission X has been changed from the waveform of the transmission immediately preceding that transmission.

[0315] For example, in a case where transmission X and transmission Y overlap, if the waveform of transmission X is unchanged from the waveform of the transmission immediately preceding transmission X, and the waveform of transmission Y is changed from the waveform of the transmission immediately preceding transmission Y, the priority of transmission X is higher than the priority of transmission Y. Note that if there is no change in waveform in both transmission X and transmission Y, the priorities from the viewpoint of waveform may be the same. Also, if there is a change in waveform in both transmission X and transmission Y, the priorities from the viewpoint of waveform may be the same.

[0316] For example, the priority may be set based on the frequency. For example, when the frequency (for example, BWP or band) is changed, the priority may be set based on whether or not the frequency has changed.

[0317] For example, a priority may be set for a transmission depending on whether the frequency of the transmission has changed from the frequency of the transmission immediately preceding it. For example, if the frequency of a transmission X has not changed from the frequency of the transmission immediately preceding it, the priority of the transmission X is higher than the priority of the transmission X if the frequency of the transmission X has changed from the frequency of the transmission immediately preceding it.

[0318] For example, in a case where transmission X and transmission Y overlap, if the frequency of transmission X has not changed from the frequency of the transmission preceding transmission X, and the frequency of transmission Y has changed from the frequency of the transmission preceding transmission Y, the priority of transmission X is higher than the priority of transmission Y. Note that if there is no change in frequency in both transmission X and transmission Y, the priorities in terms of frequency may be the same. Also, if there is a change in frequency in both transmission X and transmission Y, the priorities in terms of frequency may be the same.

[0319] The A-IoT may be introduced within a guard band or in a standalone band. In other words, the A-IoT frequency may be provided within a guard band or in a standalone band.

[0320] The priority of the signal R may be the same as the priority of the corresponding signal Y / signal Z.

[0321] If an independent UL or transmission from int.UE to A-IoT or signal R consists of multiple transmissions, the priority may be set to the highest priority among the priorities of the multiple transmissions.

[0322] In the method b-1-2 described above, one of the operations related to two overlapping communications is performed and the other is not performed, so that the operations related to the two overlapping communications can be appropriately performed. Also, by not performing some of the operations related to the two communications, the possibility of interference between the two communications can be avoided.

[0323] In method b-1-2, "drop" may be replaced with "postponement." In this case, the above-mentioned "transmission to be executed" and "transmission to be dropped" may be replaced with "transmission to be executed without postponement" and "transmission to be executed after postponement," respectively.

[0324] In method b-1-2, each of the overlapping transmissions may be dropped and not transmitted. For example, if the priority of each of the overlapping transmissions is lower than a threshold, each of the overlapping transmissions may be dropped.

[0325] (b-1-3) Overlapping transmissions are multiplexed, and resources for the multiplexed transmissions are selected to execute the transmission (hereinafter, method b-1-3).

[0326] In method b-1-3, overlapping transmissions are multiplexed and resources for the multiplexed transmissions are selected to perform the transmission. For example, multiplexing is performed in the overlap of signal R and independent UL in overlap #B.

[0327] Figure 28 is a diagram showing an example in which method b-1-3 is applied to the case shown in Figure 24. Similar to Figure 24, Figure 28 shows the signal flow between the base station (gNB), int.UE, and A-IoT UE. Note that since this is a DT case in Topology 2, there is information transmission to the A-IoT UE, but there is no information transmission from the A-IoT UE.

[0328] In Figure 28, the independent UL that overlapped in Figure 24 and the UL for reporting communication between int.UE and A-IoT (e.g., transmission of signal R) are multiplexed as a single transmission.

[0329] For example, in the case where the signal R in the overlap #B described above is a PUCCH and the information to be reported is UCI, one of the following methods is applied.

[0330] When the overlapping independent UL is a PUCCH, the signal R and the independent UL are multiplexed in the PUCCH. Note that the PUCCH resource in which the signal R and the independent UL are multiplexed may be either the PUCCH resource of the independent UL or the PUCCH resource of the signal R, or may be another PUCCH resource.

[0331] When the overlapped independent UL is a PUSCH, the signal R and the independent UL are multiplexed in a PUCCH. Note that the PUSCH resource in which the signal R and the independent UL are multiplexed may be the PUSCH resource of the independent UL.

[0332] In the case of multiplexing, channel coding and rate matching may be applied to the multiplexed information (or signals) jointly or individually. In the case of applying them individually, the coding rate of one of the signals is first determined using new parameters defined for the signal R, and then the coding rate of the other signal is determined.

[0333] When the signal R in the above-described overlap #B is a PUSCH and the overlapped independent UL is a PUCCH, UCI in the PUCCH is multiplexed with the signal R in the PUSCH. Note that the PUSCH resource onto which the UCI and the signal R are multiplexed may be the PUSCH resource of the signal R.

[0334] In the method b-1-3 described above, two overlapping transmissions are multiplexed into one transmission, so that the operations related to the two overlapping communications can be performed appropriately. Also, by multiplexing two transmissions into one transmission, the possibility of interference between the two communications can be avoided.

[0335] (b-1-4) Depending on the situation, apply either b-1-1, b-1-2, or b-1-3 above (method b-1-4).

[0336] In method b-1-4, any one of methods b-1-1, b-1-2, and b-1-3 is selectively applied. In method b-1-4, which of methods b-1-1, b-1-2, and b-1-3 is applied may be determined based on the situation. For example, it may be determined based on at least one of the following:

[0337] Whether there is a full overlap or a partial overlap For example, if one of the time periods of two transmissions completely overlaps the other, the overlap of the two transmissions corresponds to a total overlap, and if there are portions of the time periods of the two transmissions that do not overlap, the overlap of the two transmissions corresponds to a partial overlap.

[0338] -Transmission power limit For example, if the transmission power is not sufficient for simultaneous transmission (e.g., method b-1-1), method b-1-2 is applied. If the transmission power is sufficient for simultaneous transmission (e.g., method b-1-1), method b-1-1 is applied.

[0339] Frequency resources (total bandwidth of overlapping transmissions) For example, if the bands of overlapping transmissions span a bandwidth wider than a threshold (eg, X MHz), method b-1-2 may be applied; otherwise, method b-1-1 may be applied.

[0340] Frequency resources (same band (same BWP, same band, etc.) or different bands (different BWP, different bands, etc.)) For example, if the overlapping transmissions are of the same BWP, method b-1-1 may be applied, otherwise method b-1-2 may be applied. For example, if the overlapping transmissions are in the same cell group, method b-1-2 may be applied; otherwise, method b-1-1 may be applied.

[0341] Overlapping channel types / signal types For example, when there is overlap between the PRACH and signal Y / signal Z / signal R, method b-1-2 is applied. When there is overlap between the PUCCH / PUSCH and signal Y / signal Z / signal R, method b-1-1 or method b-1-3 is applied.

[0342] UE capabilities (e.g., multiplexing-related capabilities ("duplex-related capability")) UE capabilities (e.g., capabilities related to cell group / PUCCH group / RF-chain / band combination)

[0343] Numerology and / or SCS Based on the numerology and / or SCS, the method to be applied may be determined from Method b-1-1, Method b-1-2, and Method b-1-3. For example, in a case where Transmission X (e.g., an independent UL) and Transmission Y (e.g., a transmission from an int.UE to an A-IoT) overlap, if the SCS of Transmission X is the same as the SCS of Transmission Y, Method b-1-1 may be applied. For example, in a case where Transmission X and Transmission Y overlap, if the SCS of Transmission X is not the same as the SCS of Transmission Y, Method b-1-2 or Method b-1-3 may be applied.

[0344] ·Waveform For example, the method to be applied may be determined based on the waveform. The waveform may be associated with any of methods b-1-1, b-1-2, and b-1-3, and the method associated with the waveform to be used may be applied.

[0345] (variation of b-1-4) In the case of an independent UL or transmission from int.UE to A-IoT, or signal R, which is a multiple transmission, method b-1-1 is only applied if method b-1-1 is applied to all of the multiple transmissions.

[0346] In the case of an independent UL or transmission from int.UE to A-IoT, or signal R, which is a multiple transmission, method b-1-3 is only applied if method b-1-3 is applied to all of the multiple transmissions.

[0347] In the case where an independent UL or transmission from an int.UE to an A-IoT or a signal R is a plurality of transmissions, if method b-1-1 is not applied to all of the plurality of transmissions or if method b-1-3 is not applied to all of the plurality of transmissions, method b-1-2 is applied. Here, the case where method b-1-1 is not applied to all of the plurality of transmissions may be the case where a method other than method b-1-1 is applied to at least one of the plurality of transmissions.

[0348] In the method b-1-4 described above, the method to be applied to the overlapping transmissions is selected from among the methods b-1-1 to b-1-3, so that the operations related to the two overlapping communications can be appropriately performed.

[0349] (b-1-5) Execute transmission when processing time requirements are met.

[0350] Next, processing time will be described. Here, processing time means the processing time of a UE (for example, int.UE) that allows the UE to complete processing.

[0351] A processing time is defined between receiving a scheduling for an int.UE for a transmission from the BS to the A-IoT UE and transmitting the corresponding scheduling. The int.UE performs transmission only if the defined processing time requirement is met.

[0352] The processing time may be defined for each numerology and / or SCS. For example, the processing time may be defined based on which numerology and / or SCS is used, or based on whether switching of the numerology and / or SCS is required. The processing time may be associated with which numerology and / or SCS is used, whether switching of the numerology and / or SCS is required, or whether switching of the numerology and / or SCS is required and the processing time may be associated with which numerology and / or SCS is used and whether switching of the numerology and / or SCS is required.

[0353] The processing time may be defined based on the waveform. For example, the processing time may be defined based on which waveform is used, or whether a waveform switch is required. The processing time may be associated with which waveform is used, or whether a waveform switch is required, or the processing time may be associated with which waveform is used and whether a waveform switch is required.

[0354] The processing time may be defined based on frequency (e.g., carrier / band). For example, the processing time may be defined based on which carrier / band is used, or based on whether carrier / band switching is required. The processing time may be associated with which carrier / band is used, whether carrier / band switching is required, or whether carrier / band is used and whether carrier / band switching is required.

[0355] Here, if there is overlap between multiple transmissions (multiple channels / signals), the UE assumes that the overlapping channels / signals also meet the above processing time. Here, the overlapping multiple transmissions include transmission X (e.g., independent UL) and transmission Y (e.g., transmission from int. UE to A-IoT).

[0356] For example, for two overlapping channels X and Y, if the channel Y overlapping with channel X starts earlier than channel X, the processing time is compared with the time gap between receiving the scheduling from the BS and the overlapping channel Y. Note that channel X may be replaced by signal X, and channel Y may be replaced by signal Y.

[0357] For two overlapping transmissions (e.g., transmissions on channel X and channel Y), the time between the later of the two reception timings, i.e., the reception timing of the schedule for the transmission on channel X and the reception timing of the schedule for the transmission on channel Y, and the earlier of the two transmission timings, i.e., the transmission timing on channel X and the transmission timing on channel Y, may be compared with the processing time. If the time between the later of the two reception timings and the earlier of the two transmission timings is equal to or greater than the processing time, at least one of the two transmissions may be executed. For example, the two transmissions may be performed simultaneously, as in method b-1-1 above, one of the two transmissions may be dropped, as in method b-1-2, or the two transmissions may be multiplexed, as in method b-1-3.

[0358] For example, in two overlapping channels X and Y, if the numerology of channel X and / or the numerology at the time of receiving the scheduling of channel X is different from the numerology of channel Y and / or the numerology at the time of receiving the scheduling of channel Y, the processing time is determined based on one of the following numerologies. Note that channel may be replaced with signal. Furthermore, the scheduling of transmission of channel X and the scheduling of transmission of channel Y may also be included in the above-mentioned numerology comparison. - The smaller of the two numerologies -Numerology, whichever is larger Numerology of the channel that starts first among multiple overlapping channels Numerology of the channel that starts later among overlapping channels Numerology of the channel with the larger time width among multiple overlapping channels Numerology of the channel with the smaller time width among multiple overlapping channels

[0359] For example, in two overlapping channels X and Y, if the SCS of channel X and / or the SCS at the time of receiving the scheduling of channel X is different from the SCS of channel Y and / or the SCS at the time of receiving the scheduling of channel Y, the processing time is determined based on one of the following SCSs. Note that the channel may be replaced with a signal. Furthermore, the scheduling of the transmission of channel X and the scheduling of the transmission of channel Y may also be included in the above-mentioned SCS comparison. -Whichever is smaller, SCS Whichever is larger, SCS - The SCS of the channel that starts first among multiple overlapping channels -SCS of the channel that starts later among multiple overlapping channels -SCS of the channel with the larger time width among multiple overlapping channels -SCS of the channel with the smaller time width among multiple overlapping channels

[0360] For example, for two overlapping channels X and Y, if the waveform of channel X differs from the waveform at the time of receiving the scheduling of channel X and / or channel Y and / or the waveform of channel Y, the processing time is determined based on one of the following waveforms. Note that the channel may be replaced with a signal. Furthermore, the scheduling of transmission of channel X and the scheduling of transmission of channel Y may also be included in the above-mentioned waveform comparison. The waveform associated with the waveform that takes longer to process than the other waveforms. - Waveform of the channel that starts first among multiple overlapping channels Waveform of the channel that starts later among multiple overlapping channels Waveform of the channel with the larger time width among multiple overlapping channels Waveform of the channel with the smaller time width among multiple overlapping channels

[0361] In the above b-1-5, the int.UE receives first scheduling information regarding the scheduling of a first communication (e.g., transmission from the int.UE to the A-IoT) related to communication between the BS and the A-IoT UE via the int.UE, and executes the first communication scheduled by the first scheduling information after a processing time has elapsed since receiving the first scheduling information. Then, if an overlap occurs between the first communication and a second communication (e.g., an independent UL) related to communication between the int.UE and the BS, the int.UE executes at least one of the first communication and the second communication after a processing time has elapsed since receiving the first scheduling information.

[0362] According to b-1-5 above, when an int.UE communicates as an int.UE and / or when it communicates other than as an int.UE, a specific processing time can be secured for the int.UE to perform signal processing, etc., from the time it receives scheduling information related to the communication until it transmits the information corresponding to the scheduling. Furthermore, even if the communication as an int.UE overlaps with other communication (e.g., an independent UL), a specific processing time can be secured for the int.UE to perform signal processing, etc., from the time it receives scheduling until it transmits the information corresponding to the scheduling.

[0363] (b-1 overlap variation) Methods b-1-1 to b-1-4 described in b-1 above may be applied to overlap between transmission and reception, as well as overlap between transmissions, or overlap between receptions. For example, "transmission" in each of the above methods may be replaced with "reception."

[0364] There are two cases of overlap between transmission and reception: When an int.UE receives as an int.UE, other transmissions (e.g., independent ULs) occur at the int.UE, and the reception as the int.UE and the other transmissions overlap in time. When an int.UE transmits as an int.UE, another reception occurs at the int.UE, and the transmission as int.UE and the other reception overlap in time.

[0365] Here, the other reception is reception independent of operation as an int.UE. Hereinafter, reception independent of operation as an int.UE may be referred to as independent reception (independent RX). For example, in the case of b-1, independent reception includes downlink reception as a UE. Hereinafter, downlink reception as a UE independent of operation as an int.UE may be referred to as independent DL or independent DL reception.

[0366] Reception as an int.UE includes receiving signals transmitted from the A-IoT UE to the int.UE and receiving signals transmitted from the base station to the int.UE.

[0367] Furthermore, there are the following cases of overlap between receptions: When an int.UE receives as an int.UE, other reception (for example, an independent DL) occurs at the int.UE, and the reception as the int.UE and the other reception overlap in time.

[0368] In the case of overlapping transmission and reception, any of methods b-1-1 to b-1-4 may be applied as follows. (i) When method b-1-1 is applied, transmission and reception are performed simultaneously. (ii) When method b-1-2 is applied, one of transmission and reception is performed and the other is dropped. Which is performed and / or which is dropped may be determined based on the priority between the overlapping transmission and reception. (iii) When method b-1-4 is applied, it is determined whether to apply method b-1-1 or method b-1-2 (e.g., either (i) or (ii) above). For example, similar to method b-1-4, the determination may be made based on the circumstances. Here, the circumstances that are the factors for the determination include at least one of whether there is full overlap or partial overlap, the type of overlapping channel / signal, the capability of the UE, etc.

[0369] In the case of overlapping reception, any of methods b-1-1 to b-1-4 may be applied as follows. (iv) When method b-1-1 is applied, overlapping reception is performed simultaneously. (v) When method b-1-2 is applied, one of the overlapping receptions is executed and the other is dropped. Which is executed and / or which is dropped may be determined based on the priority between the overlapping receptions. (vi) When method b-1-4 is applied, it is determined whether to apply method b-1-1 or method b-1-2 (e.g., either (iv) or (v) above). For example, as with method b-1-4, the determination may be made based on circumstances. Here, the circumstances that contribute to the determination include at least one of whether there is full overlap or partial overlap, the type of overlapping channels / signals, the capability of the UE, etc.

[0370] Although the above description has been given using an example of overlap between two operations (transmit and transmit, transmit and receive, receive and receive), the present disclosure is not limited to this example and may be applied to cases where overlap occurs between three or more operations.

[0371] For example, methods b-1-1 to b-1-4 may be applied to overlap between transmission and reception, or may be applied to overlap between transmission and reception.

[0372] For example, in a case where the transmission in step 2 (hereinafter, TX1) and the reception in step 3 (hereinafter, RX) of the communication flow described using Figure 12 etc. overlap each other, and the transmission of an independent UL (hereinafter, TX2) further overlaps, any of the above methods b-1-1 to b-1-4 may be applied in the following manner. (vii) When method b-1-1 is applied, overlapping TX1, TX2 and RX are executed simultaneously. (viii) When method b-1-2 is applied, some of the overlapping operations are executed and the rest are dropped. For example, TX1 and RX are executed and TX2 is dropped. Alternatively, TX2 is executed and TX1 and RX are dropped. Which of the three overlapping operations is executed and / or dropped may be determined based on the priority among the overlapping operations (e.g., TX1, TX2, and RX). (ix) When method b-1-4 is applied, it is determined whether to apply method b-1-1 or method b-1-2 (e.g., either (vii) or (viii) above). For example, as with method b-1-4, the determination may be made based on circumstances. Here, the circumstances that contribute to the determination include at least one of whether there is full overlap or partial overlap, the type of overlapping channels / signals, the capability of the UE, etc.

[0373] Note that communication between the int.UE and the A-IoT UE may be classified as a sidelink from the perspective of the int.UE. In this case, the process (or operation) for the overlap case between the UL and the SL may be applied to overlap #A. Also, in this case, the process (or operation) for the overlap case between the UL and the UL associated with the SL may be applied to overlap #B.

[0374] Alternatively, communication between an int.UE and an A-IoT UE may be classified as downlink / uplink from the perspective of the int.UE, e.g., communication from an int.UE to an A-IoT UE is classified as downlink (DL), and communication from an A-IoT UE to an int.UE is classified as uplink (UL).

[0375] In the above-described b-1, when an overlap occurs between a first communication between the int.UE and a base station and a second communication between the base station and the A-IoT UE via the int.UE, the int.UE decides to execute at least one of the first and second communications, and executes the determined at least one of the communications. This allows appropriate communication to be performed when a communication different from the communication in the A-IoT communication system overlaps.

[0376] (b-2) When a resource in the source pool is selected by the int.UE for R2D transmission (Tx) / D2R reception (Rx) and the selected resource overlaps with a resource for SL reception (Rx) / SL transmission (Tx), the int.UE performs resource processing as follows (b-2-1) to (b-2-4).

[0377] For example, in topology 2, when an int.UE transmits as an int.UE, other transmissions (e.g., independent transmissions) may occur at the int.UE, and the transmission as the int.UE and the other transmissions may overlap in time.

[0378] In b-2, independent transmission includes SL transmission as a UE. Hereinafter, sidelink transmission as a UE, independent of operation as an int.UE, may be referred to as independent SL (independent UL) or independent SL transmission.

[0379] Here, for the above-mentioned overlap, the following two overlaps, overlap #A' and overlap #B', are considered. Overlap #A': Overlap between independent SL transmission and transmission from int.UE to A-IoT Overlap #B': overlap between independent UL transmission and UL for reporting communication between int.UE and A-IoT (e.g., transmission of signal R)

[0380] In addition, during overlap #A', transmission from int.UE to A-IoT includes transmission of at least one of the following signals: A signal to wake up the A-IoT UE and / or a carrier waveform provided to the A-IoT for backscattering (e.g., signal Y) Signal for transmitting information to A-IoT UE (e.g., signal Z) Note that signal Z may not contain information and may be a signal for backscatter transmission.

[0381] Figure 29 is a diagram showing an example of overlap in the DT case. Similar to Figure 12, Figure 29 shows the signal flow between the base station (gNB), int.UE, and A-IoT UE. Note that since this is the DT case in Topology 2, there is information transmission to the A-IoT UE, but there is no information transmission from the A-IoT UE. Figure 29 also shows that another UE other than the int.UE performs SL communication with the int.UE.

[0382] Figure 29 shows an example where an independent SL transmission and a transmission from an int.UE to an A-IoT overlap. Figure 29 also shows an example where an independent SL transmission and a UL for reporting communication between an int.UE and an A-IoT overlap.

[0383] Figure 30 is a diagram showing an example of overlap in the case of DO-DTT. Similar to Figure 13, Figure 30 shows the signal flow between the base station (gNB), int.UE, and A-IoT UE. Note that, since this is the case of DO-DTT in Topology 2, there is information transmission to the A-IoT UE and information transmission from the A-IoT UE. Figure 30 also shows that another UE other than the int.UE performs SL communication with the int.UE.

[0384] Figure 30 shows an example where an independent SL transmission and a transmission from an int.UE to an A-IoT overlap. Figure 30 also shows an example where an independent SL transmission and a UL for reporting communication between an int.UE and an A-IoT overlap.

[0385] Note that in b-2 of this embodiment, overlap is not limited to overlap of actual timing. For example, in this embodiment, overlap may not be overlap of actual timing, but may include multiple transmissions in the same time unit (e.g., any one of a slot, a certain time interval, and a switching period). For example, taking overlap #A' as an example, if an independent SL transmission and a transmission from int.UE to A-IoT are instructed / configured to be performed in the same slot, it may be determined that the independent SL transmission and the transmission from int.UE to A-IoT overlap. Furthermore, overlap may mean overlap at least in the time domain.

[0386] In topology 2, when an overlap occurs between a transmission related to the operation of the int.UE and another independent SL, the int.UE handles the overlap.

[0387] Specific response methods are described below. Each of the methods described below may be applied to each overlap type (e.g., overlap #A' and #B'). The mechanisms applied in the methods described below may differ between overlap types. The mechanisms applied in the methods described below may be applied based on the capabilities of the int.UE.

[0388] Note that the independent SL transmission may be transmission based on the scheduling of the NW, or may be transmission based on autonomous operation of the UE.

[0389] (b-2-1) Simultaneous transmission is performed. The transmission power of each may be determined based on the priority (hereinafter, method b-2-1).

[0390] In method b-2-1, overlapping transmissions are performed simultaneously. Note that in method b-2-1, transmission power may be allocated between overlapping transmissions. For example, a priority for power allocation may be set. Then, a higher transmission power may be allocated to a transmission with a higher priority.

[0391] Figure 31 is a diagram showing an example in which method b-2-1 is applied to the case shown in Figure 29. Similar to Figure 29, Figure 31 shows the flow of signals between the base station (gNB), int.UE, A-IoT UE, and other UEs. Note that since this is a DT case in Topology 2, there is information transmission to the A-IoT UE, but there is no information transmission from the A-IoT UE.

[0392] Figure 31 shows an example in which an overlapping independent SL transmission and a transmission from an int.UE to an A-IoT are transmitted simultaneously. Figure 31 also shows an example in which an overlapping independent SL transmission and a UL for reporting communication between an int.UE and an A-IoT are transmitted simultaneously.

[0393] Transmission power may be allocated based on the priority between overlapping transmissions. For example, transmission power may be allocated based on at least one of the following priorities: In the following description, "a" > "b" indicates that a has a higher priority than b:

[0394] For example, transmission power may be allocated based on the priority of the channel type and signal type of overlapping transmissions. For example, the priority may be set as follows: "PSCCH (Physical Sidelink Control Channel) / PSSCH (Physical Sidelink Shared Channel) (DG and / or CG) / PSFCH (Physical Sidelink Feedback Channel)" > "Signal Y / Signal Z" > "Sidelink-Synchronization Signal Block (S-SSB)."

[0395] For example, transmit power may be allocated based on the priority of overlapping transmission traffic flows, such as "signal Y / signal Z for DO-DTT" > "SL" > "signal Y / signal Z for DT."

[0396] Transmission power may be allocated based on the priority of the instruction / setting. For example, the priority may be set as follows: "SL with a relatively high priority instruction" > "signal Y / signal Z with a relatively low priority instruction." Alternatively, the priority may be set as follows: "signal Y / signal Z with a relatively high priority instruction" > "SL with a relatively low priority instruction." Note that the priority may be indicated in signal X (a signal from the base station to the int.UE). Furthermore, the priority for the SL may be specified by a specification, may be indicated / set, or may be determined by the int.UE.

[0397] The transmission power may be allocated based on the priority of the transmission timing. For example, the priority may be set as follows: "transmission with a relatively early start of transmission" > "transmission with a relatively late start of transmission."

[0398] Transmission power may be allocated based on the priority of the timing of scheduling / decision. For example, the priority may be set as follows: "transmission corresponding to relatively late scheduling / decision" > "transmission corresponding to relatively early scheduling / decision."

[0399] The transmit power may be allocated based on how the SL transmission is determined, for example, priority may be set as follows: "Signal Y / Signal Z" > "SL based on UE autonomous resource allocation."

[0400] Priorities may be set based on numerology and / or subcarrier spacing (SCS), and transmission power may be allocated based on the set priorities. For example, when the numerology and / or SCS are changed, priorities may be set based on whether the numerology and / or SCS have changed.

[0401] For example, for a certain transmission, priority is set depending on whether the SCS of the transmission has changed from the SCS of the transmission immediately preceding the transmission. For example, the priority of a certain transmission X whose SCS has not changed from the SCS of the transmission immediately preceding the transmission X is higher than the priority of a certain transmission X whose SCS has changed from the SCS of the transmission immediately preceding the transmission X. Note that the previous transmission may refer to, for example, the immediately preceding or most recent transmission. Alternatively, the SCS of the previous transmission may be replaced with the SCS currently being applied after being set or notified. The same applies hereinafter.

[0402] For example, in a case where transmission X (e.g., an independent SL transmission) and transmission Y (e.g., a transmission from an int.UE to an A-IoT) overlap, if the SCS of transmission X has not changed from the SCS of the transmission previous to transmission X, and the SCS of transmission Y has changed from the SCS of the transmission previous to transmission Y, the priority of transmission X is higher than the priority of transmission Y. Here, "transmission previous to transmission X" corresponds to, for example, an independent SL transmission previous to the independent SL transmission corresponding to transmission X or a transmission from an int.UE to an A-IoT, and "transmission previous to transmission Y" corresponds to, for example, an independent SL transmission previous to the transmission from an int.UE to an A-IoT corresponding to transmission Y, or a transmission from an int.UE to an A-IoT. Note that if there is no change in the SCS in both transmission X and transmission Y, the priorities in terms of the SCS may be the same. Also, if there is a change in the SCS in both transmission X and transmission Y, the priorities in terms of the SCS may be the same.

[0403] For example, in a certain transmission, priority is set depending on whether the numerology of the transmission has changed from the numerology of the transmission immediately preceding the transmission. For example, if the numerology of a certain transmission X has not changed from the numerology of the transmission immediately preceding the transmission X, the priority of the transmission X is higher than the priority of a certain transmission X if the numerology of the transmission X has not changed from the numerology of the transmission immediately preceding the transmission X. Note that the numerology of the previous transmission may be replaced by the numerology that has been set or notified and is currently being applied. The same applies below.

[0404] For example, in a case where transmission X and transmission Y overlap, if the numerology of transmission X has not changed from the numerology of the transmission preceding transmission X, and the numerology of transmission Y has changed from the numerology of the transmission preceding transmission Y, transmission X has a higher priority than transmission Y. Note that if there is no change in numerology in both transmission X and transmission Y, the priorities from the perspective of numerology may be the same. Also, if there is a change in numerology in both transmission X and transmission Y, the priorities from the perspective of numerology may be the same.

[0405] For example, the priority may be set based on the waveform. For example, when the waveform used during transmission is changed by selecting a waveform from among multiple candidate waveforms, the priority may be set based on the waveform. For example, candidate waveforms include DFT-S-OFDM waveforms, etc. Alternatively, modulation methods such as OOK (On-Off-Keying) may be included. The same applies hereinafter.

[0406] For example, a priority is set for a transmission depending on whether the waveform of that transmission has been changed from the waveform of the transmission immediately preceding that transmission. For example, if the waveform of a transmission X has not been changed from the waveform of the transmission immediately preceding that transmission, the priority of that transmission X is higher than the priority of a transmission X if the waveform of that transmission X has been changed from the waveform of the transmission immediately preceding that transmission.

[0407] For example, in a case where transmission X and transmission Y overlap, if the waveform of transmission X has not changed from the waveform of the transmission immediately preceding transmission X, and the waveform of transmission Y has changed from the waveform of the transmission immediately preceding transmission Y, the priority of transmission X is higher than the priority of transmission Y. Note that if there is no change in waveform in both transmission X and transmission Y, the priorities from the viewpoint of waveform may be the same. Also, if there is a change in waveform in both transmission X and transmission Y, the priorities from the viewpoint of waveform may be the same. Note that the waveform of the previous transmission may be replaced with the waveform that has been set or notified and is currently being applied. The same applies below.

[0408] For example, the priority may be set based on the frequency. For example, when the frequency (for example, BWP or band) is changed, the priority may be set based on whether or not the frequency has changed.

[0409] For example, a priority may be set for a transmission depending on whether the frequency of the transmission has changed from the frequency of the transmission immediately preceding it. For example, if the frequency of a transmission X has not changed from the frequency of the transmission immediately preceding it, the priority of the transmission X is higher than the priority of the transmission X if the frequency of the transmission X has changed from the frequency of the transmission immediately preceding it.

[0410] For example, in a case where transmission X and transmission Y overlap, if the frequency of transmission X has not been changed from the frequency of the transmission previous to transmission X, and the frequency of transmission Y has been changed from the frequency of the transmission previous to transmission Y, the priority of transmission X is higher than the priority of transmission Y. Note that if there is no change in frequency in both transmission X and transmission Y, the priorities in terms of frequency may be the same. Also, if there is a change in frequency in both transmission X and transmission Y, the priorities in terms of frequency may be the same. Note that the frequency of the previous transmission may be replaced with a frequency that has been set or notified and is currently being applied. The same applies hereinafter.

[0411] The A-IoT may be introduced within a guard band or in a standalone band. In other words, the A-IoT frequency may be provided within a guard band or in a standalone band.

[0412] The priority of the signal R may be the same as the priority of the corresponding signal Y / signal Z.

[0413] If an independent SL transmission, or a transmission from int.UE to A-IoT, or a signal R consists of multiple transmissions, the priority may be set to the highest priority among the priorities of the multiple transmissions.

[0414] In the method b-2-1 described above, when the operations related to the two overlapping communications are executable, the operations related to the two overlapping communications can be executed appropriately.

[0415] (b-2-2) Transmit one and not the other (hereinafter referred to as method b-2-2). For example, perform R2D transmission (Tx) and not perform SL transmission (Tx) that overlaps with that transmission. For example, perform SL transmission (Tx) and not perform R2D transmission (Tx) that overlaps with that transmission.

[0416] The transmissions to be performed and / or dropped may be determined based on a priority among the overlapping transmissions, for example, based on at least one of the following priorities:

[0417] Figure 32 is a diagram showing an example in which method b-2-2 is applied to the case shown in Figure 29. Similar to Figure 29, Figure 32 shows the flow of signals between the base station (gNB), int.UE, A-IoT UE, and other UEs. Note that since this is a DT case in Topology 2, there is information transmission to the A-IoT UE, but there is no information transmission from the A-IoT UE.

[0418] In the example of Figure 32, of the independent SL transmission that overlapped in Figure 29 and the transmission from int.UE to A-IoT, the independent SL transmission is executed, and the transmission from int.UE to A-IoT is dropped. Also, in the example of Figure 32, of the independent SL transmission that overlapped in Figure 29 and the UL for reporting communication between int.UE and A-IoT, the UL for reporting communication between int.UE and A-IoT is executed, and the independent SL transmission is dropped.

[0419] For example, transmissions to be performed and / or transmissions to be dropped may be determined based on the channel type of overlapping transmissions and the priority of signal types. For example, the priority may be set as follows: "PSCCH / PSSCH (DG and / or CG) / PSFCH" > "Signal Y / Signal Z" > "S-SSB."

[0420] For example, transmissions to be performed and / or transmissions to be dropped may be determined based on the priority of the traffic flow of overlapping transmissions. Illustratively, the priority may be set as follows: "Signal Y / Signal Z for DO-DTT" > "SL" > "Signal Y / Signal Z for DT."

[0421] Based on the priority of the instruction / setting, the transmission to be performed and / or the transmission to be dropped may be determined. For example, the priority may be set as "SL with a relatively high priority instruction" > "signal Y / signal Z with a relatively low priority instruction." Alternatively, the priority may be set as "signal Y / signal Z with a relatively high priority instruction" > "SL with a relatively low priority instruction." Note that the priority may be indicated in signal X (a signal from the base station to the int.UE). Furthermore, the priority for the SL may be specified by a specification, may be indicated / set, or may be determined by the int.UE.

[0422] A transmission to be performed and / or a transmission to be dropped may be determined based on the priority of the transmission timing. For example, the priority may be set as "a transmission that starts transmission relatively early" > "a transmission that starts transmission relatively late."

[0423] The transmissions to be performed and / or dropped may be determined based on the priority of the timing of the scheduling / decision. For example, the priority may be set as follows: "Transmissions corresponding to relatively late scheduling / decisions" > "Transmissions corresponding to relatively early scheduling / decisions."

[0424] The transmit power may be allocated based on how the SL transmission is determined, for example, priority may be set as follows: "Signal Y / Signal Z" > "SL based on UE autonomous resource allocation."

[0425] Priorities may be set based on numerology and / or subcarrier spacing (SCS), and transmissions to be performed and / or dropped may be determined based on the set priorities. For example, when the numerology and / or SCS are changed, priorities may be set based on whether the numerology and / or SCS are changed.

[0426] For example, a priority is set for a transmission depending on whether the SCS of the transmission has changed from the SCS of the transmission immediately preceding the transmission. For example, the priority of a transmission X whose SCS has not changed from the SCS of the transmission immediately preceding the transmission X is higher than the priority of a transmission X whose SCS has changed from the SCS of the transmission immediately preceding the transmission X.

[0427] For example, in a case where transmission X (e.g., an independent SL transmission) and transmission Y (e.g., a transmission from an int.UE to an A-IoT) overlap, if the SCS of transmission X has not changed from the SCS of the transmission previous to transmission X, and the SCS of transmission Y has changed from the SCS of the transmission previous to transmission Y, the priority of transmission X is higher than the priority of transmission Y. Here, "transmission previous to transmission X" corresponds to, for example, an independent SL transmission previous to the independent SL transmission corresponding to transmission X or a transmission from an int.UE to an A-IoT, and "transmission previous to transmission Y" corresponds to, for example, an independent SL transmission previous to the transmission from an int.UE to an A-IoT corresponding to transmission Y, or a transmission from an int.UE to an A-IoT. Note that if there is no change in the SCS in both transmission X and transmission Y, the priorities in terms of the SCS may be the same. Also, if there is a change in the SCS in both transmission X and transmission Y, the priorities in terms of the SCS may be the same.

[0428] For example, a priority is set for a transmission depending on whether the numerology of the transmission has changed from the numerology of the transmission preceding the transmission. For example, the priority of a transmission X whose numerology has not changed from the numerology of the transmission preceding the transmission X is higher than the priority of a transmission X whose numerology has not changed from the numerology of the transmission preceding the transmission X.

[0429] For example, in a case where transmission X and transmission Y overlap, if the numerology of transmission X has not changed from the numerology of the transmission preceding transmission X, and the numerology of transmission Y has changed from the numerology of the transmission preceding transmission Y, transmission X has a higher priority than transmission Y. Note that if there is no change in numerology in both transmission X and transmission Y, the priorities from the perspective of numerology may be the same. Also, if there is a change in numerology in both transmission X and transmission Y, the priorities from the perspective of numerology may be the same.

[0430] For example, the priority may be set based on the waveform. For example, when the waveform used during transmission is changed by selecting a waveform from among multiple candidate waveforms, the priority may be set based on the waveform. For example, candidate waveforms include DFT-S-OFDM waveforms.

[0431] For example, a priority is set for a transmission depending on whether the waveform of that transmission has been changed from the waveform of the transmission immediately preceding that transmission. For example, if the waveform of a transmission X has not been changed from the waveform of the transmission immediately preceding that transmission, the priority of that transmission X is higher than the priority of a transmission X if the waveform of that transmission X has been changed from the waveform of the transmission immediately preceding that transmission.

[0432] For example, in a case where transmission X and transmission Y overlap, if the waveform of transmission X is unchanged from the waveform of the transmission immediately preceding transmission X, and the waveform of transmission Y is changed from the waveform of the transmission immediately preceding transmission Y, the priority of transmission X is higher than the priority of transmission Y. Note that if there is no change in waveform in both transmission X and transmission Y, the priorities from the viewpoint of waveform may be the same. Also, if there is a change in waveform in both transmission X and transmission Y, the priorities from the viewpoint of waveform may be the same.

[0433] For example, the priority may be set based on the frequency. For example, when the frequency (for example, BWP or band) is changed, the priority may be set based on whether or not the frequency has changed.

[0434] For example, a priority may be set for a transmission depending on whether the frequency of the transmission has changed from the frequency of the transmission immediately preceding it. For example, if the frequency of a transmission X has not changed from the frequency of the transmission immediately preceding it, the priority of the transmission X is higher than the priority of the transmission X if the frequency of the transmission X has changed from the frequency of the transmission immediately preceding it.

[0435] For example, in a case where transmission X and transmission Y overlap, if the frequency of transmission X has not changed from the frequency of the transmission preceding transmission X, and the frequency of transmission Y has changed from the frequency of the transmission preceding transmission Y, the priority of transmission X is higher than the priority of transmission Y. Note that if there is no change in frequency in both transmission X and transmission Y, the priorities in terms of frequency may be the same. Also, if there is a change in frequency in both transmission X and transmission Y, the priorities in terms of frequency may be the same.

[0436] The A-IoT may be introduced within a guard band or in a standalone band. In other words, the A-IoT frequency may be provided within a guard band or in a standalone band.

[0437] The priority of the signal R may be the same as the priority of the corresponding signal Y / signal Z.

[0438] If an independent SL, or a transmission from int.UE to A-IoT, or a signal R consists of multiple transmissions, the priority may be set to the highest priority among the priorities of the multiple transmissions.

[0439] In the method b-2-2 described above, one of the operations related to two overlapping communications is performed and the other is not performed, so that the operations related to the two overlapping communications can be appropriately performed. Also, by not performing some of the operations related to the two communications, the possibility of interference between the two communications can be avoided.

[0440] In method b-2-2, "drop" may be replaced with "postponement." In this case, the above-mentioned "transmission to be executed" and "transmission to be dropped" may be replaced with "transmission to be executed without postponement" and "transmission to be executed after postponement," respectively.

[0441] In method b-2-2, each of the overlapping transmissions may be dropped and not transmitted. For example, if the priority of each of the overlapping transmissions is lower than a threshold, each of the overlapping transmissions may be dropped.

[0442] (b-2-3) Depending on the situation, apply either b-2-1 or b-2-2 above (method b-2-3).

[0443] In method b-2-3, either method b-2-1 or method b-2-2 is selectively applied. In method b-2-3, which of method b-2-1 or method b-2-2 is applied may be determined based on the situation. For example, it may be determined based on at least one of the following:

[0444] Whether there is a full overlap or a partial overlap For example, if one of the time periods of two transmissions completely overlaps the other, the overlap of the two transmissions corresponds to a total overlap, and if there are portions of the time periods of the two transmissions that do not overlap, the overlap of the two transmissions corresponds to a partial overlap.

[0445] -Transmission power limit For example, if the transmission power is not sufficient for simultaneous transmission (e.g., method b-2-1), method b-2-2 is applied. If the transmission power is sufficient for simultaneous transmission (e.g., method b-2-1), method b-2-1 is applied.

[0446] Frequency resources (total bandwidth of overlapping transmissions) For example, if the bands of overlapping transmissions span a bandwidth wider than a threshold (eg, X MHz), method b-2-2 may be applied; otherwise, method b-2-1 may be applied.

[0447] Frequency resources (same band (same BWP, same band, etc.) or different bands (different BWP, different bands, etc.)) For example, if the overlapping transmissions are of the same BWP, method b-2-1 may be applied, and if not, method b-2-2 may be applied. For example, if the overlapping transmissions are in the same cell group, method b-2-2 may be applied; otherwise, method b-2-1 may be applied.

[0448] Overlapping channel types / signal types For example, when there is overlap between "PSCCH / PSSCH (DG and / or CG) / PSFCH" and "signal Y / signal Z / signal R," method b-2-2 is applied. Also, when there is overlap between "S-SSB" and "signal Y / signal Z / signal R," method b-2-1 is applied.

[0449] UE capabilities (e.g., capabilities related to cell group / PUCCH group / RF-chain / band combination)

[0450] Numerology and / or SCS The method to be applied may be determined from Method b-2-1 and Method b-2-2 based on the numerology and / or SCS. For example, in a case where Transmission X (e.g., an independent SL transmission) and Transmission Y (e.g., a transmission from an int.UE to an A-IoT) overlap, if the SCS of Transmission X is the same as the SCS of Transmission Y, Method b-2-1 may be applied. For example, in a case where Transmission X and Transmission Y overlap, if the SCS of Transmission X is not the same as the SCS of Transmission Y, Method b-2-2 may be applied.

[0451] ·Waveform For example, the method to be applied may be determined based on the waveform. The waveform may be associated with either method b-2-1 or method b-2-2, and the method associated with the waveform to be used may be applied.

[0452] In the method b-2-3 described above, the method to be applied to the overlapping transmissions is selected from among the methods b-2-1 to b-2-2, so that the operations related to the two overlapping communications can be appropriately performed.

[0453] (variation of b-2-3) In the case of an independent SL transmission, or a transmission from int.UE to A-IoT, or a case where signal R is a multiple transmission, only method b-2-1 is applied if method b-2-1 is applied to all of the multiple transmissions.

[0454] In the case of an independent SL transmission, or a transmission from an int.UE to an A-IoT, or a case where the signal R is a plurality of transmissions, if method b-2-1 is not applied to all of the plurality of transmissions, method b-2-2 is applied. Here, the case where method b-2-1 is not applied to all of the plurality of transmissions may be the case where a method other than method b-2-1 is applied to at least one of the plurality of transmissions.

[0455] (b-2-4) Execute transmission when processing time requirements are met.

[0456] Next, processing time will be described. Here, processing time means the processing time of a UE (for example, int.UE) that allows the UE to complete processing.

[0457] A processing time is defined between receiving a scheduling for an int.UE for a transmission from the BS to the A-IoT UE and transmitting the corresponding scheduling. The int.UE performs transmission only if the defined processing time requirement is met.

[0458] The processing time may be defined for each numerology and / or SCS. For example, the processing time may be defined based on which numerology and / or SCS is used, or based on whether switching of the numerology and / or SCS is required. The processing time may be associated with which numerology and / or SCS is used, whether switching of the numerology and / or SCS is required, or whether switching of the numerology and / or SCS is required and the processing time may be associated with which numerology and / or SCS is used and whether switching of the numerology and / or SCS is required.

[0459] The processing time may be defined based on the waveform. For example, the processing time may be defined based on which waveform is used, or whether a waveform switch is required. The processing time may be associated with which waveform is used, or whether a waveform switch is required, or the processing time may be associated with which waveform is used and whether a waveform switch is required.

[0460] The processing time may be defined based on frequency (e.g., carrier / band). For example, the processing time may be defined based on which carrier / band is used, or based on whether carrier / band switching is required. The processing time may be associated with which carrier / band is used, whether carrier / band switching is required, or whether carrier / band is used and whether carrier / band switching is required.

[0461] Here, if there is overlap between multiple transmissions (multiple channels / signals), the UE assumes that the overlapping channels / signals also meet the above processing time. Here, the overlapping multiple transmissions include transmission X (e.g., an independent SL transmission) and transmission Y (e.g., a transmission from the int. UE to the A-IoT).

[0462] For example, for two overlapping channels X and Y, if the channel Y overlapping with channel X starts earlier than channel X, the processing time is compared with the time gap between receiving the scheduling from the BS and the overlapping channel Y. Note that channel X may be replaced by signal X, and channel Y may be replaced by signal Y.

[0463] For two overlapping transmissions (e.g., transmissions on channel X and channel Y), the time between the later of the two reception timings, i.e., the reception timing of the scheduled transmission for channel X and the reception timing of the scheduled transmission for channel Y, and the earlier of the two transmission timings, i.e., the transmission timing for channel X and the transmission timing for channel Y, may be compared with the processing time. If the time between the later of the two reception timings and the earlier of the two transmission timings is equal to or greater than the processing time, at least one of the two transmissions may be executed. For example, the two transmissions may be performed simultaneously, as in method b-2-1 above, or one of the two transmissions may be dropped, as in method b-2-2.

[0464] For example, in two overlapping channels X and Y, if the numerology of channel X and / or the numerology at the time of receiving the scheduling of channel X is different from the numerology of channel Y and / or the numerology at the time of receiving the scheduling of channel Y, the processing time is determined based on one of the following numerologies. Note that channel may be replaced with signal. Furthermore, the scheduling of transmission of channel X and the scheduling of transmission of channel Y may also be included in the above-mentioned numerology comparison. - The smaller of the two numerologies -Numerology, whichever is larger Numerology of the channel that starts first among multiple overlapping channels Numerology of the channel that starts later among overlapping channels Numerology of the channel with the larger time width among multiple overlapping channels Numerology of the channel with the smaller time width among multiple overlapping channels

[0465] For example, in two overlapping channels X and Y, if the SCS of channel X and / or the SCS at the time of receiving the scheduling of channel X is different from the SCS of channel Y and / or the SCS at the time of receiving the scheduling of channel Y, the processing time is determined based on one of the following SCSs. Note that the channel may be replaced with a signal. Furthermore, the scheduling of the transmission of channel X and the scheduling of the transmission of channel Y may also be included in the above-mentioned SCS comparison. -Whichever is smaller, SCS Whichever is larger, SCS - The SCS of the channel that starts first among multiple overlapping channels -SCS of the channel that starts later among multiple overlapping channels -SCS of the channel with the larger time width among multiple overlapping channels -SCS of the channel with the smaller time width among multiple overlapping channels

[0466] For example, for two overlapping channels X and Y, if the waveform of channel X differs from the waveform at the time of receiving the scheduling of channel X and / or channel Y and / or the waveform of channel Y, the processing time is determined based on one of the following waveforms. Note that the channel may be replaced with a signal. Furthermore, the scheduling of transmission of channel X and the scheduling of transmission of channel Y may also be included in the above-mentioned waveform comparison. The waveform associated with the waveform that takes longer to process than the other waveforms. - Waveform of the channel that starts first among multiple overlapping channels Waveform of the channel that starts later among multiple overlapping channels Waveform of the channel with the larger time width among multiple overlapping channels Waveform of the channel with the smaller time width among multiple overlapping channels

[0467] In the above b-2-4, the int.UE receives first scheduling information regarding the scheduling of a first communication (e.g., a transmission from the int.UE to the A-IoT) between the BS and the A-IoT UE via the int.UE, and executes the first communication scheduled by the first scheduling information after a processing time has elapsed since the reception of the first scheduling information. Then, if an overlap occurs between the first communication and a second communication (e.g., an independent SL transmission) between the int.UE and a UE other than the int.UE, the int.UE executes at least one of the first communication and the second communication after a processing time has elapsed since the reception of the first scheduling information.

[0468] According to the above b-2-4, when an int.UE communicates as an int.UE and / or when it communicates other than as an int.UE, a specific processing time can be secured for the int.UE to perform signal processing, etc., from the time it receives scheduling information related to the communication until it performs transmission corresponding to the scheduling. Furthermore, even if communication as an int.UE overlaps with other communication (e.g., independent SL transmission), a specific processing time can be secured for the int.UE to perform signal processing, etc., from the time it receives scheduling until it performs transmission corresponding to the scheduling.

[0469] (b-2 overlap variation) Methods b-2-1 to b-2-3 described in b-2 above may be applied to overlap between transmission and reception, as well as overlap between transmissions, or overlap between receptions. For example, "transmission" in each of the above methods may be replaced with "reception."

[0470] There are two cases of overlap between transmission and reception: When an int.UE receives as an int.UE, other transmissions (e.g., independent SL transmissions) occur at the int.UE, and the reception as the int.UE and the other transmissions overlap in time. When an int.UE transmits as an int.UE, another reception occurs at the int.UE, and the transmission as int.UE and the other reception overlap in time.

[0471] Here, the other reception is reception independent of the operation as an int.UE. Hereinafter, reception independent of the operation as an int.UE may be referred to as independent reception (independent RX). For example, in the case of b-2, independent reception includes reception of a sidelink as a UE. Hereinafter, reception of a sidelink as a UE independent of the operation as an int.UE may be referred to as independent SL reception.

[0472] Reception as an int.UE includes receiving signals transmitted from the A-IoT UE to the int.UE and receiving signals transmitted from the base station to the int.UE.

[0473] Furthermore, there are the following cases of overlap between receptions: When an int.UE receives as an int.UE, other reception (for example, an independent SL reception) occurs at the int.UE, and the reception as the int.UE and the other reception overlap in time.

[0474] In the case of overlapping transmission and reception, any of methods b-2-1 to b-2-3 may be applied as follows. (i) When method b-2-1 is applied, transmission and reception are performed simultaneously. (ii) When method b-2-2 is applied, one of transmission and reception is performed and the other is dropped. Which is performed and / or which is dropped may be determined based on the priority between the overlapping transmission and reception. (iii) When method b-2-3 is applied, it is determined whether to apply method b-2-1 or method b-2-2 (e.g., either (i) or (ii) above). For example, similar to method b-2-3, the determination may be made based on the circumstances. Here, the circumstances that are the factors for the determination include at least one of whether there is full overlap or partial overlap, the type of overlapping channel / signal, the capability of the UE, etc.

[0475] In the case of overlapping reception, any of methods b-2-1 to b-2-3 may be applied as follows. (iv) When method b-2-1 is applied, overlapping reception is performed simultaneously. (v) When method b-2-2 is applied, one of the overlapping receptions is executed and the other is dropped. Which is executed and / or which is dropped may be determined based on the priority between the overlapping receptions. (vi) When method b-2-3 is applied, it is determined whether to apply method b-2-1 or method b-2-2 (e.g., either (iv) or (v) above). For example, similar to method b-2-3, the determination may be made based on circumstances. Here, the circumstances that are factors in the determination include at least one of whether there is full overlap or partial overlap, the type of overlapping channel / signal, the capability of the UE, etc.

[0476] Although the above description has been given using an example of overlap between two operations (transmit and transmit, transmit and receive, receive and receive), the present disclosure is not limited to this example and may be applied to cases where overlap occurs between three or more operations.

[0477] For example, methods b-2-1 to b-2-3 may be applied to overlap between transmission and reception, or may be applied to overlap between transmission and reception.

[0478] For example, in a case where the transmission in step 2 (hereinafter, TX1) and the reception in step 3 (hereinafter, RX) of the communication flow described using Figure 12 etc. overlap each other, and the transmission of an independent SL (hereinafter, TX2) further overlaps, any of the above methods b-2-1 to b-2-3 may be applied in the following manner. (vii) When method b-2-1 is applied, overlapping TX1, TX2 and RX are executed simultaneously. (viii) When method b-2-2 is applied, some of the overlapping operations are executed and the rest are dropped. For example, TX1 and RX are executed and TX2 is dropped. Alternatively, TX2 is executed and TX1 and RX are dropped. Which of the three overlapping operations is executed and / or dropped may be determined based on the priority among the overlapping operations (e.g., TX1, TX2, and RX). (ix) When method b-2-3 is applied, it is determined whether to apply method b-2-1 or method b-2-2 (e.g., either (vii) or (viii) above). For example, as with method b-2-3, the determination may be made based on circumstances. Here, the circumstances that contribute to the determination include at least one of whether there is full overlap or partial overlap, the type of overlapping channels / signals, the capability of the UE, etc.

[0479] Note that communication between the int.UE and the A-IoT UE may be classified as a sidelink from the perspective of the int.UE. In this case, the process (or operation) for the case of overlap between SL and SL may be applied to overlap #A'. Also, in this case, the process (or operation) for the case of overlap between SL and UL associated with SL may be applied to overlap #B'.

[0480] Alternatively, communication between the int.UE and the A-IoT UE may be classified as downlink / uplink from the perspective of the int.UE. For example, communication from the int.UE to the A-IoT UE is classified as downlink (DL), and communication from the A-IoT UE to the int.UE is classified as uplink (UL). In this case, the process (or operation) for the overlap case between Uu (e.g., UL) and SL may be applied to overlap #A'. Also, in this case, the process (or operation) for the overlap case between SL and UL may be applied to overlap #B'.

[0481] In the above-described b-2, when an overlap occurs between a first communication between the int.UE and another UE and a second communication between the base station and the A-IoT UE via the int.UE, the int.UE determines to execute at least one of the first and second communications, and executes the determined at least one of the communications. This allows appropriate communication to be performed when a communication different from the communication in the A-IoT communication system overlaps.

[0482] In the above, a case where the other communication overlapping with the communication as an int.UE is communication between the UE and a base station (e.g., UL communication, DL communication) is described as b-1, and a case where the other communication overlapping with the communication as an int.UE is communication between UEs (e.g., SL communication) is described as b-2. Below, a case where the other communication overlapping with the communication as an int.UE includes communication between the UE and a base station (e.g., UL communication, DL communication) and communication between UEs (e.g., SL communication) is described as b-3.

[0483] (b-3) When a resource in the resource pool is selected by the int.UE for R2D transmission (Tx) / D2R reception (Rx), and the selected resource overlaps with a resource for DL ​​reception (Rx) / UL transmission (Tx) / SL reception (Rx) / SL transmission (Tx), the int.UE may handle these resource processes together.

[0484] In the case of overlapping handling of transmissions related to communication between the int.UE and the A-IoT UE, independent UL transmissions, and independent SL transmissions, these three types of overlaps may be handled together. For example, when a method in which one of the overlapping operations is performed and the rest is dropped, such as the above method b-1-2 or method b-2-2, is applied, one transmission of the highest priority among the three types is performed and the rest is dropped. Alternatively, two transmissions of the highest priority among the three types may be performed and the lowest priority transmission may be dropped.

[0485] In the case of overlapping handling of transmissions related to communication between int.UE and A-IoT UE, independent UL transmissions, and independent SL transmissions, any two of these three types may be handled first, followed by the rest.

[0486] For example, when methods such as methods b-1-2 and b-2-2 are applied, in which one of the overlapping operations is performed and the rest is dropped, the independent UL transmission and the independent SL transmission are handled first, and one of the two transmissions is dropped. After that, the transmissions that were not dropped and the transmissions related to communication between the int.UE and the A-IoT UE are handled, and one of the two transmissions is dropped.

[0487] When a method is applied in which one of the overlapping operations is performed and the rest are dropped, such as methods b-1-2 and b-2-2 above, the independent UL transmission and the transmission related to communication between the int.UE and the A-IoT UE are handled first, and one of the two transmissions is dropped. After that, the transmission that was not dropped and the independent SL transmission are handled, and one of the two transmissions is dropped.

[0488] When any two of the three types are handled first and then the remaining types are handled, the order of handling is not particularly limited.

[0489] Although the above description of b-3 uses an example in which one of the overlapping operations is performed and the remaining operations are dropped, such as methods b-1-2 and b-2-2, the present disclosure is not limited to this. Methods in which multiple operations are performed simultaneously, such as methods b-1-1 and b-2-1, and methods in which multiplexing multiple transmissions, such as method b-1-3, may also be applied.

[0490] (b-4) When a resource in the resource pool is selected by the int.UE for R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx), and the selected resource overlaps with resources such as DL reception (Rx) / UL transmission (Tx) / SL reception (Rx) / SL transmission (Tx) (other than b-1 to b-3 above), the int.UE performs resource processing as follows (b-4-1) to (b-4-3).

[0491] The multiple transmissions that may be simultaneous transmissions in the int.UE are at least one of the following patterns a to e. Note that the A-IoT device may simply be referred to as a device. Furthermore, the multiple transmissions shown in the following patterns a to e do not have to be simultaneous transmissions. Pattern a: Multiple R2Ds to multiple A-IoT devices (e.g., PRDCH, R2D synchronization acquisition signal, time acquisition signal) Pattern b: R2D to one or more A-IoT devices and UL to gNB or parent node Pattern c: CW to one or more A-IoT devices and R2D to one or more A-IoT devices Pattern d: CW to one or more A-IoT devices and UL to a gNB or parent node Pattern e: A combination of two or more of the above a to d

[0492] In addition, the UL to the gNB or parent node may be NR-Uu.

[0493] 33 to 36 are diagrams showing examples of simultaneous transmission. Four cases, Case 1 to Case 4, included in the simultaneous transmission are shown in Figures 33 to 36. The horizontal axis in each of the four cases indicates the time axis. The four cases in Figures 33 to 36 exemplarily show simultaneous R2D transmission and UL transmission, which corresponds to the above-mentioned pattern b.

[0494] Case 1 in Figure 33 corresponds to the case where simultaneous transmission means two or more transmissions that partially overlap in the time domain. Case 2 in Figure 34 corresponds to the case where simultaneous transmission means two or more transmissions that fully overlap in the time domain. Case 3 in Figure 35 corresponds to the case where simultaneous transmission means two or more transmissions that do not overlap in the time domain but are transmitted within the same time unit. Case 4 in Figure 36 corresponds to the case where simultaneous transmission means two or more transmissions without sufficient gaps.

[0495] In other words, simultaneous transmission may correspond to multiple transmissions within a particular time period, or multiple transmissions within a particular period of time.

[0496] In the frequency domain, simultaneous transmissions may refer to two or more transmissions within the same band. Alternatively, simultaneous transmissions may refer to two or more transmissions in different bands. Intra-band transmissions are referred to as "intra-band," and inter-band transmissions are referred to as "inter-band."

[0497] Next, we will explain whether the int.UE and / or CW node supports simultaneous transmission. The int.UE and / or CW node will be referred to as the int.UE / CW node. The int.UE and CW node may be interchangeable.

[0498] (b-4-1) int. UE / CW node reports whether it supports or can support simultaneous transmission.

[0499] The following describes the case where an int.UE / CW node supports simultaneous transmission. For example, either option 1 or option 2 below applies to support of simultaneous transmission.

[0500] (Option 1) In option 1, the int.UE / CW node supports simultaneous transmission. For example, simultaneous transmission of at least one of the above patterns a to e is supported by the int.UE / CW node.

[0501] For option 1, the int.UE / CW nodes may each support simultaneous transmission.

[0502] (Option 2) In option 2, the int.UE / CW node may report whether it supports simultaneous transmission.

[0503] In Option 2, an int.UE / CW node may or may not support simultaneous transmission. In other words, among int.UE / CW nodes, there may be int.UE / CW nodes that support simultaneous transmission and int.UE / CW nodes that do not support simultaneous transmission.

[0504] In option 2, the int.UE / CW node reports whether it supports TDM and / or FDM for at least one of patterns a through e, or whether it supports TDM and / or FDM for each of two or more of patterns a through e.

[0505] In option 2, multiplexing of at least one of patterns a to e is supported in a TDM manner as a basic capability of the int.UE / CW node.

[0506] In option 2, the int.UE / CW node may report which of the simultaneous transmissions from pattern a to pattern e it supports.

[0507] Whether Option 1 or Option 2 is applied may vary depending on the band combination (BC). Note that the int.UE / CW node may report its capability for each BC. Note that the BC here may be a combination of the A-IoT R2D transmission band and the NR-Uu UL band. For example, Option 2 is applied when the BC for R2D transmission and UL transmission is a specific BC. In this case, Option 1 may be applied when the BC for R2D transmission and UL transmission is a BC other than the specific BC.

[0508] Whether Option 1 or Option 2 above applies may differ depending on whether the transmissions are intraband or interband. For example, in the intraband case, Option 1 applies, and in the interband case, Option 2 applies.

[0509] (b-4-2) If the int.UE / CW node does not support simultaneous transmission, it performs priority processing. It may perform the prioritized transmission and skip the other transmission.

[0510] If the int.UE / CW node does not support simultaneous transmission, either option 1 or option 2 below applies.

[0511] (Option 1) In option 1, the int.UE / CW node does not expect multiple simultaneous transmissions to be scheduled. In option 1, the scheduling device, such as the leader or NW, does not schedule multiple simultaneous transmissions.

[0512] (Option 2) In option 2, multiple simultaneous transmissions are scheduled. That is, in option 2, the int.UE / CW node expects multiple simultaneous transmissions to be scheduled. In option 2, the scheduling device, such as the leader or NW, schedules multiple simultaneous transmissions. In option 2, when multiple simultaneous transmissions are scheduled, either option 2-1 or option 2-2 below is applied to how the multiple transmissions are handled.

[0513] (Option 2-1) A priority rule is specified. For example, if two transmissions, transmission A and transmission B, are scheduled for simultaneous transmission, at least one of the two transmissions may be executed according to the priority rule. For example, if transmission A has priority over transmission B, transmission A is executed. In this case, transmission B is not executed (is dropped).

[0514] For example, the priority is determined based on the following rules: In the following description, "a" > "b" indicates that a has a higher priority than b. · Transmissions to be performed and / or dropped may be determined based on the channel type and signal type priority of overlapping transmissions. · Decisions may be made as to which transmissions are performed and / or dropped based on the priority of the traffic flows of the overlapping transmissions. Based on the priority of the instruction / setting, the transmission to be performed and / or the transmission to be dropped may be determined. For example, the priority may be set as follows: "transmission of a signal having an instruction of a relatively high priority" > "transmission of a signal having an instruction of a relatively low priority." A transmission to be performed and / or a transmission to be dropped may be determined based on the priority of the transmission timing. For example, the priority may be set as "a transmission that starts transmission relatively early" > "a transmission that starts transmission relatively late." Based on the priority of the scheduling timing, the transmission to be performed and / or the transmission to be dropped may be determined. For example, the priority may be set as "transmission corresponding to relatively late scheduling" > "transmission corresponding to relatively early scheduling."

[0515] "Drop" may be replaced with "postpone." In this case, the above "transmission to be executed" and "transmission to be dropped" may be replaced with "transmission to be executed without being postponed" and "transmission to be executed with being postponed," respectively.

[0516] For example, at least one of the following rules may be applied: · NR-Uu UL is prioritized over other transmissions. · NR-Uu UL is not prioritized over other transmissions. A-IoT R2D takes priority over other transmissions. A-IoT R2D does not prioritize transmissions over other transmissions. A-IoT CW has priority over other transmissions. A-IoT CW does not take priority over other transmissions. A-IoT paging takes priority over other transmissions.

[0517] (Option 2-2) In option 2-2, one or more transmissions in the simultaneous transmissions are skipped by the int.UE / CW node, e.g., the int.UE / CW node decides which transmissions in the simultaneous transmissions to drop.

[0518] In b-4 above, we have explained how to handle simultaneous transmissions when the int.UE / CW node supports simultaneous transmission and when the int.UE / CW node does not support simultaneous transmission. This b-4 clarifies whether to execute multiple simultaneous transmissions individually or execute only a part of the multiple transmissions (for example, one), so multiple transmissions can be handled appropriately.

[0519] (b-4-3) If the int.UE / CW node supports simultaneous transmission, perform dynamic power sharing among multiple transmissions.

[0520] If an int.UE / CW node supports simultaneous transmission of at least one of patterns a to e, dynamic power sharing among multiple transmissions is supported. Section b-4-3 describes dynamic power sharing when simultaneous transmission is supported.

[0521] In the following, we will exemplify pattern d, i.e., simultaneous transmission of R2D to an A-IoT device and UL to a gNB or parent node. In other words, we will exemplify whether or not dynamic power sharing between A-IoT power and NR power is supported.

[0522] (Prerequisite for b-4-3) The maximum power consumption of A-IoT is P AIoT The maximum power of NR is P NR The total maximum power is expressed as P total It is written as P AIoT , P NR , and P total may be set or defined individually.

[0523] Here, "P AIoT +P NR >P total ", power adjustment is required. In this case, there are two cases depending on whether dynamic power sharing is supported or not.

[0524] (Case 1 of b-4-3) In b-4-3, "P AIoT +P NR >P total " and the int.UE / CW node supports dynamic power sharing is called Case 1. In this Case 1, one of the following Option 1 or Option 2 is applied.

[0525] 37 to 39 are diagrams showing an example of case 1 of b-4-3. In FIGS. 37 to 39, examples of option 1 to option 3 of case 1 of b-4-3 described above are shown. In option 1 to option 3 of FIGS. 37 to 39, the maximum power P of NR before power sharing is performed is shown. NR and the maximum power P of A-IoT AIoT 10 shows a power state #1 obtained by adding the above and a power state #2 obtained after power sharing has been performed on the state #1.

[0526] (Option 1) In option 1, the int.UE / CW node transmits the total transmit power P totalThe R2D transmission power of A-IoT is dropped so that it does not exceed P. Then, by dynamic power sharing, the total transmission power is total With their respective powers adjusted not to exceed , the int.UE / CW node may simultaneously perform R2D transmissions to A-IoT devices and UL transmissions to gNBs or parent nodes.

[0527] (Option 2) The int.UE / CW node transmits the total power P total The NR transmission power is dropped so that it does not exceed P. Then, by dynamic power sharing, the total transmission power is total With their respective powers adjusted not to exceed , the int.UE / CW node may simultaneously perform R2D transmissions to A-IoT devices and UL transmissions to gNBs or parent nodes.

[0528] (Option 3) The int.UE / CW node transmits the total power P total Both the R2D transmission power of A-IoT and the transmission power of NR are dropped so that they do not exceed P. Then, by dynamic power sharing, the total transmission power is total The int.UE / CW node may simultaneously perform R2D transmission to the A-IoT device and UL transmission to the gNB or parent node, with their respective powers adjusted so as not to exceed . Note that in Option 3, how to adjust the A-IoT R2D transmission power and NR transmission power may be specified by the specification or instructed by the network.

[0529] In addition, in the above options 1 to 3, NR transmission or A-IoT R2D transmission may be replaced with CW transmission.

[0530] In addition, case b-4 is an example of pattern d, i.e., dynamic power sharing in simultaneous transmission of R2D to an A-IoT device and UL to a gNB or parent node, but the present disclosure is not limited to this.

[0531] For example, consider pattern c, i.e., dynamic power sharing in simultaneous transmission of CW to one or more A-IoT devices and R2D to one or more A-IoT devices. In this example, in the above options 1 to 3, the power of NR transmission, "P NR ” is the power of CW transmission “P CW ". In Option 1, the int.UE / CW node will transmit at a total power of P total In option 2, the int.UE / CW node drops the A-IoT R2D transmit power so that the total transmit power does not exceed P total The transmit power P of CW transmission should not exceed CW In option 3, the int.UE / CW node drops the total transmit power P total Both the A-IoT R2D transmit power and the transmit power of the CW transmission are dropped so that they do not exceed

[0532] Note that which of the above options 1 to 3 is applied may be specified by the specifications, may be set by the NW, or may be determined according to the capability of the int.UE / CW node.

[0533] Which of the above options 1 to 3 to apply may be determined according to a priority rule, which may be the same as the priority rule shown in option 1 of case 2 in b-4-3, which will be described later, for example.

[0534] (Case 2 of b-4-3) In b-4-3, "P AIoT +P NR >P total " and the int.UE / CW node does not support dynamic power sharing, this is called case 2 of b-4-3. In this case 2, one of the two transmissions is performed and the other is not performed, so the total transmission power is P total For example, one of the following two options may be applied:

[0535] (Option 1) Prioritization rules are specified. For example, "P AIoT +P NR >P total " and the int.UE / CW node does not support dynamic power sharing, one of the A-IoT R2D transmission and the UL transmission may be performed according to the priority rules. In this case, the other of the two transmissions will not be performed (will be dropped).

[0536] For example, the priority is determined based on the following rules: In the following description, "a" > "b" indicates that a has a higher priority than b. · Transmissions to be performed and / or dropped may be determined based on the channel type and signal type priority of overlapping transmissions. · Decisions may be made as to which transmissions are performed and / or dropped based on the priority of the traffic flows of the overlapping transmissions. Based on the priority of the instruction / setting, the transmission to be performed and / or the transmission to be dropped may be determined. For example, the priority may be set as follows: "transmission of a signal having an instruction of a relatively high priority" > "transmission of a signal having an instruction of a relatively low priority." A transmission to be performed and / or a transmission to be dropped may be determined based on the priority of the transmission timing. For example, the priority may be set as "a transmission that starts transmission relatively early" > "a transmission that starts transmission relatively late." Based on the priority of the scheduling timing, the transmission to be performed and / or the transmission to be dropped may be determined. For example, the priority may be set as "transmission corresponding to relatively late scheduling" > "transmission corresponding to relatively early scheduling."

[0537] For example, one of the following rules applies: · NR-Uu UL is prioritized over other transmissions. · NR-Uu UL is not prioritized over other transmissions. A-IoT R2D takes priority over other transmissions. A-IoT R2D does not prioritize transmissions over other transmissions. A-IoT CW has priority over other transmissions. A-IoT CW does not take priority over other transmissions. A-IoT paging takes priority over other transmissions.

[0538] (Option 2) In option 2, one of the two transmissions is skipped by the int.UE / CW node, e.g., the int.UE / CW node decides which of the two transmissions to drop.

[0539] Note that in case 2 of b-4-3 above, pattern d, i.e., simultaneous transmission of R2D to an A-IoT device and UL to a gNB or parent node, was given as an example, but case 2 of b-4-3 may also be applied to other patterns. For example, in case of pattern c, i.e., a case where dynamic power sharing is not supported for simultaneous transmission of CW to one or more A-IoT devices and R2D to one or more A-IoT devices, in option 1, one of the A-IoT R2D transmission and CW transmission may be performed according to the priority rule. In this case, the other of the two transmissions is not performed (dropped).

[0540] In b-4-3 above, we have explained how to handle simultaneous transmissions depending on whether dynamic power sharing is supported when an int.UE / CW node supports simultaneous transmissions. This b-4-3 clarifies the operation of whether to execute each of the multiple simultaneous transmissions after adjusting the power, or to execute only a part of the multiple transmissions (for example, one), depending on whether dynamic power sharing is supported, so that multiple transmissions can be handled appropriately.

[0541] (b-4 variation) Methods b-4-1 to b-4-3 described in b-4 above may be applied to resource overlap between transmission and reception (D2R reception (Rx) / DL reception (Rx) / SL reception (Rx)), as well as resource overlap between transmission (R2D transmission (Tx) / CW transmission (Tx) / other R2D transmission (Tx) / UL transmission (Tx) / SL transmission (Tx)) and reception, or may be applied to resource overlap between reception and reception. For example, "transmission" or "Tx" in each of the above-mentioned methods may be replaced with "reception" or "Rx."

[0542] (b-5) When a resource in the resource pool is selected by the int.UE for R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx), and the selected resource partially overlaps with resources such as DL reception (Rx) / UL transmission (Tx) / SL reception (Rx) / SL transmission (Tx), the int.UE performs resource processing as follows (b-5-1) to (b-5-2).

[0543] In b-5, a case will be described in which a resource in the resource pool is selected by an int.UE for R2D transmission / D2R reception / CW transmission / UL transmission / DL reception / SL transmission / SL reception, and the selected resource partially overlaps with resources for other transmissions / receptions (see FIG. 40). Here, the other transmissions / receptions are transmissions / receptions different from the overlapping transmissions / receptions, and may be, for example, at least one of R2D transmission / D2R reception / CW transmission / UL transmission / DL reception / SL transmission / SL reception. This partial overlap may include any of the following: · The transmit / receive resources may partially overlap in time, completely overlap in frequency, partially overlap in frequency, or not overlap in frequency. · The transmit / receive resources are fully overlapped in time and partially overlapped in frequency.

[0544] (b-5-1) int. UE performs overlap processing operations only on resources in the overlapping portion.

[0545] In b-5-1, the int.UE performs overlap processing operations only on the overlapping portions. In b-5-1, the non-overlapping portions are not affected. That is, transmission / reception of the non-overlapping portions may be performed. The overlapping portions may be referred to as overlapping portions (see FIG. 41).

[0546] For example, for the overlapping portion, the int. UE transmits both signals simultaneously, where both signals may be two overlapping signals, and the transmit power of each transmission may be allocated based on priority.

[0547] For example, for the overlapping portion, the int.UE performs one of the two overlapping transmissions / receptions based on priority and drops the other.

[0548] The granularity of overlap processing may be defined. For example, the granularity of overlap processing may be defined in terms of time as chips / bits / groups of chips / groups of bits, etc. Also, the granularity of overlap processing may be defined in terms of frequency as subcarriers / RBs, for example.

[0549] (variation of b-5-1) In the case of the drop operation, the int.UE may drop the actual overlap portion and a specific period (e.g., a period of time T) before and / or after the actual overlap portion. The specific period may be set based on, for example, the time required for switching between transmit and receive processes. By dropping the specific period, a potential time for switching between transmit and receive can be secured.

[0550] (b-5-2)int.UE performs the same overlap processing operation for the entire transmission / reception resource.

[0551] In b-5-2, the UE (eg, int.UE) performs the same overlap processing operation for the entire transmission / reception (see FIG. 43).

[0552] In b-5-2, for example, the transmit power may be determined based on the overlapping portion, and the same transmit power may be applied to the entire transmission. That is, the transmit power of both the overlapping and non-overlapping portions may be determined based on the overlapping portion. The transmit power determination may be performed by the UE.

[0553] Alternatively, in b-5-2, for example, the int.UE performs some transmission or reception based on priority and drops other transmissions / receptions. For example, among multiple overlapping transmissions, the highest priority transmission is performed and all transmissions other than the highest priority transmission are dropped. In this case, the non-overlapping portions of the transmissions other than the highest priority transmission are also dropped.

[0554] Figures 40 to 43 are diagrams showing examples comparing each option of b-5. Figure 40 shows an example of a situation in which UL transmission and R2D transmission overlap in the time direction, and Figure 41 shows an example in which the above b-5-1 is applied to that situation, Figure 42 shows a variation of b-5-1, and Figure 43 shows an example in which b-5-2 is applied. Note that the horizontal axis in each example represents the time axis.

[0555] As shown in Figure 41, in b-5-1, the R2D transmission is partially dropped, and the non-dropped portion of the R2D transmission is carried out. Also, as shown in Figure 42, in a variation of b-5-1, the R2D transmission is partially dropped, and also dropped for a period of time T before and after that. Also, as shown in Figure 43, in b-5-2, the R2D transmission is dropped entirely.

[0556] In b-5 above, when an overlap occurs between a part of a first communication operation and a second communication operation different from the first communication operation, the int.UE determines a communication operation to be performed between the part of the first communication operation and the second communication operation. Then, the int.UE performs the determined communication operation. Note that the first communication operation is, for example, one of R2D transmission / D2R reception / CW transmission / UL transmission / DL reception / SL transmission / SL reception. Also, the second communication operation is, for example, one of R2D transmission / D2R reception / CW transmission / UL transmission / DL reception / SL transmission / SL reception, and is an operation different from the first communication operation.

[0557] For example, in b-5-1, overlap processing operations are applied to the overlapping portions, and non-overlapping portions are not affected. In b-5-2, the same overlap processing operations are applied to the entirety of the overlapping and non-overlapping portions. This allows for appropriate communication when multiple communications, including those in an A-IoT communication system, overlap with each other.

[0558] (b-6) When a resource in the resource pool is selected by the int.UE for repetition of R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx), and at least one of the selected repetitions overlaps with other resources for DL ​​reception (Rx) / UL transmission (Tx) / SL reception (Rx) / SL transmission (Tx), the int.UE performs resource processing as follows (b-6-1) to (b-6-2).

[0559] b-6 is an example in which repetition transmission is performed as another variation of the above b-5. b-6 describes a case in which the int.UE performs R2D transmission / D2R reception / CW transmission / UL transmission / DL reception / SL transmission / SL reception with repetition, and one or more of the repetitions overlap with other transmissions / receptions.

[0560] (b-6-1) int. UE performs overlap processing operations only on the repeated resources of the overlap portion.

[0561] In b-6-1, the int.UE performs overlap processing operations only for overlapping repetitions. In b-6-1, non-overlapping repetitions are not affected. That is, transmission / reception of non-overlapping repetitions may be performed. Overlapping repetitions may also be referred to as overlapping repetitions.

[0562] Note that, for overlapping repetitions, the same operation as in b-5 may be applied. For example, similar to b-5, the int.UE simultaneously transmits both overlapping signals. In this case, the transmit power of each transmission may be allocated based on priority. Alternatively, similar to b-5, the int.UE performs one of the overlapping transmissions / receptions based on priority and drops the other.

[0563] (b-6-1 variation 1) The different options in b-5 above apply between repeat and no repeat.

[0564] That is, the int.UE may drop the actual overlap portion repetition and a specific period (e.g., the period of time T) before and / or after the actual overlap portion repetition. The specific period may be set based on, for example, the time required for switching between transmission and reception processes. Dropping the specific period allows for potential transmission / reception switching time.

[0565] (Variation 2 of b-6-1) If an overlap with a signal X occurs in the iteration i (i is an integer between 1 and N, inclusive, and N is the number of iterations), and another overlap with a signal Y occurs in the iteration j (j is an integer between 1 and N, inclusive), then an overlap processing operation is applied to each overlap.

[0566] (b-6-2) int.UE performs the same overlap processing operation for all repetition resources.

[0567] In b-6-2, the UE (e.g., int.UE) performs the same overlap processing operation for the entire transmission / reception, i.e., in b-6-2, the UE (e.g., int.UE) performs the same overlap processing operation for all repetitions.

[0568] In b-6-2, for example, the transmit power may be determined based on the overlapping portion, and the same transmit power may be applied to all repetitions. The transmit power determination may be performed by the UE. For example, if overlap occurs in the i-th repetition (i is an integer between 1 and N, and N is the number of repetitions), the transmit power may be determined based on the i-th repetition, and the same transmit power as the i-th repetition may be applied to the 1st to Nth repetitions other than the i-th repetition.

[0569] Alternatively, in b-6-2, for example, the int.UE performs some repetitions of transmission or reception based on priority and drops other repetitions. For example, among multiple overlapping repetitions, the highest priority repetition is performed and all repetitions other than the highest priority repetition are dropped. In this case, non-overlapping transmissions among the repetitions other than the highest priority repetition are also dropped.

[0570] (b-6-2 variation 1) In the i-th iteration (where i is an integer from 1 to N, and N is the number of repetitions), an overlap with a certain signal X occurs, and in the j-th iteration (where j is an integer from 1 to N), another overlap with signal Y occurs. In such a case, one of the following is applied. · An overlap processing operation for any of the overlaps is applied. · If i < j, the overlap processing operation based on the i-th iteration is applied until before the j-th iteration, and then the overlap processing operation based on the j-th iteration is applied to the remaining part.

[0571] (Variation 2 of b-6-2) When the int.UE drops an overlapped repetition, the int.UE drops all repetitions after the overlapped repetition. In this case, the int.UE does not have to drop the repetition before the overlapped repetition.

[0572] Figures 44 to 47 are diagrams showing examples for comparing each option of b-6. Figure 44 shows an example of a situation where UL transmission overlaps with a part of the repeated transmission of R2D. For that situation, Figure 45 shows an example where b-6-1 described above is applied, Figure 46 shows an example where b-6-2 is applied, and Figure 47 shows an example where Variation 2 of b-6-2 is applied. Note that the horizontal axis in each example indicates the time axis.

[0573] As shown in Figure 45, in the example of b-6-1, the overlapping repeated transmission h of R2D is partially dropped. Also, as shown in Figure 46, in the example of b-6-2, the repeated transmission of R2D is entirely dropped. Further, as shown in Figure 47, in the example of Variation 2 of b-6-2, among the repeated transmissions of R2D, the overlapping repeated transmission of R2D and all subsequent repetitions are dropped.

[0574] The repetition of CW may be "CW corresponding to D2R repetition." Also, the repetition of CW may be "frequency hopping" of CW.

[0575] In b-6 above, when an overlap occurs between a portion of a first communication operation and a second communication operation different from the first communication operation, the int.UE determines a communication operation to be performed between the portion of the first communication operation and the second communication operation. Then, the int.UE performs the determined communication operation. Note that the first communication operation is, for example, a repeated operation of any one of R2D transmission / D2R reception / CW transmission / UL transmission / DL reception / SL transmission / SL reception, and the portion of the first communication operation is at least one of the repeated operations. Furthermore, the second communication operation is, for example, any one of R2D transmission / D2R reception / CW transmission / UL transmission / DL reception / SL transmission / SL reception, and is an operation different from the first communication operation.

[0576] For example, in b-6-1, overlap processing operations are applied to the overlapping portions, and non-overlapping portions are not affected. In b-6-2, the same overlap processing operations are applied to the entire repetition, including the overlapping and non-overlapping portions. This allows for appropriate communication when multiple communications overlap each other, even if at least one of the multiple communications, including communications in an A-IoT communication system, is repeated.

[0577] (b-7) When a resource in the resource pool is selected by the int.UE for CW transmission (Tx) having a multi-tone waveform, and at least one resource of the selected multiple tones overlaps with other resources such as DL reception (Rx), UL transmission (Tx), SL reception (Rx), and SL transmission (Tx), the int.UE performs resource processing as follows (b-7-1) to (b-7-2).

[0578] In b-7, a case where the int.UE performs CW transmission with a multi-tone waveform and at least one of the multiple tones overlaps with other transmissions / receptions is described. Note that the term "tone" may be replaced with a carrier, frequency, band, etc.

[0579] (b-7-1) int. The UE performs overlap processing operations only on resources of overlapping tones.

[0580] In b-7-1, the int.UE performs overlap processing operations only on overlapped tones. In b-7-1, non-overlapping tones are not affected. That is, CW transmission of non-overlapping tones may be performed.

[0581] For CWs of overlapping tones, the int.UE may transmit the overlapping tones. Alternatively, for CWs of overlapping tones, the int.UE may drop the overlapping tones based on priority. Alternatively, for CWs of overlapping tones, the int.UE may either transmit or drop the overlapping tones based on priority.

[0582] Note that for overlapping CW tones, the same operation as in b-5 may be applied. For example, as in b-5, the int.UE transmits both overlapping signals simultaneously. In this case, the transmit power of each transmission may be allocated based on priority. Alternatively, as in b-5, the int.UE performs one of the overlapping transmissions / receptions based on priority and drops the other.

[0583] (b-7-2) int. UE performs the same overlap processing operation on all tone resources.

[0584] In b-7-2, the UE (e.g., int.UE) performs the same overlap processing operation for the entire transmission / reception, i.e., in b-7-2, the UE (e.g., int.UE) performs the same overlap processing operation for all tones.

[0585] For example, in b-7-2, the int.UE transmits CWs of all tones. Alternatively, in b-7-2, the int.UE drops CWs of all tones. For example, the int.UE may transmit CWs of all tones or drop CWs of all tones based on priority.

[0586] Figures 48 to 50 are diagrams showing examples comparing the various options of b-7. Figure 48 shows an example of a situation in which the tone of frequency f1, one of the two tones for UL transmission and CW transmission, overlaps in the time direction. Figure 49 shows an example in which the above-mentioned b-7-1 is applied to this situation, and Figure 50 shows an example in which b-7-2 is applied. In each example, the horizontal axis represents the time axis, and the vertical axis represents the frequency axis.

[0587] As shown in Figures 48-50, in the example of option 1, the CW transmission of the overlapping tones at frequency f1 is dropped, and in the example of b-7-2, the CW transmission of both the tones at frequency f1 and frequency f2 is dropped.

[0588] Note that a multi-tone waveform is multiple unmodulated single tones, one at each frequency point.

[0589] In b-7 above, if there is an overlap in resources between a part of a first communication operation and a second communication operation different from the first communication operation, the int.UE determines the communication operation and its resources to be executed between the part of the first communication operation and the second communication operation. Then, the int.UE performs the determined communication operation. Note that the first communication operation is, for example, a multi-tone CW transmission, and the part of the first communication operation is a CW transmission of at least one tone of the multi-tone. Furthermore, the second communication operation is, for example, any one of R2D transmission, D2R reception, CW transmission, UL transmission, DL reception, SL transmission, and SL reception, and is an operation different from the first communication operation.

[0590] For example, in b-7-1, overlap processing is applied to CW transmissions of overlapping tones, but not to CW transmissions of non-overlapping tones. In addition, in b-7-2, the same overlap processing is applied to the entire system, including overlapping and non-overlapping tones. This allows for appropriate communication in A-IoT communication systems when CW transmissions of some tones in a multi-tone CW transmission overlap with other communications.

[0591] (c)int. The UE applies the above operation (a) or (b) based on each of the following conditions (c-1) to (c-3).

[0592] (c-1) Time conditions The int.UE applies the above operation (a) or (b) based on the following time conditions x to y'. x. If a DL / UL / SL scheduling grant (e.g., DL / UL / SL scheduling DCI, SL scheduling SCI) is received earlier than time X for resources in the R2D / D2R / CW resource pool. x'. If a DL / UL / SL scheduling grant (e.g., DL / UL / SL scheduling DCI, SL scheduling SCI) is received earlier than time X of the earliest resource in the R2D / D2R / CW resource pool. ·y.If a DL / UL / SL scheduling grant (e.g., DL / UL / SL scheduling DCI, SL scheduling SCI) is received later than time X for resources in the R2D / D2R / CW resource pool. ·y'. If a DL / UL / SL scheduling grant (e.g., DL / UL / SL scheduling DCI, SL scheduling SCI) is received later than time X of the earliest resource in the R2D / D2R / CW resource pool.

[0593] (c-2) Channel type / signal type The int.UE applies the above operation (a) or (b) based on the following channel type or signal type: Channel types: DL / UL / SL / R2D / D2R / CW DL / UL / SL / R2D / D2R / CW signal types

[0594] (c-3) Scheduling type The int.UE applies the above operation (a) or (b) based on the following scheduling type: DL / UL / SL are scheduled by dynamic grant DL / UL / SL are scheduled by configured grant

[0595] Here, the time condition of c-1 will be explained.

[0596] For example, the resource processing according to (a) may be applied to the above-mentioned time condition x. In this case, the int.UE receives a scheduling grant for DL ​​reception (Rx) / UL transmission (Tx) / SL reception (Rx) / SL transmission (Tx) earlier than time X before the start of transmission / reception of resources in the resource pool. This allows the int.UE to secure time to check whether the resources for DL ​​reception (Rx) / UL transmission (Tx) / SL reception (Rx) / SL transmission (Tx) overlap with resources in the resource pool for R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx).

[0597] Furthermore, for example, the resource processing according to (b) may be applied to the above-described time condition y. In this case, the int.UE receives a scheduling grant for DL ​​reception (Rx) / UL transmission (Tx) / SL reception (Rx) / SL transmission (Tx) later than the time X before the start of transmission / reception of resources in the resource pool. The int.UE does not have enough time to check whether the resources for DL ​​reception (Rx) / UL transmission (Tx) / SL reception (Rx) / SL transmission (Tx) overlap with resources in the resource pool for R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx). Therefore, the int.UE performs resource processing for overlapping resources according to the predetermined procedure (b).

[0598] In the case of time condition x', the int.UE receives a scheduling grant time X before the time when transmission / reception of the earliest resource in the resource pool starts.

[0599] Similarly, for time condition y', the int.UE receives a scheduling grant a time Y after the time when transmission / reception of the earliest resource in the resource pool begins.

[0600] Although the above proposal has been given as an example of a case where two transmission / reception resources overlap, the present disclosure is not limited to this. For example, the present disclosure may be applied to a case where three or more transmission / reception resources overlap.

[0601] Furthermore, in the above proposals, examples have been shown in which overlap processing operations are applied to two overlapping transmission / reception resources based on priority, but the present disclosure is not limited to this. For example, in the above proposals, overlap processing operations may be applied to two overlapping transmission / reception resources based on information other than priority, or overlap processing operations may be applied to two overlapping transmission / reception resources based on at least one of a specification definition, a system definition, an instruction from a network, etc.

[0602] In addition, although the above proposals have shown examples in which the int.UE performs the operations, the present disclosure is not limited thereto. Operations similar to the operations of the int.UE in the above proposals may be performed by the BS, or may be performed in other communication devices, CW nodes, or A-IoT devices.

[0603] The device may report the supportability of each of the above-mentioned proposals and each option of each proposal to a network (e.g., a base station) as capability information. The network may configure / instruct the device based on the report of the capability information from the device.

[0604] In this embodiment, "R2D," "R2D signal," "R2D message," and "R2D message type" may be interchangeable. Also, in this embodiment, "D2R," "D2R signal," "D2R message," and "D2R message type" may be interchangeable.

[0605] (effect) According to Proposal 1, when an int.UE autonomously selects resources from a resource pool to perform communication, even if there is a case where the resources overlap with other communications of the int.UE, the resource overlap can be handled appropriately.

[0606] <Prerequisites for Proposal 2> As a premise of Proposal 2, it is assumed that the R2D transmission (Tx), D2R reception (Rx), and CW transmission (Tx) of the int.UE are scheduled by the network (NW).

[0607] In Proposal 2, the description in (b), (b-1) to (b-7) above regarding "resources in the resource pool selected by int.UE for R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx), and the selected resources" shall be interpreted in the context of "resources scheduled by the network for R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx)."

[0608] <Proposal 2> In Proposal 2, the int.UE applies the above-described operations (b-1) to (b-7) based on the following conditions (1) to (3).

[0609] (1) Time conditions The int.UE applies the above-described operations (b-1) to (b-7) based on the following time conditions x to y'. If a DL / UL / SL scheduling grant (e.g., DL / UL / SL scheduling DCI, SL scheduling SCI) is received earlier than time X of the scheduled resource of R2D / D2R / CW If a DL / UL / SL scheduling grant (e.g., DL / UL / SL scheduling DCI, SL scheduling SCI) is received later than time X before the scheduled resource of R2D / D2R / CW If an R2D / D2R / CW scheduling grant (e.g., R2D / D2R / CW scheduling DCI) is received earlier than time X for the DL / UL / SL scheduled resource. If an R2D / D2R / CW scheduling grant (e.g., R2D / D2R / CW scheduling DCI) is received later than time X for the DL / UL / SL scheduled resource.

[0610] (2) Channel type / signal type The int.UE applies the above-described operations (b-1) to (b-7) based on the following channel and signal type: Channel types: DL / UL / SL / R2D / D2R / CW DL / UL / SL / R2D / D2R / CW signal types

[0611] (3) Scheduling Type The int.UE applies the above-described operations (b-1) to (b-7) based on the following scheduling type. DL / UL / SL / R2D / D2R / CW are scheduled by dynamic grant DL / UL / SL / R2D / D2R / CW is scheduled by configured grant

[0612] (effect) According to Proposal 2, when communication performed by an int.UE is scheduled by the network (NW), the int.UE determines resource selection based on time conditions, channel type / signal type, scheduling type, etc., so that even if resources overlap with other communications of the int.UE, the resource overlap can be handled appropriately.

[0613] <Prerequisites for Proposal 3> The premise of Proposal 3 is as follows: · The int.UE is provided with a resource pool for R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx). ·int.UE selects resources for R2D transmission (Tx) / D2R reception (Rx) / CW transmission (Tx) within the resource pool.

[0614] <Proposal 3> In Proposal 3, the int.UE determines the parameters for R2D / D2R / CW resource selection as shown in (a) to (f) below, and reports this to the network (NW) as shown in (g) below.

[0615] (a)int.UE decides whether to perform R2D / D2R / CW repetition based on the following (Option 1) to (Option 4).

[0616] (Option 1) Network configuration The int.UE decides whether to perform R2D / D2R / CW repetition based on the following network configurations (1) to (2). (1) The network configuration may be semi-static or dynamic. (2) Network configuration may be per cell / per resource pool / per resource.

[0617] (Option 2) Implementation of int.UE int.UE decides whether to perform R2D / D2R / CW iterations based on the implementation of int.UE.

[0618] (Option 3) The following conditions (1) to (3) apply: The int.UE determines whether to perform R2D / D2R / CW repetition based on the following conditions (1) to (3). (1) R2D / D2R reception performance based on the following items: Receiving power ·R2D / D2R was received correctly or not (2) Information on the target A-IoT device (ID, device type, etc.) (3) Message type / command type

[0619] (Option 4) A combination of the above options 1, 2, and 3 The int.UE decides whether to perform R2D / D2R / CW repetition based on the combination of Option 1 / Option 2 / Option 3 above.

[0620] For example, if repetition is enabled by the network, the int.UE can decide whether to perform repetition, and if repetition is not enabled by the network, the int.UE will not perform repetition.

[0621] (b)int.UE determines the number of repetitions of R2D / D2R / CW based on the following (Option 1) to (Option 4).

[0622] (Option 1) Network Configuration The int.UE determines the number of repetitions of R2D / D2R / CW based on the following network configurations (1) to (2). (1) The network configuration may be semi-static or dynamic. (2) Network configuration may be per cell / per resource pool / per resource.

[0623] (Option 2) Implementing int.UE int.UE determines the number of R2D / D2R / CW repetitions based on the implementation of int.UE.

[0624] (Option 3) The following conditions (1) to (3) apply: The int.UE determines the number of repetitions of R2D / D2R / CW based on the following conditions (1) to (3). (1) R2D / D2R reception performance based on the following items: Receiving power ·R2D / D2R was received correctly or not (2) Information on the target A-IoT device (ID, device type, etc.) (3) Message type / command type

[0625] (Option 4) A combination of the above options 1, 2, and 3 The int.UE determines the number of repetitions of R2D / D2R / CW based on the combination of Option 1 / Option 2 / Option 3 above.

[0626] For example, if multiple candidates for the number of repetitions are set by the network, the int.UE can select the number of repetitions from the multiple candidates. If no candidates for the number of repetitions are set by the network, the int.UE does not determine the number of repetitions.

[0627] (c)int. The UE determines whether the CW waveform is single-tone or multi-tone based on the following (Option 1) to (Option 4).

[0628] (Option 1) Network Configuration The int.UE determines whether the CW waveform is single-tone or multi-tone based on the following network configurations (1) and (2). (1) The network configuration may be semi-static or dynamic. (2) Network configuration may be per cell / per resource pool / per resource.

[0629] (Option 2) Implementing int.UE int.UE determines whether the CW waveform is single tone or multi-tone based on the implementation of int.UE.

[0630] (Option 3) The following conditions (1) to (5) apply: The int.UE determines whether the CW waveform is a single tone or a multi-tone based on the following conditions (1) to (5). (1) R2D / D2R reception performance based on the following items: Receiving power ·R2D / D2R was received correctly or not (2) Information on the target A-IoT device (ID, device type, etc.) (3) Message type / command type (4) Number of D2Rs backscattered in CW (5) Bandwidth occupied by CW backscattered D2R [Analysis] When the number of FDM-enhanced D2Rs is large, single-tone is preferable to multi-tone in terms of resource utilization.

[0631] (Option 4) A combination of the above options 1, 2, and 3 The int.UE determines whether the CW waveform is single tone or multi-tone based on the combination of Option 1 / Option 2 / Option 3 above.

[0632] For example, if multi-tone is enabled by the network, the int.UE can decide whether to use single tone or multi-tone, and if multi-tone is not enabled by the network, the int.UE will use single tone.

[0633] (d)int. The UE decides whether to transmit single-tone CW with or without frequency hopping based on the following (Option 1) to (Option 4).

[0634] (Option 1) Network Configuration The int.UE determines whether to transmit the single-tone CW with or without frequency hopping based on the following network configurations (1) and (2). (1) The network configuration may be semi-static or dynamic. (2) Network configuration may be per cell / per resource pool / per resource.

[0635] (Option 2) Implementing int.UE The int.UE decides whether to transmit single tone CW with or without frequency hopping based on the implementation of the int.UE.

[0636] (Option 3) The following conditions (1) to (3) apply: The int.UE determines whether to transmit a single tone CW with or without frequency hopping based on the following conditions (1) to (3). (1) R2D / D2R reception performance based on the following items: Receiving power ·R2D / D2R was received correctly or not (2) Information on the target A-IoT device (ID, device type, etc.) (3) Message type / command type

[0637] (Option 4) A combination of the above options 1, 2, and 3 The int.UE decides whether to transmit single-tone CW with or without frequency hopping based on the combination of Option 1 / Option 2 / Option 3 above.

[0638] For example, if frequency hopping is enabled by the network, the int.UE can decide whether to perform frequency hopping. If frequency hopping is not enabled by the network, the int.UE will transmit CW without frequency hopping.

[0639] (e)int. The UE determines the gap between two tones of multi-tone CW based on the following (Option 1) to (Option 4).

[0640] (Option 1) Network Configuration The int.UE determines the gap between two tones of the multi-tone CW based on the following network configurations (1) to (2). (1) The network configuration may be semi-static or dynamic. (2) Network configuration may be per cell / per resource pool / per resource.

[0641] (Option 2) Implementing int.UE int.UE determines the gap between two tones of multi-tone CW based on the implementation of int.UE.

[0642] (Option 3) The following conditions (1) to (5) apply: The int.UE determines the gap between two tones of the multi-tone CW based on the following conditions (1) to (5). (1) R2D / D2R reception performance based on the following items: Receiving power ·R2D / D2R was received correctly or not (2) Information on the target A-IoT device (ID, device type, etc.) (3) Message type / command type (4) Number of D2Rs backscattered in CW (5) Bandwidth occupied by CW backscattered D2R [Analysis] It should be noted that when the number of FDM-enhanced D2Rs is large, single-tone is preferable to multi-tone from the viewpoint of resource utilization.

[0643] (Option 4) A combination of the above options 1, 2, and 3 int.UE determines the gap between two tones of multi-tone CW based on the combination of Option 1 / Option 2 / Option 3 above.

[0644] For example, if multiple candidates for the gap between two tones of multi-tone CW are set by the network, the int.UE can select a gap between two tones of multi-tone CW from the multiple candidates.If no candidates for the gap between two tones of multi-tone CW are set by the network (NW), the int.UE does not determine a gap between two tones of multi-tone CW.

[0645] (f)int. The UE determines the gap between two tones of single-tone CW with frequency hopping based on the following (Option 1) to (Option 4).

[0646] (Option 1) Network Configuration The int.UE determines the gap between two tones of the single-tone CW by frequency hopping based on the following network configurations (1) to (2). (1) The network configuration may be semi-static or dynamic. (2) Network configuration may be per cell / per resource pool / per resource.

[0647] (Option 2) Implementing int.UE int.UE determines the gap between two tones of single-tone CW with frequency hopping based on the implementation of int.UE.

[0648] (Option 3) The following conditions (1) to (5) apply: The int.UE determines the gap between two tones of the single-tone CW by frequency hopping based on the following conditions (1) to (5). (1) R2D / D2R reception performance based on the following items: Receiving power ·R2D / D2R was received correctly or not (2) Information on the target A-IoT device (ID, device type, etc.) (3) Message type / command type (4) Number of D2Rs backscattered in CW (5) Bandwidth occupied by CW backscattered D2R [Analysis] When the number of FDM-enhanced D2Rs is large, single-tone is preferable to multi-tone in terms of resource utilization.

[0649] (Option 4) A combination of the above options 1, 2, and 3 int.UE determines the gap between two tones of single tone CW with frequency hopping based on the combination of Option 1 / Option 2 / Option 3 above.

[0650] For example, if the network sets multiple candidates for the gap between two tones of single-tone CW using frequency hopping, the int.UE can select a gap between two tones of single-tone CW using frequency hopping from the multiple candidates.If the network (NW) does not set a candidate for the gap between two tones of single-tone CW using frequency hopping, the int.UE does not determine a gap between two tones of single-tone CW using frequency hopping.

[0651] (g)int. The UE may report the following information (1) to (6) to the network. (1) Whether R2D / D2R / CW are repeated (2) Number of R2D / D2R / CW repetitions (3) Whether the CW waveform is single tone or multi-tone (4) Whether single-tone CW is transmitted with or without frequency hopping (5) Gap between two tones in multi-tone CW (6) Gap between two tones of single-tone CW due to frequency hopping

[0652] (effect) According to Proposal 3, when an int.UE autonomously selects resources to communicate, it determines the setting of parameters related to the resource selection based on conditions such as the network configuration, the implementation of the int.UE, reception performance, and device information, so that the determination of parameters related to the resource selection can be handled appropriately.

[0653] <Device configuration> Next, the configurations of the base station 10 and the device 20 will be described. Note that the configurations of the base station 10 and the device 20 described below are examples of functions related to the present embodiment. The base station 10 and the device 20 may have functions not shown. Furthermore, the functional divisions and / or names of the functional units are not limited as long as the functions perform the operations related to the present embodiment.

[0654] <Base station configuration> 51 is a block diagram showing an example of the configuration of a base station 10 according to an embodiment. The base station 10 includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. The base station 10 communicates with a device 20 (see FIG. 52) wirelessly. The base station 10 may be a terminal (int.UE communicating with the device 20) or a CW node.

[0655] The transmitter 101 transmits a downlink (DL) signal to the device 20. For example, the transmitter 101 transmits the DL signal under the control of the controller 103.

[0656] The DL signal may include, for example, a downlink data signal and control information (e.g., DCI (Downlink Control Information)). The DL signal may also include information indicating scheduling related to signal transmission of the device 20 (e.g., an UL grant). The DL signal may also include control information of higher layers (e.g., control information of RRC (Radio Resource Control)). The DL signal may also include a reference signal.

[0657] The channels used for transmitting DL signals include, for example, a data channel and a control channel. For example, the data channel may include a PDSCH (Physical Downlink Shared Channel), and the control channel may include a PDCCH (Physical Downlink Control Channel). For example, the base station 10 transmits control information to the device 20 using the PDCCH and transmits downlink data signals using the PDSCH.

[0658] The reference signals included in the DL signal may include at least one of, for example, a Demodulation Reference Signal (DMRS), a Phase Tracking Reference Signal (PTRS), a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information. For example, reference signals such as the DMRS and PTRS are used for demodulating downlink data signals and are transmitted using the PDSCH.

[0659] The receiving unit 102 receives an uplink (UL) signal transmitted from the device 20. For example, the receiving unit 102 receives the UL signal under the control of the control unit 103.

[0660] The control unit 103 controls the communication operations of the base station 10, including the transmission processing of the transmission unit 101 and the reception processing of the reception unit .

[0661] For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 101. The control unit 103 also outputs the data, control information, etc. received from the receiving unit 102 to the upper layer.

[0662] For example, the control unit 103 allocates resources (or channels) used for transmitting and receiving DL signals and / or resources used for transmitting and receiving UL signals based on a signal (e.g., data and control information, etc.) received from the device 20 and / or data and control information, etc. acquired from a higher layer. Information on the allocated resources may be included in control information transmitted to the device 20.

[0663] The control unit 103 configures PUCCH resources as an example of allocation of resources used for transmitting and receiving UL signals. Information related to PUCCH configuration such as a PUCCH cell timing pattern (PUCCH configuration information) may be notified to the device 20 by RRC.

[0664] Here, the transmitting unit 101 and the receiving unit 102 (which may be collectively referred to as a communication unit) communicate with the device 20.

[0665] For example, the transmitting unit 101 may transmit information regarding frequency resources used for communication involving the A-IoT device to the device 20, etc.

[0666] Also, for example, the communication unit may use the above frequency resources to perform communication involving A-IoT devices.

[0667] <Device configuration> 52 is a block diagram showing an example of a configuration of a device 20 according to an embodiment. The device 20 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. The device 20 communicates with, for example, a base station 10 wirelessly. The device 20 may be a terminal (for example, an int.UE) or a CW node.

[0668] The receiving unit 201 receives a DL signal transmitted from the base station 10. For example, the receiving unit 201 receives the DL signal under the control of the control unit 203.

[0669] The transmitter 202 transmits the UL signal to the base station 10. For example, the transmitter 202 transmits the UL signal under the control of the controller 203.

[0670] The UL signal may include, for example, an uplink data signal and control information (e.g., UCI (Uplink Control Information)). For example, information related to the processing capability of the device 20 (e.g., A-IoT capability) may be included. The UL signal may also include a reference signal.

[0671] The channels used for transmitting UL signals include, for example, a data channel and a control channel. For example, the data channel may include a PUSCH (Physical Uplink Shared Channel), and the control channel may include a PUCCH (Physical Uplink Control Channel). For example, the device 20 transmits control information from the base station 10 using the PUCCH and transmits uplink data signals using the PUSCH.

[0672] The reference signals included in the UL signal may include, for example, at least one of DMRS, PTRS, CSI-RS, SRS, and PRS. For example, the reference signals such as DMRS and PTRS are used for demodulating the uplink data signal and are transmitted using an uplink channel (for example, PUSCH).

[0673] The control unit 203 controls the communication operations of the device 20, including the reception process in the reception unit 201 and the transmission process in the transmission unit 202.

[0674] For example, the control unit 203 acquires information such as data and control information from a higher layer and outputs it to the transmitting unit 202. Also, the control unit 203 outputs, for example, the data and control information received from the receiving unit 201 to the higher layer.

[0675] For example, the control unit 203 controls transmission of information to be fed back to the base station 10. The information to be fed back to the base station 10 may include, for example, HARQ ACK / NACK, may include Channel State Information (CSI), or may include a Scheduling Request (SR). The information to be fed back to the base station 10 may be included in UCI. The UCI is transmitted, for example, in PUCCH resources.

[0676] Control unit 203 configures PUCCH resources based on configuration information (for example, configuration information such as a PUCCH cell timing pattern and / or DCI notified by RRC) received from base station 10. Control unit 203 determines PUCCH resources to be used for transmitting information to be fed back to base station 10. Under the control of control unit 203, transmission unit 202 transmits the information to be fed back to base station 10 in the PUCCH resources determined by control unit 203.

[0677] Note that the channel used for transmitting the DL signal and the channel used for transmitting the UL signal are not limited to the above-mentioned examples. For example, the channel used for transmitting the DL signal and the channel used for transmitting the UL signal may include a Random Access Channel (RACH) and a Physical Broadcast Channel (PBCH). The RACH may be used to transmit DCI including a Random Access Radio Network Temporary Identifier (RA-RNTI), for example.

[0678] Here, the receiving unit 201 and the transmitting unit 202 (which may be collectively referred to as a communication unit) communicate with the base station 10, the int.UE, and other networks.

[0679] For example, the receiver 201 may receive information regarding frequency resources to be used for communication involving A-IoT devices from the base station 10 or the int.UE network, and the controller 203 may determine the frequency resources to be used for communication involving A-IoT devices based on the information received by the receiver 201. The frequency resources to be used for communication involving A-IoT devices may be a single frequency resource, multiple contiguous frequency resources, or multiple non-contiguous frequency resources, and may include a first frequency resource used in a first frequency hop and a second frequency resource used in a second frequency hop.

[0680] Also, for example, the communication unit may use frequency resources determined by the control unit 203 to perform communication involving A-IoT devices.

[0681] The present disclosure has been described above. Note that the division of items in the above description is not essential to the present disclosure, and items described in two or more items may be used in combination as needed, and items described in one item may be applied to items described in another item (unless they are inconsistent).

[0682] <Hardware configuration, etc.> The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or the multiple devices with software.

[0683] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0684] For example, a base station, a device, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 53 is a diagram showing an example of the hardware configuration of a base station and a device according to the embodiment. The above-described base station 10 and device 20 may be physically configured as a computer including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0685] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the device 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0686] Each function in the base station 10 and the device 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and the memory 1002, causing the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

[0687] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 103 and control unit 203 may be realized by the processor 1001.

[0688] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 103 of the base station 10 and the control unit 203 of the device 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0689] The memory 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

[0690] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.

[0691] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitter 101, receiver 102, receiver 201, transmitter 202, etc. may be realized by the communication device 1004.

[0692] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0693] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0694] Furthermore, the base station 10 and the device 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0695] <Information notification, signaling> The notification of information is not limited to the embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0696] <Applicable systems> Embodiments described in the present disclosure may be applied to at least one of a system using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6G (6th generation mobile communication system), xG (xG (x is, for example, an integer or a decimal point)), 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 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other suitable systems, and next generation systems extended, modified, created, or defined based on these. Furthermore, a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G) may be applied.

[0697] <Processing procedures, etc.> The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0698] <Base station operation> In the present disclosure, a specific operation described as being performed by a base station may be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (for example, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (for example, an MME and an S-GW) may also be used.

[0699] <Input / output direction> Information, etc. (see the section on information and signals) can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may also be input / output via multiple network nodes.

[0700] <Handling of input and output information> Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0701] <Judgment method> The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0702] <Variations of form, etc.> Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0703] Although the present disclosure has been described in detail above, it is 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 in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0704] <Software> Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0705] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0706] <Information, Signals> The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0707] Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0708] <System, Network> As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0709] <parameter, channel name> Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0710] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0711] <Base station> In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0712] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

[0713] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

[0714] <Mobile station> In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0715] A mobile station may also be referred to by those skilled in the art as a 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, handset, user agent, mobile client, client, or some other suitable terminology.

[0716] <Base station / mobile station> At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0717] Furthermore, a base station in the present disclosure may be read as a terminal. For example, the embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the device 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0718] Similarly, the term "terminal" in the present disclosure may be read as "base station." In this case, the base station 10 may be configured to have the functions of the device 20 described above.

[0719] Fig. 54 shows an example configuration of a vehicle 2001. As shown in Fig. 54, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0720] The drive unit 2002 is configured, for example, by an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle), 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.

[0721] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0722] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0723] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

[0724] The information service unit 2012 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0725] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as a millimeter-wave radar, a LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., an IMU (Inertial Measurement Unit), an INS (Inertial Navigation System), etc.), an AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

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

[0727] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0728] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021-2029 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021-2029, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0729] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 2013 (or data / information decoded from the PDSCH)).

[0730] Furthermore, the communication module 2013 stores various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, sensors 2021 to 2029, and the like provided in the vehicle 2001.

[0731] <Terminology and interpretation> As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0732] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0733] <Reference signal> The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0734] <The meaning of "based on"> As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0735] <"First", "Second"> As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0736] <Means> In the configurations of each of the above-described devices, the "means" may be replaced with a "section", "circuit", "device", or the like.

[0737] <Open format> In the present disclosure, when the terms "include", "including", and their variants are used, these terms are intended to be inclusive, similar to the term "comprising". Further, the term "or" used in the present disclosure is not intended to be an exclusive disjunction.

[0738] <Time units such as TTI, frequency units such as RB, radio frame configuration> A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be referred to as a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that does not depend on numerology.

[0739] Numerology may be a communication parameter applied to at least one of the transmission and reception of a certain signal or channel. Numerology may indicate, for example, at least one of a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), the number of symbols per TTI, a radio frame configuration, a specific filtering process performed by a transceiver in the frequency domain, and a specific windowing process performed by a transceiver in the time domain.

[0740] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may be a time unit based on numerology.

[0741] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0742] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0743] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0744] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. However, the definition of TTI is not limited to this.

[0745] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0746] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0747] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0748] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0749] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

[0750] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0751] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0752] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0753] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0754] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0755] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0756] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0757] <Maximum transmission power> The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0758] <Article> In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0759] <"Different"> In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different." [Industrial Applicability]

[0760] One aspect of the present disclosure is useful in wireless communication systems. [Explanation of symbols]

[0761] 10 base station 20 devices 101,202 Transmitter 102,201 Receiver 103,203 Control unit

Claims

1. A wireless communication device that communicates with devices that are less complex than NB-IoT (Narrow Band Internet of Things) devices, a receiving unit that receives, from a network, resource pool information indicating a resource pool for R2D (reader to device) transmission / D2R (device to reader) reception / CW (Carrier Wave) transmission between the device; a control unit that determines parameters for selecting resources for the R2D transmission / D2R reception / CW transmission within the resource pool; A wireless communication device comprising:

2. a transmitter for reporting the determined parameters to the network; The parameters are: (1) Whether or not there is a repetition of R2D / D2R / CW (2) Number of R2D / D2R / CW repetitions (3) Whether the CW waveform is single tone or multi-tone (4) Whether the single tone CW is transmitted with or without frequency hopping (5) Gap between two tones in multi-tone CW (6) Gap between two tones of single-tone CW due to frequency hopping At least one of The wireless communication device of claim 1 .

3. The control unit determines the parameters based on whether the network configuration is semi-static or dynamic. The wireless communication device of claim 1 .

4. the control unit determines the parameters based on the implementation of the wireless communication device. The wireless communication device of claim 1 .

5. A wireless communication device that communicates with devices of lower complexity than NB-IoT (Narrow Band Internet of Things) devices, receiving, from a network, resource pool information indicating a resource pool for R2D (reader to device) transmission / D2R (device to reader) reception / CW (Carrier Wave) transmission to and from the device; determining parameters for selecting resources for the R2D transmission / D2R reception / CW transmission within the resource pool; Communication method.

Images