Device, wireless communication device, and wireless communication method

Abstract

A terminal according to the present invention comprises: a reception unit that receives a first signal; and a control unit that controls transmission of a second signal corresponding to the first signal and transmission of a third signal different from the second signal.

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 known as "5G"), the successor system to LTE (Long Term Evolution), technologies that satisfy requirements such as a large-capacity system, high-speed data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, and low power consumption are being considered (for example, Non-Patent Document 1).

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

[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.7.0 (2021-09)" New SID: Study on solutions for Ambient IoT (Internet of Things) in NR ", RP-234058, 3GPP TSG RAN Meeting #102, December 2023

[0005] In ambient IoT, an ambient IoT device and its communication partner transmit signals for ambient IoT to each other, but there has been insufficient consideration of the transmission of these signals, and further consideration is required.

[0006] One aspect of the present disclosure is to provide a device, a wireless communication apparatus, and a wireless communication method that can appropriately transmit signals for ambient IoT.

[0007] A device according to one aspect of the present disclosure includes a receiving unit that receives a first signal, and a control unit that controls the transmission of a second signal corresponding to the first signal and the transmission of a third signal different from the second signal.

[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 candidate topologies for CW, R2D, and D2R transmission. FIG. 7 is a diagram illustrating candidate topologies for CW, R2D, and D2R transmission. FIG. 8 is a diagram illustrating candidate topologies for CW, R2D, and D2R transmission. FIG. 9 is a diagram illustrating candidate topologies for CW, R2D, and D2R transmission. FIG. 10 is a diagram illustrating a candidate topology for CW, R2D, and D2R transmission. FIG. 11 is a diagram illustrating a time interval between an R2D and a corresponding D2R. FIG. 12 is a diagram illustrating Examples 1 and 2 of Option 0 of Proposal 1. FIG. 13 is a diagram illustrating Examples 3 and 4 of Option 0 of Proposal 1. FIG. 14 is a diagram illustrating Examples 1 and 2 of Option 1 of Proposal 1. FIG. 15 is a diagram illustrating Examples 3 and 4 of Option 1 of Proposal 1. FIG. 16 is a diagram illustrating Examples 1 and 2 of Option 2 of Proposal 1. FIG. 1 is a diagram showing a first example of option 3 of proposal 1. FIG. 2 is a diagram showing a second example of option 3 of proposal 1. FIG. 3 is a diagram showing an example of option 4 of proposal 1. FIG. 4 is a block diagram showing an example of the configuration of a base station according to an embodiment. FIG. 5 is a block diagram showing an example of the configuration of a device according to an embodiment. FIG. 6 is a diagram showing an example of the hardware configuration of a base station and a device according to the embodiment. FIG. 7 is a diagram showing an example of the configuration of a vehicle.

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

[0011] Furthermore, in the embodiments of the present disclosure described below, terms used in existing LTE, such as SS (synchronization signal), PSS (primary SS), SSS (secondary SS), PBCH (physical broadcast channel), PRACH (physical random access channel), PDCCH (physical downlink control channel), PDSCH (physical downlink shared channel), PUCCH (physical uplink control channel), and PUSCH (physical uplink shared channel), are used. This is for convenience of description, and similar signals, functions, etc. may be referred to by other names. Furthermore, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily designated as "NR-".

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

[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 an intermediate node, an assisting node, and / or a terminal (UE) (see <Device Types and Topologies> below). Note that, hereinafter, "and / or" may be simply written as " / ".

[0019] The device 20 is a communication device equipped with a wireless communication function, and may be an ambient IoT device (e.g., a sensor, etc.) as described above. Hereinafter, the ambient IoT device will also be referred to as an A-IoT UE 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, or the like 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] For Ambient IoT, for example, the following deployment scenarios and characteristics can be considered for the 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, etc. 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 the device

[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 that of RFID (Radio frequency identification).

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

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

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

[0031] Fig. 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 an 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] Figure 6 illustrates Topology 4. Topology 4 is a configuration in which a UE and an ambient IoT device communicate with each other. The ambient IoT device communicates with the UE bidirectionally. The communication related to Topology 4 may be considered as sidelink (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 in 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. Furthermore, the A-IoT device may be used interchangeably with the A-IoT UE or the A-IoT terminal. The 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 field 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, the intermediate node, the support node, and other nodes by switching the reflection coefficient of the antenna of the ambient IoT device, and transmits information to the base station, the intermediate node, the support node, and other nodes. The RF signals may also be referred to as carrier waves.

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

[0042] <Rel-19 SID> In the Rel-19 SID, necessary and feasible solutions for A-IoT were considered (Section 4.1 of Non-Patent Document 5). The considered solutions include, for example, determining which functions, procedures, etc. are necessary and which functions, procedures, etc. are not.

[0043] Additionally, several issues for A-IoT DL and UL will be discussed under the leadership of RAN 1. Issues to be discussed include: - Frame structure, synchronization and timing, and random access - Numerology, bandwidth, and multiple access - Waveform and modulation - Channel coding - DL channel / signal aspects - UL channel / signal aspects A-IoT has been approved as a topic for Rel. 19. In the discussion of A-IoT, the following 1. traffic flow, 2. device assumptions, and 3. topology can be considered.

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

[0045] 1a. DT (device terminated) Traffic includes transmission to the A-IoT UE (DL), but not transmission from the A-IoT UE (UL). 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, which includes instructions such as commands or instructions to the A-IoT UE.

[0046] 1b. 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, transmitting information corresponds to transmitting a signal containing information or transmitting a signal. In this disclosure, transmitting to a certain device X corresponds to transmitting a signal (or information) to device X. In addition, transmitting from a certain device X and transmitting by a certain device X correspond to device X transmitting a signal (or information). In addition, receiving from a certain device X corresponds to receiving a signal (or information) transmitted by device X. In addition, receiving by a certain device X corresponds to device X receiving a signal (or information).

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

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

[0050] 2b. 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, this 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 an intermediate node. Note that the base station in Topology 1 may correspond to a microcell.

[0055] 3b. Topology 2 In Topology 2, communication is performed between the base station and the A-IoT UE via an intermediate node. The A-IoT UE performs bidirectional communication with the intermediate node located between the base station and the A-IoT UE. Note that the base station in Topology 2 may correspond to a macrocell. The case of Topology 2 may also be applied to indoor cases.

[0056] For A-IoT UEs, the signal design is common to Topology 1 and Topology 2. Hereinafter, the intermediate node may be referred to as int. UE (intermediate UE). The intermediate node may also be referred to as a base station, a communication device, a network device, or a network node.

[0057] <R2D and D2R> At the RAN1#116 meeting, it was agreed to consider the physical channels for R2D data transmission and D2R data transmission.

[0058] R2D stands for "reader to device." D2R stands for "device to reader." "Reader" corresponds to a base station or intermediate node. "Device" corresponds to A-IoT.

[0059] R2D may be considered as DL in an A-IoT wireless communication system. R2D data transmission may be performed on a physical channel such as the physical reader to device channel (PRDCH). R2D control transmission may be performed on the same physical channel as R2D data transmission or on a different physical channel from R2D data transmission.

[0060] D2R can be considered as the UL in an A-IoT wireless communication system. D2R data transmission can be performed on a physical channel such as a physical device to reader channel (PDRCH). D2R control transmission can be performed on the same physical channel as D2R data transmission or on a physical channel separate from D2R.

[0061] R2D, R2D transmission, R2D signal, DL, and DL signal may be used interchangeably. D2R, D2R transmission, R2D signal, UL, and UL signal may be used interchangeably. R2D control transmission may be referred to as R2D control information or control information. D2R control transmission may be referred to as D2R control information or control information.

[0062] Carrier Wave Transmission For carrier wave (CW), R2D, and D2R transmission, the following candidate topologies can be envisaged:

[0063] 1a. D1T1-A1 Figure 8 illustrates candidate topologies for CW, R2D, and D2R transmission. In the D1T1-A1 topology, R2D and CW are transmitted by BS#1, and backscattered D2R is received by another BS#2.

[0064] 1b. D1T1-A2 Figure 9 illustrates a candidate topology for CW, R2D, and D2R transmissions. In the D1T1-A2 topology, R2D and CW are transmitted by BS#1, and backscattered D2R is received by the same BS#1.

[0065] 1c. D1T1-B Figure 10 illustrates candidate topologies for CW, R2D, and D2R transmission. In the D1T1-B topology, R2D is transmitted by BS#1, backscattered D2R is received by the same BS#1, and CW is transmitted by a CW node. Here, the CW node may be a BS other than BS#1, a UE, an IAB node, a repeater node such as an NCR (Network-Controlled Repeater), a relay node, or any other type of node.

[0066] 2a. D2T2-A1 Figure 11 illustrates a candidate topology for CW, R2D, and D2R transmissions. In the D2T2-A1 topology, R2D and CW are transmitted by UE#1, and backscattered D2R is received by another UE#2.

[0067] 2b. D2T2-A2 Figure 12 illustrates a candidate topology for CW, R2D, and D2R transmissions. In the D2T2-A2 topology, R2D and CW are transmitted by UE#1, and backscattered D2R is received by the same UE#1.

[0068] 2c. D2T2-B Figure 13 illustrates candidate topologies for CW, R2D, and D2R transmissions. In the D2T2-B topology, R2D is transmitted by UE#1, backscattered D2R is received by the same UE#1, and CW is transmitted by a CW node. Here, the CW node may be a UE other than UE#1, a BS, an IAB node, a repeater node such as an NCR, a relay node, or other types of nodes.

[0069] <Time interval between R2D and corresponding D2R> The following agreement was made regarding the time interval between an R2D and its corresponding D2R.

[0070] To study the processing time aspect of A-IoT, we use the following term: R2D_min " is used. ・T R2D_min : The minimum time between an R2D transmission and a subsequent corresponding D2R transmission

[0071] For the time interval between an R2D transmission and a subsequent corresponding D2R transmission, the following options 1 and 2 are investigated:

[0072] ・Option 1 A-IoT is [T R2D_min , T R2D_max ], the maximum time between an R2D transmission and a corresponding subsequent D2R transmission, T R2D_max " is defined.

[0073] For example, the double-headed arrow A14a in FIG. 14 corresponds to the above-mentioned "T R2D_min As shown by the double-headed arrow A14b in FIG. R2D_max " is defined as "A-IoT" R2D_min , T R2D_max For example, the A-IoT transmits a D2R within the range (timing window) shown in the dotted frame A14c in FIG.

[0074] Further research is needed to determine whether the maximum time is common or different for each A-IoT, and whether the maximum time differs by traffic type / command type (e.g., DT or DO-DTT) and / or by use case (e.g., inventory or command).

[0075] Option 2: R2D transmission followed by the corresponding D2R transmission timing "T R2D_D2R ” is determined based on the control information of the R2D transmission, where T R2D_D2R ≧T R2D_min is.

[0076] <Items under consideration> In A-IoT, ACK / NACK feedback is being considered as one of the candidates for L1 (layer 1) D2R control information. Other L1 D2R control information being considered includes CSI (channel state information) feedback and autonomous SR (scheduling request).

[0077] It has been agreed that R2D data and L1 R2D control information are transmitted on the PRDCH, where R2D data may replace any of the data, higher layer payload, and system information.

[0078] However, in A-IoT, there is room for consideration regarding the transmission formats of D2R transmission and R2D transmission (e.g., the format of PDRCH and the format of PRDCH).

[0079] For example, it may be considered whether multiple D2R transmissions (e.g., D2R transmissions corresponding to multiple R2D transmissions) are transmitted on a single PDRCH, where an R2D transmission may be replaced by an R2D reception from the perspective of an A-IoT device, and an R2D transmission may correspond to a signal transmitted on an R2D link.

[0080] Illustratively, it may be considered whether ACK / NACK feedback for multiple R2D transmissions is transmitted in one PDRCH as multiple D2R transmissions.

[0081] If the D2R transmissions (e.g., ACK / NACK feedback, etc.) included in the PDRCH are not properly defined, PDRCH resources may be wasted.

[0082] In addition, there is room for consideration regarding the size of the information blocks transmitted by the PRDCH and the PDRCH. For example, if the maximum TBS (transport block size) of the PRDCH is large, a very long interval in the time direction is dominated by one transmission of the PRDCH. Also, if the maximum TBS of the PDRCH is large, a very long interval in the time direction is dominated by one transmission of the PDRCH.

[0083] Therefore, in this embodiment, proposal 1 describes the transmission format (e.g., the configuration of the PDRCH) of multiple D2R transmissions (e.g., D2R transmissions corresponding to multiple R2D transmissions), and proposal 2 describes the size of the information blocks transmitted by the PRDCH and PDRCH.

[0084] As mentioned above, "R2D" means a link from a reader to a device, and "D2R" means a link from a device to a reader. The reader corresponds to a BS or an intermediate UE, and the device corresponds to an A-IoT device.

[0085] In this embodiment, D2R transmission may be replaced by a signal transmitted in a D2R link, by an A-IoT device transmitting a signal in the D2R link, or by a reader receiving a signal in the D2R link. Furthermore, D2R transmission may be replaced by a PDRCH transmission. Furthermore, R2D transmission may be replaced by a signal transmitted in an R2D link, by an A-IoT device receiving a signal in the R2D link, or by a reader transmitting a signal in the R2D link. Furthermore, R2D transmission may be replaced by a PRDCH transmission.

[0086] R2D reception may correspond to the device receiving a signal / channel / information transmitted by a reader. Alternatively, R2D reception may correspond to a signal / channel / information transmitted by a reader and received by a device. Note that the reader transmitting a signal / channel / information to a device, or the transmitted signal / channel / information, may be referred to as "R2D transmission."

[0087] D2R transmission may correspond to a device transmitting a signal / channel / information to a reader. Alternatively, D2R transmission may correspond to a signal / channel / information transmitted by a device and received by a reader. Note that a reader receiving a signal / channel / information from a device, or the received signal / channel / information, may be referred to as "D2R reception."

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

[0089] <Proposal 1> In the following proposal 1, the transmission of ACK / NACK feedback corresponding to the R2D transmission is taken as an example of a D2R transmission corresponding to the R2D transmission. For example, the ACK / NACK feedback corresponding to the R2D transmission indicates whether the R2D transmission has been successfully received. However, the D2R transmission corresponding to the R2D transmission is not limited to the transmission of ACK / NACK feedback corresponding to the R2D transmission. For example, the D2R transmission corresponding to the R2D transmission may be the transmission of D2R data corresponding to the R2D transmission, or the transmission of D2R control information (e.g., L1 D2R control information) corresponding to the R2D transmission.

[0090] Instructions / configurations (e.g., scheduling, resource configuration, etc.) regarding D2R transmissions corresponding to R2D transmissions may be performed by the corresponding R2D transmissions or by other information (e.g., configuration by a higher layer). When an A-IoT device attempts to perform D2R transmission, resources (e.g., time resources and / or frequency resources) for the D2R transmissions are instructed / configured, and the A-IoT device performs the D2R transmission (e.g., PDRCH transmission) in the instructed / configured resources. Note that the time resources may be specified by a time window.

[0091] Proposal 1 describes four options for D2R transmission. Option 0 and Option 1, described below, are options in which scheduling restrictions are assumed. Option 2 and Option 3 involve handling of overlapping D2R transmissions by the A-IoT device. Option 2 and Option 3 involve device behavior defined for overlapping cases. Option 4 involves the A-IoT device attempting to avoid overlaps in resource determination operations. For example, Option 4 may attempt to avoid overlaps in resource determination operations, similar to slotted ALOHA.

[0092] <Option 0 of Proposal 1> In Option 0 of Proposal 1, the A-IoT device does not assume that multiple overlapping ACK / NACK feedbacks will occur. Specifically, when the A-IoT device receives a single R2D transmission (e.g., a first R2D transmission) and intends to transmit ACK / NACK feedback corresponding to the R2D transmission (first R2D transmission), the A-IoT device does not assume that it will receive another R2D transmission (e.g., a second R2D transmission) before transmitting the ACK / NACK feedback. In other words, when the A-IoT device receives a single R2D transmission and intends to transmit ACK / NACK feedback corresponding to the R2D transmission, the A-IoT device assumes that it will receive another R2D transmission after transmitting the ACK / NACK feedback. In this case, the leader (e.g., BS or intermediate UE) does not expect to transmit a second R2D transmission after making a first R2D transmission before receiving ACK / NACK feedback corresponding to the first R2D transmission from the A-IoT device.

[0093] Alternatively, in Option 0 of Proposal 1, when an A-IoT device receives a single R2D transmission and intends to transmit ACK / NACK feedback corresponding to that R2D transmission, the A-IoT device does not expect to receive another R2D transmission for which the A-IoT device intends to transmit corresponding ACK / NACK feedback before transmitting that ACK / NACK feedback. In this case, before transmitting its ACK / NACK feedback, the A-IoT device may expect to receive another R2D transmission for which the A-IoT device may not transmit corresponding ACK / NACK feedback. In other words, when an A-IoT device receives a single R2D transmission and intends to transmit ACK / NACK feedback corresponding to the R2D transmission, it is assumed that after the A-IoT device transmits the ACK / NACK feedback, the A-IoT device will receive another R2D transmission for which the A-IoT device intends to transmit corresponding ACK / NACK feedback. Note that the R2D transmission for which the A-IoT device intends to transmit corresponding ACK / NACK feedback corresponds to an R2D transmission for which the A-IoT device is requested to transmit ACK / NACK feedback. In this case, the leader (e.g., BS or intermediate UE) does not assume that the A-IoT device will transmit another R2D transmission for which the A-IoT device intends to transmit corresponding ACK / NACK feedback before receiving the ACK / NACK feedback from the A-IoT device.

[0094] In the case where the PDRCH carrying the ACK / NACK feedback is transmitted within a time window after the corresponding R2D transmission, the A-IoT device does not expect to receive another R2D transmission before the A-IoT device transmits the ACK / NACK feedback. For example, in this case, the A-IoT device does not expect to receive another R2D transmission before the time window in which the A-IoT device transmits the ACK / NACK feedback. In this case, the A-IoT device and / or the reader considers the time window of the ACK / NACK feedback or the time window of the PDRCH. Note that the length of the time window is determined by a parameter Tmin (e.g., "T" in FIG. 14) indicating the time interval between an R2D transmission and a subsequent corresponding D2R transmission. R2D_min ") and Tmax (for example, "T" in FIG. R2D_max "). Note that in this case, the A-IoT device may expect to receive another R2D transmission after the time window in which the A-IoT device sends the ACK / NACK feedback. Alternatively, in this case, the A-IoT device may expect to receive another R2D transmission within the time window after the A-IoT device sends the ACK / NACK feedback.

[0095] FIG. 15 illustrates Examples 1 and 2 of Option 0 of Proposal 1. FIG. 16 illustrates Examples 3 and 4 of Option 0 of Proposal 1. In the four examples illustrated in FIGS. 15 and 16, the horizontal axis represents the time axis. Examples 1 and 3 illustrate R2D transmissions and PDRCHs including ACK / NACK feedback corresponding to the R2D transmissions. For example, in Example 1 of FIG. 15, the PDRCH including ACK / NACK feedback corresponding to R2D#1 is illustrated as PDRCH#1. Examples 2 and 4 illustrate R2D transmissions and the time window of the PDRCH including ACK / NACK feedback corresponding to the R2D transmissions. For example, in Example 2 of FIG. 15, the time window of the PDRCH including ACK / NACK feedback corresponding to R2D#1 is illustrated as the time window of PDRCH#1.

[0096] 15, R2D#2, which is another R2D transmission from R2D#1, is not received by the A-IoT device before PDRCH#1 including ACK / NACK feedback corresponding to R2D#1 is transmitted. In the case of Example 1, PDRCH#1 including ACK / NACK feedback corresponding to R2D#1 does not overlap with PDRCH#2 including ACK / NACK feedback corresponding to R2D#2.

[0097] In Example 2 of Figure 15, R2D#2, which is another R2D transmission from R2D#1, is not received by the A-IoT device before the time window in which PDRCH#1 including ACK / NACK feedback corresponding to R2D#1 is transmitted. Then, R2D#2 is received by the A-IoT device after the time window in which PDRCH#1 including ACK / NACK feedback corresponding to R2D#1 is transmitted. In the case of Example 2, the time window of PDRCH#1 including ACK / NACK feedback corresponding to R2D#1 does not overlap with the time window of PDRCH#2 including ACK / NACK feedback corresponding to R2D#2.

[0098] In Example 3 of Figure 16, R2D#2, which is an R2D transmission separate from R2D#1, is transmitted before PDRCH#1 including ACK / NACK feedback corresponding to R2D#1 is transmitted. In Option 0 of Proposal 1, the case of Example 3 corresponds to an error case. The A-IoT device does not assume a case in which R2D#2 is transmitted before PDRCH#1 is transmitted, as in the case of Example 3. For example, the network or the reader may instruct the A-IoT device on resources (e.g., timing, etc.) so as not to transmit R2D#2 before PDRCH#1 is transmitted, or may control the resources (e.g., timing, etc.) for transmitting R2D#2.

[0099] In Example 4 of Figure 16, R2D#2, which is an R2D transmission separate from R2D#1, is transmitted before the time window of PDRCH#1 including ACK / NACK feedback corresponding to R2D#1. In Option 0 of Proposal 1, the case of Example 4 corresponds to an error case. The A-IoT device does not assume a case in which R2D#2 is transmitted before the time window of PDRCH#1, as in the case of Example 4. For example, the network or the reader may instruct the A-IoT device on resources (e.g., timing, etc.) so as not to transmit R2D#2 before the time window of PDRCH#1, or may control the resources (e.g., timing, etc.) for transmitting R2D#2.

[0100] As described above, Option 0 of Proposal 1 allows an A-IoT device to, after receiving an R2D transmission, transmit ACK / NACK feedback corresponding to a previously received R2D transmission without receiving another R2D transmission, thereby simplifying processing (e.g., transmission processing, reception processing, scheduling) in the A-IoT device and / or reader.

[0101] Note that in Option 0 of Proposal 1 described above, when an A-IoT device receives a single R2D transmission and intends to transmit ACK / NACK feedback corresponding to the R2D transmission, the A-IoT device may not expect to receive two or more other R2D transmissions before transmitting the ACK / NACK feedback. Also, in Option 0 of Proposal 1, the R2D transmission may be R2D data. Also, in Option 0 of Proposal 1, when an A-IoT device receives a single R2D transmission and intends to transmit a D2R transmission corresponding to the R2D transmission, the A-IoT device may not expect to receive one or more other R2D transmissions before transmitting the D2R transmission.

[0102] <Option 1 of Proposal 1> In Option 1 of Proposal 1, the A-IoT device does not assume that multiple ACK / NACK feedbacks will overlap. Specifically, the A-IoT device does not assume that a PDRCH carrying ACK / NACK feedback corresponding to a single R2D transmission will overlap in the time direction with another PDRCH carrying ACK / NACK feedback corresponding to another R2D transmission. In Option 1 of Proposal 1, the A-IoT device may assume that a PDRCH carrying ACK / NACK feedback corresponding to a single R2D transmission will not overlap in the time direction with another PDRCH carrying ACK / NACK feedback corresponding to another R2D transmission.

[0103] In the case where the PDRCH carrying the ACK / NACK feedback is transmitted within a time window after the corresponding R2D transmission, the A-IoT device does not assume that the time windows of the two PDRCHs carrying the ACK / NACK corresponding to the two R2D transmissions overlap. In this case, the A-IoT device and / or reader considers the time window of the ACK / NACK feedback. Note that the length of the time window is determined by the parameter Tmin (e.g., "T" in FIG. 14) indicating the time interval between the R2D transmission and the subsequent corresponding D2R transmission. R2D_min ") and Tmax (for example, "T" in FIG. R2D_max "). Note that in this case, the A-IoT device may assume that the time windows of the two PDRCHs carrying ACK / NACK corresponding to the two R2D transmissions do not overlap.

[0104] It should be noted that in Option 1 of Proposal 1, when an A-IoT device receives a single R2D transmission and the A-IoT device attempts to send ACK / NACK feedback corresponding to that R2D transmission, it may be assumed that the A-IoT device receives another R2D transmission before sending that ACK / NACK feedback.

[0105] FIG. 17 illustrates Examples 1 and 2 of Option 1 of Proposal 1. FIG. 18 illustrates Examples 3 and 4 of Option 1 of Proposal 1. In the four examples illustrated in FIGS. 17 and 18, the horizontal axis represents the time axis. Examples 1 and 3 illustrate R2D transmissions and PDRCHs including ACK / NACK feedback corresponding to the R2D transmissions. For example, in Example 1 of FIG. 17, the PDRCH including ACK / NACK feedback corresponding to R2D#1 is indicated as PDRCH#1. Examples 2 and 4 illustrate R2D transmissions and time windows of PDRCHs including ACK / NACK feedback corresponding to the R2D transmissions. For example, in Example 2 of FIG. 17, the time window of the PDRCH including ACK / NACK feedback corresponding to R2D#1 is indicated as the time window of PDRCH#1.

[0106] In Example 1 of Figure 17, before PDRCH #1 including ACK / NACK feedback corresponding to R2D #1 is transmitted, R2D #2, which is an R2D transmission separate from R2D #1, is received by the A-IoT device. Also, in Example 1 of Figure 17, PDRCH #1 does not overlap with PDRCH #2 including ACK / NACK feedback corresponding to R2D #2. When PDRCH #1 does not overlap with PDRCH #2, as in the case of Example 1, the A-IoT device may transmit PDRCH #1 including ACK / NACK feedback corresponding to R2D #1 and transmit PDRCH #2 including ACK / NACK feedback corresponding to R2D #2.

[0107] In Example 2 of Figure 17, R2D #2, an R2D transmission separate from R2D #1, is received by the A-IoT device before the time window of PDRCH #1 including ACK / NACK feedback corresponding to R2D #1. Also, in Example 2 of Figure 17, the time window of PDRCH #1 does not overlap with the time window of PDRCH #2 including ACK / NACK feedback corresponding to R2D #2. When the time window of PDRCH #1 does not overlap with the time window of PDRCH #2, as in the case of Example 2, the A-IoT device may transmit PDRCH #1 including ACK / NACK feedback corresponding to R2D #1 within the corresponding time window and transmit PDRCH #2 including ACK / NACK feedback corresponding to R2D #2 within the corresponding time window.

[0108] In Example 3 of FIG. 18 , before PDRCH #1 including ACK / NACK feedback corresponding to R2D #1 is transmitted, R2D #2, which is an R2D transmission separate from R2D #1, is received by the A-IoT device. Then, in Example 3 of FIG. 18 , PDRCH #1 overlaps with PDRCH #2 including ACK / NACK feedback corresponding to R2D #2. In Option 1 of Proposal 1, the case of Example 3 corresponds to an error case. The A-IoT device does not assume a case in which PDRCH #1 overlaps with PDRCH #2, as in Example 3. For example, the network or reader may instruct the A-IoT device on resources (e.g., timing, etc.) for the PDRCH so that PDRCH #1 does not overlap with PDRCH #2.

[0109] In Example 4 of FIG. 18 , R2D#2, an R2D transmission separate from R2D#1, is received by the A-IoT device before the time window of PDRCH#1 containing ACK / NACK feedback corresponding to R2D#1. Then, in Example 4 of FIG. 18 , the time window of PDRCH#1 overlaps with the time window of PDRCH#2 containing ACK / NACK feedback corresponding to R2D#2. In Option 1 of Proposal 1, the case of Example 4 corresponds to an error case. The A-IoT device does not assume a case in which the time window of PDRCH#1 overlaps with the time window of PDRCH#2, as in the case of Example 4. For example, the network or reader may instruct the A-IoT device on resources (e.g., time windows, etc.) for the PDRCH so that the time window corresponding to PDRCH#1 does not overlap with the time window corresponding to PDRCH#2.

[0110] As described above, in Option 1 of Proposal 1, the A-IoT device does not assume that a PDRCH carrying ACK / NACK feedback corresponding to a single R2D transmission overlaps in time with another PDRCH carrying ACK / NACK feedback corresponding to another R2D transmission, thereby avoiding collisions of multiple PDRCHs and wasting resources.

[0111] Note that, in the above-described Option 1 of Proposal 1, overlapping of PDRCHs that transmit ACK / NACK feedback corresponding to each of two R2D transmissions (i.e., overlapping of two PDRCHs) has been given as an example, but the present disclosure is not limited thereto. For example, Option 1 of Proposal 1 may also be applied to overlapping of PDRCHs that transmit ACK / NACK feedback corresponding to each of three or more R2D transmissions (i.e., overlapping of three or more PDRCHs). For example, in Option 1 of Proposal 1, the A-IoT device does not assume that PDRCHs that transmit ACK / NACK feedback corresponding to three or more R2D transmissions overlap with each other.

[0112] Note that, in the above-described Option 1 of Proposal 1, an overlap of PDRCHs carrying ACK / NACK feedback corresponding to two R2D transmissions is taken as an example, but the present disclosure is not limited to this.

[0113] For example, Option 1 of Proposal 1 may be applied to overlap between PDRCHs carrying D2R data and PDRCHs carrying ACK / NACK feedback corresponding to R2D transmissions. For example, A-IoT devices do not expect overlap between PDRCHs carrying D2R data and PDRCHs carrying ACK / NACK feedback corresponding to R2D transmissions.

[0114] Also, for example, Option 1 of Proposal 1 may be applied to a case where PDRCHs carrying two D2R data items overlap with each other. For example, the A-IoT device does not assume that the PDRCH carrying the first D2R data item and the PDRCH carrying the second D2R data item overlap with each other.

[0115] Also, for example, Option 1 of Proposal 1 may be applied to cases where PDRCHs transmitting D2R data and PDRCHs transmitting ACK / NACK are mixed and three or more PDRCHs overlap.

[0116] <Option 2 of Proposal 1> In Option 2 of Proposal 1, the A-IoT device performs priority control when multiple ACK / NACK feedbacks overlap. Specifically, when a PDRCH carrying ACK / NACK feedback corresponding to a single R2D transmission overlaps in the time direction with another PDRCH carrying ACK / NACK feedback corresponding to another R2D transmission, the A-IoT device transmits only the PDRCH with ACK / NACK feedback for the single R2D transmission and does not transmit ACK / NACK feedback for the other R2D transmission.

[0117] In addition, when a PDRCH transmitting ACK / NACK feedback corresponding to a single R2D transmission overlaps in the time direction with another PDRCH transmitting ACK / NACK feedback corresponding to another R2D transmission, in a case where the A-IoT device transmits only a PDRCH having ACK / NACK feedback for the single R2D transmission, the A-IoT device transmits ACK / NACK feedback for one of the two R2D transmissions. Which R2D transmission is the target R2D transmission for transmitting ACK / NACK feedback may be determined based on rules defined in the specification and / or the system. Furthermore, for example, it may be determined based on the rules shown below.

[0118] Rule 1: For example, which R2D transmission is to be the target R2D transmission for transmitting ACK / NACK feedback may be determined based on the timing of the R2D transmission. For example, of two R2D transmissions, at least one of the R2D transmission that starts transmission earlier, the R2D transmission that ends transmission earlier, the R2D transmission that starts transmission later, and the R2D transmission that ends transmission later may be determined as the R2D transmission for transmitting ACK / NACK feedback.

[0119] Rule 2: For example, the R2D transmission for which ACK / NACK feedback is to be sent may be determined based on the payload / content / format / command type of the R2D transmission.

[0120] Rule 3: For example, the R2D transmission for which ACK / NACK feedback is to be transmitted may be determined based on an instruction from the leader.

[0121] Note that Option 2 of Proposal 1 includes a case where the PDRCH carrying ACK / NACK feedback is transmitted within a time window after the corresponding R2D transmission. In this case, the A-IoT device and / or reader considers the time window for ACK / NACK feedback. And, in this case of Option 2, the time windows of two PDRCHs carrying ACK / NACK corresponding to two R2D transmissions overlap. Note that the length of the time window is determined by a parameter Tmin (e.g., "T" in FIG. 14) indicating the time interval between an R2D transmission and a subsequent corresponding D2R transmission. R2D_min ") and Tmax (for example, "T" in FIG. R2D_max "). Note that in this case, the A-IoT device may assume that the time windows of two PDRCHs transmitting ACK / NACK corresponding to two R2D transmissions overlap. Then, when the time windows of two PDRCHs transmitting ACK / NACK corresponding to two R2D transmissions overlap, the A-IoT device transmits a PDRCH with ACK / NACK feedback for a single R2D transmission in that PDRCH time window, and does not transmit ACK / NACK feedback for another R2D transmission.

