Device and communication method

Abstract

This device has lower complexity than a Narrow Band Internet of Things (NB-IoT) device. The device includes a reception unit for receiving a reception signal from a wireless communication device, a control unit for controlling transmission of an acknowledgement signal corresponding to the reception signal, and a transmission unit for transmitting the acknowledgement signal to the wireless communication device. The control unit determines whether the transmission of the acknowledgement signal is necessary or not on the basis of an instruction in the reception signal.

Description

Device and communication method

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

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

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

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

[0005] In a communication system including an ambient IoT device, there is room for consideration regarding the control of ACK / NACK feedback (acknowledgment signal) corresponding to a reader-to-device (R2D) communication signal (hereinafter simply referred to as "R2D"). If necessary ACK / NACK feedback is not transmitted, lost R2D signals may not be retransmitted, potentially preventing the ambient IoT device from communicating properly. On the other hand, if unnecessary ACK / NACK feedback is transmitted, resource waste may result, reducing the throughput of device-to-reader (D2R) communication signals (hereinafter simply referred to as "D2R"), or causing the ambient IoT device to consume excessive power.

[0006] One aspect of the present disclosure contributes to providing a device and a communication method that appropriately control whether or not ACK / NACK feedback needs to be transmitted in a communication system including an ambient IoT device.

[0007] A device according to one aspect of the present disclosure is a device of lower complexity than an NB-IoT (Narrow Band Internet of Things) device, and comprises a receiving unit that receives a received signal from a wireless communication device, a control unit that controls the transmission of an acknowledgment response signal corresponding to the received signal, and a transmitting unit that transmits the acknowledgment response signal to the wireless communication device, wherein the control unit determines whether or not to transmit the acknowledgment response signal based on instructions in the received signal.

[0008] 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure. FIG. 2 is a diagram illustrating topology 1. FIG. 3 is a diagram illustrating topology 2. FIG. 4 is a diagram illustrating topology 3 in DL assistance. FIG. 5 is a diagram illustrating topology 4. FIG. 6 is a diagram illustrating backscatter transmission. FIG. 7 is a diagram illustrating an example of a candidate topology for CW / R2D / D2R transmission in topology 1. FIG. 8 is a diagram illustrating an example of a candidate topology for CW / R2D / D2R transmission in topology 2. FIG. 9 is a diagram illustrating an example of an access procedure for an A-IoT device. FIG. 10 is a diagram illustrating control of whether or not a device according to an embodiment of the present disclosure needs to transmit ACK / NACK feedback. FIG. 11 is a block diagram illustrating an example of a configuration of a base station according to an embodiment of the present disclosure. FIG. 12 is a block diagram illustrating an example of a configuration of a device according to an embodiment of the present disclosure. FIG. 13 is a diagram illustrating an example of the hardware configuration of a base station and a device according to an embodiment of the present disclosure. FIG. 14 is a diagram illustrating an example of the configuration of a vehicle according to an embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

[0019] The device 20 is a communication device equipped with a wireless communication function, and 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.

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

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

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

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

[0024] Based on the above deployment scenarios and characteristics, for example, the following RAN design targets can be formulated: power consumption, complexity, coverage, data rate, and positioning accuracy.

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

[0026] <Device Types and Topologies> Based on the results of the study items, TR 38.848 (Non-Patent Document 3) was approved. TR 38.848 considers the following categories of ambient IoT devices: Device A: Device A has no power (energy) storage, no independent signal generation or signal amplification functions, and performs backscattering transmission. Device B: Device B has power storage, no independent signal generation function, and performs backscattering transmission. Device B uses the stored power to amplify the reflected signal. Device C: Device C has power storage, independent signal generation function, and an active RF (radio frequency) component for transmission.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0056] <Device Types> The following three device types, Device 1, Device 2a, and Device 2b, are defined for A-IoT devices.

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

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

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

