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

Abstract

A terminal according to an embodiment of the present disclosure may receive a WUS configuration and a DRX configuration through higher layer signaling, and monitor at least one of a first WUS related to the start of a first timer or a second WUS related to the start of a second timer on the basis of the WUS configuration, wherein the first timer is a DRX on-duration timer of the DRX configuration, the WUS configuration includes information on WUS MOs, WUS MOs belonging to a specific window among the WUS MOs are configured as first WUS MOs for the first WUS, and the remaining WUS MOs are configured as second WUS MOs for the second WUS.

Description

A method performed by a terminal or network in a wireless communication system and an apparatus for the same

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

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

[0003] 5G NR and next-generation wireless communication systems are being designed and researched to support not only mobile communication but also various vertical services. Along with low latency, reliability, and availability, UE energy efficiency is also a critical design element in wireless communication. Currently, wireless terminals require charging approximately every day or several days, depending on usage patterns. Generally, 5G terminals consume tens of mW in RRC Idle / Inactive states and hundreds of mW in RRC Connected states. Wireless communication design aimed at conserving battery power consumption is essential for improving energy efficiency and user convenience.

[0004] Energy efficiency is even more critical for UEs using low-capacity rechargeable batteries or single coin cells that lack a continuous energy source. In vertical services, sensors and actuators are widely used for monitoring, measurement, and charging; some batteries may not be rechargeable and may need to last for at least several years. However, wearable devices such as smartwatches, rings, eHealth devices, and medical monitoring equipment generally find it difficult for batteries to last for more than 1 to 2 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 could be considered to meet the long battery life requirements mentioned above, this increases latency and may therefore not be suitable for services requiring low latency. For instance, in a fire detection / suppression scenario, the shutter must close and the sprinkler system activated within 1-2 seconds after the sensor detects a fire, but a long eDRX cycle cannot satisfy these latency requirements. As such, eDRX is not suitable for low-latency use cases.

[0006] Meanwhile, the introduction of LP WUR (low-power wake-up receiver) for power saving in terminals is currently being discussed in 5G NR, and when the terminal wakes up due to WUS detection by LP WUR, the terminal performs PDCCH monitoring.

[0007] The technical problem to be solved by the present disclosure is to provide a method for efficiently performing a wireless signal transmission and reception process and an apparatus for doing so. For example, a method for monitoring WUSs related to different operations using the LP WUR of a terminal may be provided. For example, a method for more efficiently setting / distinguishing WUS MOs (monitoring occasions) for different types of WUSs and a terminal operation that follows upon detection of each WUS may be provided.

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

[0009] A method performed by a terminal according to one aspect of the present disclosure comprises: receiving a WUS (wake-up signal) setting and a DRX (discontinuous reception) setting through upper layer signaling; and monitoring at least one of a first WUS associated with the start of a first timer or a second WUS associated with the start of a second timer based on the WUS setting, wherein the first timer is a DRX on-duration timer of the DRX setting, and the WUS setting includes information on WUS MOs (monitoring occasions), and among the WUS MOs, WUS MOs belonging to a specific window are set as first WUS MOs for the first WUS, and the remaining WUS MOs can be set as second WUS MOs for the second WUS.

[0010] The second timer above may be a timer configured independently of the DRX setting.

[0011] During a specific time when at least one of the first timer or the second timer is driven, the terminal can monitor the PDCCH (physical downlink control channel). The terminal can monitor the first WUS on one or more first WUS MOs included within the specific time.

[0012] The above terminal may omit monitoring of the second WUS on one or more second WUS MOs included within the above specific time.

[0013] The above WUS settings may include information regarding the specific window.

[0014] The above specific window can be set based on the DRX cycle of the above DRX setting.

[0015] The above specific window may be located before the start time of the above DRX cycle.

[0016] The terminal may omit at least one of periodic CSI (channel state information) reporting or periodic L1-RSRP (layer-reference signal received power) reporting during the time the second timer is operating.

[0017] The terminal can perform at least one of the periodic CSI report or the periodic L1-RSRP report within the time during which the first timer is driven.

[0018] The first WUS and the second WUS can be monitored by the LP WUR (low power wake up receiver) of the terminal.

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

[0020] An apparatus according to another aspect of the present disclosure comprises: at least one processor; and at least one memory configured to store instructions that cause the at least one processor to perform operations by being executed by the at least one processor, wherein the operations of the processor include receiving a WUS (wake-up signal) setting and a DRX (discontinuous reception) setting through upper layer signaling; and monitoring at least one of a first WUS associated with the start of a first timer or a second WUS associated with the start of a second timer based on the WUS setting, wherein the first timer is a DRX on-duration timer of the DRX setting, and the WUS setting includes information on WUS MOs (monitoring occasions), and among the WUS MOs, WUS MOs belonging to a specific window are set as first WUS MOs for the first WUS, and the remaining WUS MOs can be set as second WUS MOs for the second WUS.

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

[0022] According to another aspect of the present disclosure, a method performed by a base station comprises: transmitting a WUS (wake-up signal) setting and a DRX (discontinuous reception) setting through upper layer signaling; and transmitting at least one of a first WUS associated with the start of a first timer or a second WUS associated with the start of a second timer based on the WUS setting, wherein the first timer is a DRX on-duration timer of the DRX setting, and the WUS setting includes information on WUS MOs (monitoring occasions), and among the WUS MOs, WUS MOs belonging to a specific window are set as first WUS MOs for the first WUS, and the remaining WUS MOs are set as second WUS MOs for the second WUS.

[0023] A base station according to another aspect of the present disclosure comprises at least one processor; and at least one memory configured to store instructions that cause the at least one processor to perform operations by being executed by the at least one processor, wherein the operations of the processor include transmitting a WUS (wake-up signal) setting and a DRX (discontinuous reception) setting through upper layer signaling; and transmitting at least one of a first WUS associated with the start of a first timer or a second WUS associated with the start of a second timer based on the WUS setting, wherein the first timer is a DRX on-duration timer of the DRX setting, and the WUS setting includes information on WUS MOs (monitoring occasions), and among the WUS MOs, WUS MOs belonging to a specific window are set as first WUS MOs for the first WUS, and the remaining WUS MOs are set as second WUS MOs for the second WUS.

[0024] According to the present disclosure, signal transmission and reception can be performed efficiently in a wireless communication system. According to one embodiment, various terminal power saving operations can be performed by supporting the simultaneous configuration of LP WUS 1 and LP WUS 2 related to different operations, and by the terminal distinguishing each LP WUS using WUS MO (monitoring occasion), confusion between terminal operations regarding LP WUS 1 and terminal operations regarding LP WUS 2 can be prevented in advance.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0038] FIG. 13 illustrates the procedure for transmitting and receiving uplink / downlink signals between a base station and a terminal according to one embodiment.

[0039] FIG. 14 is a diagram illustrating LP WUS monitoring and Wake-up indication when both WUS-related operation 1 and operation 2 are set according to one embodiment.

[0040] FIG. 15 is a diagram illustrating the operation of a terminal and a network according to one embodiment.

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

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

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

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

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

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

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

[0048] In addition, terms such as "first," "second," etc. in this specification are used solely for the purpose of distinguishing one component from another and are not used to limit the components, nor are they used to limit the order or importance of the components unless specifically limited. Accordingly, a first component in one embodiment of this specification may be referred to as a second component in another embodiment, and likewise, a second component in one embodiment may be referred to as a first component in another embodiment.

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

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

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

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

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

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

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

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

[0057] <Symbols, Abbreviations, Terms>

[0058] - ACS: Adjacent Channel Selectivity

[0059] - ADC: Analog to Digital Converter

[0060] - ASCS: Adjacent Subcarrier selectivity

[0061] - ASK: Amplitude Shift Keying

[0062] - BB: Base Band

[0063] - BLER: Block Error Rate

[0064] - BPF: Band Pass Filter

[0065] - BWP: Bandwidth part

[0066] - CAP: Channel Access Procedure

[0067] - CFO: Center frequency offset

[0068] - CORESET: Control resource set

[0069] - CRC: Cyclic redundancy check

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

[0071] - CSI: Channel state information

[0072] - DCI: Downlink Control Information

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

[0074] - DRX: Discontinuous Reception

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

[0076] - eDRX: Extended DRX

[0077] - EPRE: Energy Per Resource Element

[0078] - FAR: False Alarm Rate

[0079] - FCS: Frame Check Sequence

