Method and device for performing internet of things-based communication in wireless communication system

The method addresses control information configuration in 6G IoT communication by enabling efficient D2R transmissions, enhancing data exchange and connectivity in 6G systems.

WO2026075527A1PCT designated stage Publication Date: 2026-04-09LG ELECTRONICS INC

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-10-02
Publication Date
2026-04-09

Smart Images

  • Figure KR2025015828_09042026_PF_FP_ABST
    Figure KR2025015828_09042026_PF_FP_ABST
Patent Text Reader

Abstract

A method and a device for performing Internet of things (IoT)-based communication in a wireless communication system are disclosed. The method according to one embodiment of the present disclosure may comprise steps in which a first device: identifies a second device; and performs device-to-reader (D2R) transmission for the second device. Here, at least one from among sequence information about an amble signal related to the D2R transmission, timing information about the R2D transmission to be received subsequent to the D2R transmission, and frequency information about the R2D transmission can be indicated on the basis of the D2R transmission.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for performing IoT-based communication in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more specifically, to a method and apparatus for performing Internet of Things (IoT)-based communication in a wireless communication system.

[0002] The 5th generation (5G) wireless communication system is a successor technology to 4G LTE (long term evolution) and is a new clean-slate type mobile communication system with characteristics such as high performance, low latency, and high availability. In the case of 5G NR (New Radio), 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 (or millimeter wave) bands above 24 GHz. Based on the foundational technology of 5G wireless communication, 6G wireless communication systems are being developed.

[0003] 6G wireless communication systems are being developed with the goal of (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 6G systems can be seen in four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity. Various technologies are being researched in consideration of the requirements for 6G systems, such as a peak data rate of 1 Tbps per device, an end-to-end (E2E) latency of 1ms, a maximum spectrum efficiency of 100 bps / Hz, support for mobility of 1000 km / h, satellite integration, artificial intelligence (AI), autonomous vehicles, extended reality (XR), and haptic communication.

[0004] The technical problem of the present disclosure is to a method and apparatus for performing Internet of Things (IoT)-based communication in a wireless communication system.

[0005] The technical problem of the present disclosure is to a method and apparatus for defining and configuring control information related to transmission and reception in ambient IoT communication.

[0006] The technical problem of the present disclosure is to a method and apparatus for directing the configuration of an x-amble through control information related to transmission and reception in ambient IoT communication.

[0007] The technical problems to be solved in this disclosure 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 disclosure belongs from the description below.

[0008] A method according to one embodiment of the present disclosure may include: identifying a second device by a first device; and performing a device-to-reader (D2R) transmission to the second device by the first device. Herein, at least one of sequence information of an amble signal associated with the D2R transmission, timing information of an R2D transmission to be received following the D2R transmission, or frequency information of the R2D transmission may be indicated based on the D2R transmission.

[0009] A method according to another embodiment of the present disclosure may include the step of receiving a device-to-reader (D2R) transmission from a first device to the second device by a second device; and the step of performing an R2D transmission to the first device following the D2R transmission by the second device. Herein, at least one of sequence information of an amble signal associated with the D2R transmission, timing information of the R2D transmission, or frequency information of the R2D transmission may be indicated based on the D2R transmission.

[0010] By various embodiments of the present disclosure, a method and apparatus for performing Internet of Things (IoT)-based communication in a wireless communication system may be provided.

[0011] By various embodiments of the present disclosure, a method and apparatus for defining and configuring control information related to transmission and reception in ambient IoT communication may be provided.

[0012] By various embodiments of the present disclosure, a method and apparatus for directing the configuration of an x-amble through control information related to transmission and reception in ambient IoT communication may be provided.

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

[0014] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and explain the technical features of the present disclosure together with the detailed description.

[0015] FIG. 1 illustrates an exemplary flexible network topology to which some examples of the present disclosure may be applied.

[0016] FIG. 2 illustrates an exemplary communication system to which some examples of the present disclosure may be applied.

[0017] FIG. 3 illustrates an exemplary wireless device to which some examples of the present disclosure may be applied.

[0018] FIG. 4 illustrates an exemplary communication procedure between a first node and a second node to which some examples of the present disclosure may be applied.

[0019] FIG. 5 illustrates an exemplary functional framework for AI operations to which some examples of the present disclosure may be applied.

[0020] FIG. 6 illustrates an example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

[0021] FIG. 7 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

[0022] FIG. 8 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

[0023] FIG. 9 shows an electromagnetic spectrum to which some examples of the present disclosure may be applied.

[0024] FIG. 10 illustrates an exemplary system information transmission / reception procedure to which some examples of the present disclosure may be applied.

[0025] FIG. 11 illustrates an exemplary beam management procedure to which some examples of the present disclosure may be applied.

[0026] FIG. 12 shows an example of an NTN scenario to which some examples of the present disclosure may be applied.

[0027] FIG. 13 shows another example of an NTN scenario to which some examples of the present disclosure may be applied.

[0028] FIG. 14 shows examples of sensing operations to which some examples of the present disclosure may be applied.

[0029] FIG. 15 illustrates topologies that can be supported in ambient IoT communication to which some examples of the present disclosure may be applied.

[0030] FIG. 16 shows a specific example of a topology supported in ambient IoT communication to which some examples of the present disclosure may be applied.

[0031] FIG. 17 illustrates a PRDCH generation method and a PDRCH generation method to which some examples of the present disclosure may be applied.

[0032] Figure 18 is a flowchart illustrating the procedure for an ambient IoT device to connect to a reader device.

[0033] FIG. 19 illustrates a control information and PRDCH / PDRCH transmission structure to which some examples of the present disclosure may be applied.

[0034] FIG. 20 illustrates a preamble / postamble and PRDCH / PDRCH transmission to which some examples of the present disclosure may be applied.

[0035] FIG. 21 illustrates a MAC payload structure in PRDCH / PDRCH to which some examples of the present disclosure may be applied.

[0036] FIG. 22 illustrates the repeated transmission of PDRCH according to one embodiment of the present disclosure.

[0037] FIG. 23 illustrates the operation of a first device according to an embodiment of the present disclosure.

[0038] FIG. 24 illustrates the operation of a second device according to an embodiment of the present disclosure.

[0039] FIG. 25 is a block diagram illustrating the configuration of device 1 according to one embodiment of the present disclosure.

[0040] FIG. 26 is a block diagram illustrating the configuration of device 2a according to one embodiment of the present disclosure.

[0041] FIG. 27 is a block diagram illustrating the configuration of device 2b according to one embodiment of the present disclosure.

[0042] Hereinafter, preferred embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to describe exemplary embodiments of the present disclosure and is not intended to represent the only embodiment in which the present disclosure may be practiced. The following detailed description includes specific details to provide a complete understanding of the present disclosure. However, those skilled in the art will know that the present disclosure may be practiced without such specific details.

[0043] In some cases, to avoid obscuring the concept of the present disclosure, known structures and devices may be omitted or illustrated in the form of a block diagram focusing on the core functions of each structure and device.

[0044] In the present disclosure, when a component is described as being “connected,” “combined,” or “joined” with another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, in the present disclosure, the terms “comprising” or “having” specify the presence of the mentioned features, steps, actions, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, actions, elements, components, and / or groups thereof.

[0045] In the present disclosure, terms such as "first," "second," etc. are used solely for the purpose of distinguishing one component from another and are not used to limit the components, nor do they limit the order or importance of the components unless specifically stated otherwise. Accordingly, within the scope of the present disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and likewise, a second component in one embodiment may be referred to as a first component in another embodiment.

[0046] The terms used in this disclosure are for the description of specific embodiments and are not intended to limit the claims. As used in the description of embodiments and the appended claims, the singular form is intended to include the plural form unless the context clearly indicates otherwise.

[0047] In the present disclosure, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in the present disclosure, "A or B" may be interpreted as "A and / or B." For example, in the present disclosure, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0048] A slash ( / ) or a comma used in the present disclosure 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."

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

[0050] Additionally, in the present disclosure, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Additionally, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

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

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

[0053] Technical features described individually within one drawing in this disclosure may be implemented individually or simultaneously.

[0054] In the present disclosure, a terminal or user equipment (UE) may be a portable device and may be a first node that receives a signal from a base station / second node / integrated access backhaul (IAB) node.

[0055] In the present disclosure, the base station (BS, Base Station) may be a second node / IAB node / Transmission-Reception Point (TRP).

[0056] In the present disclosure, a higher layer parameter may be a parameter configured, pre-configured, or pre-defined for a terminal. For example, a base station or 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.

[0057] In the present disclosure, "set or defined" may be interpreted as being set to a device through predefined signaling (e.g., System Information Block (SIB), MAC, RRC) from a base station or network. In the present disclosure, "set or defined" may be interpreted as being set to a device through separate signaling or being predefined without separate signaling.

[0058] In the present disclosure, transmitting or receiving a channel includes the meaning of transmitting or receiving information or a signal through said channel. For example, transmitting a control channel means transmitting control information or a signal through the control channel. Similarly, transmitting a data channel means transmitting data information or a signal through the data channel.

[0059] The technology described in this disclosure can be used in various wireless communication systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications), GPRS (general packet radio service), and EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (institute of electrical and electronics engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), LTE (long term evolution), and 5G NR.

[0060] The technology described in this disclosure can be implemented as 6G wireless technology and applied to various 6G systems. For example, 6G systems may have key factors such as eMBB (enhanced mobile broadband), URLLC (ultra-reliable low latency communications), mMTC (massive machine-type communication), AI (artificial intelligence) integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.

[0061] Network structure

[0062] FIG. 1 illustrates an exemplary flexible network topology to which some examples of the present disclosure may be applied.

[0063] To compensate for incomplete areas of network coverage, a network topology in which the split radio access network (RAN) is configured more flexibly and resiliently may be considered. To this end, various nodes such as integrated access backhaul (IAB) nodes, relays, and radio frequency (RF) repeaters, as exemplified in Fig. 1, may be applied, and a non-terrestrial network (NTN) may be integrated. For example, an IAB node may correspond to a node that provides wireless backhaul. For example, a relay may refer to any intermediate point, and in the case of a sidelink relay where a terminal functions as a relay, it may collectively refer to a terminal-to-network (U2N) relay and a terminal-to-terminal (U2U) relay. For example, an RF repeater may correspond to a node that performs simple signal amplification and forwarding functions, and in the case of a network-controlled repeater, it may adjust transmit / receive settings based on information provided by the network as well as signal amplification and forwarding. For example, NTN nodes can correspond to satellites or aircraft that provide NTN coverage that is difficult for terrestrial networks to provide. In addition to these examples, various intermediate points can be introduced to improve the network topology.

[0064] Referring to FIG. 1, a split RAN can support the division of a base station into one centralized unit (CU) and one or more distributed units (DU). The CU and DU may correspond to logical units. The CU may be further divided into a control plane (CP) portion and one or more user plane (UP) portions. Since a failure in the CU-CP affects not only the CU-UP but also the DU, various intermediate points may be introduced to compensate for this.

[0065] An intermediate point may correspond to a terminal or a base station depending on its relative relationship with other nodes. For example, an IAB node may include a mobile-termination (MT) portion and a DU. The MT may connect the IAB node to a donor node. The DU of the IAB node may serve other terminals or connect to other IAB nodes to provide multi-hop wireless backhaul to terminals. For example, an IAB node may correspond to a base station in its relative relationship with a user-side node and to a terminal in its relative relationship with a network-side node.

[0066] In some examples of the present disclosure, the description of a terminal may apply equally to an intermediate point corresponding to a terminal in relation to a network-side endpoint as well as to a user-side endpoint. Similarly, in some examples of the present disclosure, the description of a base station may apply equally to an intermediate point corresponding to a base station in relation to a user-side endpoint as well as to a network-side endpoint. In most cases where there is no additional description of the operation of three or more subjects, the communication subjects in the present disclosure are briefly described by the term terminal and / or base station (or first node and / or second node), wherein the term terminal and / or base station (or first node and / or second node) is interpreted to include or replace any endpoint or any intermediate point in relation to other nodes.

[0067] As such, in some examples of the present disclosure, for the sake of brevity of description, the subject of the operation may be referred to as a terminal and / or base station (or a first node and / or a second node). Additionally, the term terminal and / or base station (or a first node and / or a second node) may be interpreted or substituted as in the following examples: for example, the terminal (or first node) and the base station (or second node) may correspond to a first endpoint and a second endpoint, respectively; may correspond to an endpoint and an intermediate point, respectively; may correspond to an intermediate point and an endpoint, respectively; or may correspond to a first intermediate point and a second intermediate point, respectively.

[0068] In the present disclosure, there may be no intermediate points between the base station and the terminal, or there may be one or more. If intermediate points exist, the intermediate points may correspond to IAB nodes, relays, RF repeaters, NTN nodes, or nodes supporting other functions. The intermediate points may be nodes with a fixed location or nodes with an indefinite location.

[0069] Systems applicable to the present disclosure

[0070] FIG. 2 illustrates an exemplary communication system to which some examples of the present disclosure may be applied.

[0071] The communication system (100) to which the present disclosure applies includes a wireless device (110), a network device (120), and a network (130). Here, the wireless device (110) refers to a device that performs communication using wireless access technology (e.g., LTE, LTE-A, LTE-A pro, NR, 5G, 5G-A, 6G) and may be referred to as a communication / wireless / 5G / 6G device. Although not limited thereto, the wireless device (110) may include a robot (110a), a vehicle (110b-1, 110b-2), an XR (extended reality) device (110c), a hand-held device (110d), a home appliance (110e), an IoT (Internet of Thing) device (110f), and an AI (artificial intelligence) device / server (110g). For example, the vehicle may include a vehicle equipped with wireless communication capabilities, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, etc. Here, the vehicle (110b-1, 110b-2) may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device (110c) includes an augmented reality (AR) / virtual reality (VR) / mixed reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. The portable device (110d) may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), a computer (e.g., a laptop, etc.). The home appliance (110e) may include a TV, a refrigerator, a washing machine, etc. The IoT device (110f) may include a sensor, a smart meter, etc. The wireless device (110) may correspond to a terminal (or first node) or an intermediate point.The network device (120) may correspond to a base station (or a second node) or another intermediate point. For example, the network device (120) may also be implemented as a wireless device (110), and a specific wireless device (120a) may operate as a network device (120) to another wireless device (110).

[0072] Wireless devices (110a to 110f) can be connected to a network (130) through a network device (120). AI technology may be applied to the wireless devices (110a to 110f), and the wireless devices (110a to 110f) can be connected to an AI server (110g) through the network (130). The network (130) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, or a 6G network. The wireless devices (110a to 110f) may communicate with each other through the network device (120) / network (130), but may also communicate directly (e.g., sidelink communication) without going through the network device (120) / network (130). For example, vehicles (110b-1, 110b-2) can communicate directly (e.g., V2V (vehicle to vehicle) / V2X (vehicle to everything) communication). Also, an IoT device (110f) (e.g., a sensor) can communicate directly with another IoT device (e.g., a sensor) or other wireless devices (110a to 110f).

[0073] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (110a to 110f) / network devices (120) and between network devices (120). Here, wireless communication / connection can be established through various wireless access technologies such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and communication between network devices (150c) (e.g., relay, IAB (integrated access backhaul)). Through wireless communication / connection (150a, 150b, 150c), wireless devices and network devices / wireless devices, and network devices and network devices can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on the various descriptions of the present disclosure, at least some of the following may be performed: a process for setting various configuration information for transmitting / receiving wireless signals, a process for various signal processing (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), a resource allocation process, etc.

[0074] Devices applicable to the present disclosure

[0075] FIG. 3 illustrates an exemplary wireless device to which some examples of the present disclosure may be applied.

[0076] Referring to FIG. 3, the wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, LTE-A, LTE-A pro, NR, 5G, 5G-A, 6G). The wireless device (200) includes at least one processor (202) and at least one memory (204), and may additionally include at least one transceiver (206) and / or at least one antenna (208).

