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

Abstract

A user equipment (UE) according to an embodiment of the present disclosure may receive, from a base station (BS), configuration information related to at least one synchronization signal block (SSB) for at least one transmission and reception point (TRP) among a plurality of TRPs, and monitor the at least one SSB for the at least one TRP on the basis that the configuration information is related to activation of the at least one SSB.

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 performing wireless communication 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] 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 such purpose. According to one embodiment, a method for activating / deactivating an SSB (synchronization signal block) considering a plurality of TRPs (Transmission and Reception Points) may be provided. Additionally, according to one embodiment, a method for activating / deactivating an RO (RACH occasion) considering a plurality of TRPs may be provided.

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

[0005] According to one aspect of the present disclosure, a method performed by a UE may include: receiving configuration information from a BS (Base station) regarding at least one SSB (synchronization signal block) for at least one TRP (Transmission and Reception Point) among a plurality of TRPs; and monitoring the at least one SSB for the at least one TRP based on the configuration information being related to the activation of the at least one SSB.

[0006] Preferably, the method may include a step of stopping monitoring of the at least one SSB for the at least one TRP based on the fact that the setting information relates to the deactivation of the at least one SSB.

[0007] Preferably, the step of monitoring the at least one SSB for the at least one TRP may include the step of monitoring the at least one SSB for the at least one TRP at the earliest SSB time (occasion) after the offset from the time of receiving the configuration information associated with the at least one SSB.

[0008] Preferably, based on the setting information being related to the activation of the at least one SSB, at least one RO associated with the at least one SSB is determined to be valid, and based on the setting information being related to the deactivation of the at least one SSB, at least one RO associated with the at least one SSB may be determined to be invalid.

[0009] In this case, the method may further include the step of transmitting a PRACH (Physical Random Access Channel) to the BS based on at least one RO (RACH occasion) determined to be valid, and may further include the step of receiving information regarding at least one RO associated with the at least one SSB.

[0010] Preferably, configuration information related to at least one SSB for at least one TRP may include information related to the activation or deactivation of at least one RO associated with said at least one SSB.

[0011] Preferably, the configuration information associated with the at least one SSB may include at least one of a PCI (Physical Cell Identifier) ​​associated with the at least one TRP, carrier information associated with the at least one TRP, BWP (bandwidth part) information associated with the at least one TRP, or a CORESET (Control Resource Set) pool index associated with the at least one TRP.

[0012] Preferably, the at least one SSB includes an OD (on-demand) SSB, and configuration information associated with the at least one SSB can be received based on at least one of RRC (radio resource control) signaling, MAC (medium access control) CE (control element) signaling, or DCI (Downlink Control Information).

[0013] Preferably, configuration information related to at least one SSB for at least one TRP may be received based on a CORESET (Control Resource Set) pool related to the PCI (Physical Cell Identifier) ​​of at least one TRP or an RNTI (Radio Network Temporary Identifier) ​​related to the PCI of at least one TRP.

[0014] Preferably, configuration information related to at least one SSB for at least one TRP is included in information for activating or deactivating the at least one TRP, and the information for activating or deactivating the at least one TRP can be received based on at least one of RRC (radio resource control) signaling, MAC (medium access control) CE (control element) signaling, or DCI (Downlink Control Information).

[0015] Preferably, the step of monitoring the at least one SSB for the at least one TRP may include the step of monitoring the SSBs for each of the plurality of TRPs based on the setting information being related to the activation of the at least one SSB.

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

[0017] 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 are executed by the at least one processor to perform operations, wherein the operations may include: receiving configuration information from a BS (Base station) regarding at least one SSB (synchronization signal block) for at least one TRP among a plurality of TRPs; and monitoring the at least one SSB for the at least one TRP based on the configuration information being related to the activation of the at least one SSB.

[0018] The above device may further include a transmitter and receiver.

[0019] The above device may be a UE (User Equipment).

[0020] The above device may be a processing device configured to control a terminal.

[0021] According to another aspect of the present disclosure, a method performed by a BS (Base Station) may include the step of transmitting configuration information related to at least one SSB (synchronization signal block) for at least one TRP (Transmission and Reception Point) among a plurality of TRPs to a UE (User Equipment); and the step of transmitting the at least one SSB for the at least one TRP to the UE based on the configuration information being related to the activation of the at least one SSB.

[0022] A Base Station (BS) according to another aspect of the present disclosure comprises at least one processor; and at least one memory configured to store instructions that are executed by the at least one processor to perform operations, wherein the operations may include the step of transmitting configuration information related to at least one synchronization signal block (SSB) for at least one Transmission and Reception Point (TRP) among a plurality of Transmission and Reception Points (TRP) to a User Equipment (UE); and the step of transmitting the at least one SSB for the at least one TRP to the UE based on the configuration information being related to the activation of the at least one SSB.

[0023] According to the present disclosure, signal transmission and reception can be performed efficiently in a wireless communication system. According to one embodiment, by providing a method for enabling / disabling an SSB and a method for enabling / disabling an RO considering a plurality of TRPs, a base station can efficiently control whether to transmit a Type 2 SSB and whether to receive a Cat 2 RO by considering the TRP situation.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0040] Figure 16 illustrates an example of a Conditional Handover (CHO) procedure.

[0041] Figure 17 illustrates an example of on-demand SSB transmission.

[0042] FIG. 18 is a diagram illustrating the timing for performing SSB adaptation per TRP according to the present disclosure.

[0043] FIG. 19 is a diagram illustrating the operation of UE and BS for SSB adaptation per TRP according to one embodiment.

[0044] FIG. 20 illustrates the flow of a method performed by a UE for SSB adaptation per TRP according to one embodiment.

[0045] FIG. 21 illustrates the flow of a method performed by BS for SSB adaptation per TRP according to one embodiment.

[0046] FIG. 22 is a diagram illustrating the timing for performing RACH adaptation per TRP according to the present disclosure.

[0047] FIG. 23 is a diagram illustrating the operation of UE and BS for RACH adaptation per TRP according to one embodiment.

[0048] FIG. 24 illustrates the flow of a method performed by a UE for RACH adaptation per TRP according to one embodiment.

[0049] FIG. 25 illustrates the flow of a method performed by BS for RACH adaptation per TRP according to one embodiment.

[0050] 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."

[0051] 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."

[0052] 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."

[0053] 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."

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

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

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

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

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

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

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

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

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

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

[0064] <Symbols, Abbreviations, Terms>

[0065] - PDCCH: Physical Downlink Control CHannel

[0066] - DCI: Downlink Control Information

[0067] - PDSCH: Physical Downlink Shared CHannel

[0068] - PUSCH: Physical Uplink Shared CHannel

[0069] - CSI: Channel state information

[0070] - RRM: Radio resource management

[0071] - SCS: Sub-carrier spacing

[0072] - RLM: Radio link monitoring

[0073] - DCI: Downlink Control Information

[0074] - CAP: Channel Access Procedure

[0075] - Ucell: Unlicensed cell

[0076] - TBS: Transport Block Size

[0077] - TDRA: Time Domain Resource Allocation

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

[0079] - BWP: Bandwidth Part (It can be composed of consecutive resource blocks (RBs) on the frequency axis and can 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).)

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

[0081] - REG: Resource element group

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

[0083] - COT: Channel occupancy time

[0084] - SPS: Semi-persistent scheduling

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

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

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

[0088] - TRP: Transmission and Reception Point

[0089] - TAG: Timing advance group

[0090] - AmIoT: Ambient Internet of Things

[0091] - CW: Carrier Wave

[0092] - BSC: Backscattering

[0093] - BSS: Backscattered signal

[0094] - SIC: Self-Interference Cancellation

[0095] - RFID: Radio Frequency Identifier

[0096] - IN: Intermediate Node

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

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

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

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

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

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

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

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

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

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

[0107] 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 the transmission / reception of a wireless signal, a process for various signal processing (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), a resource allocation process, etc.

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

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

[0110] 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 an RF (radio frequency) unit. In this disclosure, a wireless device may mean a communication modem / circuit / chip.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0127] The terminal (110) can obtain system information transmitted from the base station (120) (403). 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.

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

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

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

[0131] 6G System Core Technology

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

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

[0134] artificial intelligence

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0178] THz communication

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

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

[0181] 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 the high frequency band, 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.

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

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

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

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

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

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

[0188] 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 transmission filter', 'spatial domain reception 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.).

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

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

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

[0192] Integrated Sensing and Communication (ISAC)

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

[0194] 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 at the same location (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).

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

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

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

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

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

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

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

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

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

[0204] In relation to the sensing operation in FIG. 10, the sensing transmission 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.

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

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

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

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

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

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

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

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

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

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

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

[0216] 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 described in FIG. 9 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 a 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.

[0217] < Network Energy Saving, NES >

[0218] Rel-18 Network Energy Saving Technology

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

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

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

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

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

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

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

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

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

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

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

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

[0231]

[0232] Cell DTX / DRX

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

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

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

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

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

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

[0239] SSB-less SCell

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

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

[0242] Conditional Hand Over (CHO)

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

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

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

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

[0247] NES Enhancement

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

[0249] (1) On-demand SSB

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

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

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

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

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

[0255] (2) On-demand SIB1 transmission

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

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

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

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

[0260] (3) Adaptation of common signal / channel transmissions

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

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

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

[0264]

[0265] <LP-WUS (low-power Wake-up Signal)과 LP-WUR (Low-Power Wake-up Receiver)>

[0266] 3GPP Standard Release 19 supports LP-WUS (low-power Wake-up Signal) and LP-WUR (Low-Power Wake-up Receiver) to reduce power consumption of terminals, and is discussing the development of technologies utilizing them.

[0267] In the present disclosure, an MR (Main Radio) receiver refers to a receiver for receiving signals according to general 3GPP NR standards and can be utilized to receive OFDM signals, etc., on NR standards. That is, the receiver currently configured by the standard terminal can be understood as an MR (Main Radio) receiver. LP-WUR refers to a receiver that can be newly configured in the terminal to receive low-power signals, and can receive newly designed low-power signals such as LP-WUS (Low-Power Wake-up Signal) or LP-SS (Low-Power Synchronization Signal), and can generally have the characteristic of being configured with low cost and low power consumption.

[0268] Low-power signals such as LP-WUS or LP-SS may refer to OFDM waveform-based sequences (e.g., Zadoff-Chu sequence, Pseudo-random sequence, m-sequence, gold sequence), but they may be configured and transmitted differently from signals transmitted with the current general OFDM symbol structure in the resource configuration of the time / frequency axes under NR standards. For example, LP-WUS is modulated with OOK (On-Off Keying) to match the slot or symbol structure of the time axis, but it may not match the RE (Resource Element) structure of the frequency axis. That is, since LP-WUS is represented as 1 if there is a signal within a specific time interval and as 0 if there is no signal, the terminal can receive the signal simply by energy detection within that specific time interval. In the OOK symbols of these LP-WUSs, it may be considered that a sequence for spectrum flattening or an OFDM sequence for increasing transmission coverage or transmitting additional information be overlaid. In particular, the overlay of an OFDM sequence can be implemented by multiplying the waveform of the sequence by the ON area of ​​the ON-OFF KEYING symbol.