[0122] In addition, in Option 2 of Proposal 1, the A-IoT device may assume that a PDRCH carrying ACK / NACK feedback corresponding to a single R2D transmission overlaps in time with another PDRCH carrying ACK / NACK feedback corresponding to another R2D transmission.

[0123] Figure 19 shows examples 1 and 2 of option 2 of proposal 1. In the two examples shown in Figure 19, the horizontal axis represents the time axis. Example 1 of Figure 19 shows R2D transmission and a PDRCH including ACK / NACK feedback corresponding to the R2D transmission. For example, in Example 1 of Figure 19, the PDRCH including ACK / NACK feedback corresponding to R2D#1 is denoted as PDRCH#1. Example 2 of Figure 19 shows R2D transmission and a time window of the PDRCH including ACK / NACK feedback corresponding to the R2D transmission. For example, in Example 2 of Figure 19, the time window of the PDRCH including ACK / NACK feedback corresponding to R2D#1 is denoted as PDRCH#1.

[0124] In Example 1 of Figure 19, PDRCH #1 including ACK / NACK feedback corresponding to R2D #1 overlaps with PDRCH #2 including ACK / NACK feedback corresponding to R2D #2. When PDRCH #1 overlaps with PDRCH #2, as in the case of Example 1, the A-IoT device transmits only a PDRCH having ACK / NACK feedback for a single R2D transmission and does not transmit ACK / NACK feedback for another R2D transmission. ACK / NACK feedback that is not transmitted is dropped. In Example 1 of Figure 19, PDRCH #1 having ACK / NACK feedback for R2D #1 is transmitted, and ACK / NACK feedback for R2D #2 is not transmitted. In this example, ACK / NACK feedback for R2D #2 is dropped. In addition, example 1 of Figure 19 corresponds to an example in which, of two R2D transmissions, R2D #1, which corresponds to the R2D transmission that starts transmission earlier or the R2D transmission that ends transmission earlier, is determined to be the R2D transmission that transmits ACK / NACK feedback.

