Method for wireless communication and apparatus therefor

Abstract

A base station, according to one embodiment of the present disclosure, may: transmit configuration information including at least one of information on a first period in which at least one of reception or transmission of orthogonal frequency division multiplexing (OFDM) signals is performed or information on a second period in which at least one of reception or transmission of at least one low-power (LP) signal is performed; receive a wake-up signal (WUS) from a terminal in the second period; and terminate the second period and start the first period on the basis of the reception of the WUS.

Description

Method for wireless communication and device for the same

[0001] The present disclosure relates to wireless communication, and more specifically, to a method for transmitting or receiving signals between various devices in a wireless communication system and an apparatus for the same.

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

[0003] Recently, the introduction of LP-SS / WUS has been discussed in NR standardization. According to this, terminals can significantly reduce power consumption by equipping a separate WUR (wake-up receiver) that operates at low power and waking up by detecting an OOK-based LP-SS / WUS signal from the base station through the WUR. However, since the base station transmits and receives LP-SS / WUS in addition to existing NR signal transmission and reception, the introduction of LP-SS / WUS for terminals may not be effective in reducing base station power consumption.

[0004] Apart from the above, support for low-power AmIoT devices is also being discussed; however, since base stations must support AmIoT signals in addition to existing NR signal transmission and reception, the introduction of AmIoT may not be effective in reducing base station power consumption.

[0005] The technical problem to be solved by the present specification is to provide a method for transmitting and receiving signals more efficiently between wireless communication devices. For example, a period during which a base station transmits or receives signals at low power may be established or defined. A method may be provided for a terminal to request the termination of the base station's low-power operation period during the period in which the base station operates at low power. Additionally, a method may be provided for the base station to terminate the low-power operation period and respond to the terminal in response to a request from the terminal.

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

[0007] According to one aspect of the present disclosure, a method performed by a base station may include: transmitting configuration information comprising at least one of a first period in which at least one of receiving or transmitting OFDM (orthogonal frequency divisional multiplexing) signals is performed, or at least one of a second period in which at least one of receiving or transmitting a low-power (LP) signal is performed; receiving a WUS (wake-up signal) from a terminal in the second period; and terminating the second period and starting the first period based on the reception of the WUS.

[0008] The above at least one LP signal may include a non-OFDM signal.

[0009] The above non-OFDM signal may include at least one of an OOK (on-off keying) modulation signal, a D2R (device-to-reader) signal for Am-IoT (ambient internet of things), or an R2D (reader-to-device) signal.

[0010] At least one of the above OFDM signals can be transmitted or received in the second section as well.

[0011] The above at least one OFDM signal may include at least one of an SSB (synchronization signal block) or a RACH (random access channel).

[0012] The above setting information may include at least one of (i) length or offset information for at least one of the first section or the second section, (ii) information for a cycle composed of the first section and the second section, (iii) information for the start offset of the cycle, or (iv) setting information for the WUS.

[0013] The base station can transmit a downlink signal to the terminal indicating the start of the first section in response to the WUS.

[0014] For example, until the reception of the above WUS, the above first section and the above second section may be repeated alternately based on the above setting information.

[0015] For example, the second section may continue until the reception of the above WUS.

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

[0017] A base station according to another aspect of the present disclosure comprises: at least one processor; and at least one memory configured to store instructions that are executed by the at least one processor to cause the at least one processor to perform operations, wherein the operations of the processor may include transmitting configuration information comprising at least one of a first period in which at least one of receiving or transmitting OFDM (orthogonal frequency divisional multiplexing) signals is performed or at least one of a second period in which at least one of receiving or transmitting a low-power (LP) signal is performed; receiving a WUS (wake-up signal) from a terminal in the second period; and terminating the second period and starting the first period based on the reception of the WUS.

[0018] According to another aspect of the present disclosure, a method performed by a device may receive from a base station configuration information comprising at least one of a first section in which the base station performs at least one of receiving or transmitting orthogonal frequency divisional multiplexing (OFDM) signals or at least one of a second section in which the base station performs at least one of receiving or transmitting at least one low-power (LP) signal; transmit a wake-up signal (WUS) requesting the start of the first section to the base station in the second section; and receive a downlink signal from the base station indicating the start of the first section in response to the WUS.

[0019] The above WUS may be transmitted based on at least one of the following: uplink data to be transmitted in the first section is generated, the downlink reception quality in the second section is below a threshold, or the device is attempting an initial connection.

[0020] An apparatus according to another aspect of the present disclosure comprises: at least one processor; and at least one memory configured to store instructions that cause the at least one processor to perform operations by being executed by the at least one processor, wherein the operations of the processor may include receiving configuration information from the base station comprising at least one of information for a first section in which the base station performs at least one of receiving or transmitting OFDM (orthogonal frequency divisional multiplexing) signals or information for a second section in which the base station performs at least one of receiving or transmitting at least one LP (low-power) signal; transmitting a WUS (wake-up signal) requesting the start of the first section to the base station in the second section; and receiving a downlink signal from the base station indicating the start of the first section in response to the WUS.

[0021] The above device may be a terminal including a transceiver or a processing device configured to control the terminal.

[0022] According to the present disclosure, signals can be transmitted and received more efficiently between wireless communication devices. According to one embodiment, a base station can operate more power-efficiently by setting / defining a section in which the base station transmits or receives signals at low power. Even when the base station is configured to transmit or receive signals during a section in which it operates at low power, a method is provided that allows a terminal to actively request the termination of the corresponding section of the base station, thereby reducing unnecessary power consumption of the base station while satisfying the terminal's service quality requirements.

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

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

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

[0026] FIG. 3 illustrates an example of a wireless device that can be applied to the present disclosure.

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

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

[0029] FIG. 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.

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

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

[0032] FIG. 9 illustrates a beam management procedure applicable to the present disclosure.

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

[0034] FIG. 11 illustrates a time / frequency resource for a sensing operation according to one embodiment of the present specification.

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

[0036] FIGS. 13 to 16 illustrate various A-IoT topologies.

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

[0038] Figure 18 is a diagram illustrating Deployment Scenario 1 in Topology 1.

[0039] Figure 19 is a diagram illustrating Deployment Scenario 2 in Topology 2.

[0040] FIG. 20 is a diagram illustrating the state transition of an A-IoT device according to one embodiment.

[0041] Figure 21 illustrates an example of UHF passive RFID application.

[0042] Figure 22 illustrates an example of the operation procedure of a base station supporting NES technology.

[0043] Figure 23 illustrates an example of a procedure for cell DTX / DRX operation.

[0044] Figure 24 illustrates an example of a procedure for CA operation using an SSB-less SCell.

[0045] Figure 25 illustrates an example of a Conditional Handover (CHO) procedure.

[0046] Figure 26 illustrates an example of on-demand SSB transmission.

[0047] FIG. 27 illustrates examples of LP-WUS signal generation based on MC-OOK / MC-ASK.

[0048] FIG. 28 illustrates an on-demand SSB procedure according to one embodiment.

[0049] FIG. 29 illustrates an on-demand SIB1 procedure according to one embodiment.

[0050] FIG. 30 is a diagram for explaining the operation of a terminal and a base station according to one embodiment.

[0051] FIG. 31 illustrates the flow of a method performed at a base station according to one embodiment.

[0052] FIG. 32 illustrates the flow of a method performed in a device according to one embodiment.

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

[0054] A slash ( / ) or a comma used in this specification may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."

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

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

[0057] Additionally, parentheses used in this specification may mean "for example." Specifically, when indicated as "control information (ABC)," "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." Also, when indicated as "control information (i.e., ABC)," "ABC" may be described as an example of "control information."

[0058] In addition, terms such as "first," "second," etc. in this specification are used solely for the purpose of distinguishing one component from another and are not used to limit the components, nor are they used to limit the order or importance of 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 likewise, a second component in one embodiment may be referred to as a first component in another embodiment.

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

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

[0061] In this specification, a terminal is a user-side device (user equipment, UE) or a consumer-side device, and may also be referred to as a first node that receives / transmits signals from / to a base station / second node / IAB node / Transmission-Reception Point (TRP). A terminal may correspond to a physical node or a logical node. A terminal may correspond to a user-side endpoint or an intermediate point between other endpoints. In communication between two points 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 fixed-location node or a non-fixed-location (or mobile) node.

[0062] In this specification, a Base Station (BS) is a device on the network side and may also be referred to as a second node / IAB node / x-NodeB (x-NodeB, where x may be an abbreviation related to Radio Access Technology (RAT)) / Transmission-Reception Point (TRP). A Base Station may correspond to a physical node or a logical node. A Base Station may correspond to an endpoint on the network side or an intermediate point between other endpoints. In communication between two points not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), a Base Station may correspond to a serving node. A Base Station may be a node with a fixed location or a node with an indefinite location.

[0063] In this specification, higher layer parameters may be set for the terminal, pre-set, or pre-defined. For example, a base station may transmit higher layer parameters to the terminal. For example, the terminal may transmit parameters such as capability to the base station as higher layer parameters. For example, higher layer parameters may be transmitted via RRC (radio resource control) signaling or MAC (medium access control) signaling.

[0064] In this specification, information / state / parameters being "configured" or "pre-configured" may be interpreted as the information / state / parameters being provided / pre-provided to the terminal through pre-defined signaling (e.g., SIB, MAC, RRC) from the base station. In this specification, information / state / parameters being "defined" or "pre-defined" may be interpreted as being known or stored in advance by the base station and the terminal without signaling between the base station and the terminal.

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

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

[0067] <Symbols, Abbreviations, Terms>

[0068] - SSB: Synchronization Signal Block

[0069] - MIB: Master Information Block

[0070] - RMSI: Remaining Minimum System Information

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

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

[0073] - BW: Bandwidth

[0074] - BWP: Bandwidth Part (It can consist of consecutive resource blocks (RBs) on the frequency axis and correspond to a single numerology (e.g., sub-carrier spacing, CP length, slot / mini-slot duration). Additionally, multiple BWPs can be configured on a single carrier (the number of BWPs per carrier may also be limited), but the number of activated BWPs per carrier may be limited to a fraction of them (e.g., 1).)

[0075] - RNTI: Radio Network Temporary Identifier

[0076] - CRC: Cyclic Redundancy Check

[0077] - SIB: System Information Block

[0078] - SIB1: SIB1 for NR devices (i.e., Remaining Minimum System Information (RMSI)). Broadcasts information necessary for cell connection of NR terminals.

[0079] - CORESET: Control Resource Set. A time / frequency resource that an NR terminal attempts to decode candidate PDCCH. The number of CORESETs per BWP may be limited.

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

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

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

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

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

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

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

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

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

[0089] - SCS: subcarrier spacing

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

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

[0092] - TB: Transport Block

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

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

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

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

[0097] - FDRA: Frequency Domain Resource Allocation

[0098] - TDRA: Time Domain Resource Allocation

[0099] - RA: Random Access

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

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

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

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

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

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

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

[0107] - RAR: Random Access Response

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

[0109] - FH: Frequency Hopping

[0110] - iBWP: initial BWP

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

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

[0113] - CS: Cyclic shift

[0114] - NB: Narrowband

[0115] - TO: Traffic Offloading

[0116] - mMTC; massive Machine Type Communications

[0117] - eMBB: enhanced Mobile Broadband Communication

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

[0119] - RedCap: Reduced Capability

[0120] - eRedCap: enhanced RedCap

[0121] - FDD: Frequency Division Duplex

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

[0123] - DRX: Discontinuous Reception

[0124] - RRC: Radio Resource Control

[0125] - RRM: Radio Resource Management

[0126] - CAP: Channel Access Procedure

[0127] - Ucell: Unlicensed cell

[0128] - COT: Channel occupancy time

[0129] - SPS: Semi-persistent scheduling

[0130] - TBS: Transport Block Size

[0131] - MM: Mobility Management

[0132] - IWSN: Industrial Wireless Sensor Network

[0133] - LPWA: Low Power Wide Area

