Device and communication method

Abstract

To provide an A-IoT device and a communication method that can take into account the influence of sampling frequency offsets, etc., during the padding period of OFDM symbols on the offset value between transmission signals (e.g., Msg1) of the device.SOLUTION: A device with lower complexity than that of an NB-IoT device includes a receiving unit that receives an R2D signal that triggers random access from a wireless communication apparatus, and a control unit that controls the transmission of a response signal that responds to the signal that triggers random access to the wireless communication apparatus, and the control unit adjusts the offset value between the response signals taking into account the influence of sampling frequency offsets in the padding period of an OFDM symbol.SELECTED DRAWING: Figure 17

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] In a communication system including an ambient IoT device, the end timing of a received signal may not coincide with the boundary of an Orthogonal Frequency Division Multiplexing (OFDM) symbol. In such cases, padding chips consisting of ON / OFF periods of an On Off Keying (OOK) symbol may be added to the end of the received signal to align the received signal with the boundary of the OFDM symbol.

[0006] However, the accumulated timing error in the padding chips due to sampling frequency offsets, etc., is not taken into account in the offset value between transmission signals (e.g., Msg1) sent by multiple devices, which means that the transmission signals from multiple devices may collide.

[0007] Therefore, the present disclosure contributes to providing an A-IoT device and communication method that can take into account the effects of sampling frequency offsets, etc., during the padding period of an OFDM symbol on the offset value between device transmission signals (e.g., Msg1, etc.).

