Device and method for supporting carrier for ambient IoT communication in wireless communication system

Abstract

According to various embodiments of the present disclosure, a method performed by a first device is provided, the method comprising the steps of: transmitting, to a second device, waveform information related to one specific waveform type from among a plurality of waveform types, the plurality of waveform types including at least one single-tone waveform type and at least one multi-tone waveform type; receiving, from the second device, capability information of the second device related to support of the specific waveform; transmitting, to the second device, a request message for uplink transmission (UL transmission) based on the specific waveform type; and receiving, from the second device, the UL transmission on the basis of the request message.

Description

Device and method for supporting carrier for ambient IoT communication in a wireless communication system

[0001] The present disclosure relates to a wireless communication system. Specifically, the present disclosure relates to a device and method for supporting a carrier for Ambient Internet of Things (Ambient IoT) communication in a wireless communication system.

[0002]

[0003] Wireless communication systems are widely deployed to provide various types of communication services, such as voice and data. Typically, wireless communication systems are multiple access systems that support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power). Examples of multiple access systems include Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA).

[0004]

[0005] To solve the above-described problems, the present disclosure provides a device and method for supporting a carrier for Ambient IoT communication in a wireless communication system.

[0006] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

[0007]

[0008] According to various embodiments of the present disclosure, a method performed by a first device is provided, the method comprising: transmitting waveform information related to one specific waveform type among a plurality of waveform types to a second device, the plurality of waveform types including at least one single-tone waveform type and at least one multi-tone waveform type; receiving capability information of the second device related to support of the specific waveform from the second device; transmitting a request message for uplink transmission (UL transmission) based on the specific waveform type to the second device; and receiving the uplink transmission from the second device based on the request message.

[0009] According to various embodiments of the present disclosure, a method performed by a second device is provided, the method comprising: receiving waveform information related to one specific waveform type among a plurality of waveform types from a first device, the plurality of waveform types including at least one single-tone waveform type and at least one multi-tone waveform type; transmitting capability information of the second device related to support of the specific waveform to the first device; receiving a request message for uplink transmission (UL transmission) based on the specific waveform type from the first device; and transmitting the uplink transmission to the first device based on the request message.

[0010] According to various embodiments of the present disclosure, a first device is provided, comprising: a transceiver; at least one processor; and at least one memory operably connectable to the at least one processor and storing instructions that, when executed by the at least one processor, perform operations, wherein the operations include all steps of a method performed by the first device according to various embodiments of the present disclosure.

[0011] According to various embodiments of the present disclosure, a second device is provided, comprising: a transceiver; at least one processor; and at least one memory operably connectable to the at least one processor and storing instructions that, when executed by the at least one processor, perform operations, wherein the operations include all steps of a method performed by the second device according to various embodiments of the present disclosure.

[0012] According to various embodiments of the present disclosure, a control device for controlling a first device in a wireless communication system is provided, the control device including at least one processor and at least one memory operably connected to the at least one processor, wherein the at least one memory stores instructions for performing operations based on being executed by the at least one processor, the operations including all steps of a method performed by the first device according to various embodiments of the present disclosure.

[0013] According to various embodiments of the present disclosure, a control device for controlling a second device in a wireless communication system is provided, the control device including at least one processor and at least one memory operably connected to the at least one processor, wherein the at least one memory stores instructions for performing operations based on being executed by the at least one processor, the operations including all steps of a method performed by the second device according to various embodiments of the present disclosure.

[0014] According to various embodiments of the present disclosure, there is provided one or more non-transitory computer-readable media storing one or more instructions, wherein the one or more instructions, when executed by one or more processors, perform operations, the operations including all steps of a method performed by a first device according to various embodiments of the present disclosure.

[0015] According to various embodiments of the present disclosure, there is provided one or more non-transitory computer-readable media storing one or more instructions, wherein the one or more instructions, when executed by one or more processors, perform operations, the operations including all steps of a method performed by a second device according to various embodiments of the present disclosure.

[0016]

[0017] To solve the above-described problems, the present disclosure can provide a device and method for supporting a carrier for Ambient IoT communication in a wireless communication system.

[0018]

[0019] The accompanying drawings are intended to aid in understanding the present disclosure and, together with detailed descriptions, may provide embodiments of the present disclosure. However, the technical features of the present disclosure are not limited to specific drawings, and the features disclosed in each drawing may be combined with each other to form new embodiments. Reference numerals in each drawing may indicate structural elements.

[0020] FIG. 1 is a diagram illustrating an example of physical channels used in a system applicable to the present disclosure and a general signal transmission method using the same.

[0021] FIG. 2 is a diagram illustrating an example of a wireless frame structure used in a system applicable to the present disclosure.

[0022] FIG. 3 is a drawing illustrating an example of a slot structure used in a system applicable to the present disclosure.

[0023] FIG. 4 is a diagram illustrating an example of a slot structure of a wireless frame used in a system applicable to the present disclosure.

[0024] FIG. 5 is a diagram illustrating an example of power consumption according to the operating state of an energy harvesting-based device with energy storage capability in a system applicable to the present disclosure, and the device energy state at that time.

[0025] FIG. 6 is a diagram illustrating an example of an operation process of a first device in a system applicable to the present disclosure.

[0026] FIG. 7 is a diagram illustrating an example of an operation process of a second device in a system applicable to the present disclosure.

[0027] FIG. 8 is a diagram illustrating an example of the structure of a first device and a second device in a system applicable to the present disclosure.

[0028]

[0029] In various embodiments of the present disclosure, “A or B” may mean “only A,” “only B,” or “both A and B.” In other words, in various embodiments of the present disclosure, “A or B” may be interpreted as “A and / or B.” For example, in various embodiments of the present disclosure, “A, B or C” may mean “only A,” “only B,” “only C,” or “any combination of A, B and C.”

[0030] In various embodiments of the present disclosure, a slash ( / ) or a comma may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B, or C."

[0031] In various embodiments of the present disclosure, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Furthermore, in various embodiments of the present disclosure, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted as equivalent to “at least one of A and B.”

[0032] Additionally, in various embodiments of the present disclosure, “at least one of A, B and C” can mean “only A,” “only B,” “only C,” or “any combination of A, B and C.” Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C.”

[0033] Additionally, parentheses used in various embodiments of the present disclosure may mean "for example." Specifically, when indicated as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information." In other words, "control information" in various embodiments of the present disclosure is not limited to "PDCCH", and "PDDCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information."

[0034] Technical features individually described in a single drawing in various embodiments of the present disclosure may be implemented individually or simultaneously.

[0035]

[0036] Common signal transmission methods in 3GPP

[0037] Physical channels and general signal transmission

[0038] FIG. 1 is a diagram illustrating an example of physical channels used in a system applicable to the present disclosure and a general signal transmission method using these channels. Specifically, FIG. 1 illustrates physical channels used in a 3GPP system and general signal transmission.

[0039] Figure 1 illustrates the physical channels and typical signal transmission used in the 3GPP system. In a wireless communication system, a terminal receives information from a base station via the downlink (DL), and the terminal transmits information to the base station via the uplink (UL). The information transmitted and received between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type and purpose of the information they transmit and receive.

[0040] When a terminal is powered on again from a powered-off state or newly enters a cell, it performs an initial cell search operation, such as synchronizing with the base station (S11). To this end, the terminal receives the PSCH (Primary Synchronization Channel) and SSCH (Secondary Synchronization Channel) from the base station to synchronize with the base station and obtain information such as the cell ID (cell identity). In addition, the terminal can obtain broadcast information within the cell by receiving the PBCH (Physical Broadcast Channel) from the base station. In addition, the terminal can receive the DL RS (Downlink Reference Signal) during the initial cell search phase to check the downlink channel status.

[0041] A terminal that has completed initial cell search can obtain more specific system information by receiving a PDCCH (Physical Downlink Control Channel) and a corresponding PDSCH (Physical Downlink Control Channel) (S12).

[0042] Thereafter, the terminal may perform a random access procedure to complete connection to the base station (S13-S16). Specifically, the terminal may transmit a preamble via a physical random access channel (PRACH) (S13) and receive a random access response (RAR) for the preamble via a physical downlink control channel (PDCCH) and a corresponding PDSCH (S14). Thereafter, the terminal may transmit a physical uplink shared channel (PUSCH) using scheduling information in the RAR (S15) and perform a contention resolution procedure such as a PDCCH and a corresponding PDSCH (S16).

