Device and communication method

Abstract

This device to which power is supplied by environmental power generation includes: a reception unit that receives a preamble; and a control unit that determines transmission of an uplink signal on the basis of a sequence and / or a resource of the preamble.

Description

Device and communication method

[0001] The present disclosure relates to devices and communication methods.

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

[0005] However, in ambient IoT, the behavior after receiving the preamble has not been sufficiently studied, and further study is required.

[0006] One aspect of the present disclosure is to provide a device and a communication method that can operate properly after receiving a preamble.

[0007] A device according to one aspect of the present disclosure is a device that is powered by energy harvesting and has a receiver that receives a preamble and a controller that determines the transmission of an uplink signal based on the sequence and / or resources of the preamble.

[0008] A device according to one aspect of the present disclosure is a device that is powered by energy harvesting, and has a receiving unit that receives a downlink signal after receiving a preamble, and a control unit that determines, based on information contained in the downlink signal, whether the downlink signal is a signal that schedules the reception of a signal containing information addressed to the device or a signal that schedules the transmission of an uplink signal.

[0009] 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 support. FIG. 3 is a diagram illustrating Topology 3 in UL support. FIG. 4 is a diagram illustrating Topology 4. FIG. 5 is a diagram illustrating backscatter transmission. FIG. 6 is a diagram illustrating Option A in R2D scheduling. FIG. 7 is a diagram illustrating Option B in R2D scheduling. FIG. 8 is a diagram illustrating Option B in R2D scheduling. FIG. 9 is a diagram illustrating Option 1A in D2R scheduling. FIG. 10 is a diagram illustrating Option 1B in D2R scheduling. FIG. 11 is a diagram illustrating Option 2 in D2R scheduling. FIG. 12 is a diagram illustrating Option 3 in D2R scheduling. FIG. 13 is a diagram illustrating Proposal 1: Option 1: Alt. 1. FIG. 14 is a diagram illustrating Proposal 2. FIG. 15 is a diagram illustrating Proposal 4. FIG. 16 is a block diagram illustrating an example of a configuration of a base station according to an embodiment. FIG. 17 is a block diagram illustrating an example of a configuration of a device according to an embodiment. FIG. 18 is a diagram illustrating an example of the hardware configuration of a base station and a device according to the present embodiment. FIG. 19 is a diagram illustrating an example of the configuration of a vehicle.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0039] 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. Also, an A-IoT device may be simply referred to as A-IoT.

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

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

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

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

[0044] For A-IoT DL and UL, several issues will be discussed under the leadership of RAN1. One of the issues to be discussed is the scheduling and timing relationship between DL and UL in A-IoT.

[0045] In Rel-19 SID, attention is focused on Topology 1 and Topology 2 among the topologies shown in FIGS.

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

[0047] In Topology 2, UL / DL 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 the case of Topology 2 may correspond to a macrocell. The case of Topology 2 may also be applied to indoor cases. Hereinafter, the intermediate node will also be referred to as intermediate UE, int.UE (intermediate UE), or Int.UE.

[0048] <Device Types in RAN1> In RAN1, for the purpose of the study, the following terms are used for device types:

[0049] Device 1: Device 1 (which may be referred to as Type 1) is a type of device that consumes a peak power of 1 μW or less. Device 1 has an energy storage and an initial sampling frequency offset (SFO) of up to Z ppm (parts per million), where Z is 10 to the power x (x is an integer greater than or equal to 0). Device 1 does not have any DL / UL amplifiers. UL transmission in Device 1 is performed by backscattering with an externally provided carrier wave (CW). Note that SFO indicates the difference in sampling frequency between the transmitting side and the receiving side. SFO may be interpreted as indicating, for example, the accuracy of time synchronization between the transmitting side and the receiving side.

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

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

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

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

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

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

[0056] R2D, R2D transmit, R2D signal, DL, and DL signal may be used interchangeably. D2R, D2R transmit, R2D signal, UL, and UL signal may be used interchangeably.

[0057] <Timing Acquisition Signal> At the RAN1#116 meeting, it was agreed to consider timing acquisition signals for R2D and D2R transmissions. Regarding timing acquisition signals, the time domain frame structure is being considered.

[0058] For example, for R2D transmissions, an R2D timing acquisition signal (eg, an R2D preamble) is included for at least timing acquisition and to indicate the start of the R2D transmission in the time domain.

[0059] For example, for D2R transmissions, a D2R timing acquisition signal (eg, a D2R preamble) is included at least for timing acquisition and to indicate the start of the D2R transmission in the time domain.

[0060] Other components, such as the midamble, postamble, periodic synchronization signal, control field, and guard period, are FFS (For Further Study).

[0061] <R2D scheduling> For R2D scheduling, the following options A and B can be considered.

[0062] Option A: In Option A, the R2D preamble is followed by a physical channel such as PRDCH, which carries the R2D higher layer information. For example, as shown in Figure 8, the P2D preamble is followed by the R2D higher layer information (PRDCH).

