Device and communication method

Abstract

To provide an A-IoT device and a communication method that clarify what values / settings are assumed when specific control information is not notified.SOLUTION: A device having lower complexity than an NB-IoT device includes a receiving unit that receives an R2D signal from a wireless communication apparatus and a control unit that, if control information is not present or is not specified in the R2D signal, identifies the control information using a predefined value / setting or a specified value.SELECTED DRAWING: Figure 14

Description

[Technical Field]

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

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

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

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

[0005] For control information indicated as L1 control information, some information fields may or may not need to be indicated, e.g., depending on the message type. That is, the required payload size may vary, e.g., depending on the message type. For example, in the case of unicast, a single time-frequency resource needs to be indicated for D2R transmission, while multiple time / frequency domain resources need to be indicated for Msg1 transmission with contention-based random access. Similarly, for control information indicated at higher layers, some information fields may or may not need to be indicated, or may not even be indicated, depending on the message type.

[0006] Therefore, if certain control information is not indicated or is not present, it is necessary to make clear what value / setting the device should assume, i.e., to specify a fallback / default setting, otherwise misunderstandings may occur between the reader and the device.

[0007] Therefore, the present disclosure contributes to providing an A-IoT device and a communication method that clarify what values / settings are assumed when specific control information is not notified.

[0008] A device according to one embodiment of the present disclosure is a device of lower complexity than an NB-IoT (Narrow Band Internet of Things) device, and includes a receiving unit that receives an R2D signal from a wireless communication device, and a control unit that, when control information is not present or is not specified in the R2D signal, identifies the control information using a predefined value / setting or a specified value. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure. [Figure 2] FIG. 1 is a diagram illustrating Topology 1. [Figure 3] FIG. 10 is a diagram illustrating Topology 2. [Figure 4] FIG. 10 is a diagram illustrating topology 3 in DL support. [Figure 5] FIG. 10 is a diagram illustrating Topology 3 in UL support. [Figure 6] FIG. 10 is a diagram illustrating Topology 4. [Figure 7] FIG. 1 is a diagram illustrating backscatter transmission. [Figure 8] 1 is a diagram showing an example of a candidate topology for CW / R2D / D2R transmission in topology 1. [Figure 9] FIG. 10 is a diagram illustrating an example of a candidate topology for CW / R2D / D2R transmission in topology 2. [Figure 10] A diagram showing an example of an access procedure for an A-IoT device. [Figure 11] A diagram showing steps in the access procedure for an A-IoT device. [Figure 12] A diagram showing an example of a four-step (or three-step) random access procedure for an A-IoT device. [Figure 13] A diagram showing an example of a two-step random access procedure for an A-IoT device. [Figure 14]FIG. 10 is a diagram illustrating an example of control information of a PRDCH. [Figure 15] FIG. 10 is a diagram illustrating an example of association between the M value of R2D and the D2R chip period. [Figure 16] 10 is a diagram showing an example of an offset between R2D, the previous Msg1, and the next Msg1. [Figure 17] A diagram showing an example of association of offsets between the information bit period of D2R and the start timing of the previous Msg1 and the next Msg1. [Figure 18] FIG. 2 is a block diagram illustrating an example of a configuration of a base station according to an embodiment of the present disclosure. [Figure 19] FIG. 1 is a block diagram illustrating an example of a configuration of a device according to an embodiment of the present disclosure. [Figure 20] FIG. 2 is a diagram illustrating an example of a hardware configuration of a base station and a device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0039] The wireless communication system 1 (wireless communication network) may include a base station, a support node, an intermediate node, and / or a terminal (UE 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0083] · The timing acquisition signal / preamble / midamble / postamble / synchronization signal can be replaced with each other.

[0084] <Rel-19 compliant WID> A new WID (Work Item Description) "New Work Item: Solutions for Ambient IoT (Internet of Things) in NR" (RP-243326) (Non-Patent Document 6) was approved in Rel-19. This WID shows the guidelines for promoting the standardization of A-IoT technology in NR, and Chapter 4 is described as follows.

[0085] General scope Definitions provided in TR 38.848, TR 38.769, and decisions in the RAN working group in Rel-19 SI in the RAN WG are incorporated into this WI, and the following are exclusive general scopes: A. The overall goal is to standardize the following ambient IoT devices: Device 1: Peak power consumption ~1 μW, energy storage, RF envelope detector receiver, initial sampling frequency offset (SFO) up to 10 X ppm, no amplification of R2D and D2R within the device, and D2R transmission of the device is backscattered against a carrier provided externally B.D1T1 (Deployment scenario 1 with connectivity topology 1) - Deployment scenario 1 using topology 1 according to B The licensed spectrum in C.FR1 operates in a frequency division duplex (FDD) scheme, with R2D being used in the downlink (DL) spectrum and D2R and CW being used in the uplink (UL) spectrum. D. Spectrum deployment in the band for NR and standalone spectrum deployment, A-IoT base station (BS) is installed indoors E. Traffic types DO-DTT, DT for rUC1 (indoor inventory) and rUC4 (indoor command) Waveform 1 carrier transmission only, no hopping, for the following cases based on F.TR 38.769 Regarding cases 1 to 4 of D1T1-B G.Proximity determination only according to Solution 1 of TR 38.769 (Un)availability of devices via H.TR 38.769 direction 1 only