[0043] A terminal that has performed the above-described procedure can then perform PDCCH / PDSCH reception (S17) and PUSCH / PUCCH (Physical Uplink Control Channel) transmission (S18) as general uplink / downlink signal transmission procedures. Control information that the terminal transmits to the base station is referred to as UCI (Uplink Control Information). UCI includes HARQ ACK / NACK (Hybrid Automatic Repeat and reQuest Acknowledgement / Negative-ACK), SR (Scheduling Request), CSI (Channel State Information), etc. CSI includes CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indication), etc. UCI is generally transmitted through PUCCH, but can be transmitted through PUSCH when control information and data must be transmitted simultaneously. In addition, the terminal can aperiodically transmit UCI through PUSCH according to a request / instruction of the network.

[0044]

[0045] OFDM (Orthogonal Frequency Division Multiplexing) Numerology

[0046] The new RAT system uses OFDM transmission scheme or a similar transmission scheme. The new RAT system may follow OFDM parameters different from those of LTE. Alternatively, the new RAT system may follow the existing LTE / LTE-A numerology but have a larger system bandwidth (e.g., 100 MHz). Alternatively, a single cell may support multiple numerologies. That is, UEs operating under different numerologies can coexist within a single cell.

[0047]

[0048] Radio frame structure

[0049] FIG. 2 is a diagram illustrating an example of the structure of a wireless frame used in a system applicable to the present disclosure.

[0050] In NR, uplink and downlink transmissions are organized into frames. A radio frame is 10 ms long and is defined by two 5 ms half-frames (HF). Each half-frame is defined by five 1 ms subframes (SF). A subframe is divided into one or more slots, and the number of slots in a subframe depends on the subcarrier spacing (SCS). Each slot contains 12 or 14 OFDM(A) symbols, depending on the cyclic prefix (CP). When a regular CP is used, each slot contains 14 symbols. When an extended CP is used, each slot contains 12 symbols. Here, the symbols can include OFDM symbols (or CP-OFDM symbols), SC-FDMA symbols (or DFT-s-OFDM symbols).

[0051] Table 1 illustrates that when CP is normally used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary depending on the SCS.

[0052] SCS (15*2^u)N slot symb N frame,u slot N subframe,u slot 15KHz (u=0)1410130KHz (u=1)1420260KHz (u=2)14404120KHz (u=3)14808240KHz (u=4)1416016

[0053] N slot symb is the number of symbols in the slot. N frame,uslot is the number of slots in the frame. N subframe,u slot is the number of slots within a subframe.

[0054]

[0055] Table 2 illustrates that when extended CP is used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary depending on the SCS.

[0056] SCS (15*2^u)N slot symb N frame,u slot N subframe,u slot 60KHz (u=2)12404

[0057] NR supports multiple numerologies (or subcarrier spacings (SCS)) to support various 5G services. For example, an SCS of 15 kHz supports wide areas in traditional cellular bands; an SCS of 30 kHz / 60 kHz supports dense urban areas, lower latency, and wider carrier bandwidth; and an SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

[0058] The NR frequency band can be defined by two types of frequency ranges (FR1, FR2). The numerical values ​​of the frequency ranges can be changed, and for example, the two types of frequency ranges (FR1, FR2) can be as shown in Table 3 below. For convenience of explanation, among the frequency ranges used in the NR system, FR1 can mean the "sub 6 GHz range", and FR2 can mean the "above 6 GHz range" and can be called millimeter wave (mmW).

[0059] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0060] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a band from 410 MHz to 7125 MHz, as shown in Table 4 below. That is, FR1 may include a frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, such as for vehicular communications (e.g., autonomous driving).

[0061] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0062] In an NR system, OFDM(A) numerologies (e.g., SCS, CP length, etc.) may be set differently between multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., SF, slot, or TTI) (conveniently referred to as TU (Time Unit)) consisting of the same number of symbols may be set differently between the merged cells.

[0063]

[0064] FIG. 3 is a drawing illustrating an example of a slot structure used in a system applicable to the present disclosure.

[0065] A slot contains multiple symbols in the time domain. For example, a slot contains 7 symbols for a regular CP, but 6 symbols for an extended CP. A carrier contains multiple subcarriers in the frequency domain. A Resource Block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A Bandwidth Part (BWP) is defined as multiple consecutive (P)RBs in the frequency domain, and can correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier can contain up to N (e.g., 5) BWPs. Data communication is performed through activated BWPs, and only one BWP can be activated for a single terminal. Each element in the resource grid is referred to as a Resource Element (RE), to which one complex symbol can be mapped.

[0066]

[0067] FIG. 4 is a diagram illustrating an example of a slot structure of a wireless frame used in a system applicable to the present disclosure.

[0068] Fig. 4 is an exemplary system, illustrating the slot structure of a frame of an NR system.

[0069] The frame structure of NR is characterized by a self-contained structure in which a DL control channel, DL or UL data, and UL control channel can all be included in a single slot unit, as shown in the example of FIG. 4. At this time, DL data scheduling information, UL data scheduling information, etc. can be transmitted in the DL control channel, and ACK / NACK information for DL ​​data, CSI information (modulation and coding scheme information, MIMO transmission-related information, etc.), scheduling requests, etc. can be transmitted in the UL control channel. In FIG. 4, a time gap for DL-to-UL or UL-to-DL switching may exist between the control region and the data region. In addition, some of DL control / DL data / UL data / UL control may not be configured within a single slot. Or, the order of each channel configuring a single slot may be different. (For example, DL control / DL data / UL control / UL data or UL control / UL data / DL control / DL data, etc.)

[0070]

[0071] Ambient IoT communication (Rel-18)

[0072] The Internet of Things (IoT) has recently attracted significant attention in the wireless communications world. By reducing the size, complexity, and power consumption of IoT devices and installing and connecting hundreds of billions to trillions of IoT devices, it can be applied to a wide range of applications. Specifically, 3GPP SA1 is discussing use cases, scenarios, and KPIs for these IoT devices, captured in TR 22.840. Furthermore, 3GPP RAN has conducted a study on IoT communications using the following SID objectives, and the output of this study is captured in TR 38.848.

[0073]

[0074] This study targets at a new 3GPP IoT technology, suitable for deployment in a 3GPP system, which relies on ultra-low complexity devices with ultra-low power consumption for the very-low end IoT applications.

[0075] The study shall provide clear differentiation, i.e. addressing use cases and scenarios that cannot otherwise be fulfilled based on existing 3GPP LPWA IoT technology e.g. NB-IoT including with reduced peak Tx power.

[0076]

[0077] In terms of energy storage, the study will consider the following device characteristics:

[0078] - Pure batteryless devices with no energy storage capability at all, and completely dependent on the availability of an external source of energy

[0079] - Devices with limited energy storage capability that do not need to be replaced or recharged manually.

[0080] Device categorization based on corresponding characteristics (e.g. energy source, energy storage capability, passive / active transmission, etc.) may be discussed during the study, in relation with the relevant use cases.

[0081] The device's peak power consumption shall be limited by its practical form factor for the intended use cases, and shall consider its energy source.

[0082]

[0083] Identify the suitable deployment scenarios and their characteristics, at least for the use cases / services agreed in SA1's “Study on Ambient power-enabled internet of Things”, comprising among at least the following aspects:

[0084] - Indoor / outdoor environment

[0085] - Basestation characteristics, e.g. macro / micro / pico cell-based deployments

[0086] - Connectivity topologies, including which node(s), e.g., basestation, UE, relay, repeater, etc. can communicate with target devices

[0087] - TDD / FDD and frequency bands in licensed or unlicensed spectrum

[0088] - Coexistence with UEs and infrastructure in frequency bands for existing 3GPP technologies

[0089] - Device originated and / or device terminated traffic assumption

[0090]

[0091] NOTE: There can be more than one deployment scenario identified for a use case, and a deployment scenario may be common to more than one use case.

[0092] NOTE: Where more than one deployment scenario is identified for a use case, the trade-offs between them should also be studied.

[0093] NOTE: The study shall not prioritize deployment aspects that should be coordinated with SA, e.g., public or private network, with or without CN connection.

[0094] NOTE: A representative use case can be studied for a group of use cases that have similar requirements.

[0095]

[0096] Formulate a set of RAN design targets based on the identified deployment scenarios and their characteristics for the relevant use cases, at least including:

[0097] - Power consumption

[0098] - Complexity

[0099] - Coverage

[0100] - Data rate

[0101] - Positioning accuracy

[0102]

[0103] NOTE: The requirements from SA1 on the relevant use cases shall be taken into consideration.

[0104] NOTE: The study shall aim to provide better coverage compared to existing non-3GPP technologies for the relevant use cases.

