Method for r2d transmission and reception and device therefor

Abstract

A method according to an embodiment of the present specification comprises the steps in which: a device receives a first signal from a reader; the device transmits, to the reader, a second signal triggered on the basis of the first signal; and the device receives a third signal from the reader on the basis of the second signal. A frequency resource related to the third signal is determined on the basis of the first signal.

Description

Method and apparatus for R2D transmission and reception

[0001] This specification relates to a method and apparatus for R2D transmission and reception.

[0002] The 5G mobile communication system is a successor technology to LTE (Long Term Evolution) and is a new clean-slate type of mobile communication system characterized by high performance, low latency, and high availability. In the case of 5G NR, all available spectrum resources can be utilized, ranging from low-frequency bands below 1 GHz to intermediate frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz. Based on the underlying technology of 5G mobile communication, 6G mobile communication systems are being developed.

[0003] The 6G (wireless communication) system aims for (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) reduced energy consumption of battery-free IoT (internet of things) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity.

[0004] Meanwhile, in Rel-19, the reader transmits signals (e.g., R2D signal, R2D message, PRDCH) by fixing the frequency position.

[0005] As mentioned above, the existing method does not specify a procedure for the reader to select / update different frequency resources over time for transmission. Therefore, if the reader repeatedly performs transmission from a fixed frequency resource / frequency location, the effects of continuous interference or frequency-selective fading existing in a specific frequency band accumulate, which may increase the reception failure rate and cause frequent retransmissions.

[0006] The purpose of this specification is to propose a method for solving the aforementioned problems.

[0007] The technical problems to be solved in this specification are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this specification belongs from the description below.

[0008] A method according to an embodiment of the present specification for solving the aforementioned technical problem comprises the steps of receiving a first signal from a reader by a device, transmitting a second signal triggered by the first signal to the reader by the device, and receiving a third signal from the reader by the device based on the second signal. The frequency resources associated with the third signal are determined based on the first signal. Since the frequency resources related to R2D transmission can be indicated / determined / changed in advance, the effects of interference and fading in R2D-related procedures can be distributed across the time-frequency domain to improve average reception quality, and resource concentration can be mitigated to reduce collision probability and delay.

[0009] According to an embodiment of the present specification, a frequency resource associated with a third signal is determined based on a first signal that triggers / schedules a second signal transmission. Accordingly, by allowing a device to receive a third signal (R2D transmission) that can be updated to a different frequency resource over time, resistance to interference and frequency-selective fading can be improved through the frequency dispersion effect over time in R2D-related procedures.

[0010] In addition, since the range of resource areas requiring monitoring for reception related to the third signal is limited, the device power consumption required for monitoring for reception of the third signal can be reduced compared to operation according to existing procedures (e.g., A-IoT random access procedure or R2D related procedure).

[0011] In addition, since the resources of the third signal are pre-assigned by the first signal (e.g., R2D signal) that schedules / triggers the second signal (e.g., D2R signal), the latency of the procedure related to the third signal can be reduced while ensuring R2D scheduling flexibility in an A-IoT environment where many devices (sensors, tags, etc.) exist.

[0012] In addition, since the frequency resources associated with the third signal are determined based on the first signal scheduling the second signal rather than a separate signal / signaling scheduling the third signal, the signaling overhead required for frequency resource indication in R2D-related procedures can be reduced.

[0013] The effects obtainable in this specification are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which this specification belongs from the description below.

[0014] Figure 1 illustrates a topology 1 related to Ambient IoT.

[0015] Figure 2 illustrates topology 2 related to Ambient IoT.

[0016] Figure 3 is an example of topology 3 related to Ambient IoT.

[0017] Figure 4 is another example of topology 3 related to Ambient IoT.

[0018] Figure 5 illustrates topology 4 related to Ambient IoT.

[0019] Figure 6 illustrates the state according to the operating state of an energy harvesting-based device.

[0020] Figure 7 is a diagram illustrating scenarios of topology 1.

[0021] Figure 8 is a diagram illustrating scenarios of topology 2.

[0022] Figure 9 illustrates the structure of device type 1.

[0023] FIG. 10 illustrates the structure of device type 2a.

[0024] Figure 11 illustrates the structure of device type 2b.

[0025] Figure 12 illustrates the entire AS procedure between the device and the reader.

[0026] FIG. 13 illustrates resource allocation for messages of a random access procedure according to an embodiment of the present specification.

[0027] FIG. 14 illustrates TDM resources for D2R transmission according to an embodiment of the present specification.

[0028] FIG. 15 illustrates a repetitive transmission based on TDM resources for D2R transmission according to an embodiment of the present specification.

[0029] FIG. 16 illustrates FDM resources for D2R transmission according to an embodiment of the present specification.

[0030] FIG. 17 illustrates a repetitive transmission based on FDM resources for D2R transmission according to an embodiment of the present specification.

[0031] FIG. 18 illustrates resources for D2R transmission according to an embodiment of the present specification.

[0032] FIG. 19 illustrates resources for R2D transmission according to an embodiment of the present specification.

[0033] FIG. 20 illustrates a repetitive transmission based on TDM resources for R2D transmission according to an embodiment of the present specification.

[0034] FIG. 21 illustrates a repetitive transmission based on FDM resources for R2D transmission according to an embodiment of the present specification.

[0035] FIG. 22 illustrates a table for determining transmission resources according to an embodiment of the present specification.

[0036] FIG. 23 illustrates the structure of Control information and PRDCH or PDRCH according to an embodiment of the present specification.

[0037] FIG. 24 illustrates a transmission including a preamble and a postamble according to an embodiment of the present specification.

[0038] FIG. 25 illustrates a MAC Payload structure according to an embodiment of the present specification.

[0039] FIG. 26 illustrates D2R transmission and midamble transmission according to an embodiment of the present specification.

[0040] FIG. 27 is a flowchart illustrating a method according to one embodiment of the present specification.

[0041] FIG. 28 is a flowchart illustrating a method according to another embodiment of the present specification.

[0042] FIG. 29 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.

[0043] In this specification, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0044] A slash ( / ) or a comma used in this specification 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."

[0045] In this specification, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

[0046] Additionally, in this specification, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Also, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

[0047] Additionally, parentheses used in this specification 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 this specification is not limited to "PDCCH," and "PDCCH" 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."

[0048] In the following explanation, 'when, if, in case of' can be replaced with 'based on'.

[0049] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.

[0050] In this specification, the terminal (UE, User Equipment) may be a portable device and may be a second node that receives a signal from a base station / first node / IAB node.

[0051] In this specification, a base station (BS, Base Station) may be a base station / first node / IAB node / transmission-reception point.

[0052] In this specification, a higher layer parameter may be a parameter that is set for the terminal, pre-set, or pre-defined. For example, a base station or a network may transmit the higher layer parameter to the terminal. For example, the higher layer parameter may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0053] In this specification, "set or defined" may be interpreted as being set or pre-configured to the device through pre-defined signaling (e.g., SIB, MAC, RRC) from a base station or network. In this specification, "set or defined" may be interpreted as being pre-configured to the device.

[0054] In the following, the downlink (DL) refers to communication from a base station to a terminal, and the uplink (UL) refers to communication from a terminal to a base station. In the downlink, the transmitter may be part of the base station and the receiver may be part of the terminal. In the uplink, the transmitter may be part of the terminal and the receiver may be part of the base station. The base station may be referred to as the first communication device and the terminal as the second communication device. The base station (BS) may be replaced by terms such as fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), Access Point (AP), network (5G network), AI system, RSU (road side unit), vehicle, robot, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, the terminal may be fixed or mobile and may be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, robot, AI module, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device.

[0055] Ambient IoT communication (Rel-18) >

[0056] Ambient IoT (A-IoT) can be a new type of device or segment that operates solely on energy harvested from the surrounding environment. For example, A-IoT can refer to a new type of Internet of Things device that operates by being powered by various energy sources harvestable from the surrounding environment, such as radio waves, light, motion, and thermal energy. Examples of A-IoT use cases are shown in Table 1 below.

[0057]

[0058] Table 2 shows matters related to IoT communication discussed in the 3GPP RAN.

[0059]

[0060] For example, active signal generation and / or backscattering may be one of the communication technologies considered to achieve low-power operation of A-IoT devices. For example, backscattering is a widely used technique in radio frequency identification (RFID) that can enable a device to communicate with a network by reflecting incident waves after modulating them with information to be transmitted. For example, the device may be powered by an incident RF signal or stored energy.

[0061] For example, A-IoT devices can be classified into various device types, such as passive, semi-passive, and active, depending on the energy storage and transmission signal generation methods. For example, a passive device does not have an energy storage device (e.g., a capacitor) and can communicate based on backscatter communication technology. For example, a semi-passive device has an energy storage device and can communicate using backscatter communication technology with the assistance of the energy storage device. For example, an active device has an energy storage device and can communicate by actively generating signals using active RF components and stored energy. For example, in the present disclosure, the following three types of IoT devices may be considered. For example, device A may be a device without energy storage and without independent signal generation (e.g., a device supporting backscatter transmission). For example, device B may be a device with energy storage and without independent signal generation (e.g., a device supporting backscatter transmission). In this case, for example, the use of the stored energy may include amplification of the reflected signal. For example, device C may be a device with energy storage and independent signal generation (e.g., a device with an active RF component for transmission).

[0062] For example, the following basic topologies may be considered to support A-IoT devices in indoor and outdoor scenarios. For example, basic topologies may include a direct connection between a base station and an A-IoT device, a connection between a base station, an intermediate node, and an A-IoT device, support for connection by an auxiliary node, and / or a connection between a terminal and an A-IoT device. The basic topologies proposed in this disclosure are merely examples, and the proposals of this disclosure may be extended and applied to other topologies.

[0063] Figure 1 illustrates a topology 1 related to Ambient IoT.

[0064] Specifically, FIG. 1 shows a topology (e.g., Topology 1) in which a base station and an A-IoT device are directly connected according to one embodiment of the present disclosure. The embodiment of FIG. 1 may be combined with various embodiments of the present disclosure.

[0065] Referring to FIG. 1, an A-IoT device (Ambient IoT device) can communicate directly and bidirectionally with a base station (BS). For example, communication between the base station and the A-IoT device may include A-IoT data and / or signals. For example, A-IoT data and / or signals may be transmitted or received based on a control channel and / or a data channel (e.g., a shared channel). In the embodiment of FIG. 1, the base station transmitting to the A-IoT device and the base station receiving from the A-IoT device may be different. For example, in the topology 1, the base station and the A-IoT device in a micro-cell environment may communicate directly with each other. For example, the base station may be located at a co-site with a base station equipped with existing 3GPP technology.

[0066] Figure 2 illustrates topology 2 related to Ambient IoT.

[0067] Specifically, FIG. 2 illustrates a topology (e.g., Topology 2) in which a base station (BS) and an A-IoT device (Ambient IoT device) are connected through an intermediate node, according to one embodiment of the present disclosure. The embodiment of FIG. 2 may be combined with various embodiments of the present disclosure.

[0068] Referring to FIG. 2, an A-IoT device can communicate bidirectionally with an intermediate node between the device and the base station. Here, for example, the intermediate node may be an A-IoT-enabled relay, IAB node, terminal, repeater, etc. For example, the intermediate node may transmit A-IoT data and / or signals between the base station and the A-IoT device. For example, A-IoT data and / or signals may be transmitted or received based on a control channel and / or a data channel (e.g., a shared channel). In the embodiment of FIG. 2, the intermediate node transmitting to the A-IoT device and the intermediate node receiving from the A-IoT device may be different. For example, in the topology 2, an intermediate node may exist between the base station in a macro-cell environment and the A-IoT device. For example, the base station may be located at a co-site with a base station equipped with existing 3GPP technology. For example, the intermediate node can be limited to a terminal, and the intermediate node can be located indoors.

[0069] Figure 3 is one example of topology 3 related to Ambient IoT. Figure 4 is another example of topology 3 related to Ambient IoT.

[0070] FIGS. 3 and 4 illustrate a topology (e.g., topology 3) supported by an assisting node according to one embodiment of the present disclosure. The embodiment of FIGS. 3 and 4 may be combined with various embodiments of the present disclosure.

[0071] Referring to FIG. 3, an auxiliary node may be supported for downlink reception. For example, an A-IoT device may transmit data / signals to a base station, and the A-IoT device may receive data / signals from an auxiliary node. Referring to FIG. 4, an auxiliary node may be supported for uplink transmission. For example, an A-IoT device may receive data / signals from a base station, and the A-IoT device may transmit data / signals to an auxiliary node. Here, for example, the auxiliary node may be an A-IoT-enabled relay, IAB node, terminal, repeater, etc.

[0072] Figure 5 illustrates topology 4 related to Ambient IoT.

[0073] Specifically, FIG. 5 illustrates a topology (e.g., topology 4) in which a terminal (UE) and an A-IoT device (Ambient IoT device) are directly connected according to one embodiment of the present disclosure. The embodiment of FIG. 5 may be combined with various embodiments of the present disclosure.

[0074] Referring to FIG. 5, an A-IoT device can communicate bidirectionally with a terminal. For example, communication between the terminal and the A-IoT device may include A-IoT data and / or signals. For example, A-IoT data and / or signals may be transmitted or received based on a control channel and / or a data channel (e.g., a shared channel).