[0125] In addition, when the R2D transmission that starts later or the R2D transmission that ends later of two R2D transmissions is determined as the R2D transmission that transmits ACK / NACK feedback, in the case of example 1 in Fig. 19 , R2D#2 is determined as the R2D transmission that transmits ACK / NACK feedback. In this case, PDRCH#2 having ACK / NACK feedback of R2D#2 is transmitted, and ACK / NACK feedback of R2D#1 is not transmitted.

[0126] In Example 2 of Figure 19, the time window of PDRCH #1 including ACK / NACK feedback corresponding to R2D #1 overlaps with the time window of PDRCH #2 including ACK / NACK feedback corresponding to R2D #2. When the time window of PDRCH #1 overlaps with the time window of PDRCH #2, as in the case of Example 2, the A-IoT device transmits a PDRCH including ACK / NACK feedback corresponding to one of the two overlapping time windows. In Example 2 of Figure 19, in the time window of PDRCH #1 including ACK / NACK feedback for R2D #1, the A-IoT device transmits PDRCH #1 while not transmitting ACK / NACK feedback for R2D #2. The ACK / NACK feedback that is not transmitted is dropped.

[0127] As described above, in Option 2 of Proposal 1, when a PDRCH transmitting ACK / NACK feedback corresponding to a single R2D transmission overlaps in the time direction with another PDRCH transmitting ACK / NACK feedback corresponding to another R2D transmission, the A-IoT device transmits only the PDRCH having ACK / NACK feedback for the single R2D transmission, and does not transmit ACK / NACK feedback for the other R2D transmission. This allows PDRCHs to be transmitted without collision even when PDRCHs (or PDRCH time windows) overlap. This makes it possible to avoid collisions between multiple PDRCHs and avoid wasting resources.