[0080] - FSK: Frequency Shift Keying

[0081] - FLL: Frequency Locked Loop

[0082] - FFT: Fast Fourier Transform

[0083] - FR1: Frequency range 1

[0084] - FR2: Frequency range 2

[0085] - ICS: In-channel Selectivity

[0086] - IF: Intermediate Frequency

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

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

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

[0090] - LO: Local Oscillator

[0091] - LNA: Low Noise Amplifier

[0092] - LPF: Low Pass Filter

[0093] - LR: LP-WUR

[0094] - MDR: Miss Detection Rate

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

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

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

[0098] - NF: Noise Figure

[0099] - OOK: On-Off keying

[0100] - OFDM: Orthogonal Frequency Division Multiplexing

[0101] - PDCCH: Physical Downlink Control Channel

[0102] - PUCCH: Physical Uplink Control Channel

[0103] - PUSCH: Physical Uplink Shared Channel

[0104] - PDSCH: Physical Downlink Shared Channel

[0105] - PRACH: Physical Random-Access Channel

[0106] - PEI: Paging Early Indication

[0107] - PO: Paging Occasion

[0108] - PTW: Paging Time Window

[0109] - PLL: Phase Locked Loop

[0110] - PAPR: Peak to Average Power Ratio

[0111] - RRC: Radio Resource Control

[0112] - RRM: Radio Resource Management

[0113] - RLM: Radio Link Monitoring

[0114] - RS: Reference Signal

[0115] - RSRP: Reference Signal Received Power

[0116] - RSRQ: Reference Signal Received Quality

[0117] - BFD: Beam Failure Detection

[0118] - RTC: Real Time Clock

[0119] - RF: Radio Frequency

[0120] - SCS: Sub-carrier spacing

[0121] - SSB: Synchronization Signal Block

[0122] - SSSG: Search Space Set Group

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

[0124] - SNR: Signal to Noise Ratio

[0125] - SC: Subcarrier

[0126] - TBS: Transport Block Size

[0127] - TDRA: Time Domain Resource Allocation

[0128] - Ucell: Unlicensed cell

[0129] - UE: User Equipment

[0130] - XR: Extended reality

[0131] - TAG: Timing advance group

[0132] - AmIoT: Ambient Internet of Things

[0133] - CW: Carrier Wave

[0134] - BSC: Backscattering

[0135] - BSS: Backscattered signal

[0136] - SIC: Self-Interference Cancellation

[0137] - RFID: Radio Frequency Identifier

[0138] - IN: Intermediate Node

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

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

[0141] - CORESET: Control Resource Set (Refers to the time and frequency resource range where PDCCH can be transmitted, and the number of CORESETs per BWP may be limited.)

[0142] - REG: Resource element group

[0143] - SFI: Slot Format Indicator (An indicator that indicates the symbol level DL / UL direction within a specific slot(s), transmitted via the group common PDCCH.)

[0144] - COT: Channel occupancy time

[0145] - SPS: Semi-persistent scheduling

[0146] - QCL: Quasi-Co-Location (The QCL relationship between two reference signals means that QCL parameters, such as Doppler shift, Doppler spread, average delay, delay spread, and spatial Rx parameters obtained from one reference signal, can also be applied to another reference signal (or the antenna port(s) of the corresponding RS). In NR systems, four QCL types are defined as follows: 'typeA': {Doppler shift, Doppler spread, average delay, delay spread}, 'typeB': {Doppler shift, Doppler spread}, 'typeC': {Doppler shift, average delay}, 'typeD': {Spatial Rx parameter}. For a certain DL RS antenna port(s), if 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.)

[0147] - TCI: Transmission Configuration Indication (A single TCI state contains QCL relationships between one or more DL RSs, such as DM-RS ports of the PDSCH, the DM-RS port of PDCCH, or the CSI-RS port(s) of a CSI-RS resource. For 'Transmission Configuration Indication' among the fields within the DCI that schedule PDSCH, the TCI state index corresponding to each code point constituting the field is activated by MAC CE, and the TCI state setting for each TCI state index is configured via RRC signaling. In Rel-16 NR systems, the TCI state is configured between DL RSs, but configuration between DL RSs and UL RSs, or between UL RSs and UL RSs, may be permitted in future releases. Examples of UL RSs include SRS, PUSCH DM-RS, and PUCCH DM-RS.)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0177] In FIG. 4, for the sake of simplicity of explanation, the first node and the second node are assumed to be a terminal and a base station, respectively, and the operation of the terminal (110) and the base station (120) transmitting and / or receiving data, and the operation performed prior to this, are illustrated. However, the operation of FIG. 4 is not limited to the operation between the terminal and the base station, but can be interpreted as the operation between the first node and the second node. Additionally, FIG. 4 illustrates the operation of direct transmission and reception of wireless signals between the terminal (110) and the base station (120), but there may be one or more intermediate points between the terminal (110) and the base station (120), and wireless signals may be transmitted and received via one or more intermediate points.

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

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

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

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

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

[0183] 6G System Core Technology

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

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

[0186] artificial intelligence

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0218] A two-side model can refer to an AI / ML model in which joint inference is performed across multiple nodes (e.g., terminals and networks). Joint inference means that inference is performed collaboratively across multiple nodes; for example, the first part of the inference may be performed by the first node, and the remainder by the second node. Two-side models can be classified into various types as follows, depending on the training method of the AI / ML model.

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

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

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

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

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

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

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

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

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

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

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

[0230] THz communication

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

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

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

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

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

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

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

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

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

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

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

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

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

[0244] Integrated Sensing and Communication (ISAC)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0273] Currently, since UEs must wake up periodically during every DRX cycle, they cause power consumption even during periods without signal or data traffic. If UEs could wake up only when there is a specific trigger, such as paging, power consumption could be significantly reduced. To this end, the introduction of a Wake-up Signal (WUS) to wake up the Main Radio (MR) and a LP WUR, a separate receiver capable of monitoring the WUS with very low power consumption, is being discussed. For example, while the MR operates as a receiver for the existing Radio Relay (NR) during data / signal transmission and reception, for power saving purposes, the MR can be turned off or switched to a deep sleep state while the LP WUR is turned on.

[0274] LP-WUS / WUR applicable devices 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-supported devices such as XR / smart glasses and smartphones.

[0275] For the 3GPP standardization of LP-WUS / WUR, research on the following matters may be necessary.

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

[0277] - LP-WUR Receiver Structure Analysis (Power Consumption, Noise Figures, etc.)

[0278] - L1 Design and Procedure Changes and Link Performance Evaluation for LP-WUS Support

[0279] - Changes to the upper-layer protocol to support this

[0280] LP-WUS can have a structure that applies equally 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.

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

[0282] In RRC Idle / Inactive mode, if MR RRM measurements are sufficiently relaxed, UE power savings of over 90% compared to existing I-DRX (including with and without PEI applied). Compared to existing eDRX, paging latency 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).

[0283] For RRC IDLE / INACTIVE mode, it can be guaranteed that the same information is transmitted regardless of the LP-WUR type, and OFDM sequences can carry the information. Duty-cycle-based monitoring, such as periodic On / Off monitoring, can be supported.

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

[0285] In RRC IDLE / INACTIVE mode, LP-SS may be transmitted repeatedly with a period of Y ms (e.g., 320 ms for initial transmission) and may have OOK-1 / OOK-4 waveforms (OOK with or without OFDM sequence). If LP-WUR is capable of receiving existing PSS / SSS, it may be permitted to perform synchronization / RRM with PSS / SSS instead of LP-SS. To mitigate and offload RRM measurements in MR, UE MR RRM requirements may be further mitigated in serving / neighboring cell measurements, and conditions for offloading serving cell RRM measurements from MR to LP-WUR need to be defined.

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

[0287] In RRC Connected mode, power savings of more than 10% compared to existing power saving techniques can be achieved under various XR traffic / system overloads, and the impact on capacity may be minimal. For FTP / IM traffic, MR switches to deep sleep, enabling power savings of up to 60% and an improvement in UPT of up to 10%. Offloading serving cell RRM measurements from UE MR to LP-WUR can also be considered.

[0288] Regarding LP-WUS-based MR-PDCCH monitoring in RRC Connected mode, a procedure for enabling / disabling monitoring needs to be defined / configured. In RRC Connected mode, ultra-deep-sleep of the MR may not be supported, and RRM / RLM / BFD / CSI measurements can still be performed by the MR. LP-WUS / LP-SS coverage may be at a level similar to PUSCH Message 3.