[0075] For example, transmission by an A-IoT device can be performed in the frequency division duplexing (FDD) spectrum (e.g., FDD UL spectrum).

[0076] < Ambient IoT solutions SI (Rel-19) >

[0077] 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 is scheduled to proceed in 3GPP NR release 19 based on the following.

[0078] This study aims to further evaluate Ambient IoT at the RAN WG level, a new 3GPP IoT technology suitable for deployment in 3GPP systems, which relies on ultra-low complexity devices with ultra-low power consumption for very low-level IoT applications. This study must provide a clear differentiation; that is, it must address use cases and scenarios that cannot be met based on existing 3GPP LPWA IoT technologies (e.g., NB-IoT with reduced peak Tx power).

[0079] General range

[0080] The definitions provided in TR 38.848 apply to this SI, and the following are exclusive general scopes.

[0081] A. The overall objective is to research a harmonized wireless interface design that minimizes differences when Ambient IoT is required to enable the following devices.

[0082] i. ~1μW peak power consumption, energy storage, initial sampling frequency offset (SFO) of up to 10X ppm, no DL or UL amplification in the device. The device's UL transmission is backscattered from the externally provided carrier wave.

[0083] ii. Peak power consumption ≤ hundreds of μW1, energy storage, initial sampling frequency offset (SFO) of up to 10X ppm, and DL and / or UL amplification in the device. UL transmission in the device may be generated internally or backscattered from carrier waves provided externally.

[0084] -X is determined in WG.

[0085] -Coverage design target: Up to 10-50m distance with the device indoors according to TR 38.848: "...range where WG can sub-select".

[0086] - According to TR 38.848, for Topologies 1 and 2 (UEs acting as intermediate nodes under NW control), there is no RRC state, no mobility (i.e., no functions such as cell selection / reselection at least), no HARQ, and no ARQ.

[0087] Note 1: It should be understood that the WG has no duty to set a specific value for "≤ hundreds of μW", and that determining whether the proposed design and its power consumption meet the "≤ hundreds of μW" requirement is a matter for the WG to discuss.

[0088] B. Deployment scenarios with the following characteristics, referring to the table in Clause 4.2.2 of TR 38.848:

[0089] - Deployment Scenario 1 using Topology 1

[0090] Base Station and Coexistence Characteristics: Microcells, Co-sites

[0091] - Deployment Scenario 2 using a UE as an intermediate node under Topology 2 and network control

[0092] Base Station and Coexistence Characteristics: Macro Cells, Co-sites

[0093] The location of the intermediate node is indoors

[0094] C. FDD's FR1 License Spectrum.

[0095] D. In-band spectrum distribution for NR, guard band for LTE / NR, standalone band(s)

[0096] E. Traffic types DO-DTT, DT focused on rUC1 (Indoor Inventory) and rUC4 (Indoor Command).

[0097] - In RAN#104, this study evaluates whether a harmonized wireless interface design (see bullet point 'A' above) can handle DO-A (Device-Initiated Autonomous) use cases and identifies which parts of the harmonized wireless interface design (see bullet point 'A' above) are insufficient for DO-A use cases.

[0098] Transmission from surrounding IoT devices (including backscattering when in use) may occur at least within the UL spectrum.

[0099] The next goal is set within the general range.

[0100] 1. Evaluation Assumptions

[0101] a) Conclude at least the following aspects of the design objectives left to the WG in Clause 5 (RAN Design Objectives) of TR 38.848 [RAN1].

[0102] Clause 5.3: Applicable maximum distance target value

[0103] Clause 5.6: Refine the definition of latency suitable for use in the RAN WG.

[0104] Clause 5.8: 2D distribution of the device

[0105] b) Define the necessary additional evaluation assumptions for deployment scenarios for coverage and coexistence evaluation. [RAN1, RAN4]

[0106] c) Identify the basic blocks / components of possible peripheral IoT device architectures by considering modern implementations of low-power, low-complexity devices that meet RAN design goals regarding power consumption and complexity. [RAN1]

[0107] d) Define link budget calculations for coverage, including whether / how to model carrier waves at nodes inside or outside the connection topology.

[0108] Note: The evaluation performance of the design target falls within the scope of the feasibility and necessity study of the proposal in the following objectives. For example, it involves inspecting the reference implementation in the field, performing simulations, and conducting analytical analysis.

[0109] Note: We strive to minimize evaluation cases in RAN1.

[0110] 2. Investigate necessary and viable solutions for Ambient IoT as defined in the general scope. This includes determining which functions, procedures, etc. are necessary and which are not, and ensuring at least the essential functions specified in Section 6.2 of TR 38.848.

[0111] Rel-19 localization studies are led by RAN3 and are limited to features that have no or minimal impact on the specification (Note: This does not imply decisions related to WI generation).

[0112] We study the feasibility and necessary functions for proximity determination (coordination with SA3 is necessary for privacy reasons).

[0113] - RAN1-led:

[0114] For Ambient IoT DL and UL:

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

[0116] Numerology, Bandwidth, and Multiple Access

[0117] Waveform and Modulation

[0118] Channel coding

[0119] Downlink Channel / Signal Aspect

[0120] Uplink Channel / Signal Side

[0121] Scheduling and Timing Relationships

[0122] We study the necessary characteristics of carrier wave waveforms provided externally to ambient IoT devices, including interference processing at ambient IoT UL receivers and NR base stations.

[0123] For Topology 2, there is no difference in the physical layer design compared to Topology 1.

[0124] RAN2 Lead:

[0125] We research and determine the functions required for the Ambient IoT Compact Protocol stack and lightweight signaling procedures that enable DO-DTT and DT data transmission, and study those functions.

[0126] for example:

[0127] Paging

[0128] Random access

[0129] Data transmission including necessary wireless resource control aspects that comply with general range limitations

[0130] Interaction with the upper class

[0131] Features not listed above are researched only if deemed essential.

[0132] RAN3 Leading:

[0133] Identify the necessary effects on the signals and procedures of the CN-RAN interface to enable the following.

[0134] Paging

[0135] Device Context Management

[0136] Data transmission

[0137] Identify RAN architecture aspects, including whether partitioned architecture support is required.

[0138] Identify potential solutions for finding Ambient IoT devices without impacting specifications. For example, reuse existing user location reports or transmit location information to the core network with minimal impact on specifications.

[0139] RAN4 Leading:

[0140] Research on the coexistence of Ambient IoT and NR / LTE.

[0141] Research on RF Requirements for Ambient IoT:

[0142] Ambient IoT BS Transmitter / Receiver

[0143] Ambient IoT devices and transmission / reception based on general range

[0144] Intermediate node (UE) and transmission / reception based on general range

[0145] RAN2 and RAN3 are expected to cooperate with SA2 to identify RAN-CN functional splits.

[0146] Note: This study targets IoT segments that are much lower than existing 3GPP IoT technologies (e.g., NB-IoT, eMTC, RedCap, etc.). This study does not aim to replace existing 3GPP LPWA technologies.

[0147] For example, as described above, the types of A-IoT devices can be classified into two as follows. For example, a Type 1 device has a maximum power consumption of approximately 1 uW, is capable of energy storage, has no amplification function, and can perform transmission by backscattering a carrier wave (CW) provided from an external source (e.g., a reader such as a base station or terminal, or a separate node). For example, a Type 2 device has a maximum power consumption of approximately several hundred uW, is capable of energy storage, has an amplification function, and can perform transmission by backscattering a carrier wave (CW) provided from an external source (e.g., a reader such as a base station or terminal, or a separate node) or by using a signal generated internally.

[0148] For example, in addition to the classification methods described above, the type / class of an A-IoT device may be distinguished based on parameters associated with device characteristics (e.g., presence / capacity of energy storage, degree of energy / power consumption, presence / capability of amplification, presence / capability of a band-pass filter (BPF), supported DL / UL transmission method(s), etc.) or combinations of parameters. Here, for example, the BPF capability may be distinguished by the 3-dB bandwidth of the supported BPF, sharpness, etc., and the UL transmission methods may be distinguished by, for example, backscattered UL transmission, UL transmission by internal signal generation, etc.

[0149] In addition, the type / class of an A-IoT device may be subdivided based on parameters associated with the above device characteristics (e.g., presence / capacity of energy storage, degree of energy / power consumption, presence / capability of amplification, presence / capability of a band-pass filter (BPF), supported DL / UL transmission method(s), etc.) or combinations of such parameters. For example, the above-described Type 2 device may be classified into Type 2a when it performs transmission by backscattering a carrier wave (CW) provided from an external source (e.g., a reader such as a base station or terminal, or a separate node), and Type 2b when it performs transmission using a signal generated internally. In this case, Types 2a and 2b may be identical in that they have a maximum power consumption of approximately several hundred uW, are capable of energy storage, and have amplification capabilities.

[0150] For example, some types / classes of A-IoT devices (e.g., device B, device C, type 1 device, and / or type 2 device) may be equipped with energy storage capabilities (e.g., capacitors or charging batteries) for the following purposes.

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

[0152] - Operation of low-power communication modules through energy storage in low RF energy states

[0153] For example, the minimum RF reception sensitivity for operating a low-power communication module may be -20dBm, and the minimum reception sensitivity for energy harvesting may be -20dBm. In this case, if the received power of the A-IoT device is distributed between -30 and -20dBm, communication may be impossible without a capacitor, and communication may be possible after a charging time with a capacitor.

[0154] - Store energy harvested from different energy sources (e.g., solar, thermal, wind, kinetic, etc.) in a single capacitor to operate a low-power communication module at a desired time.

[0155] Figure 6 illustrates the state according to the operating state of an energy harvesting-based device.

[0156] Specifically, FIG. 6 illustrates examples of power consumption and device energy status according to the operating state of an energy harvesting-based device having energy storage capacity, according to one embodiment of the present disclosure. The embodiment of FIG. 6 may be combined with various embodiments of the present disclosure.

[0157] Referring to FIG. 6(b), S1 may be a sleep state, S2 may be an active state, and P1 and P2 may be power consumption in S1 and S2, respectively. For example, the active state may refer to a state in which the device consumes power to perform operations such as receiving / transmitting for communication or sensing, and the sleep state may be a state that is not an active state.

[0158] FIG. 6(a) may represent the device energy state corresponding to FIG. 6(b). Referring to FIG. 6(a), the E1 and E2 values ​​may vary by device (type / class), and the device may report information related to the E1 value and / or information related to the E2 value to R and / or the base station as capability parameters. For example, the E2 value may be defined as the energy value in the buffered state, and the E1 value as the minimum energy value required in the active state.

[0159] For example, the transition from S1 to S2 may be possible only when the device energy state value is E2 or when E2 is reached. For example, the transition from S1 to S2 may be possible when the device energy state value is greater than E1 (i.e., within the range between E1 and E2). An embodiment of FIG. 6 illustrates an example in which the transition from S1 to S2 is performed when the device energy state value is E2 or when E2 is reached.

[0160] For example, an A-IoT device may require an externally provided CW for backscatter transmission. For example, the CW can be used to supply energy to A-IoT devices or as a CW for DL ​​transmission, regardless of the transmission mode (e.g., backscatter transmission or internally generated transmission).

[0161] For example, CW waveforms can be supported in various types. For instance, the type of CW waveform can be a single-tone CW waveform or a somewhat complex multi-tone CW waveform. For instance, single-tone CW may be advantageous over multi-tone CW in terms of the multiplexing capacity of tags or readers and in terms of interference, as it uses fewer resources. On the other hand, multi-tone CW has advantages, such as the ability to deliver more energy when transmitting CW over DL and to secure greater coverage on a single device.

[0162] Considering the advantages of these different CW waveform types, multiple CW waveform types may be supported in an A-IoT system, and the base station / IN / AN / UE may configure the CW waveform type. For example, one or more CW waveform types supported in the A-IoT communication system may be pre-configured / defined, and the base station / IN / AN / UE may select one of the one or more supported CW waveform types and transmit it to an A-IoT device. For example, the base station / IN / AN / UE may configure / instruct / display the selected CW waveform type to the A-IoT device in the form of a command / message transmitted as a preamble / frame-sync or payload.

[0163] For example, in the present disclosure, for A-IoT communication, at least one of the necessary characteristics of a carrier waveform for a carrier provided outside the A-IoT device (including interference handling at the A-IoT device UL receiver and NR base station) may be proposed. For example, in the present disclosure, for A-IoT communication, at least one of paging, random access, data transmission including necessary radio resource control aspects complying with general range limitations, interaction with upper layers (e.g., RRC layer, NAS (non-access stratum) layer, application layer, etc.), device context management, data transmission, coexistence of A-IoT and 6G / NR / LTE, and / or RF requirements for A-IoT may be proposed.

[0164] For example, technical terms used in this specification may be as follows.

[0165] - SSB: Synchronization Signal Block

[0166] - MIB: Master Information Block

[0167] - RMSI: Remaining Minimum System Information

[0168] - FR1: Frequency Range 1. Refers to the frequency range of 6 GHz or lower (e.g., 450 MHz ~ 6000 MHz).

[0169] - FR2: Frequency Range 2. Refers to the millimeter wave (mmWave) region of 24 GHz or higher (e.g., 24250 MHz ~ 52600 MHz).

[0170] - BW: Bandwidth

[0171] - BWP: Bandwidth Part

[0172] - RNTI: Radio Network Temporary Identifier

