Method performed by terminal or network in wireless communication system, and device therefor

Abstract

A terminal according to one embodiment of the present disclosure can: receive configuration information related to a wakeup signal (WUS) by means of higher-layer signaling; detect the WUS on the basis of the configuration information; determine a quasi co-location (QCL) type related to at least one from among Doppler shift, Doppler spread, average delay, delay spread and spatial Rx parameter on the basis of the capability of the terminal with respect to detection of the WUS; and detect the WUS on the basis of the QCL type.

Description

Method performed by a terminal or network in a wireless communication system and device therefor

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and device for transmitting or receiving uplink / downlink signals between terminals or networks in a wireless communication system.

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

[0003] 5G NR and next-generation wireless communication systems are being designed and researched to support not only mobile communications but also various vertical services. In addition to low latency, reliability, and availability, UE energy efficiency is also a critical design element in wireless communications. Currently, wireless communication terminals require charging approximately every day or several days, depending on usage patterns. Typically, 5G terminals consume tens of milliwatts (mW) in RRC Idle / Inactive states and hundreds of mW in RRC Connected states. Wireless communication designs that conserve battery power are crucial for improving energy efficiency and user convenience.

[0004] Energy efficiency is even more critical for UEs that rely on low-capacity rechargeable batteries or single coin cells, which lack a continuous energy source. Among vertical services, sensors and actuators are widely used for monitoring, measurement, and charging. Some batteries may not be rechargeable and may need to last at least several years. However, wearable devices such as smartwatches, rings, eHealth devices, and medical monitoring devices typically struggle to maintain their batteries for more than one to two weeks.

[0005] Power consumption can vary depending on the length of the wake-up cycle, such as the paging cycle. While setting a large eDRX cycle to achieve the long battery life described above can be considered, this increases latency and may not be suitable for services requiring low latency. For example, in a fire detection / suppression scenario, shutters must close and sprinklers must be activated within 1-2 seconds after a sensor detects a fire, but a long eDRX cycle cannot meet the latency requirements. Therefore, eDRX is not suitable for low-latency use cases.

[0006] The technical task to be achieved in the present disclosure is to provide a method and a device for efficiently performing a wireless signal transmission and reception process. For example, a method may be provided for detecting a wireless signal unseen (WUS) based on a QCL (Quasi-Co-Location) relationship with another signal. In addition, a method may be provided for determining a different QCL type defining the QCL relationship depending on the WUS detection capability of the corresponding terminal. In addition, a method may be provided for the terminal to perform PDCCH monitoring using the QCL relationship between the CORESET and the WUS after WUS detection.

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

[0008] According to one aspect of the present disclosure, a method performed by a terminal may include receiving configuration information related to a wakeup signal (WUS) through upper layer signaling; and detecting the WUS based on the configuration information. Based on a capability of the terminal for detecting the WUS, a quasi co-location (QCL) type related to at least one of a Doppler shift, a Doppler spread, an average delay, a delay spread, or a spatial Rx parameter is determined, and the terminal may detect the WUS based on the QCL type.

[0009] Based on the terminal having the ability to detect on-off keying (OOK) symbols for the WUS, the QCL type may be determined as a first QCL type. Based on the terminal having the ability to detect an orthogonal frequency division multiplexing (OFDM) sequence overlaid on the OOK symbols, the QCL type may be determined as a second QCL type.

[0010] The above first QCL type may be a subset of the above second QCL type.

[0011] The first QCL type may be related to the Doppler spread and the average delay, and the second QCL type may be related to the Doppler shift, the Doppler spread, the average delay, and the delay spread.

[0012] The first QCL type may be associated with one downlink reference signal, and the second QCL type may be associated with one or more downlink reference signals.

[0013] For example, the terminal may transmit a terminal capability report including information about the terminal's capability for WUS detection. The configuration information may include information about the QCL type determined based on the terminal capability report.

[0014] For example, the QCL type may be determined by the terminal based on the terminal's capability for WUS detection.

[0015] The terminal may detect the WUS based on the specific downlink signal and the WUS having a QCL relationship for the QCL type. The specific downlink signal may include at least one of a synchronization signal block (SSB) or a low power-synchronization signal (LP-SS).

[0016] The terminal can monitor a physical downlink control channel (PDCCH) on a control resource set (CORESET) based on detection of the WUS. The terminal can monitor the PDCCH based on the QCL relationship between the WUS and the CORESET.

[0017] The above setting information may include at least one of ID (identifier) ​​information of the CORESET or information on the QCL type between the WUS and the CORESET.

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

[0019] According to another aspect of the present disclosure, a device 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 receiving configuration information related to a wakeup signal (WUS) through upper layer signaling; and detecting the WUS based on the configuration information. Based on a capability of the device for detecting the WUS, a quasi co-location (QCL) type related to at least one of a Doppler shift, a Doppler spread, an average delay, a delay spread, or a spatial Rx parameter is determined, and the device may detect the WUS based on the QCL type.

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

[0021] According to another aspect of the present disclosure, a method performed by a base station may include receiving a terminal capability report including information on a wakeup signal (WUS) detection capability of a terminal; transmitting configuration information related to the WUS to the terminal through upper layer signaling; and transmitting the WUS to the terminal. Based on the information on the WUS detection capability, a quasi co-location (QCL) type related to at least one of a Doppler shift, a Doppler spread, an average delay, a delay spread, or a spatial Rx parameter may be determined for the WUS. The configuration information may include information on the determined QCL type.

[0022] According to another aspect of the present disclosure, a base station 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 receiving a terminal capability report including information on a wakeup signal (WUS) detection capability of a terminal; transmitting configuration information related to the WUS to the terminal via upper layer signaling; and transmitting the WUS to the terminal. Based on the information on the WUS detection capability, a quasi co-location (QCL) type related to at least one of a Doppler shift, a Doppler spread, an average delay, a delay spread, or a spatial Rx parameter may be determined for the WUS. The configuration information may include information on the determined QCL type.

[0023] According to the present disclosure, signal transmission and reception can be efficiently performed in a wireless communication system. According to one embodiment, such a terminal can detect a WUS more stably and reliably by utilizing the QCL (Quasi-Co-Location) relationship between a WUS and another signal. Furthermore, by selecting an appropriate QCL type according to the terminal's capabilities, a flexible and efficient QCL configuration is possible even in various reception environments. Furthermore, after WUS detection, the terminal can efficiently monitor the PDCCH based on the QCL relationship between the WUS and the CORESET, thereby improving PDCCH detection performance and minimizing the burden on channel estimation, thereby enabling power-efficient wireless communication.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0037] Figure 13 illustrates an uplink / downlink signal transmission / reception procedure between a base station and a terminal according to one embodiment.

[0038] Figure 14 is a diagram for explaining the QCL types that can be set between the QCL source signal and the QCL target signal.

[0039] FIG. 15 is a diagram for explaining the operation of a terminal and a network according to one embodiment.

[0040] FIG. 16 illustrates a flow of a method performed by a terminal according to one embodiment.

[0041] FIG. 17 illustrates a flow of a method performed by a base station according to one embodiment.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0056] <Symbols, Abbreviations, Terms>

[0057] - ACS: Adjacent Channel Selectivity

[0058] - ADC: Analog to Digital Converter

[0059] - ASCS: Adjacent Subcarrier selectivity

[0060] - ASK: Amplitude Shift Keying

[0061] - BB: Base Band

[0062] - BLER: Block Error Rate

