Device, wireless communication device, and wireless communication method

Abstract

This device comprises: a communication unit that performs a first operation of receiving a first signal from a wireless communication device connected to the device, and a second operation of being triggered or scheduled by the first signal to transmit a second signal to the wireless communication device or receive a third signal from the wireless communication device; and a control unit that determines whether or not to cause the communication unit to receive a fourth signal and / or transmit a fifth signal between the first operation and the second operation.

Description

Device, wireless communication apparatus, and wireless communication method

[0001] The present disclosure relates to a device, a wireless communication apparatus, and a wireless communication method.

[0002] For NR (New Radio) (also called "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, low power consumption, etc. (see, for example, Non-Patent Document 1).

[0003] Furthermore, in Release 18 (Rel-18) of 3GPP (registered trademark), ambient IoT (A-IoT: Ambient Internet of Things) is being considered (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.

[0004] 3GPP TS 38.300 V17.3.0 (2022-12)”Revised SID on Ambient IoT”, RP-232404, 3GPP TSG RAN Meeting #101, September 20233GPP TR 38.848 V1.0.0 (2023-09)3GPP TS 36.211 V16.8.0 (2023-09)”Study on solutions for Ambient IoT (Internet of Things) in NR”, RP-234058, 3GPP TSG RAN Meeting #102, December 2023

[0005] In a communication system that includes an ambient IoT device, the timeline of interactions between the ambient IoT device and other wireless communication devices is a consideration.

[0006] One aspect of the present disclosure provides a device, a wireless communication device, and a wireless communication method that allow an ambient IoT device to interact with other wireless communication devices on an appropriate timeline.

[0007] A device according to one aspect of the present disclosure includes a communication unit that performs a first operation of receiving a first signal from a wireless communication device connected to the device, and a second operation that is triggered or scheduled by the first signal and transmits a second signal to the wireless communication device or receives a third signal from the wireless communication device, and a control unit that determines whether to cause the communication unit to receive a fourth signal and / or transmit a fifth signal between the first operation and the second operation.

[0008] 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure. FIG. 1 is a diagram illustrating Topology 1. FIG. 2 is a diagram illustrating Topology 3 in DL assistance. FIG. 3 is a diagram illustrating Topology 3 in UL assistance. FIG. 4 is a diagram illustrating Topology 4. FIG. 5 is a diagram illustrating backscatter transmission. FIG. 6 is a diagram illustrating a communication flow of DT in Topology 1. FIG. 7 is a diagram illustrating a communication flow of DO-DTT in Topology 1. FIG. 8 is a diagram illustrating a communication flow of DT in Topology 2. FIG. 9 is a diagram illustrating a communication flow of DO-DTT in Topology 2. FIG. 10 is a diagram illustrating an example scenario in Topology 1. FIG. 11 is a diagram illustrating an example relationship between D2R backscatter and CW transmission in Topology 1. FIG. 12 is a diagram illustrating an example scenario in Topology 2. FIG. 13 is a diagram illustrating an example relationship between D2R backscatter and CW transmission in Topology 2. FIG. 14 is a diagram illustrating an example of consideration 1. FIG. 15 is a diagram illustrating a first example of consideration 2. FIG. 16 is a diagram illustrating a second example of consideration 2. FIG. 17 is a diagram illustrating a third example of consideration 2. FIG. 18 is a diagram illustrating a fourth example of consideration 2. FIG. 19 is a diagram illustrating a first example of consideration 3. FIG. 20 is a diagram illustrating a second example of consideration 3. FIG. 21 is a diagram illustrating a third example of consideration 3. FIG. 22 is a diagram illustrating a fourth example of consideration 2. 1 is a diagram illustrating an example of a timeline for proposal 1. FIG. 2 is a diagram illustrating an example of option 1 for proposal 2. FIG. 3 is a diagram illustrating an example of option 2 for proposal 2. FIG. 4 is a diagram illustrating an example of option 5 for proposal 2. FIG. 5 is a diagram illustrating an example of option 6 for proposal 2. FIG. 6 is a diagram illustrating an example of option 7 for proposal 2. FIG. 7 is a diagram illustrating an example of option 8 for proposal 2. FIG. 8 is a diagram illustrating an example of option 1 for proposal 3. FIG. 9 is a diagram illustrating an example of option 2 for proposal 3. FIG. 10 is a diagram illustrating an example of option 3 for proposal 3. FIG. 11 is a diagram illustrating an example of option 6 for proposal 3. FIG. 12 is a diagram illustrating an example of option 7 for proposal 3. FIG. 13 is a diagram illustrating an example of option 8 for proposal 3. FIG. 14 is a block diagram illustrating an example of a configuration of a base station according to an embodiment of the present disclosure. FIG. 15 is a block diagram illustrating an example of a configuration of a device according to an embodiment of the present disclosure. FIG. 16 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.1 is a diagram illustrating an example of a configuration of a vehicle according to an embodiment of the present disclosure.

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

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

[0011] In addition, in the embodiments of the present disclosure described below, terms 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) used in existing LTE 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-".

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

[0013] 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, a device, a terminal, etc. are set.

[0014] (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. The base station may also be referred to as a BS (Base Station), gNB, or the like. The device 20 may be 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.

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

[0016] The base station 10 transmits DL signals such as control information, setting information, and data via DL (Downlink) to the device 20. 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 via UP (Uplink) from the device 20.

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

[0018] 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 " / ".

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

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

[0021] 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, the 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 the PUCCH may be interpreted as uplink control information (UCI), control information, etc. transmitted in the PUSCH or the PUCCH.

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

[0023] In Ambient IoT, for example, the following deployment scenarios and characteristics may be considered for relevant use cases: Indoor or outdoor environment Base station type, e.g., macro / micro / pico cell-based deployment Connectivity topology, e.g., which nodes communicate with Ambient IoT devices, such as base stations, terminals (UE), relays and repeaters Duplexing method, TDD or FDD, licensed or unlicensed frequency band Coexistence with UE and network equipment in frequency bands for existing 3GPP technologies Assumptions of traffic originating from / terminating to devices

[0024] 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

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

[0026] <Device Types and Topologies> 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 or signal amplification functions, and performs backscattering transmission. Device B: Device B has power storage, no independent signal generation function, and performs backscattering transmission. Device B uses the stored power to amplify the reflected signal. Device C: Device C has power storage, independent signal generation function, and an active RF (radio frequency) component for transmission.

[0027] The complexity of device A is assumed to be about the same as RFID (Frequency Frequency Identification).

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

[0029] Fig. 2 is a diagram illustrating Topology 1. As shown in Fig. 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 directly communicates with the base station in a two-way manner.

[0030] 3 is a diagram illustrating Topology 2. As shown in FIG. 3, Topology 2 is a configuration in which a base station and an ambient IoT device communicate with each other 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, or the like.

[0031] 4 is a diagram illustrating Topology 3 in DL assistance. As shown in FIG. 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.

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

[0033] Fig. 5 is a diagram illustrating Topology 3 in UL support. As shown in Fig. 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 the ambient IoT device and a base station.

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

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

[0036] 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 side link (SL) communication.

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

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

[0039] Backscatter Transmission Base stations, intermediate nodes, support nodes, and other nodes transmit RF signals to ambient IoT devices that are activated and obtain power from the RF operating fields from the base stations, intermediate nodes, support nodes, and other nodes via inductive coupling.

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

[0041] 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 shown in FIG. 7 indicates an OFF section, which may correspond to information (bit) "0." A sine wave signal may correspond to information "1."

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

[0043] 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 may be considered.

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

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

[0046] DO-DTT (device originated - device terminated triggered) Traffic includes a trigger from the network (NW) and a transmission (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.

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

[0048] 2. Device Assumptions The following TX (transmission) and FR (frequency range) 1-FDD are assumed for A-IoT UE.

[0049] TX TX is a backscatter UL transmission without amplification or a general amplified UL transmission. Alternatively, an amplified backscatter UL transmission may be performed.

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

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

[0052] FR1 may use a sub-carrier spacing (SCS) of 15 kHz, 30 kHz, or 60 kHz, and 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 (including 240 kHz), and a bandwidth (BW) of 50 to 400 MHz.

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

[0054] 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 Topology 1 may correspond to a microcell.

[0055] 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 an intermediate node located between the base station and the A-IoT UE. Note that the base station in the case of Topology 2 may correspond to a macrocell. The case of Topology 2 may also be applied to indoor cases. Hereinafter, the intermediate node will also be referred to as an intermediate UE, int. UE, or Int. UE.

[0056] <Communication Flow> The signal design for A-IoT UEs may be designed to be common between Topology 1 and Topology 2. In order to have a common signal design for A-IoT UEs, the communication flows of DT and DO-DTT in Topology 1 and Topology 2 can be considered. The following four communication flows can be assumed as the communication flows of DT and DO-DTT in Topology 1 and Topology 2.

[0057] As shown in the four communication flows 1. to 4. below, the A-IoT UE wakes up in step 1 and receives information (or a signal) in step 2. Also, as shown in the communication flows 2. and 4. below, the A-IoT UE transmits a signal (or information) in step 3.

[0058] 1. DT Communication Flow in Topology 1 Figure 8 is a diagram showing the DT communication flow in Topology 1. Figure 8 shows the flow of signals between the base station and the A-IoT UE. Note that the communication flow shown in Figure 8 is a DT communication flow, so 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.

[0059] The following two steps are assumed in the DT communication flow in Topology 1. Note that Step 1 starts when a packet is generated in an upper layer such as the application layer of the base station (corresponding to "Packet arrival" in FIG. 8 ).

[0060] Step 1: The A-IoT UE wakes up by a signal such as a carrier waveform transmitted from a base station. The signal transmitted from the base station may correspond to an energy source that supplies energy to the A-IoT UE. The carrier waveform may be replaced with a carrier wave. Step 2: The A-IoT UE receives information from the base station.

[0061] The A-IoT UE may be woken up by a signal (e.g., a radio frequency signal (RF) signal) transmitted from a source other than the base station. Here, the signal transmitted from a source other than the base station may correspond to an energy source that supplies energy to the A-IoT UE.

[0062] 2. DO-DTT Communication Flow in Topology 1 Figure 9 is a diagram showing the DO-DTT communication flow in Topology 1. Figure 9 shows the flow of signals between a base station and an A-IoT UE. Note that the communication flow shown in Figure 9 is a DO-DTT communication flow, and therefore includes information transmission from the base station to the A-IoT UE and information transmission from the A-IoT UE to the base station.

[0063] The following three steps are assumed in the DO-DTT communication flow in Topology 1. Note that Step 1 starts when a packet is generated in a higher layer such as the application layer of the base station (corresponding to "Packet arrival" in FIG. 9).

[0064] Step 1: The A-IoT UE wakes up with a signal such as a carrier waveform sent from the base station. Step 2: The A-IoT UE receives information from the base station. Step 3: The A-IoT UE sends a signal to the base station.

[0065] 3. DT Communication Flow in Topology 2 Figure 10 is a diagram showing the DT communication flow in Topology 2. Figure 10 shows the flow of signals between the base station, the int. UE, and the A-IoT UE. Note that the communication flow shown in Figure 10 is a DT communication flow, so there is information transmission to the A-IoT UE, but there is no information transmission from the A-IoT UE.

[0066] The following four steps are assumed in the DT communication flow in Topology 2. Note that Step 0 starts when a packet is generated in an upper layer such as the application layer of the base station (corresponding to "Packet arrival" in FIG. 10).

[0067] Step 0: The int. UE receives a trigger from the base station to send a signal such as a carrier waveform to the A-IoT UE, and sends a signal to the A-IoT UE based on the trigger. Step 1: The A-IoT UE wakes up with a signal such as a carrier waveform sent from the int. UE. Step 2: The A-IoT UE receives information from the int. UE. Step X: The int. UE sends a signal to the base station.

[0068] 4. DO-DTT Communication Flow in Topology 2 Figure 11 is a diagram showing the DO-DTT communication flow in Topology 2. Figure 11 shows the flow of signals between the base station, the int. UE, and the A-IoT UE. Note that the communication flow shown in Figure 11 is a DO-DTT communication flow, and therefore includes information transmission to the A-IoT UE and information transmission from the A-IoT UE.

[0069] The following five-step communication flow is assumed for the DO-DTT communication flow in Topology 2. Note that step 0 starts when a packet is generated in a higher layer such as the application layer of the base station (corresponding to "Packet arrival" in FIG. 11).

[0070] Step 0: The int. UE receives a trigger from the base station to send a signal such as a carrier waveform to the A-IoT UE, and sends a signal to the A-IoT UE based on the trigger. Step 1: The A-IoT UE wakes up by a signal such as a carrier waveform sent from the int. UE. Step 2: The A-IoT UE receives information from the int. UE. Step 3: The A-IoT UE sends a signal to the int. UE. Step X: The int. UE sends a signal to the base station.

[0071] In addition, in the above four communication flows 1. to 4., step 2 and step 3 may be divided into two steps (in other words, may have two sub-steps).

[0072] For example, in the communication flow of DT in Topology 1 / 2, step 2 may have the following two sub-steps (step 2A and step 2B): Step 2A: The A-IoT UE receives information A (e.g., control information or signaling) from the base station / int. UE. Step 2B: The A-IoT UE receives information B (e.g., data information or signaling) from the base station / int. UE.

[0073] Also, for example, in the communication flow of DO-DTT in Topology 1 / 2, step 3 may have the following two sub-steps (step 3A and step 3B): Step 3A: The A-IoT UE transmits signal A (e.g., control information or signal) to the base station / int. UE. Step 3B: The A-IoT UE transmits signal B (e.g., data information or signal) to the base station / int. UE.

[0074] As described above, A-IoT communication involves various operational steps in various topologies, and channels and / or signals are transmitted and received at each step.

[0075] In the following description, channels and / or signals are referred to as channels / signals. For example, DL channels and / or DL ​​signals are referred to as DL channels / signals, and UL channels and / or UL signals are referred to as UL channels / signals.

[0076] Furthermore, transmitting a DL channel / signal and receiving a DL channel / signal may be referred to as DL transmission and DL reception, respectively. Furthermore, transmitting a UL channel / signal and receiving a UL channel / signal may be referred to as UL transmission and UL reception, respectively.

[0077] Furthermore, in the following description, the DL channel / signal may be at least one of the following: DL channel for control information (e.g., DL channel for transmitting control information) DL channel for data (e.g., DL channel for transmitting data) DL synchronization signal (hereinafter, synchronization signal may be referred to as "sync") DL preamble DL midamble DL postamble DL reference signal DL sequence

[0078] Note that a DL preamble is provided before a DL transmission, a DL midamble is provided between multiple DL transmissions, and a DL postamble is provided after a DL transmission.

[0079] Furthermore, in the following description, the UL channel / signal may be at least one of the following: UL channel for control information (e.g., UL channel for transmitting control information) UL channel for data (e.g., UL channel for transmitting data) UL synchronization signal (hereinafter, synchronization signal may be referred to as "sync") UL preamble UL midamble UL postamble UL reference signal UL sequence

[0080] The UL preamble is provided before a UL transmission, the UL midamble is provided between multiple UL transmissions, and the UL postamble is provided after a UL transmission.

[0081] In this embodiment, DL may be replaced with R2D (reader to device), and UL may be replaced with D2R (device to reader). Note that the reader corresponds to the BS and / or Int. UE, and the device corresponds to the A-IoT device. Note that, hereinafter, the BS and / or Int. UE may be referred to as BS / Int. UE. Also, the BS may be replaced with a gNB. That is, the BS / Int. UE may be replaced with a gNB / Int. UE.

[0082] Transmission of at least one of the UL channel for control information, the UL channel for data, and the UL signal (e.g., at least one of a preamble, an UL synchronization signal, an UL reference signal, and an UL sequence) from the A-IoT device may be scheduled / triggered by at least one of the DL channel for control information, the DL channel for data, and the DL signal (e.g., at least one of a preamble, an UL synchronization signal, an UL reference signal, and an DL sequence). Note that at least one of the DL channel for control information, the DL channel for data, and the DL signal (e.g., at least one of a preamble, an UL synchronization signal, an UL reference signal, and an DL sequence) for scheduling / triggering is transmitted from the BS / Int. UE.

[0083] Note that a UL channel / signal #y scheduled / triggered by a certain DL channel / signal #x may be referred to as a UL channel / signal #y corresponding to the DL channel / signal #x, or simply as a corresponding UL channel / signal #y. Note that DL channel / signal #x scheduling / triggering UL channel / signal #y (DL channel / signal #x schedules / triggers UL channel / signal #y) may be understood as DL channel / signal #x scheduling / triggering transmission of a corresponding UL channel / signal #y (DL channel / signal #x schedules / triggers transmission of a corresponding UL channel / signal #y).

[0084] Reception of at least one of the DL channel for control information, the DL channel for data, and DL signals (e.g., at least one of a preamble, a DL synchronization signal, a DL reference signal, and a DL sequence) at the A-IoT device may be scheduled / triggered by at least one of the DL channel for control information, the DL channel for data, and DL signals (e.g., at least one of a preamble, a UL synchronization signal, a UL reference signal, and a DL sequence). At least one of the DL channel for control information, the DL channel for data, and DL signals (e.g., at least one of a preamble, a UL synchronization signal, a UL reference signal, and a DL sequence) for scheduling / triggering is transmitted from the BS / Int. UE.

[0085] Note that a DL channel / signal #y scheduled / triggered by a certain DL channel / signal #x may be referred to as a DL channel / signal #y corresponding to the DL channel / signal #x, or simply as a corresponding DL channel / signal #y. Note that the scheduling / triggering of a DL channel / signal #y by the DL channel / signal #x may be considered as the DL channel / signal #x scheduling / triggering reception of the DL channel / signal #y.

[0086] <Device Types> It is being considered that there are multiple types of A-IoT devices in terms of power consumption. For example, the following three device types, Device 1, Device 2a, and Device 2b, have been agreed upon.

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

[0088] Device 2a (may be referred to as type 2a) Device 2a is a type of device that consumes a peak power of several hundred μW. Device 2a has energy storage and an initial sample frequency offset of up to Z [ppm] (Z is 10 to the xth power (x is an integer equal to or greater than 0)). DL and / or UL amplification is performed in device 2a. UL transmission in device 2a is performed by backscattering with an externally provided carrier wave (carrier wave (CW)).

[0089] Device 2b (may be referred to as type 2b) Device 2b is a type of device that consumes a peak power of several hundred μW. Device 2b has energy storage and an initial sample frequency offset of up to Z [ppm] (Z is 10 to the xth power (x is an integer equal to or greater than 0)). Furthermore, DL and / or UL amplification is performed in device 2b. UL transmission in device 2b is performed internally in device 2b. In other words, UL transmission in device 2b does not need to be performed by backscattering with an externally provided carrier wave (carrier wave (CW)).

[0090] <Examples of Assumed Scenarios> Next, we will explain scenarios that are considered in Topology 1. As scenarios in Topology 1, scenarios called D1T1-A, D1T1-B, and D1T1-C are considered, by way of example.

[0091] Fig. 12 is a diagram showing an example of a scenario in Topology 1. Fig. 12 shows the relationship between nodes (e.g., BS / Int.UE) and A-IoT devices in four scenarios, D1T1-A1, D1T1-A2, D1T1-B, and D1T1-C, as example scenarios.

[0092] In D1T1-A, the topology includes an indoor BS and an indoor A-IoT device. The topology also includes a node that is the source of the CW. D1T1-A is divided into D1T1-A1 and D1T1-A2.

[0093] As shown in FIG. 12, in D1T1-A1, a CW to an A-IoT device (hereinafter referred to as "CW2D" (CW to device)), an R2D communication signal (referred to as "R2D" in FIG. 12), and a D2R communication signal (referred to as "D2R" in FIG. 12) are transmitted and received. The node that transmits CW2D is different from the node that receives the D2R communication signal, and the node that transmits CW2D is the same as the node that transmits the R2D communication signal. Furthermore, the node that transmits the R2D communication signal is different from the node that receives the D2R communication signal. In other words, the R in R2D is different from the R in D2R.

[0094] As shown in FIG. 12, in D1T1-A2, the node that transmits CW2D, the node that transmits the R2D communication signal, and the node that receives the D2R communication signal are the same.

[0095] In D1T1-A, R2D communication occurs at least in the DL spectrum (also referred to as the "DL band"). This D1T1-A scenario applies only to Device 1 and Device 2a described above.

[0096] 12, in D1T1-B, an indoor BS and an indoor A-IoT device are included in the topology, and a node that is the source of the CW exists outside the topology.

[0097] In D1T1-B, R2D communication is performed at least in the DL spectrum (DL band). This D1T1-B scenario applies only to the device 1 and device 2a described above.

[0098] In D1T1-B, the node that transmits CW2D is different from the node that transmits the R2D communication signal. Also, in D1T1-B, the node that transmits CW2D is different from the node that receives the D2R communication signal. Also, in D1T1-B, the node that transmits the R2D communication signal is the same as the node that receives the D2R communication signal. In other words, the R in R2D and the R in D2R are the same.

[0099] As shown in FIG. 12, in D1T1-C, the topology includes an indoor BS and an indoor A-IoT device that performs active UL transmission.

[0100] In D1T1-C, R2D communication occurs in the DL spectrum (DL band) and D2R communication occurs in the UL spectrum (also referred to as the "UL band"). This D1T1-C scenario applies only to device 2b described above.

[0101] In D1T1-C, the node that transmits the signal for R2D communication is the same as the node that receives the signal for D2R communication, i.e., R in R2D is the same as R in D2R.

[0102] In the above scenario of Topology 1, where the D2R backscatter signal is transmitted on the same carrier as the CW for D2R backscatter, three cases are considered for CW transmission: Case 1-1, Case 1-2, and Case 1-4.

[0103] Fig. 13 is a diagram illustrating an example of the relationship between D2R backscattering and CW transmission in Topology 1. Fig. 13 shows the D2R backscattering spectrum and the CW transmission spectrum in each of three cases.

[0104] As illustrated in Figure 13, the following three cases, Case 1-1, Case 1-2, and Case 1-4, are considered for CW transmission. Case 1-1: CW is transmitted from inside the topology in the DL spectrum. Case 1-2: CW is transmitted from inside the topology in the UL spectrum. Case 1-4: CW is transmitted from outside the topology in the UL spectrum.

[0105] Next, we will explain the scenarios considered in Topology 2. As the scenarios in Topology 2, scenarios called D2T2-A, D2T2-B, and D2T2-C are considered, by way of example.

[0106] Fig. 14 is a diagram showing an example of a scenario in Topology 2. Fig. 14 shows the relationship between nodes (e.g., BS / Int.UE) and A-IoT devices in four scenarios, D2T2-A1, D2T2-A2, D2T2-B, and D2T2-C, as example scenarios.

[0107] In D2T2-A, the topology includes an outdoor BS, an indoor Int. UE, and an indoor A-IoT device. The topology also includes a node that is the source of the CW. D2T2-A is divided into D2T2-A1 and D2T2-A2.

[0108] 14, in D2T2-A1, the node that transmits CW2D is different from the node that receives the D2R communication signal, and the node that transmits CW2D 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. In other words, the R in R2D is different from the R in D2R.

[0109] As shown in FIG. 14, in D2T2-A2, the node that transmits CW2D, the node that transmits R2D communication signals, and the node that receives D2R communication signals are the same.

[0110] In the D2T2-A scenario, R2D communication is performed in the UL spectrum (UL band). This D2T2-A scenario applies only to the device 1 and device 2a described above.

[0111] 14, in the D2T2-B, the topology includes an outdoor BS, an indoor Int. UE, and an indoor A-IoT device. Also, a node that is the source of the CW exists outside the topology.

[0112] In D2T2-B, R2D communication is performed in the UL spectrum (UL band). This D2T2-B scenario applies only to the above-mentioned device 1 and device 2a.

[0113] In D2T2-B, the node that transmits CW2D is different from the node that transmits the R2D communication signal. Also, in D1T1-B, the node that transmits CW2D is different from the node that receives the D2R communication signal. Also, in D1T1-B, the node that transmits the R2D communication signal is the same as the node that receives the D2R communication signal. In other words, the R in R2D and the R in D2R are the same.

[0114] As shown in Fig. 14, in D2T2-C, the topology includes an outdoor BS, an indoor Int. UE, and an indoor A-IoT device that performs active UL transmission.

[0115] In the D2T2-C scenario, R2D communication is performed in the UL spectrum (UL band) and D2R communication is performed in the UL spectrum (UL band). This D2T2-C scenario applies only to the device 2b described above.

[0116] In D1T1-C, the node that transmits the signal for R2D communication is the same as the node that receives the signal for D2R communication, i.e., R in R2D is the same as R in D2R.

[0117] In the above scenario of Topology 2, where the D2R backscatter signal is transmitted on the same carrier as the CW for D2R backscatter, three cases are considered for CW transmission: Case 2-2, Case 2-3, and Case 2-4.

[0118] Fig. 15 is a diagram illustrating an example of the relationship between D2R backscattering and CW transmission in Topology 2. Fig. 15 shows the D2R backscattering spectrum and the CW transmission spectrum in each of three cases.

[0119] As illustrated in Figure 15, the following three cases, Case 2-2, Case 2-3, and Case 2-4, are considered for CW transmission: Case 2-2: CW is transmitted in the UL spectrum from inside the topology (i.e., Int.UE). Case 2-3: CW is transmitted in the DL spectrum from outside the topology. Case 2-4: CW is transmitted in the UL spectrum from outside the topology.

[0120] Note that the above-described scenarios are examples, and the present disclosure is not limited thereto. The present disclosure may be applied to scenarios other than those described above. Furthermore, the types of nodes, the number of nodes, the types of A-IoT devices, the number of A-IoT devices, and the bands used in the above-described scenarios are examples, and the present disclosure is not limited thereto. Furthermore, the terms "indoor" and "outdoor" in the above-described scenarios do not necessarily limit the locations of the nodes and A-IoT devices.

[0121] As described above, the band in which signals are transmitted and received, for example, the band in which CW is transmitted, may differ depending on the type of A-IoT device (e.g., device 1, device 2a, or device 2b), the topology, and the scenario applied based on the topology.

[0122] For example, as in the above-mentioned D2T2-A, D2T2-B, and D2T2-C, there are cases where R2D communication is performed in the UL band. Also, as in D2T2-C, there are cases where R2D communication and D2R communication are performed in the same UL band. Also, for example, as described above, there can be cases where the band in which the CW is transmitted is the DL band and cases where the band in which the CW is transmitted is the DL band.

[0123] <Considerations> As described above, in A-IoT systems, it is being considered that A-IoT devices will perform various operations depending on the type of device, topology, frequency used (e.g., carrier or band), etc.

[0124] Among such various operations, there is room for consideration regarding the relationship (e.g., timeline) between the time of a DL channel / signal received by the A-IoT device and the time of a UL channel / signal transmitted by the A-IoT device. Three considerations regarding the timeline will be described below as examples.

[0125] <Consideration 1> For example, in an A-IoT device, whether or not to provide time for switching between receiving a DL channel / signal and transmitting a UL channel / signal, and if so, the length of the time for switching, etc. are unclear, and therefore there is room for consideration. Note that, hereinafter, reception and transmission are referred to as Rx and Tx, respectively, and the time required to switch between reception and transmission, i.e., the time required to switch between Rx and Tx, is referred to as switching time.

[0126] For example, if the presence or absence of a switching time and the length of the switching time are not set appropriately, a DL channel / signal may arrive from another wireless communication device (e.g., a BS / Int. UE) before the A-IoT device switches from transmission to reception. In this way, there is a risk that the A-IoT device will not be able to receive the DL channel / signal that arrives before switching from transmission to reception.

[0127] Furthermore, for example, if the presence or absence of a switching time and the length of the switching time are not set appropriately, other wireless communication devices (e.g., BS / Int.UE) may not be able to properly trigger or schedule transmission or reception in the A-IoT device.

[0128] Furthermore, for example, if the presence or absence of a switching time and the length of the switching time are not set appropriately, the next reception or transmission may not be executed even though the A-IoT device has completed switching from transmission to reception or from reception to transmission. In this way, if the next reception or transmission is not executed even though the switching from reception to transmission has been completed, the communication speed may decrease, power consumption may increase, or consumption of time resources may increase.

[0129] Figure 16 is a diagram showing an example of consideration 1. Figure 16 shows two cases of interaction between a gNB / Int. UE and an A-IoT UE (A-IoT device).

[0130] When an A-IoT device operates in half-duplex FDD, a switching time from Rx to Tx and a switching time from Tx to Rx are required, as shown in Case 1 of Fig. 16. However, there is room for consideration regarding the time gap for switching from Tx to Rx and the time gap for switching from Rx to Tx.

[0131] Note that the subject of consideration as consideration item 1 is the switching time for switching from Rx to Tx, as exemplified in Case 1 of FIG. 16 . The time gap of the switching time for switching from Rx to Tx is different from the time gap between the DL channel / signal and the corresponding UL channel / signal triggered / scheduled by the DL channel signal. Note that the time gap between the DL channel / signal and the corresponding UL channel / signal triggered / scheduled by the DL channel signal may be considered as the processing time for DL ​​reception and UL transmission in the A-IoT device. For example, as shown in Case 2 of FIG. 16 , the time gap between the DL channel / signal and the corresponding UL channel / signal triggered / scheduled by the DL channel signal is considered as the processing time. The processing time may include the switching time. Alternatively, unlike Case 2 of FIG. 16 , the processing time and the switching time may be set separately.

[0132] Also, the subject of consideration as consideration 1 is the switching time for switching from Tx to Rx. The time gap for switching from Tx to Rx is different from the time gap between the UL channel / signal and the corresponding DL channel / signal in response to the UL channel signal. Note that the time gap between the UL channel / signal and the corresponding DL channel / signal in response to the UL channel signal may be considered as the processing time for UL reception and DL transmission at the BS / Int. UE.

[0133] <Consideration 2> When DL channel / signal #α received by an A-IoT device schedules / triggers the transmission of UL channel / signal #β, other operations during the time interval between the reception of DL channel / signal #α and the transmission of UL channel / signal #β (hereinafter referred to as time interval Δ) are unclear, and there is room for consideration regarding the execution of other operations during this time interval Δ.

[0134] If the operation in the time interval Δ is not performed properly, for example, a channel / signal #γ that should not be received is received during the time interval Δ and processing of the channel / signal #γ is performed, which may prevent proper transmission of the UL channel / signal #β scheduled / triggered by the DL channel / signal #α, and the transmission of the UL channel / signal #β may be discarded. Also, if the operation in the time interval Δ is not performed properly, for example, transmission processing of a channel / signal #γ that should not be transmitted is performed during the time interval Δ, which may prevent proper transmission of the UL channel / signal #β scheduled / triggered by the DL channel / signal #α, and the transmission of the UL channel / signal #β may be discarded.

[0135] Now, by way of example, consider the operation in the time interval between DL channel / signal #1 and UL channel / signal #1, where DL channel / signal #1 triggers / schedules the transmission of a corresponding UL channel / signal #1 transmitted from an A-IoT device.

[0136] FIG. 17 is a diagram showing a first example of Consideration 2. FIG. 17 shows Case 1 of interaction between a gNB / Int. UE and an A-IoT UE. FIG. 18 is a diagram showing a second example of Consideration 2. FIG. 18 shows Cases 2 and 3 of interaction between a gNB / Int. UE and an A-IoT UE. FIG. 19 is a diagram showing a third example of Consideration 2. FIG. 19 shows Cases 4 and 5 of interaction between a gNB / Int. UE and an A-IoT UE. FIG. 20 is a diagram showing a fourth example of Consideration 2. FIG. 20 shows Case 6 of interaction between a gNB / Int. UE and an A-IoT UE.

[0137] For example, if DL channel / signal #1 triggers / schedules the transmission of a corresponding UL channel / signal #1 transmitted from an A-IoT device, it may be considered whether another DL channel / signal #2 may be received in the time interval between DL channel / signal #1 and UL channel / signal #1. For example, as shown in Case 1 of Figure 17, it may be considered whether DL channel / signal #2 may be received between the reception of DL channel / signal #1 and the transmission of UL channel / signal #1.

[0138] It is worth considering whether in the time interval between this DL channel / signal #1 and UL channel / signal #1, another DL channel / signal #2 may be received that triggers / schedules the transmission of the corresponding UL channel / signal #2.

[0139] For example, if this DL channel / signal #2 may be received, it may be considered whether this DL channel / signal #2 can trigger / schedule the corresponding UL channel / signal #2 before the UL channel / signal #1. For example, as shown in Case 2 of Figure 18, it may be considered whether a DL channel / signal #2 that triggers / schedules the UL channel / signal #2 before the UL channel / signal #1 may be received between the reception of the DL channel / signal #1 and the transmission of the UL channel / signal #1. Note that the UL channel / signal #2 before the UL channel / signal #1 corresponds to the UL channel / signal #2 whose transmission is triggered / scheduled at a timing before the transmission of the UL channel / signal #1.

[0140] Furthermore, for example, if this DL channel / signal #2 may be received, it may be considered whether this DL channel / signal #2 can trigger / schedule a corresponding UL channel / signal #2 that is later than the UL channel / signal #1. For example, as shown in Case 3 of Figure 18, it may be considered whether a DL channel / signal #2 that triggers or schedules a UL channel / signal #2 that is later than the UL channel / signal #1 may be received between the reception of the DL channel / signal #1 and the transmission of the UL channel / signal #1. Note that the UL channel / signal #2 later than the UL channel / signal #1 corresponds to the UL channel / signal #2 whose transmission is triggered / scheduled at a timing later than the timing at which the UL channel / signal #1 is transmitted.

[0141] It is worth considering whether in the time interval between this DL channel / signal #1 and UL channel / signal #1, another DL channel / signal #2 may be received that triggers or schedules the reception of the corresponding DL channel / signal #3.

[0142] For example, if this DL channel / signal #2 may be received, it may be considered whether this DL channel / signal #2 can trigger / schedule the corresponding DL channel / signal #3 before the UL channel / signal #1. For example, as shown in Case 4 of Figure 19, it may be considered whether a DL channel / signal #2 may be received between the reception of DL channel / signal #1 and the transmission of UL channel / signal #1 that triggers / schedules the DL channel / signal #3 before the UL channel / signal #1.

[0143] Also, for example, if this DL channel / signal #2 may be received, it may be considered whether this DL channel / signal #2 can trigger / schedule a corresponding DL channel / signal #3 that is later than UL channel / signal #1. For example, as shown in Case 5 of Figure 19, it may be considered whether a DL channel / signal #2 that triggers / schedules a DL channel / signal #3 that is later than UL channel / signal #1 may be received between the reception of DL channel / signal #1 and the transmission of UL channel / signal #1.

[0144] Furthermore, in the time interval between this DL channel / signal #1 and UL channel / signal #1, if DL channel / signal #3 is triggered / scheduled by DL channel / signal #0 before DL channel / signal #1, it is possible to consider whether DL channel / signal #3 may be received. For example, as shown in Case 6 of Figure 20, if DL channel / signal #3 is triggered / scheduled by DL channel / signal #0 before DL channel / signal #1, it is possible to consider whether DL channel / signal #3 may be received in the time interval between DL channel / signal #1 and UL channel / signal #1.

[0145] As explained above, consideration 2 considers other operations in the time interval between DL channel / signal #1 and UL channel / signal #1 when DL channel / signal #1 triggers / schedules the transmission of UL channel / signal #1.

[0146] <Consideration 3> When DL channel / signal #α received by an A-IoT device schedules or triggers the reception of DL channel / signal #β, other operations during the time interval between the reception of DL channel / signal #α and the reception of DL channel / signal #β (hereinafter referred to as time interval Δ) are unclear, and there is room for consideration regarding the execution of other operations during this time interval Δ.

[0147] If the operation in the time interval Δ is not performed properly, for example, a channel / signal #γ that should not be received is received and processing of the channel / signal #γ is performed during the time interval Δ, which may prevent proper reception of the DL channel / signal #β scheduled or triggered by the DL channel / signal #α, and the reception of the DL channel / signal #β may be discarded. Also, if the operation in the time interval Δ is not performed properly, for example, transmission processing of the channel / signal #γ that should not be transmitted is performed during the time interval Δ, which may prevent proper reception of the DL channel / signal #β scheduled / triggered by the DL channel / signal #α, and the reception of the DL channel / signal #β may be discarded.

[0148] Now, consider, by way of example, the operation in the time interval between DL channel / signal #X1 and DL channel / signal #Y1, where DL channel / signal #X1 triggers / schedules the reception of corresponding DL channel / signal #Y1.

[0149] FIG. 21 is a diagram showing a first example of Consideration 3. FIG. 21 shows Case 1 of interaction between a gNB / Int. UE and an A-IoT UE. FIG. 22 is a diagram showing a second example of Consideration 3. FIG. 22 shows Cases 2 and 3 of interaction between a gNB / Int. UE and an A-IoT UE. FIG. 23 is a diagram showing a third example of Consideration 3. FIG. 23 shows Cases 4 and 5 of interaction between a gNB / Int. UE and an A-IoT UE. FIG. 24 is a diagram showing a fourth example of Consideration 3. FIG. 24 shows Case 6 of interaction between a gNB / Int. UE and an A-IoT UE.

[0150] For example, if DL channel / signal #X1 triggers / schedules the reception of corresponding DL channel / signal #Y1, it may be considered whether another DL channel / signal #Z may be received in the time interval between DL channel / signal #X1 and DL channel / signal #Y1. For example, as shown in Case 1 of Figure 21, it may be considered whether DL channel / signal #Z may be received between the reception of DL channel / signal #X1 and the reception of DL channel / signal #Y1.

[0151] It is worth considering whether in the time interval between this DL channel / signal #X1 and DL channel / signal #Y1, another DL channel / signal #X2 may be received that triggers / schedules the reception of the corresponding DL channel / signal #Y2.

[0152] For example, if this DL channel / signal #X2 may be received, it may be considered whether this DL channel / signal #X2 can trigger / schedule the corresponding DL channel / signal #Y2 that precedes the DL channel / signal #Y1. For example, as shown in Case 2 of Figure 22, it may be considered whether DL channel / signal #X2 that triggers / schedules the DL channel / signal #Y2 that precedes the DL channel / signal #Y1 may be received between the reception of DL channel / signal #X1 and the reception of DL channel / signal #Y1.

[0153] Furthermore, for example, if this DL channel / signal #X2 may be received, it may be considered whether this DL channel / signal #X2 can trigger / schedule the corresponding DL channel / signal #Y2 that comes after the DL channel / signal #Y1. For example, as shown in Case 3 of Figure 22, it may be considered whether a DL channel / signal #X2 that triggers / schedules the DL channel / signal #Y2 that comes after the DL channel / signal #Y1 may be received between the reception of DL channel / signal #X1 and the reception of DL channel / signal #Y1.

[0154] It is worth considering whether in the time interval between this DL channel / signal #X1 and DL channel / signal #Y1, another DL channel / signal #X2 may be received which triggers / schedules the transmission of the corresponding UL channel / signal.

[0155] For example, if this DL channel / signal #X2 may be received, it may be considered whether this DL channel / signal #X2 can trigger / schedule a corresponding UL channel / signal earlier than DL channel / signal #Y1. For example, as shown in Case 4 of Figure 23, it may be considered whether DL channel / signal #X2 that triggers / schedules a UL channel / signal earlier than DL channel / signal #Y1 may be received between the reception of DL channel / signal #X1 and the reception of DL channel / signal #Y1.

[0156] Also, for example, if this DL channel / signal #X2 may be received, it may be considered whether this DL channel / signal #X2 can trigger / schedule a corresponding UL channel / signal that is later than the DL channel / signal #Y1. For example, as shown in Case 5 of Figure 23, it may be considered whether a DL channel / signal #X2 that triggers / schedules a UL channel / signal that is later than the DL channel / signal #Y1 may be received between the reception of the DL channel / signal #X1 and the reception of the DL channel / signal #Y1.

[0157] Furthermore, in the time interval between this DL channel / signal #X1 and DL channel / signal #Y1, if the UL channel / signal is triggered / scheduled by DL channel / signal #X0 before DL channel / signal #X1, there is room for consideration as to whether the UL channel / signal may be transmitted. For example, as shown in Case 6 in Figure 24, if the UL channel / signal is triggered / scheduled by DL channel / signal #X0 before DL channel / signal #X1, there is room for consideration as to whether the UL channel / signal may be transmitted in the time interval between DL channel / signal #X1 and DL channel / signal #Y1.

[0158] As explained above, consideration 3 considers other operations in the time interval between DL channel / signal #X1 and DL channel / signal #Y1 when DL channel / signal #X1 triggers / schedules reception of DL channel / signal #Y1.

[0159] In response to the above considerations, this embodiment proposes a definition of the timeline operation regarding transmission and reception of DL channels / signals and UL channels / signals.

[0160] Illustratively, Proposal 0 and Proposal 1 below correspond to proposals for Consideration 1, Proposal 2 corresponds to proposals for Consideration 2, and Proposal 3 corresponds to proposals for Consideration 3.

[0161] In the following embodiment, the fact that a certain device (e.g., an A-IoT device) #v does not receive a certain channel / signal #w may be replaced with the fact that the device #v is not required to receive the channel / signal #w, or that the device #v is not expected to receive the channel / signal #w.

[0162] Also, in the following embodiment, a certain device (e.g., an A-IoT device) #v not transmitting a certain channel / signal #w may be replaced with the device #v not being required to transmit the channel / signal #w, or the device #v not being expected to transmit the channel / signal #w.

[0163] Also, in the following embodiment, a certain device (e.g., an A-IoT device) #v not processing a certain channel / signal #w may be replaced with the device #v not being required to process the channel / signal #w, or the device #v not being expected to process the channel / signal #w.

[0164] Furthermore, in the following embodiment, a certain device (e.g., an A-IoT device) #v not receiving a certain channel / signal #w may be replaced with a certain device (e.g., an A-IoT device) #v not processing (e.g., processing related to reception) a certain channel / signal #w.

[0165] Furthermore, in the following embodiment, the fact that a certain device (e.g., an A-IoT device) #v does not receive a certain channel / signal #w may be replaced by the fact that a certain device (e.g., an A-IoT device) #v does not execute part of the processing of a certain channel / signal #w (e.g., processing related to reception). For example, the fact that a certain device (e.g., an A-IoT device) #v does not execute part of the processing of a certain channel / signal #w (e.g., processing related to reception) may be replaced by the fact that the first half of the processing of the channel / signal #w is executed and the remaining subsequent processing is not executed.

[0166] Furthermore, in the following embodiment, the fact that the A-IoT device #v does not receive the channel / signal #w may correspond to the fact that the BS / Int. UE connected to the A-IoT device #v does not transmit the channel / signal #w. Furthermore, the fact that the A-IoT device #v does not receive the channel / signal #w may correspond to the fact that the BS / Int. UE connected to the A-IoT device #v does not receive the channel / signal #w when it transmits the channel / signal #w.

[0167] In the following embodiment, the A-IoT device #v's failure to receive the channel / signal #w may correspond to the A-IoT device #v discarding, ignoring, or dropping the channel / signal #w. Also, the A-IoT device #v's failure to receive the channel / signal #w may correspond to the A-IoT device #v ceasing, suspending, postponing, or suspending processing related to the reception of the channel / signal #w.

[0168] Furthermore, in the following embodiment, a certain device (e.g., an A-IoT device) #v not transmitting a certain channel / signal #w may be replaced with a certain device (e.g., an A-IoT device) #v not processing (e.g., processing related to transmission) a certain channel / signal #w.

[0169] Furthermore, in the following embodiment, a certain device (e.g., an A-IoT device) #v not transmitting a certain channel / signal #w may be replaced by a certain device (e.g., an A-IoT device) #v not executing part of the processing of a certain channel / signal #w (e.g., processing related to transmission). For example, not executing part of the processing of a certain channel / signal #w (e.g., processing related to transmission) may be replaced by executing the first half of the processing of the channel / signal #w and not executing the remaining subsequent processing.

[0170] In the following embodiment, the fact that the A-IoT device #v does not transmit the channel / signal #w may correspond to the fact that the BS / Int. UE connected to the A-IoT device #v does not receive the channel / signal #w transmitted by the A-IoT device #v.

[0171] In the following embodiment, the A-IoT device #v not transmitting the channel / signal #w may correspond to the A-IoT device #v discarding, ignoring, or dropping the channel / signal #w. Also, the A-IoT device #v not transmitting the channel / signal #w may correspond to the A-IoT device #v canceling, suspending, postponing, or suspending the processing related to the transmission of the channel / signal #w.

[0172] <Proposal 0> A DL to UL switching time, switching gap, or time separation is specified for an A-IoT device. Also, a UL to DL switching time, switching gap, or time separation is specified for an A-IoT device. Note that, although the following description uses switching time as an example, switching time may be replaced with switching gap or time separation.

[0173] For example, the unit of the switching time may be any of μs, ms, symbols, slots, etc. For example, the switching time may be X μs, Y ms, Z symbols, etc. Here, X, Y, and Z may be positive integers or positive real numbers.

[0174] The switching time may vary among device types of A-IoT devices. Here, the device types include Type 1, Type 2a, Type 2b, etc., as described above. The switching time may vary, for example, depending on whether the A-IoT device has a frequency shifter block in its structure. For example, the switching time in an A-IoT device that has a frequency shifter block may be longer than the switching time in an A-IoT device that does not have a frequency shifter block.

[0175] The switching time may be common across device types of A-IoT devices.

[0176] The switching time may vary depending on the topology of the connection between the devices, for example, the switching time when an A-IoT device is connected to a BS may be different from the switching time when the A-IoT device is connected to an Int. UE.

[0177] The switching time may be common within the topology of the connection between devices.

[0178] The switching time may differ depending on the carrier used for R2D reception and the carrier used for D2R transmission. For example, the switching time differs depending on whether the carrier used for R2D reception and the carrier used for D2R transmission are the same or different. For example, the switching time when the carrier used for R2D reception and the carrier used for D2R transmission are the same differs from the switching time when the carrier used for R2D reception and the carrier used for D2R transmission are different. Here, both the carrier used for R2D reception and the carrier used for D2R transmission may be included in the DL band or the UL band. Alternatively, one of the carrier used for R2D reception and the carrier used for D2R transmission may be included in the DL band, and the other may be included in the UL band.

[0179] The switching time may be common to the carrier used for R2D reception and the carrier used for D2R transmission, regardless of the carrier used for R2D reception and the carrier used for D2R transmission.

[0180] The switching time may differ depending on the band used for R2D reception and the band used for D2R transmission. For example, the switching time differs depending on whether the band used for R2D reception and the band used for D2R transmission are the same or different. For example, the switching time when the band used for R2D reception and the band used for D2R transmission are the same may differ from the switching time when the band used for R2D reception and the band used for D2R transmission are different. Furthermore, for example, the switching time when the band used for R2D reception and the band used for D2R transmission are the same DL band may differ from the switching time when the band used for R2D reception and the band used for D2R transmission are the same UL band. Here, both the band used for R2D reception and the band used for D2R transmission may be DL bands or UL bands. Alternatively, one of the band used for R2D reception and the band used for D2R transmission may be DL band, and the other may be UL band.

[0181] The switching time may be common regardless of the band used for R2D reception and the band used for D2R transmission. The switching time may be a common value between A-IoT UEs, or may be different values. The switching time may also be a maximum value. The A-IoT UE may be capable of switching in a time shorter than the switching time. For example, when the switching time is the maximum value, the A-IoT UE may be capable of switching in a time shorter than the maximum value indicated by the switching time.

[0182] <Proposal 1> Figure 25 is a diagram showing an example of a timeline for Proposal 1. Figure 25 shows Case 1 and Case 2 of interactions between a gNB / Int. UE and an A-IoT UE. In Case 1, the A-IoT device transmits a UL channel / signal #1 that starts or ends at time #n, and in Case 2, the A-IoT device receives a DL channel / signal #1 that starts or ends at time #n.

[0183] Note that time #n may be a single timing or may have a certain time interval. When time #n is a single timing, transmitting UL channel / signal #1 that starts or ends at time #n corresponds to the transmission start timing or transmission end timing of UL channel / signal #1 being time #n. Furthermore, when time #n has a time interval, transmitting UL channel / signal #1 that starts or ends at time #n corresponds to the transmission start timing or transmission end timing of UL channel / signal #1 being included in the range of time #n.

[0184] In Proposal 1, as shown in Case 1 of Figure 25, when an A-IoT device transmits UL channel / signal #1 that starts or ends at time #n, the A-IoT device does not receive DL channel / signal #2 that starts or ends less than X time units after time #n. Also, in this case, the A-IoT device does not receive a DL channel / signal that triggers / schedules DL channel / signal #2.

[0185] In Proposal 1, as shown in Case 1 of Figure 25, when an A-IoT device transmits UL channel / signal #1 that starts or ends at time #n, the A-IoT device does not receive DL channel / signal #0 that starts or ends less than Y time units before time #n. Also, in this case, the A-IoT device does not receive a DL channel / signal that schedules DL channel / signal #0 or a DL channel / signal that triggers DL channel / signal #2.

[0186] In Proposal 1, when an A-IoT device transmits a UL channel / signal #1 that starts or ends at time #n, the A-IoT device may receive a DL channel / signal #2 that starts or ends X or more time units after time #n. Also, in Proposal 1, when an A-IoT device transmits a UL channel / signal #1 that starts or ends at time #n, the A-IoT device may receive a DL channel / signal #0 that starts or ends Y or more time units before time #n.

[0187] In Proposal 1, as shown in Case 2 of Figure 25, when an A-IoT device receives a DL channel / signal #1 that starts or ends at time #n, the A-IoT device does not transmit a UL channel / signal #2 that starts or ends less than Y time units after time #n. Also, in this case, the A-IoT device does not receive a DL channel / signal that schedules / triggers the UL channel / signal #2.

[0188] In Proposal 1, as shown in Case 2 of Figure 25, when an A-IoT device receives a DL channel / signal #1 that starts or ends at time #n, the A-IoT device does not transmit a UL channel / signal #0 that starts or ends less than X time units before time #n. Also, in this case, the A-IoT device does not receive a DL channel / signal that triggers / schedules the UL channel / signal #0.

[0189] In Proposal 1, X and / or Y, which define the time range for time #n, may be defined by a specification, may be preset, or may be indicated by the BS / Int. UE. Furthermore, the time units of X and / or Y in Proposal 1 may be any of μs, ms, symbols, slots, etc., as shown in Proposal 0.

[0190] For example, X and / or Y may be defined by a specification, may be set in advance, or may be indicated by the BS / Int. UE depending on at least one of the following items: Type of A-IoT device Capability of the A-IoT device Band used for R2D reception and / or D2R transmission Whether the band used for R2D reception and / or D2R transmission is a UL band or a DL band Carrier or band used for R2D reception and / or D2R transmission Whether the carrier used for R2D reception and / or D2R transmission is the same or different Whether the band used for R2D reception and / or D2R transmission is the same or different Topology related to the connection of the A-IoT device Whether the A-IoT device is connected to a BS or an Int. UE

[0191] In the above-mentioned proposal 1, the time interval indicated by X may be the minimum time required for switching from UL transmission to DL reception, and in the above-mentioned proposal 1, the time interval indicated by Y may be the minimum time required for switching from DL reception to UL reception.

[0192] In the above-described Proposal 1, X and Y may be the same or different. Furthermore, one of X and Y may be determined based on the other.

[0193] The carrier wave used for backscattering and / or the RF signal for energy supply may be excluded from the DL channel / signal in the above Proposal 1. In other words, if the DL signal is a CW for backscattering or an RF signal for energy supply, the A-IoT device may receive the DL signal regardless of the switching time.

[0194] In Proposal 1 described above, for example, an A-IoT device performs either a first operation (e.g., DL reception) of receiving a DL channel / signal from a wireless communication device (e.g., BS / Int.UE) connected to the A-IoT device, or a second operation (e.g., UL transmission) of transmitting a UL channel / signal to the wireless communication device, and a specific time interval (e.g., a time interval indicated by X and / or Y) is set before and / or after one of the operations, and the other of the first and second operations is not performed within the specific time interval.

[0195] According to the above-described Proposal 1, since the switching time is appropriately set, the A-IoT device can communicate with other wireless communication devices on an appropriate timeline. For example, according to Proposal 1, since the switching time is appropriately set, switching from UL transmission to DL reception and / or switching from DL reception to UL reception can be performed, and therefore communication with other wireless communication devices can be performed on an appropriate timeline.

[0196] <Proposal 2> We consider the case where an A-IoT device receives a DL channel / signal #1 from a BS / Int. UE that starts or ends at time #n, and the DL channel / signal #1 triggers / schedules the transmission of a corresponding UL channel / signal #1 that starts or ends at time #m. In this case, during the time interval from time #n to time #m, the A-IoT device may perform at least one of the following options:

[0197] <Option 1 of Proposal 2> Figure 26 is a diagram showing an example of Option 1 of Proposal 2. Figure 26 shows the interaction between a gNB / Int. UE and an A-IoT UE in Option 1 of Proposal 2.

[0198] As shown in Figure 26, in Option 1 of Proposal 2, the A-IoT device does not receive any DL channels / signals in the time interval from time #n to time #m. In other words, in Option 1, the A-IoT device does not receive any DL channels / signals in the time interval from time #n to time #m.

[0199] <Option 2 of Proposal 2> Figure 27 is a diagram showing an example of Option 2 of Proposal 2. Figure 27 shows interactions between a gNB / Int. UE and an A-IoT UE in Option 2 of Proposal 2.

[0200] In Option 2 of Proposal 2, the A-IoT device does not receive the first type of DL channel / signal. In this case, in Option 2, the A-IoT device may receive a second type of DL channel / signal other than the first type. For example, the first type of DL channel / signal may be a DL channel for control information and / or a DL channel for data. Furthermore, the second type of DL channel / signal other than the first type may be a DL synchronization signal. Note that the first type and / or the second type may be defined by a specification, may be preset, or may be indicated by the BS / Int. UE.

[0201] In the example of Figure 27, the A-IoT device does not receive a DL channel for control information / data as an example of the first type, and receives a DL synchronization signal as an example of the second type.

[0202] <Option 3 of Proposal 2> Figure 28 is a diagram showing an example of Option 3 of Proposal 2. Figure 28 shows interactions between a gNB / Int. UE and an A-IoT UE in Option 3 of Proposal 2.

[0203] In Option 3 of Proposal 2, the A-IoT device does not receive a DL channel / signal whose format, purpose, and / or function are the same as those of DL channel / signal #1. For example, if at least one of the format, purpose, and / or function is the same between DL channel / signal #p and DL channel / signal #1, the A-IoT device does not receive DL channel / signal #p.

[0204] In the example of Figure 28, the A-IoT device does not receive DL channel / signal #2, which has the same format as DL channel / signal #1.

[0205] In addition, if the A-IoT device does not receive a DL channel / signal having the same format as the format of DL channel / signal #1, it may receive a DL channel / signal having a format different from the format of DL channel / signal #1.

[0206] <Option 4 of Proposal 2> Figure 29 is a diagram showing an example of Option 4 of Proposal 2. Figure 29 shows two cases of interaction between a gNB / Int. UE and an A-IoT UE in Option 4 of Proposal 2.

[0207] In Option 4 of Proposal 2, the A-IoT device does not receive another DL channel / signal #2 that triggers / schedules the transmission of the corresponding UL channel / signal #2. Also, in Option 4, the A-IoT device does not receive another DL channel / signal #2 that triggers / schedules the transmission of the corresponding UL channel / signal #2 and does not transmit the UL channel / signal #2.

[0208] In case 1 of Figure 29, the A-IoT device does not receive DL channel / signal #2 that triggers / schedules the transmission of UL channel / signal #2 after UL channel / signal #1. Also, in case 1 of Figure 29, the A-IoT device does not transmit UL channel / signal #2 after UL channel / signal #1.

[0209] In case 2 of Figure 29, the A-IoT device does not receive DL channel / signal #2 that triggers / schedules the transmission of UL channel / signal #2 before UL channel / signal #1. Also, in case 2 of Figure 29, the A-IoT device does not transmit UL channel / signal #2 before UL channel / signal #1.

[0210] <Option 5 of Proposal 2> Figure 30 is a diagram showing an example of Option 5 of Proposal 2. Figure 30 shows two cases of interaction between a gNB / Int. UE and an A-IoT UE in Option 5 of Proposal 2.

[0211] In Option 5 of Proposal 2, if the start or end of a UL channel / signal #2 triggered / scheduled by a DL channel / signal #2 is before time #m, the A-IoT device does not receive another DL channel / signal #2 that triggers / schedules the transmission of the corresponding UL channel / signal #2 and does not transmit the UL channel / signal #2. Note that in Option 5 of Proposal 2, if the start or end of a UL channel / signal #2 triggered / scheduled by a DL channel / signal #2 is after time #m, the A-IoT device may receive another DL channel / signal #2 that triggers / schedules the transmission of the corresponding UL channel / signal #2 and transmit the UL channel / signal #2.

[0212] Here, the case where UL channel / signal #2 starts or ends before time #m corresponds to the case where UL channel / signal #2 starts or ends before UL channel / signal #1. Also, the case where UL channel / signal #2 starts or ends after time #m corresponds to the case where UL channel / signal #2 starts or ends after UL channel / signal #1.

[0213] In case 1 of Figure 30, the A-IoT device receives DL channel / signal #2 which triggers / schedules the transmission of UL channel / signal #2 after UL channel / signal #1. Also, in case 1 of Figure 30, the A-IoT device transmits UL channel / signal #2 after UL channel / signal #1.

[0214] In case 2 of Figure 30, the A-IoT device does not receive DL channel / signal #2 that triggers / schedules the transmission of UL channel / signal #2 before UL channel / signal #1. Also, in case 2 of Figure 30, the A-IoT device does not transmit UL channel / signal #2 before UL channel / signal #1.

[0215] As another variation of option 5 of proposal 2, DL channel / signal #2 may not be received in case 1 of FIG. 30, and DL channel / signal #2 may be received in case 2 of FIG.

[0216] <Option 6 of Proposal 2> Figure 31 is a diagram showing an example of Option 6 of Proposal 2. Figure 31 shows two cases of interaction between a gNB / Int. UE and an A-IoT UE in Option 6 of Proposal 2.

[0217] In Option 6 of Proposal 2, the A-IoT device does not receive another DL channel / signal #2 that triggers / schedules reception of the corresponding DL channel / signal #3. Also, in Option 6, the A-IoT device does not receive another DL channel / signal #2 that triggers / schedules reception of the corresponding DL channel / signal #3, and does not receive DL channel / signal #3.

[0218] In case 1 of Figure 31, the A-IoT device does not receive DL channel / signal #2, which triggers / schedules the reception of DL channel / signal #3, which comes after UL channel / signal #1. Also, in case 1 of Figure 31, the A-IoT device does not receive DL channel / signal #3, which comes after UL channel / signal #1.

[0219] In case 2 of Figure 31, the A-IoT device does not receive DL channel / signal #2 which triggers / schedules the reception of DL channel / signal #3 before UL channel / signal #1. Also, in case 2 of Figure 31, the A-IoT device does not receive DL channel / signal #3 before UL channel / signal #1.

[0220] <Option 7 of Proposal 2> Figure 32 is a diagram showing an example of Option 7 of Proposal 2. Figure 32 shows two cases of interaction between a gNB / Int. UE and an A-IoT UE in Option 7 of Proposal 2.

[0221] In Option 7 of Proposal 2, if the start or end of DL channel / signal #3 triggered / scheduled by DL channel / signal #2 is before time #m, the A-IoT device does not receive another DL channel / signal #2 that triggers / schedules reception of the corresponding DL channel / signal #3, and does not receive DL channel / signal #3. Note that in Option 7 of Proposal 2, if the DL channel / signal #3 triggered / scheduled by DL channel / signal #2 is after time #m, the A-IoT device may receive another DL channel / signal #2 that triggers / schedules reception of the corresponding DL channel / signal #3, and may receive DL channel / signal #3.

[0222] Here, the case where DL channel / signal #3 starts or ends before time #m corresponds to the case where DL channel / signal #3 starts or ends before UL channel / signal #1. Also, here, the case where DL channel / signal #3 starts or ends after time #m corresponds to the case where DL channel / signal #3 starts or ends after UL channel / signal #1.

[0223] In case 1 of Figure 32, the A-IoT device receives DL channel / signal #2 which triggers / schedules the reception of DL channel / signal #3 after UL channel / signal #1. Also, in case 1 of Figure 32, the A-IoT device receives DL channel / signal #3 after UL channel / signal #1.

[0224] In case 2 of Figure 32, the A-IoT device does not receive DL channel / signal #2 that triggers or schedules reception of DL channel / signal #3 before UL channel / signal #1. Also, in case 2 of Figure 32, the A-IoT device does not receive DL channel / signal #3 before UL channel / signal #1.

[0225] As another variation of option 7 of proposal 2, DL channel / signal #3 may not be received in case 1 of FIG. 32, and DL channel / signal #3 may be received in case 2 of FIG.

[0226] <Option 8 of Proposal 2> Figure 33 is a diagram showing an example of Option 8 of Proposal 2. Figure 33 shows the interaction between a gNB / Int. UE and an A-IoT UE in Option 8 of Proposal 2.

[0227] In Option 8 of Proposal 2, as shown in Figure 33, the A-IoT device will not receive DL channel / signal #3 even if DL channel / signal #3 is triggered / scheduled by DL channel / signal #0 which starts or ends before time #n.

[0228] <Option 9 of Proposal 2> In Option 9 of Proposal 2, an A-IoT device may receive any DL channel / signal in the time interval from time #n to time #m. In other words, in Option 9, an A-IoT device can receive any DL channel / signal in the time interval from time #n to time #m.

[0229] <Option 10 of Proposal 2> In Option 10 of Proposal 2, an A-IoT device may receive a DL channel / signal where at least one of the format, purpose, and function of the channel / signal is the same as that of DL channel / signal #1. For example, if at least one of the format, purpose, and function of DL channel / signal #p is the same as that of DL channel / signal #1, the A-IoT device may receive DL channel / signal #p.

[0230] Referring to Figure 28, although Figure 28 shows that DL channel / signal #2 having the same format as DL channel / signal #1 is not received, if option 10 of Proposal 2 is applied, DL channel / signal #2 having the same format as DL channel / signal #1 shown in Figure 28 may be received.

[0231] In addition, when an A-IoT device receives a DL channel / signal having the same format as that of DL channel / signal #1, it does not need to receive a DL channel / signal having a format different from that of DL channel / signal #1.

[0232] <Option 11 of Proposal 2> In Option 11 of Proposal 2, the A-IoT device may receive another DL channel / signal #2 that triggers or schedules the transmission of a corresponding UL channel / signal #2. Also in Option 11, the A-IoT device may receive another DL channel / signal #2 that triggers / schedules the transmission of a corresponding UL channel / signal #2 and transmit the UL channel / signal #2.

[0233] Explaining this with reference to Figure 29, Case 1 in Figure 29 shows that DL channel / signal #2 that triggers / schedules transmission of UL channel / signal #2 after UL channel / signal #1 is not received, but if Option 11 of Proposal 2 is applied, DL channel / signal #2 shown in Case 1 in Figure 29 may be received. Also, in this case, UL channel / signal #2 shown in Case 1 in Figure 29 may be transmitted. For Case 2 in Figure 29, similarly to Case 1, if Option 11 of Proposal 2 is applied, DL channel / signal #2 shown in Case 2 in Figure 29 may be received and UL channel / signal #2 may be transmitted.

[0234] <Option 12 of Proposal 2> In Option 12 of Proposal 2, the A-IoT device may receive another DL channel / signal #2 that triggers / schedules reception of a corresponding DL channel / signal #3. Also in Option 12, the A-IoT device may receive another DL channel / signal #2 that triggers / schedules reception of a corresponding DL channel / signal #3 and receive DL channel / signal #3.

[0235] Explaining this with reference to Figure 31, Case 1 in Figure 31 shows that DL channel / signal #2 that triggers / schedules reception of DL channel / signal #3 after UL channel / signal #1 is not received, but when Option 12 of Proposal 2 is applied, DL channel / signal #2 shown in Case 1 in Figure 31 may be received. In this case, DL channel / signal #3 shown in Case 1 in Figure 31 may also be received. Also, for Case 2 in Figure 31, similarly to Case 1, when Option 12 of Proposal 2 is applied, DL channel / signal #2 and DL channel / signal #3 shown in Case 2 in Figure 31 may be received.

[0236] <Option 13 of Proposal 2> In Option 13 of Proposal 2, an A-IoT device may receive DL channel / signal #3 that is triggered / scheduled by DL channel / signal #0 that starts or ends before time #n.

[0237] Referring to Figure 33, it is shown that DL channel / signal #3 triggered / scheduled by DL channel / signal #0 starting or ending before time #n is not received, but if option 13 of Proposal 2 is applied, DL channel / signal #3 shown in Figure 33 may be received.

[0238] In any of the above-described options, the A-IoT device may need to receive or process a DL channel / signal other than DL channel / signal #1 (e.g., DL channel / signal #2). For example, reception or processing may be performed to identify the content of a DL channel / signal other than DL channel / signal #1 (e.g., DL channel / signal #2). In this case, the A-IoT device may receive or process a DL channel / signal other than DL channel / signal #1 (e.g., DL channel / signal #2) and skip subsequent processing. For example, in a case where option 4 is applied, if the A-IoT device performs reception processing of DL channel / signal #2 and determines that DL channel / signal #2 triggers / schedules UL channel / signal #2, transmission processing of UL channel / signal #2 is skipped. Also, for example, in a case where option 6 is applied, if the A-IoT device performs receive processing of DL channel / signal #2 and determines that DL channel / signal #2 triggers / schedules DL channel / signal #3, the transmit processing of UL channel / signal #2 is skipped.

[0239] Depending on which of the options in Proposal 2 described above is applied, the A-IoT device may determine whether to perform a DL channel / signal reception operation and / or a UL channel / signal transmission operation. For example, the A-IoT device may determine the DL channel / signal to receive or the UL channel / signal to transmit. Also, depending on which of the options in Proposal 2 is applied, the BS / Int. UE may determine whether to perform a DL channel / signal transmission operation and / or a UL channel / signal reception operation. For example, the BS / Int. UE may determine the DL channel / signal to transmit or the UL channel / signal to receive.

[0240] Which of the options in Proposal 2 described above is to be applied may be fixed by specifications, may be preset, or may be instructed by the BS / Int. UE. Furthermore, which of the options in Proposal 2 is to be applied may be fixed by specifications, may be preset, or may be instructed by the BS / Int. UE, depending on at least one of the following items: Type of A-IoT device Capability of the A-IoT device Band used for R2D reception and / or D2R transmission Whether the band used for R2D reception and / or D2R transmission is a UL band or a DL band Carrier or band used for R2D reception and / or D2R transmission Whether the carrier used for R2D reception and / or D2R transmission is the same or different Whether the band used for R2D reception and / or D2R transmission is the same or different Topology related to the connection of the A-IoT device Whether the A-IoT device is connected to a BS or an Int. UE

[0241] The carrier wave used for backscattering and / or the RF signal for energy supply may be excluded from the DL channel / signal in each option of Proposal 2. That is, if the DL signal is a CW for backscattering or an RF signal for energy supply, the A-IoT device may receive the DL signal independently of other DL channels / signals and UL channels / signals.

[0242] In addition, when an A-IoT device receives a DL channel / signal in a time interval between time #n and time #m, the A-IoT device may be able to receive a maximum of X DL channels / signals (X is an integer greater than or equal to 1, for example, X=1) in that time interval. In Proposal 2, DL channel / signal #1 starts or ends at time #n, and UL channel / signal #1 triggered / scheduled by DL channel / signal #1 starts or ends at time #m. In this case, X may be defined by a specification, may be preset, or may be indicated by the BS / Int. UE. For example, X may be defined by a specification, may be preset, or may be indicated by the BS / Int. UE depending on at least one of the type of the A-IoT device and the capability of the A-IoT device.

[0243] In addition, when an A-IoT device transmits UL channels / signals in the time interval between time #n and time #m, the A-IoT device may be capable of transmitting a maximum of Y UL channels / signals (Y is an integer equal to or greater than 1, for example, Y=1) in that time interval. In this case, Y may be defined by a specification, may be set in advance, or may be indicated by the BS / Int. UE. For example, X may be defined by a specification, may be set in advance, or may be indicated by the BS / Int. UE depending on at least one of the type of the A-IoT device and the capability of the A-IoT device.

[0244] In addition, if the A-IoT device receives another DL channel / signal or a DL channel / signal that triggers / schedules a UL channel / signal in the time interval between time #n and time #m, the A-IoT device may apply one of the following three alternations regarding the transmission of UL channel / signal #1 scheduled to start or end at time #m: Alt. 1: The A-IoT device can transmit UL channel / signal #1. Alt. 2: The A-IoT device cancels or drops the transmission of UL channel / signal #1. Alt. 3: The A-IoT device suspends or postpones the transmission of UL channel / signal #1 for a specific time interval.

[0245] In Proposal 2 described above, for example, an A-IoT device performs a first operation of receiving a first signal (e.g., DL channel / signal #1) from a wireless communication device (e.g., BS / Int.UE) connected to the A-IoT device, and a second operation of transmitting a second signal (e.g., UL channel / signal #1) to the wireless communication device, triggered or scheduled by the first signal, and between the first and second operations, determines whether to receive a fourth signal (e.g., DL channel / signal #2) and / or transmit a fifth signal (e.g., UL channel / signal #2).

[0246] According to the above-described proposal 2, the operation in the time interval between the reception of the DL channel / signal #1 and the transmission of the UL channel / signal #1 triggered / scheduled by the DL channel / signal #1 is appropriately set, so that the A-IoT device can communicate with other wireless communication devices on an appropriate timeline. For example, according to proposal 2, the operation in the time interval is appropriately set, so that the A-IoT device can communicate with other wireless communication devices appropriately depending on whether the reception operation or the transmission operation is possible in the time interval.

[0247] <Proposal 3> The case where an A-IoT device receives a DL channel / signal #X1 from a BS / Int. UE that starts or ends at time #n, and the DL channel / signal #X1 triggers / schedules the reception of a corresponding DL channel / signal #Y1 that starts or ends at time #m, in this case, during the time interval from time #n to time #m, the A-IoT device may perform at least one of the following options:

[0248] <Option 1 of Proposal 3> Figure 34 is a diagram showing an example of Option 1 of Proposal 3. Figure 34 shows the interaction between a gNB / Int. UE and an A-IoT UE in Option 1 of Proposal 3.

[0249] As shown in Figure 34, in Option 1 of Proposal 3, the A-IoT device does not receive any DL channel / signal (DL channel / signal #Z in Figure 34) in the time interval from time #n to time #m. In other words, in Option 1, the A-IoT device does not receive any DL channel / signal in the time interval from time #n to time #m.

[0250] <Option 2 of Proposal 3> Figure 35 is a diagram showing an example of Option 2 of Proposal 3. Figure 35 shows the interaction between a gNB / Int. UE and an A-IoT UE in Option 2 of Proposal 3.

[0251] In Option 2 of Proposal 3, the A-IoT device does not receive the first type of DL channel / signal. In this case, in Option 2, the A-IoT device may receive a second type of DL channel / signal other than the first type. For example, the first type of DL channel / signal may be a DL channel for control information and / or a DL channel for data. Furthermore, the second type of DL channel / signal other than the first type may be a DL synchronization signal. Note that the first type and / or the second type may be defined by a specification, may be preset, or may be indicated by the BS / Int. UE.

[0252] In the example of Figure 35, the A-IoT device does not receive a DL channel for control information / data as an example of the first type, and receives a DL synchronization signal as an example of the second type.

[0253] <Option 3 of Proposal 3> Figure 36 is a diagram showing an example of Option 3 of Proposal 3. Figure 36 shows the interaction between a gNB / Int. UE and an A-IoT UE in Option 3 of Proposal 3.

[0254] In Option 3 of Proposal 3, the A-IoT device does not receive a DL channel / signal whose format, purpose, and / or function are the same as those of DL channel / signal #X1. For example, if at least one of the format, purpose, and / or function is the same between DL channel / signal #p and DL channel / signal #X1, the A-IoT device does not receive DL channel / signal #p.

[0255] In the example of Figure 36, the A-IoT device does not receive DL channel / signal #X2, which has the same format as DL channel / signal #X1.

[0256] In addition, if the A-IoT device does not receive a DL channel / signal having the same format as the format of DL channel / signal #X1, it may receive a DL channel / signal having a format different from the format of DL channel / signal #X1.

[0257] <Option 4 of Proposal 3> Figure 37 is a diagram showing an example of Option 4 of Proposal 3. Figure 37 shows two cases of interaction between a gNB / Int. UE and an A-IoT UE in Option 4 of Proposal 3.

[0258] In Option 4 of Proposal 3, the A-IoT device does not receive another DL channel / signal #X2 that triggers / schedules reception of the corresponding DL channel / signal #Y2. Also, in Option 4, the A-IoT device does not receive another DL channel / signal #X2 that triggers / schedules reception of the corresponding DL channel / signal #Y2, and does not receive DL channel / signal #Y2.

[0259] In case 1 of Figure 37, the A-IoT device does not receive DL channel / signal #X2 that triggers / schedules the reception of DL channel / signal #Y2 after DL channel / signal #Y1. Also, in case 1 of Figure 37, the A-IoT device does not receive DL channel / signal #Y2 after DL channel / signal #Y1.

[0260] In case 2 of Figure 37, the A-IoT device does not receive DL channel / signal #X2 that triggers / schedules the reception of DL channel / signal #Y2 before DL channel / signal #Y1. Also, in case 2 of Figure 37, the A-IoT device does not receive DL channel / signal #Y2 before DL channel / signal #Y1.

[0261] <Option 5 of Proposal 3> Figure 38 is a diagram showing an example of Option 5 of Proposal 3. Figure 38 shows two cases of interaction between a gNB / Int. UE and an A-IoT UE in Option 5 of Proposal 3.

[0262] In option 5 of Proposal 3, if the start or end of DL channel / signal #Y2 triggered / scheduled by DL channel / signal #X2 is before time #m, the A-IoT device does not receive another DL channel / signal #X2 that triggers / schedules reception of the corresponding DL channel / signal #Y2, and does not receive DL channel / signal #Y2. Note that in option 5 of Proposal 3, if the start or end of DL channel / signal #Y2 triggered / scheduled by DL channel / signal #X2 is after time #m, the A-IoT device may receive another DL channel / signal #X2 that triggers / schedules reception of the corresponding DL channel / signal #Y2, and may receive DL channel / signal #Y2.

[0263] Here, the case where DL channel / signal #Y2 starts or ends before time #m corresponds to the case where DL channel / signal #Y2 starts or ends before DL channel / signal #Y1, and the case where DL channel / signal #Y2 starts or ends after time #m corresponds to the case where DL channel / signal #Y2 starts or ends after DL channel / signal #Y1.

[0264] In case 1 of Figure 38, the A-IoT device receives DL channel / signal #X2 that triggers / schedules the reception of DL channel / signal #Y2 after DL channel / signal #Y1. Also, in case 1 of Figure 38, the A-IoT device receives DL channel / signal #Y2 after DL channel / signal #Y1.

[0265] In case 2 of Figure 38, the A-IoT device does not receive DL channel / signal #X2 that triggers / schedules the reception of DL channel / signal #Y2 before DL channel / signal #Y1. Also, in case 2 of Figure 38, the A-IoT device does not receive DL channel / signal #Y2 before DL channel / signal #Y1.

[0266] As another variation of option 5 of proposal 3, DL channel / signal #X2 may not be received in case 1 of FIG. 38, and DL channel / signal #X2 may be received in case 2 of FIG.

[0267] <Option 6 of Proposal 3> Figure 39 is a diagram showing an example of Option 6 of Proposal 3. Figure 39 shows two cases of interaction between a gNB / Int. UE and an A-IoT UE in Option 6 of Proposal 3.

[0268] In Option 6 of Proposal 3, the A-IoT device does not receive another DL channel / signal #X2 that triggers / schedules the transmission of a corresponding UL channel / signal. Also, in Option 6, the A-IoT device does not receive another DL channel / signal #X2 that triggers / schedules the transmission of a corresponding UL channel / signal, and does not receive the UL channel / signal.

[0269] In case 1 of Figure 39, the A-IoT device does not receive DL channel / signal #X2 that triggers / schedules the transmission of a UL channel / signal after DL channel / signal #Y1. Also, in case 1 of Figure 39, the A-IoT device does not transmit a UL channel / signal after DL channel / signal #Y1.

[0270] In case 2 of Figure 39, the A-IoT device does not receive DL channel / signal #X2 that triggers / schedules the transmission of a UL channel / signal before DL channel / signal #Y1. Also, in case 2 of Figure 39, the A-IoT device does not transmit a UL channel / signal before DL channel / signal #Y1.

[0271] <Option 7 of Proposal 3> Figure 40 is a diagram showing an example of Option 7 of Proposal 3. Figure 40 shows two cases of interaction between a gNB / Int. UE and an A-IoT UE in Option 7 of Proposal 3.

[0272] In Option 7 of Proposal 3, if the start or end of a UL channel / signal triggered / scheduled by DL channel / signal #X2 is before time #m, the A-IoT device does not receive another DL channel / signal #X2 that triggers / schedules the transmission of the corresponding UL channel / signal, and does not receive the UL channel / signal. Note that in Option 7 of Proposal 3, if the UL channel / signal triggered / scheduled by DL channel / signal #X2 is after time #m, the A-IoT device may receive another DL channel / signal #X2 that triggers / schedules the transmission of the corresponding UL channel / signal, and transmit the UL channel / signal.

[0273] Here, the start or end of the UL channel / signal before time #m corresponds to the start or end of the UL channel / signal before DL channel / signal #Y1, and the start or end of the UL channel / signal after time #m corresponds to the start or end of the UL channel / signal after DL channel / signal #Y1.

[0274] In Case 1 of Figure 40, the A-IoT device receives DL channel / signal #X2 that triggers / schedules the transmission of a UL channel / signal after DL channel / signal #Y1. Also, in Case 1 of Figure 40, the A-IoT device transmits a UL channel / signal after DL channel / signal #Y1.

[0275] In Case 2 of Figure 40, the A-IoT device does not receive DL channel / signal #X2 that triggers / schedules the transmission of a UL channel / signal before DL channel / signal #Y1. Also, in Case 2 of Figure 40, the A-IoT device does not transmit a UL channel / signal before DL channel / signal #Y1.

[0276] As another variation of option 7 of proposal 3, DL channel / signal #X2 may not be received in case 1 of FIG. 40, and DL channel / signal #X2 may be received in case 2 of FIG.

[0277] <Option 8 of Proposal 3> Figure 41 is a diagram showing an example of Option 8 of Proposal 3. Figure 41 shows the interaction between a gNB / Int. UE and an A-IoT UE in Option 8 of Proposal 3.

[0278] In Option 8 of Proposal 3, as shown in Figure 41, an A-IoT device will not transmit an UL channel / signal even if the UL channel / signal is triggered / scheduled by DL channel / signal #X0 that starts or ends before time #n.

[0279] <Option 9 of Proposal 3> In Option 9 of Proposal 3, an A-IoT device may receive any DL channel / signal in the time interval from time #n to time #m. In other words, in Option 9, an A-IoT device can receive any DL channel / signal in the time interval from time #n to time #m.

[0280] <Option 10 of Proposal 3> In Option 10 of Proposal 3, an A-IoT device may receive a DL channel / signal that has the same format, purpose, and / or function as DL channel / signal #X1. For example, if at least one of the format, purpose, and / or function is the same between DL channel / signal #p and DL channel / signal #X1, the A-IoT device may receive DL channel / signal #p.

[0281] Referring to Figure 36, although Figure 36 shows that DL channel / signal #X2 having the same format as DL channel / signal #X1 is not received, if option 10 of Proposal 3 is applied, DL channel / signal #X2 having the same format as DL channel / signal #X1 shown in Figure 36 may be received.

[0282] In addition, when an A-IoT device receives a DL channel / signal having the same format as the format of DL channel / signal #X1, it does not need to receive a DL channel / signal having a format different from the format of DL channel / signal #X1.

[0283] <Option 11 of Proposal 3> In Option 11 of Proposal 3, the A-IoT device may receive another DL channel / signal #X2 that triggers / schedules reception of a corresponding DL channel / signal #Y2. Also in Option 11, the A-IoT device may receive another DL channel / signal #X2 that triggers / schedules reception of a corresponding DL channel / signal #Y2 and receive DL channel / signal #Y2.

[0284] Explaining this with reference to Figure 37, Case 1 in Figure 37 shows that DL channel / signal #X2, which triggers / schedules reception of DL channel / signal #Y2 after DL channel / signal #Y1, is not received. However, when Option 11 of Proposal 3 is applied, DL channel / signal #X2 shown in Case 1 in Figure 37 may be received. Also, in this case, DL channel / signal #Y2 shown in Case 1 in Figure 37 may be received. Regarding Case 2 in Figure 37, similarly to Case 1, when Option 11 of Proposal 3 is applied, DL channel / signal #X2 shown in Case 2 in Figure 37 may be received, and DL channel / signal #Y2 may be received.

[0285] <Option 12 of Proposal 3> In Option 12 of Proposal 3, the A-IoT device may receive another DL channel / signal #X2 that triggers / schedules the transmission of a corresponding UL channel / signal. Also in Option 12, the A-IoT device may receive another DL channel / signal #X2 that triggers / schedules the transmission of a corresponding UL channel / signal and transmit the UL channel / signal.

[0286] Explaining this with reference to Figure 39, Case 1 in Figure 39 shows that DL channel / signal #X2, which triggers / schedules the transmission of a UL channel / signal after DL channel / signal #Y1, is not received. However, when Option 12 of Proposal 3 is applied, DL channel / signal #X2 shown in Case 1 in Figure 39 may be received. In this case, the UL channel / signal shown in Case 1 in Figure 39 may be transmitted. Also, for Case 2 in Figure 39, similarly to Case 1, when Option 12 of Proposal 3 is applied, DL channel / signal #X2 shown in Case 2 in Figure 39 may be received and the UL channel / signal may be transmitted.

[0287] <Option 13 of Proposal 3> In Option 13 of Proposal 3, an A-IoT device may receive DL channel / signal #3 that is triggered / scheduled by DL channel / signal #0 that starts or ends before time #n.

[0288] Referring to Figure 41, although Figure 41 indicates that UL channels / signals triggered / scheduled by DL channel / signal #X0 that starts or ends before time #n are not transmitted, if Option 13 of Proposal 3 is applied, the UL channels / signals shown in Figure 41 may be transmitted.

[0289] In any of the above-described options, the A-IoT device may need to receive or process a DL channel / signal other than DL channel / signal #X1 and DL channel / signal #Y1 (e.g., DL channel / signal #X2). For example, reception or processing may be performed to identify the contents of DL channels / signals other than DL channel / signal #X1 and DL channel / signal #Y1. In this case, the A-IoT device may receive or process DL channels / signals other than DL channel / signal #X1 and DL channel / signal #Y1 and skip subsequent processing. For example, in a case where option 4 is applied, if the A-IoT device performs reception processing of DL channel / signal #X2 and determines that DL channel / signal #X2 triggers / schedules DL channel / signal #Y2, the reception processing of DL channel / signal #Y2 is skipped. Also, for example, in a case where option 6 is applied, if the A-IoT device performs reception processing of DL channel / signal #X2 and determines that DL channel / signal #X2 triggers / schedules a UL channel / signal, the transmission processing of the UL channel / signal is skipped.

[0290] Depending on which of the options in Proposal 3 described above is applied, the A-IoT device may determine whether to perform a DL channel / signal reception operation and / or a UL channel / signal transmission operation. For example, the A-IoT device may determine the DL channel / signal to receive or the UL channel / signal to transmit. Also, depending on which of the options in Proposal 3 is applied, the BS / Int. UE may determine whether to perform a DL channel / signal transmission operation and / or a UL channel / signal reception operation. For example, the BS / Int. UE may determine the DL channel / signal to transmit or the UL channel / signal to receive.

[0291] Which of the options in Proposal 3 described above is to be applied may be fixed by the specifications, preset, or instructed by the BS / Int. UE. Also, which of the options in Proposal 2 is to be applied may be fixed by the specifications, preset, or instructed by the BS / Int. UE, depending on at least one of the following items: Type of A-IoT device Capability of the A-IoT device Band used for R2D reception and / or D2R transmission Whether the band used for R2D reception and / or D2R transmission is a UL band or a DL band Carrier or band used for R2D reception and / or D2R transmission Whether the carrier used for R2D reception and / or D2R transmission is the same or different Whether the band used for R2D reception and / or D2R transmission is the same or different Topology related to the connection of the A-IoT device Whether the A-IoT device is connected to a BS or an Int. UE

[0292] The carrier wave used for backscattering and / or the RF signal for energy supply may be excluded from the DL channel / signal in each option of Proposal 2. That is, if the DL signal is a CW for backscattering or an RF signal for energy supply, the A-IoT device may receive the DL signal independently of other DL channels / signals and UL channels / signals.

[0293] In addition, when an A-IoT device receives a DL channel / signal in a time interval between time #n and time #m, the A-IoT device may be able to receive a maximum of X DL channels / signals (X is an integer greater than or equal to 1, for example, X=1) in that time interval. In Proposal 3, DL channel / signal #X1 starts or ends at time #n, and DL channel / signal #Y1 triggered / scheduled by DL channel / signal #1 starts or ends at time #m. In this case, X may be defined by a specification, may be preset, or may be indicated by the BS / Int. UE. For example, X may be defined by a specification, may be preset, or may be indicated by the BS / Int. UE depending on at least one of the type of the A-IoT device and the capability of the A-IoT device.

[0294] In addition, when an A-IoT device transmits UL channels / signals in the time interval between time #n and time #m, the A-IoT device may be capable of transmitting a maximum of Y UL channels / signals (Y is an integer equal to or greater than 1, for example, Y=1) in that time interval. In this case, Y may be defined by a specification, may be set in advance, or may be indicated by the BS / Int. UE. For example, X may be defined by a specification, may be set in advance, or may be indicated by the BS / Int. UE depending on at least one of the type of the A-IoT device and the capability of the A-IoT device.

[0295] In addition, if the A-IoT device receives another DL channel / signal or a DL channel / signal that triggers / schedules a UL channel / signal in the time interval between time #n and time #m, the A-IoT device may apply one of the following three alternations regarding reception of DL channel / signal #Y1, which is scheduled to start or end at time #m: Alt. 1: The A-IoT device is able to receive DL channel / signal #Y1. Alt. 2: The A-IoT device cancels or drops reception of DL channel / signal #Y1. Alt. 3: The A-IoT device suspends or postpones reception of DL channel / signal #Y1 for a specific time interval.

[0296] In Proposal 3 described above, for example, an A-IoT device performs a first operation of receiving a first signal (e.g., DL channel / signal #X1) from a wireless communication device (e.g., BS / Int.UE) connected to the A-IoT device, and a second operation of receiving a third signal (e.g., DL channel / signal #Y1) from the wireless communication device, triggered or scheduled by the first signal, and decides between the first and second operations whether to receive a fourth signal (e.g., DL channel / signal #X2) and / or transmit a fifth signal (e.g., UL channel / signal).

[0297] According to the above-described proposal 3, the operation in the time interval between the reception of the DL channel / signal #X1 and the reception of the DL channel / signal #1 triggered / scheduled by the DL channel / signal #X1 is appropriately set, so that the A-IoT device can communicate with other wireless communication devices on an appropriate timeline. For example, according to proposal 3, the operation in the time interval is appropriately set, so that the A-IoT device can communicate with other wireless communication devices appropriately depending on whether the reception operation or the transmission operation is possible in the time interval.

[0298] The above-described proposals 2 and 3 may be used in combination or may be used selectively.

[0299] For example, each option in proposal 3 may be associated with one of the options in proposal 2. Based on the correspondence, an indication of an option in proposal 2 may implicitly indicate an option in proposal 3. For example, if each option in proposal 2 is associated one-to-one with each option in proposal 3, an indication of option 3 in proposal 2 may implicitly indicate option 3 in proposal 3.

[0300] <Variations> The operation of A-IoT devices in each of the above-mentioned options of Proposal 2 and 3 is subject to at least one of the following restrictions: a minimum gap between two consecutive DL channels / signals, two consecutive UL channels / signals, and a minimum gap between one DL channel / signal and one UL channel / signal. Note that two consecutive DL channels / signals means that there is no other channel / signal between one DL channel / signal and the next DL channel / signal. Each of the above-mentioned options of Proposal 2 and 3 may be applied with the following restrictions:

[0301] If an A-IoT device receives DL channel / signal #1 starting or ending at time #n, the A-IoT device will not receive DL channel / signal #2 starting or ending less than X time units after time #n, and will not receive DL channel / signal #0 starting or ending less than Y time units before time #n. Also, in this case, the A-IoT device will not receive any DL channel / signal that triggers / schedules DL channel / signal #2 or DL ​​channel / signal #0.

[0302] If an A-IoT device transmits UL channel / signal #1 that starts or ends at time #n, the A-IoT device will not transmit UL channel / signal #2 that starts or ends less than Y time units after time #n, and will not transmit UL channel / signal #0 that starts or ends less than X time units before time #n. Also, in this case, the A-IoT device will not receive a DL channel / signal that schedules UL channel / signal #2 or UL channel / signal #0.

[0303] As shown in Proposal 1, if an A-IoT device transmits UL channel / signal #1 that starts or ends at time #n, the A-IoT device will not receive DL channel / signal #2 that starts or ends less than X time units after time #n, and will not receive DL channel / signal #0 that starts or ends less than Y time units before time #n (see Case 1 in Figure 25). Also, in this case, the A-IoT device will not receive any DL channel / signal that schedules DL channel / signal #2 or DL ​​channel / signal #0.

[0304] As shown in Proposal 1, when an A-IoT device receives DL channel / signal #1 that starts or ends at time #n, the A-IoT device shall not transmit UL channel / signal #2 that starts or ends less than Y time units after time #n, and shall not transmit UL channel / signal #0 that starts or ends less than X time units before time #n (see Case 2 in Figure 25). Also, in this case, the A-IoT device shall not receive any DL channel / signal that schedules UL channel / signal #2 or UL channel / signal #0.

[0305] Note that X and Y here may be defined by the specifications or may be instructed by the BS / Int. UE. X and Y may be determined according to the type of A-IoT device and / or the capability of the A-IoT device.

[0306] In the above-mentioned proposals, timelines of DL channels / signals and UL channels / signals are shown, but the timelines may be subject to restrictions according to frequency resources.

[0307] Let us consider a case where an A-IoT device receives a DL channel / signal #1 from a BS / Int. UE that starts or ends at time #n, and the DL channel / signal #1 triggers or schedules the transmission of a corresponding UL channel / signal #1 that starts or ends at time #m. In this case, during the time interval from time #n to time #m, the A-IoT device may perform at least one of the following options α-1 and α-2:

[0308] <Option α-1> If DL channel / signal #2 triggers / schedules UL channel / signal #2 of the same band / carrier / frequency resource as UL channel / signal #1, the A-IoT device does not receive the DL channel / signal #2. In this case, the A-IoT device does not transmit UL channel / signal #2 triggered / scheduled by DL channel / signal #2.

[0309] In option α-1, the A-IoT device receives DL channel / signal #2 if the DL channel / signal #2 triggers / schedules UL channel / signal #2 of a band / carrier / frequency resource different from that of UL channel / signal #1. In this case, the A-IoT device also transmits UL channel / signal #2 that is triggered / scheduled by DL channel / signal #2.

[0310] <Option α-2> The A-IoT device receives DL channel / signal #2 if DL channel / signal #2 triggers / schedules UL channel / signal #2 of the same band / carrier / frequency resource as UL channel / signal #1. In this case, the A-IoT device also transmits UL channel / signal #2 triggered / scheduled by DL channel / signal #2.

[0311] In option α-2, the A-IoT device does not receive DL channel / signal #2 if the DL channel / signal #2 triggers / schedules UL channel / signal #2 of a band / carrier / frequency resource different from that of UL channel / signal #1. In this case, the A-IoT device does not transmit UL channel / signal #2 triggered / scheduled by DL channel / signal #2.

[0312] Let us consider a case where an A-IoT device receives a DL channel / signal #X1 from a BS / Int. UE that starts or ends at time #n, and the DL channel / signal #X1 triggers / schedules the reception of a corresponding DL channel / signal #Y1 that starts or ends at time #m. In this case, during the time interval from time #n to time #m, the A-IoT device may perform at least one of the following options β-1 and β-2.

[0313] <Option β-1> In option β-1, if DL channel / signal #X2 triggers / schedules DL channel / signal #Y2 of the same band / carrier / frequency resource as DL channel / signal #Y1, the A-IoT device does not receive DL channel / signal #X2. In this case, the A-IoT device also does not receive DL channel / signal #Y2 triggered / scheduled by DL channel / signal #X2.

[0314] In option β-1, the A-IoT device receives DL channel / signal #X2 if DL channel / signal #X2 triggers / schedules DL channel / signal #Y2 of a band / carrier / frequency resource different from that of DL channel / signal #Y1. In this case, the A-IoT device receives DL channel / signal #Y2 triggered / scheduled by DL channel / signal #X2.

[0315] <Option β-2> In option β-2, the A-IoT device receives DL channel / signal #X2 if DL channel / signal #X2 triggers / schedules DL channel / signal #Y2 of the same band / carrier / frequency resource as DL channel / signal #Y1. In this case, the A-IoT device also receives DL channel / signal #Y2 triggered / scheduled by DL channel / signal #X2.

[0316] In option β-2, the A-IoT device does not receive DL channel / signal #X2 if DL channel / signal #X2 triggers / schedules DL channel / signal #Y2 of a band / carrier / frequency resource different from that of DL channel / signal #Y1. In this case, the A-IoT device also does not receive DL channel / signal triggered / scheduled by DL channel / signal #X2.

[0317] As described above, by imposing restrictions on the timelines of DL channels / signals and UL channels / signals according to the frequency resources, appropriate transmission and reception operations can be performed for each of the DL channels / signals and UL channels / signals according to the band / carrier / frequency resources.

[0318] 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 this 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 this embodiment.

[0319] <Configuration of Base Station> Fig. 42 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 the device 20 (see Fig. 43) by radio. The base station 10 may be an intermediate node, a support node, an Int. UE, or a terminal (a terminal of an SL that communicates with the device 20).

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

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

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

[0323] The reference signal 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.

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

[0325] 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 102. For example, the control unit 103 performs operations other than the transmission and reception described in the above embodiment (note that these operations may be performed by the reception unit 102 and / or the transmission unit 101).

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

[0327] 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 signals (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.

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

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

[0330] For example, a communication unit of the base station 10 (an example of a wireless communication device) performs either a first operation of transmitting a first signal (e.g., DL channel / signal) to a device 20 connected to the base station 10, or a second operation of receiving a second signal (e.g., UL channel / signal) from the device 20. The control unit 103 sets a specific time interval before and / or after one of the operations, and does not cause the communication unit to perform the other of the first operation and the second operation within the specific time interval.

[0331] For example, the communication unit of the base station 10 (an example of a wireless communication device) performs a first operation of transmitting a first signal (e.g., DL channel / signal) to a device 20 connected to the base station 10, and a second operation of receiving a second signal (e.g., UL channel / signal) from the device 20 or transmitting a third signal (e.g., DL channel / signal) to the device 20, triggered or scheduled by the first signal. Then, the control unit 103 determines whether to cause the communication unit to transmit a fourth signal (e.g., DL channel / signal) and / or receive a fifth signal (e.g., DL channel / signal) between the first operation and the second operation.

[0332] <Device Configuration> Fig. 43 is a block diagram showing an example of the configuration of the device 20 according to the 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, the base station 10 wirelessly. The device 20 may be, for example, an A-IoT UE or an A-IoT device.

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

[0334] The transmitting unit 202 transmits the UL signal to the base station 10. For example, the transmitting unit 202 transmits the UL signal under the control of the control unit 203.

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

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

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

[0338] The control unit 203 controls communication operations of the device 20, including reception processing in the receiving unit 201 and transmission processing in the transmitting unit 202. For example, the control unit 203 performs operations other than the transmission and reception described in the above embodiment (note that these operations may be performed by the receiving unit 201 and / or the transmitting unit 202).

[0339] For example, the control unit 203 acquires information such as data and control information from the upper 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 upper layer.

[0340] 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, Channel State Information (CSI), or 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.

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

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

[0343] Here, the receiving unit 201 and the transmitting unit 202 (which may be collectively referred to as a communication unit) communicate with a network such as the base station 10 .

[0344] For example, the communication unit of the device 20 performs either a first operation of receiving a first signal (e.g., DL channel / signal) from a base station 10 (an example of a wireless communication device) connected to the device 20, or a second operation of transmitting a second signal (e.g., UL channel / signal) to the base station 10. The control unit 203 sets a specific time interval before and / or after one of the operations, and does not cause the communication unit to perform the other of the first operation and the second operation within the specific time interval.

[0345] For example, the communication unit of the device 20 performs a first operation of receiving a first signal (e.g., DL channel / signal) from a base station 10 (an example of a wireless communication device) connected to the device 20, and a second operation of transmitting a second signal (e.g., UL channel / signal) to the base station 10 or receiving a third signal (e.g., DL channel / signal) from the base station 10, triggered or scheduled by the first signal. Then, the control unit 203 determines whether to cause the communication unit to receive a fourth signal (e.g., DL channel / signal) and / or transmit a fifth signal (e.g., DL channel / signal) between the first operation and the second operation.

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

[0347] <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 at least one of hardware and 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 directly or indirectly connected (e.g., using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or the multiple devices.

[0348] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, 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.

[0349] 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. Figure 44 is a diagram showing an example of the hardware configuration of a base station and a device according to an 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.

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

[0351] Each function in the base station 10 and the device 20 is realized by loading specified software (programs) onto hardware such as the processor 1001 and 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 storage 1003.

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

[0353] The processor 1001 also 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 the programs. 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 used 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 also be transmitted from a network via a telecommunications line.

[0354] The memory 1002 is a computer-readable recording medium and may be configured by, for example, 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.

[0355] 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 (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) 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.

[0356] 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, a communication module, etc. 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.

[0357] The input device 1005 is an input device (e.g., 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 (e.g., 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 (e.g., a touch panel).

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

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

[0360] <Notification of Information, Signaling> Notification of information is not limited to the embodiments described in the present disclosure and may be performed using other methods. For example, 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, 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.

[0361] <Applicable Systems> The embodiments described in the present disclosure are applicable to LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 (WiMAX (registered trademark The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).

[0362] <Processing Procedures, etc.> The processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be rearranged unless inconsistent. 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.

[0363] <Operation of Base Station> In the present disclosure, specific operations described as being performed by a base station may also 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, an MME or an S-GW, etc., but are not limited to these). 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.

[0364] <Direction of Input / Output> Information, etc. (see <Information, Signal>) 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.

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

[0366] <Determination 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 comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0367] <Variations of Aspects, etc.> Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched depending on the implementation. In addition, 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).

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

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

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

[0371] 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., which 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.

[0372] Note that terms described 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.

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

[0374] <Parameter and Channel Names> Furthermore, the information, parameters, and the like described in the present disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or other corresponding information. For example, a radio resource may be indicated by an index.

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

[0376] <Base Station> In the present 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. A base station may also be referred to by terms such as a macrocell, a small cell, a femtocell, and a picocell.

[0377] 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 partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a remote radio head (RRH)). The terms "cell" or "sector" refer to part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

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

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

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

[0381] <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 an autonomous mobile object operating 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.

[0382] Furthermore, the 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.

[0383] Similarly, the term "terminal" in the present disclosure may be interpreted as a base station, in which case the base station 10 may be configured to have the functions of the device 20 described above.

[0384] Fig. 45 shows a configuration example of a vehicle 2001. As shown in Fig. 45, 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.

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

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

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

[0388] 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 types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 2012 provides various types of multimedia information and multimedia services to the occupants of the vehicle 2001 by using information acquired from external devices via the communication module 2013, etc.

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

[0390] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

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

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

[0393] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021 to 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 to 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.

[0394] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from an external device 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)).

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

[0396] <Meaning and Interpretation of Terms> 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 a table, database, or other data structure), ascertaining something that is considered to be a "judging" or "determining," 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 that are considered to be a "judging" or "determining." 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.

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

[0398] <Reference Signal> A reference signal can also be abbreviated as RS (Reference Signal), and may also be called a pilot depending on the applicable standard.

[0399] <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."

[0400] "First," "Second" Any reference to an element using designations such as "first," "second," etc., used in this disclosure 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 precede the second element in some way.

[0401] <Means> The "means" in the configuration of each device above may be replaced with "section," "circuit," "device," etc.

[0402] Open Format: When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0403] <Time Units such as TTI, Frequency Units such as RB, and 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 called 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 is independent of numerology.

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

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

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

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

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

[0409] 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. Note that the definition of TTI is not limited to this.

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

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

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

[0413] 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 greater than or equal to 1 ms.

[0414] A resource block (RB) is a resource allocation unit in the time domain and the 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 be determined based on numerology.

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

[0416] 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, etc.

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

[0418] 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 BWP and numbered within the BWP.

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

[0420] 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."

[0421] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples, and various changes may be made to 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.

[0422] <Maximum Transmit Power> The "maximum transmit power" in the present disclosure may refer to the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0423] Articles 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 plural.

[0424] <"Different"> In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." Note that 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."

[0425] One aspect of the present disclosure is useful in wireless communication systems.

[0426] 10 Base station 20 Device 101, 202 Transmitter 102, 201 Receiver 103, 203 Controller

Claims

1. A device comprising: a communication unit that performs a first operation of receiving a first signal from a wireless communication device connected to the device; and a second operation that is triggered or scheduled by the first signal and that transmits a second signal to the wireless communication device or receives a third signal from the wireless communication device; and a control unit that determines whether to cause the communication unit to receive a fourth signal and / or transmit a fifth signal between the first operation and the second operation.

2. The device according to claim 1, wherein the fourth signal is a signal having a specific relationship with the first signal.

3. The device of claim 1, wherein the fourth signal is a signal that triggers or schedules the transmission or reception of a sixth signal.

4. The device according to claim 1, wherein the control unit determines whether to cause the communication unit to receive the fourth signal and / or transmit the fifth signal based on at least one of an instruction from the wireless communication device, the type of the device, the capabilities of the device, the type of the wireless communication device, and whether or not there is a difference between the frequency of the first operation and the frequency of the second operation.

5. A wireless communication device comprising: a communication unit that performs a first operation of transmitting a first signal to a device connected to the wireless communication device; and a second operation that is triggered or scheduled by the first signal and receives a second signal from the device or transmits a third signal to the device; and a control unit that determines whether to cause the communication unit to transmit a fourth signal and / or receive a fifth signal between the first operation and the second operation.

6. A wireless communication method in which a device performs a first operation of receiving a first signal from a wireless communication device connected to the device, and a second operation of transmitting a second signal to the wireless communication device or receiving a third signal from the wireless communication device, triggered or scheduled by the first signal, and determining whether to cause the device to receive a fourth signal and / or transmit a fifth signal between the first operation and the second operation.

Images