[0134] - RB: Resource Block

[0135] - CCE: Control Channel Element

[0136] - AL: Aggregation Level

[0137] - REG: Resource element group

[0138] - PRG: Physical Resource-block Group

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

[0140] - PBCH: Physical Broadcast Channel

[0141] - A-PBCH: Additional PBCH

[0142] - BD: blind detection

[0143] - EPRE: Energy Per RE

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

[0145] - TDM: Time Division Multiplexing

[0146] - FDM: Frequency Division Multiplexing

[0147] - DMRS: DeModulation Reference Signal

[0148] - TDD: Time Division Duplex

[0149] - PCI: Physical layer Cell ID

[0150] - BS: Base Station

[0151] - TD: Time Domain

[0152] - FD: Frequency Domain

[0153] - PEI: Paging Early Indication

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

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

[0156] - RSRP: Reference Signal Received Power

[0157] - PHR: Power Headroom Report

[0158] - PRB: Physical Resource Block

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

[0160] - SLIV: Starting and Length Indicator Value (An indicator value for the starting symbol index and number of symbols within a slot of a PDSCH and / or PUSCH; it can be set as a component of an entry constituting the TDRA field within the PDCCH scheduling the said PDSCH and / or PUSCH.)

[0161] - QCL: Quasi-Co-Location (The QCL relationship between two reference signals implies that QCL parameters, such as Doppler shift, Doppler spread, average delay, delay spread, and spatial Rx parameters obtained from one reference signal, can be applied to another reference signal (or the antenna port(s) of the corresponding RS). In NR systems, 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 a certain 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). It can be set to.)

[0162] - TCI: Transmission Configuration Indication (A single TCI state contains QCL relationships 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 'Transmission Configuration Indication' among the fields within the DCI that schedule PDSCH, the TCI state index corresponding to each code point constituting the field is activated by MAC CE, and the TCI state setting for each TCI state index is configured via RRC signaling. In Rel-16 NR systems, the corresponding TCI state is configured between DL RSs, but configuration between DL RSs and UL RSs, or between UL RSs and UL RSs, may be permitted in future releases. Examples of UL RSs include SRS, PUSCH DM-RS, and PUCCH DM-RS.)

[0163] - SRI: SRS resource indicator (Indicates one of the SRS resource index values ​​set in the 'SRS resource indicator' among the fields within the DCI that schedule PUSCH. When transmitting a PUSCH, the terminal can transmit the PUSCH by utilizing the same spatial domain transmission filter used for transmitting and receiving the reference signal associated with the corresponding SRS resource. In this case, the reference RS is set by RRC signaling via the SRS-SpatialRelationInfo parameter for each SRS resource, and the SS / PBCH block, CSI-RS, or SRS can be set as the reference RS.)

[0164] - TRP: Transmission and Reception Point

[0165] - TAG: Timing advance group

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

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

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

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

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

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

[0172] In this specification, there may be no intermediate points between the base station and the terminal, or there may be one or more. If intermediate points exist, the intermediate points may correspond to IAB nodes, relays, RF repeaters, NTN (non-terrestrial network) nodes, or nodes supporting other functions. The intermediate points may be nodes with a fixed location or nodes with an indefinite location.

[0173] FIG. 2 illustrates a communication system applicable to the present disclosure.

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

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

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

[0177] FIG. 3 illustrates an example of a wireless device that can be applied to the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0193] The second node of FIG. 4 supports dynamic spectrum sharing (DSS) and can provide connectivity to both nodes where 6G technology is implemented and nodes where pre-6G wireless communication technology (e.g., 5G, 4G) is implemented. That is, the first node of FIG. 4 may have 6G technology implemented or pre-6G wireless communication technology (e.g., 5G, 4G) implemented. Additionally, the first node and / or the second node may support full duplex mode as well as non-overlapping full duplex mode.

[0194] 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 the operation of the terminal (110) and the base station (120) transmitting and / or receiving data, and the operation performed prior to this, are illustrated. However, the operation of FIG. 4 is not limited to the operation between the terminal and the base station, but can be interpreted as the operation between the first node and the second node. Additionally, FIG. 4 illustrates the operation of direct transmission and reception of wireless signals between the terminal (110) and the base station (120), but there may be one or more intermediate points between the terminal (110) and the base station (120), and wireless signals may be transmitted and received via one or more intermediate points.

[0195] 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 at least one base station connection transmitted from the base station (120) according to a predefined rule. Here, the synchronization signal may include a plurality of synchronization signals classified according to structure or use (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 identify the boundary of the unit (e.g., frame, subframe, slot and / or symbol) constituting the wireless signal transmission of the base station (120) and obtain information about the base station (120) (e.g., cell identifier).

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

[0197] A terminal (110) and a base station (120) can perform a random access procedure (405). The terminal (110) can transmit and / or receive at least one message for a random access procedure (e.g., random access preamble, RAR (random access response) message, etc.) based on information related to the channel for the random access procedure of the base station (120) obtained through system information (e.g., channel location, channel structure, structure of supported preamble, etc.). For example, the terminal (110) can transmit a first message (e.g., preamble, MSG1) through the channel for the random access procedure, receive a second message (e.g., RAR message, MSG2), transmit a third message (e.g., MSG3) containing 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 message and the third message can be transmitted and received as a single message, or the second message and the fourth message can be transmitted and received as a single message.

[0198] 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 the connection (e.g., a radio resource control (RRC) layer), a layer that handles mapping between logical channels and transmission channels (e.g., a media access control (MAC) layer), and a layer that handles physical channels (e.g., a physical (PHY) layer). For example, the terminal (110) and the base station (120) can perform at least one of signaling to establish a connection, signaling to determine settings related to communication, and signaling to indicate allocated resources.

[0199] 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 data based on the signaling of control information and transmit and / or receive data. For example, when transmitting data, the terminal (110) or the base station (120) can perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and resource mapping on the information bits. Conversely, when receiving data, the terminal (110) or the base station (120) can perform at least one of signal extraction from resources, antenna-specific waveform demodulation, signal placement considering layer mapping, constellation demapping, descrambling, and channel decoding.

[0200] 6G System Core Technology

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

[0202] As core implementation technologies for 6G systems, 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.

[0203] artificial intelligence

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

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

[0206] Below, to provide a more specific explanation of AI (or AI / ML), terms may be defined as follows.

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

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

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

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

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

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

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

[0214] Referring to FIG. 5, a general functional framework may 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).

[0215] 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) performs data preparation based on raw data and can 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.) but may also be performed by multiple entities.

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

[0217] 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. If necessary, 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) delivered from the Data Collection function (10).

[0218] Trained / Updated Model (21): If there is a Model Storage function (50), it is used to transfer trained, validated, and tested AI / ML models to the Model Storage function (50) or to transfer updated versions of the models to the Model Storage function (50).

[0219] The Management function (30) is a function that supervises the operation of an AI / ML model or an AI / ML function. Additionally, the Management function (30) may make 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)).

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

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

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

[0223] 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 the 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 the data collection (10). If necessary, the inference function (40) may also perform data preparation (e.g., data pre-processing and cleaning, forming and transformation) based on the inference data (13) provided by the data collection function (10).

[0224] 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 an AI / ML model generated by the Inference function (30), and the details of the inference output may vary depending on the use case.

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

[0226] Model Transfer / Delivery (51) is used to transfer an AI / ML model to an inference function.

[0227] Cooperation levels can be defined as follows based on the capability of AI / ML functions among multiple nodes, and variations resulting from the combination of multiple levels or the separation of any one level are also possible.

[0228] Cat 0a) No collaboration framework: AI / ML algorithms are based on pure implementation and do not require changes to the wireless interface.

[0229] Cat 0b) This level corresponds to a framework that involves a wireless interface modified to fit efficient implementation-based AI / ML algorithms but without cooperation.

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

[0231] Cat 2) Collaborative AI / ML tasks can be performed among multiple nodes. This level requires the exchange of AI / ML model commands or network nodes.

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

[0233] AI / ML models can be classified 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.

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

[0235] 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 means that inference is performed collaboratively across multiple nodes; for example, the first part of the inference may be performed by the first node, and the remainder by the second node. Two-side models can be classified into various types as follows, depending on the training method of the AI / ML model.

[0236] - First type: An AI / ML model 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 / entities.

[0237] - 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) and model reconstruction (CSI compression by sub-use cases) 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).

[0238] - Third Type: Separate training of AI / ML models can be performed at multiple nodes (e.g., networks and terminals). Separate training may mean that training starts sequentially at one node and continues at another node. In this case, if the first node performs the AI / ML model first and shares the training data with the second node, the second node can perform the AI / ML model using the shared training data. For example, training for the CSI generation part may be performed by the terminal, while CSI reconstruction may be performed by the network.

[0239] FIG. 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.

[0240] The operations described below may be explained / interpreted based on an AI / ML model as shown in FIG. 6 below, even without separate mention (i.e., without explicit mention of being by / based on / for an AI / ML model). Furthermore, unless specifically limited, the AI / ML model may correspond to a one-side model in which inference is performed entirely by a single node or a two-side model in which joint inference is performed by multiple nodes.

[0241] First signaling (601): In the following description, 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., creation and / or reconstruction) of the AI / ML model of FIG. 5, or to inference data used for inference of the AI / ML model, or to feedback for the AI / ML model. If, in this specification, signaling between nodes is not required prior to an operation based on an AI / ML model, the first signaling (601) may be omitted. In this specification, if a one-side model is used, the unidirectional / bidirectional signaling (set) in this specification may correspond to the signaling of the first signaling (601). Additionally, when a two-side model is used in the present specification, unidirectional / bidirectional signaling in the present specification may correspond to the first signaling (601), and repetitive signaling operation may also correspond to the first signaling (601).

[0242] For example, in AI / ML model-based beam management, when a base station predicts (i.e., infers) high-quality beam(s) based on an AI / ML model, the base station can receive quality / intensity information for multiple beams from the terminal. Additionally, when a terminal predicts (i.e., infers) high-quality beam(s) based on an AI / ML model, the terminal can receive multiple beams from the base station.

[0243] AI / ML model-based operation (602): In the following description, an operation (e.g., computation, selection, prediction, etc.) at a specific node (e.g., terminal, network, etc.) or a common operation (e.g., computation, selection, prediction, etc.) at 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 without separate mention. For example, it may correspond to the training (i.e., creation and / or reconstruction) of the AI / ML model of FIG. 5 or to the inference of the AI / ML model. When a one-side model is used, an operation performed by a single node in this specification may correspond to an AI / ML model-based operation (602), and when a two-side model is used, a common operation performed by multiple nodes in this specification may correspond to an AI / ML model-based operation (602).

[0244] For example, in an AI / ML model-based BM, a base station can predict (i.e., infer) high-quality beam(s) based on an AI / ML model by using quality / intensity information for multiple beams received from a terminal as inference data. Additionally, a terminal can measure multiple beams received from a base station and predict (i.e., infer) high-quality beam(s) based on an AI / ML model by using the measurement results as inference data.

[0245] Second signaling (603): In the following description, 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 the second signaling (603) or a set of signaling generated as a result of an operation based on an AI / ML model, even without separate mention. For example, it may correspond to the output resulting from the inference of the AI / ML model of 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, the unidirectional / bidirectional signaling (set) in this specification may correspond to the second signaling (603). Additionally, when a two-side model is used in this specification, unidirectional / bidirectional signaling in this specification may correspond to the second signaling (603), and repetitive signaling operation may also correspond to the second signaling (603).

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

[0247] THz communication

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

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

[0250] Transmitting system information (i.e., information related to the attributes, characteristics, and / or capabilities of the BS required to use the service, etc.) (e.g., MIB, SIB, etc.) in the THz frequency band can be inefficient because, in the case of high frequency bands, beam sweeping must be performed more frequently to cover the entire area of ​​the cell as the beam width becomes narrow. 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 as shown in FIG. 8 below may be used.