[0105] NOTE: Other RAN design targets in relation to connection density, mobility, security, latency, reliability, etc. may be discussed, if necessary for the relevant use cases.

[0106] NOTE: Detailed definitions of the RAN design targets should be discussed during the study.

[0107]

[0108] Compare and assess the feasibility of meeting the design targets for relevant use cases on the basis of the deployment scenario(s) appropriate to it, and identify assumptions on required functionality to be supported.

[0109] NOTE: This is not to require a detailed WG-level of analysis.

[0110]

[0111] Note: This study shall target for an IoT segment well below the existing 3GPP IoT technologies, e.g. NB-IoT, eMTC, RedCap, etc.

[0112] This study shall not aim to replace existing 3GPP LPWA technologies.

[0113]

[0114] According to the 3GPP RAN study, the following three types of IoT devices were considered:

[0115] Device A: No energy storage, no independent signal generation, i.e. backscattering transmission

[0116] Device B: Has energy storage, no independent signal generation, i.e., backscattering transmission. The stored energy can be used for amplification of reflected signals, etc.

[0117] Device C: Has energy storage, has independent signal generation, i.e. has an active RF component for transmission

[0118]

[0119] Additionally, according to the 3GPP RAN study, at least four topologies were considered:

[0120] Topology (1): Base Station ↔ Ambient IoT device

[0121] NOTE: Includes the possibility of BS Rx and BS Tx in different BSs.

[0122]

[0123] Topology (2): Base Station ↔ Intermediate Node ↔ Ambient IoT Device

[0124] NOTE: Intermediate node can be relay, IAB, UE, repeater, etc. which is capable of ambient IoT.

[0125]

[0126] Topology (3): Base Station ↔ Assisting Node ↔ Ambient IoT Device ↔ Base Station (Topology (3): BS ↔ Assisting Node ↔ Ambient IoT Device ↔ BS)

[0127] NOTE: Assisting node can be relay, IAB, UE, repeater, etc. which is capable of ambient IoT.

[0128]

[0129] Topology (4): UE ↔ Ambient IoT device

[0130]

[0131] Ambient IoT solutions SI (Rel-19)

[0132] A study item titled “Study on solutions for Ambient IoT (Internet of Things) in NR” was approved in 3GPP NR Release 19. Specifically, the study item will be conducted in 3GPP NR Release 19 based on the following:

[0133]

[0134] The following is an excerpt from 3GPP Draft RP-234058.

[0135] This study targets a further assessment at RAN WG-level of Ambient IoT, a new 3GPP IoT technology, suitable for deployment in a 3GPP system, which relies on ultra-low complexity devices with ultra-low power consumption for the very-low end IoT applications.

[0136] The study shall provide clear differentiation, i.e. addressing use cases and scenarios that cannot otherwise be fulfilled based on existing 3GPP LPWA IoT technology e.g. NB-IoT including with reduced peak Tx power.

[0137]

[0138] General Scope

[0139] The definitions provided in TR 38.848 are taken into this SI, and the following are included in the exclusive general scope:

[0140]

[0141] A. The overall objective shall be to study a harmonized air interface design with minimized differences (where necessary) for Ambient IoT to enable the following devices:

[0142]

[0143] i. ~1 μW peak power consumption, has energy storage, initial sampling frequency offset (SFO) up to 10X ppm, neither DL nor UL amplification in the device. The device's UL transmission is backscattered on a carrier wave provided externally.

[0144]

[0145] ii. ≤ a few hundred μW peak power consumption, has energy storage, initial sampling frequency offset (SFO) up to 10X ppm, both DL and / or UL amplification in the device. The device's UL transmission may be generated internally by the device, or be backscattered on a carrier wave provided externally.

[0146]

[0147] X is to be decided in WGs.

[0148] Coverage design goal: Maximum distance of 10-50 m for indoor devices according to TR 38.848 (“…a range that WGs can sub-select within”).

[0149] For Topologies 1 & 2 (UE as intermediate node under NW control) per TR 38.848, with no RRC states, no mobility (i.e. at least no cell selection / re-selection -like function), no HARQ, no ARQ.

[0150] NOTE 1: It is to be understood that “≤ a few hundred μW” means WGs are not tasked with setting a particular value, and that it will be for WG discussions to determine if a presented design with corresponding power consumption satisfies the “≤ a few hundred μW” requirement.

[0151]

[0152] B. Deployment Scenarios with the following characteristics, referenced to the tables in Clause 4.2.2 of TR 38.848:

[0153]

[0154] Deployment Scenario 1 (Topology 1): Basestation and coexistence characteristics: Micro-cell, co-site.

[0155] Deployment scenario 2 (Topology 2): Using a UE as an intermediate node under network control. Basestation and coexistence characteristics: Macro-cell, co-site.

[0156] The location of the intermediate node is indoor.

[0157] C. FR1 licensed spectrum in FDD.

[0158] D. Spectrum deployment in-band to NR, in guard-band to LTE / NR, in standalone band(s).

[0159] E. Traffic types DO-DTT, DT, with focus on rUC1 (indoor inventory) and rUC4 (indoor command).

[0160]

[0161] From RAN#104, the study will assess whether the harmonized air interface design (per bullet 'A' above) can address the DO-A (Device-originated autonomous) use case.

[0162] Only to identify which part(s) of the harmonized air interface design (per bullet 'A' above) is / are not sufficient for the DO-A use case.

[0163] Transmission from Ambient IoT devices (including backscattering when used) can occur at least in UL spectrum.

[0164]

[0165] The following objectives are set within the General Scope:

[0166]

[0167] 1. Evaluation assumptions

[0168] a) Conclude at least the following aspects of design targets left to WGs in Clause 5 (RAN design targets) of TR 38.848 [RAN1]:

[0169]

[0170] Clause 5.3: Applicable maximum distance target value(s)

[0171] Clause 5.6: Refine the definition of latency suitable for use in RAN WGs

[0172] Clause 5.8: 2D distribution of devices

[0173] b) Define necessary further evaluation assumptions of deployment scenarios for coverage and coexistence evaluations [RAN1, RAN4].

[0174] c) Identify basic blocks / components of possible Ambient IoT device architectures, taking into account state of the art implementations of low-power low-complexity devices which meet the RAN design target for power consumption and complexity. [RAN1].

[0175] d) Define link budget calculation for coverage, including whether / how to model carrier wave from node(s) inside or outside the connectivity topology.

[0176]

[0177] NOTE: Assessment performance of the design targets is conducted within the study of feasibility and necessity of proposals in the following objectives, e.g., by inspection of reference implementations in the field, simulations, and analytically.

[0178] NOTE: Strive to minimize evaluation cases in RAN1.

[0179]

[0180] 2. Study necessary and feasible solutions for Ambient IoT as prescribed in the General Scope.

[0181] Determining which functions, procedures, etc. are needed and not needed, and ensuring at least the required functionalities in Section 6.2 of TR 38.848.

[0182] Study of positioning in Rel-19 is RAN3-led, limited to functionalities which would have no, or minimal, specification impact.

[0183] Note: this does not imply any decision relating to WI creation.

[0184] Study the feasibility and required functionalities for proximity determination.

[0185] Coordination with SA3 is required for privacy aspects.

[0186] RAN1-led:

[0187] For the Ambient IoT DL and UL, study the following items:

[0188] Frame structure, synchronization and timing, random access

[0189] Numerologies, bandwidths, and multiple access

[0190] Waveforms and modulations

[0191] Channel coding

[0192] Downlink channel / signal aspects

[0193] Uplink channel / signal aspects

[0194] Scheduling and timing relationships

[0195] Study necessary characteristics of carrier-wave waveform for a carrier wave provided externally to the Ambient IoT device, including for interference handling at Ambient IoT UL receiver and at NR basestation.

[0196] For Topology 2, no difference in physical layer design from Topology 1.

[0197] RAN2-led:

[0198] Study and decide which functions are needed for an Ambient IoT compact protocol stack and lightweight signaling procedure to enable DO-DTT and DT data transmission, and study those functions.

[0199] example:

[0200] Paging

[0201] Random access

[0202] Data transmission, including necessary radio resource control aspects, respecting the limitation in the General Scope

[0203] Interactions with upper layers

[0204] For functionalities not listed above, they are studied only if found essential.

[0205] RAN3-led:

[0206] Identify necessary impacts on signaling and procedures for CN-RAN interface to enable:

[0207] Paging

[0208] Device context management

[0209] Data transport

[0210] Identify RAN architecture aspects, including whether support for split architecture is necessary.

