Method for wireless communication and device therefor

By introducing defined states and energy harvesting methods for ambient IoT devices, the method improves signal transmission and reception efficiency and accuracy, addressing energy limitations in wireless communication systems.

WO2026029494A1PCT designated stage Publication Date: 2026-02-05LG ELECTRONICS INC

Patent Information

Application Number
PCT/KR2025/011077
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-08-02
Filing Date
2025-07-25
Publication Date
2026-02-05

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in accurately and efficiently transmitting and receiving signals, particularly for ambient IoT devices with limited energy storage, where energy harvesting techniques are needed to support operation in environments without separate power supplies.

Method used

Implementing OFF/ON/SLEEP states for ambient IoT devices with defined transition conditions and energy harvesting methods based on signal monitoring and energy level thresholds, using synchronization signals for time synchronization and power management.

Benefits of technology

Enhances signal transmission and reception accuracy and efficiency by managing device states for ambient IoT devices, enabling effective energy harvesting and reducing power consumption.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2025011077_05022026_PF_FP_ABST
    Figure KR2025011077_05022026_PF_FP_ABST
Patent Text Reader

Abstract

According to an embodiment of the present disclosure, a first apparatus: monitors a first signal transmitted by a second apparatus in a first state; switches from the first state to a second state on the basis of at least one of the first signal or information about an energy level of the first apparatus; and performs energy harvesting for charging the first apparatus with energy on the basis of a second signal received in the second state, wherein the first signal may include a synchronization signal, and the information about the energy level of the first apparatus may be related to at least one of whether the energy of the first apparatus is less than a first threshold value or whether a ratio between the energy and the maximum energy of the first apparatus is less than a second threshold value.
Need to check novelty before this filing date? Find Prior Art

Description

Method for wireless communication and device therefor

[0001] The present disclosure relates to wireless communication, and more particularly, to a method for transmitting or receiving signals between various devices in a wireless communication system and a device therefor.

[0002] The 5G mobile communications system, the successor to LTE (long-term evolution), is a new, clean-slate mobile communications system characterized by high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, from low-frequency bands below 1 GHz, to intermediate-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz. 6G mobile communications systems are being developed based on the underlying technologies of 5G mobile communications.

[0003] Recently, research is being conducted on ambient IoT (Internet of Things) communications in NR standardization. Ambient IoT devices have limited energy storage, and energy harvesting techniques are being considered to support operation in environments where separate power supplies are difficult to connect. Energy harvesting allows ambient IoT devices to collect energy from the surrounding environment, convert it into electricity, and recharge their energy storage. Wireless signals are being discussed as a primary energy source for energy harvesting.

[0004] The technical challenge of this specification is to provide a method for more accurately and efficiently transmitting and receiving signals between wireless communication devices. For example, OFF / ON / SLEEP states for AmIoT devices can be introduced, and conditions for transitioning between each state and operating methods for AmIoT devices in each state can be provided.

[0005] In addition to the technical challenges described above, other technical challenges can be inferred from the description below.

[0006] According to one aspect of the present disclosure, a method performed in a first device includes monitoring a first signal transmitted by a second device in a first state; transitioning from the first state to a second state based on at least one of the first signal or information about an energy level of the first device; and performing energy harvesting for charging energy of the first device based on a second signal received in the second state, wherein the first signal includes a synchronization signal, and the information about the energy level of the first device may be related to at least one of whether energy of the first device is less than a first threshold or whether a ratio between energy of the first device and a maximum energy is less than a second threshold.

[0007] The first device may operate based on a first clock in the first state, and may operate based on a second clock that consumes less power than the first clock in the second state.

[0008] The first device can monitor a wake-up signal (WUS) based on the second clock in the second state.

[0009] The first device can receive information about at least one of the first threshold or the second threshold from the second device.

[0010] The first device can switch to the second state after adjusting time synchronization based on the synchronization signal.

[0011] The first device can transmit information related to a point in time when the first device returns from the second state to the first state to the second device.

[0012] The first device can determine when to return from the second state to the first state based on energy consumed in the first state before transitioning to the first state.

[0013] The time period for operating in the second state can be determined depending on whether the synchronization signal is a first synchronization signal or a second synchronization signal transmitted with a longer period than the first synchronization signal.

[0014] The first state may be an ON-state, and the second state may be a SLEEP-state.

[0015] The first device may be an ambient IoT (Internet of Things) device, and the second device may be a reader device.

[0016] According to another aspect of the present disclosure, a non-transitory computer-readable recording medium having recorded thereon a program for performing the method described above may be provided.

[0017] According to another aspect of the present disclosure, a first device includes a memory configured to store instructions; and a processor configured to perform operations by executing the instructions, the operations including: monitoring a first signal transmitted by a second device in a first state; transitioning from the first state to a second state based on at least one of the first signal or information about an energy level of the first device; and performing energy harvesting for charging energy of the first device based on a second signal received in the second state, wherein the first signal includes a synchronization signal, and the information about the energy level of the first device may be related to at least one of whether energy of the first device is less than a first threshold or whether a ratio between energy of the first device and a maximum energy is less than a second threshold.

[0018] The above first device may further include a transceiver.

[0019] The first device may be an ambient IoT (internet of things) device or a processing device configured to control the ambient IoT device.

[0020] According to another aspect of the present disclosure, a method performed by a second device comprises transmitting a first signal to the first device in a first state of the first device; and transmitting a second signal for energy harvesting of the first device in a second state of the first device, wherein the second device determines that the first device has transitioned from the first state to the second state based on at least one of the transmission of the first signal or information about an energy level of the first device, wherein the first signal comprises a synchronization signal, and the information about the energy level of the first device may relate to at least one of whether energy of the first device is less than a first threshold or whether a ratio between energy of the first device and a maximum energy is less than a second threshold.

[0021] According to another aspect of the present disclosure, a second device comprises a memory configured to store instructions; and a processor configured to perform operations by executing the instructions, the operations including transmitting a first signal to a first device in a first state of the first device; and transmitting a second signal for energy harvesting of the first device in a second state of the first device, wherein the second device determines that the first device has transitioned from the first state to the second state based on at least one of the transmission of the first signal or information about an energy level of the first device, wherein the first signal comprises a synchronization signal, and the information about the energy level of the first device may relate to at least one of whether energy of the first device is less than a first threshold or whether a ratio between energy of the first device and a maximum energy is less than a second threshold.

[0022] The first state may be an ON-state, and the second state may be a SLEEP-state.

[0023] The above second device may be a reader device.

[0024] In one embodiment, signals can be transmitted and received more accurately and efficiently between wireless communication devices. For example, the state ambiguity of an AmIoT device can be resolved by allowing the AmIoT device to transition and operate according to defined OFF / ON / SLEEP states, thereby enabling more accurate and efficient signal transmission and reception between the AmIoT device and a reader (or network).

[0025] In addition to the technical effects described above, other technical effects can be inferred from the description below.

[0026] Figure 1 illustrates a flexible network topology to which some examples of this specification may be applied.

[0027] FIG. 2 illustrates an example of a communication system applicable to the present disclosure.

[0028] FIG. 3 illustrates an example of a wireless device applicable to the present disclosure.

[0029] FIG. 4 illustrates a communication procedure between a first node (e.g., a terminal) and a second node (e.g., a base station) applicable to the present disclosure.

[0030] Figure 5 illustrates a general functional architecture for an AI / ML model.

[0031] Figure 6 illustrates a communication procedure between a first node (e.g., terminal) and a second node (e.g., base station) to which an AI / ML model is applied.

[0032] FIG. 7 illustrates an electromagnetic spectrum according to one embodiment of the present disclosure.

[0033] FIG. 8 illustrates an example of a procedure for transmitting system information for THz communication to which the present disclosure applies.

[0034] Figure 9 illustrates a beam management procedure applicable to the present disclosure.

[0035] FIG. 10 illustrates an example of a sensing operation according to one embodiment of the present disclosure.

[0036] FIG. 11 illustrates time / frequency resources for sensing operations according to one embodiment of the present specification.

[0037] FIG. 12 illustrates a procedure related to a sensing operation according to one embodiment of the present specification.

[0038] Figures 13 to 16 illustrate various A-IoT topologies.

[0039] Figure 17 is a diagram for explaining EH (energy harvesting) for A-IoT.

[0040] Figure 18 is a diagram for explaining Deployment Scenario 1 in Topology 1.

[0041] Figure 19 is a diagram for explaining Deployment Scenario 2 in topology 2.

[0042] Fig. 20 is a diagram for explaining the state transition of an A-IoT device according to one embodiment.

[0043] FIG. 21 is a diagram for explaining the operation of an AmIoT device and reader according to one embodiment.

[0044] FIG. 22 illustrates a flow of a method performed by a first device according to one embodiment.

[0045] FIG. 23 illustrates a flow of a method performed by a second device according to one embodiment.

[0046] As used herein, "A or B" can mean "only A," "only B," or "both A and B." In other words, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "only A," "only B," "only C," or "any combination of A, B and C."

[0047] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0048] In this specification, "at least one of A and B" may mean "only A", "only B" or "both A and B". Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted identically to "at least one of A and B".

[0049] Additionally, in this specification, “at least one of A, B and C” can mean “only A,” “only B,” “only C,” or “any combination of A, B and C.” Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C.”

[0050] Additionally, parentheses used herein may mean "for example." Specifically, when "control information (ABC)" is indicated, "ABC" may be described as an example of "control information." For example, "control information" may include DEF as another example. In other words, "control information" in this specification is not limited to "ABC," and "ABC" may be described as an example of "control information." Furthermore, even when indicated as "control information (i.e., ABC)," "ABC" may be described as an example of "control information."

[0051] Additionally, in this specification, terms such as “first,” “second,” etc. are used only for the purpose of distinguishing one component from another component and are not used to limit the components, and do not limit the order or importance between the components unless specifically limited. Accordingly, a first component in one embodiment of this specification may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

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

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

[0054] In this specification, a terminal is a user equipment (UE) or a consumer-side device, and may also be referred to as a base station / second node / IAB node / first node that receives / transmits signals from / to a Transmission-Reception Point (TRP). A terminal may correspond to a physical node or a logical node. A terminal may correspond to an endpoint on the user side, or may correspond to an intermediate point between other endpoints. In communication between two points that are not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), a terminal may correspond to a served node. A terminal may be a node with a fixed location, or a node with an unfixed location (or mobile).

[0055] In this specification, a base station (BS) is a device on the network side, and may also be called a second node / IAB node / x-NodeB (x-NodeB, x may be an abbreviation related to radio access technology (RAT)) / Transmission-Reception Point (TRP). A BS may correspond to a physical node or a logical node. A BS may correspond to an endpoint on the network side, or may correspond to an intermediate point between other endpoints. In communication between two points that are not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), a BS may correspond to a serving node. A BS may be a node with a fixed location, or a node with an unfixed location.

[0056] In this specification, higher layer parameters may be set for the terminal, preset, or predefined. For example, the base station may transmit higher layer parameters to the terminal. For example, the terminal may transmit parameters such as capabilities to the base station as higher layer parameters. For example, the higher layer parameters may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0057] In this specification, the information / state / parameter being “configured or pre-configured” can be interpreted as the information / state / parameter being provided / pre-provided to the terminal through pre-defined signaling (e.g., SIB, MAC, RRC) from the base station. In this specification, the information / state / parameter being “defined or pre-defined” can be interpreted as the information / state / parameter being known in advance or pre-stored at the base station and the terminal without signaling between the base station and the terminal.

[0058] The technology described in this specification 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) / 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.

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

[0060] <Symbols, Abbreviations, Terms>

[0061] - SSB: Synchronization Signal Block

[0062] - MIB: Master Information Block

[0063] - RMSI: Remaining Minimum System Information

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

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

[0066] - BW: Bandwidth

[0067] - BWP: Bandwidth Part (can be composed of consecutive resource blocks (RBs) on the frequency axis and can correspond to one numerology (e.g., sub-carrier spacing, CP length, slot / mini-slot duration). In addition, multiple BWPs can be configured on one carrier (the number of BWPs per carrier can also be limited), but the number of activated BWPs can be limited to a part of it (e.g., 1) per carrier.)

[0068] - RNTI: Radio Network Temporary Identifier

[0069] - CRC: Cyclic Redundancy Check

[0070] - SIB: System Information Block