[0251] FIG. 8 illustrates an example of a procedure for transmitting system information for THz communication to which the present disclosure applies. Although this example is written with THz conditions in mind, it is also applicable to 6G communication environments where THz is not applied. Furthermore, the procedure exemplified in FIG. 8 can be combined with various embodiments of the present disclosure described below. For example, the embodiments described below may be performed based on the system information obtained by the procedure exemplified in FIG. 8.

[0252] 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 the THz frequency band, and cell #2 uses a frequency band other than the THz frequency band. Here, the system information may include at least one information / state / parameter / setting generated at the higher layer and the physical layer, respectively. For example, at least one information / state / parameter / setting generated at the higher layer may include at least one of 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 at least one information / state / parameter / setting generated at the physical layer may include at least one of SFN, half frame indicator, and SSB index. However, this is merely an example, and system information may include information, status, parameters, and settings related to Cell #1 / Cell #2 generated at various types of physical layers / upper layers. To this end, as an example, Cell #1 and Cell #2 may have a secondary cell and primary cell relationship.

[0253] The UE can obtain synchronization for cell #1 (803). Synchronization can be obtained by detecting a synchronization signal. Generally, synchronization is obtained prior to receiving system information, but since the system information for cell #1 is received in cell #2, synchronization for cell #1 can be obtained after receiving system information. For example, the UE can obtain synchronization based on system information. However, unlike FIG. 8, synchronization may be obtained before step 801 according to other examples.

[0254] The UE can transmit a signal to connect to Cell #1 (805). For example, the signal may include information for connecting to Cell #1 (e.g., a random access preamble). The structure of the signal and the resources for transmitting the signal (e.g., a channel) can be identified through system information. Subsequently, the UE and the base station can perform a connection procedure to Cell #1 and perform communication (807). In this process, operations according to various embodiments described below may be performed.

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

[0256] Communication in the THz band is expected to experience severe path loss, and to overcome this, terminals and base stations must use very sharp beams. The use of sharp beams means that terminals and base stations must perform beam control along with beamforming, and the number of beams used becomes very large. Therefore, it takes a very long time to align the transmit and receive beams between the base station and the terminal. In addition, if the beam alignment between the base station and the terminal is misaligned due to the movement of the terminal, time is frequently required to realign the beams, which may result in an unstable link. Accordingly, a beam management procedure as shown in Fig. 9 below may be used.

[0257] 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 is applicable to a 6G communication environment. Additionally, the procedure exemplified in FIG. 9 may be combined with various embodiments of the present disclosure described below. Here, a beam may be interpreted as 'spatial (configuration) information', 'spatial domain filter', 'spatial domain transmit filter', 'spatial domain receive filter', or / and a term having an equivalent technical meaning capable of distinguishing a 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.).

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

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

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

[0261] Integrated Sensing and Communication (ISAC)

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

[0263] FIG. 10 illustrates an example of a sensing operation according to an embodiment of the present disclosure. The embodiment of FIG. 10 may 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 position (e.g., monostatic sensing), and FIG. 10(b) illustrates an example of sensing using a separated sensing receiver and a sensing transmitter (e.g., bistatic sensing).

[0264] 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, in different terminals, or in a terminal and a base station, respectively.

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

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

[0267] - Second mode: A mode in which the sensing transmitter is included in the 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)

[0268] - 3rd Mode: 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)

[0269] - 4th Mode: 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)

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

[0271] - 6th mode: A mode in which the sensing transmitter is included in the 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)

[0272] 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 or in combination.

[0273] 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 the environment surrounding 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 that is scattered / reflected by one or more objects (and / or the environment surrounding the objects) from the sensing signal transmitted from the sensing transmitter. In the sensing receiver, sensing data may be derived from the scattered / reflected signal, and sensing results may be generated / obtained through processing of the sensing data. Here, the sensing result may include characteristic information (e.g., location, distance, speed, angle, etc.) about one or more objects (and / or the environment surrounding the objects). The sensing result thus generated / acquired may be utilized for wireless sensing services (e.g., detection, tracking, etc. of objects and / or environments) provided by a wireless communication system based on a 6G network of the present specification, or may be provided / disclosed to a trusted third party.

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

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

[0276] FIG. 11 illustrates a time / frequency resource for a sensing operation according to one embodiment of the present specification. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure.

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

[0278] For example, as illustrated in FIG. 11, sensing resources may be configured / assigned in units of symbols in the time domain and / or in units of resource blocks in the frequency domain. Resources other than those configured / assigned to the sensing resources may be utilized as resources for general communication. That is, sensing resources and communication resources may be configured / assigned based on time-division multiplexing (TDM) and / or frequency-division multiplexing (FDM) methods in terms of base station / terminal operation. Additionally or alternatively, unlike that illustrated in FIG. 10, sensing resources may be configured / assigned based on other units in the time domain (e.g., slot, frame, absolute time (ms, us), etc.) and / or other units in the frequency domain (e.g., subcarrier, carrier, absolute frequency (MHz, GHz), etc.).

[0279] Additionally or alternatively, in relation to the setup / allocation / scheduling of resources for general communication described herein, it may be necessary to consider the relationship between said resources and the aforementioned sensing resources. For example, when setting / allocating resources for general communication according to the embodiments of the present disclosure, said resources may be set / allocated to rate-match or puncturing resource areas corresponding to the sensing resources. For example, when scheduling resources for general communication according to the embodiments of the present disclosure, said resources may be scheduled so as not to overlap with resource areas corresponding to the sensing resources. If resources for general communication and resource areas corresponding to the sensing resources are set / allocated / scheduled to overlap according to the embodiments of the present disclosure, either one or both operations may be dropped, skipped, or postponed based on priority, predefined rules, etc. That is, in the embodiments of this specification, resources related to general communication (e.g., resources for signals / channels related to UL / DL / Sidelink-based data / control, etc.) may be configured / assigned / scheduled so as not to overlap with the aforementioned sensing resources.

[0280] Additionally, various channel modeling methods may be applied in relation to the wireless sensing described herein. Channel modeling related to sensing may mean constructing a path for transmitting and receiving sensing signals and / or scattered / reflected signals by considering the object to be sensed and / or the environment to which the object belongs. Since channel modeling may be related to the performance / requirements of sensing in a wireless communication system, it may be an important matter for verifying the validity of the sensing function.

[0281] Channels related to sensing can be classified into channels between an object (e.g., target of interest) and a sensing transmitter / receiver, and channels between the environment to which the object belongs and a sensing transmitter / receiver. In this regard, channel modeling related to sensing can be classified based on the sensing mode (e.g., the six types of modes mentioned above), whether it is an object or an 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 an environment in a base station / terminal-based monostatic sensing mode, and channel modeling for an environment in a base station / terminal-based bistatic sensing mode can be optimized and configured differently. For example, when various sensing scenarios are classified, they can be divided into channel modeling for detection, location, and tracking scenarios, channel modeling for motion recognition, and channel modeling for imaging / environment reconstruction scenarios. 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 this specification may be based on stochastic geometry channel modeling techniques and / or hybrid with ray tracing channel modeling techniques. Here, the stochastic geometry 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, channels for objects requiring high accuracy and consistency (e.g., targets of interest) can be modeled using ray tracing techniques, while channels for the environment can be modeled using probabilistic techniques.

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

[0283] 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 verify (1205) the terminal's capability for the sensing operation. In this regard, the terminal may be configured to report capability information to the base station regarding whether it supports the sensing operation. Additionally, or alternatively, if the terminal is defined in advance in the specification as supporting the sensing operation, the procedure may be omitted. Furthermore, in the case of a sensing operation in which only the base station participates, the base station may be configured to report capability information regarding whether it supports the sensing operation to the entity setting / controlling its sensing operation (e.g., a network entity at the upper level / layer of the base station).

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

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

[0286] Ambient IoT

[0287] Below, Ambient IoT (A-IoT) is explained.

[0288] A-IoT can be a new type of device or segment that operates solely on energy harvested from the surrounding environment. For example, A-IoT can refer to a new class of Internet of Things devices that operate by being powered by various energy sources harvestable from the surrounding environment, such as radio waves, light, motion, and thermal energy.

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

[0290] For example, A-IoT devices can be classified into various device types, such as passive, semi-passive, and active, depending on the energy storage and transmission signal generation methods. For instance, passive devices do not have energy storage devices (e.g., capacitors) and can communicate based on backscatter communication technology. For instance, semi-passive devices have energy storage devices and can communicate using backscatter communication technology with the assistance of energy storage devices. For instance, active devices have energy storage devices and can communicate by actively generating signals using active RF components and stored energy.

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

[0292] 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 may be combined with various embodiments of the present disclosure.

[0293] Referring to FIG. 13, an A-IoT device can communicate directly and bidirectionally with a base station. For example, communication between a base station and an A-IoT device may include A-IoT data and / or signals. For example, A-IoT data and / or signals may be transmitted or received based on a control channel and / or a data channel (e.g., a shared channel). In the embodiment of FIG. 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.

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

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

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

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

[0298] 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 may be combined with various embodiments of the present disclosure.

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

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

[0301] Currently, NR standardization considers two types of devices. For example, a Type 1 device (or device type 1) has a maximum power consumption of approximately 1 uW, is capable of energy storage, has no amplification function, and can perform transmission by backscattering a carrier wave (CW) provided from an external source (e.g., a reader such as a base station or terminal, or a separate node). For example, a Type 2 device (or device type 2) has a maximum power consumption of approximately several hundred uW, is capable of energy storage, has an amplification function, and can perform transmission by backscattering a carrier wave (CW) provided from an external source (e.g., a reader such as a base station or terminal, or a separate node) or by using a signal generated internally.

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

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

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

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

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

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

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

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

[0310] Referring to FIG. 17(b), S1 may be a sleep state and 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 or sensing, and the sleep state may be a state that is not an active state.

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

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

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

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

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

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

[0317] For example, technical terms used in A-IoT may be as follows.

[0318] - EH: Energy Harvesting

[0319] - EH device: A device that operates based on EH. While RF EH is primarily considered, an EH device does not necessarily have to be RF EH-based.

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

[0321] - ET: Energy Transfer

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

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

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

[0325] - T: Tag / ambient IoT device. An RFID standard term. It can be used interchangeably with EH device, and in the 3GPP Ambient IoT context, it primarily refers to an Ambient IoT device.

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

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

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

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

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

[0331] - D2R: May have the same meaning as T=>R or AmIoT UL. May be denoted as D=>R.

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

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

[0334] - RF-EH: RF energy harvesting

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

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

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

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

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

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

[0341] - AmIoT: Ambient IoT

[0342] - F-gap: Frequency gap

[0343] - T-gap: Time gap

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

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

[0346] - EHR: Energy Headroom Report

[0347] - BPF: Band-Pass Filter

[0348] - SM: Subcarrier Modulation

[0349] - BSS: Backscattered signal

[0350] - BSC: Backscattering

[0351] - SIC: Self-Interference Cancellation

[0352] - RFID: Radio Frequency Identifier

[0353] The methods proposed in this specification can be applied commonly to topology 1 and topology 2, and UE1 as BS and IN is referred to as reader for convenience. In addition, the present disclosure may also apply to cases where the reader receiving the BSS directly generates and transmits the CW, or where the node transmitting the CW is a separate node from the reader.

[0354] As used herein, an Ambient IoT BS (base station) (e.g., reader) may be a BS in topology 1 and a specific UE in topology 2. Additionally, as used herein, an Ambient IoT device (e.g., tag) may be interpreted as an Ambient IoT device in both topology 1 and / or topology 2.

[0355] Referring to Table 1 and Figure 18, in Deployment scenario 1 with topology 1 (D1T1) (indoor BS + indoor AIoT device), if the CW is inside 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.

[0356] D1T1-A (CW inside topology) D1T1-A 1 Different 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 different D1T1-A 2 Same 'CW' and 'R' nodes for CW2D, D2R, and R2D D1T1-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 same D1T1-C (without CW) Only for device 2b