[0211] Identify potential solutions for locating an Ambient IoT device with no specification impact, e.g., reusing existing user location report, or minimal specification impact to convey location information to core network.

[0212] RAN4-led:

[0213] Coexistence study of Ambient IoT and NR / LTE.

[0214] RF requirements study for Ambient IoT:

[0215] Ambient IoT BS transmission and reception

[0216] Ambient IoT Device, as per the General Scope, transmission and reception

[0217] Intermediate node (UE), as per the General Scope, transmission and reception

[0218] RAN2 and RAN3 are expected to identify RAN-CN functional split in coordination with SA2.

[0219]

[0220] Note: This study shall target for an IoT segment well below the existing 3GPP IoT technologies, e.g., NB-IoT, eMTC, RedCap, etc.

[0221] This study shall not aim to replace existing 3GPP LPWA technologies.

[0222]

[0223] Device type

[0224] As described above, the device types of AmIoT (ambient IoT) devices are divided into two types as follows, and there is a design target to pursue a harmonized air interface design that minimizes differences between device types.

[0225] 1) Type 1: It has a maximum power consumption of approximately 1 uW, is capable of storing energy, has no amplification function, and performs uplink transmission by backscattering a carrier wave (CW) provided from an external source (e.g., a reader such as a base station or UE, or a separate node).

[0226] 2) Type 2: It has a maximum power consumption of approximately several hundred microwatts, is capable of storing energy, has an amplification function, and performs uplink transmission by backscattering a carrier wave (CW) provided from the outside (e.g., a base station or a reader such as a UE or a separate node) or by using an internally generated signal.

[0227]

[0228] Topology

[0229] Among the topologies captured in TR 38.848, release 19 SI primarily considers the following two topologies.

[0230] 1) Topology #1: BS ↔ Ambient IoT device

[0231] a. Direct communication between base stations and AmIoT devices in a micro-cell environment

[0232] b. The base station is located co-site with a base station equipped with existing 3GPP technology.

[0233] 2) Topology #2: BS ↔ intermediate node ↔ Ambient IoT device

[0234] a. An intermediate node exists between the base station and the AmIoT device in a macro-cell environment.

[0235] b. The base station is located co-site with a base station equipped with existing 3GPP technology.

[0236] c. Intermediate nodes are limited to UEs and are located indoors.

[0237] Additionally, we are focusing on the FDD licensed spectrum in FR1, and transmissions from AmIoT devices can occur at least in the FDD UL spectrum.

[0238]

[0239] Technical terms used in this disclosure

[0240] - SSB: Synchronization Signal Block

[0241] - MIB: Master Information Block

[0242] - RMSI: Remaining Minimum System Information

[0243] - FR1: Frequency Range 1. Refers to the frequency range below 6 GHz (e.g., 450 MHz to 6000 MHz).

[0244] - FR2: Frequency Range 2. Refers to the millimeter wave (mmWave) range above 24 GHz (e.g., 24250 MHz to 52600 MHz).

[0245] - BW: Bandwidth

[0246] - BWP: Bandwidth Part

[0247] - RNTI: Radio Network Temporary Identifier

[0248] - CRC: Cyclic Redundancy Check

[0249] - SIB: System Information Block

[0250] - SIB1: SIB1 for NR devices = RMSI (Remaining Minimum System Information). Broadcasts information necessary for NR terminals to connect to the cell.

[0251] - CORESET (COntrol REsource SET): Time / frequency resource for NR terminal to attempt candidate PDCCH decoding

[0252] - CORESET#0: CORESET for Type0-PDCCH CSS set for NR devices (configured in MIB)

[0253] - Type0-PDCCH CSS set: a search space set in which an NR UE monitors a set of PDCCH candidates for a DCI format with CRC scrambled by a SI-RNTI

[0254] - MO: PDCCH Monitoring Occasion for Type0-PDCCH CSS set

[0255] - SIB1-R: (additional) SIB1 for reduced capability NR devices. May be limited to cases where it is generated as a separate TB from SIB1 and transmitted on a separate PDSCH.

[0256] - CORESET#0-R: CORESET#0 for reduced capability NR devices

[0257] - Type0-PDCCH-R CSS set: a search space set in which an redcap UE monitors a set of PDCCH candidates for a DCI format with CRC scrambled by a SI-RNTI

[0258] - MO-R: PDCCH Monitoring Occasion for Type0-PDCCH CSS set

[0259] - Cell defining SSB (CD-SSB): SSB containing RMSI scheduling information among NR SSBs

[0260] Non-cell defining SSB (non-CD-SSB): An SSB that is placed in the NR sync raster but does not contain RMSI scheduling information for the corresponding cell for measurement purposes. However, it may contain information indicating the location of the cell defining SSB.

[0261] - SCS: subcarrier spacing

[0262] - SI-RNTI: System Information Radio-Network Temporary Identifier

[0263] - Camp on: “Camp on” is the UE state in which the UE stays on a cell and is ready to initiate a potential dedicated service or to receive an ongoing broadcast service.

[0264] - TB: Transport Block

[0265] - RSA (Redcap standalone): Redcap device 또는 service만 지원하는 cell.

[0266] - SIB1(-R)-PDSCH: SIB1(-R)을 전송하는 PDSCH

[0267] - SIB1(-R)-DCI: SIB1(-R)-PDSCH를 scheduling하는 DCI. DCI format 1_0 with CRC scrambled by SI-RNTI.

[0268] - SIB1(-R)-PDCCH: SIB1(-R)-DCI를 전송하는 PDCCH

[0269] - FDRA: Frequency Domain Resource Allocation

[0270] - TDRA: Time Domain Resource Allocation

[0271] - RA: Random Access

[0272] - MSGA: preamble and payload transmissions of the random access procedure for 2-step RA type.

[0273] - MSGB: response to MSGA in the 2-step random access procedure. MSGB may consist of response(s) for contention resolution, fallback indication(s), and backoff indication.

[0274] - RO-N: normal UE 4-step RACH and 2-step RACH(if configured)를 위한 RO(RACH Occasion)

[0275] - RO-N1, RO-N2: When a separate RO is set for normal UE 2-step RACH, it is divided into RO-N1 (4-step) and RO-N2 (2-step).

[0276] - RO-R: RO (RACH Occasion) set separately from RO-N for redcap UE 4-step RACH and 2-step RACH (if configured)

[0277] - RO-R1, RO-R2: When separate ROs are set for redcap UE 2-step RACH, they are distinguished as RO-R1 (4-step) and RO-R2 (2-step).

[0278] - PG-R: MsgA-Preambles Group for redcap UEs

[0279] - RAR: Random Access Response

[0280] - RAR window: the time window to monitor RA response(s)

[0281] - FH: Frequency Hopping

[0282] - iBWP: initial BWP

[0283] - iBWP-DL(-UL): initial DL(UL) BWP

[0284] - iBWP-DL(-UL)-R: (separate) initial DL(UL) BWP for RedCap

[0285] - CS: Cyclic shift

[0286] - NB: Narrowband

[0287] - TO: Traffic Offloading

[0288] -mMTC; Massive Machine Type Communications

[0289] - eMBB: enhanced Mobile Broadband Communication

[0290] - URLLC: Ultra-Reliable and Low Latency Communication

[0291] - RedCap: Reduced Capability

[0292] - eRedCap: enhanced RedCap

[0293] - FDD: Frequency Division Duplex

[0294] - HD-FDD: Half-Duplex-FDD

[0295] - DRX: Discontinuous Reception

[0296] - RRC: Radio Resource Control

[0297] - RRM: Radio Resource Management

[0298] - IWSN: Industrial Wireless Sensor Network

[0299] - LPWA: Low Power Wide Area

[0300] - RB: Resource Block

[0301] - CCE: Control Channel Element

[0302] - AL: Aggregation Level

[0303] - PRG: Physical Resource-block Group

[0304] - DFT-s-OFDM: DFT-spread Orthogonal Frequency Division Multiplexing

[0305] - PBCH: Physical Broadcast Channel

[0306] - A-PBCH: Additional PBCH

[0307] - BD: blind detection

[0308] - EPRE: Energy Per RE

[0309] - SNR: Signal-to-Noise Ratio

[0310] - TDM: Time Division Multiplexing

[0311] - FDM: Frequency Division Multiplexing

[0312] - DMRS: DeModulation Reference Signal

[0313] - TDD: Time Division Duplex

[0314] - PCI: Physical layer Cell ID

[0315] - EH: Energy Harvesting

[0316] - EH device: A device that operates based on EH. It can include all of Device A / B / C being discussed in 3GPP. In addition, although this disclosure primarily considers RF EH, an EH device does not necessarily have to be RF EH-based.