[0071] - SIB1: SIB1 for NR devices (i.e., Remaining Minimum System Information (RMSI)). Broadcasts information necessary for NR terminals to access the cell.

[0072] - CORESET: Control Resource Set. A time / frequency resource for NR terminals to attempt candidate PDCCH decoding. The number of CORESETs per BWP may be limited.

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

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

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

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

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

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

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

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

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

[0082] - SCS: subcarrier spacing

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

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

[0085] - TB: Transport Block

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

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

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

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

[0090] - FDRA: Frequency Domain Resource Allocation

[0091] - TDRA: Time Domain Resource Allocation

[0092] - RA: Random Access

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

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

[0095] - RO-N: RO(RACH Occasion) for normal UE 4-step RACH and 2-step RACH (if configured)

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

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

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

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

[0100] - RAR: Random Access Response

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

[0102] - FH: Frequency Hopping

[0103] - iBWP: initial BWP

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

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

[0106] - CS: Cyclic shift

[0107] - NB: Narrowband

[0108] - TO: Traffic Offloading

[0109] - mMTC; massive Machine Type Communications

[0110] - eMBB: enhanced Mobile Broadband Communication

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

[0112] - RedCap: Reduced Capability

[0113] - eRedCap: enhanced RedCap

[0114] - FDD: Frequency Division Duplex

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

[0116] - DRX: Discontinuous Reception

[0117] - RRC: Radio Resource Control

[0118] - RRM: Radio Resource Management

[0119] - CAP: Channel Access Procedure

[0120] - Ucell: Unlicensed cell

[0121] - COT: Channel occupancy time

[0122] - SPS: Semi-persistent scheduling

[0123] - TBS: Transport Block Size

[0124] - MM: Mobility Management

[0125] - IWSN: Industrial Wireless Sensor Network

[0126] - LPWA: Low Power Wide Area

[0127] - RB: Resource Block

[0128] - CCE: Control Channel Element

[0129] - AL: Aggregation Level

[0130] - REG: Resource element group

[0131] - PRG: Physical Resource-block Group

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

[0133] - PBCH: Physical Broadcast Channel

[0134] - A-PBCH: Additional PBCH

[0135] - BD: blind detection

[0136] - EPRE: Energy Per RE

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

[0138] - TDM: Time Division Multiplexing

[0139] - FDM: Frequency Division Multiplexing

[0140] - DMRS: DeModulation Reference Signal

[0141] - TDD: Time Division Duplex

[0142] - PCI: Physical layer Cell ID

[0143] - BS: Base Station

[0144] - TD: Time Domain

[0145] - FD: Frequency Domain

[0146] - PEI: Paging Early Indication

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

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

[0149] - RSRP: Reference Signal Received Power

[0150] - PHR: Power Headroom Report

[0151] - PRB: Physical Resource Block

[0152] - SFI: Slot Format Indicator (특정 slot(s) 내의 심볼 level DL / UL direction 을 지시해주는 지시자로써, group common PDCCH 를 통해 전송된다.)

[0153] - SLIV: Starting and Length Indicator Value (This is an indicator value for the starting symbol index and number of symbols within the slot of the PDSCH and / or PUSCH, and can be set as a component of the entry that constitutes the TDRA field within the PDCCH that schedules the corresponding PDSCH and / or PUSCH.)

[0154] - QCL: Quasi-Co-Location (QCL relationship between two reference signals means that QCL parameters such as Doppler shift, Doppler spread, average delay, delay spread, and Spatial Rx parameter obtained from one reference signal can be applied to another reference signal (or antenna port(s) of the corresponding RS). In the NR system, four QCL types are defined as follows. 'typeA': {Doppler shift, Doppler spread, average delay, delay spread}, 'typeB': {Doppler shift, Doppler spread}, 'typeC': {Doppler shift, average delay}, 'typeD': {Spatial Rx parameter} For any DL RS antenna port(s), the first DL RS is set as a reference for QCL type X (X=A, B, C, or D), and additionally, the second DL RS is set as a reference for QCL type Y (Y=A, B, C, or D but X≠Y). (can be set as a reference for)

[0155] - TCI: Transmission Configuration Indication (A TCI state includes the QCL relationship between one or more DL RSs, such as DM-RS ports of the PDSCH, the DM-RS port of PDCCH, or the CSI-RS port(s) of a CSI-RS resource. For the 'Transmission Configuration Indication' field in the DCI that schedules the PDSCH, the TCI state index corresponding to each code point that constitutes the field is activated by the MAC CE, and the TCI state setting for each TCI state index is set through RRC signaling. In the Rel-16 NR system, the TCI state is set between DL RSs, but in future releases, setting between DL RS and UL RS or UL RS and UL RS may be allowed. Examples of UL RSs include SRS, PUSCH DM-RS, and PUCCH DM-RS.)

[0156] - SRI: SRS resource indicator (Indicates one of the SRS resource index values ​​set in the 'SRS resource indicator' among the fields in the DCI that schedules the PUSCH. When transmitting a PUSCH, the UE can transmit the PUSCH using the same spatial domain transmission filter used for transmitting and receiving the reference signal linked to the corresponding SRS resource. At this time, the reference RS is set by RRC signaling through the SRS-SpatialRelationInfo parameter for each SRS resource, and SS / PBCH block, CSI-RS, or SRS can be set as the reference RS.)

[0157] - TRP: Transmission and Reception Point

[0158] - TAG: Timing advance group

[0159] Figure 1 illustrates a flexible network topology to which some examples of this specification may be applied.

[0160] To compensate for incomplete network coverage areas, a network topology that allows for more flexible and resilient split radio access networks (RANs) may be considered. For this purpose, various nodes, such as IAB nodes, relays, and RF repeaters, as illustrated in the example in Figure 1, may be applied, or NTNs 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, or 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 simply performs the function of signal amplification and forwarding, while a network-controlled repeater may not only amplify and forward signals but also adjust transmission and reception settings based on information provided by the network. For example, an NTN node may correspond to a satellite or aircraft that provides 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.

[0161] Referring to Figure 1, a split RAN can support the division of a base station into a centralized unit (CU) and one or more distributed units (DUs). The CU and DU can correspond to logical units. The CU can 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 DUs, various intermediate points can be introduced to compensate for this.

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

[0163] In some examples of this specification, the description of a terminal can be equally applied not only to a user-side endpoint, but also to an intermediate point corresponding to a terminal in a relative relationship with a network-side endpoint. Similarly, in some examples of this specification, the description of a base station can be equally applied not only to a network-side endpoint, but also to an intermediate point corresponding to a base station in a relative relationship with a user-side endpoint. However, in most cases where there is no additional description of the operations of three or more entities, the communicating entities in this specification are briefly described as terminals and / or base stations (or first nodes and / or second nodes), and the terms terminal and / or base stations (or first nodes and / or second nodes) are interpreted to include / replace any endpoint or any intermediate point in relation to other nodes.

[0164] That is, in some examples of this specification, for the sake of simplicity of explanation, the subjects of the operation may be referred to as a base station and / or a terminal (or a first node and / or a second node). In addition, the terms base station and / or terminal (or a first node and / or a second node) may also be interpreted / replaced as in the following examples: For example, the base station (or a first node) and the terminal (or a second node) may respectively correspond to the first endpoint and the second endpoint; may respectively correspond to the endpoint and the intermediate point; may respectively correspond to the intermediate point and the endpoint; or may respectively correspond to the first intermediate point and the second intermediate point.

[0165] In this specification, there may be zero or more intermediate points between the base station and the terminal. If intermediate points exist, they may be IAB nodes, relays, RF repeaters, NTN (non-terrestrial network) nodes, or nodes supporting other functions. An intermediate point may be a node with a fixed location or a node with an unfixed location.

[0166] Figure 2 illustrates a communication system applicable to the present disclosure.

[0167] The communication system (100) of FIG. 2 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 a 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 Things) device (110f), and an AI (artificial intelligence) device / server (110g). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-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, a 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.), 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 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 act as a network device (120) to another wireless device (110).

[0168] Wireless devices (110a to 110f) can be connected to a network (130) via a network device (120). AI technology can be applied to the wireless devices (110a to 110f), and the wireless devices (110a to 110f) can be connected to an AI server (110g) via a network (130). The network (130) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR), or a 6G network. The wireless devices (110a to 110f) can communicate with each other via the network device (120) / network (130), but can 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). Additionally, IoT devices (110f) (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (110a to 110f).

[0169] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (110a to 110f) / network devices (120), network devices (120) / network devices (120). Here, the 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 the wireless communication / connection (150a, 150b, 150c), the wireless device and the network device / wireless device, and the network device and the network device can transmit / receive wireless signals to each other. For example, the wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on various descriptions of the present disclosure, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), resource allocation processes, etc. may be performed.

[0170] FIG. 3 illustrates an example of a wireless device applicable to the present disclosure.

[0171] Referring to FIG. 3, the wireless device (200) can transmit and receive wireless signals via 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).

[0172] 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 operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (206). In addition, the processor (202) may receive a wireless signal including second information / signal via the transceiver (206), and then store information obtained from 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, the memory (204) may store software code including 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 operational flowcharts disclosed herein. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology. The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via at least one antenna (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF (radio frequency) unit. In the present disclosure, a wireless device may also mean a communication modem / circuit / chip.

[0173] Hereinafter, the 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., a functional layer such as physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC), and service data adaptation protocol (SDAP)). At least one processor (202) may generate at least one Protocol Data Unit (PDU) and / or at least one Service Data Unit (SDU) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. At least one processor (202) may generate a message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. At least one processor (202) can generate a signal (e.g., a baseband signal) including a PDU, an SDU, a message, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this document, and provide the signal to at least one transceiver (206). At least one processor (202) can receive a signal (e.g., a baseband signal) from at least one transceiver (206) and obtain the PDU, SDU, message, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in this document.

[0174] At least one processor (202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. The 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 the at least one processor (202). The descriptions, functions, procedures, proposals, methods, and / or operation flowcharts 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. The descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document may be included in the at least one processor (202), or may be stored in at least one memory (204) and driven by the at least one processor (202). The descriptions, functions, procedures, suggestions, 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.

[0175] At least one memory (204) can be connected to at least one processor (202) and can store various forms of data, signals, messages, information, programs, codes, instructions and / or commands. The at least one memory (204) can be configured as a read only memory (ROM), a random access memory (RAM), an erasable programmable read only memory (EPROM), a flash memory, a hard drive, a register, a cache memory, a computer readable storage medium and / or a combination thereof. The at least one memory (204) can be located internally and / or externally to the at least one processor (202). In addition, the at least one memory (204) can be connected to the at least one processor (202) via various technologies such as a wired or wireless connection.

[0176] At least one transceiver (206) can transmit user data, control information, wireless signals / channels, etc., mentioned in the methods and / or flowcharts of this document to at least one other device. At least one transceiver (206) can receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed in this document from at least one other device. For example, at least one transceiver (206) can be connected to at least one processor (202) and can transmit and receive wireless signals. For example, at least one processor (202) can control at least one transceiver (206) to transmit user data, control information, or wireless signals to at least one other device. Furthermore, at least one processor (202) can control at least one transceiver (206) to receive user data, control information, or wireless signals from at least one other device. In addition, 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. mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts 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) may convert the processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using at least one processor (202).For this purpose, at least one transceiver (206) may include an (analog) oscillator and / or filter.

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

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