[0086] Within a general scope, the following objectives are set: RAN1 range: PRDCH and PDRCH are the only physical channels in R2D and D2R, respectively. R2D and D2R signals Multiplexing / multiple connections in R2D are only TDMA (Time Division Multiple Access), while D2R is only TDMA and FDMA (Frequency Division Multiple Access). R2D only supports OOK (On-Off-Keying)-4 modulation and provides a solution for CP (Cyclic Prefix) processing, while D2R backscatter only supports OOK and BPSK (Binary Phase Shift Keying) modulation. The R2D transmission supports only the Manchester line code in TR 38.769 The D2R transmission supports the following: · Manchester line code in TR 38.769, or no line code (select either) · Corresponding small frequency shift method according to the options of TR 38.769 R2D does not support FEC (Forward Error Correction Code). D2R supports only convolutional codes with a generating polynomial according to TS 36.212 (unless RAN1 decides to use other generating polynomials by RAN1#120bis). PRDCH and PDRCH support transmission without CRC (Cyclic Reduncancy Check) and support transmission with CRC according to the generating polynomials of 6-bit CRC and 16-bit CRC in TS 38.212 (unless RAN1 decides to use other generating polynomials by RAN1#120bis). Whether to use a CRC of which length or no CRC is determined by RAN1. D2R supports physical layer repeated transmission (repetition). R2D does not support physical layer repeated transmission.

[0087] <Access Procedure for A-IoT Devices> In an A-IoT communication session, the access procedure for an A-IoT device (hereinafter simply referred to as a device) is executed. As access procedures for A-IoT devices, two approaches, namely a two-step approach and a four-step approach, are being considered.

[0088] Figure 10 is a diagram showing an example of an access procedure for an A-IoT device. Figure 10 shows the exchange of signals between one leader and one device. The horizontal axis of Figure 10 indicates the time axis. Figure 10 shows an exchange including a two-step access procedure and a four-step access procedure.

[0089] In the two-step access procedure, the reader sends an A-IoT paging message. The A-IoT paging message corresponds to the first R2D transmission in an A-IoT communication session. The device that receives the A-IoT paging message sends a message called A-IoT Msg1 to the reader. In the two-step access procedure, A-IoT Msg1 contains information that identifies the device (e.g., device ID). A-IoT Msg1 may be considered a device 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 addressed to the device identified by the device ID included in A-IoT Msg1. A-IoT Msg2 contains information indicating contention resolution. A-IoT Msg2 may be considered contention resolution. The two-step access procedure is then completed.

[0090] In the four-step access procedure, the reader sends an A-IoT paging message. A device that receives the A-IoT paging message sends a message called A-IoT Msg1 to the reader. In the four-step access procedure, A-IoT Msg1 contains 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 A-IoT reader sends A-IoT Msg2, which contains the random ID contained in A-IoT Msg1. A-IoT Msg2 contains information indicating contention resolution. A-IoT Msg2 may be considered contention resolution. The device receives A-IoT Msg2 and sends A-IoT Msg3 to the reader. For example, if the random ID of the received A-IoT Msg2 matches the random ID of the sent A-IoT Msg1, the device sends A-IoT Msg3 to the reader. In the four-step access procedure, A-IoT Msg3 contains information that identifies the device (e.g., device ID). A-IoT Msg3 may be considered a device ID report. A reader that receives A-IoT Msg3 sends a response (e.g., R2D response). The four-step access procedure is then completed. However, in the four-step access procedure, a reader that receives A-IoT Msg3 does not have to send a response (e.g., R2D response).

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

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

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

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

[0095] In addition, in the exchanges including the access procedures shown in Figure 10 etc., A-IoT Paging, A-IoT Msg1, A-IoT Msg2, A-IoT Msg3 may be abbreviated as Paging, Msg1, Msg2, Msg3, respectively. Furthermore, A-IoT Paging, A-IoT Msg1, A-IoT Msg2, A-IoT Msg3 may be associated with names different from these names.

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

[0097] The following description will mainly focus 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 a four-step access procedure is followed by transmission / reception of an R2D command message and a D2R response.

[0098] Also, 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.

[0099] It should be noted that any of the above message types may be transmitted by unicast, multicast, broadcast, or groupcast.

[0100] <Procedures based on the agreement> Rel-19 considers inventory and command use cases as well as DO-DTT and DT traffic, and for these use cases / traffic types, steps 1 and 2 below are considered.

[0101] 1. Inventory only Step A: The reader sends an A-IoT page to the device. Step B: The device sends its device ID to the reader (via Random Access (RA) or without RA).

[0102] 2. Inventory and command Step A: The reader sends an A-IoT page to the device. Step B: The device sends its device ID to the reader (via Random Access (RA) or without RA). Step C1: The reader sends data to the device (e.g., R2D command). Step C2: The corresponding device sends data (e.g., feedback) to the reader. Note that it is unclear whether step C2 is optional.

[0103] FIG. 11 is a related diagram in TR 38.769 (Non-Patent Document 7).

[0104] <Random Access (RA) based on agreements> Regarding random access, the following steps 1 and 2 are being considered:

[0105] 1. 4 steps (or 3 steps) (see Figure 12) A-IoT Msg1: The device sends its ID to the reader. The ID is a random ID generated by the device. The size of the random ID is fixed, 16 bits. A-IoT Msg2: The reader echoes the ID received in Msg1. A-IoT Msg3: The device sends its device ID and / or other upper layer data (upon upper layer request). If the device receives Msg2 containing the same random ID as Msg1, it considers the conflict resolution successful. "Msg4" (i.e., subsequent R2D transmissions after a D2R transmission) does not always need to be sent with random access. "Msg4" can be considered to handle Msg3 transmission failures (due to various reasons).

[0106] Step 2.2 (See Figure 13) A-IoT Msg1: The device transmits its device ID and / or other upper layer data (as requested by the upper layer). A random ID (fixed 16 bits) may additionally be included in Msg1. A-IoT Msg2: If Msg1 contains a random ID, the reader echoes the ID received in Msg1.

[0107] In addition, at the 3GPP RAN2#126 and #127 meetings, the following procedures were agreed upon in relation to the above procedures.

[0108] [3GPP RAN2#126 Agreement on "4-Step" RA] 1. A-IoT Msg1: The device sends its ID to the reader. The ID is a random ID generated by the device (how it is generated is undetermined, e.g. randomly or based on the device ID). The ID size is undetermined. This does not exclude other information agreed upon in RAN1. 2. A-IoT Msg2: The reader echoes the ID received in Msg1. Msg2 may contain further information based on the agreement of RAN1. 3. A-IoT Msg3: The device sends its device ID and / or other upper layer data (as requested by the upper layer). 4. If the device receives Msg2 containing the same random ID as Msg1, it considers the contention resolution successful. RAN2 assumes that the size of the random ID in Msg1 is sufficient for contention resolution purposes. 5. "Msg4" (i.e., subsequent R2D transmissions after a D2R transmission) does not always need to be transmitted via random access. "Msg4" can be considered to handle Msg3 transmission failures (due to various reasons). The use / existence of "Msg4" can be further discussed. RAN2 does not use the term "Msg4" for further discussion of random access.

[0109] [3GPP RAN2#126 Agreement on 2-Step CB RA] 1. A-IoT Msg1: The device sends its device ID and / or other higher layer data (as required by the higher layer). It is undetermined what the device ID will be. It is undetermined whether an additional random ID is required. This does not preclude other information agreed upon in RAN1. 2. A-IoT Msg2: The reader may echo some information from Msg1. It is undetermined what that some information is. The usage / existence of "Msg2" can be further discussed.

[0110] [3GPP RAN2#127 Agreement (3-step CBRA)] For 3-step CBRA (Contention-Based Random Access) support, the fixed random ID size is 16 bits. The ID is generated randomly. -Indication of D2R failure / success will be considered. It is not yet decided whether the indication of D2R failure / success will be implicitly or explicitly indicated, and in what cases it will be required. It is also not yet decided whether the indication of D2R failure / success will only be applied in some cases.

[0111] [3GPP RAN2#127 Agreement (2-step CBRA)] For 2-step CBRA, the RAN2 specification supports Msg2. Whether it is required is up to the reader. It is not yet decided when it is required. For 2-step CBRA (when Msg2 is required), the random ID (fixed 16 bits) is also included in A-IoT Msg1 and echoed in A-IoT Msg2. If there are devices that only support 2-step RA, it is not yet decided whether other optimizations will be required for such devices. In contention-free access, A-IoT devices will directly send higher layer data (e.g., device ID) in the first D2R message after being triggered (i.e., skipping contention resolution Msg1 / 2). It remains to be determined whether short AS IDs will also be included in the message, and what type of IDs will be included for scheduling purposes. · It is yet to be determined if the leader will assign AS IDs for scheduling purposes.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0129] <Proposal 1> [assignment] For control information indicated as L1 control information, some information fields may or may not need to be indicated, e.g., depending on the message type. This means that the required payload size may vary, e.g., depending on the message type. For example, in the unicast case, a single time-frequency resource needs to be indicated for D2R transmission, while multiple time / frequency domain resources need to be indicated for Msg1 transmission with contention-based random access.

[0130] Similarly, in the case of control information indicated at higher layers, depending on, for example, the message type, some information fields may or may not need to be indicated, and some information fields may not be indicated.

[0131] Therefore, if certain control information is not indicated or is not present, it is necessary to make clear what value / setting the device should assume, i.e., to specify a fallback / default setting, otherwise misunderstandings may occur between the reader and the device.

[0132] Therefore, Proposal 1 describes a proposal to clarify what values / settings are assumed when specific control information is not notified.

[0133] [Proposal details] In proposal 1, if a particular control piece of information is not present / specified, a predefined value / setting is used, otherwise the specified value is used.

[0134] <Proposal 1-1> As shown in the following Examples 1 to 2, if the fields related to the R2D / PRDCH scheduling information and / or the D2R / PDRCH scheduling information do not exist / are not specified, predefined values / settings or specified values ​​are used as shown in the following (1-1) to (2-12).

[0135] [Example 1] When the field related to R2D / PRDCH scheduling information (scheduling information used for R2D / PRDCH scheduling) does not exist / is not specified

[0136] (Premise) R2D is a paging, a non-paging R2D message used to determine Msg1 resources, an R2D message following Msg2 or Msg3, an R2D command, etc. The control information used for scheduling R2D is present at the beginning of the same PRDCH or at the beginning of another PRDCH (see Figure 14).

[0137] (1-1) Target Device ID If this field is not present / specified, the device may assume that the scheduled R2D message type is a CBRA paging, a CFRA paging, or a non-paging R2D message used to determine Msg1 resources.

[0138] (1-2) Transaction ID If this field is not present / specified, the device may assume the value specified in the specification (e.g., in the 3GPP standard) (e.g., index is 0, index is 1, etc.).

[0139] (1-3) Chip duration If this field is not present / specified, the device may assume certain values ​​as indicated in options 1-3-1 to 1-3-2 below.

[0140] (Option 1-3-1) Specified value (2, 6, 12, or 24)

[0141] (Option 1-3-2) The same chip duration is used as for the PRDCH which carries control information.

[0142] (1-4) Message type If this field is not present / specified, the device may assume a particular message type as specified in the specification.

[0143] (1-5) TBS (number of information bits) of the physical layer, SDU size of the MAC layer, PDU size of the MAC layer If this field is not present / specified, the device may assume a specific size as indicated in options 1-5-1 to 1-5-3 below.

[0144] (Option 1-5-1) Specified value (8-bit, 16-bit, etc.)

[0145] (Option 1-5-2) The value associated with the message type

[0146] For example, if the message type is specified as Paging, the message size is assumed to be x bits; if the message type is specified as an R2D message used to determine Msg1 resources, the message size is assumed to be y bits; if the message type is specified as Msg2, the message size is assumed to be z bits.

[0147] (Option 1-5-3) The device assumes that the end of the R2D is indicated by the postamble.

[0148] [Example 2] When the field related to D2R / PDRCH scheduling information (scheduling information used for D2R / PDRCH scheduling) does not exist / is not specified

[0149] (Premise) D2R includes Msg1, Msg3, D2R after random access, D2R for data transfer, D2R for R2D reception feedback, etc.

[0150] (2-1) Target Device ID If this field is not present / specified, the device may assume that the message type for the scheduled D2R is Msg1 (for both CBRA and CFRA), or Msg1 for CBRA (Contention Based Random Access).

[0151] (2-2) Transaction ID If this field is not present / specified, the device MAY assume the value specified in the specification (e.g., index is 0, index is 1, etc.).

[0152] (2-3) Physical layer TBS, MAC layer SDU size, MAC layer PDU size If this field is not present / specified, the device may assume a specific size as indicated in options 2-3-1 to 2-3-2 below.

[0153] (Option 2-3-1) Values ​​specified in the specification (e.g. 8-bit, 16-bit, etc.)

[0154] (Option 2-3-2) The value associated with the message type

[0155] For example, if the message type of the CBRA is Msg1, the message size is assumed to be 16 bits. If the message type of the CFRA is Msg1, the message size is assumed to be y bits. If the message type is Msg3, the message size is assumed to be z bits.

[0156] (2-4) Chip duration: T chip If this field is not present / specified, the device may assume certain values ​​as indicated in options 2-4-1 to 2-4-3 below.

[0157] (Option 2-4-1) Values ​​specified in the specifications (e.g., 266.66 μs, 133.33 μs, 66.67 μs, etc.)

[0158] (Option 2-4-2) Same chip duration as previous D2R transmission

[0159] (Option 2-4-3) The association between R2D chip periods is specified and the value associated with the R2D that schedules the D2R is used.

[0160] For example, there is a one-to-one correspondence between the R2D chip duration and the D2R chip duration. An R2D chip duration M=2 corresponds to a D2R chip duration of 33.33 μs, an R2D chip duration M=6 corresponds to a D2R chip duration of 11.11 μs, an R2D chip duration M=12 corresponds to a D2R chip duration of 5.56 μs, and an R2D chip duration M=24 corresponds to a D2R chip duration of 2.78 μs.

[0161] (2-5) Minute frequency shift coefficient R If this field is not present / specified, the device may assume the specific values ​​indicated in the following options 2-5-1 to 2-5-2.

[0162] (Option 2-5-1) Values ​​specified in the specification (e.g. R=1, R=2, etc.)

[0163] (Option 2-5-2) The same small frequency shift coefficient R as in the previous D2R transmission

[0164] (2-6) Information bit duration T b If this field is not present / specified, the device may assume the specific values ​​indicated in the following options 2-6-1 to 2-6-2.

[0165] (Option 2-6-1) No repetition (i.e., repetition factor is 1)

[0166] (Option 2-6-2) Same information bit duration as previous D2R transmission

[0167] (2-7) Repetition factor for block-level repetition If this field is not present / specified, the device may assume certain values ​​as indicated in options 2-7-1 to 2-7-2 below.

[0168] (Option 2-7-1) No repetition (i.e., repetition factor is 1)

[0169] (Option 2-7-2) Same repetition factor as the previous D2R transmission

[0170] (2-8) FEC coding rate, whether FEC is applied If this field is not present / specified, the device may assume certain values ​​as indicated in options 2-8-1 to 2-8-2 below.

[0171] (Option 2-8-1) FEC does not apply

[0172] (Option 2-8-2) Same coding rate as previous D2R transmission

[0173] (2-9) Time offset from R2D scheduling If this field is not present / specified, the device may assume certain values ​​as indicated in options 2-9-1 to 2-9-3 below.

[0174] (Option 2-9-1) T specified as the offset between R2D and Msg1 offset1

[0175] (Option 2-9-2) A specific time interval as defined in the specification

[0176] (Option 2-9-3) Same time offset as the previous D2R transmission

[0177] (2-10) Number of times Msg1 is transmitted in CBRA (e.g., X=1 or 2) If this field is not present / specified, the device may assume that the number of times Msg1 is sent is 1.

[0178] (2-11) X-amble (D2R preamble or midamble) sequence length If this field is not present / specified, the device may assume certain values ​​as indicated in the following options 2-11-1 to 2-11-2.

[0179] (Option 2-11-1) Specified value (7-bit or 31-bit sequence)

[0180] (Option 2-11-2) Same time offset as the previous D2R transmission

[0181] (2-12) Spacing between X-ambles (preamble or midamble of D2R) If this field is not present / specified, the device may assume the following as indicated in options 2-12-1 to 2-12-3.

[0182] (Option 2-12-1) Assume no midamble.

[0183] (Option 2-12-2) Assume a specific period as specified in the specification.

[0184] (Option 2-13-3) Assume the same period as the previous D2R transmission.

[0185] <Proposal 1-2> The required field size for a particular control information varies depending on the message type, i.e., the value / setting restrictions applicable to a particular control information may be specified depending on the message type.

[0186] [Example] (1) TBS, message size The TBS and message size may be specified according to the message type, for example, as in the following examples 1-1 to 1-4. (Example 1-1) Msg1 for CBRA (Contention Based Random Access) may be limited to a maximum of 16 bits, for example, which corresponds to 1 bit indicating the TBS / message size.

[0187] (Example 1-2) Msg1 for CFRA (Contention Free Random Access) may be limited to a maximum of, for example, 128 bits, 256 bits, etc. This corresponds to 5 and 6 bits indicating the TBS / message size.

[0188] (Example 1-3) Msg3 may be limited to a maximum of, for example, 128 bits, 256 bits, etc. This corresponds to 5 and 6 bits indicating the TBS / message size.

[0189] (Example 1-4) The R2D message used to determine the Msg1 resource may be limited to, for example, a maximum of 8 bits, 16 bits, etc. This corresponds to 0 bits (i.e., no indication field required) and 1 bit indicating the TBS / message size.

[0190] (2) D2R information bit length T b Msg1 of the CBRA may be limited to at least large values ​​such as 133.33 μs, 66.67 μs, 33.33 μs, 16.67 μs, 8.33 μs, 4.17 μs.

[0191] Although the message size of Msg1 in CBRA is small at 16 bits, it may be the first transmission from a device, so coverage must be ensured. Therefore, a large information bit length can be used to help ensure coverage.

[0192] (3) D2R chip duration T chip Msg1 of the CBRA may be limited to at least large values ​​such as 266.66 μs, 133.33 μs, 66.67 μs, 33.33 μs, 16.67 μs, 8.33 μs, 4.17 μs.

[0193] Although the message size of Msg1 in CBRA is small (16 bits), it may be the first transmission from a device, so coverage must be ensured. Therefore, a large information bit length can be used to help ensure coverage.

[0194] (Effects of Proposal 1) According to Proposal 1, if the fields related to R2D / PRDCH scheduling information and / or D2R / PDRCH scheduling information are not present / specified, the A-IoT device uses predefined or specified values / settings. This allows the A-IoT device to clarify what values / settings to assume even if specific control information is not signaled.

[0195] <Proposal 2> [assignment] In wireless communications, configuration based on control information requires a trade-off between notification flexibility and signaling overhead. That is, the more flexible the notification, the greater the signaling overhead for notification. Therefore, as a means for reducing the notification overhead, a technique is needed that limits notification flexibility depending on the content specified by other control information.

[0196] Here, when restricting this flexibility, the applicable values ​​for specific control information may differ depending on the conditions. For example, if the same or similar chip durations are used between a receive-to-transmit delay (R2D) and a corresponding transmit-to-receive delay (D2R), the applicable values ​​for the D2R chip duration may be restricted depending on the corresponding R2D chip duration.

[0197] [Proposal details] In Proposal 2, an example will be given to explain a case where applicable values / settings are specified for other control information depending on the value of the specified control information.

[0198] [Example] (1) Association of R2D chip periods with D2R chip periods Depending on the R2D chip period (hereinafter referred to as the M value), the range of the corresponding D2R chip period may be defined.

[0199] For example, if the M value of R2D is set as follows, the terminal may limit the corresponding D2R chip period to the following range (see FIG. 15): M=2, D2R chip period range: approximately 133.33μs to 8.33μs M=6, D2R chip period range: approximately 66.67μs to 4.17μs M=12, D2R chip period range: approximately 16.67μs to 1.04μs M=24, D2R chip period range: approximately 8.33 μs to 0.69 μs or 0.52 μs

[0200] (Note) The ranges of the D2R chip period shown above are examples, and the present disclosure is not limited to these, and other ranges of values ​​may be applied.

[0201] In this way, by limiting the range of applicable D2R chip periods using the R2D M value, it is possible to reduce the total number of usable D2R chip period values ​​overall, and also reduce the number of bits required to notify this information. For example, if all values ​​from 133.33 μs to 0.52 μs were allowed as D2R chip period values, a bit length of 4 bits would be required, but by limiting the range according to the M value as described above, it is possible to express D2R chip periods with fewer bits.

[0202] (2) D2R information bit period and T offset2 Association with The offset between the start timing of the previous Msg1 and the start timing of the next Msg1 (hereinafter referred to as T offset2 ), the information bit period of D2R (T b ) the correspondence relationship may be defined according to (see FIG. 16).

[0203] For example, the terminal is b and T offset2 By associating with T offset2 and then transmit Msg1 (see FIG. 17). T b is in the range of 266.67μs to 33.33μs:T offset2 =z1μs T b is in the range of 33.33μs to 11.11μs:T offset2 =z2μs T b is in the range of 11.11μs to 4.17μs:T offset2 =z3μs T b is in the range of 4.17μs to 1.04μs:T offset2 =z4μs

[0204] (Note) Each of the above T offset2 The corresponding values ​​are merely examples, and the present disclosure is not limited thereto, and other values ​​and ranges may be applied.

[0205] Also, the duration of Msg1 is T b × TBS (TBS: number of information bits). b The change in the length and T of Msg1 offset2 The setting value of will be affected.

[0206] (Effects of Proposal 2) According to Proposal 2, by restricting the values / settings applicable to other control information based on existing control information, it is possible to reduce the number of bits required for notification while maintaining flexible communication control.

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

[0208] <Base station configuration> 18 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. 19) wirelessly. The base station 10 may be a terminal (an intermediate UE communicating with the device 20) or a CW node.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0233] 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 the intermediate UE, 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 a single frequency resource, multiple contiguous frequency resources, or multiple non-contiguous frequency resources, and may include a first frequency resource used in a first frequency hop and a second frequency resource used in a second frequency hop.

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

[0235] For example, the control unit may determine whether the chip duration of the R2D data is determined from the R2D clock acquisition portion by a code point in the chip duration field of the R2D control of the R2D signal.

[0236] For example, the control unit may determine that if the chip duration field of the R2D control of the R2D signal indicates a chip duration greater than or equal to Y, the chip duration indicated by the R2D control is the same as the chip duration determined from the clock acquisition portion.

[0237] For example, the control unit may determine whether the chip duration of the R2D data is determined from the R2D clock acquisition portion or the chip duration field of the R2D control, depending on another field of the R2D preamble / R2D control.

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

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

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

[0241] In the present disclosure, the term "apparatus" may be interchangeable with any two terms selected from a set of terms such as "circuit," "device," "unit," "module," "chip," "means," etc. The hardware configurations of the base station 10 and the device 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

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

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

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

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

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

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

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

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

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

[0251] <Information notification, signaling> The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and 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) and System Information Block (SIB))), other signals, or a combination of at least two of these. Note that the physical layer signaling may be referred to as Layer 1 (L1) control information. The MAC signaling may be referred to as a MAC Control Element (CE) or a MAC Protocol Data Unit (PDU), for example. Furthermore, the RRC signaling may be referred to as an RRC message or an information element (IE) in the RRC message. The RRC message may be, for example, a message used for controlling an RRC connection (for example, setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, a measurement report, or notification of a terminal's capabilities, or may be an information element within the message. Furthermore, notification of information may be explicit or implicit. Note that explicit notification of certain information means notification of the certain information itself, and implicit notification of certain information may mean notification of information other than the certain information, or may mean that the certain information is considered to have been notified when a certain condition is satisfied.Furthermore, notification of information may include not only notification between the same layers of different devices (e.g., between a lower layer or an upper layer of the base station 10 and the device 20) but also notification between different layers in the same or different devices (e.g., between a lower layer and an upper layer in the base station 10 or the device 20). Furthermore, notification of information from one device to another device may be performed via one or more devices. Regarding any information (e.g., a variable, a constant, a parameter, a setting) described in the present disclosure, even if not specifically stated in the above embodiments, information indicating / specifying (or related to) the any information (value) may be notified from any first device (e.g., a terminal / base station) to any second device (e.g., a base station / terminal).

[0252] <Applicable systems> Each aspect / embodiment described in the present disclosure may be implemented using any of a wide variety of standards, including Long Term Evolution (LTE), LTE-Advanced (LTE-A), International Mobile Telecommunications-Advanced (IMT-Advanced), 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 5G-A (5G-Advanced), 6G (6th generation mobile communication system), xG (xth generation mobile communication system (x is, for example, an integer or a decimal), Future Radio Access (FRA), New Radio (NR), New radio access (NX), Future generation radio access (FX), Open Radio Access Network (O-RAN), Wideband Code Division Multiple Access (W-CDMA, registered trademark), Global System for Mobile communications (GSM, registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), and Institute of Electrical and Electronics Engineers (IEEE). 802.11, IEEE802.11x (where x is any character string such as b, a, g, n, ac, ax, be, or bn, and when x=n it is called Wi-Fi4, when x=ac it is called Wi-Fi5, when x=ax it is called Wi-Fi6 or Wi-Fi6E, when x=be it is Wi-Fi7, and when x=bn it is called Wi-Fi8, etc. Wi-Fi is a registered trademark.), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), network virtualization technology (e.g., NFV (Network Function Virtualization), SFC (Service Function Chaining), SDN (Software Defined Networking)), LPWA (Low Power Wide Area), etc. Furthermore, each aspect / embodiment described in the present disclosure may be applied to a system based on a combination of at least two of these technologies. Furthermore, "based on" naturally refers not only to a system that uses the technology, but also to a system that uses an extension or modification of the technology.

[0253] <Base station> In the present disclosure, any two terms selected from a set of terms such as "base station (BS)", "radio base station", "fixed station (fixed station)", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point (AP)", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "radio unit (RU)", "remote unit (RU)", "control unit (CU)", "distributed unit (DU)", "remote radio head (RRH)", "node", "gateway", "terrestrial base station", "stratospheric base station", "unmanned aerial vehicle", "high altitude platform station (HAPS)", "airborne platform", "panel", "cell", "radio access network (RAN)", and "network" may be used interchangeably. Each cell accommodated by a base station may be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, a serving cell, or a super cell. In the present disclosure, any two terms selected from a set of terms such as "cell," "sector," "cell group," "carrier," "component carrier," "cluster," "bandwidth part (BWP)," and "carrier bandwidth" may be used interchangeably.

[0254] <Device> In the present disclosure, any two terms selected from the set of terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "Device", "Module" and "Terminal" may be used interchangeably.

[0255] A terminal may be referred to 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, router (e.g., home router, mobile router, etc.), TCU (Telematics Control Unit), or some other suitable terminology.

[0256] <Mobile> The base station and the terminal may each be composed of one or more devices. The devices constituting at least a portion of the base station and the terminal may be called a transmitting device, a receiving device, a communication device, etc. Note that the devices constituting at least a portion of the base station and the terminal may be, for example, an object itself, such as a vehicle, a transport vehicle, an automobile, a motorcycle, a bicycle, a connected car, an excavator, a bulldozer, a wheel loader, a dump truck, a forklift, a train, a bus, a handcar, a rickshaw, a ship and other watercraft, an airplane, a rocket, an unmanned aerial vehicle, a stratospheric base station (e.g., a High Altitude Platform Station (HAPS)), an artificial satellite (e.g., a Low Earth Orbit (LEO) satellite, a Medium Earth Orbit (MEO) satellite, a Geostationary Earth Orbit (GEO) satellite), a drone (registered trademark), a multicopter, a quadcopter, a balloon, or an Internet of Things (IoT) device (e.g., a smart meter, a sensor), or may include, but are not limited to, an object or device mounted on the object. Furthermore, the object may be a moving object (hereinafter referred to as a "moving object"; this does not exclude the case where the moving object is in a stationary state where it is not moving), or may be a fixedly positioned object (hereinafter referred to as a "non-moving object").

[0257] Furthermore, a base station in the present disclosure may be read as a terminal. For example, the aspects / 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)) or communication of a non-terrestrial network (NTN). In this case, the terminal may be configured to have at least some of 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, "sidelink") or terms corresponding to NTN (for example, feeder link or service link). For example, an uplink channel or a downlink channel may be read as a sidelink channel.