[0173] - CRC: Cyclic Redundancy Check

[0174] - SIB: System Information Block

[0175] - SIB1: SIB1 for NR devices = RMSI (Remaining Minimum System Information). Broadcasts information necessary for cell connection of NR terminals.

[0176] - CORESET: Control REsource SET. The time / frequency resource at which the terminal attempts candidate PDCCH decoding.

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

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

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

[0180] - SIB1-R: (additional) SIB1 for reduced capability NR devices. This may be limited to cases where it is created as a separate TB from SIB1 and transmitted via a separate PDSCH.

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

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

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

[0184] - Cell defining SSB (CD-SSB): An NR SSB that includes RMSI scheduling information

[0185] - Non-cell defining SSB (non-CD-SSB): Refers to an SSB deployed in an NR sync raster that does not include the corresponding cell's RMSI scheduling information for measurement purposes. However, it may include information indicating the location of the cell defining SSB.

[0186] - SCS: subcarrier spacing

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

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

[0189] - TB: Transport Block

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

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

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

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

[0194] - FDRA: Frequency Domain Resource Allocation

[0195] - TDRA: Time Domain Resource Allocation

[0196] - RA: Random Access

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

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

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

[0200] - RO-N1, RO-N2: When separate ROs are configured for normal UE 2-step RACH, they are distinguished as RO-N1 (4-step) and RO-N2 (2-step).

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

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

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

[0204] - RAR: Random Access Response

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

[0206] - FH: Frequency Hopping

[0207] - iBWP: initial BWP

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

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

[0210] - CS: Cyclic shift

[0211] - NB: Narrowband

[0212] - TO: Traffic Offloading

[0213] -mMTC; Massive Machine Type Communications

[0214] - eMBB: enhanced Mobile Broadband Communication

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

[0216] - RedCap: Reduced Capability

[0217] - eRedCap: enhanced RedCap

[0218] - FDD: Frequency Division Duplex

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

[0220] - DRX: Discontinuous Reception

[0221] - RRC: Radio Resource Control

[0222] - RRM: Radio Resource Management

[0223] - MM: Mobility Management

[0224] - IWSN: Industrial Wireless Sensor Network

[0225] - LPWA: Low Power Wide Area

[0226] - RB: Resource Block

[0227] - CCE: Control Channel Element

[0228] - AL: Aggregation Level

[0229] - PRG: Physical Resource-block Group

[0230] - DFT-s-OFDM: DFT-spread OFDM

[0231] - PBCH: Physical Broadcast Channel

[0232] - A-PBCH: Additional PBCH

[0233] - BD: blind detection

[0234] - EPRE: Energy Per RE

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

[0236] - TDM: Time Division Multiplexing

[0237] - FDM: Frequency Division Multiplexing

[0238] - DMRS: DeModulation Reference Signal

[0239] - TDD: Time Division Duplex

[0240] - PCI: Physical layer Cell ID

[0241] - EH: Energy Harvesting

[0242] - EH device: A device that operates based on EH. It may include all of Device A / B / C currently under discussion by 3GPP. Additionally, while this specification primarily considers RF EH, the EH device does not necessarily have to be RF EH-based.

[0243] - 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 an RF-based energy harvesting basis. (Modulated) CW, NR / LTE DL / UL signals, etc. can be ES, and a dedicated signal / channel for ES can be designed to support it.

[0244] - ET: Energy Transfer

[0245] - CW: Carrier wave. Ambient IoT devices supporting backscattering-based UL transmission transmit information by modulating and backscattering the “externally provided” CW. Ambient IoT devices supporting independent signal generation-based UL transmission transmit information by modulating the “internally generated” CW. Unless otherwise noted, it is assumed to refer to the “externally provided” CW for backscattering. The CW can be used as an ES (Energizing Signal) for RF energy transfer.

[0246] - CWN: Carrier Wave Node. A node that provides the above CW. It may be a base station, IN, AN, or UE, and a separate CWN may exist for the purpose of providing CW.

[0247] - R: Reader / Interrogator. This is an RFID standard term. In the 3GPP Ambient IoT context, depending on the topology, gNBs / eNBs, intermediate / assisting nodes, UEs, etc., can act as readers. Furthermore, since Ambient IoT is not limited to 4G / 5G communication systems, it can include base stations, intermediate / assisting nodes, and UEs of next-generation communication systems. It may also refer to an Ambient IoT reader.

[0248] - T: Tag / ambient IoT device. An RFID standard term. It may be interchangeable with EH device in this specification, and in the 3GPP Ambient IoT context, it primarily refers to Ambient IoT device, Device A / B / C. The abbreviation 'T' above may be interpreted / replaced with 'D', which signifies Ambient IoT Device.

[0249] - D: Ambient IoT device (may have the same meaning as T above)

[0250] - 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 or forward link. 'R=>T' can be interpreted / replaced with 'R=>D' (Reader-to-Device).

[0251] - R2D: R-to-D link (Can be synonymous with R=>T. Can be denoted as R=>D.)

[0252] - CW2D: CWN-to-D link (CW node to Ambient IoT device link)

[0253] - T=>R: Tag-to-Reader or Tag-to-Reader communication link. If the base station or intermediate / assisting node is a reader, it may have the same meaning as a UL or reverse / backward link. 'T=>R' can be interpreted / substituted as 'D=>R' (Device-to-Reader).

[0254] - D2R: May have the same meaning as T=>R. Can be written as D=>R.

[0255] - R<=>T: Includes cases of R=>T and T=>R, or R=>T or T=>R. May apply to both R=>T and T=>R.

[0256] - R<=>D: Includes cases of R2D and D2R, or R2D or D2R. May apply to both R2D and D2R. (May have the same meaning as R<=>T)

[0257] - RF-EH: RF energy harvesting

[0258] - PRDCH: Physical R2D CHannel (may be denoted as PR2DCH). Physical channel for R2D communication.

[0259] - PDRCH: Physical D2R CHannel (may be denoted as PD2RCH). Physical channel for D2R communication.

[0260] - BS: Base Station

[0261] - IN: Intermediate node. In Topology 2 (BS ↔ IN ↔ Ambient IoT device), IN acts as a reader. Relays, IABs, UEs, repeaters, etc., can be INs.

[0262] - AN: Assisting node. It can assist with DL transmission in Topology 3-1 (BS -> AN -> Ambient IoT device -> BS) or assist with UL transmission in Topology 3-2 (BS -> Ambient IoT device -> AN -> BS). Relays, IABs, UEs, repeaters, etc. can be ANs.

[0263] - 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 form distinct from Ambient IoT devices or Devices A / B / C. In Topology 4 (UE ↔ Ambient IoT device), the UE acts as a reader.

[0264] - Device: Unless otherwise noted, and when used alone, it refers to the EH device, Ambient IoT device, or Device A / B / C without distinction.

[0265] - AmIoT: Ambient IoT (=A-IoT)

[0266] - F-gap: Frequency gap

[0267] - T-gap: Time gap

[0268] - TD: Time Domain

[0269] - FD: Frequency Domain

[0270] - PEI: Paging Early Indication

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

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

[0273] - RSRP: Reference Signal Received Power

[0274] - ESRP: ES Received Power. May refer to RSRP measured using ES. May have the same meaning as ES-RSRP.

[0275] - PRB: Physical Resource Block

[0276] - EH circuit: A circuit that performs EH operation. An EH device can be viewed as including the EH circuit as a component.

[0277] - PHR: Power Headroom Report

[0278] - EHR: Energy Headroom Report

[0279] - BPF: Band-Pass Filter

[0280] - SM: Subcarrier Modulation

[0281] The methods proposed in this specification can be applied commonly to topology 1 and topology 2, and UE1 as gNB and IN is referred to as reader for convenience. Additionally, the embodiments of this specification can be extended to cases where the reader receiving the BSS may directly generate and transmit the CW, or where the node transmitting the CW is a separate node from the reader.

[0282] As used herein, an Ambient IoT BS (base station) (e.g., reader) may be a gNB in ​​topology 1 and a specific UE in topology 2. Additionally, an Ambient IoT device (e.g., tag) as used herein may be interpreted as an Ambient IoT device in both topology 1 and / or topology 2. This will be explained below with reference to Table 3, FIG. 7, and FIG. 8.

[0283] Table 3 illustrates Ambient IoT scenarios. In Table 3, R is the leader, D is the device, and CW is the CW node. In Table 3, the D1T1 series scenarios are topology 1 scenarios. Figure 7 is a diagram illustrating topology 1 scenarios. In Table 3, the D2T2 series scenarios are topology 2 scenarios. Figure 8 is a diagram illustrating topology 2 scenarios.

[0284] In this case, depending on the scenario, the leader for R2D transmission and the leader for D2R reception may be the same or different nodes. Additionally, depending on the scenario, the CW node performing CW2D transmission may be the same or different node as the leader.

[0285]

[0286] The structure of device type 1 / 2a / 2b will be explained below with reference to FIGS. 9 to 11.

[0287] FIG. 9 illustrates the structure of device type 1. FIG. 10 illustrates the structure of device type 2a. Devices 1 and 2a perform D2R transmission by backscattering CW.

[0288] FIG. 11 illustrates the structure of device type 2b. Device 2b is equipped with a local oscillator at the transmitting end so that it can perform D2R transmission without the assistance of CW.

[0289] Device 1 is a simple structure that does not have amplifiers for R2D reception and D2R transmission at the receiving end and transmitting end, respectively. In contrast, devices 2a and 2b are structures that have a reflection amplifier and a power amplifier at the transmitting end, respectively, for D2R transmission.

[0290] Meanwhile, this specification proposes preamble, midamble, and postamble design methods that can be used for Ambient IoT transmission and reception. In this specification, the term "x-amble" is used to refer collectively to preamble, midamble, and postamble. Characteristically, a preamble refers to a transmission that occurs at the very beginning of a specific D2R or R2D transmission, a midamble in the middle, and a postamble at the very end.

[0291] Meanwhile, the preamble, midamble, and postamble mentioned in this specification may be transmitted together with D2R, R2D transmissions (e.g., PDRCH, PRDCH), etc., or may be transmitted included in said D2R, R2D transmissions.

[0292] The device ID mentioned in this specification may refer to a unique ID embedded within each device. However, instead of the device ID used in this specification, a method of using an ID such as a C-RNTI that can be exchanged between devices / readers during the inventory round phase may also be considered.

[0293] The state mentioned in this specification refers to states such as ON / SLEEP / OFF to increase the available time of a device in an Ambient IoT system. In this case, the ON state is defined as a state in which the device can perform TX / RX while consuming energy. The SLEEP state is defined as a state in which the device can perform energy harvesting without performing TX / RX, while maintaining memory content or timer / clock, etc., from the ON state. The OFF state is defined as a state in which the device can perform energy harvesting without maintaining memory content or timer / clock, etc., from the ON state, and without performing TX / RX.

[0294] In this document, ' / ' means 'and', 'or', or 'and / or' depending on the context.

[0295] Figure 12 illustrates the entire AS procedure between the device and the reader.

[0296] The entire Access Stratum (AS) procedure can be summarized as follows.

[0297] Step A: A-IoT paging. Upon a service request, the reader sends an A-IoT paging message specifying the device(s) requiring a response.

[0298] Step B: Transmission of D2R data (Device ID). The triggered A-IoT device(s) perform device ID transmission either through the A-IoT random access procedure or without using the procedure.

[0299] Step C1: (If necessary) R2D data transmission (e.g., Reader -> Device data transmission for command transmission)

[0300] Step C2: (If necessary) D2R data transmission (e.g., device -> reader data transmission for response to command)

[0301] In step A of FIG. 12, paging (i.e., Msg0) may include one or more device IDs, a device group ID, or all devices, so that one or more or all devices that receive it may trigger the random access procedure of Step B.

[0302] In Step B of FIG. 12, Msg1 / Msg2 / Msg3 / (Msg4) are each considered for a random access (RA) procedure to be performed by multiple devices in an Ambient IoT system. Among these, Msg1 / Msg3 are D2R signals / channels transmitted by the device, and Msg2 / (Msg4) are R2D signals / channels transmitted by the reader. In this specification, 'Msg1' can be interpreted / replaced as an Access Random ID message, 'Msg2' can be interpreted / replaced as a Random ID Response message, and 'Msg3' can be interpreted / replaced as a D2R message (Device to Reader, D2R, message). At this time, if the Reader sets / instructs multiple devices to a time gap index / frequency gap index for D2R transmission, the Msg1 / Msg3 of the multiple devices can be transmitted via TDM / FDM. In this specification, 'time gap index' may be interpreted as a value related to a time domain resource, a value related to a time resource, or a value based on a time resource indication field. Additionally, in this specification, 'frequency gap index' may be interpreted as a value related to a frequency domain resource, a value related to a frequency resource, or a value based on a frequency resource indication field. On the other hand, Msg2 is primarily considered to use TDM. This is based on the following technical considerations. Since the presence or absence of bandpass filtering capability varies by device (or device type), it may be difficult for each device to appropriately filter and receive multiple FDMed R2D signals / channels transmitted via FDM from the reader. Considering this, TDM is considered for the transmission of Msg2.

[0303] This specification proposes a method for configuring TDMed / FDMed resources for Msg1 / Msg2 / Msg3 / (Msg4) in a contention-based access procedure (or random access procedure) in an ambient IoT system.