[0060] <Candidate Topologies> Next, candidate topologies for CW / R2D / D2R transmission will be described.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0076] <Access Procedure of A-IoT Device> In an A-IoT communication session, an access procedure of an A-IoT device (hereinafter also simply referred to as a device) is executed. Two approaches, a two-step approach and a four-step approach, are being considered for the access procedure of an A-IoT device.

[0077] Fig. 10 is a diagram showing an example of an access procedure for an A-IoT device. Fig. 10 shows signal exchange between one reader and one device. The horizontal axis of Fig. 10 indicates the time axis. Fig. 10 shows exchanges including a two-step access procedure and a four-step access procedure.

[0078] In the two-step access procedure, the reader transmits an A-IoT paging message. The A-IoT paging corresponds to the first R2D transmission in an A-IoT communication session. The device that receives the A-IoT paging transmits a message called A-IoT Msg1 to the reader. In the two-step access procedure, the A-IoT Msg1 includes information that identifies the device (e.g., a device ID). The A-IoT Msg1 may be considered a device ID report. The reader that receives the A-IoT Msg1 transmits a message called A-IoT Msg2 to the device. For example, the reader that receives the A-IoT Msg1 transmits A-IoT Msg2 addressed to the device identified by the device ID included in the A-IoT Msg1. The A-IoT Msg2 includes information indicating contention resolution. A-IoT Msg2 can be considered as contention resolution, and the two-step access procedure is then completed.

[0079] In the four-step access procedure, the reader sends an A-IoT paging. The device that receives the A-IoT paging sends a message called A-IoT Msg1 to the reader. In the four-step access procedure, A-IoT Msg1 includes a random ID. A-IoT Msg1 may be considered a random ID report. The reader that receives A-IoT Msg1 sends a message called A-IoT Msg2 to the device. For example, the reader that receives A-IoT Msg1 sends A-IoT Msg2 that includes the random ID included in A-IoT Msg1. A-IoT Msg2 includes information indicating contention resolution. A-IoT Msg2 may be considered contention resolution. The device receives A-IoT Msg2 and transmits A-IoT Msg3 to the reader. For example, if the random ID of the received A-IoT Msg2 matches the random ID of the transmitted A-IoT Msg1, the device transmits A-IoT Msg3 to the reader. In the four-step access procedure, A-IoT Msg3 includes information that identifies the device (e.g., a device ID). A-IoT Msg3 may be considered a device ID report. The reader that receives A-IoT Msg3 transmits a response (e.g., an R2D response). The four-step access procedure is then completed. However, in the four-step access procedure, the reader that receives A-IoT Msg3 does not have to transmit a response (e.g., an R2D response).

[0080] For example, in an "inventory" use case such as checking the presence of an A-IoT device, each communication session includes only the above two-step access procedure or four-step access procedure. Note that the "inventory" use case is not limited to checking the presence of an A-IoT device.

[0081] For example, in the use case of "inventory + command", which includes checking the presence of an A-IoT device and issuing instructions to the A-IoT device, as shown in FIG. 10, each communication session involves sending an R2D command message and a D2R response after the above-mentioned two-step access procedure or four-step access procedure.

[0082] In addition, in the exchange including the access procedure shown in FIG. 10 etc., a contention-based access procedure such as slotted-ALOHA may be applied at least to A-IoT Msg1.

[0083] In an A-IoT communication session, a single A-IoT page may be sent to multiple devices. The multiple devices that receive the single A-IoT page may then continue with subsequent transmission / reception in the communication session. The subsequent transmission / reception in the devices may be at least one of sending an A-IoT Msg1, receiving an A-IoT Msg2, sending an A-IoT Msg3, receiving an R2D response, receiving an R2D command message, and sending a D2R response, as shown in FIG. 10 .

[0084] In the exchange including the access procedure shown in Fig. 10 etc., A-IoT paging, A-IoT Msg1, A-IoT Msg2, and A-IoT Msg3 may be abbreviated as paging, Msg1, Msg2, and Msg3, respectively. Also, A-IoT paging, A-IoT Msg1, A-IoT Msg2, and A-IoT Msg3 may be associated with names different from these names.