[0357] Next, referring to Table 2 and Figure 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 inside 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.

[0358] D2T2-A (CW inside topology) D2T2-A1 Different 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 different D2T2-A2 Same 'CW' and 'R' nodes for CW2D, D2R, and R2D D1T1-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 same D1T1-C (without CW) Only for device 2b

[0359] Data encoding and modulation for R2D / D2R

[0360] For R2D / D2R communication, low-power / low-complexity modulation methods such as ASK (e.g., OOK), PSK (e.g., BPSK), and FSK (e.g., B-FSK) can be considered. Additionally, for efficient control of R2D / D2R communication, a chip, which is the basic unit of modulation application, can be defined, and based on this, the start and / or end times between the transmission symbols (e.g., OFDM symbols) of coexisting 4G / 5G / 6G communication systems and AmIoT transmission symbols can be aligned, or parameters for R2D / D2R communication (e.g., R2D / D2R data / chip rate, FS value) can be indicated / controlled.

[0361] A chip, which is the basic unit of modulation application, can be defined as a unit of bit sequence or phase sequence at the channel / baseband / data encoder output stage. For example, when Manchester Encoding (ME, e.g., an encoding method in which data-0 is mapped to {+phase, -phase} or {1, 0} and data-1 is mapped to {-phase, +phase} or {0, 1}, or conversely, data-0 is mapped to {-phase, +phase} or {0, 1} and data-1 is mapped to {+phase, -phase} or {1, 0}) is applied to data-0, a 2-chip Manchester codeword consisting of {1, 0} is generated.

[0362] Based on the definition of these chips, codeword durations can be defined for the channel / baseband / data encoding schemes being considered in AmIoT communication. As previously explained, in the case of ME codewords, the codeword duration can be defined as 2 chips. In the case of Extended / Repeated ME (e-ME / r-ME), codeword durations can be defined as 4 chips, 8 chips, etc., depending on the degree of extension / repetition. For example, in the case of e-ME / r-ME with 4 chips, the method may be such that data-0 is mapped to {1, 1, 0, 0} or {1, 0, 1, 0}, respectively.

[0363] In the case of PIE, as shown in the UHF passive RFID application example illustrated in Fig. 21, the length of the low section (PW) is set equally by R regardless of data-0 and data-1, and data-0 and data-1 are identified by the difference in the high section. R can select / determine the lengths of data-0 and data-1 within a certain range and can instruct T regarding this selection / determination information through R=>T preamble or frame sync. To support this method in Topology 2 for AmIoT communication, the base station can set / instruct the IN (e.g., UE) information regarding the lengths of data-0 and data-1. Alternatively, it can set / instruct information regarding the difference between the length of data-0 and the length of data-1 and the length of data-0. The IN (e.g., UE) can perform R2D transmission and / or D2R reception operations using the set / instructed information.

[0364] When applying the PIE method for AmIoT communication, the chip can be defined in the following two ways.

[0365] (1) Method 1: A method of defining a chip based on the Low / off / -phase (e.g., PW in Fig. 21) duration.

[0366] The codeword / encoded (symbol) duration of Data-0 may be defined as 2 chips, and data-1 may be defined as N1 (>2) chips.

[0367] Eg, the data-0 codeword / encoded (symbol) duration may be defined in the form {high, low} with 2 chips, and the data-1 codeword / encoded (symbol) duration may be defined in the form {high, high, low} when there are 3 chips (N1=3) and {high, high, high, low} when there are 4 chips (N1=4).

[0368] To apply Method 1, the data-0 codeword / encoded (symbol) duration may be limited to twice the chip duration and the data-1 codeword / encoded (symbol) duration to an integer multiple of the chip duration, or Method 1 may be applied only when these conditions are satisfied.

[0369] (2) Method 2: A method of defining a chip based on the Reference (e.g., data-0) codeword / encoded (symbol) duration (e.g., based on Tari in Fig. 21)

[0370] It may be a method where the codeword / encoded (symbol) duration of Data-0 is defined as 1 chip, and data-1 is defined as N2 (>1) chips.

[0371] Eg, data-0 codeword / encoded (symbol) duration is defined as {high, low} with 1 chip, and data=1 codeword / encoded (symbol) duration can be {high, high, low} when 1.5 chips (N2=1.5) and {high, high, high, low} when 2 chips (N2=2).

[0372] To apply method 2, the data-1 codeword / encoded (symbol) duration may be limited to X / 2 times the chip duration (where X is an integer greater than or equal to 3), or method 2 may be applied only when these conditions are satisfied.

[0373] The codeword / encoded (symbol) duration, data rate, FS value, etc. can be controlled at the chip unit defined above, and such control information can be transmitted / instructed through preamble / midamble / postamble / sync signals and / or payload.

[0374] A Reader (or AmIoT device) may select / determine between the above-mentioned Method 1 and Method 2, and transmit / instruct the selection / decision information to the AmIoT device (or reader) through frame sync / preamble / midamble / postamble / sync signals. Alternatively, in Topology 2 for AmIoT communication, a base station may set / instruct one of Method 1 and Method 2 to an IN (e.g., UE). The IN (e.g., UE) may perform R2D transmission and / or D2R reception operations by applying the set / instructed method.

[0375] < Network Energy Saving, NES >

[0376] Rel-18 Network Energy Saving Technology

[0377] Energy conservation in base stations is considered important in wireless communication systems, including 3GPP, as it contributes to building eco-friendly networks by reducing carbon emissions and lowering the operational expenditures (OPEX) of telecommunications operators. In particular, as the introduction of 5G communication demands high transmission rates, base stations must be equipped with a greater number of antennas and provide services through wider bandwidths and frequency bands. Consequently, recent studies indicate that the energy costs of base stations have reached 20% of total OPEX. Accordingly, 5G systems are adopting various technologies to reduce energy consumption under the name of Network Energy Savings (NES), and the standardization of related technologies is expected to continue.

[0378] With the application of NES technology, the base station can perform operations such as controlling on / off for a certain duration in the time axis, controlling transmit / receive resources for UE-common or UE-specific signals / channels, changing the amount of resources in the frequency axis, controlling transmission power, or turning on / off antenna ports, TRPs (transmission-reception points), etc. in the spatial domain.

[0379] Figure 22 illustrates an example of the operation procedure of a base station supporting NES technology.

[0380] Referring to FIG. 22, the base station can identify the NES solution(s) to be applied (1305). The NES solution(s) may be related to the control of signal transmission and reception (e.g., on / off), beam operation, handover procedures, channel measurement and reporting, etc. Which NES solution(s) to apply may be adaptively selected based on the current situation (e.g., cell load level, characteristics of connected terminals, etc.) or may be predefined. The base station that has identified the NES solution(s) can perform signaling for the NES (1310). The specific signaling procedure may vary depending on the identified NES solution(s). For example, the base station may transmit common information regarding the NES solution(s), transmit configuration information necessary for NES operation to at least one terminal, or transmit control information regarding the progress of the NES operation to at least one terminal. Additionally, the base station may receive capability information related to the NES from at least one terminal. Subsequently, the base station performs operations for the NES. At this time, the base station can perform operations for NES based on the signaling performed earlier (1315). That is, depending on the system information, configuration information, and control information transmitted through the signaling, the base station can turn on / off the transmission and reception of a specific signal, turn on / off elements of the spatial domain, or adjust resources for the transmission and reception of a measurement signal.

[0381] NES technology can be performed through a procedure as shown in Fig. 22. Examples of NES solutions that can be performed by a procedure as shown in Fig. 22 are as follows.

[0382] - Intra-system energy saving solution: A RAN node may request a neighboring RAN node to switch at least one SSB beam into its inactive cell, or perform paging using a limited set of beams to an inactive terminal (e.g., a stationary terminal).

[0383] - Inter-system energy saving solution: An NG-RAN node owning a capacity booster cell can autonomously switch the cell to an inactive state.

[0384] - SSB-less SCell solution: If no SSB or SMTC (SSB-based RRM measurement timing configuration) settings are provided for the SCell, the terminal can obtain timing reference and AGC sources from other serving cells. In FR1 or FR2, the base station can set up intra-band CA or inter-band CA including an SSB-less SCell, in which case SSB / SIB transmission can be triggered by the terminal's WUS (wake-up signal). Accordingly, as the period of common channels / signals such as SSB increases, the base station can remain in a sleep state for a longer period of time.

[0385] - Cell DTX / DRX Solution: To reduce the downlink transmit / uplink receive activity time of a base station, periodic cell DTX / DRX patterns (e.g., active and inactive periods) may be set commonly for terminals within a cell having the corresponding feature. Here, the cell DTX pattern and the cell DRX pattern may be set and activated separately, and up to two cell DTX / DRX patterns may be set per MAC entity. When cell DTX is set and activated, at least one of monitoring SPS opportunities or PDCCH monitoring may be suspended during the cell DTX inactive period. When cell DRX is set and activated, at least one of transmission from CG resources or SR transmission may be suspended during the cell DRX inactive period. Cell DTX / DRX may be enabled / disabled via RRC signaling or L1 group common signaling.

[0386] Parameters such as active duration and cycle may be set for the cell DTX / DRX. The active duration is the period during which the terminal waits to transmit an SR or CG after receiving a PDCCH or SPS opportunity, and the cycle specifies the periodic repetition of the active duration and the inactive duration. When both the cell DTX and cell DRX are set, parameters such as the active duration and cycle are common. If the base station recognizes an emergency call or public safety-related service (e.g., MPS or MCS), the network may release or disable the cell DTX / DRX settings so as not to affect the service. Additionally, at least some overlap is required between the active duration of the terminal's connected mode DRX and the active duration of the cell DTX / DRX. For example, the period of the terminal's connected mode DRX may be a multiple of the cell DTX / DRX period, or vice versa.

[0387] - Conditional Handover (CHO) Solution: A CHO procedure, performed in such a way that the execution of a handover is determined by the terminal, is used while NES technology is applied (e.g., when a cell enables or disables Cell DTX / DRX). In this case, the terminal may use an NES-specific CHO event to execute a CHO for a candidate cell, and as an additional triggering condition for this, the reception of a DCI that enables CHO condition(s) set as an NES event indication may be applied.

[0388] - Spatial and power domain adaptation solution: To support the gNB for transceiver muting and / or transmission power adaptation, the terminal may be configured to report multiple CSI entries in the CSI report based on multiple sub-configurations. Each sub-configuration corresponds to a spatial domain adaptation pattern (e.g., a subset of available spatial elements) and / or a data channel (e.g., PDSCH) and a power offset between CSI and RS. Depending on the application of the spatial and power domain adaptation solution, CSI configuration, measurement, and / or reporting behavior may be affected.

[0389] Cell DTX / DRX

[0390] To operate the base station in sleep mode for a relatively long period without frequent wake-ups, base station DTX / DRX was proposed for NES purposes. The base station can reduce energy consumption by using DTX transmission under low system load conditions by setting cell DTX and setting the on-duration of terminals' C-DRX within the active period of cell DTX. FIG. 23 illustrates an example of a procedure for cell DTX / DRX operation.

[0391] Referring to FIG. 23, the base station transmits system information to the terminal (1401), and the terminal checks information related to cell DTX / DRX (1402). For example, the system information may include MIB, SIB1, etc. In relation to NES technology, MIB may include information related to cell barring (e.g., cellBarred), and SIB1 may include information related to cell barring status (e.g., cellBarredNES). Specifically, if cellBarred included in the MIB is set to a value indicating that it is not barred (e.g., notBarred), the terminal may determine that the cell is not barred, regardless of whether it supports NES cell DTX / DRX. Conversely, if cellBarred included in the received MIB is set to a value indicating that the cell is barred (e.g., barred), a terminal that does not support NES cell DTX / DRX may determine that the cell is barred. However, if the terminal has the capability to support NES cell DTX / DRX, the terminal checks SIB1 to determine the cell blocking status. If cellBarred in the MIB is set to barred and cellBarredNES is absent in SIB1, the terminal supporting NES cell DTX / DRX treats the cell as blocked and can perform cell reselection to another cell. On the other hand, if cellBarred in the MIB is set to barred and cellBarredNES is included in SIB1, the terminal supporting NES cell DTX / DRX can determine that the cell is not blocked.