[0258] The present disclosure is also applicable to cases where at least some of the devices constituting the base station and the terminal operate outside the earth (for example, in the atmosphere or outer space).

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

[0260] <Processing procedures, etc.> The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented. <Base station operation> In the present disclosure, a specific operation described as being performed by a base station may be performed by its upper node or by some of its upper nodes (e.g., CU, RU, or DU, etc.) in some cases. It is clear that various operations performed for communication with a terminal in a RAN or core network may be performed by at least some of the base station and other network nodes other than the base station. The other network node may be one node or a combination of multiple nodes. The network node is, for example, a node provided in various core networks such as EPC (Evolved Packet Core) and 5GC (5G Core Network), and provides one or more network functions (NF: Network Functions), but is not limited to this.

[0261] Furthermore, in the present disclosure, the operation of "a terminal receives information from a base station" accompanies the operation of "the base station transmits the information to the terminal," "the base station generates the information," or both. Similarly, the operation of "a terminal transmits information to a base station" accompanies the operation of "the base station receives the information from the terminal." Furthermore, the operation of "a terminal is configured to ..." or "configure UE to ..." may include the operation of "a base station transmits configuration information regarding the configuration of the terminal" and the operation of "a terminal configures a predetermined operation based on the configuration information."

[0262] <Variations of form, etc.> Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched depending on the implementation.