[0063] Option B Unlike Option A, Option B has a physical channel such as R2D PHY layer control. In Option B, the R2D preamble is followed by the R2D PHY layer control, which is followed by a physical channel such as PRDCH that carries R2D upper layer information. For example, as shown in Figure 9, the P2D preamble is followed by the R2D PHY layer control. The R2D PHY layer control is followed by the R2D upper layer information. In Option B, the R2D upper layer information (PRDCH) is scheduled by the R2D PHY layer control.

[0064] In Option B, an R2D preamble may be transmitted between the R2D physical layer control and the R2D upper layer information as shown in Figure 10. An R2D midamble may be transmitted between the R2D physical layer control and the R2D upper layer information as shown in Figure 11. The R2D preamble and R2D midamble allow the network and A-IoT to resynchronize R2D transmissions.

[0065] <D2R Scheduling> For D2R scheduling, the following options 1, 2, and 3 can be envisaged.

[0066] Option 1 In option 1, a PDRCH carrying D2R data / response is scheduled by a higher layer R2D command, such as R2D higher layer information.

[0067] Regarding reception of R2D upper layer information, the following options 1A and 1B can be envisaged.

[0068] Option 1 - Option 1A In Option 1A, the R2D preamble is followed by the R2D upper layer information that carries the upper layer command. For example, as shown in Figure 12, the R2D preamble is followed by the R2D upper layer information. The D2R data / response (PDRCH) is scheduled by the R2D upper layer information.

[0069] Option 1 - Option 1B Unlike Option 1A, Option 1B has R2D physical layer control. In Option 1B, the R2D preamble is followed by the R2D physical layer control, which is followed by the R2D upper layer information. For example, as shown in Figure 13, the P2D preamble is followed by the R2D physical layer control. The R2D physical layer control is followed by the R2D upper layer information. In Option 1B, the R2D upper layer information (PRDCH) is scheduled by the R2D physical layer control.

[0070] Option 2: Unlike Option 1, Option 2 does not have R2D upper layer information. In Option 2, D2R data / response is scheduled by R2D physical layer control. For example, as shown in Figure 14, the R2D preamble is followed by R2D physical layer control. The R2D physical layer control is followed by D2R data / response. The D2R data / response (PDRCH) is scheduled by the R2D physical layer control.

[0071] Option 3: Unlike Options 1 and 2, Option 3 does not have R2D upper layer information and R2D physical layer control. For example, as shown in Figure 15, the R2D preamble is followed by D2R data / response. The D2R data / response is scheduled by the R2D preamble.

[0072] <Consideration 1> As described above in <R2D scheduling> and <D2R scheduling>, in A-IoT, after receiving an R2D preamble, there are two behaviors: one is to receive information from the network (R2D scheduling) and the other is to transmit information to the network (D2R scheduling).

[0073] R2D scheduling option A + D2R scheduling option 1A Option A, described above in <R2D scheduling>, is an A-IoT operation for receiving information from the network after receiving an R2D preamble. Option 1A, described above in <D2R scheduling>, is an A-IoT operation for transmitting information to the network after receiving an R2D preamble.

[0074] When A-IoT operates in Option A and Option 1A, the operation of A-IoT after receiving the R2D preamble is the same (common) for Option A and Option 1A. For example, when A-IoT operates in Option A, A-IoT receives the R2D preamble and then receives the PRDCH as shown in Figure 8. The payload of the PRDCH is R2D upper layer information. When A-IoT operates in Option 1A, A-IoT receives the R2D preamble and then receives the PRDCH as shown in Figure 12. The payload of the PRDCH is R2D upper layer information.

[0075] Therefore, when A-IoT operates in both Option A and Option 1A, it performs the common operation of receiving R2D upper layer information and can recognize whether to schedule (execute) D2R data / response based on the R2D upper layer information (there is no problem with adopting this case).

[0076] R2D scheduling option A + D2R scheduling option 1B Option A, described above in <R2D scheduling>, is an A-IoT operation for receiving information from the network after receiving an R2D preamble. Option 1B, described above in <D2R scheduling>, is an A-IoT operation for transmitting information to the network after receiving an R2D preamble.

[0077] When the A-IoT operates in both Option A and Option 1B, the operation of the A-IoT after receiving the R2D preamble cannot be said to be rational. For example, as shown in Figure 8, there is no reason to make the A-IoT operate differently between the case where there is no D2R data / response and R2D upper layer information is received (Option A) and the case where there is D2R data / response and R2D physical layer control and R2D upper layer information is received (Option 1B) as shown in Figure 13. In other words, there is no particular reason to make the A-IoT's operation in R2D scheduling and D2R scheduling different in order to receive R2D physical layer control (there is no particular reason to actively adopt this case).