[0128] Note that, in the above-described Option 2 of Proposal 1, an overlap of PDRCHs transmitting ACK / NACK feedback corresponding to each of two R2D transmissions (i.e., overlap of two PDRCHs) has been given as an example, but the present disclosure is not limited thereto. For example, Option 2 of Proposal 1 may be applied to an overlap of PDRCHs transmitting ACK / NACK feedback corresponding to each of three or more R2D transmissions (i.e., overlap of three or more PDRCHs). For example, when PDRCHs transmitting ACK / NACK feedback corresponding to three R2D transmissions overlap with each other, the A-IoT device may transmit only one of the PDRCHs transmitting ACK / NACK feedback corresponding to the three R2D transmissions, and may not transmit ACK / NACK feedback corresponding to the remaining two R2D transmissions. Note that in this case, the method of determining one of the R2D transmissions may be based on the above-described Rules 1 to 3, etc.

[0129] Note that, in the above-described Option 2 of Proposal 1, overlapping of PDRCHs carrying ACK / NACK feedback corresponding to two R2D transmissions is taken as an example, but the present disclosure is not limited to this.

[0130] For example, Option 2 of Proposal 1 may be applied to an overlap between a PDRCH transmitting D2R data and a PDRCH transmitting ACK / NACK feedback corresponding to an R2D transmission. For example, when a PDRCH transmitting D2R data and a PDRCH transmitting ACK / NACK feedback corresponding to an R2D transmission overlap, the A-IoT device may transmit only one of the PDRCH transmitting D2R data and the PDRCH transmitting ACK / NACK feedback corresponding to the R2D transmission, and not the other. In this case, the method for determining one of the R2D transmissions may be based on Rules 1 to 3 described above.