[0304] As used in this specification, the term "slot" may refer to a slot considered in slotted ALOHA operation. Such a slot may have a variable length in the time domain depending on the reader's settings or instructions. Alternatively, in A-IoT, a slot in slotted ALOHA may be defined as an access occasion.

[0305] TDM / FDM transmission of Msg1 and Msg3

[0306] In this specification, a case where the Msg1 resource undergoes TDM & FDM can be considered, and a case where the Msg3 resource also undergoes TDM & FDM can be considered. For example, a case can be considered where the Msg1 resource undergoes TDM n times within a specific slot in an inventory round to generate n sub-slots, and each sub-slot undergoes FDM m times to generate m frequency domain resources. In such a case where Msg1 undergoes TDM & FDM, Msg3 can also be considered to undergo TDM & FDM in a similar manner.

[0307] Specifically, after receiving Msg2 within the aforementioned specific slot, the Msg3 resource is TDMed n times to create n sub-slots, and each sub-slot is FDMed m times to create m frequency domain resources. Meanwhile, when the Msg1 resource is configured by TDMing and FDMing as described above, the corresponding Msg2 resource can be TDMed and transmitted. At this time, the Msg2 resource can be configured / defined to be TDMed and transmitted in the order of time first - frequency second (or frequency first - time second) relative to the Msg1 resource. This can be illustrated as shown in Fig. 13.

[0308] FIG. 13 illustrates resource allocation for messages of a random access procedure according to an embodiment of the present specification.

[0309] Specifically, in Fig. 13, we considered the case where n=3 and m=2, and the Msg2 resource is arranged in a frequency first - time second manner based on the Msg1 resource. Specifically, based on the Msg1 resource, the Msg2 resource can be arranged first in an increasing order of frequency index within the same time index, and then the time index can be increased, and the Msg2 resource can be arranged consecutively in an increasing order of frequency index within that time index.

[0310] In the case where multiple responses to multiple Msg1s are transmitted to Msg2 as described above, the device sets a Msg2 transmission window after a certain period of time following the transmission of Msg1 and begins monitoring the transmission of Msg2 during the window. At this time, the start time and length of the window can be indicated / set by the reader through the L1 control info, L2 control info, MAC CE, or premable of Msg0 that triggered the Msg1. If Msg0 does not indicate / set / include the start time and length of the window, or if the L1 control info, L2 control info, MAC CE, or premable of Msg0 indicates / sets the exclusion of the start time and length of the window, the device determines the start time and length of the window using a stored pre-defined value and monitors Msg2. Alternatively, if Msg0's L1 control info, L2 control info, MAC CE, or premable instructs the use of a pre-defined value, the device monitors Msg2 by determining the window start time and length using the stored pre-defined value.

[0311] More specifically, a specific 1 bit of L1 or L2 control information or MAC CE indicates whether to use a pre-defined value or to set the window start time and length using a value specified or set thereafter. If the specific 1 bit indicates a value to be specified or set, the device obtains the value from the bits following that specific 1 bit and uses the obtained value to set the window start time and length. However, if the specific 1 bit indicates the use of a pre-defined value, the device determines that there are no bits specifying a value to be specified or set following that specific 1 bit. That is, in this case, the reader does not include bits specifying a value to be specified or set in the L1 or L2 control information or MAC CE following the specific 1 bit.

[0312] Furthermore, in the embodiments of this specification, one cell refers to one sub-slot in time, and adjacent sub-slots of adjacent cells may be assigned to be physically adjacent or separated by a certain time interval. Also, one cell refers to one frequency resource for one D2R transmission in frequency, and adjacent frequency resources of adjacent cells may be assigned to be physically adjacent or separated by a certain frequency interval.

[0313] Additionally, in the embodiments of this specification, a single R2D or D2R transmission / repeated transmission may be transmitted by filling all resources within the sub-slot or by filling only a portion thereof. In the case of partial transmission, the device may transmit such that the start and end of each R2D or D2R transmission / repeated transmission fall within the allocated sub-slot, or transmit such that only the start of each R2D or D2R transmission / repeated transmission falls within the allocated sub-slot, or transmit such that only the end of each R2D or D2R transmission / repeated transmission falls within the allocated sub-slot.

[0314] In this specification, 'R2D transmission' may be interpreted / replaced as 'R2D signal', 'R2D information', 'R2D message', or 'PRDCH'. Also, 'D2R transmission' may be interpreted / replaced as 'D2R signal', 'D2R information', 'D2R message', or 'PDRCH'. Additionally, 'frequency hopping' may be interpreted / replaced as FDM-based time-varying sub-band selection and reselection.

[0315] [Method #1] D2R transmission method for ACK / NACK for R2D transmission

[0316] For one or more R2D transmission(s), feedback (ACK and / or NACK) for each R2D of one or more device(s) may be transmitted to the leader. For example, if a past R2D transmission (e.g., Msg0 or Msg2) or an R2D transmission requiring feedback requests feedback, the device transmits feedback for that R2D transmission or subsequent R2D transmission(s). For example, the device may transmit feedback based on the configuration of the R2D transmission. Specifically, the device may transmit feedback only when there is an ACK. Specifically, the device may transmit feedback only when there is a NACK. Specifically, the device may transmit feedback for both ACK and NACK. The size of the control info or TB that transmits / transmits / carries the feedback may be a fixed value. Accordingly, even if the leader does not specify / allocate the length of the resource to the R2D, the device can calculate a D2R resource containing feedback (only) with a fixed info size or TB size value.

[0317] Feedback regarding the above R2D is transmitted to the reader via D2R transmission. For example, multiple devices may perform Msg1 transmission, and the reader may transmit Msg2 in response using a TDMed resource. In this case, the Msg2 transmission may transmit feedback (ACK and / or NACK) for each of the multiple Msg1 transmissions through a single PRDCH or through separate PRDCHs. For example, a single PRDCH may contain different feedbacks for different Msg1 transmissions. Alternatively, a single PRDCH may contain one or more feedback(s) for one or some Msg1 transmission(s), and another PRDCH may contain one or more feedback(s) for other some Msg1 transmission(s). In this case, the device that receives the Msg2 transmission may transmit feedback regarding the reception of Msg2 to the D2R.

[0318] For cases where feedback for R2D is transmitted via D2R transmission, the reader can set up D2R resources for feedback through R2D transmissions such as Msg0 or Msg3. For example, as shown in FIG. 13, Msg 2 is transmitted, and Msg2 response transmissions from R00 to R21 for multiple Msg1s can be transmitted via one or multiple PRDCHs. At this time, the devices that transmitted Msg1 can transmit feedbacks for Msg2 together via TDM and FDM using Msg3 transmission resources from R00 to R21.

[0319] Alternatively, if Msg2 is transmitted as in Fig. 13, unlike Fig. 13, a method of allocating Msg3 resources for feedback as follows can be considered.

[0320] - Method 1: Feedback resource allocation in the TDM method

[0321] According to the transmission order of Msg2 in FIG. 13, the order of D2R resources for transmitting feedback to Msg2 through Msg3 can be determined. This is explained with reference to FIG. 14. FIG. 14 illustrates TDM resources for D2R transmission according to an embodiment of the present specification.

[0322] For example, as shown in FIG. 14, the D2R resource of Msg3 can be determined as one of the TDM resources. Accordingly, the device determines the Msg3 time resource based on the time order of the Msg1 resource it transmitted and the Msg2 resource it received. For example, if Msg1 is transmitted to the R01 resource or Msg2 is received to the R01 resource, feedback for Msg2 is transmitted to the R01 resource in chronological order.

[0323] At this time, the Msg3 feedback resources are set to the same frequency as in FIG. 14, and the Msg3 frequency may be the same as or different from the Msg2 transmission frequency. If Msg2 specifies the frequency for Msg3, Msg3 is transmitted at that frequency, and if it is not specified, Msg3 is transmitted at the same frequency as the Msg2 transmission frequency.

[0324] Meanwhile, if the repetitive transmission of feedback, the number of repetitions / method of repetition, or the allocation of repetitive transmission resources is indicated based on Msg0 or Msg2, or if Msg1 is repetitively transmitted, the device may repetitively transmit the feedback based on TDM. In particular, if Msg1 is repetitively transmitted based on TDM, the device may repetitively transmit the feedback based on TDM. This is explained with reference to FIG. 15. FIG. 15 illustrates repetitive transmission based on TDM resources for D2R transmission according to an embodiment of the present specification.

[0325] For example, resources for repeated transmission can be configured as TDM resources (e.g., R00, R00 of F1 in Fig. 15 (a)).

[0326] For example, resources for repeated transmission can be configured as TDM resources with frequency hopping applied (e.g., R00 of F1 and R00 of F0 in Fig. 15(b)).

[0327] - Method 2: Feedback resource allocation in the FDM method

[0328] According to the transmission order of Msg2 in FIG. 13, the order of D2R resources for transmitting feedback to Msg2 through Msg3 can be determined. This is explained with reference to FIG. 16. FIG. 16 illustrates FDM resources for D2R transmission according to an embodiment of the present specification.

[0329] For example, as shown in FIG. 16, the D2R resource of Msg3 can be determined as one of the FDM resources. Accordingly, the device determines the frequency resource of Msg3 according to the time order of the Msg1 resource it transmitted and the Msg2 resource it received. For example, when Msg1 is transmitted to the R01 resource or Msg2 is received to the R01 resource, the device transmits feedback for Msg2 to the R01 resource in frequency order.

[0330] For example, Msg3 feedback resources can be set at different frequency positions at the same time, as in FIG. 16 (b). For example, Msg3 feedback resources can be set at different frequency positions at different times, as in FIG. 16 (a). Meanwhile, if multiple frequencies based on Msg3 are indicated / set in Msg0 or Msg2, each device transmits Msg3 to one of the FDM resources at those frequencies. In this case, the transmission time of Msg3 can be determined according to the indication / setting of the transmission of Msg0 or Msg2.

[0331] Meanwhile, if the repetitive transmission of feedback, the number of repetitions / method of repetition, or the allocation of repetitive transmission resources is indicated based on Msg0 or Msg2, or if Msg1 is repetitively transmitted, the device may repetitively transmit the feedback based on FDM. In particular, if Msg1 is repetitively transmitted based on FDM, the device may repetitively transmit the feedback based on FDM. This is explained with reference to FIG. 17. FIG. 17 illustrates repetitive transmission based on FDM resources for D2R transmission according to an embodiment of the present specification.

[0332] For example, as shown in FIG. 17, repetitive resources can be configured using only FDM, or resources can be configured by repeating FDM resources over time. Specifically, the FDM resource in FIG. 16 (a) can be configured as in FIG. 17 (a) for repetitive transmission, and the FDM resource in FIG. 16 (b) can be configured as in FIG. 17 (b) for repetitive transmission.

[0333] Meanwhile, in the embodiments of this specification, one cell refers to one sub-slot in time, and adjacent sub-slots of adjacent cells may be assigned to be physically adjacent or separated by a certain time interval. Also, one cell refers to one frequency resource for one D2R transmission in frequency, and adjacent frequency resources of adjacent cells may be assigned to be physically adjacent or separated by a certain frequency interval.

[0334] In the above methods, the feedback transmitted to the D2R may be transmitted included in L1 control information, L2 control information, or MAC SDU. When such feedback is transmitted repeatedly, the first D2R transmission may consist of an x-amble and a PDRCH.

[0335] For example, when D2R is repeated, only PDRCH may be repeatedly transmitted, or both x-amble and PDRCH may be repeatedly transmitted.

[0336] For example, if only PDRCH is repeatedly transmitted, only PDRCH can be repeatedly transmitted without x-amble.

[0337] For example, if only the PDRCH is repeatedly transmitted, only the MAC PDU (TB) can be repeatedly transmitted without the x-amble and L1 control info.

[0338] For example, if only PDRCH is repeatedly transmitted, only L1 control info can be repeatedly transmitted without x-amble and TB.

[0339] For example, if only PDRCH is repeatedly transmitted, only x-amble and L1 control info may be repeatedly transmitted without TB.

[0340] For example, if only PDRCH is repeatedly transmitted, only x-amble and TB may be repeatedly transmitted without L1 control info.

[0341] For example, while repeatedly transmitting PDRCH containing L1 control information and TB, another x-amble may be included at the beginning / middle / in the middle / after of each repeated transmission.

[0342] For example, a PDRCH containing only TB or L1 control info may be repeatedly transmitted, and another x-amble may be included at the beginning / middle / in the middle / after of each repeated transmission.

[0343] In this case, another x-amble may be repeatedly transmitted, containing an x-amble different from the x-amble of the first D2R transmission. For example, if the first D2R transmission includes a preamble and a PDRCH, subsequent transmissions may repeat only a midamble (or postamble) and a PDRCH without a preamble. In this manner, a postamble may be transmitted at the end of the last repeated PDRCH.

[0344] [Method #2] R2D transmission method of ACK / NACK for D2R transmission

[0345] If a past R2D transmission (e.g., Msg0 or Msg2) directs / configures feedback, or if a device requiring feedback requests feedback via a D2R transmission, the reader transmits feedback for that D2R transmission or for the D2R transmission(s) that occurred after that R2D / D2R transmission. For example, the reader may transmit feedback based on the configuration of the R2D transmission or the request for the D2R transmission. Specifically, the reader may transmit feedback only upon an ACK. Specifically, the reader may transmit feedback only upon a NACK. Specifically, the reader may transmit feedback for both an ACK and a NACK. The size of the control info or TB that transmits / transmits / carries the feedback may be a fixed value. Accordingly, even if the reader does not direct / allocate the length of the resource via R2D, the device can calculate an R2D resource containing feedback (only) with a fixed info size or TB size value.

[0346] Multiple devices may perform D2R transmissions such as Msg1, and in response, a reader may transmit R2D transmissions such as Msg2 using a TDMed resource. In this case, based on the R2D transmission, feedback (ACK and / or NACK) for each of the multiple D2R transmissions may be transmitted through a single PRDCH or through different PRDCHs. For example, a single PRDCH may contain different feedbacks for different Msg1 transmissions. For example, a single PRDCH may contain one or more feedback(s) for one or some Msg1 transmission(s), and another PRDCH may contain one or more feedback(s) for another set of Msg1 transmission(s).

[0347] D2R resources are described below with reference to FIG. 18. FIG. 18 illustrates resources for D2R transmission according to an embodiment of the present specification. Referring to FIG. 18 (a), D2R transmission resources can be transmitted via TDM. Referring to FIG. 18 (b), D2R transmission resources can be transmitted via TDM / FDM. Referring to FIG. 18 (c), D2R transmission resources can be transmitted via FDM.

[0348] In this case, the reader cannot transmit each R2D transmission resource, which transmits feedback for each of the multiple D2R transmissions, at different frequencies at the same time. This is because some devices lack the ability to distinguish and receive different transmissions at different frequencies. Therefore, the R2D resources transmitting feedback for each D2R transmission must be configured using TDM or by applying both TDM and FDM. At this time, the R2D frequency / time location where the feedback is transmitted may indicate the previous R2D transmission, or the device may indicate / request the D2R transmission. Embodiments of the R2D resources will be described in detail below with reference to FIG. 19.

[0349] FIG. 19 illustrates resources for R2D transmission according to an embodiment of the present specification.

[0350] FIG. 19(a) shows an example 1 of the configuration of R2D resources that transmit feedback for each of the D2R transmissions. Specifically, with reference to FIG. 19(a), resources may be arranged so that each feedback is transmitted to R2D at different times through frequency resources that are the same as or different from the D2R transmission frequency.

[0351] FIG. 19(b) illustrates an example 2 of the configuration of R2D resources that transmit feedback for each of the D2R transmissions. Specifically, with reference to FIG. 19(b), resources may be arranged so that each feedback is frequency-hopping and transmitted to R2D at different times through frequency resources that are the same as or different from the D2R transmission frequency.

[0352] FIG. 19(c) illustrates Example 3 of the configuration of R2D resources that transmit feedback for each of the D2R transmissions. Specifically, with reference to FIG. 19(c), resources can be arranged so that each feedback is transmitted to the R2D at different times through frequency resources that are the same as or different from the D2R transmission frequency.

[0353] Meanwhile, feedbacks can be transmitted repeatedly. This will be explained below with reference to FIGS. 20 and FIGS. 21.

[0354] FIG. 20 illustrates a repetitive transmission based on TDM resources for R2D transmission according to an embodiment of the present specification. FIG. 21 illustrates a repetitive transmission based on FDM resources for R2D transmission according to an embodiment of the present specification. FIG. 20 and FIG. 21 show embodiments of resource configuration during repetitive transmission of feedback.

[0355] If a previously transmitted R2D transmission, such as Msg0, indicates a repeated transmission or indicates the number of repetitions or the method, or if Msg1 is transmitted repeatedly or if the device requests / instructs the reader to transmit feedback repeatedly via Msg1, the reader can transmit feedback for D2R to R2D using resources configured as shown in FIGS. 20 and 21.

[0356] Figures 20 (a) and (b) show Examples 1 and 2 of TDMed feedback iterative transmission.

[0357] Figures 21 (a) and (b) show Examples 1 and 2 of FDMed feedback iterative transmission.

[0358] In the above methods, the feedback transmitted to the R2D may be transmitted included in L1 control information, L2 control information, or MAC SDU. When such feedback is transmitted repeatedly, the first R2D transmission may consist of an x-amble and a PRDCH.

[0359] For example, when R2D is repeated, only PRDCH may be repeatedly transmitted, or both x-amble and PRDCH may be repeatedly transmitted.

[0360] For example, if only PRDCH is repeatedly transmitted, only PRDCH can be repeatedly transmitted without x-amble.

[0361] For example, if only PRDCH is repeatedly transmitted, only MAC PDU (TB) can be repeatedly transmitted without x-amble and L1 control info.

[0362] For example, if only PRDCH is repeatedly transmitted, only L1 control info can be repeatedly transmitted without x-amble and TB.

[0363] For example, if only PRDCH is repeatedly transmitted, only x-amble and L1 control info may be repeatedly transmitted without TB.

[0364] For example, if only PRDCH is repeatedly transmitted, only x-amble and TB may be repeatedly transmitted without L1 control info.

[0365] For example, PRDCH containing L1 control information and TB may be repeatedly transmitted, and another x-amble may be included at the beginning / middle / in the middle / after of each repeated transmission.

[0366] For example, PRDCH containing only TB or L1 control info may be repeatedly transmitted, and another x-amble may be included at the beginning / middle / in the middle / after of each repeated transmission.

[0367] In this case, another x-amble may be repeatedly transmitted, containing an x-amble different from the x-amble of the first R2D transmission. For example, if the first R2D transmission includes a preamble and a PRDCH, subsequent transmissions may repeat only a midamble (or postamble) and a PRDCH without a preamble. In this manner, a postamble may be transmitted at the end of the last repeated PRDCH.

[0368] Additionally, in the above methods, multiple feedbacks transmitted to R2D for different devices may be transmitted to a single PRDCH or to different PRDCHs. When transmitted collectively to a single PRDCH, it includes multiple feedbacks of a single PRDCH following a single preamble. In this case, the single PRDCH may include one or more L1 control info, one or more L2 control info, one or more MAC CEs, or one or more MAC SDUs, each of which may include one or more feedbacks.

[0369] [Method #3] Frequency hopping method for D2R or R2D transmission for feedback

[0370] When MSG0 transmitted by the reader to R2D triggers RA, the D2R transmission resources and frequency hopping of Msg1 or Msg3 may be set / instructed based on the Msg0 R2D transmission (e.g., Msg0 or R2D message). Alternatively, the D2R transmission resources and frequency hopping of Msg3 may be set / instructed based on the Msg2 R2D transmission (e.g., Msg2 or R2D message). Alternatively, the transmission resources and frequency hopping of the corresponding D2R transmission may be set / instructed based on the R2D transmission that triggers the D2R transmission (e.g., R2D message). For example, the D2R transmission resources and frequency hopping may be set / instructed based on L1 or L2 control information of the R2D transmission.

[0371] For example, D2R transmission resources considering hopping may be indicated / configured according to the indication / configuration of an R2D transmission (e.g., Msg0 or 2) that directly or indirectly triggers a D2R transmission (e.g., Msg1 or Msg3). Such indication / configuration may include information on at least one of: i) the location of frequencies to be targeted for frequency hopping or frequency hopping intervals; ii) the device ID, device type, or device group to perform frequency hopping; iii) whether to sustain D2R transmission through frequency hopping for a certain number of sub-slots and the maximum number of D2R transmissions; and / or iv) whether to repeatedly transmit the same D2R message for each transmission resource or to transmit different D2R messages each time a D2R resource is hopping.