[0078] R2D scheduling option A + D2R scheduling option 2 After receiving the R2D preamble, the A-IoT performs the following operations: Option A, described above in <R2D scheduling>, receives information from the network. After receiving the R2D preamble, the A-IoT performs the following operations: Option 2, described above in <D2R scheduling>, transmits information to the network.

[0079] When A-IoT operates in both Option A and Option 2, the behavior of A-IoT after receiving the R2D preamble differs between Option A and Option 2.

[0080] (1) For R2D scheduling (Option A), the A-IoT receives a PRDCH after receiving an R2D preamble. The payload of the PRDCH is R2D upper layer information. For example, as shown in Figure 8, the A-IoT receives the R2D upper layer information after receiving an R2D preamble. (2) For D2R scheduling (Option 2), the A-IoT receives a PRDCH after receiving an R2D preamble. The payload of the PRDCH is physical layer control information. For example, as shown in Figure 14, the A-IoT receives an R2D physical layer control after receiving an R2D preamble.

[0081] Currently, there is no proposed method for A-IoT to determine whether to perform operation (1) or (2) after receiving the R2D preamble.

[0082] Therefore, in the present disclosure, in Proposal 1, a method for determining whether to perform the operation (1) or (2) is proposed.

[0083] <Proposal 1> Proposal 1 offers the following options 1 and 2.

[0084] <Proposal 1: Option 1> In R2D scheduling and D2R scheduling, the following (1) and (2) are supported.

[0085] (1) For R2D scheduling, the R2D preamble is followed by a physical channel such as PRDCH that carries higher layer information. There is no R2D physical layer control for R2D scheduling. (2) For D2R scheduling, the R2D preamble is followed by R2D physical layer control. The R2D physical layer control schedules the PDRCH that carries D2R data / response transmission. Physical layer control information for D2R scheduling is carried on the PRDCH.

[0086] After receiving the R2D preamble, A-IoT receives the PRDCH. A-IoT performs the following behaviors 1 and 2 on the PRDCH payload.

[0087] Action 1: A-IoT assumes that the payload of the PRDCH is upper layer information. For example, A-IoT assumes that the payload of the received PRDCH is R2D upper layer information. Action 2: A-IoT assumes that the payload of the PRDCH is physical control information that schedules D2R data / response on the PDRCH. For example, A-IoT assumes that the payload of the PRDCH is R2D physical layer control.

[0088] Regarding the operation of A-IoT, the following Alt.1 to Alt.4 are provided.

[0089] <Proposal 1: Option 1: Alt. 1> The A-IoT performs either Action 1 or Action 2 based on the sequence / resource of the received R2D preamble. Different sequences / resources of the R2D preamble correspond to Action 1 or Action 2. The resource may be a time resource / frequency resource.

[0090] Figure 16 is a diagram explaining Proposal 1: Option 1: Alt. 1. For example, as shown by arrow A16a in Figure 16, when the sequence / time resource / frequency resource of the received R2D preamble is "#A", A-IoT performs operation 1. In other words, when A-IoT receives the R2D preamble shown by arrow A16a in Figure 16, it assumes that the payload of the PRDCH is R2D upper layer information.

[0091] For example, as shown by arrow A16b in Figure 16, if the sequence / time resource / frequency resource of the received R2D preamble is "#B", the A-IoT performs operation 2. In other words, when the A-IoT receives the R2D preamble shown by arrow A16b in Figure 16, it assumes that the PRDCH payload is R2D physical layer control. The A-IoT schedules D2R data / response based on the R2D physical layer control.

[0092] <Proposal 1: Option 1: Alt. 2> A-IoT performs both operation 1 and operation 2. After receiving the R2D preamble, A-IoT receives the PRDCH and assumes that the payload is operation 1 or operation 2.

[0093] The A-IoT may receive multiple PRDCHs on different resources, and may assume either Action 1 or Action 2 for each of the multiple PRDCHs.

[0094] For example, the A-IoT may receive two PRDCHs on two resources in different time domains, and the A-IoT may assume either operation 1 or operation 2 for each of the two PRDCHs.

[0095] <Proposal 1: Option 1: alt.3> A-IoT first performs either operation 1 or operation 2, and if it fails, performs the other. For example, A-IoT performs operation 1 on one PRDCH. If A-IoT fails to perform operation 1 (for example, if the payload of the PRDCH is not higher layer information), it performs operation 2 on the one PRDCH.

[0096] <Proposal 1: Option 1: alt.4> The A-IoT is instructed / activated by an R2D signal (e.g., PRDCH) to perform either operation 1 or operation 2. In other words, the A-IoT performs either operation 1 or operation 2 by a kind of mode switch. For example, if operation 1 is instructed / activated by an R2D signal, the A-IoT will perform operation 1 until the next instruction / activation is made. The R2D signal may be R2D physical layer control / R2D upper layer information, or may be a signal different from the R2D physical layer control / R2D upper layer information.

[0097] <Proposal 1: Option 2> In R2D scheduling and D2R scheduling, the following (1) and (2) are supported.