[0317] - ES: Energizing Signal. A signal / channel transmitted by a base station / IN / AN / UE for the purpose of supplying RF energy to a device operating on RF-based energy harvesting. (Modulated) CW, NR / LTE DL / UL signals, etc. can be ES, and a dedicated signal / channel for ES can be designed to support it.

[0318] - ET: Energy Transfer

[0319] CW: Carrier wave. Ambient IoT devices supporting backscattering-based UL transmission transmit information by modulating and backscattering "externally provided" CW. Ambient IoT devices supporting independent signal generation-based UL transmission transmit information by modulating "internally generated" CW. Unless otherwise specified, "externally provided" CW for backscattering is assumed. CW can be used as an energizing signal (ES) for RF energy transfer.

[0320] - R: Reader / interrogator. This is a standard RFID term. In the 3GPP Ambient IoT context, readers can include gNB / eNB, intermediate / assisting nodes, and UEs, depending on the topology. Furthermore, Ambient IoT is not limited to 4G / 5G communication systems, and can include base stations, intermediate / assisting nodes, and UEs in next-generation communication systems.

[0321] - T: Tag / ambient IoT device. RFID standard term. In this disclosure, it can be interchanged with EH device, and in the 3GPP Ambient IoT context, it mainly refers to Ambient IoT device, Device A / B / C.

[0322] - R→T: Reader-to-Tag or Reader-to-Tag communication link. If the base station or intermediate / assisting node is the reader, it may have the same meaning as DL.

[0323] - T→R: Tag-to-Reader or Tag-to-Reader communication link. If the base station or intermediate / assisting node is the reader, it may have the same meaning as UL.

[0324] - R↔T: Includes cases of R→T and T→R, or R→T or T→R. It may be the case that both R→T and T→R apply.

[0325] - BS: Base Station

[0326] - IN: Intermediate node. In Topology 2 (BS ↔ IN ↔ Ambient IoT device), IN acts as the reader. Relay, IAB, UE, repeater, etc. can be IN.

[0327] - AN: Assisting node. It can assist DL transmission in Topology 3-1 (BS → AN → Ambient IoT device → BS), or assist UL transmission in Topology 3-2 (BS → Ambient IoT device → AN → BS). Relay, IAB, UE, repeater, etc. can be AN.

[0328] - UE: User Equipment. In the case of LTE, NR, or next-generation communication systems, it refers to the LTE, NR, or next-generation communication system UE / terminal, respectively. It is a general wireless communication terminal type that is distinct from Ambient IoT devices or Device A / B / C. In Topology 4 (UE ↔ Ambient IoT device), the UE acts as the reader.

[0329] - Device: Unless otherwise stated, and when used alone, refers to EH device, Ambient IoT device, or Device A / B / C indiscriminately.

[0330] - AmIoT: Ambient IoT

[0331] - F-gap: Frequency gap

[0332] - T-gap: Time gap

[0333] - TD: Time Domain

[0334] - FD: Frequency Domain

[0335] - PEI: Paging Early Indication

[0336] - LP-WUS: Low-Power Wake-Up Signal

[0337] - LP-SS: Low-Power Synchronization Signal

[0338] - RSRP: Reference Signal Received Power

[0339] - ESRP: ES Received Power. This may refer to RSRP measured using ES. It may have the same meaning as ES-RSRP.

[0340] - PRB: Physical Resource Block

[0341] - EH circuit: A circuit that performs EH operations. An EH device can be viewed as containing an EH circuit in component form.

[0342] - PHR: Power Headroom Report

[0343] - EHR: Energy Headroom Report

[0344] - BPF: Band-Pass Filter

[0345] - SM: Subcarrier Modulation

[0346]

[0347] Composition and Method of the Invention

[0348] In this disclosure, '()' can be interpreted as both excluding the content within () and including the content within the parentheses.

[0349] In this disclosure, ' / ' may mean including all of the contents separated by / (and) or including only some of the contents separated by / (or).

[0350] Ambient IoT devices can be characterized as maintenance-free, meaning they can operate permanently without battery replacement. This is achieved by harvesting energy from RF signals and / or other sources of ambient energy. According to 3GPP SA1 study results document TR 22.840, RF energy harvesting can have the following advantages and potential applications:

[0351] The main advantage of RF-based energy harvesting is its availability in deployed environments and the fact that RF power is controllable.

[0352] For example, power can be sent by a transmitter on demand or periodically.

[0353] Potential applications include logistics / warehouse, manufacturing, smart homes, health monitoring, and environmental monitoring etc.

[0354]

[0355] In the 3GPP Rel-18 Ambient IoT study, Ambient IoT devices were classified into the following types / classes.

[0356] (1) Device A: No energy storage, no independent signal generation, i.e. backscattering transmission

[0357] Complexity comparable to UHF passive RFID.

[0358] (2) Device B: Has energy storage, no independent signal generation, i.e. backscattering transmission. Use of stored energy can include amplification for reflected signals.

[0359] Complexity is expected to be somewhere b / w Device A and C.

[0360] (3) Device C: Has energy storage, has independent signal generation, i.e. active RF component for transmission.

[0361] Complexity will be orders of magnitude lower than NB-IoT.

[0362]

[0363] Additionally, the ongoing Rel-19 Ambient IoT solutions study classifies devices into the following two types / classes and pursues a harmonized air interface design that minimizes differences between device types / classes.

[0364] - Device i: has a maximum power consumption of approximately 1 uW, is capable of storing energy, has no amplification function, and performs uplink transmission by backscattering a carrier wave (CW) provided from an external source (e.g., a base station or a reader such as a UE or a separate node).

[0365] - Device ii: has a maximum power consumption of approximately several hundred microwatts, is capable of storing energy, has an amplification function, and performs uplink transmission by backscattering a carrier wave (CW) provided from the outside (e.g., a base station or a reader such as a UE or a separate node) or by using a signal generated internally.

[0366] In addition to the above classification methods, Ambient IoT device types / classes can be distinguished in various ways using parameters related to device characteristics (e.g., presence / capacity of energy storage, degree of energy / power consumption, presence / capability of amplification, presence / capability of BPF, supported DL / UL transmission method(s), etc.) or combinations of parameters. (Here, BPF capability can be distinguished by 3-dB bandwidth, sharpness, etc. of the supported BPF, and UL transmission methods can be distinguished by, for example, backscattered UL transmission, UL transmission by internal signal generation, etc.)

[0367] For some Ambient IoT device types / classes (e.g., Device B / C / i / ii), energy storage capability, i.e. capacitor or charging battery, may be provided for the following purposes:

[0368] - Securing stable energy at the time of reception / transmission

[0369] - Operation of low-power communication module through energy storage in low RF energy state

[0370] For example, the minimum RF Rx sensitivity for operating a low-power communication module may be -20 dBm, and the minimum Rx sensitivity for energy harvesting may be -20 dBm. In this case, if the ambient IoT device Rx power ranges between -30 and -20 dBm, communication is impossible without a capacitor, but communication may be possible after a charging time with a capacitor.

[0371] - Energy harvested from various energy sources (e.g., solar, thermal, wind, kinetic, etc.) is accumulated in a single capacitor and a low-power communication module is operated at a desired time.

[0372]

[0373] FIG. 5 is a diagram illustrating an example of power consumption according to the operating state of an energy harvesting-based device with energy storage capability in a system applicable to the present disclosure, and the device energy state at that time.

[0374] Figure 5 is an example of power consumption according to the operating state of an energy harvesting-based device with energy storage capability, and the device energy state at that time.

[0375] In the figure below of Fig. 5, S1 may be a sleep state, S2 may be an active state, and P1 and P2 may be power consumption in the S1 and S2 states, respectively.

[0376] Active state can mean a state in which the device consumes power to perform operations such as receiving / transmitting, sensing, etc. for communication, and sleep state can be a state that is not active.

[0377] The upper figure of Fig. 5 may be a device energy state corresponding to the figure below.

[0378] E1, E2 values ​​may vary by device (type / class) and may be reported by the device to the R / base station as capability parameters.

[0379] E2 can be defined as the energy value in the buffer state, and E1 can be defined as the minimum energy value required in the active state.

[0380] The transition from S1 to S2 is possible only when the device energy state value is Alt.G1) E2, or has reached E2, or is greater than Alt.G2) E1, i.e., is possible in the range of E1 to E2, and Alt.G1 is assumed in Fig. G1.

[0381] Ambient IoT devices can be implemented in a variety of connection topologies. For example, the Rel-18 Ambient IoT study defined the following four connection topologies to support Ambient IoT communications in 3GPP communication systems.