[0269] Generally, PDCCH monitoring accounts for a significant portion of the power consumption of a terminal in RRC_CONNECTED mode (hereinafter referred to as CONNECTED mode). Since the terminal monitors the PDCCH using the Main Radio (MR), increasing the sleep time of the Main Radio can be effective for saving the terminal's power. Conventionally, to save the terminal's power, DRX operations were introduced, which allow the terminal to perform PDCCH monitoring at regular intervals; WUS (Wake-Up Signal), which can indicate whether to perform PDCCH monitoring during that interval; and adaptation operations, which can adjust the frequency of PDCCH monitoring within the DRX Active Time. All of these operations were introduced for the purpose of reducing the terminal's power consumption by reducing the time the terminal monitors the PDCCH and guaranteeing a sleep time during which the Main Radio does not operate.

[0270] 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 a relatively low power level, resulting in lower power consumption compared to the MR. Therefore, a terminal in CONNECTED mode can reduce power consumption by operating the MR in a sleep state to avoid PDCCH monitoring, and if the LP-WUS can be received via the low-power LR and utilized to wake up the MR, it can be expected to be effective for power saving. Through this, the terminal can effectively maintain a long sleep time for the MR, which consumes less power. Additionally, one can consider receiving other instructions via the LP-WUS, such as an action to temporarily switch the MR to a sleep state, and operating the MR accordingly.

[0271] The LP-WUS may include a payload transmitted in the form of the aforementioned OOK. Generally, the payload can be said to contain information that is actually instructed to the terminal. In addition, it may consist of a preamble for other purposes (e.g., synchronization acquisition) and an OFDM sequence overlaid on the OOK symbol. That is, the LP-WUS can be said to include information transmitted through the payload and information transmitted through the overlaid OFDM sequence.

[0272] LP-WUR can be defined by classifying it into two types.

[0273] (1) LP-WUR Type #1: WUR capable of energy detection only

[0274] (2) LP-WUR Type #2: WUR capable of sequence detection

[0275] In the case of LP-WUR Type 1, the focus is on low cost, and it is a WUR capable of determining only the presence or absence of a signal, that is, only energy detection. Therefore, it is a receiver capable of receiving only information transmitted through the OOK symbol, i.e., the payload.

[0276] LP-WUR Type 2 is a WUR that is more expensive than Type 1 and can detect OFDM sequences and energy. Therefore, it is a receiver capable of receiving not only payloads but also information transmitted through overlaid OFDM sequences. In addition, it can receive PSS / SSS of existing NR signals.

[0277]

[0278] <MTRP 전송>

[0279] The following describes an MTRP transmission method in which M TRPs transmit data to a single terminal (User equipment, UE).

[0280] DL MTRP-URLLC refers to the transmission of the same data / DCI by multiple TRPs using different layer / time / frequency resources. For example, TRP 1 transmits the same data / DCI from Resource 1, and TRP 2 transmits the same data / DCI from Resource 2. A UE configured with the DL MTRP-URLLC transmission method receives the same data / DCI using different layer / time / frequency resources. In this case, the UE is instructed by the base station on which QCL RS / type (i.e., DL TCI state) to use at the layer / time / frequency resource receiving the same data / DCI. For example, if the same data / DCI is received from Resource 1 and Resource 2, the UE is instructed on the DL TCI state to use for Resource 1 and the DL TCI state to use for Resource 2. Since the UE receives the same data / DCI through both Resource 1 and Resource 2, high reliability can be achieved. These DL MTRP URLLCs can be applied to PDSCH / PDCCH.

[0281] Conversely, UL MTRP-URLLC refers to a scenario where multiple TRPs receive the same data / UCI from a single UE using different layer, time, and frequency resources. For example, TRP 1 receives the same data / UCI from the UE via Resource 1, and TRP 2 receives it via Resource 2; subsequently, the received data / UCI is shared through a connected backhaul link between the TRPs. A UE configured with the UL MTRP-URLLC transmission mode transmits the same data / UCI using different layer, time, and frequency resources. In this case, the UE receives instructions from the base station regarding which Tx beam and Tx power (i.e., UL TCI state) to use from the layer, time, and frequency resource transmitting the same data / UCI. For instance, if the same data / UCI is transmitted from both Resource 1 and Resource 2, the UE is instructed on the UL TCI state to be used for Resource 1 and the UL TCI state to be used for Resource 2. These UL MTRP URLLCs can be applied to PUSCH / PUCCH.

[0282] In addition, from the perspective of DCI (downlink control information) transmission, MTRP transmission methods can be divided into i) M-DCI (multiple DCI) based MTRP transmission, where each TRP transmits a different DCI, and ii) S-DCI (single DCI) based MTRP transmission, where a single TRP transmits a DCI. For example, in the case of S-DCI, since all scheduling information for the data transmitted by the M TRP must be conveyed through a single DCI, it can be used in an ideal BackHaul (BH) environment where dynamic cooperation between two TRPs is possible.

[0283] Below, we will introduce MTRP transmission introduced in the NR standard.

[0284] (1) NR Release 16 MTRP transmission

[0285] In NR Standard Release 16, S-DCI-based MTRP PDSCH and M-DCI-based MTRP PDSCH are supported.

[0286] - R16 S-DCI-based MTRP PDSCH

[0287] S-DCI-based MTRP PDSCH transmission can be further subdivided to use one of the SDM / FDM / TDM methods.

[0288] In the case of SDM, a single TB is transmitted over multiple layers, but layers belonging to different DMRS CDM groups are transmitted to different Tx beams (i.e., QCL RS or TCI states). This increases the number of layers compared to the existing STRP transmission method, thereby improving transmission capacity. Additionally, when a single TB is transmitted over multiple layers, some layers are transmitted to TRP 1 and the remaining layers to TRP 2, which can improve channel reliability through diversity gain.

[0289] In the case of FDM, two schemes, scheme 2a and scheme 2b, are supported. Scheme 2a is a method in which a single TB is transmitted to multiple RBs (multi-RB), but RBs belonging to different RB groups are transmitted to different Tx beams (i.e., QCL RS or TCI states). Scheme 2b is a method in which the same TB is transmitted to different RB groups, but RBs belonging to different RB groups are transmitted to different Tx beams (i.e., QCL RS or TCI states).

[0290] In the case of TDM, two methods, scheme 3 and scheme 4, are supported. Scheme 4 (=interslot TDM) is a method in which the same TB is repeatedly transmitted across multiple slots, but slots belonging to different slot groups are transmitted to different Tx beams (i.e., QCL RS or TCI states). In contrast, Scheme 3 (=intraslot TDM) is a method in which the same TB is repeatedly transmitted across multiple OFDM symbol groups, but some OFDM symbol groups and the remaining OFDM symbol groups are transmitted to different Tx beams (i.e., QCL RS or TCI states).

[0291] - R16 M-DCI-based MTRP PDSCH

[0292] M-DCI-based MTRP PDSCH transmission is a method in which each TRP schedules and transmits a PDSCH via DCI. That is, TRP 1 transmits PDSCH 1 via DCI 1, and TRP 2 transmits PDSCH 2 via DCI 2. When PDSCH 1 and PDSCH 2 overlap on the same frequency time resource, two PDSCHs are received for the same RE, thereby increasing resource efficiency and transmission capacity. To this end, the R16 standard introduced a CORESET pool, which is a group of multiple CORESETs. TRP 1 transmits a PDCCH through a CORESET belonging to CORESET Pool 0, and TRP 1 also transmits the PDSCH scheduled by that PDCCH. Similarly, TRP 2 transmits a PDCCH through a CORESET belonging to CORESET Pool 1, and TRP 2 also transmits the PDSCH scheduled by that PDCCH. Similarly, for PUSCH, a specific TRP can schedule a PUSCH transmission to a UE through a CORESET belonging to each CORESET pool. In the case of PUCCH, some PUCCH resources are scheduled by TRP 1 to receive UCIs, while the remaining PUCCH resources are scheduled by TRP 2 to receive UCIs. For PUSCH or PUCCH, the channels scheduled / used by each TRP are TDMed together so that no overlap occurs, meaning no increase in transmission capacity can be expected; however, the UE can send independent PUSCH / PUCCH to TRP 1 and TRP 2, respectively.

[0293] Additionally, the UE may recognize a PUSCH (or PUCCH) scheduled by the DCI received from a different CORESET (or a CORESET belonging to a different CORESET group) as a PUSCH (or PUCCH) transmitted to a different TRP, or as a PUSCH (or PUCCH) of a different TRP. Furthermore, the method for UL transmission (e.g., PUSCH / PUCCH) transmitted to a different TRP can be applied in the same way to UL transmission (e.g., PUSCH / PUCCH) transmitted to a different panel belonging to the same TRP.

[0294] The CORESET group ID (or CORESET pool index having the same meaning) described or mentioned in the present invention may refer to an index / identification information (e.g., ID) for distinguishing the CORESET for each TRP / panel. Furthermore, the CORESET group may be a group / union of CORESETs distinguished by the index / identification information (e.g., ID) for distinguishing the CORESET for each TRP / panel / the said CORESET group ID. For example, the CORESET group ID may be specific index information defined within the CORESET settings. For example, the CORESET group may be set / indicated / defined by an index defined within the CORESET settings for each CORESET. And / or the CORESET group ID may refer to an index, identification information, indicator, etc., for distinguishing / identifying CORESETs configured / associated with each TRP / panel, and the CORESET group ID described / mentioned in this document may be replaced and expressed with a specific index, specific identification information, or specific indicator for distinguishing / identifying CORESETs configured / associated with each TRP / panel. The above CORESET group ID, that is, the specific index, specific identification information, or specific indicator for distinguishing / identifying CORESETs configured / associated with each TRP / panel, may be configured / indicated through upper-level signaling (upper-level signaling, e.g., RRC signaling), L2 signaling (e.g., MAC-CE), L1 signaling (e.g., DCI), etc.For example, PDCCH detection for each TRP / panel may be configured / instructed to be performed at the level of the corresponding CORESET group, and / or uplink control information (e.g., CSI, HARQ-A / N, SR) and / or uplink physical channel resources (e.g., PUCCH / PRACH / SRS resources) may be configured / instructed to be managed / controlled separately at the level of the corresponding CORESET group for each TRP / panel, and / or HARQ A / N (process / retransmission) for PDSCH / PUSCH, etc. scheduled at the level of the corresponding CORESET group for each TRP / panel may be managed.

[0295] For example, the upper-level parameter ControlResourceSet IE (information element) is used to set a time / frequency control resource set (CORESET). For instance, the control resource set (CORESET) may be related to the detection and reception of downlink control information. The ControlResourceSet IE may include a CORESET-related ID (e.g., controlResourceSetID), an index of the CORESET pool for the CORESET (e.g., CORESETPoolIndex), time / frequency resource settings for the CORESET, and TCI information related to the CORESET. For instance, the index of the CORESET pool (e.g., CORESETPoolIndex) may be set to 0 or 1. In the above description, the CORESET group may correspond to the CORESET pool, and the CORESET group ID may correspond to the CORESET pool index (e.g., CORESETPoolIndex). A ControlResourceSet (i.e., CORESET) can be configured via upper-level signaling (e.g., RRC signaling).

[0296] (2) NR Release 17 MTRP Transmission

[0297] NR Standard Release 17 supports MTRP PDCCH repeat transmission, MTRP PDCCH / PDSCH SFN transmission, S-DCI-based MTRP PUSCH repeat transmission, and single PUCCH resource-based MTRP PUCCH repeat transmission. These transmission techniques all involve the repeated transmission of the same content (i.e., DCI, UL TB, or UCI) as an improvement direction for URLLC targets to increase reliability. In the case of MTRP PDCCH repeat transmission, it is repeated via TDM or FDM, while MTRP PDCCH / PDSCH SFN is repeated over the same time, frequency, and layer. Additionally, S-DCI-based MTRP PUSCH repeat transmission and single PUCCH resource-based MTRP PUCCH repeat transmission are each repeated via TDM.