[0179] For example, the device may be a portable device such as a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), or a portable computer (e.g., a 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 image information / signals, audio information / signals, data, and / or information input from a user.

[0180] For example, the device may be a mobile device such as a mobile robot, a vehicle, a train, an aerial vehicle (AV), a ship, etc. In this case, the device may further include at least one of a driving unit including at least one of an engine, a motor, a power train, wheels, brakes, and a steering unit of the device, a power supply unit including a wired / wireless charging circuit, a battery, etc. that supplies power, a sensor unit that senses status 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 obtains location information of the mobile device through a global positioning system (GPS) and various sensors.

[0181] For example, the device may be an XR device such as an HMD, a head-up display (HUD) installed in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a 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 obtains control information, data, etc. from the outside and outputs the generated XR object, and a sensor unit that senses status information, environmental information, and user information of the device or the surroundings of the device.

[0182] For example, the device may be a robot that can be classified into industrial, medical, household, military, etc. types 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 status information, environmental information, and user information of the device or its surroundings, and a driving unit that performs various physical actions, such as moving the robot joints.

[0183] For example, the device may be an AI device such as a TV, a projector, a smartphone, a PC, a laptop, a digital broadcasting terminal, a tablet PC, a wearable device, a set-top box (STB), a radio, a washing machine, a refrigerator, digital signage, a robot, a 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 status information, environmental information, and user information of the device or its surroundings, and a training unit that trains a model composed of an artificial neural network using learning data.

[0184] The structure of the wireless device illustrated in FIG. 3 may be understood as a part of a terminal (or first node), or as a part of an intermediate point, or as a 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 communications. However, if the front haul and / or back haul communications are based on wireless communications, at least one transceiver (206) illustrated in FIG. 3 may be used for front haul and / or back haul communications, and a wired transceiver may not be included.

[0185] FIG. 4 illustrates a communication procedure between a first node (e.g., a terminal) and a second node (e.g., a base station) applicable to the present disclosure.

[0186] The second node of FIG. 4 supports dynamic spectrum sharing (DSS), which can provide connectivity to both nodes implementing 6G technology and nodes implementing pre-6G wireless communication technologies (e.g., 5G, 4G). That is, the first node of FIG. 4 can implement either 6G technology or pre-6G wireless communication technologies (e.g., 5G, 4G). Furthermore, the first node and / or the second node can support full duplex mode as well as non-overlapping full duplex mode.

[0187] In Fig. 4, for the sake of simplicity of explanation, the first node and the second node are assumed to be a terminal and a base station, respectively, and operations of the terminal (110) and the base station (120) transmitting and / or receiving data and operations performed prior thereto are illustrated. However, the operations of Fig. 4 are not limited to operations between the terminal and the base station, and may be interpreted as operations between the first node and the second node. In addition, although Fig. 4 illustrates direct wireless signal transmission and reception operations between the terminal (110) and the base station (120), one or more intermediate points may exist between the terminal (110) and the base station (120), and wireless signals may be transmitted and received via one or more intermediate points.

[0188] Referring to FIG. 4, the terminal (110) and the base station (120) can perform synchronization (401). For example, the terminal (110) performs an initial cell search operation. Specifically, the terminal (110) can detect a synchronization signal for connection to at least one base station transmitted from the base station (120) according to a predefined rule. Here, the synchronization signal can include a plurality of synchronization signals classified according to structure or purpose (e.g., a first synchronization signal (e.g., a primary synchronization signal), a second synchronization signal (e.g., a secondary synchronization signal), etc.). Through this, the terminal (110) can confirm the boundary of a unit (e.g., a frame, a subframe, a slot, and / or a symbol) constituting a wireless signal transmission of the base station (120) and obtain information (e.g., a cell identifier) ​​about the base station (120).

[0189] The terminal (110) can obtain system information transmitted from the base station (120) (403). The system information is information related to the properties, characteristics, and / or capabilities of the base station (120) required to access the base station (120) and use the service, and can be classified according to the content (e.g., whether it is essential for access), transmission structure (e.g., channel used, whether provided on-demand), etc., and can be classified into, for example, first system information (e.g., master information block (MIB), primary system information), second system information (e.g., system information block (SIB), secondary system information), etc. If necessary, the terminal (110) can transmit a signal requesting system information before receiving the system information. However, the request and provision of system information can be performed after the random access procedure described below.

[0190] The terminal (110) and the base station (120) can perform a random access procedure (405). The terminal (110) can transmit and / or receive at least one message (e.g., a random access preamble, a random access response (RAR) message, etc.) for the random access procedure based on information related to a channel for the random access procedure 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) can transmit a first message (e.g., a preamble, MSG1) through the channel for the random access procedure, receive a second message (e.g., an RAR message, MSG2), transmit a third message (e.g., MSG3) including information related to the terminal (110) (e.g., identification information) to the base station (120) using scheduling information included in the second message, and receive a fourth message (e.g., MSG4) for contention resolution and / or connection establishment. As another example, the first and third messages may be sent and received as one message, or the second and fourth messages may be sent and received as one message.

[0191] The terminal (110) and the base station (120) can perform signaling of control information (407). Here, the control information can be defined in various layers, such as a layer that controls a connection (e.g., a radio resource control (RRC) layer), a layer that handles mapping between logical channels and transport 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) can perform at least one of signaling for establishing a connection, signaling for determining settings related to communication, and signaling for indicating allocated resources.

[0192] The terminal (110) and the base station (120) can transmit and / or receive data (409). In other words, the terminal (110) and the base station (120) can process, transmit, and / or receive data based on signaling of control information. 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. Conversely, when receiving data, the terminal (110) or the base station (120) can perform at least one of signal extraction from resources, waveform demodulation for each antenna, signal arrangement considering layer mapping, constellation demapping, descrambling, and channel decoding.

[0193] <6G System Core Technologies>

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

[0195] As core implementation technologies of the 6G system, technologies such as artificial intelligence (AI), THz (terahertz) communication, optical wireless technology, FSO backhaul network, massive 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.

[0196] artificial intelligence

[0197] Incorporating AI into communications can streamline and improve real-time data transmission. AI can use numerous analytics to determine how complex target tasks should be performed. This means AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handovers, network selection, and resource scheduling can be performed instantly using AI. AI can also play a crucial role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. Furthermore, AI can facilitate rapid communication in brain-computer interfaces (BCIs). 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.

[0198] The following describes a functional framework for AI / ML operations.

[0199] Below, to explain AI (or AI / ML) more specifically, the terms can be defined as follows.

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

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

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

[0203] - AI / ML Inference: The process of making predictions or inducing decisions based on collected data and the AI ​​model using a trained AI model.

[0204] Life Cycle Management (LCM) procedures for AI / ML models (i.e., model training, model deployment, model inference, model monitoring, model updates, etc.) can be divided into functionality-based LCM and model-based LCM. In functionality-based LCM, AI / ML models may not be identified by the network, and the network can direct the activation / deactivation / fallback / switching of AI / ML functionality. In model-ID (identifier)-based LCM, AI / ML models can be identified by the network, and the network / terminal can activate / deactivate / select / switch AI / ML models based on the model ID.

[0205] Figure 5 illustrates a general functional architecture for an AI / ML model.

[0206] In particular, Figure 5 illustrates a general functional architecture relevant to both Functionality-based LCM and Model-based LCM. Some of the functions or some of the data / information / command flows (i.e., arrows) illustrated in Figure 5 may be omitted.

[0207] Referring to FIG. 5, a general functional framework can be configured to include a data collection function (10), a model training function (20), a management function (30), an inference function (40), and a model storage function (50).

[0208] The Data Collection function (10) is a function that provides input data to the Model Training function (20), Management function (30), and Inference function (40). The Data Collection function (10) can perform data preparation based on raw data and provide input data processed through data preparation. Examples of raw data may include received data / measurement data from terminals or other network entities, inference / output of AI / ML models, etc. The Data Collection function (10) may be performed by a single entity (e.g., terminal, network node, etc.) or may be performed by multiple entities.

[0209] Here, training data (11) refers to data required as input for the AI / ML Model Training function (20). Monitoring data (12) refers to data required as input for the Management (30) of the AI / ML model or AI / ML function. Inference data (13) refers to data required as input for the AI / ML Inference function (30).

[0210] The Model Training function (20) is a function that performs AI / ML model training, validation, and testing, which can generate model performance metrics that can be used as part of the AI / ML model testing procedure. The Model Training function (20) can perform data preparation (e.g., data pre-processing and cleaning, forming, and transformation) based on the Training Data (11) transferred from the Data Collection function (10), if necessary.

[0211] Trained / Updated Model (21): If there is a Model Storage function (50), it is used to pass a trained, validated and tested AI / ML model to the Model Storage function (50) or to pass an updated version of the model to the Model Storage function (50).

[0212] The Management function (30) is a function that supervises the operation of the AI / ML model or AI / ML function. In addition, the Management function (30) may perform decisions to ensure appropriate inference operations based on data received from the Data Collection function (10) (i.e., Monitoring Data (12)) and / or data received from the Inference function (40) (i.e., Inference Output (41)).

[0213] Management Instruction (32) is information required as input to manage the Inference function (40). The relevant information may include selection / (de)activation / switching of an AI / ML model or AI / ML-based function, and may also include fallback to non-AI / ML operations (i.e., not relying on the inference process).

[0214] A Model Transfer / Delivery Request (33) can be used to request model(s) from Model Storage (50).

[0215] A Performance Feedback / Retraining Request (31) refers to information required as input to the Model Training function (20) (e.g., for the purpose of (re)training or updating the model).

[0216] The Inference function (40) is a function that provides output from the process of applying an AI / ML model or AI / ML function using data (i.e., Inference Data (13)) provided by Data Collection (10) as input. Data preparation (e.g., data preprocessing and cleaning, formatting, and transformation) may also be performed based on the Inference Data (13) delivered by Data Collection (10). If necessary, the Inference function (40) may also perform data preparation (e.g., data preprocessing and cleaning, forming, and transformation) based on the Inference Data (13) provided by Data Collection function (10).

[0217] Inference Output (41) is data used in the Management function (30) to monitor the performance of an AI / ML model or AI / ML function. Inference Output (41) may include the inference output of the AI / ML model generated by the Inference function (30), and the details of the inference output may vary depending on the use case.

[0218] The Model Storage function (50) stores a learned / updated model that can be used to perform the Inference function (40). The Model Storage function (50) illustrated in FIG. 5 can be used as a reference point (if any) when applicable to protocol termination, model transmission / delivery, and related processes. Furthermore, the Model Storage function (50) is merely an example and is not intended to limit the storage location of actual AI / ML models, and may be omitted.

[0219] Model Transfer / Delivery (51) is used to transfer AI / ML models to inference functions.

[0220] The level of cooperation can be defined as follows depending on the capability of AI / ML functions between multiple nodes, and variations due to combination of multiple levels or separation of any one level are also possible.

[0221] Cat 0a) No collaboration framework: AI / ML algorithms are purely implementation-based and do not require any changes to the wireless interface.

[0222] Cat 0b) This level corresponds to a framework with a modified wireless interface tailored to efficient implementation-based AI / ML algorithms, but without collaboration.

[0223] Category 1) involves inter-node support to improve the AI / ML algorithms of each node. For example, this applies when a specific node receives support from another node (for training, adaptation, etc.) and vice versa. At this level, model exchange between network nodes is not required.

[0224] Category 2) Joint AI / ML tasks can be performed across multiple nodes. This level requires the exchange of AI / ML model commands or network nodes.

[0225] FIG. 5 is a diagram illustrating an overall functional framework for an AI / ML model, and not all functions and / or all data / information / command signals illustrated in FIG. 5 may be performed within a specific node, but only some of them may be performed.

[0226] AI / ML models can be divided into one-side models and two-side models depending on whether training and / or inference are performed on a single node or jointly / sequentially on multiple nodes.

[0227] A one-side model can refer to an AI / ML model in which inference is performed entirely by a single node (e.g., a terminal or network). Here, AI / ML model training can also be performed entirely by a single node. AI / ML model training and inference can be performed by the same node, or they can be performed by separate nodes.

[0228] A two-side model can refer to an AI / ML model in which joint inference is performed across multiple nodes (e.g., terminals and networks). Joint inference refers to inference being performed jointly across multiple nodes. For example, the first part of the inference may be performed by a first node, and the remaining part by a second node. Two-side models can be categorized into several types depending on the training method of the AI / ML model, as follows:

[0229] - First type: AI / ML models can be trained on a single node. In this case, joint training can be performed. The trained model can then be distributed to other nodes / objects.

[0230] - Second type: Joint training of AI / ML models can be performed on multiple nodes / entities (e.g., networks and terminals). Joint training can mean that model generation (e.g., CSI generation part) and model reconstruction (CSI compression by sub-use case) are trained in the same loop for forward activation and backward gradient. In this type, joint training can include both simultaneous training (i.e., model generation training and model reconstruction training are performed simultaneously) and sequential training (i.e., model reconstruction training is performed after model generation training).

[0231] - Third type: Separate training of AI / ML models can be performed on multiple nodes (e.g., networks and terminals). Separate training may mean that training begins sequentially on one node and continues on other nodes. In this case, the first node first performs the AI / ML model and shares the training data with the second node. The second node can then use the shared training data to perform the AI / ML model. For example, training for the CSI generation part may be performed by the terminal, while CSI reconstruction may be performed by the network.

