Method and device for determining transmission power in TRP system
The method for determining uplink transmission power in TRP systems using closed loop power control adjustment states addresses inefficiencies in power consumption and interference, enhancing communication performance by optimizing power control.
Patent Information
- Application Number
- PCT/KR2025/004741
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-04-15
- Filing Date
- 2025-04-08
- Publication Date
- 2025-10-23
AI Technical Summary
In asymmetric TRP systems, terminals face increased power consumption and interference due to suboptimal uplink transmission power determination, particularly when communicating with a second TRP using path loss considerations from a first TRP, leading to inefficient power control.
A method for determining uplink transmission power in a communication system supporting multiple TRPs, involving the reception of messages indicating supported closed loop power control adjustment states and using associated power control information to set transmission power for each TRP, enabling efficient power control and reduced interference.
This approach allows for efficient power control in TRP systems, reducing interference and power waste, and improving communication performance by optimizing transmission power based on closed loop power control.
Smart Images

Figure KR2025004741_23102025_PF_FP_ABST
Abstract
Description
Method and device for determining transmission power in a TRP system
[0001] The present disclosure relates to improved communication technologies, and more particularly, to a technique for determining uplink (UL) transmission power in a communication system supporting one or more transmission and reception points (TRPs).
[0002] Communication networks (e.g., 5G communication networks, 6G communication networks, etc.) are being developed to provide improved communication services compared to existing communication networks (e.g., long term evolution (LTE), advanced LTE-A (LTE-A), etc.). 5G communication networks (e.g., new radio (NR) communication networks) can support frequency bands above 6 GHz as well as frequency bands below 6 GHz. That is, 5G communication networks can support FR1 bands and / or FR2 bands. 5G communication networks can support various communication services and scenarios compared to LTE communication networks. For example, usage scenarios of 5G communication networks can include enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communication (URLLC), massive Machine Type Communication (mMTC), etc.
[0003] Compared to 5G, 6G communication networks can support a wider range of communication services and scenarios. 6G communication networks can meet requirements for ultra-high performance, ultra-high bandwidth, ultra-high space, ultra-high precision, ultra-intelligence, and / or ultra-reliability. 6G communication networks can support diverse and wide frequency bands and be applied to various usage scenarios (e.g., terrestrial communications, non-terrestrial communications, sidelink communications, etc.).
[0004] Meanwhile, multiple transmission and reception points (mTRPs) can be introduced into communication networks (e.g., 5G and / or 6G). mTRPs can be geographically separated. Base stations can use mTRPs to communicate with terminals. mTRP technology can be used to address quality of service (QoS) degradation issues for cell-edge terminals and / or inter-cell interference issues. mTRP technology can also be used to provide additional communication paths in environments where non-line-of-sight (NLOS) paths are limited.
[0005] mTRP-based communication can be performed based on either the coherent joint transmission (CJT) scheme or the non-CJT (NCJT) scheme. In the CJT scheme, mTRP can perform cooperative communication based on a stable backhaul link and provide synchronized communication services to terminals. In the NCJT scheme, mTRP can provide communication services to terminals without cooperation. For example, in the NCJT scheme, mTRP can perform scheduling operations, precoding matrix selection operations, and modulation and coding scheme (MCS) determination operations without cooperation.
[0006] In an asymmetric TRP system, a terminal may perform DL (downlink) communication with an sTRP, and a terminal may perform UL (uplink) communication with an mTRP. The terminal may perform DL (downlink) communication with a first TRP supporting a macro cell, and the terminal may perform UL (uplink) communication with a second TRP supporting a micro cell. When the terminal performs UL communication with the second TRP using a transmission power determined by considering a path loss in the link between the terminal and the first TRP, the power consumption of the terminal may increase, and interference caused by the UL communication may increase. A method for determining the transmission power to solve the above problem may be needed. In addition, methods for controlling (e.g., determining) the transmission power based on a closed loop (CL) in the TRP system may be needed.
[0007] An object of the present disclosure to solve the above problems is to provide a method and device for determining UL (uplink) transmission power in a communication system supporting one or more transmission and reception points (TRPs).
[0008] According to embodiments of the present disclosure for achieving the above object, a method of a user equipment (UE) includes the steps of: receiving a first message from a base station including information indicating that a plurality of closed loop power control (CLPC) adjustment states are supported; receiving a second message from the base station including information indicating first power control information associated with a first CLPC adjustment state among the plurality of CLPC adjustment states; determining a first transmission power based on the first power control information; and transmitting a first uplink (UL) transmission to a first transmission and reception point (TRP) associated with the first CLPC adjustment state using the first transmission power.
[0009] The first message may include at least one of an index of each of the plurality of CLPC adjustment states, power control information of each of the plurality of CLPC adjustment states, information indicating that two transmit power control (TPC) commands are set in the second message for the plurality of CLPC adjustment states, mapping information between the plurality of CLPC adjustment states and a plurality of transmission configuration indicator (TCI) states, mapping information between the plurality of CLPC adjustment states and a plurality of sounding reference signal (SRS) resource sets, or mapping information between the plurality of CLPC adjustment states and a plurality of control resource sets (CORESETs).
[0010] The first power control information may include at least one of a first CL (closed loop) index or a first TPC command.
[0011] The above first CL index may be a CL index for an SRS associated with TCI status information included in the second message.
[0012] The second message may further include information indicating second power control information associated with a second CLPC regulation state among the plurality of CLPC regulation states.
[0013] The method of the UE may further include: determining a second transmission power based on the second power control information; and transmitting a second UL transmission to a second TRP associated with the second CLPC adjustment state using the second transmission power.
[0014] The above first UL transmission may be at least one of a physical uplink control channel (PUCCH) transmission, a physical uplink shared channel (PUSCH) transmission, or an SRS transmission.
[0015] The first message may be an RRC (radio resource control) message, and the second message may be DCI (downlink control information).
[0016] According to embodiments of the present disclosure for achieving the above object, a method of a base station includes the steps of: transmitting to a user equipment (UE) a first message including information indicating that a plurality of closed loop power control (CLPC) adjustment states are supported; and transmitting to the UE a second message including information indicating first power control information associated with a first CLPC adjustment state among the plurality of CLPC adjustment states, wherein a first transmission power determined based on the first power control information is used for a first uplink (UL) transmission for a first transmission and reception point (TRP) associated with the first CLPC adjustment state.
[0017] The first message may include at least one of an index of each of the plurality of CLPC adjustment states, power control information of each of the plurality of CLPC adjustment states, information indicating that two transmit power control (TPC) commands are set in the second message for the plurality of CLPC adjustment states, mapping information between the plurality of CLPC adjustment states and a plurality of transmission configuration indicator (TCI) states, mapping information between the plurality of CLPC adjustment states and a plurality of sounding reference signal (SRS) resource sets, or mapping information between the plurality of CLPC adjustment states and a plurality of control resource sets (CORESETs).
[0018] The first power control information may include at least one of a first CL (closed loop) index or a first TPC command.
[0019] The above first CL index may be a CL index for an SRS associated with TCI status information included in the second message.
[0020] The second message may further include information indicating second power control information associated with a second CLPC regulation state among the plurality of CLPC regulation states.
[0021] The second transmission power determined based on the second power control information can be used for a second UL transmission for a second TRP associated with the second CLPC adjustment state.
[0022] According to embodiments of the present disclosure for achieving the above object, a user equipment (UE) includes at least one processor, wherein the at least one processor causes the UE to receive a first message from a base station, the first message including information indicating that a plurality of closed loop power control (CLPC) adjustment states are supported; receive a second message from the base station, the second message including information indicating first power control information associated with a first CLPC adjustment state among the plurality of CLPC adjustment states; determine a first transmission power based on the first power control information; and transmit a first uplink (UL) transmission to a first transmission and reception point (TRP) associated with the first CLPC adjustment state using the first transmission power.
[0023] The first message may include at least one of an index of each of the plurality of CLPC adjustment states, power control information of each of the plurality of CLPC adjustment states, information indicating that two transmit power control (TPC) commands are set in the second message for the plurality of CLPC adjustment states, mapping information between the plurality of CLPC adjustment states and a plurality of transmission configuration indicator (TCI) states, mapping information between the plurality of CLPC adjustment states and a plurality of sounding reference signal (SRS) resource sets, or mapping information between the plurality of CLPC adjustment states and a plurality of control resource sets (CORESETs).
[0024] The first power control information may include at least one of a first CL (closed loop) index or a first TPC command.
[0025] The above first CL index may be a CL index for an SRS associated with TCI status information included in the second message.
[0026] The second message may further include information indicating second power control information associated with a second CLPC regulation state among the plurality of CLPC regulation states.
[0027] The at least one processor may further cause the UE to determine a second transmit power based on the second power control information; and transmit a second UL transmission on a second TRP associated with the second CLPC adjustment state using the second transmit power.
[0028] According to the present disclosure, a user equipment (UE) can receive configuration information for a plurality of closed loop power control (CLPC) adjustment states from a base station, and can receive a message including power control information associated with one of the plurality of CLPC adjustment states from the base station. The UE can determine transmission power based on the power control information, and can perform uplink (UL) communication with a transmission and reception point (TRP) associated with one of the CLPC adjustment states using the transmission power. Based on the above-described operations, a closed loop (CL)-based power control operation in a TRP system can be efficiently performed, interference problems and / or power waste problems due to the use of high transmission power can be resolved, and the problem of communication performance degradation due to the use of low transmission power can be resolved. Therefore, the performance of a communication system (e.g., a TRP system) can be improved.
[0029] Figure 1 is a conceptual diagram illustrating embodiments of a communication system.
[0030] Figure 2 is a block diagram illustrating embodiments of communication nodes constituting a communication system.
[0031] Figure 3 is a block diagram illustrating embodiments of communication nodes that perform communication.
[0032] Figure 4a is a block diagram illustrating embodiments of a transmission path.
[0033] Figure 4b is a block diagram illustrating embodiments of a receiving path.
[0034] Figure 5 is a conceptual diagram illustrating embodiments of system frames in a communication system.
[0035] Figure 6 is a conceptual diagram illustrating embodiments of subframes in a communication system.
[0036] Figure 7 is a conceptual diagram illustrating embodiments of slots in a communication system.
[0037] Figure 8 is a conceptual diagram illustrating embodiments of time-frequency resources in a communication system.
[0038] Figure 9 is a conceptual diagram illustrating an embodiment of an asymmetric TRP system.
[0039] FIG. 10 is a conceptual diagram illustrating embodiments of a power parameter list including a path loss offset.
[0040] FIG. 11a is a conceptual diagram illustrating embodiments of MAC CE for activating a TCI state of a joint type.
[0041] FIG. 11b is a conceptual diagram illustrating embodiments of MAC CE for activating independent type TCI states.
[0042] FIG. 12a is a conceptual diagram illustrating embodiments of MAC CE for activating a TCI state of a joint type.
[0043] FIG. 12b is a conceptual diagram illustrating embodiments of MAC CE for activating independent type TCI states.
[0044] FIG. 13 is a flowchart illustrating embodiments of a UL communication method in an asymmetric TRP system.
[0045] Figure 14 is a flowchart illustrating embodiments of a UL communication method in a TRP system.
[0046] This disclosure may be subject to various modifications and various embodiments. Specific embodiments are illustrated and described in detail in the drawings. However, this is not intended to limit the disclosure to specific embodiments, but rather to encompass all modifications, equivalents, and alternatives falling within the spirit and technical scope of the disclosure.
[0047] While terms such as "first" and "second" may be used to describe various components, these components should not be limited by these terms. These terms are used solely to distinguish one component from another. For example, without departing from the scope of the present disclosure, a first component could be referred to as a "second component," and similarly, a second component could also be referred to as a "first component." The term "and / or" may refer to a combination of multiple related items described herein or to any of multiple related items described herein.
[0048] In the present disclosure, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B.” Additionally, in the present disclosure, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B.”
[0049] In the present disclosure, (re)transmission may mean “transmission,” “retransmission,” or “transmission and retransmission,” (re)setting may mean “setting,” “resetting,” or “setting and resetting,” (re)connection may mean “connection,” “reconnection,” or “connection and reconnection,” and (re)connection may mean “connection,” “reconnection,” or “connection and reconnection.”
[0050] When a component is referred to as being "connected" or "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but that there may be other components intervening. Conversely, when a component is referred to as being "directly connected" or "connected" to another component, it should be understood that there are no other components intervening.
[0051] The terminology used in this disclosure is only used to describe specific embodiments and is not intended to limit the present disclosure. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this disclosure, it should be understood that the terms "comprises" or "has" indicate the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, but do not preclude the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.
[0052] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which this disclosure pertains. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined herein.
[0053] Hereinafter, preferred embodiments of the present disclosure will be described in more detail with reference to the attached drawings. In order to facilitate an overall understanding in describing the present disclosure, the same reference numerals will be used for identical components in the drawings, and redundant descriptions of identical components will be omitted. In addition to the embodiments explicitly described in the present disclosure, operations may be performed according to combinations of embodiments, extensions of embodiments, and / or modifications of embodiments. The performance of some operations may be omitted, and the order of operation may be changed.
[0054] In an embodiment, even if a method (e.g., transmitting or receiving a signal) performed by a first communication node among communication nodes is described, a corresponding second communication node can perform a method (e.g., receiving or transmitting a signal) corresponding to the method performed by the first communication node. That is, if an operation of a UE (user equipment) is described, a corresponding base station can perform an operation corresponding to the operation of the UE. Conversely, if an operation of a base station is described, a corresponding UE can perform an operation corresponding to the operation of the base station.
[0055] A base station may be referred to as a NodeB, an evolved NodeB, a gNodeB (next generation node B), a gNB, a device, an apparatus, a node, a communication node, a BTS (base transceiver station), a RRH (radio remote head), a TRP (transmission reception point), a RU (radio unit), an RSU (road side unit), a radio transceiver, an access point, an access node, etc. A UE may be referred to as a terminal, a device, an apparatus, a node, a communication node, an end node, an access terminal, a mobile terminal, a station, a subscriber station, a mobile station, a portable subscriber station, an OBU (on-broad unit), etc.
[0056] In the present disclosure, signaling may be at least one of upper layer signaling, MAC signaling, or PHY (physical) signaling. A message used for upper layer signaling may be referred to as an "upper layer message" or an "upper layer signaling message." A message used for MAC signaling may be referred to as a "MAC message" or a "MAC signaling message." A message used for PHY signaling may be referred to as a "PHY message" or a "PHY signaling message." Upper layer signaling may refer to a transmission and reception operation of system information (e.g., a master information block (MIB), a system information block (SIB)) and / or a radio resource control (RRC) message. MAC signaling may refer to a transmission and reception operation of a MAC control element (CE). PHY signaling may refer to a transmission and reception operation of control information (e.g., downlink control information (DCI), uplink control information (UCI), sidelink control information (SCI)). For convenience, the signaling message may be referred to as a first signaling message (e.g., the first message), a second signaling message (e.g., the second message), a third signaling message (e.g., the third message), etc.
[0057] In the present disclosure, “an operation (e.g., a transmission operation) is set” may mean that “setting information for the operation (e.g., an information element, a parameter)” and / or “information instructing the performance of the operation” is signaled. “An information element (e.g., a parameter) is set” may mean that the information element is signaled. In the present disclosure, “a signal and / or a channel” may mean a signal, a channel, or “a signal and a channel,” and a signal may be used to mean “a signal and / or a channel.”
[0058] The communication network to which the embodiment is applied is not limited to what is described below, and the embodiment may be applied to various communication networks (e.g., 4G communication networks, 5G communication networks, and / or 6G communication networks). Here, the communication network may be used in the same sense as the communication system.
[0059] Figure 1 is a conceptual diagram illustrating embodiments of a communication system.
[0060] Referring to FIG. 1, the communication system (100) may include a plurality of communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6). In addition, the communication system (100) may further include a core network (e.g., a serving-gateway (S-GW), a packet data network (PDN)-gateway (P-GW), a mobility management entity (MME)). If the communication system (100) is a 5G communication system (e.g., a new radio (NR) system), the core network may include an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), etc.
[0061] A plurality of communication nodes (110 to 130) can support a communication protocol (e.g., LTE communication protocol, LTE-A communication protocol, NR communication protocol, etc.) specified in the 3GPP (3rd generation partnership project) standard. The plurality of communication nodes (110 to 130) may support CDMA (code division multiple access) technology, WCDMA (wideband CDMA) technology, TDMA (time division multiple access) technology, FDMA (frequency division multiple access) technology, OFDM (orthogonal frequency division multiplexing) technology, Filtered OFDM technology, CP (cyclic prefix)-OFDM technology, DFT-s-OFDM (discrete Fourier transform-spread-OFDM) technology, OFDMA (orthogonal frequency division multiple access) technology, SC (single carrier)-FDMA technology, NOMA (non-orthogonal multiple access) technology, GFDM (generalized frequency division multiplexing) technology, FBMC (filter bank multi-carrier) technology, UFMC (universal filtered multi-carrier) technology, SDMA (space division multiple access) technology, etc. Each of the plurality of communication nodes may have the following structure.
[0062] Figure 2 is a block diagram illustrating embodiments of communication nodes constituting a communication system.
[0063] Referring to FIG. 2, a communication node (200) may include at least one processor (210), a memory (220), and a transmission / reception device (230) that is connected to a network and performs communication. In addition, the communication node (200) may further include an input interface device (240), an output interface device (250), a storage device (260), etc. Each component included in the communication node (200) may be connected by a bus (270) and communicate with each other.
[0064] The processor (210) can execute program commands stored in at least one of the memory (220) and the storage device (260). The processor (210) may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor in which the methods according to embodiments of the present disclosure are performed. Each of the memory (220) and the storage device (260) may be configured with at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory (220) may be configured with at least one of a read-only memory (ROM) and a random access memory (RAM).
[0065] Referring again to FIG. 1, the communication system (100) may include a plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) and a plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6). Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) may form a macro cell. Each of the fourth base station (120-1) and the fifth base station (120-2) may form a small cell. The fourth base station (120-1), the third terminal (130-3), and the fourth terminal (130-4) may be within the cell coverage of the first base station (110-1). The second terminal (130-2), the fourth terminal (130-4), and the fifth terminal (130-5) may be within the cell coverage of the second base station (110-2). The fifth base station (120-2), the fourth terminal (130-4), the fifth terminal (130-5), and the sixth terminal (130-6) may be within the cell coverage of the third base station (110-3). The first terminal (130-1) may be within the cell coverage of the fourth base station (120-1). The sixth terminal (130-6) may be within the cell coverage of the fifth base station (120-2).
[0066] Here, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be referred to as a NodeB (NB), an evolved NodeB (eNB), a gNB, an advanced base station (ABS), a high reliability-base station (HR-BS), a base transceiver station (BTS), a radio base station, a radio transceiver, an access point, an access node, a radio access station (RAS), a mobile multihop relay-base station (MMR-BS), a relay station (RS), an advanced relay station (ARS), a high reliability-relay station (HR-RS), a home NodeB (HNB), a home eNodeB (HeNB), a road side unit (RSU), a radio remote head (RRH), a transmission point (TP), a transmission and reception point (TRP), etc.
[0067] Each of the plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) may be referred to as a user equipment (UE), terminal equipment (TE), advanced mobile station (AMS), high reliability-mobile station (HR-MS), terminal, access terminal, mobile terminal, station, subscriber station, mobile station, portable subscriber station, node, device, on board unit (OBU), etc.
[0068] Meanwhile, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may operate in a different frequency band or may operate in the same frequency band. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to each other via an ideal backhaul link or a non-ideal backhaul link, and may exchange information with each other via the ideal backhaul link or the non-ideal backhaul link. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to the core network via the ideal backhaul link or the non-ideal backhaul link. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit a signal received from the core network to the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6), and can transmit a signal received from the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) to the core network.
[0069] Additionally, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may support MIMO transmission (e.g., single user (SU)-MIMO, multi user (MU)-MIMO, massive MIMO, etc.), coordinated multipoint (CoMP) transmission, carrier aggregation (CA) transmission, transmission in an unlicensed band, sidelink communication (e.g., device to device communication (D2D), proximity services (ProSe)), Internet of Things (IoT) communication, dual connectivity (DC), etc. Here, each of the plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) can perform an operation corresponding to the base station (110-1, 110-2, 110-3, 120-1, 120-2) and an operation supported by the base station (110-1, 110-2, 110-3, 120-1, 120-2). For example, the second base station (110-2) can transmit a signal to the fourth terminal (130-4) based on the SU-MIMO scheme, and the fourth terminal (130-4) can receive a signal from the second base station (110-2) by the SU-MIMO scheme. Alternatively, the second base station (110-2) can transmit signals to the fourth terminal (130-4) and the fifth terminal (130-5) based on the MU-MIMO method, and each of the fourth terminal (130-4) and the fifth terminal (130-5) can receive signals from the second base station (110-2) based on the MU-MIMO method.
[0070] Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can transmit a signal to the fourth terminal (130-4) based on the CoMP scheme, and the fourth terminal (130-4) can receive a signal from the first base station (110-1), the second base station (110-2), and the third base station (110-3) based on the CoMP scheme. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit and receive a signal with terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) within its cell coverage based on the CA scheme. Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can control sidelink communication between the fourth terminal (130-4) and the fifth terminal (130-5), and each of the fourth terminal (130-4) and the fifth terminal (130-5) can perform sidelink communication under the control of the second base station (110-2) and the third base station (110-3), respectively.
[0071] Meanwhile, communication nodes performing communication in a communication network may be configured as follows. The communication node illustrated in Fig. 3 may be a specific embodiment of the communication node illustrated in Fig. 2.
[0072] Figure 3 is a block diagram illustrating embodiments of communication nodes that perform communication.
[0073] Referring to FIG. 3, each of the first communication node (300a) and the second communication node (300b) may be a base station or a UE. The first communication node (300a) may transmit a signal to the second communication node (300b). The transmission processor (311) included in the first communication node (300a) may receive data (e.g., a data unit) from a data source (310). The transmission processor (311) may receive control information from the controller (316). The control information may include at least one of system information, RRC configuration information (e.g., information configured by RRC signaling), MAC control information (e.g., MAC CE), or PHY control information (e.g., DCI, SCI).
[0074] The transmitting processor (311) may perform a processing operation on data (e.g., an encoding operation, a symbol mapping operation, etc.) to generate data symbol(s). The transmitting processor (311) may perform a processing operation on control information (e.g., an encoding operation, a symbol mapping operation, etc.) to generate control symbol(s). In addition, the transmitting processor (311) may generate synchronization / reference symbol(s) for a synchronization signal and / or a reference signal.
[0075] The Tx MIMO processor (312) may perform a spatial processing operation (e.g., a precoding operation) on data symbol(s), control symbol(s), and / or synchronization / reference symbol(s). The output (e.g., a symbol stream) of the Tx MIMO processor (312) may be provided to modulators (MODs) included in the transceivers (313a to 313t). The modulators (MODs) may perform a processing operation on the symbol stream to generate modulation symbols, and may perform an additional processing operation (e.g., an analog conversion operation, an amplification operation, a filtering operation, an upconversion operation) on the modulation symbols to generate signals. The signals generated by the modulators (MODs) of the transceivers (313a to 313t) may be transmitted via the antennas (314a to 314t).
[0076] Signals transmitted by the first communication node (300a) may be received by antennas (364a to 364r) of the second communication node (300b). Signals received by the antennas (364a to 364r) may be provided to demodulators (DEMODs) included in transceivers (363a to 363r). The demodulator (DEMOD) may perform a processing operation (e.g., a filtering operation, an amplification operation, a downconversion operation, a digital conversion operation) on the signal to obtain samples. The demodulator (DEMOD) may perform an additional processing operation on the samples to obtain symbols. The MIMO detector (362) may perform a MIMO detection operation on the symbols. The receiving processor (361) may perform a processing operation (e.g., a deinterleaving operation, a decoding operation) on the symbols. The output of the receiving processor (361) may be provided to a data sink (360) and a controller (366). For example, data may be provided to the data sink (360), and control information may be provided to the controller (366).
[0077] Meanwhile, the second communication node (300b) can transmit a signal to the first communication node (300a). The transmitting processor (368) included in the second communication node (300b) can receive data (e.g., data units) from a data source (367) and perform a processing operation on the data to generate data symbol(s). The transmitting processor (368) can receive control information from the controller (366) and perform a processing operation on the control information to generate control symbol(s). In addition, the transmitting processor (368) can perform a processing operation on a reference signal to generate reference symbol(s).
[0078] The Tx MIMO processor (369) may perform spatial processing operations (e.g., precoding operations) on data symbol(s), control symbol(s), and / or reference symbol(s). The output (e.g., symbol stream) of the Tx MIMO processor (369) may be provided to modulators (MODs) included in the transceivers (363a to 363t). The modulators (MODs) may perform processing operations on the symbol streams to generate modulation symbols, and may perform additional processing operations (e.g., analog conversion operations, amplification operations, filtering operations, upconversion operations) on the modulation symbols to generate signals. The signals generated by the modulators (MODs) of the transceivers (363a to 363t) may be transmitted via the antennas (364a to 364t).
[0079] Signals transmitted by the second communication node (300b) may be received by the antennas (314a to 314r) of the first communication node (300a). The signals received by the antennas (314a to 314r) may be provided to demodulators (DEMODs) included in the transceivers (313a to 313r). The demodulator (DEMOD) may perform a processing operation (e.g., a filtering operation, an amplification operation, a downconversion operation, a digital conversion operation) on the signal to obtain samples. The demodulator (DEMOD) may perform an additional processing operation on the samples to obtain symbols. The MIMO detector (320) may perform a MIMO detection operation on the symbols. The receiving processor (319) may perform a processing operation (e.g., a deinterleaving operation, a decoding operation) on the symbols. The output of the receiving processor (319) may be provided to a data sink (318) and a controller (316). For example, data may be provided to the data sink (318) and control information may be provided to the controller (316).
[0080] Memories (315 and 365) can store data, control information, and / or program code. Scheduler (317) can perform scheduling operations for communication. The processors (311, 312, 319, 361, 368, 369) and controllers (316, 366) illustrated in FIG. 3 may be the processor (210) illustrated in FIG. 2 and may be used to perform the methods described in the present disclosure.
[0081] FIG. 4a is a block diagram illustrating embodiments of a transmission path, and FIG. 4b is a block diagram illustrating embodiments of a reception path.
[0082] Referring to FIGS. 4A and 4B, a transmission path (410) may be implemented in a communication node that transmits a signal, and a reception path (420) may be implemented in a communication node that receives a signal. The transmission path (410) may include a channel coding and modulation block (411), an S-to-P (serial-to-parallel) block (512), an N IFFT (Inverse Fast Fourier Transform) block (413), a P-to-S (parallel-to-serial) block (414), a CP (cyclic prefix) addition block (415), and an UC (up-converter) (UC) (416). The receiving path (420) may include a DC (down-converter) (421), a CP removal block (422), an S-to-P block (423), an N FFT block (424), a P-to-S block (425), and a channel decoding and demodulation block (426). Here, N may be a natural number.
[0083] In the transmission path (410), information bits may be input to a channel coding and modulation block (411). The channel coding and modulation block (411) may perform a coding operation (e.g., a low-density parity check (LDPC) coding operation, a polar coding operation, etc.) and a modulation operation (e.g., a quadrature phase shift keying (QPSK), a quadrature amplitude modulation (QAM), etc.) on the information bits. The output of the channel coding and modulation block (411) may be a sequence of modulation symbols.
[0084] The S-to-P block (412) can convert modulation symbols in the frequency domain into parallel symbol streams to generate N parallel symbol streams. N can be an IFFT size or an FFT size. The N IFFT block (413) can perform an IFFT operation on the N parallel symbol streams to generate signals in the time domain. The P-to-S block (414) can convert the output (e.g., parallel signals) of the N IFFT block (413) into a serial signal to generate a serial signal.
[0085] The CP addition block (415) can insert a CP into a signal. The UC (416) can up-convert the frequency of the output of the CP addition block (415) to an RF (radio frequency) frequency. Additionally, the output of the CP addition block (415) can be filtered at the baseband before up-conversion.
[0086] A signal transmitted from a transmission path (410) may be input to a reception path (420). An operation in the reception path (420) may be the reverse operation of the operation in the transmission path (410). A DC (421) may down-convert the frequency of the received signal to a baseband frequency. A CP removal block (422) may remove a CP from a signal. The output of the CP removal block (422) may be a serial signal. An S-to-P block (423) may convert the serial signal into parallel signals. An N FFT block (424) may perform an FFT algorithm to generate N parallel signals. A P-to-S block (425) may convert the parallel signals into a sequence of modulation symbols. A channel decoding and demodulation block (426) may perform a demodulation operation on the modulation symbols and perform a decoding operation on the result of the demodulation operation to restore data.
[0087] In FIGS. 4A and 4B , Discrete Fourier Transform (DFT) and Inverse DFT (IDFT) may be used instead of FFT and IFFT. Each of the blocks (e.g., components) in FIGS. 4A and 4B may be implemented by at least one of hardware, software, or firmware. For example, some of the blocks in FIGS. 4A and 4B may be implemented by software, and the remaining blocks may be implemented by hardware or a “combination of hardware and software.” In FIGS. 4A and 4B , a block may be subdivided into multiple blocks, multiple blocks may be integrated into a single block, some blocks may be omitted, and blocks supporting other functions may be added.
[0088] Figure 5 is a conceptual diagram illustrating embodiments of a system frame in a communication system.
[0089] Referring to FIG. 5, time resources in a communication system can be divided into frame units. For example, system frames can be set consecutively in the time domain of the communication system. The length of a system frame can be 10 ms (milliseconds). The system frame number (SFN) can be set from #0 to #1023. In this case, 1024 system frames can be repeated in the time domain of the communication system. For example, the SFN of the system frame after system frame #1023 can be #0.
[0090] A system frame may include two half frames. A half frame may be 5 ms long. A half frame located at the beginning of the system frame may be referred to as "half frame #0," and a half frame located at the end of the system frame may be referred to as "half frame #1." A system frame may include 10 subframes. A subframe may be 1 ms long. The 10 subframes within a system frame may be referred to as "subframes #0-9."
[0091] Figure 6 is a conceptual diagram illustrating embodiments of subframes in a communication system.
[0092] Referring to FIG. 6, one subframe may include n slots, where n may be a natural number. Accordingly, one subframe may be composed of one or more slots.
[0093] Figure 7 is a conceptual diagram illustrating embodiments of slots in a communication system.
[0094] Referring to FIG. 7, a single slot may include one or more symbols. A single slot illustrated in FIG. 7 may include 14 symbols. The length of a slot may vary depending on the number and length of symbols contained in the slot. Alternatively, the length of a slot may vary depending on numerology.
[0095] In a communication system, the numerology applied to physical signals and channels may be variable. The numerology may be variable to meet various technical requirements of the communication system. In a communication system applying CP (cyclic prefix)-based OFDM waveform technology, the numerology may include subcarrier spacing and CP length (or CP type). Table 1 may be a first embodiment of a method for configuring a numerology for a CP-OFDM-based communication system. At least some of the numerologies in Table 1 may be supported depending on the frequency band in which the communication system operates. In addition, the communication system may additionally support numerologies not listed in Table 1.
[0096]
[0097] When the subcarrier spacing is 15 kHz (e.g., μ=0), the slot length can be 1 ms. In this case, one system frame can contain 10 slots. When the subcarrier spacing is 30 kHz (e.g., μ=1), the slot length can be 0.5 ms. In this case, one system frame can contain 20 slots.
[0098] When the subcarrier spacing is 60 kHz (e.g., μ=2), the slot length can be 0.25 ms. In this case, one system frame can contain 40 slots. When the subcarrier spacing is 120 kHz (e.g., μ=3), the slot length can be 0.125 ms. In this case, one system frame can contain 80 slots. When the subcarrier spacing is 240 kHz (e.g., μ=4), the slot length can be 0.0625 ms. In this case, one system frame can contain 160 slots.
[0099] A symbol may be configured as a downlink (DL) symbol, a flexible (FL) symbol, or an uplink (UL) symbol. A slot consisting solely of DL symbols may be referred to as a "DL slot," a slot consisting solely of FL symbols may be referred to as an "FL slot," and a slot consisting solely of UL symbols may be referred to as a "UL slot."
[0100] The slot format can be semi-statically configured by higher layer signaling (e.g., RRC signaling). Information indicating the semi-static slot format can be included in the system information, and the semi-static slot format can be configured cell-specifically. In addition, the semi-static slot format can be additionally configured for each terminal through terminal-specific higher layer signaling (e.g., RRC signaling). The flexible symbol of the cell-specifically configured slot format can be overridden to a downlink symbol or an uplink symbol by terminal-specific higher layer signaling. In addition, the slot format can be dynamically indicated by physical layer signaling (e.g., a slot format indicator (SFI) included in DCI). The semi-statically configured slot format can be overridden by a dynamically indicated slot format. For example, the semi-statically configured flexible symbol can be overridden to a downlink symbol or an uplink symbol by the SFI.
[0101] The reference signal may be a channel state information-reference signal (CSI-RS), a sounding reference signal (SRS), a demodulation-reference signal (DM-RS), a phase tracking-reference signal (PT-RS), etc. The channel may be a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), etc. In the present disclosure, a control channel may mean a PDCCH, a PUCCH, or a PSCCH, and a data channel may mean a PDSCH, a PUSCH, or a PSSCH.
[0102] Figure 8 is a conceptual diagram illustrating embodiments of time-frequency resources in a communication system.
[0103] Referring to FIG. 8, a resource consisting of one symbol (e.g., an OFDM symbol) in the time domain and one subcarrier in the frequency domain may be defined as a "RE (resource element)". Resources consisting of one OFDM symbol in the time domain and K subcarriers in the frequency domain may be defined as a "REG (resource element group)". A REG may include K REs. A REG may be used as a basic unit for resource allocation in the frequency domain. K may be a natural number. For example, K may be 12. N may be a natural number. In the slot illustrated in FIG. 7, N may be 14. N OFDM symbols may be used as a basic unit for resource allocation in the time domain.
[0104] In the present disclosure, RB may mean CRB (common RB). Alternatively, RB may mean PRB or VRB (virtual RB). In a communication system, CRB may mean RB that constitutes a set of consecutive RBs (e.g., a common RB grid) based on a reference frequency (e.g., point A). Carriers and / or bandwidth portions may be arranged on the common RB grid. That is, the carrier and / or bandwidth portions may be composed of CRB(s). RBs or CRBs that constitute the bandwidth portions may be referred to as PRBs, and within the bandwidth portions, the CRB index may be appropriately converted to the PRB index.
[0105] Downlink data can be transmitted via the PDSCH. The base station can transmit PDSCH configuration information (e.g., scheduling information) to the terminal via the PDCCH. The terminal can obtain the PDSCH configuration information by receiving the PDCCH (e.g., downlink control information (DCI)). For example, the PDSCH configuration information can include the MCS (modulation coding scheme) used for transmitting and receiving the PDSCH, time resource information of the PDSCH, frequency resource information of the PDSCH, feedback resource information for the PDSCH, etc. The PDSCH can refer to a radio resource through which downlink data is transmitted and received. Alternatively, the PDSCH can refer to the downlink data itself. The PDCCH can refer to a radio resource through which downlink control information (e.g., DCI) is transmitted and received. Alternatively, the PDCCH can refer to the downlink control information itself.
[0106] A terminal can perform a monitoring operation on the PDCCH to receive a PDSCH transmitted from a base station. The base station can inform the terminal of the configuration information for the PDCCH monitoring operation using a higher layer message (e.g., an RRC (radio resource control) message). The configuration information for the PDCCH monitoring operation can include CORESET (control resource set) information and search space information.
[0107] CORESET information may include PDCCH DMRS (demodulation reference signal) information, PDCCH precoding information, PDCCH occasion information, etc. The PDCCH DMRS may be a DMRS used to demodulate the PDCCH. The PDCCH occasion may be a region where the PDCCH can exist. That is, the PDCCH occasion may be a region where DCI can be transmitted. The PDCCH occasion may be referred to as a PDCCH candidate. The PDCCH occasion information may include time resource information and frequency resource information of the PDCCH occasion. In the time domain, the length of the PDCCH occasion may be indicated in symbol units. In the frequency domain, the size of the PDCCH occasion may be indicated in RB units (e.g., in PRB (physical resource block) units or CRB (common resource block) units).
[0108] The search space information may include a coreset identifier (ID) associated with the search space, a period of PDCCH monitoring, and / or an offset. The period and offset of PDCCH monitoring may each be indicated on a slot-by-slot basis. In addition, the search space information may further include an index of the symbol at which the PDCCH monitoring operation begins.
[0109] A base station can configure a bandwidth part (BWP) for downlink communication. The BWP can be configured differently for each terminal. The base station can inform the terminal of the BWP configuration information using higher layer signaling. The higher layer signaling can mean "transmission operation of system information" and / or "transmission operation of RRC (radio resource control) message." The number of BWPs configured for one terminal can be one or more. The terminal can receive BWP configuration information from the base station and check the BWP(s) configured by the base station based on the BWP configuration information. When multiple BWPs are configured for downlink communication, the base station can activate one or more BWPs among the multiple BWPs. The base station can transmit the configuration information of the activated BWP(s) to the terminal using at least one of higher layer signaling, a medium access control (MAC) control element (CE), or DCI. The base station can perform downlink communication using the activated BWP(s). The terminal can identify the activated BWP(s) by receiving configuration information of the activated BWP(s) from the base station, and perform a downlink reception operation in the activated BWP(s).
[0110] Meanwhile, a communication system (e.g., NR communication system, 5G communication system, 6G communication system) may support usage scenarios such as enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communication (URLLC), and massive Machine Type Communication (mMTC). A communication system (e.g., a communication network) may support transmission and reception point (TRP) technology (e.g., multiple TRP (mTRP) technology and / or single TRP (sTRP) technology). A communication system supporting the TRP technology may be referred to as a TRP system (e.g., mTRP system and / or sTRP system). In the present disclosure, TRP may have a meaning including sTRP and / or mTRP, and TRP may mean sTRP or mTRP depending on the context. TRP may mean an antenna set, an antenna group, and / or an antenna array. A TRP may be associated with a CORESET and / or a beam (e.g., a beam group).
[0111] mTRP technology may fall under the category of MIMO technology. mTRP may have characteristics (e.g., level characteristics) of macrocells, small cells, picocells, and / or femtocells. mTRP can perform data transmission for a single terminal. In a channel (e.g., a link) with uneven channel conditions due to obstacles and / or interference, mTRP can attenuate the effects of the obstacles and / or interference. mTRP can improve the data transmission rate for terminals located at cell edge areas.
[0112] mTRP-based communication can be performed using either coherent joint transmission (CJT) or non-CJT (NCJT) methods. In CJT, the base station can obtain channel information between each mTRP and the terminal and perform preprocessing on the data based on this channel information. In this case, the overhead associated with transmitting channel information may increase, and synchronization constraints between TRPs may arise. In NCJT, the base station may not need to know the channel information between each mTRP and the terminal. mTRPs can transmit data to the terminal without performing preprocessing operations such as phase compensation. The complexity of NCJT may be lower than that of CJT.
[0113] NCJT-based mTRP communication can be performed based on a single DCI scheme or a multiple DCI scheme. In the single DCI scheme, PDSCHs transmitted by an mTRP can be scheduled by a single DCI. A single DCI can be transmitted by one TRP among the mTRPs. In the multiple DCI scheme, the PDSCHs transmitted by each TRP can be scheduled by the DCI transmitted by each TRP. For example, a first PDSCH transmitted by a first TRP can be scheduled by a first DCI transmitted by the first TRP, and a second PDSCH transmitted by a second TRP can be scheduled by a second DCI transmitted by the second TRP. In other words, multiple PDSCHs can be scheduled using multiple DCIs.
[0114] In a single SCI scheme, a terminal can expect to receive PDSCHs transmitted by different TRPs over the same time and frequency resources and across different layers. Alternatively, the terminal can expect to receive PDSCHs transmitted by different TRPs over the same frequency resources and across the same layer but across different time resources (e.g., across different time domains). Alternatively, the terminal can expect to receive PDSCHs transmitted by different TRPs over the same time resources and across the same layer but across different frequency resources (e.g., across different frequency domains).
[0115] In a multi-DCI scheme, scheduling of PDSCHs for each TRP can be performed by a separate DCI. The PDSCHs scheduled by multiple DCIs may fully overlap or partially overlap. Alternatively, the PDSCHs scheduled by multiple DCIs may not overlap. In both single-DCI and multi-DCI schemes, the DCI may include transmission configuration indicator (TCI) status information for the PDSCH.
[0116] The indication / setting of the TCI state for the terminal can be interpreted as the indication / setting of a beam (e.g., a transmit beam and / or a receive beam). In other words, the TCI state can have a meaning corresponding to the beam. From the perspective of DL (downlink) communication, the setting of the TCI state can mean the setting of QCL (quasi co-location). From the perspective of UL (uplink) communication, the setting of the TCI state can mean the setting of a spatial filter. The unified TCI state can indicate (e.g., set) a common beam regardless of DL communication and UL communication. Alternatively, the unified TCI state can indicate (e.g., set) a common beam for each of DL communication and UL communication. The unified TCI can be referred to as UTCI.
[0117] Enhancements (e.g., PDCCH enhancements) may be implemented to improve the reliability and / or robustness of mTRP communications. Deployment scenarios for PDCCH enhancements can be categorized into single frequency network (SFN) and non-SFN scenarios.
[0118] In the SFN scheme, different TRPs or different panels can transmit the same PDCCH using the same resources (e.g., the same time resources, the same frequency resources, and / or the same spatial resources). In other words, all TRPs or all panels can transmit the same PDCCH using the same DMRS configuration, the same DMRS location, and / or the same DMRS sequence. At this time, the TCI states for the reception perspective of the TRPs or panels can be implicitly set differently. The above embodiment can be performed based on multiple TCI states of the CORESET. There may be synchronization constraints for ideal or near-ideal backhaul between TRPs.
[0119] In the NSFN scheme, the PDCCH generated from each TRP can be multiplexed in the time domain and / or frequency domain, and the multiplexed PDCCH can be transmitted to the terminal. The scheme may be an mTRP-based PDCCH repetition scheme. In the NSFN scheme, the same number of bits as the encoded bits transmitted through one PDCCH generated from each TRP can be divided for each TRP, and the bits (e.g., encoded bits) for each TRP can be transmitted through different PDCCH candidates. The scheme may be an sTRP-based PDCCH transmission scheme.
[0120] In the mTRP-based PDCCH repetition scheme, the PDCCH can be repeatedly generated as many times as the number of TRPs, and the PDCCH can be transmitted in the same search space (e.g., search spaces having the same index) within different search space sets having the same number of PDCCH candidates. At this time, the search space sets can exist within the same CORESET or different CORESETs. Since one TCI state can be associated with each CORESET, when the PDCCH is transmitted in different search spaces within the same CORESET, only one TCI state can be indicated (e.g., set) for the PDCCHs transmitted in the different search spaces. In this case, the UE can receive the PDCCH from one TRP at a specific time.
[0121] When a PDCCH is transmitted in the same search space within different CORESETs, the UE can implicitly expect to receive the PDCCH from either the sTRP or the mTRP, depending on the number of TCI states (e.g., TCI states indicated or configured by the base station). In this case, a single PDCCH can be split as many times as the number of TRPs, and the split PDCCHs can be transmitted on different PDCCH candidates. At this time, the aggregation level and the combined aggregation level can be the same. In the above embodiment, the PDCCH candidates can be assigned to different CORESETs. The payload size for the final distributed PDCCH combination can be the same as the payload size of the PDCCH transmitted in the sTRP. Therefore, in terms of decoding complexity, the sTRP-based PDCCH transmission scheme can be advantageous over the mTRP-based PDCCH repetition scheme.
[0122] A terminal can perform mTRP communication or sTRP communication with a base station. mTRP communication between the terminal and the base station can be performed through an mTRP associated with the base station. sTRP communication between the terminal and the base station can be performed through an sTRP associated with the base station. mTRP communication may be referred to as first TRP communication, and sTRP communication may be referred to as second TRP communication. Alternatively, mTRP communication may be referred to as second TRP communication, and sTRP communication may be referred to as first TRP communication. "The terminal performs first TRP communication with the base station" may mean "the terminal performs mTRP communication or sTRP communication with the base station through one or more TRPs associated with the base station." "The terminal performs second TRP communication with the base station" may mean "the terminal performs sTRP communication or mTRP communication with the base station through one or more TRPs associated with the base station."
[0123] In a communication system, integrated TCI can be supported. A base station can transmit information about a pool (e.g., a list) of TCI states to a terminal using RRC signaling. The terminal can receive information about a pool (e.g., a list) of TCI states through RRC signaling from the base station. The base station can set type information about the TCI state to the terminal. The type information can be a joint DL / UL beam indication or a separate DL / UL beam indication. A joint DL / UL beam indication can be referred to as a 'joint indication or joint type.' An independent DL / UL beam indication can be referred to as an 'independent indication or independent type.'
[0124] When a joint type (e.g., joint indication) is set, TCI states (e.g., one TCI state) for DL and UL may be set. In other words, DL TCI state setting and UL TCI state setting may be the same. The UE may expect that the TCI state indicated by the information element included in the PDSCH configuration information applies to both DL (e.g., DL signal / channel) and UL (e.g., UL signal / channel). The signal / channel may refer to a signal and / or a channel. When an independent type (e.g., independent indication) is set, TCI states for DL and UL may be set respectively. In other words, DL TCI state setting may be distinguished from UL TCI state setting. The UE may expect that the UL TCI state indicated by the information element included in the UL BWP configuration information applies to UL (e.g., UL signal / channel). The UL signal / channel may include a PUSCH, a PUCCH, and / or an SRS.
[0125] After the pool (e.g., pool list) for TCI states is configured (e.g., indicated) by RRC signaling, the base station can use DCI (e.g., DCI signaling) to indicate the TCI state (e.g., application of the TCI state). Due to the constraint of the DCI size (e.g., bits in the DCI field), the base station can preferentially activate candidate TCI state(s) using MAC signaling (e.g., MAC CE signaling). In other words, as many (e.g., maximum number) candidate TCI state(s) as can be indicated (e.g., configured) via DCI can be preferentially activated by MAC CE.
[0126] For the activated candidate TCI state(s), the DCI may contain code points corresponding to a single TCI state or two TCI states, depending on the TCI state type (e.g., joint type or independent type). If the joint type is set, the code points corresponding to a single TCI state may be conveyed by the DCI. If the independent type is set, the code points corresponding to two TCI states may be conveyed by the DCI.
[0127] Unified TCI extensions for multiple TRPs can be supported. Up to two TRPs can be supported. The base station can configure up to 128 TCI states for the TCI state pool via RRC configuration. The base station can activate up to 32 TCI states for eight codepoints using MAC CE. The base station can indicate up to four TCI states for two TRPs using DCI.
[0128] To check the DL channel status, a synchronization signal block (SSB) and / or a CSI-RS may be used. SSB may be transmitted periodically for time synchronization between the UE and the base station. SSB may be transmitted without a transmission request (e.g., a transmission request). Therefore, the transmission overhead of SSB may be smaller than that of CSI-RS. SSB may be transmitted within a specific frequency range. Due to limitations in the transmission frequency range, SSB may not be used to check the channel status for the frequency range that the UE wishes to measure and / or the frequency range supported by the entire system. In channel status measurement, SSB and CSI-RS may each have advantages and disadvantages. For measuring (e.g., checking) the DL channel status, either SSB or CSI-RS may be used depending on specific environments and / or specific conditions.
[0129] Channel state reports (e.g., CSI reports) can be categorized into three types. For example, channel state reports can be categorized into periodic channel state reports, semi-persistent channel state reports, and aperiodic channel state reports. In periodic channel state reports (e.g., periodic CSI reports), a terminal can transmit a channel state report to a base station according to a period set by the base station. In semi-static channel state reports (e.g., semi-static CSI reports), a terminal can transmit a channel state report to a base station during a certain period. In aperiodic channel state reports (e.g., aperiodic CSI reports), a terminal can transmit a channel state report to a base station according to a request from the base station (e.g., a CSI request). In other words, channel state reports can be transmitted intermittently.
[0130] A channel state report may include a precoding matrix indicator (PMI), a rank indicator (RI), a layer indicator (LI), a channel quality indicator (CQI), a CSI reference resource indicator (CRI), an SS / PBCH block resource indicator (SSBRI), a reference signal received power (RSRP), and / or a signal to interference plus noise ratio (SINR). A channel state report may include a capability index. A channel state report may include up to eight pieces of information. A CSI-RS may be used to measure a channel state. A base station may transmit an RRC message including resource information of a CSI-RS (e.g., CSI-ResourceConfig, CSI-Measconfig) to a terminal. The terminal may receive the RRC message from the base station and obtain the resource information of the CSI-RS included in the RRC message.
[0131] The resource information of the CSI-RS may include at least one of a time resource on which the CSI-RS is transmitted, a frequency resource on which the CSI-RS is transmitted, a transmission period of the CSI-RS, or a resource type of the CSI-RS (e.g., a periodic type, a semi-static type, or an aperiodic type). In addition, the RRC message may include configuration information for a CSI measurement report (e.g., CSI-ReportConfig). The type of the CSI-RS resource and the type of the CSI report (e.g., a CSI measurement report) may be configured independently. For example, when an aperiodic CSI report is required, the UE may perform measurement on all CSI-RS resources regardless of periodic CSI-RS resources, semi-static CSI-RS resources, and aperiodic CSI-RS resources, and transmit an aperiodic CSI report including the measurement result to the base station. For another example, if periodic CSI reporting is required, the terminal may perform measurements on periodic CSI-RS resources and transmit a periodic CSI report including the measurement results to the base station. For another example, if semi-static CSI reporting is required, the terminal may perform measurements on periodic CSI-RS resources and / or semi-static CSI-RS resources and transmit an aperiodic CSI report including the measurement results to the base station.
[0132] CSI-RS resource configuration can have a hierarchical structure. In other words, CSI-RS resources can be configured hierarchically. To indicate factors for obtaining minimal channel information, a set of REs with a specific pattern in the time and frequency domains can be referred to as a resource. Resource sets can be defined to indicate (e.g., configure) a set of resources at once. A separate ID can be assigned to distinguish each resource and resource set. Different resource sets can contain different resources, or different resource sets can contain the same resource(s). To flexibly utilize resources and resource sets, a group (e.g., a resource set list) containing resource sets can be configured, and the group can be defined based on resource configuration information (e.g., CSI-ResourceConfig). A specific ID can be configured for each set of resource sets (e.g., a resource set list).
[0133] A set of CSI-RS resources may be defined as a "CSI-RS resource set list" or "set list." In the present disclosure, periodic may be referred to as P, semi-persistent may be referred to as SP, and aperiodic may be referred to as AP. In other words, periodic CSI-RS, semi-persistent CSI-RS, and aperiodic CSI-RS may be referred to as P CSI-RS, SP CSI-RS, and AP CSI-RS, respectively, and periodic CSI reports, semi-persistent CSI reports, and aperiodic CSI reports may be referred to as P CSI reports, SP CSI reports, and AP CSI reports, respectively. CSI-RS resource(s) by type (e.g., P, SP, AP) may be set as a unit of a CSI-RS resource set list. CSI-RS resource set(s) and / or CSI-RS resource(s) belonging to the same CSI-RS resource set list can be interpreted as having the same type. Since the CSI-RS resource set list is configured by type, CSI reports can be requested or transmitted by CSI-RS resource set list. The resource configuration of CSI-RS can have a hierarchical structure in the order of CSI-RS resource → CSI-RS resource set → CSI-RS resource set list. One or more CSI-RS resources can belong to a CSI-RS resource set, and one or more CSI-RS resource sets can belong to a CSI-RS resource set list.
[0134] The configuration information of a CSI report may be transmitted to a terminal together with the configuration information of CSI-RS resources. Depending on the purpose of CSI measurement (e.g., channel measurement, interference measurement), configuration information (e.g., allocation information) for different CSI-RS resource set lists may be transmitted to the terminal. The configuration information of a CSI report may include all information necessary for a terminal to transmit a CSI report. For example, the configuration information of a CSI report may include at least one of a CSI report type (e.g., P, SP, AP), a time resource for which CSI measurement is required, a frequency resource for which CSI measurement is required, or a type of information included in the CSI report. The channel through which the CSI report is transmitted may vary depending on the size of the CSI report. For example, a P CSI report may be transmitted via a PUCCH. An SP CSI report may be transmitted via a PUCCH or a PUSCH. An AP CSI report may be transmitted via a PUSCH. The size of an AP CSI report may be larger than the size of an SP CSI report, and the size of an SP CSI report may be larger than the size of a P CSI report.
[0135] The type-specific CSI reporting procedure can be performed as follows. The base station can transmit an RRC message including configuration information for CSI measurement, configuration information for CSI-RS resources, and / or configuration information for CSI reporting to the terminal. The terminal can obtain configuration information for CSI measurement, configuration information for CSI-RS resources, and / or configuration information for CSI reporting from the base station. In the P CSI reporting procedure, the terminal can measure a DL channel based on P CSI-RS without a separate triggering signal (e.g., a triggering signal), and transmit a CSI report including the measurement result to the base station according to a CSI reporting cycle configured by RRC signaling (e.g., an RRC message).
[0136] In the SP CSI reporting procedure, the base station may transmit information (e.g., MAC CE) indicating activation of SP CSI measurement / reporting to the terminal. When SP CSI measurement / reporting is activated, the terminal may measure a DL channel based on the P CSI-RS and transmit a CSI report including the measurement result to the base station according to a CSI reporting cycle set by RRC signaling (e.g., an RRC message). The transmission operation of the CSI report may be performed until information (e.g., MAC CE) indicating deactivation of SP CSI measurement / reporting is received from the base station. Activation signaling and / or deactivation signaling for SP CSI measurement / reporting may be required for the SP CSI reporting procedure. In the period between the activation signaling and the deactivation signaling, the terminal may measure a DL channel based on the SP CSI-RS and transmit a CSI report including the measurement result to the base station.
[0137] In the AP CSI reporting procedure, the base station can transmit a signaling message (e.g., DCI or MAC CE) to the terminal to trigger AP CSI measurement / reporting. The signaling message can indicate one CSI report. The terminal can receive the signaling message from the base station and confirm that AP CSI measurement / reporting is triggered based on the signaling message. The AP CSI-RS resource measured by the terminal can be an AP CSI-RS resource existing N slots after a slot in which a signaling message triggering AP CSI measurement / reporting is received, and the AP CSI report can be transmitted M slots after a slot in which a signaling message triggering AP CSI measurement / reporting is received. Each of N and M can be a natural number. Information about the N slots indicating the AP CSI-RS resource and / or information about the M slots indicating the timing of the AP CSI report can be transmitted to the terminal via RRC signaling. Information about N slots indicating AP CSI-RS resources and / or information about M slots indicating timing of AP CSI reporting may be transmitted to the terminal together with configuration information of CSI measurement, configuration information of CSI-RS resources, and / or configuration information of CSI reporting.
[0138] A terminal can individually perform data transmission using multiple panels. In other words, the terminal can independently perform data transmission using each of the multiple panels. The terminal can transmit information necessary for data transmission for each panel to the terminal. The base station can obtain information necessary for data transmission for each panel from the terminal. One of the pieces of information necessary for data transmission for each panel may be power headroom information (e.g., power headroom report (PHR)). Power headroom information may refer to the remaining power other than the power used by the terminal for data transmission. Power headroom information may be set on a subframe basis. The transmission power for data may be a predicted value (e.g., predicted transmission power) rather than a value used for actual transmission (e.g., actual transmission power). The power used for actual data transmission cannot exceed the maximum transmission power supported by the terminal. The predicted transmission power may exceed the maximum transmission power supported by the terminal. The power headroom information reported by the terminal may have a positive or negative value.
[0139] The PHR can be transmitted from the terminal to the base station through the MAC layer. In other words, the PHR can be included in the MAC CE. A PH (power headroom) index (e.g., a PH value) can be defined in a table (e.g., mapping information between the PH index and the transmission power interval) in a technical specification. In the table, the PH index can be mapped to each transmission power interval. For example, the PH index can indicate PH 0, and the PH 0 can be mapped to -23dB ≤ PH < -22dB in the table. The size of the PHR field included in the MAC CE can vary depending on the number of PH indices. The terminal can transmit the PHR per panel. The path loss associated with the PHR can be determined based on the RS (reference signal) linked to the beam configuration (e.g., TCI state and / or QCL). Whether to transmit the PHR per panel can be determined depending on the terminal capability. For example, some terminals may support per-panel PHR transmission, while others may not. A terminal may report to the base station information regarding whether it supports per-panel PHR transmission. A parameter indicating whether PHR transmission for mTRP is supported (e.g., twoPHRmode) may be used as a parameter for information regarding whether per-panel PHR transmission is supported. Methods for improving the performance of uplink communication in an mTRP environment (e.g., an mTRP system) are needed.
[0140] Figure 9 is a conceptual diagram illustrating an embodiment of an asymmetric TRP system.
[0141] Referring to FIG. 9, a macro cell (e.g., a macro TRP, a first TRP) can cover a relatively large area, and a micro cell (e.g., a micro TRP, a second TRP) can cover a relatively small area. Downlink traffic (e.g., traffic for downlink data transmission) may be greater than uplink traffic (e.g., traffic for uplink data transmission). Therefore, transmission resources may be set with a focus on downlink. The transmission power of a base station may be greater than the transmission power of a terminal, and the downlink coverage may be wider than the uplink coverage.
[0142] A microcell (e.g., a second TRP) adjacent to a terminal may exist. The power efficiency of uplink communication for the adjacent microcell may be better than the power efficiency of uplink communication for the macrocell (e.g., the first TRP) to which the terminal is connected. A TRP may be an entity that transmits and receives data with the terminal. A TRP and a cell may have corresponding meanings. A TRP may be used with the same meaning as a cell depending on the context. A cell may be used with the same meaning as a TRP depending on the context. A specific TRP (e.g., a serving cell) may perform a control function for another TRP (e.g., a TRP dependent on the specific TRP). A specific TRP may perform a data scheduling function.
[0143] While a terminal performs DL (downlink) communication with a macro cell, the terminal can perform UL (uplink) communication with a micro cell. If channel reciprocity is established between the DL channel for the macro cell and the UL channel for the micro cell, the terminal can determine (e.g., set) the transmission power for the UL channel of the micro cell based on the path loss determined based on the RS received from the macro cell. Alternatively, in an asymmetric TRP system, the terminal can perform DL communication with one TRP (e.g., a macro cell) and UL communication with multiple TRPs (e.g., a macro cell and a micro cell). In the above-described asymmetric TRP system, the terminal can determine (e.g., set) the transmission power for the UL channel of each of the macro cell and the micro cell based on the path loss determined based on the RS received from the macro cell. In this case, the UL transmission power for the micro cell can be set to a high power. In other words, since the UL transmission power for a microcell is determined by considering the channel status between the macrocell and the terminal, rather than the channel status between the microcell and the terminal, the UL transmission power for the microcell can be set to high power. In the above-described situation (e.g., when the distance between the macrocell and the terminal is longer than the distance between the microcell and the terminal), even though UL communication (e.g., transmission of a channel and / or signal) for the microcell is possible using low transmission power, UL communication for the microcell may be performed using high transmission power. Therefore, power of the terminal may be wasted, and UL communication using high transmission power may cause interference to other terminals.
[0144] To address the above-described issues, a method for setting UL transmission power in an asymmetric TRP system may require supplementation. The asymmetric TRP system may include mTRPs, wherein among the mTRPs, an sTRP may perform DL communication, and the mTRP may perform UL communication. An sTRP performing DL communication may be referred to as a DL sTRP. An mTRP performing UL communication may be referred to as a UL mTRP. A method for power control (e.g., power setting, power determination) for UL communication in an asymmetric TRP system will be described. While the power control method for the PUSCH is described in the present disclosure, the power control method for the PUSCH may be applied to other UL channels and / or other UL signals.
[0145] In an asymmetric TRP system, an additional path loss offset may be used for UL communication for UL TRP. The UL TRP may refer to the TRP that is the target of UL communication. The path loss offset may be referred to as a PL (path loss) offset. The path loss offset may refer to a path loss offset value. The path loss offset and the path loss offset value may be used interchangeably. In the present disclosure, a signaling method for the path loss offset, a method for linking the path loss offset and the TCI state, etc. will be proposed.
[0146] The base station can transmit UL transmission power configuration information for TCI settings (e.g., TCI state type) to the terminal via signaling (e.g., RRC signaling). The terminal can receive UL transmission power configuration information for TCI settings via signaling from the base station. The TCI state type can be a joint type or an independent type. A TCI state of the joint type can be referred to as a joint TCI state. A TCI state of the independent type can be referred to as an independent TCI state.
[0147] A UL TCI state list (e.g., a UL TCI state pool) may be additionally configured depending on the TCI state type. If the TCI state type is a joint type, the UE may expect the DL TCI state pool to follow the UL TCI state pool. The TCI state list may be transmitted by DL dedicated signaling (e.g., PDSCH configuration). If the TCI state type is an independent type, the base station may configure UL TCI state(s) to the UE separately from the DL TCI state(s). The UL TCI state(s) may be configured by UL dedicated signaling (e.g., BWP-UplinkDedicated). The UE may perform UL communication based on the UL TCI state(s). The UL communication (e.g., UL transmission) may include PUSCH transmission, SRS transmission, and / or PUCCH transmission. UL TCI state(s) can be interpreted as a UL TCI state list or a UL TCI state pool, depending on the context. DL TCI state(s) can be interpreted as a DL TCI state list or a DL TCI state pool, depending on the context.
[0148] When a type for an integrated TCI state is indicated (e.g., set), power configuration information for UL communication (e.g., power control information, power configuration parameters, power control parameters, power parameter list) can be indicated (e.g., set) to the terminal. The type for the integrated TCI state can be set to the terminal together with a power parameter list for UL communication. The power parameter list can be distinguished by an identifier (ID). The power parameter list can include parameters required for UL communication (e.g., power control of UL communication) (e.g., alpha (α), p0, closed loop (CL) index, etc.).
[0149] If the base station supports a unified TCI state (e.g., a unified TCI framework), a list(s) of power parameters (e.g., a list(s) of candidate power parameters) for each TCI state may be transmitted to the terminal. The terminal may receive the list(s) of power parameters (e.g., a list(s) of candidate power parameters) for each TCI state via signaling from the base station. In the present disclosure, the list of power parameters may refer to a list of power parameters for UL communication.
[0150] When a base station sets TCI state(s) for a joint type to a terminal, the base station may transmit a power parameter list and / or a power parameter list ID for each TCI state to the terminal. In other words, "information on TCI state(s) for a joint type and a power parameter list for each TCI state" or "information on TCI state(s) for a joint type, a power parameter list for each TCI state, and a power parameter list ID for each TCI state" may be transmitted together to the terminal. The power parameter list ID may mean an ID of the power parameter list. The power parameter list ID may mean a UL power control ID (e.g., Uplink-powerControlID). When a base station sets TCI state(s) for an independent type to a terminal, the base station may transmit a power parameter list and / or a power parameter list ID for each TCI state to the terminal. In other words, "information on TCI state(s) for independent types and a list of power parameters for each TCI state" or "information on TCI state(s) for independent types, a list of power parameters for each TCI state, and a power parameter list ID for each TCI state" may be transmitted together to the terminal. Alternatively, the base station may transmit common power parameter list(s) for UL communication to the terminal through signaling regardless of the TCI state. The terminal may receive the common power parameter list(s) through signaling from the base station. The common power parameter list(s) may be used for UL communication for all TCI states.
[0151] When a base station performs communication with a terminal based on an integrated TCI state, the base station can transmit to the terminal a list of applicable power parameters (e.g., a common power parameter list) regardless of the TCI state through signaling. Alternatively, when the base station performs communication with a terminal based on a joint TCI state or an independent TCI state, the base station can transmit to the terminal a list of power parameters for each TCI through signaling. The list of power parameters and the type setting of the TCI state (e.g., type setting information) can be included in one signaling message, and the base station can transmit the one signaling message to the terminal. The terminal can receive one signaling message from the base station and check the list of power parameters and the type setting of the TCI state (e.g., type setting information) included in the one signaling message.
[0152] When a terminal is capable of measuring (e.g., measuring a reference signal (RS)) a TRP (e.g., UL TRP) that is a target of UL communication, the terminal can determine transmission power based on the result of the measurement. In an asymmetric TRP system, a situation may occur where the terminal does not receive an RS from the UL TRP. In other words, in an asymmetric TRP system, the terminal may not be able to perform measurements for the UL TRP. In the above-described situation, methods for obtaining (e.g., setting, indicating, determining) a power offset (e.g., path loss offset) for UL communication for the UL TRP are required. In the present disclosure, methods for setting a power offset for UL communication for the UL TRP in an asymmetric TRP system will be proposed.
[0153] The transmission power may vary depending on the type of TCI state (e.g., joint or independent). In an asymmetric TRP system, a terminal may receive control information from a DL TRP (e.g., a TRP that is a target of DL communication) and perform UL communication with one or more UL TRPs based on the control information. A power parameter (e.g., a power parameter list) set together with a TCI state may be referred to as an “other UL transmission parameter.” The other UL transmission parameter may include at least one of alpha, p0, or a CL index. In addition, the other UL transmission parameter may further include other parameter(s) for power control in addition to the above parameters. Setting a power parameter (e.g., a power parameter list) together with a TCI state may mean that the power parameter (e.g., the power parameter list) is associated with (e.g., mapped to) the TCI state.
[0154] ○ Proposal #1: A method for setting path loss offsets (e.g., an indication method) based on whether power parameters (e.g., path loss offsets) are associated with TCI states.
[0155] The method for setting the path loss offset for a terminal can be classified into method #1 and method #2 based on whether the power parameter is associated with a TCI state. The path loss offset can be a type of power parameter. In method #1, the path loss offset can be set to be associated with a TCI state. In method #2, the path loss offset can be set regardless of the TCI state. In other words, in method #2, the path loss offset can be set not to be associated with a TCI state. In method #2, the path loss offset can be a common path loss offset applicable to all TCI states. In proposal #1, the path loss offset can be used to determine the transmit power for UL communication for UL TRP in an asymmetric TRP system.
[0156] In method #1, the base station can transmit a TCI state configuration (e.g., a TCI state configuration message) including TCI state information and a path loss offset to the terminal via signaling (e.g., RRC signaling). The terminal can receive the TCI state configuration via the signaling from the base station and check the TCI state information and the path loss offset included in the TCI state configuration. The path loss offset can be associated with the TCI state information. For example, if the TCI state configuration includes N TCI states, N path loss offsets associated with the N TCI states can be included in the TCI state configuration.
[0157] In method #2, the base station can transmit a DCI including a path loss offset (e.g., a single path loss offset) to the terminal. The terminal can receive the DCI from the base station and check the path loss offset included in the DCI. Alternatively, in method #2, the base station can transmit a MAC CE including a path loss offset (e.g., a single path loss offset) to the terminal. The terminal can receive the MAC CE from the base station and check the path loss offset included in the MAC CE. The MAC CE can be used to indicate active TCI state(s) and / or the path loss offset. Alternatively, in method #2, the base station can transmit an RRC message including a path loss offset (e.g., a single path loss offset) to the terminal. The terminal can receive the RRC message from the base station and check the path loss offset included in the RRC message. The path loss offset can be included in an RRC message for transmitting BWP-only information. In other words, the path loss offset can be included in the BWP-only information.
[0158] In the present disclosure, a path loss offset that is not associated with a TCI state may be referred to as a common path loss offset. The common path loss offset may be applied to determine the transmit power of UL communication regardless of the TCI state. A path loss offset for each TCI state may be referred to as a dedicated path loss offset (or TCI path loss offset). The base station may transmit at least one of the common path loss offset or the dedicated path loss offset to the terminal through signaling. The terminal may receive at least one of the common path loss offset or the dedicated path loss offset through signaling from the base station.
[0159] The value of the common path loss offset can be a value having a wide range. The value of the common path loss offset can be an absolute value. The value of the dedicated path loss offset can be set as a relative value based on the value of the common path loss offset. The common path loss offset (e.g., the value of the common path loss offset) can be transmitted via an RRC configuration (e.g., RRC signaling) and / or a MAC CE configuration (e.g., MAC CE signaling). The dedicated path loss offset (e.g., the value of the dedicated path loss offset) can be transmitted via MAC CE and / or DCI. In the present disclosure, the path loss offset can be interpreted as the common path loss offset or the dedicated path loss offset depending on the context. The path loss offset value can mean the value of the path loss offset.
[0160] ○ Proposal #2: Method 1 for setting path loss offset based on RRC signaling
[0161] ● Proposal #2-1
[0162] The base station can generate a list of power parameters (e.g., another list of UL transmission parameters) including a path loss offset and transmit the list of power parameters to the terminal via signaling. The terminal can receive the list of power parameters via signaling from the base station and verify the information included in the list of power parameters. The terminal can determine the transmission power based on the verified information and perform UL communication for the UL TRP using the transmission power.
[0163] TCI state information (e.g., TCI state configuration information) may include at least one of a TCI state ID, a power parameter list ID (e.g., a power parameter list ID associated with the TCI state ID), or a power parameter list (e.g., a power parameter list corresponding to the power parameter list ID). The base station may inform the terminal of the TCI state ID, the power parameter list ID, and / or the power parameter list by transmitting the TCI state information to the terminal through signaling. The path loss offset may be included in the TCI state information, which is an RRC configuration.
[0164] FIG. 10 is a conceptual diagram illustrating embodiments of a power parameter list including a path loss offset.
[0165] Referring to FIG. 10, a power parameter list may include alpha, p0, CL (closed loop) (e.g., CL index), and / or path loss offset (e.g., path loss offset value). The parameter(s) included in the power parameter list may be used for UL communication (e.g., PUSCH transmission, SRS transmission, PUCCH transmission, etc.). A power parameter list may include an alpha set for each type of UL communication. For example, a power parameter list may include an alpha set for PUSCH transmission, an alpha set for SRS transmission, and / or an alpha set for PUCCH transmission. An alpha set may include alpha, p0, and / or CL (e.g., CL index). A path loss offset may exist in the power parameter list independently of the alpha sets. A single path loss offset may be included in the power parameter list. The path loss offset may be applied regardless of the type of UL communication. In other words, the path loss offset may be commonly applied to all UL communications.
[0166] An ID for each power parameter list can be set. The power parameter list ID can be expressed as a UL power control ID. In the embodiment of FIG. 10, the UL power control ID can mean a power parameter list ID. The power parameter list ID can be associated with a "DL or joint TCI state ID" or a "UL TCI state ID." N power parameter list IDs can be set. N can be equal to the maximum number of UL TCI states. N can be a natural number.
[0167] Proposal #2-2
[0168] The base station can transmit a path loss offset (e.g., a value of the path loss offset) to the terminal along with the TCI state configuration. According to Proposal #2-2, the signaling of the TCI state configuration can be changed to convey the path loss offset to the terminal. Unlike Proposal #2-2, in the above-described Proposal #2-1, the power parameter list (e.g., a power parameter list including the path loss offset) can be conveyed to the terminal without changing the signaling for the TCI state configuration. For example, according to Proposal #2-2, the TCI state configuration can include a TCI state ID, QCL information, PCI (physical cell identifier) information, UL power control ID, path loss offset (e.g., a power control offset), etc. The path loss offset can be included in the TCI state information, which is an RRC configuration.
[0169] ○ Proposal #3: Method 2 for Setting Path Loss Offset Based on RRC Signaling
[0170] The base station can transmit to the terminal an RRC message (e.g., an RRC message including BWP-UplinkDedicated) including a common path loss offset that can be used regardless of the TCI state. In other words, the common path loss offset can be included in the UL BWP dedicated configuration information (e.g., UL BWP dedicated information), which is an RRC configuration. The common path loss offset can be applied to all TCI states. The terminal can receive the RRC message from the base station and check the common path loss offset included in the RRC message. Proposal #3 may not be applicable to terminals that do not support the integrated TCI state.
[0171] If a power parameter list including a path loss offset is not set to the terminal (e.g., if the power parameter list indicated to the terminal does not include a path loss offset) or a TCI state configuration including a path loss offset is not indicated to the terminal (e.g., if the TCI state configuration indicated to the terminal does not include a path loss offset), the terminal can expect to receive an RRC message (e.g., BWP-UplinkDedicated) including a common path loss offset. In other words, the terminal can expect an RRC message (e.g., BWP-UplinkDedicated) received from the base station including a common path loss offset.
[0172] The terminal can support Proposal #3 by default. If the path loss offset is not indicated to the terminal by signaling according to Proposal #3, the terminal can expect the path loss offset to be indicated to the terminal by signaling according to Proposal #2-1 or Proposal #2-2.
[0173] ○ Proposal #4: Method for setting path loss offset based on MAC signaling (e.g., MAC CE) and / or PHY (physical) signaling (e.g., DCI)
[0174] ● Proposal #4-1
[0175] The latency according to the method of indicating the path loss offset based on RRC signaling (e.g., Proposal #2) may be greater than the latency according to the method of indicating the path loss offset based on MAC signaling and / or PHY signaling. In terms of latency, the gain of PHY signaling may be greater than the gain of MAC signaling. The information size constraint in PHY signaling may be greater than the information size constraint in MAC signaling.
[0176] MAC CE can be used to enable or disable the TCI state. DCI can be used to indicate the TCI state. A list of power parameters (e.g., path loss offset) and / or update information for the list of power parameters (e.g., path loss offset) can be indicated (e.g., set) by MAC CE and / or DCI. The update information for the list of power parameters can include at least a path loss offset.
[0177] Fig. 11a is a conceptual diagram illustrating embodiments of a MAC CE for activating a joint type TCI state. Fig. 11b is a conceptual diagram illustrating embodiments of a MAC CE for activating an independent type TCI state.
[0178] Referring to FIGS. 11A and 11B , in the integrated TCI framework, TCI state activation can be indicated by MAC CE. The maximum number of activated TCI states can vary depending on the TCI state type (e.g., joint type or independent type). For a joint TCI type (e.g., a TCI state of a joint type), up to 16 TCI states can be activated, and up to 2 TCI states can be mapped to one code point. For an independent TCI type (e.g., a TCI state of an independent type), up to 32 TCI states can be activated, and up to 4 TCI states can be mapped to one code point.
[0179] A base station can transmit a MAC CE including a path loss offset to a terminal. To set a path loss offset through the MAC CE, values of the path loss offset (e.g., path loss offset values) can be determined based on a quantization level, and the path loss offset values determined based on the quantization level can be included in a path loss offset list. In other words, a path loss offset list including path loss offset values determined based on the quantization level can be generated. The path loss offset list can be preset in the base station (e.g., TRP) and / or the terminal. Alternatively, the path loss offset list can be set (e.g., instructed) to the terminal through signaling from the base station.
[0180] The index of each path loss offset value included in the path loss offset list can be set. The base station can transmit a MAC CE including the index of the path loss offset value to the terminal. The index of the path loss offset value can be expressed by bit(s) in the MAC CE. Alternatively, the path loss offset value can be converted into binary form, the converted path loss offset value can be expressed by bit(s) in the MAC CE, and the sign (e.g., positive (+) or negative (-)) of the converted path loss offset value can be expressed by a bit (e.g., a reserved bit) in the MAC CE.
[0181] One or more path loss offset values per TCI state may be included in the MAC CE. One or more path loss offset values per TRP may be included in the MAC CE. When path loss offset values are allocated per TCI state, the maximum number of allocated path loss offset values may vary depending on the TCI type. For a joint TCI type, up to 16 path loss offset values may be allocated, and 16 bits may be additionally required to represent the signs of the 16 path loss offset values. For an independent TCI type, up to 32 path loss offset values may be allocated, and 32 bits may be additionally required to represent the signs of the 32 path loss offset values.
[0182] For example, the path loss offset list can be set as shown in Table 2 below.
[0183]
[0184] When the path loss offset list is set as in Table 2, 2×16 bits or 2×32 bits may be required within the MAC CE to set the path loss offset value using the MAC CE. 16 or 32 more bits may be required within the MAC CE to indicate the sign of the path loss offset value.
[0185] Code points can be mapped to TCI states. Based on the proposed methods, code points can be mapped to path loss offset values. Information (e.g., 1-bit information) indicating whether a path loss offset value is set for each TCI state may be required. The MAC CE may further include information indicating whether a path loss offset value is set for each TCI state.
[0186] FIG. 12a is a conceptual diagram illustrating embodiments of a MAC CE for activating a TCI state of a joint type. FIG. 12b is a conceptual diagram illustrating embodiments of a MAC CE for activating a TCI state of an independent type.
[0187] Referring to FIGS. 12A and 12B , the MAC CE may further include fields for indicating a path loss offset. The fields for indicating a path loss offset may include a path loss offset field, a P field, and / or an I field. The path loss offset field may indicate an actual value (e.g., an absolute value) for the path loss offset. Alternatively, when a path loss offset list is set as in Table 2, the path loss offset field may be set to an index indicating a specific path loss offset value within the path loss offset list. The P field may indicate whether a path loss offset corresponding to (e.g., associated with, mapped to) a TCI state ID exists within the MAC CE. The size of the P field may be 1 bit. For example, a P1 field set to a first value (e.g., 0) may indicate that a path loss offset (e.g., a path loss offset value) corresponding to TCI state ID1 does not exist within the MAC CE, and a P1 field set to a second value (e.g., 0) may indicate that a path loss offset (e.g., a path loss offset value) corresponding to TCI state ID1 exists within the MAC CE.
[0188] The I field can indicate the sign (e.g., positive (+) or negative (-)) of the path loss offset value. The size of the I field can be 1 bit. For example, the I1 field set to a first value (e.g., 0) can indicate that the sign of the path loss offset value corresponding to the TCI state ID1 is positive (+), and the I1 field set to a second value (e.g., 1) can indicate that the sign of the path loss offset value corresponding to the TCI state ID1 is negative (-).
[0189] In the embodiment of FIG. 12a, the size of the Path Loss Offset field may be 7 bits, and the Path Loss Offset field may indicate an actual value (e.g., an absolute value) for the path loss offset. In the embodiment of FIG. 12a, a MAC CE (e.g., a MAC CE message) may include a Path Loss Offset field, a P field, and an I field. In the embodiment of FIG. 12a (e.g., when a joint TCI type is used), the number of TCI states (N) may be 16. In the embodiment of FIG. 12b, the size of the Path Loss Offset field may be 2 bits, and the Path Loss Offset field may be set to an index that indicates a specific path loss offset value within a path loss offset list (e.g., a path loss offset table defined in Table 2). In the embodiment of FIG. 12b, the MAC CE may include a Path Loss Offset field and a P field. In other words, in the embodiment of FIG. 12b, the MAC CE may not include an I field.
[0190] The path loss offset value may be indicated for each TCI state. Alternatively, multiple path loss offset values (e.g., two path loss offset values) may be mapped to a single code point. Unlike the embodiment described above, the path loss offset value may be indicated for each TRP. In this case, it may be considered that a single path loss offset value is mapped to a code point.
[0191] The path loss offset value may be configured to be mapped one-to-one with the activation code point of the TCI state. Alternatively, the path loss offset value may be configured to be mapped many-to-one with the activation code point of the TCI state. When the path loss offset value is mapped many-to-one with the activation code point of the TCI state, each path loss offset value may be associated with each TRP. If the terminal supports up to four TRPs and a joint TCI state is indicated, one code point may be associated with up to four TCI states, and there may be as many path loss offset values as the number of TCI states associated with one code point.
[0192] Proposal #4-2
[0193] When a MAC CE (e.g., a MAC CE message) includes a single TCI state, the MAC CE may be used for indication purposes rather than activation of the TCI state. In a general procedure of the unified TCI state framework, a MAC CE may activate multiple TCI states associated with multiple code points, and a DCI may indicate a specific code point (e.g., a single code point) to the terminal. According to the procedure described above, the terminal may perform communication (e.g., UL communication and / or DL communication) with one or more TRPs using the TCI states associated with the single code point.
[0194] Information about the path loss offset (e.g., the path loss offset value) may be indicated by DCI (e.g., reserved bit(s) in the DCI) instead of MAC CE. For example, a bit (e.g., 1 bit) included in the DCI may indicate whether to use the path loss offset value associated with the TCI state (e.g., the TCI state indicated by the DCI). Since the information adjacent to uplink scheduling (e.g., scheduled uplink resources) in the time domain is DCI (e.g., DCI for TCI indication), not MAC CE (e.g., MAC CE for TCI indication and / or activation), it may be necessary for the base station to notify the terminal in advance whether to apply the path loss offset value associated with the TCI state depending on the situation. The terminal may not know whether the scheduling information is information for communicating with another TRP, and it may be necessary for the base station to dynamically notify the terminal whether to apply the path loss offset value by taking into account the environment of the terminal.
[0195] The path loss offset value may depend on the location of the terminal. Therefore, the base station can directly set (e.g., indicate) the path loss offset value to the terminal using DCI. In other words, the base station can transmit DCI including the path loss offset value and / or the TCI state indication to the terminal without association with the TCI state(s). The fields for indicating the path loss offset (e.g., the path loss offset value) included in the DCI may be identical to or similar to the fields (e.g., the path loss offset field, the P field, and / or the I field) of the embodiments of FIG. 12A and / or FIG. 12B.
[0196] The path loss offset value may be included in the DCI for uplink scheduling (e.g., DCI including a UL grant). In order to maximize the use of the location of the terminal before uplink scheduling, the path loss offset value may be included in the DCI for uplink scheduling. The path loss offset value may be determined based on the location of the terminal. To distinguish from the DCI for TCI status indication (e.g., legacy DCI format) and / or to avoid conflicts with the operation of legacy terminals, a separate DCI format including the path loss offset value may be defined. The DCI format including the path loss offset value may include information of a code point associated with an activated TCI state. The code point included in the DCI format may be associated with the path loss offset value. The terminal may receive the above-described DCI (e.g., DCI format), check the path loss offset value included in the DCI, and perform TRP (e.g., UL TRP) and UL communication using the transmission power determined based on the path loss offset value.
[0197] Proposal #4-3
[0198] According to the above-mentioned proposal #4-1 and / or proposal #4-2, at least the TCI state and the path loss offset value are associated with one code point, and it may be impossible to indicate an independent path loss offset value (based on the association). To solve the above-mentioned problem, the base station may transmit to the terminal a MAC CE including a list (e.g., a path loss offset list) including path loss offset value(s) that are not related to the TCI state. The terminal may receive the MAC CE from the base station and check the path loss offset list included in the MAC CE. Each path loss offset value may be mapped to one code point, and each path loss offset value may be activated based on the mapping relationship. Thereafter, in the transmission procedure of the DCI for indicating the TCI state, the DCI may include information indicating a code point associated with (e.g., mapped to) a specific path loss offset value.
[0199] The MAC CE may include information about TCI states and information about path loss offset values, and the path loss offset values within the MAC CE may be set independently of the TCI states. In other words, the path loss offset values within the MAC CE may not have any correlation with the TCI states. The DCI transmitted after the MAC CE may include information about code points for each of the TCI states and the path loss offset values. For example, the DCI may include N code points for activating a TCI state and M code points for activating (e.g., indicating) a path loss offset value. Each of N and M may be a natural number. For example, N may be 8. The bit(s) (e.g., fields) indicating the N code points for activating a TCI state and the bit(s) (e.g., fields) indicating the M code points for activating (e.g., indicating) a path loss offset value may be set independently within the DCI.
[0200] ○ Proposal #5: Method for setting path loss offset based on RRC signaling, MAC signaling, and / or PHY signaling
[0201] ● Proposal #5-1
[0202] Proposal #5-1 can be efficient when there are a large number of indicative (e.g., configurable) candidate path loss offset values. In other words, Proposal #5-1 can be used when there are a large number of indicative (e.g., configurable) candidate path loss offset values. The base station can transmit configuration information for all candidate path loss offset values to the terminal using RRC signaling. The terminal can receive configuration information for all candidate path loss offset values through the RRC signaling of the base station. The base station can generate a MAC CE including code points mapped to N path loss offset values (e.g., candidate path loss offset values) among all candidate path loss offset values, and transmit the MAC CE to the terminal. N can be a natural number. The code point included in the MAC CE can indicate activation of the N path loss offset values mapped to the code point. The terminal can receive the MAC CE from the base station and identify the N path loss offset values activated by the code points included in the MAC CE. In other words, the terminal can check N path loss offset values mapped to code points included in the MAC CE.
[0203] A base station can generate a DCI including information indicating one path loss offset value among N path loss offset values activated by a MAC CE, and transmit the DCI to a terminal. The terminal can receive the DCI from the base station and determine one path loss offset value based on the information included in the DCI. The terminal can determine a transmission power considering the path loss offset value, and perform UL communication using the transmission power. The candidate path loss offset values indicated by RRC signaling can be set independently of a TCI state (e.g., a TCI state setting). Proposal #5-1 may be an extended method for Proposal #4-3.
[0204] Proposal #5-2
[0205] A base station can configure a list for UL power control (e.g., a list of other UL transmission parameters). There can be multiple alpha set groups associated with one UL power control ID (e.g., one power parameter list ID). The base station can transmit to a terminal a MAC CE or DCI including information indicating a single alpha set within the multiple alpha set groups associated with one UL power control ID. The terminal can receive the MAC CE or DCI from the base station and identify the single alpha set indicated by the information included in the MAC CE or DCI. In the embodiment of FIG. 10, a single alpha set can exist within an alpha set group. Based on the above-described method, multiple alpha sets can exist within an alpha set group. The number of multiple alpha sets belonging to an alpha set group can be equal to the maximum number of mTRPs.
[0206] Among multiple alpha sets, one alpha set can be indicated by a MAC CE or DCI. A single TCI state ID configured by RRC signaling can be associated with multiple alpha sets. The base station can transmit a MAC CE or DCI including information indicating a single alpha set among the multiple alpha sets to the terminal. The terminal can receive the MAC CE or DCI from the base station and identify the single alpha set indicated by the information included in the MAC CE or DCI. The terminal can apply the single alpha set to determine the transmission power for UL communication (e.g., PUSCH transmission, SRS transmission, PUCCH transmission). The alpha set can mean an alpha set for each of PUSCH (e.g., PUSCH transmission), SRS (e.g., SRS transmission), and PUCCH (e.g., PUCCH transmission). The alpha set can include an alpha, p0, and / or a CL index. In addition, the alpha set can further include a path loss offset.
[0207] Considering multiple UL TRPs, multiple path loss offset values as well as multiple UL power parameters (e.g., transmit power parameters) can be set to the terminal by RRC signaling. The base station can indicate to the terminal one or more of the multiple path loss offset values and / or one or more of the multiple UL power parameters using dynamic signaling (e.g., MAC CE and / or DCI). The terminal can identify one or more of the multiple path loss offset values and / or one or more of the multiple UL power parameters indicated by the RRC signaling and dynamic signaling of the base station. A single TCI state ID can be associated with at least multiple path loss offset values. The base station can transmit to the terminal a MAC CE or DCI including information indicating one of the multiple path loss offset values. The terminal can receive the MAC CE or DCI from the base station and identify one of the path loss offset values indicated by the information included in the MAC CE or DCI.
[0208] ● Proposal #5-3
[0209] Information indicating whether to use the path loss offset value indicated based on the above-described proposal(s) may be included in the MAC CE or DCI. The base station may transmit the MAC CE or DCI including the information indicating whether to use the path loss offset value to the terminal. In other words, the application or non-application of the path loss offset value may be dynamically signaled to the terminal. The terminal may receive the MAC CE or DCI from the base station and determine whether to use the path loss offset value based on the information included in the MAC CE or DCI.
[0210] A dedicated path loss offset value and / or a common path loss offset value for each TCI state can be set to the terminal by RRC signaling from the base station. Application or non-application of the path loss offset value (e.g., the dedicated path loss offset value or the common path loss offset value) can be indicated to the terminal by dynamic signaling from the base station (e.g., MAC CE or DCI). One bit in the DCI can be used to indicate application or non-application of the path loss offset value.
[0211] ● Proposal #5-4
[0212] The base station can transmit a path loss offset value associated with a TCI state to the terminal via RRC signaling. Alternatively, the base station can transmit a path loss offset value unrelated to the TCI state (e.g., a path loss offset value not associated with a TCI state) to the terminal via RRC signaling. The terminal can check the path loss offset value set by the RRC signaling of the base station. The base station can update the path loss offset value set by the RRC signaling using MAC CE or DCI. An absolute value or a relative value for the path loss offset value can be transmitted to the terminal. The path loss offset value set by the RRC signaling can be additionally corrected by MAC CE or DCI. The correction value by the MAC CE or DCI can be an absolute value or a relative value (e.g., a relative value for the path loss offset value set by the RRC signaling).
[0213] Information for updating (e.g., correcting) a path loss offset value may be included in a message other than an RRC message (e.g., a MAC CE or). The other message may refer to a signaling message. The terminal may update (e.g., correct) the path loss offset value based on information indicated by RRC signaling and dynamic signaling (e.g., a MAC CE or DCI). In other words, the terminal may use information (e.g., a value for correcting the path loss offset value) indicated by dynamic signaling (e.g., a MAC CE or DCI) to update (e.g., correct) the path loss offset value indicated by the RRC signaling. The terminal may determine the transmission power based on the updated path loss offset value and perform UL communication (e.g., UL transmission) using the transmission power.
[0214] Meanwhile, the base station can set (e.g., transmit) information about the path loss offset (e.g., the path loss offset value) to the terminal using an RRC message (e.g., RRC signaling). The terminal can receive the RRC message from the base station and check the information about the path loss offset included in the RRC message. The base station can send update information (e.g., correction information) about the path loss offset to the terminal using another message (e.g., MAC CE and / or DCI). The terminal can receive another message from the base station and check the update information included in the other message. The update information about the path loss offset can be set to the terminal by dynamic signaling. The terminal can update (e.g., correct) the path loss offset indicated by the RRC message based on the update information indicated by the other message. The terminal can determine the transmission power based on the updated path loss offset and perform UL communication (e.g., UL transmission) using the transmission power.
[0215] An RRC message may indicate a rough value for the path loss offset. For example, the difference between the first path loss offset and the second path loss offset indicated by the RRC message may be large. Other messages (e.g., MAC CE and / or DCI) may indicate a fine value for the path loss offset (e.g., a fine update value, a fine correction value). For example, the difference between the third path loss offset and the fourth path loss offset indicated by the other message may be small. The base station may first transmit information about the path loss offset (e.g., a rough value) to the terminal using an RRC message, and additionally transmit update information about the path loss offset (e.g., a fine value) to the terminal using another message.
[0216] In the present disclosure, a path loss offset can be set based on a PDCCH order. When a terminal requires UL communication (e.g., UL data transmission) for a UL TRP, a base station can instruct the terminal to perform a RACH procedure (e.g., an RA procedure) for the UL TRP by transmitting a PDCCH order (e.g., DCI for the PDCCH order) to the terminal. The PDCCH order can include information about a path loss offset. The terminal can receive the PDCCH order from the base station, and can determine whether performance of the RACH procedure for the UL TRP is required based on the PDCCH order, and can determine a path loss offset based on the PDCCH order.
[0217] The terminal can determine the transmission power based on the path loss offset and perform the RACH procedure for the UL TRP using the transmission power. For example, the terminal can transmit Msg1, Msg3, and / or MsgA using the transmission power determined based on the path loss offset. The legacy PDCCH order may not include information about the path loss offset. The DCI format for the PDCCH order that includes information about the path loss offset may be distinguished from the DCI format for the legacy PDCCH order.
[0218] ○ Proposal #6: Definition of a New DCI Format
[0219] A new DCI format other than the existing DCI (e.g., legacy DCI) for the PDCCH order may be defined. The legacy DCI for the PDCCH order may be DCI format 1_0 with a cyclic redundancy check (CRC) scrambled by a cell-RNTI (radio network temporary identifier). The new DCI format for the PDCCH order may include at least information about a path loss offset (e.g., a path loss offset value). Additionally, the new DCI format may include TCI state information. The information about the path loss offset included in the new DCI format and the TCI state information may be correlated with each other. The information about the path loss offset included in the new DCI format may indicate a relative value for the path loss between the DL TRP and the UE. A table for the relative value(s) for the path loss between the DL TRP and the UE may be configured in a format identical to or similar to Table 2. The new DCI format may include an index or code point indicating a value within the table (e.g., a path loss offset value, a relative value). Alternatively, a field included in the new DCI format may indicate an actual value for the path loss offset. The field indicating the actual value for the path loss offset may be set to M bits, where M may be a natural number.
[0220] ○ Proposal #7: Use of legacy DCI formats
[0221] A legacy DCI format for a PDCCH order may be used, and information about a path loss offset may be transmitted and received in a RACH procedure triggered by the legacy DCI format. Information about the path loss offset may mean an update value, a correction value, a correction coefficient, etc. for the path loss offset. Information about the path loss offset may be included in Msg2, Msg4, and / or MsgB. Msg2, Msg4, and / or MsgB may further include TCI state information. Information about the path loss offset and TCI state information included in Msg2, Msg4, and / or MsgB may be correlated with each other.
[0222] A terminal can receive a legacy DCI order from a base station and perform a RACH procedure based on the legacy DCI order. The RACH procedure can be performed between the terminal and a UL TRP. In the RACH procedure, the terminal can receive Msg2, Msg4, or MsgB including "information about path loss offset" or "information about path loss offset and TCI state information." The terminal can determine transmission power based on the information about path loss offset received in the RACH procedure, and perform UL TRP and UL communication using the transmission power. In the 4-step RA procedure, transmission of Msg3 can be performed using the transmission power determined based on the information about path loss offset.
[0223] ○ Proposal #8: Use of RRC messages and / or MAC CE
[0224] The base station can generate an RRC message and / or MAC CE including TCI state information and information about a path loss offset, and transmit the RRC message and / or MAC CE to the terminal. The terminal can receive the RRC message and / or MAC CE from the base station, and check information (e.g., TCI state information and path loss offset) included in the RRC message and / or MAC CE. The TCI state information and the path loss offset included in the RRC message and / or MAC CE can be associated with each other. For example, the RRC message and / or MAC CE can include a path loss offset associated with each TCI state.
[0225] In a RACH procedure based on a PDCCH order, a base station can generate a PDCCH order including TCI state information associated with a path loss offset, and transmit the PDCCH order to a terminal. The terminal can receive the PDCCH order from the base station and check information included in the PDCCH order. For example, the terminal can check the TCI state information included in the PDCCH order, and check the path loss offset associated with the TCI state information (e.g., a TCI state indicated by the TCI state information). In other words, the terminal can check the path loss offset associated with the TCI state indicated by the PDCCH order among path loss offsets preset by an RRC message and / or MAC CE. The terminal can determine the transmission power based on the path loss offset, and perform the RACH procedure (e.g., Msg1 transmission, Msg3 transmission, MsgA transmission) using the transmission power.
[0226] ○ Proposal #9: Indicate whether to apply or not to apply path loss offset.
[0227] The base station can transmit to the terminal "information indicating application of a path loss offset" or "information indicating non-application of a path loss offset" using at least one of an RRC message, MAC CE, or DCI. The terminal can receive at least one of an RRC message, MAC CE, or DCI from the base station, and can determine application or non-application of a path loss offset based on information included in the received message (e.g., the RRC message, MAC CE, and / or DCI). One or more path loss offsets can be preset in the base station and the terminal, and information indicating application or non-application of at least one of the one or more path loss offsets can be indicated by at least one of the RRC message, MAC CE, or DCI.
[0228] When application of a path loss offset is indicated, the terminal can determine the transmission power considering the path loss offset and perform UL communication (e.g., RACH procedure) using the transmission power. When non-application of a path loss offset is indicated, the terminal can determine the transmission power without considering the path loss offset and perform UL communication (e.g., RACH procedure) using the transmission power.
[0229] Considering the mobility and / or communication environment of the terminal, the base station can dynamically control whether to apply or not to apply a path loss offset. The base station can transmit an RRC message including information on a plurality of path loss offsets to the terminal, and can transmit a dynamic signaling message (e.g., MAC CE and / or DCI) including information indicating whether to apply or not to apply at least one path loss offset among the plurality of path loss offsets indicated by the RRC message to the terminal. The terminal can receive the RRC message from the base station and confirm the plurality of path loss offsets indicated by the RRC message. The terminal can receive a dynamic signaling message (e.g., MAC CE and / or DCI) from the base station, and can confirm whether to apply or not to apply at least one path loss offset among the plurality of path loss offsets based on information included in the dynamic signaling message.
[0230] In the embodiments described above, the TCI status information can be replaced with an SSB index. The terminal can determine the reception direction (e.g., reception beam) of the SSB having the SSB index as the transmission direction (e.g., transmission beam) and transmit an RA preamble in the transmission direction. The SSB index can be an SSB index set (e.g., indicated) to the terminal by the base station. Alternatively, the SSB index can be an SSB index determined based on the measurement results of the terminal.
[0231] A base station can generate a candidate list for path loss offsets. The candidate list can include one or more candidate path loss offsets. A candidate path loss offset can refer to a path loss offset that can be transmitted to a terminal. The base station can generate RACH configuration information (e.g., system information and / or an RRC message) including a candidate list for path loss offsets and transmit the RACH configuration information to the terminal. The terminal can receive the RACH configuration information from the base station and check the candidate list for path loss offsets included in the RACH configuration information.
[0232] The base station can transmit to the terminal at least one of DCI, Msg2, Msg4, or MsgB, which includes information indicating one path loss offset (e.g., candidate path loss offset) in the candidate list. The terminal can receive at least one of DCI, Msg2, Msg4, or MsgB from the base station, and can identify one path loss offset indicated by the information included in the message (e.g., DCI, Msg2, Msg4, and / or MsgB). The terminal can determine a transmission power based on the one path loss offset, and can perform UL communication using the transmission power.
[0233] A terminal may transmit information indicating whether it supports the function(s) proposed (e.g., described) in the present disclosure to a base station. The information indicating whether the function(s) are supported may be included in a UE capability report transmitted by the terminal. The base station may receive information indicating whether the function(s) are supported from the terminal, generate information for the terminal based on whether the function(s) are supported, and transmit the generated information to the terminal via signaling. The terminal may receive the information generated based on whether the function(s) are supported via signaling from the base station, and perform the function(s) based on the information.
[0234] FIG. 13 is a flowchart illustrating embodiments of a UL communication method in an asymmetric TRP system.
[0235] Referring to FIG. 13, an asymmetric TRP system may include a first TRP, a second TRP, and a terminal. The first TRP may be a first TRP forming a macro cell as illustrated in FIG. 9. The first TRP may refer to a serving cell, a serving base station, etc. The second TRP may be a second TRP forming a micro cell as illustrated in FIG. 9. The communication coverage (e.g., service coverage) of the first TRP may be wider than the communication coverage (e.g., service coverage) of the second TRP. The terminal may be a terminal located in an overlapping area between the macro cell and the micro cell as illustrated in FIG. 9. The terminal may perform DL communication with the first TRP. The terminal may perform UL communication with the first TRP and the second TRP. Alternatively, the terminal may perform UL communication with the second TRP. The first TRP may transmit a path loss offset value to the terminal through signaling (S1301). The path loss offset value can be determined by the first TRP or a base station associated with the first TRP. The path loss offset value can be set based on the above-described proposal(s) (e.g., proposal #1, proposal #2, proposal #2-1, proposal #2-2, proposal #3, proposal #4, proposal #4-1, proposal #4-2, proposal #4-3, proposal #5, proposal #5-1, proposal #5-2, proposal #5-3, proposal #5-4, proposal #6, proposal #7, proposal #8, and / or proposal #9). The first TRP can indicate the path loss offset value to the terminal through signaling based on the above-described proposal(s).
[0236] The terminal can receive a path loss offset value through signaling from the base station (S1301). The terminal can determine the transmission power for UL communication with the second TRP based on the path loss offset value (S1302). The terminal can determine the transmission power based on the following mathematical expression 1 or 2. In the following mathematical expression 1 or 2, PL offsetcan be a path loss offset (e.g., path loss offset value). In Equation 1 below or Equation 2 below, may be a path loss determined based on the measurement results of a reference signal (or synchronization signal) received from the first TRP.
[0237]
[0238]
[0239] PUSCH occasion i is the slot index within the SFN (system frame number). can be defined as μ can be the subcarrier spacing (SCS) for PUSCH. s can be the start symbol of PUSCH. may refer to the carrier of the serving cell (c). PUSCH may be set in a section of length L from the start symbol (s). can be used as an argument to distinguish between sets of parameters (e.g., parameter groups). can be used as a factor for distinguishing the power control adjustment state. b can be used to indicate the active BWP in which the PUSCH is transmitted. can indicate the resource index of RS for measuring path loss.
[0240] When a common path loss offset value is set in the terminal, the terminal can determine the transmission power for UL communication with the second TRP by applying the common path loss offset value regardless of the TCI state for the second TRP. When dedicated path loss offset value(s) are set in the terminal, the terminal can determine the transmission power for UL communication with the second TRP by applying a dedicated path loss offset value associated with (e.g., mapped to) the TCI state for the second TRP among the dedicated path loss offset value(s).
[0241] The terminal may perform UL communication with the second TRP using the transmission power determined in S1302 (S1303). In other words, the terminal may transmit a PUSCH, an SRS, and / or a PUCCH to the second TRP. The transmission power for each of the SRS transmission and the PUCCH transmission may be determined using Equation 1, an equation similar to Equation 1, an equation 2, or an equation similar to Equation 2. The second TRP may receive a PUSCH, an SRS, and / or a PUCCH from the terminal (S1303). The second TRP may expect that the transmission power of the UL transmission received from the terminal is determined based on Equation 1, an equation similar to Equation 1, an equation 2, or an equation similar to Equation 2.
[0242] The terminal may determine the transmission power for UL communication with the first TRP (S1304). The transmission power for UL communication with the first TRP may be determined based on the following mathematical expression 3. The transmission power for UL communication with the first TRP may be determined without considering the path loss offset value.
[0243]
[0244] The terminal may perform UL communication with the first TRP using the transmission power determined in S1304 (S1305). In other words, the terminal may transmit a PUSCH, an SRS, and / or a PUCCH to the first TRP. The transmission power for each of the SRS transmission and the PUCCH transmission may be determined using Equation 3 or a mathematical formula similar to Equation 3. The first TRP may receive a PUSCH, an SRS, and / or a PUCCH from the terminal (S1305). The first TRP may expect that the transmission power of the UL transmission received from the terminal is determined based on Equation 3 or a mathematical formula similar to Equation 3. The transmission power determined in S1304 may be different from the transmission power determined in S1302. For example, the transmission power determined in S1304 may be greater than or equal to the transmission power determined in S1302.
[0245] In the present disclosure, path loss offset values can be classified into common path loss offset values and dedicated path loss offset values. The common path loss offset value may be a path loss offset value that is commonly applicable regardless of the TCI state. In other words, the path loss offset value may be applicable to all TCI states. The dedicated path loss offset value may be associated with one or more TCI states. A terminal may basically expect that a common path loss offset value is set (e.g., indicated) to the terminal. If a common path loss offset value is not set to the terminal, the terminal may expect that a dedicated path loss offset value is set to the terminal.
[0246] The base station can set a common path loss offset value to the terminal by default. If it is determined that setting a dedicated path loss offset value is necessary, the base station can set a dedicated path loss offset value to the terminal without setting a common path loss offset value. Alternatively, the base station can set a common path loss offset value to the terminal by default, and if it is determined that setting a dedicated path loss offset value is necessary, it can additionally set the dedicated path loss offset value to the terminal. In other words, both the common path loss offset value and the dedicated path loss offset value can be set to the terminal. The common path loss offset value may mean a default path loss offset value, and the dedicated path loss offset value may mean an additional path loss offset value.
[0247] When both a common path loss offset value and a dedicated path loss offset value are set in a terminal, the terminal can select one path loss offset value from among the common path loss offset value and the dedicated path loss offset value, and determine the transmission power using the selected one path loss offset value. The terminal can select one path loss offset value with a higher priority from among the common path loss offset value and the dedicated path loss offset value. The common path loss offset value may have a higher priority than the dedicated path loss offset value. Alternatively, the dedicated path loss offset value may have a higher priority than the common path loss offset value. The priorities for the path loss offset values may be predefined in the technical specification. A change of the TCI state may be indicated before a UL transmission (e.g., UL communication) for a UL TRP is indicated (e.g., requested). Therefore, the dedicated path loss offset value may have a higher priority than the common path loss offset value.
[0248] The path loss offset value can be set in the terminal based on at least one of system information, RRC signaling, MAC CE, or DCI. The terminal can be expected to determine the transmission power for the UL transmission using the path loss offset value indicated by the message (e.g., signaling message, signal) received at the time closest to the time point of performing the UL transmission in the time domain. In other words, the terminal can receive the path loss offset values from the base station at multiple time points before the time point of performing the UL transmission, and can determine the transmission power for the UL transmission using the path loss offset value indicated by the signaling received at the time point closest to the UL transmission in the time domain among the path loss offset values.
[0249] For example, the terminal may receive a common path loss offset value from the base station at a first time point, and may receive a dedicated path loss offset value from the base station at a second time point after the first time point in the time domain, and may determine a transmit power for the UL transmission at a third time point after the second time point in the time domain using the dedicated path loss offset value indicated at the second time point adjacent to the third time point for UL transmission. As another example, the terminal may receive a dedicated path loss offset value from the base station at a first time point, and may receive a common path loss offset value from the base station at a second time point after the first time point in the time domain, and may determine a transmit power for the UL transmission at a third time point after the second time point in the time domain using the common path loss offset value indicated at the second time point adjacent to the third time point for UL transmission.
[0250] Considering the delay in the network, the priority of signaling indicating a path loss offset value can be set. DCI can have the highest priority, MAC CE can have a lower priority than the DCI, and RRC signaling can have a lower priority than the MAC CE. When multiple path loss offset values are set in a terminal by multiple signalings, the terminal can select one path loss offset value among the multiple path loss offset values considering the signaling priority, and determine the transmission power for UL transmission using the selected one path loss offset value. For example, when a DCI indicating a first path loss offset value and a MAC CE indicating a second path loss offset value are received, since the DCI has a higher priority than the MAC CE, the terminal can determine the transmission power for UL transmission using the first path loss offset value indicated by the DCI.
[0251] The terminal may update the path loss offset value by considering the signaling priority. For example, if a MAC CE indicating a second path loss offset value is received after receiving a DCI indicating a first path loss offset value, the terminal may not update the first path loss offset value to the second path loss offset value because the DCI has a higher priority than the MAC CE. For another example, if a DCI indicating a second path loss offset value is received after receiving a MAC CE indicating a first path loss offset value, the terminal may update the first path loss offset value to the second path loss offset value because the DCI has a higher priority than the MAC CE.
[0252] Meanwhile, the terminal can perform UL communication (e.g., UL transmission) for UL TRP as well as DL TRP. In other words, the terminal can perform UL communication for all TRPs. The terminal can support up to two TRPs. Power correction (e.g., a power correction value) for each TRP may be required. In the TRP system, a CL (closed loop)-based power correction procedure for each TRP may be performed. For example, the terminal can determine the transmission power for UL communication for the first TRP by performing a CL-based power correction procedure (e.g., a CL-based power control procedure) for a first TRP (e.g., a DL TRP), and the terminal can determine the transmission power for UL communication for the second TRP (e.g., a UL TRP) by performing a CL-based power correction procedure for the second TRP. The fact that a CL-based power compensation procedure is performed for each of the two TRPs may mean that "the two closed loop power control (CLPC) adjustment states are independent closed loops." The number of CLPC adjustment states may increase or decrease depending on the maximum number of TRPs supported by the terminal. The number of CLPC adjustment states may be equal to the maximum number of TRPs supported by the terminal.
[0253] A base station can transmit configuration information (e.g., SRS configuration information) including SRS power control adjustment states (e.g., srs-PowerControlAdjustmentStates) to a terminal via signaling. The terminal can receive the configuration information from the base station and check information (e.g., sameAsFci2 or separateClosedLoop) indicated by the SRS power control adjustment states included in the configuration information. When the SRS power control adjustment states are set to independent CL (e.g., separateClosedLoop), the terminal can determine that a CL-based power adjustment procedure for each of the TRPs is performed. When the SRS power control adjustment states are set to independent CL (e.g., separateClosedLoop), the base station can transmit information (e.g., power control information) for a CL-based power adjustment procedure for each of the TRPs to the terminal.
[0254] A method may be needed to establish a mapping between CLPC control states and TRPs. For example, rules for establishing a mapping between CLPC control states and TRPs may be needed. A method may also be needed to distinguish CLPC control states mapped to TRPs. For example, an identifier (e.g., an index) may be needed to distinguish CLPC control states.
[0255] CLPC throttle states can be associated with TCI states (e.g., UL TCI states), and TCI states (e.g., UL TCI states) can be associated with SRS resource sets (e.g., SRS). In other words, CLPC throttle states can be associated with SRS resource sets. For example, CLPC throttle state #0 can be associated with SRS resource set #0, and CLPC throttle state #1 can be associated with SRS resource set #1. A mapping relationship for CLPC throttle state #0 - TCI state #0 - SRS resource set #0 can be established. A mapping relationship for CLPC throttle state #1 - TCI state #1 - SRS resource set #1 can be established.
[0256] Alternatively, CLPC control states can be associated with DL TCI states or CORESET indices. CLPC control states can be associated (e.g., mapped) to SRS resource sets, TCI states (e.g., UL TCI states or DL TCI states), or CORESET indices in descending or ascending order. A base station can transmit a transmit power control (TPC) command for a CLPC control state to a terminal. A terminal can receive a TPC command for a CLPC control state from the base station. If the TPC command is associated with CLPC control state #0, the terminal can use the TPC command to determine the transmit power for UL communication with a TRP associated with the TCI state (or SRS resource set) mapped to CLPC control state #0. When a TPC command is associated with CLPC control state #1, the terminal may use the TPC command to determine the transmit power for UL communication with the TRP associated with the TCI state (or SRS resource set) mapped to CLPC control state #1. The TPC command is expressed in the mathematical expressions 1 to 3 described above. can be used to determine. Or, the TPC command is in the mathematical expressions 1 to 3 described above. It can be used to determine other parameters.
[0257] SRS resource set #0 can be explicitly or implicitly associated with CLPC control state #0. SRS resource set #1 can be explicitly or implicitly associated with CLPC control state #1. The base station can transmit association information (e.g., mapping information) between the SRS resource set (or TCI state) and the CLPC control state to the terminal through signaling. The message for the signaling can be at least one of an RRC message, MAC CE, or DCI. The terminal can receive association information between the SRS resource set (or TCI state) and the CLPC control state through signaling from the base station.
[0258] The base station can transmit to the terminal an RRC message including at least one of association information between an SRS resource set (or TCI state) and a CLPC control state, a CLPC control state index, or power control information. The power control information can include at least one of a p0, alpha, CL, or TPC command. The power control information can be power control information for each CLPC control state (e.g., CLPC control state). The RRC message can include association information and / or power control information for an SRS resource set corresponding to each of one or more CLPC control state indices. The terminal can receive the RRC message from the base station and check information included in the RRC message (e.g., association information between an SRS resource set (or TCI state) and a CLPC control state, a CLPC control state index, and / or power control information). The base station can transmit to the terminal another signaling message (e.g., MAC CE and / or DCI) including one index.
[0259] The terminal can receive another signaling message from the base station and identify one index included in the another signaling message. The one index may be an SRS resource set index, a TCI state index (e.g., a TCI state ID), and / or a CLPC throttling state index. When the one index is an SRS resource set index or a TCI state index, the terminal can identify a CLPC throttling state (e.g., a CLPC throttling state index) associated with the SRS resource set index or the TCI state index, determine transmission power based on power control information associated with the CLPC throttling state, and perform UL communication using the transmission power. The UL communication may be UL communication with TRP(s) associated with the SRS resource set index or the TCI state index corresponding to the CLPC throttling state. When the one index is a CLPC throttling state index, the terminal can determine transmission power based on power control information associated with the CLPC throttling state, and perform UL communication using the transmission power. The above UL communication may be UL communication with TRP(s) associated with an SRS resource set index or TCI state index corresponding to a CLPC control state.
[0260] Whether multiple CLPC adjustment states are supported can be determined based on the configuration of the upper layer parameter SRS power control adjustment states (e.g., srs-PowerControlAdjustmentStates). If the SRS power control adjustment states are set to independent CL (e.g., separateClosedLoop), the configuration can indicate that multiple CLPC adjustment states are supported. The base station can transmit an RRC message including the SRS power control adjustment states to the terminal. The terminal can receive the RRC message from the base station and determine whether multiple CLPC adjustment states are supported based on the configuration of the SRS power control adjustment states included in the RRC message (e.g., sameAsFci2 or separateClosedLoop). Alternatively, the base station can transmit information indicating whether multiple CLPC adjustment states are supported to the terminal using MAC CE and / or DCI. The terminal can determine whether multiple CLPC adjustment states are supported based on the information included in the MAC CE and / or DCI received from the base station.
[0261] When multiple CLPC control states are supported, the base station can transmit to the terminal a signaling message (e.g., an RRC message, MAC CE, and / or DCI) that includes information indicating whether each of the multiple CLPC control states is used (e.g., an enable indication or a disable indication). The terminal can receive the signaling message from the base station and determine whether each of the multiple CLPC control states is used based on the information included in the signaling message. For example, when CLPC control state #0 is used, the terminal can determine the transmit power based on the path loss offset associated with the SRS resource set mapped to CLPC control state #0, and perform UL communication with the TRP associated with the SRS resource set using the transmit power.
[0262] When multiple CLPC throttle states are supported (e.g., when a terminal supports multiple CLPC throttle states), the base station may transmit a TPC command for each of the multiple CLPC throttle states to the terminal. A TPC command for CLPC throttle state #0 (e.g., a first CLPC throttle state) may be referred to as TPC command #0 (e.g., a first TPC command). A TPC command for CLPC throttle state #1 (e.g., a second CLPC throttle state) may be referred to as TPC command #1 (e.g., a second TPC command). The TPC command may be included in DCI (e.g., DCI format 0_1, DCI format 0_2, and / or DCI format 2_3). A method may be needed to distinguish which CLPC throttle state a TPC command transmitted by the base station is for. In other words, mapping information (e.g., linkage information) between TPC commands and CLPC throttle states may be needed.
[0263] A base station can transmit mapping information between a TPC command and a CLPC control state to a terminal using a signaling message (e.g., an RRC message, a MAC CE, and / or DCI). The terminal can receive the signaling message from the base station and check the mapping information between the TPC command and the CLPC control state included in the signaling message. The mapping between the TPC command and the CLPC control state can be set on a group basis (e.g., a terminal group). In this case, the mapping information between the TPC command and the CLPC control state can be included in DCI format 2_3. Alternatively, the mapping between the TPC command and the CLPC control state may not be set on a group basis (e.g., a terminal group). In other words, the mapping between the TPC command and the CLPC control state can be set on a terminal basis. In this case, the mapping information between the TPC command and the CLPC control state can be included in DCI format 0_1, DCI format 0_2, DCI format 1_1, and / or DCI format 1_2. Alternatively, a new DCI format containing mapping information between TPC commands and CLPC control states can be defined. Combinations of the above methods can be supported.
[0264] When an existing DCI format (e.g., DCI format 0_1, DCI format 0_2, DCI format 1_1, DCI format 1_2, DCI format 2_3) is used, the reserved bit(s) included in the existing DCI format can be used to indicate a CLPC throttling state index. One bit can be used to indicate a CLPC throttling state index. For example, a bit set to a first value (e.g., 0) can indicate CLPC throttling state index #0, and a bit set to a second value (e.g., 1) can indicate CLPC throttling state index #1. When any field included in the DCI indicates CLPC throttling state index #0, information included in the DCI (e.g., scheduling information, power control information (e.g., TPC command), TCI state information, SRS related information) can be used for CLPC throttling state index #0. If any field included in the DCI indicates CLPC throttling state index #1, information included in the DCI (e.g., scheduling information, power control information (e.g., TPC command), TCI state information, SRS related information) may be used for CLPC throttling state index #1. "Information included in the DCI being used for a certain CLPC throttling state index" may mean "information included in the DCI being used for communication with a TRP associated with a certain CLPC throttling state index."
[0265] Alternatively, information for communicating with each of the plurality of TRPs may be included in a single DCI (e.g., a payload of a single DCI). For example, a single DCI may include information for communicating with a first TRP (e.g., scheduling information, power control information, TCI state information, SRS-related information) and information for communicating with a second TRP (e.g., scheduling information, power control information, TCI state information, SRS-related information). The power control information may include a CL index, a TPC command, and / or a CLPC throttled state index. Any field included in the DCI (e.g., a field having a size of 1 bit) may indicate that the DCI includes a plurality of pieces of power control information. Alternatively, a distinguishing factor for the CLPC throttled state may be included in the MAC CE. The CLPC throttled state may be applied to UL transmissions (e.g., SRS transmissions, PUCCH transmissions, and / or PUCCH transmissions).
[0266] Figure 14 is a flowchart illustrating embodiments of a UL communication method in a TRP system.
[0267] Referring to FIG. 14, a TRP system may include a base station, a first TRP, a second TRP, and a terminal. The first TRP and the second TRP may be linked to the base station. In other words, the first TRP and the second TRP may be connected to the base station. Alternatively, the first TRP may function as a base station. The TRP system to which the embodiment of FIG. 14 is applied may be a general TRP system or an asymmetric TRP system (e.g., the asymmetric TRP system illustrated in FIG. 9). The general TRP system may refer to a TRP system other than an asymmetric TRP system. The terminal may perform DL communication with the first TRP and / or the second TRP. The terminal may perform UL communication with the first TRP and / or the second TRP. The terminal may be located in an overlapping area between the communication coverage (e.g., service coverage) of the first TRP and the communication coverage (e.g., service coverage) of the second TRP.
[0268] A base station may generate CLPC configuration information. The CLPC configuration information may include at least one of information indicating that a plurality of CLPC throttle states are supported (e.g., two CLPC throttle states), an index of each of the plurality of CLPC throttle states (e.g., a CLPC throttle state index), power control information of each of the plurality of CLPC throttle states (e.g., p0, alpha, CL (closed loop) (e.g., CL index), TPC command), information indicating that two TPC commands are set in DCI for the plurality of CLPC throttle states, mapping information between the plurality of CLPC throttle states and the plurality of TCI states, mapping information between the plurality of CLPC throttle states and the plurality of SRS resource sets (e.g., the plurality of SRSs), or mapping information between the plurality of CLPC throttle states and the plurality of CORESETs.
[0269] For example, information indicating that multiple CLPC adjustment states (e.g., two CLPC adjustment states) are supported may be ClosedLoopPowerControlAdjustmentStates (e.g., srs-PowerControlAdjustmentStates) set to independent CL (e.g., separateClosedLoop). Alternatively, SRS power control adjustment states (e.g., srs-PowerControlAdjustmentStates) set to independent CL (e.g., separateClosedLoop) may indicate that multiple CLPC adjustment states (e.g., two CLPC adjustment states) are supported.
[0270] A base station may transmit a signaling message (e.g., an RRC message, MAC CE, and / or DCI) including CLPC configuration information to a terminal (S1401). The signaling message may be referred to as a first message. The terminal may receive a signaling message including CLPC configuration information from the base station (S1401). The terminal may check information included in the CLPC configuration information. The base station may generate DCI. The DCI may include information (e.g., scheduling information, power control information, TPC information, and / or SRS-related information) for communication (e.g., UL communication) with one TRP. For example, the DCI may include one CLPC control state index and one power control information (e.g., a TPC command and / or a CL index). The DCI may include TCI state information, and an SRS (e.g., an SRS resource set) associated with the TCI state information may indicate one CLPC control state. The base station may transmit DCI to the terminal (S1402). The terminal may receive DCI from the base station (S1402). The DCI may be referred to as a second message.
[0271] The terminal can check a CLPC throttling state index based on information included in the DCI, and can determine that the scheduling information included in the DCI is scheduling information for communication with a TRP (e.g., a first TRP) associated with the CLPC throttling state index. The terminal can determine that the power control information (e.g., a TPC command and / or a CL index) included in the DCI is power control information for communication with a TRP (e.g., a first TRP) associated with the CLPC throttling state index. Alternatively, the CL index of an SRS (e.g., an SRS resource set) associated with a TCI state included in the DCI can indicate one CLPC throttling state (e.g., one CLPC throttling state index), and the terminal can determine that the scheduling information included in the DCI is scheduling information for communication with a TRP (e.g., a first TRP) associated with one CLPC throttling state (e.g., one CLPC throttling state index). The terminal may determine that power control information (e.g., a TPC command and / or a CL index) included in the DCI is power control information for communication with a TRP (e.g., a first TRP) associated with one CLPC throttled state (e.g., one CLPC throttled state index). A first value (e.g., i0) of the CL index of an SRS (e.g., an SRS resource set) associated with the TCI state may indicate the first CLPC throttled state, and a second value (e.g., i1) of the CL index of an SRS (e.g., an SRS resource set) associated with the TCI state may indicate the second CLPC throttled state.
[0272] The CLPC throttling state index can be mapped to an SRS resource set (e.g., SRS), a TCI state, and / or a CORESET, and the terminal can identify a TRP (e.g., a first TRP) associated with the CLPC throttling state index based on the mapping relationship. The terminal can determine the transmission power based on the power control information (e.g., a TPC command and / or a CL index) associated with the CLPC throttling state index (S1403). The power control information associated with the CLPC throttling state index is expressed in the above-described mathematical expressions 1 to 3. can be used to determine the power control information. The power control information can be a TPC command and / or a CL index. may be a power control state (e.g., PUSCH power control state, PUCCH power control state, SRS power control state). The terminal selects a "new power control state based on the existing power control state + power control information (e.g., CL index) linked to the CLPC control state index." can be decided, and the decided The transmission power can be determined based on the transmission power. The terminal can perform UL communication (e.g., PUCCH transmission, PUSCH transmission, and / or SRS transmission) with the first TRP using the transmission power (S1404). The first TRP can receive UL transmission from the terminal (S1404).
[0273] Alternatively, the DCI generated by the base station may include information (e.g., scheduling information, power control information, TCI state information, and / or SRS-related information) for communication (e.g., UL communication) of multiple TRPs. For example, the DCI may include information for communication with a first TRP and information for communication with a second TRP. The DCI may include two pieces of TCI state information, two CLPC control state indices, two TPC commands, and / or two CL indices. The base station may transmit the DCI to the terminal (S1402). The terminal may receive the DCI from the base station (S1402).
[0274] The terminal can check two CLPC throttling state indices included in the DCI, and can determine that the scheduling information (e.g., first scheduling information) included in the DCI is scheduling information for communication with a first TRP associated with the first CLPC throttling state index. The terminal can determine that the first power control information (e.g., first TPC command and / or first CL index) included in the DCI is power control information for communication with a first TRP associated with the first CLPC throttling state index. The terminal can determine that the scheduling information (e.g., second scheduling information) included in the DCI is scheduling information for communication with a second TRP associated with the second CLPC throttling state index. The terminal can determine that the second power control information (e.g., second TPC command and / or second CL index) included in the DCI is power control information for communication with a second TRP associated with the second CLPC throttling state index.
[0275] Alternatively, the CL index of the first SRS (e.g., the first SRS resource set) associated with the first TCI state included in the DCI may indicate the first CLPC throttling state (e.g., the first CLPC throttling state index), and the terminal may determine that the scheduling information included in the DCI is scheduling information for communication with a TRP (e.g., the first TRP) associated with the first CLPC throttling state (e.g., the first CLPC throttling state index). The terminal may determine that the first power control information (e.g., the first TPC command and / or the first CL index) included in the DCI is power control information for communication with a TRP (e.g., the first TRP) associated with the first CLPC throttling state (e.g., the first CLPC throttling state index). A CL index of a second SRS (e.g., a second SRS resource set) associated with a second TCI state included in the DCI may indicate a second CLPC throttling state (e.g., a second CLPC throttling state index), and the terminal may determine that scheduling information included in the DCI is scheduling information for communication with a TRP (e.g., a second TRP) associated with the second CLPC throttling state (e.g., the second CLPC throttling state index). The terminal may determine that second power control information (e.g., a second TPC command and / or a second CL index) included in the DCI is power control information for communication with a TRP (e.g., a second TRP) associated with the second CLPC throttling state (e.g., the second CLPC throttling state index).
[0276] The CLPC adjustment state index may be mapped to an SRS resource set, a TCI state, and / or a CORESET, and the terminal may identify a first TRP and a second TRP associated with each of the first and second CLPC adjustment state indices based on the mapping relationship. The terminal may determine transmission power based on first power control information associated with the first CLPC adjustment state index and / or a CL index corresponding to the first CLPC adjustment state index (S1403). The terminal may determine transmission power based on second power control information associated with the second CLPC adjustment state index and / or a CL index corresponding to the second CLPC adjustment state index (S1403). The power control information associated with each of the first and second CLPC adjustment state indices (e.g., the first power control information and the second power control information) may be expressed as in the above-described mathematical expressions 1 to 3. can be used to determine. The terminal can perform UL communication (e.g., PUCCH transmission, PUSCH transmission, and / or SRS transmission) with the first TRP using the transmission power determined based on the first power control information associated with the first CLPC adjustment state index (S1404). The first TRP can receive UL transmission from the terminal (S1404). The terminal can perform UL communication (e.g., PUCCH transmission, PUSCH transmission, and / or SRS transmission) with the second TRP using the transmission power determined based on the second power control information associated with the second CLPC adjustment state index (S1405). The second TRP can receive UL transmission from the terminal (S1405).
[0277] Embodiments of the present disclosure can be applied not only to an asymmetric TRP system but also to a general TRP system (e.g., a general communication system). In a general TRP system, a terminal can perform DL communication with n TRPs, and a terminal can perform UL communication with n TRPs. n can be a natural number. In other words, a terminal can perform DL communication and UL communication with the same TRPs (e.g., the same number of TRPs).
[0278] To set an appropriate transmission power in an asymmetric TRP system, improved methods for power parameter(s) may be proposed in the present disclosure. A base station, a TRP, and / or a terminal may perform operations for setting power parameter(s) (e.g., a path loss offset value) and / or determining transmission power based on a single proposal or a combination of multiple proposals.
[0279] The methods proposed in this disclosure can be applied to UL grant-based PUSCH transmission, grant-free PUSCH transmission, configured grant (CG) PUSCH transmission, and / or semi-persistent (SP) PUSCH transmission. The methods proposed in this disclosure can be applied not only to PUSCH transmission (e.g., UL-SCH (shared channel) transmission for an activated serving cell) but also to other UL transmissions (e.g., SRS transmission, PUCCH transmission, etc.). The methods proposed in this disclosure can be applied to sidelink communication, supplementary uplink (SUL) communication, etc. The methods proposed in this disclosure can be applied to licensed band communication as well as unlicensed band communication.
[0280] In the present disclosure, a base station may be interpreted as a cell (e.g., a serving cell) or a TRP (e.g., a serving TRP) depending on the context. In other words, the operation of the base station may be interpreted as the operation of a cell or a TRP depending on the context. A terminal may report information indicating whether it supports the function(s) proposed in the present disclosure to the base station. The information indicating whether the function(s) are supported may be included in a UE capability report (e.g., UE capability information) transmitted by the terminal. The base station may receive the UE capability report from the terminal, and may identify the function(s) supported by the terminal based on the information included in the UE capability report, and may perform signaling and / or operations for the identified function(s). The method proposed in the present disclosure may be used alone. A combination of the methods proposed in the present disclosure may be used. The methods proposed in the present disclosure may be performed independently or non-independently of the type of TCI state.
[0281] The operations of the method according to the present disclosure can be implemented as a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes any type of recording device that stores information readable by a computer system. Furthermore, a computer-readable recording medium can be distributed across network-connected computer systems, allowing the computer-readable program or code to be stored and executed in a distributed manner.
[0282] Additionally, the computer-readable recording medium may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. The program instructions may include not only machine language codes produced by a compiler, but also high-level language codes that can be executed by a computer using an interpreter, etc.
[0283] While some aspects of the present disclosure have been described in the context of a device, they may also represent a description of a corresponding method, wherein a block or device corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of a method may also be described as a corresponding block or item or a feature of a corresponding device. Some or all of the method steps may be performed by (or using) a hardware device, such as, for example, a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, at least one or more of the most significant method steps may be performed by such a device.
[0284] A programmable logic device (e.g., a field-programmable gate array) may be used to perform some or all of the functions of the methods described in the present disclosure. The field-programmable gate array may operate in conjunction with a microprocessor to perform one of the methods described in the present disclosure. In general, the methods are preferably performed by some hardware device.
[0285] Although the present disclosure has been described with reference to preferred embodiments thereof, it will be understood by those skilled in the art that various modifications and changes may be made to the present disclosure without departing from the spirit and scope of the present disclosure as set forth in the claims below.
Claims
1. As a method of UE (user equipment), A step of receiving a first message from a base station including information indicating that multiple closed loop power control (CLPC) adjustment states are supported; A step of receiving a second message from the base station, the second message including information indicating first power control information associated with a first CLPC regulation state among the plurality of CLPC regulation states; A step of determining a first transmission power based on the first power control information; and A step of transmitting a first uplink (UL) transmission to a first transmission and reception point (TRP) associated with the first CLPC control state using the first transmit power, UE's method.
2. In claim 1, The first message includes at least one of an index of each of the plurality of CLPC control states, power control information of each of the plurality of CLPC control states, information indicating that two transmit power control (TPC) commands are set in the second message for the plurality of CLPC control states, mapping information between the plurality of CLPC control states and a plurality of transmission configuration indicator (TCI) states, mapping information between the plurality of CLPC control states and a plurality of sounding reference signal (SRS) resource sets, or mapping information between the plurality of CLPC control states and a plurality of control resource sets (CORESETs). UE's method.
3. In claim 1, The first power control information includes at least one of a first CL (closed loop) index or a first TPC command. UE's method.
4. In claim 3, The above first CL index is a CL index for an SRS associated with the TCI status information included in the second message. UE's method.
5. In claim 1, The second message further includes information indicating second power control information associated with a second CLPC regulation state among the plurality of CLPC regulation states. UE's method.
6. In claim 5, A step of determining a second transmission power based on the second power control information; and Further comprising the step of transmitting a second UL transmission to a second TRP associated with the second CLPC control state using the second transmit power. UE's method.
7. In claim 1, The above first UL transmission is at least one of a PUCCH (physical uplink control channel) transmission, a PUSCH (physical uplink shared channel) transmission, or an SRS transmission. UE's method.
8. In claim 1, The first message is an RRC (radio resource control) message, and the second message is DCI (downlink control information). UE's method.
9. As a method of base station, A step of transmitting a first message to a UE (user equipment) including information indicating that multiple closed loop power control (CLPC) adjustment states are supported; and A step of transmitting to the UE a second message including information indicating first power control information associated with a first CLPC adjustment state among the plurality of CLPC adjustment states, The first transmission power determined based on the first power control information is used for the first UL (uplink) transmission for the first TRP (transmission and reception point) associated with the first CLPC adjustment state. Base station method.
10. In claim 9, The first message includes at least one of an index of each of the plurality of CLPC control states, power control information of each of the plurality of CLPC control states, information indicating that two transmit power control (TPC) commands are set in the second message for the plurality of CLPC control states, mapping information between the plurality of CLPC control states and a plurality of transmission configuration indicator (TCI) states, mapping information between the plurality of CLPC control states and a plurality of sounding reference signal (SRS) resource sets, or mapping information between the plurality of CLPC control states and a plurality of control resource sets (CORESETs). Base station method.
11. In claim 9, The first power control information includes at least one of a first CL (closed loop) index or a first TPC command. Base station method.
12. In claim 11, The above first CL index is a CL index for an SRS associated with the TCI status information included in the second message. Base station method.
13. In claim 9, The second message further includes information indicating second power control information associated with a second CLPC regulation state among the plurality of CLPC regulation states. Base station method.
14. In claim 13, The second transmission power determined based on the second power control information is used for the second UL transmission for the second TRP associated with the second CLPC adjustment state. Base station method.
15. As UE (user equipment), Contains at least one processor, At least one processor of the UE, Receiving a first message from a base station including information indicating that multiple closed loop power control (CLPC) adjustment states are supported; Receive a second message from the base station, the second message including information indicating first power control information associated with a first CLPC regulation state among the plurality of CLPC regulation states; Determine the first transmission power based on the first power control information; and Causing a first uplink (UL) transmission to be transmitted to a first transmission and reception point (TRP) associated with the first CLPC control state using the first transmit power; UE.
16. In claim 15, The first message includes at least one of an index of each of the plurality of CLPC control states, power control information of each of the plurality of CLPC control states, information indicating that two transmit power control (TPC) commands are set in the second message for the plurality of CLPC control states, mapping information between the plurality of CLPC control states and a plurality of transmission configuration indicator (TCI) states, mapping information between the plurality of CLPC control states and a plurality of sounding reference signal (SRS) resource sets, or mapping information between the plurality of CLPC control states and a plurality of control resource sets (CORESETs). UE.
17. In claim 15, The first power control information includes at least one of a first CL (closed loop) index or a first TPC command. UE.
18. In claim 17, The above first CL index is a CL index for an SRS associated with the TCI status information included in the second message. UE.
19. In claim 15, The second message further includes information indicating second power control information associated with a second CLPC regulation state among the plurality of CLPC regulation states. UE.
20. In claim 19, At least one processor of the UE, Determine the second transmission power based on the second power control information; and further causing a second UL transmission to be transmitted to a second TRP associated with the second CLPC control state using the second transmit power; UE.
Citation Information
Patent Citations
Wire for high frequency power transmission
KR1020240129505A