[0077] The processor (202) controls the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document. For example, the processor (202) may process information within the memory (204) to generate a first information / signal and then transmit a wireless signal containing the first information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a second information / signal through the transceiver (206) and then store information obtained from the signal processing of the second information / signal in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, memory (204) may store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the descriptions, functions, procedures, proposals, methods, and / or sequences of operations disclosed in this document. Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology. A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through at least one antenna (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeable with a radio frequency (RF) unit. In this disclosure, a wireless device may mean a communication modem / circuit / chip.

[0078] Hereinafter, hardware elements of the wireless device (200) will be described in more detail. Although not limited thereto, at least one protocol layer may be implemented by at least one processor (202). For example, at least one processor (202) may implement at least one layer (e.g., functional layers such as PHY (physical), MAC (media access control), RLC (radio link control), PDCP (packet data convergence protocol), RRC (radio resource control), and SDAP (service data adaptation protocol). At least one processor (202) may generate at least one PDU (Protocol Data Unit) and / or at least one SDU (service data unit) according to the descriptions, functions, procedures, proposals, methods and / or operation sequences disclosed in this document. At least one processor (202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods and / or operation sequences disclosed in this document. At least one processor (202) may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document and provide it to at least one transceiver (206). At least one processor (202) may receive a signal (e.g., a baseband signal) from at least one transceiver (206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document.

[0079] At least one processor (202) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. At least one processor (202) may be implemented by hardware, firmware, software, or a combination thereof. For example, at least one application-specific integrated circuit (ASIC), at least one digital signal processor (DSP), at least one digital signal processing device (DSPD), at least one programmable logic device (PLD), or at least one field programmable gate array (FPGA) may be included in at least one processor (202). The descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be included in at least one processor (202) or stored in at least one memory (204) and driven by at least one processor (202). The descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this document may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.

[0080] At least one memory (204) may be connected to at least one processor (202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. At least one memory (204) may be composed of ROM (read-only memory), RAM (random access memory), EPROM (erasable programmable read-only memory), flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. At least one memory (204) may be located inside and / or outside of at least one processor (202). Additionally, at least one memory (204) may be connected to at least one processor (202) via various technologies, such as wired or wireless connections.

[0081] At least one transceiver (206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc. of this document to at least one other device. At least one transceiver (206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc. disclosed in this document from at least one other device. For example, at least one transceiver (206) may be connected to at least one processor (202) and may transmit and receive wireless signals. For example, at least one processor (202) may control at least one transceiver (206) to transmit user data, control information, or wireless signals to at least one other device. Additionally, at least one processor (202) may control at least one transceiver (206) to receive user data, control information, or wireless signals from at least one other device. Additionally, at least one transceiver (206) may be connected to at least one antenna (208), and at least one transceiver (206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in this document through at least one antenna (208). In this document, at least one antenna may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). At least one transceiver (206) may convert the received wireless signals / channels, etc., from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc., using at least one processor (202).At least one transceiver (206) can convert user data, control information, wireless signals / channels, etc. processed using at least one processor (202) from a baseband signal to an RF band signal. To this end, at least one transceiver (206) may include an (analog) oscillator and / or filter.

[0082] The components of the wireless device described with reference to FIG. 3 may be referred to by other terms in terms of their function. For example, the processor (202) may be referred to as the control unit, the transceiver (206) as the communication unit, and the memory (204) as the storage unit. In some cases, the communication unit may be used to mean at least a part of the processor (202) and the transceiver (206).

[0083] The structure of the wireless device described with reference to FIG. 3 can be understood as the structure of at least part of various devices. For example, the structure of the wireless device illustrated in FIG. 3 may be at least part of the various devices described with reference to FIG. 2 (e.g., robot (110a), vehicle (110b-1, 110b-2), XR device (110c), portable device (110d), home appliance (110e), IoT device (110f), AI device / server (110g)). Furthermore, according to various embodiments, the device may include other components in addition to the components illustrated in FIG. 3.

[0084] For example, the device may be a portable device such as a smartphone, smartpad, wearable device (e.g., smart watch, smart glasses), or portable computer (e.g., laptop, etc.). In this case, the device may further include at least one of a power supply unit that supplies power and includes a wired / wireless charging circuit, a battery, etc., an interface unit that includes at least one port for connection with another device (e.g., an audio input / output port, a video input / output port), and an input / output unit for inputting and outputting video information / signals, audio information / signals, data, and / or information input by a user.

[0085] For example, the device may be a mobile device such as a mobile robot, vehicle, train, manned / unmanned aerial vehicle (AV), or ship. In this case, the device may further include at least one of a drive unit comprising at least one of an engine, motor, power train, wheel, brake, and steering device of the device; a power supply unit that supplies power and includes a wired / wireless charging circuit, battery, etc.; a sensor unit that senses state information, environmental information, and user information of the device or its surroundings; an autonomous driving unit that performs functions such as path maintenance, speed control, and destination setting; and a position measurement unit that acquires position information of the moving body through a GPS (global positioning system) and various sensors.

[0086] For example, the device may be an XR device such as an HMD, a HUD (head-up display) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. In this case, the device may further include at least one of a power supply unit that supplies power and includes a wired / wireless charging circuit, a battery, etc., an input / output unit that acquires control information, data, etc. from the outside and outputs a generated XR object, and a sensor unit that senses state information, environment information, and user information of the device or the surroundings of the device.

[0087] For example, the device may be a robot that can be classified into industrial, medical, household, military, etc., depending on the purpose or field of use. In this case, the device may further include at least one of a sensor unit that senses state information, environmental information, and user information of the device or its surroundings, and a drive unit that performs various physical actions, such as moving robot joints.

[0088] For example, the device may be an AI device such as a TV, projector, smartphone, PC, laptop, digital broadcasting terminal, tablet PC, wearable device, set-top box (STB), radio, washing machine, refrigerator, digital signage, robot, vehicle, etc. In this case, the device may further include at least one of an input unit that acquires various types of data from the outside, an output unit that generates output related to sight, hearing, or touch, a sensor unit that senses state information, environmental information, and user information of the device or its surroundings, and a training unit that learns a model composed of an artificial neural network using training data.

[0089] The structure of the wireless device illustrated in FIG. 3 may be understood as part of a terminal (or first node), or part of an intermediate point, or part of a base station (or second node). If the device illustrated in FIG. 3 is a base station (or second node), the device may further include a wired transceiver for front haul and / or back haul communication. If the front haul and / or back haul communication is based on wireless communication, at least one transceiver (206) illustrated in FIG. 3 is used for front haul and / or back haul communication, and a wired transceiver may not be included.

[0090] Communication procedures

[0091] FIG. 4 illustrates an exemplary communication procedure between a first node and a second node to which some examples of the present disclosure may be applied.

[0092] FIG. 4 illustrates the operation of a first node (110) (e.g., a terminal) and a second node (120) (e.g., a base station) transmitting and / or receiving data, and the operation performed prior to this.

[0093] In step S101, the first node (110) and the second node (120) can perform synchronization. For example, the terminal (110) performs an initial cell search operation. Specifically, the terminal (110) can detect at least one synchronization signal transmitted from the base station (120) according to a predefined rule. Here, the synchronization signal may include a plurality of synchronization signals (e.g., a primary synchronization signal, a secondary synchronization signal) classified according to structure or use. Through this, the terminal (110) can identify the boundaries of the frame, subframe, slot, and / or symbol of the base station (120) and obtain information about the base station (120) (e.g., a cell identifier).

[0094] In step S103, the first node (110) can obtain system information transmitted from the second node (120). For example, the system information is information related to the attributes, characteristics, and / or capabilities of the base station (120) required to connect to the base station (120) and use the service, and can be classified according to content (e.g., whether it is essential for connection), transmission structure (e.g., the channel used, whether it is provided on-demand), etc., and can be classified, for example, into a master information block (MIB) and a system information block (SIB). If necessary, the terminal (110) may transmit a signal requesting system information prior to receiving the system information. Such request and provision of system information may be performed after a random access procedure described later.

[0095] In step S105, the first node (110) and the second node (120) can perform a random access procedure. For example, the terminal (110) can transmit and / or receive at least one message for a random access procedure (e.g., a random access preamble, a RAR (random access response) message, etc.) based on information related to the random access channel of the base station (120) obtained through system information (e.g., channel location, channel structure, structure of a supported preamble, etc.). For example, the terminal (110) may transmit a preamble (e.g., message 1 (MSG1)) through a random access channel, receive a random access response (RAR) message (e.g., message 2 (MSG2)), transmit a message (e.g., message 3 (MSG3)) containing information related to the terminal (110) (e.g., identification information) to the base station (120) using scheduling information included in the RAR message, and receive a message (e.g., message 4 (MSG4)) for contention resolution and / or connection establishment. As another example, MSG1 and MSG3 may be transmitted and received as a single message (e.g., message A (MSG A), or MSG2 and MSG4 may be transmitted and received as a single message (e.g., message B (MSG B).

[0096] In step S107, the first node (110) and the second node (120) can perform signaling of control information. For example, the control information may be defined in various layers, such as a layer that controls the connection (e.g., a radio resource control (RRC) layer), a layer that handles mapping between logical channels and transmission channels (e.g., a media access control (MAC) layer), and a layer that handles physical channels (e.g., a physical (PHY) layer). For example, the terminal (110) and the base station (120) may perform at least one of signaling to establish a connection, signaling to determine settings related to communication, and signaling to indicate allocated resources.

[0097] In step S109, the first node (110) and the second node (120) can transmit and / or receive data. For example, the terminal (110) and the base station (120) can process data based on the signaling of control information and transmit and / or receive data. For example, when transmitting data, the terminal (110) or the base station (120) can perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and resource mapping on the information bits. For example, when receiving data, the terminal (110) or the base station (120) can perform at least one of extracting a signal from a resource, antenna-specific waveform demodulation, signal placement considering layer mapping, constellation demapping, descrambling, and channel decoding.

[0098] 6G System Core Technology

[0099] As core implementation technologies for 6G systems, technologies such as artificial intelligence (AI), THz (Terahertz) communication, optical wireless technology, free space optics (FSO) backhaul network, multiple input multiple output (MIMO) technology, blockchain, 3D networking, quantum communication, unmanned aerial vehicles, cell-free communication, wireless information and energy transfer (WIET), integration of sensing and communication, integration of access backhaul networks, holographic beamforming, big data analysis, and large intelligent surface (LIS) can be adopted.

[0100] artificial intelligence

[0101] The introduction of AI into communications can streamline and enhance real-time data transmission. AI can determine how complex target tasks are performed using numerous analyses. AI can increase efficiency and reduce processing latency. Time-consuming tasks such as handover, network selection, and resource scheduling can be performed instantly using AI. AI can also play a significant role in machine-to-machine (M2M), machine-to-human, and human-to-machine communication. Furthermore, AI can enable rapid communication in Brain-Computer Interfaces (BCI). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0102] FIG. 5 illustrates an exemplary functional framework for AI operations to which some examples of the present disclosure may be applied.

[0103] Below, to provide a more specific explanation of AI (or AI / ML (machine learning)), terms can be defined as follows.

[0104] - Data collection: Data collected from network nodes, management entities, or terminals, serving as a basis for AI model training, data analysis, and inference.

[0105] - AI model: A data-driven algorithm that applies AI technology to generate a set of outputs containing predictive information and / or decision parameters based on a set of inputs.

[0106] - AI / ML Training: An online or offline process of training an AI model by learning features and patterns that best represent data and acquire an AI / ML model trained for inference.

[0107] - AI / ML Inference: A process of making predictions or deriving decisions based on collected data and an AI model using a trained AI model.

[0108] Referring to FIG. 5, the data collection function (10) is a function that collects input data and provides processed input data to the model training function (20) and the model inference function (30).

[0109] Examples of input data may include measurements from terminals or other network entities, feedback from actors, and outputs from AI models.

[0110] The data collection function (10) performs data preparation based on input data and provides the input data processed through data preparation. Here, the data collection function (10) does not perform specific data preparation (e.g., data pre-processing and cleaning, forming and transformation) for each AI algorithm, and can perform data preparation common to AI algorithms.

[0111] After the data preparation process is performed, the data collection function (10) can provide training data (11) to the model training function (20) and provide inference data (12) to the model inference function (30). Here, the training data (11) corresponds to data required as input for the AI ​​model training function (20), and the inference data (12) corresponds to data required as input for the AI ​​model inference function (30).

[0112] The data collection function (10) may be performed by a single entity (e.g., terminal, RAN node, network node, etc.) but may also be performed by multiple entities. In this case, training data (11) and inference data (12) from multiple entities may be provided to the model training function (20) and the model inference function (30), respectively.

[0113] The model training function (20) may correspond to a function that performs AI model training, validation, and testing, which can generate model performance metrics as part of the AI ​​model testing procedure. If necessary, the model training function (20) may also be responsible for data preparation (e.g., data pre-processing and cleaning, formatting and transformation, etc.) based on training data (11) provided by the data collection function (10).

[0114] Here, model deployment / update (13) can be used to initially deploy a trained, validated, and tested AI model to the model inference function (30) or to provide an updated model to the model inference function (30).

[0115] The model inference function (30) may correspond to a function that provides an AI model inference output (16) (e.g., a prediction or a decision). The model inference function (30) may provide model performance feedback (14) to the model training function (20) where applicable. Additionally, the model inference function (30) may be responsible for data preparation (e.g., data pre-processing and cleaning, formatting and transformation, etc.) based on the inference data (12) provided by the data collection function (10) if necessary.

[0116] Here, output (16) refers to the inference output of an AI model generated by the model inference function (30), and the details of the inference output may vary depending on the use case.

[0117] Model performance feedback (14) can be used to monitor the performance of the AI ​​model if available, and this feedback may be omitted.

[0118] The actor function (40) is a function that receives an output (16) from the model inference function (30) and triggers or performs a corresponding operation / action. The actor function (40) can trigger an operation / action on another entity (e.g., one or more terminals, one or more RAN nodes, one or more network nodes, etc.) or on itself.

[0119] Feedback (15) can be used to derive training data (11) and inference data (12), or to monitor the performance of the AI ​​model, the impact on the network, etc.

[0120] Meanwhile, the definitions of training, validation, and testing in data sets used in AI / ML can be distinguished as follows.

[0121] - Training data: Refers to the dataset used to train a model.

[0122] - Validation data: This refers to a dataset used to validate a model that has already been trained. Validation data typically refers to a dataset used to prevent overfitting of the training dataset. Additionally, validation data can refer to a dataset used to select the best model among the various models trained during the learning process. Therefore, validation can be viewed as a type of training.

[0123] - Test data: Refers to the dataset for final evaluation. This data is unrelated to training.

[0124] For example, within the entire dataset, training data and validation data can be divided in a ratio of approximately 8:2 or 7:3. Alternatively, within the entire dataset, training data:validation data:test data can be divided in a ratio of 6:2:2.

[0125] Depending on whether the base station and the terminal possess the capability for AI / ML functions, the cooperation level can be defined as follows, and variations resulting from the combination of multiple levels below or the separation of any one level are also possible.

[0126] Category 0a: This corresponds to a no collaboration framework. In this case, the AI / ML algorithm is based on pure implementation and may not require changes to the wireless interface.

[0127] Category 0b: Corresponds to a framework that involves a wireless interface modified to fit efficient implementation-based AI / ML algorithms but lacks cooperation.

[0128] Category 1: This applies to cases involving inter-node support to improve the AI / ML algorithms of each node. For example, it applies when a terminal receives support from a base station (for training, adaptation, etc.), and vice versa. At this level, model exchange between network nodes is not required.

[0129] Category 2: This applies to cases where joint ML operations between a terminal and a base station can be performed. This level requires AI / ML model commands or exchanges between network nodes.

[0130] The functions exemplified in Figure 5 above may be implemented at RAN nodes (e.g., base station, TRP, base station CU, etc.), network nodes, network operator's OAM (operation administration maintenance), or terminals.

[0131] Alternatively, two or more entities among a RAN, a network node, a network operator's OAM, or a terminal may cooperate to implement the functions exemplified in FIG. 5. For example, one entity may perform some of the functions of FIG. 5, and another entity may perform the remaining functions. As such, some of the functions exemplified in FIG. 5 are performed by a single entity (e.g., a terminal, a RAN node, a network node, etc.), the transmission / provision of data / information between each function may be omitted. For example, if the model training function (20) and the model inference function (30) are performed by the same entity, the transmission / provision of model distribution / update (13) and model performance feedback (14) may be omitted.

[0132] Alternatively, any one of the functions exemplified in FIG. 5 may be performed by two or more entities among the RAN, network node, network operator's OAM, or terminal in collaboration. This may be referred to as a split AI operation.

[0133] FIG. 6 illustrates an example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

[0134] For example, the AI ​​model training function can be performed by network nodes (e.g., core network nodes, network operator's OAM, etc.), and the AI ​​model inference function can be performed by RAN nodes (e.g., base station, TRP, base station's CU, etc.).

[0135] Step 1: RAN Node 1 and RAN Node 2 can transmit input data (e.g., training data) for training an AI model to a network node. Here, RAN Node 1 and RAN Node 2 can also transmit data collected from terminals to the network node (e.g., terminal measurements related to RSRP (reference signal received power), RSRQ (reference signal received quality), and SINR (signal to interference-plus-noise ratio) of the serving cell and neighboring cells, terminal location, speed, etc.).

[0136] Step 2: Network nodes can train AI models using the received training data.

[0137] Step 3: The network node can distribute / update the AI ​​model to RAN Node 1 and / or RAN Node 2. RAN Node 1 (and / or RAN Node 2) may also continue model training based on the received AI model.

[0138] For the sake of convenience of explanation, it is assumed that the AI ​​model was deployed / updated only to RAN Node 1.

[0139] Step 4: RAN Node 1 can receive input data (e.g., inference data) for AI model inference from the terminal and RAN Node 2.

[0140] Step 5: RAN Node 1 can perform AI model inference using the received inference data to generate output data (e.g., prediction or decision).

[0141] Step 6: If applicable, RAN node 1 can send model performance feedback to network nodes.

[0142] Step 7: RAN Node 1, RAN Node 2, and the terminal (or 'RAN Node 1 and the terminal', or 'RAN Node 1 and RAN Node 2') can perform an action based on the output data. For example, in the case of a load balancing action, the terminal may move from RAN Node 1 to RAN Node 2.

[0143] Step 8: RAN Node 1 and RAN Node 2 can transmit feedback information to network nodes.

[0144] FIG. 7 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

[0145] For example, both AI model training and AI model inference functions can be performed by RAN nodes (e.g., base station, TRP, base station's CU, etc.).

[0146] Step 1: The terminal and RAN node 2 can transmit input data (e.g., training data) for training an AI model to RAN node 1.

[0147] Step 2: RAN Node 1 can train an AI model using the received training data.

[0148] Step 3: RAN Node 1 can receive input data (e.g., inference data) for AI model inference from the terminal and RAN Node 2.

[0149] Step 4: RAN Node 1 can perform AI model inference using the received inference data to generate output data (e.g., prediction or decision).

[0150] Step 5: RAN Node 1, RAN Node 2, and the terminal (or 'RAN Node 1 and the terminal', or 'RAN Node 1 and RAN Node 2') can perform an action based on the output data. For example, in the case of a load balancing action, the terminal may move from RAN Node 1 to RAN Node 2.

[0151] Step 6: RAN Node 2 can send feedback information to RAN Node 1.

[0152] FIG. 8 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

[0153] For example, the AI ​​model training function may be performed by a RAN node (e.g., base station, TRP, base station CU, etc.), and the AI ​​model inference function may be performed by a terminal.

[0154] Step 1: A terminal can transmit input data (e.g., training data) for training an AI model to a RAN node. Here, the RAN node can collect data (e.g., terminal measurements related to RSRP, RSRQ, SINR of the serving cell and neighboring cells, terminal location, velocity, etc.) from various terminals and / or other RAN nodes.

[0155] Step 2: The RAN node can train an AI model using the received training data.

[0156] Step 3: The RAN node can distribute / update the AI ​​model to the terminal. The terminal may also continue model training based on the received AI model.

[0157] Step 4: Input data (e.g., inference data) for AI model inference can be received from terminals and RAN nodes (and / or other terminals).

[0158] Step 5: The terminal can perform AI model inference using the received inference data to generate output data (e.g., prediction or decision).

[0159] Step 6: If applicable, the terminal can transmit model performance feedback to the RAN node.

[0160] Step 7: The terminal and the RAN node can perform actions based on the output data.

[0161] Step 8: The terminal can transmit feedback information to the RAN node.

[0162] THz communication

[0163] Data transmission rates can be increased by expanding bandwidth. This can be achieved by using sub-THz communication with wide bandwidth and applying advanced large-scale MIMO technology. THz waves, also known as sub-millimeter radiation, generally refer to a frequency band between 0.1 THz and 10 THz with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz–300 GHz band range (sub-THz band) is considered the primary portion of the THz band for cellular communication. Adding the sub-THz band to the mmWave band increases 6G cellular communication capacity. Among the defined THz bands, the 300 GHz–3 THz band is located in the far-infrared (IR) frequency band. Although the 300 GHz–3 THz band is part of the broadband, it lies at the boundary of the broadband and immediately following the RF band. Therefore, this 300 GHz–3 THz band exhibits similarities to RF.

[0164] FIG. 9 shows an electromagnetic spectrum to which some examples of the present disclosure may be applied.

[0165] Key characteristics of THz communication include (i) widely available bandwidth to support very high data transmission rates, and (ii) high path loss occurring at high frequencies (highly directional antennas are indispensable). The narrow beam width generated by highly directional antennas reduces interference. The small wavelength of THz signals allows a much larger number of antenna elements to be integrated into devices and BSs operating in this band. This enables the use of advanced adaptive array technologies that can overcome range limitations.

[0166] When transmitting system information (e.g., MIB) of a cell in the THz frequency band, it can be inefficient because, in the case of high frequency bands, beam sweeping must be performed more frequently to cover the entire area of ​​the cell as the beam width becomes narrower. In particular, transmitting system information using this method is even more inefficient when there are not many users in the cell.

[0167] FIG. 10 illustrates an exemplary system information transmission / reception procedure to which some examples of the present disclosure may be applied.

[0168] The example of FIG. 10 is applicable not only to THz communication environments but also to 6G communication environments where THz communication is not applied. In addition, the procedure exemplified in FIG. 10 can be combined with various embodiments of the present disclosure described below. For example, embodiments described below can be performed based on system information obtained by the procedure exemplified in FIG. 10.

[0169] In step S1010, the second node (120) (e.g., a base station) can transmit system information of cell #1 through cell #2. For example, the base station provides at least two cells, cell #1 uses a THz frequency band, and cell #2 uses a frequency band other than the THz frequency band. Here, the system information may include at least one of a system frame number (SFN) generated at a higher layer, a PDCCH configuration for SIB1, cell barring, cell re-selection, and subcarrier spacing, and may include at least one of a synchronization signal / PBCH (physical broadcast channel) block index generated at a physical layer. To this end, as an example, cell #1 and cell #2 may have a secondary cell and primary cell relationship.

[0170] In step S1030, the first node (110) (e.g., a terminal) can acquire synchronization for cell #1. Synchronization can be acquired by detecting a synchronization signal. Generally, synchronization is acquired prior to receiving system information, but since the system information of cell #1 is received in cell #2, the acquisition of synchronization for cell #1 can be performed after receiving system information. For example, the terminal can acquire synchronization based on system information. Alternatively, the acquisition of synchronization may be performed prior to step S1010.

[0171] In step S1050, the first node (110) may transmit a signal to connect to cell #1. For example, the signal may include a random access preamble. The structure of such a signal and the resource for transmitting the signal (e.g., a channel) may be identified through system information. Subsequently, in step S1070, the first node (110) and the second node (120) may perform a connection procedure to cell #1 and perform communication.

[0172] The procedure described with reference to FIG. 10 may be performed when the first node (110) first connects to cell #1 of the second node (120). Alternatively, a similar procedure may be performed when the first node (110) handovers to cell #1 of the second node (120). However, in the case of a handover, the system information of cell #1 may be received from a cell of a different base station other than cell #2 of the second node (120).

[0173] Communication in the THz band is expected to experience severe path loss, and to overcome this, terminals and base stations may be required to use very sharp beams. The use of sharp beams implies that terminals and base stations must perform beam control in addition to beamforming, meaning that a very large number of beams are utilized. Consequently, aligning the transmit and receive beams between the base station and the terminal takes a very long time. Furthermore, if the beam alignment between the base station and the terminal is disrupted due to the movement of the terminal, time is frequently required to realign the beams, which may lead to link instability.

[0174] FIG. 11 illustrates an exemplary beam management procedure to which some examples of the present disclosure may be applied.

[0175] Figure 11 illustrates an example of a procedure for searching and / or selecting beams for THz communication, but this procedure is not limited to a THz environment and can also be applied in a 6G communication environment where THz communication is not applied.

[0176] Here, the term "beam" can be interpreted as other terms having equivalent technical meanings capable of distinguishing beams, such as "spatial domain filter," "spatial domain transmit filter," "spatial domain receive filter," reference signal (RS) resources for distinguishing beams, and SSB index.

[0177] In step S1110, the second node (120) (e.g., base station) may set resources for beam management to the first node (110) (e.g., terminal). Here, the resources may include at least one of time-frequency resources, channels, and spatial resources (e.g., antenna ports). For example, the base station may utilize a beam search signal (BSS) that is transmitted spatially separated from the existing downlink signal / channel for beam search. Here, the BSS may be transmitted based on a dedicated port for beam search. The dedicated port may be a port different from the port for transmitting the existing downlink signal / channel (e.g., SSB, PDSCH (physical downlink shared channel), etc.). BSS is a term defined for convenience of explanation, and the technical concept according to the present embodiment is not limited to the term BSS itself. For example, a signal transmitted based on a dedicated port defined / set for beam search may be included in the technical concept according to the present embodiment.

[0178] In step S1130, the second node (120) (e.g., a base station) transmits measurement signals using multiple transmission beams. For example, the measurement signals may include at least one of a reference signal and a synchronization signal. At this time, the measurement signals may be transmitted as many times as the number of beams requiring measurement, and may be transmitted using a multi-beam transmission method that forms multiple beams simultaneously to reduce sweeping time. Here, multi-beam transmission may be performed based on at least one of a multi-panel, a sub-array, or a true time delay (TTD).

[0179] In step S1150, the first node (110) (e.g., a terminal) may transmit a feedback signal to the second node (120) (e.g., a base station). The feedback signal may indicate at least one beam selected by the terminal. The terminal may select at least one preferred beam based on the measurement signals received in step S1130.

[0180] In step S1170, the first node (110) and the second node (120) can communicate. For example, the second node (120) can perform transmission to the first node (110) using the receiving beam of the first node (110) selected in step S1150. If channel reciprocity is established, the transmission beam of the first node (110) can also be determined through steps S1130 and S1150, so the transmission operation from the first node (110) can also be performed using a beam that has a reciprocity relationship with the beam selected in step S1150. If channel reciprocity is not established, a procedure including the transmission of measurement signal(s) by the first node (110) and the transmission of feedback signal(s) by the second node (120) may be performed first to determine the transmission beam of the first node (110).

[0181] Non-terrestrial networks (NTN)

[0182] FIGS. 12 and FIGS. 13 show examples of NTN scenarios to which some examples of the present disclosure may be applied.

[0183] NTN can represent a network or network segment that uses RF (radio frequency) resources mounted on a satellite (or UAS (unmanned aerial system) platform).

[0184] Figure 12 shows an example of a typical scenario of an NTN based on a transparent payload, and Figure 13 shows an example of a typical scenario of an NTN based on a regenerative payload.

[0185] Referring to FIG. 12, the satellite (or UAS platform) can establish a service link with a terminal. The satellite (or UAS platform) can be connected to a gateway via a feeder link. The satellite can be connected to a data network via the gateway. A beam footprint may refer to an area where signals transmitted by the satellite can be received.

[0186] Referring to FIG. 13, a satellite (or UAS platform) can establish a service link with a terminal. The satellite (or UAS platform) connected to the terminal can be connected to another satellite (or UAS platform) via inter-satellite links (ISL). Another satellite (or UAS platform) can be connected to a gateway via a feeder link. Based on a regenerated payload, the satellite can be connected to a data network via another satellite and a gateway. If no ISL exists between the satellite and another satellite, a feeder link between the satellite and the gateway may be required.

[0187] FIGS. 12 and 13 are merely examples of NTN scenarios, and NTN can be implemented based on various scenarios. For example, a satellite (or UAS platform) can implement a transparent or regenerative (with on-board processing) payload. For example, a satellite (or UAS platform) can generate multiple beams across a designated service area depending on the field of view of the satellite (or UAS platform). For example, the field of view of the satellite (or UAS platform) may vary depending on the on-board antenna diagram and the minimum elevation angle.

[0188] For example, the transparent payload may include radio frequency filtering, frequency conversion, and amplification. Therefore, the waveform signal repeated by the payload may not be altered.

[0189] For example, the regeneration payload may include radio frequency filtering, frequency conversion and amplification, demodulation / decoding, switching and / or routing, and coding / modulation. For example, the regeneration payload may be substantially the same as carrying all or part of the base station functions on a satellite (or UAS platform).

[0190] Integrated Sensing and Communication (ISAC)

[0191] Wireless sensing is a technology that uses radio frequencies to determine the instantaneous linear velocity, angle, distance (or range) of an object, thereby obtaining information about the characteristics of the environment and / or objects within the environment. Since radio frequency sensing capabilities do not require connecting to objects via devices within a network, they can provide services for determining object locations without the need for devices. The ability to obtain range, velocity, and angle information from radio frequency signals can provide a wide range of new functions, such as various object detection, object recognition (e.g., vehicles, humans, animals, UAVs), high-precision localization, tracking, and activity recognition. Wireless sensing services can provide information to various industries (e.g., unmanned aerial vehicles, smart homes, V2X, factories, railways, public safety, etc.) that enable applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, wireless sensing may utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of a wireless sensing service, such as sensing operations, may depend on the transmission, reflection, and scattering processing of wireless sensing signals. Therefore, wireless sensing can provide an opportunity to enhance existing communication systems from communication networks to wireless communication and sensing networks.

[0192] FIG. 14 shows examples of sensing operations to which some examples of the present disclosure may be applied.

[0193] Specifically, FIG. 14(a) illustrates an example of monostatic sensing operation using a sensing receiver and a sensing transmitter located at the same position. FIG. 14(b) illustrates an example of bistatic sensing operation using a sensing receiver and a sensing transmitter located at separate positions. A sensing receiver receives a signal that is reflected or scattered by a sensing object from a sensing signal transmitted from a sensing transmitter, and can extract or acquire sensing data based on the received signal. A sensing result can be generated or determined through appropriate processing of this sensing data. The sensing result can be provided to a trusted third-party entity or service outside the 3GPP system via an entity or service within the 3GPP system.

[0194] Ambient IoT (ambient internet of things)

[0195] Recently, the Internet of Things (IoT) has been attracting significant attention in the world of wireless communication. By reducing the size, complexity, and power consumption of IoT devices, and by installing and connecting tens of billions to hundreds of billions of IoT devices, it becomes possible to apply them to various fields.

[0196] In this regard, the IoT technology is being developed under the name Ambient IoT (AmIoT) for various use cases, scenarios, requirements, signaling, configuration, etc.

[0197] For example, active signal generation and / or backscattering may be one of the communication techniques considered to achieve low-power operation of AmIoT devices. For example, backscattering can enable the device to communicate with the network by reflecting incident waves after modulating them with the information to be transmitted. For example, the device may be powered by an incident RF signal or stored energy.

[0198] AmIoT 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, passive devices do not have energy storage devices (e.g., capacitors) and can communicate based on backscatter communication technology. For example, semi-passive devices have energy storage devices and can communicate using backscatter communication technology with the assistance of energy storage devices. For example, active devices have energy storage devices and can communicate by actively generating signals using active RF components and stored energy.

[0199] In the present disclosure, the following types of IoT devices may be considered.

[0200] Device type 1 has a maximum power consumption of approximately 1 uW and can perform uplink transmission by backscattering a carrier wave (CW) provided from an external source (e.g., a reader such as a base station / terminal or a separate node). For example, device type 1 may be a device without energy storage and without independent signal generation.

[0201] Device type 2 has a maximum power consumption of approximately several hundred uW and can perform uplink transmission by backscattering carrier waves provided from an external source (e.g., a reader such as a base station / terminal or a separate node) or through signals generated internally. Specifically, a device type that performs signal transmission via backscatter may be referred to as device type 2a, and a device type that performs signal transmission via signals generated internally may be referred to as device type 2b. For example, device type 2a is a device with energy storage and no independent signal generation, in which case the use of the stored energy may include amplification of the reflected signal. Additionally, for example, device type 2b may be a device with energy storage and independent signal generation (e.g., a device with active RF components for transmission).

[0202] In addition, in addition to the classification methods described above, the type / class of AmIoT devices can 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.

[0203] Regarding AmIoT communication, various basic topologies may be considered to support AmIoT devices in indoor and outdoor scenarios. For example, basic topologies may include a direct connection topology between a base station and an AmIoT device, a topology where the base station and an AmIoT device are connected through an intermediate node, a topology where connection via an auxiliary node is supported, and / or a connection topology between a terminal and an AmIoT device.

[0204] The basic topologies described in this disclosure are merely examples, and the proposals of this disclosure may be extended to other types of topologies.

[0205] FIG. 15 illustrates topologies that can be supported in ambient IoT communication to which some examples of the present disclosure may be applied.

[0206] FIG. 15(a) shows a direct connection topology between a base station and an AmIoT device (e.g., topology 1) according to an embodiment of the present disclosure.

[0207] Referring to FIG. 15(a), the AmIoT device can communicate directly and bidirectionally with a base station. For example, communication between the base station and the AmIoT device may include AmIoT data and / or signals. For example, AmIoT 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 this regard, the base station performing transmission to the AmIoT device and the base station performing reception from the AmIoT device may be different. For example, in Topology 1, the base station and the AmIoT 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.

[0208] FIG. 15(b) shows a topology (e.g., topology 2) in which a base station and an AmIoT device are connected through an intermediate node according to an embodiment of the present disclosure.

[0209] Referring to FIG. 15(b), an AmIoT device can communicate bidirectionally with an intermediate node between the device and the base station. For example, the intermediate node may be an AmIoT-enabled relay, IAB node, terminal, repeater, etc. The intermediate node may transmit AmIoT data and / or signals between the base station and the AmIoT device. AmIoT 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 this regard, the intermediate node performing transmission to the AmIoT device and the intermediate node performing reception from the AmIoT device may be different. For example, in Topology 2, an intermediate node may exist between the base station and the AmIoT device in a macro-cell environment. 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 may be limited to a terminal, and the intermediate node may be located indoors.

[0210] FIG. 15(c) shows a topology (e.g., topology 3) in which connection by an auxiliary node is supported according to an embodiment of the present disclosure.

[0211] Referring to the left topology of FIG. 15(c), an auxiliary node may be supported for downlink reception. For example, an AmIoT device may transmit data / signals to a base station, and an AmIoT device may receive data / signals from an auxiliary node. Additionally, referring to the right topology of FIG. 15(c), an auxiliary node may be supported for uplink transmission. For example, an AmIoT device may receive data / signals from a base station, and an AmIoT device may transmit data / signals to an auxiliary node. For example, the auxiliary node may be an AmIoT-enabled relay, IAB node, terminal, repeater, etc.

[0212] FIG. 15 (d) shows a connection topology (e.g., topology 4) between a terminal and an AmIoT device according to an embodiment of the present disclosure.

[0213] Referring to FIG. 15 (d), the AmIoT device can communicate bidirectionally with the terminal. For example, communication between the terminal and the AmIoT device may include AmIoT data and / or signals. AmIoT data and / or signals may be transmitted or received based on a control channel and / or a data channel (e.g., a shared channel).

[0214] FIG. 16 shows a specific example of a topology supported in ambient IoT communication to which some examples of the present disclosure may be applied.

[0215] Figure 16 (a) illustrates various cases of topology 1, and Figure 16 (b) illustrates various cases of topology 2.

[0216] Referring to Fig. 16(a), in the case of D1T1-A1, different leaders, Node R1 (e.g., Leader 1) and Node R2 (e.g., Leader 2), may each be responsible for R2D channel transmission and D2R channel reception. In this case, the CW signal may be transmitted by Node R1. In the case of D1T1-A2, the same leader, Node R, may be responsible for both R2D channel transmission and D2R channel reception. In this case, the CW signal may be transmitted by Node R. In the case of D1T1-B, the same leader, Node R, may be responsible for both R2D channel transmission and D2R channel reception. In this case, the CW signal may be transmitted by a separate CW node. In this regard, Nodes R / R1 / R2 may all be base stations or network nodes connected to base stations.

[0217] Referring to Fig. 16(b), in the case of D2T2-A1, different leaders, Node R1 (e.g., Leader 1) and Node R2 (e.g., Leader 2), may each be responsible for R2D channel transmission and D2R channel reception. In this case, the CW signal may be transmitted by Node R1. In the case of D2T2-A2, the same leader, Node R, may be responsible for both R2D channel transmission and D2R channel reception. In this case, the CW signal may be transmitted by Node R. In the case of D2T2-B, the same leader, Node R, may be responsible for both R2D channel transmission and D2R channel reception. In this case, the CW signal may be transmitted by a separate CW node. In this regard, Nodes R / R1 / R2 may all be terminals that perform the role of an intermediate node (IN). Alternatively, in the case of D2T2-A1, the R1 node may be a base station and the R2 node may be a terminal, or the R1 node may be a terminal and the R2 node may be a base station.

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

[0219] In this regard, CW waveforms can be supported in various types. For example, the type of CW waveform can be a single-tone CW waveform or a somewhat complex multi-tone CW waveform. For example, 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 because 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.

[0220] Considering the advantages of these different CW waveform types, multiple CW waveform types may be supported in the AmIoT system, and the base station / IN / AN / UE may configure the CW waveform type. For example, one or more CW waveform types supported by the AmIoT 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 the AmIoT device. For example, the base station / IN / AN / UE may configure / instruct / display the selected CW waveform type to the AmIoT device in the form of a command / message transmitted as a preamble / frame-sync or payload.

[0221] In the present disclosure, for AmIoT communication, at least one of the necessary characteristics of a carrier waveform for a carrier provided outside the AmIoT device (including interference handling at the AmIoT device UL receiver and NR base station) may be proposed. Additionally, in the present disclosure, for AmIoT 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 AmIoT with 6G / NR / LTE, and / or RF requirements for AmIoT may be proposed.

[0222] Technical terms used in this disclosure may be as follows.

[0223] - SSB: Synchronization Signal Block

[0224] - MIB: Master Information Block

[0225] - RMSI: Remaining Minimum System Information

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

[0227] - FR2: Frequency Domain 2. Refers to the millimeter wave (mmWave) region above 24 GHz (e.g., 24,250 MHz ~ 52,600 MHz).

[0228] - BW: Bandwidth

[0229] - BWP: Bandwidth Part

[0230] - RNTI: Radio Network Temporary Identifier

[0231] - CRC: Cyclic Redundancy Check

[0232] - SIB: System Information Block

[0233] - SIB1: SIB1 for NR devices (e.g., RMSI). Broadcasts information necessary for cell connection of NR terminals.

[0234] - CORESET: Control Resource Set. Time / frequency resource for which the NR terminal attempts candidate PDCCH decoding.

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

[0236] - Type0-PDCCH CSS Set: A search space set in which NR terminals monitor a set of PDCCH candidates for DCI format with CRCs scrambled to SI-RNTI.

[0237] - MO: PDCCH monitoring opportunity for Type0-PDCCH CSS set

[0238] - SIB1-R: (Additional) SIB1 for NR devices with reduced capability. Limited to cases where it is created as a separate TB from the SIB1 and transmitted via a separate PDSCH.

[0239] - CORESET#0-R: CORESET#0 for Reduced Capability NR Devices

[0240] - Type0-PDCCH-R CSS Set: A search space set with redcap UEs monitoring a set of PDCCH candidates for DCI format with CRCs scrambled with SI-RNTI.

[0241] - MO-R: PDCCH monitoring opportunity for Type0-PDCCH CSS set

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

[0243] - Non-cell defining SSB (non-CD-SSB): Refers to an SSB placed 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.

[0244] - SCS: Subcarrier spacing

[0245] - SI-RNTI: System Information-RNTI

[0246] - Camp On: "Camp On" is a terminal state where the UE remains in a cell and is ready to start potential dedicated services or receive ongoing broadcast services.

[0247] - TB: Transport Block

[0248] - RSA (Redcap standalone): A cell that supports only the Redcap device or service.

[0249] - SIB1(-R)-PDSCH: PDSCH transmitting SIB1(-R)

[0250] - SIB1(-R)-DCI: DCI scheduling SIB1(-R)-PDSCH. DCI format 1_0 CRC scrambled by SI-RNTI.

[0251] - SIB1(-R)-PDCCH: PDCCH transmitting SIB1(-R)-DCI

[0252] - FDRA: Frequency Domain Resource Allocation

[0253] - TDRA: Time Domain Resource Allocation

[0254] - RA: Random Access

[0255] - MSGA: Transmission of preamble and payload for a two-stage RA type random access procedure.

[0256] - MSGB: Response to MSGA in a two-stage random access procedure. MSGB may consist of responses to contention resolution, fallback instructions, and backoff instructions.

[0257] - RO-N: RO (RACH Occasion) for general terminal 4-stage RACH and 2-stage RACH (if configured)

[0258] - RO-N1, RO-N2: When a separate RO is configured for general terminal 2-stage RACH, it is classified as RO-N1 (4 stages) and RO-N2 (2 stages).

[0259] - RO-R: RO (RACH Occasion) configured separately from RO-N for Redcap terminal Level 4 RACH and Level 2 RACH (if configured)

[0260] - RO-R1, RO-R2: When a separated RO is configured for Redcap terminal 2-stage RACH, it is classified as RO-R1 (4 stages) and RO-R2 (2 stages).

[0261] - PG-R: MsgA-preamble group for redcap terminals

[0262] - RAR: Random Access Response

[0263] - RAR Window: Time window to monitor RA responses

[0264] - FH: Frequency Hopping

[0265] - iBWP: Initial BWP

[0266] - iBWP-DL(-UL): Initial DL(UL) BWP

[0267] - iBWP-DL(-UL)-R: Initial DL(UL) BWP (separated) for redcap

[0268] - CS: Cyclic shift

[0269] - NB: Narrowband

[0270] - TO: Traffic Offloading

[0271] - mMTC: Massive Machine Type Communications

[0272] - eMBB: Enhanced Mobile Broadband Communication

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

[0274] - RedCap: Reduced Capability

[0275] - eRedCap: Enhanced RedCap

[0276] - FDD: Frequency Division Duplex

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

[0278] - DRX: Discontinuous Reception

[0279] - RRC: Radio Resource Control

[0280] - RRM: Radio Resource Management

[0281] - MM: Mobility Management

[0282] - IWSN: Industrial Wireless Sensor Network

[0283] - LPWA: Low Power Wide Area

[0284] - RB: Resource Block

[0285] - CCE: Control Channel Element

[0286] - AL: Aggregation Level

[0287] - PRG: Physical Resource-block Group

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

[0289] - PBCH: Physical Broadcast Channel

[0290] - A-PBCH: Additional PBCH

[0291] - BD: Blind detection

[0292] - EPRE: Energy Per RE

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

[0294] - TDM: Time Division Multiplexing

[0295] - FDM: Frequency Division Multiplexing

[0296] - DMRS: Demodulation Reference Signal

[0297] - TDD: Time Division Duplex

[0298] - PCI: Physical layer Cell ID

[0299] - EH: Energy Harvesting

[0300] - EH Device: A device operating based on EH. This may include all device types in AmIoT. Additionally, while this disclosure primarily considers RF EH, the EH device is not necessarily required to be RF EH-based.

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

[0302] - ET: Energy Transfer

[0303] - CW: Carrier wave. AmIoT devices supporting backscattering-based UL transmission transmit information by modulating and backscattering an "externally provided" CW. AmIoT devices supporting independent signal generation-based UL transmission transmit information by modulating an "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.

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

[0305] - R: Reader / Interrogator. In the AmIoT description, depending on the topology, gNB / eNB, intermediate node (IN) / assisting node (AN), terminal, etc., can be readers. Additionally, since AmIoT is not limited to 4G / 5G communication systems, it may include base stations, intermediate nodes / assisting nodes, and terminals of next-generation communication systems. It may also mean an AmIoT reader.

[0306] - T: Tag / AmIoT device. It may be interchangeable with EH device in this disclosure, and in the AmIoT description, it mainly refers to an AmIoT device, device type 1 / 2a / 2b.

[0307] - D: AmIoT device (may have the same meaning as the aforementioned T)

[0308] - R=>T: Reader-to-Tag or Reader-to-Tag communication link. May have the same meaning as DL or forward link when the base station or intermediate node / auxiliary node is the reader.

[0309] - R2D: Reader (R)-to-Device (D) Link (May have the same meaning as R=>T or AmIoT DL. May be denoted as R=>D.)

[0310] - CW2D: CWN-to-Device(D) Link (CW Node-to-AmIoT Device Link)

[0311] - T=>R: Tag-to-Reader or Tag-to-Reader communication link. If the base station or intermediate / auxiliary node is the leader, it may have the same meaning as a UL or reverse / backward link.

[0312] - D2R: Device (D)-to-Reader (R) Link (May have the same meaning as T=>R or AmIoT UL. May be denoted as D=>R.)

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

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

[0315] - RF-EH: RF energy harvesting

[0316] - PRDCH: Physical R2D Channel (may be denoted as PR2DCH). A physical channel for R2D communication.

[0317] - PDRCH: Physical D2R Channel (may be denoted as PD2RCH). A physical channel for D2R communication.

[0318] - BS: Base Station

[0319] - IN: Intermediate node. In Topology 2 (BS <-> IN <-> AmIoT device), IN acts as the leader. Relays, IABs, terminals, repeaters, etc. can be IN.

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

[0321] - 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 AmIoT devices or device types 1 / 2a / 2b. In Topology 4 (UE <-> AmIoT device), the UE acts as the leader.

[0322] - Device: Unless otherwise noted, and when used alone, refers to an EH device, an AmIoT device, or device type 1 / 2a / 2b without distinction.

[0323] - AmIoT: Ambient IoT

[0324] - F-gap: Frequency gap

[0325] - T-gap: Time gap

[0326] - TD: Time Domain

[0327] - FD: Frequency Domain

[0328] - PEI: Paging Early Indication

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

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

[0331] - RSRP: Reference Signal Received Power

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

[0333] - PRB: Physical Resource Block

[0334] - EH Circuit: A circuit that performs EH operation. An EH device can be viewed as including an EH circuit in the form of a component.

[0335] - PHR: Power Headroom Report

[0336] - EHR: Energy Headroom Report

[0337] - BPF: Band-Pass Filter

[0338] - SM: Subcarrier Modulation

[0339] - PIE: Pulse interval encoding

[0340] Ambient IoT (AmIoT)-based communication

[0341] The present disclosure describes a method for transmitting and receiving signals in Topology 1 and Topology 2, in which direct communication (i.e., mono-static communication) between a base station (or / and intermediate node) and an IoT device is performed among four topologies. However, this is merely one embodiment, and the present disclosure may also be applied to Topology 3 and / or Topology 4.

[0342] For example, in Topology 1, the direction from a base station (e.g., gNB) to a device (e.g., AmIoT device) may be referred to as DL, R2T, or R2D, and the direction from a device to a base station may be referred to as UL, T2R, or D2R. The base station may transmit R2D messages or data information to the device via an R2D signal, and the device may transmit D2R messages or data information to the base station via a D2R signal.

[0343] For example, in Topology 2, the direction from an intermediate node (IN) to a device (e.g., an AmIoT device) may be referred to as DL, R2T, or R2D, and the direction from the device to an intermediate node (IN) may be referred to as UL, T2R, or D2R. The intermediate node (IN) can transmit R2D messages or data information to the device via an R2D signal, and the device can transmit D2R messages or data information to the intermediate node (IN) via a D2R signal.

[0344] Additionally, in this disclosure, the preamble, midamble, and postamble of a D2R transmission and an R2D transmission may refer to the sequence transmitted at the very beginning, the sequence transmitted in the middle, and the sequence transmitted at the very end of the said D2R transmission and R2D transmission.

[0345] For example, physical channels such as PRDCH (physical reader device channel) and PDRCH (physical device reader channel) can transmit upper-layer Transport Blocks (TBs) (e.g., MAC PDUs) and also transmit Layer 1 (layer 1) control information or Layer 2 (layer 2) control information (e.g., MAC headers or MAC control elements). For example, in the case of PRDCH or PDRCH, transmission may begin with a preamble and end with a postamble. Additionally, a midamble may be included between the transmission of Layer 1 / Layer 2 control information or TBs. In this disclosure, the expression x-amble may be used as a word referring to the preamble, midamble, and postamble. Additionally, the preamble, midamble, and postamble described in this disclosure may be transmitted together with D2R transmissions, R2D transmissions (e.g., PDRCH, PRDCH), etc., or may be transmitted included in said D2R transmissions or said R2D transmissions.

[0346] FIG. 17 illustrates a PRDCH generation method and a PDRCH generation method to which some examples of the present disclosure may be applied.

[0347] Referring to FIG. 17, the generation of PRDCH / PDRCH can be composed of CRC attachment, FEC (forward error correction) encoding, TB repetitions, line code encoding, modulation, chip repetitions, and waveform generation.

[0348] Referring to FIG. 17(a), for the R2D information bit, PRDCH can be generated through CRC attachment, line coding, and OOK (On-Off Keying)-1 / OOK-4 generation based on the OFDM waveform. Also, referring to FIG. 17(b), for the D2R information bit, PDRCH can be generated through CRC attachment, coding, and modulation.

[0349] For example, PRDCH / PDRCH generation may be based on one or more of the seven steps described below.

[0350] - Step 1 (CRC attachment): K CRC bits {c_0^CRC, c_1^CRC, ..., c_(K-1)^CRC} are added to the N data bits of the original transmission block {b_0, b_1, b_2, b_N-1}.

[0351] - Step 2 (FEC): The (N + K) bits {b_0, b_1, b_2, ..., b_N-1, c_0^CRC, c_1^CRC, ..., c_(K-1)^CRC} obtained in Step 1 are encoded into a convolutional code with, for example, a 1 / 3 code rate, and a code block {c_0^FEC, c_1^FEC, ..., c_(3(N+K)-1)^FEC} containing a total of 3(N+K) bits is output.

[0352] - Step 3 (TB iteration): If repeated transmission is scheduled, the code block generated in Step 2 is repeated according to the scheduled number of iterations (e.g., 2), and a bit block {c_0^FEC, c_1^FEC, ..., c_(3(N+K)-1)^FEC, c_0^FEC, c_1^FEC, ..., c_(3(N+K)-1)^FEC} containing a total of 6 (N+K) bits is output.

[0353] - Step 4 (Line Code Encoding): The code block repeated in Step 3 is encoded using a line code of length 2, for example, and an encoded block {c_(0,0)^LC, c_(0,1)^LC, c_(1,0)^LC, c_(1,1)^LC, ..., c_(3(N+K)-1,0)^LC, c_(3(N+K)-1,1)^FEC, c_(0,0)^LC, c_(0,1)^LC, c_(1,0)^LC, c_(1,1)^LC, ..., c_(3(N+K)-1,0)^LC, c_(3(N+K)-1,1)^FEC} containing a total of 12 (N+K) bits is output.

[0354] - Step 5 (Modulation): Each bit of the encoded block generated in Step 4 is mapped to 1 / 0 for OOK or +1 / -1 for BPSK (Binary Phase Shift Keying). Each OOK or BPSK symbol is considered a chip for backscatter modulation. In OOK, 1 and 0 represent high and low voltages, respectively, which are reflected in the envelope amplitude of the chip generated by the analog circuit. In BPSK, +1 and -1 represent phase changes of 0 degrees and 180 degrees, respectively, which are reflected in the envelope phase of the chip generated during the backscatter modulation process. The modulator outputs a chip block containing a total of 12(N+K) chips, expressed, for example, as {s_0, s_1, s_2, ..., s_(12(N+K)-1)}.

[0355] - Step 6 (Chip iteration): If repeated transmission is scheduled, each chip of the chip block generated in Step 5 is repeated according to the scheduled number of chip iterations (e.g., 2), and a chip block {s_0, s_0, s_1, s_1, s_2, s_2, ..., s_(12(N+K)-1), s_(12(N+K)-1)} containing a total of 24 (N+K) chips is output.

[0356] - Step 7 (Waveform Generation): A single carrier waveform is proposed for D2R transmission.

[0357] Various methods for determining the transmission block size (TB size, TBS) of PRDCH and / or PDRCH in relation to AmIoT communication are described below.

[0358] In describing the present disclosure, " / " means "and", "or", or "and / or" depending on the context.

[0359] The embodiments described below are separated solely for the sake of clarity of explanation; each embodiment may be applied independently, or the proposed method / configuration of one embodiment may be combined with or substituted with the proposed method / configuration of another embodiment.

[0360] Connection process in Ambient IoT communication

[0361] The process of an ambient IoT device connecting to a reader device is described. As an example of the present disclosure, FIG. 18 is a flowchart for describing the procedure for an ambient IoT device to access a reader device. Specifically, the connection procedure may consist of an MSG0 transmission / reception procedure, an MSG1 transmission / reception procedure, an MSG2 transmission / reception procedure, an MSG3 transmission / reception procedure, an MSG4 transmission / reception procedure, and an MSG5 transmission / reception procedure.

[0362] (MSG0 Transmission and Reception Procedure)

[0363] In one example of the present disclosure, a base station / intermediate node transmits an MSG0 (e.g., a query signal or / and a PDCCH order, etc.) to an ambient IoT device, and the ambient IoT device can receive the MSG0. One or more leaders may transmit the MSG0 according to the instructions of an upper node. For example, according to the instructions of a base station, multiple intermediate nodes (INs) managed by the same base station (e.g., multiple terminals) may transmit the MSG0.

[0364] For example, if MSG0 is a query signal, the terminal can decide whether to transmit MSG1 based on MSG0. MSG0 can be used as a DL sync signal such as PSS / SSS. For example, MSG0 can be reused as a DL sync signal such as PSS / SSS or defined as a new sync signal.

[0365] In this case, MSG0 may include connection-related system information. For example, connection-related system information may include a timer value for the connection operation and information related to the time interval during which MSG1 transmission is possible (e.g., information related to the start time, length, window pattern, etc.). Additionally or alternatively, connection-related system information may be transmitted via a separate MSG0 for each specific device type, and said MSG0 may indicate that said system information applies only to that specific device type.

[0366] Additionally or alternatively, MSG0 may include information for resolving conflicts. For example, MSG0 may include probability-based access information, UE ID-based access information, early indication-based access information, UE group / type-based access information, service / access type-based access information, etc.

[0367] (MSG1 Transmission and Reception Procedure)

[0368] The ambient IoT device can (re)transmit MSG1 to the reader device. For example, the ambient IoT device can (re)transmit MSG1 to the reader device using a backscattering method. The method described below can also be applied to the transmission and reception of messages following MSG1 (e.g., MSG 3 / 5, etc.).

[0369] In one example of the present disclosure, when MSG1 is transmitted using a slotted ALOHA method, the ambient IoT device may transmit MSG1 at a time aligned with a specific time (e.g., the time of transmission of a DL sync signal transmitted by a reader device, etc., or MSG0, the time of transmission of a CW (carrier wave), the time of backscattering transmission (e.g., ambient IoT device A or B), etc.). The slotted ALOHA method is a method of transmitting data per unit time (e.g., slot). In another example, the ambient IoT device may transmit MSG1 by selectively backscattering the CW.

[0370] Additionally, MSG 1 may include a sequence for collision avoidance. The sequence for collision avoidance may be determined based on at least one of the options described below.

[0371] When multiple readers transmit MSG0, the terminal may respond to only one MSG0 transmission. For example, the terminal may transmit MSG1 in response to the MSG0 transmission received first, or respond only to the MSG0 received with the highest intensity.

[0372] (MSG2 Transmission and Reception Procedure)

[0373] An ambient IoT device may receive MSG2 (from a reader device) after performing MSG1 (re)transmission. In one example of the present disclosure, MSG2 may include / indicate ACK or / and NACK information. For example, if the reader device successfully receives MSG1 and allows a connection, MSG2 may include / indicate an ACK. If the reader device fails to successfully receive MSG1 or / and does not allow a connection, MSG2 may include / indicate a NACK.

[0374] For example, if MSG2 includes / indicates an ACK, MSG2 may include at least one of information included in MSG1 (e.g., sequence information), transmission / reception resources of MSG1 (e.g., time / frequency resources), time / frequency for transmission / reception of MSG (e.g., MSG0, MSG1, MSG2, MSG3, MSG4 and / or MSG5, etc.), or CW time / frequency information for backscattering. If MSG2 includes / indicates a NACK, MSG2 may include a back-off time.

[0375] (MSG3 Transmission and Reception Procedure)

[0376] In one embodiment of the present disclosure, when an ACK containing / indicating an ACK is received, the ambient IoT device may transmit MSG3 (to a reader device). As an example, the ambient IoT device may transmit MSG3 using a backscattering method. The selection of a time interval / time point / frequency / resource for MSG3 transmission may be determined / selected according to at least one of the transmission / reception time interval / time point / frequency / resource selection methods of MSG2.

[0377] MSG3 may include at least one of a UE ID, sequence, early instruction, UE group / type, connection type, RRC connection / resume request message for initial connection, and a C-RNTI MAC CE for the UE within RRC_CONNECTED.

[0378] Here, the UE ID (e.g., C-RNTI) may be scrambled, masked, or attached to all UL messages. The sequence may be part or all of the sequence selected for MSG1. As another example, the sequence may be part or all of the newly selected sequence using at least one of the MSG1 sequence selection methods described above. The early indication may include a device type (e.g., Device A, Device B, or Device C) and / or other processing time. The RRC connection / resumption request message may include a UE ID (e.g., s-TMSI or resumption ID), etc.

[0379] (MSG4 and MSG5 Transmission and Reception Procedures)

[0380] An ambient IoT device that transmitted MSG 3 can receive MSG4 (from a reader device). At this time, MSG4 may include a UE ID (or / and contention resolution MAC CE) or / and sequence information. Here, the sequence may be selected / determined according to at least one of the MSG1 sequence selection methods described above.

[0381] If MSG4 contains the UE ID (or device ID) or sequence of the ambient IoT device, the ambient IoT device can transmit MSG5 (to the reader device).

[0382] For example, MSG5 may include terminal capability information. For example, the terminal capability information may include capability information related to device type (e.g., device type A, B, C), other processing time, early indication (e.g., device type, other processing time), terminal group / type, connection type, etc. Additionally or alternatively, MSG5 may include at least one of UE ID, sequence, and user data.

[0383] Control Information and PRDCH / PDRCH Transmission Structure

[0384] The following describes the transmission structure of control information and PRDCH / PDRCH in relation to R2D / D2R transmission in AmIoT communication.

[0385] FIG. 19 illustrates a control information and PRDCH / PDRCH transmission structure to which some examples of the present disclosure may be applied.

[0386] Referring to FIG. 19, each transmission structure option can be transmitted immediately after the preamble. Additionally, a postamble can be transmitted immediately after the transmission of each transmission structure option.

[0387] For example, if a PRDCH transmission or PDRCH transmission based on the transmission structure of option a or option b is performed including a preamble and a postamble, it may be based on a structure such as that shown in FIG. 20.

[0388] FIG. 20 illustrates a preamble / postamble and PRDCH / PDRCH transmission to which some examples of the present disclosure may be applied.

[0389] Referring to FIG. 20, R2D / D2R transmission may be performed based on the Manchester code method, which is an example, and may also be performed based on other methods. Additionally, the preamble and postamble illustrated in FIG. 20 may also correspond to an example. As a specific example, the D2R preamble may be transmitted consisting only of a clock acquisition portion for D2R timing acquisition without a start indicator. And / or, the postamble may be transmitted for a different length while maintaining a high voltage, or in the form of a specific sequence consisting of high voltage and low voltage. And / or, R2D / D2R transmission may be performed by transmitting only the preamble and PRDCH / PDRCH without a postamble.

[0390] Additionally, as illustrated in FIG. 19, L1 control information of R2D transmission may be transmitted based on one or more of the following methods.

[0391] (Method 2-1) L1 control information may exist at the end of the preamble as part of the R2D preamble. In this case, the chip duration of the L1 control information may be the same as the chip duration of the preamble. For example, L1 control information may be added immediately after the clock acquisition part of FIG. 20, and PRDCH may be transmitted thereafter. At this time, the structure of PRDCH transmission may be the same as option a or option b of FIG. 19. In the case of option b, PRDCH may start with L2 control information.

[0392] (Method 2-2) L1 control information may exist between the R2D preamble and the PRDCH. In this case, the structure of the PRDCH transmission may be the same as option c, option d, or option e of FIG. 19. In the case of option d, the L1 control information may be transmitted through a separate R2D control channel. In the case of option c or option e, the L1 control information may be transmitted in a separate part without a separate channel.

[0393] (Method 2-3) L1 control information may exist as part of PRDCH at the beginning of PRDCH. In this case, the chip section of L1 control information may be the same as the chip section of PRDCH. At this time, the structure of PRDCH transmission may be the same as option b of FIG. 19, and PRDCH may start with L1 control information.

[0394] FIG. 21 illustrates a MAC payload structure in PRDCH / PDRCH to which some examples of the present disclosure may be applied.

[0395] The MAC payload structure illustrated in FIG. 21 may be an example of the structure of the payload (e.g., MAC payload) in FIG. 19. Here, the MAC payload may correspond to a single transmission block (TB).

[0396] In options a, c, and d of FIG. 21, the L2 control information may or may not be located at the beginning of the MAC payload. In this case, whether the L2 control information is included in the L1 control information or the clock acquisition portion of the preamble described in FIG. 19 may be indicated. Alternatively, without separate indication, the MAC payload may always include or not include the L2 control information. Alternatively, whether the L2 control information is included in the first bit / field of the L2 control information or in the bit / field immediately preceding the L2 control information may be indicated. Alternatively, the L2 control information may be included in the MAC CE following the MAC subheader of FIG. 21. Additionally, padding may be added to the end portion of the payload of FIG. 21.

[0397] When a payload (e.g., TB) is configured at the MAC layer as shown in FIG. 21, the payload can be transmitted to the physical layer, and the physical layer can configure PRDCH or PDRCH by adding a CRC to the payload. At this time, L1 control information, L2 control information, or whether a CRC is added to TB can be indicated in the MAC CE. And / or, in FIG. 21, the L2 control information can be classified as a specific MAC CE located before the payload (always) or as a MAC header.

[0398] FIG. 22 illustrates the repeated transmission of PDRCH according to one embodiment of the present disclosure.

[0399] FIG. 22 illustrates a case where a midamble is indicated between two consecutive PDRCH repeated transmissions by L1 / L2 control information in the R2D direction or L1 / L2 control information in the D2R direction.

[0400] Referring to FIG. 22, in the repeated transmissions of PDRCH, a (D2R) preamble may be transmitted before the first PDRCH transmission begins. A (D2R) midamble may be included between two consecutive PDRCH transmissions, and a (D2R) postamble may be transmitted after the last PDRCH transmission.

[0401] Meanwhile, although FIG. 22 illustrates only the repeated transmission of PDRCH, the repeated transmission of PRDCH can also be performed with the same structure.

[0402] Control information for Ambient IoT (AmIoT)-based communication and x-Ambble configuration instructions based on said control information

[0403] The present disclosure proposes a method for configuring / defining control information related to D2R transmission (e.g., PDRCH transmission) for ambient IoT-based communication. In addition, the present disclosure proposes a method for instructing x-amble configuration (e.g., x-amble configuration in D2R transmission) based on said control information.

[0404] A reader transmitting a PRDCH may or may not include L1 control information (L1CI) within the PRDCH. In this case, the L1CI transmitted via the R2D method, i.e., the R2D L1CI, may include control information for PRDCH transmission and / or control information for PDRCH transmission.

[0405] Additionally, the reader transmitting the PRDCH may or may not include L2 control information (L2CI) within the PRDCH. In this case, the L2CI transmitted via the R2D method, i.e., the R2D L2CI, may include control information for PRDCH transmission and / or control information for PDRCH transmission.

[0406] Additionally, a device transmitting a PDRCH (e.g., an AmIoT device) may or may not include L1 control information (L1CI) within the PDRCH. In this case, the L1CI transmitted via the D2R method, i.e., the D2R L1CI, may include control information for the PDRCH transmission, control information for the PRDCH transmission (e.g., a subsequent PRDCH transmission), and / or information for reporting to a reader.

[0407] Additionally, a device transmitting a PDRCH (e.g., an AmIoT device) may or may not include L2 control information (L2CI) within the PDRCH. In this case, the L2CI transmitted via the D2R method, i.e., the D2R L2CI, may include control information for the PDRCH transmission, control information for the PRDCH transmission (e.g., a subsequent PRDCH transmission), and / or information for reporting to a reader.

[0408] In this regard, the information reported to the reader may include buffer status, remaining D2R data size, device energy status / level, etc. Additionally, L2CI may be the MAC CE, MAC header / sub-header, or a part thereof included in the MAC PDU.

[0409] Based on one or more of the embodiments described below, the reader and / or device can transmit and receive control information (CI) transmitted via the R2D method, i.e., R2D CI, and / or CI transmitted via the D2R method, i.e., D2R CI.

[0410] In this case, if the total size of the control information (CI) is variable (e.g., see Example 2 and Example 2), the reader or device decoding it may first decode information indicating the CI length (e.g., length indicator) before decoding the entire CI, and then decode the entire CI. Alternatively, if the size of the CI is fixed at a maximum size but only some field(s) included in the CI are valid (e.g., see Example 3 and Option 3B of Example 3), the entire CI containing information indicating the CI length may be decoded at once, and then only the valid field(s) among them may be stored / used. In this case, the reader or device receiving it may treat the invalid field(s) as reserved or all zero values. Alternatively, the reader or device receiving it may treat the field(s) that are reserved or all zero values ​​as invalid field(s).

[0411] The embodiments described below are distinguished solely for the sake of clarity and convenience of explanation; some embodiments may be applied in combination with other embodiments, and each embodiment may be applied independently.

[0412] Example 1

[0413] This embodiment relates to a method for indicating the existence of control information (CI), specifically D2R CI, transmitted via the D2R method.

[0414] The reader or device may indicate whether a CI exists within the PDRCH based on one or more of the options described below. Such option(s) may indicate only the presence of L1CI, or may indicate the presence of L2CI instead of L1CI. Alternatively, such option(s) may indicate the presence of both L1CI and L2CI.

[0415] (Option 1) A method in which the reader indicates whether to transmit CI / payload / MAC header / MAC SDU within the PDRCH using an R2D preamble transmitted immediately before the PDRCH, or the device indicates whether to transmit CI / payload / MAC header / MAC SDU within the PDRCH using a D2R preamble transmitted immediately before the PDRCH.

[0416] With respect to Option 1, a specific part of the R2D preamble or D2R preamble may indicate the presence of CI / payload / MAC header / MAC SDU within the PDRCH. For example, the presence of CI / payload / MAC header / MAC SDU within the PDRCH may be indicated based on the length, pattern, and / or value of a specific part of the preamble. A device receiving the transmission of the R2D preamble may determine the presence of L1CI or L2CI within the PDRCH based on that specific part and may receive the CI and PDRCH based on this. A reader receiving the transmission of the D2R preamble may determine the presence of L1CI or L2CI within the PDRCH based on that specific part and may receive the CI and PDRCH based on this.

[0417] The specific part may be one, part, or whole of the start indicator, clock acquisition part, or a part added immediately after the clock acquisition part of the R2D preamble or D2R preamble. If the specific part is the added part, it may be the last part of the preamble, or the R2D preamble / D2R preamble part transmitted immediately before PRDCH / PDRCH.

[0418] (Option 2) A method in which a specific part of the corresponding PRDCH or PDRCH indicates whether CI / payload / MAC header / MAC SDU within the PDRCH is transmitted.

[0419] With respect to Option 2, a specific part of the corresponding PRDCH or PDRCH may indicate the presence of CI / payload / MAC header / MAC SDU within the PDRCH. For example, the presence (and transport structure) of CI / payload / MAC header / MAC SDU within the PDRCH may be indicated based on the length, pattern, and / or value of a specific part of the PRDCH or PDRCH. A device may determine the presence and transport structure of L1CI or L2CI within the PDRCH based on that specific part, and transmit the corresponding CI and PDRCH based on this. A reader may determine the presence and transport structure of L1CI or L2CI within the PDRCH based on that specific part, and receive the corresponding CI and PDRCH based on this.

[0420] The specific part may be located at the very beginning of the PRDCH or PDRCH, or on a specific bit / symbol / chip. If located at the very beginning, the part may be the first part of the PRDCH or PDRCH, or it may be the PRDCH or PDRCH part transmitted immediately after the R2D preamble / D2R preamble.

[0421] If information indicating the specific part and the CI transmission length (e.g., a length indicator) is transmitted separately, such information may be transmitted immediately after, after, immediately before, or before the specific part. In this case, the specific part and the information may be transmitted as the same CI within a single CI, transmitted separately within different CIs (e.g., L1CI and L2CI, or R2D CI and D2R CI), or transmitted separately within the preamble and CI. If the specific part indicates that the CI does not exist, the information indicating the CI transmission length may not be transmitted or may be set to a specific value. This specific value may be zero, the largest value, or the smallest value, and may indicate that no CI (and MAC payload) will be transmitted after this information.

[0422] (Option 3) A method in which the value of a specific part of the corresponding PRDCH or PDRCH indicates whether CI / payload / MAC header / MAC SDU within the PDRCH is transmitted (and the transmission structure as in Option 2) and the length of the CI transmission.

[0423] A specific value set in a specific part of the corresponding PRDCH or PDRCH may indicate the presence of CI / payload / MAC header / MAC SDU within the PDRCH (and a transmission structure such as Option 2). That specific part may be an L1CI length indicator indicating the length of L1CI within the PRDCH or PDRCH, or an L2CI length indicator indicating the length of L2CI within the PRDCH or PDRCH.

[0424] For example, a specific value of the L1CI length indicator can indicate whether an L1CI is transmitted within the PDRCH. As a specific example, a value of 00 of the L1CI length indicator can indicate that no L1CI exists within the PDRCH. Additionally, a value of 01 or 10 of the L1CI length indicator can indicate that an L1CI exists within the PDRCH and indicate the length of the L1CI information. In this case, the values ​​of 01 and 10 can indicate different L1CI lengths.

[0425] Additionally, a value of 11 for the L1CI length indicator indicates a future use where the L1CI can be extended if new features are added, and can be set to a reserved value in the current method. Alternatively, a value of 11 for the L1CI length indicator may indicate that the PDRCH transmission is terminated without a MAC payload immediately after the L1CI. That is, the value of 11 may indicate that the PDRCH consists only of the L1CI. Alternatively, a value of 11 for the L1CI length indicator may indicate that the PDRCH transmission is terminated without a postamble. That is, the value of 11 may indicate that the PDRCH consists only of the L1CI and the MAC payload.

[0426] For example, a specific value of the L2CI length indicator can indicate whether L2CI is transmitted within the PDRCH. As a specific example, a value of 00 of the L2CI length indicator can indicate that there is no L2CI within the PDRCH. Additionally, a value of 01 or 10 of the L2CI length indicator can indicate that there is an L2CI within the PDRCH and indicate the length of the L2CI information. In this case, the values ​​of 01 and 10 can indicate different L2CI lengths.

[0427] Additionally, a value of 11 for the L2CI length indicator indicates a future use where the L2CI can be extended if new features are added, and can be set to a reserved value in the current method. Alternatively, a value of 11 for the L2CI length indicator may indicate that the PDRCH transmission is terminated immediately after the L2CI without a MAC payload and MAC SDU. That is, the value of 11 may indicate that the MAC payload consists only of the L2CI. Alternatively, a value of 11 for the L2CI length indicator may indicate that the PDRCH transmission is terminated without a postamble.

[0428] In the method described above, if the L1CI length indicator indicates that L1CI does not exist, L1CI may contain only the L1CI length indicator. In this case, a MAC payload may not be transmitted immediately after L1CI or immediately after the L1CI length indicator, or a specific MAC payload (e.g., system information) may be transmitted. Subsequently, the PDRCH transmission may be terminated by transmitting a postamble without a MAC payload immediately after L1CI or the L1CI length indicator. Alternatively, the PDRCH transmission may be terminated immediately after L1CI or the L1CI length indicator. Alternatively, the PDRCH transmission may be terminated after transmitting a specific MAC payload of a fixed length immediately after L1CI or the L1CI length indicator. Alternatively, the PDRCH transmission may be terminated after transmitting a MAC payload and a postamble immediately after L1CI or the L1CI length indicator.

[0429] With respect to Option 3, a specific part may be located at the very beginning or very end of PRDCH, PDRCH, or L1CI, or may be located on a specific bit / symbol / chip. If the specific part is located at the very beginning, it may be the first part / field of PRDCH, PDRCH, or L1CI, or the first part / field of PRDCH, PDRCH, or L1CI transmitted immediately after the R2D preamble or D2R preamble.

[0430] The device can determine whether an L1CI or L2CI exists within the PDRCH based on the relevant specific portion, and can transmit the corresponding CI and PDRCH based on this. Additionally, the reader can determine whether an L1CI or L2CI exists within the PDRCH based on the relevant specific portion, and can receive the corresponding CI and PDRCH based on this.

[0431] In the aforementioned options, a specific part may be composed of one or N bits / symbols / chips. A single chip may be composed of one high voltage and one low voltage.

[0432] For example, if transmission is performed at low voltage and / or high voltage for a specific length, the low voltage and / or high voltage of the specific length may indicate whether L1CI is present within the PDRCH. As a specific example, a low voltage and / or high voltage of K chip / symbol lengths may indicate that L1CI is present within the PDRCH, and a low voltage and / or high voltage of L chip / symbol lengths may indicate that L1CI is not present within the PDRCH.

[0433] As another example, specific patterns of low and / or high voltages can indicate whether L1CI is present within the PDRCH. Specifically, if a specific section consists of low-high-high-low voltages, it indicates the presence of L1CI within the PDRCH, and if a specific section consists of high-low-low-high voltages, it indicates the absence of L1CI within the PDRCH.

[0434] As another example, if transmission according to a specific pattern of low voltage and / or high voltage is performed for a specific length, the presence of L1CI within the PDRCH can be indicated through a combination of the specific pattern and the specific length.

[0435] In the aforementioned options, the PDRCH may be transmitted as a response to the PRDCH, or may be one of multiple PDRCHs transmitted after the PRDCH.

[0436] In the aforementioned options, a specific part may indicate one of the following D2R / PDRCH transmission structures, or one of the following D2R / PDRCH transmission structures may be determined by indicating the presence of CI / payload / MAC header / MAC SDU.

[0437] - Preamble only (no PDRCH)

[0438] - D2R LICI only

[0439] - D2R payload including D2R L1CI and L2CI

[0440] - D2R payload excluding D2R L1CI and L2CI

[0441] - D2R payload including L2CI only (D2R without L1CI)

[0442] - D2R payload only excluding L2CI (D2R no L1CI)

[0443] The device can determine the existence of L1CI or L2CI within the PDRCH and the transmission structure based on the specific part, and based on this, can transmit the corresponding CI and PDRCH.

[0444] The reader can determine the existence of an L1CI or L2CI within the PDRCH and the transmission structure based on the specific part, and based on this, can receive the corresponding CI and PDRCH.

[0445] Example 2

[0446] This embodiment relates to a method for indicating control information (CI) transmitted via D2R, namely the length (e.g., size) of the D2R CI.

[0447] A reader or device may indicate the length of control information (CI) within the PDRCH based on one or more of the options described below. Additionally, as described in Example 1, the reader or device may indicate the presence of the CI along with the CI length. The options described below may indicate only the length and / or presence of L1CI, or only the length and / or presence of L2CI instead of L1CI. Alternatively, both the length and / or presence of L1CI and L2CI may be indicated. In this case, the CI length may be the total number of bits / symbols / chips constituting the CI, or the number of information field(s) included in the CI.

[0448] (Option 1) Method in which the R2D preamble or D2R preamble transmitted immediately before the corresponding PRDCH or PDRCH indicates the CI length within the PDRCH

[0449] In relation to Option 1, a specific part of the R2D preamble or D2R preamble may indicate the length of the CI within the PDRCH. For example, the length of the CI within the PDRCH may be indicated based on the length, pattern, and / or value of a specific part of the preamble. A device receiving the transmission of the R2D preamble may determine the length of the L1CI or L2CI within the PDRCH based on that specific part and transmit the CI and PDRCH based on this. Additionally, a reader receiving the transmission of the D2R preamble may determine the length of the L1CI or L2CI within the PDRCH based on that specific part and receive the CI and PDRCH based on this.

[0450] The specific part may be one, part, or whole of the start indicator, clock acquisition part, or a part added immediately after the clock acquisition part of the R2D preamble or D2R preamble. If the specific part is the added part, it may be the last part of the R2D preamble or D2R preamble, or the R2D preamble part or D2R preamble part transmitted immediately before PRDCH or PDRCH.

[0451] (Option 2) A method in which a specific part of the corresponding PRDCH or PDRCH indicates the length of the CI within the PDRCH.

[0452] With respect to Option 2, a specific part of the corresponding PRDCH or PDRCH may indicate the length of the CI within the PDRCH. For example, the length of the CI within the PDRCH may be indicated based on the length, pattern, and / or value of that specific part. The device may determine the length of the L1CI or L2CI within the PDRCH based on that specific part and transmit the corresponding CI and PDRCH based on this. The reader may determine the length of the L1CI or L2CI within the PDRCH based on that specific part and receive the corresponding CI and PDRCH based on this.

[0453] The specific part may be located at the very beginning of the PRDCH or PDRCH, or on a specific bit / symbol / chip. If located at the very beginning, the part may be the first part of the PRDCH or PDRCH, or it may be the PRDCH or PDRCH part transmitted immediately after the R2D preamble or D2R preamble.

[0454] (Option 3) A method in which the value of a specific part of the corresponding PRDCH or PDRCH indicates whether the CI within the PDRCH is transmitted and the length of the CI transmission.

[0455] Since the method is the same as Option 3 of Example 1, a redundant detailed description is omitted.

[0456] The device can determine whether an L1CI or L2CI exists within the PDRCH and its length based on the relevant specific part, and can transmit the corresponding CI and PDRCH based on this. The reader can determine whether an L1CI or L2CI exists within the PDRCH and its length based on the relevant specific part, and can receive the corresponding CI and PDRCH based on this.

[0457] In the aforementioned options, a specific part may be composed of one or N bits / symbols / chips. A single chip may be composed of one high voltage and one low voltage.

[0458] For example, if transmission is performed at low and / or high voltages for a specific length, the low and / or high voltages of that specific length may indicate the length of L1CI within the PDRCH. As a specific example, low and / or high voltages of K chip / symbol lengths may indicate that L1CI within the PDRCH is composed of a long length, and low and / or high voltages of L chip / symbol lengths may indicate that L1CI within the PDRCH is composed of a short length. Additionally, low and / or high voltages of M chip / symbol lengths may indicate that L1CI does not exist within the PDRCH. Therefore, low and / or high voltages of K chip / symbol lengths and L chip / symbol lengths may indicate that L1CI exists within the PDRCH.

[0459] As another example, specific patterns of low and / or high voltages can indicate the length of L1CI within the PDRCH. Specifically, if a specific section consists of low-high-high-low voltages, it may indicate that L1CI within the PDRCH is long, and if a specific section consists of high-low-low-high voltages, it may indicate that L1CI within the PDRCH is short. Additionally, if a specific section consists of high-low-low-low voltages, it may indicate that L1CI is not present within the PDRCH. Therefore, if a specific section consists of low-high-high-low voltages or high-low-low-low voltages, it may indicate that L1CI is present within the PDRCH.

[0460] As another example, if transmission according to a specific pattern of low voltage and / or high voltage is performed for a specific length, the length of the L1CI within the PDRCH can be indicated through a combination of the specific pattern and the specific length. Alternatively, the combination of the specific pattern and the specific length can indicate the presence of the L1CI within the PDRCH and, if present, the length of the L1CI.

[0461] Example 3

[0462] This embodiment relates to the alignment method of information fields within the control information (CI) transmitted via D2R, specifically the D2R CI.

[0463] L1CI or L2CI may be composed of one or more information fields. For example, R2D L1CI or L2CI may include information such as time / frequency domain resource allocation of PDRCH, TB (transport block) size, modulation and coding rate (e.g., MCS), chip duration, device ID, device group ID, etc. Additionally, D2R L1CI or L2CI may include information such as time / frequency domain resource allocation of PDRCH, TB size, modulation and coding rate (e.g., MCS), chip duration, device ID, device group ID, etc., or may include information such as buffer status, remaining D2R data size, device energy status / level, etc., which aid in PDRCH or PRDCH transmission transmitted after PDRCH.

[0464] At this time, the PDRCH encoding device can determine / verify the order in which the information fields included in the corresponding CI are arranged according to one or more options described below, and can transmit the CI and PDRCH based on this. Additionally, the reader decoding the PDRCH can determine / verify the order in which the information fields included in the corresponding CI are arranged according to one or more options described below, and can receive the CI and PDRCH based on this.

[0465] (Option 1) A method in which the sorting order of information fields within a CI is determined by the length of the CI.

[0466] The reader and the device can determine the length of the L1CI or L2CI according to the method described in Example 2, and can transmit and receive the corresponding CI and PDRCH according to the alignment method of the information fields within the CI mapped to the determined length.

[0467] For example, if the length of the CI is determined to be a short length, a long length, or a specific value, the information fields included in the CI may be arranged in a specific order based on the determined length. As a specific example, if the length of the L1CI is determined to be a short length or a first length value according to the method described in Example 2, the L1CI may consist only of time domain resource allocation or TB size. If the length of the L1CI is determined to be a long length or a second length value, the L1CI may include information fields arranged in the order of device ID (or device group ID), TB size (or time domain resource allocation), modulation, and coding rate.

[0468] (Option 2) How information fields within the CI indicate one of the candidates for the sort order

[0469] As with Options 2A / 2B described below, the CI order indicator of the R2D preamble or D2R preamble or PRDCH or PDRCH may indicate one of the candidates for the alignment order. In this case, the CI order indicator may be located immediately before, at the very beginning, at the very end, or immediately after the corresponding CI. For example, in the case of L1CI, the CI order indicator for the alignment order within L1CI, i.e., the L1CI order indicator, may be located immediately before (e.g., within the preamble), at the very beginning, at the very end, or immediately after the corresponding L1CI.

[0470] For example, if the L1CI sequence indicator indicates a first value, the L1CI may consist only of a time domain resource allocation or a TB size. If the L1CI sequence indicator indicates a second value, the L1CI may include information fields arranged in the order of device ID (or device group ID), TB size (or time domain resource allocation), modulation, and coding rate.

[0471] - Option 2A. A method in which the R2D preamble or D2R preamble transmitted immediately prior to the relevant PRDCH or PDRCH indicates the alignment method of information fields within the CI in the PDRCH; that is, a method in which the R2D preamble or D2R preamble performs the function of a CI order indicator.

[0472] In the case of Option 2A, a specific part of the R2D preamble or D2R preamble may function as a CI order indicator and may indicate the alignment method of information fields within the CI in the PDRCH. For example, the alignment method for information fields within the CI in the PDRCH may be indicated based on the length, pattern, and / or value of a specific part of the preamble. The device may determine the alignment method for information fields of L1CI or L2CI in the PDRCH based on said specific part and transmit the corresponding CI and PDRCH based on this. The reader may determine the alignment method for information fields of L1CI or L2CI in the PDRCH based on said specific part and receive the corresponding CI and PDRCH based on this.

[0473] The specific part may be one, part, or whole of the start indicator, clock acquisition part, or a part added immediately after the clock acquisition part of the R2D preamble or D2R preamble. If the specific part is the added part, it may be the last part of the preamble, or the preamble part transmitted immediately before PRDCH or PDRCH.

[0474] - Option 2B. A method in which a specific part of the said PRDCH or PDRCH indicates the alignment method of information fields within the CIs in the PDRCH; that is, a method in which a specific part of the PRDCH or PDRCH performs the function of a CI order indicator.

[0475] In the case of Option 2B, a specific part of the PRDCH or PDRCH may function as a CI order indicator and may indicate the alignment method of information fields within the CIs in the PDRCH. For example, the alignment method for information fields of the CIs in the PDRCH may be indicated based on the length, pattern, and / or value of a specific part of the PRDCH or PDRCH. The device may determine the alignment method for information fields of L1CI or L2CI within the PDRCH based on that specific part and transmit the CIs and PDRCH based on this. The reader may determine the alignment method for information fields of L1CI or L2CI within the PDRCH based on that specific part and receive the CIs and PDRCH based on this.

[0476] The specific part may be located at the very beginning of the PRDCH or PDRCH, or on a specific bit / symbol / chip. If located at the very beginning, the part may be the first part of the PRDCH or PDRCH, or it may be the PRDCH or PDRCH part transmitted immediately after the R2D preamble or D2R preamble.

[0477] (Option 3) Method of sorting information fields according to their priority / sorting order

[0478] Information fields within CI can be sorted based on the priority / sorting order of all pre-set / determined information fields.

[0479] For example, priority / sorting order can be predetermined / defined in the order of device ID, device group ID, time / frequency domain resource allocation, TB size, modulation and coding rate, and chip segment. In this case, if the information included in the CI includes only the device ID and TB size, the CI can be configured by sorting the information in the order of device ID and TB size.

[0480] - Option 3A. A field indicator may exist at the beginning of each information field to indicate whether the field is included. For example, there may be a total of N fields, and N 1-bit field indicators may indicate whether the field is included in CI.

[0481] For example, the priority / sorting order of all information fields can be determined in the order of Device ID, Device Group ID, Time / Frequency Domain Resource Allocation, TB Size, Modulation and Coding Rate, and Chip Section. In this case, a field indicator may be included at the beginning of each field for Device ID, Device Group ID, Time / Frequency Domain Resource Allocation, TB Size, Modulation and Coding Rate, and Chip Section within the CI. If a specific field is included in the CI, the field indicator for that field may indicate 1 (or 0), and if a specific field is not included in the CI, the field indicator for that field may indicate 0 (or 1). That is, a CI consisting only of Device ID and TB Size may be composed of "1"+"Device ID"+"000"+"1"+"TB Size"+"00".

[0482] The receiving reader can determine / verify, through each field indicator, what information the field represents and whether the field is included.

[0483] - Option 3B. A method in which the included information fields contain values ​​corresponding to the information in those fields, and the non-included fields contain specific values.

[0484] For example, the priority / sorting order of all information fields can be determined in the order of Device ID, Device Group ID, Time / Frequency Domain Resource Allocation, TB Size, Modulation and Coding Rate, and Chip Segment. If the information included in the CI consists only of Device ID and TB Size, the CI includes fields in the order of Device ID, Device Group ID, Time / Frequency Domain Resource Allocation, TB Size, Modulation and Coding Rate, and Chip Segment; the fields for Device ID and TB Size indicate the values ​​of the corresponding information, while the remaining fields (e.g., in the order of Device Group ID, Time / Frequency Domain Resource Allocation, Modulation and Coding Rate, and Chip Segment) may each indicate specific values. In this case, the specific value may indicate that the corresponding field is not included or is invalid. Additionally, the specific value for this purpose may be set identically or differently for each field.

[0485] Example 4

[0486] The present embodiment relates to a method for indicating an x-amble configuration (hereinafter referred to as D2R x-amble) associated with D2R transmission via an R2D CI and / or a D2R CI. Here, the x-amble may include a preamble, a midamble, and / or a postamble.

[0487] Example 4-1

[0488] First, I will explain how to specify input parameters for the D2R x-amble sequence generator using R2D CI.

[0489] In the following, a method is proposed for generating / determining a D2R sequence for a D2R transmission (e.g., D2R x-amble, D2R CI, or PDRCH) based on instructions from an R2D CI. In this case, the R2D CI triggering the D2R transmission may include / instruct configuration information (e.g., input parameters) for generating / determining the D2R sequence.

[0490] A device that receives an R2D CI from a reader can generate / determine a D2R sequence based on the corresponding configuration information and can perform a D2R transmission including the generated / determined D2R sequence.

[0491] In this regard, the R2D CI may indicate / determine configuration information including one or more indicated / determined input parameter(s) as shown in the example below. A device that receives such configuration information may generate / determine a D2R sequence as shown in the example below, according to the indicated / determined input parameter(s).

[0492] For example, the device can generate a circular / cyclic shift D2R sequence R according to the formula R(s)=f(s). Here, f(s) can be represented as the cyclic shift value s for the basic sequence. For the corresponding D2R sequence, the reader can indicate the value s via the R2D CI. Alternatively, the device can determine the value s based on R2D preamble transmission parameters or PRDCH transmission parameters (e.g., R2D preamble sequence, preamble length, chip interval, time occasion, frequency position, etc.).

[0493] As another example, the device can generate a D2R sequence R(c) using the value of sequence c as input. In this case, the initialization of sequence c can be executed according to the formula c_init=f(n). For the corresponding D2R sequence, the reader can specify the value of n, which is an input parameter for the initialization of sequence c, via the R2D CI. Alternatively, the device can determine the value of n based on R2D preamble transmission parameters or PRDCH transmission parameters (e.g., R2D preamble sequence, preamble length, chip interval, time occasion, frequency position, etc.).

[0494] As another example, the device may transmit a D2R sequence R(i) for the i-th sequence among multiple sequences stored in the device. For the corresponding D2R sequence, the reader may indicate the value of i via the R2D CI. Alternatively, the device may determine the value of i based on R2D preamble transmission parameters or PRDCH transmission parameters (e.g., R2D preamble sequence, preamble length, chip interval, time occasion, frequency position, etc.).

[0495] The aforementioned D2R sequence R can be generated / determined as a function of multiple input parameters. One, some, or all of the said multiple input parameters can be indicated / determined through R2D CI. In this case, some parameters not indicated / determined through R2D CI can be indicated / determined through D2R CI.

[0496] Additionally, the D2R sequence R can be expressed as R=f(m1, m2, m3, ...), and each m value may be the aforementioned s value, n value, or i value. Additionally or alternatively, the m value(s) may be one / some / all of the values ​​described below. All of the m value(s) may be indicated / determined through R2D CI, all may be indicated / determined through D2R CI, or some of the m value(s) may be indicated / determined through R2D CI and some may be indicated / determined through D2R CI.

[0497] 1) Leader's Leader ID value

[0498] A virtual / real ID value broadcast / directed by the corresponding reader via R2D, or an ID value determined (virtually or randomly) by the device.

[0499] 2) Start time of D2R transmission

[0500] A value determined based on the start time of the D2R preamble or the start time of the PDRCH, as the D2R transmission start time. Additionally or alternatively, a value instructed to the device by the reader, or determined by the device (within the time range instructed by the reader).

[0501] 3) Start / End time of R2D transmission

[0502] The start / end time of the R2D transmission that triggered the D2R transmission, which is the start / end time of the R2D preamble / midamble / postamble, or a value determined based on the start / end time of the PRDCH. Additionally or alternatively, a value instructed to the device by the reader, or determined by the device (within the time range instructed by the reader).

[0503] 4) Frequency position of R2D transmission

[0504] A value corresponding to the frequency position of the R2D transmission that triggered the D2R transmission (e.g., frequency index or modulo operation value for ARFCN). Additionally or alternatively, a value instructed to the device by the reader or determined by the device based on the reception of the R2D.

[0505] 5) Frequency position of D2R transmission

[0506] A value corresponding to the frequency position of the D2R transmission (e.g., a frequency index or a modulo operation value for ARFCN). Alternatively, a value corresponding to the difference between the frequency position of the R2D transmission that triggered the D2R transmission and the frequency position of the D2R transmission (e.g., a value corresponding to the frequency shift of the D2R transmission from the frequency position of the R2D transmission). Additionally, or alternatively, a value indicated to the device by the reader, a value determined by the device based on the D2R transmission, or a value determined by the device based on the R2D reception and the D2R frequency shift.

[0507] 6) Sequence ID (or arbitrary ID)

[0508] A base sequence ID value for sequence generation / determination. Alternatively, a sequence-based input ID value for sequence generation / determination. Additionally or alternatively, a value instructed to the device by the reader, a value determined by the device based on the corresponding D2R transmission, or a value determined by the device based on the corresponding R2D reception and D2R frequency shift.

[0509] 7) Device ID (or Device Group ID, Device Type ID)

[0510] A device-specific ID, the ID of the device group to which the device belongs, or the ID of the device type based on the capability supported by the device. Additionally or alternatively, a value instructed to the device by the reader, a value determined by the device based on the corresponding D2R transmission, or a value determined by the device based on the corresponding R2D reception and D2R frequency shift.

[0511] The values ​​described above are not limited to the descriptions / examples provided, and various variations or other parameters may be applied. Additionally, the values ​​described above may be used individually or in combination of two or more values.

[0512] Example 4-2

[0513] Next, we will explain how to specify input parameters for the D2R x-amble sequence generator using D2R CI.

[0514] In the following, a method is proposed for generating / determining a D2R sequence for a D2R transmission (e.g., D2R x-amble, D2R CI, or PDRCH) based on instructions from a D2R CI. In this case, the D2R CI may include / instruct configuration information (e.g., input parameters) for generating / determining the D2R sequence.

[0515] The device can generate / determine a D2R sequence based on the corresponding configuration information included in the D2R CI, and can perform a D2R transmission including the generated / determined D2R sequence.

[0516] In this regard, the D2R CI may indicate / determine configuration information including one or more indicated / determined input parameter(s) as shown in the example below. The device may generate / determine a D2R sequence according to the indicated / determined input parameter(s) as shown in the example below.

[0517] For example, the device can generate a circular / cyclic shift D2R sequence R according to the formula R(s)=f(s), where f(s) can be represented as a cyclic shift value s for a basic sequence. For the corresponding D2R sequence, the value s can be indicated via the D2R CI. Alternatively, the device can determine the value s based on D2R preamble transmission parameters or PDRCH transmission parameters (e.g., D2R preamble sequence, preamble length, chip interval, time occasion, frequency position, etc.). Alternatively, the device can determine the value s based on R2D preamble transmission parameters or PRDCH transmission parameters (e.g., R2D preamble sequence, preamble length, chip interval, time occasion, frequency position, etc.).

[0518] As another example, the device may generate a D2R sequence R(c) using the value of sequence c as input. In this case, the initialization of sequence c may be executed according to the formula c_init=f(n). For the corresponding D2R sequence, the value of n, which is an input parameter for the initialization of sequence c, may be specified via the D2R CI. Alternatively, the device may determine the value of n based on D2R preamble transmission parameters or PDRCH transmission parameters (e.g., D2R preamble sequence, preamble length, chip interval, time occasion, frequency position, etc.). Alternatively, the device may determine the value of n based on R2D preamble transmission parameters or PRDCH transmission parameters (e.g., R2D preamble sequence, preamble length, chip interval, time occasion, frequency position, etc.).

[0519] As another example, the device may transmit a D2R sequence R(i) for the i-th sequence among multiple sequences stored in the device. For the corresponding D2R sequence, the value of i may be indicated via the D2R CI. Alternatively, the device may determine the value of i based on D2R preamble transmission parameters or PDRCH transmission parameters (e.g., D2R preamble sequence, preamble length, chip interval, time occasion, frequency position, etc.). Alternatively, the device may determine the value of i based on R2D preamble transmission parameters or PRDCH transmission parameters (e.g., R2D preamble sequence, preamble length, chip interval, time occasion, frequency position, etc.).

[0520] The aforementioned D2R sequence R can be generated / determined as a function of multiple input parameters. One, some, or all of the said multiple input parameters can be indicated / determined through D2R CI. In this case, some parameters not indicated / determined through D2R CI can be indicated / determined through R2D CI.

[0521] Additionally, the D2R sequence R can be expressed as R=f(m1, m2, m3, ...), and each m value may be the aforementioned s value, n value, or i value. Additionally or alternatively, the m value(s) may be one / some / all of the values ​​described below. All of the m value(s) may be indicated / determined through R2D CI, all may be indicated / determined through D2R CI, or some of the m value(s) may be indicated / determined through R2D CI and some may be indicated / determined through D2R CI.

[0522] 1) Leader's Leader ID value

[0523] A virtual / real ID value broadcast / directed by the corresponding reader via R2D, or an ID value determined (virtually or randomly) by the device.

[0524] 2) Start time of D2R transmission