[0372] According to these instructions / settings, the device determines D2R resources for each of multiple consecutive or discontinuous sub-slots, and can perform different D2R transmissions or repeat the same D2R transmission through the determined resources. The device can continue / perform such transmissions for the maximum number of times / repetitions mentioned above.

[0373] For example, when different D2R transmissions occur, different TBs may be transmitted based on each D2R transmission.

[0374] For example, when different D2R transmissions occur, a segment of one TB can be transmitted based on each D2R transmission. Specifically, one TB can be divided into multiple segments. The device can transmit each segment to the reader via a separate D2R transmission. The segments received by the reader can be restored into one TB through assembly.

[0375] In the case of repetitive transmission, if a single D2R transmission is the length of one sub-slot, the device can perform repetitive transmission for every sub-slot. In the case of repetitive transmission, if a single D2R transmission is the length of N sub-slots, the device can perform repetitive transmission for every N sub-slots.

[0376] In this manner, the D2R transmission transmitted via frequency hopping may correspond to a feedback message for Msg1 or Msg2 or a device-only transmission or R2D transmission, and frequency hopping may be performed in the following manner.

[0377] Method 1: Frequency hopping based on frequency interval delta

[0378] Based on the R2D transmission (R2D message), eight frequency resource locations (F0 to F7) are indicated / set / determined. The device selects the first frequency resource in the first sub-slot allocated for the D2R transmission. For example, the first sub-slot and the first frequency may be indicated to the device by the reader based on the R2D transmission (R2D message). For example, the first sub-slot and the first frequency may be selected randomly by the device. For example, the first sub-slot and the first frequency may be selected by the device according to a predefined rule.

[0379] Subsequently, the device selects a frequency resource in the second sub-slot based on the frequency interval delta of the instructed / set / determined frequency hopping. For example, the delta value may be instructed to the device by the reader based on an R2D transmission (R2D message). For example, the delta value may be randomly selected / determined by the device. For example, the delta value may be selected / determined by the device according to a predefined rule. Accordingly, if the frequency resource of the first sub-slot is F1 and delta = 4, the frequency resource of the second sub-slot is F5.

[0380] Method 1A: F1 and F5 are paired. Subsequently, for D2R transmission or repetitive transmission in sub-slots, the device performs D2R transmission or repetitive transmission by switching frequency resources from F5 to F1 and back from F1 to F5.

[0381] Method 1B: When delta is indicated / set / determined as 4, the frequency resource of the third sub-slot after F5 is F9. However, since only resource locations from F0 to F7 are set, the frequency resource of the third sub-slot is determined as F2 as a result of 9 mod 7 = 2. Subsequently, D2R transmission is transmitted or repeated by hopping from the sub-slot to F6, F3, etc., up to the final sub-slot.

[0382] Method 2: Frequency pairing-based frequency hopping

[0383] Based on R2D transmission (R2D message), eight frequency resource locations (F0 to F7) can be indicated / set / determined as follows. For example, F0 can be paired with F4, and F1 and F5, F2 and F6, and F3 and F7 can be paired together. Specifically, the reader can set / instruct the terminal to frequency pairs of (F0, F4), (F1, F5), (F2, F6), and (F3, F7).

[0384] In this manner, the device selects the first frequency resource or frequency pair in the first sub-slot allocated for D2R transmission. For example, if the first frequency resource is selected, the frequency pair to which the first frequency belongs is selected. For example, the first sub-slot and the first frequency may be instructed to the device by the reader based on an R2D transmission (R2D message). For example, the first sub-slot and the first frequency may be selected randomly by the device. For example, the first sub-slot and the first frequency may be selected by the device according to a predefined rule.

[0385] Method 2A: Subsequently, for D2R transmission or repeat transmission in each sub-slot, the device performs D2R transmission or repeat transmission for a maximum number of transmissions / repeat transmissions while alternating between frequency positions belonging to the selected frequency pair. For example, if F0 of (F0, F4) is the first frequency resource, hopping can be performed in the order of F0 -> F4 -> F0 -> F4 -> F0 -> F4 -> F0 -> F4..

[0386] Method 2B: Subsequently, for D2R transmission or repeat transmission in each sub-slot, the device re-selects a different frequency pair and performs D2R transmission or repeat transmission once at the frequency positions belonging to the second re-selected pair. Then, it re-selects the next frequency pair again and performs D2R transmission or repeat transmission in the re-selected pair, and performs D2R transmission or repeat transmission while re-selecting pairs for the maximum number of transmissions / repeats. For example, hopping can be performed in the order of (F0 -> F4) --> (F1 -> F5) --> (F2 -> F6) --> (F3 -> F7). As a specific example, if frequency pairs are indicated / set / determined as (F0, F4), (F1, F5), (F2, F6), and (F3, F7), the device first selects (F0, F4) and transmits at F0 and F4 respectively. Subsequently, the device transmits from F2 and F6 of (F2, F6) respectively through frequency pair reselection. Then, the device reselects / changes the frequency pair to (F1, F5) and (F3, F7) through frequency pair reselection, and transmits from F1, F5, F3, and F7 respectively. Afterward, the device reselects / changes the frequency pair to (F0, F4) and repeats the above process to transmit or repeat D2R transmissions for the maximum number of transmissions / repeats.

[0387] Method 3: Transmission resource table configuration method

[0388] FIG. 22 illustrates a table for determining transmission resources according to an embodiment of the present specification.

[0389] For example, all transmission resources may be configured as shown in the table of FIG. 22 according to the instruction / setting / decision of the R2D transmission above. In this case, empty frequency / time resources in the table refer to resources that are used for another R2D / D2R transmission or resources that are not allocated for R2D / D2R transmission for NR / LTE transmission. Another D2R transmission resource may be another D2R transmission resource triggered by the same R2D transmission or another R2D transmission, or it may be a device transmission for a specific device or device group, or a D2R transmission resource dedicated to a device group.