[0263] The present disclosure has been described above, but it is for illustrative purposes only, and the present invention is not limited to the aspects / embodiments described in the present disclosure. The present disclosure can be implemented in modified and altered forms without departing from the spirit of the invention. The present disclosure and its modifications and alterations are included in the scope of the present invention and its equivalents.

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

[0265] <Radio resource definition> The radio resource may be defined by a combination of resource units in one or more domains, such as the time domain, the frequency domain, the spatial domain, the code domain, and the power domain.

[0266] For example, resources in the time domain may be defined by one or more time units. The one or more time units may include, but are not limited to, a radio frame, a subframe, a slot, a symbol, a transmission time interval (TTI), or a combination of at least two of these. The time unit may be a fixed-length time unit independent of numerology, a variable-length time unit dependent on numerology, or both. Examples of fixed-length time units include, but are not limited to, a subframe consisting of one or more slots and a radio frame including multiple subframes. Examples of variable-length time units include, but are not limited to, a symbol and a slot including a fixed number of symbols. A certain time unit may be divided into shorter time units. Examples of shorter time units include, but are not limited to, a minislot consisting of fewer symbols than the number of symbols constituting a slot. The above-described time units may include, for example, time units used as units for scheduling, link adaptation, etc. Furthermore, any time unit in the present disclosure may be read as another time unit.