[0525] A value determined based on the start time of the D2R preamble or the start time of the PDRCH, as the D2R transmission start time. Additionally or alternatively, a value instructed to the device by the reader, or determined by the device (within the time range instructed by the reader).

[0526] 3) Start / End time of R2D transmission

[0527] The start / end time of the R2D transmission that triggered the D2R transmission, which is the start / end time of the R2D preamble / midamble / postamble, or a value determined based on the start / end time of the PRDCH. Additionally or alternatively, a value instructed to the device by the reader, or determined by the device (within the time range instructed by the reader).

[0528] 4) Frequency position of R2D transmission

[0529] A value corresponding to the frequency position of the R2D transmission that triggered the D2R transmission (e.g., frequency index or modulo operation value for ARFCN). Additionally or alternatively, a value instructed to the device by the reader or determined by the device based on the reception of the R2D.

[0530] 5) Frequency position of D2R transmission

[0531] A value corresponding to the frequency position of the D2R transmission (e.g., a frequency index or a modulo operation value for ARFCN). Alternatively, a value corresponding to the difference between the frequency position of the R2D transmission that triggered the D2R transmission and the frequency position of the D2R transmission (e.g., a value corresponding to the frequency shift of the D2R transmission from the frequency position of the R2D transmission). Additionally, or alternatively, a value indicated to the device by the reader, a value determined by the device based on the D2R transmission, or a value determined by the device based on the R2D reception and the D2R frequency shift.