[0392] In the case of FIG. 23, the terminal has the capability to support NES cell DTX / DRX, and it is assumed that cellBarred in the MIB is set to notBarred or cellBarred in the MIB is set to barred, and cellBarredNES is included in SIB1. Accordingly, the terminal can perform a random access procedure to connect to the base station (1403) and then perform communication. At this time, the base station performs a cell DTX / DRX operation and transmits configuration information related to the cell DTX / DRX operation to the terminal (1404). The configuration information related to the cell DTX / DRX operation (e.g., CellDTXDRX-Config) includes at least one parameter related to the cell DTX / DRX, and may include, for example, at least one of an on-duration timer, a cycle start offset, a slot offset, a configuration type (e.g., DTX, DRX, or DTX-DRX), and an activation state of the DTX / DRX (e.g., active, inactive). In addition, the configuration information may further include information for receiving and interpreting control information related to cell DRX / DRX (e.g., DCI-related information).

[0393] Subsequently, the base station transmits control information related to cell DTX / DRX to the terminal (1405). The control information related to cell DTX / DRX may include DCI having a specified format (e.g., format 2_9). When an operation for a serving cell is set according to at least one of cell DTX operation and cell DRX operation by configuration information (e.g., cellDTXDRX-Config), the terminal can identify a set of search spaces (e.g., Type3-PDCCH CSS set) for monitoring PDCCH that transmits control information of the specified format during the active time through an upper layer parameter (e.g., SearchSpace), and obtain the location of information about the serving cell within the control information through an upper layer parameter (e.g., positionInDCI-cellDTRX). Then, the terminal can obtain the control information based on the identified set of search spaces and location.

[0394] Control information related to cell DTX / DRX may be used to indicate the activation or deactivation of cell DTX and / or cell DRX, and / or to provide an NES-mode indicator, and may include, for example, at least one block including a cell DTX / DRX indicator and an NES-mode indicator. In this case, when the serving cell is set to a supplementary uplink (SUL) carrier, the indication for the activation or deactivation of cell DRX by the cell DTX / DRX indicator may be applied to both the UL carrier and the SUL carrier.

[0395] Subsequently, the terminal and the base station can communicate based on the cell DTX / DRX (1406). Specifically, the base station can turn on / off the transmission and reception of signals according to the settings related to the cell DTX / DRX, and accordingly, the terminal can selectively monitor signals from the base station. During DTX-OFF, the base station enters sleep mode to reduce energy consumption. At this time, the base station DTX cycle can be aligned with the terminal DRX cycle. The base station DTX-ON can completely cover the terminal's DRX-ON. Furthermore, the base station can align the transmission of Xn / NG and the transmission of Uu for NES purposes. The DTX / DRX mechanism triggers the switching of reference signal resource set groups, and the base station can perform dormancy-like behavior of transmitting SSB, SIB, and CSI-RS sparingly or not transmitting them to reduce energy consumption. The terminal can receive downlink signals / channels sparingly or not receive them according to the base station's settings. Once the base station DTX / DRX operation is triggered, during the DTX / DRX OFF period, the terminal can discontinuously receive the corresponding CSI-RS, SSB, or PDCCH.

[0396] SSB-less SCell

[0397] Figure 24 illustrates an example of a procedure for CA operation using an SSB-less SCell.

[0398] Referring to FIG. 24, the base station transmits configuration information for SCell to the terminal. That is, the base station transmits configuration information for CA to provide services to the terminal through CA operation. Here, the CA operation may be intra-band CA or inter-band CA. For example, the configuration information for SCell may include information containing information for adding SCell (e.g., sCellToAddModList), and specifically, may include a cell index, physical cell identifier, information related to DL-UL settings, information related to BWP, information related to cell DTX / DRX, information related to downlink frequency (e.g., FrequencyInfoDL), etc. Subsequently, the terminal determines the settings for CA operation and can perform communication using the base station's PCell and SCell. At this time, the terminal can confirm that the SCell is an SSB-free SCell based on the information related to the downlink frequency included in the configuration information and can check the related parameters. For example, the terminal can determine that the SCell is an SSB-less SCell by confirming the existence of a parameter (e.g., SSBlessSCell) indicating that it is an SSB-less SCell, and can determine the timing reference and AGC source for the SCell based on information about the reference cell (e.g., referenceCell). In the case of FIG. 24, the reference cell may be a PCell. Therefore, the terminal can use the PCell as the timing reference and AGC source for communication in the SCell.

[0399] Conditional Hand Over (CHO)

[0400] FIG. 25 illustrates an example of a Conditional HandOver (CHO) procedure. The order of the actions exemplified in FIG. 25 may vary depending on the case.

[0401] Referring to FIG. 25, the base station transmits configuration information for CHO to the terminal (1601). The configuration information for CHO may include information related to conditional reconfiguration (e.g., ConditionalReconfiguration, CondReconfigToAddModList) and information related to the configuration for reporting (e.g., ReportConfigNR). Here, the information related to the configuration for reporting may include information related to events related to reporting, identifiers of events (e.g., condEventId), information indicating whether it is an NES-specific CHO event (e.g., nesEvent), etc. In the example of FIG. 25, event information indicating that it is an NES-specific CHO event is received.

[0402] The base station transmits information to the terminal that enables NES-specific CHO execution conditions (1602). The information that enables NES-specific CHO execution conditions may be transmitted via control information of a specified format (e.g., DCI format 2_9). The information that enables NES-specific CHO execution conditions may be referred to as an NES-mode indicator, and, for example, as 1-bit information, an associated upper layer parameter (e.g., nesEvent) is set, and if the serving cell of the associated block in the corresponding DCI is the primary cell, it indicates that NES-specific CHO execution conditions are enabled.

[0403] Subsequently, the terminal performs a measurement (1603) and transmits the measurement report to the base station (1604). The base station determines the CHO based on the measurement report and performs signaling for a handover request with adjacent base stations indicated by the measurement report (1606). The base station determines the adjacent base stations that have affirmed admission through signaling as candidate base stations and transmits information about the candidate base stations to the terminal (1607). Accordingly, the terminal evaluates the CHO execution conditions for the candidate base stations (1608). Accordingly, when a candidate cell satisfying the conditions is determined, the terminal detaches from the old cell and synchronizes with the new cell (1609). At this time, since the terminal has previously received event information indicating that it is an NES-specific CHO event and has also received information enabling the NES-specific CHO execution conditions, it can determine whether the event is satisfied. In other words, when an NES-mode indicator is received through a lower layer and conditional triggering configuration information (e.g., condTriggerConfig) includes information indicating that it is an NES-specific CHO event (e.g., nesEvent), the terminal determines that an event associated with a corresponding measurement identifier (e.g., measId) is satisfied, and accordingly, can determine that the CHO execution condition is satisfied.

[0404] NES Enhancement

[0405] In 3GPP NR release 19, discussions on NES enhancement are scheduled to take place, and (1) on-demand SSB, (2) on-demand SIB1 transmission and (3) adaptation of common signal / channel transmissions are being considered as major targets.

[0406] (1) On-demand SSB

[0407] A method to reduce energy consumption can be discussed in which the base station transmits SSBs to specific cells through an on-demand SSB process and does not transmit SSBs to those cells when the on-demand SSB process is not present. In existing NR systems, it was difficult to reduce energy consumption even when the base station had no data to receive or send, as SSBs had to be transmitted periodically at all times for purposes such as time / frequency synchronization or RRM measurement. Considering this, the base station's energy consumption can be reduced by allowing it to refrain from transmitting SSBs and only perform transmissions when the on-demand SSB process is involved. This on-demand SSB process can be triggered through one of the following methods.

[0408] 1) The terminal requests the base station's SSB transmission by transmitting an uplink signal / channel (e.g., PRACH, PUCCH, PUSCH, SRS, etc. in an NR system).

[0409] 2) Base Station (or TRP) #1 requests SSB transmission from Base Station (or TRP) #2 via an interface between base stations (e.g., Xn interface in an NR system) or backhaul signaling.

[0410] 3) Signal whether the corresponding SSB is transmitted via Scell ​​activation / deactivation signaling

[0411] Considering coexistence with existing NR terminals, the on-demand SSB operation for connected mode terminals and SCells in Release 19 is limited, but in future releases or next-generation communication systems, on-demand SSB operation (for SSB transmission on a PCell) may be defined considering inactive or idle mode terminals or initial connected terminals. Additionally, carrier aggregation (CA) including the SCell may be applied to both intra-band CA and inter-band CA, and the SSB on the SCell transmitted through the on-demand SSB process may be utilized for at least time / frequency synchronization, L1 / L3 measurement, SCell activation, and other functionalities.

[0412] (2) On-demand SIB1 transmission

[0413] A method to reduce energy consumption can be discussed in which the base station transmits a SIB1 for a specific cell through an on-demand SIB1 process, and does not transmit the SIB1 for that cell when the on-demand SIB1 process is not present. In existing NR systems, it was difficult to reduce energy consumption even when the base station had no data to receive or send, because it was always necessary to periodically provide a SIB1 containing system information and random access information for initial access or idle mode terminals to connect to a cell. Considering this, the base station's energy consumption can be reduced by allowing it to refrain from transmitting SIB1 and only transmit it when the on-demand SIB1 process is involved. The base station's SIB1 transmission can be triggered by the terminal transmitting an uplink signal / channel (e.g., PRACH in an NR system), and specifically, the following scenarios can be considered, but may not be limited to them.

[0414] 1) Scenario 1: As shown in FIG. 26 (a), a terminal that receives an SSB (and / or other downlink signal / channel) at cell #1 and recognizes that SIB1 is not being transmitted on cell #1 can trigger the transmission of SIB1 by transmitting a signal requesting SIB1 (for convenience, the signal is referred to as WUS, wake-up signal) based on information provided by the SSB (and / or other downlink signal / channel) and / or predetermined information. A base station that receives the WUS can transmit a specific DL signal / channel on cell #1 in response, or transmit SIB1 on cell #1 (or without transmitting the DL signal / channel).

[0415] 2) Scenario 2: As shown in FIG. 26 (b), a terminal that receives an SSB (and / or other downlink signal / channel such as SIB1) at cell #1 and realizes that SIB1 is not being transmitted on cell #2 may attempt to camp-on through cell #2. Based on the information provided in the received SSB (and / or other downlink signal / channel such as SIB1) and / or predetermined information, the terminal may transmit a signal requesting SIB1 (i.e., WUS) onto cell #1 to trigger the transmission of SIB1 to cell #2. A base station that receives the WUS may transmit a specific DL signal / channel (on cell #1 or cell #2) in response, or transmit SIB1 to cell #1 or cell #2 (or without transmitting the DL signal / channel).

[0416] 3) Scenario 3: As shown in FIG. 26 (c), a terminal that receives an SSB (and / or other downlink signal / channel such as SIB1) at cell #1 and realizes that SIB1 is not being transmitted on cell #2 may attempt to camp-on through cell #2. Based on the information provided by the received SSB (and / or other downlink signal / channel such as SIB1) and / or predetermined information, the terminal may transmit a signal requesting SIB1 (i.e., WUS) onto cell #2 to trigger the transmission of SIB1 for cell #2. A base station that receives the WUS may transmit a specific DL signal / channel (on cell #1 or cell #2) in response, or transmit SIB1 for cell #2 onto cell #1 or cell #2 (or without transmitting the DL signal / channel).

[0417] (3) adaptation of common signal / channel transmissions