[0085] The message type may be any of A-IoT paging, A-IoT Msg1, A-IoT Msg2, A-IoT Msg3, R2D response, R2D command message, and D2R response. The R2D response may be omitted. The message type may be interchangeably referred to as message. The message may be interchangeably referred to as signal or information. For example, message transmission / reception may be interchangeably referred to as signal transmission / reception. The R2D command message may be referred to as R2D data.

[0086] The following description will be primarily based on an example of a four-step access procedure and "inventory+command" communication. However, the present disclosure is not limited to this. The present disclosure may be applied to a two-step access procedure or to "inventory" communication. An example of "inventory+command" communication corresponds to an example in which an R2D command message and a D2R response are sent / received after the four-step access procedure.

[0087] In the following description, one or more steps (e.g., processes) may be omitted (or skipped). For example, as described above, in the case of a two-step approach, the transmission / reception of A-IoT Msg3 may be omitted. Also, as described above, in the case of "inventory" communication, the R2D command message and D2R response may be omitted.

[0088] Any of the above message types may be transmitted by unicast, multicast, broadcast, or groupcast.

[0089] <Explanation of terms> Here, the terms used in relation to the A-IoT mentioned above will be explained.

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

[0091] Reader: A D2R receiver reader can be either a BS or a UE. A UE that acts as a reader may be called an intermediate UE. The R2D transmitter and D2R receiver may be the same node or different nodes.

[0092] R2D: Abbreviation for Reader-to-Device link. PRDCH: Abbreviation for physical R2D channel. D2R: Abbreviation for Device-to-Reader link. PDRCH: Abbreviation for physical D2R channel.

[0093] DT traffic: Abbreviation for Device Terminated traffic. DT traffic is, for example, traffic that sends a command from a reader to a device, and is terminated at the device.

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

[0095] Timing acquisition signal / preamble / midamble / postamble / synchronization signal can be interchanged.

[0096] ACK / NACK Feedback: The ACK / NACK feedback corresponding to R2D may be 1-bit information or a sequence-based signal, for example, a sequence-based signal in which sequence A represents an ACK and sequence B represents a NACK.

[0097] "ACK / NACK" has the following meaning: - ACK: Successful reception / decoding of the R2D message, successful completion of device operation corresponding to the R2D message. - NACK: Failure in reception / decoding of the R2D message, failure of device operation corresponding to the R2D message.

[0098] In this application, it is assumed that ACK / NACK feedback is transmitted via PHY (physical) layer signaling, although this application does not exclude ACK / NACK feedback transmitted via higher layer signaling.

[0099] ACK / NACK feedback is sent from the A-IoT device in response to the R2D data.

[0100] For example, the A-IoT device may transmit ACK / NACK feedback when it receives "inventory + command" R2D data, i.e., R2D data after contention resolution. Also, for example, the A-IoT device may transmit ACK / NACK feedback when it receives "command-only" R2D data, i.e., R2D data when contention is not resolved.

[0101] In addition, in this case, "sending ACK / NACK feedback" includes any of the following Alternative (Alt) methods: (Alt. 0) Sending an ACK when the R2D data is successfully decoded, and sending a NACK when the R2D data cannot be successfully decoded. (Alt. 1) Sending an ACK when the R2D data is successfully decoded, and not sending feedback when the R2D data cannot be successfully decoded. (Alt. 2) Not sending feedback when the R2D data is successfully decoded, and sending a NACK when the R2D data cannot be successfully decoded.

[0102] In addition, in this case, "not sending ACK / NACK feedback" means not sending feedback regardless of whether the R2D data was successfully decoded or not.

[0103] <Considerations> In a communication system including ambient IoT devices, a mechanism is needed for A-IoT devices to decide whether to send ACK / NACK feedback corresponding to R2D.

[0104] For example, in the case of DT, ACK / NACK feedback is useful as it allows the reader to know whether the R2D was successfully received by the device or not.

[0105] On the other hand, for DO-DTT, ACK / NACK feedback is not required since the PRDCH containing the R2D upper layer payload is for scheduling D2R data.