[0532] 6) Sequence ID (or arbitrary ID)

[0533] A base sequence ID value for sequence generation / determination. Alternatively, a sequence-based input ID value for sequence generation / determination. Additionally or alternatively, a value instructed to the device by the reader, a value determined by the device based on the corresponding D2R transmission, or a value determined by the device based on the corresponding R2D reception and D2R frequency shift.

[0534] 7) Device ID (or Device Group ID, Device Type ID)

[0535] A device-specific ID, the ID of the device group to which the device belongs, or the ID of the device type based on the capability supported by the device. Additionally or alternatively, a value instructed to the device by the reader, a value determined by the device based on the corresponding D2R transmission, or a value determined by the device based on the corresponding R2D reception and D2R frequency shift.

[0536] The values ​​described above are not limited to the descriptions / examples provided, and various variations or other parameters may be applied. Additionally, the values ​​described above may be used individually or in combination of two or more values.

[0537] Example 4-3

[0538] This embodiment describes a method for indicating input parameters to a sequence generator of a D2R x-amble through R2D CI and D2R CI.

[0539] Specifically, a method may be applied in which the first input parameter(s) of the D2R x-amble sequence generator are indicated via R2D CI, and the second input parameter(s) of the D2R x-amble sequence generator are indicated via D2R CI.