[0098] (1) For R2D scheduling, a physical channel such as PRDCH carrying higher layer information follows the R2D preamble. There is no R2D physical layer control for R2D scheduling. (2) For D2R scheduling, the R2D physical layer control follows the R2D preamble. The R2D physical layer control schedules the PDRCH carrying D2R data / response transmission. The R2D physical layer control information for D2R scheduling is carried on a physical R2D channel (PHY R2D channel) different from the PRDCH.

[0099] After receiving the R2D preamble, the A-IoT performs the following actions:

[0100] Action 1: After receiving the R2D preamble, the A-IoT receives the PRDCH. The payload of the PRDCH is higher layer information. Action 2: After receiving the R2D preamble, the A-IoT receives a physical R2D channel different from the PRDCH. The payload of the physical R2D channel is physical layer control information that schedules the PDRCH that carries the D2R data / response.

[0101] Regarding the operation of A-IoT, the following Alt.1 to Alt.4 are provided.

[0102] <Proposal 1: Option 2: alt.1> Based on the sequence / resource of the received R2D preamble, A-IoT performs either Action 1 or Action 2. Different sequences / resources of the R2D preamble correspond to Action 1 or Action 2.

[0103] Figure 17 is a diagram explaining Proposal 1: Option 2: Alt. 1. For example, as shown by arrow A17a in Figure 17, when the sequence / time resource / frequency resource of the received R2D preamble is "#A", A-IoT performs operation 1. In other words, when A-IoT receives the R2D preamble shown by arrow A17a in Figure 17, it assumes that the payload of the PRDCH is R2D upper layer information.

[0104] For example, the A-IoT performs operation 2 when the sequence / time resource / frequency resource of the received R2D preamble is "#B", as shown by arrow A17b in Figure 17. In other words, when the A-IoT receives the R2D preamble shown by arrow A17b in Figure 17, it assumes R2D physical layer control on a physical channel other than PRDCH. The A-IoT schedules D2R data / response based on the R2D physical layer control.

[0105] <Proposal 1: Option 2: Alt. 2> A-IoT performs both operation 1 and operation 2. After receiving the R2D preamble, A-IoT receives both the PRDCH and the physical R2D channel for control information.

[0106] The A-IoT may receive the PRDCH and the physical R2D channel for control information on different resources, for example, the A-IoT may receive the PRDCH and the physical R2D channel on two resources that are in different time domains.

[0107] <Proposal 1: Option 2: alt.3> A-IoT will first perform either operation 1 or operation 2, and if it fails, will perform the other. For example, A-IoT will perform operation 1 on the PRDCH. If A-IoT fails to perform operation 1 (for example, if the payload of the PRDCH is not higher layer information), it will perform operation 2 on the physical R2D channel.

[0108] <Proposal 1: Option 2: alt.4> The A-IoT is instructed / activated by an R2D signal to perform either operation 1 or operation 2. In other words, the A-IoT performs either operation 1 or operation 2 using a kind of mode switch. For example, if the A-IoT is instructed / activated to perform operation 1 by an R2D signal, it will perform operation 1 until the next instruction / activation is given.

[0109] <Proposal 1: Variation> The A-IoT may have the following different operations for reception in operation 1 or operation 2.

[0110] A-IoT assumes different payload sizes for reception. A-IoT assumes different waveforms / modulation / coding schemes for reception. Coding schemes may be used interchangeably with coding. A-IoT assumes whether midambles / postambles are included for reception.

[0111] <Proposal 1: Summary> Based on the sequence and / or resource of the R2D preamble, the A-IoT determines whether the downstream signal received after the R2D preamble is R2D upper layer information including information addressed to the A-IoT, or R2D physical layer control to schedule the transmission of D2R data / response. This operation allows the A-IoT to operate appropriately after receiving the preamble.

[0112] <Consideration 2> As described above in <R2D scheduling> and <D2R scheduling>, in A-IoT, after receiving an R2D preamble, there are two operations: receiving information from the network (R2D scheduling) and transmitting information to the network (D2R scheduling).

[0113] R2D scheduling option A + D2R scheduling option 3 Option A, described above in <R2D scheduling>, is an A-IoT operation for receiving information from the network after receiving an R2D preamble. Option 3, described above in <D2R scheduling>, is an A-IoT operation for transmitting information to the network after receiving an R2D preamble.

[0114] When A-IoT operates in both Option A and Option 3, the behavior of A-IoT after receiving the R2D preamble differs between Option A and Option 3.

[0115] (1) For R2D scheduling (Option A), the A-IoT receives a PRDCH after receiving an R2D preamble. The payload of the PRDCH is R2D upper layer information. For example, as shown in Figure 8, the A-IoT receives the R2D upper layer information after receiving the R2D preamble. (2) For D2R scheduling (Option 3), the A-IoT transmits D2R data / response after receiving an R2D preamble. For example, as shown in Figure 15, the A-IoT transmits D2R data / response after receiving the R2D preamble.