[0063] - BPF: Band Pass Filter

[0064] - BWP: Bandwidth part

[0065] - CAP: Channel Access Procedure

[0066] - CFO: Center frequency offset

[0067] - CORESET: Control resource set

[0068] - CRC: Cyclic redundancy check

[0069] - CP-OFDMA: Cyclic Prefix-Orthogonal Frequency-Division Multiple Access

[0070] - CSI: Channel state information

[0071] - DCI: Downlink Control Information

[0072] - DCP: DCI with CRC scrambled by PS-RNTI

[0073] - DRX: Discontinuous Reception

[0074] - DFT-S-OFDMA: Discrete Fourier Transform-Spread-Orthogonal Frequency-Division Multiple Access

[0075] - eDRX: Extended DRX

[0076] - EPRE: Energy Per Resource Element

[0077] - FAR: False Alarm Rate

[0078] - FCS: Frame Check Sequence

[0079] - FSK: Frequency Shift Keying

[0080] - FLL: Frequency Locked Loop

[0081] - FFT: Fast Fourier Transform

[0082] - FR1: Frequency range 1

[0083] - FR2: Frequency range 2

[0084] - ICS: In-channel Selectivity

[0085] - IF: Intermediate Frequency

[0086] - LP-WUS (or simply WUS): Low Power-Wake Up Signal

[0087] - LP-WUR (or simply LR): Low Power-Wake Up Receiver, an Rx module responsible for receiving and processing low-power wake-up signals / channels.

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

[0089] - LO: Local Oscillator

[0090] - LNA: Low Noise Amplifier

[0091] - LPF: Low Pass Filter

[0092] - LR: LP-WUR

[0093] - MDR: Miss Detection Rate

[0094] - MC-ASK: Multiple Carrier-Amplitude Shift Keying

[0095] - MC-FSK: Multiple Carrier-Frequency Shift Keying

[0096] - MR: Main Radio, Tx / Rx module responsible for transmitting and receiving NR signals / channels excluding low-power wake-up related signals / channels

[0097] - NF: Noise Figure

[0098] - OOK: On-Off keying

[0099] - OFDM: Orthogonal Frequency Division Multiplexing

[0100] - PDCCH: Physical Downlink Control Channel

[0101] - PUCCH: Physical Uplink Control Channel

[0102] - PUSCH: Physical Uplink Shared Channel

[0103] - PDSCH: Physical Downlink Shared Channel

[0104] - PRACH: Physical Random-Access Channel

[0105] - PEI: Paging Early Indication

[0106] - PO: Paging Occasion

[0107] - PTW: Paging Time Window

[0108] - PLL: Phase Locked Loop

[0109] - PAPR: Peak to Average Power Ratio

[0110] - RRC: Radio Resource Control

[0111] - RRM: Radio Resource Management

[0112] - RLM: Radio Link Monitoring

[0113] - RS: Reference Signal

[0114] - RSRP: Reference Signal Received Power

[0115] - RSRQ: Reference Signal Received Quality

[0116] - RTC: Real Time Clock

[0117] - RF: Radio Frequency

[0118] - SCS: Sub-carrier spacing

[0119] - SSB: Synchronization Signal Block

[0120] - SSSG: Search Space Set Group

[0121] - SINR: Signal to Interference plus Noise Ratio

[0122] - SNR: Signal to Noise Ratio

[0123] - SC: Subcarrier

[0124] - TBS: Transport Block Size

[0125] - TDRA: Time Domain Resource Allocation

[0126] - Ucell: Unlicensed cell

[0127] - UE: User Equipment

[0128] - XR: Extended reality

[0129] - TAG: Timing advance group

[0130] - AmIoT: Ambient Internet of Things

[0131] - CW: Carrier Wave

[0132] - BSC: Backscattering

[0133] - BSS: Backscattered signal

[0134] - SIC: Self-Interference Cancellation

[0135] - RFID: Radio Frequency Identifier

[0136] - IN: Intermediate Node

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

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

[0139] - CORESET: COntrol REsourse SET (refers to the time-frequency resource area where PDCCH can be transmitted, and the number of CORESETs per BWP may be limited.)

[0140] - REG: Resource element group

[0141] - SFI: Slot Format Indicator (an indicator indicating the symbol level DL / UL direction within a specific slot(s), transmitted through the group common PDCCH.)

[0142] - COT: Channel occupancy time

[0143] - SPS: Semi-persistent scheduling

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

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

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

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

[0148] To compensate for incomplete network coverage areas, a network topology that allows for more flexible and resilient split radio access networks (RANs) may be considered. For this purpose, various nodes, such as IAB nodes, relays, and RF repeaters, as illustrated in the example in Figure 1, may be applied, or NTNs may be integrated. For example, an IAB node may correspond to a node that provides wireless backhaul. For example, a relay may refer to any intermediate point, or in the case of a sidelink relay where a terminal functions as a relay, it may collectively refer to a terminal-to-network (U2N) relay and a terminal-to-terminal (U2U) relay. For example, an RF repeater may correspond to a node that simply performs the function of signal amplification and forwarding, while a network-controlled repeater may not only amplify and forward signals but also adjust transmission and reception settings based on information provided by the network. For example, an NTN node may correspond to a satellite or aircraft that provides NTN coverage that is difficult for terrestrial networks to provide. In addition to these examples, various intermediate points can be introduced to improve the network topology.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0168] For example, the device may be a mobile device such as a mobile robot, a vehicle, a train, an aerial vehicle (AV), a ship, etc. In this case, the device may further include at least one of a driving unit including at least one of an engine, a motor, a power train, wheels, brakes, and a steering unit of the device, a power supply unit including a wired / wireless charging circuit, a battery, etc. that supplies power, a sensor unit that senses status information, environmental information, and user information of the device or its surroundings, an autonomous driving unit that performs functions such as path maintenance, speed control, and destination setting, and a position measurement unit that obtains location information of the mobile device through a global positioning system (GPS) and various sensors.

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

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

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

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

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

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

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

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

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

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

[0179] The terminal (110) and the base station (120) can perform signaling of control information (407). Here, the control information can be defined in various layers, such as a layer that controls a connection (e.g., a radio resource control (RRC) layer), a layer that handles mapping between logical channels and transport channels (e.g., a media access control (MAC) layer), and a layer that handles physical channels (e.g., a physical (PHY) layer). For example, the terminal (110) and the base station (120) can perform at least one of signaling for establishing a connection, signaling for determining settings related to communication, and signaling for indicating allocated resources.

[0180] The terminal (110) and the base station (120) can transmit and / or receive data (409). In other words, the terminal (110) and the base station (120) can process, transmit, and / or receive data based on signaling of control information. For example, when transmitting data, the terminal (110) or the base station (120) can perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and resource mapping on the information bits. Conversely, when receiving data, the terminal (110) or the base station (120) can perform at least one of signal extraction from resources, waveform demodulation for each antenna, signal arrangement considering layer mapping, constellation demapping, descrambling, and channel decoding.

[0181] <6G System Core Technologies>

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

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

[0184] artificial intelligence

[0185] Incorporating AI into communications can streamline and improve real-time data transmission. AI can use numerous analytics to determine how complex target tasks should be performed. This means AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handovers, network selection, and resource scheduling can be performed instantly using AI. AI can also play a crucial role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. Furthermore, AI can facilitate rapid communication in brain-computer interfaces (BCIs). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0228] THz communication (terahertz communication)

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

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

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

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

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

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

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

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

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

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

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

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

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

