Method and device for beam management in wireless communication system
The unified TCI state method in 5G systems addresses beam management challenges, enhancing data transmission speeds and reliability by integrating downlink and uplink beam management for diverse services.
Patent Information
- Application Number
- PCT/KR2026/096637
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-20
- Filing Date
- 2026-05-06
- Publication Date
- 2026-11-12
AI Technical Summary
Existing 5G mobile communication systems face challenges in efficiently managing transmit and receive beams, particularly in ultra-high frequency bands, which affect data transmission speeds, coverage, and reliability for diverse services such as eMBB, mMTC, and URLLC.
A method and apparatus for managing transmit and receive beams using a unified TCI state that integrates both downlink and uplink beam management, allowing for efficient beam application through joint or separate TCI states, facilitated by MAC-CE and DCI-based instructions, to optimize beam alignment and resource allocation in 5G systems.
Enhances beam management in 5G systems, improving data transmission speeds, coverage, and reliability across various services by optimizing beam alignment and resource allocation, thereby supporting enhanced Mobile BroadBand (eMBB), massive Machine-Type Communications (mMTC), and Ultra-Reliable Low-Latency Communications (URLLC).
Smart Images

Figure KR2026096637_12112026_PF_FP_ABST
Abstract
Description
Method and device for beam management in a wireless communication system
[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method for managing transmit and receive beams in a wireless communication system and an apparatus capable of performing the same.
[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.
[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.
[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands to comply with various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.
[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.
[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).
[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.
[0008] According to one embodiment of the present disclosure, an apparatus and method capable of effectively providing services in a mobile communication system are provided.
[0009] According to one embodiment of the present disclosure, a method performed by user equipment (UE) may include: receiving configuration information associated with an uplink signal from a base station, wherein the configuration information includes information regarding resource sets corresponding to transmission configuration indicator (TCI) states; receiving information from the base station indicating a second TCI state different from a first TCI state set for the UE among the TCI states; identifying a resource set corresponding to the second TCI state based on the configuration information; and transmitting the uplink signal to the base station using the resource set based on the second TCI state.
[0010] According to one embodiment of the present disclosure, an apparatus and a method capable of effectively providing services in a wireless communication system may be provided.
[0011] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below.
[0012] FIG. 1 is a diagram illustrating the basic structure of the time-frequency domain in a wireless communication system according to one embodiment of the present disclosure.
[0013] FIG. 2 is a drawing illustrating a frame, subframe, and slot structure in a wireless communication system according to one embodiment of the present disclosure.
[0014] FIG. 3 is a drawing illustrating an example of a bandwidth portion setting in a wireless communication system according to one embodiment of the present disclosure.
[0015] FIG. 4 is a diagram of the beam application time that can be considered when using an integrated TCI method in a wireless communication system according to one embodiment of the present disclosure.
[0016] FIG. 5 is a diagram showing another MAC-CE structure for activating and indicating a joint TCI state or a separate DL or UL TCI state in a wireless communication system according to one embodiment of the present disclosure.
[0017] FIG. 6 is a diagram illustrating an example of setting a control area of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.
[0018] FIG. 7 is a diagram illustrating the structure of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.
[0019] FIG. 8 is a diagram showing a transmit / receive beam management method in a wireless communication system according to one embodiment of the present disclosure.
[0020] FIG. 9 is a diagram showing the operation of a terminal for transmitting and receiving beam management according to one embodiment of the present disclosure.
[0021] FIG. 10 is a diagram showing the operation of a base station for transmitting and receiving beam management according to one embodiment of the present disclosure.
[0022] FIG. 11 is a drawing illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.
[0023] FIG. 12 is a drawing illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.
[0024] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.
[0025] In describing the embodiments, technical details that are well known in the art to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.
[0026] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the dimensions of each component do not entirely reflect their actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference numbers.
[0027] The advantages and features of the present disclosure, and the methods for achieving them, will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components. Furthermore, in describing the present disclosure, if it is determined that a detailed description of a related function or configuration might unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout the specification.
[0028] Hereinafter, the base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. The terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. In this disclosure, the Downlink (DL) refers to the wireless transmission path of a signal transmitted by the base station to the terminal, and the Uplink (UL) refers to the wireless transmission path of a signal transmitted by the terminal to the base station. Furthermore, while LTE or LTE-A systems may be described as examples below, embodiments of this disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technologies (5G, new radio, NR) developed after LTE-A may be included therein, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.
[0029] At this point, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing instruction means to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).
[0030] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to their corresponding functions.
[0031] In this embodiment, the term "part" refers to a software or hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Thus, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.
[0032] Wireless communication systems are evolving from providing early voice-oriented services to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards like 3GPP’s HSPA (High Speed Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2’s HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE’s 802.16e.
[0033] As a representative example of a broadband wireless communication system, the LTE system employs the Orthogonal Frequency Division Multiplexing (OFDM) method for the downlink (DL) and the Single Carrier Frequency Division Multiple Access (SC-FDMA) method for the uplink (UL). The uplink refers to a wireless link through which a terminal (User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (eNode B, or base station (BS)), and the downlink refers to a wireless link through which a base station transmits data or control signals to a terminal. The above multiple access method can distinguish the data or control information of each user by allocating and operating time-frequency resources to be sent for each user so that they do not overlap, that is, so that orthogonality is established.
[0034] As a future communication system following LTE, that is, a 5G communication system, it must be able to freely reflect the diverse requirements of users and service providers, and therefore, services that satisfy various requirements simultaneously must be supported. Services being considered for the 5G communication system include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).
[0035] eMBB aims to provide data transmission speeds that are superior to those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to provide a peak data rate of 20 Gbps in the downlink and 10 Gbps in the uplink from the perspective of a single base station. Furthermore, while providing these peak data rates, the 5G communication system must also provide an increased user-perceived data rate. To satisfy these requirements, it necessitates improvements in various transmission and reception technologies, including enhanced Multi-Input Multi-Output (MIMO) transmission technology. Additionally, while LTE transmits signals using a maximum bandwidth of 20 MHz in the 2 GHz band, the 5G communication system can meet the data transmission speeds required by using a frequency bandwidth wider than 20 MHz in frequency bands of 3–6 GHz or above 6 GHz.
[0036] Simultaneously, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide IoT, mMTC requires support for a large number of terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. Since IoT devices are attached to various sensors and equipment to provide communication functions, the system must be able to support a large number of terminals within a cell (e.g., 1,000,000 terminals / km²). Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in dead zones not covered by cells, such as building basements; therefore, they may require wider coverage compared to other services provided by 5G communication systems. Terminals supporting mMTC must consist of low-cost devices, and since it is difficult to frequently replace terminal batteries, a very long battery life of 10 to 15 years may be required.
[0037] Finally, URLLC is a mission-critical cellular-based wireless communication service. For example, consider services used for remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency alerts. Therefore, the communication provided by URLLC must offer very low latency and very high reliability. For instance, services supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds, and simultaneously 10 -5The following packet error rate requirements apply. Therefore, for services supporting URLLC, 5G systems must provide a Transmit Time Interval (TTI) smaller than other services, and at the same time, design considerations may be required to allocate a wide resource in the frequency band to ensure the reliability of the communication link.
[0038] The three 5G services, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted within a single system. In this case, different transmission and reception techniques and parameters may be used between the services to satisfy the different requirements of each service. Of course, 5G is not limited to the three services mentioned above.
[0039] Hereinafter, a / b may be understood as at least one of a or b.
[0040] [NR Time-Frequency Resources]
[0041] The frame structure of the 5G system will be explained in more detail below with reference to the drawings.
[0042] FIG. 1 is a diagram illustrating the basic structure of a time-frequency domain, which is a wireless resource domain in which data or a control channel is transmitted in a 5G system according to one embodiment of the present disclosure.
[0043] The horizontal axis of FIG. 1 represents the time domain, and the vertical axis represents the frequency domain. In the time and frequency domains, the basic unit of a resource is a resource element (RE, 101), which can be defined as one OFDM symbol (102) on the time axis and one subcarrier (103) on the frequency axis. In the frequency domain (For example, 12) consecutive REs can form a single resource block (Resource Block, RB, 104). In the time axis, a single subframe (110) may contain multiple OFDM symbols (102). For example, the length of one subframe may be 1 ms.
[0044] FIG. 2 is a drawing illustrating a frame, subframe, and slot structure in a wireless communication system according to one embodiment of the present disclosure.
[0045] FIG. 2 illustrates an example of a frame (200), subframe (201), and slot (202) structure. One frame (200) can be defined as 10ms. One subframe (201) can be defined as 1ms, and thus one frame (200) can be composed of a total of 10 subframes (201). One slot (202, 203) can be defined as 14 OFDM symbols (i.e., the number of symbols per slot ( = 14). One subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per one subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing. In one example of FIG. 2, cases where μ=0 (204) and μ=1 (205) are shown as the setting value for the subcarrier spacing. When μ=0 (204), one subframe (201) may be composed of one slot (202), and when μ=1 (205), one subframe (201) may be composed of two slots (203). That is, the number of slots per one subframe ( ) may vary, and accordingly, the number of slots per frame ( ) may vary. Depending on each subcarrier spacing setting μ and It can be defined by [Table 1] below.
[0046] [Table 1]
[0047]
[0048] [Bandwidth Section (BWP)]
[0049] Next, the Bandwidth Part (BWP) setting in the 5G communication system will be explained in detail with reference to the drawing.
[0050] FIG. 3 is a drawing illustrating an example of a bandwidth portion setting in a wireless communication system according to one embodiment of the present disclosure.
[0051] FIG. 3 shows an example in which the terminal bandwidth (UE bandwidth) (300) is configured into two bandwidth portions, namely bandwidth portion #1 (BWP#1) (301) and bandwidth portion #2 (BWP#2) (302). The base station may configure one or more bandwidth portions for the terminal, and may configure at least some of the information in [Table 2] below for each bandwidth portion.
[0052] [Table 2]
[0053]
[0054] Of course, the above examples are not limited, and various parameters related to bandwidth portions may be configured for the terminal in addition to configuration information. At least some of the information may be transmitted from the base station to the terminal via higher-layer signaling, for example, Radio Resource Control (RRC) signaling. Among the one or more configured bandwidth portions, at least one bandwidth portion may be activated. Whether a configured bandwidth portion is activated may be transmitted semi-statically from the base station to the terminal via RRC signaling or dynamically via DCI.
[0055] According to one embodiment, prior to the RRC connection, the terminal may receive an Initial Bandwidth Part (Initial BWP) for initial connection from the base station via a Master Information Block (MIB). More specifically, during the initial connection phase, the terminal may receive configuration information for a Control Resource Set (CORESET) and a Search Space via the MIB, through which a PDCCH for receiving system information required for initial connection (which may correspond to Remaining System Information (RMSI) or System Information Block 1 (SIB1)) can be transmitted. The control area and search space configured via the MIB may each be considered as Identity (ID) 0. The base station may notify the terminal via the MIB of configuration information, such as frequency allocation information, time allocation information, and numerology, for Control Area #0. Additionally, the base station may notify the terminal via the MIB of configuration information regarding the monitoring period and monitoring occasion for Control Area #0, i.e., configuration information for Search Space #0. The terminal may consider the frequency region set as control region #0 obtained from the MIB as the initial bandwidth portion for initial access. In this case, the identifier (ID) of the initial bandwidth portion may be considered as 0.
[0056] The settings for the bandwidth supported by 5G can be used for various purposes.
[0057] According to some embodiments, if the bandwidth supported by the terminal is smaller than the system bandwidth, this can be supported through a bandwidth portion setting. For example, by setting a frequency position of the bandwidth portion (setting information 2) to the terminal, the terminal can transmit and receive data at a specific frequency position within the system bandwidth.
[0058] In addition, according to some embodiments, a base station may set multiple bandwidth portions for a terminal for the purpose of supporting different numerologies. For example, to support data transmission and reception using both a 15 kHz subcarrier interval and a 30 kHz subcarrier interval for a terminal, two bandwidth portions may be set to subcarrier intervals of 15 kHz and 30 kHz, respectively. Different bandwidth portions may be frequency division multiplexed (FDM), and if data is to be transmitted and received with a specific subcarrier interval, the bandwidth portion set to that subcarrier interval may be used.
[0059] According to one embodiment, for the purpose of reducing the power consumption of the terminal, a base station may set a bandwidth portion having a different bandwidth size for the terminal. For example, if the terminal supports a very large bandwidth, such as 100 MHz, and always transmits and receives data using that bandwidth, very large power consumption may occur. In particular, in a situation where there is no traffic, performing monitoring of an unnecessary downlink control channel using a large bandwidth of 100 MHz may be very inefficient in terms of power consumption. For the purpose of reducing the power consumption of the terminal, the base station may set a bandwidth portion of a relatively small bandwidth, such as 20 MHz, for the terminal. In a situation where there is no traffic, the terminal can perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, it can transmit and receive data using the 100 MHz bandwidth portion according to the instructions of the base station.
[0060] Regarding the method of configuring the bandwidth portion, terminals prior to RRC connection (Connected) can receive configuration information for the Initial Bandwidth Part (Initial BWP) via the MIB during the initial connection phase. More specifically, the terminal can receive a configuration of a control area (i.e., CORESET) for a downlink control channel through which a DCI scheduling a System Information Block (SIB) can be transmitted from the MIB of the Physical Broadcast Channel (PBCH). The bandwidth of the control area configured by the MIB can be considered as the Initial Bandwidth Part, and through this configured Initial Bandwidth Part, the terminal can receive the Physical Downlink Shared Channel (PDSCH) through which the SIB is transmitted. In addition to receiving the SIB, the Initial Bandwidth Part may also be utilized for other system information (OSI), paging, and random access.
[0061] [Change Bandwidth Part (BWP)]
[0062] When one or more bandwidth parts are set for a terminal, the base station may instruct the terminal to change (or switch, transition) the bandwidth part using the Bandwidth Part Indicator field within the DCI. For example, in FIG. 3, if the currently active bandwidth part of the terminal is Bandwidth Part #1 (301), the base station may indicate Bandwidth Part #2 (302) to the terminal using the Bandwidth Part Indicator within the DCI, and the terminal may perform a bandwidth part change to Bandwidth Part #2 (302) indicated by the received Bandwidth Part Indicator within the DCI.
[0063] As mentioned above, since DCI-based bandwidth portion changes can be directed by the DCI scheduling PDSCH or PUSCH, when a terminal receives a bandwidth portion change request, it must be able to receive or transmit the PDSCH or PUSCH scheduled by the DCI in the changed bandwidth portion without difficulty. To this end, the standard specifies the delay time (T) required when changing the bandwidth portion. BWP The requirements for ) have been defined, and can be defined, for example, as shown in [Table 3] below.
[0064] [Table 3]
[0065]
[0066] According to one embodiment, the requirement for bandwidth portion change delay time supports Type 1 or Type 2 depending on the capability of the terminal. The terminal can report the supported bandwidth portion delay time type to the base station.
[0067] In accordance with the aforementioned requirements for bandwidth portion change delay time, if the terminal receives a DCI containing a bandwidth portion change indicator in slot n, the terminal performs a change to the new bandwidth portion indicated by the bandwidth portion change indicator in slot n+T BWP Completion can be achieved at a time no later than this. In this case, the terminal can perform transmission and reception for the data channel scheduled by the corresponding DCI in the changed new bandwidth portion. If the base station intends to schedule a data channel in the new bandwidth portion, the terminal's bandwidth portion change delay time (T BWPBased on ), time-domain resource allocation for a data channel can be determined. That is, when a base station schedules a data channel with a new bandwidth portion, in the method for determining time-domain resource allocation for a data channel, the data channel can be scheduled after the bandwidth portion change delay time. Accordingly, the terminal [is notified] that the DCI instructing the bandwidth portion change is the bandwidth portion change delay time (T BWP You may not expect to indicate a slot offset (K0 or K2) value smaller than )
[0068] If a terminal receives a DCI (e.g., DCI format 1_1 or 0_1) instructing a change in the bandwidth portion, the terminal may not perform any transmission or reception during a time interval corresponding to the time interval from the third symbol of the slot in which the PDCCH containing the DCI was received to the beginning of the slot indicated by the slot offset value (K0 or K2) indicated by the time domain resource allocation indicator field within the DCI. For example, if a terminal receives a DCI instructing a change in the bandwidth portion in slot n, and the slot offset value indicated by the DCI is K, the terminal may not perform any transmission or reception from the third symbol of slot n to the symbol before slot n+K (i.e., the last symbol of slot n+K-1).
[0069] [Unified TCI state]
[0070] The following describes a method for instructing and activating a single TCI (Transmission Configuration Indication) state based on the unified TCI method. The unified TCI method can be referred to as a method that integrates the transmit / receive beam management methods—which were previously distinguished in Rel-15 and Rel-16 as the TCI state method used for downlink reception and the spatial relation info method used for uplink transmission—into a single TCI state. Therefore, when a terminal receives instructions from a base station based on the unified TCI method, it can perform beam management using the TCI state for uplink transmission as well. If the terminal receives a TCI-State, which is a higher-layer signaling with the higher-layer signaling tci-stateId-r17, from the base station, the terminal can perform operations based on the unified TCI method using the corresponding TCI-State. The TCI-State can exist in two forms: a joint TCI state or a separate TCI state.
[0071] The first form is a joint TCI state, and the terminal can receive instructions from the base station regarding the TCI state to be applied for both uplink transmission and downlink reception through a single TCI-State. If the terminal receives instructions for a TCI-State based on the joint TCI state, the terminal can receive instructions from the base station regarding parameters to be used for downlink channel estimation using the RS corresponding to qcl-Type1 within the joint TCI state-based TCI-State, and parameters to be used as a downlink reception beam or reception filter using the RS corresponding to qcl-Type2. If the terminal receives instructions for a TCI-State based on the joint TCI state, the terminal can receive instructions from the base station regarding parameters to be used as an uplink transmission beam or transmission filter using the RS corresponding to qcl-Type2 within the joint DL / UL TCI state-based TCI-State. In this case, if the terminal receives instructions for the joint TCI state, the terminal can apply the same beam to both uplink transmission and downlink reception.
[0072] The second form is a separate TCI state, and the terminal can individually receive instructions from the base station for an UL TCI state to be applied for uplink transmission and a DL TCI state to be applied for downlink reception. If the terminal is instructed to the UL TCI state, the terminal can receive instructions from the base station for parameters to be used as an uplink transmission beam or transmission filter using the reference RS or source RS set within the UL TCI state. If the terminal is instructed to the DL TCI state, the terminal can receive instructions from the base station for parameters to be used for downlink channel estimation using the RS corresponding to qcl-Type1 set within the DL TCI state, and parameters to be used as a downlink reception beam or reception filter using the RS corresponding to qcl-Type2.
[0073] If the terminal is instructed with both a DL TCI state and a UL TCI state, the terminal may be instructed with parameters to be used as an uplink transmit beam or transmit filter using a reference RS or source RS set within the corresponding UL TCI state. In this case, the terminal may be instructed with parameters to be used for downlink channel estimation using an RS corresponding to qcl-Type1 set within the DL TCI state, and parameters to be used as a downlink receive beam or receive filter using an RS corresponding to qcl-Type2. At this time, if the reference RS or source RS set within the DL TCI state and the UL TCI state instructed to the terminal are different, the terminal may apply beams individually to uplink transmit and downlink receive, respectively, based on the instructed UL TCI state and DL TCI state.
[0074] A terminal can receive up to 128 upper-layer signalings for each specific bandwidth part within a specific cell as joint TCI states from the base station, and among the separate TCI states, DL TCI states can be received as up to 64 or 128 upper-layer signalings (e.g., configuration information) for each specific bandwidth part within a specific cell based on terminal capability reporting, and among the separate TCI states, DL TCI states and joint TCI states can use the same upper-layer signaling structure. For example, if 128 joint TCI states are configured and 64 DL TCI states are configured among the separate TCI states, the 64 DL TCI states can be included in the 128 joint TCI states.
[0075] According to one embodiment, among the separate TCI states, the UL TCI state can be set to up to 32 or 64 upper layer signalings per specific bandwidth part within a specific cell based on terminal capability reporting. Similar to the relationship between the DL TCI state and the joint TCI state among the separate TCI states, the UL TCI state and the joint TCI state among the separate TCIs may also use the same upper layer signaling structure, or the UL TCI state among the separate TCIs may use a different upper layer signaling structure from the joint TCI state and the DL TCI state among the separate TCI states.
[0076] Using different or identical upper-layer signaling structures in this way may be defined in the specifications, or may be distinguished through another upper-layer signaling configured by the base station based on a terminal capability report containing information on which of the two usage modes the terminal can support.
[0077] The terminal can receive instructions regarding transmit / receive beams in an integrated TCI manner by utilizing either the joint TCI state or the separate TCI state configured by the base station. The terminal can receive a configuration from the base station regarding whether to use either the joint TCI state or the separate TCI state through upper-layer signaling (e.g., configuration information).
[0078] The terminal receives instructions related to the transmit / receive beam using one of the selected methods among the joint TCI state and the separate TCI state through upper layer signaling, and at this time, there may be two types of transmit / receive beam instructions from the base station: a MAC-CE based instruction method and a MAC-CE based activation and DCI based instruction method.
[0079] If the terminal receives instructions regarding transmit / receive beams using the joint TCI state method through upper layer signaling (e.g., configuration information), the terminal can perform transmit / receive beam application operations by receiving a MAC-CE from the base station that indicates the joint TCI state. In this case, the base station can schedule the terminal to receive a PDSCH containing the corresponding MAC-CE via a PDCCH. If there is only one joint TCI state included in the MAC-CE, the terminal can determine the uplink transmit beam or transmit filter and the downlink receive beam or receive filter using the indicated joint TCI state starting 3 ms after the transmission of a PUCCH containing HARQ-ACK information indicating whether the PDSCH containing the MAC-CE was successfully received. If there are two or more joint TCI states included in the MAC-CE, the terminal may activate the indicated joint TCI states by verifying that the multiple joint TCI states indicated by the MAC-CE correspond to each code point in the TCI state field of DCI format 1_1 or 1_2 starting 3 ms after the transmission of a PUCCH containing HARQ-ACK information indicating whether reception of the PDSCH containing the MAC-CE was successful. Subsequently, the terminal may receive DCI format 1_1 or 1_2 and apply a single joint TCI state indicated by the TCI state field within the DCI to the uplink transmit and downlink receive beams. At this time, DCI format 1_1 or 1_2 may include downlink data channel scheduling information (with DL assignment) or may not include it (without DL assignment).
[0080] If a terminal receives instructions regarding transmit / receive beams using a separate TCI state method through upper layer signaling, the terminal can perform a transmit / receive beam application operation by receiving a MAC-CE from the base station that indicates a separate TCI state. In this case, the base station can schedule the terminal to receive a PDSCH containing the MAC-CE via a PDCCH. If there is only one set of separate TCI states included in the MAC-CE, the terminal can determine the uplink transmit beam or transmit filter and the downlink receive beam or receive filter using the separate TCI states included in the indicated set of separate TCI states starting 3 ms after the transmission of a PUCCH containing HARQ-ACK information indicating whether the PDSCH was successfully received. At this time, the separate TCI state set may be referenced as a single or multiple separate TCI states that a single code point of the TCI state field in DCI format 1_1 or 1_2 may have, and a separate TCI state set may include one DL TCI state, one UL TCI state, or one DL TCI state and one UL TCI state. If there are two or more separate TCI state sets included by MAC-CE, the terminal may activate the indicated separate TCI state sets after 3 ms following the transmission of PUCCH containing HARQ-ACK information indicating whether the PDSCH was successfully received, by confirming that the multiple separate TCI state sets indicated by MAC-CE correspond to each code point of the TCI state field in DCI format 1_1 or 1_2.In this case, each code point in the TCI state field of DCI format 1_1 or 1_2 may indicate one DL TCI state, one UL TCI state, or one DL TCI state and one UL TCI state each. The terminal receives DCI format 1_1 or 1_2 and can apply the separate set of TCI states indicated by the TCI state field within the corresponding DCI to the uplink transmit and downlink receive beams. In this case, DCI format 1_1 or 1_2 may include downlink data channel scheduling information (with DL assignment) or may not include it (without DL assignment).
[0081] FIG. 4 is a diagram of the beam application time that can be considered when using an integrated TCI method in a wireless communication system according to one embodiment of the present disclosure. As described above, the terminal receives a DCI format 1_1 or 1_2 from a base station that includes downlink data channel scheduling information (e.g., with DL assignment) or does not include it (e.g., without DL assignment), and can apply a set of one joint TCI state or separate TCI state indicated by the TCI state field within the DCI to the uplink transmit and downlink receive beams.
[0082] - DCI format 1_1 or 1_2 with DL (downlink) assignment (400): If a terminal receives DCI format 1_1 or 1_2 containing downlink data channel scheduling information from a base station (401) and indicates a set of one joint TCI state or separate TCI state based on the integrated TCI method, the terminal receives a PDSCH scheduled based on the received DCI (405) and can transmit a PUCCH containing a HARQ-ACK indicating whether the reception of the DCI and PDSCH was successful (410). At this time, the HARQ-ACK may include the meaning of whether the reception of the DCI (downlink control information) and PDSCH (physical downlink shared channel) was successful, and if at least one of the DCI and PDSCH is not received, the terminal can transmit a NACK (negative-acknowledgement), and if both are successfully received, the terminal can transmit an ACK.
[0083] - DCI format 1_1 or 1_2 without DL assignment (450): If the terminal receives DCI format 1_1 or 1_2 from the base station that does not include downlink data channel scheduling information (455) and indicates one joint TCI state or separate set of TCI states based on the integrated TCI method, the terminal may assume at least one combination of the following for the DCI.
[0084] ■ Includes CRC scrambled using CS-RNTI.
[0085] ■ The value of all bits assigned to all fields used as RV (Redundancy Version) fields is 1.
[0086] ■ The value of all bits assigned to all fields used as MCS (Modulation and Coding Scheme) fields is 1.
[0087] ■ The value of all bits assigned to all fields used as NDI (New Data Indication) fields is 0.
[0088] ■ For FDRA (Frequency Domain Resource Allocation) Type 0, the value of all bits allocated to the FDRA field is 0; for FDRA Type 1, the value of all bits allocated to the FDRA field is 1; and for the FDRA method dynamicSwitch, the value of all bits allocated to the FDRA field is 0.
[0089] The terminal may transmit a PUCCH containing a HARQ-ACK indicating whether reception of DCI format 1_1 or 1_2, in which the above-described items are assumed, was successful (460).
[0090] - For both DCI format 1_1 or 1_2 with DL assignment (400) and without DL assignment (450), if the new TCI state indicated by the DCI (401, 455) is the same as the TCI state that was previously indicated and applied to the uplink transmit and downlink receive beams, the terminal may maintain the previously applied TCI state. If the new TCI state is different from the previously indicated TCI state, the terminal may determine the application time of the joint TCI state or separate TCI state set that can be indicated from the TCI state field included in the DCI as after the first slot (420, 470) (430, 480) after a time equal to BAT (beam application time, 415, 465) after the PUCCH transmission, and may use the previously indicated TCI-state until before the slot (420, 470) (425, 475).
[0091] - For both DCI format 1_1 or 1_2 with DL assignment (400) and without DL assignment (450), BAT can be set to upper layer signaling based on terminal capability reporting information as a specific number of OFDM symbols, and the numerology for BAT and the first slot after BAT can be determined based on the smallest numerology among all cells to which the joint TCI state or separate TCI state set indicated through DCI is applied.
[0092] A terminal may apply a single joint TCI state indicated via MAC-CE or DCI to the reception of control resource sets connected to all terminal-specific search spaces, the reception of PDSCH scheduled to PDCCH transmitted from the control resource set, the transmission of PUSCH, and / or the transmission of all PUCCH resources.
[0093] If a separate set of TCI states indicated via MAC-CE or DCI includes a DL TCI state, the terminal can apply the separate set of TCI states to the reception of control resource sets connected to all terminal-specific search spaces, and to the reception of PDSCH scheduled to PDCCH transmitted from said control resource sets, and can apply it to all PUSCH and PUCCH resources based on the previously indicated UL TCI state.
[0094] If a separate set of TCI states indicated via MAC-CE or DCI includes a single UL TCI state, the terminal may apply a separate set of TCI states to all PUSCH and PUCCH resources. In this case, the terminal may apply the previously indicated DL TCI state to receiving control resource sets connected to all terminal-specific search spaces, and to receiving PDSCH scheduled to PDCCH transmitted from said control resource sets.
[0095] If a separate set of TCI states indicated by MAC-CE or DCI includes one DL TCI state and one UL TCI state, the terminal may apply the DL TCI state to the reception of control resource sets connected to all terminal-specific search spaces and to the reception of PDSCH scheduled to PDCCH transmitted from said control resource sets, and may apply the UL TCI state to all PUSCH and PUCCH resources.
[0096] [Unified TCI state MAC-CE]
[0097] A single TCI state instruction and activation method based on an integrated TCI method is described below. A terminal receives a PDSCH containing the following MAC-CE from a base station and, starting from the third slot after transmitting a HARQ-ACK for the PDSCH to the base station, can interpret each code point of the TCI state field in DCI format 1_1 or 1_2 based on the information in the MAC-CE received from the base station. That is, the terminal can activate each entry of the MAC-CE received from the base station to each code point of the TCI state field in DCI format 1_1 or 1_2.
[0098] FIG. 5 is a diagram showing another MAC-CE structure for activating and indicating a joint TCI state or a separate DL or UL TCI state in a wireless communication system according to one embodiment of the present disclosure. The meaning of each field within the MAC-CE structure may be as follows.
[0099] - Serving Cell ID (500): This field may indicate which serving cell the MAC-CE is to be applied to. The length of this field may be 5 bits. If the serving cell indicated by this field is included in one or more of the upper layer signalings simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, or simultaneousU-TCI-UpdateList4, the MAC-CE may be applied to all serving cells included in one or more of the lists simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, or simultaneousU-TCI-UpdateList4 that contain the serving cell indicated by this field.
[0100] - DL BWP ID (505): This field may indicate which DL BWP the MAC-CE is to be applied to, and the meaning of each code point in this field may correspond to each code point of the bandwidth part indicator in the DCI. The length of this field may be 2 bits.
[0101] - UL BWP ID (510): This field may indicate which UL BWP the MAC-CE applies to. The meaning of each code point in this field may correspond to each code point of the bandwidth part indicator within the DCI. The length of this field may be 2 bits.
[0102] - P i(515): This field can indicate whether each code point of the TCI state field in DCI format 1_1 or 1_2 has multiple TCI states or one TCI state. If P i If the value of is 1, it means that the corresponding i-th code point has multiple TCI states, which may mean that the code point can include a separate DL TCI state and a separate UL TCI state. If P i If the value of is 0, it means that the corresponding i-th code point has a single TCI state, which means that the code point may contain one of a joint TCI state, a separate DCI TCI state, or a separate UL TCI state.
[0103] - D / U (520): This field may indicate whether the TCI state ID field within the same octet is a joint TCI state, a separate DL TCI state, or a separate UL TCI state. If this field is 1, the TCI state ID field within the same octet may be a joint TCI state or a separate DL TCI state. If this field is 0, the TCI state ID field within the same octet may be a separate UL TCI state.
[0104] - TCI state ID (525): This field may indicate a TCI state that can be identified by the upper layer signaling TCI-StateId. If the D / U field is set to 1, this field may be used to represent the TCI-StateId, which can be represented by 7 bits. If the D / U field is set to 0, the MSB (most significant bit) of this field may be identified as the reserved bit, and the remaining 6 bits may be used to represent the upper layer signaling UL-TCIState-Id. The maximum number of TCI states that can be enabled is 8 for joint TCI states and 16 for separate DL or UL TCI states.
[0105] - R: Represents a reserved bit and can be set to 0.
[0106] Regarding the MAC-CE structure of FIG. 5 described above, the terminal may include a third octet containing fields P1, P2, ..., P8 in FIG. 5 in the MAC-CE structure, regardless of whether unifiedTCI-StateType-r17 in MIMOparam-r17 within ServingCellConfig, which is an upper layer signaling, is set to joint or separate. In this case, the terminal may perform TCI state activation using a fixed MAC-CE structure, regardless of the upper layer signaling received from the base station. As another example, regarding the MAC-CE structure of FIG. 5 described above, if unifiedTCI-StateType-r17 in MIMOparam-r17 within ServingCellConfig, which is an upper layer signaling, is set to joint, the terminal may omit the third octet containing fields P1, P2, ..., P8 in FIG. 5. In this case, the terminal can save up to 8 bits of the payload of the corresponding MAC-CE according to the upper layer signaling set from the base station. Additionally, all D / U fields located from the fourth octet to the first bit in FIG. 5 can be identified as R fields, and all R fields can be set to 0 bits.
[0107] [PDCCH: DCI related]
[0108] Next, we will explain Downlink Control Information (DCI) in 5G systems in detail.
[0109] In a 5G system, scheduling information for uplink data (or Physical Uplink Shared Channel (PUSCH)) or downlink data (or Physical Downlink Shared Channel (PDSCH)) can be transmitted from a base station to a terminal via DCI. The terminal can monitor the fallback DCI format and the non-fallback DCI format for PUSCH or PDSCH. The fallback DCI format may consist of fixed fields predefined between the base station and the terminal, and the non-fallback DCI format may include configurable fields.
[0110] DCI can be transmitted via the Physical Downlink Control Channel (PDCCH) after undergoing channel coding and modulation processes. For example, a Cyclic Redundancy Check (CRC) is attached to the DCI message payload, and the CRC can be scrambled into a Radio Network Temporary Identifier (RNTI) corresponding to the terminal's identity. Different RNTIs may be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control commands, or random access responses. For example, the RNTI is not transmitted explicitly but is included in the CRC calculation process. Upon receiving a DCI message transmitted over the PDCCH, the terminal checks the CRC using the assigned RNTI; if the CRC check result is correct, the terminal knows that the message was transmitted to it.
[0111] For example, a DCI scheduling a PDSCH for System Information (SI) can be scrambled to SI-RNTI. A DCI scheduling a PDSCH for Random Access Response (RAR) messages can be scrambled to RA-RNTI. A DCI scheduling a PDSCH for Paging messages can be scrambled to P-RNTI. A DCI notifying a Slot Format Indicator (SFI) can be scrambled to SFI-RNTI. A DCI notifying Transmit Power Control (TPC) can be scrambled to TPC-RNTI. A DCI scheduling a terminal-specific PDSCH or PUSCH can be scrambled to C-RNTI (Cell RNTI).
[0112] DCI format 0_0 can be used as a countermeasure DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI may include, for example, at least some of the information in [Table 4] below.
[0113] [Table 4]
[0114]
[0115] DCI format 0_1 can be used as a non-defense DCI for scheduling PUSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 0_1 with the CRC scrambled with C-RNTI may include, for example, at least some of the information in [Table 5] below.
[0116] [Table 5]
[0117]
[0118]
[0119] DCI format 1_0 can be used as a countermeasure DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI may include, for example, at least some of the information in [Table 6] below.
[0120] [Table 6]
[0121]
[0122] DCI format 1_1 can be used as a non-defense DCI for scheduling PDSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI may include, for example, at least some of the information in [Table 7] below.
[0123] [Table 7]
[0124]
[0125] [PDCCH: CORESET, REG, CCE, Search Space]
[0126] In the following, the downlink control channel in a 5G communication system is described in more detail with reference to the drawings.
[0127] FIG. 6 illustrates an example of a control resource set (CORESET) in which a downlink control channel is transmitted in a 5G wireless communication system. For example, FIG. 6 illustrates an example in which two control resources (control resource #1 (601), control resource #2 (602)) are set within a terminal bandwidth part (UE bandwidth part) (610) on the frequency axis and one slot (620) on the time axis. The control resources (601, 602) can be set in a specific frequency resource (603) within the entire terminal bandwidth part (610) on the frequency axis. On the time axis, they can be set with one or more OFDM symbols, which can be defined as the control resource set duration (Control Resource Set Duration, 604). Referring to the example illustrated in FIG. 6, control resource #1 (601) is set with a control resource length of 2 symbols, and control resource #2 (602) is set with a control resource length of 1 symbol.
[0128] The control domain in the aforementioned 5G can be configured by a base station to a terminal through upper-layer signaling (e.g., System Information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). Configuring a control domain to a terminal means providing information such as a control domain identifier, the frequency location of the control domain, and the symbol length of the control domain. For example, it may include at least some of the information in [Table 8] below.
[0129] [Table 8]
[0130]
[0131] In [Table 8], the tci-StatesPDCCH (simply named TCI (Transmission Configuration Indication) state) configuration information may include information on one or more SS (Synchronization Signal) / PBCH (Physical Broadcast Channel) block indices or CSI-RS (Channel State Information Reference Signal) indices that are in a QCL (Quasi Co Located) relationship with the DMRS transmitted in the corresponding control area.
[0132] FIG. 7 is a diagram showing an example of a basic unit of time and frequency resources that constitute a downlink control channel that can be used in 5G. For example, according to FIG. 7, the basic unit of time and frequency resources that constitute a control channel can be referenced as a REG (Resource Element Group, 703). For example, the REG (703) can be defined as 1 OFDM symbol (701) on the time axis and 1 PRB (Physical Resource Block, 702) on the frequency axis, i.e., 12 subcarriers. A base station can concatenate REGs (703) to form a downlink control channel allocation unit.
[0133] As illustrated in FIG. 7, if the basic unit to which a downlink control channel is allocated in 5G is called a CCE (Control Channel Element, 704), then 1 CCE (704) can be composed of multiple REGs (703). For example, if the REG (703) illustrated in FIG. 7 is described, the REG (703) can be composed of 12 REs, and if 1 CCE (704) is composed of 6 REGs (703), then 1 CCE (704) can be composed of 72 REs. When a downlink control area is established, the area can be composed of multiple CCEs (704), and a specific downlink control channel can be mapped to and transmitted by one or multiple CCEs (704) according to the Aggregation Level (AL) within the control area. The CCEs (704) within the control area are distinguished by numbers, and the numbers of the CCEs (704) can be assigned according to a logical mapping method.
[0134] The basic unit of the downlink control channel, namely the REG (703) illustrated in FIG. 7, may include both the REs to which the DCI is mapped and the DMRSs (705), which are reference signals for decoding the DCI, to which the REs are mapped. As shown in FIG. 7, three DMRSs (705) may be transmitted within one REG (703). The number of CCEs required to transmit the PDCCH may be 1, 2, 4, 8, or 16 depending on the Aggregation Level (AL), and different numbers of CCEs may be used to implement link adaptation of the downlink control channel. For example, when AL=L, one downlink control channel may be transmitted through L CCEs. The terminal must detect the signal without knowing information about the downlink control channel, and a search space representing a set of CCEs is defined for blind decoding. A search space is a set of downlink control channel candidates consisting of CCEs that a terminal must attempt to decode on a given aggregation level, and since there are various aggregation levels that form a group of 1, 2, 4, 8, or 16 CCEs, a terminal may have multiple search spaces. A search space set can be defined as a set of search spaces on all configured aggregation levels.
[0135] According to one embodiment, the search space may be classified into a common search space and a terminal-specific (UE-specific) search space. A certain group of terminals or all terminals may examine the common search space of the PDCCH to receive cell-common control information, such as dynamic scheduling or paging messages regarding system information. For example, PDSCH scheduling allocation information for the transmission of an SIB containing cell operator information, etc., may be received by examining the common search space of the PDCCH. In the case of the common search space, since a certain group of terminals or all terminals must receive the PDCCH, it may be defined as a set of pre-agreed CCEs. Scheduling allocation information for a terminal-specific PDSCH or PUSCH may be received by examining the terminal-specific search space of the PDCCH. The terminal-specific search space may be defined terminal-specifically as a function of the terminal's identity and various system parameters.
[0136] In 5G, parameters for the search space for a PDCCH can be configured from the base station to the terminal via upper layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station may configure the terminal the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the occasion for monitoring in slot-symbol units for the search space, the search space type (common search space or terminal-specific search space), the combination of DCI format and RNTI to be monitored in the search space, and the control domain index to be monitored in the search space. For example, at least some of the information in [Table 9] below may be included.
[0137] [Table 9]
[0138]
[0139] According to the configuration information, the base station may configure one or more sets of search spaces for the terminal. According to some embodiments, the base station may configure search space set 1 and search space set 2 for the terminal, and the base station may configure DCI format A scrambled with X-RNTI in search space set 1 to be monitored in a common search space, and the base station may configure DCI format B scrambled with Y-RNTI in search space set 2 to be monitored in a terminal-specific search space.
[0140] According to the configuration information, one or more sets of search spaces may exist in a common search space or a terminal-specific search space. For example, Search Space Set #1 and Search Space Set #2 may be configured as a common search space, and Search Space Set #3 and Search Space Set #4 may be configured as a terminal-specific search space.
[0141] In the common search space, the following combinations of DCI formats and RNTI can be monitored. Of course, they are not limited to the examples below.
[0142] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, SI-RNTI
[0143] - DCI format 2_0 with CRC scrambled by SFI-RNTI
[0144] - DCI format 2_1 with CRC scrambled by INT-RNTI
[0145] - DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, TPC-PUCCH-RNTI
[0146] - DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI
[0147] In terminal-specific search spaces, the following combinations of DCI formats and RNTI can be monitored. Of course, they are not limited to the examples below.
[0148] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI
[0149] - DCI format 1_0 / 1_1 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI
[0150] The specified RNTIs may follow the definitions and uses below.
[0151] C-RNTI (Cell RNTI): Used for terminal-specific PDSCH scheduling
[0152] TC-RNTI (Temporary Cell RNTI): Used for terminal-specific PDSCH scheduling
[0153] CS-RNTI (Configured Scheduling RNTI): Used for semi-statically configured terminal-specific PDSCH scheduling.
[0154] RA-RNTI (Random Access RNTI): Used for PDSCH scheduling during the random access phase
[0155] P-RNTI (Paging RNTI): Used for PDSCH scheduling where paging is transmitted.
[0156] SI-RNTI (System Information RNTI): Used for PDSCH scheduling where system information is transmitted.
[0157] INT-RNTI (Interruption RNTI): Used to indicate whether PDSCH has been punctured.
[0158] TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to instruct power control commands to the PUSCH
[0159] TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Used to instruct power control commands to the PUCCH
[0160] TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to instruct power regulation commands to the SRS
[0161] The aforementioned specified DCI formats may follow the definitions in [Table 10] below.
[0162] [Table 10]
[0163]
[0164] In 5G, the search space of aggregation level L in the control domain p and search space set s can be expressed as [Equation 1] below.
[0165] [Mathematical Formula 1]
[0166]
[0167] The value may be 0 for the common search space.
[0168] In the case of a terminal-specific search space, the value may correspond to a value that changes depending on the terminal's identity (C-RNTI or ID set for the terminal by the base station) and the time index.
[0169] In 5G, as multiple sets of search spaces can be configured with different parameters (e.g., parameters in [Table 9]), the set of search space sets monitored by the terminal may vary at each point in time. For example, if search space set #1 is configured for an X-slot period and search space set #2 is configured for a Y-slot period and X and Y are different, the terminal may monitor both search space set #1 and search space set #2 in a specific slot, and monitor either search space set #1 or search space set #2 in a specific slot.
[0170] [PUCCH: Transmission Related]
[0171] In an NR system, a terminal can transmit control information (UCI, uplink control information) to a base station via PUCCH. The control information may include at least one of a HARQ-ACK indicating whether demodulation / decoding of a TB (transport block) received by the terminal via PDSCH was successful, a scheduling request (SR) in which the terminal requests resource allocation from the base station for uplink data transmission (e.g., PUSCH), and channel state information (CSI) which is information for reporting the channel state of the terminal.
[0172] PUCCH resources can be broadly classified into long PUCCH and short PUCCH depending on the length of the allocated symbols. In an NR system, long PUCCH has a length of 4 symbols or more within a slot, while short PUCCH has a length of 2 symbols or less within a slot.
[0173] To explain Long PUCCH in more detail, Long PUCCH can be used to improve uplink cell coverage and therefore can be transmitted via a single carrier transmission method, such as DFT-S-OFDM, rather than OFDM transmission. Long PUCCH supports transmission formats such as PUCCH format 1, PUCCH format 3, and PUCCH format 4, depending on the number of control information bits supported and whether terminal multiplexing is supported through Pre-DFT OCC support in front of IFFT (Inverse Fast Fourier Transform).
[0174] First, PUCCH format 1 is a long PUCCH format based on DFT-S-OFDM that can support up to 2 bits of control information and uses 1 RB of frequency resources. The control information can be composed of a combination of HARQ-ACK and SR, or each of them. PUCCH format 1 is composed of repeating OFDM symbols containing a DMRS (DeModulation Reference Signal), which is a demodulation reference signal (or reference signal), and OFDM symbols containing a UCI.
[0175] For example, if the number of transmitted symbols in PUCCH format 1 is 8, the 8 symbols may be composed sequentially of DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, and UCI symbol, starting from the first starting symbol. The DMRS symbol is an orthogonal code (or orthogonal sequence or spreading code, w) on the time axis within a sequence corresponding to a length of 1 RB on the frequency axis within a single OFDM symbol. i It can be spread using (m)) and transmitted after performing IFFT.
[0176] For the UCI symbol, the terminal generates d(0) by modulating 1-bit control information using BPSK (Binary Phase-Shift Keying) and 2-bit control information using QPSK (Quadrature Phase-Shift Keying), scrambles the generated d(0) by multiplying it by a sequence corresponding to a length of 1 RB along the frequency axis, and applies an orthogonal code (or orthogonal sequence or spreading code, w) along the time axis to the scrambled sequence i It can be spread using (m) and transmitted after performing IFFT.
[0177] According to one embodiment, the terminal generates a sequence based on a group hopping or sequence hopping setting and a set ID received from a base station as upper layer signaling (e.g., setting information), and generates a sequence corresponding to a length of 1 RB by cyclic shifting the generated sequence with an initial CS (cyclic shift) value set as an upper signal.
[0178] w i (m) is given the length of the spreading code (NSF). It is determined as follows, and specifically given as shown in the following [Table 11]. i represents the index of the spreading code itself, and m represents the indices of the elements of the spreading code. Here, the numbers inside [ ] in [Table 11] are It means, for example, if the length of the spreading code is 2 and the index i of the set spreading code is 0, the spreading code w i (m) is , It became w i (m)=
[0011] .
[0179] [Table 11]
[0180]
[0181] Next, PUCCH format 3 is a long PUCCH format based on DFT-S-OFDM that can support control information of more than 2 bits, and the number of RBs used can be configured through the upper layer. For example, the control information can be composed of a combination of HARQ-ACK, SR, and CSI, or each of them. In PUCCH format 3, the DMRS symbol positions are presented in the following [Table 12] depending on whether frequency hopping within the slot is performed and whether additional DMRS symbols are configured.
[0182] [Table 12]
[0183]
[0184] For example, if the number of transmitted symbols in PUCCH format 3 is 8 symbols, the first starting symbol of the 8 symbols is 0, and DMRS can be transmitted at the 1st and 5th symbols. [Table 12] applies in the same way to the DMRS symbol positions in PUCCH format 4.
[0185] Next, PUCCH format 4 is a long PUCCH format based on DFT-S-OFDM (Orthogonal Frequency Division Multiplexing) capable of supporting control information exceeding 2 bits, and it utilizes 1 RB of frequency resources. The control information can consist of a combination of HARQ-ACK, SR, and CSI, or each of them individually. The difference between PUCCH format 4 and PUCCH format 3 is that PUCCH format 4 for multiple terminals can be multiplexed within a single RB. Multiplexing of PUCCH format 4 for multiple terminals is possible by applying Pre-DFT OCC (Orthogonal Cover Code) to the control information before the IFFT layer. However, the number of control information symbols that can be transmitted by a single terminal may decrease depending on the number of terminals being multiplexed. The number of multiplexable terminals, i.e., the number of different available OCCs, can be 2 or 4, and the number of OCCs and the OCC index to be applied can be configured through the upper layer.
[0186] Next, short PUCCH is described. Short PUCCH can be transmitted in both the downlink centric slot and the uplink centric slot, and generally, it can be transmitted at the last symbol of the slot or at the OFDM symbols following it (e.g., the very last OFDM symbol, the second-to-last OFDM symbol, or the last two OFDM symbols). Of course, it is also possible for Short PUCCH to be transmitted at any location within the slot. Furthermore, Short PUCCH can be transmitted using one OFDM symbol or two OFDM symbols. Short PUCCH can be used to reduce latency compared to long PUCCH in situations where uplink cell coverage is good, and it can be transmitted via CP-OFDM.
[0187] According to one embodiment, Short PUCCH can support transmission formats such as PUCCH format 0 and PUCCH format 2 depending on the number of control information bits that can be supported. First, PUCCH format 0 is a short PUCCH format that can support up to 2 bits of control information and can use 1 RB of frequency resources. The control information can be composed of a combination of HARQ-ACK and SR, or each thereof. PUCCH format 0 is structured to transmit only a sequence mapped to 12 subcarriers along the frequency axis within a single OFDM symbol, without transmitting DMRS. The terminal can generate a sequence based on the group hopping or sequence hopping settings and the configured ID received as an upper signal from the base station, cyclic shift the generated sequence with the final CS value obtained by adding a different CS value depending on whether it is an ACK or a NACK to the indicated initial CS (cyclic shift) value, map it to 12 subcarriers, and transmit it.
[0188] For example, if the HARQ-ACK is 1 bit, the terminal can generate the final CS by adding 6 to the initial CS value if it is an ACK, and the final CS by adding 0 to the initial CS if it is a NACK, as shown in [Table 13] below. The CS value 0 for NACK and the CS value 6 for ACK are defined in the standard, and the terminal can transmit a 1-bit HARQ-ACK by generating PUCCH format 0 according to the values defined in the standard.
[0189] [Table 13]
[0190]
[0191] For example, if the HARQ-ACK is 2 bits, the terminal can add 0 to the initial CS value if (NACK, NACK), add 3 to the initial CS value if (NACK, ACK), add 6 to the initial CS value if (ACK, ACK), and add 9 to the initial CS value if (ACK, NACK), as shown in [Table 14] below. The CS values 0 for (NACK, NACK), 3 for (NACK, ACK), 6 for (ACK, ACK), and 9 for (ACK, NACK) are defined in the standard, and the terminal can transmit a 2-bit HARQ-ACK by generating PUCCH format 0 according to the values defined in the standard. If the final CS value exceeds 12 due to the CS value added to the initial CS value according to ACK or NACK, modulo 12 may be applied to the final CS value since the sequence length is 12.
[0192] [Table 14]
[0193]
[0194] Next, PUCCH format 2 is a short PUCCH format that supports control information exceeding 2 bits, and the number of RBs used can be set through the upper layer. The control information can consist of a combination of HARQ-ACK, SR, and CSI, or each of them. When the index of the first subcarrier is #0, PUCCH format 2 allows the position of the subcarrier where the DMRS is transmitted within a single OFDM symbol to be fixed to the subcarriers having indices #1, #4, #7, and #10. The control information can be mapped to the remaining subcarriers, excluding the subcarrier where the DMRS is located, through a modulation process following channel coding.
[0195] To summarize, the settable values and their ranges for each PUCCH format described above can be summarized as shown in [Table 15] below. In [Table 15] below, cases where a value does not need to be set are indicated as NA.
[0196] [Table 15]
[0197]
[0198] Meanwhile, to improve uplink coverage, multi-slot repetition may be supported for PUCCH formats 1, 3, and 4, and PUCCH repetition may be configured per PUCCH format. The terminal may perform repeated transmissions for PUCCH containing UCIs for a number of slots configured via nrofSlots, which is an upper layer signaling. For PUCCH repeated transmissions, PUCCH transmissions for each slot are performed using the same number of consecutive symbols, and the number of consecutive symbols may be configured for the terminal via nrofSymbols within PUCCH-format1, PUCCH-format3, or PUCCH-format4, which is an upper layer signaling. For PUCCH repeated transmissions, PUCCH transmissions for each slot are performed using the same starting symbol, and the corresponding starting symbol may be configured via startingSymbolIndex within PUCCH-format1, PUCCH-format3, or PUCCH-format4, which is an upper layer signaling. For PUCCH repeated transmissions, a single PUCCH-spatialRelationInfo can be configured for a single PUCCH resource. For PUCCH repeated transmissions, if the terminal is configured to perform frequency hopping in PUCCH transmissions in different slots, the terminal can perform frequency hopping on a slot-by-slot basis. Additionally, if the terminal is configured to perform frequency hopping in PUCCH transmissions in different slots, the terminal can start PUCCH transmission from the first PRB index configured via the upper layer signaling 'startingPRB' in even-numbered slots, and start PUCCH transmission from the second PRB index configured via the upper layer signaling 'secondHopPRB' in odd-numbered slots.Additionally, if the terminal is configured to perform frequency hopping in PUCCH transmissions in different slots, the index of the slot in which the first PUCCH transmission is directed to the terminal is 0, and the PUCCH repeat count value may increase regardless of whether PUCCH transmission is performed in each slot during the total configured PUCCH repeat transmission count. If the terminal is configured to perform frequency hopping in PUCCH transmissions in different slots, the terminal may not expect frequency hopping within the slot to be configured during PUCCH transmission. If the terminal is not configured to perform frequency hopping in PUCCH transmissions in different slots but is configured to perform frequency hopping within the slot, the first and second PRB indices may apply equally within the slot. If the number of uplink symbols available for PUCCH transmission is less than nrofSymbols configured in the upper layer signaling, the terminal may not transmit PUCCH. Even if the terminal fails to perform a PUCCH transmission in any slot for any reason during a PUCCH repeat transmission, the terminal can increase the number of PUCCH repeat transmissions.
[0199] In NR Release 17, the terminal can set the number of slots for repeated transmission for each PUCCH resource within PUCCH-ResourceExt, which is an extension of PUCCH-Resource, an upper layer signaling for PUCCH resources, through the upper layer signaling pucch-RepetitionNrofSlots-r17. If the upper layer signaling pucch-RepetitionNrofSlots-r17 is set, the corresponding PUCCH resource is scheduled, and the upper layer signaling nrofSlots is also set, the terminal can determine the number of slots for repeated transmission of the corresponding PUCCH resource through pucch-RepetitionNrofSlots-r17 and ignore the upper layer signaling nrofSlots.
[0200] [PUCCH: PUCCH resource configuration]
[0201] Next, the PUCCH resource configuration of a base station or terminal is described. A base station may be able to configure PUCCH resources per BWP through an upper layer for a specific terminal. The PUCCH resource configuration may be as shown in the following [Table 16].
[0202] [Table 16]
[0203]
[0204]
[0205] Based on [Table 16], one or more PUCCH resource sets may be configured within the PUCCH resource settings for a specific BWP, and some of the PUCCH resource sets may have a maximum payload value for UCI transmission configured. Each PUCCH resource set may contain one or more PUCCH resources, and each PUCCH resource may belong to one of the PUCCH formats described above.
[0206] For the PUCCH resource set, the maximum payload value of the first PUCCH resource set may be fixed at 2 bits. Accordingly, the maximum payload value may not be set separately through the upper layer, etc. When the remaining PUCCH resource sets are configured, the index of the corresponding PUCCH resource set may be set in ascending order according to the maximum payload value, and the maximum payload value may not be set for the last PUCCH resource set. The upper layer configuration for the PUCCH resource set may be as shown in [Table 17] below.
[0207] [Table 17]
[0208]
[0209] The resourceList parameter in [Table 17] may include the IDs of PUCCH resources belonging to the PUCCH resource set.
[0210] If a PUCCH resource set is not configured during initial connection, a PUCCH resource set consisting of multiple cell-specific PUCCH resources, as shown in [Table 18] below, may be used in the initial BWP. Within this PUCCH resource set, the PUCCH resource to be used for initial connection may be indicated via SIB (system information block) 1.
[0211] [Table 18]
[0212]
[0213] The maximum payload for each PUCCH resource included in the PUCCH resource set can be 2 bits for PUCCH format 0 or 1, and for other formats, it can be determined based on the symbol length, number of PRBs, and maximum code rate. The symbol length and number of PRBs can be set per PUCCH resource, and the maximum code rate can be set per PUCCH format.
[0214] Next, the selection of a PUCCH resource for UCI transmission is described. For SR transmission, a PUCCH resource for the SR corresponding to the schedulingRequestID can be configured through the upper layer as shown in [Table 19] below. The PUCCH resource can be a resource belonging to PUCCH format 0 or PUCCH format 1.
[0215] [Table 19]
[0216]
[0217] The configured PUCCH resource can have its transmission period and offset set through the periodicityAndOffset parameter of [Table 19]. If there is uplink data for the terminal to transmit at the time corresponding to the configured period and offset, the PUCCH resource is transmitted, otherwise the PUCCH resource may not be transmitted.
[0218] For CSI transmission, the PUCCH resources to transmit periodic or semi-persistent CSI reports via PUCCH can be configured in the pucch-CSI-ResourceList parameter as shown in [Table 20] below. The pucch-CSI-ResourceList parameter may contain a list of PUCCH resources for each BWP for the cell or CC to which the corresponding CSI report will be transmitted. The PUCCH resources may be resources belonging to PUCCH format 2, PUCCH format 3, or PUCCH format 4. The transmission period and offset of the PUCCH resources can be configured through the reportSlotConfig in [Table 20].
[0219] [Table 20]
[0220]
[0221] In the case of HARQ-ACK transmission, a resource set of PUCCH resources to be transmitted may first be selected based on the payload of the UCI containing the HARQ-ACK. For example, a PUCCH resource set with a minimum payload not smaller than the UCI payload may be selected. Next, a PUCCH resource within the PUCCH resource set may be selected through a PUCCH resource indicator (PRI) within the DCI that scheduled the transport block (TB) corresponding to the HARQ-ACK, and the PRI may be a PUCCH resource indicator specified in [Table 6] or [Table 7]. The relationship between the PRI and the PUCCH resource selected from the PUCCH resource set may be as shown in the following [Table 21].
[0222] [Table 21]
[0223]
[0224] If the number of PUCCH resources in the selected PUCCH resource set is greater than 8, a PUCCH resource can be selected by the following [Equation 2].
[0225] [Mathematical Formula 2]
[0226]
[0227] In [Mathematical Formula 2] is the index of the selected PUCCH resource within the PUCCH resource set, can be referenced as the number of PUCCH resources belonging to the PUCCH resource set, and can be referenced as a PRI value, and can be referenced as the total number of CCEs of CORESET p to which the receiving DCI belongs, and can be referenced as the first CCE index for the receiving DCI.
[0228] According to one embodiment, the time at which the PUCCH resource is transmitted is from the TB transmission corresponding to the HARQ-ACK. It is after the slot. Candidate values are set to the upper layer and, more specifically, can be set to the dl-DataToUL-ACK parameter within PUCCH-Config specified in [Table 16]. One of these candidates The value may be selected by the PDSCH-to-HARQ feedback timing indicator within the DCI that schedules the TB, and this value may be the value specified in [Table 5] or [Table 6]. Meanwhile, The unit of the value may be a slot unit or a subslot unit. Here, a subslot can be referenced as a unit of length smaller than a slot, and one or more symbols may constitute a single subslot.
[0229] Next, the case where two or more PUCCH resources are located within a single slot is described. A terminal may transmit a UCI through one or two PUCCH resources within a single slot or sub-slot, and when a UCI is transmitted through two PUCCH resources within a single slot / sub-slot, i) each PUCCH resource does not overlap at the symbol level, and ii) at least one PUCCH resource may be a short PUCCH. Meanwhile, the terminal may not expect to transmit multiple PUCCH resources for HARQ-ACK transmission within a single slot.
[0230] [PUCCH: Transmit Beam Related]
[0231] Next, the uplink transmit beam configuration to be used for PUCCH transmission is described. If the terminal does not have a terminal-specific configuration for the PUCCH resource configuration (e.g., dedicated PUCCH resource configuration), the PUCCH resource set may be provided via the upper-layer signaling pucch-ResourceCommon. In this case, the beam configuration for the PUCCH transmission may be based on the beam configuration used in the PUCCH transmission scheduled via the Random Access Response (RAR) UL grant. If the terminal has a terminal-specific configuration for the PUCCH resource configuration (dedicated PUCCH resource configuration), the beam configuration for the PUCCH transmission may be provided via the upper-layer signaling pucch-spatialRelationInfoId included in [Table 16]. If the terminal has received one pucch-spatialRelationInfoId, the beam configuration for the terminal's PUCCH transmission may be provided via one pucch-spatialRelationInfoId. If a terminal has received multiple pucch-spatialRelationInfoIDs, the terminal may be instructed to activate one of the multiple pucch-spatialRelationInfoIDs through MAC CE (control element). The terminal may receive up to 8 pucch-spatialRelationInfoIDs through upper signaling and may be instructed to activate only one of them.When the terminal is instructed to activate an arbitrary pucch-spatialRelationInfoID via MAC CE, the terminal transmits a HARQ-ACK for the PDSCH, from the slot in which the MAC CE containing the activation information for the pucch-spatialRelationInfoID is transmitted. Starting from the first slot appearing after the slot, pucch-spatialRelationInfoID activation via MAC CE can be applied. For example, μ is the numerology applied to PUCCH transmission, and can be referenced as the number of slots per subframe in a given numerology. The upper layer configuration (or settings) for pucch-spatialRelationInfo may be as shown in the following [Table 22].
[0232] [Table 22]
[0233]
[0234] Based on [Table 22], there may be one referenceSignal setting within a specific pucch-spatialRelationInfo setting, for example, the referenceSignal may be an ssb-Index representing a specific SS / PBCH, a csi-RS-Index representing a specific CSI-RS, or srs representing a specific SRS. If the referenceSignal is set to an ssb-Index, the terminal may set the beam used when receiving the SS / PBCH corresponding to the ssb-Index among the SS / PBCHs within the same serving cell as the beam for PUCCH transmission. If a servingCellId is provided, the terminal may set the beam used when receiving the SS / PBCH corresponding to the ssb-Index among the SS / PBCHs within the cell indicated by the servingCellId as the beam for PUCCH transmission.
[0235] If referenceSignal is set to csi-RS-Index, the terminal may set the beam used to receive the CSI-RS corresponding to csi-RS-Index among the CSI-RS within the same serving cell as the beam for PUCCH transmission, or if servingCellId is provided, the terminal may set the beam used to receive the CSI-RS corresponding to csi-RS-Index among the CSI-RS within the cell indicated by servingCellId as the beam for PUCCH transmission.
[0236] If referenceSignal is set to srs, the terminal may set the transmit beam used to transmit the SRS corresponding to the resource index provided by the upper signaling resource within the same serving cell and / or the active uplink BWP as the beam for PUCCH transmission. As another example, if servingCellID and / or uplinkBWP are provided, the terminal may set the transmit beam used to transmit the SRS corresponding to the resource index provided by the upper signaling resource within the cell indicated by servingCellID and / or uplinkBWP and / or the uplink BWP as the beam for PUCCH transmission.
[0237] Within a specific pucch-spatialRelationInfo setting, there may exist a single pucch-PathlossReferenceRS-Id setting. The PUCCH-PathlossReferenceRS in [Table 23] can be mapped to the pucch-PathlossReferenceRS-Id in [Table 22]. Up to four settings are possible through the pathlossReferenceRSs within the parent signaling PUCCH-PowerControl in [Table 23]. If PUCCH-PathlossReferenceRS is connected to SS / PBCH via the parent signaling referenceSignal, it receives the ssb-Index, and if it is connected to CSI-RS, it receives the csi-RS-Index.
[0238] [Table 23]
[0239]
[0240] [PUCCH: Regarding transmission power]
[0241] In one embodiment of the present disclosure, a method is described in which, when a terminal transmits uplink control information through a Physical Uplink Control Channel (PUCCH) in response to a power control command received from a base station, the terminal sets and transmits the transmission power of the uplink control channel. For example, the uplink control channel transmission power (P) of the terminal is described together with a PUCCH power control adjustment state corresponding to the i-th transmission unit and closed-loop index l. PUCCH ) can be determined as shown in [Equation 3] below, expressed in dBm units. In [Equation 3] below, if the terminal supports multiple carrier frequencies in multiple cells, each parameter can be determined separately for the primary cell c, carrier frequency f, and bandwidth part b, and can be distinguished by indices b, f, and c.
[0242] [Mathematical Formula 3]
[0243]
[0244] - P CMAX,f,c (i): The maximum transmission power available to the terminal in the i-th transmission unit, determined based on the terminal's power class, parameters activated from the base station, and various parameters built into the terminal.
[0245] - P 0_PUCCH,b,f,c (q u ): P 0_PUCCH,b,f,c (q u ) is P 0_NOMINAL_PUCCH and P 0_UE_PUCCH (q u It can be composed of the sum of ). P 0_NOMINAL_PUCCH is set to a cell-specific value via p0-nominal, which is cell-specific upper-layer signaling, and if such a setting does not exist, P 0_NOMINAL_PUCCH can be 0 dBm. P 0_UE_PUCCH (q u ) is set as a terminal-specific value through the p0-PUCCH-Value within the p0-PUCCH, which is an upper-layer signaling in the primary cell c, with bandwidth part b, carrier frequency f, and q u is greater than or equal to 0 and Q u It can be a smaller value. Q u is P 0_UE_PUCCH It can represent the size of the set of values and can be set through the upper-layer signaling maxNrofPUCCH-P0-PerSet. P 0_UE_PUCCH The set of values can be configured through the upper-layer signaling p0-Set, and if such a configuration does not exist It can be identified as.
[0246] - μ: Subcarrier spacing configuration value
[0247] - Bandwidth part b, carrier frequency f, and the amount of resources used in the i-th PUCCH transmission unit within the primary cell c (e.g., the number of Resource Blocks (RBs) used for PUCCH transmission in the frequency axis) can be referenced.
[0248] - PL b,f,c (q d ): As pathloss representing the path loss between the base station and the terminal, the terminal uses the Reference Signal (RS) resource q signaled by the base station. d Path loss can be calculated from the difference between the transmission power and the terminal reception signal level of the reference signal.
[0249] - For PUCCH format 0, if the upper layer signaling deltaF-PUCCH-f0 is set, the corresponding value is used; for PUCCH format 1, if the upper layer signaling deltaF-PUCCH-f1 is set, the corresponding value is used; for PUCCH format 2, if the upper layer signaling deltaF-PUCCH-f2 is set, the corresponding value is used; for PUCCH format 3, if the upper layer signaling deltaF-PUCCH-f3 is set, the corresponding value is used; for PUCCH format 4, if the upper layer signaling deltaF-PUCCH-f4 is set, the corresponding value is used; and for all PUCCH formats, if the upper layer signaling is not set, 0 may be used.
[0250] - As a PUCCH transmission power adjustment factor within the bandwidth part b, carrier frequency f, and primary cell c, different calculation methods can be used depending on the PUCCH format.
[0251] - g b,f,c(i,l): This may represent the PUCCH power control adjustment status value for the i-th PUCCH transmission unit corresponding to the closed-loop index l within the primary cell c, with bandwidth part b and carrier frequency f. Here, the closed-loop power adjustment for PUCCH transmission may use an accumulation method that applies values instructed by TPC commands by accumulating them.
[0252] PUCCH power control adjustment status g b,f,c (i,l) can be determined through bandwidth part b, carrier frequency f, primary cell c, i-th transmission unit, and closed-loop index l.
[0253] - δPUCCH,b,f,c(i,l): In a bandwidth part b, carrier frequency f, and primary cell c, the value indicated by the TPC command field included in DCI format 1_0, 1_1, or 1_2 that schedules the i-th PUCCH transmission unit corresponding to the closed loop index l and the PDSCH reception, or the value indicated by the TPC command field included in DCI format 2_2 that is transmitted with a CRC scrambled with TPC-PUCCH-RNTI.
[0254] ○ If the terminal has received the upper layer signaling, twoPUCCH-PC-AdjustmentStates and PUCCH-SpatialRelationInfo, the closed loop index l can have a value of 0 or 1.
[0255] ○ If the terminal does not receive the upper layer signaling, such as twoPUSCH-PC-AdjustmentStates or PUCCH-SpatialRelationInfo, the closed loop index l may have a value of 0.
[0256] If the terminal obtains a TPC command value through the TPC command field included in DCI format 1_0, 1_1, or 1_2 that schedules PDSCH reception, and the terminal receives PUCCH-SpatialRelationInfo, which is an upper layer signaling, the terminal can obtain a connection relationship between the pucch-SpatialRelationInfoId value and the closedLoopIndex value that sets the closed loop index l based on an index that can be obtained through the upper layer signaling p0-PUCCH-Id. If the terminal receives a MAC-CE corresponding to pucch-SpatialRelationInfoId, the terminal can determine the closedLoopIndex value that sets the closed loop index l based on the corresponding p0-PUCCH-Id index.
[0257] If the terminal obtains a TPC command value from the TPC command field included in DCI format 2_2, which is transmitted along with a CRC scrambled in TPC-PUCCH-RNTI, it can obtain a value based on the closed-loop index field included in the DCI format 2_2.
[0258] - Within the primary cell c, bandwidth part b, carrier frequency f, PUCCH power control regulation state g for the i-th PUCCH transmission unit corresponding to the closed-loop index l. b,f,c (i,l) can be calculated as in [Equation 4].
[0259] [Mathematical Formula 4]
[0260]
[0261] ○ δPUCCH,b,f,c(m,l) may be a value indicated by the TPC command field included in DCI format 1_0, 1_1, or 1_2 that schedules PDSCH reception with the m-th PUCCH transmission unit corresponding to the closed-loop index l within the bandwidth part b, carrier frequency f, and primary cell c as described above, or a value indicated by the TPC command field included in DCI format 2_2 that is transmitted along with a CRC scrambled with TPC-PUCCH-RNTI. If TPC command accumulation operation is possible, the δPUCCH,b,f,c value may have a value in [dB] units corresponding to the value indicated by the TPC command field included in DCI format 1_0, 1_1, 1_2, or 2_2 as shown in [Table 26]. For example, if the value of the TPC command field is 0, δPUCCH,b,f,c may have a value of -1 dB.
[0262] ○ is the aforementioned TPC command value for a specific set C i It can mean the sum of δPUCCH,b,f,c for all corresponding transmission units within. In this case, c(C i ) is set C i It can be referenced as the number of all elements contained within. C i can be referred to as a set of DCIs containing all TPC command values to perform the TPC command accumulation operation for the i-th PUCCH transmission unit. C i To determine, define a start point and an end point in the time dimension, and C all DCIs received by the terminal within the two points. i It can be included as an element of.
[0263] ● C i The end point for determining is K from the start symbol of the i-th PUCCH transmission unit. PUCCH(i) It can be a point earlier by the symbol.
[0264] ● C i The starting point for determining is K from the start symbol of the i-i0th PUCCH transmission unit. PUCCH It can be a point earlier by (i-i0)-1 symbols. In this case, i0, a positive integer, is the above C i The end point for determining (K from the start symbol of the i-th PUCCH transmission unit) PUCCH (i) K from the start symbol of the i - i0th PUCCH transmission unit compared to the point (i) earlier by a number of symbols. PUCCH The time point that is (i-i0) symbols earlier can be determined as the smallest value that satisfies the condition that it is an earlier time point.
[0265] ● For example, C i The end point for determining can be defined as sym(i), and K from the start symbol of the i-i0th PUCCH transmission unit PUCCH If the time point (i-i0) earlier can be defined as sym(i - i0), then if sym(i) = sym(i - 1) > sym(i - 2) > sym(i - 3) holds, then i0 can be determined as 2.
[0266] [PUSCH: Regarding transmission method]
[0267] Next, the scheduling method for PUSCH transfers is described. PUSCH transfers may be dynamically scheduled by a UL grant within the DCI, or operated by a configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transfers may be provided by DCI format 0_0 or 0_1.
[0268] Configured grant Type 1 PUSCH transmissions can be configured semi-statically by receiving configuredGrantConfig, which includes rrc-ConfiguredUplinkGrant of [Table 24], through a higher-level signaling (e.g., configuration information), without receiving UL grants within the DCI. Configured grant Type 2 PUSCH transmissions can be scheduled semi-continuously by UL grants within the DCI after receiving configuredGrantConfig, which does not include rrc-ConfiguredUplinkGrant of [Table 24], through a higher-level signaling. When a PUSCH transmission is operated by a configured grant, the parameters applied to the PUSCH transmission may be applied through configuredGrantConfig, the higher-level signaling of [Table 24], with the exception of dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and / or scaling of UCI-OnPUSCH, which are provided by pusch-Config, the higher-level signaling of [Table 25]. If the terminal is provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of [Table 24], the terminal can apply tp-pi2BPSK in pusch-Config of [Table 25] to PUSCH transmissions operated by the configured grant.
[0269] [Table 24]
[0270]
[0271]
[0272] Next, the PUSCH transmission method is described. The DMRS antenna port for PUSCH transmission may be the same as the antenna port for SRS transmission. PUSCH transmission may follow a codebook-based transmission method and a non-codebook-based transmission method, respectively, depending on whether the value of txConfig in pusch-Config in [Table 25], the upper signaling, is 'codebook' or 'nonCodebook'.
[0273] As described above, PUSCH transmissions can be dynamically scheduled via DCI format 0_0 or 0_1 and semi-statically configured by a configured grant. If a terminal is instructed to schedule a PUSCH transmission via DCI format 0_0, the terminal may perform beam configuration for the PUSCH transmission using the pucch-spatialRelationInfoID corresponding to the terminal-specific PUCCH resource corresponding to the minimum ID within an active uplink BWP in the serving cell. In this case, the PUSCH transmission is based on a single antenna port. Within a BWP where the PUCCH resource containing pucch-spatialRelationInfo is not configured, the terminal may not expect scheduling for the PUSCH transmission via DCI format 0_0. If the terminal has not configured the txConfig within the pusch-Config of [Table 25], the terminal may not expect to be scheduled via DCI format 0_1.
[0274] [Table 25]
[0275]
[0276] Next, codebook-based PUSCH transmission is described. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1 and can operate semi-statically via a configured grant. When codebook-based PUSCH is dynamically scheduled via DCI format 0_1 or semi-statically configured via a configured grant, the terminal can determine a precoder for PUSCH transmission based on the SRS Resource Indicator (SRI), Transmission Precoding Matrix Indicator (TPMI), and the transmission rank (number of PUSCH transmission layers).
[0277] In this case, the SRI may be provided via the SRS resource indicator field within the DCI or configured via the higher-level signaling srs-ResourceIndicator. When a terminal receives at least one SRS resource during codebook-based PUSCH transmission, it may receive up to two. When the terminal receives an SRI via the DCI, the SRS resource indicated by the provided SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted prior to the PDCCH containing that SRI. For example, the TPMI and transmission rank may be provided via the precoding information and number of layers field within the DCI or configured via the higher-level signaling precodingAndNumberOfLayers. The TPMI may be used to indicate the precoder applied to the PUSCH transmission. If the terminal receives one SRS resource, the TPMI may be used to indicate the precoder to be applied from the configured one SRS resource. If the terminal is configured with multiple SRS resources, TPMI can be used to specify the precoder to be applied to the SRS resource indicated by SRI.
[0278] The precoder to be used for PUSCH transmission can be selected from an uplink codebook having the same number of antenna ports as the nrofSRS-Ports value in the upper signaling SRS-Config. In codebook-based PUSCH transmission, the terminal can determine the codebook subset based on TPMI and the codebookSubset in the upper signaling pusch-Config. The codebookSubset in the upper signaling pusch-Config can be set to one of 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', or 'nonCoherent' based on the UE capability reported by the terminal to the base station. If the terminal reports 'partialAndNonCoherent' as the UE capability, the terminal may not expect the value of the upper signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent'. Additionally, if the terminal reports 'nonCoherent' as a UE capability, the terminal may not expect the value of the parent signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent'. If nrofSRS-Ports in the parent signaling SRS-ResourceSet points to two SRS antenna ports, the terminal may not expect the value of the parent signaling codebookSubset to be set to 'partialAndNonCoherent'.
[0279] A terminal can receive one SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'codebook', and one SRS resource within that SRS resource set can be indicated via SRI. If multiple SRS resources are configured within the SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'codebook', the terminal can expect that the value of nrofSRS-Ports within the upper signaling SRS-Resource will be set to the same value for all SRS resources.
[0280] A terminal may transmit one or more SRS resources included in an SRS resource set in which the value of usage is set to 'codebook' according to the upper signaling, to a base station, and the base station may select one of the SRS resources transmitted by the terminal and instruct the terminal to perform PUSCH transmission using the transmit beam information of the corresponding SRS resource. In this case, in codebook-based PUSCH transmission, SRI is used as information to select the index of one SRS resource and may be included in the DCI. Additionally, the base station may include information in the DCI that instructs the TPMI and rank to be used by the terminal for PUSCH transmission. The terminal may perform PUSCH transmission by using the SRS resource instructed by the SRI, applying the instructed rank based on the transmit beam of the corresponding SRS resource and the precoder instructed by the TPMI.
[0281] Next, non-codebook-based PUSCH transmission is described. Non-codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1 and can operate semi-statically via configured grant. If at least one SRS resource is configured within an SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'nonCodebook', the terminal can receive a non-codebook-based PUSCH transmission scheduled via DCI format 0_1.
[0282] For an SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'nonCodebook', the terminal can receive one connected NZP CSI-RS resource (non-zero power CSI-RS). The terminal can perform calculations for a precoder for SRS transmission by measuring the NZP CSI-RS resource connected to the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of the aperiodic SRS transmission at the terminal is less than 42 symbols, the terminal may not expect the information for the precoder for SRS transmission to be updated.
[0283] If the value of resourceType within the SRS-ResourceSet, which is the upper signaling (e.g., configuration information), is set to 'aperiodic', the connected NZP CSI-RS may be indicated by the SRS request field within DCI format 0_1 or 1_1. In this case, if the connected NZP CSI-RS resource is a non-periodic NZP CSI-RS resource, the existence of the connected NZP CSI-RS may be indicated if the value of the SRS request field within DCI format 0_1 or 1_1 is not '00'. In this case, the corresponding DCI may not indicate cross-carrier or cross-BWP scheduling. Additionally, if the value of the SRS request indicates the existence of the NZP CSI-RS, the NZP CSI-RS may be located in the slot where the PDCCH containing the SRS request field was transmitted. In this case, the TCI states configured on the scheduled subcarrier may not be set to QCL-TypeD.
[0284] If a periodic or semi-persistent SRS resource set is established, the associated NZP CSI-RS can be indicated via the associated CSI-RS within the parent signaling SRS-ResourceSet. For non-codebook-based transmissions, the terminal may not expect the parent signaling spatialRelationInfo for the SRS resource and the associated CSI-RS within the parent signaling SRS-ResourceSet to be established together.
[0285] When a terminal is configured with multiple SRS resources, the terminal can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. In this case, the SRI may be indicated via the field SRS resource indicator within the DCI or configured via the higher-level signaling srs-ResourceIndicator. Similar to the codebook-based PUSCH transmission described above, when the terminal receives the SRI via the DCI, the SRS resource indicated by the provided SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted prior to the PDCCH containing the SRI. The terminal may use one or multiple SRS resources for SRS transmission, and the maximum number of SRS resources that can be transmitted simultaneously within the same symbol in a single SRS resource set, as well as the maximum number of SRS resources, can be determined by the UE capability reported by the terminal to the base station. In this case, the SRS resources transmitted simultaneously by the terminal occupy the same RB. The terminal configures one SRS port for each SRS resource. Only one SRS resource set can be configured with the value of usage in the upper signaling SRS-ResourceSet set set to 'nonCodebook', and up to four SRS resources can be configured for non-codebook based PUSCH transmission.
[0286] The base station transmits one NZP-CSI-RS associated with an SRS resource set to the terminal, and the terminal can calculate a precoder to be used when transmitting one or more SRS resources within the SRS resource set based on the results measured upon receiving the NZP-CSI-RS. The terminal applies the calculated precoder when transmitting one or more SRS resources within an SRS resource set where usage is set to 'nonCodebook' to the base station, and the base station can select one or more SRS resources from among the received one or more SRS resources. In this case, in non-codebook-based PUSCH transmission, the SRI represents an index capable of expressing a combination of one or more SRS resources, and the said SRI may be included within the DCI. In this case, the number of SRS resources indicated by the SRI transmitted by the base station may be the number of transmission layers of the PUSCH, and the terminal can transmit the PUSCH by applying the precoder applied for SRS resource transmission to each layer.
[0287] [PUSCH: Regarding transmission power]
[0288] In one embodiment of the present disclosure, a method is described in which a terminal sets and transmits the transmission power of the uplink data channel in response to a power control command received from a base station and transmits uplink data through an uplink data channel (PUSCH; Physical Uplink Shared Channel). The uplink data channel transmission power of the terminal, together with the i-th transmission unit, parameter set setting index j, and the PUSCH power control adjustment state corresponding to the closed loop index l, can be determined as shown in [Equation 5] below, which is expressed in dBm units. In [Equation 5] below, if the terminal supports multiple carrier frequencies in multiple cells, each parameter can be determined separately for cell c, carrier frequency f, and bandwidth part b, and can be distinguished by indices b, f, and c.
[0289] [Mathematical Formula 5]
[0290]
[0291] - P CMAX,f,c (i): The maximum transmission power available to the terminal in the i-th transmission unit, which can be determined by the terminal's power class, parameters activated from the base station, and various parameters built into the terminal.
[0292] - P 0_PUSCH,b,f,c (j): P 0_PUSCH,b,f,c (j) is P 0_NOMINAL_PUSCH,f,c (j) and P 0_UE_PUSCH,b,f,c It consists of the sum of (j). P 0_NOMINAL_PUSCH,f,c (j) is set to cell-specific upper-layer signaling for the terminal, and P 0_UE_PUSCH,b,f,c(j) may be a value set to terminal-specific upper layer signaling. Here, when j=0, it means PUSCH to transmit msg3; when j=1, it means configured grant PUSCH; and if j={2, ..., J-1}, it means grant PUSCH.
[0293] - μ: Subcarrier spacing configuration value
[0294] - It can refer to the amount of resources used in the i-th PUSCH transmission unit (e.g., the number of Resource Blocks (RBs) used for PUSCH transmission in the frequency axis).
[0295] - α b,f,c (j) A value for compensating for path loss, which can be determined through upper layer settings and SRI (SRS Resource Indicator) (in the case of dynamic grant PUSCH).
[0296] - PL b,f,c (q d ): Can be referenced as pathloss, representing the path loss between the base station and the terminal. The terminal receives the Reference Signal (RS) resource q signaled by the base station. d Pathloss is calculated from the difference between the transmitted power and the terminal received signal level of the reference signal. The reference signal index is q d It refers to the downlink path loss estimate calculated by the terminal using the reference signal, and the reference signal index q dThe terminal can determine this through upper layer settings and SRI (in the case of dynamic grant PUSCH or ConfiguredGrantConfig-based configured grant PUSCH (type 2 configured grant PUSCH) that does not include upper layer settings rrc-ConfiguredUplinkGrant) or through upper layer settings.
[0297] - It may refer to a value determined by the format of the information transmitted via MCS (Modulation Coding Scheme) and PUSCH (TF: transport format, e.g., whether UL-SCH is included or CSI is included, etc.).
[0298] - f b,f,c (i,l): A closed-loop power control adjustment value, which can represent the value for the closed-loop index l, which can be determined by the upper layer setting and SRI for PUSCH. Here, closed-loop power adjustment for PUSCH transmission can be supported by dividing it into an accumulation method, which applies the value indicated by the TPC command by accumulating it, and an absolute method, which applies the value indicated by the TPC command directly; this can be determined based on whether the upper layer parameter tpc-Accumulation is set. If the upper layer parameter tpc-Accumulation is set to disabled, closed-loop power adjustment for PUSCH transmission is performed using the absolute method, and if tpc-Accumulation is not set, closed-loop power adjustment for PUSCH transmission is performed using the accumulation method.
[0299] PUSCH power control adjustment status f b,f,c (i,l) can be determined through bandwidth part b, carrier frequency f, cell c, i-th transmission unit, and closed-loop index l.
[0300] - δPUSCH,b,f,c(i,l): A value indicated by a TPC command field included in DCI format 0_0, 0_1, or 0_2 that schedules the i-th PUSCH transmission unit corresponding to the closed-loop index l within bandwidth part b, carrier frequency f, and cell c, or a value indicated by a TPC command field included in DCI format 2_2 that is transmitted with a CRC scrambled with TPC-PUSCH-RNTI.
[0301] ○ If the terminal has received the upper layer signaling twoPUSCH-PC-AdjustmentStates, the closed loop index l can have a value of 0 or 1.
[0302] ○ If the terminal has not received twoPUSCH-PC-AdjustmentStates, which is an upper layer signaling, or has scheduled a PUSCH transmission based on RAR UL grant, the closed loop index l may have a value of 0.
[0303] ● If the terminal receives the upper layer signaling ConfiguredGrantConfig and performs a PUSCH transmission or retransmission for it, the closed loop index l may follow the upper layer signaling powerControlLoopToUse value.
[0304] ● If the terminal has received the upper layer signaling SRI-PUSCH-PowerControl, the terminal can obtain the connection between the value indicated by the SRI (SRS resource indicator) field within the DCI format that scheduled the PUSCH transmission and the closed loop index l established through the upper layer signaling sri-PUSCH-ClosedLoopIndex, and can determine the closed loop index l based on the value indicated by the SRI field within the DCI format based on the corresponding connection.
[0305] ● If the terminal has been scheduled to send a PUSCH transmission based on a DCI format that does not include an SRI field, or has not been set to SRI-PUSCH-PowerControl, which is an upper layer signaling, the terminal can identify the closed loop index l as 0.
[0306] ● If the terminal is instructed to a TPC command value through the TPC command field included in DCI format 2_2, which is transmitted along with a CRC scrambled with TPC-PUSCH-RNTI, the closed loop index l can be instructed through the closed loop index field included in DCI format 2_2.
[0307] - If the terminal has not been configured with upper-layer signaling, namely tpc-accumulation, that is, if TPC command accumulation operation is possible for the terminal, then within bandwidth part b, carrier frequency f, cell c, the PUSCH power control regulation state f for the i-th PUSCH transmission unit corresponding to the closed-loop index l. b,f,c (i,l) can be calculated as in [Equation 6].
[0308] [Mathematical Formula 6]
[0309]
[0310] ○ δPUSCH,b,f,c(m,l) may be a value indicated by the TPC command field included in DCI format 0_0, 0_1, or 0_2, which schedules the m-th PUSCH transmission unit corresponding to the closed-loop index l within the bandwidth part b, carrier frequency f, and cell c as described above, or a value indicated by the TPC command field included in DCI format 2_2, which is transmitted along with a CRC scrambled with TPC-PUSCH-RNTI. If TPC command accumulation operation is possible, the δPUSCH,b,f,c value may have a value in [dB] units corresponding to the value indicated by the TPC command field included in DCI format 0_0, 0_1, 0_2, or 2_2, as shown in [Table 26] below. For example, if the value of the TPC command field is 0, δPUSCH,b,f,c may have a value of -1 dB.
[0311] ○ is the aforementioned TPC command value for a specific set D i It can mean the sum of δPUSCH,b,f,c for all corresponding transmission units within. In this case, c(D i ) is set D i It can be referenced as the number of all elements contained within. D i can mean a set of DCIs containing all TPC command values for which a TPC command accumulation operation is to be performed for the i-th PUSCH transmission unit. D i To determine, define a start point and an end point in the time dimension, and all DCIs received by the terminal within the two points are D i It can be included as an element of.
[0312] ● D i The end point for determining is K from the start symbol of the i-th PUSCH transmission unit. PUSCH(i) It can be a point earlier by the symbol.
[0313] ● D i The starting point for determining is K from the start symbol of the i-i0th PUSCH transmission unit. PUSCH It can be a point earlier by (i-i0)-1 symbols. In this case, i0, a positive integer, is the above D i The end point for determining (K from the start symbol of the i-th PUSCH transmission unit) PUSCH (i) From the starting symbol of the i-i0th PUSCH transmission unit, K from the point (i) earlier by a number of symbols. PUSCH It can be determined as the smallest value that satisfies the condition that the time point earlier by (i-i0) symbols becomes an earlier time point in time.
[0314] ● For example, D i The end point for determining can be defined as sym(i), and K from the start symbol of the i-i0th PUSCH transmission unit PUSCH If a time point (i-i0) earlier can be defined as sym(i-i0), then if sym(i) = sym(i-1) > sym(i-2) > sym(i-3) holds, then i0 can be determined as 2.
[0315] - If the terminal has been configured with upper-layer signaling, namely TPC-Accumulation, that is, if TPC command accumulation operation is impossible for the terminal, then within bandwidth part b, carrier frequency f, cell c, the PUSCH power control regulation state f for the i-th PUSCH transmission unit corresponding to the closed-loop index l. b,f,c (i,l) can be calculated as in [Equation 7].
[0316] [Mathematical Formula 7]
[0317]
[0318] ○ δPUSCH,b,f,c(i,l) may be a value indicated by the TPC command field included in DCI format 0_0, 0_1, or 0_2, which schedules the i-th PUSCH transmission unit corresponding to the closed-loop index l within the bandwidth part b, carrier frequency f, and cell c as described above, or a value indicated by the TPC command field included in DCI format 2_2, which is transmitted along with a CRC scrambled with TPC-PUSCH-RNTI. If TPC command accumulation operation is not possible, the δPUSCH,b,f,c value may have a value in [dB] units corresponding to the value indicated by the TPC command field included in DCI format 0_0, 0_1, 0_2, or 2_2, as shown in [Table 26] below. For example, if the value of the TPC command field is 0, δPUSCH,b,f,c may have a value of -4 dB.
[0319] [Table 26]
[0320]
[0321] [Regarding SRS]
[0322] Next, a method for estimating the uplink channel using the transmission of the terminal's Sounding Reference Signal (SRS) is described. To transmit configuration information for SRS transmission to the terminal, the base station may set at least one SRS configuration for each uplink BWP, and the base station may also set at least one SRS resource set for each SRS configuration. For example, the base station and the terminal may exchange upper-level signaling information as follows to transmit information regarding the SRS resource set.
[0323] - srs-ResourceSetId: SRS resource set index
[0324] - srs-ResourceIdList: A set of SRS resource indices referenced by the SRS resource set
[0325] - resourceType: This is the time-axis transmission setting for the SRS resource referenced in the SRS resource set, and can be set to one of 'periodic', 'semi-persistent', or 'aperiodic'. If set to 'periodic' or 'semi-persistent', associated CSI-RS information may be provided depending on the usage of the SRS resource set. If set to 'aperiodic', a non-periodic SRS resource trigger list and slot offset information may be provided, and associated CSI-RS information may be provided depending on the usage of the SRS resource set.
[0326] - usage: A setting regarding the usage of the SRS resource referenced in the SRS resource set, which can be set to one of 'beamManagement', 'codebook', 'nonCodebook', or 'antennaSwitching'.
[0327] - alpha, p0, pathlossReferenceRS, srs-PowerControlAdjustmentStates: Provides parameter settings for controlling the transmit power of the SRS resource referenced in the SRS resource set.
[0328] The terminal can understand that the SRS resources included in the set of SRS resource indices referenced in the SRS resource set are based on the information set in the SRS resource set.
[0329] Additionally, the base station and the terminal may transmit and / or receive upper-layer signaling information to convey individual configuration information for the SRS resource. For example, the individual configuration information for the SRS resource may include time-frequency axis mapping information within the slot of the SRS resource, which may include information regarding frequency hopping within or between slots of the SRS resource. Additionally, the individual configuration information for the SRS resource may include the time-axis transmission setting of the SRS resource, which may be set to one of 'periodic', 'semi-persistent', or 'aperiodic'. This may be restricted to having the same time-axis transmission setting as the SRS resource set containing the SRS resource. If the time-axis transmission setting of the SRS resource is set to 'periodic' or 'semi-persistent', the SRS resource transmission period and slot offset (e.g., periodicityAndOffset) may additionally be included in the time-axis transmission setting.
[0330] A base station may enable, deactivate, or trigger SRS transmission to a terminal via upper-layer signaling, including RRC signaling or MAC CE signaling, or L1 signaling (e.g., DCI). For example, a base station may enable or deactivate periodic SRS transmission to a terminal via upper-layer signaling. The base station may instruct the terminal to activate an SRS resource set with resourceType set to periodic via upper-layer signaling, and the terminal may transmit an SRS resource referenced in the activated SRS resource set. The time-frequency axis resource mapping within the slot of the transmitted SRS resource may be based on resource mapping information set in the SRS resource, and the slot mapping, including the transmission period and slot offset, may be based on periodicityAndOffset set in the SRS resource. Additionally, a spatial domain transmission filter applied to the transmitted SRS resource may reference spatial relation info set in the SRS resource, or may reference associated CSI-RS information set in the SRS resource set containing the SRS resource. The terminal can transmit an SRS resource within an active uplink BWP for a periodic SRS resource activated through upper layer signaling.
[0331] For example, a base station can enable or disable semi-persistent SRS transmission to a terminal via upper-layer signaling. The base station can instruct the terminal to enable an SRS resource set via MAC CE signaling, and the terminal can transmit an SRS resource referenced in the enabled SRS resource set. The SRS resource set enabled via MAC CE signaling may be limited to an SRS resource set where the resourceType is set to semi-persistent. The time-frequency axis resource mapping within the slot of the transmitted SRS resource may be based on resource mapping information set in the SRS resource, and the slot mapping, including the transmission period and slot offset, may be based on periodicityAndOffset set in the SRS resource. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation info set in the SRS resource, or may refer to associated CSI-RS information set in the SRS resource set containing the SRS resource. If spatial relation info is configured in the SRS resource, the spatial domain transmission filter can be determined by referring to the configuration information regarding the spatial relation info transmitted via MAC CE signaling that enables semi-persistent SRS transmission without following it. The terminal can transmit the SRS resource within the uplink BWP enabled for the semi-persistent SRS resource activated via upper layer signaling.
[0332] For example, a base station can trigger an aperiodic SRS transmission to a terminal via the DCI. The base station can indicate one of the aperiodic SRS resource triggers (aperiodicSRS-ResourceTrigger) through the SRS request field of the DCI. The terminal can understand that among the configuration information of the SRS resource set, an SRS resource set containing the aperiodic SRS resource trigger indicated via the DCI from the list of aperiodic SRS resource triggers has been triggered. The terminal can transmit the SRS resource referenced in the triggered SRS resource set. The time-frequency axis resource mapping within the slot of the transmitted SRS resource can be based on the resource mapping information set in the SRS resource. Additionally, the slot mapping of the transmitted SRS resource can be determined through the slot offset between the PDCCH containing the DCI and the SRS resource, which can refer to the value(s) included in the set of slot offsets set in the SRS resource set. For example, the slot offset between a PDCCH containing a DCI and an SRS resource may be the value specified in the time domain resource assignment field of the DCI from among the offset value(s) included in the slot offset set configured in the SRS resource set. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource may refer to the spatial relation info configured in the SRS resource, or may refer to the associated CSI-RS information configured in the SRS resource set containing the SRS resource. The terminal may transmit the SRS resource within an uplink BWP that is enabled for a non-periodic SRS resource triggered via the DCI.
[0333] When a base station triggers aperiodic SRS transmission to a terminal via DCI, a minimum time interval may be required between the PDCCH containing the DCI triggering the aperiodic SRS transmission and the transmitted SRS so that the terminal can apply configuration information for the SRS resource and transmit the SRS. The time interval for the terminal's SRS transmission can be defined as the number of symbols between the last symbol of the PDCCH containing the DCI triggering the aperiodic SRS transmission and the first symbol mapped to the first transmitted SRS resource(s). The minimum time interval can be determined by referencing the PUSCH preparation procedure time required for the terminal to prepare for PUSCH transmission. Additionally, the minimum time interval may have different values depending on the usage of the SRS resource set containing the transmitted SRS resource. For example, the minimum time interval can be determined by N2 symbols defined based on the terminal's processing capability according to the terminal's capability, by referencing the terminal's PUSCH preparation procedure time. Additionally, considering the usage of the SRS resource set including the transmitted SRS resource, if the usage of the SRS resource set is set to 'codebook' or 'antennaSwitching', the minimum time interval can be set to N2 symbols, and if the usage of the SRS resource set is set to 'nonCodebook' or 'beamManagement', the minimum time interval can be set to N2+14 symbols.The terminal transmits an aperiodic SRS when the time interval for the aperiodic SRS transmission is greater than or equal to the minimum time interval, and can ignore the DCI that triggers the aperiodic SRS when the time interval for the aperiodic SRS transmission is less than the minimum time interval.
[0334] [Table 27]
[0335]
[0336] The spatialRelationInfo setting information in [Table 27] is intended to be applied to the beam information of a reference signal (e.g., the beam used for the SRS transmission) by referencing a single reference signal. For example, the spatialRelationInfo setting may include at least some of the information shown in [Table 28] below.
[0337] [Table 28]
[0338]
[0339] By referring to the spatialRelationInfo setting, the index of the reference signal to be referenced in order to use the beam information of a specific reference signal—namely, the SS / PBCH block index, CSI-RS index, and / or SRS index—can be set. The upper signaling referenceSignal may be configuration information indicating which reference signal's beam information to reference for the corresponding SRS transmission. ssb-Index can be referenced as the SS / PBCH block index, csi-RS-Index can be referenced as the CSI-RS index, and srs can be referenced as the SRS index. If the value of the upper signaling referenceSignal is set to 'ssb-Index', the terminal can apply the receiving beam used when receiving the SS / PBCH block corresponding to ssb-Index as the transmitting beam for the corresponding SRS transmission. If the value of the upper signaling referenceSignal is set to 'csi-RS-Index', the terminal can apply the receiving beam used when receiving the CSI-RS corresponding to csi-RS-Index as the transmitting beam for the corresponding SRS transmission. If the value of the upper signaling referenceSignal is set to 'srs', the terminal can apply the transmitting beam used when transmitting the SRS corresponding to srs as the transmitting beam for the corresponding SRS transmission.
[0340] [Regarding SRS transmission power]
[0341] In one embodiment of the present disclosure, a method is described in which a terminal sets and transmits the transmission power of an uplink reference signal (e.g., Sounding Reference Signal (SRS)) in response to a power control command received from a base station. The uplink reference signal transmission power (P) of the terminal is described together with an SRS power control adjustment state corresponding to the i-th transmission unit and closed-loop index l. SRS ) can be determined as shown in the following [Equation 8], expressed in dBm units. In the following [Equation 8], if the terminal supports multiple carrier frequencies in multiple cells, each parameter can be determined separately for cell c, carrier frequency f, and bandwidth part b, and can be distinguished by indices b, f, and c.
[0342] [Mathematical Formula 8]
[0343]
[0344] - P CMAX,f,c (i): This can be referenced as the maximum transmission power available to the terminal in the i-th transmission unit, and is determined by the terminal's power class, parameters activated from the base station, and various parameters built into the terminal.
[0345] - P 0_SRS,b,f,c (q s ): For bandwidth part b, carrier frequency f, and cell c, it can be set to p0 within the SRS-ResourceSet, which is the upper layer signaling, and SRS resource set q s It can be configured through the upper layer signaling, SRS-ResourceSet and SRS-ResourceSetId.
[0346] - μ: Subcarrier spacing configuration value
[0347] - M SRS,b,f,c(i): Can be referenced as the amount of resources used in the i-th SRS transmission unit (e.g., the number of Resource Blocks (RBs) used for SRS transmission in the frequency axis).
[0348] - α SRS,b,f,c (j): Can be set to alpha, which is the upper layer signaling for bandwidth part b, carrier frequency f, and cell c, and SRS resource set q s It can be configured through the upper layer signaling, SRS-ResourceSet and SRS-ResourceSetId.
[0349] - PL b,f,c (q d ): Can be referenced as pathloss representing the path loss between the base station and the terminal, and the terminal uses the Reference Signal (RS) resource q signaled by the base station. d Path loss is calculated from the difference between the transmission power and the terminal reception signal level of the reference signal.
[0350] - h b,f,c (i,l): Can be referenced as the SRS power control adjustment status value for the i-th SRS transmission unit corresponding to the closed-loop index l within the band part b, carrier frequency f, and cell c.
[0351] The SRS power control adjustment state can be determined through bandwidth part b, carrier frequency f, cell c, and the i-th transmission unit.
[0352] - If the terminal is configured to have the same power control adjustment state value between SRS and PUSCH transmissions via srs-PowerControlAdjustmentStates, which is a higher-layer signaling (e.g., RRC signaling), the SRS power control adjustment state can be represented as shown in [Equation 9] below. In [Equation 9], f b,f,c(i,l) can be referred to as the current PUSCH power control adjustment state. In this case, through the various methods of Example 1 described above, f b,f,c (i,l) can be calculated, and the calculated value is h b,f,c It can be used by substituting into (i,l).
[0353] [Mathematical Formula 9]
[0354]
[0355] - If the terminal is not configured for PUSCH transmission in bandwidth part b, carrier frequency f, cell c, or is configured to have separate power control adjustment state values between SRS transmission and PUSCH transmission through srs-PowerControlAdjustmentStates, which is an upper layer signaling (e.g., RRC signaling), and tpc-Accumulation, which is an upper layer signaling, is not configured, the SRS power control adjustment state can be represented independently of the closed loop l as shown in [Equation 10] below.
[0356] [Mathematical Formula 10]
[0357]
[0358] - δ SRS,b,f,c (m): This may be a value indicated by the TPC command field included in DCI format 2_3, and the value may be based on [Table 17].
[0359] ○ is the aforementioned TPC command value for a specific set S i δ for all transmission units corresponding within SRS,b,f,c It can be referenced as the sum of. In this case, c(S i ) is set S i It can be referenced as the number of all elements belonging within. S ican be referred to as a set of DCIs containing all TPC command values for which a TPC command accumulation operation is to be performed for the i-th PUSCH transmission unit. S i To determine, a start point and an end point are defined in the time dimension, and all DCIs received by the terminal between the two points are S i It can be included as an element of.
[0360] ● S i The end point for determining is K from the start symbol of the i-th SRS transmission unit. SRS (i) It can be a point earlier by the symbol.
[0361] ● S i The starting point for determining is K from the start symbol of the i-i0th SRS transmission unit. SRS It may be a point earlier by (i-i0)-1 symbols. In this case, i0, a positive integer, is the above S i End point for determining (K from the start symbol of the i-th SRS transmission unit) SRS (i) K from the start symbol of the i - i0th SRS transmission unit compared to the point (i) earlier by a number of symbols. SRS It can be determined as the smallest value that satisfies the condition that the time point earlier by (i-i0) symbols becomes an earlier time point in time.
[0362] ● For example, S i The end point for determining can be defined as sym(i), and K from the start symbol of the i-i0th SRS transmission unit SRS The time point earlier by (i-i0) symbols can be defined as sym(i - i0), and if sym(i) = sym(i-1) > sym(i-2) > sym(i-3) holds, i0 can be determined as 2.
[0363] - If the terminal is not configured for PUSCH transmission in bandwidth part b, carrier frequency f, cell c, or is configured to have separate power control adjustment state values between SRS transmission and PUSCH transmission through the upper layer signaling srs-PowerControlAdjustmentStates, and the upper layer signaling tpc-Accumulation is configured (e.g., when TPC command accumulation operation cannot be performed and absolute TPC command values can be applied), the SRS power control adjustment state can be represented independently of the closed loop l as shown in [Equation 11] below.
[0364] [Mathematical Formula 11]
[0365]
[0366] ○ δ SRS,b,f,c (i) may be a value indicated by the TPC command field included in DCI format 2_3 within bandwidth part b, carrier frequency f, and cell c as described above. The value may follow [Table 26]. For example, if the value of the TPC command field is 0, δ SRS,b,f,c It can have a value of -4 dB.
[0367] Embodiments of the present disclosure are described in detail below together with the accompanying drawings. The contents of the present disclosure may be applied to FDD (frequency division duplex) and TDD (time division duplex) systems. In the present disclosure, upper signaling (or upper layer signaling) is a signal transmission method transmitted from a base station to a terminal using a physical layer downlink data channel, or from a terminal to a base station using a physical layer uplink data channel, and may be referred to as RRC signaling, PDCP (packet data convergence protocol) signaling, or a MAC (medium access control) control element (MAC CE).
[0368] In the present disclosure, the terminal may determine whether cooperative communication is applied in various ways. For example, the PDCCH(s) that assign the PDSCH to which cooperative communication is applied may have a specific format, and the terminal may determine whether it is applied based on whether it is in a specific format. As another example, the PDCCH(s) that assign the PDSCH to which cooperative communication is applied may include a specific indicator indicating whether cooperative communication is applied, and the terminal may determine whether it is applied based on the specific indicator. As yet another example, the PDCCH(s) that assign the PDSCH to which cooperative communication is applied may be scrambled with a specific RNTI, and the terminal may determine whether cooperative communication is applied based on whether it is scrambled with a specific RNTI. As yet another example, various methods may be used, such as assuming the application of cooperative communication in a specific section indicated to the upper layer. For convenience of explanation thereafter, the terminal receiving a PDSCH to which cooperative communication is applied based on similar conditions described above may be referred to as a non-coherent joint transmission (NC-JT) case.
[0369] In the present disclosure below, determining the priority between A and B may be referred to in various ways, such as selecting the one with higher priority according to a predetermined priority rule and performing the corresponding action, or omitting or dropping the action for the one with lower priority.
[0370] In the following disclosure, the examples described above are explained through a number of embodiments, but these are not independent and one or more embodiments may be applied simultaneously or in combination.
[0371] For convenience in the following description of the present disclosure, cells, transmission points, panels, beams, and / or transmission directions that can be distinguished through upper layer / L1 (layer 1) parameters such as TCI state or spatial relation information, or indicators such as cell ID (identity), TRP ID, and panel ID, may be described uniformly as TRP (transmission reception point), beam, or TCI state. Accordingly, in actual application, TRP, beam, or TCI state may be appropriately replaced with one of the above terms.
[0372] In the present disclosure, when determining whether cooperative communication is applied, the terminal may use various methods, such as the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied having a specific format, or the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied including a specific indicator indicating whether cooperative communication is applied, or the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied being scrambled with a specific RNTI, or assuming the application of cooperative communication in a specific section indicated to an upper layer. For convenience of explanation thereafter, the case in which the terminal receives a PDSCH to which cooperative communication is applied based on conditions similar to those above will be referred to as the NC-JT case.
[0373] Hereinafter, the base station, as the entity performing resource allocation for terminals, may be at least one of a gNode B, a gNB (next generation node B), an eNode B (EUTRAN (Evolved-UMTS (Universal Mobile Telecommunications System) Terrestrial Radio Access Network) node B), a Node B, a BS (Base Station), a radio access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Although embodiments of the present disclosure are described below as an example of a 5G system, this is merely an example. Embodiments of the present disclosure may be applied to other communication systems having similar technical backgrounds or channel types. For example, LTE (long term evolution) or LTE-A (advanced) mobile communication and mobile communication technologies developed after 5G may be included in other communication systems. Accordingly, the embodiments of the present disclosure may be applied to other communication systems with some modifications, provided that they do not deviate significantly from the scope of the present disclosure, in the judgment of a person skilled in the art.
[0374] Furthermore, in describing the present disclosure, if it is determined that a detailed description of related functions or configurations would unnecessarily obscure the essence of the present disclosure, such detailed description may be omitted. Additionally, the terms described below are defined in consideration of their functions within the present disclosure, and these definitions may vary depending on the intentions or practices of the user or operator. Therefore, their definitions should be based on the content throughout this specification.
[0375] In describing the present disclosure below, the term "upper layer signaling" may be a signaling corresponding to at least one or a combination of at least one of the following signalings.
[0376] - MIB (Master Information Block)
[0377] - SIB (System Information Block) or SIB
[0378] - RRC (Radio Resource Control)
[0379] - MAC (Medium Access Control) CE (Control Element)
[0380] In addition, L1 signaling may be a signaling corresponding to at least one or a combination of at least one of the following physical layer channels or signaling methods using signaling.
[0381] - PDCCH (Physical Downlink Control Channel)
[0382] - DCI (Downlink Control Information)
[0383] - Terminal-specific (UE-specific) DCI
[0384] - Group common DCI
[0385] - Common DCI
[0386] - Scheduling DCI (e.g., DCI used for the purpose of scheduling downlink or uplink data)
[0387] - Non-scheduling DCI (e.g., DCI not intended for scheduling downlink or uplink data)
[0388] - PUCCH (Physical Uplink Control Channel)
[0389] - UCI (Uplink Control Information)
[0390] In the present disclosure below, determining the priority between A and B may be referred to in various ways, such as selecting the one with the higher priority according to a predetermined priority rule and performing the corresponding action, or omitting or dropping the action for the one with the lower priority.
[0391] The term "slot" as used in the present disclosure below may be a general term that can refer to a specific time unit corresponding to a Transmit Time Interval (TTI). For example, the term "slot" may refer to a slot used in a 5G NR system, or a slot or subframe used in a 4G LTE system.
[0392] In the present disclosure, the examples described above are explained through a number of embodiments, but these are not independent, and one or more embodiments may be applied simultaneously or in combination. For example, the embodiments described above and the embodiments described below can be combined by a person skilled in the art.
[0393] The present disclosure may be primarily used in FR (frequency range) 2 (above 6 GHz), commonly referred to as the mmW band, or FR3 (7 GHz to 24 GHz), which is a candidate band for 6G communication systems, and operation in FR1 (below 6 GHz) may also not be excluded.
[0394] FIG. 8 is a diagram showing a transmission / reception beam management method in a wireless communication system according to one embodiment of the present disclosure.
[0395] Referring to FIG. 8, when a base station (e.g., gNB) according to one embodiment is connected to and operated with a plurality of terminals (e.g., UE1, UE2, UE3), the base station may provide the terminals with quasi-static uplink transmission configuration information through upper layer signaling. For example, such quasi-static uplink transmission configuration information may include a periodic PUCCH resource for a Scheduling Request (SR) that allows the terminal to request scheduling as there is data to be transmitted to the base station, a periodic PUCCH resource for a periodic CSI transmission that allows the terminal to periodically report channel status information between the terminal and the base station to the base station, a Type-1 configured grant PUSCH resource that allows the terminal to periodically send uplink data to the base station, and / or a periodic SRS that allows the terminal to periodically measure the uplink channel at the base station.
[0396] If the terminal and the base station are operating in FR2 or FR3 as described above, the terminal can perform uplink transmission to the base station using a directional transmit beam. The base station can receive uplink transmission (e.g., uplink data) using a receive beam corresponding to the transmit beam. For example, when the base station operates a receive beam corresponding to the transmit beam of one or more terminals, the base station may consider a first case (800) in which it operates one transmit / receive beam in a specific time resource for all frequency bands in which the terminal and the base station operate. The base station may also consider a second case (850) in which it operates one transmit / receive beam in all time resources for some frequency bands among all frequency bands in which the terminal and the base station operate, and may also consider a combination of the two methods (e.g., a combination of the first case (800) and the second case (850)).
[0397] According to one embodiment, through the first case (800), an example of a case in which a terminal and a base station operate one transmit / receive beam in a specific time resource for all frequency bands in which the terminal and the base station operate can be described. For example, a base station (e.g., gNB) can schedule a first terminal (801) (e.g., UE1), a second terminal (802) (e.g., UE2), and a third terminal (803) (e.g., UE3) in different frequency resources in a specific time resource. The base station can form a base station receiving beam (810) corresponding to the transmit beams of the three terminals, and can apply the formed transmit beams / receive beams to all frequency resources of the corresponding time resource, thereby receiving quasi-static uplink transmissions of the three terminals. For example, a base station (e.g., gNB) may schedule a fourth terminal (804) (e.g., UE4), a fifth terminal (805) (e.g., UE5), and a sixth terminal (806) (e.g., UE6) on different frequency resources at another specific time resource, and may form a base station receiving beam (811) corresponding to the transmitting beams of the three terminals, and may apply the formed transmitting beams / receiving beams to all frequency resources of the time resource, thereby enabling the base station to receive quasi-static uplink transmissions of the three terminals. For example, the base station may schedule the 7th terminal (807) (e.g., UE7), the 8th terminal (808) (e.g., UE8), and the 9th terminal (809) (e.g., UE9) on different frequency resources at another specific time resource, and form a base station reception beam (812) corresponding to the transmission beams of the three terminals, and apply the formed transmission beams / reception beams to all frequency resources of the corresponding time resource, thereby allowing the base station to receive quasi-static uplink transmissions from the three terminals. At this time, if the position changes as the 1st terminal (801) moves or if the direction in which the user holds the 1st terminal (801) changes, the transmission beam may change, and the base station may dynamically transmit a beam change instruction to the terminal to respond to this (813).Unless there is a reconfiguration of the upper layer signaling, the base station may expect to receive quasi-static uplink transmissions by scheduling the first terminal (801), the second terminal (802), and the third terminal (803) in different frequency resources within the same time resource, even though a beam change instruction has been provided for the first terminal (801). For these time and frequency resources, a dynamic beam change may be applied to the quasi-static uplink transmissions configured with the upper layer signaling. In this case, when the first terminal (801) performs a quasi-static uplink transmission in the corresponding time resource in the changed beam direction, the base station's receiving beam direction, which is aligned with the transmission beam direction of the first terminal (801), the transmission beam direction of the second terminal (802), and the transmission beam direction of the third terminal (803) before the beam change is applied, may not match the transmission beam direction of the first terminal after the beam change is applied (814). For example, the changed transmission beam direction of the first terminal (801) and the reception beam direction of the base station may not be aligned.
[0398] As another example, through the second case (850), an example is described of a case in which one transmit / receive beam is operated in all time resources for each frequency band among the entire frequency bands in which the terminal and the base station operate. For example, a base station (e.g., gNB) may form a receive beam for receiving quasi-static uplink transmissions of each terminal for each frequency band in a specific time resource. In the first frequency band, the second frequency band, and the third frequency band in which the third terminal (851), the fifth terminal (852), and the ninth terminal (853) each operate, the transmit beam used by each terminal for transmission and the corresponding receive beam of the base station are aligned with each other (aligned with Rx beam 1 (854), aligned with Rx beam 2 (855), aligned with Rx beam 3 (856)). For example, the base station may operate different transmit / receive beams for each frequency band in another specific time resource. In the first frequency band, second frequency band, and third frequency band where the first terminal (857), fourth terminal (858), and eighth terminal (859) each operate, the transmission beam used by each terminal for transmission and the corresponding reception beam of the base station are aligned with each other (aligned with Rx beam 1 (860), aligned with Rx beam 2 (861), aligned with Rx beam 3 (862)). At this time, if the position changes as the third terminal (851) moves or if the direction in which the user holds the third terminal (851) changes, the transmission beam may change, and the base station may dynamically transmit a beam change instruction to the terminal to respond to this (863). Unless there is a reset for upper layer signaling, the base station can expect to receive quasi-static uplink transmissions by scheduling the third terminal (851), the fifth terminal (852), and the ninth terminal (853) to different frequency resources in the same time resource, even though a beam change instruction for the third terminal (851) has been provided.For these time and frequency resources, dynamic beam changes may be applied to quasi-static uplink transmissions configured as upper layer signaling. In this case, if the third terminal (851) performs quasi-static uplink transmission within a portion of the frequency band allocated to the time resource in the changed beam direction, the transmission beam direction of the third terminal (851), the transmission beam direction of the fifth terminal (852), and the transmission beam direction of the ninth terminal (853) before the beam change is applied may not align with the receiving beam direction of the base station (864) in the corresponding frequency band after the beam change is applied. For example, if the transmission beam of the third terminal (851) is changed due to a change in the position of the third terminal (851), the direction of the changed transmission beam and the direction of the base station's existing receiving beam (e.g., Rx beam1) may not be aligned.
[0399] In this case, the dynamic beam change instruction from the base station to the terminal can be performed in various ways. For example, if the terminal is configured with upper-layer signaling for the integrated TCI state method, the beam change instruction can be performed based on the TCI state that can be instructed to the terminal by the base station via DCI. For example, if the terminal is not configured with upper-layer signaling for the integrated TCI state method, the beam change instruction may be performed based on spatial relation information that can be instructed to the terminal by the base station via MAC-CE.
[0400] Therefore, as described above, if a problem occurs with quasi-static uplink transmission (SR), periodic CSI (channel state information), periodic SRS, and Type-1 configured grant PUSCH, which serve an important purpose in the communication environment between a terminal and a base station, significant problems may arise in the overall communication between the terminal and the base station. For example, if a beam change for SR transmission is performed but the base station fails to properly receive the changed transmission beam due to the situation described above, the terminal may find it difficult to transmit uplink data.
[0401] To resolve this situation, the terminal may receive not only a beam change instruction from the base station, but also additional instructions regarding the resources used by the base station's receiving beam corresponding to the changed beam. Regarding this instruction method, the terminal and the base station may consider a combination of at least one of the following items.
[0402] [Method 1-1]
[0403] A terminal may receive instructions from a base station for a beam change instruction, in addition to at least one of the following combined resources, and may apply said instructions to quasi-static uplink transmission. For example, the terminal may receive a change request (or instruction request) for at least one of time resource-related information, frequency resource-related information, or code-related information along with a beam change instruction.
[0404] - Information regarding time resources
[0405] ■ The terminal may receive information related to time resources as additional information, and, for example, at least one combination of a slot or sub-slot offset, a symbol offset, a quasi-static uplink channel and a signal period and a slot offset may be indicated to the terminal.
[0406] - Information related to frequency resources
[0407] ■ The terminal may receive frequency resource-related information as additional information, and, for example, at least one combination of an RBG (resource block group) offset, an RB (resource block) offset, an RE (resource element) offset, a starting RB position and a number of consecutive RBs, and a comb offset value may be instructed to the terminal.
[0408] - Code-related information
[0409] ■ The terminal may receive code-related information as additional information, and, for example, at least one combination of cyclic shift, sequence ID, and sequence initialization may be instructed to the terminal.
[0410] Regarding the additional resource instructions described above, the terminal may determine whether to apply these instructions to some or all of the quasi-static uplink transmissions configured for the terminal. For example, the terminal may apply the instructions to at least one combination of upper layer signaling, MAC signaling, and L1 (layer 1) signaling from the base station, or to a fixedly defined specification.
[0411] If one or more quasi-static uplink transmission methods for the same purpose are configured for the terminal regarding the additional resource instructions described above, the terminal may apply the additional resource instructions described above to all quasi-static uplink transmission methods for the same purpose, apply them to the first transmission method among one or more quasi-static uplink transmission methods for the same purpose, receive additional instructions for one or more specific transmission methods among one or more quasi-static uplink transmission methods for the same purpose and apply them only to said one or more specific transmission methods, or receive individual instructions and apply them for each configuration. For example, if N (>1) SR configurations are provided to the terminal (e.g., multiple SchedulingRequestIds are configured for the terminal), when the terminal receives additional instructions related to time resources, the terminal may be expected to apply the additional instructions related to time resources only to the SR configuration corresponding to the smallest value among the SchedulingRequestIds configured for the terminal. As another example, if N (>1) SR settings are provided to a terminal (e.g., multiple SchedulingRequestIds are set to the terminal), when the terminal receives additional instructions regarding time resources, the terminal can expect to receive additional instructions regarding time resources equal to the number of SchedulingRequestIds set to the terminal. If 2 SchedulingRequestIds are set to the terminal and slot offsets are specified as additional instructions regarding time resources, the terminal can expect 2 slot offsets to be specified, equal to the number of SchedulingRequestIds. In this case, these 2 specified slot offsets can be applied sequentially, starting from the lowest SchedulingRequestId.In other words, the first slot offset can be applied to the SR configuration with the lowest SchedulingRequestId, and the second slot offset can be applied to the SR configuration with the next lowest SchedulingRequestId. (As another example, the two slot offsets can be applied sequentially starting from the highest scheuling requestid. That is, the first slot offset can be applied to the SR configuration with the highest SR ID, and the second slot offset can be applied to the SR configuration with the next lowest SR ID.)
[0412] Regarding the additional resource instructions described above, such instructions may be included within a beam change instruction or may be notified to the terminal individually. If such instructions are included within a beam change instruction, the terminal may expect such information to be included within a TCI state or spatial relation information. If notified individually, the terminal may expect such information to be notified from the base station according to a combination of at least one of upper layer signaling, MAC signaling, and L1 signaling. If such instructions are included within a beam change instruction, the terminal may expect that at least one value of the time, frequency, or code resources described above be set in the upper layer signaling within the beam change instruction signaling (e.g., TCI state or spatial relation information). Alternatively, the terminal may receive at least one combination of the time, frequency, and code resources described above as a single upper-layer signaling and may be assigned an ID for each combination, and may receive such combinations in the form of multiple lists, and may expect each combination and its corresponding ID to be connected to the beam change instruction signaling described above. In this case, the terminal may receive a configuration from the base station via the upper-layer signaling such that ID information corresponding to the combination of additional resources described above is included within the beam change instruction signaling described above. As another example, the terminal may receive a configuration via additional upper-layer signaling regarding the connection relationship between the upper-layer signaling related to the beam change instruction signaling and the ID information corresponding to the combination of additional resources described above within the bandwidth portion (e.g., BWP configuration information) or the serving cell configuration (e.g., serving cell configuration information).For example, the terminal can receive configuration information from the base station regarding the correspondence relationship between information for beam changing and ID information corresponding to a resource combination (e.g., a combination of time, frequency, and code resources).
[0413] The additional resource indication described above may be applied to the terminal by updating the upper layer signaling value configured for each quasi-static uplink transmission method, or the additional resource indication described above may be applied to the terminal as an additional offset to the upper layer signaling value configured for each quasi-static uplink transmission method. For example, if the method involves updating the upper layer signaling value, when the terminal applies the indication to the SR, it may apply the indicated value instead of the periodicityAndOffset value within the schedulingRequestResourceConfig, which is the upper layer signaling. For example, when setting the additional resource indication to the terminal, there may be a method of updating the value by setting the value of the configuration information (e.g., resource value) that needs to be changed to the terminal. In this case, the base station may transmit the first resource value to the terminal for changing the resources, and the terminal may perform signal transmission using the received first resource value. For example, the method described above may be referenced as a method of setting the full configuration.
[0414] As another example, when setting resource instructions to a terminal, the base station may set only information regarding the difference (e.g., delta value) compared to the value of the setting information previously set to the terminal (e.g., second resource value). In this case, the terminal can identify a new resource value (e.g., first resource value) based on the information regarding the difference (e.g., delta value) from the previously set resource value (e.g., second resource value) and perform signal transmission using the new resource value (e.g., first resource value).
[0415] [Method 1-2]
[0416] In addition to a beam change instruction from the base station, the terminal may receive at least one of the following combined configuration information instructions (or configurations), and may apply the instructions (or configurations) to quasi-static uplink transmission. That is, by pre-connecting quasi-static uplink transmission resources corresponding to each transmit beam / receive beam that can be dynamically indicated, the terminal may receive instructions (or configurations) for quasi-static uplink transmission resources corresponding to the changed beam when the beam changes, apply the changed beam to the transmission resources, and transmit to the base station. At this time, the terminal may receive instructions (or configurations) for at least one of the following combined transmission resources, and may apply the instructions (or configurations, configurations) to quasi-static uplink transmission.
[0417] If a terminal receives one SR configuration information from a base station and performs SR transmission quasi-statically based on the provided configuration information, the terminal may receive an additional SR configuration ID and / or PUCCH resource ID in addition to the beam change instruction, and may replace the one SR configuration and / or PUCCH resource ID currently in use.
[0418] If a terminal receives multiple SR settings (or multiple SR setting information) from a base station and performs SR transmission quasi-statically based on the provided setting information, the terminal may receive (or be configured with) multiple SR setting IDs and / or PUCCH resource IDs in addition to beam change instructions, and the terminal may replace each of the multiple SR settings and / or PUCCH resource IDs currently in use. For example, if a terminal performs SR transmission quasi-statically based on two SR settings based on two SR setting information, the terminal may receive two additional SR setting IDs and / or PUCCH resource IDs in addition to beam change instructions, and may replace each of the two SR settings and / or PUCCH resource IDs currently in use. At this time, if the indicated (or set) SR setting ID and / or PUCCH resource ID is the same as the previously set information or the indicated information, the terminal may consider that the beam change was intended to be applied to the same SR setting ID and / or PUCCH resource ID, even if the base station instructed a beam change. For example, the terminal may identify that the change was made from the first beam to the second beam, but the same SR setting ID and / or PUCCH resource ID as before is applied.
[0419] Similar to the case of the SR described above, the terminal may replace the previously used configuration information by additionally receiving (or being configured with) CSI report configuration information corresponding to the periodic CSI report, PUCCH, PUSCH resource configuration information, Type-1 configured grant PUSCH configuration information, and / or SRS resource set or SRS resource configuration information.
[0420] [Method 1-3]
[0421] The terminal may receive upper layer signaling (or configuration information) from the base station as additional configuration information, which means that dynamic beam change instructions from the base station are not applied to each of the quasi-static uplink transmission mode and / or quasi-static downlink reception mode. For example, the terminal may receive upper layer signaling (e.g., configuration information) for each SR transmission setting, for each PUCCH resource connected to the SR setting, for each Type-1 configured grant setting, for each periodic SRS setting, for each periodic CSI report setting, for each search space setting, and / or for each CORESET (control resource set) setting, and the dynamic beam change instructions received by the terminal may not be applied to the quasi-static uplink transmission mode and / or quasi-static downlink reception mode indicated by the configuration information.
[0422] The terminal may receive configuration information (or an indicator) from the base station indicating that dynamic beam change instructions are not applied to any of the specified transmission and / or reception methods, and may not apply beam change instructions to the transmission and / or reception methods indicated by the configuration information (or an indicator).
[0423] If new upper layer signaling (e.g., configuration information) is configured for the terminal, dynamically directed beam change instructions may not be applied to the corresponding quasi-static uplink transmission configuration. If new upper layer signaling (e.g., configuration information) is not configured for the terminal, the terminal may apply dynamically directed beam change instructions to the corresponding quasi-static uplink transmission configuration. The operating principle of the corresponding upper layer signaling may be applied in the opposite manner to that described above (i.e., dynamic beam change instructions may be applied when the upper layer signaling is configured, and dynamic beam change instructions may not be applied when the upper layer signaling is not configured).
[0424] The terminal can avoid cases where the transmit and receive beams that the base station can implementally and quasi-statically use for time resources, frequency resources, and / or code resources quasi-statically configured to the terminal do not match dynamically changing beam change instructions that the terminal can receive. For example, cases where the transmit / receive beams used quasi-statically do not match beam change instructions can be prevented.
[0425] The terminal may receive upper layer signaling (e.g., configuration information) from the base station for at least one combination of the above-described [Method 1-1], [Method 1-2], or [Method 1-3]. For example, the terminal may receive upper layer signaling (e.g., configuration information) per serving cell, per bandwidth portion, per SR configuration, per periodic PUCCH resource, per Type-1 configured grant PUCCH resource, per CSI report configuration, per periodic SRS resource or / and per periodic SRS resource set configuration.
[0426] For example, the terminal can perform the operation [Method 1-1] described above by receiving upper layer signaling (e.g., configuration information) from the base station and according to the configuration level of the upper layer signaling (e.g., per serving cell, per bandwidth portion, per SR configuration, per periodic PUCCH resource, per Type-1 configured grant PUSCH resource, per CSI report configuration, per periodic SRS resource or / and per periodic SRS resource set configuration).
[0427] For example, the terminal can perform the operation of [Method 1-2] described above by receiving upper layer signaling from the base station and according to the setting level of the upper layer signaling (e.g., per serving cell, per bandwidth portion, per SR setting, per periodic PUCCH resource, per Type-1 configured grant PUCCH resource, per CSI report setting, per periodic SRS resource or / and per periodic SRS resource set setting).
[0428] For example, the terminal can perform the operation of [Method 1-3] above by receiving upper layer signaling from the base station and according to the setting level of the upper layer signaling (e.g., per serving cell, per bandwidth portion, per SR setting, per periodic PUCCH resource, per Type-1 configured grant PUSCH resource, per CSI report setting, per periodic SRS resource or / and per periodic SRS resource set setting).
[0429] For example, a terminal may perform one of [Method 1-1] and [Method 1-3] depending on the setting level of the upper layer signaling (e.g., per serving cell, per bandwidth portion, per SR setting, per periodic PUCCH resource, per Type-1 configured grant PUCCH resource, per CSI report setting, per periodic SRS resource or / and per periodic SRS resource set setting) by receiving upper layer signaling from a base station. For example, the base station may set one value of [Method 1-1] support or [Method 1-3] support to the terminal through the upper layer signaling (e.g., setting information). For example, if the upper layer signaling (e.g., setting information regarding support) is not set, the terminal may identify that it does not support both [Method 1-1] and [Method 1-3].
[0430] For example, a value set for the terminal may be a value for indicating whether [Method 1-1] or [Method 1-3] is supported. For example, a first value may be set for the terminal, and the first value may indicate which method is supported among [Method 1-1] or [Method 1-3]. In this case, if the first value is “01”, Method [1-1] may be supported, and if the first value is “10”, Method 1-3 may be supported. As another example, a first value indicating whether [Method 1-1] is supported and a second value indicating whether [Method 1-3] is supported may be set for the terminal, and if the first value is “1”, it may indicate that [Method 1-1] is supported, and if the first value is “0”, it may indicate that [Method 1-1] is not supported. If the second value is “1”, it may be indicated that [Method 1-3] is supported, and if the second value is “0”, it may be indicated that [Method 1-3] is not supported. As another example, whether [Method 1-1] or [Method 1-3] is supported may be indicated to the terminal in the form of a bitmap.
[0431] For example, the terminal may perform one of the operations described in [Method 1-2] and [Method 1-3] above by receiving upper layer signaling from the base station and depending on the setting level of the upper layer signaling (e.g., per serving cell, per bandwidth portion, per SR setting, per periodic PUCCH resource, per Type-1 configured grant PUCCH resource, per CSI report setting, per periodic SRS resource or / and per periodic SRS resource set setting). For example, the base station may set one value of [Method 1-2] support or [Method 1-3] support to the terminal through the upper layer signaling (e.g., setting information regarding support status). For example, if the upper layer signaling (e.g., setting information regarding support status) is not set, the terminal may identify that neither [Method 1-2] nor [Method 1-3] is supported. For example, the value set to the terminal may be a value indicating whether [Method 1-2] or [Method 1-3] is supported.
[0432] For example, the terminal may perform one of the above-described [Method 1-1], [Method 1-2], and [Method 1-3] by receiving upper layer signaling from the base station and, depending on the setting level of the upper layer signaling (e.g., per serving cell, per bandwidth portion, per SR setting, per periodic PUCCH resource, per Type-1 configured grant PUCCH resource, per CSI report setting, per periodic SRS resource or / and per periodic SRS resource set setting). For example, the base station may set one of the values [Method 1-1] support, [Method 1-2] support, or [Method 1-3] support to the terminal through the upper layer signaling (e.g., setting information regarding support status). For example, if the corresponding upper layer signaling is not set, the terminal may identify that [Method 1-1], [Method 1-2], and [Method 1-3] are not supported. For example, a value set to the terminal may be a value for indicating whether [Method 1-1], [Method 1-2], and [Method 1-3] are supported.
[0433] For example, the above-described [Method 1-1], [Method 1-2], or [Method 1-3] may be applied when the terminal operates as an integrated TCI state framework and is instructed to one TCI state. For example, the above-described [Method 1-1], [Method 1-2], or [Method 1-3] may be applied when the terminal operates as a spatial relation information framework and is instructed to activate and / or instruct one spatial relation information.
[0434] The above-described [Method 1-1], [Method 1-2], and / or [Method 1-3] may apply when the terminal is instructed to one or two TCI states when operating with an integrated TCI state framework. If the terminal is instructed to two TCI states, the terminal may be instructed to set the upper layer signaling (e.g., configuration information associated with the TCI state) for each upper layer signaling configuration level among the two instructed TCI states (e.g., SR configuration, periodic PUCCH resource, Type-1 configured grant PUSCH resource, CSI report configuration, periodic SRS resource or / and periodic SRS resource set configuration) to determine which TCI state to apply. (For example, if the upper layer signaling setting candidate values are first, second, and both, and first is set, the terminal applies the first of the two indicated TCI states; if second is set, it applies the second of the two indicated TCI states; and if both is set, it may apply both indicated TCI states.) If the aforementioned additional resource instructions exist within a TCI state, they may be applied. In this case, if the terminal receives the setting of both via the upper layer signaling regarding which TCI state to apply, it can expect that the additional resource instruction information is identical if the aforementioned additional resource instructions exist within the two TCI states. (For example, containing substantially identical additional resource instruction information within the two TCI states.)
[0435] As another example, the terminal may receive configuration information from the base station regarding whether to apply a TCI state, and the configuration information may include information indicating that both TCI states should be applied (e.g., “both”). In this case, the terminal can expect that if additional resource instructions (e.g., instructions to change code, frequency, or time resources) exist, the resource instructions will be applied equally to each of the two TCI states.
[0436] The above-described [Method 1-1], [Method 1-2], and / or [Method 1-3] may be applied when the terminal operates as a spatial relation information framework and one or two spatial relation informations are activated and / or indicated. If the terminal is activated and / or indicated with two spatial relation informations, the terminal can expect that the additional resource indication information described above will be the same if the additional resource indication exists within the two spatial relation informations.
[0437] The above-described [Method 1-1] to [Method 1-3] can be similarly applied by the terminal not only to quasi-static uplink transmission methods, but also to quasi-static downlink reception methods such as search space and CORESET, which are downlink control channel related configuration information, and periodic channel state information reference signals (e.g., periodic CSI-RS).
[0438] As described above, if the terminal receives instructions regarding quasi-static uplink transmission resources in addition to beam change instructions, the terminal may determine when to apply said instructions by a combination of at least one of the following items.
[0439] [Method 2-1]
[0440] When a terminal is instructed to use a beam change method based on MAC-CE spatial relation information update method when receiving additional instructions for quasi-static uplink transmission resources, the terminal may use the existing MAC-CE application time as the point in time for applying the additional quasi-static uplink transmission resources, or the terminal may define and use an additional time to the existing MAC-CE application time through additional upper layer signaling (e.g., configuration information).
[0441] - If the terminal uses the existing MAC-CE application time, the terminal may transmit a PUCCH containing HARQ (hybrid automatic repeat request)-ACK (acknowledgement) information regarding the MAC-CE to the base station in the n-th slot after receiving the MAC-CE. In this case, the terminal n + Starting from the first slot after the point in time, beam changes and additional quasi-static uplink transmission resources become available. At this time, can be referenced as the number of slots per subframe according to the subcarrier spacing, and the subcarrier spacing is 15*2 μ 2 at kHz μ It can be defined as. For example, in the case of a 60 kHz and 120 kHz subcarrier interval, The number of OFDM symbols corresponding to each can be 168 and 336, respectively.
[0442] - If the terminal defines an additional time for the existing MAC-CE application time, the terminal may transmit a PUCCH containing HARQ-ACK information for the MAC-CE to the base station in the n-th slot after receiving the MAC-CE. In this case, if the base station has set a higher-layer signaling (e.g., configuration information related to the MAC-CE application time) that signifies defining an additional time for the MAC-CE application time, the terminal n + Starting from the first slot after the point in time, beam changes and additional quasi-static uplink transmission resources become available. At this time, can be referenced as the number of slots per subframe according to the subcarrier spacing, and the subcarrier spacing is 15*2 μ 2 at kHz μ It can be defined as a number. For example, μ can be referred to as the subcarrier interval for PUCCH transmission. For example, μ s may be referenced as a subcarrier interval for beam changes and additionally indicated quasi-static uplink transmission resources. The terminal may report to the base station, via terminal capability, a minimum value of additional processing time (or, delay time) per subcarrier interval. In this case, the terminal may report only the additional processing time (or, delay time) corresponding to the 60 kHz subcarrier interval among the FR2 and FR3 band subcarrier intervals, or may report additional processing time (or, delay time) values for each subcarrier interval for at least one combination of 60 kHz, 120 kHz, 480 kHz, and 960 kHz. Upon receiving terminal capability from the terminal, the base station, based on the reported minimum value, k via upper-layer signaling ss You can receive the setting. For example, k ss can be referred to as additional processing time (or delay time). In this case, k ss can correspond to the value at which the base station is set to upper-layer signaling from the minimum value of the additional processing time (or delay time) reported by the aforementioned terminal capability, in terms of the number of slots, the number of symbols, or absolute time units. As another example, simply k ssmay correspond to N additional slots, and N may be a natural number greater than or equal to 1. If there are multiple quasi-static uplink transmission resources additionally indicated for beam changing, the terminal may determine the final processing time (or delay time) by considering the subcarrier interval that causes the longest additional time among them (i.e., corresponding to the lowest subcarrier interval).
[0443] [Method 2-2]
[0444] When a terminal is additionally instructed on a quasi-static uplink transmission resource and uses a DCI-based TCI state instruction method based on an integrated TCI state framework as a beam change method, the terminal may apply the beam application time for the existing integrated TCI state, apply a new beam application time considering additional processing time, or operate according to conditions.
[0445] - If the terminal applies a beam application time for an existing integrated TCI state, the terminal may apply a beam change and additional quasi-static uplink transmission resources from the first slot appearing after the number of symbols corresponding to the beam application time, starting from a PUCCH transmission containing HARQ-ACK information corresponding to a DCI containing an instruction to change the integrated TCI state. In this case, the terminal may report information regarding the minimum beam application time to the base station as terminal capability (or capability information), and the base station may set the beam application time value assumed by the terminal as beamAppTime through upper layer signaling based on the reported terminal capability.
[0446] - If the terminal defines an additional time for the beam application time of the existing integrated TCI state, the terminal may additionally report a longer minimum beam application time value to the base station through the new terminal capability. Subsequently, if the terminal receives specific upper layer signaling (e.g., configuration information, RRC message) from the base station, the terminal may use the longer beam application time value defined through the new terminal capability to direct beam changes and apply additional quasi-static uplink transport resources. If the terminal does not receive specific upper layer signaling from the base station, the terminal can expect the base station to set the upper layer signaling, beamAppTime, based on the minimum beam application time reported through the existing terminal capability. In this case, the terminal may use the set beamAppTime value to direct beam changes and apply additional quasi-static uplink transport resources. At this time, the terminal can expect the value of the minimum beam application time reported through the existing terminal capability to be shorter than or equal to the minimum beam application time reported through the new terminal capability.
[0447] - If the terminal defines additional time for the beam application time of the existing integrated TCI state, the terminal may report this additional application time to the base station through the new terminal capability. Subsequently, if the terminal receives specific higher-layer signaling (e.g., configuration information, RRC message) from the base station, the terminal can expect the base station to set the higher-layer signaling, beamAppTime, based on the sum of the additional beam application time reported through the new terminal capability and the minimum beam application time reported through the existing terminal capability. In this case, the terminal may consider (or identify) the beamAppTime finally set by the base station as the final higher-layer signaling as the final beam application time, using the sum of the additional beam application time reported through the new terminal capability and the minimum beam application time reported through the existing terminal capability. (For example, the minimum beam application time is a minimum value reported by the terminal as a terminal capability, and the base station can set the actual beam application time based on this minimum value through upper-layer signaling (e.g., RRC message).) Alternatively, if the terminal receives specific upper-layer signaling (e.g., configuration information, RRC message) from the base station, the terminal can expect the base station to set the upper-layer signaling, beamAppTime, based on the minimum beam application time reported as a terminal capability.In this case, in addition to the configured beamAppTime value, an additional beam application time (e.g., which can be named addBeamAppTime) that the terminal can report through a new terminal capability may be added, and the time beamAppTime + addBeamAppTime may be considered (or identified) as the final beam application time. In this case, after receiving a DCI that changes the integrated TCI state, the terminal may apply the modified integrated TCI state starting from the first slot appearing after the beamAppTime + addBeamAppTime symbol, starting from the end of the OFDM symbol for the PUCCH transmission containing HARQ-ACK information corresponding to the DCI. If the terminal has not received a specific upper layer signaling from the base station, the terminal may expect the base station to configure the upper layer signaling beamAppTime based on the minimum beam application time reported through the existing terminal capability. In this case, the terminal may use the configured beamAppTime value to direct the beam change and apply additional quasi-static uplink transmission resources.
[0448] - If the terminal defines additional time for the beam application time for the existing integrated TCI state, the terminal may decide whether to report additional application time through the new terminal capability based on the value of the minimum beam application time reported through the existing terminal capability. If the terminal reports a minimum beam application time greater than a certain value through the existing terminal capability, the terminal and the base station may expect to reuse the minimum beam application time reported through the existing terminal capability report for beam change instructions and the application of additional quasi-static uplink transmission resources. In this case, the terminal and the base station may expect that no information regarding additional minimum beam application time is reported through the new terminal capability. If the terminal reports a minimum beam application time less than a certain value through the existing terminal capability, the terminal may report a value greater than the beam application time reported through the existing terminal capability and apply it through the new terminal capability for beam change instructions and the application of additional quasi-static uplink transmission resources. For example, the terminal can report a minimum beam application time value to the base station at subcarrier intervals using existing terminal capabilities (e.g., capability information), using one of the OFDM symbol count units {1, 2, 4, 7, 14, 28, 42, 56, 70, 84, 98, 112, 224, 336}.For example, the terminal can report only for FR2 for values {84, 98, 112, 224, 336} (for example, the terminal can report 14 for 15 kHz, 28 for 30 kHz, 84 for a 60 kHz subcarrier interval, and 224 for a 120 kHz subcarrier interval). In this case, the terminal can determine one of the above-mentioned values {1, 2, 4, 7, 14, 28, 42, 56, 70, 84, 98, 112, 224, 336} as a reference value. If the determined reference value is n and the terminal reports a value less than or equal to n through existing terminal capabilities, the terminal can expect information related to the minimum beam application time to be reported through new terminal capabilities. Additionally, the value of the minimum beam application time reported through the new terminal capability can be expected to be greater than the value reported through the existing terminal capability (less than or equal to n). Otherwise (if the terminal reports a value greater than the reference value n), the terminal can expect that information regarding the minimum beam application time will not be reported through the new terminal capability. As another example, if the terminal reports a value less than n through the existing terminal capability, the terminal may or may not report information regarding the minimum beam application time through the new terminal capability. If the terminal reports information regarding the minimum beam application time through the new terminal capability, the reported value can be expected to be greater than or equal to the value reported through the existing terminal capability (less than or equal to n).If the terminal does not report information regarding the minimum beam application time through the new terminal capability, the base station may implicitly identify that the terminal has reported a value named n to the base station, even if the terminal has reported at least one combination of [Method 1-1], [Method 1-2], [Method 1-3], [Method 2-1], or [Method 2-2] without including information regarding the minimum beam application time within the new terminal capability. If the base station sets up upper layer signaling (e.g., configuration information) related to at least one combination of [Method 1-1], [Method 1-2], [Method 1-3], [Method 2-1], or [Method 2-2] to the terminal, and the terminal reports the minimum beam application time based on at least one combination of the existing terminal capability and the new terminal capability through the above method, the base station may set up beamAppTime, an upper layer signaling, to the terminal based on the larger value among the reported values. Otherwise (if the base station does not set the upper layer signaling (e.g., configuration information) associated with at least one combination of [Method 1-1], [Method 1-2], [Method 1-3], [Method 2-1], or [Method 2-2] to the terminal), the base station may set the upper layer signaling, beamAppTime, to the terminal based on the value reported by the terminal with existing terminal capabilities. In this case, the value of n may be one of {1, 2, 4, 7, 14, 28, 42, 56, 70, 84, 98, 112, 224, 336}, and the value of n may be a value such as 168, considering the number of OFDM symbols within 3 ms at a 60 kHz subcarrier interval.
[0449] The terminal may receive a list of one or more serving cells via upper-layer signaling (e.g., RRC, MAC CE) (e.g., if the terminal operates with the integrated TCI state framework, it may receive simultaneousU-TCI-UpdateList1-r17, simultaneousU-TCI-UpdateList2-r17, simultaneousU-TCI-UpdateList3-r17, or / and simultaneousU-TCI-UpdateList4-r17 included in the upper-layer signaling CellGroupConfig, or if the terminal operates with the spatial relation information framework, it may receive simultaneousTCI-UpdateList1-r16 or / and simultaneousTCI-UpdateList2-r16. In such cases, even if the terminal receives a beam change instruction for a specific serving cell within the serving cell list, it may apply the same beam change instruction to all serving cells within the serving cell list.
[0450] To apply at least one combination of the above-described [Method 1-1], [Method 1-2], [Method 1-3], [Method 2-1], or [Method 2-2], the terminal may receive upper layer signaling (e.g., configuration information) from the base station. In this case, when the terminal dynamically receives a beam change instruction, it may change the transmission beam for the quasi-static uplink transmission, as well as change the time, frequency, and / or code resources, by receiving additional information for the quasi-static uplink transmission, and transmit uplink data to the base station based on the changed beam. At this time, upper layer signaling (e.g., configuration information) can be configured from the base station to the terminal by cell group, by serving cell, by bandwidth portion, or by applicable quasi-static uplink channel (e.g., periodic PUCCH, Type-1 configured grant PUSCH resource, scheduling request setting, CSI report setting), or / and by quasi-static uplink signal (periodic SRS resource set or periodic SRS resource, or SRS config).
[0451] For one or more of the multiple serving cells in the serving cell list, the terminal may have received upper layer signaling (e.g., configuration information) that can apply at least one combination of [Method 1-1], [Method 1-2], [Method 1-3], [Method 2-1], or [Method 2-2] described above, and may not have received upper layer signaling (e.g., configuration information) for the remaining one or more serving cells. In this case, the terminal may apply at least one combination of [Method 1-1], [Method 1-2], [Method 1-3], [Method 2-1], or [Method 2-2] described above only to the serving cell that received the upper layer signaling, and may ignore resource change instructions and apply only beam change instructions to the remaining serving cells. At this time, upper layer signaling may be configured from the base station to the terminal by cell group, by serving cell, by bandwidth portion, or by applicable quasi-static uplink channel (e.g., periodic PUCCH, Type-1 configured grant PUSCH resource, scheduling request setting, CSI report setting), or / and by quasi-static uplink signal (periodic SRS resource set or periodic SRS resource, or SRS config). Additionally, the terminal may have received upper layer signaling configured to apply at least one combination of [Method 1-1], [Method 1-2], [Method 1-3], [Method 2-1], or [Method 2-2] described above for some serving cells within a specific serving cell list, and may not have received upper layer signaling configured for one or more of the remaining serving cells.In this case, the terminal may assume the same beam application time for one or more serving cells (first serving cell group) that have received upper layer signaling. In this case, the beam application time may be determined based on the smallest subcarrier interval among the one or more serving cells. The terminal may assume the same beam application time for one or more serving cells (second serving cell group) that have not received upper layer signaling. In this case, the beam application time may be determined based on the smallest subcarrier interval among the one or more serving cells, and the terminal may expect that the first serving cell group and the second serving cell group will have the same or different beam application times.
[0452] In another way, if a terminal receives an upper layer signaling (e.g., configuration information) capable of applying at least one combination of [Method 1-1], [Method 1-2], [Method 1-3], [Method 2-1], or [Method 2-2] described above, per specific serving cell, per specific bandwidth portion within a serving cell, or per applicable quasi-static uplink channel (e.g., periodic PUCCH, Type-1 configured grant PUSCH resource, scheduling request setting, CSI report setting), or / and per quasi-static uplink signal (periodic SRS resource set or periodic SRS resource, or SRS config), the terminal may receive an upper layer signaling (e.g., configuration information) from a base station such that the serving cell where the configuration exists is not included in the serving cell list of the upper layer signaling.
[0453] The terminal may be notified or configured by the base station through at least one combination of upper layer signaling, MAC-CE signaling, and L1 signaling for at least one combination of [Method 1-1], [Method 1-2], and [Method 1-3], [Method 2-1], and [Method 2-2] described above (dynamic). The terminal may expect that at least one combination of [Method 1-1], [Method 1-2], and [Method 1-3], [Method 2-1], and [Method 2-2] is fixedly defined in the specification. Additionally, if the terminal is notified (or configured) of a specific combination of one or more methods through at least one combination of upper layer signaling, MAC-CE signaling, and L1 signaling from the base station, it may mean that the terminal is unable to support one or more other specific combinations of methods. For example, the terminal may expect that the above [Method 1-1] and / or [Method 2-2] are fixedly defined in the specification regarding the method for setting up the upper layer signaling related to uplink transmission power (e.g., setting information related to uplink transmission power). As another example, the terminal may be notified (or set) by the base station regarding the above [Method 1-2] and / or [Method 2-1] through a combination of at least one of upper layer signaling, MAC-CE signaling, and L1 signaling, and in such case, the terminal may consider (or identify) that it has been notified (or set) by the base station that the above [Method 1-1] and / or [Method 2-2] are not supported.
[0454] The terminal may report to the base station, as terminal capability (or capability information), whether it is possible to support at least one combination of [Method 1-1], [Method 1-2], and [Method 1-3], [Method 2-1], and [Method 2-2] described above. In this case, if the terminal reports to the base station as terminal capability that a combination of one or more specific methods is possible, it may be considered (or identified) that the terminal has reported that it is not possible to support one or more other combinations of specific methods. For example, the terminal may report to the base station whether it is possible to support [Method 1-1] and / or [Method 2-2]. As another example, the terminal may report to the base station that it is possible to support [Method 1-2] and / or [Method 2-1], and such terminal capability reporting may mean that the terminal is not possible to support [Method 1-1] and / or [Method 2-2].
[0455] A terminal may receive one or more pieces of information related to an indicator for an uplink and / or downlink transmit / receive beam through upper layer signaling (e.g., RRC signaling) from a base station. For example, as an indicator for an uplink and / or downlink transmit / receive beam (which may be referred to as “beam indicator”), the terminal may receive one or more TCI states, one or more TCI-UL-states, and / or one or more spatial relation information through upper layer signaling for each downlink bandwidth portion, each uplink bandwidth portion, each carrier, and / or each serving cell.
[0456] A terminal may receive at least one combination of time resources, frequency resources, or code resources configured per uplink transmission channel that can be transmitted quasi-statically from a base station via upper layer signaling. For example, such a combination of resources may be referred to as “uplink transmission radio resources.” For example, the terminal may expect that the “uplink transmission radio resources” include time resource information such as slot offset, slot period, and / or symbol offset. As another example, the terminal may expect that the “uplink transmission radio resources” include time resource information such as slot offset. As yet another example, the terminal may expect that the “uplink transmission radio resources” include information such as slot offset and / or frequency resource offset.
[0457] For each quasi-static uplink transmission channel, the terminal may expect to be configured with one or more “uplink transmission radio resources.” For example, the quasi-static uplink transmission channel described above may include at least one combination of an SR configuration, a CSI report configuration, a 1-stage PUCCH configuration used for reporting transmit / receive beam information originating from the terminal, and / or a Type-1 configured grant PUSCH resource configuration.
[0458] The terminal can receive upper layer signaling (e.g., configuration information) from the base station indicating that each “uplink transmission wireless resource” is connected to one or more of the above one or more “beam indicator” information.
[0459] - For example, the terminal may receive radio resource information that the terminal will primarily use for transmitting a scheduling request from the base station via upper layer signaling within the scheduling request configuration. For example, such upper layer signaling (e.g., configuration information) may include periodicityAndOffset and / or PUCCH-ResourceId within SchedulingRequestConfig or SchedulingRequestResourceConfig. Additionally, the terminal may receive one or more “uplink transmission radio resources” and “beam indicator” information corresponding to each “uplink transmission radio resource.” For example, the terminal may receive upper layer signaling (e.g., configuration information) indicating (or indicating) the connection relationship between the first “uplink transmission radio resource” and the first “beam indicator” information, and upper layer signaling (e.g., configuration information) indicating (or indicating) the connection relationship between the second “uplink transmission radio resource” and the second “beam indicator” information. Subsequently, if the terminal receives the first “beam indicator” from the base station, the terminal may perform the transmission of the scheduling request based on the first “uplink transmission radio resource” connected to the first “beam indicator” when transmitting the scheduling request. For example, if the first “uplink transmission radio resource” includes slot offset and / or slot period information, the terminal may apply the first “uplink transmission radio resource” connected to the first “beam indicator” instead of the radio resource information to be used as the basis when transmitting the scheduling request via upper layer signaling from the base station.
[0460] - As another example, the terminal may receive radio resource information that the terminal will primarily use for transmitting the CSI report from the base station via upper layer signaling within the CSI report-related settings. For example, the upper layer signaling described above (e.g., setting information) may include ltm-CSI-ReportConfigToAddModList, CSI-MeasConfig, or CSI-ReportConfig. Additionally, this upper layer signaling may be configured to the terminal from the base station via CSI-ReportPeriodicityAndOffset and / or PUCCH-CSI-Resource within the periodic within the reportConfigType within CSI-ReportConfig. (For example, CSI-ReportConfig includes information about reportConfigType, the information about reportConfigType includes information about periodic, and the information about periodic may include CSI-ReportPeriodicityAndOffset and / or PUCCH-CSI-Resource. In this case, the radio resource information to be used by default for CSI report transmission may be set to the terminal via CSI-ReportPeriodicityAndOffset and / or PUCCH-CSI-Resource.) As another example, such upper-layer signaling (e.g., configuration information) may be set to the terminal by the base station via CSI-ReportPeriodicityAndOffset and / or PUCCH-CSI-Resource included in semiPersistentOnPUCCH, which is included in reportConfigType within CSI-ReportConfig.As another example, such upper-layer signaling (e.g., configuration information) may be configured to the terminal by the base station through reportSlotConfig and / or reportSlotOffsetList included in semiPersistentOnPUSCH, which is included in reportConfigType within CSI-ReportConfig. As another example, such upper-layer signaling (e.g., configuration information) may be configured to the terminal by the base station through reportSlotOffsetList included in aperiodic, which is included in reportConfigType within CSI-ReportConfig. Additionally, the terminal may be configured with one or more “uplink transmission radio resources” and “beam indicator” information corresponding to each “uplink transmission radio resource.” For example, the terminal may receive upper-layer signaling (e.g., first information) signifying (or indicating) a connection relationship (or association relationship) between the first “uplink transmission wireless resource” and the first “beam indicator” information, and upper-layer signaling (e.g., second information) signifying a connection relationship (or association relationship) between the second “uplink transmission wireless resource” and the second “beam indicator” information. Subsequently, if the terminal receives the first “beam indicator” from the base station, the terminal may perform CSI report transmission based on the first “uplink transmission wireless resource” connected to the first “beam indicator” when transmitting a CSI report corresponding to the first beam indicator. For example, if the first “uplink transmission wireless resource” includes slot offset and / or slot period information, the terminal may apply the first “uplink transmission wireless resource” connected to the first “beam indicator” instead of the wireless resource information to be used as the basis for transmitting the corresponding CSI report via upper-layer signaling by the base station.
[0461] - As another example, the terminal may receive radio resource information from the base station to be used by default for transmitting CSI reports via upper layer signaling. For example, the radio resource information to be used by default may be included within a Type-1 configured grant related setting. Such upper layer signaling (e.g., setting information) may be included within ConfiguredGrantConfig and / or rrc-ConfiguredUplinkGrant. Additionally, the terminal may receive one or more “uplink transmission radio resources” and “beam indicator” information corresponding to each “uplink transmission radio resource.” More specifically, the terminal may receive upper layer signaling (e.g., first information) signifying (or indicating) a connection relationship (or association relationship) between the first “uplink transmission radio resource” and the first “beam indicator” information, and upper layer signaling (e.g., second information) signifying (or indicating) a connection relationship (or association relationship) between the second “uplink transmission radio resource” and the second “beam indicator” information. Subsequently, if the terminal receives a first “beam indicator” from the base station, the terminal may perform a Type-1 configured grant uplink transmission based on a first “uplink transmission radio resource” connected to the first “beam indicator” during a Type-1 configured grant uplink transmission corresponding to the first beam indicator. For example, if the first “uplink transmission radio resource” includes slot offset and / or slot period information, the terminal may apply the first “uplink transmission radio resource” connected to the first “beam indicator” instead of the radio resource information to be used as the basis for the Type-1 configured grant uplink transmission via upper layer signaling from the base station.
[0462] The terminal may or may not include an uplink setting in which the upper layer signaling setting per quasi-static uplink transmission channel described above signifies (or indicates) a connection relationship between one or more “uplink transmission wireless resources” and “beam indicators” described above. The terminal may or may not receive setting information indicating a connection relationship between wireless resources and beam indicators.
[0463] When a terminal receives a specific “beam indicator” from a base station, there may be no configuration information for the “uplink transmission radio resource” connected to the “beam indicator” received by the terminal after the application time of the configured “beam indicator.” In this case, the terminal may perform uplink transmission using the “uplink transmission radio resource” connected to the beam indicator that was used before the currently indicated beam indicator was applied, or the terminal may use the radio resource configuration information configured to be used by default for each of the aforementioned quasi-static uplink transmission channels and / or upper layer signaling.
[0464] When a terminal receives a specific “beam indicator” from a base station, configuration information for an “uplink transmission radio resource” connected to the “beam indicator” received by the terminal may exist after the application time of the received “beam indicator.” In this case, the terminal may perform uplink transmission using the “uplink transmission radio resource” connected to the currently indicated beam indicator, or the terminal may use radio resource configuration information configured to be used by default for each upper layer signaling.
[0465] When a terminal receives the aforementioned “beam indicator,” it may support the method solely through upper-layer signaling settings that represent the connection relationship between the “uplink transmission wireless resource” connected to the aforementioned “beam indicator,” without including additional information within the said “beam indicator.”
[0466] The terminal may include N pieces of “uplink transmission wireless resource” information (e.g., N may be an integer greater than or equal to 0) within the “beam indicator” described above. For each upper layer signaling setting for the quasi-static uplink transmission channel, the terminal may receive a setting through upper layer signaling regarding which of the N pieces of “uplink transmission wireless resource” information that may be included within the “beam indicator” described above will be applied.
[0467] For example, a terminal may be notified (or configured) of a “beam indicator” (N=0) that does not include “uplink transmission radio resource” information from a base station through a combination of at least one of upper layer signaling, MAC-CE signaling, or L1 signaling. In this case, when the terminal receives the “beam indicator” from the base station, the terminal may use radio resource configuration information that is configured to be used by default for each upper layer signaling for the quasi-static uplink transmission channel. For example, a radio resource configured to be used by default may be referred to by various terms such as default resource, basic resource, or configured resource. For example, the unit of a radio resource may vary. (e.g., RB (resource block), RE (resource element), subcarrier, RBG (resource block group)) As another example, the terminal may be notified (or configured) of a “beam indicator” (N=1) that includes one “uplink transmission radio resource” information from a base station through a combination of at least one of upper layer signaling, MAC-CE signaling, or L1 signaling. In this case, the terminal can receive a setting via upper layer signaling regarding whether or not one “uplink transmission radio resource” information that may be included in the “beam indicator” described above is applied, for each upper layer signaling setting for the quasi-static uplink transmission channel described above. In this case, the terminal can expect that one “uplink transmission radio resource” that may be set within the “beam indicator” is commonly applied to different types of quasi-static uplink transmission channels.
[0468] As another example, a terminal may be notified (or configured) of a “beam indicator” (N=2) containing two pieces of “uplink transmission radio resource” information from a base station through a combination of at least one of upper layer signaling, MAC-CE signaling, or L1 signaling. In this case, for each upper layer signaling configuration for a quasi-static uplink transmission channel, the terminal may be configured from the base station via upper layer signaling regarding which of the two “uplink transmission radio resources” that may be included in the aforementioned “beam indicator” is applied or not applied. For example, the upper layer signaling (e.g., configuration information received from the base station) may have the meaning of applying the first piece of information among the two “uplink transmission radio resource” pieces of information, or the meaning of applying the second piece of information. For example, the base station may indicate to the terminal which uplink transmission radio resource among the multiple uplink transmission radio resources associated with the beam indicator is to be applied for uplink communication. For example, a base station may indicate a resource to be applied to a terminal through a bitmap, a specific value (e.g., if “10”, a first uplink transmission radio resource; if “01”, a second uplink transmission radio resource), or an indicator. In such a case, if the terminal is configured via upper layer signaling to apply the same value of “uplink transmission radio resource” to different types of quasi-static uplink transmission channels (e.g., if the terminal is configured to apply the first of two “uplink transmission radio resources” that can be configured within a “beam indicator” for one scheduling request-related setting and one periodic CSI report-related setting), the “uplink transmission radio resource” can be expected to be applied commonly to different types of quasi-static uplink transmission channels.
[0469] As another example, a terminal may be notified (or configured) of a “beam indicator” (N>=0) containing N pieces of “uplink transmission radio resource” information for each different type of quasi-static uplink transmission channel from a base station through at least one combination of upper layer signaling, MAC-CE signaling, or L1 signaling. In this case, for each upper layer signaling setting for the quasi-static uplink transmission channel described above, the terminal may be configured via upper layer signaling to determine which information among the N “uplink transmission radio resources” that may be included in the “beam indicator” described above is applied or not applied. For example, the terminal may expect N “uplink radio resources” to be included for each scheduling request related setting, CSI report related setting, and Type-1 configured grant related setting. (For example, N uplink radio resources may be configured for each scheduling request configuration, CSI report configuration, and Type-1 configured grant configuration. For example, uplink radio resources may be dedicated for each scheduling request configuration, CSI report configuration, and Type-1 configured grant configuration.) For example, for a scheduling request configuration, upper layer signaling (e.g., configuration information) may mean to apply the first information among the N “uplink transmission radio resource” information, or to apply the second information.In such cases, if the terminal is configured by the base station via upper layer signaling to apply “uplink transmission radio resources” of the same value to different types of quasi-static uplink transmission channels (e.g., the terminal is instructed to apply the first information among N “uplink transmission radio resources” that can be configured within the “beam indicator” for one scheduling request-related setting and one periodic CSI report-related setting), the said “uplink transmission radio resources” can be expected to be applied individually to different types of quasi-static uplink transmission channels. For example, the terminal may be configured with N radio resources by the base station for each uplink transmission type (e.g., SR, CSI report, type-1 configured grant). The terminal may be instructed by the base station to use the first radio resource among the N radio resources for the first transmission type (e.g., SR). In this case, the terminal may use the first radio resource among the N radio resources not only for the first transmission type (e.g., SR) but also for the second transmission type (e.g., CSI report, type-1 configured grant).
[0470] In the present disclosure, the expression “uplink transmission radio resource included within a beam indicator” may be replaced with various expressions. For example, it may be expressed as “uplink transmission radio resource associated with a beam indicator” or “uplink transmission radio resource mapped to a beam indicator.” Additionally, the term “beam indicator” may be replaced with the term “information indicating a beam.” Furthermore, the expression “uplink transmission radio resource” may be replaced with various terms such as “radio resource,” “resource,” “uplink resource,” etc.
[0471] FIG. 9 is a diagram showing the operation of a terminal for transmitting and receiving beam management according to one embodiment of the present disclosure.
[0472] According to one embodiment, at step 900, the terminal may transmit terminal capability (or capability information) to the base station. The terminal capability signaling that may be reported may be for a combination of at least one of terminal capabilities corresponding to PUSCH, PUCCH, SRS transmission, integrated TCI state operation, spatial relation operation, or the terminal capability corresponding to [Method 1-1], [Method 1-2], [Method 1-3], [Method 2-1], and / or [Method 2-2] described above. In another example, step 900 for the terminal to report terminal capability may be omitted.
[0473] According to one embodiment, at step 905, the terminal may receive upper layer signaling (e.g., configuration information) from the base station based on the reported terminal capability. At this time, the terminal may receive upper layer parameters from the base station for at least one combination of upper layer signaling related to PUSCH, PUCCH, SRS transmission (e.g., configuration information), upper layer signaling related to integrated TCI state operation (e.g., configuration information), upper layer signaling related to spatial relation operation (e.g., configuration information), and upper layer signaling related to support for [Method 1-1], [Method 1-2], [Method 1-3], [Method 2-1], and / or [Method 2-2] (e.g., configuration information).
[0474] According to one embodiment, in step 910, the terminal may perform quasi-static uplink transmission and quasi-static downlink reception operations based on the upper layer signaling settings of the base station. For example, the quasi-static uplink transmission of the terminal may include at least one combination of periodic PUCCH resource settings for SR or periodic CSI reports, Type-1 configured grant PUSCH resource settings for quasi-static uplink data transmission, or periodic SRS resource settings for quasi-static sounding reference signal transmission. For example, the quasi-static downlink reception of the terminal may include at least one combination of search space and / or CORESET settings for receiving downlink control channels, and periodic CSI-RS resource settings for quasi-static downlink channel measurement and time / frequency synchronization of the terminal.
[0475] According to one embodiment, at step 915, the terminal may receive a beam change instruction from the base station. For example, the dynamic beam change instruction method from the base station to the terminal may be based on a TCI state that can be indicated via DCI if the terminal is configured with upper layer signaling (e.g., configuration information) for the integrated TCI state method. If the terminal is not configured with upper layer signaling (e.g., configuration information) for the integrated TCI state method, the dynamic beam change instruction method may be based on spatial relation info that can be indicated via MAC-CE.
[0476] According to one embodiment, at step 920, the terminal may receive a resource change instruction from the base station and may apply the resource change instruction to some or all of the quasi-static uplink transmission and quasi-static downlink reception modes. The application of such resource change instruction may be notified to the terminal by at least one combination of upper layer signaling, MAC signaling, and L1 signaling from the base station, or may follow matters fixedly defined in the specification (e.g., the resource change instruction may be applied only to specific quasi-static uplink transmission and quasi-static downlink reception modes, and may be applied to at least one combination of the terminal's SR transmission, periodic CSI transmission, Type-1 configured grant PUSCH transmission, and periodic SRS transmission as defined in the specification. As the simplest example, the terminal may apply the resource change instruction only to SR transmission). For example, step 920 may be omitted depending on a notification (or setting) from the base station (e.g., conveying whether a resource change instruction is applied from the base station to the terminal via a combination of at least one of upper layer signaling, MAC signaling, and L1 signaling, or / and using a beam change instruction method that does not include a resource change instruction). For example, the base station may separately set whether a resource change instruction is given to the terminal, or indicate only a beam change without a resource change instruction.
[0477] According to one embodiment, in step 925, the terminal may perform quasi-static uplink transmission and / or quasi-static downlink reception operations according to the beam and / or resources changed according to the instructions of the base station in steps 915 and 920.
[0478] The above-described flowchart illustrates an exemplary method that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the method illustrated in the flowchart in this specification. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.
[0479] At least one of steps 900 to 925 of the present disclosure may be omitted, and as another example, additional steps may be included in addition to steps 900 to 925.
[0480] FIG. 10 is a diagram showing the operation of a base station for transmitting and receiving beam management according to one embodiment of the present disclosure.
[0481] Referring to FIG. 10, in step 1000 according to one embodiment, the base station may receive terminal capability (or capability information) from the terminal. At this time, the terminal capability signaling that may be reported from the terminal may be for at least one combination of terminal capabilities corresponding to [Method 1-1], [Method 1-2], [Method 1-3], [Method 2-1], and / or [Method 2-2], PUSCH (physical uplink shared channel), PUCCH (physical uplink control channel), terminal capability related to SRS transmission, terminal capability related to integrated TCI state operation, terminal capability related to spatial relation operation, and terminal capability corresponding to [Method 1-1], [Method 1-2], [Method 1-3], [Method 2-1], and / or [Method 2-2]. For example, step 1000 related to the transmission of the terminal capability information may be omitted.
[0482] According to one embodiment, at step 1005, the base station may transmit upper layer signaling (e.g., configuration information) to the terminal based on the terminal capability reported by the terminal. For example, the upper layer signaling that may be transmitted to the terminal may be upper layer parameters for at least one combination of upper layer signaling related to PUSCH, PUCCH, SRS transmission, upper layer signaling related to integrated TCI state operation, upper layer signaling related to spatial relation operation, and upper layer signaling related to support for [Method 1-1], [Method 1-2], [Method 1-3], [Method 2-1], and / or [Method 2-2] described above.
[0483] According to one embodiment, in step 1010, the base station may receive a quasi-static uplink transmission from the terminal based on an upper layer signaling setting transmitted to the terminal, and perform a transmission operation for receiving a quasi-static downlink at the terminal. For example, the quasi-static uplink transmission of the terminal may include at least one combination of periodic PUCCH resource settings for SR or periodic CSI reports, Type-1 configured grant PUSCH resource settings for quasi-static uplink data transmission, and periodic SRS resource settings for quasi-static sounding reference signal transmission. For example, the quasi-static downlink reception of the terminal may include at least one combination of search space and / or CORESET settings for receiving a downlink control channel, and periodic CSI-RS resource settings for quasi-static downlink channel measurement and time / frequency synchronization of the terminal.
[0484] According to one embodiment, at step 1015, the base station may transmit a beam change instruction to the terminal. For example, the dynamic beam change instruction that the base station may notify the terminal may be performed based on a TCI state that can be indicated via DCI if the terminal has been configured with upper layer signaling (e.g., configuration information) for the integrated TCI state method. For example, if the terminal has not been configured with upper layer signaling (e.g., configuration information) for the integrated TCI state method, the dynamic beam change instruction may be performed based on spatial relation information that can be indicated via MAC-CE.
[0485] According to one embodiment, at step 1020, the base station may transmit a resource change instruction to the terminal, and the terminal may be expected to apply the resource change instruction to some or all of the quasi-static uplink transmission and quasi-static downlink reception modes. The application of such resource change instruction may be notified to the terminal by at least one combination of upper layer signaling, MAC signaling, and L1 signaling from the base station, or may be in accordance with matters fixedly defined in the specification (e.g., the said resource change instruction may be applied only to specific quasi-static uplink transmission and quasi-static downlink reception modes, and may be applied in accordance with specifications defined for at least one combination of the terminal's SR transmission, periodic CSI transmission, Type-1 configured grant PUSCH transmission, and periodic SRS transmission. As the simplest example, the terminal may apply the resource change instruction only to SR transmission). For example, step 1020 may be omitted based on a notification (or setting) from a base station (e.g., conveying from the base station to the terminal whether the resource change instruction is applied through a combination of at least one of upper layer signaling, MAC signaling, and L1 signaling, and / or using a beam change instruction method that does not include the resource change instruction).
[0486] According to one embodiment, in step 1025, the base station may expect the terminal to perform quasi-static uplink transmission and / or quasi-static downlink reception operations according to the changed beam and / or changed resource based on the indication of the base station in steps 1015 and 1020.
[0487] The above-described flowchart illustrates an exemplary method that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the method illustrated in the flowchart in this specification. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.
[0488] At least one of steps 1000 to 1025 of the present disclosure may be omitted, and as another example, additional steps may be included in addition to steps 1000 to 1025.
[0489] FIG. 11 is a drawing illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.
[0490] Referring to FIG. 11, the terminal may include a transceiver (referring to a terminal receiver (1100) and a terminal transmitter (1110), a memory (not shown), and a terminal processing unit (1105, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver (1100, 1110), memory, and terminal processing unit (1105) of the terminal may operate. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more components or fewer components than the components described above. Furthermore, the transceiver, memory, and processor may be implemented in the form of a single chip.
[0491] According to one embodiment, the transceiver may transmit and / or receive a signal with a base station. Here, the signal may include control information and data. To this end, the transceiver may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver, and the components of the transceiver are not limited to an RF transmitter and an RF receiver.
[0492] In addition, the transceiver can receive a signal through a wireless channel and output it to a processor, and transmit the signal output from the processor through a wireless channel.
[0493] According to one embodiment, the memory may store programs and data necessary for the operation of the terminal. Additionally, the memory may store control information or data included in signals transmitted or received by the terminal. The memory may be composed of a storage medium or a combination of storage media, such as ROM, RAM, a hard disk, CD-ROM, and DVD. Additionally, there may be multiple memories.
[0494] In addition, the processor can control a series of processes to enable the terminal to operate according to the aforementioned embodiment. For example, the processor can receive a DCI composed of two layers and control the components of the terminal to receive multiple PDSCHs simultaneously. There may be multiple processors, and the processors can perform the operation of controlling the components of the terminal by executing a program stored in memory.
[0495] FIG. 12 is a drawing illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.
[0496] Referring to FIG. 12, a base station may include a transceiver unit (referring to a base station receiver unit (1200) and a base station transmitter unit (1210)), a memory (not shown), and a base station processing unit (1205, or a base station control unit or processor). Depending on the communication method of the base station described above, the transceiver unit (1200, 1210), the memory, and the base station processing unit (1205) of the base station may operate. However, the components of the base station are not limited to the examples described above. For example, the base station may include more components or fewer components than the components described above. In addition, the transceiver unit, the memory, and the processor may be implemented in the form of a single chip.
[0497] According to one embodiment, the transceiver may transmit and / or receive a signal with a terminal. Here, the signal may include control information and data. To this end, the transceiver may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver, and the components of the transceiver are not limited to an RF transmitter and an RF receiver.
[0498] In addition, the transceiver receives a signal through a wireless channel and outputs it to a processor, and can transmit the signal output from the processor through a wireless channel.
[0499] According to one embodiment, the memory can store programs and data necessary for the operation of the base station. Additionally, the memory can store control information or data included in signals transmitted and received by the base station. The memory may be composed of a storage medium or a combination of storage media, such as ROM, RAM, a hard disk, CD-ROM, and DVD. Additionally, there may be multiple memories.
[0500] A processor can control a series of processes to enable a base station to operate according to the embodiments of the present disclosure described above. For example, the processor can control each component of the base station to configure two layers of DCIs containing allocation information for a plurality of PDSCHs and to transmit them. There may be multiple processors, and the processors can perform control operations on the components of the base station by executing a program stored in memory.
[0501] Methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.
[0502] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of this disclosure.
[0503] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), Electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disc storage devices, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.
[0504] Additionally, the program may be stored on an attachable storage device accessible via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to the device performing the embodiment of the present disclosure through an external port. Additionally, a separate storage device on the communication network may be connected to the device performing the embodiment of the present disclosure.
[0505] In the specific embodiments of the present disclosure described above, the components included in the invention are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed of a singular form, or even if a component is expressed in the singular form, it may be composed of a plural form.
[0506] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of the present disclosure and to aid in understanding the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art that other variations based on the technical concept of the present disclosure are possible. Furthermore, each of the above embodiments may be combined and operated as needed. For example, parts of one embodiment of the present disclosure and parts of another embodiment may be combined to operate a base station and a terminal. For example, parts of the first embodiment and the second embodiment of the present disclosure may be combined to operate a base station and a terminal. In addition, although the above embodiments are presented based on an FDD LTE system, other variations based on the technical concept of the above embodiments may be implemented in other systems such as a TDD LTE system, 5G, or NR system.
[0507] Meanwhile, the order of description in the drawings illustrating the method of the present disclosure does not necessarily correspond to the order of execution, and the order of execution may be changed or executed in parallel.
[0508] Alternatively, the drawings describing the method of the present disclosure may omit some components and include only some components to the extent that the essence of the present invention is not impaired.
[0509] In addition, the method of the present disclosure may be implemented by combining some or all of the contents included in each embodiment to the extent that it does not impair the essence of the invention.
[0510] Various embodiments of the present disclosure have been described above. The foregoing description of the present disclosure is for illustrative purposes only, and the embodiments of the present disclosure are not limited to the disclosed embodiments. Those skilled in the art will understand that modifications can be easily made to other specific forms without altering the technical spirit or essential features of the present disclosure. The scope of the present disclosure is defined by the claims set forth below rather than by the foregoing detailed description, and all modifications or variations derived from the meaning and scope of the claims and their equivalents should be interpreted as being included within the scope of the present disclosure.
Claims
In a method performed by UE (user equipment), A step of receiving configuration information associated with an uplink signal from a base station, wherein the configuration information includes information on resource sets corresponding to TCI (transmission configuration indicator) states; A step of receiving information from the base station indicating a second TCI state different from the first TCI state set for the UE among the TCI states; A step of identifying a resource set corresponding to the second TCI state based on the above setting information; and A method comprising the step of transmitting the uplink signal to the base station using the resource set based on the second TCI state. In claim 1, A method in which, based on the information indicating the second TCI state, the beam for transmitting the uplink signal is changed from a first beam corresponding to the first TCI state to a second beam corresponding to the second TCI state. In claim 1, The information indicating the above second TCI status is included in either DCI (downlink control information) or MAC (medium access control) CE (control element), and A method in which the uplink signal comprises one of an SR (scheduling request), an SRS (sounding reference signal), a periodic PUCCH (physical uplink control channel), or a CG (configured grant) PUSCH (physical uplink shared channel). In claim 1, The method further includes the step of transmitting capability information to the base station, the information regarding a minimum beam application time obtained by adding a second time for processing to a first time for the application of the second TCI state. The second TCI is applied after the beam application time from the slot in which HARQ-ACK (hybrid automatic repeat request-acknowledgement) information corresponding to DCI (downlink control information) including the information indicating the second TCI is transmitted, and A method in which the above beam application time is determined based on the above minimum beam application time. In a method performed by a base station, A step of transmitting configuration information associated with an uplink signal to a UE (user equipment), wherein the configuration information includes information about resource sets corresponding to TCI (transmission configuration indicator) states; A step of transmitting to the UE information indicating a second TCI state different from a first TCI state set for the UE among the TCI states; and The method includes the step of receiving the uplink signal from the above UE using a resource set based on the second TCI state, and A method in which the resource set corresponding to the second TCI state is based on the setting information. In claim 5, A method in which, based on the information indicating the second TCI state, the beam for the uplink signal is changed from a first beam corresponding to the first TCI state to a second beam corresponding to the second TCI state. In claim 5, The information indicating the above second TCI status is included in either DCI (downlink control information) or MAC (medium access control) CE (control element), and A method in which the uplink signal comprises one of an SR (scheduling request), an SRS (sounding reference signal), a periodic PUCCH (physical uplink control channel), or a CG (configured grant) PUSCH (physical uplink shared channel). In claim 5, The method further includes the step of receiving capability information from the above UE, the information regarding a minimum beam application time, which is the sum of a first time for the application of the second TCI state and a second time for processing. The second TCI is applied after the beam application time from the slot in which HARQ-ACK (hybrid automatic repeat request-acknowledgement) information corresponding to DCI (downlink control information) including the information indicating the second TCI is transmitted, and A method in which the above beam application time is determined based on the above minimum beam application time. Regarding UE (user equipment): At least one transceiver; At least one processor communicatively coupled to the above at least one transceiver; and It includes at least one memory that is communicationally coupled to the above at least one processor and stores instructions, and The above instructions are executed individually or in any combination by the above at least one processor, so that the UE: Receive configuration information associated with an uplink signal from a base station, and said configuration information includes information about resource sets corresponding to TCI (transmission configuration indicator) states. Receive information from the base station indicating a second TCI state different from the first TCI state set for the UE among the TCI states, and Based on the above setting information, identify a resource set corresponding to the above second TCI state, and A UE that enables the base station to transmit the uplink signal using the resource set based on the second TCI state. In claim 9, A UE in which, based on the information indicating the second TCI state, the beam for transmitting the uplink signal is changed from a first beam corresponding to the first TCI state to a second beam corresponding to the second TCI state. In claim 9, The information indicating the above second TCI status is included in either DCI (downlink control information) or MAC (medium access control) CE (control element), and The above uplink signal comprises one of an SR (scheduling request), an SRS (sounding reference signal), a periodic PUCCH (physical uplink control channel), or a CG (configured grant) PUSCH (physical uplink shared channel), in a UE. In claim 9, The above commands are the above UE: The base station is instructed to transmit capability information including information on a minimum beam application time, which is the sum of a first time for the application of the second TCI state and a second time for processing. The second TCI is applied after the beam application time from the slot in which HARQ-ACK (hybrid automatic repeat request-acknowledgement) information corresponding to DCI (downlink control information) including the information indicating the second TCI is transmitted, and The above beam application time is determined based on the above minimum beam application time, UE. In the case of a base station, Regarding the base station: At least one transceiver; At least one processor communicatively coupled to the above at least one transceiver; and It includes at least one memory that is communicationally coupled to the above at least one processor and stores instructions, and The above instructions are executed individually or in any combination by the above at least one processor, so that the base station: Transmits configuration information associated with an uplink signal to UE (user equipment), said configuration information includes information about resource sets corresponding to TCI (transmission configuration indicator) states, Information is transmitted to the above UE indicating a second TCI state different from the first TCI state set for the UE among the above TCI states, and From the above UE, receive the uplink signal using a resource set based on the above second TCI state, and The resource set corresponding to the above second TCI state is a base station based on the above setting information. In claim 13, A base station in which, based on the information indicating the second TCI state, the beam for the uplink signal is changed from a first beam corresponding to the first TCI state to a second beam corresponding to the second TCI state. In claim 13, The information indicating the above second TCI status is included in either DCI (downlink control information) or MAC (medium access control) CE (control element), and A base station in which the above uplink signal includes one of an SR (scheduling request), an SRS (sounding reference signal), a periodic PUCCH (physical uplink control channel), or a CG (configured grant) PUSCH (physical uplink shared channel).