[0106] If necessary ACK / NACK feedback is not sent, the lost R2D retransmissions may not be performed and the ambient IoT devices may not be able to communicate properly, whereas sending unnecessary ACK / NACK feedback may waste resources, reducing D2R throughput or causing the ambient IoT devices to consume excessive power.

[0107] However, at present, there is no clear definition of how to control the transmission of ACK / NACK feedback corresponding to R2D in a communication system including ambient IoT devices.

[0108] Therefore, this embodiment proposes control regarding transmission of ACK / NACK feedback corresponding to R2D.

[0109] Note that, for illustrative purposes, the communication flow of the communication session shown in Figure 10 is considered in this discussion. Also, for illustrative purposes, the following description will be given assuming that the device is capable of monitoring only a single frequency band (or a single frequency bandwidth).

[0110] In this embodiment, "frequency," "frequency resource," and "frequency domain resource" may be interchangeable. Also, in this embodiment, "signal monitoring" may be interchangeable with "signal reception."

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0127] <Proposal> (Control of whether ACK / NACK feedback is transmitted) Based on instructions in R2D, the A-IoT device determines whether it will transmit corresponding ACK / NACK feedback to R2D.

[0128] The instructions in R2D may be sent via R2D preamble / L1 R2D control / upper layer R2D payload (upper layer R2D control / upper layer R2D data).

[0129] The following options are available for an A-IoT device to decide whether to send ACK / NACK feedback:

[0130] (Option 1: Message / Command Type) Based on the R2D message / command, the A-IoT device decides whether to send the corresponding ACK / NACK feedback to R2D.

[0131] (Option 1-1) For certain message / command types, the A-IoT device sends corresponding ACK / NACK feedback to the R2D.

[0132] (Option 1-2) For specific message / command types, the A-IoT device does not send ACK / NACK feedback corresponding to R2D. (Example 1) If R2D sends a paging message, the A-IoT device does not send ACK / NACK feedback corresponding to R2D. (Example 2) If R2D sends Msg2, the A-IoT device does not send ACK / NACK feedback corresponding to R2D.

[0133] (Options 1-3) The A-IoT device decides whether to send ACK / NACK feedback based on whether the R2D message / command is for DT or DO-DTT.

[0134] Note that DT means that the R2D message / command does not request a trigger, does not request a schedule of D2R data, and does not request a D2R upper layer payload.

[0135] DO-DTT also means that the R2D message / command is either a request for a trigger, a request for scheduling D2R data, or a request for D2R upper layer payload.

[0136] In the case of DT, the A-IoT device sends the corresponding ACK / NACK feedback to R2D.

[0137] In the case of DO-DTT, the A-IoT device does not send any ACK / NACK feedback corresponding to the R2D.

[0138] (Variations of Options 1-3) When an R2D is used for both DT and DO-DTT purposes, the A-IoT device may adopt the method described in any of the following Alternatives.

[0139] (Alt. 1) When R2D is used for both DT and DO-DTT purposes, the A-IoT device transmits corresponding ACK / NACK feedback to R2D. That is, as shown in case 1 in Fig. 11, the A-IoT device transmits ACK / NACK feedback as long as R2D transmits DT information.

[0140] (Alt. 2) When R2D is used for both DT and DO-DTT purposes, the A-IoT device does not transmit ACK / NACK feedback corresponding to R2D. That is, as shown in case 2 in Fig. 11 , as long as R2D transmits DO-DTT information, the A-IoT device does not transmit ACK / NACK feedback regardless of whether DT information is present or not.

[0141] (Option 2: Cast Type) The A-IoT device decides whether to send the corresponding ACK / NACK feedback to R2D based on the cast type.

[0142] The cast types include unicast, groupcast, and broadcast.

[0143] (Option 2-1) For a specific cast type, the A-IoT device sends a corresponding ACK / NACK feedback to R2D. (Example) If the cast type is unicast, the A-IoT device sends a corresponding ACK / NACK feedback to R2D.