[0232] Figure 6 illustrates a communication procedure between a first node (e.g., terminal) and a second node (e.g., base station) to which an AI / ML model is applied.

[0233] The operations described below can be described / interpreted based on the AI / ML model proposed in this specification, as shown in Fig. 6 below, even without separate mention (i.e., without explicit mention of being by / based on / for the AI / ML model). In addition, unless specifically limited, the AI / ML model can correspond to a one-side model in which inference is entirely performed by a single node, or a two-side model in which joint inference is performed by multiple nodes.

[0234] First signaling (601): In the description below, the signaling (e.g., information / data / channel / signal, etc.) or set of signaling between a specific node (e.g., terminal, network, etc.) and another node may be interpreted as the signaling or set of signaling of the first signaling (601) used to perform an operation based on an AI / ML model, even if not otherwise mentioned. For example, it may correspond to training data for training (i.e., generation and / or reconstruction) the AI / ML model of FIG. 5, or correspond to inference data used for inference of the AI / ML model, or correspond to feedback for the AI / ML model, etc. If signaling between nodes is not required prior to an operation based on an AI / ML model in the present specification, the first signaling (601) may be omitted. If a one-side model is used in the present specification, the one-way / two-way signaling (set) in the present specification may correspond to the signaling of the first signaling (601). In addition, when a two-side model is used in this specification, the one-way / two-way signaling in this specification may correspond to the first signaling (601), and also, a repetitive signaling operation may correspond to the first signaling (601).

[0235] For example, in AI / ML model-based beam management (BM), if a base station predicts (i.e., infers) beam(s) with good quality based on an AI / ML model, the base station can receive quality / intensity information for multiple beams from a terminal. Furthermore, if a terminal predicts (i.e., infers) beam(s) with good quality based on an AI / ML model, the terminal can receive multiple beams from the base station.

[0236] AI / ML model-based operation (602): In the description below, an operation (e.g., calculation, selection, prediction, etc.) in a specific node (e.g., terminal, network, etc.) or a joint operation (e.g., calculation, selection, prediction, etc.) in multiple nodes (e.g., terminal, network, etc.) may correspond to an AI / ML model-based operation (602) based on one or more functions in the functional framework of the AI / ML model, even if not mentioned separately. For example, it may correspond to training (i.e., generation and / or reconstruction) of the AI / ML model of FIG. 5 or inference of the AI / ML model, etc. When a one-side model is used, an operation performed by a single node in the present specification may correspond to an AI / ML model-based operation (602), and also, when a two-side model is used, a joint operation performed by multiple nodes in the present specification may correspond to an AI / ML model-based operation (602).

[0237] For example, in an AI / ML model-based BM, the base station can use quality / intensity information for multiple beams received from the terminal as inference data to predict (i.e., infer) beam(s) with good quality based on the AI / ML model. Furthermore, the terminal can measure multiple beams received from the base station and use the measurement results as inference data to predict (i.e., infer) beam(s) with good quality based on the AI / ML model.

[0238] Second signaling (603): In the description below, signaling (e.g., information / data / channel / signal, etc.) or a set of signaling between a specific node (e.g., terminal, network, etc.) and another node may be interpreted as a second signaling (603) or a set of signaling generated due to (as a result of) an operation based on an AI / ML model, even if not otherwise mentioned. For example, it may correspond to an output resulting from inference of the AI / ML model in FIG. 5. If signaling between nodes is not required as a result of an operation based on an AI / ML model in this specification, the second signaling (603) may be omitted. If a one-side model is used in this specification, a one-way / two-way signaling (set) in this specification may correspond to the second signaling (603). In addition, when a two-side model is used in this specification, the one-way / two-way signaling in this specification may correspond to the second signaling (603), and also, a repetitive signaling operation may correspond to the second signaling (603).

[0239] For example, in an AI / ML model-based BM, the base station can transmit to the terminal the beam(s) predicted based on the AI / ML model as candidates so that the terminal can determine the optimal beam. Furthermore, the terminal can report to the base station the beam(s) predicted based on the AI / ML model to request the base station to transmit the candidate beams as candidates for determining the optimal beam.

[0240] THz communication (terahertz communication)

[0241] Data rates can be increased by increasing bandwidth. This can be achieved by utilizing sub-THz communications with wide bandwidths and applying advanced massive MIMO technology. THz waves, also known as sub-millimeter waves, typically refer to the frequency range between 0.1 THz and 10 THz, with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz to 300 GHz band (sub-THz band) is considered a key part of the THz spectrum for cellular communications. Adding the sub-THz band to the mmWave band will increase the capacity of 6G cellular communications. Among the defined THz bands, 300 GHz to 3 THz lies in the far infrared (IR) frequency band. While part of the optical band, the 300 GHz to 3 THz band lies at the boundary of the optical band, immediately following the RF band. Therefore, this 300 GHz to 3 THz band exhibits similarities to RF.

[0242] Figure 7 illustrates the electromagnetic spectrum according to one embodiment of the present disclosure. The embodiment of Figure 7 can be combined with various embodiments of the present disclosure. Key characteristics of THz communications include (i) a widely available bandwidth to support very high data rates, and (ii) high path loss at high frequencies (highly directional antennas are essential). The narrow beamwidth generated by the highly directional antenna reduces interference. The small wavelength of THz signals allows for a much larger number of antenna elements to be integrated into devices and base stations operating in this band. This enables the use of advanced adaptive array techniques to overcome range limitations.

[0243] Transmitting system information (i.e., information related to the properties, characteristics, and / or capabilities of a BS required to use a service, such as MIB, SIB, etc.) in the THz frequency band may be inefficient because, as the beam width becomes narrower in high frequency bands, more beam sweeps must be performed to cover the entire area of ​​the cell. In particular, transmitting system information in this manner is even more inefficient when there are not many users in the cell. Accordingly, a system information transmission procedure such as that illustrated in FIG. 8 may be used.

[0244] Figure 8 illustrates an example of a procedure for transmitting system information for THz communications to which the present disclosure applies. While this example was developed with THz in mind, it is also applicable to 6G communication environments where THz is not applicable. Furthermore, the procedure illustrated in Figure 8 can be combined with various embodiments of the present disclosure described below. For example, the embodiments described below can be performed based on system information acquired through the procedure illustrated in Figure 8.

[0245] Referring to FIG. 8, the base station can transmit system information of cell #1 through cell #2 (801). That is, the base station provides at least two cells, cell #1 uses a THz frequency band, and cell #2 uses a non-THz frequency band. Here, the system information can include at least one information / state / parameter / setting generated in each of a higher layer and a physical layer. For example, the at least one information / state / parameter / setting generated in the higher layer can include at least one of an SFN, control information setting for SIB1 (e.g., PDCCH configuration for SIB1, etc.), information related to cell selection / entry (e.g., cell barring, cell re-selection, etc.), and subcarrier spacing, and the at least one information / state / parameter / setting generated in the physical layer can include at least one of an SFN, a half frame indicator, and an SSB index. However, this is merely an example, and system information may include information / status / parameters / settings related to Cell #1 / Cell #2 generated from various types of physical layers / upper layers. For this purpose, as an example, Cell #1 and Cell #2 may have a relationship as a secondary cell and a primary cell.

[0246] The UE can acquire synchronization for cell #1 (803). Synchronization can be acquired by detecting a synchronization signal. Typically, synchronization is acquired before receiving system information. However, since the system information for cell #1 is received from cell #2, synchronization acquisition for cell #1 can be performed after receiving the system information. For example, the UE can acquire synchronization based on the system information. However, unlike FIG. 8, in another example, synchronization acquisition can be performed before step 801.

[0247] The UE may transmit a signal for accessing cell #1 (805). For example, the signal may include information for accessing cell #1 (e.g., a random access preamble). The structure of the signal and the resources for transmitting the signal (e.g., a channel) may be identified through system information. Thereafter, the UE and the base station may perform an access procedure for cell #1 and communicate (807). During this process, operations according to various embodiments described below may be performed.

[0248] The procedure described with reference to FIG. 8 may be performed when UE (801) first accesses cell #1 of the base station. Alternatively, a similar procedure may be performed when UE (801) hands over to cell #1 of the base station. However, in the case of handover, the system information of cell #1 may be received from a cell of a base station other than cell #2 of the base station.

[0249] Communications in the THz band are expected to experience extremely severe path loss, and to overcome this, terminals and base stations must use extremely sharp beams. The use of sharp beams means that terminals and base stations must perform beam control in addition to beamforming, and the number of beams used increases significantly. Consequently, it takes a very long time to align the transmit and receive beams between the base station and terminals. Furthermore, if the beam alignment between the base station and terminals is misaligned due to the movement or movement of the terminals, frequent re-alignment of the beams is required, which can lead to link instability. Accordingly, a beam management procedure, as illustrated in FIG. 9 below, may be employed.