[0131] Also, for example, Option 2 of Proposal 1 may be applied to cases where PDRCHs transmitting two D2R data overlap each other. For example, when a PDRCH transmitting first D2R data and a PDRCH transmitting second D2R data overlap, the A-IoT device transmits a PDRCH transmitting only one of the first D2R data and the second D2R data, and does not need to transmit the other D2R data. In this case, the method for determining which R2D data to transmit may be based on the above-mentioned Rules 1 to 3.

[0132] Also, for example, option 2 of proposal 1 may be applied to cases where PDRCHs transmitting D2R data and PDRCHs transmitting ACK / NACK are mixed and three or more PDRCHs overlap.

[0133] <Option 3 of Proposal 1> In Option 3 of Proposal 1, when multiple ACK / NACK feedbacks overlap, the A-IoT device transmits the information collectively. Specifically, when a PDRCH transmitting ACK / NACK feedback corresponding to a single R2D transmission overlaps in the time direction with another PDRCH transmitting ACK / NACK feedback corresponding to another R2D transmission, the A-IoT device transmits a PDRCH having ACK / NACK feedback for the two R2D transmissions in a single PDRCH. That is, multiple ACK / NACK feedback information is transmitted collectively in a single PDRCH. Note that multiple ACK / NACK feedback information may be converted into a single piece of information (e.g., bundling), or may be maintained as separate pieces of information.

[0134] Note that Option 3 of Proposal 1 includes a case where the PDRCH carrying ACK / NACK feedback is transmitted within a time window after the corresponding R2D transmission. In this case, the A-IoT device and / or reader considers the time window for ACK / NACK feedback. And, in this case of Option 3, the time windows of two PDRCHs carrying ACK / NACK corresponding to two R2D transmissions overlap. Note that the length of the time window is determined by a parameter Tmin (e.g., "T" in FIG. 14) indicating the time interval between an R2D transmission and a subsequent corresponding D2R transmission. R2D_min ") and Tmax (for example, "T" in FIG. R2D_max "). Note that in this case, the A-IoT device may assume that the time windows of the two PDRCHs transmitting ACK / NACKs corresponding to the two R2D transmissions overlap. Then, when the time windows of the two PDRCHs transmitting ACK / NACKs corresponding to the two R2D transmissions overlap, the A-IoT device transmits a PDRCH with ACK / NACK feedback for each of the two R2D transmissions in the PDRCH time window.

[0135] In addition, in a situation where a PDRCH transmitting ACK / NACK feedback corresponding to a single R2D transmission overlaps in the time direction with another PDRCH transmitting ACK / NACK feedback corresponding to another R2D transmission, there are two PDRCHs transmitting ACK / NACK feedback. In Option 3 of Proposal 1, the A-IoT device transmits ACK / NACK feedback for the two R2D transmissions on one of the two PDRCHs. Which PDRCH transmits the ACK / NACK feedback may be determined based on rules defined in the specification and / or the system. Furthermore, for example, it may be determined based on the following rules.

[0136] Rule 1: For example, which PDRCH is to transmit ACK / NACK feedback may be determined based on the timing of the PDRCH. For example, at least one of the PDRCH that starts transmitting ACK / NACK feedback latest among the multiple PDRCHs and the PDRCH that ends transmission latest may be determined as the PDRCH that transmits the ACK / NACK feedback.

