Method and apparatus for d2r transmission based on repetition

Abstract

A method, according to one embodiment of the present specification, comprises the steps of: receiving a first R2D message; transmitting a first D2R message on the basis of a resource selected from among X*Y resources; receiving a second R2D message; and transmitting a second D2R message on the basis of an i-th value from among one or more values. On the basis of the first R2D message, a first number of repetitions commonly used for first D2R transmission related to each of one or more first D2R messages is indicated, and on the basis of the second R2D message, a second number of repetitions commonly used for second D2R transmission related to each of one or more second D2R messages is indicated.

Description

Method and apparatus for D2R transmission based on iteration

[0001] This specification relates to a method and apparatus for iteration-based D2R transmission.

[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, the Ambient IoT device transmits msg1 (Access Random ID message) and msg3 (D2R Upper Layer Data Transfer message) during the random access procedure.

[0005] One or more D2R transmissions (by one or more devices) may be scheduled based on a single R2D message. For example, one or more values ​​related to frequency resource indication may be indicated based on the R2D message. When one or more D2R transmissions are scheduled based on the R2D message as described above, it may be difficult for each device receiving the R2D message to clearly identify or determine the value related to its D2R transmission (e.g., one of the one or more values ​​mentioned above). Specifically, the following problems may arise.

[0006] Each device becomes unable to uniquely specify the value to be applied to its D2R transmission. Furthermore, there is a possibility that different interpretations of the value applied to the D2R transmission may occur depending on the device. Specifically, a discrepancy may arise between the scheduling results intended by the reader and the actual device behavior.

[0007] The possibility of collisions increases as values ​​related to frequency resources are incorrectly selected. For example, if multiple devices perform D2R transmission over the same frequency resource, mutual interference and collisions may occur, potentially degrading reception performance.

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

[0009] Meanwhile, D2R transmissions can be generated based on repetition. In other words, a device can perform D2R transmissions based on repetition. In a single procedure (e.g., an Ambient IoT-related procedure), the transmission and reception of multiple R2D messages (e.g., first / second R2D messages) and multiple D2R messages (e.g., first / second D2R messages) between a reader and a base station can be performed sequentially. As described above, a single R2D message (e.g., a first R2D message or a second R2D message) can schedule one or more D2R messages (e.g., one or more first D2R messages or one or more second D2R messages). At this time, the question arises whether one or more repetition counts (per D2R transmission) should be indicated through each R2D message in the same form as the frequency resource indication described above, or whether the same number of repetition counts should be applied to all D2R transmissions considering that they are part of the same procedure. In other words, it is unclear whether the number of repetitions for each D2R transmission must be specified individually for each R2D message, or whether the same number of repetitions must be applied uniformly to all D2R transmissions within the same procedure.

[0010] Due to such ambiguity, the interpretation of the number of repetitions may differ between the reader and the device, which may consequently degrade the consistency of D2R transmission operations. Additionally, if the number of repetitions is individually specified for each D2R transmission, the amount of control information increases, which may lead to increased signaling overhead. Furthermore, since the reader must separately manage the number of repetitions for each D2R transmission by each device, implementation complexity may increase, and errors in applying the number of repetitions may result in transmission failure or degraded reception performance. Moreover, the operational efficiency of wireless resources may decrease, and the consistency of the entire procedure may be compromised.

[0011] Another objective of this specification is to propose a method for more effectively indicating the number of repetitions for multiple D2R messages (e.g., a first D2R message, a second D2R message) transmitted and received within the same procedure.

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

[0013] A method according to an embodiment of the present specification for solving the aforementioned technical problem comprises the steps of receiving a first R2D (Reader to Device) message, transmitting a first D2R (Device to Reader) message based on a resource selected from X*Y resources, receiving a second R2D message, and transmitting a second D2R message based on an i-th value among one or more values. Based on the first R2D message, the number of time resources X and the number of frequency resources Y are indicated. The X*Y resources are associated with the transmission of one or more first D2R messages. Based on the second R2D message, the one or more values ​​associated with frequency resources are indicated. The one or more values ​​are associated with the transmission of one or more second D2R messages. The first D2R message includes a first ID based on a random number. The second R2D message includes one or more second IDs. The i-th value is determined based on the order of the second IDs associated with the first ID among the one or more second IDs. It is characterized by indicating a first repetition number commonly used for first D2R transmissions associated with each of the one or more first D2R messages based on the first R2D message, and a second repetition number commonly used for second D2R transmissions associated with each of the one or more second D2R messages based on the second R2D message.

[0014] Accordingly, the device can clearly determine the value for its D2R transmission from among one or more values ​​associated with frequency resource indication. Additionally, since one repetition count is indicated for one or more D2R messages (based on the same kind / type) (e.g., one or more first D2R messages or one or more second D2R messages), the repetition count can be indicated more effectively, and ambiguity regarding the application of the repetition count can be resolved.

[0015] According to the embodiments of the present specification, the device can resolve ambiguities regarding the determination of a value for D2R transmission (transmission of a second D2R message) among lower or higher values ​​related to frequency resources. Therefore, since the problem of multiple devices mistaking the same value for their own value can be prevented, the possibility of D2R transmission collisions and interference can be reduced.

[0016] In addition, by mapping frequency resource-related values ​​based on the order of the second ID associated with the first ID without a separate additional mapping field, the structure of the second R2D message can be simplified and control overhead reduced.

[0017] Even if D2R messages are transmitted and received sequentially within the same procedure, the data size (payload size) and transmission power may differ for each D2R message. According to an embodiment of this specification, a first number of repetitions commonly used for the first D2R transmission associated with each of the one or more first D2R messages is indicated based on the first R2D message, and a second number of repetitions commonly used for the second D2R transmission associated with each of the one or more second D2R messages is indicated. Thus, the number of repetitions suitable for the message characteristics can be indicated. As a specific example, a larger number of repetitions may be indicated for a second D2R message with a relatively larger payload, and a smaller number of repetitions may be indicated for a first D2R message with a relatively smaller payload. Through this, unnecessary repetitions in each D2R transmission can be minimized, thereby increasing wireless resource utilization and the power efficiency of the device.

[0018] In addition, since there is no need to individually specify the number of repetitions for each D2R message having the same characteristics, signaling overhead can be reduced by decreasing the amount of control information (e.g., the payload size of the first and second R2D messages). Furthermore, implementation complexity can be mitigated by simplifying the repetition management logic of the device and reader.

[0019] In addition, the reliability of D2R transmission can be improved by reducing errors in applying the number of repetitions, and the consistency and efficiency of resource management for D2R message(s) scheduled by the same R2D message can be improved.

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

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

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

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

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

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

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

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

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

[0029] FIG. 9 illustrates the structure of device type 1.

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

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

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

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

[0034] FIG. 14 shows examples of indexing of MSG1 resources according to embodiments of the present specification.

[0035] FIG. 15 illustrates frequency-first indexing and time-first indexing of MSG3 resources according to an embodiment of the present specification.

[0036] FIG. 16 shows examples of mapping between MSG3 resources and IDs according to embodiments of the present specification.

[0037] FIG. 17 illustrates other examples of mapping between MSG3 resources and IDs according to embodiments of the present specification.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0059]

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

[0061]

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

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

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

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

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

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

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

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

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

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

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

[0073] 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 the 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 the auxiliary node. Here, for example, the auxiliary node may be an A-IoT-enabled relay, IAB node, terminal, repeater, etc.

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

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

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

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

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

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

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