[0250] FIG. 9 illustrates a beam management procedure applicable to the present disclosure. FIG. 9 illustrates an example of a procedure for searching and / or selecting beams for THz communication, but is not limited to a THz environment, and the present disclosure is applicable to a 6G communication environment. In addition, the procedure illustrated in FIG. 9 can be combined with various embodiments of the present disclosure described below. Here, a beam may be interpreted as 'spatial (setting) information', 'spatial domain filter', 'spatial domain transmission filter', 'spatial domain reception filter', or / and a term having an equivalent technical meaning that can distinguish the beam (e.g., Reference signal, SSB (Synchronization Signal Block) Index, TRP (transmission reception point), panel, cell, TP (transmission point), base station, control resource related information (e.g., CORESET (control resource set) related information, etc.).

[0251] Referring to FIG. 9, a base station can configure resources for beam management (901). Here, the resources can include at least one of time-frequency resources, channels, and spatial resources (e.g., antenna ports). For example, the base station can utilize a beam search signal (BSS) that is transmitted spatially separated from existing downlink signals / channels for beam search. Here, the BSS can be transmitted based on a dedicated port for beam search. The dedicated port can be a different port from a port for transmitting existing downlink signals / channels (e.g., synchronization signals (e.g., SSB, etc.), data channels (e.g., PDSCH, 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. That is, a signal transmitted based on a dedicated port defined / configured for beam search can be included in the technical concept according to the present embodiment.

[0252] The base station can transmit measurement signals using multiple transmission beams (903). For example, the measurement signals can include at least one of a reference signal and a synchronization signal. At this time, the measurement signals can be transmitted as many times as the number of beams that require measurement, and can be transmitted using a multi-beam transmission method that forms multiple beams simultaneously to reduce sweeping time. Here, the multi-beam transmission can be performed based on at least one of a multi-panel, a sub-array, and a true time delay (TTD).

[0253] The UE may transmit a feedback signal to the base station (905). The feedback signal indicates at least one beam selected by the UE. The UE may select at least one preferred beam based on the received measurement signals. The UE and the base station may communicate (907). At this time, the UE and the base station may communicate using the previously selected beam. If channel reciprocity is established, the transmission beam of the UE may also be determined through operations 903 and 905, and thus the transmission of the UE may also be performed using the beam selected in operation 905. If channel reciprocity is not established, a procedure including transmission of measurement signals by the UE and transmission of a feedback signal by the base station may be performed first to determine the transmission beam of the UE. In operation 907, operations according to various embodiments described below may be performed.

[0254] Integrated Sensing and Communication (ISAC)

[0255] Wireless sensing is a technology that uses radio frequencies to determine the instantaneous linear velocity, angle, distance (range), etc. of an object, thereby obtaining information about the characteristics of the environment and / or objects within the environment. Because radio frequency sensing does not require a networked device to connect to the object, it can provide a service for object positioning without a device. The ability to obtain range, velocity, and angle information from radio frequency signals can enable a wide range of new capabilities, such as various object detection, object recognition (e.g., vehicles, humans, animals, UAVs), and high-precision localization, tracking, and activity recognition. Wireless sensing services can provide information to a variety of industries (e.g., drones, smart homes, V2X, factories, railways, public safety, etc.), enabling 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 can utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of wireless sensing services, i.e., sensing operations, may depend on the transmission, reflection, and scattering of wireless sensing signals. Therefore, wireless sensing offers an opportunity to enhance existing communication systems from a communications network to a wireless communication and sensing network.

[0256] FIG. 10 illustrates an example of a sensing operation according to an embodiment of the present disclosure. The embodiment of FIG. 10 can be combined with various embodiments of the present disclosure. Specifically, FIG. 10(a) illustrates an example of sensing using a sensing receiver and a sensing transmitter located at the same location (e.g., monostatic sensing), and FIG. 10(b) illustrates an example of sensing using a separated sensing receiver and sensing transmitter (e.g., bistatic sensing).

[0257] For example, in a wireless communication system based on a 6G network of the present specification, referring to FIG. 10(a), the sensing transmitter and the sensing receiver may be configured to be included in a single base station (i.e., the same base station) or a single terminal (i.e., the same terminal). Alternatively, referring to FIG. 10(b), the sensing transmitter and the sensing receiver may be configured to be included in different base stations, different terminals, or each terminal and base station.

[0258] In this regard, the following six types of sensing modes can be defined based on whether the sensing transmitter and sensing receiver are included in the base station or the terminal, respectively.

[0259] - Mode 1: A mode in which the sensing transmitter and sensing receiver are contained in a single base station (e.g., base station-based sensing mode in monostatic mode).

[0260] - Second mode: A mode in which the sensing transmitter is included in a first base station and the sensing receiver is included in a second base station different from the first base station (e.g., base station-based sensing mode in bistatic mode).

[0261] - Mode 3: A mode in which the sensing transmitter is included in the base station and the sensing receiver is included in the terminal (e.g., base station-terminal sensing mode).

[0262] - Mode 4: A mode in which the sensing transmitter is included in the terminal and the sensing receiver is included in the base station (e.g., terminal-base station sensing mode).

[0263] - Mode 5: A mode in which the sensing transmitter and sensing receiver are contained in a single terminal (e.g., terminal-based sensing mode in monostatic mode).

[0264] - 6th mode: A mode in which the sensing transmitter is included in a first terminal and the sensing receiver is included in a second terminal different from the first terminal (e.g., terminal-based sensing mode in bistatic mode).

[0265] In a wireless communication system based on a 6G network of the present specification, one or more of the six types of sensing modes described above may be utilized independently / in combination.

[0266] In relation to the sensing operation in FIG. 10, the sensing transmitter may transmit a sensing signal for sensing one or more objects (and / or an environment around the objects). For example, the sensing signal may correspond to a radio (frequency) signal defined to be transmittable by a base station / terminal in a wireless communication system based on a 6G network of the present specification. The sensing receiver may receive a signal scattered / reflected by one or more objects (and / or an environment around the objects) from a sensing signal transmitted from the sensing transmitter. In the sensing receiver, sensing data may be derived from the scattered / reflected signals, and sensing results may be generated / obtained through processing of the sensing data. Here, the sensing results may include characteristic information (e.g., location, distance, speed, angle, etc.) about one or more objects (and / or the environment around the objects). The sensing results generated / obtained in this way may be utilized for wireless sensing services (e.g., detection, tracking, etc. of objects and / or environments) provided in the wireless communication system based on the 6G network of the present specification, or may be provided / disclosed to a trusted third party.

[0267] Additionally, the sensing operation in FIG. 10 is described as a representative example of the operation in a wireless communication system based on a 6G network, but can be extended and applied to cases where terminals / base stations / signals based on networks of previous generations (e.g., 4G, 5G, etc.) are utilized.

[0268] Additionally, with respect to the wireless sensing described herein, in a wireless communication system based on a 6G network of the present specification, time / frequency resources for sensing operations and time / frequency resources for general communications (e.g., UL / DL / sidelink-based communications, etc.) may be scheduled / configured separately.

[0269] FIG. 11 illustrates time / frequency resources for sensing operations according to one embodiment of the present disclosure. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure.

[0270] Referring to FIG. 11, time / frequency resources (hereinafter, sensing resources) for the aforementioned sensing operation (e.g., sensing operation based on FIG. 10) can be set / allocated separately from time / frequency resources (hereinafter, communication resources) for general communication.

[0271] For example, as illustrated in FIG. 11, sensing resources can be set / allocated in units of symbols in the time domain and / or resource blocks in the frequency domain. Resources other than those for which the sensing resources are set / allocated can be utilized as resources for general communication. That is, sensing resources and communication resources can be set / allocated based on a time-division multiplexing (TDM) scheme and / or a frequency-division multiplexing (FDM) scheme in terms of the operation of the base station / terminal. Additionally or alternatively, unlike what is illustrated in FIG. 10, sensing resources can also be set / allocated based on other units in the time domain (e.g., slots, frames, absolute time (ms, us), etc.) and / or other units in the frequency domain (e.g., subcarriers, carriers, absolute frequencies (MHz, GHz), etc.).

[0272] Additionally or alternatively, in connection with the setting / allocation / scheduling of resources for general communication as described herein, the relationship between the resources and the aforementioned sensing resources may need to be considered. For example, when setting / allocating resources for general communication according to the embodiment(s) of the present disclosure, the resources may be set / allocated to rate-match or puncture the resource region corresponding to the sensing resource. For example, when scheduling resources for general communication according to the embodiment(s) of the present disclosure, the resources may be scheduled so as not to overlap with the resource region corresponding to the sensing resource. If the resources for general communication according to the embodiment(s) of the present disclosure and the resource region corresponding to the sensing resource are set / allocated / scheduled to overlap, one or both operations may be dropped, skipped, or postponed based on priorities, predefined rules, etc. That is, in the embodiment(s) of the present specification, it may be desirable that resources related to general communication (e.g., resources for signals / channels related to UL / DL / Sidelink-based data / control, etc.) are set / allocated / scheduled so as not to overlap with the sensing resources described above.

[0273] Additionally, various channel modeling methods may be applied in connection with the wireless sensing described herein. Channel modeling related to sensing may refer to configuring a path for transmitting and receiving sensing signals and / or scattered / reflected signals, taking into account the object being sensed and / or the environment in which the object resides. Channel modeling may be related to the performance / requirements of sensing in wireless communication systems, and thus may be an important factor in validating the sensing function.

[0274] Channels related to sensing can be divided into channels between objects (e.g., targets of interest) and sensing transmitters / receivers, and channels between the environment to which the object belongs and sensing transmitters / receivers. In this regard, channel modeling related to sensing can be divided based on sensing mode (e.g., the six types of modes described above), whether there is an object / environment, and / or sensing scenarios. For example, channel modeling for a target in a base station / terminal-based monostatic sensing mode, channel modeling for a target in a base station / terminal-based bistatic sensing mode, channel modeling for the environment in a base station / terminal-based monostatic sensing mode, and channel modeling for the environment in a base station / terminal-based bistatic sensing mode can be configured and optimized differently. For example, when various sensing scenarios are classified, channel modeling for detection, location, and tracking scenarios, channel modeling for motion recognition, and channel modeling for imaging / environment reconstruction scenarios can be divided, etc. Additionally, channel modeling related to sensing may be based on statistical channel modeling techniques and / or deterministic channel modeling techniques. For example, modeling for sensing in a wireless communication system based on a 6G network of the present disclosure may be based on stochastic geometric channel modeling techniques and / or hybrid with ray tracing channel modeling techniques. Here, the stochastic geometric channel model may be based on various statistical characteristics of the channel state. Furthermore, the hybrid channel model may be based on both ray tracing techniques and stochastic techniques.In the case of a hybrid approach, a method can be applied in which the channel for the object (e.g., the target of interest) that requires high accuracy and consistency is modeled using a ray tracing technique, and the channel for the environment is modeled using a probabilistic technique.

[0275] FIG. 12 illustrates a procedure related to a sensing operation according to one embodiment of the present disclosure. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure.

[0276] For example, in a wireless communication system based on a 6G network of the present specification, in the case of a sensing operation in which a terminal participates, the base station may need to confirm (1205) the capability of the terminal for the sensing operation. In this regard, the terminal may be configured to report capability information on whether it supports the sensing operation to the base station. Additionally or alternatively, if the terminal is defined in advance in the standard as supporting the sensing operation, the procedure may be omitted. In addition, in the case of a sensing operation in which only the base station participates, the base station may be configured to report capability information on whether it supports the sensing operation to an entity that configures / controls its sensing operation (e.g., a network entity at an upper level / layer of the base station).

[0277] For example, the base station can perform signaling with the terminal to exchange configuration information related to the sensing operation. For example, the base station can set / instruct the terminal about the mode of the sensing operation (e.g., based on the six types of modes described above), the subject of the sensing operation (e.g., sensing transmitter, sensing receiver), the resource of the sensing operation (e.g., sensing resource as in FIG. 11), the target of utilizing the sensing result (e.g., type of wireless sensing service based on 6G network, trusted third party), channel modeling for sensing (e.g., channel between the base station / terminal and object / environment), etc. (1210). For example, the base station can also set / instruct such information from a network entity at an upper level / layer of the base station.

[0278] For example, the base station and / or the terminal may perform a sensing operation based on the set / instructed information (1215). For example, the base station and / or the terminal may, as a sensing transmitter and / or a sensing receiver, perform procedures such as transmitting a sensing signal, receiving a scattered / reflected signal, deriving sensing data, obtaining a sensing result through processing the sensing data, and providing the sensing result, as in FIG. 9 described above. As an example, in the operation of the base station / terminal described herein, the sensing result provided through the sensing operation may be utilized.

[0279] Ambient IoT

[0280] Below, we explain Ambient IoT (A-IoT).

[0281] A-IoT could be a new type / segment of devices that operate solely on energy harvested from the surrounding environment. For example, A-IoT could refer to a new type of Internet of Things device that is powered by various energy sources harvested from the surrounding environment, such as radio waves, light, motion, and heat.

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

[0283] For example, A-IoT devices can be categorized into various device types, such as passive, semi-passive, and active, depending on how they store energy and generate transmission signals. For example, passive devices do not have an energy storage device (e.g., a capacitor) and can communicate based on backscatter communication technology. For example, semi-passive devices have an energy storage device and can communicate using backscatter communication technology with the help of the energy storage device. For example, active devices have an energy storage device and can actively generate signals using active RF components and the stored energy to communicate.

[0284] For example, the following basic topologies may be considered to support A-IoT devices in indoor and outdoor scenarios. For example, the basic topologies may include direct connections between base stations and A-IoT devices, connections between base stations and intermediate nodes and A-IoT devices, connection support by auxiliary nodes, and / or connections between terminals and A-IoT devices. The basic topologies proposed in this disclosure are merely examples, and the proposals in this disclosure may be extended / applied to other topologies.

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

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

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

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

[0289] FIG. 15 illustrates a topology (e.g., Topology 3) supported by an auxiliary node according to one embodiment of the present disclosure. The embodiment of FIG. 15 may be combined with various embodiments of the present disclosure.

[0290] Referring to (a) of Fig. 15, an auxiliary node may be supported for downlink reception. For example, an A-IoT device may transmit data / signals to a base station, and the A-IoT device may receive data / signals from the auxiliary node. Referring to (b) of Fig. 15, an auxiliary node may be supported for uplink transmission. For example, an A-IoT device may receive data / signals from a base station, and the A-IoT device may transmit data / signals to an auxiliary node. Here, for example, the auxiliary node may be an A-IoT-capable relay, an IAB node, a terminal, a repeater, etc.

[0291] FIG. 16 illustrates a topology (e.g., Topology 4) in which a terminal and an A-IoT device are directly connected, according to one embodiment of the present disclosure. The embodiment of FIG. 16 can be combined with various embodiments of the present disclosure.

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

[0293] For example, transmission by an A-IoT device may be performed over a frequency division duplexing (FDD) spectrum (e.g., an FDD UL spectrum).

[0294] The current NR standardization considers two device types. For example, a Type 1 device (or device type 1) has a maximum power consumption of approximately 1 uW, can store energy, has no amplification capabilities, and can transmit by backscatter a carrier wave (CW) provided externally (e.g., a reader such as a base station or terminal, or a separate node). For example, a Type 2 device (or device type 2) has a maximum power consumption of approximately several hundred uW, can store energy, has amplification capabilities, and can transmit by backscatter a carrier wave (CW) provided externally (e.g., a reader such as a base station or terminal, or a separate node) or by using an internally generated signal.

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

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

[0297] For example, some types / classes of A-IoT devices may have energy storage capabilities (e.g., capacitors or charging batteries) for the following purposes:

[0298] - Stable energy security at the time of reception / transmission

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

[0300] For example, the minimum RF reception sensitivity for operation of a low-power communication module may be -20 dBm, and the minimum reception sensitivity for energy harvesting may be -20 dBm. In this case, if the reception power of the A-IoT device ranges between -30 and -20 dBm, communication may not be possible without a capacitor, but communication may be possible after a charging time with a capacitor.

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

[0302] FIG. 17 illustrates power consumption and device energy states according to the operating states of an energy harvesting-based device with energy storage capabilities, according to an embodiment of the present disclosure. The embodiment of FIG. 17 may be combined with various embodiments of the present disclosure.

[0303] Referring to (b) of Fig. 17, S1 may be a sleep state, S2 may be an active state, and P1 and P2 may be power consumption in S1 and S2, respectively. For example, the active state may mean a state in which the device consumes power to perform operations such as receiving / transmitting for communication and sensing, and the sleep state may be a state in which it is not an active state.

[0304] Figure 17(a) may represent a device energy state corresponding to Figure 17(b). Referring to Figure F5(a), the E1 value and the E2 value may differ depending on the device (type / class), and the device may report information related to the E1 value and / or information related to the E2 value to R and / or the base station as capability parameters. For example, the E2 value may be defined as an energy value in a buffered state, and the E1 value may be defined as a minimum energy value required in an active state.

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

[0306] For example, A-IoT devices may require externally provided CW for backscatter transmission. For example, CW may be used to power A-IoT devices or as CW for downlink transmission, regardless of the transmission mode (e.g., backscatter transmission or internally generated transmission).

[0307] For example, CW waveforms can be supported in various types. For example, the CW waveform type can be a single-tone CW waveform type or a more complex multi-tone CW waveform type. For example, single-tone CW can 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 being able to transfer more energy when transmitting CW in DL, and also securing greater coverage from a single device.

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

[0309] For example, the present disclosure may propose at least one of the following for A-IoT communication: frame structure, synchronization and timing, random access, numerology, bandwidth, multiple access, waveforms, modulation, channel coding, channel / signal aspects, scheduling and timing relationships, and / or required characteristics of carrier waveforms for carriers provided external to the A-IoT device (including interference handling at the A-IoT device UL receiver and the NR base station). For example, the present disclosure may propose at least one of the following for A-IoT communication: paging, random access, data transmission including required radio resource control aspects to comply with general range limitations, interaction with upper layers (e.g., RRC layer, non-access stratum (NAS) layer, application layer, etc.), device context management, data transmission, coexistence of A-IoT and 6G / NR / LTE, and / or RF requirements for A-IoT.

[0310] For example, technical terms used in A-IoT may include:

[0311] - EH: Energy Harvesting

[0312] - EH device: A device that operates based on EH. It mainly considers RF EH, but an EH device does not necessarily have to be RF EH-based.

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

[0314] - ET: Energy Transfer

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

[0316] - CWN: Carrier Wave Node. A node that provides the CW. It may be a base station / IN / AN / UE, and there may be a separate CWN for CW provision purposes.

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

[0318] - T: Tag / ambient IoT device. This is a standard RFID term. It can be interchanged with EH device, and in the 3GPP Ambient IoT context, it mainly refers to an Ambient IoT device.

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

[0320] - R=>T: Reader-to-Tag or Reader-to-Tag communication link. If the base station or intermediate / assisting node is the reader, it can have the same meaning as DL or forward link.

[0321] - R2D: R-to-D link (can mean the same as R=>T or AmIoT DL. Can also be written as R=>D.)

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

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

[0324] - D2R: It can mean the same thing as T=>R or AmIoT UL. It can be written as D=>R.

[0325] - R<=>T: Includes cases where R=>T and T=>R, or R=>T or T=>R. It may be the case that both R=>T and T=>R apply.

[0326] - R<=>D: Includes R2D and D2R, or either R2D or D2R. This may apply to both R2D and D2R. (This may have the same meaning as R<=>T.)

[0327] - RF-EH: RF energy harvesting

[0328] - PRDCH: Physical R2D CHannel (may be written as PR2DCH). A physical channel for R2D communication.

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

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

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

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

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

[0334] - AmIoT: Ambient IoT

[0335] - F-gap: Frequency gap

[0336] - T-gap: Time gap

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

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

[0339] - EHR: Energy Headroom Report

[0340] - BPF: Band-Pass Filter

[0341] - SM: Subcarrier Modulation

[0342] - BSS: Backscattered signal

[0343] - BSC: Backscattering

[0344] - SIC: Self-Interference Cancellation

[0345] - RFID: Radio Frequency Identifier

[0346] The methods proposed in this specification can be commonly applied to both topologies 1 and 2, and UE1, which serves as a BS and an IN, is conveniently referred to as a reader. Furthermore, the present disclosure can also be applied to cases where a reader receiving a BSS can directly generate and transmit a CW, or where the node transmitting the CW is a separate node from the reader.

[0347] The Ambient IoT BS (base station) (e.g., reader) used in this specification can be a BS in topology 1 and a specific UE in topology 2. In addition, the Ambient IoT device (e.g., tag) used in this specification can be interpreted as an Ambient IoT device in both topology 1 and / or topology 2.

[0348] Referring to Table 1 and Fig. 18, in Deployment scenario 1 with topology 1 (D1T1) (indoor BS + indoor AIoT device), if the CW is within the topology, it can be defined as D1T1-A, and if the CW is outside the topology, it can be defined as D1T1-B. Finally, if there is no CW, it can be defined as D1T1-C.

[0349] D1T1-A(CW inside topology)D1T1-A1Different nodes for CW2D / R2D and D2R - 'CW' in CW2D and 'R' in D2R are different - 'CW' in CW2D and 'R' in R2D are the same - 'R' in R2D and 'R' in D2R are differentD1T1-A2Same 'CW' and 'R' nodes for CW2D, D2R and R2DD1T1-B (CW outside topology) - 'CW' in CW2D and 'R' in D2R are different - 'CW' in CW2D and 'R' in R2D are different - 'R' in R2D and 'R' in D2R are the sameD1T1-C (without CW)Only for device 2b

[0350] Next, referring to Table 2 and Fig. 19, in Deployment scenario 2 with topology 2 (D2T2) (outdoor BS + Indoor Intermediate UE + Indoor AIoT device), similarly to the above, if the CW is within the topology, it can be defined as D2T2-A, and if the CW is outside the topology, it can be defined as D2T2-B. Finally, if there is no CW, it can be defined as D2T2-C.

[0351] D2T2-A(CW inside topology)D2T2-A1Different nodes for CW2D / R2D and D2R - 'CW' in CW2D and 'R' in D2R are different - 'CW' in CW2D and 'R' in R2D are the same - 'R' in R2D and 'R' in D2R are differentD2T2-A2Same 'CW' and 'R' nodes for CW2D, D2R and R2DD1T1-B (CW outside topology) - 'CW' in CW2D and 'R' in D2R are different - 'CW' in CW2D and 'R' in R2D are different - 'R' in R2D and 'R' in D2R are the sameD1T1-C (without CW)Only for device 2b

[0352] Energy harvesting for ambient IoT communication

[0353] As described above, it is assumed that the AmIoT device has energy storage (common to all device types). When the AmIoT device receives RF power / energy and / or other power / energy greater than the activation threshold (named Act_TH for convenience in this disclosure. It can also be expressed as receiver sensitivity, and in the case of RFID, a value of about -20 dBm is used, and for the AmIoT device, a lower value such as -30 / -35 / -40 dBm can be considered) that can activate the AmIoT device, the AmIoT device can initiate operation by utilizing the energy stored in the energy storage. If the stored energy becomes low after the transmission and / or reception operation is initiated, energy harvesting (EH) may need to be performed (instead of the transmission or reception operation).

[0354] Each AmIoT device may have different amounts of energy storage, different power consumption during transmission and / or reception, different charging efficiencies when performing EH, and different transmission / reception and / or EH timings. To maximize the efficiency of AmIoT communication from a reader perspective, it may be desirable to exchange signals / channels for inventory / command / proximity services, etc., at times when as many AmIoT devices as possible can transmit and receive.

[0355] However, from the perspective of a reader who wants to communicate with many AmIoT devices, it is difficult to know which AmIoT devices are capable of communication or not, and there is a problem that even the state definition for AmIoT devices is not defined.

[0356] Meanwhile, inventory may include, for example, the process of identifying and managing a list of AmIoT devices or tags existing in the surrounding environment.

[0357] Therefore, in this specification, we aim to increase AmIoT communication efficiency by defining states according to energy storage status and / or associated AmIoT device operations and proposing an efficient method for transitioning between states.

[0358] The distinction between the proposed concepts in the following description is for convenience of explanation and should not be construed as a requirement that each proposal constitute an independent embodiment. Each proposal may be implemented individually, or at least some of the proposals may be combined.

[0359] An AmIoT device may be referred to simply as a device or a Tag.

[0360] [Proposal #1] AmIoT device state

[0361] In one embodiment, states are defined based on energy storage status and / or associated AmIoT device operation. The index for each state is arbitrarily proposed, and the order may vary.

[0362] (1) State 1: OFF

[0363] The OFF state is a state in which an AmIoT device can perform EH. In the OFF state, even if the AmIoT device receives power greater than Act_TH (threshold), it may have difficulty transmitting and / or receiving. Volatile memory (e.g., random access memory, RAM, or dynamic RAM, DRAM, etc.) may not be refreshed (or, conversely, information stored in volatile memory may be lost). Refreshing volatile memory may refer to the operation of charging volatile memory to prevent information stored in volatile memory from being erased. For example, an AmIoT device in the ON or SLEEP state may transition to the OFF state when the remaining energy falls below a specific value (TH1) or the ratio of the remaining energy to the maximum energy that the device can store falls below a specific value (TH2). The TH1 or TH2 value may be predefined or may be set / instructed by the reader, and may be defined / set / instructed differently depending on the device type.

[0364] (2) State 2: ON

[0365] When receiving a power greater than Act_TH (when the amount of energy charged simultaneously becomes greater than a specific value (TH_A1) or the ratio of the amount of energy charged to the maximum energy that the device can store becomes greater than a specific value (TH_B1)), the AmIoT device can transmit and / or receive. Volatile memory (e.g., random access memory, RAM, or dynamic RAM, DRAM, etc.) can be refreshed and maintained during the ON state (or information stored in the volatile memory can be maintained). When an AmIoT device in OFF or SLEEP state performs EH and the amount of energy charged becomes greater than a specific value (TH_A2) or the ratio of the amount of energy charged to the maximum energy that the device can store becomes greater than a specific value (TH_B2), it can transition to the ON state. At least one of the TH_A1 or TH_B1 or TH_A2 or TH_B2 values ​​may be predefined or set / indicated from the reader, and may be defined / set / indicated differently depending on the device type.

[0366] Depending on the architecture of the AmIoT device, simultaneous transmission / reception of signals / channels and EH may or may not be possible. For example, if the AmIoT device has only a single antenna and can only switch between signal / channel transmission / reception and EH, only one of the signal / channel transmission / reception and EH operations may be possible at a given point in time. As another example, even if the AmIoT device has only a single antenna, simultaneous transmission / reception of signals / channels and EH may be possible in the case of splitting-based operation, although there is a 3 dB loss. Alternatively, if the AmIoT device has separate antennas for signal / channel transmission / reception and EH, simultaneous transmission / reception of signals / channels and EH may also be possible in this case. If the AmIoT device cannot perform signal / channel transmission / reception and EH simultaneously, it can be assumed that it does not perform EH in the ON state. If the AmIoT device can perform EH simultaneously, it can be assumed that it can perform EH even in the ON state. The same principle can be applied to the simultaneous transmission and reception of signals / channels and EH in the SLEEP state.

[0367] When an AmIoT device can be equipped with one or more clocks, for convenience, the clock that consumes relatively little power is called LP-clock (low power clock), and the clock that does not can be called NM-clock (normal clock). Even when the AmIoT device is ON, it can receive AmIoT-WUS (wake-up signal) (defined separately for reception purposes via LP-clock). In this case, the AmIoT device can operate with either NM-clock or LP-clock.

[0368] (3) State 3: SLEEP

[0369] An AmIoT device in the ON state can transition to the SLEEP state depending on the amount of remaining energy and / or the time spent in the ON state, as described in [Proposal #2] below. An AmIoT device in the SLEEP state may have a separate state (or sub-state) defined based on some or all of the following factors, or even if it is classified into the same state (or sub-state), the operation of the AmIoT device in the SLEEP state may be defined differently depending on which factor is applied.

[0370] 1) Whether duty-cycle-based operation is applied: If duty-cycle is applied, the operation of maintaining the ON state for a certain time period T_1 and maintaining the SLEEP state for the next T_2 is repeated, and T_1 + T_2 represents the duty-cycle periodicity. If duty-cycle is not applied, the ON state can be maintained for a certain time period T_3 (or the ON state can be maintained without defining a time period such as T_3 and considering the energy state) and transition to the SLEEP state. Here, the T_1 and / or T_2 and / or T_3 and / or periodicity values ​​can be predefined or can be values ​​set / indicated by the reader, and can be defined / set / indicated differently depending on the device type.

[0371] 2) When duty-cycle-based operation is applied, distinction according to the length of periodicity (and / or ON period): Even if the ON / SLEEP state is switched based on duty-cycle, there may be duty-cycles with different periodicity lengths. For example, duty-cycle #1 may have periodicity #1 and duty-cycle #2 may have periodicity #2. In addition, the ON period constituting duty-cycle #1 may be T_1A, the SLEEP period may be T_2A, that is, periodicity #1 = T_1A + T_2A, and the ON period constituting duty-cycle #2 may be T_1B, the SLEEP period may be T_2B, that is, periodicity #2 = T_1B + T_2B. Here, the values ​​of T_1A and / or T_2A and / or T_1B and / or T_2B and / or periodicity #1 and / or periodicity #2 may be predefined or set / indicated by the reader, and may be defined / set / indicated differently depending on the device type. If the periodicity #1 value is relatively smaller than the periodicity #2 value, duty-cycle #1 may be named a short duty-cycle, and duty-cycle #2 may be named a long duty-cycle.

[0372] 3) When an AmIoT device can be equipped with one or more clocks, depending on which clock it operates: For convenience, a clock that consumes relatively little power is called an LP-clock (low power clock), and a clock that does not is called an NM-clock (normal clock). Depending on whether the AmIoT device operates with the NM-clock or the LP-clock in the SLEEP state, it can be distinguished into different (sub-)states, and it can operate only with the LP-clock in the SLEEP state and operate with the NM-clock (and / or LP-clock) in the ON state. In addition, the type of signal / channel to be received may be defined differently or may be set / instructed by the reader depending on whether it operates with the NM-clock or the LP-clock. For example, when operating in the SLEEP state, a preamble and / or synchronization signal (identical or similar to a signal attempted to be received in the ON state) can be received through the NM-clock, and an AmIoT-WUS (wake-up signal) (separately defined for reception purposes via the LP-clock but not received in the ON state) can be received through the LP-clock.

[0373] 4) Depending on which signal / channel is received: Depending on whether the AmIoT device receives a preamble and / or synchronization signal (same or similar to the signal it tries to receive in ON state) in SLEEP state or an AmIoT-WUS (wake-up signal) (defined separately for reception via LP-clock and not received in ON state), it can be divided into different (sub-)states, and it can receive an AmIoT-WUS (wake-up signal) (defined separately for reception via LP-clock and not received in ON state) in SLEEP state and not receive an AmIoT-WUS in ON state. When receiving an AmIoT-WUS signal in SLEEP state, the AmIoT device can operate with NM-clock or with LP-clock.

[0374] 5) Whether the memory is refreshed: Depending on whether the AmIoT device refreshes or maintains the volatile memory in the SLEEP state, it can be divided into different (sub-)states.