[0382] Topology (1): Base Station ↔ Ambient IoT device

[0383] NOTE: Includes the possibility of BS Rx and BS Tx in different BSs.

[0384] Topology (2): Base Station ↔ Intermediate Node ↔ Ambient IoT Device

[0385]

[0386] NOTE: Intermediate node can be relay, IAB, UE, repeater, etc. which is capable of ambient IoT.

[0387] Topology (3): Base Station ↔ Assisting Node ↔ Ambient IoT Device ↔ Base Station (Topology (3): BS ↔ Assisting Node ↔ Ambient IoT Device ↔ BS)

[0388] NOTE: Assisting node can be relay, IAB, UE, repeater, etc. which is capable of ambient IoT.

[0389] Topology (4): UE ↔ Ambient IoT device.

[0390] The present disclosure supports multiple carrier wave types with different characteristics for Ambient IoT communication, and allows a base station / IN / AN / UE to select a type / class / capability of Ambient IoT device and a communication network environment, thereby enabling a wireless communication system to support various Ambient IoT devices and services.

[0391]

[0392] Carrier wave support method for Ambient IoT communication

[0393] Ambient IoT devices can support backscattered UL transmission for low-power UL transmission. For example, the previously described Ambient IoT devices A / B / i / ii can support backscattered UL transmission. Ambient IoT devices require externally provided CW for backscattered UL transmission. CW can also be used to power Ambient IoT devices or as a carrier wave for DL ​​transmission, regardless of the UL transmission mode (i.e., backscattered UL transmission or internally generated UL transmission).

[0394] CW waveforms can be supported in various types. For example, they can be single-tone CW or more complex multi-tone waveforms. Single-tone CW uses fewer resources and thus can be advantageous over multi-tone CW in terms of tag or reader multiplexing capacity and interference. On the other hand, multi-tone CW offers advantages such as greater energy transfer when transmitting CW downlink and greater coverage from a single device.

[0395] Considering the somewhat conflicting advantages of these different CW waveform types, we propose a method to support multiple CW waveform types in an Ambient IoT system, allowing them to be configured by the base station / IN / AN / UE, and by Ambient IoT device type / class / capability.

[0396] In the present disclosure, if CW1 and CW2 are each composed of a single tone but the tones have different frequency positions, CW1 and CW2 can be classified as different CW waveform types. In addition, if CW3 and CW4 are each composed of multiple tones but the number of tones they comprise or the frequency positions they comprise are different, CW3 and CW4 can be classified as different CW waveform types.

[0397]

[0398] How the base station / IN / AN / UE sets / indicates the CW waveform type

[0399] In the Ambient IoT communication system, the supported CW waveform types can be set / defined in the spec in advance, and the base station / IN / AN / UE can select one of the supported CW waveform types and transmit it to the Ambient IoT device via DL. For example, single-tone CW and multi-tone CW are supported, and the base station / IN / AN / UE can select one of the single-tone CW and multi-tone CW and transmit it to the Ambient IoT device via DL. The base station / IN / AN / UE can set / instruct / indicate to the Ambient IoT device the CW waveform type to be used from the selected time (Ts, applied immediately if Ts=0) later (during a specific time Td, where Td can be defined in the form of a timing window) in the form of a preamble / frame-sync transmitted via DL or a command / message transmitted as a payload.

[0400] The base station / IN / AN / UE can configure / select a CW waveform type based on the Ambient IoT device type / class / capability report (after transmitting an ACK) or transmit the CW waveform type information selected / configured by the base station / IN / AN / UE (together with the Ambient IoT device type / class / capability) during paging (inventory), so that backscattering can be performed only for Ambient IoT devices (of a specific Ambient IoT device type / class or with capability) that support the selected / configured CW waveform type.

[0401] When an Ambient IoT device receives CW waveform type information transmitted by a base station / IN / AN / UE in the above manner, the Ambient IoT device can use the received CW waveform type information to determine whether to perform UL transmission (or whether to respond) (based on its own device type / class / capability) (in response to DL reception). Or, when UL transmission is possible, the device can decide between backscattered UL transmission and internally generated UL transmission. Or, the received CW waveform information can be used to determine UL transmission timing. For example, when performing UL transmission by receiving a single-tone CW type, a larger Td,max (maximum allowable response time for a DL command) value can be applied compared to when receiving a multi-tone CW type.

[0402] The above method is single-tone CW, but if the positions of the tones on the frequency are different and are defined as different CW waveform types, it can include a method in which N single-tone CWs with different tones positions are set / defined in advance in the spec, and the base station / IN / AN / UE selects one of the N single-tone CWs supported and transmits it to the Ambient IoT device as a DL. In this case, the base station / IN / AN / UE can set / instruct / display a value corresponding to the index of the single-tone CW selected from among the N single-tone CWs to the Ambient IoT device in the form of a preamble / frame-sync / command / message transmitted as a DL.

[0403] Or, when supporting multiple single-tone CWs with different tones in frequency position as above, the same CW waveform type can be defined and the relative frequency offset value can be set / indicated / displayed to the Ambient IoT device. To this end, one reference single-tone CW that can be a reference for the relative frequency offset value can be set / defined in advance, and the remaining N-1 single-tone CWs supported can be set / indicated / displayed as relative frequency offset values ​​from the reference single-tone CW. The reference single-tone CW can be, for example, the CW with the lowest / highest / center frequency position (e.g., lowest / highest / center SCS index) among the supported single-tone CWs.

[0404] The above frequency offset indication method can be used to support multiple multi-tone CW waveforms by applying different frequency shift values ​​based on a single multi-tone CW waveform. In the same manner as in the single-tone CW, a reference multi-tone CW can be defined, and the remaining multi-tone CWs supported can be set / indicated / indicated as relative frequency offset values ​​from the reference multi-tone CW. The reference multi-tone CW can be, for example, the CW at the lowest / highest / center frequency position (e.g., lowest / highest / center SCS index) among the supported multi-tone CWs.

[0405] Even if CW is frequency shifted and transmitted as DL as above, the base station / IN / AN / UE may want to fix the frequency position received as UL to a certain level due to interference issues, etc. For example, in order to support this operation, when the Ambient IoT device receives the (relative) frequency position information of the DL CW transmitted by the base station / IN / AN / UE in the above manner, it can use the received information to decide whether to perform UL transmission (or whether to respond) (based on its own device type / class / capability) (in response to DL reception), or determine the UL transmission frequency position during UL transmission. In the latter case, for example, when applying the frequency shift (by a method such as subcarrier modulation), the frequency shift value to be applied can be adjusted using the (relative) frequency position information of the received DL CW.

[0406]

[0407] How to set CW waveform type by device type / class / capability

[0408] In the Ambient IoT communication system, the CW waveform types supported are set / defined in advance in the spec for each Ambient IoT device type / class / capability, and the base station / IN / AN / UE can select one of the CW waveform types supported for each Ambient IoT device type / class / capability or for a specific device type / class / capability and transmit it to the Ambient IoT device as DL. This method may include setting one CW waveform type supported for a specific device type / class / capability, and supporting only a preset fixed form of CW waveform type for the corresponding device type / class / capability.

[0409] The base station / IN / AN / UE can set / instruct / indicate to the Ambient IoT device the CW waveform type to be used (during a specific time Td, where Td can be defined as a timing window) after a certain time (Ts, applied immediately if Ts=0) selected by Ambient IoT device type / class / capability, in the form of a preamble / frame-sync transmitted in DL or a command / message transmitted in the payload.

[0410] The base station / IN / AN / UE can set / select the final CW waveform type (after transmitting an ACK) based on the Ambient IoT device type / class / capability report, or can transmit the CW waveform type information selected / set by the base station / IN / AN / UE (together with the Ambient IoT device type / class / capability) during paging (inventory), so that backscattering can be performed only for Ambient IoT devices (of a specific Ambient IoT device type / class or with capability) that support the selected / set CW waveform type.

[0411] When an Ambient IoT device receives CW waveform type information transmitted by a base station / IN / AN / UE according to its Ambient IoT device type / class / capability, the Ambient IoT device can refer to the received CW waveform type information and / or the Ambient IoT device type / class / capability to determine whether to perform UL transmission (or whether to respond) (in response to DL reception) (based on its own device type / class / capability). Or, when UL transmission is possible, the device can decide between backscattered UL transmission and internally generated UL transmission. Or, the received CW waveform information can be used to determine the UL transmission timing. For example, when performing UL transmission by receiving a single-tone CW type, a larger Td,max (maximum allowable response time for a DL command) value can be applied compared to when receiving a multi-tone CW type.