[0390] In this manner, the device sets / determines D2R transmission or repetitive transmission resources according to the table of FIG. 22 and selects resources for D2R transmissions or D2R repetitive transmissions. For example, if the device selects resource F0 (D2R1) in sub-slot 1, it determines resources for the same D2R1 as follows. Specifically, the device selects resource F5 in sub-slot 2, resource F1 in sub-slot 3, and resource F6 in sub-slot 4 to continue D2R transmission or repetitively transmit D2R. Subsequently, the table is repeated to perform D2R transmission / repetitive transmission by repeating F0, F5, F1, and F6.

[0391] For example, the device can select D2R3 resources (resources F1, F6, F2, and F7) to perform D2R transmission / repeating transmission. Specifically, the device can switch from D2R1 resources to D2R3 resources to transmit / repeate, and then switch from D2R2 resources to D2R4 resources to transmit / repeate.

[0392] Meanwhile, the frequency hopping method of this specification may be similarly applied to R2D transmissions or R2D repeated transmissions. In this case, frequency hopping instruction / setting information for the R2D transmission may be provided based on L1 or L2 control information of a previously transmitted R2D transmission. In this case, the R2D transmission to which frequency hopping is applied may be related to feedback for i) Msg0, ii) Msg2 and / or iii) Msg3. In other words, the device may receive i) Msg0, ii) Msg2 and / or iii) Msg3 from the reader based on frequency hopping.