[0375] Considering the above factors, an embodiment of configuring sub-state(s) of SLEEP states may include at least one of the following (i) to (iv). One or more SLEEP sub-states may be defined among the following sub-states, or each of the following may represent a single state. The index for each (sub-)state is arbitrarily proposed, and the order thereof may be changed. In the present invention, the term "SLEEP state" may collectively refer to some or all of the (sub-)states as in the examples below.

[0376] (i) State 3-1: It operates on a duty-cycle basis, and operates with the same NM-clock as when it is ON even in the SLEEP state. The memory is refreshed and maintained (or the information stored in volatile memory is maintained). At this time, since the duty-cycle-based operation must operate according to the periodicity section / ON section / SLEEP section, the counter (for each section) may need to be running (for example, the AmIoT device can recognize that the periodicity time has elapsed when the counter starts running from the periodicity start point and becomes 0 or expires).

[0377] (ii) State 3-2: It operates based on duty cycle, and operates with NM-clock when ON and LP-clock when SLEEP. The memory is refreshed and maintained (or information stored in volatile memory is maintained). At this time, AmIoT-WUS (wake-up signal) (separately defined for reception through LP-clock, not received in ON state) can be received through LP-clock. At this time, since it must operate according to periodicity section / ON section / SLEEP section in duty cycle-based operation, a counter (for each section) may need to be running (for example, the AmIoT device can recognize that the periodicity time has elapsed when the counter starts running from the periodicity start point and becomes 0 or expires).