[0242] Integrated Sensing and Communication (ISAC)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0267] FIG. 13 illustrates an example of a procedure between a base station and a terminal performing FR1, FR2, or FR2-2 transmission and reception of one or more physical channels / signals to which the method proposed in this specification can be applied.

[0268] Figure 13 (a) illustrates an example of UL data / channel transmission and reception. The base station can transmit configuration information related to UL data / channel to the terminal via upper layer signaling (1301). The terminal can receive DCI for UL data scheduling and / or information for UL channel transmission from the base station (1302). Based on this, the terminal can transmit UL data / channel to the base station (1303).

[0269] Figure 13 (b) illustrates an example of transmission and reception of DL data / channel. The base station can transmit configuration information related to DL data / channel to the terminal via upper layer signaling (1304). The terminal can receive DCI for DL ​​data scheduling and / or information for DL ​​channel transmission from the base station (1305). Based on this, the terminal can receive DL data / channel from the base station (1306). If HARQ-ACK is configured for reception of the corresponding DL data / channel, the terminal can transmit HARQ-ACK to the base station (1307).

[0270] LP WUR (low power wake up receiver)

[0271] Currently, UEs must wake up periodically for each DRX cycle, resulting in power consumption even during periods without signal / data traffic. If UEs could wake up only when there are specific triggers, such as paging, power consumption could be significantly reduced. To achieve this, the introduction of a wake-up signal (WUS) that wakes up the MR (Main Radio) and a separate receiver, the LP WUR, that can monitor the WUS with very little power is being discussed. For example, the MR operates as a receiver in existing NR during data / signal transmission and reception, but to save power, the MR can be turned off or transitioned to a deep sleep state while the LP WUR is turned on.

[0272] LP-WUS / WUR applicable targets may include, for example, (i) IoT devices such as industrial wireless sensors, controllers, and actuators, (ii) wearable devices such as smartwatches, smart rings, eHealth devices, and medical monitoring devices, and / or (iii) eMBB-enabled devices such as XR / smart glasses and smartphones.

[0273] For 3GPP standardization of LP-WUS / WUR, research on the following may be required:

[0274] - Power saving effects, coverage, system overhead, network energy impact, etc. of LP-WUS / WUR.

[0275] - LP-WUR receiver structure analysis (power consumption, noise figure, etc.)

[0276] - L1 design and procedure changes and link performance evaluation to support LP-WUS

[0277] - Changes to upper layer protocols to support this

[0278] LP-WUS can have a structure that is equally applicable to both RRC IDLE / INACTIVE and RRC CONNECTED modes. The modulation scheme of LP-WUS can be based on OOK-1 / OOK-4. One or more OFDM sequences can be overlaid on each OOK symbol.

[0279] 1) LP WUR operation in RRC Idle / Inactive mode

[0280] In RRC Idle / Inactive mode, if MR RRM measurements are sufficiently relaxed, UE power savings of up to 90% or more can be achieved compared to existing I-DRX (including with and without PEI). Compared to existing eDRX, paging delay can be significantly reduced and moderate power savings can be achieved (provided that LP-WUS monitoring and paging monitoring after MR startup are not limited to existing eDRX PTW).

[0281] Regardless of the LP-WUR type, the same information can be guaranteed to be transmitted in RRC IDLE / INACTIVE mode, and OFDM sequences can carry the information. Duty-cycle-based monitoring, such as periodic On / Off monitoring, can be supported.

[0282] For RRC IDLE / INACTIVE mode, LP-WUS based paging trigger procedures (e.g., configuration parameters, subgrouping, monitoring entry / exit conditions, etc.) can be configured / defined.

[0283] In RRC IDLE / INACTIVE mode, LP-SS can be transmitted repeatedly with a period of Y ms (e.g., 320 ms for initial transmission) and can have OOK-1 / OOK-4 waveform (OOK with or without OFDM sequence). If LP-WUR can receive existing PSS / SSS, it may be allowed to perform synchronization / RRM with PSS / SSS instead of LP-SS. In order to relax and offload RRM measurement of MR, UE MR RRM request can be additionally relaxed in serving / neighbor cell measurement, and conditions for offloading serving cell RRM measurement from MR to LP-WUR need to be defined.

[0284] 2) LP WUR operation in RRC Connected mode

[0285] In RRC Connected mode, power savings of up to 10% can be achieved compared to existing power-saving techniques for various XR traffic / system overheads, with minimal capacity impact. For FTP / IM traffic, the MR can enter deep sleep, achieving up to 60% power savings and up to 10% UPT improvement. Offloading serving cell RRM measurements from the UE MR to the LP-WUR can also be considered.

[0286] Regarding LP-WUS-based MR-PDCCH monitoring in RRC Connected mode, monitoring activation / deactivation procedures need to be defined / configured. In RRC CONNECTED mode, MR's ultra-deep sleep may not be supported, and RRM / RLM / BFD / CSI measurements can still be performed by the MR. LP-WUS / LP-SS coverage can be at a level similar to that of PUSCH Message 3.

[0287] TCI (transmission configuration indication) State related to LP-WUS

[0288] As described above, MR (Main radio) refers to a receiver for receiving signals included in a terminal of a general NR standard, and can be utilized to receive OFDM signals, etc. on the NR standard. For example, a receiver equipped in a terminal of an existing NR standard can be understood as MR. LP-WUR refers to a receiver that can be additionally configured in a terminal to receive a low-power signal, and can receive newly designed low-power signals such as LP-WUS or LP-SS, and can generally have the characteristics of being configured with low cost and low power consumption. As described above, LP WUS can be simply referred to as WUS.

[0289] Low-power signals such as LP-WUS or LP-SS can be structured differently from signals transmitted with the current general OFDM symbol structure in the time / frequency axis resource configuration of the NR standard. For example, LP-WUS is modulated with OOK (On-Off Keying) to match the slot or symbol structure of the time axis, but can be transmitted without matching / aligning with the unit resource (e.g., RE, subcarrier, or RB) structure of the frequency axis. For example, LP-WUS is configured as ON (e.g., 1) when a signal is present within a specific time interval, and OFF (e.g., 0) when a signal is absent, so that a terminal can receive WUS simply by detecting energy within a specific time interval. It can also be considered that the OOK symbol of such LP-WUS has a sequence for spectrum flattening, or an OFDM sequence for increasing transmission coverage or transmitting additional information be overlaid.

[0290] Several architecture candidates for LP-WUR are being discussed, and the power consumption of LP-WUR in the 'on' and 'off' states may differ accordingly. Accordingly, the 'on' state power consumption of LP-WUR may be significant, or for other reasons, the terminal may be required to activate or deactivate LP-WUR. To this end, conditions for entering the LP-WUR activated state (entry conditions) and exiting the activated state (exit conditions) can be defined.

[0291] The indicated LP-WUS may include a payload transmitted in the form of an OOK symbol. Generally, the payload can be said to contain the information actually indicated to the terminal. Additionally, it may consist of a preamble for other purposes (e.g., synchronization) and an OFDM sequence overlaid on the OOK symbol. For example, the LP-WUS may be said to include at least one of the information transmitted via the payload and the information transmitted via the overlaid OFDM sequence.

[0292] For example, LP-WUR can be defined by dividing it into two types.

[0293] - LP-WUR Type #1: Wake-up receiver capable of energy detection only

[0294] - LP-WUR Type #2: Wake-up receiver capable of sequence detection (as well as energy detection)