[0081] General range

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

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

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

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

[0086] -X is determined in WG.

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

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

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

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

[0091] - Deployment Scenario 1 using Topology 1

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

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

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

[0095] The location of the intermediate node is indoors

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

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

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

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

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

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

[0102] 1. Evaluation Assumptions

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

[0104] Clause 5.3: Applicable maximum distance target value

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

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

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

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

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

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

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

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

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

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

[0115] - RAN1-led:

[0116] For Ambient IoT DL and UL:

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

[0118] Numerology, Bandwidth, and Multiple Access

[0119] Waveform and Modulation

[0120] Channel coding

[0121] Downlink Channel / Signal Aspect

[0122] Uplink Channel / Signal Side

[0123] Scheduling and Timing Relationships

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

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

[0126] RAN2 Lead:

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

[0128] for example:

[0129] Paging

[0130] Random access

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

[0132] Interaction with the upper class

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

[0134] RAN3 Leading:

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

[0136] Paging

[0137] Device Context Management

[0138] Data transmission

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

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

[0141] RAN4 Leading:

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

[0143] Research on RF Requirements for Ambient IoT:

[0144] Ambient IoT BS Transmitter / Receiver

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0167] - SSB: Synchronization Signal Block

[0168] - MIB: Master Information Block

[0169] - RMSI: Remaining Minimum System Information

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

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

[0172] - BW: Bandwidth

[0173] - BWP: Bandwidth Part

[0174] - RNTI: Radio Network Temporary Identifier

[0175] - CRC: Cyclic Redundancy Check

[0176] - SIB: System Information Block

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

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

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

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

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

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

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

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

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

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

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

[0188] - SCS: subcarrier spacing

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

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

[0191] - TB: Transport Block

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

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

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

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

[0196] - FDRA: Frequency Domain Resource Allocation

[0197] - TDRA: Time Domain Resource Allocation

[0198] - RA: Random Access

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

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

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

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

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

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

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

[0206] - RAR: Random Access Response

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

[0208] - FH: Frequency Hopping

[0209] - iBWP: initial BWP

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

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

[0212] - CS: Cyclic shift

[0213] - NB: Narrowband

[0214] - TO: Traffic Offloading

[0215] -mMTC; Massive Machine Type Communications

[0216] - eMBB: enhanced Mobile Broadband Communication

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

[0218] - RedCap: Reduced Capability

[0219] - eRedCap: enhanced RedCap

[0220] - FDD: Frequency Division Duplex

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

[0222] - DRX: Discontinuous Reception

[0223] - RRC: Radio Resource Control

[0224] - RRM: Radio Resource Management

[0225] - MM: Mobility Management

[0226] - IWSN: Industrial Wireless Sensor Network

[0227] - LPWA: Low Power Wide Area

[0228] - RB: Resource Block

[0229] - CCE: Control Channel Element

[0230] - AL: Aggregation Level

[0231] - PRG: Physical Resource-block Group

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

[0233] - PBCH: Physical Broadcast Channel

[0234] - A-PBCH: Additional PBCH

[0235] - BD: blind detection

[0236] - EPRE: Energy Per RE

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

[0238] - TDM: Time Division Multiplexing

[0239] - FDM: Frequency Division Multiplexing

[0240] - DMRS: DeModulation Reference Signal

[0241] - TDD: Time Division Duplex

[0242] - PCI: Physical layer Cell ID

[0243] - EH: Energy Harvesting

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

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

[0246] - ET: Energy Transfer

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

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

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

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

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

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

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

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

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

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

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

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

[0259] - RF-EH: RF energy harvesting

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

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

[0262] - BS: Base Station

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

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

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

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

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

[0268] - F-gap: Frequency gap

[0269] - T-gap: Time gap

[0270] - TD: Time Domain

[0271] - FD: Frequency Domain

[0272] - PEI: Paging Early Indication

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

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

[0275] - RSRP: Reference Signal Received Power

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

[0277] - PRB: Physical Resource Block

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

[0279] - PHR: Power Headroom Report

[0280] - EHR: Energy Headroom Report

[0281] - BPF: Band-Pass Filter

[0282] - SM: Subcarrier Modulation

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

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

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

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

[0287]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0307] TDM / FDM transmission of Msg1 and Msg3

[0308] 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 X times within a specific slot in an inventory round to generate X sub-slots, and each sub-slot undergoes FDM Y times to generate Y 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.

[0309] Specifically, after receiving Msg2 within the aforementioned specific slot, the Msg3 resource is TDMed X times to create X sub-slots, and each sub-slot is FDMed Y times to create Y 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.

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

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

[0312] 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 preamble of Msg0 that triggered the Msg1. If Msg0 does not indicate / set / include the start time and length of the window, or if Msg0's L1 control info, L2 control info, MAC CE, or preamble indicates / sets the exclusion of the start time and length of the window, the device monitors Msg2 by determining the start time and length of the window using a stored pre-defined value. Alternatively, if Msg0's L1 control info, L2 control info, MAC CE, or preamble indicates the use of a pre-defined value, the device monitors Msg2 by determining the start time and length of the window using a stored pre-defined value.

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

[0314] In 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.