[0137] Rule 2: For example, which PDRCH transmits ACK / NACK feedback may be determined based on the timing of R2D transmission. For example, when ACK / NACK feedback corresponding to each of a plurality of R2D transmissions is transmitted on the PDRCH, at least one of the PDRCHs with the latest start of transmission and the latest end of transmission among the plurality of R2D transmissions may be determined as the PDRCH with which ACK / NACK feedback is transmitted.

[0138] Rule 3: For example, the PDRCH to transmit ACK / NACK feedback may be determined based on an instruction from the leader.

[0139] Rule 4: For example, the PDRCH on which ACK / NACK feedback is transmitted may be determined based on the payload / content / format / command type of the R2D transmission.

[0140] In addition, in Option 3 of Proposal 1, the A-IoT device may assume that a PDRCH carrying ACK / NACK feedback corresponding to a single R2D transmission overlaps in time with another PDRCH carrying ACK / NACK feedback corresponding to another R2D transmission.

[0141] Figure 20 is a diagram showing a first example of Option 3 of Proposal 1. In the example shown in Figure 20, the horizontal axis represents the time axis. Figure 20 shows R2D transmission and a PDRCH including ACK / NACK feedback corresponding to the R2D transmission. For example, in Figure 20, the PDRCH including ACK / NACK feedback corresponding to R2D#1 is shown as PDRCH#1. In Option 3 of Proposal 1, when overlapping occurs as in Case 1, ACK / NACK feedback is provided in the format shown in Case 2.

[0142] In Case 1 of Figure 20, PDRCH #1 including ACK / NACK feedback corresponding to R2D #1 overlaps with PDRCH #2 including ACK / NACK feedback corresponding to R2D #2. When PDRCH #1 overlaps with PDRCH #2 as in Case 1, the A-IoT device transmits a PDRCH (PDRCH #2 in Case 2 of Figure 20) having ACK / NACK feedback for the two R2D transmissions in a single PDRCH as in Case 2. Case 2 of Figure 20 corresponds to an example in which, of the two PDRCHs, PDRCH #2, which is the PDRCH whose transmission starts latest or whose transmission ends latest, is determined as the PDRCH from which ACK / NACK feedback is transmitted.

[0143] Figure 21 is a diagram showing a second example of Option 3 of Proposal 1. In the example shown in Figure 21, the horizontal axis represents the time axis. Figure 21 shows R2D transmissions and PDRCH time windows including ACK / NACK feedback corresponding to the R2D transmissions. For example, in Figure 21, the PDRCH time window including ACK / NACK feedback corresponding to R2D#1 is shown as the time window of PDRCH#1. In Option 3 of Proposal 1, when overlapping occurs as in Case 1, ACK / NACK feedback is provided in the format shown in Case 2.

[0144] In Case 1 of Figure 21, the time window of PDRCH #1 including ACK / NACK feedback corresponding to R2D #1 overlaps with the time window of PDRCH #2 including ACK / NACK feedback corresponding to R2D #2. When the time window of PDRCH #1 overlaps with the time window of PDRCH #2 as in Case 1, the A-IoT device transmits a PDRCH including ACK / NACK feedback for the two R2D transmissions in a single PDRCH time window (the time window of PDRCH #2 in Case 2 of Figure 21) as in Case 2. Case 2 of Figure 21 exemplarily corresponds to an example in which, of the two PDRCH time windows, the PDRCH with the latest start of transmission or the PDRCH with the latest end of transmission is determined as the PDRCH time window in which ACK / NACK feedback is transmitted.

[0145] As described above, in Option 3 of Proposal 1, when a PDRCH transmitting ACK / NACK feedback corresponding to a single R2D transmission overlaps in the time direction with another PDRCH transmitting ACK / NACK feedback corresponding to another R2D transmission, the A-IoT device transmits a PDRCH having ACK / NACK feedback for the two R2D transmissions in a single PDRCH. This allows PDRCHs to be transmitted without collision even when PDRCHs (or PDRCH time windows) overlap. This makes it possible to avoid collisions between multiple PDRCHs and avoid wasting resources.

[0146] Note that, in the above-described Option 3 of Proposal 1, an overlap of PDRCHs that transmit ACK / NACK feedback corresponding to each of two R2D transmissions (i.e., an overlap of two PDRCHs) has been given as an example, but the present disclosure is not limited thereto. For example, Option 3 of Proposal 1 may be applied to an overlap of PDRCHs that transmit ACK / NACK feedback corresponding to each of three or more R2D transmissions (i.e., an overlap of three or more PDRCHs). For example, when PDRCHs that transmit ACK / NACK feedback corresponding to three R2D transmissions overlap each other, the A-IoT device may transmit PDRCHs including ACK / NACK feedback corresponding to the three R2D transmissions.

[0147] Note that, although the above-described Option 3 of Proposal 1 takes the example of overlapping PDRCHs that carry ACK / NACK feedback corresponding to two R2D transmissions, the present disclosure is not limited to this.

[0148] For example, Option 3 of Proposal 1 may be applied to overlap between a PDRCH carrying D2R data and a PDRCH carrying ACK / NACK feedback corresponding to an R2D transmission. For example, when a PDRCH carrying D2R data overlaps with a PDRCH carrying ACK / NACK feedback corresponding to an R2D transmission, the A-IoT device may transmit a PDRCH including the D2R data and the ACK / NACK feedback corresponding to the R2D transmission.

[0149] Also, for example, Option 3 of Proposal 1 may be applied to the case where PDRCHs carrying two D2R data items overlap with each other. For example, when a PDRCH carrying first D2R data and a PDRCH carrying second D2R data overlap, the A-IoT device may transmit a PDRCH including the first D2R data and the second D2R data.

[0150] Also, for example, option 3 of Proposal 1 may be applied to cases where PDRCHs transmitting D2R data and PDRCHs transmitting ACK / NACK are mixed and three or more PDRCHs overlap.

[0151] <Option 4 of Proposal 1> In Option 4 of Proposal 1, the A-IoT device determines resources so that multiple ACK / NACK feedback transmissions do not overlap when these transmissions occur. Specifically, in a case where a PDRCH carrying ACK / NACK feedback is transmitted within a time window after a corresponding R2D transmission and the time windows of two PDRCHs carrying ACK / NACKs corresponding to the two R2D transmissions overlap, the A-IoT device transmits two PDRCHs carrying ACK / NACKs corresponding to the two R2D transmissions, respectively. In this case, the A-IoT device and / or reader considers the time window of the ACK / NACK feedback. Note that the length of the time window is determined by a parameter Tmin (e.g., "T" in FIG. 14) indicating the time interval between an R2D transmission and a subsequent corresponding D2R transmission. R2D_min ") and Tmax (for example, "T" in FIG. R2D_max ").

[0152] Note that restrictions may be imposed on Option 4 of Proposal 1. As an example of restrictions, if two R2D transmissions are R2D#1 and R2D#2 and R2D#1 starts or ends transmission earlier than R2D#2, the A-IoT device may transmit PDRCH#1 corresponding to R2D#1 earlier than PDRCH#2 corresponding to R2D#2. Alternatively, if R2D#1 starts or ends transmission earlier than R2D#2, the A-IoT device may transmit PDRCH#2 corresponding to R2D#2 earlier than PDRCH#1 corresponding to R2D#1.

[0153] As another example of the restriction, two D2R resources (e.g., PDRCH) may be determined / selected so that the time domain resources do not overlap with each other. Note that when two D2R resources are determined / selected so that they do not overlap, the time domain resources may be continuous or discontinuous in the time direction. In other words, even if the time windows overlap, the resources (e.g., PDRCH) used for actual transmission are determined / selected so that they do not overlap with each other.

[0154] Figure 22 is a diagram showing an example of Option 4 of Proposal 1. In the example shown in Figure 22, the horizontal axis represents the time axis. In the example shown in Figure 22, R2D transmissions and time windows of PDRCHs including ACK / NACK feedback corresponding to the R2D transmissions are shown. For example, in Figure 22, the time window of PDRCHs including ACK / NACK feedback corresponding to R2D#1 is shown as the time window of PDRCH#1.