[0412] [example]

[0413] - Only for device types / classes that support backscattered UL transmission (only), multiple CW waveform types can be preset so that the base station / IN / AN / UE can set / select them, and for device types / classes that support internally generated UL transmission or when operating in internally generated UL transmission mode, the CW waveform transmitted to DL can be fixed to a specific CW waveform type that is preset / defined, for example, as one of the following.

[0414] - Fixed to multi-tone for the purpose of increasing DL coverage, increasing energy transfer efficiency, etc.

[0415] - Fixed to single-tone for the purpose of saving DL resources and minimizing interference.

[0416]

[0417] Multi-channel / session support method

[0418] In order to shorten the time required by performing inventory / paging process simultaneously in an Ambient IoT communication system and / or to minimize collision by appropriately distributing DL / UL signals, multi-channel can be supported. Multi-channel can be composed of a set of frequency resources (of the same size or different sizes for each channel) that do not overlap each other. In a multi-channel environment, the CW waveform type related settings can be preset / defined in the spec for each channel in common and / or for each channel and / or for each device type / class / capability, or can be set / instructed / indicated to Ambient IoT in the form of a message / command transmitted as a preamble / frame-sync or payload transmitted by a base station / IN / AN / UE to a DL for a specific channel and / or for each channel and / or for each device type / class / capability.

[0419] In addition, in order to reduce the time required for inventory / paging in the Ambient IoT communication system, multiple sessions can be supported, and multiple parallel sessions can be opened to simultaneously perform inventory / paging processes for different Ambient IoT devices (types / classes / states). Here, multiple sessions can be configured as a set of logical or virtual channels through which inventory / paging processes are performed between Ambient IoT devices and base stations / IN / AN / UEs. In a multi-session environment, the CW waveform type-related settings can be preset / defined in the spec for each session in common and / or by each session and / or by each device type / class / capability, or can be configured / instructed / indicated to Ambient IoT in the form of a message / command transmitted as a preamble / frame-sync or payload transmitted by the base station / IN / AN / UE to DL for each specific session and / or by each session and / or by each device type / class / capability.

[0420] Alternatively, when supporting multiple channels / sessions, channels / sessions can be configured / set for each CW waveform type, or multiple channels / sessions can be configured / set for each CW waveform type.

[0421] In the above multi-channel / session environment, Ambient IoT devices can be assigned to different channels / sessions based on device type / class / state, UL transmission payload characteristics, UL transmission timing / number of times, etc., or a combination thereof, and inventory / paging processes can be performed simultaneously.

[0422]

[0423] [Description of the first device (base station / IN / AN / UE) claim]

[0424] The embodiments described below are specifically described with reference to FIG. 6 in terms of the operation of the first device. The methods described below are distinguished for convenience of explanation, and it is understood that some components of one method may be substituted for or combined with some components of another method, as long as they are not mutually exclusive.

[0425] FIG. 6 is a diagram illustrating an example of an operation process of a first device in a system applicable to the present disclosure.

[0426] In the embodiment of FIG. 6, the first device may correspond to a base station / IN / AN / UE, and the second device may correspond to an Ambient IoT device.

[0427] In step S610, the first device transmits waveform information related to a specific waveform type among a plurality of waveform types to the second device. The plurality of waveform types include at least one single-tone waveform type and at least one multi-tone waveform type.

[0428] At step S620, the first device receives capability information of the second device related to support of the specific waveform from the second device.

[0429] At step S630, the first device transmits to the second device a request message for uplink transmission (UL transmission) based on the specific waveform type.

[0430] At step S640, the first device receives the uplink transmission from the second device based on the request message.

[0431]

[0432] According to various embodiments of the present disclosure, the waveform information may include information on a reference waveform type and information on a relative frequency offset with respect to the reference waveform type. The specific waveform type may be based on the reference waveform type and the frequency offset.

[0433] According to various embodiments of the present disclosure, the capability information may include information on whether the second device supports a single-tone waveform type or a multi-tone waveform type.

[0434] According to various embodiments of the present disclosure, the uplink transmission may be related to backscattered UL transmission or internally generated UL transmission based on the capability information.

[0435] According to various embodiments of the present disclosure, an uplink transmission may be based on an uplink transmission timing window associated with the specific waveform type. The uplink transmission timing window may have a larger value when the specific waveform type is associated with at least one single-tone waveform type than when the specific waveform type is associated with at least one multi-tone waveform type.

[0436] According to various embodiments of the present disclosure, the at least one singletone waveform type may be associated with a plurality of singletone waveforms having different tonal positions. Each of the plurality of singletone waveforms may be associated with a different index. The waveform information may include an index associated with the specific waveform.

[0437] According to various embodiments of the present disclosure, the waveform information may be transmitted in the form of a preamble, frame synchronization, command, or message.

[0438]

[0439] According to various embodiments of the present disclosure, a first device is provided in a wireless communication system. The first device includes a transceiver and at least one processor, wherein the at least one processor is configured to perform the operating method of the first device according to FIG. 6.

[0440]

[0441] According to various embodiments of the present disclosure, an apparatus for controlling a first device in a wireless communication system is provided. The apparatus includes at least one processor and at least one memory operably connected to the at least one processor. The at least one memory may be configured to store instructions for performing an operating method of the first device according to FIG. 6 based on instructions executed by the at least one processor.

[0442]

[0443] According to various embodiments of the present disclosure, one or more non-transitory computer-readable media (CRM) storing one or more instructions are provided. The one or more instructions, when executed by one or more processors, perform operations, and the operations may include a method of operating a first device according to FIG. 6.

[0444]

[0445] [Description of the second device (Ambient IoT device) claim]

[0446] The embodiments described below are specifically described with reference to FIG. 7 in terms of the operation of a second device (Reader / interrogator or base station (BS)). The methods described below are distinguished for convenience of explanation, and it is understood that some components of one method may be substituted for some components of another method, or may be applied in combination with each other, as long as they are not mutually exclusive.

[0447] FIG. 7 is a diagram illustrating an example of an operation process of a second device in a system applicable to the present disclosure.

[0448] In the embodiment of FIG. 7, the first device may correspond to a base station / IN / AN / UE, and the second device may correspond to an Ambient IoT device.

[0449] In step S710, the second device receives waveform information related to a specific waveform type among a plurality of waveform types from the first device. The plurality of waveform types include at least one single-tone waveform type and at least one multi-tone waveform type.

[0450] At step S720, the second device transmits capability information of the second device related to support of the specific waveform to the first device.

[0451] At step S730, the second device receives a request message for uplink transmission (UL transmission) based on the specific waveform type from the first device.

[0452] At step S740, the second device transmits the uplink transmission to the first device based on the request message.

[0453]

[0454] According to various embodiments of the present disclosure, the waveform information may include information on a reference waveform type and information on a relative frequency offset with respect to the reference waveform type. The specific waveform type may be based on the reference waveform type and the frequency offset.

[0455] According to various embodiments of the present disclosure, the capability information may include information on whether the second device supports a single-tone waveform type or a multi-tone waveform type.

[0456] According to various embodiments of the present disclosure, the uplink transmission may be related to backscattered UL transmission or internally generated UL transmission based on the capability information.

[0457] According to various embodiments of the present disclosure, an uplink transmission may be based on an uplink transmission timing window associated with the specific waveform type. The uplink transmission timing window may have a larger value when the specific waveform type is associated with at least one single-tone waveform type than when the specific waveform type is associated with at least one multi-tone waveform type.

[0458] According to various embodiments of the present disclosure, the at least one singletone waveform type may be associated with a plurality of singletone waveforms having different tonal positions. Each of the plurality of singletone waveforms may be associated with a different index. The waveform information may include an index associated with the specific waveform.

[0459] According to various embodiments of the present disclosure, the waveform information may be received in the form of a preamble, frame synchronization, command, or message.

[0460]

[0461] According to various embodiments of the present disclosure, a second device is provided in a wireless communication system. The second device includes a transceiver and at least one processor, wherein the at least one processor may be configured to perform the operating method of the second device according to FIG. 7.

[0462]

[0463] According to various embodiments of the present disclosure, an apparatus for controlling a second device in a wireless communication system is provided. The apparatus includes at least one processor and at least one memory operably connected to the at least one processor. The at least one memory may be configured to store instructions for performing an operating method of the second device according to FIG. 7 based on instructions executed by the at least one processor.

[0464]