[0418] Methods to reduce energy consumption by controlling common signal / channel transmissions such as SSB, PRACH, and paging can be discussed. While completely turning off the SSB can significantly reduce the energy consumption of the base station, the absence of an SSB that performs functions such as time / frequency synchronization or RRM measurement may result in unstable operation for the corresponding cell from the terminal's perspective. Considering this, energy saving effects for the base station can be achieved by changing the transmission pattern of the SSB (e.g., transmission period, period per SSB candidate index(es), SSB candidate index(es) transmitted within one transmission period, transmission power, etc.) depending on the situation.

[0419] In the case of PRACH resources, in the case of contention-based random access, energy consumption can increase because the base station always attempts to receive from the configured PRACH resources since it is unknown when the terminal will transmit PRACH. Considering this, the energy of the base station can be saved by applying methods to adjust the amount of PRACH resources (e.g., adjusting the period of the PRACH resources, adjusting the amount of resources by pre-configuring PRACH resource set #1 and set #2 and giving instructions such as whether to turn on only one set or both sets, or providing the amount of PRACH resources corresponding to each SSB index uniformly or non-uniformly).

[0420] In the case of paging, conventionally, paging frames (PF) and / or paging occasions (PO) were distributed along the time axis within the DRX cycle (or paging cycle), and terminals attempted to receive paging at specific PF / POs derived from their ID-based formulas. From the base station's perspective, if it intended to transmit paging to multiple terminals simultaneously, it was necessary to transmit paging while frequently breaking the data. To reduce the resulting energy consumption of the base station, it is possible to consider placing the PF and / or PO for paging reception as close to the time axis as possible, or placing them using different frequency axis resources within the same timeframe.

[0421] LP-WUS

[0422] The generation / transmission and reception of LP-WUS signals may be (for example) as follows, but are not necessarily limited thereto.

[0423] In conventional NR systems, base stations generate and transmit OFDM signals for control and data signals, and terminals can receive these OFDM signals using a coherent detection / demodulation-based receiver that requires (relatively) accurate synchronization. In other words, this requires RF modules and baseband modules such as power-consuming bandpass filters, FFTs, and local oscillators. However, to receive signals at low power in LP-WUR, a non-coherent detection / demodulation-based receiver that does not require such power-consuming modules can be used. Additionally, OOK (on-off keying) and FSK (frequency shift keying) can be used as LP-WUS signals for such receivers. Meanwhile, if an LP-WUS generated in a manner completely different from conventional NR signal generation is introduced, network vendors may face the burden of having to build transmitters for generating new signals.

[0424] As one method to transmit these OOK / FSK signals while maximizing the utilization of the base station's OFDM transmitter, MC-OOK (multi-carrier OOK) or MC-FSK signals can be used. In this case, an MC-OOK (or MC-FSK) signal refers to a signal generated by using only a subset of the OFDM subcarriers to create a time-domain waveform similar in shape to, for example, the OOK (or FSK) waveform. Through this, reception based on non-coherent detection / demodulation can be achieved at the receiver while maximizing the utilization of the OFDM transmitter.

[0425] waveform example for LP-WUS

[0426] The method of generating the LP-WUS signal may be (for example) one of the following, but is not limited to.

[0427] (1) MC (multi-carrier)-OOK (on-off keying) or MC-ASK (amplitude shift keying) for M-bit transmission

[0428] Figure 27 illustrates examples of LP-WUS signal generation based on MC-OOK / MC-ASK.

[0429] Referring to FIG. 27, for MC-ASK waveform generation, it is assumed that K represents the iFFT size of CP-OFDMA and N represents the number of subcarriers (SC) used by LP-WUS (including potential guard bands). For this, at least one of the following methods may be used.

[0430] (a) Option OOK-1: 1 OFDM in-symbol single-bit method

[0431] The SCs of LP-WUS operate as follows.

[0432] If OOK=1, all SCs are modified.

[0433] If OOK=0, all SCs are set to zero power (from a baseband perspective).

[0434] (b) Option OOK-2: Parallel M-bit OOK in the frequency domain

[0435] N LP-WUS SCs are divided into M segments (M = 2 in the drawing), and guard bands may exist between or around the segments.

[0436] If OOK=1, all SCs of the corresponding segment are modified.

[0437] If OOK=0, all SCs in the corresponding segment are set to zero power (from a baseband perspective).

[0438] (c) Option OOK-3: Multitone Single Bit OOK

[0439] N LP-WUS SCs are divided into L segments (L = 2 in the drawing), and there are no guard bands between the segments, but there may be some around them.

[0440] When OOK=1, one subcarrier known by the UE is modulated for each segment, and the remaining SCs are set to zero power (in terms of baseband).

[0441] If OOK=0, all SCs of all segments are set to zero power (from a baseband perspective).

[0442] (d) Option OOK-4: M-bit OOK conversion in the time domain

[0443] N SCs (OOK-1 based) are generated by transformations (e.g., DFT / least squares).

[0444] - N' samples are generated from M bits.

[0445] - Signal modification may or may not be used.

[0446] - Truncation or other additional modifications may or may not be used, and if not used, N is equal to N'.

[0447] N' can be the same as K.

[0448] For example, the above OOK-4 method can be viewed as a process in which, in order to send an M bit LP-WUS payload, M bits are first changed to M1 bit / sample (each bit is repeated as M0 bit / sample or a sequence of M0 bit / sample is mapped to each bit), N' bit / sample is generated by passing through the 'signal generation and modification' and / or 'DFT / Least Square' blocks shown in the figure, and then N bit / sample is input to the IFFT through the process of truncation of N' to N.

[0449] (2) MC-FSK (frequency shift keying) for M-bit transmission

[0450] (a) Option FSK-1: N LP-WUS subcarriers (SC) are divided into M pairs of segments, and guard bands may exist between and around the segments.

[0451] A segment may include a single subcarrier or multiple consecutive SCs.

[0452] In a segment pair, one segment is modulated and the other is set to zero power (in terms of baseband).

[0453] (b) Option FSK-2: N LP-WUS SCs are 2 M It is divided into segments, and guard bands may exist between and around the segments.

[0454] A segment may include a single subcarrier or multiple consecutive SCs.

[0455] 2 M Only one of the segments is modulated, and the SC of the remaining segments is set to zero power (in terms of baseband).

[0456] Low power transceiver for network energy saving

[0457] As described above, the AmIoT device can receive an R2D signal from a reader and transmit a D2R signal by performing backscattering on the CW or generating an internally generated signal. In performing these transmission and reception operations, the AmIoT device may consume only a peak power of several hundred μW. On the other hand, since the base station / reader performing AmIoT communication simultaneously performs NR communication as well as AmIoT communication in the same / adjacent frequency band, from the perspective of the base station, it may be difficult to obtain a significant reduction in power consumption by performing AmIoT communication.

[0458] In addition, according to discussions on the introduction of LP-WUS in Rel-19 NR, power consumption can be significantly reduced by having a terminal implement / equip a separate low power (LP) receiver / RF (or WUR: wake-up receiver) and attempting to receive OOK-based signals from the base station through the WUR (rather than the MR: main radio). On the other hand, since the base station communicates with WUR-supported terminals while simultaneously communicating with existing NR terminals in the same / adjacent frequency band, it may be difficult to obtain a significant reduction in power consumption from the base station's perspective by transmitting LP-WUS signals.

[0459] Assuming that all terminals in a next-generation communication system are capable of AmIoT communication and / or LP-WUS transmission and reception, base stations can also be equipped with low-power transceivers (especially when there is no significant data traffic) and can enjoy energy saving effects by operating only the low-power transceivers.

[0460] Therefore, in this specification, a low-power transceiver / radio / RF implemented by a base station is defined for convenience as an ESR (energy saving radio) (e.g., when the base station operates as an ESR, it can perform AmIoT communication and / or LP-WUS transmission / reception), and a method is proposed to obtain an energy saving effect by operating the said ESR.

[0461] In addition, it is assumed in the present disclosure that the terminal also has MR and LP-R implemented (AmIoT communication and / or LP-WUS transmission / reception can be performed when the terminal operates as a low-power radio).

[0462] [Proposal #1] Switching between Main Radio (MR) and ESR (Energy Saving Radio)

[0463] For example, a base station switching operation between MR and ESR is proposed, and detailed information regarding the operation of the base station and terminal in the MR and ESR sections is described in subsequent proposals.

[0464] The base station may perform periodic switching operations between MR and ESR. To perform such switching operations, information regarding the entire cycle and the MR and / or ESR periods may be signaled from the base station. For example, one cycle may include the MR duration and the ESR duration, and the cycle may be set periodically. In this case, the reference point where the cycle starts may be a value that is predefined (e.g., system frame number 0) or separately signaled, and the periodicity and / or offset value of the cycle may be signaled from the reference point. Within the cycle, at least one of the offset and / or duration value of the MR period and the offset and / or duration value of the ESR period may be (separately) signaled / set. Alternatively, once the MR (or ESR) period is determined, the remaining period within a single cycle may be determined as the ESR (or MR) period. For example, if the cycle period is signaled as 320 ms, the terminal recognizes that the cycle is repeated with a period of 320 ms from system frame number 0, and if the MR duration is signaled as 100 ms, the terminal recognizes that within the 320 ms cycle, the (front) 100 ms is the period during which the base station's MR operates and the remaining 220 ms is the period during which the base station's ESR operates.

[0465] Depending on the situation, the MR section may be expanded / contracted, the ESR section may be contracted / expanded, or the MR / ESR section may be created opportunistically. For example, when a specific signal (e.g., UL WUS, PRACH, PUCCH, PUSCH, SRS, D2R) (from a terminal) is received in the MR section, or when a DL signal / channel (PDCCH, PDSCH, DM-RS, CSI-RS, LP-WUS) to be sent to a terminal is generated, the MR section of the base station may be expanded. As another example, when a specific signal (e.g., UL WUS, PRACH, PUCCH, PUSCH, SRS, D2R) (from a terminal) is received during the ESR period, or when a DL signal / channel (PDCCH, PDSCH, DM-RS, CSI-RS, LP-WUS) to be sent to a terminal is generated, the base station may switch to the MR period (for a predefined or set duration, or for the same amount of time as the MR period determined within the cycle) or operate only in MR, rather than in cycle-based operation where MR / ESR is switched.

[0466] As another example, a base station may operate in ESR mode and switch to MR upon receiving a request from a terminal. In the case of such periodic switching between MR and ESR, the terminal can predict when the base station will operate in MR mode; however, for the base station, operating in MR mode periodically may be disadvantageous from an energy-saving perspective. Therefore, it may be more advantageous for the base station to continue operating in ESR mode until a separate request is made from the terminal. To support this operation, it may be necessary to define the UL signal / channel through which the terminal requests the base station's MR switching (e.g., (early) termination of the ESR operation period / initiation of the MR operation period). When the terminal's UL signal / channel requesting the base station's MR switching is defined as an MR WUS (e.g., referred to as an MR WUR since it is a WUS for waking up the base station's MR), at least the following items regarding the said MR WUS may be defined in advance or configured by the base station. Meanwhile, MR WUS may be referred to as UL WUS or simply WUS, or more generally as UL signal.

[0467] - Time axis resources (e.g., symbol / slot position / count, M value for OOK signal generation, chip duration / count)

[0468] - Frequency axis resources (e.g., sub-carrier / RB location / number, small / large frequency gap size from CW in AmIoT communication)

[0469] - Sequence information (e.g., sequence type / length, cyclic shift value, modulation method such as ASK / PSK / FSK, line coding method such as Manchester encoding)

[0470] By transmitting the MR WUS signal defined / configured in this way, the terminal can expect the base station operating in ESR to switch to MR. Alternatively, if the base station successfully receives the MR WUS signal, it may explicitly transmit whether the MR WUS reception was successful via a DL signal / channel (e.g., LP-WUS, PDCCH), and the terminal receiving the said DL signal / channel can expect the base station to switch to MR. Alternatively, (in addition to the signaling of the MR WUS reception success via the base station's DL signal / channel (e.g., LP-WUS, PDCCH), or even without such signaling), the terminal can expect the base station to switch to MR after transmitting the MR WUS signal defined / configured in this way and receiving a signaling for ESR-to-MR switching (as proposed below). When the terminal receives such signaling from the base station, the terminal may receive the signaling in either the MR or LP-R state, and if terminal switching between MR and LP-R is required, the following processing time may be required. In addition, triggering conditions for the terminal to transmit MR WUS may be defined, and the terminal may transmit MR WUS if at least one of the following examples is satisfied.

[0471] - UL data arrival

[0472] - When the DL reception quality value is below a (predefined / set) threshold value: This may be to cause the base station to operate in MR so that the terminal receives DL signals from the base station more frequently, thereby increasing measurement accuracy and determining whether to continue communication in the serving cell or handover to another cell. Here, the reference signal for measuring the DL reception quality value may be predefined or set, and may be, for example, at least one of LP-SS, LP-WUS, and SSB.

[0473] - When the terminal attempts an initial connection (as in the example of Proposal #3 below)

[0474] As described above, when switching between the MR / ESR of the base station or extension of a specific section occurs, or when the switching pattern between the MR / ESR changes, it may be necessary to notify a specific terminal or multiple terminals of this.

[0475] - For example, the base station can notify the terminal of that switching from the MR phase to the ESR phase (or from the ESR phase to the MR phase) starting from slot T through UE-specific, group-common, or cell-specific DL signals / channels (e.g., PDCCH, LP-WUS, LP-SS, SSB, PDSCH) transmitted at slot T or before slot T. Upon receiving the DL signals / channels, the terminal can recognize that the base station is operating in the ESR phase (or MR phase) starting from slot T.

[0476] - For example, the base station may notify the terminal via UE-specific, group-common, or cell-specific DL signals / channels (e.g., PDCCH, LP-WUS, LP-SS, SSB, PDSCH) that the MR period (or ESR period) may continue for an additional period of time until slot T. Upon receiving the said DL signals / channels, the terminal can recognize that the base station maintains the MR period (or ESR period) until slot T.

[0477] - For example, when multiple candidates for switching patterns between MR / ESR are defined / configured, the base station can notify the terminal of which candidate pattern will be applied from slot T time through UE-specific, group-common, or cell-specific DL signals / channels (e.g., PDCCH, LP-WUS, LP-SS, SSB, PDSCH).

[0478] A terminal that receives the corresponding DL signal / channel can know the MR / ESR switching pattern that the base station will apply from slot T.

[0479] Additionally, the base station may signal whether an MR (or ESR) segment exists within an MR / ESR switching cycle, and may inform the terminal whether the next N (where N is a value that is predefined or set, e.g., N=1) MR (or ESR) segments exist or not through signaling in a specific defined segment (e.g., a time window that is a certain time segment ahead of the start point of the MR / ESR segment). Upon receiving such signaling, the terminal can determine whether N MR (or ESR) segments exist in the future. When the terminal receives such a DL signal / channel or signaling from the base station, it may receive the signaling in an MR or LP-R state, and if terminal switching between MR and LP-R is required, the following processing time may be required.

[0480] Meanwhile, if cell DTX / DRX operation is configured, the base station may operate in MR during the base station's DTX / DRX active period and in ESR during the non-active period. Conversely, when the base station operates in MR, the terminal / base station may perform operations defined / configured during the cell DTX / DRX active period, and when the base station operates in ESR, the terminal / base station may perform operations defined / configured during the cell DTX / DRX non-active period. Additionally, the terminal's switching operation between MR and LP-R may be performed according to whether the base station is operating in MR or in ESR. Specifically, through the above methods, a terminal that recognizes that the base station is operating in MR may perform MR operations during that period, and a terminal that recognizes that the base station is operating in ESR may perform LP-R operations during that period.

[0481] When a base station performs switching from MR to ESR and / or switching from ESR to MR, a processing time may be considered. This processing time may be a value that is predefined or reported by the base station. Likewise, when a terminal performs switching from MR to LP-R and / or switching from LP-R to MR, a processing time may be considered, and this processing time may be a value that is predefined or reported by the terminal to the base station through capability signaling.

[0482] [Proposal #2] Base Station / Terminal Operation in Main Radio (MR) and ESR (Energy Saving Radio) Sections

[0483] During the ESR period, the base station may not transmit or receive at least some of the OFDM-based signals supported during the MR period. For example, by performing (only) the transmission and reception of at least some of the D2R / R2D signals / channels, CW, or LP-SS / LP-WUS for AmIoT communication instead of OFDM-based signals, the energy consumption of the base station can be significantly reduced by operating only radios that have much lower complexity and lower power consumption. However, considering the importance of some channels, channels that the base station must transmit and receive may be defined even during the ESR period, and may include at least one of the following signals / channels.

[0484] - DL SSB transmission (for performing DL measurements on the terminal, etc.)

[0485] - Receive UL RACH (for initial connection or random access procedure support)

[0486] - Positioning reference signal transmission

[0487] - CSI-RS (for tracking) transmission

[0488] - Energizing signal (such as CW for energy harvesting of AmIoT communication terminals)

[0489] In the case of the above energizing signal, there may be a constraint that the energizing signal is transmitted only at the time of SSB transmission to minimize energy consumption of the base station.

[0490] When considering AmIoT communication, the following operations can be performed during the base station's ESR interval.

[0491] - At least for idle mode terminals, an R2D signal needs to be transmitted (periodically). This R2D signal may be primarily needed to synchronize time / frequency between the base station and the terminal. Alternatively, the terminal may be allowed to measure the DL reception quality of the serving / neighboring cell based on this R2D signal.

[0492] - Even if the base station is in an ESR period, CW transmission can be performed (e.g., CW inside topology), or CW transmission during the ESR period can be performed at a separate node (e.g., CW outside topology). If the base station transmits CW during an ESR period, it may be advantageous in terms of minimizing energy consumption to generate and transmit CW based on a single carrier (with a sampling clock lower than that of OFDM signal transmission) rather than transmitting CW based on OFDM single (or multi) tone.

[0493] - During the ESR period, the base station may continue to receive D2R signals from the terminal. Depending on the D2R signal received, the base station may decide whether to remain in ESR or switch to MR. If the received power of the D2R signal is low, or if the D2R signal contains information indicating that the terminal transmitting the D2R signal is an AmIoT device type 1 / 2a, the base station may perform DL signal / channel (e.g., SSB) transmission with reduced TX power applied. This is intended to minimize the imbalance between DL coverage and UL coverage, and it may be desirable to apply relatively low transmission power when serving only cell center terminals or low UL power terminals.

[0494] When considering LP-SS / LP-WUS communication, the following operations may be performed during the base station's ESR interval. Meanwhile, the LP WUS transmitted downlink to the terminal may be referred to as DL WUS or simply WUS.

[0495] - At least for idle mode terminals, it is necessary to periodically transmit LP-SS signals. These LP-SS signals may be primarily needed to synchronize time / frequency between the base station and the terminal. Alternatively, the terminal may be allowed to measure the DL reception quality of the serving / neighboring cell based on these LP-SS signals.

[0496] If the terminal can also generate and transmit LP-SS / LP-WUS signals (uplink), the base station can continue to receive LP-SS / LP-WUS signals from the terminal during the ESR period. Depending on the LP-SS / LP-WUS signals received, the base station may decide whether to remain in ESR or switch to MR. If the received power of the LP-SS / LP-WUS signal is low, the base station may transmit DL signals / channels (e.g., SSB) with reduced TX power applied. This is intended to minimize the imbalance between DL coverage and UL coverage, and it may be desirable to apply relatively low transmission power when serving only cell center terminals or low UL power terminals.

[0497] [Proposal #3] Application Examples for Main Radio (MR) and ESR (Energy Saving Radio) Sections

[0498] (1) Example 1: On-demand SSB procedure

[0499] FIG. 28 illustrates an on-demand SSB procedure according to one embodiment.

[0500] Referring to FIG. 28, during the ESR interval, the base station can transmit an R2D signal and / or LP-SS ( / LP-WUS / SSB) at a designated frequency resource (instead of SSB transmission) (2805).

[0501] The terminal can perform monitoring / detection on a frequency resource (named for convenience as raster for ESR) where R2D signals and / or LP-SS ( / LP-WUS / SSB) are transmitted (2810). At this time, the terminal may not know whether the base station is operating as MR or as ESR, so it may be searching for both raster for ESR and SSB sync rasters, or searching for only one of the two types.

[0502] When a terminal discovers an R2D or LP-SS ( / LP-WUS / SSB) in the corresponding raster for ESR, it may transmit a D2R or LP-WUS through an uplink resource linked to the corresponding raster for ESR (2815). The linkage relationship between the corresponding raster for ESR and the uplink resource may be predefined or configured. Additionally, the terminal may transmit a D2R or LP-WUS through an uplink resource when the reception quality for the R2D or LP-SS ( / LP-WUS / SSB) satisfies a specific condition. The specific condition here may mean that the reception quality is above a predefined or pre-configured threshold.

[0503] When the base station receives the D2R or LP-WUS transmitted by the terminal, it turns on MR (2820) and can transmit SSB (2825).

[0504] The terminal can receive an SSB through a sync raster linked to a raster for ESR or D2R or LP-WUS transmission resource (2825). At this time, the link relationship between the raster for ESR and the sync raster (for SSB) and / or the link relationship between the D2R or LP-WUS transmission resource and the sync raster (for SSB) may be defined or configured in advance.

[0505] After receiving an SSB from a base station (in the MR state), the terminal can transmit an UL WUS (for SIB1 request). The base station that receives the UL WUS transmits a corresponding SIB1 signal, and the terminal can expect to receive a corresponding SIB1 signal after transmitting the UL WUS.

[0506] (2) Example 2: On-demand SIB1 procedure

[0507] FIG. 29 illustrates an on-demand SIB1 procedure according to one embodiment.

[0508] Referring to FIG. 29, the network can signal that the cell is in ESR operation (or in MR / ESR switching operation) and that SIB1 is not currently being transmitted through information such as an SSB on the cell or an SSB / SIB on another cell (2905). The SSB on the cell may be transmitted only during the MR period or, exceptionally, during the ESR period. Additionally, the UL WUS resource for requesting the transmission of SIB1 on the cell may be determined by being predefined, signaled by an SSB on the cell, signaled by an SSB / SIB on another cell, or a combination thereof.

[0509] A terminal that requires receiving SIB1 to camp-on to the cell may request SIB1 transmission through an UL WUS resource (2910). The UL WUS resource may be PRACH when transmitted during the base station's MR (or ESR) period, and may be D2R or LP-WUS ( / LP-SS) when transmitted during the ESR period.

[0510] When the base station receives UL WUS, it turns on MR (2915) and can transmit SIB1 (2920).

[0511] - If the base station receives UL WUS during the ESR period, it may switch to MR and initiate SIB1 transmission. Alternatively, if the base station successfully receives UL WUS during the ESR period, it may switch to MR after explicitly signaling the reception status via a DL signal / channel (or after switching to MR and then explicitly signaling the reception status via a DL signal / channel) and begin SIB1 transmission. At this time, there may be an ESR to MR switching delay of the base station, and SIB1 transmission may begin from the SIB1 PDCCH transmission occasion that occurs after that delay.

[0512] - On the other hand, if UL WUS is received in the MR section, the base station can start SIB1 transmission without a separate switching delay.

[0513] The terminal can receive SIB1 (2920).

[0514] - If the terminal transmits UL WUS during the period of operation in LP-R, it may start receiving SIB1 after switching to MR. Alternatively, if the terminal transmits UL WUS during the period of operation in LP-R and recognizes that the base station has properly received the UL WUS signal through the reception of the base station's DL signal / channel, it may then switch to MR and start receiving SIB1 (or if the terminal transmits UL WUS during the period of operation in LP-R and switches to MR and recognizes that the base station has properly received the UL WUS signal through the reception of the base station's DL signal / channel). At this time, there may be an LP-R to MR switching delay of the terminal, and it may start receiving SIB1 from the SIB1 PDCCH monitoring occasion that arrives after that delay (or after the minimum / maximum value between the base station's ESR to MR switching delay and the terminal's LP-R to MR switching delay).

[0515] - On the other hand, if the terminal transmits UL WUS during the MR period, the terminal may start receiving SIB1 without a separate switching delay, or may start receiving SIB1 from the SIB1 PDCCH monitoring occasion that arrives after the base station's ESR to MR switching delay. Alternatively, if the terminal transmits UL WUS during the MR period and the base station recognizes that it has properly received the UL WUS signal through the base station's DL signal / channel reception, it may start receiving SIB1 from the SIB1 PDCCH monitoring occasion that arrives after the base station's ESR to MR switching delay.

[0516] - If the terminal transmits UL WUS and attempts to detect SIB1 for a certain period but fails to detect SIB1, it may switch back to LP-R to attempt to retransmit UL WUS, or attempt to retransmit UL WUS while maintaining MR.

[0517] FIG. 30 is a diagram illustrating the operation of a terminal and a base station according to one embodiment.

[0518] Referring to FIG. 30, the base station can transmit configuration information related to the MR / ESR period (3005). The configuration information may be provided through upper layer signaling, such as RRC / system information signaling, for example. The configuration information related to the MR / ESR period may include information regarding switching in the MR / ESR period (e.g., periodicity / offset of the cycle, MR / ESR duration / offset). For example, information regarding at least one of the length of the MR duration and ESR duration, duration offset, period, offset of the start of the period, or switching pattern may be included in the configuration information related to the MR / ESR period.

[0519] The base station can perform MR / ESR operations based on configuration information related to the MR / ESR period (3010). Based on the configuration information, the terminal can also operate as MR during the base station's MR period and as LP-R during the base station's ESR period. For example, the terminal can turn on MR and turn off LP-R during the base station's MR duration. The terminal can turn off MR and turn on LP-R during the base station's ESR duration.

[0520] When UL data to be transmitted is generated / arrived, the terminal can transmit MR WUS to the base station (based on a pre-configured / defined resource) (3015).

[0521] A base station that receives the MR WUS can change to a mode that operates only with MR, rather than switching between MR and ESR (3020).

[0522] The base station can notify the terminal of this mode change by transmitting a DL signal / channel (3025). The terminal that receives the DL signal / channel can recognize the base station's mode change.

[0523] By enabling the base station that performs AmIoT / LP-WUS communication with the terminal to operate based on a separate radio (e.g., ESR) (instead of the main radio), the energy consumption of the base station can be significantly reduced.

[0524] Meanwhile, the MR section of the base station mentioned in this specification may be expressed as a section operating in a first section or a first mode / state, and the ESR section may be expressed as a section operating in a second section or a second mode / state. The base station may support the transmission and reception of (all) OFDM signals in the MR section, and may support at least one of the transmission or reception of LP signals in the ESR section. The LP signals may include, for example, at least one of an OOK modulation signal, an OFDM overlaid OOK signal, and D2R and R2D signals for Am IoT. In the ESR section, at least one of all OFDM signals supported in the MR section may be supported.

[0525] FIG. 31 illustrates the flow of a method performed at a base station according to one embodiment. FIG. 31 is an example of implementation for at least some of the proposals described above, and the proposals described above may be referenced to aid in understanding FIG. 31, even without separate mention.

[0526] Referring to FIG. 31, a base station may transmit configuration information including at least one of a first period in which at least one of the reception or transmission of OFDM (orthogonal frequency divisional multiplexing) signals is performed, or at least one of a second period in which at least one of the reception or transmission of at least one LP (low-power) signal is performed (3105). For example, the configuration information may be transmitted through at least one upper layer signaling.

[0527] The base station can receive a WUS (wake up signal) from the terminal in the second section (3110).

[0528] The base station can terminate the second section and start the first section based on the reception of the WUS (3115).

[0529] For example, until the reception of the above WUS, the above first section and the above second section may be repeated alternately based on the above setting information.

[0530] For example, the second section may continue until the reception of the above WUS.

[0531] The above at least one LP signal may include a non-OFDM signal.

[0532] The above non-OFDM signal may include at least one of an OOK (on-off keying) modulation signal, a D2R (device-to-reader) signal for Am-IoT (ambient internet of things), or an R2D (reader-to-device) signal.

[0533] At least one of the above OFDM signals can be transmitted or received in the second section as well.

[0534] The above at least one OFDM signal may include at least one of an SSB (synchronization signal block) or a RACH (random access channel).

[0535] The above setting information may include at least one of (i) length or offset information for at least one of the first section or the second section, (ii) information for a cycle composed of the first section and the second section, (iii) information for the start offset of the cycle, or (iv) setting information for the WUS.

[0536] The base station may transmit a downlink signal to the terminal indicating the start of the first section in response to the WUS. The downlink signal may be an OFDM signal, but is not limited thereto, and may be, for example, an LP WUS.

[0537] For example, if there is a specific end time pre-set through configuration information for the second section, the base station may terminate (stop) the second section early before the specific end time based on WUS reception, or maintain the second section only until the specific end time (of the cycle) and then continue the first section thereafter.

[0538] FIG. 32 illustrates the flow of a method performed in a device according to one embodiment. FIG. 32 is an example of implementation for at least some of the proposals described above, and the proposals described above may be referenced to aid in understanding FIG. 32 unless otherwise noted. In FIG. 32, the device may be a terminal including a transceiver or a processing device configured to control a terminal.

[0539] Referring to FIG. 32, the device may receive configuration information from the base station, which includes at least one of a first section in which the base station performs at least one of receiving or transmitting OFDM (orthogonal frequency divisional multiplexing) signals, or at least one of a second section in which the base station performs at least one of receiving or transmitting at least one LP (low-power) signal (3205). For example, the configuration information may be received through at least one upper layer signaling.

[0540] The device may transmit a WUS (wake-up signal) to the base station in the second section (3210). For example, the WUS may be for requesting the start of the first section and / or the end of the second section.

[0541] The device can receive / detect from the base station a downlink signal indicating the start of the first section (and / or the end of the second section) in response to the WUS (3215). For example, the downlink signal may be received to confirm that the first section has started in response to the request of the device. For example, the downlink signal may be a downlink OFDM signal, but is not limited thereto, and may be, for example, an LP WUS. For example, the downlink signal may be received / detect in the first section initiated in response to the request of the device.

[0542] The above WUS may be transmitted based on at least one of the following: uplink data to be transmitted in the first section is generated, the downlink reception quality in the second section is below a threshold, or the device is attempting an initial connection.

[0543] For example, until the transmission of the above WUS, the first section and the second section may be repeated alternately based on the above setting information.

[0544] For example, the second section may continue until the transmission of the above WUS.

[0545] The above at least one LP signal may include a non-OFDM signal.

[0546] The above non-OFDM signal may include at least one of an OOK (on-off keying) modulation signal, a D2R (device-to-reader) signal for Am-IoT (ambient internet of things), or an R2D (reader-to-device) signal.

[0547] At least one of the above OFDM signals can be transmitted or received in the second section as well.

[0548] The above at least one OFDM signal may include at least one of an SSB (synchronization signal block) or a RACH (random access channel).

[0549] The above setting information may include at least one of (i) length or offset information for at least one of the first section or the second section, (ii) information for a cycle composed of the first section and the second section, (iii) information for the start offset of the cycle, or (iv) setting information for the WUS.

[0550] For example, if there is a specific end time pre-set through configuration information for the second section, the second section may be terminated (stopped) early before the specific end time based on the WUS, or the second section may be maintained only until the specific end time (of the cycle), after which the first section may continue.

[0551] The embodiments described above are combinations of the components and features of the present disclosure in a specific form. Each component or feature should be considered optional unless otherwise explicitly stated. Each component or feature may be implemented in a form not combined with other components or features. Additionally, it is possible to construct 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 obvious that embodiments may be constructed by combining claims that are not explicitly related in the claims, or that they may be included as new claims by amendment after filing.

[0552] It is obvious to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the features of the present disclosure. Accordingly, the foregoing detailed description should not be interpreted restrictively in all respects and should be considered illustrative. The scope of the present disclosure shall be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present disclosure are included within the scope of the present disclosure.

[0553] The present disclosure may be used in a terminal, base station, or other equipment of a wireless mobile communication system.

Claims

1. In a method performed by a base station, Transmitting configuration information comprising at least one of a first period during which at least one of the reception or transmission of OFDM (orthogonal frequency divisional multiplexing) signals is performed, or information regarding a second period during which at least one of the reception or transmission of at least one LP (low-power) signal is performed; Receiving a WUS (wake-up signal) from the terminal in the second section; and A method comprising terminating the second section and starting the first section based on reception of the WUS.

2. In Paragraph 1, A method in which at least one LP signal comprises a non-OFDM signal.

3. In Paragraph 2, A method wherein the above-mentioned non-OFDM signal comprises at least one of an OOK (on-off keying) modulation signal, a D2R (device-to-reader) signal for Am-IoT (ambient internet of things), or an R2D (reader-to-device) signal.

4. In Paragraph 1, A method in which at least one of the above OFDM signals is transmitted or received in the second interval as well.

5. In Paragraph 4, A method in which the at least one OFDM signal comprises at least one of an SSB (synchronization signal block) or a RACH (random access channel).

6. In Paragraph 1, A method in which the first section and the second section alternately repeat based on the setting information until the above WUS is received.

7. In Paragraph 1, A method comprising at least one of the above setting information, wherein the above setting information includes (i) length or offset information for at least one of the first section or the second section, (ii) information for a cycle composed of the first section and the second section, (iii) information for the start offset of the cycle, or (iv) setting information for the WUS.

8. In Paragraph 1, A method further comprising transmitting a downlink signal to the terminal indicating the start of the first section in response to the above WUS.

9. In Paragraph 1, A method in which the second section continues until the reception of the above WUS.

10. A computer-readable non-transitory recording medium storing a program for performing the method described in claim 1.

11. Regarding base stations, At least one processor; and It includes at least one memory configured to store instructions that cause the at least one processor to perform operations by being executed by the at least one processor, and The operations of the above processor are, Transmitting configuration information comprising at least one of a first period during which at least one of the reception or transmission of OFDM (orthogonal frequency divisional multiplexing) signals is performed, or information regarding a second period during which at least one of the reception or transmission of at least one LP (low-power) signal is performed; Receiving a WUS (wake-up signal) from the terminal in the second section; and A base station comprising terminating the second section and starting the first section based on reception of the above WUS.

12. In a method performed by a device, Receive configuration information from the base station comprising at least one of a first section in which the base station performs at least one of receiving or transmitting OFDM (orthogonal frequency divisional multiplexing) signals, or at least one of a second section in which the base station performs at least one of receiving or transmitting at least one LP (low-power) signal; Transmitting a WUS (wake-up signal) requesting the start of the first section to the base station in the second section; and A method comprising receiving a downlink signal from the base station indicating the start of the first section in response to the above WUS.

13. In Paragraph 12, A method in which the above WUS is transmitted based on at least one of the following: uplink data to be transmitted in the first section is generated, downlink reception quality in the second section is below a threshold, or the device is attempting an initial connection.

14. Regarding the device, At least one processor; and It includes at least one memory configured to store instructions that cause the at least one processor to perform operations by being executed by the at least one processor, and The operations of the above processor are, Receive configuration information from the base station comprising at least one of a first section in which the base station performs at least one of receiving or transmitting OFDM (orthogonal frequency divisional multiplexing) signals, or at least one of a second section in which the base station performs at least one of receiving or transmitting at least one LP (low-power) signal; Transmitting a WUS (wake-up signal) requesting the start of the first section to the base station in the second section; and A device comprising receiving a downlink signal from the base station indicating the start of the first section in response to the above WUS.

15. In Paragraph 14, The above device is a device that is a terminal further comprising a transceiver or a processing device configured to control the terminal.

Images