[0289] [LP-WUS-based PDCCH Monitoring and CSI Reporting]

[0290] As previously described, 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, the receiver equipped in an existing NR standard terminal can be understood as MR. LP-WUR refers to a receiver that can be additionally configured in a terminal to receive low-power signals, and can receive newly designed low-power signals such as LP-WUS or LP-SS, and generally has the characteristic of being configured with low cost and low power consumption. As described above, LP WUS can be briefly referred to as WUS.

[0291] Low-power signals, such as LP-WUS or LP-SS, can be configured differently from signals transmitted using the current general OFDM symbol structure in the resource configuration of the time / frequency axes under NR standards. For example, LP-WUS is modulated using the OOK (On-Off Keying) method to align with the slot or symbol structure of the time axis, but it may be transmitted without aligning with or matching the unit resource (e.g., RE, subcarrier, or RB) structure of the frequency axis. For instance, LP-WUS is configured to indicate the presence of a signal (e.g., 1) or absence of a signal (e.g., 0) within a specific time interval, allowing the terminal to receive the WUS simply by detecting energy within that specific time interval. It may also be considered that a sequence for spectrum flattening or an OFDM sequence for increasing transmission coverage or transmitting additional information be overlaid on the OOK symbol of such LP-WUS.

[0292] Various candidates are being discussed regarding the architecture of the LP-WUR, and accordingly, the power consumption of the LP-WUR in the 'on' and 'off' states may vary. Consequently, if the power consumption of the LP-WUR in the 'on' state is large enough to be non-negligible, or for other reasons, the terminal may be required to activate or deactivate the LP-WUR. To this end, entry conditions for the terminal to enter the activated state of the LP-WUR and exit conditions for exiting the activated state can be defined.

[0293] The LP-WUS being directed may include a payload transmitted in the form of an OOK. Generally, the payload can be said to contain information actually directed to the terminal. In addition, 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 through the payload and the information transmitted through the overlaid OFDM sequence.

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

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

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

[0297] In the case of LP-WUR type #1, it is a wake-up receiver configured at low cost that can only determine whether there is a signal or not (energy detection or envelope detection). Therefore, it is a receiver that can only receive information transmitted through the OOK symbol, i.e., the payload.

[0298] 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 is a receiver capable of receiving not only the payload but also information transmitted through overlaid OFDM sequences. Additionally, depending on the implementation, it may be possible to receive PSS / SSS of existing NR signals.

[0299] Generally, PDCCH monitoring accounts for a large portion of the power consumption of a terminal in RRC_CONNECTED mode (hereinafter CONNECTED mode). Since the terminal monitors the PDCCH using MR, increasing the sleep time of MR can be effective for saving the terminal's power. To save the terminal's power, Rel-15 / 16 / 17 introduced a DRX operation that turns PDCCH monitoring on / off at regular intervals, a signal that can indicate whether to perform PDCCH monitoring during that period, and an adaptation operation that can adjust the frequency of PDCCH monitoring within the DRX Active Time. All of these operations were introduced for the purpose of reducing the time the terminal monitors the PDCCH and guaranteeing a sleep time during which MR does not operate, thereby allowing the terminal to reduce power consumption.

[0300] One can consider a method to reduce the frequency of PDCCH monitoring performed by the terminal's MR by utilizing the newly introduced LP-WUS / LP-WUR. The terminal's LP-WUR operates at relatively low power, resulting in lower power consumption compared to MR. Therefore, a terminal in CONNECTED mode can reduce power consumption by operating the MR in a (deep / light / micro) sleep state to avoid PDCCH monitoring. Furthermore, if the LP-WUS is received via the low-power LR and utilized to wake up the MR based on the corresponding instruction, it can be expected to be effective for power saving. Through this, the terminal can effectively maintain a longer sleep time for the MR, which consumes less power. Additionally, one can consider receiving other instructions via LP-WUS, such as an action to temporarily switch the MR to a sleep state, and operating the MR accordingly.

[0301] The terminal can receive LP-WUS and be instructed to start PDCCH monitoring. For example, the terminal receives LP-WUS by utilizing LP-WUR when MR is off or in a sleep state. By activating MR and performing PDCCH monitoring only when the correct LP-WUS is received, the terminal can reduce unnecessary PDCCH monitoring or lower the frequency of PDCCH monitoring, thereby expecting power saving effects.

[0302] The present disclosure proposes an operation in which a terminal receives an LP-WUS and is instructed to start PDCCH monitoring. The terminal may receive the LP-WUS and perform PDCCH monitoring based on a set period and / or based on dynamic instructions. When both the operation based on the set period and the operation based on dynamic instructions are set, a terminal operation is proposed.

[0303] The present disclosure proposes an operation in which a terminal in CONNECTED mode receives an LP-WUS and, based thereon, PDCCH monitoring is enabled. For example, the terminal receives an LP-WUS and, through it, may be instructed to control PDCCH monitoring (for one or more cells).

[0304] The operation in which a terminal receives LP-WUS and enables PDCCH monitoring can be implemented in various ways. An example of enabling PDCCH monitoring by LP-WUS for a terminal configured with C-DRX may include at least one of the following.

[0305] - Operation 1) The terminal may receive LP-WUS in a time interval prior to the start time of the periodically configured drx-onDurationTimer to receive instructions on whether to start the drx-onDurationTimer. (This may be an operation that replaces the DCP.) For reference, in 3GPP NR, the DCP is a DCI (e.g., a DCI with a scrambled CRC via PS-RNTI) used to signal paging / power saving control information to a specific group of UEs (or all UEs). The UE may perform instructions given by the DCP, such as changing PDCCH / PDSCH monitoring, switching to power saving mode, etc.

[0306] - Operation 2) The terminal may receive LP-WUS outside of the existing C-DRX active time to be instructed on a period for potential PDCCH monitoring. For example, LP-WUS reception and PDCCH monitoring according to Operation 2 may be set up / performed independently without being linked to DRX settings / active time settings.

[0307] Operation 1 can be understood as an operation in which LP-WUS replaces the function of DCP (e.g., wake-up indication) through the existing NR's MR. For example, instead of the existing DCI format 2_6 for DCP, the start of the periodically configured drx-onDurationTimer can be indicated via LP-WUS. The terminal reduces power consumption by keeping the MR in a sleep state during periods that are not potential DRX active time, and receives LP-WUS while operating as LP-WUR. Based on the reception of LP-WUS, the start of drx-onDurationTimer can be determined according to the configured DRX.

[0308] Operation 2 may be an operation that receives LP-WUS outside of the configured C-DRX active time (or regardless of the C-DRX active time) to receive additional potential PDCCH monitoring intervals. Since Operation 2 is a different operation from the existing method in which PDCCH monitoring is directed / executed in conjunction with the C-DRX active time, additional constraints that were not previously configured may be considered / configured.

[0309] For example, a terminal configured with Operation 2 may be expected to monitor the LP-WUS according to the configured period. Upon receiving the LP-WUS, the terminal may start a specific timer to enable the terminal to perform PDCCH monitoring. This configuration of Operation 2 may not affect operations related to existing DRX timers (excluding drx-onDurationTimer). RRM, RLM, and BFD measurement requirements related to existing DRX operations may be assumed. Regarding periodic CSI / L1-RSRP reporting, the terminal may be configured not to perform unless instructed to wake up, or to perform regardless of whether instructed to wake up. For a terminal configured with only Operation 2, PDCCH monitoring based on the existing C-DRX period and drx-onDurationTimer may not be triggered while monitoring the LP-WUS.

[0310] If both Operation 1 and Operation 2 are configured on the terminal, PDCCH monitoring is performed in accordance with the current standard in the existing configured C-DRX, and additional PDCCH monitoring may be instructed through LP-WUS in other sections.

[0311] Below, we propose a method for the operation of a terminal when both operation 1 and operation 2 are configured. Additionally, we propose a timer that is started by the LP-WUS when operation 2 is configured.

[0312] For convenience of explanation, the LP WUS for operation 1 may be represented as LP WUS1, and the LP WUS for operation 2 may be represented as LP WUS2. An LP WUS not limited to LP WUS1 / 2 may mean either LP WUS1 or LP WUS2, or may encompass both.