[0116] Currently, there is no proposed method for A-IoT to determine whether to perform operation (1) or (2) after receiving the R2D preamble.

[0117] Therefore, in this disclosure, in Proposal 2, a method for determining whether to perform operation (1) or (2) is proposed.

[0118] <Proposal 2> In R2D scheduling and D2R scheduling, the following (1) and (2) are supported.

[0119] (1) For R2D scheduling, the R2D preamble is followed by a physical channel such as PRDCH carrying higher layer information. There is no R2D physical layer control for R2D scheduling. (2) For D2R scheduling, the R2D preamble triggers a PDRCH carrying D2R data / response transmission.

[0120] After receiving the R2D preamble, the A-IoT performs the following operations 1 and 2.

[0121] Action 1: After receiving the R2D preamble, A-IoT receives the PRDCH. The payload of the PRDCH is higher layer information. Action 2: After receiving the R2D preamble, A-IoT sends D2R data / response on the PDRCH.

[0122] Based on the sequence / resource of the received R2D preamble, the A-IoT will perform either Action 1 or Action 2. Different sequences / resources of the R2D preamble correspond to Action 1 or Action 2.

[0123] Figure 18 is a diagram explaining Proposal 2. For example, as shown by arrow A18a in Figure 18, when the sequence / time resource / frequency resource of the received R2D preamble is "#A", A-IoT performs operation 1. In other words, when A-IoT receives the R2D preamble shown by arrow A18a in Figure 18, it assumes that the payload of the PRDCH is R2D upper layer information.

[0124] For example, as shown by arrow A18b in Figure 18, when the sequence / time resource / frequency resource of the received R2D preamble is "#B", A-IoT performs operation 2. In other words, when A-IoT receives the R2D preamble shown by arrow A18b in Figure 18, it transmits D2R data / response on PRDCH.

[0125] The A-IoT may first perform operation 1, and if that fails, perform operation 2. For example, the A-IoT may first perform operation 1. If the execution of operation 1 fails (for example, if the PRDCH is not received), the A-IoT may perform operation 2.

[0126] The A-IoT may be instructed / activated by the R2D signal to perform either operation 1 or operation 2. In other words, the A-IoT may perform either operation 1 or operation 2 by a kind of mode switch. For example, if the A-IoT is instructed / activated to perform operation 1 by the R2D signal, it may continue to perform operation 1 until it is next instructed / activated.

[0127] <Proposal 2: Summary> Based on the sequence and / or resource of the R2D preamble, the A-IoT determines whether to receive R2D upper layer information including information addressed to the A-IoT after the R2D preamble or to send D2R data / response. This operation allows the A-IoT to operate appropriately after receiving the preamble.

[0128] <Consideration 3> As described above in <R2D scheduling> and <D2R scheduling>, in A-IoT, after receiving an R2D preamble, there are two operations: receiving information from the network (R2D scheduling) and transmitting information to the network (D2R scheduling).

[0129] R2D scheduling option B + D2R scheduling option 1A Option B described above in <R2D scheduling> is an A-IoT operation for receiving information from the network after receiving an R2D preamble. Option 1A described above in <D2R scheduling> is an A-IoT operation for transmitting information to the network after receiving an R2D preamble.

[0130] When the A-IoT operates in both Option B and Option 1A, the operation of the A-IoT after receiving the R2D preamble cannot be said to be rational. For example, as shown in Figure 9, there is no reason to make the A-IoT operate differently when there is no D2R data / response and R2D physical layer control and R2D upper layer information are received (Option B), and when there is D2R data / response and R2D upper layer information is received (Option 1A) as shown in Figure 12. In other words, there is no particular reason to make the A-IoT's operation in R2D scheduling and D2R scheduling different in order to receive R2D physical layer control (there is no particular reason to actively adopt this case).

[0131] R2D scheduling option B + D2R scheduling option 1B After receiving the R2D preamble, the A-IoT performs the following operations: Option B, described above in <R2D scheduling>, receives information from the network. After receiving the R2D preamble, the A-IoT performs the following operations: Option 1B, described above in <D2R scheduling>, transmits information to the network.

[0132] When A-IoT operates in Option B and Option 1B, the operation of A-IoT after receiving the R2D preamble is the same (common) for Option B and Option 1B. For example, when A-IoT operates in Option B, A-IoT receives R2D physical layer control and R2D upper layer information after receiving the R2D preamble, as shown in Figure 9. The R2D physical layer control schedules the PRDCH carrying the R2D upper layer information. When A-IoT operates in Option 1B, A-IoT receives R2D physical layer control and R2D upper layer information after receiving the R2D preamble, as shown in Figure 13. The R2D upper layer information schedules the PDRCH carrying the D2R data / response.

[0133] Therefore, when A-IoT operates in both Option B and Option 1B, it performs the common operation of R2D physical layer control and receiving R2D upper layer information, and can recognize whether to schedule (execute) D2R data / response based on the R2D upper layer information (there is no problem with adopting this case).