[0267] Numerology is a parameter that defines the physical layer structure, and may be a parameter based on at least one of subcarrier spacing (SCS), symbol length, cyclic prefix length, and sampling time, for example.

[0268] Resources in the frequency domain may be defined, for example, by one or more frequency units. The one or more frequency units may include, for example, subcarriers, resource blocks (RBs), bandwidth parts (BWPs), carrier bandwidths, or a combination of at least two of these, but the terminology of the frequency units is not limited to these. The number of subcarriers included in a frequency unit may be a fixed number regardless of numerology, or a variable number that changes depending on numerology. For example, an RB is composed of a predetermined number of consecutive subcarriers in the frequency domain, and the number of subcarriers included in the RB may be the same regardless of numerology, for example, 12, but is not limited to this. A BWP may be composed of, for example, one or more consecutive RBs within a certain carrier bandwidth, but is not limited to this. For example, one or more BWPs may be configured within one carrier, and at least one of the BWPs may be activated. Any frequency unit in the present disclosure may be interchangeable with another frequency unit.

[0269] Furthermore, resources in both the time domain and the frequency domain may be defined by one or more time / frequency units each consisting of a time unit and a frequency unit, such as, but not limited to, a resource element (RE) consisting of one symbol and one subcarrier, a resource element group (REG) consisting of a predetermined number of REs, or a control resource set (CORESET) consisting of a predetermined number of symbols and a predetermined number of RBs.