[0313] The distinction between the proposals below is for the sake of convenience of explanation and is not to be interpreted restrictively to the meaning that each proposal must be implemented in an independent form. Depending on the implementation, at least some of the multiple proposals may be implemented in a combined form, or each proposal may be implemented individually.

[0314] Proposal 1

[0315] According to one embodiment, an operation is proposed to start a timer so that the terminal performs PDCCH monitoring by receiving LP-WUS outside of the C-DRX active time.

[0316] A terminal configured with Operation 2 can receive LP-WUS2 and be instructed to perform PDCCH monitoring. Outside of the C-DRX active time, the terminal can receive LP-WUS2 and start a specific timer (e.g., a timer related to the DRX active time) to initiate PDCCH monitoring. As an example, the following three specific timers can be considered for starting upon receiving LP-WUS2.

[0317] (1) drx-onDurationTimer

[0318] When the existing DRX operation is configured, the terminal starts drx-onDurationTimer according to the periodic C-DRX to start PDCCH monitoring. For example, it can be said that the terminal starts drx-onDurationTimer at specific intervals (e.g., DRX cycle) to start the DRX active time.

[0319] For example, in the case of Operation 2, where PDCCH monitoring is initiated via an LP-WUS2 instruction outside of the existing C-DRX active time, it may be considered that the terminal operation is performed by starting the drx-onDurationTimer. For example, if the LP-WUS2 for Operation 2 is received, the terminal may not start the drx-onDurationTimer at the periodic start time of the drx-onDurationTimer given by the DRX configuration (e.g., the start time of the DRX cycle), but may start the drx-onDurationTimer (non-periodically) based on the time of reception of the LP-WUS2 for Operation 2. For convenience, the terminal's PDCCH monitoring indicated by the LP-WUS2 outside of the C-DRX active time, as in Operation 2, is referred to as potential (or dynamic) PDCCH monitoring.

[0320] Meanwhile, when drx-onDurationTimer starts, it is necessary to consider the operations that must be performed according to existing standards. It must be considered whether the CSI / L1-RSRP reporting operation performed during the DRX active time under existing standards and the operation 2, which performs PDCCH monitoring by receiving LP-WUS2 outside of the C-DRX active time, can be correlated.

[0321] Table 1 is an excerpt from Section 5.7 of the current NR standard document TS 38.321.

[0322] 5.7 Discontinuous Reception (DRX)1> if drx-onDurationTimer associated with the current DRX cycle is not started as specified in this clause:2> if, when evaluating all DRX Active Time conditions as specified in this clause, it is determined that the MAC entity would not be in Active Time even considering grants / assignments / DRX Command MAC CE / Long DRX Command MAC CE received and Scheduling Request sent until 4 ms prior to symbol n; and and]2> allowCSI-SRS-Tx-MulticastDRX-Active is not configured, or none of the active BWPs of the Serving Cell are configured with cfr-ConfigMulticast, or 5.When evaluating all DRX Active Time conditions specified in Clause 7b, if it is determined that not all multicast DRXs would be in Active Time even considering multicast assignments / DRX Command MAC CE for MBS multicast received until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in Clause 5.7b and all multicast sessions are configured with multicast DRX:[ if allowCSI-SRS-Tx-MulticastDRX-Active is not configured, or if cfr-ConfigMulticast is not configured for any of the active BWP(s) of the Serving Cell(s), or if all multicast DRXes would not be in Active Time considering multicast assignments / DRX Command MAC CE for MBS multicast received until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in Clause 5.7b and all multicast sessions are configured with multicast DRX:]3> do not transmit periodic SRS and semi-persistent SRS as defined in TS 38.214 [7] does not transmit periodic SRS and semi-persistent SRS defined in TS 38.214 [7];]3> Do not report semi-persistent CSI configured on PUSCH;[ not report semi-persistent CSI configured on PUSCH;]3> If ps-TransmitPeriodicL1-RSRP is not configured with value true:[ if ps-TransmitPeriodicL1-RSRP is not configured with value true:]4> Do not report periodic CSI that is L1-RSRP on PUCCH.[ not report periodic CSI that is not L1-RSRP on PUCCH.]3> If ps-TransmitOtherPeriodicCSI is not configured with value true:[ if ps-TransmitOtherPeriodicCSI is not configured with value true:]4> Do not report periodic CSI that is not L1-RSRP on PUCCH.

[0323] In Table 1, the ps-TransmitPeriodicL1-RSRP / ps-TransmitOtherPeriodicCSI parameters are used to determine whether periodic CSI / L1-RSRP reporting should be performed regardless of whether the DRX is active time. If the parameter is set to true, periodic CSI / L1-RSRP reporting is performed during the time interval of the configured drx-onDurationTimer (a potential operating interval that is not actually turned on) even if it is not the DRX active time.

[0324] According to the interpretation of the provisions in Table 1, a terminal that is in DRX active time after starting drx-onDurationTimer must perform periodic CSI / L1-RSRP reporting (if configured to perform the corresponding operation). In the existing periodic DRX operation, the terminal periodically performs PDCCH monitoring and reports channel conditions and signal reception quality to the base station, and the base station can be efficiently configured so that the terminal can smoothly receive the transmitted PDCCH. Alternatively, periodic CSI / L1-RSRP reporting may be performed regardless of whether the terminal wakes up during the time when drx-onDurationTimer is operating.

[0325] This reporting behavior of the terminal is performed at specific intervals within the operating period of drx-onDurationTimer, or within the period during which it is required to operate. In other words, if the terminal has started drx-onDurationTimer according to existing standards, it is configured to perform periodic CSI / L1-RSRP reporting. Therefore, periodic CSI / L1-RSRP reporting may need to be performed whenever a PDCCH monitoring period (potentially indicated by LP-WUS) is initiated by drx-onDurationTimer.

[0326] Since such Periodic CSI / L1-RSRP reporting is performed periodically according to the originally set DRX cycle, it may not be necessary to perform it every time for dynamic PDCCH monitoring directed by LP-WUS2.

[0327] Therefore, when drx-onDurationTimer is started by an LP-WUS directive, it is necessary to specify that periodic CSI / L1-RSRP reporting is always performed together, or to specify it as an exception behavior in existing standards (e.g., not performing CSI / L1-RSRP reporting). For example, in addition to the condition in Table 1, "if drx-onDurationTimer associated with the current DRX cycle is not started, do not perform CSI / L1-RSRP reporting," a condition such as "if drx-onDurationTimer is not started in relation to the periodic DRX active time, perform CSI / L1-RSRP reporting" can be added (if drx-onDurationTimer is started in relation to the periodic DRX active time, perform CSI / L1-RSRP reporting, and if drx-onDurationTimer is not started in relation to the periodic DRX active time, do not perform CSI / L1-RSRP reporting." For example, the case of performing periodic CSI / L1-RSRP reporting may be limited to when drx-onDurationTimer is started by an existing DRX operation or by operation 1, rather than when drx-onDurationTimer is started by LP-WUS2 for operation 2.

[0328] (2) drx-inactivityTimer

[0329] It is possible to consider that drx-inactivityTimer is started via the instructions of LP-WUS2. The drx-inactivityTimer in the current standard is a timer that starts when drx-onDurationTimer is running and the PDCCH instructs a new transmission of the UL or DL. For example, drx-inactivityTimer is a timer intended to finish receiving the scheduled data in full when the terminal receives a DCI scheduling a new transmission (i.e., when there is a new data transmission).

[0330] Non-periodic potential PDCCH monitoring outside of the existing C-DRX active time can be performed by starting drx-inactivityTimer. As with existing standards, the period during which drx-inactivityTimer is running is the DRX active time, and it can be distinguished from the periodic DRX by being started by a different timer.

[0331] However, even in the case of drx-inactivityTimer, it is not clearly defined whether CSI / L1-RSRP reporting should be performed, so a definition may be necessary. In general, DRX operations always start with drx-onDurationTimer first, followed by drx-inactivityTimer starting based on subsequent conditions. CSI / L1-RSRP reporting can also be performed during the period when drx-onDurationTimer has started and is running, and during the subsequent operation period of drx-inactivityTimer, it may or may not be performed (depending on the reporting period setting).

[0332] Since the current standard does not define a case where drx-inactivityTimer starts first without the start of drx-onDurationTimer, it may be necessary to additionally define whether CSI / L1-RSRP reporting should be performed when drx-inactivityTimer is started directly by LP-WUS2 (without the start of drx-onDurationTimer). In DRX operation according to the current standard, since drx-onDurationTimer starts and drx-inactivityTimer starts upon receiving a PDCCH indicating a new transmission, CSI / L1-RSRP reporting can be performed during the period when drx-onDurationTimer and drx-inactivityTimer are operating. Considering this, in one embodiment, CSI / L1-RSRP reporting can be restricted through the higher layer parameter CSI-mask so that CSI / L1-RSRP reporting is performed only during the operation period of drx-onDurationTimer.

[0333] Therefore, to initiate the dynamic PDCCH monitoring period directed by LP-WUS2 with drx-inactivityTimer, CSI / L1-RSRP reporting can be restricted to be performed only in drx-onDurationTimer. Alternatively, it can be defined so that CSI / L1-RSRP reporting is not performed during the drx-inactivityTimer operation period initiated by LP-WUS, rather than the PDCCH directing new transmission.

[0334] (3) new timer

[0335] A new timer different from the existing DRX timer can be defined. This new timer can be defined as a timer that starts dynamic PDCCH monitoring by LP-WUS2, rather than when the DRX operation according to the C-DRX cycle (e.g., the on-duration time starting with the WUS of Operation 1) begins. In other words, LP-WUS2 receiving outside the existing C-DRX active time triggers the start of the new timer, and the terminal can monitor the PDCCH during the period when the new timer is operating.

[0336] After the timer starts, if a PDCCH instructing a new transmission is received, the drx-inactivityTimer starts in the same way as the existing DRX operation, and the same timer may also start for other operations such as retransmission and HARQ. For example, it can be said that only the initial timer that starts the DRX active time starts with a new timer rather than the drx-onDurationTimer.

[0337] For example, this new timer can be included in the DRX configuration, and the length of the timer can be defined to be the same as or different from drx-onDurationTimer. As a timer to start the DRX, it can be the same length as drx-onDurationTimer. Alternatively, since it is PDCCH monitoring dynamically started by LP-WUS2, it can be expected that subsequent PDCCH transmissions will occur within a short period of time, and based on this, it can be defined / configured to have a shorter length than drx-onDurationTimer.

[0338] Since it is defined as a new timer, the existing CSI / L1-RSRP reporting behavior can also be defined differently.

[0339] 1) For example, Periodic CSI / L1-RSRP reporting may not be performed during the new timer operation period.