[0134] R2D scheduling option B + D2R scheduling option 2 After receiving the R2D preamble, the A-IoT performs the following operations: receiving information from the network (option B, described above in <R2D scheduling>). After receiving the R2D preamble, the A-IoT performs the following operations: transmitting information to the network (option 2, described above in <D2R scheduling>).

[0135] When A-IoT operates in both Option B and Option 2, the behavior of A-IoT after receiving the R2D preamble differs between Option B and Option 2.

[0136] (1) For Option B (R2D scheduling), the A-IoT receives the R2D physical layer control and R2D upper layer information after receiving the R2D preamble. For example, as shown in Figure 9, the A-IoT receives the R2D physical layer control and R2D upper layer information after receiving the R2D preamble. (2) For Option 2 (D2R scheduling), the A-IoT receives the physical layer control information after receiving the R2D preamble. For example, as shown in Figure 14, the A-IoT receives the R2D physical layer control after receiving the R2D preamble.

[0137] Currently, there is no proposed method for A-IoT to determine whether to perform operation (1) or (2) after receiving the R2D preamble.

[0138] Therefore, in this disclosure, in Proposal 3, a method for determining whether to perform operation (1) or (2) is proposed.

[0139] <Proposal 3> In R2D scheduling and D2R scheduling, the following (1) and (2) are supported.

[0140] (1) For R2D scheduling, the R2D preamble is followed by physical layer control information that schedules the PRDCH carrying the R2D upper layer information. (2) For D2R scheduling, the R2D preamble is followed by physical layer control information that schedules the PDRCH carrying the D2R data / response.

[0141] At least one bit in the physical layer control information may indicate whether to schedule a PRDCH or a PDRCH.

[0142] The physical layer control information may be carried on the PRDCH. The physical layer control information may be carried on a PHY layer R2D channel other than the PRDCH.

[0143] Regarding the operation of A-IoT, the following options 1 and 2 are provided.

[0144] <Proposal 3: Option 1> The resources, payload size, scrambling ID, and other parameters (waveform, modulation, and coding scheme) for receiving physical layer control information for R2D scheduling and physical layer control information for D2R scheduling are the same. Whether TX (transmission) or RX (reception) is to be performed may be indicated by the physical layer control information.

[0145] In order to align the sizes of the physical layer control information for R2D scheduling and the physical layer control information for D2R scheduling, the following Alt. 1 and Alt. 2 are provided.

[0146] <Proposal 3: Option 1: alt.1> If the size of the physical control (PHY control) for R2D scheduling is smaller than the size of the physical control for D2R scheduling, the A-IoT performs the following operations (1) / (2): (1) The A-IoT generates zero padding bits until the payload size of the physical control for R2D scheduling is equal to the size of the physical control for D2R scheduling. (2) The A-IoT truncates (reduces) several bits (or specific fields) of the physical control for D2R scheduling so that the size of the physical control for D2R scheduling is equal to the size of the physical control for R2D scheduling. The truncated bits may be the first several most significant bits or the first several least significant bits.

[0147] <Proposal 3: Option 1: alt.2> If the size of the physical control for R2D scheduling is larger than the size of the physical control for D2R scheduling, the A-IoT performs the following operations (1) / (2): (1) The A-IoT generates zero padding bits until the payload size of the physical control for D2R scheduling is equal to the size of the physical control for R2D scheduling. (2) The A-IoT truncates (reduces) several bits (or specific fields) of the physical control for R2D scheduling so that the size of the physical control for R2D scheduling is equal to the size of the physical control for D2R scheduling. The truncated bits may be the first several most significant bits or the first several least significant bits.

[0148] <Proposal 3: Option 2> The resources, payload size, scrambling ID, and other parameters (waveform, modulation, and coding scheme) for receiving physical layer control information for R2D scheduling and D2R scheduling are different. The following Alt. 1 and Alt. 2 are provided for Option 2.

[0149] <Proposal 3: Option 2: alt.1> A-IoT blind decodes physical layer control for R2D scheduling or D2R scheduling with different resource / size / scrambling / other parameters.

[0150] <Proposal 3: Option 2: alt.2> Based on the sequence / resource of the received R2D preamble, the A-IoT receives physical layer control for R2D scheduling or D2R scheduling with corresponding resources / payload size / scrambling ID / other parameters (waveform / modulation / coding scheme). Different sequences / resources of the R2D preamble correspond to physical layer control for R2D scheduling or physical layer control for D2R scheduling.

[0151] <Proposal 3: Summary> After receiving the R2D preamble, the A-IoT receives the R2D physical layer control. Based on the information contained in the R2D physical layer control, the A-IoT determines whether the received R2D physical layer control is a signal to schedule the reception of R2D upper layer information including information addressed to the A-IoT, or a signal to schedule the transmission of D2R data / response. This operation allows the A-IoT to operate appropriately after receiving the preamble.