[0465] According to various embodiments of the present disclosure, one or more non-transitory computer-readable media (CRM) storing one or more commands are provided. The one or more commands, when executed by one or more processors, perform operations, and the operations may include a method of operating a second device according to FIG. 7.

[0466]

[0467] Wireless devices applicable to the present disclosure

[0468] Below, examples of wireless devices to which various embodiments of the present disclosure are applied are described.

[0469] FIG. 8 is a diagram illustrating an example of the structure of a first device and a second device in a system applicable to the present disclosure.

[0470] The first device (1600) may include a processor (1610), an antenna unit (1620), a transceiver (1630), and a memory (1640).

[0471] The processor (1610) performs baseband-related signal processing and may include a higher layer processing unit (1611) and a physical layer processing unit (1615). The higher layer processing unit (1611) may process operations of a MAC layer, an RRC layer, or higher layers. The physical layer processing unit (1615) may process operations of a PHY layer. For example, when the first device (1600) is a base station device in base station-to-terminal communication, the physical layer processing unit (1615) may perform uplink reception signal processing, downlink transmission signal processing, etc. For example, when the first device (1600) is a first terminal device in terminal-to-terminal communication, the physical layer processing unit (1615) may perform downlink reception signal processing, uplink transmission signal processing, sidelink transmission signal processing, etc. In addition to performing baseband-related signal processing, the processor (1610) may also control the overall operation of the first device (1600).

[0472] The antenna unit (1620) may include one or more physical antennas, and when it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (1630) may include an RF (Radio Frequency) transmitter and an RF receiver. The memory (1640) may store information processed by the processor (1610), and software, an operating system, applications, etc. related to the operation of the first device (1600), and may also include components such as a buffer.

[0473] The processor (1610) of the first device (1600) may be configured to implement the operation of the base station in the base station-to-terminal communication (or the operation of the first terminal device in the terminal-to-terminal communication) in the embodiments described in the present disclosure.

[0474]

[0475] The second device (1650) may include a processor (1660), an antenna unit (1670), a transceiver (1680), and a memory (1690).

[0476] The processor (1660) performs baseband-related signal processing and may include a higher layer processing unit (1661) and a physical layer processing unit (1665). The higher layer processing unit (1661) may process operations of a MAC layer, an RRC layer, or higher layers. The physical layer processing unit (1665) may process operations of a PHY layer. For example, when the second device (1650) is a terminal device in base station-terminal communication, the physical layer processing unit (1665) may perform downlink reception signal processing, uplink transmission signal processing, etc. For example, when the second device (1650) is a second terminal device in terminal-to-terminal communication, the physical layer processing unit (1665) may perform downlink reception signal processing, uplink transmission signal processing, sidelink reception signal processing, etc. In addition to performing baseband-related signal processing, the processor (1660) may also control the overall operation of the second device (1660).

[0477] The antenna unit (1670) may include one or more physical antennas, and when including multiple antennas, may support MIMO transmission and reception. The transceiver (1680) may include an RF transmitter and an RF receiver. The memory (1690) may store information processed by the processor (1660), and software, an operating system, applications, etc. related to the operation of the second device (1650), and may also include components such as a buffer.

[0478] The processor (1660) of the second device (1650) may be configured to implement operations of the terminal in base station-to-terminal communication (or operations of the second terminal device in terminal-to-terminal communication) in the embodiments described in the present disclosure.

[0479] In the operation of the first device (1600) and the second device (1650), the same explanations given for the base station and the terminal (or the first terminal and the second terminal in the terminal-to-terminal communication) in the examples of the present disclosure may be applied, and any duplicate explanations are omitted.

[0480]

[0481] Here, the wireless communication technology implemented in the device (1600, 1650) of the present disclosure may include various other wireless communication technologies as well as LTE, NR, and 6G.

[0482]

[0483] The claims described in the various embodiments of the present disclosure may be combined in various ways. For example, the technical features of the method claims of the various embodiments of the present disclosure may be combined and implemented as a device, and the technical features of the device claims of the various embodiments of the present disclosure may be combined and implemented as a method. Furthermore, the technical features of the method claims of the various embodiments of the present disclosure may be combined and implemented as a device, and the technical features of the method claims of the various embodiments of the present disclosure may be combined and implemented as a method.

Claims

1. In a method performed by a first device, A step of transmitting waveform information related to a specific waveform type among a plurality of waveform types to a second device; The above plurality of waveform types include at least one single-tone waveform type and at least one multi-tone waveform type; A step of receiving capability information of the second device related to support of the specific waveform from the second device; A step of transmitting a request message for uplink transmission (UL transmission) based on the specific waveform type to the second device; comprising a step of receiving the uplink transmission based on the request message from the second device; method.

2. In paragraph 1, The above waveform information includes information of a reference waveform type and information of a relative frequency offset for the reference waveform type, The above specific waveform type is based on the above reference waveform type and the above frequency offset. method.

3. In paragraph 1, The above capability information includes information on whether the second device supports a single-tone waveform type or a multi-tone waveform type. method.

4. In paragraph 3, The above uplink transmission is related to backscattered UL transmission or internally generated UL transmission based on the above capability information. method.

5. In paragraph 1, Uplink transmission is based on an uplink transmission timing window associated with the specific waveform type, The above uplink transmission timing window has a larger value when the specific waveform type is associated with the at least one singletone waveform type than when the specific waveform type is associated with the at least one multitone waveform type. method.

6. In paragraph 1, The at least one single tone waveform type is associated with a plurality of single tone waveforms having different tonal positions, Each of the above multiple singleton waveforms is associated with a different index, The waveform information includes an index associated with the specific waveform. method.

7. In paragraph 1, The above waveform information is transmitted in the form of a preamble, frame synchronization, command, or message. method.

8. In a method performed by a second device, A step of receiving waveform information related to a specific waveform type among a plurality of waveform types from a first device; The above plurality of waveform types include at least one single-tone waveform type and at least one multi-tone waveform type; A step of transmitting capability information of the second device related to support of the specific waveform to the first device; A step of receiving a request message for uplink transmission (UL transmission) based on the specific waveform type from the first device; A step of transmitting the uplink transmission based on the request message to the first device, method.

9. In paragraph 8, The above waveform information includes information of a reference waveform type and information of a relative frequency offset for the reference waveform type, The above specific waveform type is based on the above reference waveform type and the above frequency offset. method.

10. In paragraph 8, The above capability information includes information on whether the second device supports a single-tone waveform type or a multi-tone waveform type. method.

11. In paragraph 10, The above uplink transmission is related to backscattered UL transmission or internally generated UL transmission based on the above capability information. method.

12. In paragraph 8, Uplink transmission is based on an uplink transmission timing window associated with the specific waveform type, The above uplink transmission timing window has a larger value when the specific waveform type is associated with the at least one singletone waveform type than when the specific waveform type is associated with the at least one multitone waveform type. method.

13. In paragraph 8, The at least one single tone waveform type is associated with a plurality of single tone waveforms having different tonal positions, Each of the above multiple singleton waveforms is associated with a different index, The waveform information includes an index associated with the specific waveform. method.

14. In paragraph 8, The above waveform information is received in the form of a preamble, frame synchronization, command, or message. method.

15. In the first device, Transmitter and receiver; at least one processor; and At least one memory operably connectable to said at least one processor and storing instructions that, when executed by said at least one processor, perform operations; The above actions are, Comprising all steps of the method according to any one of claims 1 to 7, First device.

16. In the second device, Transmitter and receiver; at least one processor; and At least one memory operably connectable to said at least one processor and storing instructions that, when executed by said at least one processor, perform operations; The above actions are, Comprising all steps of the method according to any one of claims 8 to 14, Second device.

17. In a control device that controls the first device, at least one processor; and comprising at least one memory operably connected to at least one of the processors; The at least one memory stores instructions for performing operations based on being executed by the at least one processor, The above actions are, Comprising all steps of the method according to any one of claims 1 to 7, controller.

18. In a control device that controls a second device, at least one processor; and comprising at least one memory operably connected to at least one of the processors; The at least one memory stores instructions for performing operations based on being executed by the at least one processor, The above actions are, Comprising all steps of the method according to any one of claims 8 to 14, controller.

19. In one or more non-transitory computer-readable media storing one or more instructions, The one or more instructions perform operations based on being executed by one or more processors, The above actions are, Comprising all steps of the method according to any one of claims 1 to 7, Computer readable medium.

20. In one or more non-transitory computer-readable media storing one or more instructions, The one or more instructions perform operations based on being executed by one or more processors, The above actions are, Comprising all steps of the method according to any one of claims 8 to 14, Computer readable medium.

Images