[0340] - Periodic CSI / L1-RSRP reporting can be performed within the existing C-DRX active time interval or within the original drx-onDurationTimer operating interval (even if the actual timer is not operating). The terminal performs the CSI / L1-RSRP reporting operation at regular intervals. Based on the periodic reporting, a PDCCH suitable for reception by the terminal can be transmitted. If additional channel condition reports are required, the base station may instruct the aperiodic CSI reporting operation within the new timer operating interval.

[0341] 2) As another example, Periodic CSI reporting can be performed during the new timer operation period.

[0342] - Periodic CSI reporting can be configured to be performed by the terminal during the new timer operation period. If a new timer is started upon receiving LP-WUS2, it can be expected that there will be scheduling thereafter, and CSI reporting can be defined to be performed for smoother transmission. For example, the terminal performs CSI reporting while starting the new timer, and the base station can transmit a PDCCH instructing a new transmission. In the case of L1-RSRP reporting, it may or may not be performed.

[0343] - Whether the actual operation of periodic CSI (and / or L1-RSRP) reporting is performed can be pre-configured / instructed to the terminal. Whether the terminal performs periodic CSI reporting and periodic L1-RSRP reporting within the operation period of the new timer through instructions from LP-WUS2 can be configured / instructed, respectively, via higher layer parameters.

[0344] The above definition of operation between CSI / L1-RSRP reporting and timers can be configured in the same way even when LP-WUS2, which receives outside the C-DRX active time interval, initiates PDCCH monitoring—an operation other than the existing DRX—using 1) drx-onDurationTimer and 2) drx-inactivityTimer. For example, periodic CSI / L1-RSRP reporting may not be performed or may be configured to be performed even within the operation interval of drx-onDurationTimer and drx-inactivityTimer, which initiate dynamic PDCCH monitoring initiated by LP-WUS2, and each report may be configured / instructed through higher layer parameters.

[0345] Referring again to Table 1, whether periodic L1-RSRP reporting and CSI reporting are performed when the terminal has not started the current DRX cycle via drx-onDurationTimer can be configured through the higher layer parameters ps-TransmitPeriodicL1-RSRP and ps-TransmitOtherPeriodicCSI, respectively. If ps-TransmitPeriodicL1-RSRP in Table 1 is true, the terminal can perform L1-RSRP reporting within the original drx-onDurationTimer operation period even without waking up. If ps-TransmitOtherPeriodicCSI in Table 1 is true, the terminal performs CSI reporting (not L1-RSRP) within the original drx-onDurationTimer operation period even without waking up.

[0346] When dynamic PDCCH monitoring directed by LP-WUS2 is initiated via drx-onDurationTimer, drx-inactivityTimer, or new timer, a correlation with the two parameters ps-TransmitPeriodicL1-RSRP and ps-TransmitOtherPeriodicCSI can be defined. Since the actions set by these parameters are related to periodic reporting within the periodic C-DRX operation period, even though the actual terminal does not wake up, periodic CSI / L1-RSRP reporting may not be performed regardless of these parameters during the dynamic PDCCH monitoring period (dynamic DRX active time) directed by LP-WUS2. Therefore, periodic CSI / L1-RSRP reporting within the dynamic PDCCH monitoring period directed by LP-WUS2 can be set / directed respectively through new parameter settings other than ps-TransmitPeriodicL1-RSRP and ps-TransmitOtherPeriodicCSI.

[0347] Proposal 2

[0348] According to one embodiment, an operation is proposed in which a terminal is configured such that both periodic C-DRX (e.g., operation 1) via LP-WUS1 and dynamic PDCCH monitoring (e.g., operation 2) via LP-WUS2 can be indicated, and the terminal receives LP-WUS1 indicating periodic C-DRX within a dynamic PDCCH monitoring interval.

[0349] The terminal may receive LP-WUS1 in a time interval prior to the start time of the periodically configured drx-onDurationTimer to be instructed on whether to start the drx-onDurationTimer (e.g., Operation 1), or receive LP-WUS2 outside the existing C-DRX active time to be instructed on a potential PDCCH monitoring interval (e.g., Operation 2). Operation 1 may replace the operation of the Rel-16 DCP, which instructs a wake-up via DCI format 2_6, through LP-WUS. The terminal may be configured for both Operation 1 and 2 to be instructed to wake up via LP-WUS1 for the periodic C-DRX, and to be instructed to wake up dynamically via LP-WUS2 even outside the C-DRX active time.

[0350] For a terminal configured with both of these actions, if the terminal instructs the wake-up of the MR (to perform PDCCH monitoring) via LP-WUS, the sleeping MR wakes up and starts the operation. In this case, it is generally assumed that the LR stops monitoring the LP-WUS unless there is a specific other purpose. If the MR wakes up for PDCCH monitoring, the LR may not perform LP-WUS monitoring. A terminal instructed for dynamic PDCCH monitoring may not need to monitor another LP-WUS instructing dynamic PDCCH monitoring within that interval. Therefore, for the monitoring occasions of LP-WUS2 instructing dynamic PDCCH monitoring, the terminal may not actually perform LP-WUS2 monitoring. For example, LP WUS2 monitoring for operation 2 may not be performed while the terminal is woken up and monitoring PDCCH based on LP-WUS for operation 1 and / or operation 2 (or due to another cause / event) (or while MR is in the On state).

[0351] However, instructions for periodic C-DRX can be expected to be received by monitoring LP-WUS1 via LR even within the PDCCH monitoring interval (DRX active time interval). In the case of existing Rel-16 DCPs, if a DCP monitoring occasion occurs within the DRX active time, the terminal does not monitor the DCP. However, in the proposals of the present disclosure that instruct PDCCH monitoring via LP-WUS, there is no need to refrain from performing monitoring when there is a monitoring occasion for LP-WUS1 (Operation 1) instructing periodic C-DRX within the DRX active time. For example, even while monitoring PDCCH via MR in the current DRX cycle, the terminal can determine in advance whether to start the DRX on duration timer in the next DRX cycle by monitoring LP-WUS1 for Operation 1. In the case of existing Rel-16, PDCCH monitoring is performed with only one MR, monitoring DCI format 2_6 and general scheduling DCIs. Therefore, it can be configured to monitor DCI format 2_6 only outside of DRX active time and not monitor it inside DRX active time. However, in the case of LP-WUS, monitoring is performed with different receivers for MR and LR, and the operation of MR monitoring PDCCH and the operation of LR monitoring LP-WUS can be independent.