[0540] The present method proposes a method for generating / determining a D2R sequence for a D2R transmission (e.g., D2R x-amble, D2R CI, or PDRCH) based on instructions from R2D CI and D2R CI. In this case, R2D CI and D2R CI may together include / instruct configuration information (e.g., input parameters) for generating / determining the corresponding D2R sequence.

[0541] The device can generate / determine a D2R sequence based on the corresponding configuration information included in the R2D CI and D2R CI, and can perform a D2R transmission including the generated / determined D2R sequence.

[0542] For example, the R2D CI can indicate / determine configuration information including one or more input parameter(s) (indicated / determined) as in the example described in Example 4-1, and the D2R CI can indicate / determine configuration information including one or more input parameter(s) (indicated / determined) as in the example described in Example 4-2. Based on this, the device can generate / determine a D2R sequence as in the example described above, according to the input parameter(s) indicated / determined by the R2D CI and the D2R CI. The input parameter(s) indicated / determined by the R2D CI and the D2R CI may be the same or different parameters.

[0543] Examples 4-4

[0544] This embodiment describes a method for indicating input parameters to a sequence generator of a D2R x-amble through an R2D CI, a D2R CI, and / or an R2D payload.

[0545] Specifically, a method may be applied in which the first and / or second input parameter(s) of the D2R x-amble sequence generator are indicated via R2D CI and D2R CI, and the third input parameter(s) of the D2R x-amble sequence generator are indicated via R2D payload.