[0152] <Consideration 4> As described above in <R2D scheduling> and <D2R scheduling>, in A-IoT, after receiving an R2D preamble, there are two operations: receiving information from the network (R2D scheduling) and transmitting information to the network (D2R scheduling).

[0153] R2D scheduling option B + D2R scheduling option 3 After receiving the R2D preamble, the A-IoT performs the following operations: receiving information from the network (option B, described above in <R2D scheduling>). After receiving the R2D preamble, the A-IoT performs the following operations: transmitting information to the network (option 3, described above in <D2R scheduling>).

[0154] When A-IoT operates in both Option B and Option 3, the behavior of A-IoT after receiving the R2D preamble differs between Option B and Option 3.

[0155] (1) For R2D scheduling (Option B), the A-IoT receives an R2D preamble and then receives an R2D physical layer control and R2D upper layer information. For example, as shown in Figure 9, the A-IoT receives an R2D preamble and then receives an R2D physical layer control and R2D upper layer information. (2) For D2R scheduling (Option 3), the A-IoT receives an R2D preamble and then transmits D2R data / response. For example, as shown in Figure 15, the A-IoT receives an R2D preamble and then transmits D2R data / response.

[0156] Currently, there is no proposed method for A-IoT to determine whether to perform operation (1) or (2) after receiving the R2D preamble.

[0157] Therefore, in the present disclosure, in Proposal 4, a method for determining whether to perform the operation (1) or (2) is proposed.

[0158] <Proposal 4> In R2D scheduling and D2R scheduling, the following (1) and (2) are supported.

[0159] (1) For R2D scheduling, the R2D preamble is followed by R2D physical layer control information, which schedules the PRDCH carrying the R2D upper layer information. (2) For D2R scheduling, the R2D preamble triggers the PDRCH carrying the D2R data / response.

[0160] After receiving the R2D preamble, the A-IoT performs the following operations 1 and 2.

[0161] Action 1: After receiving the R2D preamble, the A-IoT receives R2D physical layer control information to schedule the PRDCH. For Action 1, the A-IoT may perform the following actions 1a and 1b: Action 1a: The A-IoT receives the PRDCH. The payload of the PRDCH is physical control information to schedule the PRDCH. Action 1b: The A-IoT receives a physical R2D channel different from the PRDCH. The payload of the physical R2D channel is physical control information to schedule the PRDCH. Action 2: After receiving the R2D preamble, the A-IoT transmits D2R data / response on the PRDCH.

[0162] Based on the sequence / resource of the received R2D preamble, the A-IoT will perform either Action 1 or Action 2. Different sequences / resources of the R2D preamble correspond to Action 1 or Action 2.

[0163] Figure 19 is a diagram illustrating Proposal 4. For example, as shown by arrow A19a in Figure 19, when the sequence / time resource / frequency resource of the received R2D preamble is "#A", the A-IoT performs Operation 1. In other words, when the A-IoT receives the R2D preamble shown by arrow A19a in Figure 19, it assumes that the payload of the PRDCH is R2D physical layer control. The R2D physical layer control schedules the PRDCH carrying R2D upper layer information.

[0164] For example, as shown by arrow A19b in Figure 19, when the sequence / time resource / frequency resource of the received R2D preamble is "#B", A-IoT performs operation 2. In other words, when A-IoT receives the R2D preamble shown by arrow A19b in Figure 19, it transmits D2R data / response on the PDRCH.

[0165] The A-IoT may first perform operation 1, and if that fails, perform operation 2. For example, the A-IoT may first perform operation 1. If the execution of operation 1 fails (for example, if the PRDCH is not received), the A-IoT may perform operation 2.

[0166] The A-IoT may be instructed / activated by the R2D signal to perform either operation 1 or operation 2. In other words, the A-IoT may perform either operation 1 or operation 2 by a kind of mode switch. For example, if the A-IoT is instructed / activated to perform operation 1 by the R2D signal, it may continue to perform operation 1 until it is next instructed / activated.

[0167] <Proposal 4: Summary> Based on the sequence and / or resources of the R2D preamble, the A-IoT determines whether to receive the R2D physical layer control that schedules the reception of R2D upper layer information, including information addressed to the A-IoT. This operation allows the A-IoT to operate appropriately after receiving the preamble.

[0168] <Capabilities> The A-IoT may report information about its R2D scheduling capabilities. For example, the A-IoT may report information about which of the options described above under <R2D scheduling> it can operate with.

[0169] The A-IoT may report information about its D2R scheduling capabilities, for example, whether it can operate with any of the options described above under <D2R scheduling>.

[0170] A-IoT may report which of the proposed operations described in Proposals 1 to 4 it will perform.

[0171] <Terminology> R2D physical layer control may correspond to the R2D control transmission described above in <R2D and D2R>. The R2D physical layer control may be transmitted on the PRDCH or on a physical channel different from the PRDCH.