[0298] - R17 S-DCI-based MTRP PDCCH iterative transmission

[0299] In NR Standard Release 17, for MTRP PDCCH recurring transmission, multiple CORESETs with different TCI states (i.e., different QCL RS) are configured for the UE, and multiple SS (Search Space) sets are configured, each connected to the respective CORESETs. By instructing / configuring the UE that the SS set connected to one CORESET is linked to the SS set connected to another CORESET for recurring transmission, the UE can know that the PDCCH candidates of the corresponding SS set are being recurring.

[0300] For example, two CORESETs, CORESET 0 and CORESET 1, are set for the UE, and CORESET 0 and CORESET 1 are connected to SS Set 0 and SS Set 1, respectively, and SS Set 0 and SS Set 1 may be linked. The UE can recognize that the PDCCH candidate of SS Set 0 and the PDCCH candidate of SS Set 1 have repeatedly transmitted the same DCI, and through a specific rule, recognize that a specific PDCCH candidate of SS Set 0 and a specific PDCCH candidate of SS Set 1 are a pair set to repeatedly transmit the same DCI. These two PDCCH candidates are called linked PDCCH candidates, and the UE can successfully decode the corresponding DCI if it correctly receives either of the two PDCCH candidates. However, when receiving a PDCCH candidate of SS set 0, the QCL RS of the TCI state of COERSET 0 connected to SS set 0 (i.e., the DL beam) is used, and when receiving a PDCCH candidate of SS set 1, the QCL RS of the TCI state of COERSET 1 connected to SS set 1 (i.e., the DL beam) is used, thereby receiving the linked PDCCH candidates in different beams.

[0301] - R17 MTRP SFN PDCCH

[0302] As a special case of MTRP PDCCH repeated transmission, multiple TRPs can repeatedly transmit the same DCI through the same time / frequency / DMRS port, which can be called SFN PDCCH transmission. However, for SFN PDCCH transmission, the base station sets multiple TCI states in a single CORESET instead of setting multiple CORESETs with different TCI states. When the UE receives a PDCCH candidate through the SS set connected to that single CORESET, it attempts to estimate the channel of the PDCCH DMRS and decode it by utilizing all of the corresponding multiple TCI states.

[0303] - R17 MTRP SFN PDSCH

[0304] When the above MTRP PDSCH is repeatedly transmitted, the two TRPs repeatedly transmit the corresponding channel to different resources. However, in a special case where the resources used by the two TRPs are identical—that is, when the same channel is repeatedly transmitted through the same frequency, time, and layer (=DMRS port)—the reliability of the channel can be improved. In this case, the repeated transmission of the same channel is combined and received without distinguishing resources, so it is recognized as a single channel from the receiver's perspective. In the NR standard Release 17, two DL TCI states for PDSCH DMRS reception can be configured for PDSCH SFN transmission.

[0305] - R17 S-DCI-based MTRP PUSCH repeated transmission

[0306] In NR Standard Release 17, the base station sets two SRS sets for the UE to perform S-DCI-based MTRP PUSCH transmission, and each SRS set is used to indicate the UL Tx port and UL beam / QCL information for TRP 1 and TRP 2, respectively. Additionally, the base station performs SRS resource indication per SRS set through two SRI fields in a single DCI, and can indicate up to two PC (Power Control) parameter sets. For example, the first SRI field can indicate the SRS resources and PC parameter set defined in SRS Set 0, and the second SRI field can indicate the SRS resources and PC parameter set defined in SRS Set 1. The UE is indicated the UL Tx port, PC parameter set, and UL beam / QCL information for TRP 1 through the first SRI field, and thereby performs PUSCH transmission at the TO corresponding to SRS Set 0. Similarly, the UE is instructed via the second SRI field regarding the UL Tx port, PC parameter set, and UL beam / QCL information toward TRP 2, and thereby performs PUSCH transmission at the TO corresponding to SRS set 1. The existing single field has been expanded to two fields to allow for the specification of fields such as TPMI, PTRS, and TPC, in addition to the SRI field, for each TRP. Furthermore, a 2-bit SRS resource set indicator field has been introduced to select a specific one of the two SRS sets to perform STRP PUSCH repeated transmission, or to select both to perform MTRP PUSCH repeated transmission. That is, if the field is 00 or 01, it indicates SRS set 0 and SRS set 1, respectively, and performs STRP PUSCH transmission corresponding to each SRS set; if it is 10, it indicates (SRS set 0, SRS set 1) and performs MTRP PUSCH transmission with the SRS set pairs in the specified order.That is, SRS set 0 corresponds to the first PUSCH TO. If 11, it indicates (SRS set 1, SRS set 0) and performs MTRP PUSCH transmissions with SRS set pairs in the specified order. That is, SRS set 1 corresponds to the first PUSCH TO.

[0307] - R17 Single PUCCH resource-based MTRP PUCCH repeated transfer

[0308] In NR Standard Release 17, for MTRP PUCCH transmission based on a single PUCCH resource, the base station enables / configures two spatial relation infos for the UE on a single PUCCH resource (or enables / configures two sets of PC (power control) parameters in the case of FR1). When a UL UCI is transmitted through the PUCCH resource, each spatial relation info is used to indicate the spatial relation info toward TRP 1 and TRP 2, respectively. For example, through the value indicated in the first spatial relation info, the UE is instructed on the Tx beam / PC parameters toward TRP 1, and uses this information to perform PUCCH transmission at the TO (Transmission Occasion) corresponding to TRP 1. Similarly, through the value indicated in the second spatial relation info, the UE is instructed on the Tx beam / PC parameters toward TRP 2, and uses this information to perform PUCCH transmission at the TO corresponding to TRP 2.

[0309] In NR Standard Release 17, the configuration method was improved to allow two spatial relation infos to be configured in a PUCCH resource for MTRP PUCCH iterative transmission. That is, if PC (power control) parameters such as PLRS, Alpha, P0, and Closed loop index are configured in each spatial relation info, a spatial relation RS can be configured. Consequently, PC information and spatial relation RS information corresponding to two TRPs can be configured through the two spatial relation infos; the UE transmits to the PUCCH using the first spatial relation info in TO 1, and transmits to the PUCCH with the same UCI (i.e., CSI, ACKNAK, SR) using the second spatial relation info in TO 2. Hereinafter, a PUCCH resource with two spatial relation infos configured will be referred to as an MTRP PUCCH resource, and a PUCCH resource with one spatial relation info configured will be referred to as an STRP PUCCH resource.

[0310]

[0311] <TCI 스테이트 / beam indication의 의미>

[0312] The meaning of using or mapping a specific TCI state (or TCI) when receiving data / DCI / UCI for a certain frequency / time / space resource may mean that, in the case of the downlink, the channel is estimated from the DM-RS using the QCL type and QCL RS indicated by the corresponding downlink TCI state at that frequency / time / space resource, and the data / DCI is received / demodulated through the estimated channel.

[0313] In the case of the uplink, this may mean that DM-RS and data / UCI are transmitted / modulated using the Tx beam and / or Tx power directed by the corresponding uplink TCI state in that frequency / time / space resource.

[0314] The uplink TCI state contains the UE's Tx beam and / or Tx power, and instead of the TCI state, spatial relation info, etc., may be set for the UE through other parameters.

[0315] The uplink TCI state may be directly specified in the DCI transmitting the uplink grant, or it may refer to spatial relation information of the SRS resource specified through the SRI field of the UL grant DCI. Alternatively, it may refer to open-loop transmit power control parameters connected to values ​​specified through the SRI field of the UL grant DCI. Or, the uplink TCI may be specified using the DL grant DCI.

[0316] In this invention, TO refers to each channel transmitted at different times when multiple channels are TDMed, each channel transmitted to different frequencies / RBs when FDMed, and each channel transmitted to different layers / beams / DM-RS ports when SDMed. One TCI state is mapped to each TO. When the same channel is transmitted repeatedly, the complete DCI / data / UCI is transmitted to a single TO, and the receiving end receives multiple TOs to increase the reception success rate.

[0317]

[0318] <MTRP 환경에서의 SSB 및 RACH 적응 (Adaptation)>

[0319] The present disclosure proposes the adaptation of a Type 2 SSB in an MTRP environment, and the Type 1 SSB and Type 2 SSB can be classified as Options 1 to 3 below.

[0320] - SSB Type Classification Option 1

[0321] Type 1 SSB: This may refer to an SSB that is periodically transmitted on a first cell or a second cell. If the period, etc., for the SSB is determined / defined / set, the SSB may be transmitted continuously at that period (without on or off intervals, or without activation or deactivation). If Type 1 SSB refers to an SSB transmitted on a first cell, the first cell may be a timing reference cell. If Type 1 SSB refers to an SSB transmitted on a second cell, the second cell may be in an intra-band or inter-band CA (carrier aggregation) relationship with the first cell, and (especially in an inter-band CA environment) the second cell may be set as a timing reference cell for the first cell, or (especially in an intra-band CA environment) the second cell may be determined / defined as a timing reference cell for the first cell (e.g., any cell, PCell, or PSCell within the same TAG (timing advance group)). In addition, only the following Type 2 SSB may be transmitted on the first cell without Type 1 SSB.

[0322] Type 2 SSB (or on-demand SSB): This may refer to an SSB in which transmission on the first cell is activated by instructions from the base station (via RRC / MAC-CE / DCI, etc.). Or it may refer to an SSB in which transmission is activated by a request from a terminal. For the activated SSB, the SSB may be deactivated if the deactivation is explicitly instructed via RRC / MAC-CE / DCI, etc., or if the number of transmissions or transmission interval is set / instructed in the RRC / MAC-CE / DCI that instructs the SSB activation and the SSB is deactivated after the number of transmissions or transmission interval is passed, or if there is a pre-set / defined number of transmissions or transmission interval and the SSB is deactivated after the number of transmissions or transmission interval is passed after the SSB is activated, or (if the first cell is SCell) if the activation for the first cell is completed (or if the CSI for the first cell is successfully reported), or (if the first cell is SCell) if the first cell is deactivated and the SSB is deactivated, or (if the first cell is PCell) if the SSB is deactivated after a handover is performed, or the SSB may be deactivated by a request from the terminal.

[0323] - SSB Type Classification Option 2

[0324] A method in which one or more SSB settings are configured and an SSB corresponding to one of the SSB settings can be transmitted by a base station instruction or a request from a terminal. At this time, between different SSB settings, at least the SSB periodicity values ​​may differ, and adaptation to the SSB periodicity can be performed by changing the activated SSB setting.

[0325] Type 1 SSB: Among the configured SSB settings, this may refer to a reference setting or an SSB setting with the largest SSB period. An SSB corresponding to that reference setting may be called a Type 1 SSB. If an SSB setting corresponding to a Type 2 SSB is not enabled, an SSB setting corresponding to a Type 1 SSB may be enabled. Conversely, if an SSB setting corresponding to a Type 2 SSB (or an SSB setting not corresponding to a Type 1 SSB) is enabled, an SSB setting corresponding to a Type 1 SSB may be disabled. Or, if the SSB occasions configured based on a specific (standard) setting among the configured SSB settings (hereinafter referred to as standard SSB occasions for convenience of explanation) are a subset of the SSB occasions configured based on another setting (hereinafter referred to as extended SSB occasions for convenience of explanation), the standard SSB occasions may be defined as Type 1 SSB (regardless of the actual activated SSB setting), and in this case, Type 2 SSB may be defined as the remaining SSB occasions among the extended SSB occasions (included in the actual activated setting) excluding the standard SSB occasions.