[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 that triggers random access from a wireless communication device, and a control unit that controls the transmission of a response signal that responds to the signal that triggers random access to the wireless device, and the control unit adjusts the offset value between the response signals taking into account the effect of a sampling frequency offset in the padding period of an OFDM symbol. [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] 1A and 1B are diagrams illustrating examples of candidate topologies for CW / R2D / D2R transmission in Topology 1. [Figure 9] 10A and 10B are diagrams illustrating examples of candidate topologies for CW / R2D / D2R transmission in Topology 2. [Figure 10] 10A and 10B are diagrams illustrating the signal structure of an R2D timing acquisition signal. [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] 10 is a diagram showing an example of an offset between R2D, the previous Msg1, and the next Msg1. [Figure 15] FIG. 10 is a diagram showing an example of padding chips for R2D. [Figure 16] FIG. 10 is a diagram illustrating an example of padding in agreement 1. [Figure 17] FIG. 1 is a diagram illustrating a problem in this proposal. [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. The communication related to Topology 4 may be considered as sidelink (SL) communication.

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

[0039] The wireless communication system 1 (wireless communication network) may include a base station, a support node, an intermediate node, and / or a terminal (UE 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 an unamplified backscatter UL transmission, an amplified backscatter UL transmission, or a general amplified 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 signal of R2D communication is the same as the node that receives the signal of D2R communication generated and transmitted by the A-IoT device. That is, the R in R2D is the same as the R in D2R.

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

[0077] <Timing Acquisition in R2D / D2R Transmission> In a communication system including an A-IoT device, the candidate topologies described above are considered, and signals of R2D communication (hereinafter simply referred to as "R2D") and signals of D2R communication (hereinafter simply referred to as "D2R") are transmitted and received.

[0078] It has been agreed to consider the timing acquisition signal in such R2D / D2R transmission. Note that timing acquisition may be replaced by (time) synchronization. Hereinafter, the timing acquisition signal for R2D is referred to as the R2D timing acquisition signal, and the timing acquisition signal for D2R is referred to as the D2R timing acquisition signal.

[0079] Regarding R2D transmission, it has been agreed that the R2D timing acquisition signal is included in R2D at least for timing acquisition and to notify the start (or start or starting point) of R2D transmission in the time domain. Here, the R2D timing acquisition signal may be, for example, an R2D preamble.

[0080] For D2R transmissions, it is agreed that a D2R timing acquisition signal is included in the D2R at least for timing acquisition purposes and to indicate the beginning of the D2R transmission in the time domain, where the D2R timing acquisition signal may be, for example, a D2R preamble.

[0081] For example, as shown in Figure 10, a preamble consisting of at least two parts including a start-indicator part and a clock-acquisition part is configured for the R2D timing acquisition signal immediately before the transmission of the physical channel, where the start-indicator part is located immediately before the clock acquisition part.

[0082] The start indicator portion signals the start of the R2D transmission. The clock acquisition portion provides chip synchronization for at least the subsequent physical channel transmission. The preamble may be considered not to be part of the physical channel.

[0083] The R2D preamble may be placed temporally before the R2D control / data, and the D2R preamble may be placed temporally before the D2R control / data. Note that in this specification and drawings, control information and / or data (information) may be abbreviated and referred to as control / data.

[0084] <Tip> "Chip" refers to the ON / OFF period of an OOK (On Off Keying) symbol. Also, the "M" in OOK refers to the number of chips in one OFDM symbol. A D2R / R2D chip may be an "OOK (On-Off-Keying) symbol", "FSK (Frequency Shift Keying) symbol", or "PSK (Phase Shift Keying) symbol". FSK / PSK may be applied only to D2R.

[0085] The ON / OFF or amplitude a1 / a2 of the OOK may be chip '0' / chip '1'. The FSK frequencies f1 / f2 may be chip '0' / chip '1'. The phase p1 / p2 of PSK may be chip '0' / chip '1'.

[0086] For example, the amplitude a1 may be a chip '0' and the amplitude a2 may be a chip '0'.

[0087] Bit '0' (data '0') / bit '1' (data '1') of D2R / R2D may be represented by one or more chips depending on the coding scheme.

[0088] For example, if line coding is not applied to D2R, bit '0' / bit '1' may be represented as chip '0' / chip '1'.

[0089] For example, when Manchester encoding is applied to D2R / R2D, bit '0' / bit '1' may be represented by multiple chips, e.g., bit '0' may be represented by chip '01' / chip '10'.

[0090] When FM0 (frequency modulation 0) / Miller coding is applied to D2R, bit '0' / bit '1' may be represented by multiple chips, for example, bit '0' may be represented by chip '00' / chip '11', and bit '1' may be represented by chip '10' / chip '01'.

[0091] For example, when PIE (pulse interval encoding) coding is applied to R2D, bit '0' / bit '1' may be represented by multiple chips. For example, bit '0' may be represented by chip '10' / chip '01'. Bit '1' may be represented by chip '1110' / chip '0001' (multiple 0s and 1s).

[0092] <Terminology> Here, the terms related to the above-mentioned A-IoT are summarized and explained.

[0093] · A-IoT device or device: A device included in an A-IoT system having any of the types of devices mentioned above

[0094] · Leader: D2R receiver · The leader may be either a BS or a UE. A UE serving as a leader may be referred to as an intermediate UE. · The R2D transmitter and the D2R receiver may be the same node or different nodes.

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

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

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

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

[0099] <Rel-19 corresponding 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 outlines the policy for advancing the standardization of A-IoT technology in NR, and Chapter 4 states the following:

[0100] General range The definitions provided in TR 38.848, TR 38.769, and decisions of the RAN Working Group in the Rel-19 SI of the RAN WG are incorporated into this WI, and the following are of exclusive general scope: 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 R2D and D2R amplification within the device, the device's D2R transmission is backscattered relative to the externally provided carrier 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 D1T1-B cases 1 to 4 G.Proximity determination only according to Solution 1 of TR 38.769 (Un)availability of devices via H.TR 38.769 direction 1 only

[0101] 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. R2D transmission only supports Manchester line code in TR 38.769 D2R transmission supports: Manchester line code or no line code in TR 38.769 (choose one) Corresponding small frequency shift scheme according to options in TR 38.769 R2D does not support FEC (Forward Error Correction Code). D2R only supports convolutional codes with generator polynomials according to TS 36.212 (unless RAN1 decides to use another generator polynomial according to RAN1#120bis). PRDCH and PDRCH support transmission without CRC (Cyclic Reduncancy Check) and with CRC according to the 6-bit CRC and 16-bit CRC generating polynomials in TS 38.212 (unless RAN1 decides to use a different generating polynomial by RAN1#120bis). The length of CRC to use or whether to use no CRC is decided by RAN1. D2R supports repetition in the physical layer. R2D does not support repetition in the physical layer.

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

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

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

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

[0106] <Random Access (RA) Based on Agreement Items> Regarding random access, the following procedures 1 and 2 are under consideration.

[0107] 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 at 16 bits. · A-IoT Msg2: The reader echoes the ID received in Msg1. · A-IoT Msg3: The device sends the device ID and / or other upper layer data (in response to upper layer requests). · When the device receives Msg2 containing the same random ID as Msg1, it considers the contention resolution to be successful. · "Msg4" (i.e., subsequent R2D transmission after D2R transmission) does not always need to be sent in random access. "Msg4" can be considered to handle the failure of Msg3 transmission (due to various reasons).

[0108] 2. 2 Steps (see Figure 13) · A-IoT Msg1: The device sends the device ID and / or other upper layer data (in response to upper layer requests). A random ID (fixed 16 bits) may be additionally included in Msg1. · A-IoT Msg2: If Msg1 contains a random ID, the reader echoes the ID received in Msg1.

[0109] <Time Region Occasion of Msg1> After receiving the R2D message that triggers random access, the device transmits Msg1. Rel-19 supports up to two time-domain occasions for transmitting Msg1 associated with one R2D message, and these occasions are used to determine the Msg1 resource. For example, as shown in Figure 14, for the first Msg1 transmission, the start of the transmission occasion is T after the R2D message ends. offset1 In the case of the second Msg1 transmission, the start of the transmission occasion is T after the end of R2D. offset1 +T offset2 This is the point in time.

[0110] <Padding Tip> In the case of R2D, the end of the R2D may or may not be aligned with an OFDM symbol boundary. If the number of chips generated for the R2D transmission does not fully occupy the last OFDM symbol, padding is used (see, for example, Figure 15). The content of the padding chips can be assumed to be up to the reader implementation; that is, padding chips can be on-chip, off-chip, on-chip and off-chip, etc., depending on the reader's choice.

[0111] <Agreement 1> At the RAN1#121 meeting, the following agreement was reached regarding padding:

[0112] Agreement If the number of chips generated for R2D transmission does not completely occupy the last OFDM symbol, padding is used as follows: (Alt1a): The content of the padding depends on the reader implementation and is transparent to the device. · In any timing relationship, timeline determinations refer to the end of the padding. Note: This means that the device must be aware of the duration of the padding or the last OFDM symbol boundary, depending on the implementation. Note: The padding time may be used as the additional time required for D2R FEC / CRC calculations (if applicable).

[0113] Based on this Agreement1, T offset1 The start timing of the padding is the end timing. The content of the padding is up to the reader implementation and is transparent to the device (see Figure 16).

[0114] <Agreement 2> At the RAN1#121 meeting, the timing of the second Msg1 transmission (T offset2 ), the following agreement has been reached:

[0115] Agreement T offset2 =αT offset1 +βT msg1 where T msg1 , α, and β are as follows: T msg1 is the duration of the time domain resource of the first Msg1. ·α=0.25 and β=1.25.

[0116] The above agreement is based on the following principles: Depending on the device, the accuracy of the clock count may vary, and the SFO (Sampling Frequency Offset: the difference in sampling frequency between the transmitter and receiver):e may be up to ±10%. In the first Msg1 transmission occasion shown in Figure 14, the latest Msg1 transmission timing considering the influence of SFO is (1+e)T offset1 +(1+e)T msg1 Here, T msg1 is the transmission period of Msg1. In the second Msg1 transmission occasion shown in Figure 14, the earliest Msg1 transmission timing considering the influence of SFO is (1-e)T offset1 +(1-e)T offset2 This becomes: The latest Msg1 transmission timing of the first Msg1 and the earliest Msg1 transmission timing of the second Msg1 must not overlap. That is, (1+e)T offset1 +(1+e)T msg1 <(1-e)T offset1 +(1-e)T offset2 Based on the above equation, the following equation is derived:

number

[0117] <Issues> Agreement 1 does not specify the content of the padding, which may include, for example, on-chip, off-chip, or both on-chip and off-chip. Therefore, devices cannot use padding chips to calibrate their clocks. Therefore, the last time a device calibrates its clock before transmitting Msg1 is at the end of the chip generated for the R2D transmission (see Figure 17).

[0118] During the padding chips, the device clock may be shifted. However, the cumulative timing error during the padding chips is T offset2 Therefore, the first Msg1 and the second Msg1 may overlap in the time domain (see Figure 17). offset1 In addition to the transmission period of Msg1, the influence of SFO in the padding chips must also be considered.

[0119] Therefore, in this proposal, T offset2We propose a method to accurately evaluate the effect of sampling frequency offset, including padding chips, on the value of .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0137] <Proposal 1> The padding period for the last OFDM symbol of the R2D transmission is T offset2 T offset2 is given by the following formula: T offset2 =γT padding +αT offset1 +βT msg1 where T padding is the duration of the time domain resource used for padding the last OFDM symbol when the number of chips generated for R2D transmission does not fully occupy the last OFDM symbol. γ may be specified as a single value in the specification. (For example, it may be the same as α or a value such as 0.25.) γ may vary depending on device type / capability (For example, Device 1, Device 2a, Device 2b, etc. in the above-mentioned <Device Type>.)

[0138] The control unit of the ambient IoT device or reader calculates the effects of sampling frequency offset, including padding chips, using the above-mentioned formula. The control unit of the ambient IoT device or reader uses the calculated evaluation value to adjust the timing of sending and receiving the signal that triggers random access or the triggered signal (Msg1). The control unit of the ambient IoT device or reader controls the communication unit (transmitter or receiver) so that transmission or reception is performed according to the adjusted transmission and reception timing.

[0139] (Variation 1 of Proposal 1) T offset2 may be given by the following formula:

number

number

[0140] (Variation 2 of Proposal 1) T offset2 may be given by the following formula:

number

[0141] X and T as follows: padding A range of values ​​may be specified. Y1 > T padding In the case of, X = Z1, Y1 < T padding In the case of <Y2, X = Z2, ··· etc The unit of Y1 is μs, chip, bit, etc.

[0142] (Effect of Proposal 1) According to Proposal 1, the padding period of the last OFDM symbol is made to be considered at T offset2 By doing so, the duration of the time-domain resource used for padding the last OFDM symbol: T padding and the sampling frequency offset: e, for the value of T offset2 the influence by the sampling frequency offset including the padding chip can be accurately evaluated. Also, by explicitly defining the error range that may occur due to the sampling frequency offset including the padding chip, inconsistencies in implementation and uncertainties in design can be suppressed, and a highly reliable and stable system can be realized.

[0143] <Proposal 2> The device assumes / expects that the padding period is based on the following specific designs (1) to (¾). (1) As a specific design, rising / falling edges may be used for each X. · X may be an OOK (On Off Keying) waveform. · Manchester coding may be used for X. (2) The specific design may be applied to the end Y (interval) of the last OFDM symbol. Note that Y may include or not include parity chips for CP (cyclic prefix) processing. [[ID=3?]](For example, when M (the number of chips in one OFDM symbol) = 24, two ON chips may be included.) (3) X and Y may be specified in the specification. (For example, X = 2, Y = 2, etc.) It may vary depending on the M value of OOK. Note that the units of X and Y are chips, μs, or other units.

[0144] The control unit of the ambient IoT device (or reader) evaluates the effects of sampling frequency offsets, including padding chips, by assuming / expecting the specific design described above. The control unit of the ambient IoT device (or reader) determines the timing of transmission and reception using the assumed or calculated evaluation value. The control unit of the ambient IoT device (or reader) controls the communication unit (transmitter or receiver) so that transmission control or reception control is performed according to the determined timing of transmission and reception.

[0145] (Effects of Proposal 2) According to Proposal 2, by assuming the clock waveform during the padding period, the expected tail Y (interval) of the last OFDM symbol, the number of chips in the OFDM symbol (M value), etc., it is possible to accurately evaluate the impact of sampling frequency offsets, including padding chips, on various implementation systems.

[0146] (Variations of Proposal 1 and Proposal 2) Proposal 1 and Proposal 2 are based on the time offset T between the R2D that triggers Msg1 and the first Msg1. offset1 , T indicating the time offset between Msg2 and Msg3 offset3 , T indicating the time offset between R2D and D2R other than Msg1 offset4 Other time offset values ​​may also be applied.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0192] <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)), or LPWA (Low Power Wide Area). 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0215] 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, the R2D signal triggering random access; a control unit that controls transmission of a response signal in response to the signal that triggers the random access to the wireless communication device; Equipped with the control unit adjusts the offset value between the response signals in consideration of an effect of a sampling frequency offset in a padding period of an OFDM symbol. device.

2. adjusting the offset value between the response signals to take into account the duration of time domain resources used for padding the last OFDM symbol in case the number of chips generated for the R2D signal does not fully occupy the last OFDM symbol; The device of claim 1 .

3. adjusting the offset value between the response signals taking into account the value of the maximum sampling frequency offset; The device of claim 1 .

4. adjusting an offset value between the response signals taking into account the duration of a time domain resource of the first response signal; 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 that triggers random access; adjusting an offset value between response signals responding to the signal that triggers the random access, taking into account an effect of a sampling frequency offset in a padding period of an OFDM symbol, and transmitting the response signals to the wireless communication device; Communication method.

Images