[0315] In this specification, an x-amble may include at least one of a preamble, a midamble, and / or a postamble. An x-amble may be a specific sequence or a specific binary pattern (e.g., all '1's or all '0's or a combination of '1's and '0's'). Meanwhile, in this specification, in addition to the D2R preamble transmitted prior to the PDRCH, if an x-amble is added immediately after the D2R preamble, immediately before or after the PDRCH, or within the PDRCH, the added x-amble occupies the time / frequency resources of the PDRCH. In this case, the length corresponding to the x-amble may or may not be included in the TB size or message size of the PDRCH. Additionally, if an x-amble is added according to the option(s) below, and the addition of the x-amble exceeds the allocated PDRCH resource range, the following actions may be performed. For example, the device may truncate the portion of the resource that exceeds the allocated PDRCH resource range to transmit the PDRCH within the allocated resource range. For example, a device may transmit a PDRCH that includes a portion of the resource that exceeds the allocated PDRCH resource range. Accordingly, the reader may receive it taking this into account.

[0316] RA trigger method based on MSG3 size

[0317] According to one embodiment, when MSG0 indicates an S3 value or less, only devices whose size of MSG3 data to be transmitted (for example, data stored in the Layer 2 buffer for MSG3 of the current device) or device ID length to be included in MSG3 is less than or equal to the indicated S3 value can transmit MSG1.

[0318] According to one embodiment, if MSG0 indicates a value greater than or equal to S3, only devices whose size of the MSG3 data to be transmitted (e.g., data stored in the Layer 2 buffer for MSG3 of the current device) or device ID length to be included in the MSG3 is greater than or equal to the indicated S3 value may transmit MSG1. If a device fails to transmit MSG1 according to the S3 value, the device may continue to monitor MSG0 to receive the next MSG0 and transmit MSG1 according to the received next MSG0. In this case, the previous MSG0-1 may indicate whether to transmit the next MSG0-2 and the timing (e.g., monitoring period or time / frequency resources). MSG0-1 and MSG0-2 may indicate the transmission of MSG3 for different MSG3 sizes or device ID lengths. In this case, MSG0-1 may be a paging message and MSG0-2 may be a subsequent paging message. MSG0-1 and MSG0-2 can be paging and subsequent paging that constitute the inventory process of the same round.

[0319] According to one embodiment, a device transmits MSG1 and receives MSG2 in response thereto, and if MSG2 indicates an S3 value or less, only devices whose size of MSG3 data to be transmitted (for example, data stored in the Layer 2 buffer for MSG3 of the current device) or device ID length to be included in MSG3 is less than or equal to the indicated S3 value can transmit MSG3.

[0320] According to one embodiment, if MSG2 indicates a value greater than or equal to S3, only devices whose size of the MSG3 data to be transmitted (e.g., data stored in the Layer 2 buffer for MSG3 of the current device) or device ID length to be included in the MSG3 is greater than or equal to the indicated S3 value may transmit MSG3. If a device fails to transmit MSG3 according to the S3 value, the device may continue to monitor MSG2 to receive the next MSG2 and transmit MSG3 according to the received next MSG2. In this case, the previous MSG2-1 may indicate whether to transmit the next MSG2-2 and the timing (e.g., monitoring period or time / frequency resources). The previous MSG2-1 and the next MSG2-2 may be transmitted as a response to the device(s) that transmitted MSG1 prior to the transmission of MSG2-1. Meanwhile, MSG2-1 and MSG2-2 may indicate the transmission of MSG3 for different MSG3 sizes or device ID lengths.

[0321] [Method #1] RA trigger and x-amble method based on repetition number and / or coding rate

[0322] The device receives MSG0, and if a repetition number and / or coding rate is specified based on MSG0, the device transmits MSG1 PDRCH based on the specified repetition number and / or coding rate.

[0323] In this case, if the repetition number is not specified or is specified as 1, the device transmits MSG1 PDRCH without repetition. Additionally, if the coding rate is not specified or is specified as 1, the device may transmit MSG1 PDRCH omitting channel coding. In this case, MSG1 may be a random number, a specific sequence, or the ID of the device.

[0324] In such MSG1 transmissions, the reader may trigger MSG1 transmissions for device(s) or a group of devices by changing the repetition number and / or coding rate based on MSG0. In this case, the device may respond only to MSG0s that indicate a supported repetition number and / or coding rate. A device that does not receive a response to MSG1 via MSG2 or fails to (successfully) transmit MSG3 may act as follows: The device may continue to monitor MSG0 and trigger MSG1 transmissions until it receives a response to MSG2 or successfully transmits MSG3.

[0325] At this time, the repetition number and / or coding rate of the MSG0 PRDCH may also be changed and transmitted. In particular, the repetition number and / or coding rate of the MSG1 PDRCH indicated by the MSG0 may be indicated as a value proportional to the repetition number and / or coding rate applied to the transmission of the MSG0 PRDCH.

[0326] The device receives MSG2, and if a repetition number and / or coding rate is specified based on MSG0 or MSG2, the device transmits MSG3 PDRCH based on the specified repetition number and / or coding rate.

[0327] In this case, if the repetition number is not specified or is specified as 1, the device transmits MSG3 PDRCH without repetition. Additionally, if the coding rate is not specified or is specified as 1, the device may transmit MSG3 PDRCH omitting channel coding. In this case, MSG3 may include a random number, a specific sequence, or the device ID.

[0328] In such MSG3 transmissions, the reader may direct MSG3 transmissions of a device(s) or group of devices by changing the repetition number and / or coding rate with one or more MSG2 transmissions. In this case, the device may transmit MSG3 only for MSG2s that indicate a supported repetition number and / or coding rate. A device that does not receive a response to MSG3 via MSG4 or fails to transmit MSG3 (successfully) may act as follows: The device may continue to monitor MSG2s until it receives a response via MSG4 or successfully transmits MSG3, and transmit MSG3 upon receiving the next MSG2.

[0329] At this time, the repetition number and / or coding rate of the MSG0 or MSG2 PRDCH may also be changed and transmitted. In particular, the repetition number and / or coding rate of the MSG3 PDRCH indicated by the MSG0 or MSG2 may be indicated as a value proportional to the repetition number and / or coding rate applied to the transmission of the MSG0 or MSG2 PRDCH.

[0330] Meanwhile, when the above MSG1 PDRCH or MSG3 PDRCH is transmitted based on a specified repetition number and / or coding rate, the preamble / midamble / postamble of the PDRCH may also be repeated and transmitted together according to the specified repetition number and / or coding rate. For example, if a repetition number = 3 or a coding rate = 1 / 3 is specified, the device may transmit the sequence of x-ambles by repeating it three times in sequence units or by repeating it three times in sequence bit or chip units. For example, if a repetition number = 2 and a coding rate = 1 / 3 are specified together, the device may transmit the sequence of x-ambles by repeating it six times in sequence units or by repeating it six times in sequence bit or chip units. In this case, the repeated sequence may be repeated continuously or discontinuously. For example, if repeated discontinuously, it may be repeated before / in the middle / after the PDRCH, or it may be transmitted by repeating it discontinuously within the PDRCH at regular intervals or according to a certain rule.

[0331] Meanwhile, depending on the repetition number and / or coding rate of the PDRCH to be transmitted, the device may transmit the PDRCH by selecting a PDRCH resource specified for a specific repetition number and / or coding rate. For example, if the PDRCH is associated with MSG1 or MSG3, the device may transmit MSG3 or MSG1 by selecting an MSG3 or MSG1 resource in the following manner.

[0332] Alt 1: If MSG3 size or Device ID length is greater than or equal to S3, or if MSG3 size or Device ID length is less than S3, the device selects an MSG1 resource mapped to the repetition number and / or coding rate specified by MSG0, and sends MSG1 PDRCH to the selected MSG1 resource.

[0333] For example, if MSG2 received in response to MSG1 transmission indicates a repetition number and / or coding rate, MSG3 is transmitted based on the indicated repetition number and / or coding rate. On the other hand, if there is no repetition number and / or coding rate indicated by MSG2, MSG3 is transmitted based on the repetition number and / or coding rate mapped to the MSG1 resource transmitted by the device.

[0334] Alt 2: If MSG3 size or Device ID length is greater than or equal to S3 and MSG3 PDSCH cannot be transmitted based on the repetition number and / or coding rate specified by MSG0 or MSG2 with the size of the MSG3 PDSCH resource specified based on MSG2, the device may operate as follows: The device transmits MSG3 PDSCH by changing the repetition number and / or coding rate specified based on MSG0 or MSG2 to a different repetition number and / or coding rate.

[0335] At this time, the device determines the coding rate with an MSG3 transmission length that is as close as possible to the size of the resource.

[0336] For example, the device determines possible coding rate(s) such that the size of the resource and the MSG3 transmission length are equal, or the MSG3 transmission length is less than or equal to the size of the resource. If there are multiple possible coding rate(s), the device selects the lowest coding rate. Specifically, if both 1 / 2 and 1 / 3 coding rates are possible, the device selects the 1 / 3 coding rate. Specifically, if there is a specified coding rate, the device selects the specified coding rate based on MSG0 / 2.

[0337] Meanwhile, if the repetition number and / or coding rate is changed as described above, the changed repetition number and / or coding rate of MSG3 PDSCH may be indicated based on the D2R control info of MSG3 PDSCH.

[0338] Alt 3: The device itself determines the repetition number and / or coding rate to match the size of the time / frequency resource indicated by MSG2 and transmits MSG3 PDSCH.

[0339] At this time, the device determines the coding rate with an MSG3 transmission length that is as close as possible to the size of the resource.

[0340] For example, the device determines possible coding rate(s) such that the size of the resource and the MSG3 transmission length are equal, or the MSG3 transmission length is smaller than or equal to the size of the resource.

[0341] In this case, if there are multiple possible coding rate(s), the device selects the lowest coding rate. Specifically, if both 1 / 2 and 1 / 3 coding rates are possible, the device selects the 1 / 3 coding rate. Specifically, if there is a specified coding rate, the device selects the specified coding rate based on MSG0 / 2.

[0342] In particular, if there is no repetition number and / or coding rate specified by MSG0 or MSG2, or if there is no pre-configured or pre-defined repetition number and / or coding rate, the device determines a repetition number and / or coding rate in accordance with the size of the time / frequency resource specified by MSG2. The device transmits an MSG3 PDSCH based on the determined repetition number and / or coding rate. If there is a repetition number and / or coding rate specified by MSG0 or MSG2, or if there is a pre-configured or pre-defined repetition number and / or coding rate, the device transmits an MSG3 PDSCH based on the specified repetition number and / or coding rate.

[0343] Meanwhile, as described above, if the device determines the repetition number and / or coding rate, the repetition number and / or coding rate determined based on the D2R control info of the MSG3 PDSCH may be indicated.

[0344] Meanwhile, in this specification, the device may fail to transmit PDRCH repeatedly for the promised number of repetitions due to insufficient energy or other reasons. For example, it may be assumed that although the reader instructed the device to transmit MSG1 or MSG3 PDRCH N times, the device transmits PDRCH only once due to insufficient energy or other reasons, or transmits PDRCH only k times, which is less than N. In this case, if the device transmits only once or k ( <N)번 만큼만 반복 전송한다면, 디바이스는 PDRCH 전송 마지막에 x-amble을 전송하고 전송을 중단한다. 이때 x-amble은 특정 sequence값을 갖는 midamble일 수 있다. 특정 sequence값에 기초하여 D2R 전송의 early stop이 지시될 수 있다.

[0345] Additionally, if the reader does not specify the number of repeated transmissions, the device may transmit PDRCH only once or repeatedly. Even in this case, the device transmits an x-amble at the end of the PDRCH transmission and stops the transmission. Here, the x-amble may be a midamble with a specific sequence value. Based on the specific sequence value, the stop of D2R transmission may be indicated.

[0346] When a PDRCH transmission is performed in this manner, the reader performs blind detection on the corresponding x-amble and attempts to detect whether a PDRCH transmission follows the x-amble (e.g., based on energy).

[0347] [Method #2] x-amble / padding-based MSG3 transmission method

[0348] The control information of PRDCH may indicate TBS-like information for scheduling PRDCH transmissions. The indicated TBS information may be a maximum TB size, particularly when the reader cannot accurately estimate the amount of data available for D2R transmission on the device side. Therefore, if the amount of data available for D2R transmission is greater than or equal to the indicated TB size, PDRCH transmits an amount of data corresponding to the indicated TB size. On the other hand, if the amount of data available for D2R transmission is smaller than the indicated TB size, PDRCH may include unnecessary padding corresponding to the indicated TB size. According to the embodiments of this specification, an x-amble, such as a midamble, may be added to the PDRCH for padding. The midamble may be added to the middle or end of the PDRCH according to a rule.

[0349] The messages (MSG0, MSG1, MSG2, MSG3) mentioned in this specification in relation to the Ambient IoT random access procedure may be referred to or replaced by other terms as follows. For example, MSG0 may be referred to or replaced by the first R2D message or A-IoT Paging message. For example, MSG1 may be referred to or replaced by the first D2R message or Access Random ID message. For example, MSG2 may be referred to or replaced by the second R2D message or Random ID Response message. For example, MSG3 may be referred to or replaced by the second D2R message or D2R Upper Layer Data Transfer message.

[0350] For example, if MSG3 frequency resources are allocated via MSG0 or MSG2, a common time resource is allocated to multiple frequency resources, or the length of the time resource is allocated / instructed via MSG0 or MSG2. In this case, the length of the time resource can be allocated / instructed to match the maximum MSG3 size. Therefore, if the MSG3 size that the actual device intends to send (for example, the size of the data currently stored in the device's MSG3 Layer 2 buffer) is smaller than the maximum size, an issue may arise regarding how to fill the allocated time resource. In this case, the device may transmit an MSG3 PDRCH according to one or some of the following options.

[0351] In the options below, if the pre-amble or midamble typically added consists of two parts (sequence + square wave), the x-amble added via this option can be added as a sequence only or as a square wave only.

[0352] Opt 1: Regardless of the instructions of MSG0 or MSG2, the device transmits MSG3 as follows.

[0353] Opt 1-1: If the MSG3 size length to be transmitted is smaller than a specific size (e.g., the maximum size above), add x-amble to the MSG3 PDRCH and transmit.

[0354] For example, when transmission is typically performed via Preamble + MSG3 PDRCH, a Midamble is added before, after, or at an intermediate point of the PDRCH according to the above conditions.

[0355] In particular, if the difference between a specific size and the MSG3 size to be transmitted is greater than or equal to the x-amble length, the device fills the time resources with one or more x-amble(s) and transmits the MSG3 PDRCH. If, after filling the x-amble once or multiple times, the remaining resource portion is smaller than or equal to the x-amble length, the device may fill and transmit using the following Opt 1-2 method.

[0356] Opt 1-2: If the MSG3 size length to be transmitted is equal to a specific size (e.g., the maximum size above), or if the difference between the specific size and the MSG3 size to be transmitted is less than or equal to the x-amble length, the device transmits MSG3 PDRCH without x-amble.

[0357] At this time, the device fills the remaining resource portion with one of the following paddings and transmits it.

[0358] padding the remaining length with signals corresponding to '0' or '1'

[0359] Pad the entire remaining length with a high (or low) voltage signal

[0360] padding with signals from a portion of the x-amble trimmed to fit the remaining length

[0361] padding with signals from a portion of the MSG3 payload trimmed to fit the remaining length

[0362] padding with signals from a portion of the CRC trimmed to fit the remaining length

[0363] Meanwhile, if the MSG3 size to be transmitted is larger than the maximum MSG3 size, the device segments the data to be transmitted and transmits an MSG3 PDRCH equal to the maximum MSG3 size. Subsequently, in order to transmit the remaining data after segmentation via the next MSG3 PDRCH, the device monitors for the next MSG2 transmission immediately after the MSG3 PDRCH it has transmitted, or immediately after a specific time has elapsed starting from the end of the last resource among the MSG3 time resources. If the next MSG2 is received during the specific monitoring time and the MSG2 indicates or allocates an MSG3 resource for the next segment, the device transmits the next MSG3 PDRCH containing the next segment. In this case, if the next segment is the last segment and is smaller than the maximum MSG3 size, the device may transmit the next MSG3 PDRCH according to the aforementioned Opt 1-1 (adding x-amble) or Opt 1-2 (padding).

[0364] Opt 2:

[0365] If MSG0 or MSG2 indicates x-amble or padding, or includes a specific indicator, the device transmits MSG3 PDRCH according to the above Opt1.

[0366] If MSG0 or MSG2 does not specify an x-amble or padding, or does not include a specific indicator, the device transmits MSG3 PDRCH according to one of the following options.

[0367] Opt 2-1: If the MSG3 size to be transmitted is smaller than the maximum size, the device adds the following padding at the beginning / end, middle, or specific point of the MSG3 PDRCH to match the maximum size and transmits it.

[0368] At this time, the remaining resource portion is filled with one of the following paddings and transmitted.

[0369] A. Pad the remaining length with signals corresponding to '0' or '1'

[0370] B. Pad the entire remaining length with a high (or low) voltage signal

[0371] C. Padding with signals from a portion of the x-amble trimmed to the remaining length

[0372] D. Padding with signals from a portion of the MSG3 payload trimmed to fit the remaining length

[0373] E. Padding with signals from a portion of the CRC trimmed to fit the remaining length

[0374] Opt 2-2: Assuming the reader knows the MSG3 size, the device transmits the current actual MSG3 size without padding. Specifically, the device transmits the MSG3 PDRCH without padding.

[0375] Opt 2-3: The device adds control info to the MSG3 PDRCH and indicates the current actual MSG3 size as the control info. In this case, the MSG3 PDRCH is transmitted without padding.

[0376] Alternatively, the device transmits the MSG3 PDRCH by adding L1 / L2 control info to the MSG3 PDRCH. In this case, the size of the L1 / L2 control info is equal to the difference between a specific size and the MSG3 size to be transmitted. If the L1 / L2 control info includes information indicating the MSG3 size and other necessary information, the bits that do not contain information can be set to all 0 or all 1.

[0377] Meanwhile, if the MSG3 size to be transmitted is larger than the maximum MSG3 size, the device segments the data to be transmitted and transmits an MSG3 PDRCH equal to the maximum MSG3 size. Subsequently, in order to transmit the remaining data after segmentation via the next MSG3 PDRCH, the device monitors for the next MSG2 transmission immediately after transmitting the MSG3 PDRCH it has transmitted, or immediately after a specific time has elapsed starting from the end of the last resource among the MSG3 time resources. If the device receives the next MSG2 during the specific monitoring time and the MSG2 indicates or allocates an MSG3 resource for the next segment, the device transmits the next MSG3 PDRCH containing the next segment. At this time, if the next segment is the last segment and is smaller than the maximum MSG3 size, the next MSG3 PDRCH can be transmitted according to the above Opt 2-1 / 2-2 / 2-3.

[0378] Opt 3:

[0379] If MSG0 or MSG2 indicates the exact MSG3 size that the device intends to transmit (or an MSG3 size with an error of less than a certain number of bits), the following operation may be performed. Specifically, assuming the reader knows the MSG3 size, the device transmits the exact MSG3 size without padding.

[0380] If MSG0 or MSG2 does not specify the MSG3 size, or if the specified MSG3 size differs from the size the device intends to transmit and the difference exceeds a certain number of bits, the following operation may be performed. Specifically, the device transmits the MSG3 PDRCH by adding padding or x-amble, such as the option mentioned above, to the MSG3 PDRCH to match the maximum size.

[0381] Opt 4: (If MSG0 or MSG2 directs rate matching) If the MSG3 size to be transmitted is smaller than the maximum size, the device may repeat a portion of the MSG3 payload. In other words, the device may transmit MSG3 PDRCH to match the maximum size through repetition-based rate matching.

[0382] At this time, the device can transmit the MSG3 PDRCH by adding L1 / L2 control info to the MSG3 PDRCH, and the L1 / L2 control info can indicate whether or not the rate matching is indicative.

[0383] If MSG0 or MSG2 does not instruct rate matching, assuming the reader knows the MSG3 size, the device transmits with the exact MSG3 size without padding.

[0384] If the device sends an ACK or NACK for MSG2 to D2R, in addition to the above options, it can indicate whether MSG3 PDRCH is an ACK or a NACK using D2R L1 control info within MSG3 PDRCH.

[0385] For example, the device may apply the above options only when transmitting an ACK for MSG2.

[0386] For example, an ACK for MSG2 can be indicated by a specific sequence of D2R x-amble or by D2R L1 / L2 control info.

[0387] Meanwhile, if the device transmits a NACK for MSG2, it transmits MSG3 PDRCH by applying one of the following options.

[0388] Opt 3-1: The device transmits MSG3 PDRCH with only the size of NACK, without padding / x-amble.

[0389] Opt 3-2: The device transmits PDRCH including NACK along with padding / x-amble.

[0390] Opt 3-3: The device transmits MSG3 PDRCH with only L1 / L2 control info including NACK, without the PDRCH payload.

[0391] Opt 3-4: The device transmits only the D2R preamble sequence corresponding to NACK without MSG3 PDRCH.

[0392] Meanwhile, when the device transmits an ACK via MSG3 PDRCH as per the above options, it may indicate the ACK with a specific sequence of x-amble or L1 control info. Additionally, when the device transmits a NACK via MSG3 PDRCH as per the above options, the device transmits a D2R preamble sequence corresponding to the NACK and a PDRCH indicating the NACK.

[0393] When the device transmits an ACK or NACK as described above, the reader can perform the following actions.

[0394] For example, the reader can perform blind detection of ACK / NACK. For example, the reader can decode ACK or NACK information within the PDRCH. For example, the reader can determine that the PDRCH is ACK / NACK based on the sequence of D2R x-ambles. For example, the reader can determine that the PDRCH is ACK / NACK by decoding instructions of D2R L1 / L2 control info within the PDRCH.

[0395] For example, in this specification, even if the device does not additionally transmit the x-amble, a D2R preamble may always be transmitted by default before the PDRCH.

[0396] MSG1-based Msg3 resource determination method

[0397] According to one embodiment, it may be assumed that the device transmits Msg1, and that Msg0 or Msg2 does not explicitly indicate a Msg3 resource for the device or Msg1. In this case, the device may transmit Msg3 by determining the Msg3 resource in one or some of the following options.

[0398] According to one embodiment, the device transmits Msg1 and can transmit Msg3 by determining a Msg3 resource in one or some of the following ways. In this case, if Msg0 or Msg2 explicitly indicates a Msg3 resource for the device or Msg1, the indicated Msg3 resource may be selected preferentially over the determined Msg3 resource, and Msg3 may be transmitted to the selected Msg3 resource.

[0399] Opt 1: Index based Msg3 resource determination

[0400] If Msg0 or Msg2 specifies the number of frequency resources Y and the number of time resources X for Msg 3, Msg3 resources equal to the product of X and Y are allocated according to the specified X and Y. In this case, if Msg0 or Msg2 does not explicitly specify the Msg3 resources for a specific Msg1 or the specific device that transmitted it, the device determines the Msg3 resources mapped to the Msg1 resources it transmitted as follows, and transmits Msg3 using the determined Msg3 resources. This will be explained below with reference to FIG. 14.

[0401] FIG. 14 shows examples of indexing of MSG1 resources according to embodiments of the present specification.

[0402] For example, the device indexes the resources Msg1 and Msg3 as in the examples of FIG. 14, and when Msg1 is transmitted to the resource corresponding to index = k, Msg3 is also transmitted to the resource corresponding to index = k.

[0403] In this case, the mapping between Msg1 resources and Msg3 resources can be determined according to specific rules, pre-defined, or directed. The leader may also direct the following mapping through Msg0 or Msg2.

[0404] Figures 14 (a) to (d) show examples related to MSG1 resource indexing.

[0405] For example, if the Msg1 resource is indexed as in one of (a) to (d) of FIG. 14, and the Msg3 resources are assigned / directed as X=2, Y=2 (in the case where 4 Msg3 resources are assigned / directed), the Msg1 resources and Msg3 resources can be mapped in the following Option1-1 or Option1-2 manner.

[0406] FIG. 15 illustrates frequency-first indexing and time-first indexing of MSG3 resources according to an embodiment of the present specification.

[0407] Option1-1: Frequency-first indexing (Indexing from frequency to time resources)

[0408] Figure 15 (a) illustrates frequency-first indexing.

[0409] Referring to Fig. 15(a), in the case of frequency-first indexing, indexing is first performed on all frequency resources in the first time resource (e.g., Msg3 resource index 1 -> Msg3 resource index 2), and then indexing is performed by moving to all frequency resources in the next time resource (e.g., Msg3 resource index 3 -> Msg3 resource index 3). Indexing in the same manner as above is performed up to all frequency resources in the last time resource.

[0410] Option1-2: Time-first indexing (Indexing from time to frequency resources)

[0411] Figure 15 (b) illustrates time-first indexing.

[0412] Referring to Fig. 15(b), in the case of time-first indexing, indexing is first performed on all time resources on the first frequency resource (e.g., Msg3 resource index 1 -> Msg3 resource index 2), and then indexing is performed by moving to all time resources on the next frequency resource (e.g., Msg3 resource index 1 -> Msg3 resource index 2). Indexing in the same manner as above is performed up to all time resources on the last frequency resource.

[0413] Opt 2: Prioritize the same frequency

[0414] If the same frequency resource as Msg1 transmitted by the device is allocated for Msg3, the device transmits Msg3 using the same frequency resource.

[0415] At this time, the Msg3 frequency resource is allocated based on Msg0 or Msg2.

[0416] If a frequency resource for Msg3 identical to the frequency resource for Msg1 transmitted by the device is not allocated, the device operates with one of the following options.

[0417] If Msg2 specifies the Msg3 frequency resource for the device, the device transmits Msg3 to the specified Msg3 frequency resource.

[0418] If Msg2 does not specify the Msg3 frequency resource for the corresponding device, it operates as one of the following options.

[0419] Option 2-1: The device monitors the next Msg2 transmission within the current or next Msg2 monitoring cycle. Based on the next Msg2, the same Msg3 frequency resource as the Msg1 transmitted by the device may be allocated, or a different Msg3 frequency resource may be allocated.

[0420] Option 2-2: The device sends Msg1 back.

[0421] Option 2-3: The device (stops the random access process) and monitors and receives Msg0 again.

[0422] Opt 3: Device ID based resource determination

[0423] Option 3-1: When one or more IDs are indicated as Msg0 or Msg2, the frequency resource for the corresponding ID is determined according to the formula Device ID mod Y = frequency resource index. If there are multiple IDs with the same frequency resource index value, these ID(s) are sorted in ascending or descending order, and the first ID to the last ID is mapped sequentially from the first time resource to the last time resource for the determined frequency resource.

[0424] Option 3-2: When one or more IDs are indicated as Msg0 or Msg2, the time resource for the corresponding ID is determined according to the formula Device ID mod X = time resource index. If there are multiple IDs with the same time resource index value, these ID(s) are sorted in ascending or descending order, and the first ID to the last ID is mapped sequentially to the first frequency resource to the last frequency resource for the determined time resource.

[0425] The above ID is a device ID or a random number.

[0426] If the response to Msg1 transmitted by the device is included in Msg2, the device transmits Msg3 using the Msg3 resource mapped to its ID.

[0427] Opt 4: The order of the ID list in Msg0 or Msg2

[0428] Option 4-1: If one or more IDs are indicated as Msg0 or Msg2, the indicated ID(s) are sorted in ascending or descending order according to their ID values ​​(e.g., ID#1, ID#2, ID#3, ID#4), and the IDs can be mapped to the msg3 resource according to Alt 1 or Alt 2 below. For example, the IDs can be mapped to the Msg3 resource in frequency priority from the first ID to the last ID as in Alt 1 below. For example, the IDs can be mapped to the Msg3 resource in sequence in time priority from the first ID to the last ID as in Alt 2 below.

[0429] Option 4-2: When one or more IDs are indicated as Msg0 or Msg2, based on the order of indication of ID(s) within Msg0 or Msg2 (e.g., ID#1, ID#2, ID#3, ID#4), map the Msg3 resources to the IDs in frequency priority from the first ID to the last ID as shown in Alt 1 below, or map the Msg3 resources to the IDs in sequence in time priority as shown in Alt 2.

[0430] FIG. 16 shows examples of mapping between MSG3 resources and IDs according to embodiments of the present specification.

[0431] Alt 1: Frequency Priority Mapping

[0432] Figures 16 (a) and (b) illustrate frequency-first mapping.

[0433] Referring to Fig. 16(a), in the frequency priority case, IDs are first mapped to all frequency resources in the first time resource, and then moved to all frequency resources in the next time resource and mapped to IDs. This type of mapping is performed up to all frequency resources in the last time resource.

[0434] FIG. 17 illustrates other examples of mapping between MSG3 resources and IDs according to embodiments of the present specification.

[0435] Alt 2: Time-first mapping

[0436] Figures 17 (a) and (b) illustrate time-first mapping.

[0437] Referring to Fig. 17(a), in the time-first case, IDs are first mapped to all time resources on the first frequency resource, and then moved to all time resources on the next frequency resource and mapped to IDs. This type of mapping is performed up to all time resources on the last frequency resource.

[0438] The above ID is a device ID or a random number.

[0439] If the response to Msg1 transmitted by the device is included in Msg2, the device transmits Msg3 using the Msg3 resource mapped to its ID.

[0440] If Msg1 or Msg3 is transmitted as per the above option, an action according to the following example may be performed.

[0441] For example, if the total number of Msg1 transmission resources and the total number of Msg3 transmission resources are the same for the same Msg0, the device determines and transmits the Msg3 resources as per the above option.

[0442] For example, if the total number of Msg3 transmission resources is greater than the total number of Msg1 transmission resources for the same Msg0, the device determines and transmits the Msg3 resources as per the above option. In this case, the reader and the device do not perform Msg3 transmission or reception with Msg3 resources that are not mapped to Msg1 resources.

[0443] For example, if the total number of Msg3 transmission resources is smaller than the total number of Msg1 transmission resources for the same Msg0, the device determines and transmits the Msg3 resources as per the above option. In this case, the device that transmitted Msg1 to a Msg1 resource not mapped to a Msg3 resource performs one of the following actions.

[0444] Alt 1: The device monitors the next Msg2 transmission within the current or next Msg2 monitoring cycle.

[0445] Based on the following Msg2, a Msg3 frequency resource identical to the frequency resource of Msg1 transmitted by the device may be allocated, or a different Msg3 frequency resource may be allocated.

[0446] At this time, excluding the Msg1 resource(s) mapped to the Msg3 resource(s) according to the previous Msg2 transmission, the remaining unmapped Msg1 resource(s) are mapped to the Msg3 resource(s) allocated according to the next Msg2 transmission.

[0447] Alt 2: The device sends Msg1 again.

[0448] Alt 3: The device (stops the random access process) and monitors and receives Msg0 again.

[0449] Meanwhile, based on the L1 / L2 control information of Msg0 or Msg2, information that is commonly applied to each time resource (e.g., information related to at least one of D2R transmission chip duration, data rate (or bit duration) or coding rate) may be indicated.

[0450] Specifically, the reader may indicate information regarding a common D2R transmission data rate (or bit duration) and / or coding rate for all frequency resources transmitted to the same time resource through the L1 / L2 control information of Msg0 or Msg2. For example, based on Msg0, at least one of information regarding a common D2R chip duration, information regarding a data rate (or bit duration), and / or coding rate (e.g., information regarding channel coding) may be indicated for each of the Msg1 transmissions (D2R transmissions) based on all frequency resources (in the same time resource). For example, based on Msg2, at least one of information regarding a common D2R chip duration, information regarding a data rate (or bit duration), and / or coding rate (e.g., information regarding channel coding) may be indicated for each of the Msg3 transmissions (D2R transmissions) based on all frequency resources (in the same time resource).

[0451] When the device transmits Msg1 or Msg3 to a specific time resource according to the above option, the device transmits Msg1 or Msg3 based on information related to the chip duration, data rate (or bit duration) and / or coding rate indicated for the specific time resource.

[0452] At this time, the reader can instruct different D2R transmission data rates or coding rates for different time resources through the L1 / L2 control information of Msg0 or Msg2. For example, in FIG. 15 (a), the first time resources 1 and 2 and the second time resources 3 and 4 can be instructed with different chip durations, data rates, or coding rates.

[0453] Meanwhile, different time resources in the above options may be allocated contiguously or discontinuously. For example, as in FIG. 15 (a), a case may be assumed where Msg3 resources X=2, Y=2 are allocated. The first time resource location of Msg3 resource index 1 and Msg3 resource 2 for the same time resource may be contiguous or discontinuous with the second time resource location of Msg3 resource index 3 and Msg3 resource index 4.

[0454] When a msg3 resource based on a first time resource location and a msg3 resource based on a second time resource location are allocated discontinuously in the time domain, the following embodiments may be considered.

[0455] For example, the interval between the first and second time resources can be indicated based on Msg0 or Msg2 transmitted before the first time resource.

[0456] For example, a second Msg2 may be transmitted between the first and second time resources, and based on the second Msg2, the location of the second time resource (for example, the start time and time interval) may be indicated.

[0457] Control information and PRDCH or PDRCH transmission structure

[0458] FIG. 18 illustrates the Control information and PRDCH or PDRCH transmission structure options of the present specification. In FIG. 18, 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. 18 includes a preamble and a postamble, it may be transmitted as in FIG. 19.

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

[0460] 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 shown in FIG. 19, or as a specific sequence consisting of high and low voltages.

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

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

[0463] Alt 1

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

[0465] For example, L1 control info may be added immediately after the clock acquisition part of FIG. 19, 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. 18. In the case of option b, PRDCH starts with L2 control info.

[0466] Alt 2

[0467] 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. 18.

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

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

[0470] Alt 3

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

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

[0473] FIG. 20 illustrates an example of the structure of the MAC payload of FIG. 18 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. 18 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. 21 may include the L2 control info. Additionally, padding may be added to the last part of the payload of FIG. 21. When a payload (i.e., TB) is configured at the MAC layer of a device / reader as shown in FIG. 21, 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. 21, L2 control information can also be classified as a specific MAC CE that is always located before the payload or as a MAC header.

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

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

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

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

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

[0479] 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. 24 (e.g., the processor (110, 210) of FIG. 24).

[0480] 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. 24) in the form of instructions / programs (e.g., instruction, executable code) for driving at least one processor (e.g., 110, 210 of FIG. 24).

[0481] The embodiments described above will be explained in detail below with reference to FIGS. 22 and 23 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.

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

[0483] Referring to FIG. 22, a method according to one embodiment of the present specification includes a first R2D message receiving step (S2210), a first D2R message transmission step (S2220), a second R2D message receiving step (S2230), and a second D2R message transmission step (S2240).

[0484] In S2210, the device receives a first R2D (Reader to Device) message from the reader. For example, the first R2D message may be msg0 (e.g., an A-IoT Paging message).

[0485] For example, based on the first R2D message, the number of time resources X and the number of frequency resources Y may be indicated. X*Y resources may be associated with the transmission of one or more first D2R (Device to Reader) messages.

[0486] In S2220, the device transmits a first D2R message to the reader based on a selected resource among the X*Y resources. More specifically, the device selects a resource among the X*Y resources for transmitting the first D2R message. The device transmits the first D2R message based on the selected resource. For example, the first D2R message may be msg1 (e.g., Access Random ID message).

[0487] In S2230, the device receives a second R2D message from the reader. For example, based on the second R2D message, one or more values ​​related to a frequency resource indication (e.g., N SFS The R SFS ( ) is indicated. The above one or more values ​​may be associated with the transmission of one or more second D2R messages.

[0488] In S2240, the device transmits a second D2R message to the reader based on the i-th value among the one or more values. For example, the second D2R message may be msg3 (e.g., D2R Upper Layer Data Transfer message).

[0489] According to one embodiment, the first D2R message may include a first ID based on a random number (e.g., a Random ID field). The second R2D message may include one or more second IDs (e.g., one or more Echoed Random ID fields). The i-th value may be determined based on the order of the second IDs associated with the first ID among the one or more second IDs. This embodiment may be based on Opt 4 (Option 4-2) in the MSG1-based Msg3 resource determination scheme. As a specific example, the value of the second ID may be identical to the value of the first ID.

[0490] According to one embodiment, a first repetition number commonly used for a first D2R transmission associated with each of the one or more first D2R messages may be indicated based on the first R2D message. A second repetition number commonly used for a second D2R transmission associated with each of the one or more second D2R messages may be indicated based on the second R2D message. This embodiment may be based on Method #1. For example, the first repetition number may mean a repetition number indicated for MSG1 associated with the device(s) or device group described above. For example, the second repetition number may mean a repetition number indicated for MSG3 associated with the device(s) or device group described above.

[0491] For example, based on the fact that the first number of repetitions is 1, the first D2R transmission can be performed without repetition.

[0492] For example, based on the fact that the second repetition count is 1, the second D2R transmission can be performed without repetition.

[0493] For example, the second number of repetitions may be different from the first number of repetitions. As a specific example, the second number of repetitions may be based on a value proportional to the first number of repetitions.

[0494] According to one embodiment, the second D2R transmission based on each of the one or more values ​​may be performed based on the same time resource. This embodiment may be based on an embodiment related to FIG. 16(b). Performing the second D2R transmission based on the same time resource may mean that the second D2R transmission starts at the same timing. Specifically, the second D2R transmission based on each of the one or more values ​​may be performed (or started) based on the same timing.

[0495] According to an embodiment related to information commonly applied to each time resource described above, parameters / information for a second D2R transmission based on the same time resource (same timing) (e.g., at least one of channel coding, data rate (=1 / bit duration), and / or chip duration) may be common. This will be explained in detail below.

[0496] For example, the duration of the D2R bit associated with the second D2R transmission may be the same.

[0497] As a specific example, based on the second R2D message, information related to the duration of the D2R bit commonly used for the second D2R transmission may be indicated.

[0498] For example, the chip duration associated with the second D2R transmission may be the same.

[0499] According to one embodiment, the D2R Transport Block Size (TBS) may be indicated based on the second R2D message. This embodiment may be based on Method #2.

[0500] For example, the second D2R message may be generated based on the segmentation of the data, based on the fact that the size associated with the data to be transmitted is larger than the D2R TBS. As a specific example, the second D2R message may include a segment of the data. i) based on the fact that the segment is the last segment of the data, and ii) based on the fact that the size associated with the segment is smaller than the D2R TBS: the second D2R message may include padding.

[0501] For example, based on the fact that the size associated with the data to be transmitted is smaller than or equal to the D2R TBS, the second D2R message may be generated without the segmentation of the data. As a specific example, based on the fact that the size associated with the data to be transmitted is smaller than the D2R TBS, the second D2R message may include padding.

[0502] According to one embodiment, first channel coding information commonly used for the first D2R transmission may be indicated based on the first R2D message. Second channel coding information commonly used for the second D2R transmission may be indicated based on the second R2D message. This embodiment may be based on Method #1. This embodiment is intended to unify whether channel coding is used (e.g., channel coding used or channel coding omitted) for D2R transmissions associated with D2R message(s) having common characteristics (e.g., first D2R message(s) or second D2R message(s)).

[0503] For example, based on the first channel coding information above, whether or not to use channel coding related to the first D2R transmission can be determined / instructed.

[0504] For example, based on the second channel coding information above, whether or not to use channel coding related to the second D2R transmission can be determined / instructed.

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

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

[0507] S2310 to S2340 described below correspond to S2210 to S2240 described in FIG. 22. Considering the above correspondence, redundant descriptions are omitted. That is, the specific description of the operation of the reader described below can be replaced by the description / execution of FIG. 22 corresponding to the operation.

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

[0509] Referring to FIG. 23, a method according to another embodiment of the present specification includes a first R2D message transmission step (S2310), a first D2R message reception step (S2320), a second R2D message transmission step (S2330), and a second D2R message reception step (S2340).

[0510] In S2310, the reader transmits a first R2D (Reader to Device) message to the device. For example, based on the first R2D message, the number of time resources X and the number of frequency resources Y may be indicated. X*Y resources may be associated with the transmission of one or more first D2R (Device to Reader) messages.

[0511] In S2320, the reader receives a first D2R message from the device based on a resource selected from among the X*Y resources.

[0512] In S2330, the reader transmits a second R2D message to the device. For example, one or more values ​​related to frequency resource indications are indicated based on the second R2D message. The one or more values ​​may be associated with the transmission of one or more second D2R messages.

[0513] In S2340, the reader receives a second D2R message from the device based on the i-th value among the one or more values.

[0514] According to one embodiment, the first D2R message may include a first ID based on a random number (e.g., a Random ID field). The second R2D message may include one or more second IDs (e.g., one or more Echoed Random ID fields). The i-th value may be determined based on the order of the second IDs associated with the first ID among the one or more second IDs.

[0515] According to one embodiment, a first repetition number commonly used for a first D2R transmission associated with each of the one or more first D2R messages may be indicated based on the first R2D message. A second repetition number commonly used for a second D2R transmission associated with each of the one or more second D2R messages may be indicated based on the second R2D message.

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

[0517] 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. 24.

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

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

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

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

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

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

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

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

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

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

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

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

[0530] 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 R2D (Reader to Device) message from a reader by a device, wherein the number of time resources X and the number of frequency resources Y are indicated based on the first R2D message, and X*Y resources are associated with the transmission of one or more first D2R (Device to Reader) messages; A step of transmitting a first D2R message to the reader by the device based on a resource selected from among the X*Y resources; The step of receiving a second R2D message from the reader by the device, wherein one or more values ​​related to frequency resource indication are indicated based on the second R2D message, and the one or more values ​​are related to the transmission of one or more second D2R messages; and The method includes the step of transmitting a second D2R message to the reader by the device based on the i-th value among the one or more values, The above first D2R message includes a first ID based on a random number, and The above second R2D message includes one or more second IDs, and The above i-th value is determined based on the order of the second IDs associated with the first ID among the above one or more second IDs, and Based on the above first R2D message, a first repetition number commonly used for the first D2R transmission associated with each of the one or more first D2R messages is indicated, and A method characterized by indicating a second repetition number commonly used for second D2R transmissions associated with each of the one or more second D2R messages based on the second R2D message.

2. In Paragraph 1, A method characterized in that the first D2R transmission is performed without repetition based on the fact that the first number of repetitions is 1.

3. In Paragraph 1, A method characterized in that the second D2R transmission is performed without repetition based on the fact that the second repetition count is 1.

4. In Paragraph 1, A method characterized in that the second number of repetitions is different from the first number of repetitions.

5. In Paragraph 4, A method characterized in that the second number of repetitions is based on a value proportional to the first number of repetitions.

6. In Paragraph 1, A method characterized in that the second D2R transmission based on each of the above one or more values ​​is performed based on the same timing.

7. In Paragraph 1, A method characterized by indicating the D2R Transport Block Size (TBS) based on the second R2D message.

8. In Paragraph 7, Based on the fact that the size of the data to be transmitted is larger than the above D2R TBS, A method characterized in that the second D2R message is generated based on the segmentation of the data.

9. In Paragraph 8, The above second D2R message includes a segment of the data, and i) based on the fact that the above segment is the last segment of the data, and ii) based on the fact that the size associated with the above segment is smaller than the D2R TBS: A method characterized in that the above second D2R message includes padding.

10. In Paragraph 8, A method characterized in that, based on the fact that the size associated with the data to be transmitted is smaller than or equal to the D2R TBS, the second D2R message is generated without the segmentation of the data.

11. In Paragraph 10, A method characterized in that the second D2R message includes padding, based on the fact that the size associated with the data to be transmitted is smaller than the D2R TBS.

12. In Paragraph 1, Based on the above first R2D message, first channel coding information commonly used for the above first D2R transmission is indicated, and A method characterized by indicating second channel coding information commonly used for the 2 D2R transmission based on the second R2D message.

13. In Paragraph 12, A method characterized by determining whether to use channel coding related to the first D2R transmission based on the first channel coding information.

14. In Paragraph 12, A method characterized by determining whether to use channel coding related to the second D2R transmission based on the second channel coding information.

15. 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 14, based on execution by the one or more processors.

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

17. 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 the device to perform all steps of the method according to any one of claims 1 to 14.

18. Regarding the method, A step of transmitting a first R2D (Reader to Device) message to a device by a reader, wherein the number of time resources X and the number of frequency resources Y are indicated based on the first R2D message, and X*Y resources are associated with the transmission of one or more first D2R (Device to Reader) messages; A step of receiving a first D2R message from the device by the reader based on a resource selected from among the X*Y resources; The step of transmitting a second R2D message to the device by the reader, wherein one or more values ​​related to frequency resource indication are indicated based on the second R2D message, and the one or more values ​​are related to the transmission of one or more second D2R messages; and The method includes the step of receiving a second D2R message from the device by the reader based on the i-th value among the one or more values, The above first D2R message includes a first ID based on a random number, and The above second R2D message includes one or more second IDs, and The above i-th value is determined based on the order of the second IDs associated with the first ID among the above one or more second IDs, and Based on the above first R2D message, a first repetition number commonly used for the first D2R transmission associated with each of the one or more first D2R messages is indicated, and A method characterized by indicating a second repetition number commonly used for second D2R transmissions associated with each of the one or more second D2R messages based on the second R2D message.

19. 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 18.

Images