[0326] Type 2 SSB: In addition to the SSB settings corresponding to Type 1 SSB, one or more SSB settings for Type 2 SSB may be configured, and when the SSB settings corresponding to Type 2 SSB are activated, all SSBs belonging to the activated SSB settings may be defined as Type 2 SSBs. Alternatively, if an SSB time point configured based on a specific (reference) setting among the configured SSB settings (referred to as the reference SSB time point for convenience) becomes a subset of an SSB time point configured based on another setting (referred to as the extended SSB time point for convenience), the reference SSB time point may be defined as a Type 1 SSB (regardless of the actual activated SSB settings), and in this case, the Type 2 SSB may be defined as the remaining SSB time points among the extended SSB time points (included in the actual activated settings) excluding the reference SSB time point. One of the one or more SSB settings may be activated by an instruction from the base station (via RRC / MAC-CE / DCI) or by a request from the terminal. For the enabled SSB setting, the SSB may be disabled if the disablement is explicitly instructed via RRC / MAC-CE / DCI, etc., or if the number of transmissions or transmission interval is set / instructed in the RRC / MAC-CE / DCI that instructs the SSB activation and the SSB is disabled after the number of transmissions or transmission interval is passed, or if there is a pre-set / defined number of transmissions or transmission interval and the SSB is disabled after the number of transmissions or transmission interval is passed after the SSB is enabled, or if the first cell is SCell, the SSB is disabled when the activation for the first cell is completed (or when CSI reporting for the first cell is successfully reported), or if the first cell is SCell, the SSB is disabled when the first cell is disabled, or if the first cell is PCell, the SSB is disabled after a handover is performed, or the SSB is disabled by a request from the terminal.

[0327] - SSB Type Classification Option 3

[0328] A method in which one or more SSB settings are configured and an SSB corresponding to one of the SSB settings can be transmitted by a base station instruction or a request from a terminal. In this case, there exists an SSB (i.e., Type 1 SSB) that is continuously and periodically transmitted regardless of the (de)activation of the SSB setting, and an additional SSB setting to be transmitted to the SSB can be (de)activated. At least the SSB period or SSB timing pattern may differ between different SSB settings, and adaptation to the SSB period can be performed by changing the activated SSB setting.

[0329] Type 1 SSB: may mean an SSB corresponding to the default SSB setting, and continuous periodic transmission may be guaranteed regardless of the (de)activation of the SSB setting(s) corresponding to Type 2 SSB.

[0330] Type 2 SSB: One or more SSB settings for Type 2 SSB may be configured. One of the one or more SSB settings may be activated by a command from the base station (via RRC / MAC-CE / DCI) or by a request from the terminal. For the enabled SSB setting, the SSB may be disabled if the disablement is explicitly instructed via RRC / MAC-CE / DCI, etc., or if the number of transmissions or transmission interval is set / instructed in the RRC / MAC-CE / DCI that instructs the SSB activation and the SSB is disabled after the number of transmissions or transmission interval is passed, or if there is a pre-set / defined number of transmissions or transmission interval and the SSB is disabled after the number of transmissions or transmission interval is passed after the SSB is enabled, or if the first cell is SCell, the SSB is disabled when the activation for the first cell is completed (or when the CSI for the first cell is successfully reported), or if the first cell is SCell, the SSB is disabled when the first cell is disabled, or if the first cell is PCell, the SSB is disabled after a handover is performed, or the SSB is disabled by a request from the terminal.

[0331]

[0332] The RO category is explained below.

[0333] RACH configuration may refer to one or more of RACH-ConfigCommon, RACH-ConfigCommonTwoStepRA, RACH-ConfigDedicated, RACH-ConfigGeneric, RACH-ConfigGenericTwoStepRA, and RACH-ConfigTwoTA of the NR standard TS 38.331 specification, and is referred to as RACH config for convenience.

[0334] RACH occasions (ROs) on a specific time / frequency can be configured through a RACH config. In the present invention, the RACH config can also be substituted with RO. Additionally, by setting / instructing the terminal with an RCI (RACH configuration index), the base station can configure the PRACH preamble format, the time axis position of the RO (e.g., the period / offset of the RO or the RACH slot containing the RO, the frame / subframe / slot / symbol index where the RO or the RACH slot containing the RO starts or is included), and the duration of the RO or the RACH slot containing the RO.

[0335] Based on this configuration, the present disclosure proposes the adaptation of Cat 2 RO in an MTRP environment, and the RO categories, namely Cat 1 RO and Cat 2 RO, can be classified as Options A to B below.

[0336] - RO Category Classification Option A: Set by the same RCI

[0337] Cat 1 RO: This is an RO configured for legacy terminals. Legacy terminals refer to 3GPP NR standard Release 19 terminals and terminals prior to 3GPP NR standard Release 19 that do not support RACH adaptation features introduced in 3GPP NR standard Release 19 NES.

[0338] Cat 2 RO: Set by the same RCI as Cat 1 RO, but can be set to have different time and / or frequency resources.

[0339] For example, one or more of the values ​​such as frame-unit period(s) of a RACH slot containing a Cat 2 RO, frame-unit offset(s) of a RACH slot containing a Cat 2 RO, etc., may be additionally set, and the period / offset(s) may be values ​​that are set separately and may be values ​​that are set as delta values ​​from the period / offset for a Cat 1 RO.

[0340] As another example, separate frequency-related parameters for Cat 2 ROs can be additionally set (e.g., frequency axis RB level offset between the minimum RO in the frequency domain from the UL BWP PRB index 0 set via msg1-FrequencyStart, and the number of ROs being FDMed set via msg1-FDM).

[0341] As another example, the preceding examples may be applied to additionally set a (time axis) muting pattern / masking pattern that determines (or considers) some Cat 2 RO resources as invalid (i.e., invalid) among virtual Cat 2 RO resources with different time and / or frequency resources from Cat 1 RO. With such a muting pattern / masking pattern applied, the remaining ROs excluding those determined to be invalid may be determined as Cat 2 ROs. Alternatively, a separate time resource parameter may not be applied. If Cat 1 RO and Cat 2 RO overlap (partially or entirely on the time / frequency axis), the terminal may determine that the Cat 1 RO is valid and the Cat 2 RO is invalid.

[0342] - RO Category Classification Option B: Set by different RCIs

[0343] Cat 1 RO: This is the RO configured for legacy terminals.

[0344] Cat 2 RO: Set by an RCI value different from that of Cat 1 RO. The Cat 2 RO can be set through the same RACH config as the RACH config that sets the Cat 1 RO, or through a separate RACH config. The time and / or frequency resource parameters described as examples for the Cat 2 RO in the above RO category classification option A may be applied to the RCI (set for the Cat 2 RO) to finally determine the Cat 2 RO. Alternatively, no separate time and / or frequency resource parameters may be applied other than the RCI. If the Cat 1 RO and the Cat 2 RO overlap (partially or entirely on the time / frequency axis), the terminal may determine that the Cat 1 RO is valid and the Cat 2 RO is invalid.

[0345] The terminal performs SSB-to-RO mapping for the above Cat 1 ROs (i.e., mapping the corresponding SSB index for each RO or preamble index within the RO) and SSB-to-RO mapping for the Cat 2 ROs separately. In other words, the terminal performs SSB-to-RO mapping for the Cat 1 ROs and separately performs SSB-to-RO mapping for the Cat 2 ROs.

[0346] A terminal may receive a Cat 2 RO configured for a single serving cell (or a single BWP or a single TRP). The terminal may receive a signal from the base station regarding whether the Cat 2 RO is valid or whether it is active or inactive. Such signaling methods may include higher-layer signaling such as RRC signaling, MAC CE, DCI, etc. Alternatively, after receiving a signal that the Cat 2 RO is valid or active, if a certain timer (the value of the timer may be a predefined or set / instructed value) expires, the terminal may determine that the Cat 2 RO is invalid or inactive.

[0347] Meanwhile, to support MTRP operation (intra-cell or inter-cell) in the NR system, a function has been introduced to configure an SSB having a PCI value different from the serving cell PCI. For example, an SSB of PCI#1 is configured for a single serving cell, and as an additional SSB transmitted over that serving cell is configured, that additional SSB can be configured as PCI#2. Depending on the capability of the terminal, the number of SSBs having a PCI value different from the serving cell PCI may vary, and up to 7 can be configured. An SSB having a PCI value different from the serving cell PCI in this manner can be configured using at least one of the following functions.

[0348] - QCL RS of TCI state (may refer to DL TCI and / or UL TCI and / or unified / joint TCI)

[0349] - For path-loss estimation

[0350] - Used for MPE (Maximum Permissible Exposure), beam failure detection, radio link monitoring, etc.

[0351] - Applications for beam measurement to support mobility (e.g., SS-RSRP, SS-RSRQ, L1-RSRP, L1-SINR, etc.) and SMTC settings for this purpose

[0352] - For PCI#2 SSB-based SSB to RO mapping when configuring the RACH corresponding to TA#2, where 2 TAs are configured for a single serving cell, TA#1 is linked to TRP#1 (with PCI#1 SSB), and TA#2 is linked to TRP#2 (with PCI#2 SSB).