[0378] (iii) State 3-3: (Not duty-cycle-based) It can remain ON for a certain period T_3 (or remain ON without defining a time period such as T_3 and consider the energy state) and then transition to SLEEP. Memory may not be refreshed (or information stored in volatile memory may be lost). In this SLEEP state, operations via NM-clock / LP-clock may not be applied, and counters may not run.

[0379] (iv) State 3-4: Operates on a duty-cycle basis like State 3-1 or 3-2, but the periodicity and / or ON period may be longer or shorter than the duty-cycle of State 3-1 or 3-2.

[0380] Expressions such as State 3-X, 3-Y may be used to refer to States (i) to (iv) together or to refer to at least one of them.

[0381] As described above, SLEEP (sub-)states can be defined, and different types of duty-cycles (e.g., the short duty-cycle and long duty-cycle described above) can be operated while maintaining only one SLEEP state. In addition, when operating based on a long duty-cycle, if a certain condition is satisfied (e.g., when the ON period T_1B of the long duty-cycle exceeds a certain value, or when the remaining energy value or its ratio after operation during the ON period is below a certain value), the memory can be defined not to be refreshed (or the information stored in volatile memory can be lost).

[0382] As shown in the example of Fig. 20, if the energy value charged by performing EH during the OFF state exceeds a certain value, the device can transition to the ON state. If a duty-cycle-based operation is defined / set, the AmIoT device can repeatedly perform the process of transitioning to the SLEEP state and performing EH after operating in the ON state for a certain period.

[0383] [Proposal #2] State Transition Instructions

[0384] In addition to or separately from state transitions based on duty cycles and / or the remaining energy amount / rate of the AmIoT device, as in [Proposal #1], we propose a reader-directed state transition method. Specifically, at least one of the following examples may be considered.

[0385] - Instructs an AmIoT device operating in the ON state to transition to the SLEEP state.

[0386] - Instructs the AmIoT device (operating on a duty-cycle basis) to transition from the SLEEP state to the OFF state: This can cause the AmIoT device to continue to perform EH-only operations until it is fully charged.

[0387] - Instructs an AmIoT device operating in SLEEP state 3-X to transition to SLEEP state 3-Y.

[0388] - In general, it instructs an AmIoT device operating in state A to transition to state B.

[0389] An AmIoT device that receives the above instructions can perform a state transition corresponding to the instructions. Alternatively, only AmIoT devices that satisfy specific conditions can perform a state transition corresponding to the instructions.

[0390] Alternatively, state transition can be performed when a specific condition is satisfied without a separate instruction from a reader. Here, the specific condition may mean that the remaining energy amount of the AmIoT device is more than / less than a specific value (TH1), or the ratio of the remaining energy amount to the maximum energy that the device can store is more than / less than a specific value (TH2). The TH1 or TH2 value may be a value defined in advance or set / instructed by the reader, and when performing a transition from state A to state B, the TH1 or TH2 value may be the same or different depending on the combination of {A, B}, and the TH1 or TH2 value may be defined / set / instructed differently depending on the device type. For example, if the threshold defined / set for the transition from state A to state B is TH_A and the threshold defined / set for the transition from state B to state A is TH_B, then the relationship TH_B > TH_A can be set / defined to reduce frequent transitions or ping-pong effects between states.

[0391] Alternatively, Opt 1) the reader can instruct the AmIoT device in state A to transition to the lower state B, or Opt 2) the AmIoT device in state A can operate to transition to the lower state B when its energy charge falls below a certain level. In this case, state A and state B can be considered as ON / SLEEP or state 3-X / state 3-Y or SLEEP / OFF or ON / OFF, respectively, and the “certain level” above can be predefined based on the ON section (or periodicity length) of the duty-cycle and the device type, or can be a value directly set / instructed by the reader.

[0392] Some or all of the above combinations of state transitions may have latency between the time the transition instruction is received (or when specific conditions for the transition are met) and the time the transition is completed. This latency may vary by device (type) and may be reported (from the device to the reader) via capability signaling for each device (type).

[0393] It may also be necessary to determine when an AmIoT device receives a transition indication such as the above. For example, the AmIoT device may expect to receive the indication during the ON state and / or may expect to receive it outside the ON period (e.g., within the SLEEP state). If the rule is set to receive it outside the ON period, the AmIoT device may be instructed to monitor the indication within a time window immediately preceding the ON period in the duty cycle (which may be a certain gap before the start of the ON period). Furthermore, if the rule is set to receive it outside the ON period, the transition indication may be transmitted from the reader to the AmIoT device via a preamble and / or a synchronization signal (in the case of NM-clock operation) or AmIoT-WUS (in the case of LP-clock operation). Depending on the AmIoT device type and / or the current device state, the point in time at which the transition instruction is monitored and / or the signal / channel through which the transition instruction is transmitted may be defined / set differently.

[0394] Furthermore, the above transition can be applied within the same duty cycle or to the next duty cycle. If applied to the next duty cycle, it can be indicated that the transition will be applied for the next N duty cycles (i.e., the value of N).

[0395] [Proposal #3] ON section operation

[0396] For example, the On interval operation in Proposal #3 can be applied to the Duty-cycle based operation described above.

[0397] The presence of an ON period within a duty cycle can be signaled. The AmIoT device can monitor the signaling during the ON state, and / or the AmIoT device can monitor the signaling outside the ON period (e.g., within the SLEEP state). If the rule is set to monitor outside the ON period, the AmIoT device can be instructed to monitor the signaling within the time window immediately preceding the ON period in the duty cycle (the time window can be a certain gap before the start of the ON period). If the AmIoT device / terminal receives the signaling that there is no ON period, it may not transition to the ON state in the corresponding duty cycle. In addition, the above transition may be applied only within the same duty cycle or may be applied to the next duty cycle. When applied to the next duty-cycle, it can also be indicated whether there is an ON period within the next N duty-cycles (either for each duty-cycle or for N duty-cycles in common) (i.e., the value of N or whether there is an ON period for each of the N duty-cycles). Also, when applied to the next duty-cycle, it can be indicated what type of AmIoT communication will occur in the next ON period (e.g., whether it is a synchronization signal / preamble transmission or an inventory-related signal / channel or a command-related signal / channel or a proximity service-related signal / channel or an R2D RX or a D2R TX).

[0398] An AmIoT device may perform different operations within an ON period (or duty cycle) depending on the type of signal detected during the ON period. For example, a specific embodiment may include at least one of the following:

[0399] 1) If a signal for simple synchronization purposes such as a synchronization signal / preamble is found, the ON section is terminated immediately after receiving the signal: Considering an AmIoT device that assumes an initial sampling frequency offset (SFO) value as large as 10^5 ppm, it may be quite vulnerable to time / frequency synchronization. A signal for simple synchronization purposes such as a synchronization signal / preamble may be transmitted for the purpose of aligning the ON sections that occur periodically for each duty cycle among multiple AmIoT devices. In this case, the AmIoT device can determine that the ON section alignment is the purpose of the ON section without transmitting / receiving additional signals / channels for AmIoT communication, and can therefore adjust the ON section timing (e.g., synchronize time) based on the synchronization purpose signal and immediately terminate the ON section.