[0546] The present method proposes a method for generating / determining a D2R sequence for a D2R transmission (e.g., D2R x-amble, D2R CI, or PDRCH) based on instructions of an R2D CI, a D2R CI, and / or an R2D payload. Here, the R2D CI is an L1CI and / or L2CI, the D2R CI is an L1CI and / or L2CI, and the R2D payload may be an L2CI (e.g., MAC CE or MAC header / subheader) and / or upper / higher layer signaling.

[0547] In this case, the R2D CI, D2R CI, and / or R2D payload may together include / indicate configuration information (e.g., input parameters) for generating / determining the corresponding D2R sequence.

[0548] The device can generate / determine a D2R sequence based on the R2D CI, D2R CI, and / or the corresponding configuration information included in the R2D payload, and can perform a D2R transmission including the generated / determined D2R sequence.

[0549] For example, the R2D CI may indicate / determine configuration information including one or more input parameter(s) (indicated / determined) as in the example described in Example 4-1, and the D2R CI may indicate / determine configuration information including one or more input parameter(s) (indicated / determined) as in the example described in Example 4-2. Additionally, the R2D payload may indicate / determine configuration information including one or more input parameter(s) by replacing the R2D CI in the example described in Example 4-1 with the R2D payload or a MAC CE / header / subheader within the payload. Based on this, the device may generate / determine a D2R sequence as in the example described above according to the input parameter(s) indicated / determined in the R2D CI, D2R CI, and / or R2D payload. The input parameter(s) indicated / determined by the R2D CI, D2R CI, and / or R2D payload may be the same or different parameters.