[0144] (Option 2-2) For a specific cast type, the A-IoT device does not send ACK / NACK feedback corresponding to R2D. (Example) If the cast type is groupcast or broadcast, the A-IoT device does not send ACK / NACK feedback corresponding to R2D.

[0145] (Option 3: R2D Format Type) The A-IoT device determines whether to send ACK / NACK feedback corresponding to R2D based on the R2D format type.

[0146] The R2D format types include a type that transmits only L1 R2D control, a type that transmits only upper layer R2D payload, and a type that transmits both L1 R2D control and upper layer R2D payload.

[0147] (Option 3-1) For a specific R2D format type, the A-IoT device transmits ACK / NACK feedback corresponding to R2D. (Example) If the R2D format type is a type that transmits both L1 R2D control and upper layer R2D payload, the A-IoT device transmits ACK / NACK feedback corresponding to R2D.

[0148] (Option 3-2) For a specific R2D format type, the A-IoT device does not transmit ACK / NACK feedback corresponding to R2D. (Example) If the R2D format type is a type that transmits only L1 R2D control or a type that transmits only upper layer R2D payload, the A-IoT device does not transmit ACK / NACK feedback corresponding to R2D.

[0149] (Option 4: CRC (Cyclic Redundancy Check)) If a CRC is attached to R2D, the A-IoT device transmits ACK / NACK feedback corresponding to R2D, and if a CRC is not attached to R2D, the A-IoT device does not transmit ACK / NACK feedback.

[0150] (Other) The A-IoT device may explicitly indicate to the reader whether or not to send ACK / NACK feedback corresponding to the R2D.

[0151] The A-IoT device may send ACK / NACK feedback only if the target / destination of the R2D is its own device, in which case the A-IoT device will not send ACK / NACK feedback if the target / destination of the R2D is not its own device.

[0152] <Variation 1 of Proposal 1> As described above, in this case, "sending ACK / NACK feedback" includes any of the following methods: Alt. 0 / 1 / 2. (Alt. 0) Send an ACK if the R2D data is successfully decoded, and send a NACK if the R2D data is not successfully decoded. (Alt. 1) Send an ACK if the R2D data is successfully decoded, and do not send feedback if the R2D data is not successfully decoded. (Alt. 2) Do not send feedback if the R2D data is successfully decoded, and send a NACK if the R2D data is not successfully decoded.

[0153] Alt. 1 and Alt. 2 require fewer ACK or NACK transmissions than Alt. 0, which allows for reduced power consumption.

[0154] In the case of Alt. 1 or Alt. 2, the A-IoT device can be in a "sleep" or "off" state during TX resources, where TX and / or RX are not performed, RF energy harvesting may be performed, and timing counting may or may not be performed.

[0155] In Alt. 1, if the reader does not receive an ACK feedback, it will interpret it as a NACK and retransmit R2D. That is, Alt. 1 allows the reader to reliably retransmit R2D if the A-IoT device fails to successfully decode the R2D data.

[0156] In wireless communication, the number of times that R2D cannot be decoded correctly is usually far less than the number of times that R2D can be decoded correctly, so Alt. 2 can reduce power consumption more than Alt. 1.

[0157] The above Alt. 1 / 2 may be applied as an alternative, with the condition that it applies when the A-IoT device determines whether to send ACK / NACK feedback corresponding to R2D based on the R2D upper layer payload.

[0158] Note that "successfully decoding R2D data" may mean successfully decoding the R2D upper layer payload, or may mean successfully decoding the R2D PHY layer payload.

[0159] <Variation 2 of Proposal 1> When an A-IoT device transmits ACK / NACK feedback, the following options are available for determining which of the above Alt. 0 / 1 / 2 methods to use.

[0160] (Option 1: Message / Command Type) Based on the R2D message / command, the A-IoT device may decide which method (Alt. 0 / 1 / 2) to use to send the corresponding ACK / NACK feedback to R2D.

[0161] (Option 1-1) For specific message / command types, the A-IoT device sends corresponding ACK / NACK feedback to R2D via a specific method in Alt. 0 / 1 / 2.