[0295] For LP-WUR type #1, it is a wake-up receiver that is configured for low cost and can only determine the presence or absence of a signal (energy detection or envelope detection). Therefore, it is a receiver that can only receive information transmitted through the OOK symbol, i.e., the payload.

[0296] LP-WUR Type #2 is a wake-up receiver capable of detecting OFDM sequences at a higher cost than Type #1 and also capable of energy detection. Therefore, it can receive not only payloads but also information transmitted via overlaid OFDM sequences. Furthermore, depending on the implementation, it may also be capable of receiving PSS / SSS of existing NR signals.

[0297] NR signals can be configured with a QCL relationship based on other signals and TCI states. For example, multiple TCI states can be configured to a terminal via higher layer signaling. For example, assume that TCI state #1 configures that the signal has a QCL relationship with DL RS #1, and TCI state #2 configures that the signal has a QCL relationship with DL RS #2. For example, if the signal is a PDSCH, when the terminal receives a PDSCH scheduling DCI, if the TCI field included in the DCI indicates TCI state #1, the terminal assumes that the PDSCH (or DMRS) and DL RS #1 are QCL, and can receive the PDSCH based on the channel properties for DL ​​RS #1 (e.g., see Table 1 below). If the TCI field included in the DCI indicates TCI state #2, the UE can assume that the PDSCH (or DMRS) and DL RS#2 are QCL-ed and receive the PDSCH based on the channel properties for DL ​​RS#2 (e.g., see Table 1 below). The channel properties that can be assumed as QCL (e.g., see Table 1 below) may vary depending on the QCL type, and the QCL type can also be configured through upper layer signaling. Meanwhile, QCL information can be configured or predefined not only for dynamic scheduling of PDSCH but also for reception of various other DL signals.

[0298] Meanwhile, by extending the TCI state / QCL configuration between existing NR signals, LP-WUS can also consider establishing a QCL relationship for the TCI state with existing NR signals. In other words, for LP-WUS monitoring of RRC CONNECTED mode terminals, LP-WUS can consider establishing a QCL relationship based on the existing NR signal / channel / CORESET and TCI state.

[0299] In this specification, a method for setting a QCL relationship for a TCI state of an LP-WUS received by an LP-WUR is proposed. According to an embodiment, since signals that can be received, information that can be acquired, and / or channel estimation and processing for signal reception may differ depending on LP-WUR types #1 and #2, the QCL relationship for the TCI state may be set / defined differently for each LP-WUR type. In addition, according to an embodiment, an operation is proposed in which a terminal that receives an LP-WUS with a QCL relationship for the TCI state performs PDCCH monitoring with an MR based on the received LP-WUS. For example, the WUS may be used as a QCL source for PDCCH monitoring.

[0300] At least one of the methods proposed in this specification may include a method for establishing a QCL relationship for the TCI state of an LP-WUS received by a terminal in RRC CONNECTED mode and a PDCCH monitoring operation of an MR according to the method. However, the scope of application of the proposed methods is not limited to RRC CONNECTED mode and may also be applied to RRC_IDLE / INACTIVE mode.

[0301] A TCI state contains QCL relationships between one or more DL RSs, such as DMRS and CSI-RS. A QCL relationship is typically established between two RSs (reference signals), meaning that channel estimation-related parameters (e.g., Doppler shift, Doppler spread, average delay, delay spread, and / or spatial Rx parameters) obtained from one RS can be applied to another RS ​​(or its antenna port(s)). For each of these parameters, four QCL types are defined in NR systems, as shown in Table 1 below.

[0302] QCL TypeDescriptionQCL-TypeADoppler shift, Doppler spread, average delay, delay spreadQCL-TypeBDoppler shift, Doppler spreadQCL-TypeCAverage delay, Doppler shiftQCL-TypeDSpatial Rx parameter

[0303] For example, when DL RS#1 and DL RS#2 are set to have QCL-TypeA, this means that among the channel estimation-related parameters obtained from DL RS#1, Doppler shift, Doppler spread, average delay, and delay spread can be applied and utilized in the same way when estimating DL RS#2. In this specification, for convenience, DL RS#1 is referred to as QCL source and DL RS#2 as QCL target. For example, the TCI state of PDCCH DMRS is set to have TRS and QCL-TypeA, and in this case, PDCCH DMRS can be referred to as QCL target and TRS can be referred to as QCL source.

[0304] Figure 14 summarizes the QCL source and QCL target relationships between DL RSs defined in the NR standard TS 38.214.

[0305] In Fig. 14, P-TRS means periodic tracking reference signal, AP-TRS means aperiodic tracking reference signal, and CSI-RS BM / CSI means CSI-RS for beam management and CSI-RS for CSI, respectively.

[0306] In this disclosure, we propose a method for setting TCI states and QCL relationships for LP-WUS reception by utilizing the TCI states and QCL relationships in the NR standard. We also propose a method for setting QCL sources for existing NR signals that can be QCL sources for LP-WUS received by a terminal and / or for CORESETs in which PDCCH monitoring is performed after WUS detection.

[0307] Proposal 1: Example of establishing a QCL relationship for the TCI state of LP-WUS.

[0308] As an example, Proposal 1 can be applied to RRC_CONNECTED mode.

[0309] For example, a TCI state can be set that can help a terminal (in RRC_CONNECTED mode) receive LP-WUS, or can help the terminal MR operation after being indicated by LP-WUS. As mentioned above, Fig. 14 shows the QCL relationship for all NR RSs, and among them, the QCL relationship after RRC signaling for FR1 (bands below 6 GHz) is summarized in Table 2 below.

[0310] QCL SourceQCL targetQCL typeSSBTRSQCL-TypeCTRSCSI-RS (for CSI)QCL-TypeATRSCSI-RS (for CSI)QCL-TypeBTRSDMRSQCL-TypeACSI-RSDMRSQCL-TypeA

[0311] In general, LP-WUS can be primarily considered to be transmitted in an environment of SCS 15 kHz and 30 kHz in FR1. Therefore, it may be preferable to consider the QCL relationships in Table 2 for LP-WUS rather than all the QCL relationships in Fig. 14.

[0312] Additionally, considering that LP-WUR can be constructed with low-cost components, it can be assumed that it does not form a receive beam, and the related QCL-TypeD (spatial Rx parameter) may not be set with respect to LP-WUS.

[0313] For QCL-TypeB, since it is set only in one case in the NR standard where the CSI-RS for CSI purposes has TRS as a QCL source, it may not be considered in setting the QCL relationship of LP-WUS, or it may be considered to be set in a limited manner in relation to QCL-TypeA that includes it.

[0314] According to one embodiment, the TCI state related to LP-WUS reception may preferentially consider QCL-TypeA and QCL-TypeC.

[0315] We propose an existing NR signal / channel / CORESET that can establish a QCL relationship with LP-WUS. We propose an existing NR signal / channel / CORESET that can become a QCL source for LP-WUS, which is a QCL target.

[0316] For example, when LP-WUR receiving LP-WUS is classified into type #1 that can only receive OOK and type #2 that can also receive OFDM signals, the QCL source and / or QCL-Type that can be set according to each type can be set to be the same or different.