[0550] As stated above, the embodiments of the present disclosure are described separately merely for convenience and clarity of explanation, and the proposed methods described in the embodiments may be combined, merged, or substituted for one another.

[0551] FIGS. 23 and 24 illustrate the operation of a device and a network node in relation to a method of performing AmIoT communication according to the embodiments of the present disclosure described above.

[0552] In FIGS. 23 and 24, the first device and / or the second device may correspond to any one of a base station, an intermediate node (IN), an auxiliary node (AN), a terminal, or an AmIoT device, respectively, based on various topologies in AmIoT communication. For example, in FIGS. 23 and 24, based on topology 1 / 2, the first device may correspond to an AmIoT device, and the second device may correspond to a leader (e.g., a base station, an intermediate node (IN), an auxiliary node (AN), or a terminal).

[0553] FIG. 23 illustrates the operation of a first device according to an embodiment of the present disclosure.

[0554] Referring to FIG. 23, the first device can identify the second device (S2310) and can perform D2R transmission for the identified second device (S2320).

[0555] For example, the first device can identify the second device by performing a search procedure and a synchronization procedure for the surroundings, and can perform a synchronization procedure with the second device.

[0556] In this regard, at least one of sequence information of an amble signal associated with a D2R transmission, timing information of an R2D transmission to be received following the D2R transmission (e.g., information related to the start / end time of the R2D transmission), or frequency information of the R2D transmission may be indicated based on the D2R transmission.