[0162] (Option 1-2) The A-IoT device sends the corresponding ACK / NACK feedback to R2D in a specific manner in Alt. 0 / 1 / 2 based on whether the R2D message / command is for DT or DO-DTT.

[0163] (Option 2: Cast Type) The A-IoT device may determine which method, Alt. 0 / 1 / 2, to use to send ACK / NACK feedback corresponding to R2D based on the cast type.

[0164] (Option 2-1) In the case of a specific cast type, the A-IoT device sends corresponding ACK / NACK feedback to R2D using a specific method in Alt. 0 / 1 / 2.

[0165] (Option 3: R2D Format Type) The A-IoT device may determine whether to send ACK / NACK feedback corresponding to R2D using Alt. 0 / 1 / 2 based on the R2D format type.

[0166] (Option 3-1) For a specific R2D format type, the A-IoT device sends the corresponding ACK / NACK feedback to the R2D using a specific method in Alt. 0 / 1 / 2.

[0167] (Other) When transmitting ACK / NACK feedback corresponding to R2D, the A-IoT device may explicitly indicate to the reader which of Alt. 0 / 1 / 2 methods to apply.

[0168] When the A-IoT device determines which of Alt. 0 / 1 / 2 to apply based on the R2D upper layer payload, if the A-IoT device fails to successfully decode the R2D upper layer payload, it may take one of the following Alt.: (Alt. a) The A-IoT device sends NACK feedback. (Alt. b) The A-IoT device does not send ACK / NACK feedback.

[0169] (Effect) According to the above proposal, it is possible to appropriately control whether or not to transmit ACK / NACK feedback corresponding to R2D, so that R2D required for the A-IoT device is retransmitted, a decrease in D2R throughput is prevented, and power consumption of the A-IoT device can be reduced.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0183] Furthermore, for example, the communication unit may use the above frequency resources to perform communication involving an A-IoT device.

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

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

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

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

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

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

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

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

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

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

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

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

[0196] For example, the receiver 201 may receive information regarding frequency resources to be used for communication involving the A-IoT device from the base station 10 or the network of intermediate UEs, and the controller 203 may determine the frequency resources to be used for communication involving the A-IoT device based on the information received by the receiver 201. The frequency resources to be used for communication involving the A-IoT device may be one frequency resource, a plurality of contiguous frequency resources, or a plurality of non-contiguous frequency resources, and may include a first frequency resource used in a first frequency hop and a second frequency resource used in a second frequency hop.

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

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

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

[0200] Functions include, but are not limited to, judgment, determination, judgment, 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.

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

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

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

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

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

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

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

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

[0209] 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. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0252] "First," "Second" Any reference to an element using a designation 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 in some way precede the second element.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A device with lower complexity than an NB-IoT (Narrow Band Internet of Things) device, comprising: a receiving unit that receives a received signal from a wireless communication device; a control unit that controls the transmission of an acknowledgement signal corresponding to the received signal; and a transmitting unit that transmits the acknowledgement signal to the wireless communication device, wherein the control unit determines whether or not to transmit the acknowledgement signal based on an instruction in the received signal.

2. The device according to claim 1, wherein the control unit determines not to transmit the acknowledgement signal if the received signal is a paging message or Msg2.

3. The device according to claim 1, wherein the control unit determines to transmit the acknowledgment signal if the message / command of the received signal is DT (device terminated), and not to transmit the acknowledgment signal if the message / command is DO-DTT (device originated - device terminated triggered).

4. The device according to claim 1, wherein the control unit determines to transmit the acknowledgment signal if the cast type of the received signal is unicast, and not to transmit the acknowledgment signal if the cast type is groupcast or broadcast.

5. A communication method in which a device with lower complexity than an NB-IoT (Narrow Band Internet of Things) device receives a received signal from a wireless communication device, determines whether or not to send an acknowledgement signal corresponding to the received signal based on an instruction in the received signal, and sends the acknowledgement signal to the wireless communication device.

Images