[0270] Furthermore, resources in the spatial domain may be defined, for example, by one or more spatial units, including, but not limited to, a beam, a layer of MIMO (Multi-Input Multi-Output), an antenna port, or a combination of at least two of these.

[0271] Furthermore, the resources in the code domain may be defined by one or more code units, such as, but not limited to, a cyclic shift (CS), an orthogonal cover code (OCC), or a combination thereof.

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

[0273] <Means> The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc. [Industrial Applicability]

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

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

Claims

1. A device with lower complexity than a Narrow Band Internet of Things (NB-IoT) device, a receiver for receiving an R2D signal from a wireless communication device; a control unit that determines control information using predefined values / settings or specified values ​​if the control information is not present or specified in the R2D signal; 1. A device comprising:

2. The defined value / setting or specified value is a value specified in or assumed by the specification, The device of claim 1 .

3. The defined value / setting or specified value is the same value as that of PRDCH. The device of claim 1 .

4. The predefined value / setting or specified value is a value associated with a message type; The device of claim 1 .

5. Devices with lower complexity than NB-IoT (Narrow Band Internet of Things) devices, receiving an R2D signal from a wireless communication device; If control information is not present or is not specified in the R2D signal, then using a predefined value / setting or a specified value to identify the control information. Communication method.

Images