[0393] [Method #4] Method to control Rel-20 devices or enhanced devices from connecting to a reader that supports only Rel-19

[0394] According to the present specification, the methods for controlling whether a reader that supports only Rel-19 connects or disconnects a Rel-20 device or device type 2 are as follows.

[0395] Opt 1: The reader transmits its release / version information via R2D messages.

[0396] For example, all R2D messages, system information, or Msg0 or Msg2 transmitted by the reader, such as Paging, may contain the reader's release / version information. For example, specific patterns in the L1 control info, L2 control info, MAC CE, or preamble of these messages indicate / contain the reader's release / version information.

[0397] If the release / version information obtained from the reader indicates a release / version earlier than that of the device, the device does not respond to the reader's R2D transmission. For example, even if an R2D transmission triggers a D2R transmission, the device ignores it and does not execute the D2R transmission.

[0398] Alternatively, the device executes a D2R transmission to indicate the device type or the release / version information of the device using a specific pattern / length of the L1 control info or L2 control info or MAC CE or preamble of the D2R transmission, thereby preventing the reader from proceeding with the corresponding RA procedure.

[0399] Opt 2: The reader transmits the release / version information of the devices it supports or the type of the device via an R2D message.

[0400] For example, any R2D message, system information, or paging message such as Msg0 or Msg2 transmitted by the reader may include device release / version information or device type. For example, specific patterns of L1 control info, L2 control info, MAC CE, or preamble of such messages indicate / include device release / version information or device type.

[0401] If the release / version information or device type obtained from the reader indicates an earlier release / version or a different device type than the device in question, the device does not respond to the reader's R2D transmission. For example, even if an R2D transmission triggers a D2R transmission, the device ignores it and does not execute the D2R transmission.

[0402] Alternatively, the device executes a D2R transmission to indicate the device type or the release / version information of the device using a specific pattern / length of the L1 control info or L2 control info or MAC CE or preamble of the D2R transmission, thereby preventing the reader from proceeding with the corresponding RA procedure.

[0403] Opt 3: Indicates the device type or device release / version information in the D2R message sent to the reader.

[0404] For example, when triggering an RA procedure based on Msg0, the device type or release / version information of the device is indicated by a specific pattern / length of L1 control info or L2 control info or MAC CE or preamble of a D2R transmission such as Msg1, Msg3, or Msg5.

[0405] Subsequently, the device does not respond to the R2D transmission of the corresponding reader. For example, even if the R2D transmission triggers a D2R transmission, the device ignores it and does not execute the D2R transmission.

[0406] Alternatively, the device subsequently expects the reader to send an R2D message to instruct the disconnection / termination of the connection with the device.

[0407] Opt 4: Set the pattern / length of the start indicator and / or clock acquisition part of the R2D preamble transmitted by the R19 reader to be different from the pattern / length transmitted by the R20 reader.

[0408] In this method, the device determines the release / version of the reader or whether the device supports it based on the pattern / length of the start indicator and / or clock acquisition part of the R2D preamble; if it is an older release / version or does not support it, the device does not respond to the R2D transmission from the reader. For example, even if an R2D transmission triggers a D2R transmission, the device ignores it and does not execute the D2R transmission.

[0409] Alternatively, the device executes a D2R transmission to indicate the device type or the release / version information of the device using a specific pattern / length of the L1 control info or L2 control info or MAC CE or preamble of the D2R transmission, thereby preventing the reader from proceeding with the corresponding RA procedure.

[0410] Opt 5: The R2D message transmitted by the R19 reader includes a specific ID (e.g., message type ID, command ID, reader ID, etc.) and indicates the release / version of the reader based on the specific ID value.

[0411] For example, readers of past release / versions and current release versions are made to select a reader ID from a different list of reader ID values ​​and include it in L1 / L2 control info, MAC CE, MAC header / SDU, system information, or parent messages. For example, the reader ID is set so that the R19 reader has values ​​from 0 to 255, and the R20 reader has values ​​of 256 or higher.

[0412] Alternatively, readers of past release / versions and current release versions select a command / message ID from a different list of command or message ID values ​​and include it in L1 / L2 control info, MAC CE, MAC header / SDU, or parent messages. For example, the command / message ID is set so that the R19 reader has values ​​from 0 to 255, and the R20 reader has values ​​of 256 or higher.

[0413] Accordingly, the device identifies the release / version of the reader or whether the device supports it based on a specific ID; if it is an older release / version or not supported, the device does not respond to the reader's R2D transmission. For example, even if an R2D transmission triggers a D2R transmission, the device ignores it and does not execute the D2R transmission.

[0414] Alternatively, the device executes a D2R transmission to indicate the device type or the release / version information of the device using a specific pattern / length of the L1 control info or L2 control info or MAC CE or preamble of the D2R transmission, thereby preventing the reader from proceeding with the corresponding RA procedure.

[0415] Opt 6: An R2D message that triggers a D2R transmission, such as Paging, indicates the device type or device release / version to respond to.

[0416] For example, without the need for the device to determine the reader's release / version or whether the device is supported, the reader can be instructed via Msg0, such as paging, to respond with D2R transmissions only for specific device types or specific device releases / versions.

[0417] Accordingly, the device continuously monitors the R2D transmissions of the corresponding reader, and performs a D2R transmission if the reader triggers a D2R transmission of its device type or its device release / version via a Msg0 such as paging; otherwise, it does not perform a D2R transmission and continues to monitor for new R2D transmissions.

[0418] Opt 7: Readers of a specific release / version, or readers that support or do not support a specific device type, or readers that support or do not support a specific release / version, perform R2D transmission on a specific frequency channel.

[0419] For example, on frequency channel F0, the Rel-19 reader performs R2D transmission, and on channel F1, the Rel-20 reader performs R2D transmission.

[0420] Alternatively, on frequency channel F0, a reader supporting Rel-19 devices performs R2D transmission, and on channel F1, a reader supporting Rel-20 devices performs R2D transmission. Alternatively, on channel F1, a reader not supporting Rel-19 devices performs R2D transmission. Alternatively, on channel F0, a reader not supporting Rel-20 devices performs R2D transmission.

[0421] Accordingly, the device determines whether it supports the device based on the location of the R2D transmission frequency resource of the reader, receives the R2D through the frequency resource of the supported reader, and performs the RA procedure to establish a connection.

[0422] Opt 8: Devices that support or do not support a specific release / version, or specific device types, perform D2R transmission over a specific frequency channel.

[0423] For example, on frequency channel F0, a Rel-19 device is mapped to perform D2R transmission, and on channel F1, a Rel-20 device is mapped to perform D2R transmission.

[0424] Alternatively, on frequency channel F0, a device supporting an Rel-19 reader is mapped to perform D2R transmission, and on channel F1, a device supporting an Rel-20 reader is mapped to perform D2R transmission. Alternatively, on channel F1, a device not supporting an Rel-19 reader is mapped to perform D2R transmission. Alternatively, on channel F0, a device not supporting an Rel-20 reader is mapped to perform D2R transmission.

[0425] At this time, the reader may set the mapping of D2R frequency channels through an R2D message (e.g., Msg0, 2), or the mapping information may be stored in the device's memory.

[0426] Accordingly, the device that receives an R2D message from the reader triggering D2R transmission determines the frequency resources according to the mapping and performs D2R transmission.

[0427] For example, Msg 1 or Msg 3 is transmitted from the determined frequency resource. Subsequently, D2R transmission may be performed from a different frequency resource depending on the instructions / allocation / settings of the reader. However, if there are no such instructions / allocations / settings, D2R transmission is performed only from the determined frequency resource.

[0428] In this case, if the device receives CW and backscattering, it can perform D2R transmission through frequency shifting. When performing such frequency shifting, the device performs D2R transmission by frequency shifting to the D2R frequency determined according to the mapping, or performs D2R transmission without frequency shifting if the D2R frequency determined according to the mapping is the CW frequency.

[0429] Alternatively, devices of specific releases / versions / types can be configured to perform frequency shifting, while other devices are configured not to perform frequency shifting.

[0430] For example, the R20 device or device type 2 can be configured to always perform D2R transmission with frequency shift, and the R19 device or device type 1 can be configured to always perform D2R transmission without frequency shift.

[0431] These settings can be set by the reader via R2D messages (e.g., Msg0, 2), or the mapping information can be stored in the device's memory.

[0432] Alternatively, devices of a specific release / version / type may be configured to perform a large frequency shift, while other devices may perform a small frequency shift.

[0433] For example, the R20 device or device type 2 can be configured to always perform D2R transmission with a large frequency shift, and the R19 device or device type 1 can be configured to perform D2R transmission with a small frequency shift or without a frequency shift.

[0434] These settings can be set by the reader via R2D messages (e.g., Msg0, 2), or the mapping information can be stored in the device's memory.

[0435] Alternatively, devices of a specific release / version / type may be configured to frequency shift in one direction, while other devices may frequency shift in the other direction.

[0436] For example, the R20 device or device type 2 can be configured to always perform D2R transmission by frequency shifting in the high frequency direction, and the R19 device or device type 1 can be configured to perform D2R transmission by frequency shifting in the low frequency direction or without frequency shifting.

[0437] These settings can be set by the reader via R2D messages (e.g., Msg0, 2), or the mapping information can be stored in the device's memory.

[0438] Through this D2R transmission, the reader can identify the release / version / type of the device and determine whether to approve or reject the device's connection attempt.

[0439] Opt 9: Devices that support or do not support a specific release / version, or specific device types, perform D2R transmission in a specific time interval (e.g., sub-slot(s) or slot(s)).

[0440] For example, in a slot for D2R transmission such as Msg 1, a Rel-19 device is mapped to perform D2R transmission in the first sub-slot(s), and a Rel-20 device is mapped to perform D2R transmission in the second sub-slot(s).

[0441] Or, for example, in a slot for D2R transmission such as Msg 1, a device supporting a Rel-19 reader is mapped to perform D2R transmission in the first sub-slot(s), and a device supporting a Rel-20 reader is mapped to perform D2R transmission in the second sub-slot(s). Or, a device not supporting a Rel-19 reader is mapped to perform D2R transmission in the second sub-slot(s). Or, a device not supporting a Rel-20 reader is mapped to perform D2R transmission in the first sub-slot(s).

[0442] At this time, the reader may set a mapping of time intervals such as the sub-slot(s) mentioned above, or the mapping information may be stored in the device's memory. When the reader maps a time interval, it transmits the time interval mapping information to the devices via R2D messages (e.g., Msg0, Msg2) that trigger D2R transmission.

[0443] Accordingly, a device that receives an R2D message from a reader that triggers D2R transmission determines a time interval, such as a sub-slot(s), according to the mapping and performs D2R transmission. For example, Msg 1 or Msg 3 is transmitted in the determined sub-slot(s). Subsequently, D2R transmission may be performed in a different time resource according to the reader's instructions / assignments / settings. However, if there are no such instructions / assignments / settings, D2R transmission is performed only in the determined time resource.

[0444] Through this D2R transmission, the reader can identify the release / version / type of the device and determine whether to approve or reject the device's connection attempt.

[0445] Opt 10: The reader sends specific indicators via R2D messages that can only be interpreted or cannot be interpreted by specific device releases / versions / types.

[0446] For example, all R2D messages, system information, or paging messages such as Msg0 or Msg2 transmitted by the reader may contain specific indicators. For example, specific patterns of L1 control info, L2 control info, MAC CE, or preambles of these messages may indicate or contain specific indicators.

[0447] The above specific indicator can be interpreted by the R20 device or device type 2, and the R19 device or device type 1 can interpret the specific indicator as reserved bit(s).

[0448] In this case, a specific indicator may be an access barring indication; if so, the device interpreting it prohibits access to the corresponding reader (for a set period or permanently) according to the indicator. The device may prohibit access only to that specific reader, or it may prohibit access to all other readers performing R2D transmissions on that reader's R2D frequency channel. Meanwhile, the reader may indicate or set, via an R2D message, whether the prohibition is for a set period or permanently, and the value of the prohibition period. In this prohibited state, all R2D transmissions received on that reader's R2D frequency channel are to be ignored.

[0449] In this case, if the received R20 device or device type 2 has a specific indicator (e.g., reserved bit(s) indicating a specific value) in the R2D message (e.g., Msg0, 2), it determines that the reader supports it and decides that it can connect to the reader. Accordingly, it can trigger D2R transmission in response to the R2D message of the reader.

[0450] If no specific indicator is present (e.g., if reserved bit(s) that do not indicate a specific value are received), the device does not respond to the R2D transmission from the corresponding reader. For example, even if an R2D transmission triggers a D2R transmission, the device ignores it and does not execute the D2R transmission.

[0451] Alternatively, the device executes a D2R transmission to indicate the device type or the release / version information of the device using a specific pattern / length of the L1 control info or L2 control info or MAC CE or preamble of the D2R transmission, thereby preventing the reader from proceeding with the corresponding RA procedure.

[0452] Meanwhile, the R19 device or device type 1 interprets a specific indicator only as reserved bit(s) and does not support special operations for that specific indicator. However, the R19 device or device type 1 can trigger a D2R transmission in response to an R2D message from the corresponding reader.

[0453] Alternatively, the above specific indicator allows the R19 device or device type 1 to interpret it, and also allows the R20 device or device type 2 to interpret it.

[0454] In this case, the R19 device, device type 1, R20 device, or device type 2 determines that the reader supports it based on a specific indicator (e.g., reserved bit(s) indicating a specific value) and decides that it can connect to the reader. Accordingly, it can trigger a D2R transmission in response to the R2D message of the reader.

[0455] If no specific indicator is present (e.g., if reserved bit(s) that do not indicate a specific value are received), the device does not respond to the R2D transmission from the corresponding reader. For example, even if an R2D transmission triggers a D2R transmission, the device ignores it and does not execute the D2R transmission.

[0456] Alternatively, the device executes a D2R transmission to indicate the device type or the release / version information of the device using a specific pattern / length of the L1 control info or L2 control info or MAC CE or preamble of the D2R transmission, thereby preventing the reader from proceeding with the corresponding RA procedure.

[0457] [Method #5] Device type fallback method

[0458] If the reader determines that it does not support a specific device release / version / type according to Method #4 above, the device may operate by converting to a device release / version / type supported by the reader. This method is a device fallback operation that causes the enhanced device to perform the operation of a basic device (device type 1) when the reader does not support the enhanced device (device type 2).

[0459] Method 1: To communicate with a reader that does not support Device 2a, Device 2a performs fallback by disabling or adjusting some or all functions of the following device transceivers.

[0460] The device disables the frequency shift or large frequency shift functions, or adjusts the shift size to support only small frequency shifts.

[0461] At this time, the reader can indicate / set whether to disable, and the shift size / decrease value through the R2D message (e.g., Msg0 or 2).

[0462] The device disables the reflection amp function or lowers the amplification size or final TX power to zero.

[0463] At this time, the reader can indicate / set whether to disable, amplification size / reduction value, final Tx power value, or Tx power reduction value through the R2D message (e.g., Msg0 or 2).

[0464] At this time, the reflection amp performs the role of amplifying the D2R transmission transmitted by backscattering the CW.

[0465] The device disables the LNA and / or BB amp function or adjusts the amplification size to low or zero.

[0466] To communicate with a reader that does not support Device 2b, Device 2b operates as follows.

[0467] The device disables the power amp function or lowers the amplification size or final TX power to zero.

[0468] At this time, the reader can indicate / set whether to disable, amplification size / reduction value, final Tx power value, or Tx power reduction value through the R2D message (e.g., Msg0 or 2).

[0469] The device adjusts the carrier frequency generated by the local oscillator (LO) to match the D2R transmission frequency.

[0470] For example, if the control information of an R2D message indicates / allocates a D2R frequency resource, the device adjusts the carrier frequency generated by the LO to match the indicated / allocated D2R frequency.

[0471] The device disables the LNA and / or BB amp function or adjusts the amplification size to low or zero.

[0472] Alternatively, a device type 2b may simultaneously be equipped with a transmitter of type 2a. In this case, for D2R transmission toward a reader that does not support 2b, the device switches from the 2b transmitter to the 2a transmitter to perform D2R transmission through backscattering.

[0473] Meanwhile, the device can indicate / report the device's capability or type to the reader.

[0474] For example, it may indicate / report whether the device type is type 2 and whether it supports fallback to type 1. In this case, the L1 / L2 control info of the D2R transmission, or the MAC CE, MAC header, or the pattern / length of the preamble may indicate this.

[0475] If it is determined that the reader does not support device 2a or 2b according to the method(s) of Method #4, or if it is determined that the reader does not allow D2R transmission or RA connection of device 2a or 2b, or if the reader sets / instructs device fallback, a device supporting the fallback operation of this specification may convert to a device type 1 operation as described above and perform an RA procedure and D2R transmission according to the reader's R2D transmission. In this case, the reader may set / instruct device fallback or transmit power setting / adjustment information for device fallback through L1 / L2 control info, MAC CE, MAC header, system information, or the pattern / length of the preamble of the R2D message (e.g., Msg0 or 2).

[0476] Example 1: When a reader indicates the release / version / type of a device supported by R2D transmission or the release / version of the reader, device type 2 can always perform the fallback of this specification in a rel-19 reader or a rel-20 device or a reader that does not support device type 2.

[0477] For example, device type 2 that supports fallback connects by falling back if the reader is an R20 device or does not support type 2, or is a rel-19 reader.

[0478] However, device type 2 that does not support fallback does not connect to the reader if the reader is an R20 device, does not support type 2, or is a rel-19 reader.

[0479] If the reader supports an R20 device or type 2, or is a rel-20 reader, connect without fallback.

[0480] Example 2: When device type 2 receives a specific indicator from the R2D transmission of the reader, device type 2 may perform the fallback of the present specification according to the specific indicator.

[0481] For example, device type 2 that supports fallback can fallback and connect if there is no specific indicator, and can connect without fallback if there is an indicator.

[0482] For example, a specific indicator may indicate support for a Rel-20 reader or Rel-20 device or device type 2.

[0483] Alternatively, if the above specific indicator is present, the connection is established via fallback, and if there is no indicator, the connection can be established without fallback.

[0484] For example, a specific indicator may indicate that a Rel-19 reader or Rel-20 device is not supported or that device type 2 is not supported.

[0485] Alternatively, a specific indicator may indicate a device type 2 fallback.

[0486] Meanwhile, device type 2 that does not support fallback does not connect to the reader when there is no specific indicator mentioned above, and can connect to the reader when there is an indicator.

[0487] For example, a specific indicator may indicate support for a Rel-20 reader or Rel-20 device or device type 2.

[0488] Alternatively, if the above specific indicator is present, the reader may not be connected, and if there is no indicator, the reader may be connected.

[0489] For example, a specific indicator may indicate that a Rel-19 reader or Rel-20 device is not supported or that device type 2 is not supported.

[0490] Example 3: The reader instructs a parameter to set the amp power for device type 2 via R2D transmission (e.g., Msg0 or 2).

[0491] In the case of Device type 2, the device performs D2R transmission by adjusting the TX power of the reflection or power amp according to the specified parameters.

[0492] In addition, the reader can set a frequency shift value. For example, the reader restricts the type 2 device to perform only a small frequency shift by setting only a small frequency shift value and not setting a large frequency shift value.

[0493] In this case, the Device may not know the release / version of the reader.

[0494] For such device operation, the reader can transmit L1 / L2 control info or MAC CE or MAC header or system information or pattern / length of preamble of R2D transmission (e.g., Msg0 or 2) to the device, and the above parameters (TX power value or power control value or shift magnitude value or D2R frequency position).

[0495] Rel-20 devices or Device type 2 devices enable or disable fallback behavior as follows.

[0496] Opt 1: When receiving Msg0 such as Paging to trigger RA to perform D2R transmission, or when performing D2R transmission triggered by R2D transmission, a Device type 2 that supports fallback enables the fallback operation.

[0497] Alt 1: After performing D2R transmission in this way, if the received R2D transmission does not instruct a fallback according to the above instruction / setting method, the device disables the fallback operation and returns to device type 2 to perform D2R transmission.

[0498] If the subsequently received R2D transmission indicates a fallback, the fallback operation is reactivated to perform a D2R transmission.

[0499] Alt 2: After performing D2R transmission in this way, if the received R2D transmission instructs a return to device type 2 according to the above instruction / setting method, the device disables the fallback operation, returns to device type 2, and performs D2R transmission.

[0500] If the subsequently received R2D transmission does not instruct a return to device type 2, the fallback operation is activated again to perform a D2R transmission.

[0501] Opt 2: Method for determining whether to enable / disable fallback for every R2D transmission

[0502] Alt 1: If the received R2D transmission does not instruct fallback activation according to the above instruction method, the D2R transmission for the R2D transmission operates as device type 2 with fallback disabled.

[0503] Meanwhile, if the received R2D transmission instructs fallback activation, the D2R transmission for that R2D is performed by activating fallback.

[0504] Alt 2: If the received R2D transmission instructs to disable fallback or return to device type 2 according to the above instruction method, the D2R transmission for the R2D transmission operates as device type 2 with fallback disabled.

[0505] Meanwhile, if the received R2D transmission does not instruct to disable fallback or return to device type 2, the D2R transmission for that R2D transmission is performed with fallback enabled.

[0506] Control information and PRDCH or PDRCH transmission structure

[0507] FIG. 23 illustrates the Control information and PRDCH or PDRCH transmission structure options of the present specification. In FIG. 23, each transmission option is transmitted immediately after the preamble. Additionally, a postamble may be transmitted immediately after the transmission of each transmission option. For example, if the PRDCH or PDRCH transmission of option a or option b of FIG. 23 includes a preamble and a postamble, it may be transmitted as in FIG. 24.

[0508] FIG. 24 illustrates a transmission including a preamble and a postamble according to an embodiment of the present specification. The method illustrated in FIG. 24 is an example, and D2R transmission may be performed differently depending on the implementation method. It will be described in detail below.

[0509] For example, D2R transmission may be performed in a manner other than the Manchester code. For example, the D2R preamble may be transmitted only as a clock acquisition part for D2R timing acquisition without a start indicator. For example, the postamble may also be transmitted for a different length by maintaining a high voltage as in FIG. 24, or as a specific sequence consisting of high and low voltages.

[0510] For example, only the preamble and PRDCH / PDRCH can be transmitted without the postamble of Fig. 24.

[0511] As shown in Fig. 23, R2D L1 control information can be transmitted in one of the following ways.

[0512] Alt 1

[0513] L1 control information is included at the end of the preamble as part of the R2D preamble. In Alt 1, the chip duration of the L1 control information may be the same as the preamble chip duration.

[0514] For example, L1 control info may be added immediately after the clock acquisition part of FIG. 24, and then PRDCH may be transmitted. In this case, the structure of PRDCH transmission may be the same as option a or b of FIG. 23. In the case of option b, PRDCH starts with L2 control info.

[0515] Alt 2

[0516] L1 control information is located between the R2D preamble and the PRDCH. At this time, the structure of the PRDCH transmission may be the same as option c, d, or e of FIG. 23.

[0517] In the case of Option d, L1 control information is transmitted through a separate R2D control channel.

[0518] In the case of Option c or e, L1 control information is transmitted as a separate part without a separate channel.

[0519] Alt 3

[0520] L1 control information is included in the beginning of the PRDCH as part of the PRDCH. The chip duration of the L1 control information can be the same as the PRDCH chip duration.

[0521] At this time, the structure of the PRDCH transmission may be the same as option b in Fig. 23, and the PRDCH starts with L1 control info.

[0522] FIG. 25 illustrates an example of the structure of the MAC payload of FIG. 23 according to the present specification. In this case, the MAC payload may correspond to a single transport block. In Options a, c, and d, the L2 control info may or may not be located at the beginning of the MAC payload. In this case, the clock acquisition part of the L1 control info or preamble of FIG. 23 may indicate that the L2 control info is included. Alternatively, without a separate indication, the MAC payload may always include or not include the L2 control info. Alternatively, the first bit / field of the L2 control info or the bit / field immediately preceding the L2 control info may indicate whether or not the L2 control info is included. Alternatively, the MAC CE (Control Element) following the MAC subheader of FIG. 25 may include the L2 control info. Additionally, padding may be added to the last part of the payload of FIG. 25. When a payload (i.e., TB) is configured at the MAC layer of a device / reader as shown in FIG. 25, the MAC layer of the device / reader transmits the payload to the physical layer of the device / reader. The physical layer can configure PRDCH or PDRCH transmission by adding a CRC to the TB. At this time, L1 control info, L2 control info, or MAC CE can indicate whether a CRC is added to the TB. In FIG. 25, L2 control information can also be classified as a specific MAC CE that is always located before the payload or as a MAC header.

[0523] FIG. 26 illustrates D2R transmission and midamble transmission according to an embodiment of the present specification.

[0524] A reader transmitting the PRDCH may or may not include L1 control information (L1CI) within the PRDCH. In this case, the R2D L1CI transmitted to the R2D may include control information for PRDCH transmission and / or control information for PDRCH transmission. Additionally, the reader may or may not include L2 control information (L2CI) within the PRDCH. In this case, the R2D L2CI transmitted to the R2D may include control information for PRDCH transmission and / or control information for PDRCH transmission.

[0525] Additionally, the device transmitting the PDRCH may or may not include L1 control information (L1CI) within the PDRCH. In this case, the D2R L1CI transmitted to the D2R may include i) control information for the PDRCH transmission, ii) control information for subsequent PRDCH transmission, and / or iii) reporting information. Additionally, the device may or may not include L2 control information (L2CI) within the PDRCH. In this case, the D2R L2CI transmitted to the D2R may include i) control information for the PDRCH transmission, ii) control information for PRDCH transmission, and / or iii) reporting information. The reporting information may include buffer status, remining D2R data size, device energy status / level, etc.