[0352] FIG. 14 is a diagram illustrating LP WUS monitoring and Wake-up indication when both WUS-related operation 1 and operation 2 are configured according to one embodiment. Specifically, the terminal operation illustrated in FIG. 14 includes an operation for LP-WUS1 monitoring in which a terminal that has been instructed to dynamic PDCCH monitoring through LP-WUS2 can instruct the start of drx-onDurationTimer based on the C-DRX cycle.

[0353] Referring to Fig. 14, LP-WUS1 on the monitoring occasion (M1) from the left indicates the start of drx-onDurationTimer based on a periodic C-DRX cycle, which can be said to mean that LP-WUS replaces the role of DCP. Subsequently, there are monitoring occasions (M2, M3) of LP-WUS2 for operation 2, but since they are within the MR's DRX active time, the terminal does not actually perform monitoring of LP-WUS2 via LR. Actual LP-WUS2 monitoring does not occur during the shaded monitoring occasions, such as monitoring occasions (M2, M3, M7). Subsequently, during the LP-WUS2 monitoring occasions (M4, M5, M6), the terminal actually performs LP-WUS2 monitoring.

[0354] Meanwhile, the dotted arrow indicates that there was no wake-up indication for MR because LP-WUS was not detected.

[0355] When a wake-up indication is given during the LP-WUS2 monitoring occasion (M6), the terminal's MR starts dynamic PDCCH monitoring based on the LP-WUS2. Dynamic PDCCH monitoring can be performed based on the drx-onDurationTimer, drx-inactivityTimer, or new timer of Proposal 1. At this time, since the LP-WUS2 monitoring occasion (M7) falls within the DRX active time, LP-WUS2 monitoring is not actually performed. However, on the LP-WUS1 monitoring occasion (M8), the terminal can perform LP WUS 1 monitoring to explicitly receive instructions for the next periodic C-DRX.

[0356] In this way, even if MR is monitoring PDCCH, the terminal can monitor LP-WUS 1 using LR and receive instructions regarding it.

[0357] For example, even if the terminal is monitoring the PDCCH via MR (even if it is the DRX active time), it can always monitor and receive LP-WUS1 (LP-WUS replacing the Rel-16 DCP) which indicates the subsequent periodic DRX active time (of Operation 1). If the terminal fails to receive LP-WUS1, how it operates for the next C-DRX cycle can be determined by following the existing higher layer parameter ps-WakeUp setting or through a new parameter setting similar to it. If the new parameter (or ps-WakeUp) is true, the subsequent periodic DRX active time (drx-onDurationTimer) is started even if the terminal has not fully received LP-WUS1, and if the new parameter (or ps-WakeUp) is absent, the subsequent periodic DRX active time (drx-onDurationTimer) is not started if the terminal has not fully received LP-WUS.

[0358] For this proposed method, it may be considered that the monitoring occasions of LP-WUS1, which directs periodic C-DRX, and LP-WUS2, which directs dynamic PDCCH monitoring, are set separately. Each monitoring occasion can be set separately.

[0359] Alternatively, the LP-WUS period and monitoring symbol can be configured through a single setting (e.g., through the LP-WUS 1 / 2 common setting), and LP-WUS 1 / 2 can be distinguished through the monitoring window. For example, an LP-WUS received within the monitoring window may be LP-WUS1 indicating periodic C-DRX, while an LP-WUS received outside the monitoring window may be LP-WUS2 indicating dynamic PDCCH monitoring. For instance, among the WUS monitoring occasions configured through the LP-WUS 1 / 2 common setting, WUS monitoring occasions belonging to the monitoring window can be configured / determined / defined as monitoring occasions for LP WUS 1, and WUS monitoring occasions not belonging to the monitoring window can be configured / determined / defined as monitoring occasions for LP WUS 2. Conversely, WUS monitoring occasions belonging to the monitoring window may become monitoring occasions for LP WUS 2, while the rest may become monitoring occasions for LP WUS 1.

[0360] For example, the monitoring window is associated with a periodic C-DRX, and the interval may be set prior to the start of drx-onDurationTimer at the same or longer interval, but is not limited thereto.

[0361] The proposed method has the advantage of reducing the overhead of signaling for WUS MO settings compared to the case where WUS MO1 (monitoring occasion) settings for operation 1 and WUS MO2 settings for operation 2 are each performed as separate signaling.

[0362] In addition, the proposed method has the advantage of resolving the ambiguity problem (e.g., whether the MO monitors LP WUS1 or LP WUS2) that occurs when WUS MO1 for operation 1 and WUS MO2 for operation 2 are each individually configured with separate signaling.

[0363] In addition, the proposed method has the advantage of being able to adjust the monitoring ratio between LP WUS1 and LP WUS2 and the monitoring positions of the two WUSs at once by setting / changing the position / size of the window while the WUS MOs are configured / arranged.

[0364] In addition, the existing DCP method had a limitation that Wake up indication had to be performed only relative to the DRX cycle position, but the proposed method has the advantage of being able to alleviate this limitation by setting / changing the window (independently of the DRX cycle).

[0365] Proposal 3

[0366] According to one embodiment, a terminal operation that receives LP-WUS and performs PDCCH monitoring is proposed.

[0367] If a terminal configured with DRX is configured with LP-WUS, PDCCH monitoring in the existing C-DRX cycle can be determined by whether operation 1, which instructs periodic C-DRX wake-up through LP-WUS1, is configured.

[0368] (1) Case 1: Configure to allow both periodic C-DRX via LP-WUS1 and dynamic PDCCH monitoring via LP-WUS2 to be indicated.

[0369] As described in Proposal 2 above, the respective monitoring occasions for LP-WUS1 / 2, which instruct periodic C-DRX and dynamic PDCCH monitoring, can be configured to be distinct. LP-WUS2, which instructs dynamic PDCCH monitoring, does not monitor when the terminal is currently in MR operation (PDCCH monitoring), but can monitor when MR is not in operation. LP-WUS1, which instructs the wake-up of periodic C-DRX, can always monitor regardless of whether MR is in operation.

[0370] Meanwhile, some operations that are supposed to be performed during the DRX active time according to existing standards may not be performed during the PDCCH monitoring period directed by LP-WUS. For example, if CSI reporting (and / or L1-RSRP reporting) is configured or directed to be performed during the (dynamic) PDCCH monitoring period directed by LP-WUS, and that period overlaps with the periodic C-DRX period (drx-onDurationTimer operation period), the periodic CSI reporting (and / or L1-RSRP reporting) may be omitted (since it has already been performed, there is no need to repeat it).

[0371] (2) Case 2: Configure to allow only dynamic PDCCH monitoring via LP-WUS2.

[0372] CSI / L1-RSRP during periodic C-DRX intervals can be performed within the original operating interval of drx-onDurationTimer, just as before. PDCCH monitoring is not performed by the terminal unless otherwise instructed by LP-WUS. LP-WUS1, which instructs the wake-up of periodic C-DRX, instructs the start of drx-onDurationTimer, where PDCCH monitoring is not performed.

[0373] If the terminal is configured with LP-WUS1 / 2 capable of transmitting periodic C-DRX instructions and dynamic PDCCH monitoring instructions, it may consider dynamically instructing operations in the existing DRX.

[0374] Through the DCI received during the previous DRX active time, you can instruct whether to perform PDCCH monitoring and CSI / L1-RSRP reporting operations during the next DRX active time (periodic C-DRX). When starting the next periodic drx-onDurationTimer, the DCI can instruct to perform only PDCCH monitoring, only CSI / L1-RSRP reporting, or both.

[0375] Alternatively, LP-WUS can be used to instruct whether to perform PDCCH monitoring and CSI / L1-RSRP reporting operations. When starting drx-onDurationTimer based on LP-WUS1 which instructs periodic wake-up of C-DRX, the terminal can be instructed to perform only PDCCH monitoring, only CSI / L1-RSRP reporting, or both.

[0376] Proposal 4

[0377] According to one embodiment, a method for setting LP-WUS monitoring occasions (distinguished by terminal operation) is proposed.