[0155] In Figure 22, the time window of PDRCH #1 including ACK / NACK feedback corresponding to R2D #1 overlaps with the time window of PDRCH #2 including ACK / NACK feedback corresponding to R2D #2. When the time window of PDRCH #1 overlaps with the time window of PDRCH #2, as in the case of Figure 22, the A-IoT device transmits a PDRCH including ACK / NACK feedback corresponding to each time window in each of the two overlapping time windows. Note that the PDRCHs transmitted in this case do not overlap. The A-IoT device may determine / select resources so that the PDRCHs transmitted do not overlap.

[0156] As described above, in Option 4 of Proposal 1, in a case where the time windows of two PDRCHs transmitting ACK / NACKs corresponding to two R2D transmissions overlap, the A-IoT device transmits two PDRCHs transmitting ACK / NACKs corresponding to the two R2D transmissions, respectively. This allows the PDRCHs to be transmitted without collision even when the PDRCH time windows overlap. This makes it possible to avoid collisions between multiple PDRCHs and avoid wasting resources.

[0157] Note that, in the above-described Option 4 of Proposal 1, the overlap of PDRCH time windows transmitting ACK / NACK feedback corresponding to each of two R2D transmissions (i.e., the overlap of two PDRCH time windows) has been given as an example, but the present disclosure is not limited thereto. For example, Option 4 of Proposal 1 may be applied to the overlap of PDRCH time windows transmitting ACK / NACK feedback corresponding to each of three or more R2D transmissions (i.e., the overlap of three or more PDRCH time windows). For example, when the PDRCH time windows transmitting ACK / NACK feedback corresponding to three R2D transmissions overlap each other, the A-IoT device may transmit PDRCHs including ACK / NACK feedback corresponding to the three R2D transmissions, respectively.

[0158] Note that, in the above-mentioned Option 4 of Proposal 1, the overlap of the PDRCH time windows that transmit ACK / NACK feedback corresponding to each of the two R2D transmissions is given as an example, but the present disclosure is not limited to this.

[0159] For example, Option 4 of Proposal 1 may be applied to the overlap of the time window of the PDRCH carrying D2R data and the time window of the PDRCH carrying ACK / NACK feedback corresponding to the R2D transmission. For example, if the time window of the PDRCH carrying D2R data and the time window of the PDRCH carrying ACK / NACK feedback corresponding to the R2D transmission overlap, the A-IoT device may transmit the PDRCH carrying the D2R data and the PDRCH carrying ACK / NACK feedback corresponding to the R2D transmission, respectively.

[0160] Also, for example, Option 4 of Proposal 1 may be applied to a case where the time windows of the PDRCHs transmitting two D2R data items overlap each other. For example, when the time window of the PDRCH transmitting the first D2R data item overlaps with the time window of the PDRCH transmitting the second D2R data item, the A-IoT device may transmit the PDRCH for the first D2R data item and the PDRCH for the second D2R data item, respectively.

[0161] Also, for example, Option 4 of Proposal 1 may be applied to cases where the time windows of the PDRCHs transmitting D2R data and the time windows of the PDRCHs transmitting ACK / NACKs are mixed and three or more PDRCH time windows overlap.

[0162] As described above, in Proposal 1, an A-IoT device receives a first R2D transmission and controls a first D2R transmission corresponding to the first R2D transmission (e.g., a PDRCH for ACK / NACK feedback corresponding to the first R2D transmission) and a second D2R transmission different from the first D2R transmission. For example, according to Option 0, the A-IoT device does not expect to receive another R2D transmission (e.g., a second R2D transmission) between the first R2D transmission and the first D2R transmission. Furthermore, according to Option 1, the A-IoT device does not expect the first D2R transmission and the second D2R transmission to overlap. Furthermore, according to Option 2, when the first D2R transmission and the second D2R transmission overlap, the A-IoT device transmits one of the transmissions but not the other. According to option 3, the A-IoT device transmits a D2R transmission that includes both the first and second D2R transmissions when the first and second D2R transmissions overlap. According to option 4, the A-IoT device transmits each of the first and second D2R transmissions when the first and second D2R transmissions overlap.

[0163] Here, control of transmission includes control of the timing of transmission, control of the setting of resources used for transmission, determination of whether transmission is possible, determination of the order of transmission, and the like.

[0164] In Proposal 1 above, "overlap" corresponds to at least one of the following three:

[0165] Partially overlapping in the time domain. Note that when the PDRCHs are partially overlapping, the D2R transmission may be performed only in the overlapping parts, only in the non-overlapping parts, or both in the overlapping and non-overlapping parts.

[0166] - Full overlap in the time domain Note that when the PDRCHs overlap completely, this may include a case where the PDRCHs are the same size and completely overlap each other, and a case where the PDRCHs are different sizes and therefore overlapping and non-overlapping portions are mixed. When overlapping and non-overlapping portions are mixed, D2R transmission may be performed only on the overlapping portions, or may be performed only on the non-overlapping portions, or may be performed on both the overlapping and non-overlapping portions. Note that when overlapping and non-overlapping portions are mixed because the PDRCHs are different sizes, this may correspond to the case of partial overlap described above.

[0167] - Non-overlapping in the time domain, but transmitted or scheduled within the same time unit, where the size of the time unit may be, for example, at least one of X symbols, X slots, and X chips (X is a real number greater than or equal to 0), or a time window of x milliseconds (x is a real number greater than or equal to 0).

[0168] Although the above description has been given as an example of a PDRCH that transmits ACK / NACK feedback corresponding to R2D transmission, the above-described options may be applied to other PDRCH / D2R transmissions. For example, at least one of the above-described options may be applied to the relationship between D2R data transmission and ACK / NACK corresponding to R2D data. Furthermore, for example, at least one of the above-described options may be applied to the relationship between D2R data transmission and D2R data transmission.

[0169] Although the above-described options have been described using an example of two overlapping PDRCHs, the present disclosure is not limited thereto, and each of the above-described options may be applied to three or more overlapping PDRCHs.

[0170] Furthermore, which of the above options is applied may be defined by the specification, may be defined by the system, may be set by a method such as upper layer signaling, may be indicated by a method such as PHY layer signaling, or may be determined based on the type of device / message.

[0171] In addition, which of the above-mentioned options is applied may be determined based on whether or not two PDRCHs are transmitted to the same reader. For example, when two PDRCHs are transmitted to the same reader, a method of transmitting one PDRCH including two ACK / NACK feedbacks addressed to the same reader, as in option 3, is applied. Alternatively, when two PDRCHs are transmitted to the same reader, a method of transmitting one PDRCH of two ACK / NACK feedbacks addressed to different readers and not transmitting the other, as in option 2, is applied. Furthermore, when two PDRCHs are not transmitted to the same reader, for example, any of option 0, option 1, and option 4 is applied.

[0172] In addition, which of the above-mentioned options is applied may be determined based on whether two PRDCHs associated with two PDRCHs are associated with the same leader. Here, the leader associated with a PRDCH may be the leader that transmitted the PRDCH. If two PRDCHs associated with two PDRCHs are associated with the same leader, option 2 or option 3 is applied. If two PRDCHs associated with two PDRCHs are not associated with the same leader, any of option 0, option 1, and option 4 is applied.

[0173] The above-described options may be combined as appropriate. For example, if four overlapping PDRCHs exist, any three of the four may be selected as D2R transmissions to be transmitted based on option 2, and one PDRCH including the selected three may be transmitted based on option 3.

[0174] In addition, information indicating whether or not at least one or each of the above-mentioned options is supported may be reported from the A-IoT device to the network (e.g., a reader) as capability information.

[0175] <Proposal 2> Proposal 2 describes code block segmentation performed in PRDCH transmission and PDRCH transmission. In code block segmentation, specific information (data, control information) is segmented into multiple code blocks. The specific information may be referred to as a TB (transport block). In this segmentation, the size of the code block and the number of code blocks to be segmented are specified. Note that "code block" may be replaced with "segment." Furthermore, "code block segmentation" may be replaced with "data segmentation" or "TB segmentation."

[0176] First, the code block segmentation performed in PRDCH transmission will be described.

[0177] The number of bits in one code block may be defined in the specification, may be defined in the system, may be instructed to the A-IoT device, or may be instructed to the intermediate UE.

[0178] The number of code blocks may be defined in the specification, may be defined in the system, may be instructed to the A-IoT device, or may be instructed to the intermediate UE.

[0179] The number of bits in one code block may be calculated based on the number of code blocks and the total number of bits of information to be segmented.