[0172] The R2D upper layer information may be data transmitted to the A-IoT. In this case, the R2D upper layer information may correspond to the R2D data transmission described above in <R2D and D2R>. Data, information, and signal may be used interchangeably.

[0173] The R2D upper layer information may be data for controlling the A-IoT. For example, the R2D upper layer information may be data for scheduling D2R data / responses. In this case, the R2D upper layer information may correspond to the R2D control transmissions described above in <R2D and D2R>.

[0174] The D2R data / response may correspond to the D2R data transmission / D2R control transmission described above in <R2D and D2R>.

[0175] R2D physical layer control, R2D physical layer control information, physical layer control information, physical control information, physical control, physical layer control, PRDCH, and physical channel may be used interchangeably.

[0176] The R2D Upper Layer Information, Upper Layer Information, and Physical Channel may be used interchangeably. The D2R Data / Response, PDRCH, and Physical Channel may be used interchangeably.

[0177] <Base Station> Fig. 20 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. 21) by radio. The base station 10 may be an intermediate node, a support node, or a terminal (a terminal in SL that communicates with the device 20).

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

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

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

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

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

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

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

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

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

[0187] Here, the control unit 103 may control the sequence and / or resources of the preamble so that the device 20 can determine the transmission of the uplink signal. The preamble may be an R2D preamble. The uplink signal may be D2R data / response.

[0188] The control unit 103 may include information in the downlink signal transmitted after the preamble. The information may indicate whether the downlink signal is a signal for scheduling reception of a signal including information addressed to the device or a signal for scheduling transmission of an uplink signal. The downlink signal may be R2D physical layer control. The signal including information addressed to the device may be R2D upper layer information.

[0189] <Device Configuration> Fig. 21 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. The device 20 may be considered as a device that receives power from energy harvesting.

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

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

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

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

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

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

[0196] The control unit 203 controls the communication operations of the device 20 , including the reception processing in the receiving unit 201 and the transmission processing in the transmitting unit 202 .

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

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

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

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

[0201] Here, the receiving unit 201 receives a preamble, which may be an R2D preamble.

[0202] The control unit 203 may determine the transmission of the uplink signal based on the preamble sequence and / or the resource, which may be a time resource / frequency resource, and the uplink signal may be D2R data / response.

[0203] The control unit 203 may determine, based on the sequence and / or resources of the preamble, whether a downlink signal received after the preamble is a signal including information addressed to the device 20 or a signal scheduling transmission of an uplink signal. The signal including information addressed to the device 20 may be R2D upper layer information. The signal scheduling transmission of an uplink signal may be R2D physical layer control.

[0204] The control unit 203 may determine, based on the sequence and / or resources of the preamble, to receive a signal that schedules reception of a signal that includes information addressed to the device 20. The signal that includes information addressed to the device 20 may be R2D upper layer information. The signal that schedules reception of a signal that includes information addressed to the device 20 may be R2D physical layer control.

[0205] After receiving the preamble, the receiver 201 may receive a downlink signal, which may be an R2D physical layer control signal.

[0206] The control unit 203 may determine, based on information included in the downlink signal, whether the downlink signal is a signal for scheduling reception of a signal including information addressed to the device 20 or a signal for scheduling transmission of an uplink signal. The signal including information addressed to the device 20 may be R2D upper layer information. The uplink signal may be D2R data / response.

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

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

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

[0210] For example, a base station, a device, or the like 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. 22 is a diagram illustrating an example of the hardware configuration of a base station and a device according to this embodiment. The above-described base station 10 and device 20 may be physically configured as a computer including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0227] <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 numerical comparison (e.g., comparison with a predetermined value).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A device powered by energy harvesting, comprising: a receiver that receives a preamble; and a controller that determines the transmission of an uplink signal based on the sequence and / or resources of the preamble.

2. The device according to claim 1, wherein the control unit determines, based on the sequence and / or resources of the preamble, whether a downlink signal received after the preamble is a signal containing information addressed to the device or a signal scheduling transmission of the uplink signal.

3. The device according to claim 1, wherein the control unit determines reception of a signal that schedules reception of a signal containing information addressed to the device based on the sequence and / or resources of the preamble.

4. A device powered by energy harvesting, comprising: a receiver that receives a downlink signal after receiving a preamble; and a controller that determines, based on information contained in the downlink signal, whether the downlink signal is a signal that schedules the reception of a signal containing information addressed to the device or a signal that schedules the transmission of an uplink signal.

5. A communication method for a device powered by energy harvesting, comprising: receiving a preamble; and determining to transmit an uplink signal based on a sequence and / or resources of the preamble.

6. A communication method for a device powered by energy harvesting, comprising: receiving a downstream signal after receiving a preamble; and determining, based on information contained in the downstream signal, whether the downstream signal is a signal that schedules the reception of a signal containing information addressed to the device or a signal that schedules the transmission of an upstream signal.

Images