[0557] According to the present disclosure, an amble signal associated with D2R transmission may include at least one of a D2R preamble, a D2R midamble, or a D2R postamble.

[0558] Additionally, according to the present disclosure, the sequence information may be associated with input parameters for generating a sequence of amble signals associated with D2R transmission.

[0559] For example, if the sequence of the corresponding amble signal is generated through a cyclic shift method, the sequence information may correspond to a cyclic shift value for a base sequence. As another example, if the sequence of the corresponding amble signal is generated through a sequence initialization method, the sequence information may correspond to an input parameter value for initializing the sequence. As yet another example, if the sequence of the corresponding amble signal is selected from among a plurality of sequences stored in the first device, the sequence information may correspond to an identifier for the selected sequence.

[0560] Additionally, according to the present disclosure, the sequence information may include an identifier for a second device. The identifier for the second device may be indicated by the second device or determined by the first device.

[0561] Additionally, according to the present disclosure, the sequence information may include at least one of an identifier for a first device, an identifier for a device group to which the first device belongs, or an identifier for a device type of the first device.

[0562] Additionally, according to the present disclosure, at least one of the aforementioned sequence information, timing information, or frequency information may be indicated through D2R control information (e.g., D2R L1CI, D2R L2CI) associated with the D2R transmission.

[0563] The method described in the example of FIG. 23 can be performed by the wireless device (200) of FIG. 3. That is, the first device of FIG. 23 can be implemented as the wireless device (200). For example, one or more processors (202) of the wireless device (200) of FIG. 3 can be configured to identify a second device and perform D2R transmission to the second device.

[0564] Furthermore, one or more memories (204) of the wireless device (200) may store instructions for performing the method described in the example of FIG. 23 or the examples described above when executed by one or more processors (202).

[0565] FIG. 24 illustrates the operation of a second device according to an embodiment of the present disclosure.

[0566] Referring to FIG. 24, the second device may receive at least one of a channel or signal related to D2R transmission to the second device from the first device (S2410), and subsequently, may perform R2D transmission to the first device (S2420).

[0567] In this regard, at least one of sequence information of an amble signal associated with a D2R transmission, timing information of an R2D transmission to be received following the D2R transmission (e.g., information related to the start / end time of the R2D transmission), or frequency information of the R2D transmission may be indicated based on the D2R transmission.

[0568] In the example of FIG. 24, the specific features regarding the amble signal, sequence information, timing information, frequency information, and settings / instructions for the information related to D2R transmission are the same as those described with reference to FIG. 23, so redundant descriptions are omitted.

[0569] The method described in the example of FIG. 24 can be performed by the wireless device (200) of FIG. 3. That is, the network node of FIG. 24 can be implemented as the wireless device (200). For example, one or more processors (202) of the wireless device (200) of FIG. 3 can be configured to receive a D2R transmission to a second device and to perform an R2D transmission to a first device following the said D2R transmission.

[0570] Furthermore, one or more memories (204) of the wireless device (200) may store instructions for performing the method described in the example of FIG. 24 or the examples described above when executed by one or more processors (202).

[0571] FIGS. 25 through 27 relate to types and configurations of AmIoT devices to which some examples of the present disclosure may be applied. Each of the devices 1, 2a, and 2b of FIGS. 25 through 27 may correspond to each of the device types 1, 2, and 3 described above in the present disclosure.

[0572] Device 1 may be collectively referred to as a device having a peak power consumption of 1 μW or less, capable of storing energy, having an initial sampling frequency offset (SFO) of up to 10X ppm, and having no DL or UL amplification function. The UL transmission of Device 1 may be backscattered from an externally provided carrier wave.

[0573] Device 2a has a peak power consumption of less than several hundred μW, can store energy, has an initial sampling frequency offset (SFO) of up to 10X ppm, and can have DL and / or UL amplification capabilities. The UL transmission of device 2a can be backscattered from an externally provided carrier wave.

[0574] Device 2b has a peak power consumption of less than several hundred μW, can store energy, has an initial sampling frequency offset (SFO) of up to 10X ppm, and can have DL and / or UL amplification capabilities. The device's UL transmission can be generated internally within the device.

[0575] FIG. 25 relates to the configuration of device 1 to which some examples of the present disclosure may be applied. As an example of the present disclosure, as illustrated in FIG. 25, device 1 may include at least one of an antenna, a matching network, an RF energy harvester, an energy storage, a power management unit, digital BB logic, a memory, a clock generator, a receiving block, and a transmitting block.

[0576] The antenna may be shared or separated for the RF energy harvester and the receiver / transmitter. A matching network may match the impedance between the antenna and other components (e.g., including blocks related to the RF energy harvester and receiver). The RF energy harvester may include a rectifier that converts the RF signal (AC) into DC.

[0577] An energy storage unit (e.g., a capacitor) can store energy harvested from an RF energy harvester. A power management unit (PMU) can store energy from the energy harvester into the energy storage unit and supply power to active component blocks that require power supply.

[0578] Digital BB logic may include functional blocks such as encoders, decoders, and controllers. Memory may include 1) non-volatile memory (NVM), such as EEPROM, for permanently storing device IDs, etc., and 2) registers for temporarily storing information necessary for operation only while energy is available in the energy storage. A clock generator may provide the necessary clock signal.

[0579] The receiving block may include an RF BPF, an RF envelope detector, a baseband LPF, and a comparator. An RF BPF may be used to improve selectivity; however, the RF BPF may not be present depending on the implementation. RAN4 RF requirements (if present, e.g., ACS) and peak power consumption targets may be considered. An RF envelope detector may convert the RF signal to baseband. A baseband LPF may improve the quality of the input signal to the comparator by filtering out harmonics and high-frequency components; however, the baseband LPF may not be present depending on the implementation. The comparator may determine the high / low of the input signal.

[0580] The transmission-related block may include a backscatter modulator. The backscatter modulator can switch the impedance to modulate the backscatter signal with the transmission signal of the BB logic. The waveform / modulation type is FFS.

[0581] FIG. 26 relates to the configuration of device 2a to which some examples of the present disclosure may be applied. As an example of the present disclosure, as illustrated in FIG. 26, device 2a may include at least one of an antenna, a matching network, an energy harvester, an energy storage unit, a power management unit, digital BB logic, a memory, a clock generator, a reflection amplifier, a receiving block, and a transmitting block.

[0582] A reflection amplifier can amplify the reflected backscattering signal. At least one of R2D / CW2D and D2R can be amplified by a reflection amplifier or an LNA.

[0583] The receiving block may include at least one of an RF band-pass filter (BPF), a low noise amplifier (LNA), an RF envelope detector, a BB amplifier, a BB low-pass filter (LPF), a comparator, or an N-bit analog-to-digital converter (ADC).

[0584] An LNA can be used to improve the signal strength and sensitivity of the receiver, and at least one of R2D / CW2D and D2R can be amplified by a reflection amplifier or an LNA. An RF envelope detector (RF-ED) can detect the envelope in the RF signal. A BB amplifier can improve signal strength by amplifying the BB signal. A BB LPF can improve the input signal quality to the comparator / ADC by filtering harmonics and high-frequency components.

[0585] The transmission-related block may include a backscatter modulator and a large frequency shifter. The backscatter modulator can modulate the backscatter signal into the transmission signal of the BB logic by switching the impedance. A large frequency shifter may be used to shift the backscatter signal from one frequency (e.g., FDD-DL frequency) to another frequency (e.g., FDD-UL frequency).

[0586] Since the overlapping configuration between device 2a and device 1 has been described in FIG. 25, the overlapping description is omitted.

[0587] FIG. 27 relates to the configuration of device 2b to which some examples of the present disclosure may be applied. As an example of the present disclosure, as illustrated in FIG. 27, device 2b may include at least one of an antenna, a matching network, an energy harvester, an energy storage unit, a power management unit, digital BB logic, a memory, a clock generator, a receiving block, and a transmitting block. Here, the energy harvester may harvest energy from RF signals, the sun, vibrations / movements, temperature differences, etc.

[0588] The receiving block may include an RF BPF, an LNA, an RF envelope detector, a BB amplifier, a BB LPF, a comparator, and an N-bit ADC. The transmitting block may include at least one of a transmitting modulator, a DAC, a low-pass filter, a mixer, a local oscillator, and a power amplifier.

[0589] Baseband bits can be modulated by a modulator depending on the modulation scheme. Baseband blocks can be part of BB logic. A digital-to-analog converter (DAC) can convert a digital signal into an analog signal. A low-pass filter can filter out unwanted signals. A mixer can convert a baseband signal to the RF range. A local oscillator can generate a carrier frequency. A power amplifier (PA) can amplify the transmitted signal.

[0590] In describing the present disclosure, each of the configurations in FIGS. 25 to 27 may be included in at least one transceiver illustrated in FIG. 3.

[0591] The embodiments described above of the present disclosure may be applied independently. Additionally or alternatively, all or part of each operation of the embodiments described above of the present disclosure may be performed in combination.

[0592] Although the method proposed in this disclosure has been described with an example applied to 3GPP LTE / LTE-A, 5G, and 6G systems, it is possible to apply it to various wireless communication systems in addition to 3GPP LTE / LTE-A, 5G, and 6G systems.

Claims

A step of identifying a second device by a first device; and The method includes the step of performing a D2R (device-to-reader) transmission to the second device by the first device, wherein A method in which at least one of sequence information of an amble signal associated with the D2R transmission, timing information of an R2D transmission to be received following the D2R transmission, or frequency information of the R2D transmission is indicated based on the D2R transmission. In paragraph 1, A method in which the amble signal associated with the above D2R transmission comprises at least one of a D2R preamble, a D2R midamble, or a D2R postamble. In paragraph 1, A method in which the above sequence information relates to input parameters for generating the sequence of the above amble signal. In paragraph 3, A method in which, based on the fact that the sequence of the above ambulance signal is generated through a cyclic shift method, the sequence information corresponds to a cyclic shift value for the base sequence. In paragraph 3, A method based on the fact that the sequence of the above ambulance signal is generated through a sequence initialization method, wherein the sequence information corresponds to an input parameter value for the initialization of the sequence. In paragraph 3, A method in which, based on the selection of a sequence of the above ambulance signals from among a plurality of sequences stored in the first device, the sequence information corresponds to an identifier for the selected sequence. In paragraph 3, The above sequence information includes an identifier for the second device, and A method in which an identifier for the second device is indicated by the second device or determined by the first device. In paragraph 3, A method comprising at least one of the sequence information including an identifier for the first device, an identifier for the device group to which the first device belongs, or an identifier for the device type of the first device. In paragraph 1, A method in which the above timing information includes information related to the start or end time of the R2D transmission. In paragraph 1, A method in which at least one of the sequence information, the timing information, or the frequency information is indicated through D2R control information associated with the D2R transmission. In paragraph 1, The first device above corresponds to a device in ambient Internet of Things communication, and The above-mentioned second device corresponds to a reader in ambient IoT communication, and is a method corresponding to a reader that is a base station or an intermediate node. One or more transceivers; and It includes one or more processors connected to the above one or more transmitters and receivers, and The above one or more processors are: Identifying the second device by the first device; The first device is configured to perform a D2R (device-to-reader) transmission to the second device, wherein A device in which at least one of sequence information of an amble signal associated with the D2R transmission, timing information of an R2D transmission to be received following the D2R transmission, or frequency information of the R2D transmission is indicated based on the D2R transmission. A step of receiving at least one of a channel or signal associated with a device-to-reader (D2R) transmission from a first device to the second device by a second device; and The method includes the step of performing an R2D transmission to the first device following the D2R transmission by the second device, wherein A method in which at least one of sequence information of an amble signal associated with the D2R transmission, timing information of the R2D transmission, or frequency information of the R2D transmission is indicated based on the D2R transmission. One or more transceivers; and It includes one or more processors connected to the above one or more transmitters and receivers, and The above one or more processors are: By the second device, at least one of a channel or signal associated with a D2R (device-to-reader) transmission from the first device to the second device is received; The second device is configured to perform an R2D transmission to the first device following the D2R transmission, wherein A device in which at least one of sequence information of an amble signal associated with the D2R transmission, timing information of the R2D transmission, or frequency information of the R2D transmission is indicated based on the D2R transmission. One or more processors; and A processing device comprising one or more computer memories that are operably connected to one or more processors and store instructions for performing a method according to any one of claims 1 to 11 based on execution by one or more processors. One or more non-transitory computer-readable media storing one or more instructions that are executed by one or more processors to control the execution of a method according to any one of claims 1 through 11.

Citation Information

Patent Citations

  • Narrowband internet-of-things (NB-IOT) enhacements

    US20200314760A1

Cited By

  • Frequency hopping for ambient internet of things reader-to-device repetitions

    US20260213783A1