[0180] The number of code blocks and the number of bits in each code block may be determined based on a transport block size (TBS). The rules for this determination may be defined in the specifications. For example, the maximum size per segment is X (X is a real number equal to or greater than 0). If the TBS is greater than X, the TB is segmented into N segments (N is a real number equal to or greater than 0). N is the smallest value that satisfies the condition that the size of each segment is equal to or less than X.

[0181] As signal processing for each code block transmitted on the PRDCH, the reader adds a cyclic redundancy check (CRC). The A-IoT device may generate ACK / NACK feedback corresponding to the PRDCH.

[0182] A CRC may be generated based on and appended to each code block, or a CRC may be jointly generated for multiple code blocks.

[0183] An ACK / NACK feedback corresponding to R2D is generated for each code block. Alternatively, an ACK / NACK feedback corresponding to R2D is generated for each code block group. When an ACK / NACK feedback is generated for each code block group, the number of code blocks in one group may be defined in a specification, may be defined in a system, may be instructed to the A-IoT device, or may be instructed to the intermediate UE.

[0184] In the PRDCH transmission, the PRDCH may be retransmitted. The A-IoT device may be instructed which code blocks of the PRDCH are to be retransmitted. The A-IoT device may be instructed which code block groups of the PRDCH are to be retransmitted. The intermediate UE may be instructed which code blocks of the PRDCH are to be retransmitted. The intermediate UE may be instructed which code block groups of the PRDCH are to be retransmitted. The instruction in this case may be performed by the network (e.g., BS).

[0185] Next, the code block segmentation performed in the PDRCH transmission will be described.

[0186] The number of bits in one code block may be defined in the specification, may be defined in the system, may be instructed to the A-IoT device, or may be instructed to the intermediate UE.

[0187] The number of code blocks may be defined in the specification, may be defined in the system, may be instructed to the A-IoT device, or may be instructed to the intermediate UE.

[0188] The number of bits in one code block may be calculated based on the number of code blocks and the total number of bits of information to be segmented.

[0189] The number of code blocks and the number of bits in each code block may be determined based on the TBS. Note that the rules for this determination may be defined in the specifications. For example, the specifications define a maximum size X per segment (X is a real number equal to or greater than 0). If the TBS is greater than X, the TB is segmented into N segments (N is a real number equal to or greater than 0). Note that N is the smallest value that satisfies the condition that the size of each segment is equal to or less than X.

[0190] As signal processing for each code block transmitted via the PDRCH, the A-IoT device adds a CRC and performs FEC.

[0191] A CRC may be generated based on and appended to each code block, or a CRC may be jointly generated for multiple code blocks.

[0192] FEC is performed on each code block, or FEC may be performed jointly on multiple code blocks.

[0193] In the PDRCH transmission, the PDRCH may be retransmitted. The A-IoT device may be instructed which code blocks of the PDRCH are to be retransmitted. The A-IoT device may be instructed which code block groups of the PDRCH are to be retransmitted. The intermediate UE may be instructed which code blocks of the PDRCH are to be retransmitted. The intermediate UE may be instructed which code block groups of the PDRCH are to be retransmitted. The instruction in this case may be performed by the network (e.g., BS).

[0194] As described above, according to Proposal 2, by segmenting PRDCH transmissions into code blocks, it is possible to prevent a very long interval in the time direction from being dominated by a single PRDCH transmission. Also, according to Proposal 2, by segmenting PDRCH transmissions into code blocks, it is possible to prevent a very long interval in the time direction from being dominated by a single PDRCH transmission.

[0195] It should be noted that Proposal 2 may be a proposal that supports hybrid automatic repeat request (HARQ) / ARQ operation.

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

[0197] In the present disclosure, A / B may mean at least one of A and B. In the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0198] In the present disclosure, higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof.

[0199] The MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0200] The physical layer signaling may be, for example, downlink control information (DCI).

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

[0202] <Configuration of Base Station> Fig. 23 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. 24) wirelessly. The base station 10 may be a CW node or a terminal (for example, an intermediate node communicating with the device 20). The intermediate node may be referred to as an intermediate UE.

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

[0204] The DL signal may include, for example, a downlink data signal and control information (e.g., Downlink Control Information (DCI)). 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 Radio Resource Control (RRC)). The DL signal may also include a reference signal.

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

[0206] The reference signal included in the DL signal may include at least one of a demodulation reference signal (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 DMRS and PTRS are used for demodulating downlink data signals and are transmitted using the PDSCH.

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

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

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

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

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

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

[0213] For example, the transmitter 101 of the base station 10 (an example of a wireless communication device) transmits a first R2D transmission (an example of a first signal). Then, the controller 103 controls the reception of a first D2R transmission (an example of a second signal) corresponding to the first R2D transmission and the reception of a second D2R transmission (an example of a third signal) different from the first D2R transmission. Here, the control of reception includes control of reception timing, setting of reception resources, determination of whether reception is possible, etc.

[0214] For example, the control unit 103 of the base station 10 (an example of a wireless communication device) divides information (e.g., TB) into multiple blocks (e.g., code blocks or segments). Then, the transmission unit 101 transmits the multiple blocks. For example, the transmission unit 101 transmits the multiple blocks on the PRDCH.

[0215] <Device Configuration> Fig. 24 is a block diagram showing an example of the configuration of a device 20 according to an embodiment. The device 20 is a device with lower complexity than a Narrow Band-Internet of Things (NB-IoT) device, and is, for example, an A-IoT UE or an A-IoT device. The device 20 may be considered to be a device that receives power from energy harvesting. For example, the device 20 may be considered to be a device that receives power from the base station 10 or a CW supplied from the base station 10.

[0216] 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 device.

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

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

[0219] The UL signal may include, for example, an uplink data signal and control information (e.g., UCI). For example, information related to the processing capabilities of the device 20 (e.g., UE capability) may be included. The UL signal may also include a reference signal.

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

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

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

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

[0224] 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, 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 in the resources of the PUCCH.

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

[0226] 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 Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI), for example.

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

[0228] For example, the receiving unit 201 of the device 20 receives a first R2D transmission (an example of a first signal). The control unit 203 controls the transmission of a first D2R transmission (an example of a second signal) corresponding to the first R2D transmission and the transmission of a second D2R transmission (an example of a third signal) different from the first D2R transmission. Here, the control of transmission includes control of transmission timing, setting of transmission resources, determination of whether or not to transmit, etc.

[0229] For example, the control unit 203 of the device 20 divides information (e.g., a TB) into multiple blocks (e.g., code blocks or segments). The transmission unit 202 then transmits the multiple blocks. The transmission unit 202 transmits the multiple blocks on the PDRCH.

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

[0231] <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 be realized by combining software with the single device or the multiple devices.

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

[0233] For example, a base station, an intermediate node, a terminal, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 25 is a diagram showing an example of the hardware configuration of a base station and a terminal according to this embodiment. The above-described base station 10 and terminal 20 may be physically configured as a computer device 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.

[0234] 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 terminal 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.

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

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

[0237] 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 these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 203 of the terminal 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

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

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

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

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

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

[0243] Furthermore, the base station 10 and the terminal 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.

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

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

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

[0247] <Base Station Operation> In the following, a base station may be read as an intermediate node. A specific operation described as being performed by a base station in the present disclosure may also be performed by its upper node in some cases. It is clear that in a network consisting of one or more network nodes having a base station, 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 is not limited to these). While 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0266] Furthermore, a base station in the present disclosure may be read as a terminal. For example, the embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0307] 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 in the plural form.

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

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

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

Claims

1. A device comprising: a receiving unit that receives a first signal; and a control unit that controls the transmission of a second signal corresponding to the first signal and the transmission of a third signal different from the second signal.

2. The device according to claim 1, wherein the control unit does not anticipate receiving a fourth signal between receiving the first signal and transmitting the second signal.

3. The device of claim 1, wherein the control unit does not assume that transmission of the third signal overlaps with transmission of the second signal.

4. The device of claim 1, wherein the control unit controls transmission of at least one of the second signal and the third signal when transmission of the third signal overlaps with transmission of the second signal.

5. A wireless communication device comprising: a transmitter that transmits a first signal; and a controller that controls reception of a second signal corresponding to the first signal and reception of a third signal different from the second signal.

6. A wireless communication method, in which a device receives a first signal, and controls transmission of a second signal corresponding to the first signal and transmission of a third signal different from the second signal.

Images