[0353] As described above, to support MTRP operation in an NR system or a 6G system, multiple TRP indices / CORESET pool indices / SSBs having PCI values ​​(different from the PCI of the serving cell SSB) may be configured for the terminal. For example, TRP 1 transmits a PDCCH through a CORESET belonging to CORESET pool index 0 (or linked to TRP index 0 or linked to PCI #A), and TRP 1 can also transmit the PDSCH scheduled by that PDCCH. TRP 2 transmits a PDCCH through a CORESET belonging to CORESET pool index 1 (or linked to TRP index 0 or linked to PCI #A), and TRP 2 can also transmit the PDSCH scheduled by that PDCCH. In the case of PUSCH, a specific TRP can schedule a PUSCH transmission to a UE through a CORESET belonging to each CORESET pool index (or linked to each TRP index or linked to each PCI). In the case of PUCCH, some PUCCH resources may be scheduled by TRP 1 to receive the UCI, while the remaining PUCCH resources may be scheduled by TRP 2 to receive the UCI. For convenience, two TRP operations were used as an example, but this can be extended to operations involving two or more TRPs.

[0354] The SSB adaptation described in this disclosure may mean at least one of the following operations. In the following, Type 2 SSB may be replaced with an on-demand SSB. Also, the serving cell in the description of Type 1 / 2 SSB operations may be replaced with a TRP (or a TRP index / CORESET pool index / PCI corresponding to the TRP). Additionally, SSB adaptation information may mean the following switching information, which may return to the state prior to switching after a certain period of time (pre-defined / configured or indicated).

[0355] - Switching between No SSB and Type 2 SSB transmission: For example, by enabling Type 2 SSB while no SSB is being transmitted to the corresponding serving cell, or by disabling Type 2 SSB while it is enabled, no SSB is transmitted to the corresponding serving cell.

[0356] - Switching between Type 1 SSB transmission and Type 2 SSB transmission (e.g., Type 2 SSB is activated and Type 1 SSB is not transmitted while Type 1 SSB is transmitting, or Type 2 SSB is deactivated and Type 1 SSB is transmitted while Type 2 SSB is activated)

[0357] - Switching between Type 1 SSB-only transmission and Type 1+2 SSB transmission (e.g., Type 2 SSB is activated while only Type 1 SSB is being transmitted, so that both Type 1 SSB and Type 2 SSB are transmitted, or Type 2 SSB is deactivated while both Type 1 SSB and Type 2 SSB are activated, so that only Type 1 SSB is transmitted)

[0358] The RACH adaptation described in this disclosure may mean at least one of the following operations. Additionally, the serving cell in the Cat 1 RO / Cat 2 RO operation description may be replaced with a TRP (or a TRP index / CORESET pool index / PCI corresponding to the TRP). Additionally, the RACH adaptation information may mean the following switching information and may return to the state prior to switching g after a certain period of time (pre-defined / configured or indicated). Being valid for a Cat 1 RO and / or a Cat 2 RO means that a PRACH transmission using the said RO is allowed, and being invalid for a Cat 1 RO and / or a Cat 2 RO means that a PRACH transmission using the said RO is not allowed.

[0359] - Switching between Cat 1 RO and Cat 2 RO: (For example, when only Cat 1 RO is determined to be enabled / valid, Cat 2 RO can be enabled and Cat 1 RO deactivated (or become invalid), or when Cat 2 RO is enabled, Cat 2 RO can be deactivated and Cat 1 RO enabled (or become valid))

[0360] - Switching between Cat 1 RO and Cat 1+2 RO (for example, when only Cat 1 RO is determined to be enabled / valid, Cat 2 RO may be enabled so that both Cat 1 RO and Cat 2 RO are valid, or when both Cat 1 RO and Cat 2 RO are enabled, Cat 2 RO may be disabled and only Cat 1 RO may be enabled (or become a state where it is determined to be valid)).

[0361] - Switching between No RO and Cat 2 RO: For example, a Cat 2 RO can be activated when there is no valid RO in the corresponding serving cell, or a Cat 2 RO can be deactivated when the Cat 2 RO is activated, so that there is no valid RO in the corresponding serving cell.

[0362] In the following description, TRP can be represented as serving cell, carrier, BWP, subband, TRxP, CORESET pool, etc., and TRP index can be replaced with serving cell index, carrier index, BWP index, subband index, TRxP index, CORESET pool index, etc.

[0363] (1) SSB adaptation by TRP

[0364] In the following, we propose a signaling method for SSB adaptation per TRP in intra-cell or inter-cell multi-TRP situations, as well as the operation of a terminal receiving such signaling.

[0365] First, regarding signaling methods for SSB adaptation by TRP, [Method #1-1] to [Method #1-4] can be considered as follows.

[0366] [Method #1-1] Method for including TRP-related information in SSB adaptation-related signaling via RRC / MAC-CE / DCI / LP-WUS

[0367] As described above, SSB adaptation can be performed by (de)enabling Type 2 SSB (or on-demand SSB). In this case, one or a combination of RRC / MAC-CE / DCI / LP-WUS can be used as the signaling to (de)enabling Type 2 SSB. TRP-specific Type 2 SSB (de)enabling signaling can be performed by including TRP-related information (i.e., TRP index / CORESET pool index / PCI index) in the signaling (or by treating each TRP as if it were a single serving cell).

[0368] Example 1) The on / off (or enabled / disabled) status of a Type 2 SSB for each TRP (or TRP index / CORESET pool index / PCI) can be transmitted from the base station through RRC signaling. For example, a terminal that receives an RRC signal indicating that a Type 2 SSB corresponding to PCI #A set in a serving cell is in an off state or disabled can recognize that the PCI #A SSB (i.e., the Type 2 SSB corresponding to PCI #A) is not transmitted on the serving cell.

[0369] Example 2) A separate field can be created in MAC-CE / DCI / LP-WUS signaling that is distinguished by TRP (or TRP index / CORESET pool index / PCI). For example, if the nth bit or field within MAC-CE or DCI is predefined / configured or determined by a rule to be linked to TRP index k (or CORESET pool index k or PCI #k), the terminal can recognize that the Type 2 SSB corresponding to TRP index k (or CORESET pool index k or PCI #k) is turned on / off or enabled / disabled when it receives the Type 2 SSB on / off (or enabled / disabled) status / status through the nth bit or field.

[0370] Example 3) Type 2 SSB (de)enable signaling per TRP (or TRP index / CORESET pool index / PCI) can be performed by a combination of RRC signaling and MAC-CE / DCI / LP-WUS signaling. For example, multiple Type 2 SSB configuration indices can be configured through RRC signaling, and each Type 2 SSB configuration index can be linked to a TRP (or TRP index / CORESET pool index / PCI). Through MAC-CE / DCI signaling, one of the Type 2 SSB configuration indices may be indicated. For example, a Type 2 SSB configuration index #n is linked with a TRP index k (or CORESET pool index k or PCI #k) in advance via RRC signaling, and when the Type 2 SSB configuration index #n is indicated via MAC-CE / DCI signaling, the terminal can recognize that the Type 2 SSB corresponding to the linked TRP index k (or CORESET pool index k or PCI #k) is turned on / off or enabled / disabled.

[0371] [Method #1-2] How to set / instruct SSB adaptation of a TRP through CORESET pool index / DCI / RNTI linked to a TRP

[0372] A base station may configure one or more CORESET pool indices / DCIs / RNTIs and link one (or multiple) PCIs to each CORESET pool index / DCI / RNTI. For example, if CORESET pool index #n and PCI #k are linked and a terminal receives a DCI through a CORESET belonging to CORESET pool index #n, the SSB adaptation information instructed / configured through that DCI (or the PDSCH scheduled by that DCI) can be applied to PCI #k. For another example, if DCI format #n and PCI #k are linked and a terminal receives DCI format #n, the SSB adaptation information instructed / configured through that DCI (or the PDSCH scheduled by that DCI) can be applied to PCI #k. As another example, when RNTI value X and PCI #k are linked and the terminal receives a PDCCH (or PDSCH) scrambled with RNTI X, the SSB adaptation information instructed / configured through the PDCCH (or PDSCH) can be applied to PCI #k.

[0373] [Method #1-3] Method for setting / instructing the adaptation of an SSB linked to a TRP using separate TRP adaptation signaling

[0374] One or a combination of RRC, MAC-CE, DCI, and LP-WUS may be used as a signaling to adapt, turn on / off, or (de)activate the TRP. When the association between TRP index n and PCI #k is predefined / configured or determined by a rule, the terminal can recognize that the PCI #k (Type 1 and / or Type 2) SSB associated with the TRP index n is activated (for a certain period of time) when it receives a signaling that TRP index n is turned on or activated (for a certain period of time), and conversely, recognize that the PCI #k (Type 1 and / or Type 2) SSB associated with the TRP index n is deactivated (for a certain period of time) when it receives a signaling that TRP index n is turned off or deactivated (for a certain period of time).

[0375] [Method #1-4] A method to apply TRP-common SSB adaptation or apply SSB adaptation only to specific TRPs without signaling for TRP-specific SSB adaptation, even in serving cells where multiple TRP operations are configured / applied.

[0376] One or more TRP indexes / CORESET pool indexes / PCIs may be configured for a serving cell. When SSB adaptation is signaled for the said serving cell by RRC / MAC-CE / DCI / LP-WUS or a combination thereof, the terminal may apply at least one of the following actions. Additionally, which of the following actions to apply may be configured separately. Furthermore, if there is no such separate configuration, a rule for which action to perform may be defined in advance.

[0377] - SSB adaptation can be applied commonly to all SSBs corresponding to all TRP indexes / CORESET pool indexes / PCIs configured in the corresponding serving cell. For example, if PCI #B is configured in addition to PCI #A for a serving cell, and Type 2 SSB (dis)activation is configured / instructed, the terminal may consider that both PCI #A and PCI #B are commonly Type 2 SSB (dis)activated.

[0378] - SSB adaptation can be applied only to the PCI set in the serving cell (not the additional PCI). For example, if PCI #B is additionally set to PCI #A for the serving cell, and Type 2 SSB (dis)enable is set / instructed, the terminal may consider that Type 2 SSB (dis)enable is only for PCI #A (and that the SSB corresponding to PCI #B is maintained in a transmission state without adaptation).

[0379] - SSB adaptation may be applied only to PCIs corresponding to specific TRP index / CORESET pool index / PCI. Specifically, there may be TRP index / CORESET pool index / PCI(s) for which SSB adaptation is predefined / configured or separately configured. For example, for a serving cell configured with PCI #A, PCI #B, and PCI #C, SSB adaptation behavior for PCI #A and PCI #B may be pre-configured. In this case, if Type 2 SSB (de)activation is configured / instructed, the terminal may consider that Type 2 SSB (de)activation is enabled only for PCI #A and PCI #B (and that the SSB corresponding to PCI #C remains in a transmission state without adaptation).

[0380]

[0381] The aforementioned SSB adaptive signaling by TRP index / CORESET pool index / PCI may also be indicated by SSB index (group). For example, as in [Method #1-1], when a base station transmits SSB adaptive signaling via RRC / MAC-CE / DCI / LP-WUS and a terminal receives it, the activation / deactivation or on / off status of the SSB index (group) may be set / instructed by TRP index / CORESET pool index / PCI.

[0382] As another example, when signaling the SSB adaptation of the TRP through the CORESET pool index / DCI format / RNTI linked to the TRP as in [Method #1-2], the activation / deactivation or on / off status of the SSB index (group) per TRP can be set / instructed.

[0383] As another example, when the activation / deactivation or on / off status of an SSB index (group) is set / instructed as in [Method #1-4], the application of such setting / instruction may be applied commonly to all TRPs within the serving cell or to specific TRPs only.

[0384]

[0385] Additionally, when a terminal requests adaptation to a Type 2 SSB via an uplink, one or more TRP indices / CORESET pool indices / PCIs may be associated with a single uplink signal / channel. For example, if a specific PRACH preamble index (or PRACH occasion) and PCI #A are associated in advance, the terminal may transmit the PRACH preamble index (or PRACH belonging to the PRACH occasion) to request SSB adaptation to PCI #A, and may expect to receive a downlink signal / channel corresponding to the PRACH (e.g., a RAR (random access response) or a PDCCH / PDSCH that directs / sets SSB adaptation to PCI #A).

[0386] As another example, if a specific PRACH preamble index (or PRACH time) is linked with PCI #A and PCI #B in advance, the terminal may transmit the corresponding PRACH preamble index (or the PRACH belonging to the PRACH time) to request SSB adaptation for PCI #A and / or PCI #B, and may expect to receive a downlink signal / channel corresponding to the PRACH (e.g., RAR or PCI #A / B SSB or PDCCH / PDSCH that directs / sets SSB adaptation for PCI #A / B).

[0387] Meanwhile, SSB adaptation and RACH adaptation can operate in conjunction. If a Type 2 SSB corresponding to a specific TRP index / CORESET pool index / PCI is turned off or disabled by the proposed SSB adaptation setting / instruction per TRP above, a Cat 2 RO corresponding to the same TRP index / CORESET pool index / PCI may also be determined to be invalid or disabled. Additionally, if a Type 2 SSB corresponding to a specific TRP index / CORESET pool index / PCI is turned on or enabled by the proposed SSB adaptation setting / instruction per TRP above, a Cat 2 RO corresponding to the same TRP index / CORESET pool index / PCI may also be determined to be valid or enabled.

[0388]

[0389] The following describes the operation of a terminal that has received signaling for SSB adaptation by TRP.

[0390] When a terminal receives a signaling that activates a Type 2 SSB corresponding to a specific TRP index / CORESET pool index / PCI, it can expect to receive the corresponding SSB from a specific point in time after the time of receiving the signaling.

[0391] For example, for a specific SSB index, it may be pre-configured / defined or indicated that an SSB can be transmitted at slot #n, slot #n+k, slot #n+2k…, where slot #k may represent an SSB period. From the first SSB transmission time (occasion) after receiving a Type 2 SSB enable signal, the terminal can expect to receive an SSB, and the value of T may be pre-defined or set / instructed by the base station.

[0392] FIG. 18 is a diagram illustrating the timing for performing SSB adaptation per TRP according to the present disclosure.

[0393] Referring to FIG. 18, SSB timings are periodically set and information regarding this may be provided to a terminal. The terminal may receive a Type 2 SSB at SSB timing #3, which is the earliest among the SSB timings located after a time offset of T (e.g., T symbol / slot / msec) from a first timing (t1) (e.g., located after a second timing (t2)), where the first timing (t1) may correspond to the SSB adaptation instruction / setting DL signal / channel reception timing.

[0394] The corresponding SSB point in Fig. 18 may refer to an SSB burst that includes all SSB indices, or an SSB burst consisting only of the SSB index(s) actually transmitted when signaling that only some of the total SSB indices are transmitted through a specific parameter (e.g., ssb-PositionsInBurst). In this case, the size of T may vary per TRP or a specific value may be signaled (considering the case of non-ideal backhaul between TRPs).

[0395] For example, when an SSB adaptation corresponding to TRP #A is indicated / set through a DL signal / channel received from a CORESET corresponding to TRP #A (e.g., a CORESET belonging to CORESET pool index 0), the terminal may apply an alpha value as T. On the other hand, when an SSB adaptation corresponding to TRP #B is indicated / set through a DL signal / channel received from a CORESET corresponding to TRP #A (e.g., a CORESET belonging to CORESET pool index 0), (considering the case of non-ideal backhaul between TRPs), when performing an SSB adaptation operation corresponding to TRP #B, the terminal may apply an alpha+delta value as T (e.g., delta>0, where the delta value may be a predefined or set / instructed value) or the T value itself may be indicated / set through the corresponding DL signal / channel.

[0396] As another example, when an SSB adaptation corresponding to a certain TRP index / CORESET pool index / PCI (e.g., serving cell PCI) is indicated / set, the terminal applies an alpha value as T, and when an SSB adaptation corresponding to a different TRP index / CORESET pool index / PCI (e.g., added PCI) is indicated / set, an alpha+delta value (e.g., delta>0, where delta may be a predefined or set / instructed value) is applied as T, or the T value itself may be indicated / set through a DL signal / channel that sets / instructs the SSB adaptation.

[0397] Similarly, if a terminal receives a signaling that a Type 2 SSB corresponding to a specific TRP index / CORESET pool index / PCI is disabled, it can expect that the corresponding SSB will not be received from a specific point in time after the time of receiving such signaling. Specifically, the terminal can expect that no SSB will be received from the time of the first SSB transmission (occasion) T3 symbol / slot / msec after receiving the instruction to disable the Type 2 SSB, and the corresponding T3 value may be a value predefined or set / instructed by the base station. Alternatively, the terminal may assume that it was automatically disabled or turned off after T4 hours from the time of activation, and the corresponding T4 value may be a value predefined (per TRP index / CORESET pool index / PCI) or set by the base station. In this case, the magnitude of T3 may vary per TRP or a specific value may be signaled (considering the case of non-ideal backhaul between TRPs).

[0398] For example, when Type 2 SSB disable corresponding to TRP #A is indicated / set through a DL signal / channel received from a CORESET corresponding to TRP #A (e.g., a CORESET belonging to CORESET pool index 0), the terminal may apply the alpha2 value as T3. On the other hand, when SSB adaptation corresponding to TRP #B is indicated / set through a DL signal / channel received from a CORESET corresponding to TRP #A (e.g., a CORESET belonging to CORESET pool index 0), (considering the case of non-ideal backhaul between TRPs), when performing the Type 2 SSB disable operation corresponding to TRP #B, the terminal may apply the alpha2+delta2 value (e.g., delta2>0, where the delta2 value may be a predefined or set / instructed value) as T3, or the T3 value itself may be indicated / set through the corresponding DL signal / channel. As another example, when Type 2 SSB disablement corresponding to a certain TRP index / CORESET pool index / PCI (e.g., serving cell PCI) is instructed / set, the terminal applies the alpha2 value as T3, and when Type 2 SSB disablement corresponding to a different TRP index / CORESET pool index / PCI (e.g., added PCI) is instructed / set, the alpha2+delta2 value (e.g., delta2>0, where delta2 may be a predefined or set / instructed value) is applied as T3, or the T3 value itself may be instructed / set through a DL signal / channel that sets / instructs Type 2 SSB disablement.

[0399]

[0400] If an additional PCI is configured in the serving cell PCI and the added PCI SSB is disabled, the terminal may not perform the TRP operation associated with the added PCI. Here, not performing the TRP operation associated with the added PCI may include at least one of the following terminal operations. Additionally, whether or not to perform the following operations may be predefined or separately configured.

[0401] - In the case of a DL / UL signal / channel where an added PCI SSB is set / directed as a QCL RS (or when examining the QCL relationship set for a specific DL / UL signal channel and following the QCL RSs linked to the QCL RS, it is found that the added PCI SSB is set / directed as a QCL RS), reception / transmission for the corresponding DL / UL signal / channel is not performed. Or, if there is a DL / UL signal / channel where an added PCI SSB is directed as a QCL RS (or when examining the QCL relationship set for a specific DL / UL signal channel and following the QCL RSs linked to the QCL RS, it is found that the added PCI SSB is directed as a QCL RS), the terminal may not expect the corresponding PCI SSB to be disabled.

[0402] - Omit measurements and reporting for added PCIs (e.g., L1 measurements for L1-RSRP / L1-SINR, L3 RRM measurements for RSRP / RSRP, radio link monitoring, beam failure detection / recovery).

[0403] - PDCCH monitoring in CORESETs belonging to CORESET pool indexes linked to added PCIs is not performed, or DL / UL scheduling information is ignored even if PDCCH is detected in the CORESET.

[0404] - Does not perform HARQ-ACK codebook configuration / feedback corresponding to CORESET pool indexes linked to added PCI.

[0405]

[0406] FIG. 19 is a diagram illustrating the operation of UE and BS for SSB adaptation per TRP according to one embodiment.

[0407] Referring to FIG. 19, the UE may receive configuration information from the BS in addition to the SSB for a specific serving cell in step 1905, which includes at least one SSB(s) having a PCI value different from the serving cell PCI to support multiple TRP operations (intra-cell or inter-cell).

[0408] Subsequently, the UE may receive SSB adaptation instructions specific to the TRP index / CORESET pool index / PCI from the BS based on at least one of [Method #1-1] to [Method #1-4] described above. Specifically, it may receive instructions to disable a TRP-specific type 2 SSB as in step 1910.

[0409] Upon receiving this, the UE may prohibit the performance of operations related to the TRP-specific Type 2 SSB, as in step 1915. Specifically, a UE that receives an SSB adaptation (i.e., an instruction to disable the TRP-specific Type 2 SSB) may not perform measurements and reports associated with the TRP-specific Type 2 SSB. In particular, it may prohibit the performance of operations related to the TRP-specific Type 2 SSB at the earliest SSB occasion after the offset from the time of receiving the instruction to disable the Type 2 SSB.

[0410]

[0411] FIG. 20 illustrates the flow of a method performed by a UE for SSB adaptation per TRP according to one embodiment.

[0412] Referring to FIG. 20, the UE may receive configuration information from the BS in addition to the SSB for a specific serving cell in step 2005, which includes at least one SSB(s) having a PCI value different from the serving cell PCI to support multiple TRP operations (intra-cell or inter-cell).

[0413] Subsequently, the UE may receive instructions for SSB adaptation by TRP index / CORESET pool index / PCI based on at least one of [Method #1-1] to [Method #1-4] described above. Specifically, it may receive instructions to disable a TRP-specific type 2 SSB as in step 2010.

[0414] Upon receiving this, the UE does not perform operations related to the corresponding TRP-specific Type 2 SSB. That is, it does not perform measurements or reports linked to the corresponding TRP-specific Type 2 SSB. In particular, it may prohibit the performance of operations related to the TRP-specific Type 2 SSB at the earliest SSB occasion offset from the time of receiving the instruction to disable the TRP-specific Type 2 SSB.

[0415]

[0416] FIG. 21 illustrates the flow of a method performed by BS for SSB adaptation per TRP according to one embodiment.

[0417] Referring to FIG. 21, BS can transmit configuration information associated with at least one SSB(s) having a PCI value different from the serving cell PCI to support multiple TRP operations (intra-cell or inter-cell) in addition to the SSB for a specific serving cell in step 2105 to the UE.

[0418] Subsequently, BS may direct SSB adaptation by TRP index / CORESET pool index / PCI based on at least one of [Method #1-1] to [Method #1-4] described above. Specifically, BS may transmit a directive to disable a TRP-specific type 2 SSB as in step 2110.

[0419] Preferably, the UE receiving this does not perform operations related to the TRP-specific Type 2 SSB. That is, it does not perform measurements and reports linked to the TRP-specific Type 2 SSB.

[0420]

[0421] (2) RACH adaptation by TRP

[0422] Below, we propose a signaling method for RACH adaptation by intra-cell or inter-cell multiple TRP and a terminal operation that receives the signaling.

[0423] First, regarding signaling methods for RACH adaptation by TRP, [Method #2-]1 to [Method #2-4] can be considered as follows.

[0424] [Method #2-1] Method for including TRP-related information in RACH adaptation-related signaling via RRC / MAC-CE / DCI / LP-WUS

[0425] As with the example of RACH adaptation operation described above, RACH adaptation can be performed by (de)enabling Cat 2 RO. In this case, one or a combination of RRC / MAC-CE / DCI / LP-WUS may be used as the signaling to (de)enabling Cat 2 RO. By including TRP-related information (i.e., TRP index / CORESET pool index / PCI value) in the signaling (or by treating each TRP as if it were a single serving cell), TRP-specific Cat 2 RO (de)enabling signaling can be performed. In the following, DCI may refer to at least a paging DCI scrambled with P-RNTI, and may also apply to DCI scrambled with other RNTIs (e.g., a DCI scrambled with C-RNTI (PDCCH order to indicate CFRA (contention-free random access)) or a DCI scrambled with PEI-RNTI).

[0426] Example 1) The on / off (or enabled / disabled) status of a Cat 2 RO for each TRP (or TRP index / CORESET pool index / PCI) can be transmitted from a base station through RRC signaling. For example, a terminal that receives an RRC signal indicating that a Cat 2 RO corresponding to PCI #A set in a serving cell is in an off state or disabled can recognize that the Cat 2 RO corresponding to PCI #A SSB on the serving cell is not valid.

[0427] Example 2) A separate field can be created in MAC-CE / DCI / LP-WUS signaling that is distinguished by TRP (or TRP index / CORESET pool index / PCI). For example, if the nth bit or field within MAC-CE or DCI is predefined / configured or determined by a rule to be associated with TRP index k (or CORESET pool index k or PCI #k), the terminal can recognize that the Cat 2 RO corresponding to TRP index k (or CORESET pool index k or PCI #k) is turned on / off or enabled / disabled when it receives the Cat 2 RO on / off (or enabled / disabled) status / status through the corresponding nth bit or field. Alternatively, a specific field within MAC-CE / DCI / LP-WUS may indicate which TRP (or TRP index / CORESET pool index / PCI) it is, and a separate field may indicate the Cat 2 RO on / off (or enabled / disabled) status / status.

[0428] For example, when an additional PCI value is indicated through a PDCCH order DCI that triggers CFRA (contention-free random access) (e.g., a DCI in which the FDRA (frequency domain resource allocation) field of DCI format 1_0 scrambled with C-RNTI is composed entirely of 0s) (e.g., the 1 bit information of the PRACH association field is indicated as 1) and Cat 2 RO on (or Cat 2 RO enabled) is indicated through a separate 1-bit indicator, the terminal can recognize that the Cat 2 RO is valid among the ROs associated with the additional PCI.

[0429] As another example, when a serving cell PCI value is indicated through a PDCCH order DCI that triggers CFRA (e.g., a DCI in which the FDRA field of DCI format 1_0 scrambled with C-RNTI is composed entirely of 0s) (e.g., the 1 bit information of the PRACH association field is indicated as '0') and Cat 2 RO on (or Cat 2 RO activation) is indicated through a separate 1-bit indicator, the terminal can recognize that a Cat 2 RO is valid among the ROs associated with the serving cell PCI.

[0430] Example 3) Cat 2 RO (de)enable signaling per TRP (or TRP index / CORESET pool index / PCI) can be performed by a combination of RRC signaling and MAC-CE / DCI / LP-WUS signaling. For example, multiple Cat 2 RO setting indices can be set through RRC signaling, and each Cat 2 RO setting index can be linked to a TRP (or TRP index / CORESET pool index / PCI). Through MAC-CE / DCI / LP-WUS signaling, one of the Cat 2 RO setting indices may be indicated. For example, a Cat 2 RO configuration index #n is linked with a TRP index k (or CORESET pool index k or PCI #k) in advance via RRC signaling, and when the Cat 2 RO configuration index #n is indicated via MAC-CE / DCI / LP-WUS signaling, the terminal can recognize that the Cat 2 RO corresponding to the linked TRP index k (or CORESET pool index k or PCI #k) is turned on / off or enabled / disabled.

[0431] [Method #2-2] How to configure / instruct RACH adaptation of a TRP via CORESET pool index / DCI format / RNTI linked to the TRP

[0432] A base station may configure one or more CORESET pool indices / DCI formats / RNTIs and link one (or multiple) PCIs for each CORESET pool index / DCI format / RNTI. For example, if CORESET pool index #n and PCI #k are linked and a terminal receives a DCI through a CORESET belonging to CORESET pool index #n, the RACH adaptation information instructed / configured through that DCI (or the PDSCH scheduled by that DCI) can be applied to the Cat 2 RO linked to PCI #k. For another example, if DCI format #n and PCI #k are linked and a terminal receives DCI format #n, the RACH adaptation information instructed / configured through that DCI (or the PDSCH scheduled by that DCI) can be applied to the Cat 2 RO linked to PCI #k. As another example, when an RNTI value X and PCI #k are linked and a terminal receives a PDCCH (or PDSCH) scrambled with RNTI X, the RACH adaptation information instructed / set through the said PDCCH (or PDSCH) can be applied to a Cat 2 RO linked to PCI #k.

[0433] [Method #2-3] Method for setting / instructing the adaptation of an RO linked to a TRP using separate TRP adaptation signaling

[0434] One or a combination of RRC, MAC-CE, DCI, and LP-WUS may be used as a signaling to adapt, turn on / off, or (de)activate the TRP. When the association between TRP index n and PCI #k is predefined / configured or determined by a rule, the terminal can recognize that when it receives a signaling that TRP index n is turned on or activated (for a certain period of time), the Cat 2 RO (and Cat 1 RO) corresponding to the PCI #k associated with the TRP index n is activated (for a certain period of time), and conversely, when it receives a signaling that TRP index n is turned off or deactivated (for a certain period of time), the terminal can recognize that the Cat 2 RO (and Cat 1 RO) corresponding to the PCI #k associated with the TRP index n is deactivated (for a certain period of time).

[0435] [Method #2-4] A method to apply RACH adaptation to TRPs commonly or to specific TRPs only, without signaling for TRP-specific RACH adaptation, even in serving cells where Multi-TRP operation is configured / applied.

[0436] One or more TRP indexes / CORESET pool indexes / PCIs may be configured for a serving cell. When RACH adaptation is signaled for the said serving cell by one or a combination of RRC / MAC-CE / DCI / LP-WUS, the terminal may apply at least one of the following actions. Additionally, which of the following actions to apply may be configured separately. Furthermore, if there is no such separate configuration, a rule for which action to perform may be defined in advance.

[0437] - RACH adaptation can be applied commonly to Cat 2 ROs corresponding to all TRP indexes / CORESET pool indexes / PCIs configured in the corresponding serving cell. For example, if PCI #B is configured in addition to PCI #A for a serving cell, and Cat 2 RO (dis)activation is configured / instructed, the terminal may consider that both PCI #A and PCI #B are commonly Cat 2 RO (dis)activated.

[0438] - RACH adaptation can be applied only to the PCI set in the serving cell (not an additional PCI). For example, if PCI #B is set in addition to PCI #A for the serving cell, and Cat 2 RO (dis)enable is set / instructed, the terminal may consider that Cat 2 RO (dis)enabled only for PCI #A (and that the RO corresponding to PCI #B remains in a valid state without adaptation).

[0439] - RACH adaptation may be applied only to PCIs corresponding to specific TRP indexes / CORESET pool indexes / PCIs. Specifically, there may be TRP indexes / CORESET pool indexes / PCI(s) for which RACH adaptation is predefined / configured or separately configured. For example, for a serving cell configured with PCI #A, PCI #B, and PCI #C, RACH adaptation behavior for PCI #A and PCI #B may be pre-configured. In this case, if Cat 2 RO (dis)activation is configured / instructed, the terminal may consider that Cat 2 RO (dis)activation is enabled only for PCI #A and PCI #B (and that the RO corresponding to PCI #C remains in a valid state without adaptation).

[0440]

[0441] Additionally, when a terminal requests adaptation to Cat 2 RO via an uplink, one or more TRP indexes / CORESET pool indexes / PCIs may be linked for a single uplink signal / channel.

[0442] For example, if a specific PRACH preamble index (or PRACH time) and PCI #A are linked in advance, the terminal may transmit the PRACH preamble index (or PRACH belonging to the PRACH time) to request RACH adaptation for PCI #A, and may expect to receive a downlink signal / channel corresponding to the PRACH (e.g., PDCCH / PDSCH that directs / sets RACH adaptation for RAR or PCI #A).

[0443] As another example, if a specific PRACH preamble index (or PRACH time) and PCI #A and PCI #B are linked in advance, the terminal may transmit the PRACH preamble index (or PRACH belonging to the PRACH time) to request RACH adaptation for PCI #A and / or PCI #B, and may expect to receive a downlink signal / channel corresponding to the PRACH (e.g., PDCCH / PDSCH that directs / sets RACH adaptation for RAR or PCI #A / B).

[0444] Meanwhile, SSB adaptation and RACH adaptation can operate in conjunction. If a Type 2 SSB corresponding to a specific TRP index / CORESET pool index / PCI is turned off or disabled by signaling of RRC / MAC-CE / DCI / LP-WUS or a combination thereof, a Cat 2 RO corresponding to the same TRP index / CORESET pool index / PCI may also be determined to be invalid or disabled. Additionally, if a Type 2 SSB corresponding to a specific TRP index / CORESET pool index / PCI is turned on or enabled by signaling of RRC / MAC-CE / DCI / LP-WUS or a combination thereof, a Cat 2 RO corresponding to the same TRP index / CORESET pool index / PCI may also be determined to be valid or enabled.

[0445] FIG. 22 is a diagram illustrating the timing for performing RACH adaptation per TRP according to the present disclosure.

[0446] Referring to FIG. 22, when a terminal receives a signaling that activates a Cat 2 RO corresponding to a specific TRP index / CORESET pool index / PCI, RACH transmission from the corresponding Cat 2 RO may be possible from a specific point in time after the time of receiving the signaling. After receiving the Cat 2 RO activation instruction, the terminal may be able to transmit RACH from the first Cat 2 RO after T symbol / slot / msec, and the value of T may be a value that is predefined or set / instructed by the base station. In this case, the magnitude of T may vary per TRP or a specific value may be signaled (considering the case of non-ideal backhaul between TRPs).

[0447] For example, when a RACH adaptation corresponding to TRP #A is indicated / set through a DL signal / channel received from a CORESET corresponding to TRP #A (e.g., a CORESET belonging to CORESET pool index 0), the terminal may apply an alpha value as T. On the other hand, when a RACH adaptation corresponding to TRP #B is indicated / set through a DL signal / channel received from a CORESET corresponding to TRP #A (e.g., a CORESET belonging to CORESET pool index 0), (considering the case of non-ideal backhaul between TRPs), when performing a RACH adaptation operation corresponding to TRP #B, the terminal may apply an alpha+delta value as T (e.g., delta>0, where the delta value may be a predefined or set / instructed value) or the T value itself may be indicated / set through the corresponding DL signal / channel.

[0448] As another example, when a RACH adaptation corresponding to a certain TRP index / CORESET pool index / PCI (e.g., serving cell PCI) is indicated / set, the terminal applies an alpha value as T, and when a RACH adaptation corresponding to another TRP index / CORESET pool index / PCI (e.g., additional PCI) is indicated / set, an alpha+delta value (e.g., delta>0, where delta may be a predefined or set / instructed value) is applied as T, or the T value itself may be indicated / set through a DL signal / channel that sets / instructs the RACH adaptation.

[0449] Similarly, if a terminal receives a signal indicating that a Cat 2 RO corresponding to a specific TRP index / CORESET pool index / PCI is disabled, RACH transmission from the corresponding Cat 2 RO may not be allowed from a specific point in time after the time of receiving such signal. Specifically, the terminal can determine that RACH transmission is not allowed from the first Cat 2 RO after T2 symbols / slots / msec after receiving the Cat 2 RO disable instruction, and the corresponding T2 value may be a value predefined or set / instructed by the base station. Alternatively, the terminal may consider that it has been automatically disabled or turned off after T3 hours from the time of activation, and the corresponding T3 value may be a value predefined (per TRP index / CORESET pool index / PCI) or set by the base station. In this case, the magnitude of T2 may vary per TRP or a specific value may be signaled (considering cases of non-ideal backhaul between TRPs).

[0450] For example, when Cat 2 RO deactivation corresponding to TRP #A is indicated / set through a DL signal / channel received from a CORESET corresponding to TRP #A (e.g., a CORESET belonging to CORESET pool index 0), the terminal may apply the alpha2 value as T2. On the other hand, when RACH adaptation corresponding to TRP #B is indicated / set through a DL signal / channel received from a CORESET corresponding to TRP #A (e.g., a CORESET belonging to CORESET pool index 0), (considering the case of non-ideal backhaul between TRPs), when performing the Cat 2 RO deactivation operation corresponding to TRP #B, the terminal may apply the value alpha2+delta2 (e.g., delta2>0, where the delta2 value may be a predefined or set / instructed value) as T2, or the T2 value itself may be indicated / set through the corresponding DL signal / channel.

[0451] As another example, when Cat 2 RO disable corresponding to a certain TRP index / CORESET pool index / PCI (e.g., serving cell PCI) is instructed / set, the terminal applies the alpha2 value as T2, and when Cat 2 RO disable corresponding to another TRP index / CORESET pool index / PCI (e.g., additional PCI) is instructed / set, the alpha2+delta2 value (e.g., delta2>0, where delta2 may be a predefined or set / instructed value) is applied as T2, or the T2 value itself may be instructed / set through a DL signal / channel that sets / instructs Cat 2 RO disable.

[0452] If a PCI added to a serving cell PCI is configured, but the Cat 2 RO corresponding to the added PCI is disabled, the terminal may not perform the TRP operation associated with the added PCI. Here, not performing the TRP operation associated with the added PCI may include at least one of the following terminal operations. Additionally, whether or not to perform the following operations may be predefined or separately configured.

[0453] - In the case of a DL / UL signal / channel where an added PCI SSB is set as a QCL RS (or when examining the QCL relationships set / instructed for a specific DL / UL signal channel and following the QCL RSs linked to the QCL RS, the additional PCI SSB is found to be set / instructed as a QCL RS), reception / transmission for the DL / UL signal / channel is not performed. Or, if there is a DL / UL signal / channel where an added PCI SSB is indicated as a QCL RS (or when examining the QCL relationships set for a specific DL / UL signal channel and following the QCL RSs linked to the QCL RS, the additional PCI SSB is found to be indicated as a QCL RS), the terminal may not expect the PCI SSB to be disabled.

[0454] - Omit measurements and reporting for added PCIs (e.g., L1 measurements for L1-RSRP / L1-SINR, L3 RRM measurements for RSRP / RSRP, radio link monitoring, beam failure detection / recovery).

[0455] - PDCCH monitoring in CORESETs belonging to CORESET pool indexes linked to added PCIs is not performed, or DL / UL scheduling information is ignored even if PDCCH is detected in the CORESET.

[0456] - Does not perform HARQ-ACK codebook configuration / feedback corresponding to CORESET pool indexes linked to added PCIs.

[0457]

[0458]

[0459] FIG. 23 is a diagram illustrating the operation of UE and BS for RACH adaptation per TRP according to one embodiment.

[0460] Referring to FIG. 23, the UE may receive configuration information from the BS in addition to the SSB for a specific serving cell in step 2305, which includes at least one SSB(s) having a PCI value different from the serving cell PCI to support multiple TRP operations (intra-cell or inter-cell).

[0461] Next, the UE may receive from the BS information regarding Cat 1 ROs and Cat 2 ROs associated with the SSB of the serving cell PCI (i.e., legacy SSB) in step 2310, and information regarding Cat 1 ROs and Cat 2 ROs associated with the SSB of the additional PCI (e.g., TRP-specific type 2 SSB). The two pieces of information may be received separately or together.

[0462] Subsequently, based on at least one of the above-described [Method #2-1] to [Method #2-4], RACH adaptation per TRP index / CORESET pool index / PCI (i.e., activation of a Cat 2 RO linked to an SSB of an added PCI or a TRP-specific Type 2 SSB) may be indicated. Specifically, an instruction to activate a Cat 2 RO linked to an SSB of an added PCI (or a TRP-specific Type 2 SSB) may be received as in step 2315.

[0463] Finally, in step 2320, the UE can perform a PRACH transmission to the BS based on the Cat 2 RO associated with the added PCI's SSB (or TRP-specific Type 2 SSB). In particular, the PRACH transmission can be performed on the earliest RO after the offset from the time of receiving the activation instruction for the Cat 2 RO.

[0464] FIG. 24 illustrates the flow of a method performed by a UE for RACH adaptation per TRP according to one embodiment.

[0465] Referring to FIG. 24, in step 2405, the UE may receive configuration information associated with at least one SSB(s) having a PCI value different from the serving cell PCI to support multiple TRP operations (intra-cell or inter-cell) in addition to the SSB for a specific serving cell.

[0466] Next, in step 2410, the UE may receive information related to Cat 1 ROs and Cat 2 ROs associated with the SSB of the serving cell PCI (i.e., legacy SSB), and information related to Cat 1 ROs and Cat 2 ROs associated with the SSB of the additional PCI (e.g., TRP-specific type 2 SSB). The two pieces of information may be received separately or together.

[0467] Subsequently, at step 2415, the UE may receive instructions for RACH adaptation per TRP index / CORESET pool index / PCI (i.e., activation of Cat 2 RO linked to the SSB of the added PCI (or TRP-specific Type 2 SSB)) based on at least one of [Method #2-1] to [Method #2-4] described above. Specifically, as in step 2415, the UE may receive instructions for activation of Cat 2 RO linked to the SSB of the added PCI (or TRP-specific Type 2 SSB).

[0468] Finally, in step 2420, the UE can perform a PRACH transmission based on a Cat 2 RO associated with an added PCI SSB (or a TRP-specific Type 2 SSB). In particular, the UE can perform a PRACH transmission on the earliest RO after an offset from the time of receiving the activation instruction for the Cat 2 RO.

[0469]

[0470] FIG. 25 illustrates the flow of a method performed by BS for RACH adaptation per TRP according to one embodiment.

[0471] Referring to FIG. 25, in addition to the SSB for a specific serving cell in step 2505, BS can transmit configuration information associated with at least one SSB(s) having a PCI value different from the serving cell PCI to support multiple TRP operations (intra-cell or inter-cell).

[0472] Next, BS can transmit information related to Cat 1 ROs and Cat 2 ROs associated with the SSB of the serving cell PCI (i.e., legacy SSB) in step 2510, and information related to Cat 1 ROs and Cat 2 ROs associated with the SSB of the additional PCI (e.g., TRP-specific type 2 SSB). The two pieces of information may be transmitted separately or together.

[0473] Subsequently, at step 2515, BS may transmit instructions for RACH adaptation per TRP index / CORESET pool index / PCI (i.e., activation of Cat 2 RO linked to the SSB of the added PCI (or TRP-specific type 2 SSB)) based on at least one of [Method #2-1] to [Method #2-4] described above. Specifically, as in step 2515, BS may transmit instructions for activation of Cat 2 RO linked to the SSB of the added PCI (or TRP-specific type 2 SSB).

[0474] Finally, in step 2520, the BS can receive the PRACH transmitted based on the Cat 2 RO associated with the added PCI's SSB (or TRP-specific Type 2 SSB). In particular, the PRACH can be received from the earliest RO after the offset from the time of transmission of the Cat 2 RO's enable instruction.

[0475]

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

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

[0478] 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 UE (User Equipment), A step of receiving configuration information related to at least one SSB (synchronization signal block) for at least one TRP among a plurality of TRPs from a BS (Base station); and Based on the above setting information being related to the activation of the at least one SSB, the method comprises the step of monitoring the at least one SSB for the at least one TRP. method.

2. In Paragraph 1, Based on the fact that the above configuration information relates to the deactivation of the at least one SSB, the step of stopping the monitoring of the at least one SSB for the at least one TRP, method.

3. In Paragraph 1, The step of monitoring the at least one SSB for the at least one TRP is A step comprising monitoring the at least one SSB for the at least one TRP at the earliest SSB time (occasion) after the offset from the time of receiving configuration information related to the at least one SSB, method.

4. In Paragraph 1, Based on the above setting information being related to the activation of at least one SSB, it is determined that at least one RO (RACH occasion) associated with the at least one SSB is valid, and Based on the above setting information relating to the deactivation of the at least one SSB, the at least one RO associated with the at least one SSB is determined to be invalid, method.

5. In Paragraph 4, A method further comprising the step of transmitting a PRACH (Physical Random Access Channel) to the BS based on at least one RO determined to be valid. method.

6. In Paragraph 4, The method further comprises the step of receiving information regarding at least one RO associated with the above at least one SSB. method.

7. In Paragraph 1, Configuration information related to at least one SSB for the above at least one TRP is, Information including the activation or deactivation of at least one RO associated with the above at least one SSB, method.

8. In Paragraph 1, Configuration information related to at least one SSB for the above at least one TRP is, Comprising at least one of a PCI (Physical Cell Identifier) ​​associated with the at least one TRP, carrier information associated with the at least one second TRP, BWP (bandwidth part) information associated with the at least one TRP, or a CORESET (Control Resource Set) pool index associated with the at least one TRP, method.

9. In Paragraph 1, Configuration information related to at least one SSB for the above at least one TRP is, Received based on a CORESET (Control Resource Set) pool associated with the PCI (Physical Cell Identifier) ​​of at least one TRP or an RNTI (Radio Network Temporary Identifier) ​​associated with the PCI of at least one TRP, method.

10. In Paragraph 1, Configuration information related to at least one SSB for the at least one TRP is included in information for activating or deactivating the at least one TRP, and Information for activating or deactivating the above at least one TRP is received based on at least one of RRC (radio resource control) signaling, MAC (medium access control) CE (control element) signaling, or DCI (Downlink Control Information). method.

11. In Paragraph 1, The step of monitoring the at least one SSB for the at least one TRP is Based on the above setting information being related to the activation of at least one SSB, the method comprises the step of monitoring SSBs for each of the plurality of TRPs. method.

12. In Paragraph 1, The above at least one SSB includes an OD (on-demand) SSB, and Configuration information related to the above at least one SSB is received based on at least one of RRC (radio resource control) signaling, MAC (medium access control) CE (control element) signaling, or DCI (Downlink Control Information), method.

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

14. Regarding the device, At least one processor; and It includes at least one memory configured to store instructions that perform operations by being executed by the above at least one processor, and The above operations are, A step of receiving configuration information related to at least one SSB (synchronization signal block) for at least one TRP among a plurality of TRPs from a BS (Base station); and Based on the above setting information being related to the activation of the at least one SSB, the method comprises the step of monitoring the at least one SSB for the at least one TRP. machinery and tools.

15. In Paragraph 14, The above device further includes a transmitter and receiver, and The above device is a UE (User Equipment), machinery and tools.

16. In Paragraph 14, The above device is a processing device configured to control UE (User Equipment), machinery and tools.

17. In a method performed by the BS (Base Station), A step of transmitting configuration information related to at least one SSB (synchronization signal block) for at least one TRP among a plurality of TRPs (Transmission and Reception Points) to a UE (User Equipment); and Based on the fact that the above configuration information relates to the activation of the at least one SSB, the method comprises the step of transmitting the at least one SSB for the at least one TRP to the UE. method.

18. At the BS (Base Station), At least one processor; and It includes at least one memory configured to store instructions that perform operations by being executed by the above at least one processor, and The above operations are, A step of transmitting configuration information related to at least one SSB (synchronization signal block) for at least one TRP among a plurality of TRPs (Transmission and Reception Points) to a UE (User Equipment); and Based on the fact that the above configuration information relates to the activation of the at least one SSB, the method comprises the step of transmitting the at least one SSB for the at least one TRP to the UE. BS.

Images