[0317] With QCL source and / or QCL-Type settings that are distinct for each type, OOK-based LP-WUR (LP-WUR type #1) sets the TCI state only for a specific QCL Type for a limited specific RS, while OFDM-based LP-WUR (LP-WUR type #2) can set multiple QCL Types for one or more RSs. OOK-based LP-WUR sets only a specific QCL-Type for one QCL source, while OFDM-based LP-WUR can set more than one QCL Type for one or more QCL sources.

[0318] For example, OOK-based LP-WUR (LP-WUR Type #1) may be configured only with SSB and QCL-TypeC, which are legacy NR signals. OFDM-based LP-WUR (LP-WUR Type #2) may be configured to have QCL-TypeA for TRS and CSI-RS for CSI purposes, and QCL-TypeC for SSB. In other words, OOK-based LP-WUR may be configured only with QCL-TypeC for SSB as a QCL source, and OFDM-based LP-WUR may be configured with QCL-TypeA or QCL-TypeC for SSB, TRS, and / or CSI-RS as a QCL source.

[0319] Whether or not to actually utilize the TCI state for receiving LP-WUS can be determined based on the capabilities of the terminal. On the base station side, the TCI state related to the transmission of LP-WUS and its QCL relationship can be set / instructed regardless of the LP-WUR type. The terminal can decide to apply the QCL relationship for the TCI state set in the terminal to the actual reception of LP-WUS depending on the LP-WUR type supported. The base station can set multiple TCI states regardless of the LP-WUR type, and the terminal can select which TCI state is actually applied according to the supported LP-WUR type. Alternatively, if the terminal can inform the base station of the LP-WUR it supports through the capability report, the base station can set the TCI state related to LP-WUS transmission accordingly.

[0320] For example, it may be considered that QCL-TypeD is set for transmission of LP-WUS. QCL-TypeD is set to utilize spatial Rx parameters and can generally be related to transmission per beam. For example, QCL-TypeD means that for a QCL target signal whose TCI state is set to have a relationship with SSB and QCL-TypeD, the terminal can receive the corresponding QCL target signal based on the reception direction (spatial Rx parameter) of the beam that received the SSB. Therefore, QCL-TypeD-related operations for LP-WUS that has been set with such specific RS and TCI state may be considered.

[0321] When a terminal receives an LP-WUS with an LP-WUR, the operation can be determined based on the configured TCI state. The TCI state is configured so that the received LP-WUS has a QCL relationship with the SSB, and multiple LP-WUS can be transmitted based on an SSB burst (a burst including multiple SSBs). The terminal can receive an SSB transmitted on a specific beam among the SSB bursts for system information reception, synchronization purposes, etc. Based on the TCI state for the reception beam, the terminal can receive an LP-WUS. Based on the reception beam of a specific SSB, the LP-WUS with the best quality among the multiple LP-WUSs can be smoothly received. For example, SSBs and multiple WUSs (or multiple WUS Monitoring occasions) within an SSB burst can be associated / linked with each other, and a QCL type D assumption for the same beam can be made between the linked SSB-WUSs.

[0322] If QCL-TypeD can be set in LP-WUS, it can be considered that the actual transmission of LP-WUS varies depending on which terminal or terminal group the transmission is targeting. For example, if LP-WUS is transmitted targeting a terminal group, it can be set to have a QCL relationship with an RS transmitted in a relatively broad beam, and if it is transmitted targeting a specific terminal, it can be set to have a QCL relationship with an RS transmitted in a relatively narrow beam. Alternatively, RSs that can have a QCL relationship can be set differently depending on whether the transmission is targeting a terminal group or a terminal. In this case, the terminal can receive the LP-WUS by distinguishing whether it is targeting a terminal or a terminal group based on the TCI state.

[0323] If QCL-TypeD can be set for LP-WUS, the terminal can receive LP-WUS based on a specific beam. In this case, multiple candidate LP-WUS can be set for one or more different beams so that the terminal can receive LP-WUS without a problem even when the beam transmitting LP-WUS is changed without a separate instruction / reconfiguration. By setting the TCI state corresponding to QCL-TypeD for multiple beams (RS transmitted by them), if the terminal does not receive LP-WUS smoothly on the beam on which it was receiving it, the terminal can operate to receive LP-WUS based on a different beam in the candidate LP-WUS monitoring occasion without a separate reconfiguration. The terminal can implicitly operate to receive LP-WUS in another LP-WUS monitoring occasion by utilizing LP-WUR without receiving a separate instruction. Alternatively, an instruction to activate / deactivate that the beam based on which LP-WUS is received has changed can be included through MAC CE or DCI.

[0324] LP-SS can be considered as a reference signal with which LP-WUS can have a QCL relationship. LP-SS can provide synchronization information for LP-WUS reception and additional information configured separately. Therefore, when a terminal receives LP-WUS with LP-WUR, it can consider an operation that utilizes channel estimation-related information of previously received LP-SS. For example, the TCI state can be set so that LP-WUS has a QCL relationship with LP-SS, and QCL information acquired based on LP-SS can be used for LP-WUS reception.

[0325] To achieve this, the LP-SS may need to have a QCL relationship with the existing NR signal. The LP-SS may have a QCL relationship with TRS or SSB. For example, if the TCI state of the LP-SS is set so that transmission is performed per beam and has a QCL-TypeD relationship with SSB, and the TCI state of the LP-WUS is set so that the LP-SS has a QCL-TypeD relationship, then the beam of the LP-WUS can be formed based on the transmission of the LP-SS.

[0326] For example, the TCI state of LP-WUR may be configured to have a QCL relationship for both a plurality of signals, for example, a conventional NR signal (e.g., SSB) and LP-SS. Depending on the LP-WUR type supported by the terminal, the terminal may be configured to have a QCL relationship for the NR signal and / or the LP-SS. For example, a terminal supporting OOK-based LP-WUR may be configured to have a QCL relationship for LP-SS, and a terminal supporting OFDM-based LP-WUR may be configured to have a QCL relationship for SSB. All of these can be configured regardless of the LP-WUR type, and may be explicitly determined through the capability reported by the terminal and / or the configuration / instruction of the base station. Depending on the LP-WUR type, the TCI state that can be configured for the terminal may be automatically distinguished as an NR signal or LP-SS, or may be distinguished and configured through the terminal capability and the instruction of the base station.

[0327] Additionally, even for terminals supporting OFDM-based LP-WUR, it may be considered that the TCI state of the QCL relationship targeting LP-SS is indicated / set according to the preference of the terminal or the instruction of the base station.

[0328] When configuring transmission and reception of LP-WUS (higher layer signaling), a list of up to N TCI states can be configured. When CORESET is configured according to the NR standard, up to 64 TCI states can be configured. Similarly, a list of up to 64 or more or fewer TCI states can be configured for LP-WUS. At this time, TCI states distinguished by LP-WUR type can be configured in the list. If the terminal reports the LP-WUR type supported, all configured TCI states can be configured related to the corresponding LP-WUR type. Alternatively, the configurable TCI states can be configured by considering all LP-WUR types, and only TCI states that can be supported according to the terminal's capability can be indicated.

[0329] Existing NR signals that can have a QCL relationship for TCI state configuration may include at least one of SSB, TRS, and / or CSI-RS, and may additionally include a CORESET related to PDCCH monitoring. For example, TCI state information configured for LP-WUS may include information about a specific CORESET ID and QCL relationship. Which TCI state will be used by the UE when actually receiving LP-WUS may be indicated via RRC signaling, or may be indicated by a MAC CE activation command to select (at least) one of the configured TCI states. The TCI state may be indicated via SIB1 and / or SIBx (a system information block that provides information related to LP-WUS). If the TCI state is set but there is no separate instruction, the terminal can perform LP-WUS reception assuming that the SSB involved in the recent random access procedure (e.g., the SSB mapped to the RO used for RACH preamble transmission according to the SSB-to-RO mapping relationship) or the SSB found during the initial access process has a QCL relationship.

[0330] Proposal 2: Example of establishing QCL relations for the TCI state of LP-WUS

[0331] As an example, Proposal 2 can be applied to RRC_IDLE / INACTIVE mode.

[0332] An LP-WUS occasion (LO) may include multiple LP-WUS MOs (monitoring occasions). For example, an LO may be composed of N * K LP-WUS MOs, where N is the number of beams (or TCI states) corresponding to the LP-WUS, and K is the number of LP-WUS MOs per beam. For example, K may be an integer greater than or equal to 1. When transmitting an LP-WUS (including an instruction regarding paging) to a terminal in IDLE / INACTIVE mode, transmission per beam and multiple LP-WUS transmissions through each beam may be supported. Therefore, the number N of beams related to LP-WUS transmission may need to be determined through the TCI state configuration of the LP-WUS.

[0333] As in the example of Proposal 1 above, it can be considered that LP-SS is configured as the QCL source of LP-WUS. In this case, it can be assumed that SSB is configured as the QCL source of LP-SS. Following this configuration, the terminal can obtain QCL information related to LP-WUS reception through LP-SS and QCL information related to LP-SS reception through SSB.

[0334] For example, the number of LP-WUS MOs corresponding to a beam can be defined for each QCL relationship between LP-WUS, LP-SS, and SSB.

[0335] (1) Case 1: When the LP-WUS beam index is determined based on the SSB index

[0336] This may be useful when the TCI state of the LP-SS is not set and the LP-WUS is set or assumed to have a QCL relationship with the SSB.

[0337] When a terminal in IDLE / INACTIVE mode receives an LP-WUS that can instruct paging, the terminal may assume that the QCL relationship of the LP-WUS is set separately, or if not set, that it has a QCL relationship with SSB.

[0338] When a terminal in IDLE / INACTIVE mode receives an LP-WUS that can instruct paging, the number of beams N corresponding to the LP-WUS may vary depending on the number of SSBs (the number of beams). N is a natural number that is a multiple of 1 or 2, for example, the number of SSBs (N SSB ) of 2 n can be defined as a power of 2 (where n is an integer). The maximum value of N can be determined as one of the powers of 2. N SSB If is greater than N, the terminal can assume that the N beams are transmitted as a broad beam that can include adjacent beams among the beams transmitting SSB. Alternatively, the index of the LP-WUS transmission beam can be values ​​selected from N indices among the SSB indices with as equal intervals as possible. N SSB If is less than N, multiple LP-WUS beam indices can be set to correspond to one SSB index in sequence.

[0339] For example, N SSB If =8, N can be determined as 1, 2, 4, 8, 16, etc.

[0340] - When N=1, 8 SSB indices correspond to LP-WUS beam index 0.

[0341] - When N=4, SSB index 0, 1 may correspond to LP-WUS beam index 0, SSB index 2, 3 may correspond to LP-WUS beam index 1, SSB index 4, 5 may correspond to LP-WUS beam index 2, and SSB index 6, 7 may correspond to LP-WUS beam index 3. Alternatively, one of SSB index 0, 1, for example, 0, may correspond to LP-WUS beam index 0, one of SSB index 2, 3, for example, 2, may correspond to LP-WUS beam index 1, one of SSB index 4, 5, for example, 4, may correspond to LP-WUS beam index 2, and one of SSB index 6, 7, for example, 6, may correspond to LP-WUS beam index 3.

[0342] - When N=8, the SSB index and LP-WUS beam index correspond one-to-one.

[0343] - In case of N=16, SSB index 0 can be repeatedly matched with LP-WUS beam index 0, 1, and SSB index 1 can be matched with LP-WUS beam index 2, 3, and thus SSB index 7 can be matched with LP-WUS index 14, 15.

[0344] (2) Case 2: When the LP-WUS beam index is determined based on the LP-SS index

[0345] This may be useful when LP-SS is set or assumed to have a QCL relationship with SSB, and LP-WUS is set or assumed to have a QCL relationship with LP-SS (or SSB).

[0346] When a terminal in IDLE / INACTIVE mode receives an LP-WUS that can instruct paging, the terminal may assume that the QCL relationship of the LP-WUS is separately set, or, if not set, that it has a QCL relationship with the LP-SS.

[0347] When a terminal in IDLE / INACTIVE mode receives an LP-WUS that can indicate paging, the number of beams N corresponding to the LP-WUS may vary depending on the number of LP-SSs (the number of beams). Based on the QCL relationship between the LP-WUS and LP-SS, the number of LP-SSs can be calculated instead of the number of SSBs, as in Case 1.

[0348] For example, when the number of LP-SS is expressed as M, if M=8, N can be determined as 1, 2, 4, 8, 16, etc.

[0349] - When N=1, 8 LP-SS indices correspond to LP-WUS beam index 0.

[0350] - When N=4, LP-SS index 0, 1 may correspond to LP-WUS beam index 0, LP-SS index 2, 3 may correspond to LP-WUS beam index 1, LP-SS index 4, 5 may correspond to LP-WUS beam index 2, and LP-SS index 6, 7 may correspond to LP-WUS beam index 3. Alternatively, one of LP-SS index 0, 1, for example, 0 may correspond to LP-WUS beam index 0, one of LP-SS index 2, 3, for example, 2 may correspond to LP-WUS beam index 1, one of LP-SS index 4, 5, for example, 4 may correspond to LP-WUS beam index 2, and one of LP-SS index 6, 7, for example, 6 may correspond to LP-WUS beam index 3.

[0351] - When N=8, the LP-SS index and LP-WUS beam index correspond one-to-one.

[0352] - In case of N=16, LP-SS index 0 and LP-WUS beam index 0, 1, and LP-SS index 1 and LP-WUS beam index 2, 3 can be repeatedly performed to correspond to LP-SS index 7 and LP-WUS index 14, 15.

[0353] When Case 1 or Case 2 is applied, the type of LP-WUR can be considered. For OFDM-based LP-WUR terminals, since SSB (PSS / SSS) can be received, N can be determined by applying the method of Case 1, and for OOK-based LP-WUR terminals, N can be determined by applying the method of Case 2 with LP-SS.

[0354] Alternatively, if a certain amount of time has not passed since the terminal received the SSB, the number of N can be determined as the number of SSBs, as in Case 1.

[0355] Alternatively, the base station can directly instruct the terminal the N value related to LP-WUS reception.

[0356] For example, if the terminal is given at least one of the QCL relationship of the LP-SS or the LP-SS configuration and / or the configuration regarding the number of beams in the LP-SS, and thus the number N of beams corresponding to the LP-WUS is not explicitly given, the terminal may determine N to be the same value as the number of LP-SS. If the number N of beams corresponding to the LP-WUS is explicitly set to the terminal, the QCL relationship of the LP-WUS (SSB or LP-SS) and the LP-WUS beam index supported by the terminal may be determined differently depending on the LP-WUR type based on Case 1 or Case 2.

[0357] Proposal 3: MR operation of RRC_CONNECTED mode terminal after receiving LP-WUS with TCI state set (e.g., PDCCH monitoring)

[0358] It can be considered that (existing) CORESET is set as the QCL source of LP-WUS.

[0359] According to the current NR standard, a CORESET for PDCCH monitoring in a UE can have a list of up to 64 TCI states. For CORESETs other than CORESET 0 (e.g., a CORESET for SIB 1 scheduling), the selection of one of the TCI states configured by RRC signaling or RRC can be instructed via the MAC CE activation command. If no instruction is given, the UE can receive PDCCH DMRS in the corresponding CORESET, assuming that the SSB received during the initial access phase has a QCL relationship.

[0360] If an LP-WUS is configured to have a QCL relationship with a specific CORESET, when a UE receives a PDCCH monitoring instruction using the LP-WUS, the specific CORESET may be given priority in subsequent PDCCH monitoring, or the LP-WUS's reception channel estimation information may be utilized when receiving the specific CORESET. The TCI state that can be configured in the LP-WUS may include a specific CORESET (e.g., CORESET ID) and a specific QCL type. For example, if the TCI state of an LP-WUS is configured to have a QCL relationship with CORESET#k, when the UE performs the indicated operation upon receiving a PDCCH monitoring instruction using LP-WUS, SS set monitoring related to CORESET#k may be given priority, or channel estimation information may be utilized when receiving a PDCCH for CORESET#k during the SS set monitoring. Meanwhile, information on the linkage relationship between a CORESET and an SS set may be included in the SS set configuration configured through upper layer signaling.

[0361] Alternatively, if the TCI state is set such that the LP-WUS has a specific CORESET or SSB / TRS / CSI-RS and QCL-TypeD, such a setting may be intended to provide information that can assist in subsequent PDCCH reception rather than providing direct beam information (spatial Rx parameters) related to the actual LP-WUS transmission. For example, if the UE successfully receives the LP-WUS, the QCL information of the LP-WUS may be helpful in determining the reception beam when performing subsequent MR PDCCH monitoring operations.

[0362] Meanwhile, the following may apply with respect to the above suggestions 1, 2 and / or 3.

[0363] As described above, LP SS and LP WUS can be introduced into the NR standard to support LP WUR, and LP WUS can be simply referred to as WUS.

[0364] - LP SS (Low Power Synchronization Signal): Transmitted in On Off Keying (OOK) mode on consecutive symbols within a slot, and EPRE for SSB, first RB location, number of symbols, etc. can be provided as SIB1-based parameters (lpss StartSymbol, lpss periodicityOffset, etc.). The UE can perform synchronization by aligning the LPSS reception time with the SSB beam and QCL (quasi co location) relationship.

[0365] - WUS(Wake Up Signal): Uses the same OOK structure, but WUS Monitoring Occasions(MOs) are defined within one WUS occasion, and a WUS occasion can be linked to a paging occasion. The period of a WUS occasion can be the same as the DRX period in IDLE / INACTIVE state. The UE can monitor only in the slots / symbols specified by the bitmap(WUS_available_slot / symbol). If a UE dedicated codepoint is detected in WUS, Type 2 PDCCH CSS can be activated to receive a paging message.

[0366] LPSS / WUS parameters may be provided for RRC_IDLE / INACTIVE states. For UEs in RRC_CONNECTED state, the start position of WUS MO monitoring may be determined based on drx onDurationTimer or wus PDCCHMonitoringTimer, depending on the configuration option. It may operate in the same SCS as the active DL BWP. WUS monitoring may be omitted during the ACTIVE Time or DTX inactive period.

[0367] - The WUS sequence can be generated based on ZC (Zadoff Chu), and the root sequence number and cyclic shift can be provided through upper layer signaling. The generated sequence can be overlaid on the OOK (On Off Keying) symbol, which can generate a complex value block x(k,l). At this time, the number of 'ON' bits (M value) can be set differently depending on the DRX state (IDLE / INACTIVE or CONNECTED).

[0368] - The LPSS sequence can be set to any of the lengths {6, 8, 12, 16, 32}, and four bit patterns can be predefined for this setting. An additional ZC-based sequence can be generated based on upper layer signaling. LPSS can also be converted to an OOK symbol block and then mapped.

[0369] Figure 15 is a diagram illustrating the operation of a terminal and a network according to one embodiment. Since Figure 15 is an implementation example of at least some of the previously described proposals, the previously described proposals may be referenced even if not otherwise specifically mentioned.

[0370] Referring to FIG. 15, a terminal can transmit a terminal capability report to a base station (A05).

[0371] A base station can provide various configuration information to a terminal through at least one upper-layer signaling (A10). The configuration information may include, for example, at least one of configuration information for WUS, configuration information for CORESET, configuration information for SS set, configuration information for antenna port, configuration information for TCI state, or configuration information for PDCCH.

[0372] The base station can transmit various DL signals (A15). The DL signals may include at least one of a downlink reference signal, SSB, LP-SS, PDCCH, and / or PDSCH. The downlink reference signal may include at least one of the signals listed in Table 1.

[0373] The base station can generate a WUS (A20) and transmit it to the terminal (A30). The WUS can be generated based on OOK modulation. The WUS can include OOK symbols overlaid with an OFDM sequence.

[0374] The terminal can monitor and detect WUS based on configuration information for WUS (A25). For example, the terminal can detect WUS based on the QCL type of the DL signal that becomes the QCL source signal. The QCL type can be related to at least one of Doppler shift, Doppler spread, average delay, delay spread, or spatial Rx parameter. The QCL type can be determined based on the WUS detection capability of the terminal. The DL signal that becomes the QCL source signal can include at least one of SSB (synchronization signal block) or LP-SS (low power-synchronization signal).

[0375] For example, the terminal may transmit a terminal capability report including information about the terminal's capability for WUS detection. The configuration information may include information about the QCL type determined based on the terminal capability report.

[0376] For example, the QCL type may be determined by the terminal itself based on the terminal's ability to detect the WUS.

[0377] Based on the terminal having the ability to detect on-off keying (OOK) symbols for the WUS, the QCL type may be determined as a first QCL type. Based on the terminal having the ability to detect an orthogonal frequency division multiplexing (OFDM) sequence overlaid on the OOK symbols, the QCL type may be determined as a second QCL type.

[0378] The above first QCL type may be a subset of the above second QCL type.

[0379] The first QCL type may be related to the Doppler spread and the average delay, and the second QCL type may be related to the Doppler shift, the Doppler spread, the average delay, and the delay spread.

[0380] The base station can generate a PDCCH (A35) and transmit it to the terminal (A45).

[0381] The terminal can monitor a physical downlink control channel (PDCCH) on a control resource set (CORESET) based on detection of a WUS (A40). The terminal can monitor the PDCCH based on the QCL relationship between the WUS and the CORESET. The configuration information can include at least one of ID (identifier) ​​information of the CORESET or information on the QCL type between the WUS and the CORESET.

[0382] The WUS detection operation of the terminal described above can be performed in the RRC Connected and / or RRC idle / inactive state.

[0383] Figure 16 illustrates a flowchart of a method performed by a terminal according to one embodiment. Since Figure 16 is an implementation example of at least some of the proposals described above, the proposals described above may be referenced even if not otherwise specifically mentioned.

[0384] Referring to FIG. 16, the terminal can receive configuration information related to WUS (wakeup signal) through upper layer signaling (B05).

[0385] The terminal can detect the WUS based on the above configuration information (B10). The terminal's WUS detection operation can be performed in the RRC Connected and / or RRC idle / inactive states.

[0386] Based on the capability of the terminal for the above WUS detection, a QCL (quasi co-location) type related to at least one of Doppler shift, Doppler spread, average delay, delay spread, or spatial Rx parameter can be determined.

[0387] The above terminal can detect the WUS based on the QCL type.

[0388] Based on the terminal having the ability to detect on-off keying (OOK) symbols for the WUS, the QCL type may be determined as a first QCL type. Based on the terminal having the ability to detect an orthogonal frequency division multiplexing (OFDM) sequence overlaid on the OOK symbols, the QCL type may be determined as a second QCL type.

[0389] The above first QCL type may be a subset of the above second QCL type.

[0390] The first QCL type may be related to the Doppler spread and the average delay, and the second QCL type may be related to the Doppler shift, the Doppler spread, the average delay, and the delay spread.

[0391] The first QCL type may be associated with one downlink reference signal, and the second QCL type may be associated with one or more downlink reference signals.

[0392] For example, the terminal may transmit a terminal capability report including information about the terminal's capability for WUS detection. The configuration information may include information about the QCL type determined based on the terminal capability report.

[0393] For example, the QCL type may be determined by the terminal based on the terminal's capability for WUS detection.

[0394] The terminal may detect the WUS based on the specific downlink signal and the WUS having a QCL relationship for the QCL type. The specific downlink signal may include at least one of a synchronization signal block (SSB) or a low power-synchronization signal (LP-SS).

[0395] The terminal can monitor a physical downlink control channel (PDCCH) on a control resource set (CORESET) based on detection of the WUS. The terminal can monitor the PDCCH based on the QCL relationship between the WUS and the CORESET.

[0396] The above setting information may include at least one of ID (identifier) ​​information of the CORESET or information on the QCL type between the WUS and the CORESET.

[0397] Figure 17 illustrates a flowchart of a method performed by a base station according to one embodiment. Figure 17 is an implementation example of at least some of the proposals described above, and thus, the proposals described above may be referenced even if not otherwise specifically mentioned.

[0398] Referring to Figure 17, the base station can receive a terminal capability report from the terminal (C05).

[0399] The base station can transmit configuration information related to the WUS (wakeup signal) to the terminal through upper layer signaling (C10).

[0400] The base station can transmit the WUS to the terminal (C15).

[0401] For example, the terminal capability report may include information about the terminal's wakeup signal (WUS) detection capability. Based on the information about the WUS detection capability, the base station may determine a QCL (quasi co-location) type related to at least one of a Doppler shift, a Doppler spread, an average delay, a delay spread, or a spatial Rx parameter for the WUS. The configuration information may include information about the determined QCL type.

[0402] The base station may determine the QCL type as a first QCL type based on whether the terminal has the ability to detect on-off keying (OOK) symbols for the WUS. The base station may determine the QCL type as a second QCL type based on whether the terminal has the ability to detect an orthogonal frequency division multiplexing (OFDM) sequence overlaid on the OOK symbols.

[0403] The above first QCL type may be a subset of the above second QCL type.

[0404] The first QCL type may be related to the Doppler spread and the average delay, and the second QCL type may be related to the Doppler shift, the Doppler spread, the average delay, and the delay spread.

[0405] The first QCL type may be associated with one downlink reference signal, and the second QCL type may be associated with one or more downlink reference signals.

[0406] A specific downlink signal and the WUS may be in a QCL relationship for the QCL type. The specific downlink signal may include at least one of a synchronization signal block (SSB) or a low power-synchronization signal (LP-SS).

[0407] The base station may transmit a physical downlink control channel (PDCCH) to the terminal on a control resource set (CORESET) based on the transmission of the WUS. The WUS and the CORESET may be in a QCL relationship. The configuration information may include at least one of ID (identifier) ​​information of the CORESET or information on the QCL type between the WUS and the CORESET.

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

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

[0410] 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 terminal, Receive configuration information related to WUS (wakeup signal) through upper layer signaling; and Including detecting the WUS based on the above setting information, Based on the capability of the terminal for the WUS detection, a QCL (quasi co-location) type related to at least one of Doppler shift, Doppler spread, average delay, delay spread, or spatial Rx parameter is determined, A method wherein the terminal detects the WUS based on the QCL type.

2. In paragraph 1, Based on the above terminal having the ability to detect OOK (on-off keying) symbols for the WUS, the QCL type is determined as the first QCL type, A method wherein the QCL type is determined as a second QCL type based on the terminal having the ability to detect an OFDM (orthogonal frequency divisional multiplexing) sequence overlaid on the OOK symbols.

3. In paragraph 2, A method wherein the first QCL type is a subset of the second QCL type.

4. In paragraph 2, The above first QCL type is related to the Doppler spread and the average delay, A method related to the Doppler shift, the Doppler spread, the average delay and the delay spread of the second QCL type.

5. In paragraph 2, The above first QCL type is associated with one downlink reference signal, A method wherein the second QCL type is related to one or more downlink reference signals.

6. In paragraph 1, Further comprising transmitting a terminal capability report including information on the terminal's capability for the above WUS detection, A method wherein the above setting information includes information about the QCL type determined based on the terminal capability report.

7. In paragraph 1, A method wherein the QCL type is determined by the terminal based on the terminal's ability to detect the WUS.

8. In paragraph 1, The terminal detects the WUS based on the fact that the specific downlink signal and the WUS are in a QCL relationship for the QCL type, A method wherein the specific downlink signal comprises at least one of a synchronization signal block (SSB) or a low power-synchronization signal (LP-SS).

9. In paragraph 1, Further comprising monitoring a PDCCH (physical downlink control channel) on a CORESET (control resource set) based on detection of the above WUS, A method for monitoring the PDCCH based on the above terminal being in a QCL relationship with the WUS and the CORESET.

10. In paragraph 9, A method wherein the above setting information includes at least one of ID (identifier) ​​information of the CORESET or information on the QCL type between the WUS and the CORESET.

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

12. In the device, at least one processor; and At least one memory configured to store instructions that are executed by said at least one processor to cause said at least one processor to perform operations, The operations of the above processor are: Receive configuration information related to WUS (wakeup signal) through upper layer signaling; and Including detecting the WUS based on the above setting information, Based on the capability of the device for the WUS detection, a QCL (quasi co-location) type related to at least one of Doppler shift, Doppler spread, average delay, delay spread or spatial Rx parameter is determined, The above device is a device that detects the WUS based on the QCL type.

13. In paragraph 12, A device wherein the above device is a terminal including a transceiver or a processing device configured to control the terminal.

14. In a method performed by a base station, Receive a terminal capability report containing information about the terminal's wakeup signal (WUS) detection capability; Transmitting configuration information related to WUS to the terminal through upper layer signaling; and Including transmitting the WUS to the terminal, Based on the information about the WUS detection capability, a QCL (quasi co-location) type related to at least one of a Doppler shift, a Doppler spread, an average delay, a delay spread, or a spatial Rx parameter is determined for the WUS, A method wherein the above setting information includes information about the determined QCL type.

15. At the base station, at least one processor; and At least one memory configured to store instructions that are executed by said at least one processor to cause said at least one processor to perform operations, The operations of the above processor are: Receive a terminal capability report containing information about the terminal's wakeup signal (WUS) detection capability; Transmitting configuration information related to WUS to the terminal through upper layer signaling; and Including transmitting the WUS to the terminal, Based on the information about the WUS detection capability, a QCL (quasi co-location) type related to at least one of a Doppler shift, a Doppler spread, an average delay, a delay spread, or a spatial Rx parameter is determined for the WUS, The above setting information is a base station including information on the determined QCL type.

Images