[0378] As in Proposal 2, regarding the start of the periodic C-DRX Active Time and the start of dynamic PDCCH monitoring, it may be considered that the monitoring occasions of LP-WUS1 / 2 capable of indicating these events are set identically or separately. Operation 1 may include the start of the periodic C-DRX Active Time (start of drx-onDurationTimer), and Operation 2 may include the start of dynamic PDCCH monitoring (start of new timer). The MO of LP-WUS1 indicating Operation 1 is referred to as LMO 1, and the MO of LP-WU2S indicating Operation 2 is referred to as LMO 2 for explanation.

[0379] (1) LP-WUS MO is determined by a single setting (e.g., period, offset, symbols, etc.), and the indicated operation can be distinguished according to the monitoring window.

[0380] The frequency band received by the terminal's LP-WUR is located in a specific area within a single BWP (or cell) and can receive the LP-WUS. At that location, the LP-WUR can periodically monitor the LP-WUS, and the base station can transmit a wake-up instruction if one is received. Therefore, the terminal's LP-WUR receives a configuration for an LP-WUS MO consisting of a period, monitoring symbol, offset, etc., and monitors the LP-WUS based on this. At this time, a parameter such as a specific offset (e.g., lpwus_offset) is set and can be configured for a symbol / slot that is time-advancing from the start point of the periodic drx-onDurationTimer. Through this, a kind of monitoring window can be established for a certain number of symbols / slots that are time-advancing from the start point of the drx-onDurationTimer. The terminal can distinguish the operation of instructions that can be received through the LP-WUS based on whether the occasion of the LP-WUS being monitored based on the same settings belongs to a symbol / slot that is preceded by a specific offset from the start point of drx-onDurationTimer (in other words, whether the LP-WUS MO is located within the monitoring window). The terminal can determine that the LP-WUS MO outside the monitoring window is LMO 2 and expect that the LP-WUS received at that location will instruct operation 2. The terminal can determine that the LP-WUS inside the monitoring window is LMO 1 and expect that the LP-WUS received at that location will instruct operation 1.

[0381] (2) LMO 1 and LMO 2 can be set separately with each setting, and the actions indicated by each LMO can be distinguished.

[0382] LP-WUS MO can be configured separately for each operation. LMO 1, which can indicate Operation 1, can be configured for a slot / symbol preceding the start time of the periodic drx-onDurationTimer. For example, LMO 1 can be configured to be the same as the period of the configured legacy C-DRX Active Time and can be set to repeat for a certain number of slots / symbols. That is, it can be configured to monitor LP-WUS1 on a specific symbol for a certain number of slots preceding the start time of the drx-onDurationTimer.

[0383] LMO 2, capable of instructing Operation 2, can be configured without being restricted by the period of the legacy DRX Active Time. However, considering the general power saving gain, it may be desirable to set it to be smaller than the period of the long DRX cycle. The terminal can receive instructions for a separate operation through a separate LP-WUS2 MO.

[0384] Each of Operation 1 and Operation 2 may be configured simultaneously or independently. Operation 2 relates to PDCCH monitoring dynamically directed by LP-WUS2, and Operation 1 may be directed to LP-WUS1 regarding whether to start the periodic drx-onDurationTimer. Considering that LP-WUS1 replaces the DCP in the existing standard, Operation 1 can reliably inform the terminal of whether to start the periodic drx-onDurationTimer by transmitting the signal to LP-WUS1, ensuring that the terminal does not misreceive or miss the signal. In the periodic C-DRX cycle, the start time and period of the drx-onDurationTimer are fixed, and the base station directs whether to start it via LP-WUS1 or the DCP. In standards up to Rel-18, the monitoring occasion of the DCP corresponds to the DCI that can be verified via the ps-RNTI receivable within the monitoring window. The terminal can determine the start time for starting DCP monitoring through a parameter called ps-offset, and can continue monitoring DCP within that interval (excluding the minimum time gap required to prepare PDCCH monitoring), and does not expect subsequent DCI reception once it receives a complete DCI format 2_6. In other words, it can receive instructions for the start of drx-onDurationTimer, which has a fixed time point, at multiple monitoring occasions.

[0385] It can be considered that such terminal operation also applies to operation 1, where LP-WUS1 replaces the DCP. Whether or not a monitoring window for LP-WUS is set on the terminal, it is expected to receive a start instruction for drx-onDurationTimer at a given point in time from multiple LP-WUS MOs. Accordingly, the terminal monitors LP-WUS1 for LMO 1 defined for multiple slots preceding the drx-onDurationTimer at a fixed start time. The terminal is expected to receive LP-WUS1 instructing whether to start the next drx-onDurationTimer, and is not expected to receive multiple LP-WUSs instructing other operations. The terminal monitors multiple LP-WUSs in chronological order before the start time of drx-onDurationTimer (considering the minimum time gap), and upon receiving LP-WUS1 that indicates the start of drx-onDurationTimer, it can terminate LP-WUS monitoring without expecting LP-WUSs with different instructions from subsequent LP-WUS MOs. Through this structure in which multiple LP-WUS MOs indicate a single start time, even if an LP-WUS is missing or fully received, or if the LP-WUS cannot be monitored at all due to other operations of the terminal, it can be expected that other LP-WUS MOs can monitor the LP-WUS and receive instructions through them.

[0386] Therefore, Operation 1 and Operation 2 can be distinguished into a form where the start time of PDCCH monitoring is fixed and multiple LP-WUSs can instruct it (start of drx-onDurationTimer) and a form where a single LP-WUS can instruct the start time of a single PDCCH monitoring (start of new timer). Thus, generally, PDCCH monitoring instruction through Operation 1 can be considered more robust, and PDCCH monitoring through Operation 2 can be considered more dynamic.

[0387] When Operation 1 and Operation 2 are simultaneously configured on a terminal, the terminal can distinguish between Operation 1, which is robust enough to receive complete instructions, and Operation 2, which can have lower power saving gain and latency through dynamic instructions. Therefore, even if the LP-WUS2 of Operation 2 is not fully received (for one or multiple LP-WUS MOs), the terminal can expect to receive instructions for Operation 1 because Operation 1 is configured. If the LP-WUS1 reception quality is poor even for Operation 1, the terminal can be configured to stop receiving LP-WUS and fallback to an operation utilizing MR.

[0388] Meanwhile, the following may apply in relation to the above proposals 1, 2 and / or 3.

[0389] As described above, LP SS and LP WUS may be introduced into the NR standard to support LP WUR, and LP WUS may be briefly referred to as WUS.

[0390] - LP SS (Low Power Synchronization Signal): Transmitted in the On / Off Keying (OOK) manner over consecutive symbols within a slot, and the EPRE for the SSB, the first RB position, the 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 in a quasi-co-location (QCL) relationship.

[0391] - WUS (Wake Up Signal): It uses the same OOK structure, but WUS Monitoring Occasions (MOs) are defined within a single WUS occasion, and a WUS occasion can be associated with a paging occasion. The cycle of a WUS occasion can be the same as the DRX cycle in the IDLE / INACTIVE state. UEs can only monitor slots / symbols specified by the bitmap (WUS_available_slot / symbol). When the WUS detects a UE dedicated codepoint, it enables Type 2 PDCCH CSS to receive paging messages.

[0392] LPSS / WUS parameters may be provided for the RRC_IDLE / INACTIVE state. For UEs in the RRC_CONNECTED state, the start position of WUS MO monitoring may be determined based on drx onDurationTimer or wus PDCCHMonitoringTimer according to the configuration options. 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.

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

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

[0395] FIG. 15 is a diagram illustrating the operation of a terminal and a network according to one embodiment. Since FIG. 15 is an example of an implementation of at least some of the proposals described above, the proposals described above may be referenced without further separate mention.

[0396] Referring to FIG. 15, the base station may receive a UE capability report from the terminal. The UE capability report may include information about the WUR / WUS supported by the terminal.

[0397] The base station may provide at least one upper layer signaling to the terminal (A10). The upper layer signaling may include various configuration information. The configuration information may include configuration information for the WUS. The configuration information for the WUS may include information for WUS MOs for WUS monitoring. The configuration information may include configuration information for the DRX.

[0398] The base station can transmit a WUS corresponding to at least one of the first WUS or the second WUS to the terminal (A20).