[0400] 2) The AmIoT device can assume different ON periods depending on the type of command received during the ON period. For example, when receiving a query signal for inventory (case 1) and when receiving a simple command (case 2), the AmIoT device can assume different ON period lengths (e.g., the ON period corresponding to case 1 is longer than the ON period corresponding to case 2). Alternatively, when receiving a specific R2D signal (e.g., preamble, command), the ON period can be extended for a set period of time (e.g., based on an inactivity timer). As another example, a WUS signal can be received during (or before) the ON period and, based on the information contained in the WUS, the AmIoT device can decide whether to end or continue the ON period. If the WUS indicates the start of inventory / query / command / proximity (including the receiving AmIoT device), the AmIoT device can extend / set the ON period according to the received message. If a WUS is received but it is determined to be unrelated to the AmIoT device, the ON section can be terminated immediately.

[0401] 3) If no simple synchronization signal such as synchronization signal / preamble is found during the ON period, it remains ON for at least the duty cycle (e.g., during the periodicity period): The AmIoT device may need to adjust the timing by receiving a synchronization signal to align the ON period or after the transition from OFF to ON period. However, if no such synchronization signal is found during the ON period, the device may continue to extend the ON period and attempt to receive the synchronization signal during the entire duty cycle. This behavior is applicable only when the AmIoT device operates on the LP-clock. If the synchronization signal is not found during the entire duty cycle, the AmIoT device may transition to OFF state (considering high energy consumption) or transition to SLEEP state for the entire next (N) duty cycles and then attempt to receive the synchronization signal during the ON period of the duty cycle.

[0402] 4) If a synchronization signal (named longP-sync for convenience) is transmitted infrequently with a periodicity of about once per duty cycle, as above, it may not be easy to align the ON periods between multiple AmIoT devices. Considering this, a synchronization signal (named shortP-sync for convenience) that is transmitted frequently with a slightly shorter period can be defined. For example, longP-sync can be transmitted once per duty-cycle periodicity, and shortP-sync can be transmitted N (>1) times per duty-cycle periodicity (the N value can be predefined or set / indicated by the reader). If an AmIoT device discovers longP-sync, it can transition to SLEEP state until the next duty cycle. However, if it discovers shortP-sync, it can transition to SLEEP state only for a time of about {duty-cycle periodicity / N} and attempt to receive longP-sync or shortP-sync. Alternatively, if it is signaled via shortP-sync which transmission number is in N times within a duty cycle (e.g., if the SFN value, count-down value starting from N, etc. are signaled), power saving can be achieved by transitioning to SLEEP state until the start of the next duty cycle based on that information. Meanwhile, if such longP-sync and / or shortP-sync signals are defined, a rule can be set to monitor the signal(s) in all or some specific state(s) among the states defined in [Proposal #1] above. In addition, the shortP-sync signal can be utilized to support scenarios with relatively tight timing requirements (e.g., AmIoT communication in TDD band).

[0403] Meanwhile, the AmIoT device can also decide on its own whether to wake up in the next ON interval based on the amount of energy consumed by the AmIoT device during the current ON interval. If the remaining energy amount / rate due to (long) R2D / D2R reception / transmission is less than or equal to a specific value (which may be predefined or set / instructed by the reader), it may not wake up for the next N ON intervals (within consecutive duty cycles) (or after a D2R reception operation during an ON interval within a specific duty-cycle regardless of the remaining energy amount / rate). A different value of N may be determined depending on the specific value of the remaining energy amount / rate. For example, N may be 1 if the remaining energy amount is less than or equal to TH_1 but greater than TH_2, or N may be 2 if the remaining energy amount is less than or equal to TH_2. Since the AmIoT device itself may not be able to determine whether to wake up during the given N value and / or ON period, the intended communication with the reader may not work properly. Therefore, the AmIoT device can directly signal whether to wake up during the N value and / or ON period through the D2R signal / channel, or report the remaining energy amount / rate to enable the reader to predict the ON period operation for the next N duty cycles. The applicability of this method may vary by device type, and for example, it may only be applied to device type 2 (or device type 2b), while device type 1 (or device type 1 / 2a) may be forced to always wake up during the given ON period.

[0404] Figure 21 illustrates an implementation example of AmIoT device and reader operation based on at least some of the above-described proposals. Even without specific mention, the above descriptions may be referenced to aid understanding of Figure 21.

[0405] Referring to FIG. 21, a device can receive configuration information from a leader (or network) (A05). For example, the configuration information can include duty-cycle-related parameters such as periodicity and the length of the ON period.

[0406] An AmIoT device can perform a state transition from OFF to ON based on its stored energy level (A10). For example, an AmIoT device can perform a state transition from OFF to ON when a certain level (threshold) of energy is stored through energy harvesting.

[0407] An AmIoT device can perform R2D signal reception (A15) and / or D2R signal transmission (e.g., transmission based on backscattering of the R2D signal) (A20). For example, the AmIoT device can perform operations such as R2D reception and / or D2R transmission when it receives energy greater than Act_TH. The R2D signal may correspond to, for example, a PRDCH (Physical R2D CHannel), and the D2R signal may correspond to a PDRCH (Physical D2R CHannel).

[0408] An AmIoT device can transition to a SLEEP state after performing operations during a configured ON period (A25). An AmIoT device can also perform energy harvesting in the SLEEP state.

[0409] According to the present disclosure, by defining states according to energy storage status and / or associated AmIoT device operations and applying an efficient state transition method, the reader can communicate with as many AmIoT devices as possible, thereby increasing AmIoT communication efficiency.

[0410] FIG. 22 illustrates a flowchart of a method performed by a first device according to one embodiment. As an example, in FIG. 22, the first device may be an ambient IoT (Internet of Things) device, and the second device may be a reader device.

[0411] Referring to FIG. 22, the first device can monitor the first signal transmitted by the second device in the first state (B05).

[0412] The first device can transition from a first state to a second state (B10). For example, the first device can transition from the first state to the second state based on at least one of the first signal or information about an energy level of the first device. The first signal can include a synchronization signal. The information about the energy level of the first device can relate to at least one of whether the energy of the first device is less than a first threshold or whether a ratio between the energy of the first device and a maximum energy is less than a second threshold.

[0413] For example, the first state may be an ON-state and the second state may be a SLEEP-state.

[0414] The first device can perform energy harvesting for energy charging of the first device based on the second signal received in the second state (B15).

[0415] The first device may operate based on a first clock in the first state, and may operate based on a second clock that consumes less power than the first clock in the second state.

[0416] The first device can monitor a wake-up signal (WUS) based on the second clock in the second state.

[0417] The first device can receive information about at least one of the first threshold or the second threshold from the second device.

[0418] The first device can switch to the second state after adjusting time synchronization based on the synchronization signal.

[0419] The first device can transmit information related to the point in time when the second device returns to the first state.

[0420] The first device can determine when to return from the second state to the first state based on energy consumed in the first state before transitioning to the second state.

[0421] The time period for operating in the second state can be determined depending on whether the synchronization signal is a first synchronization signal or a second synchronization signal transmitted with a longer period than the first synchronization signal.

[0422] FIG. 23 illustrates a flow of a method performed by a second device according to one embodiment. As an example, in FIG. 23, the first device may be an ambient IoT (Internet of Things) device, and the second device may be a reader device.

[0423] Referring to FIG. 23, the second device can transmit a first signal to the first device in the first state of the first device (C05).

[0424] The second device can transmit a second signal for energy harvesting of the first device in the second state of the first device (C10).

[0425] The second device may determine that the first device has transitioned from the first state to the second state based on at least one of the transmission of the first signal or information about an energy level of the first device. The first signal may include a synchronization signal. The information about the energy level of the first device may relate to at least one of whether the energy of the first device is less than a first threshold or whether a ratio between the energy of the first device and a maximum energy is less than a second threshold.

[0426] For example, the first state may be an ON-state and the second state may be a SLEEP-state.

[0427] The first device may operate based on a first clock in the first state, and may operate based on a second clock that consumes less power than the first clock in the second state.

[0428] The first device may transmit a wake-up signal (WUS) in the second state based on the operation of the second clock in the second state.

[0429] The second device can transmit information about at least one of the first threshold or the second threshold from the second device to the first device.

[0430] The first device can switch to the second state after adjusting time synchronization based on the synchronization signal.

[0431] The second device can receive information from the first device regarding the point in time when the second state returns to the first state.

[0432] The first device can determine when to return from the second state to the first state based on energy consumed in the first state before transitioning to the second state.

[0433] The time period for operating in the second state can be determined depending on whether the synchronization signal is a first synchronization signal or a second synchronization signal transmitted with a longer period than the first synchronization signal.

[0434] The embodiments described above are combinations of components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form embodiments or incorporated as new claims through post-application amendments.

[0435] It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the scope of the present disclosure. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present disclosure are intended to be included within the scope of the present disclosure.

[0436] The present disclosure can be used in an AmIoT device, Reader, IN, terminal, base station, or other equipment of a wireless mobile communication system.

Claims

1. In a method performed in a first device, Monitor the first signal transmitted by the second device in the first state; Transitioning from the first state to the second state based on at least one of the first signal or information about the energy level of the first device; and Including performing energy harvesting for energy charging of the first device based on the second signal received in the second state, The first signal above includes a synchronization signal, A method wherein the information about the energy level of the first device relates to at least one of whether the energy of the first device is below a first threshold or whether the ratio between the energy of the first device and the maximum energy is below a second threshold.

2. In the first paragraph, the first device, In the above first state, it operates based on the first clock, A method, wherein in the second state, the method operates based on a second clock that consumes less power than the first clock.

3. In paragraph 2, A method wherein the first device monitors a wake-up signal (WUS) based on the second clock in the second state.

4. In paragraph 1, A method further comprising receiving information about at least one of the first threshold or the second threshold from the second device.

5. In paragraph 1, A method in which the first device switches to the second state after adjusting time synchronization based on the synchronization signal.

6. In paragraph 1, A method further comprising transmitting information related to a point in time when returning from the second state to the first state to the second device.

7. In paragraph 6, A method wherein the first device determines when to return from the second state to the first state based on energy consumed in the first state before transitioning to the first state.

8. In paragraph 1, A method in which the time interval for operating in the second state is determined depending on whether the synchronization signal is a first synchronization signal or a second synchronization signal transmitted with a longer cycle than the first synchronization signal.

9. In paragraph 1, The first state is an ON-state, the second state is a SLEEP-state, The above first device is an ambient IoT (Internet of Things) device, A method wherein the second device is a reader device.

10. A non-transitory computer-readable recording medium having recorded thereon a program for performing the method described in paragraph 1.

11. In the first device, a memory configured to store instructions; and A processor configured to perform operations by executing the above instructions, The above actions are, Monitor the first signal transmitted by the second device in the first state; Transitioning from the first state to the second state based on at least one of the first signal or information about the energy level of the first device; and Including performing energy harvesting for energy charging of the first device based on the second signal received in the second state, The first signal above includes a synchronization signal, A first device, wherein information about the energy level of the first device relates to at least one of whether the energy of the first device is below a first threshold or whether the ratio between the energy of the first device and the maximum energy is below a second threshold.

12. In paragraph 11, A first device, wherein the first device is an ambient IoT (internet of things) device or a processing device configured to control the ambient IoT device.

13. A method performed by a second device, Transmitting a first signal to the first device in a first state of the first device; and Including transmitting a second signal for energy harvesting of the first device in a second state of the first device, The second device determines that the first device has transitioned from the first state to the second state based on at least one of the transmission of the first signal or information about the energy level of the first device, The first signal above includes a synchronization signal, A method wherein the information about the energy level of the first device relates to at least one of whether the energy of the first device is below a first threshold or whether the ratio between the energy of the first device and the maximum energy is below a second threshold.

14. In the second device, a memory configured to store instructions; and A processor configured to perform operations by executing the above instructions, The above actions are, Transmitting a first signal to the first device in a first state of the first device; and Including transmitting a second signal for energy harvesting of the first device in a second state of the first device, The second device determines that the first device has transitioned from the first state to the second state based on at least one of the transmission of the first signal or information about the energy level of the first device, The first signal above includes a synchronization signal, A second device, wherein information about the energy level of the first device relates to at least one of whether the energy of the first device is below a first threshold or whether the ratio between the energy of the first device and the maximum energy is below a second threshold.

15. In paragraph 14, The first state is an ON-state, the second state is a SLEEP-state, The second device is a reader device.

Citation Information

Patent Citations

  • Communication system for sensor networks

    KR1020160149992A

  • Method and apparatus for controlling of power in energy harvesting beacon system

    KR1020180032422A

Cited By

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

    US20260213783A1