[0526] In this case, L2CI can be a MAC CE included in the MAC PDU, a MAC header / sub-header, or a part of these.

[0527] Various embodiments of the present disclosure may be combined with one another.

[0528] In terms of implementation, the operations of the first device (e.g., Ambient IoT Device or Reader, BS, IN, AN, UE) / second device (e.g., Reader, BS, IN, AN, UE or Ambient IoT Device) according to the embodiments described above can be processed by the device of FIG. 29 (e.g., the processor (110, 210) of FIG. 29).

[0529] In addition, the operations of the first device (e.g., Ambient IoT Device or Reader, BS, IN, AN, UE) / second device (e.g., Reader, BS, IN, AN, UE or Ambient IoT Device) according to the above-described embodiment may be stored in memory (e.g., 140, 240 of FIG. 29) in the form of instructions / programs (e.g., instruction, executable code) for driving at least one processor (e.g., 110, 210 of FIG. 29).

[0530] The embodiments described above will be explained in detail below with reference to FIGS. 27 and 28 in terms of the operation of a first device (e.g., Ambient IoT Device) and a second device (e.g., Reader, base station, intermediate node, auxiliary node). The methods described below are distinguished only for convenience of explanation, and it is understood that a part of one method may be substituted with a part of another method or combined with one another and applied.

[0531] FIG. 27 is a flowchart illustrating a method according to one embodiment of the present specification.

[0532] Referring to FIG. 27, a method according to one embodiment of the present specification may include a first signal receiving step (S2710), a second signal transmitting step (S2720), and a third signal receiving step (S2730).

[0533] In S2710, the device receives a first signal from the reader.

[0534] In S2720, the device transmits a second signal triggered based on the first signal to the reader.

[0535] In S2730, the device receives a third signal from the reader based on the second signal.

[0536] According to one embodiment, the frequency resource associated with the third signal may be determined based on the first signal. This embodiment may be based on Method #2 / Method #3.

[0537] According to one embodiment, a plurality of frequency resources associated with a plurality of R2D (Reader to Device) transmissions may be indicated based on the first signal.

[0538] For example, the plurality of frequency resources may include frequency resources based on frequency regions set differently over time. As a specific example, the frequency resources may be based on FIG. 19 (b) / Fig. 19 (c).

[0539] According to one embodiment, the frequency resource associated with the third signal may be determined based on i) the first signal or ii) the frequency resource associated with the second signal. This embodiment may be based on Method #2 / Method #3.

[0540] For example, the frequency resource associated with the third signal may be the same as the frequency resource associated with the second signal.

[0541] According to one embodiment, the first signal may include control information related to a physical layer or a MAC layer. Specifically, the first signal may include control information generated in a physical layer or a MAC layer. For example, the control information may indicate the frequency resource related to the third signal. For example, the frequency resource related to the third signal may be indicated based on the control information. As a specific example, the control information may be L1 control information or L2 control information.

[0542] According to one embodiment, the first signal or the third signal may be based on an R2D channel, an R2D signal, or an R2D message.

[0543] For example, the first signal may be based on a paging message or an access trigger message (e.g., msg0). The second signal may be based on an access random ID message (e.g., msg1). The third signal may be based on a random ID response message (e.g., msg2).

[0544] For example, the first signal may be based on a Random ID Response message (e.g., msg2). The second signal may be based on a D2R Upper Layer Data Transfer message (e.g., msg3). The third signal may be based on a feedback message.

[0545] As a specific example, the feedback message may be a message configured to be transmitted only when the information related to the reception of the second signal is i) ACK, ii) NACK, or iii) ACK / NACK. More specifically, the feedback message may be one of i) an ACK feedback message related to the second signal, ii) a NACK feedback message related to the second signal, or iii) an ACK feedback message and a NACK feedback message related to the second signal.

[0546] According to one embodiment, the second signal can be transmitted based on backscattering of the carrier wave.

[0547] According to one embodiment, a fallback operation related to the type may be performed based on the fact that the type of the device is not supported by the reader. This embodiment may be based on Method #4 / Method #5.

[0548] For example, whether the type of the device is supported by the reader can be determined based on one of Opt1 to Opt10 of Method #4.

[0549] For example, the fallback operation may be based on Method #5. As a specific example, the fallback operation may include disabling or controlling some or all of the functions associated with the device.

[0550] Transmission by the reader may be R2D (Reader to Device) transmission, and transmission by the device may be D2R (Device to Reader) transmission.

[0551] According to one embodiment, the device and the reader may be based on devices operating based on one of four topologies related to Ambient IoT (see FIG. 1 to 5). Specifically, the reader may be i) a base station, ii) user equipment, iii) an intermediate node, or iv) an assisting node. The device may be an Ambient IoT (Internet of Things) device.

[0552] Operations based on S2710 to S2730 described above can be implemented by the device of FIG. 29. For example, referring to FIG. 29, the device (100) can control one or more transceivers (130) and / or one or more memories (140) to perform operations based on S2710 to S2730.

[0553] The embodiments described above will be explained in detail below in terms of the operation of the second device.

[0554] S2810 to S2830 described below correspond to S2710 to S2730 described in FIG. 27. Considering the above correspondence, redundant descriptions are omitted. That is, the specific description of the operation of the second device described below may be replaced by the description / embodiment of FIG. 27 corresponding to the operation.

[0555] FIG. 28 is a flowchart illustrating a method according to another embodiment of the present specification.

[0556] Referring to FIG. 28, a method according to another embodiment of the present specification may include a first signal transmission step (S2810), a second signal reception step (S2820), and a third signal transmission step (S2830).

[0557] In S2810, the reader transmits a first signal to the device.

[0558] In S2820, the reader receives a second signal triggered from the device based on the first signal.

[0559] In S2830, the reader transmits a third signal to the device based on the second signal.

[0560] According to one embodiment, the frequency resource associated with the third signal may be determined based on the first signal. This embodiment may be based on Method #2 / Method #3.

[0561] Operations based on S2810 to S2830 described above can be implemented by the device of FIG. 29. For example, referring to FIG. 29, a reader (200) can control one or more transceivers (230) and / or one or more memories (240) to perform operations based on S2810 to S2830.

[0562] Hereinafter, an apparatus to which the embodiments of the present specification can be applied (an apparatus implementing the method / operation according to the embodiments of the present specification) will be described with reference to FIG. 29.

[0563] FIG. 29 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.

[0564] The first device (100) may include a processor (110), an antenna unit (120), a transceiver (130), and a memory (140).

[0565] The processor (110) performs baseband-related signal processing and may include an upper layer processing unit (111) and a physical layer processing unit (115). The upper layer processing unit (111) may process operations of the MAC layer, RRC layer, or higher upper layers. The physical layer processing unit (115) may process operations of the PHY layer. For example, if the first device (100) is a base station device in base station-terminal communication, the physical layer processing unit (115) may perform uplink reception signal processing, downlink transmission signal processing, etc. For example, if the first device (100) is a first terminal device in terminal-terminal communication, the physical layer processing unit (115) 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 (110) may also control the overall operation of the first device (100).

[0566] The antenna section (120) may include one or more physical antennas, and if it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (130) may include an RF (Radio Frequency) transmitter and an RF receiver. The memory (140) may store information processed by the processor (110) and software, operating systems, applications, etc. related to the operation of the first device (100), and may include components such as a buffer.

[0567] The processor (110) of the first device (100) may be configured to implement the operation of the base station in base station-terminal communication (or the operation of the first terminal device in terminal-terminal communication) in the embodiments described in this disclosure.

[0568] The second device (200) may include a processor (210), an antenna unit (220), a transceiver (230), and a memory (240).

[0569] The processor (210) performs baseband-related signal processing and may include an upper layer processing unit (211) and a physical layer processing unit (215). The upper layer processing unit (211) may process operations of the MAC layer, RRC layer, or higher upper layers. The physical layer processing unit (215) may process operations of the PHY layer. For example, if the second device (200) is a terminal device in base station-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, etc. For example, if the second device (200) is a second terminal device in terminal-terminal communication, the physical layer processing unit (215) 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 (210) may also control the overall operation of the second device (210).

[0570] The antenna section (220) may include one or more physical antennas, and if it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (230) may include an RF transmitter and an RF receiver. The memory (240) may store information processed by the processor (210) and software, operating systems, applications, etc. related to the operation of the second device (200), and may include components such as a buffer.

[0571] The processor (210) of the second device (200) may be configured to implement the operation of the terminal in base station-terminal communication (or the operation of the second terminal device in terminal-terminal communication) in the embodiments described in this disclosure.

[0572] In the operation of the first device (100) and the second device (200), the details described in the examples of the present disclosure regarding the base station and terminal (or the first terminal and the second terminal in terminal-to-terminal communication) in base station-to-terminal communication may be applied in the same way, and redundant descriptions are omitted.

[0573] Here, the wireless communication technology implemented in the device of the present disclosure may include LTE, NR, and 6G, as well as Narrowband Internet of Things (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of Low Power Wide Area Network (LPWAN) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above.

[0574] Additionally or alternatively, the wireless communication technology implemented in the device of the present disclosure may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above.

[0575] Additionally or generally, the wireless communication technology implemented in the device of the present disclosure may include at least one of ZigBee, Bluetooth, and a Low Power Wide Area Network (LPWAN) for low-power communication, but is not limited to the names mentioned above. For example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4 and may be referred to by various names.

Claims

1. Regarding the method, A step of receiving a first signal from a reader by a device; A step of transmitting a second signal triggered based on the first signal to the reader by the device; and The method includes the step of receiving a third signal from the reader based on the second signal by the device; A method characterized in that the frequency resources associated with the third signal are determined based on the first signal.

2. In Paragraph 1, A method characterized by indicating a plurality of frequency resources associated with a plurality of R2D (Reader to Device) transmissions based on the first signal above.

3. In Paragraph 2, A method characterized in that the above plurality of frequency resources include frequency resources based on frequency regions set differently over time.

4. In Paragraph 1, A method characterized in that the frequency resource associated with the third signal is determined based on i) the first signal or ii) the frequency resource associated with the second signal.

5. In Paragraph 4, A method characterized in that the frequency resource associated with the third signal is the same as the frequency resource associated with the second signal.

6. In Paragraph 1, The first signal above includes control information generated in the physical layer or MAC layer, and A method characterized in that the above control information indicates the frequency resource associated with the above third signal.

7. In Paragraph 1, A method characterized in that the first signal or the third signal is based on an R2D channel, an R2D signal, or an R2D message.

8. In Paragraph 1, The first signal above is based on a paging message or an access trigger message, and The second signal above is based on an access random ID message, and A method characterized in that the third signal is based on a Random ID Response message.

9. In Paragraph 1, The first signal above is based on a Random ID Response message, and The above second signal is based on a D2R Upper Layer Data Transfer message, and A method characterized in that the above third signal is based on a feedback message.

10. In Paragraph 9, A method characterized in that the feedback message is one of i) an ACK feedback message related to the second signal, ii) a NACK feedback message related to the second signal, or iii) an ACK feedback message and a NACK feedback message related to the second signal.

11. In Paragraph 1, A method characterized in that the second signal is transmitted based on backscattering of a carrier wave.

12. In Paragraph 1, A method characterized by performing a fallback operation related to the type based on the fact that the type of the device is not supported by the reader.

13. In Paragraph 12, A method characterized in that the above fallback operation includes disabling or controlling some or all of the functions associated with the device.

14. Regarding the device, One or more transmitters / receivers; One or more processors; and It includes one or more memories connected to the above one or more processors and storing instructions, A device characterized by the above instructions enabling the device to perform all steps of the method according to any one of claims 1 to 13, based on execution by the one or more processors.

15. An electronic device comprising one or more memories and one or more processors connected to the one or more memories, An electronic device characterized in that the one or more of the above memories store instructions that cause the electronic device to perform all steps of the method according to any one of claims 1 to 13, based on execution by the one or more processors.

16. In a non-transitory computer-readable storage medium for storing instructions, A non-transitory computer-readable storage medium characterized by instructions executable by one or more processors that cause a device to perform all steps of a method according to any one of claims 1 to 13.

17. Regarding the method, A step of transmitting a first signal to a device by a reader; A step of receiving a second signal triggered by the device based on the first signal by the reader; and The method includes the step of transmitting a third signal to the device based on the second signal by the reader; A method characterized in that the frequency resources associated with the third signal are determined based on the first signal.

18. Regarding Reader, One or more transmitters / receivers; One or more processors; and It includes one or more memories connected to the above one or more processors and storing instructions, A reader characterized by the above instructions, based on execution by the one or more processors, causing the reader to perform all steps of the method according to claim 17.

Images