[0399] The terminal can monitor the WUS based on the WUS MOs (A15). The WUS may include at least one of the first WUS or the second WUS. The first WUS may trigger the start of the first timer, and the second WUS may trigger the start of the second timer. The first timer may be the DRX on-duration timer of the DRX setting. The second timer may be a timer configured independently of the DRX setting. Among the WUS MOs, the WUS MOs belonging to a specific window may be set as the first WUS MOs for the first WUS, and the remaining WUS MOs may be set as the second WUS MOs for the second WUS.

[0400] The terminal can monitor the PDCCH via MR based on WUS reception (A20). The base station can transmit the PDCCH to the terminal (A30).

[0401] FIG. 16 illustrates the flow of a method performed by a terminal according to one embodiment. Since FIG. 16 is an example of an implementation of at least some of the proposals described above, the proposals described above may be referenced without further separate mention.

[0402] Referring to FIG. 16, the terminal can receive WUS (wake-up signal) settings and DRX (discontinuous reception) settings through upper layer signaling (B05).

[0403] The terminal can monitor at least one of the first WUS associated with the start of the first timer or the second WUS associated with the start of the second timer based on the WUS setting (B10). The first timer may be the DRX on-duration timer of the DRX setting.

[0404] The above WUS settings may include information regarding WUS MOs (monitoring occasions). Among the above WUS MOs, WUS MOs belonging to a specific window may be set as first WUS MOs for the first WUS, and the remaining WUS MOs may be set as second WUS MOs for the second WUS.

[0405] The second timer above may be a timer configured independently of the DRX setting.

[0406] During a specific time when at least one of the first timer or the second timer is driven, the terminal can monitor the PDCCH (physical downlink control channel). The terminal can monitor the first WUS on one or more first WUS MOs included within the specific time.

[0407] The above terminal may omit monitoring of the second WUS on one or more second WUS MOs included within the above specific time.

[0408] The above WUS settings may include information regarding the specific window.

[0409] The above specific window can be set based on the DRX cycle of the above DRX setting.

[0410] The above specific window may be located before the start time of the above DRX cycle.

[0411] The terminal may omit at least one of periodic CSI (channel state information) reporting or periodic L1-RSRP (layer-reference signal received power) reporting during the time the second timer is operating.

[0412] The terminal can perform at least one of the periodic CSI report or the periodic L1-RSRP report within the time during which the first timer is driven.

[0413] The first WUS and the second WUS can be monitored by the LP WUR (low power wake up receiver) of the terminal.

[0414] FIG. 17 illustrates the flow of a method performed by a base station according to one embodiment. Since FIG. 17 is an example of an implementation of at least some of the proposals described above, the proposals described above may be referenced without further separate mention.

[0415] Referring to FIG. 17, the base station can transmit WUS (wake-up signal) settings and DRX (discontinuous reception) settings through upper layer signaling (C05).

[0416] Based on the above WUS settings, the base station may transmit at least one of a first WUS associated with the start of a first timer or a second WUS associated with the start of a second timer (C10).

[0417] The first timer above may be the DRX on-duration timer of the DRX setting above.

[0418] The above WUS settings may include information regarding WUS MOs (monitoring occasions). Among the above WUS MOs, WUS MOs belonging to a specific window may be set as first WUS MOs for the first WUS, and the remaining WUS MOs may be set as second WUS MOs for the second WUS.

[0419] The second timer above may be a timer configured independently of the DRX setting.

[0420] During a specific time when at least one of the first timer or the second timer is in operation, the base station may transmit a PDCCH (physical downlink control channel) to the terminal. The base station may transmit the second WUS on one or more first WUS MOs included within the specific time.

[0421] The base station may omit the transmission of the second WUS on one or more second WUS MOs included within the specific time.

[0422] The above WUS settings may include information regarding the specific window.

[0423] The above specific window can be set based on the DRX cycle of the above DRX setting.

[0424] The above specific window may be located before the start time of the above DRX cycle.

[0425] The base station may not receive at least one of periodic CSI (channel state information) reports or periodic L1-RSRP (layer-reference signal received power) reports during the time the second timer is operating.

[0426] The base station can receive at least one of the periodic CSI report or the periodic L1-RSRP report within the time during which the first timer is driven.

[0427] The above first WUS and the above second WUS may be related to the terminal's LP WUR (low power wake up receiver).

[0428] The embodiments described above are combinations of the components and features of the present disclosure in a specific form. Each component or feature should be considered optional unless otherwise explicitly stated. Each component or feature may be implemented in a form not combined with other components or features. Additionally, it is possible to construct embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment, or may be replaced with corresponding components or features of another embodiment. It is obvious that embodiments may be constructed by combining claims that are not explicitly related in the claims, or that they may be included as new claims by amendment after filing.

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

[0430] 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 WUS (wake-up signal) settings and DRX (discontinuous reception) settings through upper layer signaling; and Based on the above WUS settings, it includes monitoring at least one of a first WUS associated with the start of a first timer or a second WUS associated with the start of a second timer. The first timer above is the DRX on-duration timer of the DRX setting, and The above WUS configuration includes information regarding WUS MO (monitoring occasions), and A method in which WUS MOs belonging to a specific window among the above WUS MOs are set as first WUS MOs for the first WUS, and the remaining WUS MOs are set as second WUS MOs for the second WUS.

2. In Paragraph 1, A method in which the second timer is a timer configured independently of the DRX setting.

3. In Paragraph 1, During a specific time when at least one of the first timer or the second timer is in operation, the terminal monitors the PDCCH (physical downlink control channel), and A method in which the terminal monitors the first WUS on one or more first WUS MOs included within the specific time.

4. In Paragraph 3, A method in which the terminal omits monitoring of the second WUS on one or more second WUS MOs included within the specific time.

5. In Paragraph 1, A method in which the above WUS settings include information about the above specific window.

6. In Paragraph 1, A method in which the above specific window is configured based on the DRX cycle of the above DRX setting.

7. In Paragraph 6, A method in which the specific window above is located before the start time of the DRX cycle.

8. In Paragraph 1, A method in which the terminal omits at least one of periodic CSI (channel state information) reporting or periodic L1-RSRP (layer-reference signal received power) reporting during the time in which the second timer is driven.

9. In Paragraph 1, A method in which the terminal performs at least one of the periodic CSI report or the periodic L1-RSRP report within the time during which the first timer is driven.

10. In Paragraph 1, A method in which the first WUS and the second WUS are monitored by the LP WUR (low power wake up receiver) of the terminal.

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

12. Regarding the device, At least one processor; and It includes at least one memory configured to store instructions that cause the at least one processor to perform operations by being executed by the at least one processor, and The operations of the above processor are, Receive WUS (wake-up signal) settings and DRX (discontinuous reception) settings through upper layer signaling; and Based on the above WUS settings, it includes monitoring at least one of a first WUS associated with the start of a first timer or a second WUS associated with the start of a second timer. The first timer above is the DRX on-duration timer of the DRX setting, and The above WUS configuration includes information regarding WUS MO (monitoring occasions), and A device in which WUS MOs belonging to a specific window among the above WUS MOs are set as first WUS MOs for the first WUS, and the remaining WUS MOs are set as second WUS MOs for the second WUS.

13. In Paragraph 12, The above device is a device that is a terminal including a transceiver or a processing device configured to control the terminal.

14. In a method performed by a base station, Transmit WUS (wake-up signal) settings and DRX (discontinuous reception) settings through upper-layer signaling; and Based on the above WUS settings, it includes transmitting at least one of a first WUS associated with the start of a first timer or a second WUS associated with the start of a second timer. The first timer above is the DRX on-duration timer of the DRX setting, and The above WUS configuration includes information regarding WUS MO (monitoring occasions), and A method in which WUS MOs belonging to a specific window among the above WUS MOs are set as first WUS MOs for the first WUS, and the remaining WUS MOs are set as second WUS MOs for the second WUS.

15. Regarding base stations, At least one processor; and It includes at least one memory configured to store instructions that cause the at least one processor to perform operations by being executed by the at least one processor, and The operations of the above processor are, Transmit WUS (wake-up signal) settings and DRX (discontinuous reception) settings through upper-layer signaling; and Based on the above WUS settings, it includes transmitting at least one of a first WUS associated with the start of a first timer or a second WUS associated with the start of a second timer. The first timer above is the DRX on-duration timer of the DRX setting, and The above WUS configuration includes information regarding WUS MO (monitoring occasions), and A base station in which WUS MOs belonging to a specific window among the above WUS MOs are set as first WUS MOs for the first WUS, and the remaining WUS MOs are set as second WUS MOs for the second WUS.

Images