Patent Application
20250234302
This application is based on and claims priority under 35 U.S.C. § 119 to Korean Patent Application No. 10-2024-0006281, filed on Jan. 15, 2024, in the Korean Intellectual Property Office, the disclosure of which is herein incorporated by reference in its entirety.
The present disclosure relates to the operation of terminal and base station in a wireless communication system. More particularly, the present disclosure relates to a method and an apparatus for power control in a wireless communication system.
5th generation (5G) mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6 GHz” bands such as 3.5 GHz, but also in “Above 6 GHz” bands referred to as mmWave including 28 GHz and 39 GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz (THz) bands (for example, 95 GHz to 3 THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.
At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, a layer 2 (L2) pre-processing, and network slicing for providing a dedicated network specialized to a specific service.
Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.
Moreover, there has been ongoing standardization in air interface architecture/protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture/service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.
As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.
Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.
As described above, the development of a mobile communication system has made it possible to provide various services, and a measure to provide these services effectively are required.
The above information is presented as background information only to assist with an understanding of the disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the disclosure.
The disclosed embodiments are intended to provide an apparatus and a method for effectively providing services in a mobile communication system.
A method performed by a terminal in a wireless communication system in the present disclosure to solve the above problems, comprises receiving, from a base station, a radio resource control (RRC) message including first power control configuration information for an uplink (UL) channel; and transmitting, to the base station, the UL channel based on at least one of the first power control configuration information or second power control configuration information. The RRC message includes the second power control configuration information in case that the RRC message further includes unified transmission configuration indication (TCI) state type configuration information, The first power control configuration information relates to a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).
A method performed by a base station in a wireless communication system in the present disclosure to solve the above problems, comprises, transmitting, to a terminal, a radio resource control (RRC) message including first power control configuration information for an uplink (UL) channel; and receiving, from the terminal, the UL channel based on at least one of the first power control configuration information or second power control configuration information. The RRC message includes the second power control configuration information in case that the RRC message further includes unified transmission configuration indication (TCI) state type configuration information, The first power control configuration information relates to a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).
The disclosed embodiments provide an apparatus and a method for effectively providing services in a mobile communication system.
Before undertaking the DETAILED DESCRIPTION below, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document: the terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation; the term “or,” is inclusive, meaning and/or; the phrases “associated with” and “associated therewith,” as well as derivatives thereof, may mean to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, or the like; and the term “controller” means any device, system or part thereof that controls at least one operation, such a device may be implemented in hardware, firmware or software, or some combination of at least two of the same. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.
Moreover, various functions described below can be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer readable medium. The terms “application” and “program” refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer readable program code. The phrase “computer readable program code” includes any type of computer code, including source code, object code, and executable code. The phrase “computer readable medium” includes any type of medium capable of being accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. A “non-transitory” computer readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals. A non-transitory computer readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.
Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.
For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts:
Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.
In describing the embodiments, descriptions related to technical contents well-known in the relevant art and not associated directly with the disclosure will be omitted. Such an omission of unnecessary descriptions is intended to prevent obscuring of the main idea of the disclosure and more clearly transfer the main idea.
For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Furthermore, the size of each element does not completely reflect the actual size. In the respective drawings, the same or corresponding elements are assigned the same reference numerals.
The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described below in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth below, but may be implemented in various different forms. The following embodiments are provided only to completely disclose the disclosure and inform those skilled in the art of the scope of the disclosure, and the disclosure is defined only by the scope of the appended claims. Throughout the specification, the same or like reference signs indicate the same or like elements. Furthermore, in describing the disclosure, a detailed description of known functions or configurations incorporated herein will be omitted when it is determined that the description may make the subject matter of the disclosure unnecessarily unclear. The terms which will be described below are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the users, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.
In the following description, a base station is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a base station (BS), a wireless access unit, a base station controller, and a node on a network. A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the disclosure, a “downlink (DL)” refers to a radio link via which a base station transmits a signal to a terminal, and an “uplink (UL)” refers to a radio link via which a terminal transmits a signal to a base station. Furthermore, in the following description, LTE or LTE-A systems may be described by way of example, but the embodiments of the disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. Examples of such communication systems may include 5th generation mobile communication technologies (5G, new radio, and NR) developed beyond LTE-A, and in the following description, the “5G” may be the concept that covers the exiting LTE, LTE-A, and other similar services. In addition, based on determinations by those skilled in the art, the disclosure may also be applied to other communication systems through some modifications without significantly departing from the scope of the disclosure.
Herein, it will be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart block or blocks. These computer program instructions may also be stored in a computer usable or computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that implement the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.
Furthermore, each block in the flowchart illustrations may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
As used in embodiments of the disclosure, the term “unit” refers to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), and the “unit” may perform certain functions. However, the “unit” does not always have a meaning limited to software or hardware. The “unit” may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the “unit” includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The elements and functions provided by the “unit” may be either combined into a smaller number of elements, or a “unit,” or divided into a larger number of elements, or a “unit.” Moreover, the elements and “units” may be implemented to reproduce one or more CPUs within a device or a security multimedia card. Furthermore, the “unit” in embodiments may include one or more processors.
A wireless communication system is advancing to a broadband wireless communication system for providing high-speed and high-quality packet data services using communication standards, such as high-speed packet access (HSPA) of 3GPP, LTE (long-term evolution or evolved universal terrestrial radio access (E-UTRA)), LTE-Advanced (LTE-A), LTE-Pro, high-rate packet data (HRPD) of 3GPP2, ultra-mobile broadband (UMB), IEEE 802.16e, and the like, as well as typical voice-based services.
As a typical example of the broadband wireless communication system, an LTE system employs an orthogonal frequency division multiplexing (OFDM) scheme in a downlink (DL) and employs a single carrier frequency division multiple access (SC-FDMA) scheme in an uplink (UL). The uplink refers to a radio link via which a user equipment (UE) or a mobile station (MS) transmits data or control signals to a base station (BS) or eNode B, and the downlink refers to a radio link via which the base station transmits data or control signals to the UE. The multiple access scheme may separate data or control information of respective users by allocating and operating time-frequency resources for transmitting the data or control information for each user so as to avoid overlapping each other, that is, so as to establish orthogonality.
Since a 5G communication system, which is a post-LTE communication system, must freely reflect various requirements of users, service providers, and the like, services satisfying various requirements must be supported. The services considered in the 5G communication system include enhanced mobile broadband (eMBB) communication, massive machine-type communication (mMTC), ultra-reliability low-latency communication (URLLC), and the like.
eMBB aims at providing a data rate higher than that supported by existing LTE, LTE-A, or LTE-Pro. For example, in the 5G communication system, eMBB must provide a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink for a single base station. Furthermore, the 5G communication system must provide an increased user-perceived data rate to the UE, as well as the maximum data rate. In order to satisfy such requirements, transmission/reception technologies including a further enhanced multi-input multi-output (MIMO) transmission technique are required to be improved. Also, the data rate required for the 5G communication system may be obtained using a frequency bandwidth more than 20 MHz in a frequency band of 3 to 6 GHz or 6 GHz or more, instead of transmitting signals using a transmission bandwidth up to 20 MHz in a band of 2 GHz used in LTE.
In addition, mMTC is being considered to support application services such as the Internet of Things (IoT) in the 5G communication system. mMTC has requirements, such as support of connection of a large number of UEs in a cell, enhancement coverage of UEs, improved battery time, a reduction in the cost of a UE, and the like, in order to effectively provide the Internet of Things. Since the Internet of Things provides communication functions while being provided to various sensors and various devices, it must support a large number of UEs (e.g., 1,000,000 UEs/km2) in a cell. In addition, the UEs supporting mMTC may require wider coverage than those of other services provided by the 5G communication system because the UEs are likely to be located in a shadow area, such as a basement of a building, which is not covered by the cell due to the nature of the service. The UE supporting mMTC must be configured to be inexpensive, and may require a very long battery lifetime such as 10 to 15 years because it is difficult to frequently replace the battery of the UE.
Lastly, URLLC is a cellular-based mission-critical wireless communication service. For example, URLLC may be used for services such as remote control for robots or machines, industrial automation, unmanned aerial vehicles, remote health care, and emergency alert. Thus, URLLC must provide communication with ultra-low latency and ultra-high reliability. For example, a service supporting URLLC must satisfy an air interface latency of less than 0.5 ms, and may also requires a packet error rate of 10−5 or less. Therefore, for the services supporting URLLC, a 5G system must provide a transmit time interval (TTI) shorter than those of other services, and also may require a design for assigning a large number of resources in a frequency band in order to secure reliability of a communication link.
The three services in 5G, that is, eMBB, URLLC, and mMTC, may be multiplexed and transmitted in a single system. In this case, different transmission/reception techniques and transmission/reception parameters may be used between services in order to satisfy different requirements of the respective services. Of course, 5G is not limited to the three services described above.
In the following description, the term “a/b” may be understood as at least one of a and b.
Hereinafter, a frame structure of a 5G system will be described in more detail with reference to the accompanying drawings.
In
An example of a structure of a frame 200, a subframe 201, and a slot 202 is illustrated in
Next, a bandwidth part (BWP) configuration in a 5G communication system will be described in detail with reference to the accompanying drawings.
Obviously, the above example is not limiting, and various parameters related to the bandwidth part may be configured for the UE, in addition to the above configuration information. The base station may transfer the configuration information to the UE through upper layer signaling, for example, radio resource control (RRC) signaling. One configured bandwidth part or at least one bandwidth part among multiple configured bandwidth parts may be activated. Whether or not the configured bandwidth part is activated may be transferred from the base station to the UE semi-statically through RRC signaling, or dynamically through downlink control information (DCI).
According to an embodiment, before a radio resource control (RRC) connection, an initial bandwidth part (BWP) for initial access may be configured for the UE by the base station through a master information block (MIB). More specifically, the UE may receive configuration information regarding a control resource set (CORESET) and a search space which may be used to transmit a PDCCH for receiving system information (which may correspond to remaining system information (RMSI) or system information block 1 (SIB1) necessary for initial access through the MIB in the initial access step. Each of the control resource set and the search space configured through the MIB may be considered identity (ID) 0. The base station may notify the UE of configuration information, such as frequency allocation information, time allocation information, and numerology, regarding control region #0 through the MIB. In addition, the base station may notify the UE of configuration information regarding the monitoring cycle and occasion with regard to control resource set #0, that is, configuration information regarding search space #0, through the MIB. The UE may consider that a frequency domain configured by control resource set #0 acquired from the MIB is an initial bandwidth part for initial access. The ID of the initial bandwidth part may be considered to be 0.
The bandwidth part-related configuration supported by 5G may be used for various purposes.
According to an embodiment, if the bandwidth supported by the UE is smaller than the system bandwidth, this may be supported through the bandwidth part configuration. For example, the base station may configure the frequency location (configuration information 2) of the bandwidth part for the UE, so that the UE can transmit/receive data at a specific frequency location within the system bandwidth.
In addition, according to an embodiment, the base station may configure multiple bandwidth parts for the UE for the purpose of supporting different numerologies. For example, in order to support a UE's data transmission/reception using both a subcarrier spacing of 15 kHz and a subcarrier spacing of 30 kHz, two bandwidth parts may be configured as subcarrier spacings of 15 kHz and 30 kHz, respectively. Different bandwidth parts may be subjected to frequency division multiplexing (FDM), and if data is to be transmitted/received at a specific subcarrier spacing, the bandwidth part configured as the corresponding subcarrier spacing may be activated.
In addition, according to an embodiment, the base station may configure bandwidth parts having different sizes of bandwidths for the UE for the purpose of reducing power consumed by the UE. For example, if the UE supports a substantially large bandwidth, for example, 100 MHz, and always transmits/receives data with the corresponding bandwidth, a substantially large amount of power consumption may occur. Particularly, it may be substantially inefficient from the viewpoint of power consumption to unnecessarily monitor the downlink control channel with a large bandwidth of 100 MHz in the absence of traffic. In order to reduce power consumed by the UE, the base station may configure a bandwidth part of a relatively small bandwidth (for example, a bandwidth part of 20 MHz) for the UE. The UE may perform a monitoring operation in the 20 MHz bandwidth part in the absence of traffic, and may transmit/receive data with the 100 MHz bandwidth part as instructed by the base station if data has occurred.
In connection with the bandwidth part configuring method, UEs, before being RRC-connected, may receive configuration information regarding the initial bandwidth part through an MIB in the initial access step. To be more specific, a UE may have a control resource set (i.e., CORESET) configured for a downlink control channel which may be used to transmit downlink control information (DCI) for scheduling a system information block (SIB) from the MIB of a physical broadcast channel (PBCH). The bandwidth of the control resource set configured by the MIB may be considered as the initial bandwidth part, and the UE may receive, through the configured initial bandwidth part, a physical downlink shared channel (PDSCH) through which an SIB is transmitted. The initial bandwidth part may be used not only for the purpose of receiving the SIB, but also for other system information (OSI), paging, random access, or the like.
If a UE has one or more bandwidth parts configured therefor, the base station may indicate, to the UE, to change (or switch or transition) the bandwidth parts by using a bandwidth part indicator field inside DCI. As an example, if the currently activated bandwidth part of the UE is bandwidth part #1 301 in
As described above, DCI-based bandwidth part changing may be indicated by DCI for scheduling a PDSCH or a PUSCH, and thus, upon receiving a bandwidth part change request, the UE needs to be able to receive or transmit the PDSCH or PUSCH scheduled by the corresponding DCI in the changed bandwidth part with no problem. To this end, requirements for the delay time (TBWP) required during a bandwidth part change are specified in standards, and may be defined as given in Table 3 below, for example.
Note 1:
The requirements for the bandwidth part change delay time support type 1 or type 2, depending on the capability of the UE. The UE may report the supportable bandwidth part change delay time type to the base station.
If the UE has received DCI including a bandwidth part change indicator in slot n, according to the above-described requirement regarding the bandwidth part change delay time, the UE may complete a change to the new bandwidth part indicated by the bandwidth part change indicator at a timepoint not later than slot n+TBWP, and may transmit/receive a data channel scheduled by the corresponding DCI in the newly changed bandwidth part. If the base station wants to schedule a data channel by using the new bandwidth part, the base station may determine time domain resource allocation regarding the data channel, based on the UE's bandwidth part change delay time (TBWP). That is, when scheduling a data channel by using the new bandwidth part, the base station may schedule the corresponding data channel after the bandwidth part change delay time, in connection with the method for determining time domain resource allocation regarding the data channel. Accordingly, the UE may not expect that the DCI indicating a bandwidth part change may indicate a slot offset (K0 or K2) value smaller than the bandwidth part change delay time (TBWP).
If the UE has received DCI (for example, DCI format 11 or 0_1) indicating a bandwidth part change, the UE may perform no transmission or reception during a time interval from the third symbol of the slot used to receive a PDCCH including the corresponding DCI to the start point of the slot indicated by a slot offset (K0 or K2) value indicated by a time domain resource allocation indicator field in the corresponding DCI. For example, if the UE has received DCI indicating a bandwidth part change in slot n, and if the slot offset value indicated by the corresponding DCI is K, the UE may perform no transmission or reception from the third symbol of slot n to the symbol before slot n+K (for example, the last symbol of slot n+K−1).
Referring to
The main functions of the NR SDAP 425 or 470 may include some of functions below:
With regard to the SDAP layer device, the UE may be configured, through an RRC message, whether to use the header of the SDAP layer device with regard to each PDCP layer device or with regard to each bearer or with regard to each logical channel, or whether to use functions of the SDAP layer device. If an SDAP header is configured, the non-access stratum (NAS) quality of service (QoS) reflection configuration 1-bit indicator (NAS reflective QoS) of the SDAP header and the access stratum (AS) QoS reflection configuration 1-bit indicator (AS reflective QoS) may indicate, to the UE, that the UE can update or reconfigure mapping information regarding the QoS flow and data bearer of the uplink and downlink. The SDAP header may include QoS flow ID information indicating the QoS. The QoS information may be used as data processing priority, scheduling information, etc. for smoothly supporting services.
The main functions of the NR PDCP 430 or 465 may include some of functions below:
The above-mentioned reordering of the NR PDCP device refers to a function of reordering PDCP PDUs received from a lower layer in an order based on the PDCP sequence number (SN), and may include a function of transferring data to an upper layer in the reordered sequence. Alternatively, the reordering of the NR PDCP device may include at least one of a function of instantly transferring data without considering the order, a function of recording PDCP PDUs lost as a result of reordering, a function of reporting the state of the lost PDCP PDUs to the transmitting side, and a function of requesting retransmission of the lost PDCP PDUs.
The main functions of the NR RLC 435 or 460 may include some of functions below:
The in-sequence delivery of the NR RLC device refers to a function of delivering RLC SDUs, received from the lower layer, to the upper layer in sequence. The in-sequence delivery of the NR RLC device may include at least one of a function of, if one original RLC SDU is segmented into multiple RLC SDUs and the segmented RLC SDUs are received, reassembling the RLC SDUs and delivering the reassembled RLC SDUs, a function of reordering the received RLC PDUs with reference to the RLC sequence number (SN) or PDCP sequence number (SN), a function of recording RLC PDUs lost as a result of reordering, a function of reporting the state of the lost RLC PDUs to the transmitting side, and a function of requesting retransmission of the lost RLC PDUs. The in-sequence delivery of the NR RLC device may include a function of, if there is a lost RLC SDU, successively delivering only RLC SDUs before the lost RLC SDU to the upper layer, and may include a function of, if a predetermined timer has expired although there is a lost RLC SDU, successively delivering all RLC SDUs received before the timer was started to the upper layer. Alternatively, the in-sequence delivery of the NR RLC device may include a function of, if a predetermined timer has expired although there is a lost RLC SDU, successively delivering all currently received RLC SDUs to the upper layer. In addition, the in-sequence delivery of the NR RLC device may include a function of processing RLC PDUs in the received order (regardless of the sequence number order, in the order of arrival) and delivering same to the PDCP device regardless of the order (out-of-sequence delivery), and may include a function of, in the case of segments, receiving segments which are stored in a buffer or which are to be received later, reconfiguring same into one complete RLC PDU, processing, and delivering same to the PDCP device. The NR RLC layer may include no concatenation function, which may be performed in the NR MAC layer or replaced with a multiplexing function of the NR MAC layer.
The out-of-sequence delivery of the NR RLC device refers to a function of directly delivering RLC SDUs received from the lower layer to the upper layer regardless of the sequence. The out-of-sequence delivery of the NR RLC device may include at least one of a function of, if one original RLC SDU is segmented into multiple RLC SDUs and the segmented RLC SDUs are received, reassembling the RLC SDUs and delivering the reassembled RLC SDUs, and a function of storing the RLC SN or PDCP SN of received RLC PDUs, and recording RLC PDUs lost as a result of reordering.
The NR MAC 440 or 455 may be connected to multiple NR RLC layer devices configured in one UE, and the main functions of the NR MAC may include some of functions below:
An NR PHY layer 445 or 450 may perform operations of channel-coding and modulating upper layer data, thereby obtaining OFDM symbols, and delivering the same through a radio channel, or demodulating OFDM symbols received through the radio channel, channel-decoding the same, and delivering the same to the upper layer.
The detailed structure of the radio protocol structure may be variously changed according to the carrier (or cell) operating scheme. For example, in case that the base station transmits data to the UE, based on a single carrier (or cell), the base station and the UE may use a protocol structure having a single structure with regard to each layer, such as 400. On the other hand, in case that the base station transmits data to the UE, based on carrier aggregation (CA) which uses multiple carriers in a single TRP, the base station and the UE may use a protocol structure which has a single structure up to the RLC, but multiplexes the PHY layer through a MAC layer, such as 410. As another example, in case that the base station transmits data to the UE, based on dual connectivity (DC) which uses multiple carriers in multiple TRPs, the base station and the UE may use a protocol structure which has a single structure up to the RLC, but multiplexes the PHY layer through a MAC layer, such as 420.
Hereinafter, a single TCI state indication and activation method based on a unified TCI scheme is described. The unified TCI scheme may mean a scheme of integrating and managing, through a TCI state, a transmission/reception beam management scheme, which has been classified as a TCI state scheme used in downlink reception of a UE and a spatial relation info scheme used in uplink transmission in conventional Rel-15 and 16. Therefore, in a case where a UE receives an indication from a base station, based on the unified TCI scheme, the UE may perform beam management even for uplink transmission by using a TCI state. If the higher layer signaling TCI-State having the higher layer signaling tci-stateld-r17 is configured for a UE by a base station, the UE may perform an operation based on the unified TCI scheme by using the TCI-State. TCI-State may exist in two types including a joint TCI state and a separate TCI state.
The first type is a joint TCI state, and all TCI states to be applied to uplink transmission and downlink reception may be indicated to a UE by a base station through one value of TCI-State. If joint TCI state-based TCI-state is indicated to the UE, a parameter to be used in downlink channel estimation may be indicated to the UE by using an RS corresponding to qcl-Type1 in the joint TCI state-based TCI-state, and a parameter to be used as a downlink reception beam or reception filter may be indicated thereto by using an RS corresponding to qcl-Type2. If joint TCI state-based TCI-state is indicated to the UE, a parameter to be used as an uplink transmission beam or transmission filter may be indicated to the UE by using an RS corresponding to qcl-Type2 in a corresponding joint DL/UL TCI state-based TCI-state. If a joint TCI state is indicated to the UE, the UE may apply the same beam to uplink transmission and downlink reception.
The second type is a separate TCI state, and a UL TCI state to be applied to uplink transmission and a DL TCI state to be applied to downlink reception may be individually indicated to a UE by a base station. If a UL TCI state is indicated to the UE, a parameter to be used as an uplink transmission beam or transmission filter may be indicated to the UE by using a reference RS or a source RS configured in the UL TCI state. If a DL TCI state is indicated to the UE, a parameter to be used in downlink channel estimation may be indicated to the UE by using an RS corresponding to qcl-Type1 configured in the DL TCI state, and a parameter to be used as a downlink reception beam or reception filter may be indicated thereto by using an RS corresponding to qcl-Type2.
If a DL TCI state and a UL TCI state are indicated to the UE together, a parameter to be used as an uplink transmission beam or transmission filter may be indicated to the UE by using a reference RS or a source RS configured in the UL TCI state, a parameter to be used in downlink channel estimation may be indicated to the UE by using an RS corresponding to qcl-Type1 configured in the DL TCI state, and a parameter to be used as a downlink reception beam or reception filter may be indicated thereto using an RS corresponding to qcl-Type2. If the reference RSs or source RSs configured in the DL TCI state and UL TCI state indicated to the UE are different from each other, the UE may apply individual beams to uplink transmission and downlink reception, based on the indicated UL TCI state and DL TCI state.
A maximum of 128 joint TCI states may be configured for a particular bandwidth part in a particular cell for the UE by the base station through higher layer signaling, a maximum of 64 or 128 DL TCI states among separate TCI states may be configured for a particular bandwidth part in a particular cell through higher layer signaling, based on a UE capability report, and a DL TCI state among separate TCI states and a joint TCI state may use the same higher layer signaling structure. For example, if 128 joint TCI states are configured and 64 DL TCI states among separate TCI states are configured, the 64 DL TCI states may be included in the 128 joint TCI states.
A maximum of 32 or 64 UL TCI states among separate TCI states may be configured for a particular bandwidth part in a particular cell through higher layer signaling, based on a UE capability report, and a UL TCI state among separate TCI states and a joint TCI state may also use the same higher layer signaling structure like the relation between a DL TCI state among separate TCI states and a joint TCI state, or a UL TCI state among separate TCI states may also use a higher layer signaling structure different from that of a joint TCI state and a DL TCI state among separate TCI states.
As described above, using different or identical higher layer signaling structures may be defined in a specification, or may be distinguished through another higher layer signaling configured by a base station, based on a UE capability report including information on a usage scheme which a UE is able to support among two types of usage schemes.
A transmission/reception beam-related indication may be received by a UE in a unified TCI scheme by using one scheme among a joint TCI state and a separate TCI state configured by a base station. Whether to use one of a joint TCI state and a separate TCI state may be configured for a UE by a base station through higher layer signaling.
A UE may receive a transmission/reception beam-related indication through higher layer signaling by using one scheme selected from among a joint TCI state and a separate TCI state, and a method of transmission/reception beam indication by a base station may be classified as two types of methods including a MAC-CE-based indication method and a MAC-CE-based activation and DCI-based indication method.
In a case where a UE receives a transmission/reception beam-related indication through higher layer signaling by using a joint TCI state scheme, the UE may receive a MAC-CE indicating a joint TCI state from a base station to perform a transmission/reception beam application operation, and the base station may schedule reception of a PDSCH including the MAC-CE to the UE through a PDCCH. If there is one joint TCI state included in a MAC-CE, the UE may determine an uplink transmission beam or transmission filter and a downlink reception beam or reception filter by using the indicated joint TCI state after 3 ms after PUCCH transmission including HARQ-ACK information meaning whether a PDSCH including the MAC-CE has been successfully received. If there are two or more joint TCI states included in a MAC-CE, the UE may identify that multiple joint TCI states indicated by the MAC-CE correspond to respective codepoints of a TCI state field of DCI format 1_1 or 1_2, after 3 ms after PUCCH transmission including HARQ-ACK information meaning whether a PDSCH including the MAC-CE has been successfully received, and activate the indicated joint TCI states. Thereafter, the UE may receive DCI format 1_1 or 1_2 to apply one joint TCI state indicated by a TCI state field in the DCI to uplink transmission and downlink reception beams. DCI format 1_1 or 1_2 may include downlink data channel scheduling information (with DL assignment) or not include same (without DL assignment).
In a case where a UE receives a transmission/reception beam-related indication through higher layer signaling by using a separate TCI state scheme, the UE may receive a MAC-CE indicating a separate TCI state from a base station to perform a transmission/reception beam application operation, and the base station may schedule reception of a PDSCH including the MAC-CE to the UE through a PDCCH. If a MAC-CE includes one separate TCI state set, the UE may determine an uplink transmission beam or transmission filter and a downlink reception beam or reception filter by using separate TCI states included in the indicated separate TCI state set after 3 ms after PUCCH transmission including HARQ-ACK information meaning whether a corresponding PDSCH has been successfully received. A separate TCI state set may indicate a single or multiple separate TCI states which one codepoint of a TCI state field in DCI format 1_1 or 1_2 may have, and one separate TCI state set may include one DL TCI state, include one UL TCI state, or include one DL TCI state and one UL TCI state. If a MAC-CE includes two or more separate TCI state sets, the UE may identify that multiple separate TCI state sets indicated by the MAC-CE correspond to respective codepoints of a TCI state field of DCI format 1_1 or 1_2, after 3 ms after PUCCH transmission including HARQ-ACK information meaning whether a corresponding PDSCH has been successfully received, and may activate the indicated separate TCI state sets. Each codepoint of the TCI state field of DCI format 1_1 or 12 may indicate one DL TCI state, indicate one UL TCI state, or indicate one DL TCI state and one UL TCI state. The UE may receive DCI format 1_1 or 12 to apply a separate TCI state set indicated by a TCI state field in the DCI to uplink transmission and downlink reception beams. DCI format 1_1 or 1_2 may include downlink data channel scheduling information (with DL assignment) or not include same (without DL assignment).
The UE may transmit a PUCCH including a HARQ-ACK indicating whether DCI format 1_1 or 1_2 for which the items described above are assumed has been successfully received (560).
A UE may apply one joint TCI state indicated through a MAC-CE or DCI to reception for control resource sets connected to all UE-specific search spaces, reception of a PDSCH scheduled by a PDCCH transmitted from the control resource sets and transmission of a PUSCH, and transmission of all PUCCH resources.
If one separate TCI state set indicated through a MAC-CE or DCI includes one DL TCI state, a UE may apply the one separate TCI state set to reception for control resource sets connected to all UE-specific search spaces and to reception of a PDSCH scheduled by a PDCCH transmitted from the control resource sets, and apply a previously indicated UL TCI state to all PUSCH and PUCCH resources.
If one separate TCI state set indicated through a MAC-CE or DCI includes one UL TCI state, a UE may apply the one separate TCI state set to all PUSCH and PUCCH resources, and apply a previously indicated DL TCI state to reception for control resource sets connected to all UE-specific search spaces and reception of a PDSCH scheduled by a PDCCH transmitted from the control resource sets.
If one separate TCI state set indicated through a MAC-CE or DCI includes one DL TCI state and one UL TCI state, a UE may apply the DL TCI state to reception for control resource sets connected to all UE-specific search spaces and reception of a PDSCH scheduled by a PDCCH transmitted from the control resource sets, and apply the UL TCI state to all PUSCH and PUCCH resources.
Hereinafter, a single TCI state indication and activation method based on a unified TCI scheme is described. A PDSCH including a MAC-CE described below may be scheduled to a UE by a base station, and the UE may interpret each codepoint of a TCI state field in DCI format 1_1 or 1_2, based on information in the MAC-CE received from the base station, after 3 slots from transmission of a HARQ-ACK for the PDSCH to the base station. That is, the UE may activate each entry of the MAC-CE received from the base station in each codepoint of the TCI state field in DCI format 1_1 or 1_2.
With respect to the MAC-CE structure of
Next, downlink control information (DCI) in a 5G communication system will be described in detail.
In a 5G system, scheduling information regarding uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) is included in DCI and transferred from a base station to a UE through the DCI. The UE may monitor, with regard to the PUSCH or PDSCH, a fallback DCI format and a non-fallback DCI format. The fallback DCI format may include a fixed field predefined between the base station and the UE, and the non-fallback DCI format may include a configurable field.
The DCI may be subjected to channel coding and modulation processes and then transmitted through a physical downlink control channel (PDCCH) after a channel coding and modulation process. A cyclic redundancy check (CRC) may be attached to the payload of a DCI message, and the CRC may be scrambled by a radio network temporary identifier (RNTI) corresponding to the identity of the UE. Different RNTIs may be used according to the purpose of the DCI message, for example, UE-specific data transmission, power control command, or random access response. That is, the RNTI may not be explicitly transmitted, but may be transmitted while being included in a CRC calculation process. Upon receiving a DCI message transmitted through the PDCCH, the UE may identify the CRC by using the allocated RNTI, and if the CRC identification result is right, the UE may know that the corresponding message has been transmitted to the UE.
For example, DCI for scheduling a PDSCH regarding system information (SI) may be scrambled by an SI-RNTI. DCI for scheduling a PDSCH regarding a random access response (RAR) message may be scrambled by an RA-RNTI. DCI for scheduling a PDSCH regarding a paging message may be scrambled by a P-RNTI. DCI for notifying of a slot format indicator (SFI) may be scrambled by an SFI-RNTI. DCI for notifying of transmit power control (TPC) may be scrambled by a TPC-RNTI. DCI for scheduling a UE-specific PDSCH or PUSCH may be scrambled by a cell RNTI (C-RNTI).
DCI format 0_0 may be used as fallback DCI for scheduling a PUSCH, and in this case, the CRC may be scrambled by a C-RNTI. DCI format 0_0 in which the CRC is scrambled by a C-RNTI may include the following pieces of information given in Table 4 below, for example.
DCI format 0_1 may be used as non-fallback DCI for scheduling a PUSCH, and in this case, the CRC may be scrambled by a C-RNTI. DCI format 0_1 in which the CRC is scrambled by a C-RNTI may include the following pieces of information given in Table 5 below, for example.
DCI format 1_0 may be used as fallback DCI for scheduling a PDSCH, and in this case, the CRC may be scrambled by a C-RNTI. DCI format 1_0 in which the CRC is scrambled by a C-RNTI may include the following pieces of information given in Table 6 below, for example.
DCI format 1_1 may be used as non-fallback DCI for scheduling a PDSCH, and in this case, the CRC may be scrambled by a C-RNTI. DCI format 1_1 in which the CRC is scrambled by a C-RNTI may include the following pieces of information given in Table 7 below, for example.
Hereinafter, a downlink control channel in a 5G communication system will be described in more detail with reference to the accompanying drawings.
A control resource set in 5G described above may be configured for a U by a base station through upper layer signaling (for example, system information, master information block (MIB), radio resource control (RRC) signaling). The description that a control resource set is configured for a UE means that information such as a control resource set identity, the control resource set's frequency location, and the control resource set's symbol duration is provided. For example, this information may include the following pieces of information given in Table 8 below.
In Table 8, tci-StatesPDCCH (simply referred to as transmission configuration indication (TCI) state) configuration information may include information of one or multiple SS/PBCH block indexes or channel state information reference signal (CSI-RS) indexes, which are quasi-co-located (OCLed) with a DMRS transmitted in a corresponding CORESET.
Provided that the basic unit of downlink control channel allocation in 5G is a control channel element 804 as illustrated in
The basic unit of the downlink control channel illustrated in
Search spaces may be classified into common search spaces and UE-specific search spaces. A group of UEs or all UEs may search a common search space of the PDCCH in order to receive cell-common control information such as dynamic scheduling regarding system information or a paging message. For example, PDSCH scheduling allocation information for transmitting an SIB including a cell operator information or the like may be received by searching the common search space of the PDCCH. In the case of a common search space, a group of UEs or all UEs need to receive the PDCCH, and the common search space may thus be defined as a predetermined set of CCEs. Scheduling allocation information regarding a UE-specific PDSCH or PUSCH may be received by searching the UE-specific search space of the PDCCH. The UE-specific search space may be defined UE-specifically as a function of various system parameters and the identity of the U.
In 5G, parameters for a search space regarding a PDCCH may be configured for the UE by the base station through upper layer signaling (for example, SIB, MIB, or RRC signaling). For example, the base station may provide the U with configurations such as the number of PDCCH candidates at each aggregation level L, the monitoring cycle regarding the search space, the monitoring occasion with regard to each symbol in a slot regarding the search space, the search space type (common search space or U-specific search space), a combination of an RNTI and a DCI format to be monitored in the corresponding search space, a control resource set index for monitoring the search space, and the like. For example, the information configured for the UE by the base station may include the following pieces of information in Table 9 below.
According to configuration information, the base station may configure one or multiple search space sets for the UE. According to an embodiment, the base station may configure search space set 1 and search space set 2 for the UE, may configure DCI format A scrambled by an X-RNTI to be monitored in a common search space in search space set 1, and may configure DCI format B scrambled by a Y-RNTI to be monitored in a UE-specific search space in search space set 2.
According to configuration information, one or multiple search space sets may exist in a common search space or a UE-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 UE-specific search space.
Combinations of DCI formats and RNTIs given below may be monitored in a common search space. Of course, the combinations of DCI formats and RNTIs monitored in a common search space are not limited to the examples given below:
Combinations of DCI formats and RNTIs given below may be monitored in a UE-specific search space. Obviously, the examples given below are not limiting:
Enumerated RNTIs may follow the definition and usage given below:
The DCI formats enumerated above may follow the definitions given in Table 10 below, for example.
In 5G, the search space at aggregation level L in connection with CORESET p and search space set s may be expressed by Equation 1 below.
The
value may correspond to a value changed by the UE's identity (C-RNTI or ID configured for the UE by the base station) and the time index in the case of a UE-specific search space.
In 5G, multiple search space sets may be configured by different parameters (for example, parameters in Table 9), and the group of search space sets monitored by the UE at each timepoint may differ accordingly. For example, if search space set #1 is configured at by X-slot cycle, if search space set #2 is configured at by Y-slot cycle, and if X and Y are different, the UE may monitor search space set #1 and search space set #2 both in a specific slot, and may monitor one of search space set #1 and search space set #2 both in another specific slot.
In an NR system, a UE may transmit control information (UCI) to a base station through a PUCCH. The control information may include at least one of a HARQ-ACK indicating whether the UE has succeeded in demodulating/decoding a transport block (TB) having been received through a PDSCH, a scheduling request (SR) through which the UE requests a PUSCH base station to allocate resources for uplink data transmission, and channel state information (CSI) that is information for reporting a channel state of the UE.
PUCCH resources may be generally classified as for a long PUCCH and a short PUCCH according to the length of allocated symbols. In an NR system, a long PUCCH has a length of 4 or more symbols in a slot, and a short PUCCH has a length of 2 or less symbols in a slot.
In a more detailed description of a long PUCCH, a long PUCCH may be used for the purpose of increasing uplink cell coverage, and thus may be transmitted in a DFT-S-OFDM scheme relating to single carrier transmission rather than OFDM transmission. A long PUCCH supports transmission formats, such as PUCCH format 1, PUCCH format 3, and PUCCH format 4, according to the number of supportable control information bits, and support or nonsupport of UE multiplexing through pre-DFT OCC support at an IFFT front end.
First, PUCCH format 1 is a DFT-S-OFDM-based long PUCCH format capable of supporting control information up to 2 bits, and uses as many frequency resources as 1 RB. The control information may be configured by a HARQ-ACK, an SR, or a combination thereof. PUCCH format 1 has a structure in which an OFDM symbol including a demodulation reference signal (DMRS) that is a demodulation reference signal (or reference signal) and an OFDM symbol including UCI are repeated.
For example, if the number of transmission symbols of PUCCH format 1 is 8, the 8 symbols may be configured by a DMRS symbol, a UCI symbol, a DMRS symbol, a UCI symbol, a DMRS symbol, a UCI symbol, a DMRS symbol, and a UCI symbol sequentially starting from the first starting symbol. DMRS symbols may be spread using an orthogonal code (or orthogonal sequence or spreading code, wi(m)) on the time axis for a sequence corresponding to the length of 1 RB on the frequency axis in one OFDM symbol, may be subject to IFFT, and then be transmitted.
In relation to UCI symbols, the UE may perform BPSK modulation of 1-bit control information or QPSK modulation of 2-bit control information to generate d(0), multiply the generated d(0) by a sequence corresponding to the length of 1 RB on the frequency axis to scramble same, spread the scrambled sequence by using an orthogonal code (or orthogonal sequence or spreading code, wi(m)) on the time axis, perform IFFT of the spread sequence, and then transmit same.
The UE generates a sequence, based on a group hopping or sequence hopping configuration and a configured ID configured by the base station through higher layer signaling, and performs a cyclic shift of the generated sequence by using an initial cyclic shift (CS) value configured through a higher signal to generate a sequence corresponding to the length of 1 RB.
wi(m) is determined such as
when the length (NSF) of a spreading code is given and, specifically, is given as shown in [Table 11] below. i means the index of the spreading code itself, and m denotes the index of each element of the spreading code. Herein, the numbers in the square brackets [ ] in [Table 11] indicate φ(m), and if the length of a spreading code is 2 and the configured index i of the spreading code is 0 (i=0), the spreading code wi(m) becomes wi(0)=ej2π·0/N
Next, PUCCH format 3 is a DFT-S-OFDM-based long PUCCH format capable of supporting control information greater than 2 bits, and the number of used RBs is configurable through a higher layer. The control information may be configured by a combination or each of a HARQ-ACK, an SR, and CSI. DMRS symbol positions in PUCCH format 3 are present in [Table 12] below according to whether there is frequency hopping in a slot, and whether an additional DMRS symbol is configured.
If the number of transmission symbols of PUCCH format 3 is 8, a DMRS is transmitted on a first symbol and a fifth symbol when the 0-th symbol is used as the first starting symbol of the 8 symbols. [Table 12] is applied even to DMRS symbol positions of PUCCH format 4 in the same way.
Next, PUCCH format 4 is a DFT-S-OFDM-based long PUCCH format capable of supporting control information greater than 2 bits, and uses as many frequency resources as 1 RB. The control information may be configured by a combination or each of a HARQ-ACK, an SR, and CSI. The difference between PUCCH format 4 and PUCCH format 3 is that, in a case of PUCCH format 4, PUCCH formats 4 of several UEs are multiplexable in one RB. It is possible to multiplex PUCCH formats 4 of multiple UEs through pre-DFT orthogonal cover code (OCC) application to control information at an IFFT front end. However, the number of control information symbols transmittable by one UE is reduced according to the number of multiplexed UEs. The number of multiplexable UEs, that is, the number of available different OCCs may be 2 or 4, and the number of OCCs and OCC indexes to be applied may be configured through a higher layer.
Next, short PUCCHs are described. A short PUCCH may be transmitted on both a downlink-centric slot and an uplink-centric slot, and in general, may be transmitted on the last symbol of a slot or an OFDM symbol positioned in a back part (e.g., the last OFDM symbol, the second last OFDM symbol, or the last two OFDM symbols). It is also possible for a short PUCCH to be transmitted on a random position in a slot. A short PUCCH may be transmitted using one OFDM symbol or two OFDM symbols. A short PUCCH may be used to shorten a delay time, compared to a long PUCCH, in a situation where uplink cell coverage is good, and may be transmitted in a CP-OFDM scheme.
A short PUCCH may support transmission formats, such as PUCCH format 0 and PUCCH format 2, according to the number of supportable control information bits. First, PUCCH format 0 is a short PUCCH format capable of supporting control information up to 2 bits, and uses as many frequency resources as 1 RB. The control information may be configured by a combination or each of a HARQ-ACK and an SR. PUCCH format 0 has a structure of not transmitting a DMRS and transmitting only a sequence mapped to 12 subcarriers on the frequency axis in one OFDM symbol. The UE may generate a sequence, based on a group hopping or sequence hopping configuration and a configured ID configured by the base station through a higher signal, perform a cyclic shift (CS) of the generated sequence by using a final CS value obtained after adding, to an indicated initial CS value, a CS value varying according to an ACK or NACK, map the sequence to 12 subcarriers, and transmit the mapped sequence.
For example, in a case where a HARQ-ACK has 1 bit, as shown in [Table 13] below, if the HARQ-ACK is an ACK, the UE may generate the final CS by adding 6 to the initial CS value, and if the HARQ-ACK is a NACK, the UE may generate the final CS by adding 0 to the initial CS. The value of 0 that is a CS value for NACK and the value of 6 that is a CS value for ACK are defined in a specification, and the UE may generate PUCCH format 0 according to the values defined in the specification to transmit a 1-bit HARQ-ACK.
For example, in a case where a HARQ-ACK has 2 bits, as shown in [Table 1] below, the UE may add 0 to the initial CS value if the HARQ-ACK is (NACK, NACK), add 3 to the initial CS value if the HARQ-ACK is (NACK, ACK), add 6 to the initial CS value if the HARQ-ACK is (ACK, ACK), and add 9 to the initial CS value if the HARQ-ACK is (ACK, NACK). The value of 0 that is a CS value for (NACK, NACK), the value of 3 that is a CS value for (NACK, ACK), the value of 6 that is a CS value for (ACK, ACK), and the value of 9 that is a CS value for (ACK, NACK) are defined in a specification, and the UE may generate PUCCH format 0 according to the values defined in the specification to transmit a 2-bit HARQ-ACK. If the final CS value exceeds 12 due to the CS value added to the initial CS value according to an ACK or NACK, since length of the sequence is 12, modulo 12 may be applied to the final CS value.
Next, PUCCH format 2 is a short PUCCH format supporting control information greater than 2 bits, and the number of used RBs may be configured through a higher layer. The control information may be configured by a combination or each of a HARQ-ACK, an SR, and CSI. If the index of a first subcarrier is #0, PUCCH format 2 may be fixed to subcarriers having indexes of #1, #4, #7, and #10 as the positions of subcarriers on which a DMRS is transmitted in one OFDM symbol. The control information may undergo channel coding and then a modulation process to be mapped to the remaining subcarriers except the subcarriers on which the DMRS is positioned.
In summary, configurable values for each PUCCH format described above and the ranges thereof may be organized as shown in [Table 15] below. Values not required to be configured are represented by N.A. in [Table 15] below.
For uplink coverage improvement, multi-slot repeated transmission may be supported for PUCCH formats 1, 3, and 4, and PUCCH repeated transmission may be configured for each PUCCH format. The UE may perform repeated transmission of a PUCCH including UCI as many times as the number of slots configured through the higher layer signaling nrofSlots. For PUCCH repeated transmission, a PUCCH transmission on each slot is performed using the same number of consecutive symbols, and the number of consecutive symbols may be configured through nrofSymbols in the higher layer signaling PUCCH-format1, PUCCH-format3, or PUCCH-format4. For PUCCH repeated transmission, a PUCCH transmission on each slot is performed using the same starting symbol, and the starting symbol may be configured through startingSymbolIndex in the higher layer signaling PUCCH-format1, PUCCH-format3, or PUCCH-format4. For PUCCH repeated transmission, single PUCCH-spatialRelationlnfo may be configured for a single PUCCH resource. For PUCCH repeated transmission, if the UE is configured to perform frequency hopping between PUCCH transmissions on different slots, the UE may perform frequency hopping in a unit of a slot. In addition, if the UE is configured to perform frequency hopping between PUCCH transmissions on different slots, the UE may start a PUCCH transmission on an even-numbered slot at a first PRB index configured through the higher layer signaling startingPRB, and start a PUCCH transmission on an odd-numbered slot at a second PRB index configured through the higher layer signaling secondHopPRB. Additionally, if the UE is configured to perform frequency hopping between PUCCH transmissions on different slots, the index of a slot indicated for the UE to perform a first PUCCH transmission thereon is 0, and through a configured entire PUCCH repeated transmission count, a PUCCH repeated transmission count value may be increased independently of whether PUCCH transmission is performed on each slot. If the UE is configured to perform frequency hopping between PUCCH transmissions on different slots, the UE does not expect that frequency hopping in a slot at the time of PUCCH transmission is configured. If performing frequency hopping between PUCCH transmissions on different slots is not configured for the UE and frequency hopping in a slot is configured, the first and second PRB indexes may also be identically applied in the slot. If the number of uplink symbols on which PUCCH transmission is possible is smaller than a number indicated by nrofSymbols configured through higher layer signaling, the UE may not transmit a PUCCH. Even if the UE has failed PUCCH transmission on a slot for a reason during PUCCH repeated transmission, the UE may increase the PUCCH repeated transmission count.
In NR Release 17, the number of slots for repeated transmission of each PUCCH resource in PUCCH-ResourceExt that is an expansion of the higher layer signaling PUCCH-Resource for PUCCH resources may be configured through the higher layer signaling pucch-RepetitionNrofSlots-r17. If the higher layer signaling pucch-RepetitionNrofSlots-r17 is configured, a corresponding PUCCH is configured, and the higher layer signaling nrofSlots is also configured, the UE may determine the number of slots on which the corresponding PUCCH is repeatedly transmitted through pucch-RepetitionNrofSlots-r17, and disregard the higher layer signaling nrofSlots.
Next, a PUCCH resource configuration of a base station or a UE is described. The base station may be able to configure a PUCCH resource for each BWP for a particular UE through a higher layer. A PUCCH resource configuration may be as shown in [Table 16] below.
According to [Table 16], one or multiple PUCCH resource sets may be configured in a PUCCH resource configuration for a particular BWP, and a maximum payload value for UCI transmission may be configured for some of the PUCCH resource sets. One or multiple PUCCH resources may belong to each PUCCH resource set, and each PUCCH resource may belong to one of the PUCCH formats described above.
With respect to the PUCCHresource sets, a maximumpayload value of the first PUCCH resource set may be fixed to 2 bits. Accordingly, the value may not be separately configuredthrough ahigherlayer. Ifthe remaining PUCCHresource sets are configured, the index of a corresponding PUCCH resource set may be configured in an ascending order according to the maximum payload value, and no maximum payload value may be configured for the last PUCCH resource set. A higher layer configuration for a PUCCH resource set may be as shown in [Table 17] below.
The parameter resourceList in [Table 17] may include IDs of PUCCH resources belonging to a PUCCH resource set.
At the time of initial access, or if a PUCCH resource set is not configured, a PUCCH resource set, as shown in [Table 18] below, configured by multiple PUCCH resources which are cell-specific in an initial BWP, may be used. A PUCCH resource to be used for initial access in the PUCCH resource set may be indicated through SIB1.
A maximum payload of each of PUCCH resources included in the PUCCH resource set may be 2 bits in a case of PUCCH format 0 or 1, and may be determined according to a symbol length, the number of PRBs, and a maximum code rate in a case of the remaining formats. The symbol length and the number of PRBs may be configured for each PUCCH resource, and the maximum code rate may be configured for each PUCCH format.
Next, PUCCH resource selection for UCI transmission is described. In a case of SRtransmission, a PUCCH resource for an SR corresponding to schedulingRequestID as shown in [Table 19] below may be configured through a higher layer. The PUCCH resource may be a resource belonging to PUCCH format 0 or PUCCH format 1.
A transmission period and an offset of the configured PUCCH resource may be configured through the parameter periodicityAndOffset in [Table 19]. If there is uplink data to be transmitted by the UC at a time point corresponding to the configured period and offset, the PUCCH resource is transmitted, and otherwise, the PUCCH resource may not be transmitted.
In a case of CSI transmission, a PUCCH resource on which a periodic CSI report or a semi-persistent CSI report through a PUCCH is to be transmitted may be configured in the parameter pucch-CSI-ResourceList as shown in [Table 20] below. The parameter pucch-CSI-ResourceList may include a list of PUCCH resources for each BWP for a cell or CC on which the CSI report is to be transmitted. The PUCCH resource may be a resource belonging to PUCCH format 2, PUCCH format 3, or PUCCH format 4. A transmission period and an offset of the PUCCH resource may be configured through reportSlotConfig in [Table 20].
In a case of HARQ-ACK transmission, a resource set of PUCCH resources to be transmitted may be first selected according to a payload of UCI including the HARQ-ACK. That is, PUCCH resource set having a minimum payload not smaller than that of the UCI payload may be selected. Next, a PUCCH resource in the PUCCH resource set may be selected through a PUCCH resource indicator (PRI) in DCI scheduling a TB corresponding to the HARQ-ACK, and the PRI may be a PUCCH resource indicator specified in [Table 6] or [Table 7]. A relation between a PRI and a PUCCH resource selected in the PUCCH resource set may be as shown in [Table 21] below.
If the number of PUCCH resources in a selected PUCCH resource set is greater than 8, a PUCCH resource may be selected by [Equation 2] below.
In [Equation 2], rPUCCH denotes the index of the selected PUCCH resource in the PUCCH resource set, RPUCCH denotes the number of the PUCCH resources belonging to the PUCCH resource set, ΔPRI denotes a PRI value, NCCE,p denotes a total number of CCEs of CORESET p to which reception DCI belongs, and nCCE,p denotes the index of a first CCE for the reception DCI.
A time point at which the PUCCH resource is transmitted is a time point after K1 slots after transmission of a TB corresponding to the HARQ-ACK. A candidate of the K1 value is configured through a higher layer and, more specifically, may be configured in the parameter dl-DataToUL-ACK in PUCCH-Config specified in [Table 16]. One K1 value among these candidates may be selected by a PDSCH-to-HARQ feedback timing indicator in DCI scheduling a TB, and the value may be a value specified in [Table 5] or [Table 6]. The unit of the K1 value may be a unit of a slot or a unit of a subslot. Here, a subslot is a length unit smaller than a slot, and one subslot may be configured by one or multiple symbols.
Next, a case where two or more PUCCH resources are positioned in one slot is described. A UE may transmit UCI through one or two PUCCH resources in one slot or subslot, and when UCI is transmitted through two PUCCH resources in one slot/subslot, i) each PUCCH resource does not overlap in a unit of a symbol, and ii) at least one PUCCH resource may be a short PUCCH. The UE may not expect to transmit multiple PUCCH resources for HARQ-ACK transmission in one slot.
Next, an uplink transmission beam configuration to be used in PUCCH transmission is described. If a UE does not have a UE-specific configuration (dedicated PUCCH resource configuration) for a PUCCH resource configuration, a PUCCH resource set is provided through the higher layer signaling pucch-ResourceCommon, and a beam configuration for PUCCH transmission follows a beam configuration used in PUSCH transmission scheduled through a random access response (RAR) UL grant. If the UE has a UE-specific configuration (dedicated PUCCH resource configuration) for a PUCCH resource configuration, a beam configuration for PUCCH transmission may be provided through the higher signaling pucch-spatialRelationInfold included in [Table 16]. If one value of pucch-spatialRelationInfold is configured for the UE, a beam configuration for PUCCH transmission of the UE may be provided through the one value of pucch-spatialRelationInfold. If multiple values of pucch-spatialRelationInfoID are configured for the UE, activation of one value of pucch-spatialRelationInfoID among the multiple values may be indicated to the UE through a MAC control element (CE). A maximum of 8 values of pucch-spatialRelationInfoID may be configured for the UE through higher signaling, and only one value of pucch-spatialRelationInfoID among the 8 values being activated may be indicated thereto. If activation of a random value of pucch-spatialRelationInfoID is indicated to the UE through a MAC CE, the UE may apply pucch-spatialRelationInfoID activation through the MAC CE starting from a slot first appearing after 3Nslotsubframe,μ, slots after a slot transmitting a HARQ-ACK for a PDSCH transmitting the MAC CE containing activation information on pucch-spatialRelationInfoID. μ is a numerology applied to PUCCH transmission, and Nslotsubframe,μ, indicates the number of slots per subframe at the given numerology. A higher layer configuration for pucch-spatialRelationlnfo may be as shown in [Table 22] below.
According to [Table 22], one referenceSignal configuration may exist in a particular pucch-spatialRelationlnfo configuration, the referenceSignal may be ssb-Index indicating a particular SS/PBCH, csi-RS-Index indicating a particular CSI-RS, or srs indicating a particular SRS. If referenceSignal is configured to be ssb-Index, the UE may configure, as a beam for PUCCH transmission, a beam used when an SS/PBCH corresponding to the ssb-Index is received among SS/PBCHs in the same serving cell, or when servingCellld is provided, the UE may configure, as abeam for PUCCH transmission, abeam used when an SS/PBCH corresponding to the ssb-Index is received among SS/PBCHs in a cell indicated by the servingCellld. If referenceSignal is configured to be csi-RS-Index, the UE may configure, as a beam for PUCCH transmission, a beam used when a CSI-RS corresponding to the csi-RS-Index is received among CSI-RSs in the same serving cell, or when servingCellld is provided, the UE may configure, as a beam for PUCCH transmission, a beam used when a CSI-RS corresponding to the csi-RS-Index is received among CSI-RSs in a cell indicated by the servingCellId. If referenceSignal is configured to be srs, the UE may configure, as a beam for PUCCH transmission, a transmission beam used when an SRS corresponding to a resource index provided through a higher signaling resource is transmitted in the same serving cell and/or in an activated uplink BWP, or when servingCellID and/or uplinkBWP is provided, the UE may configure, as a beam for PUCCH transmission, a transmission beam used when an SRS corresponding to a resource index provided through a higher signaling resource is transmitted in a cell and/or in an uplink BWP indicated by the servingCellID and/or uplinkBWP. There may be one pucch-PathlossReferenceRS-Id configuration in a particular pucch-spatialRelationlnfo configuration. PUCCH-PathlossReferenceRS in [Table 23] may be mapped to pucch-PathlossReferenceRS-Id in [Table 22], and a maximum of four values are configurable through pathlossReferenceRSs in the higher signaling PUCCH-PowerControl in [Table 23]. If PUCCH-PathlossReferenceRS is connected to an SS/PBCH through the higher signaling referenceSignal, ssb-Index may be configured, and if same is connected to a CSI-RS, csi-RS-Index may be configured.
As an embodiment of the disclosure, a method of, when uplink control information is transmitted through an uplink control channel (physical uplink control channel, PUCCH) in response to a power control command received from a base station, configuring and transmitting the transmission power of the uplink control channel by a UE will be described. Uplink control channel transmission power (PPUCCH) of the UE may be determined as [Equation 3] below expressed by a unit of dBm together with a PUCCH power control adjustment state corresponding to the i-th transmission unit and closed loop index 1. In [Equation 3] below, when the UE supports multiple carrier frequencies in multiple cells, each parameter may be determined by primary cell c, carrier frequency f, and bandwidth part b, and may be distinguished by the indexes b, f, and c.
The PUCCH power control adjustment state gb,f,c(i, l) may be determined through bandwidth part b, carrier frequency f, primary cell c, the i-th transmission unit, and closed loop index 1.
Next, a PUSCH transmission scheduling scheme will be described. PUSCH transmission may be dynamically scheduled by a UL grant inside DCI, or operated by means of configured grant Type 1 or Type 2. Dynamic scheduling indication regarding PUSCH transmission may be made by DCI format 0_0 or 0_1.
Configured grant Type 1 PUSCH transmission may be configured semi-statically by receiving configuredGrantConfig including rrc-ConfiguredUplinkGrant in Table 24 through upper signaling, without receiving a UL grant inside DCI. Configured grant Type 2 PUSCH transmission may be scheduled semi-persistently by a UL grant inside DCI after receiving configuredGrantConfig not including rrc-ConfiguredUplinkGrant in Table 24 through upper signaling. If PUSCH transmission is operated by a configured grant, parameters applied to the PUSCH transmission are applied through configuredGrantConfig (upper signaling) in Table 24 except for dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH, which are provided by pusch-Config (upper signaling) in Table 25. If provided with transformPrecoder inside configuredGrantConfig (upper signaling) in Table 24, the UE applies tp-pi2BPSK inside pusch-Config in Table 25 to PUSCH transmission operated by a configured grant.
Next, a PUSCH transmission method will be described. The DMRS antenna port for PUSCH transmission is identical to an antenna port for SRS transmission. PUSCH transmission may follow a codebook-based transmission method and a non-codebook-based transmission method according to whether the value of txConfig inside pusch-Config in Table 25, which is upper signaling, is “codebook” or “nonCodebook.”
As described above, PUSCH transmission may be dynamically scheduled through DCI format 0_0 or 0_1, and may be semi-statically configured by a configured grant. Upon receiving indication of scheduling regarding PUSCH transmission through DCI format 0_0, the UL performs beam configuration for PUSCH transmission by using pucch-spatialRelationInfoID corresponding to a UL-specific PUCCH resource corresponding to the minimum ID inside an activated uplink BWP inside a serving cell, and the PUSCH transmission is based on a single antenna port. The UL does not expect scheduling regarding PUSCH transmission through DCI format 0 0 inside a BWP having no configured PUCCH resource including pucch-spatialRelationlnfo. If the UL has no configured txConfig inside pusch-Config in Table 25, the UL does not expect scheduling through DCI format 0_1.
Next, codebook-based PUSCH transmission will be described. The codebook-based PUSCH transmission may be dynamically scheduled through DCI format 0_0 or 0_1, and may be operated semi-statically by a configured grant. If a codebook-based PUSCH is dynamically scheduled through DCI format 0_1 or configured semi-statically by a configured grant, the UE determines a precoder for PUSCH transmission, based on an SRS resource indicator (SRI), a transmission precoding matrix indicator (TPMI), and a transmission rank (the number of PUSCH transmission layers).
The SRI may be indicated through the SRS resource indicator (a field inside DCI) or configured through srs-ResourceIndicator (upper signaling). During codebook-based PUSCH transmission, the UE has at least one SRS resource configured therefor, and may have a maximum of two SRS resources configured therefor. If the UE is provided with the SRI through DCI, the SRS resource indicated by the corresponding SRI refers to the SRS resource corresponding to the SRI, among SRS resources transmitted prior to the PDCCH including the corresponding SRI. In addition, the TPMI and the transmission rank may be given through “precoding information and number of layers” (a field inside DCI) or configured through precodingAndNumberOfLayers (upper signaling). The TPMI is used to indicate a precoder to be applied to PUSCH transmission. If multiple SRS resources are configured for the UE, the TPMI is used to indicate a precoder to be applied in an SRS resource indicated through the SRI. If multiple SRS resources are configured for the UE, the TPMI is used to indicate a precoder to be applied in an SRS resource indicated through the SRI.
The precoder to be used for PUSCH transmission is selected from an uplink codebook having the same number of antenna ports as the value of nrofSRS-Ports inside SRS-Config (upper signaling). In connection with codebook-based PUSCH transmission, the UE determines a codebook subset, based on codebookSubset inside pusch-Config (upper signaling) and TPMI. The codebookSubset inside pusch-Config (upper signaling) may be configured to be one of “fullyAndPartialAndNonCoherent,” “partialAndNonCoherent,” or “noncoherent,” based on UE capability reported by the UE to the base station. If the UE reported “partialAndNonCoherent” as UE capability, the UE does not expect that the value of codebookSubset (upper signaling) may be configured as “fullyAndPartialAndNonCoherent.” In addition, if the UE reported “nonCoherent” as UE capability, UE does not expect that the value of codebookSubset (upper signaling) may be configured as “fullyAndPartialAndNonCoherent” or “partialAndNonCoherent.” If nrofSRS-Ports inside SRS-ResourceSet (upper signaling) indicates two SRS antenna ports, the UE does not expect that the value of codebookSubset (upper signaling) may be configured as “partialAndNonCoherent.”
The UE may have one SRS resource set configured therefor, wherein the value of usage inside SRS-ResourceSet (upper signaling) is “codebook,” and one SRS resource may be indicated through an SRI inside the corresponding SRS resource set. If multiple SRS resources are configured inside the SRS resource set wherein the value of usage inside SRS-ResourceSet (upper signaling) is “codebook,” the UE expects that the value of nrofSRS-Ports inside SRS-Resource (upper signaling) is identical for all SRS resources.
The UE transmits, to the base station, one or multiple SRS resources included in the SRS resource set wherein the value ofusage is configured as “codebook” according to upper signaling, and the base station selects one from the SRS resources transmitted by the UE and indicates the UE to be able to transmit a PUSCH by using transmission beam information of the corresponding SRS resource. In connection with the codebook-based PUSCH transmission, the SRI is used as information for selecting the index of one SRS resource, and is included in DCI. Additionally, the base station adds information indicating the rank and TPMI to be used by the UE for PUSCH transmission to the DCI. Using the SRS resource indicated by the SRI, the UE may apply, in performing PUSCH transmission, the precoder indicated by the rank and TPMI indicated based on the transmission beam of the corresponding SRS resource, thereby performing PUSCH transmission.
Next, non-codebook-based PUSCH transmission will be described. The non-codebook-based PUSCH transmission may be dynamically scheduled through DCI format 0_0 or 0_1, and may be operated semi-statically by a configured grant. If at least one SRS resource is configured inside an SRS resource set wherein the value of usage inside SRS-ResourceSet (upper signaling) is “nonCodebook,” non-codebook-based PUSCH transmission may be scheduled for the UE through DCI format 0_1.
With regard to the SRS resource set wherein the value of usage inside SRS-ResourceSet (upper signaling) is “nonCodebook,” one connected NZP CSI-RS resource (non-zero power CSI-RS) may be configured for the UE. The UE may calculate 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 an aperiodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of aperiodic SRS transmission in the UE is less than 42 symbols, the UE does not expect that information regarding the precoder for SRS transmission may be updated.
If the configured value of resourceType inside SRS-ResourceSet (upper signaling) is “aperiodic,” the connected NZP CSI-RS is indicated by an SRS request which is a field inside DCI format 0_1 or 1_1. If the connected NZP CSI-RS resource is an aperiodic NZP CSI-RS resource, the existence of the connected NZP CSI-RS may be indicated with regard to the case in which the value of SRS request (a field inside DCI format 0_1 or 11) is not “00.” The corresponding DCI may not indicate cross carrier or cross BWP scheduling. In addition, if the value of SRS request indicates the existence of a NZP CSI-RS, the NZP CSI-RS is positioned in the slot used to transmit the PDCCH including the SRS request field. In this case, TCI states configured for the scheduled subcarrier are not configured as QCL-TypeD.
If there is a periodic or semi-persistent SRS resource set configured, the connected NZP CSI-RS may be indicated through associatedCSI-RS inside SRS-ResourceSet (upper signaling). With regard to non-codebook-based transmission, the UE does not expect that spatialRelationInfo which is upper signaling regarding the SRS resource and associatedCSI-RS inside SRS-ResourceSet (upper signaling) may be configured together.
If multiple SRS resources are configured for the UE, the UE may determine a precoder to be applied to PUSCH transmission and the transmission rank, based on an SRI indicated by the base station. The SRI may be indicated through the SRS resource indicator (a field inside DCI) or configured through srs-ResourceIndicator (upper signaling). Similarly to the above-described codebook-based PUSCH transmission, if the UE is provided with the SRI through DCI, the SRS resource indicated by the corresponding SRI refers to the SRS resource corresponding to the SRI, among SRS resources transmitted prior to the PDCCH including the corresponding SRI. The UE may use one or multiple SRS resources for SRS transmission, and the maximum number of SRS resources that can be transmitted simultaneously in the same symbol inside one SRS resource set and the maximum number of SRS resources are determined by UE capability reported to the base station by the UE. SRS resources simultaneously transmitted by the UE occupy the same RB. The UE configures one SRS port for each SRS resource. There may be only one configured SRS resource set wherein the value of usage inside SRS-ResourceSet (upper signaling) is “nonCodebook,” and a maximum of four SRS resources may be configured for non-codebook-based PUSCH transmission.
The base station may transmit one NZP-CSI-RS connected to the SRS resource set to the UE, and the UE may calculate the precoder to be used when transmitting one or multiple SRS resources inside the corresponding SRS resource set, based on the result of measurement when the corresponding NZP-CSI-RS is received. The UE applies the calculated precoder when transmitting, to the base station, one or multiple SRS resources inside the SRS resource set wherein the configured usage is “nonCodebook,” and the base station selects one or multiple SRS resources from the received one or multiple SRS resources. In connection with the non-codebook-based PUSCH transmission, the SRI may indicate an index that may express one SRS resource or a combination of multiple SRS resources. 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 UE transmits the PUSCH by applying the precoder applied to SRS resource transmission to each layer.
As an embodiment of the disclosure, a method of, when uplink data is transmitted through an uplink data channel (physical uplink shared channel, PUSCH) in response to a power control command received from a base station, configuring and transmitting the transmission power of the uplink data channel by a UE will be described. Uplink data channel transmission power of the UE may be determined as Equation 5 below represented by a unit of dBm together with a PUSCH power control adjustment state corresponding to the i-th transmission unit, parameter set configuration index j, and closed loop index 1. In [Equation 5] below, when the UE supports multiple carrier frequencies in multiple cells, each parameter may be determined by cell c, carrier frequency f, and bandwidth part b, and may be distinguished by the indexes b, f, and c.
The PUSCH power control adjustment state fb,f,c(i, l) may be determined through bandwidth part b, carrier frequency f, cell c, the i-th transmission unit, and closed loop index l.
Power headroom reporting indicates that a UE measures the difference (i.e., this represents the available transmission power of the UE) between the nominal maximum transmission power of the UE (nominal UE maximum transmit power) and estimated power for uplink transmission and transmits the difference to a base station. Power headroom reporting may be used to support power aware packet scheduling. The estimated power for uplink transmission may be estimated power for UL-SCH (PUSCH) transmission per activated serving cell, estimated power for UL-SCH and PUCCH transmission of, in an SpCell, another MAC entity (e.g., E-UTRA MAC entity in EN-DC, NE-DC, and NGEN-DC cases in a 3GPP specification), and estimated power for SRS transmission per activated serving cell. The UE may trigger power headroom reporting if at least one of the following trigger events is satisfied.
Power headroom reporting may be triggered according to trigger events and the UE may determine power headroom reporting according to the following additional conditions.
If one or more events of the trigger events occur and power headroom reporting is triggered, and an uplink transmission resource allocated through downlink control information is able to accommodate a MAC entity for power headroom reporting and a subheader therefor, the UE performs power headroom reporting through the uplink resource. The uplink resource indicates a resource for uplink transmission scheduled by the first uplink grant or the first downlink control information format (first DCI format) scheduling the initial transmission of a transport block (TB) after power headroom triggering. That is, after a power headroom trigger occurs, the UE may perform power headroom reporting through an uplink transmission scheduled by the first uplink grant or the first downlink control information format among uplink resources which are able to accommodate a MAC entity for a power headroom and a subheader therefor. Alternatively, after a power headroom trigger occurs, the UE may perform power headroom reporting through a configured grant PUSCH transmission which are able to accommodate a MAC entity for a power headroom and a subheader therefor.
The UE may, at the time of power headroom reporting for a particular cell, select, calculate, and report one of two types of pieces of power headroom information. The first type is an actual PHR and is power headroom information calculated based on the transmission power of an actually transmitted uplink signal (e.g., PUSCH). The second type is a virtual PHR (or reference format) and is power headroom information calculated based on a transmission power parameter configured in a higher layer although there is no uplink signal (e.g., PUSCH) actually transmitted. After power headroom reporting is triggered, the UE may, as described above, calculate an actual PHR, based on higher layer information for periodic/semi-persistent SRS transmission and configured grant transmission and downlink control information received until a time point including a PDCCH monitoring interval in which the first DCI format scheduling a PUSCH, through which a MAC CE including a power headroom report is to be transmitted, is received. If the UE receives downlink control information after a PDCCH monitoring interval in which the first DCI format is received, or determines a periodic/semi-persistent SRS transmission or configured grant transmission, the UE may calculate a virtual PHR for a corresponding cell. Alternatively, after power headroom reporting is triggered, the UE may calculate an actual PHR, based on higher layer information for periodic/semi-persistent SRS transmission and configured grant transmission and downlink control information received until a time point before T′proc,2=Tproc,2 corresponding to a PUSCH preparation process time described above with respect to the first uplink symbol of a configured grant PUSCH through which transmission of corresponding power headroom information is possible. If the UE receives downlink control information after a time point before T′proc,2 with respect to the first uplink symbol of a configured grant PUSCH, or determines a periodic/semi-persistent SRS transmission or configured grant transmission, the UE may calculate a virtual PHR for a corresponding cell.
If the UE calculates an actual PHR with respect to actual PUSCH transmission, power headroom reporting information for support cell c, carrier f, bandwidth part b, and PUSCH transmission time point i may be expressed as shown in [Equation 8] below.
As another example, if the UE calculates a virtual PHR, based on a transmission power parameter configured in a higher layer, power headroom reporting information for support cell c, carrier f, bandwidth part b, and PUSCH transmission time point i may be expressed as shown in [Equation 9] below.
According to [Equation 8] above, power headroom information may be calculated by using the difference between transmission power for PUSCH transmission occasion i and maximum output power. According to [Equation 9], power headroom information may be calculated by using the difference between {tilde over (P)}CMAx,f,c(i), which is maximum output power when it is assumed that a parameter (e.g., MPR, A-MPR (Additional MPR), P-MPR (Power Management MPR), etc.) related to maximum power reduction (MPR) and ΔTc are 0, and reference PUSCH transmission power using a default transmission power parameter (e.g., P0_NOMINAL_PUSCH,f,c(0), p0 and alpha of P0-PUSCH-AlpahSet having p0-PUSCH-AlphaSetId=0, PLb,f,c(qd) corresponding to pusch-PathlossReferenceRS-Id=0, and a closed loop power adjustment value having closed loop index 1=0). Description of each variable in [Equation 8] and [Equation 9] above may be referenced to the description of the variables in [Equation 5]. A-MPR is an MPR satisfying an additional emission requirement (e.g., when NR freq. band and additionalSpectrumEmission indicated through RRC are combined (Table 6.2.3.1-1A in TS 38.101-1), a network signaling label is identified and an A-MPR value according thereto is defined in Table 6.2.3.1-1 in TS 38.101-1) indicated by a base station through higher layer signaling. P-MPR is a MPR which is an output power reduction of a UE maximally allowed for support cell c (maximum allowed UE output power reduction for serving cell c) and has a purpose of satisfying applicable electromagnetic energy absorption requirements. A-MPR and P-MPR may be referenced to 3GPP specification TS 38.101-1 section 6.2. First type power headroom information in a communication system to which the disclosure is applicable may indicate power headroom information for PUSCH transmission power, second type power headroom information may indicate power headroom information for PUCCH transmission power, and third type power headroom information may indicate power headroom information for SRS transmission power. However, the disclosure is not limited thereto.
If MR-DC or UL-CA is not supported, a base station configures “false” as the higher layer parameter “multiplePHR” for a corresponding UE. This implies that the UE supports power headroom reporting for a PCell through a MAC CE having a single entry as indicated by reference numeral 910 in
If a UE supports multi-RAT dual connectivity (MR-DC) or uplink carrier aggregation (UL-CA), a base station may configure “true” as the higher layer parameter “multiplePHR” for the UE to perform power headroom reporting for each support cell. This implies that the UE supports power headroom reporting for multiple support cells through a MAC CE having multiple entries, such as a first format 1000 or a second format 1002 illustrated in
Next, an uplink channel estimation method using sounding reference signal (SRS) transmission of a UE will be described. The base station may configure at least one SRS configuration with regard to each uplink BWP in order to transfer configuration information for SRS transmission to the UE, and may also configure as least one SRS resource set with regard to each SRS configuration. As an example, the base station and the UE may exchange upper signaling information as follows, in order to transfer information regarding the SRS resource set.
The UE may understand that an SRS resource included in a set of SRS resource indices referred to by an SRS resource set follows the information configured for the SRS resource set.
In addition, the base station and the UE may transmit/receive upper layer signaling information in order to transfer individual configuration information regarding SRS resources. As an example, the individual configuration information regarding SRS resources may include time-frequency domain mapping information inside slots of the SRS resources, and this may include information regarding intra-slot or inter-slot frequency hopping of the SRS resources. The individual configuration information regarding SRS resources may include time domain transmission configuration of SRS resources, and may be configured as one of “periodic,” “semi-persistent,” and “aperiodic” The time domain transmission configuration of SRS resources may be limited to have the same time domain transmission configuration as the SRS resource set including the SRS resources. If the time domain transmission configuration of SRS resources is configured as “periodic” or “semi-persistent,” the time domain transmission configuration may further include an SRS resource transmission cycle and a slot offset (for example, periodicityAndOffset).
The base station may activate or deactivate SRS transmission for the UE through upper layer signaling including RRC signaling or MAC CE signaling, or L1 signaling (for example, DCI). For example, the base station may activate or deactivate periodic SRS transmission for the UE through upper layer signaling. The base station may indicate activation of an SRS resource set having resourceType configured as “periodic” through upper layer signaling, and the UE may transmit the SRS resource referred to by the activated SRS resource set. Intra-slot time-frequency domain resource mapping of the transmitted SRS resource follows resource mapping information configured for the SRS resource, and slot mapping, including the transmission cycle and slot offset, follows periodicityAndOffset configured for the SRS resource. In addition, the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation info configured for the SRS resource, or may refer to associated CSI-RS information configured for the SRS resource set including the SRS resource. The UE may transmit the SRS resource inside the uplink BWP activated with regard to the periodic SRS resource activated through upper layer signaling.
For example, the base station may activate or deactivate semi-persistent SRS transmission for the UE through upper layer signaling. The base station may indicate activation of an SRS resource set through MAC CE signaling, and the UE may transmit the SRS resource referred to by the activated SRS resource set. The SRS resource set activated through MAC CE signaling may be limited to an SRS resource set having resourceType configured as “semi-persistent.” Intra-slot time-frequency domain resource mapping of the transmitted SRS resource follows resource mapping information configured for the SRS resource, and slot mapping, including the transmission cycle and slot offset, follows periodicityAndOffset configured for the SRS resource. In addition, the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation info configured for the SRS resource, or may refer to associated CSI-RS information configured for the SRS resource set including the SRS resource. If the SRS resource has spatial relation info configured therefor, the spatial domain transmission filter may be determined, without following the same, by referring to configuration information regarding spatial relation info transferred through MAC CE signaling that activates semi-persistent SRS transmission. The UE may transmit the SRS resource inside the uplink BWP activated with regard to the semi-persistent SRS resource activated through upper layer signaling.
For example, the base station may trigger aperiodic SRS transmission by the UE through DCI. The base station may indicate one of aperiodic SRS triggers (aperiodicSRS-ResourceTrigger) through the SRS request field of DCI. The UE may understand that the SRS resource set including the aperiodic SRS resource trigger indicated through DCI in the aperiodic SRS resource trigger list, among configuration information of the SRS resource set, has been triggered. The UE may transmit the SRS resource referred to by the triggered SRS resource set. Intra-slot time-frequency domain resource mapping of the transmitted SRS resource follows resource mapping information configured for the SRS resource. In addition, slot mapping of the transmitted SRS resource may be determined by the slot offset between the SRS resource and a PDCCH including DCI, and this may refer to value(s) included in the slot offset set configured for the SRS resource set. Specifically, as the slot offset between the SRS resource and the PDCCH including DCI, a value indicated in the time domain resource assignment field of DCI, among offset value(s) included in the slot offset set configured for the SRS resource set, may be applied. In addition, the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation info configured for the SRS resource, or may refer to associated CSI-RS information configured for the SRS resource set including the SRS resource. The UE may transmit the SRS resource inside the uplink BWP activated with regard to the aperiodic SRS resource triggered through DCI.
If the base station triggers aperiodic SRS transmission by the UE through DCI, a minimum time interval may be necessary between the transmitted SRS and the PDCCH including the DCI that triggers aperiodic SRS transmission, in order for the UE to transmit the SRS by applying configuration information regarding the SRS resource. The time interval for SRS transmission by the UE may be defined as the number of symbols between the last symbol of the PDCCH including the DCI that triggers aperiodic SRS transmission and the first symbol mapped to the first transmitted SRS resource among transmitted SRS resource(s). The minimum time interval may be determined with reference to the PUSCH preparation procedure time needed by the UE to prepare PUSCH transmission. The minimum time interval may have a different value depending on the place ofuse of the SRS resource set including the transmitted SRS resource. For example, the minimum time interval may be determined as N2 symbols defined in consideration of UE processing capability that follows the UE's capability with reference to the UE's PUSCH preparation procedure time. In addition, if the place of use of the SRS resource set is configured as “codebook” or “antennaSwitching” in consideration of the place of use of the SRS resource set including the transmitted SRS resource, the minimum time interval may be determined as N2 symbols, and if the place of use of the SRS resource set is configured as “nonCodebook” or “beamManagement,” the minimum time interval may be determined as N2+14 symbols. The UE may transmit an aperiodic SRS if the time interval for aperiodic SRS transmission is larger than or equal to the minimum time interval, and may ignore the DCI that triggers the aperiodic SRS if the time interval for aperiodic SRS transmission is smaller than the minimum time interval.
Configuration information spatialRelationInfo in Table 29 above may be applied, with reference to one reference signal, to a beam used for SRS transmission corresponding to beam information of the corresponding reference signal. For example, configuration of spatialRelationInfo may include information as in Table 30 below.
Referring to the spatialRelationInfo configuration, an SS/PBCH block index, CSI-RS index, or SRS index may be configured as the index of a reference signal to be referred to in order to use beam information of a specific reference signal. Upper signaling referenceSignal corresponds to configuration information indicating which reference signal's beam information is to be referred to for corresponding SRS transmission, ssb-Index refers to the index of an SS/PBCH block, csi-RS-Index refers to the index of a CSI-RS, and srs refers to the index of an SRS. If upper signaling referenceSignal has a configured value of “ssb-Index,” the UE may apply the reception beam which was used to receive the SS/PBCH block corresponding to ssb-Index as the transmission beam for the corresponding SRS transmission. If upper signaling referenceSignal has a configured value of “csi-RS-Index,” the UE may apply the reception beam which was used to receive the CSI-RS corresponding to csi-RS-Index as the transmission beam for the corresponding SRS transmission. If upper signaling referenceSignal has a configured value of “srs,” the UE may apply the reception beam which was used to transmit the SRS corresponding to srs as the transmission beam for the corresponding SRS transmission.
As an embodiment of the disclosure, a method in which, when a UE performs transmission through an uplink reference signal (sounding reference signal, SRS) in response to a power control command received from a base station, the UE configures the transmission power of the uplink reference signal and transmits same will be described. Uplink reference signal transmission power (PSRS) of the UE may be determined as [Equation 10] below expressed by a unit of dBm together with an SRS power control adjustment state corresponding to the i-th transmission unit and closed loop index 1. In [Equation 10] below, when the UE supports multiple carrier frequencies in multiple cells, each parameter may be determined by cell c, carrier frequency f, and bandwidth part b, and may be distinguished by the indexes b, f, and c.
P0_SRS,b,f,c(qs)-: This may be configured by p0 in SRS-ResourceSet, which is higher layer signaling, for bandwidth part b, carrier frequency f, and cell c, and the SRS resource set qs may be configured through SRS-ResourceSet and SRS-ResourceSetId, which are higher layer signaling.
The SRS power control adjustment state may be determined through bandwidth part b, carrier frequency f, cell c, and the i-th transmission unit.
In LTE and NR, a UE may perform a procedure in which, while being connected to a serving base station, the UE reports capability supported by the UE to the corresponding base station. In the following description, the above-described procedure will be referred to as a UE capability report.
The base station may transfer a UE capability enquiry message to the UE in a connected state so as to request a capability report. The message may include a UE capability request with regard to each radio access technology (RAT) type of the base station. The RAT type-specific request may include supported frequency band combination information and the like. In addition, in the case of the UE capability enquiry message, UE capability with regard to multiple RAT types may be requested through one RRC message container transmitted by the base station, or the base station may transfer a UE capability enquiry message including multiple UE capability requests with regard to respective RAT types. That is, a capability enquiry may be repeated multiple times in one message, and the UE may configure a UE capability information message corresponding thereto and report the same multiple times. In next-generation mobile communication systems, a UE capability request may be made regarding multi-RAT dual connectivity (MR-DC), such as NR, LTE, E-UTRA—NR dual connectivity (EN-DC). The UE capability enquiry message may be transmitted initially after the UE is connected to the base station, in general, but may be requested in any condition if needed by the base station.
Upon receiving the UE capability report request from the base station in the above step, the UE configures UE capability according to band information and RAT type requested by the base station. The method in which the UE configures UE capability in an NR system is summarized below.
1. If the UE receives a list regarding LTE and/or NR bands from the base station at a UE capability request, the UE constructs band combinations (BCs) regarding EN-DC and NR standalone (SA). That is, the UE configures a candidate list of BCs regarding EN-DC and NR SA, based on bands received from the base station at a request through FreqBandList. Bands have priority in the order described in FreqBandList.
2. If the base station sets “eutra-nr-only” flag or “eutra” flag and requests a UE capability report, the UE removes everything related to NR SA BCs from the configured BC candidate list. Such an operation may occur only if an LTE base station (eNB) requests “eutra” capability.
3. The UE then removes fallback BCs from the BC candidate list configured in the above step. As used herein, a fallback BC refers to a BC that can be obtained by removing a band corresponding to at least one SCell from a specific BC, and since a BC before removal of the band corresponding to at least one SCell can already cover a fallback BC, the same can be omitted. This step is applied in MR-DC as well, that is, LTE bands are also applied. BCs remaining after the above step constitute the final “candidate BC list.”
4. The UE selects BCs appropriate for the requested RAT type from the final “candidate BC list” and configures BCs to report. In this step, the UE configures supportedBandCombinationList in a determined order. That is, the UE configures BCs and UE capability to report according to a preconfigured rat-Type order. (nr→eutra-nr→eutra). In addition, the UE configures featureSetCombination regarding the configured supportedBandCombinationList and configures a list of “candidate feature set combinations” from a candidate BC list from which a list regarding fallback BCs (including capability of the same or lower step) is removed. The “candidate feature set combinations” may include all feature set combinations regarding NR and EUTRA-NR BCs, and may be obtained from feature set combinations of containers of UE-NR-Capabilities and UE-MRDC-Capabilities.
5. If the requested RAT type is eutra-nr and has an influence, featureSetCombinations is included on both containers of UE-MRDC-Capabilities and UE-NR-Capabilities. However, the feature set of NR is included only in UE-NR-Capabilities.
After the UE capability is configured, the UE transfers a UE capability information message including the UE capability to the base station. The base station performs scheduling and transmission/reception management appropriate for the UE, based on the UE capability received from the UE.
Hereinafter, embodiments of the disclosure will be described in detail in conjunction with the accompanying drawings. The contents of the disclosure may be applied to FDD and TDD systems. As used herein, upper signaling (or upper layer signaling”) is a method for transferring signals from a base station to a UE by using a downlink data channel of a physical layer, or from the UE to the base station by using an uplink data channel of the physical layer, and may also be referred to as “RRC signaling,” “PDCP signaling,” or “MAC control element (MAC CE).”
Hereinafter, in the disclosure, the UE may use various methods to determine whether or not to apply cooperative communication, for example, PDCCH(s) that allocates a PDSCH to which cooperative communication is applied have a specific format, or PDCCH(s) that allocates a PDSCH to which cooperative communication is applied include a specific indicator indicating whether or not to apply cooperative communication, or PDCCH(s) that allocates a PDSCH to which cooperative communication is applied are scrambled by a specific RNTI, or cooperative communication application is assumed in a specific range indicated by an upper layer. Hereinafter, it will be assumed for the sake of descriptive convenience that NC-JT case refers to a case in which the UE receives a PDSCH to which cooperative communication is applied, based on conditions similar to those described above.
Hereinafter, determining priority between A and B may be variously described as, for example, selecting an entity having a higher priority according to a predetermined priority rule and performing an operation corresponding thereto, or omitting or dropping operations regarding an entity having a lower priority.
Hereinafter, the above examples may be described through several embodiments, but they are not independent of each other, and one or more embodiments may be applied simultaneously or in combination.
Hereinafter, for the sake of descriptive convenience, a cell, a transmission point, a panel, a beam, and/or a transmission direction which can be distinguished through an upper layer/L1 parameter such as a TCI state or spatial relation information, a cell ID, a TRP ID, or a panel ID may be described as a TRP, a beam, or a TCI state as a whole. Therefore, when actually applied, a TRP, a beam, or a TCI state may be appropriately replaced with one of the above terms.
Hereinafter, in the disclosure, the UE may use various methods to determine whether or not to apply cooperative communication, for example, PDCCH(s) that allocates a PDSCH to which cooperative communication is applied have a specific format, or PDCCH(s) that allocates a PDSCH to which cooperative communication is applied include a specific indicator indicating whether or not to apply cooperative communication, or PDCCH(s) that allocates a PDSCH to which cooperative communication is applied are scrambled by a specific RNTI, or cooperative communication application is assumed in a specific range indicated by an upper layer. Hereinafter, it will be assumed for the sake of descriptive convenience that NC-JT case refers to a case in which the UE receives a PDSCH to which cooperative communication is applied, based on conditions similar to those described above.
Hereinafter, embodiments of the disclosure will be described in detail in conjunction with the accompanying drawings. Hereinafter, a base station refers to an entity that allocates resources to a terminal, and may be at least one of a gNode B, a gNB, an eNode B, a node B, a base station (BS), a radio access unit, a base station controller, or a node on a network. A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the following description of embodiments of the disclosure, 5G systems will be described by way of example, but the embodiments of the disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. Examples of such communication systems may include LTE or LTE-A mobile communication systems and mobile communication technologies developed beyond 5G. Therefore, based on determinations by those skilled in the art, the embodiments of the disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the disclosure. The contents of the disclosure may be applied to FDD and TDD systems.
Furthermore, in describing the disclosure, a detailed description of known functions or configurations incorporated herein will be omitted when it is determined that the description may make the subject matter of the disclosure unnecessarily unclear. The terms which will be described below are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the users, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.
In the following description of the disclosure, upper layer signaling may refer to signaling corresponding to at least one signaling among the following signaling, or a combination of one or more thereof:
In addition, L1 signaling may refer to signaling corresponding to at least one signaling method among signaling methods using the following physical layer channels or signaling, or a combination of one or more thereof:
Hereinafter, determining priority between A and B may be variously described as, for example, selecting an entity having a higher priority according to a predetermined priority rule and performing an operation corresponding thereto, or omitting or dropping operations regarding an entity having a lower priority.
As used herein, the term “slot” may generally refer to a specific time unit corresponding to a transmit time interval (TTI), may specifically refer to a slot used in a 5G NR system, or may refer to a slot or a subframe used in a 4G LTE system.
Hereinafter, the above examples may be described through several embodiments, but they are not independent of each other, and one or more embodiments may be applied simultaneously or in combination.
As an embodiment of the disclosure, a method of configuring, for a UE, a transmission power parameter when the UE supports a unified TCI state is described. This embodiment may be operated in combination with other embodiments.
The higher layer signaling ServingCellConfig may be configured for a UE by a base station and, additionally, the higher layer signaling MIMOParam-r17 may be configured in ServingCellConfig for the UE. The detailed higher layer signaling structures of ServingCellConfig and MIMOParam-r17 may be shown in [Table 31] below.
As shown in [Table 31] above, the higher layer signaling unifiedTCI-StateType-r17 may be configured in MIMOParam-r17 for the UE by the base station, and the value may be one of separate or joint.
As shown in [Table 31], the higher layer signaling uplink-PowerControlToAddModList may be configured in MIMOParam-r17 for the UE. The higher layer signaling uplink-PowerControlToAddModList, if the higher layer signaling unifiedTCI-StateType is configured in a corresponding serving cell for the UE, may include transmission power parameters for a PUSCH, a PUCCH, and an SRS for the UE. According to the higher layer signaling uplink-PowerControlToAddModList, a corresponding parameter may include a list of a maximum of 64 values of Uplink-powerControl-r17 and Uplink-powerControlId-r17. The higher layer signaling Uplink-powerControl-r17 may have a structure as shown in [Table 32] below.
As shown in [Table 31], pathlossReferenceLinking may be configured in ServingCellConfig for the UE. The higher layer signaling pathlossReferenceLinking may indicate which of an SpCell or SCell in which the UE refers to a list of reference signals for pathloss amount measurement.
As shown in [Table 32], the UE may include ul-powercontrolld-r17 in one Uplink-powerControl-r17 parameter, individual POAlphaSet-r17 applicable to each of a PUSCH, a PUCCH, or an SRS may be configured for the UE, and each POAlphaSet-r17 may include p, alpha, and a closed loop index that are uplink transmission power parameters described above.
The higher layer signalings in [Table 31] above maybe appliedto allbandwidth parts in the corresponding serving cell. [Table 33] below represents a higher layer signaling structure configurable for the UE for each uplink bandwidth part (e.g., BWP-UplinkDedicated).
As shown in [Table 33], the higher layer signaling ul-TCI-StateList-r17 may be configured for the UE, and one of explicitlist or unifiedTCI-StateRef-r17 may be configured for the UE with respect to the higher layer signaling. If explicitlist is configured for the UE with respect to the higher layer signaling ul-TCI-StateList-r17, a list of UL TCI states usable in a corresponding uplink bandwidth part may be explicitly configured for the UE through ul-TCI-ToAddModList-r17. If unifiedTCI-StateRef-r17 is configured for the UE with respect to the higher layer signaling ul-TCI-StateList-r17, a joint TCI state or UL TCI state usable in a corresponding uplink bandwidth part may not be explicitly configured for the UE for the uplink bandwidth part, and the UE may refer to and use a joint TCI state or UL TCI state configured for another uplink bandwidth part. The higher layer signaling unifiedTCI-StateRef-r17 may indicate an index of a random bandwidth part in a random serving cell. In addition, the UE may expect that a serving cell including a bandwidth part for which unifiedTCI-StateRef-r17 is configured, and a random serving cell including a bandwidth part configurable by the base station through unifiedTCI-StateRef-r17 have the same value of unifiedTCI-StateType.
As shown in [Table 33], if unifiedTCI-StateType is configured for the UE, the higher layer signaling ul-powerControl may be configured for the UE and ul-powerControl may refer to one value of Uplink-powerControlId-r17. In this case, the higher layer signaling ul-powerControl may be configured for the UE with respect to all uplink bandwidth parts in a particular serving cell, or the higher layer signaling ul-powerControl may not be configured with respect to all the uplink bandwidth parts. If unifiedTCI-StateRef-r17 is configured in BWP-UplinkDedicated for the UE or the UE receives a configuration referring to a different serving cell and bandwidth part through a value of unifiedTCI-StateRef-r17 in PDSCH-Config, and unifiedTCI-StateType is configured as joint, the UE may expect that ul-powerControl is configured for the UE in a referred serving cell and all uplink bandwidth parts in the serving cell, or ul-powerControl is not configured in the referred serving cell and all the uplink bandwidth parts in the serving cell. The higher layer signaling ul-powerControl may be configured for the UE only when a condition of NoTCI-PC is satisfied, and the condition of NoTCI-PC may indicate that the higher layer signaling ul-powerControl is not configured in a joint TCI state or UL TCI state in a corresponding serving cell.
As shown in [Table 33], if unifiedTCI-StateType is configured for the UE, the higher layer signaling pathlossReferenceRSToAddModList-r17 may be configured for the UE, and the higher layer signaling may indicate a list of reference signals usable to calculate a pathloss amount when a PUSCH, a PUCCH, or an SRS is transmitted in a case where the UE supports a unified TCI state. If unifiedTCI-StateType is not configured for the UE, the UE may not include any list in the higher layer signaling.
If unifiedTCI-StateType is configured for the UE, when a reference signal for pathloss amount measurement is indicated to the UE through a TCI state indication, the indicated reference signal for pathloss amount measurement may indicate a reference signal for pathloss amount measurement configured in a serving cell to which the indicated TCI state is applied. In this case, if pathlossReferenceLinking is configured for the UE, the UE may consider that the indicated reference signal for pathloss amount measurement indicates a reference signal for pathloss amount measurement configured in a serving cell configured through pathlossReferenceLinking.
If the UE operates based on a unified TCI state, that is, if the higher layer signaling unifiedTCI-StateType is configured for the UE as joint or separate, a higher layer signaling structure of a TCI state indicatable to the UE by the base station may be determined. If the higher layer signaling unifiedTCI-StateType is configured for the UE as joint, a joint TCI state may be configured and indicated for the UE by the base station by using a higher layer signaling structure shown in [Table 34] below. If the higher layer signaling unifiedTCI-StateType is configured for the UE as separate, a DL TCI state may be configured and indicated for the UE by the base station by using a higher layer signaling structure shown in [Table 34] below, and a UL TCI state may be configured and indicated for the UE by the base station by using a higher layer signaling structure shown in [Table 35] below.
Ifthe higher layer signaling unifiedTC-StateType is configured for the UE as joint, the UE may expect that pathlossReferenceRS-Id-r17 in [Table 34] below is always configured, if unifiedTCI-StateType is configured as separate or unifiedTC-StateType is not configured, the UE may expect that pathlossReferenceRS-Id-r17 is not configured, and the name of such a condition may be defined as JointTCI1.
If the higher layer signaling unifiedTCI-StateType is configured for the UE as separate, the UE may expect that pathlossReferenceRS-Id-r17 in [Table 35] below is always configured, and the name of such a condition may be defined as mandatory.
In consideration of the higher layer signaling structure described above, the UE may use two types of uplink transmission power determination methods when operating according to a unified TCI state.
The parameter ul-powerControl may be configured for each of one or more uplink bandwidth parts configured in a particular serving cell. That is, when the UE performs all uplink transmission in each uplink bandwidth part, the UE may apply a set of transmission power parameters (e.g., p0, alpha, and closed loop index) identifiable through ul-powerControl configured for a corresponding uplink bandwidth part. Therefore, the UE does not use an individual transmission power parameter according to an uplink channel and signal, and may use only one common set of transmission power parameters.
The parameter ul-powerControl is not configured for each of one or more uplink bandwidth parts configured in a particular serving cell, and the UE may apply a set of transmission power parameters (e.g., p0, alpha, and closed loop index) identifiable through the higher layer signaling ul-powerControl-r17 in a joint TCI state or UL TCI state as shown in [Table 34] or [Table 35]. Therefore, different values of ul-powerControl-r17 may be configured for the UE for different joint TCI states or UL TCI states, accordingly, the UE may operate various transmission power parameters compared to [Method 1-1], and use different transmission power parameters according to uplink transmission situations and UE and base station operation scenarios.
Commonly for [Method 1-1] and [Method 1-2] described above, a reference signal for pathloss amount measurement may be configured for the UE in a joint TCI state or UL TCI state. That is, as described above, if the UE operates according to a unified TCI state, a reference signal for pathloss amount measurement may be always configured for the UE in a joint TCI state or UL TCI state, and the UE may determine a pathloss amount to be reflected at the time of determination of uplink transmission power by using a reference signal for pathloss amount measurement configured in a configured and indicated unified TCI state. In addition, the UE may track a maximum of four reference signals for pathloss amount measurement per random serving cell to update a maximum of four different pathloss amounts.
The UE may transfer whether the UE supports a combination of at least one of [Method 1-1] and [Method 1-2], to the base station through a UE capability report. In addition, a combination of at least one of [Method 1-1] and [Method 1-2] may be configured for the UE by the base station through higher layer signaling.
If the UE does not operate according to a unified TCI state, that is, if unifiedTCI-StateType is not configured for the UE, the UE may consider the following items at the time of determination of the transmission power of a PUSCH, a PUCCH, and an SRS, and such a method may be named [Method 1-3].
Higher layer signaling related to a transmission power parameter applicable at the time of PUSCH transmission may be configured for the UE according to [Table 36] and [Table 37] below.
Description of each higher layer signaling parameter in [Table 36] and [Table 37] may be as follows.
If the UE does not operate according to a unified TCI state, that is, if unifiedTCI-StateType is not configured for the UE, higher layer signaling related to a transmission power parameter applicable at the time of PUCCH transmission may be configured for the UE according to [Table 38] below.
Description of each higher layer signaling parameter in [Table 38] may be as follows.
Higher layer signaling related to a transmission power parameter applicable at the time of SRS transmission may be configured for the UE according to [Table 39] and [Table 40] below.
Description of each higher layer signaling parameter in [Table 39] and [Table 40] may be as follows.
If the UE operates according to a unified TCI state, that is, if unifiedTCI-StateType is configured for the UE, some or all of higher layer signalings used at the time of determination of the transmission power of a PUSCH, a PUCCH, and an SRS in a case where the UE does not operate according to a unified TCI state may not be configured.
For example, if the UE operates according to a unified TCI state, that is, if unifiedTCI-StateType is configured for the UE, PUSCH-PowerControl in [Table 36] and [Table 37] may not be configured for the UE at the time of determination of PUSCH transmission power. That is, if the UE operates according to a unified TCI state, tpc-Accumulation, msg3-Alpha, twoPUSCH-PC-AdjustmentStates, p0-NominalWithoutGrant, deltaMCS, olpc-ParameterSetDCI-0-1, olpc-ParameterSetDCI-0-2, p0-AlphaSets, pathlossReferenceRSToAddModList, p0-PUSCH-SetList, and p0-PUSCH-SetList2, which may be included in PUSCH-PowerControl in [Table 36] and [Table 37], may not be configured for the UE. As described above, when the above higher layer signaling fails to be configured for the UE, the following restrictions may exist.
For example, if the UE operates according to a unified TCI state, that is, if unifiedTCI-StateType is configured for the UE, PUCCH-PowerControl in [Table 38] may not be configured for the UE at the time of determination of PUCCH transmission power. That is, if the UE operates according to a unified TCI state, deltaF-PUCCH-f0, deltaF-PUCCH-f1, deltaF-PUCCH-f2, deltaF-PUCCH-f3, deltaF-PUCCH-f4, twoPUCCH-PC-AdjustmentStates, p0-Set, and pathlossReferenceRSs, which may be included in PUCCH-PowerControl in [Table 38], may not be configured for the UE. As described above, when the above higher layer signaling fails to be configured for the UE, the following restrictions may exist.
For example, if the UE operates according to a unified TCI state, that is, if unifiedTCI-StateType is configured for the UE, alpha, p0, and pathlossReferenceRS in [Table 40] may not be configured for the UE at the time of determination of SRS transmission power. As described above, when the above higher layer signaling fails to be configured for the UE, the following restrictions may exist.
In summary of the above items, it may be identified that if the UE operates according to a unified TCI state, that is, if unifiedTCI-StateType is configured for the UE, some of higher layer signalings capable of determining PUSCH, PUCCH, and SRS transmission power are not configured. As described above, in a case where the UE operates according to a unified TCI state, some higher layer signalings has substitutable basic (default) values defined in case that the signalings are not configured. However, configuring the higher layer signalings may restrict functions operable by the UE. For example, if two closed loop indexes for control of PUSCH transmission power being possible fails to be configured for the UE (e.g., twoPUSCH-PC-AdjustmentStates is not configured), the UE is able to use only one closed loop index for control of PUSCH transmission power. Therefore, in a case where the base station transfer a TPC command for transmission power control by the UE, it may be impossible to perform individual transmission power control required according to the type of uplink traffic of the UE (e.g., eMBB traffic, which requires high transmission throughput, and URLLC traffic, which demands low error rates and high robustness, etc.) or which TRP toward which the UE performs uplink transmission. Therefore, in a case where unifiedTCI-StateType is configured for the UE, some higher layer signalings not configured may make only restricted uplink transmission power control methods possible for the UE.
As an embodiment of the disclosure, an additional method of configuring a transmission power parameter when a unified TCI state is supported is described. This embodiment may be operated in combination with other embodiments.
As mentioned in the first embodiment, in a case where unifiedTCI-StateType is configured for a UE, some of higher layer signalings for control of uplink transmission power may fail to be configured for the UE. Hereinafter, a method of solving restrictions occurring due to the above reason is described. The UE may operate through a combination of at least one of the following methods so as to easily control uplink transmission power when operating according to a unified TCI state.
If unifiedTCI-StateType is configured for the UE, some of higher layer signalings for control of PUSCH, PUCCH, and SRS transmission power may not be configured for the UE.
For control of PUSCH transmission power, if unifiedTCI-StateType is configured for the UE, pusch-PowerControl may not be configured for the UE.
For control of PUCCH transmission power, if unifiedTCI-StateType is configured for the UE, pucch-PowerControl may not be configured for the UE.
For control of SRS transmission power, if unifiedTCI-StateType is configured for the UE, p0, alpha, and pathlossReferenceRS in SRS-ResourceSet may not be configured for the UE.
If unifiedTCI-StateType is configured for the UE, some of higher layer signalings for control of PUSCH, PUCCH, and SRS transmission power may not be configured for the UE.
For control of PUSCH transmission power, if unifiedTCI-StateType is configured for the UE, only some higher layer signalings in pusch-PowerControl may be configured for the UE. Parameters configurable for the UE among the higher layer signalings in pusch-PowerControl may be a combination of at least one of the following items:
For control of PUSCH transmission power, if unifiedTCI-StateType is configured for the UE, some higher layer signalings in pusch-PowerControl may not be configured for the UE. Parameters, which may not be configured for the UE, among the higher layer signaling s in pusch-PowerControl may be a combination of at least one of the following items:
In a case where the UE operates according to a unified TCI state, the UE may apply p0, alpha, and a closed loop index included in ul-powerControl-r17 in [Table 33] at the time of determination of PUSCH transmission power regardless of a TCI state indicated to the UE as in [Method 1-1], and may apply p0, alpha, and a closed loop index included in p0AlphaSetforPUSCH-r17 in ul-powerControl-r17 in [Table 34] and [Table 35] below configurable in a TCI state indicated to the UE at the time of determination of PUSCH transmission power as in [Method 1-2]. Therefore, if the UE does not operate according to a unified TCI state, the higher layer signalings sri-PUSCH-MappingToAddModList and sri-PUSCH-MappingToAddModList2, which have been used to indicate a PUSCH transmission power parameter by using an SRI field in DCI, may not be configured.
For the higher layer signaling p0-AlphaSets, if unifiedTCI-StateType is configured for the UE, the UE may replace the higher layer signaling by p0-r17 and alpha-r17 in the higher layer signaling p0AlphaSetforPUSCH-r17 in [Table 32] being configured.
For the higher layer signaling pathlossReferenceRSToAddModList, if unifiedTCI-StateType is configured for the UE, the UE may replace the higher layer signaling by the higher layer signaling pathlossReferenceRSToAddModList-r17 in [Table 33] being configured, and the base station may indicate, to the UE, one of reference signals for measuring a pathloss amount, which are configured for the UE as described above.
For control of PUCCH transmission power, if unifiedTCI-StateType is configured for the UE, only some higher layer signalings in pucch-PowerControl may be configured for the UE. Parameters configurable for the UE among the higher layer signalings in pucch-PowerControl may be a combination of at least one of the following items:
For control of PUCCH transmission power, if unifiedTCI-StateType is configured for the UE, some higher layer signalings in pucch-PowerControl may not be configured for the UE. Parameters, which may not be configured for the UE, among the higher layer signalings in pucch-PowerControl may be a combination of at least one of the following items:
For the higher layer signaling p0-Set, if unifiedTCI-StateType is configured for the UE, the UE may replace the higher layer signaling by p0-r17 in the higher layer signaling p0AlphaSetforPUCCH-r17 in [Table 32] being configured.
For the higher layer signaling pathlossReferenceRSs, if unifiedTCI-StateType is configured for the UE, the UE may replace the higher layer signaling by the higher layer signaling pathlossReferenceRSToAddModList-r17 in [Table 33] being configured, and the base station may indicate, to the UE, one of reference signals for measuring a pathloss amount, which are configured for the UE as described above.
For control of SRS transmission power, if unifiedTCI-StateType is configured for the UE, p0 and srs-PowerControlAdjustmentStates in SRS-ResourceSet may be configured for the UE.
For control of SRS transmission power, if unifiedTCI-StateType is configured for the UE, some higher layer signalings in SRS-ResourceSet may not be configured for the UE. Parameters, which may not be configured for the UE, among the higher layer signalings in SRS-ResourceSet may be a combination of at least one of the following items:
For the higher layer signaling alpha, if unifiedTCI-StateType is configured for the UE, the UE may replace the higher layer signaling by alpha-r17 in the higher layer signaling p0AlphaSetforSRS-r17 in [Table 32] being configured.
For the higher layer signaling pathlossReferenceRSs, if unifiedTCI-StateType is configured for the UE, the UE may replace the higher layer signaling by the higher layer signaling pathlossReferenceRSToAddModList-r17 in [Table 33] being configured, and the base station may indicate, to the UE, one of reference signals for measuring a pathloss amount, which are configured for the UE as described above.
If unifiedTCI-StateType is configured for the UE, some of higher layer signalings for control of PUSCH, PUCCH, and SRS transmission power may not be configured for the UE, and new higher layer signaling may be configured therefor as below.
For control of PUSCH transmission power, if unifiedTCI-StateType is configured for the UE, pusch-PowerControl may not be configured for the UE, and a combination of at least one of the following higher layer signalings may be configured in the higher layer signaling PUSCH-config. The following higher layer signalings may have a part such as “-r17,” “-r18,” or “-r19” (e.g., tpc-Accumulation-r17 or p0-PUSCH-SetList2-r18) added after the name of each parameter:
The UE may additionally consider a combination of at least one of the following conditions for PUSCH transmission power control.
For control of PUCCH transmission power, if unifiedTCI-StateType is configured for the UE, pucch-PowerControl may not be configured for the UE, and a combination of at least one of the following higher layer signalings may be configured in the higher layer signaling PUCCH-config. The following higher layer signalings may have a part such as “-r17,” “-r18,” or “-r19” (e.g., deltaF-PUCCH-f0-r17 or twoPUCCH-PC-AdjustmentStates-r18) added after the name of each parameter:
The UE may additionally consider a combination of at least one of the following conditions for PUCCH transmission power control.
For control of SRS transmission power, if unifiedTCI-StateType is configured for the UE, p0, alpha, and pathlossReferenceRS may not be configured in SRS-ResourceSet for the UE, and p0 may be configured in the higher layer signaling SRS-config. A part, such as “-r17,” “-r18,” or “-r19,” or a part such as “-srs” for expressing p0 being applied to an SRS may be added after p0 (e.g., p0-srs-r18).
The UE may additionally consider a combination of at least one of the following conditions for SRS transmission power control.
If unifiedTCI-StateType is configured for the UE, some of higher layer signalings for control of PUSCH, PUCCH, and SRS transmission power may not be configured for the UE, and the UE may receive new higher layer signaling in a bandwidth part configuration as below.
For control of PUSCH transmission power, if unifiedTCI-StateType is configured for the UE, pusch-PowerControl may not be configured for the UE, and a combination of at least one of the following higher layer signalings may be configured in the higher layer signaling BWP-UplinkDedicated. The following higher layer signalings may have a part such as “-r17,” “-r18,” or “-r19” added after the name of each parameter, may have a part such as “-pusch” to express that a corresponding higher layer signaling is applied to a PUSCH, or may have both of the parts (e.g., tpc-Accumulation-PUSCH-r17 or p0-PUSCH-SetList2-r18):
The UE may additionally consider a combination of at least one of the following conditions for PUSCH transmission power control.
For control of PUCCH transmission power, if unifiedTCI-StateType is configured for the UE, pucch-PowerControl may not be configured for the UE, and a combination of at least one of the following higher layer signalings may be configured in the higher layer signaling BWP-UplinkDedicated. The following higher layer signalings may have a part such as “-r17,” “-r18,” or “-r19” added after the name of each parameter, may have a part such as “-pucch” to express that a corresponding higher layer signaling is applied to a PUCCH, or may have both of the parts (e.g., deltaF-PUCCH-f0-r17 or twoPUCCH-PC-AdjustmentStates-r18):
The UE may additionally consider a combination of at least one of the following conditions for PUCCH transmission power control.
For control of SRS transmission power, if unifiedTCI-StateType is configured for the UE, p0, alpha, and pathlossReferenceRS may not be configured in SRS-ResourceSet for the UE, and p0 may be configured in the higher layer signaling BWP-UplinkDedicated. A part, such as “-r17,” “-r18,” or “-r19,” or a part such as “-srs” for expressing p0 being applied to an SRS may be added after p0 (e.g., p0-srs-r18).
The UE may additionally consider a combination of at least one of the following conditions for SRS transmission power control.
With respect to each of [Method 2-1] to [Method 2-3], for control of PUSCH transmission power, if unifiedTCI-StateType is configured for the UE, a combination of at least one of the following higher layer signalings may not be configured for the UE in the higher layer signaling pusch-PowerControl, PUSCH-config, or BWP-UplinkDedicated:
In a case where the UE operates according to a unified TCI state, the UE may apply p0, alpha, and a closed loop index included in ul-powerControl-r17 in [Table 33] at the time of determination of PUSCH transmission power regardless of a TCI state indicated to the UE as in [Method 1-1], and may apply p0, alpha, and a closed loop index included in p0AlphaSetforPUSCH-r17 in ul-powerControl-r17 in [Table 34] and [Table 35] below configurable in a TCI state indicated to the UE at the time of determination of PUS CH transmission power as in [Method 1-2].
Higher layer signalings may be higher layer signalings used in open-loop power control (OLPC). Through p0-PUSCH-SetList and p0-PUSCH-SetList2, another p0 value indicatable by the same SRI may be configured for the UE by the base station. In this case, through an open-loop power control parameter set indication field in DCI, the UE may receive an indication of one of a value configured through the higher layer signaling p0-AlphaSets and a value configured through the higher layer signalings p0-PUSCH-SetList and p0-PUSCH-SetList2, to determine final p0 at time of determination of PUSCH transmission power. However, since [Method 1-1] is a method of using common p0, alpha, and closed loop index at determination of all uplink transmission power, there may be no reason to use additional p0 through p0-PUSCH-SetList and p0-PUSCH-SetList2 described above. In addition, since [Method 1-2] enables indication of different transmission power parameters p0, alpha, and closed loop index through a TCI state, signaling flexibility may be already sufficiently ensured even if additional p0 is not used through p0-PUSCH-SetList and p0-PUSCH-SetList2 described above. Therefore, in a case where the UE operates according to a unified TCI state, higher layer signaling (e.g., olpc-ParameterSetDCI-0-1, olpc-ParameterSetDCI-0-2, p0-PUSCH-SetList, or p0-PUSCH-SetList2) used in open-loop power control may not be configured for the UE, and the UE may not support an open-loop power control parameter set indication field in DCI format 0_1, 0_2, and 0_3,
On the contrary, if uplink transmission power control signaling is indicated to the UE by the base station through [Method 1-2], the flexibility of the signaling may relate to the number of cases where different p0 values are connected to different TCI states. That is, the number of transmission power parameter sets in which different p0 values are connected to the same alpha value and the same closed loop index value may be greater than 64 that is a maximum number of UL TCI state. For example, the total number of possible value candidates of the higher layer signaling alpha is 8 including alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, and alphal, two closed loop indexes including i0 and i1 are possible, and thus a total of 16 combinations of alpha and a closed loop index may be possible. In addition, integers between −16 and 15 are possible as a value of p0 and thus a possible total number of the values is 32, and the number of all possible combinations of p0, alpha, and a closed loop index may be 512 in total. Therefore, if multiple different TRPs exist in a particular serving cell operating in an FR2 band and the UE operates multiple transmission/reception beams, the UE may require various combinations of transmission power parameters. In this case, for signaling flexibility which may be insufficient with a method capable of indicating a maximum of 8 activated TCI states, if open-loop power control is additionally employed, additionally flexibility may be ensured on signaling. Therefore, for control of PUSCH transmission power, if unifiedTCI-StateType is configured for the UE, a combination of at least one of the following higher layer signalings may be configured in the higher layer signaling PUSCH-config for the UE. In order to distinguish between the following higher layer signalings and existing higher layer signaling, a part such as “-UTCI” and/or a part such as “-r17,” “-r18,” or “-r19” may be added in the parameter name of the following higher layer signalings (e.g., olpc-ParameterSet-UTCI-DCI-0-1 or p0-PUSCH-SetList-UTCI-r18):
olpc-ParameterSet-DCI-0-1 and olpc-ParameterSet-DCI-0-2 may indicate the length of an open-loop power control parameter set indication field which may be included in DCI, and 1 or 2 bits may be possible. The higher layer signaling p0-PUSCH-SetList may indicate additional p0 corresponding to a codepoint of each TCI state field in DCI. The length of the higher layer signaling p0-PUSCH-SetList may be a power of 2 with the exponent being the larger value of the lengths of TCI state fields included in DCI formats 0_1 and 0_2, and a p0 value corresponding to the length of p0-PUSCH-SetList may be configured for the UE. For example, if the lengths of TCI state fields in DCI formats 0_1 and 0_2 are 3 bits and 2 bits, respectively, the length of the higher layer signaling p0-PUSCH-SetList may be 8 that is a power of 2 having the exponent of 3, which is the larger value among 3 bits and 2 bits, and a total of 8 identical or different p0 values may be configured. The UE may determine which p0 which the UE is to apply to calculate uplink transmission power according to the value of an open-loop power control parameter set indication field in DCI received by the UE, through a method as below. In a case of the higher layer signaling p0-PUSCH-SetList2, if two TCI states are indicated to the UE through TCI state in DCI (the second joint TCI state in a case of joint TCI state, and the second UL TCI state in a case of separate TCI state), the UE may interpret and apply the TCI state in the following method as the second joint TCI state or the second UL TCI state indicated to the UE.
As another method, the higher layer signaling p0-PUSCH-SetList may include a maximum of two different values of p0.
A UE may be notified by a base station of at least one of [Method 1-1], [Method 1-2], [Method 1-3], [Method 2-0], [Method 2-1], [Method 2-2], or [Method 2-3] through at least one of higher layer signaling, MAC-CE signaling, or L1 signaling, or may expect at least one of [Method 1-1], [Method 1-2], [Method 1-3], [Method2-0], [Method 2-1], [Method 2-2], or [Method 2-3] to be statically defined in a specification. In the disclosure, phrases such as “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B, or C,” “at least one of A, B, and C,” and “at least one of A, B, or C” may include any one or all possible combinations of the items listed in a corresponding phrase of the respective phrases.
Additionally, if a UE is notified by a base station of a combination of one or more specific methods through at least one of higher layer signaling, MAC-CE signaling, or L1 signaling, it may imply that the UE is unable to support other combinations of the one or more specific methods. In other words, if the UE is notified of at least one of [Method 1-1], [Method 1-2], [Method 1-3], [Method 2-0], [Method 2-1], [Method 2-2], or [Method 2-3] by the base station, it may imply that the UE is unable to support the one or more other methods except for the at least one.
For example, the UE may expect [Method 1-1] and/or [Method 2-2] to be statically defined in a specification for higher layer signaling configuration methods related to uplink transmission power.
In another example, the UE may be notified of [Method 1-2] and/or [Method 2-3] by the base station through at least one of higher layer signaling, MAC-CE signaling, or L1 signaling. In such cases, the UE may consider that at least one of the methods not notified (e.g., [Method 1-1] and/or [Method 2-0]) not being supported is notified by the base station.
The UE may report, to the base station as UE capability, whether the UE is able to support at least one of [Method 1-1], [Method 1-2], [Method 1-3], [Method 2-0], [Method 2-1], [Method 2-2], or [Method 2-3]. If the UE reports, to the base station as UE capability, whether the UE is able to a combination of one or more specific methods, it may be considered that the UE reports that the UE is unable to support other combinations of one or more specific methods. In other words, if the UE reports, to the base station as UE capability, that the UE is able to at least one of [Method 1-1], [Method 1-2], [Method 1-3], [Method 2-0], [Method 2-1], [Method 2-2], or [Method 2-3], it may be considered that the UE reports that the UE is unable to support one or more methods of the remaining methods except for the reported at least one method. In other words, it may be considered that the UE reports that the UE is unable to support other methods or other methods not reported as UE capability.
For instance, the UE may report, to the base station, whether the UE is able to support [Method 1-1], [Method 1-2], [Method 2-0], and/or [Method 2-3]. In this case, the UE may report, to the base station as a UE capability report, that the UE is able to support [Method 1-2] and/or [Method 2-3], and the UE capability report may imply that the UE is unable to support [Method 1-1] and/or [Method 2-0].
In operation 1100, a UE may transmit a UE capability to a base station. UE capability signaling which may be reported at this time may relate to at least one of a UE capability related to PUSCH, PUCCH, and SRS transmission, a UE capability related to a unified TCI state operation, or a UE capability corresponding to at least one of [Method 1-1], [Method 1-2], [Method 1-3], [Method 2-0], [Method 2-1], [Method 2-2], or [Method 2-3]. Omission of operation 1100 is possible.
In operation 1105, the UE may receive higher layer signaling from the base station according to the reported UE capability. The UE may define higher layer parameters for a combination of at least one of higher layer signaling related to PUSCH, PUCCH, and SRS transmission, higher layer signaling related to a unified TCI state operation, or higher layer signaling related to supporting of [Method 1-1] to [Method 1-3] or [Method 2-0] to [Method 2-3], which is received from the base station, and use one of the defined higher layer parameters.
In operation 1110, the UE may be notified by the base station of whether to perform UE operation 1 or 2 according to whether a particular condition is satisfied. The particular condition may be a condition under which [Method 2-0] to [Method 2-3] are performed. For example, the particular condition may be a combination of at least one of the following items:
If the UE satisfies the particular condition, in operation 1115, the UE may perform UE operation 1 in determining uplink transmission power. UE operation 1 may follow at least one of [Method 1-1], [Method 1-2], [Method 2-0], [Method 2-2], or [Method 2-3].
If the UE does not satisfy the particular condition, in operation 1120, the UE may perform UE operation 2 in determining uplink transmission power. UE operation 2 may follow [Method 1-3].
A flowchart described above illustrates an exemplified method implementable according to the principle of the disclosure, and a method illustrated in the flowchart of this specification may be variously modified. For example, a series of operations are illustrated, but various operations in each drawing may overlap with each other, occur in parallel, occur in a different sequence, or occur several times. In another example, an operation may be omitted or replaced with another operation.
In operation 1200, a base station may receive a UE capability from a UE. UE capability signaling which may be received by the base station may relate to at least one of a UE capability related to PUSCH, PUCCH, and SRS transmission, a UE capability related to a unified TCI state operation, or a UE capability corresponding to at least one of [Method 1-1], [Method 1-2], [Method 1-3], [Method 2-0], [Method 2-1], [Method 2-2], or [Method 2-3]. Omission of operation 1200 is possible.
In operation 1205, the base station may transmit higher layer signaling to the UE according to the UE capability reported by the UE. The UE may define higher layer parameters for a combination of at least one of higher layer signaling related to PUSCH, PUCCH, and SRS transmission, higher layer signaling related to a unified TCI state operation, or higher layer signaling related to supporting of [Method 1-1] to [Method 1-3] or [Method 2-0] to [Method 2-3], which is received from the base station, and use one of the defined higher layer parameters.
In operation 1210, the base station may determine whether the UE is to perform UE operation 1 or 2 according to whether the UE satisfies a particular condition, and notify the UE of the determination. The particular condition may be a condition under which [Method 2-0] to [Method 2-3] are performed. For example, the particular condition may be a combination of at least one of the following items:
If the UE satisfies the particular condition, in operation 1215, the base station may expect that the UE is to perform UE operation 1 in determining uplink transmission power. UE operation 1 may follow at least one of [Method 1-1], [Method 1-2], [Method 2-0], [Method 2-2], or [Method 2-3].
If the UE does not satisfy the particular condition, in operation 1220, the base station may expect that the UE is to perform UE operation 2 in determining uplink transmission power. UE operation 2 may follow [Method 1-3].
The above-described flowchart illustrates an exemplary method that may be implemented according to the principle of the disclosure, and various changes may be made to the method shown in the flowchart herein. For example, although shown as a series of operations, various operations in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In another example, an operation may be omitted or replaced with another operation.
Referring to
The transceiver may transmit/receive signals with the base station. The signals may include control information and data. To this end, the transceiver may include an RF transmitter configured to up-convert and amplify the frequency of transmitted signals, an RF receiver configured to low-noise-amplify received signals and down-convert the frequency thereof, and the like. However, this is only an embodiment of the transceiver, and the components of the transceiver are not limited to the RF transmitter and the RF receiver.
In addition, the transceiver may receive signals through a radio channel, output the same to the processor, and transmit signals output from the processor through the radio channel.
The memory may store programs and data necessary for operations of the UE. In addition, the memory may store control information or data included in signals transmitted/received by the UE. The memory may include storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media. In addition, the memory may include multiple memories.
Furthermore, the processor may control a series of processes such that the UE can operate according to the above-described embodiments. For example, the processor may control components of the UE to receive DCI configured in two layers so as to simultaneously receive multiple PDSCHs. The processor may include multiple processors, and the processor may perform operations of controlling the components of the UE by executing programs stored in the memory.
Referring to
The transceiver may transmit/receive signals with the UE. The signals may include control information and data. To this end, the transceiver may include an RF transmitter configured to up-convert and amplify the frequency of transmitted signals, an RF receiver configured to low-noise-amplify received signals and down-convert the frequency thereof, and the like. However, this is only an embodiment of the transceiver, and the components of the transceiver are not limited to the RF transmitter and the RF receiver.
In addition, the transceiver may receive signals through a radio channel, output the same to the processor, and transmit signals output from the processor through the radio channel.
The memory may store programs and data necessary for operations of the base station. In addition, the memory may store control information or data included in signals transmitted/received by the base station. The memory may include storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media. In addition, the memory may include multiple memories.
The processor may control a series of processes such that the base station can operate according to the above-described embodiments of the disclosure. For example, the processor may control components of the base station to configure DCI configured in two layers including allocation information regarding multiple PDSCHs and to transmit the same. The processor may include multiple processors, and the processor may perform operations of controlling the components of the base station by executing programs stored in the memory.
Methods disclosed in the claims and/or methods according to the embodiments described in the specification of the disclosure may be implemented by hardware, software, or a combination of hardware and software.
When the methods are implemented by software, a computer-readable storage medium for storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium may be configured for execution by one or more processors within the electronic device. The at least one program includes instructions that cause the electronic device to perform the methods according to various embodiments of the disclosure as defined by the appended claims and/or disclosed herein.
These programs (software modules or software) may be stored in non-volatile memories including a random access memory and a flash memory, a read only memory (ROM), an electrically erasable programmable read only memory (EEPROM), a magnetic disc storage device, a compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other type optical storage devices, or a magnetic cassette. Alternatively, any combination of some or all of them may form a memory in which the program is stored. In addition, a plurality of such memories may be included in the electronic device.
Furthermore, the programs may be stored in an attachable storage device which can access the electronic device through communication networks such as the Internet, Intranet, local area network (LAN), wide LAN (WLAN), and storage area network (SAN) or a combination thereof. Such a storage device may access the electronic device via an external port. Also, a separate storage device on the communication network may access a portable electronic device.
In the above-described detailed embodiments of the disclosure, an element included in the disclosure is expressed in the singular or the plural according to presented detailed embodiments. However, the singular form or plural form is selected appropriately to the presented situation for the convenience of description, and the disclosure is not limited by elements expressed in the singular or the plural. Therefore, either an element expressed in the plural may also include a single element or an element expressed in the singular may also include multiple elements.
The embodiments of the disclosure described and shown in the specification and the drawings are merely specific examples that have been presented to easily explain the technical contents of embodiments of the disclosure and help understanding of embodiments of the disclosure, and are not intended to limit the scope of embodiments of the disclosure. That is, it will be apparent to those skilled in the art that other variants based on the technical idea of the disclosure may be implemented. Also, the above respective embodiments may be employed in combination, as necessary. For example, a part of one embodiment of the disclosure may be combined with a part of another embodiment to operate a base station and a terminal. As an example, a part of a first embodiment of the disclosure may be combined with a part of a second embodiment to operate a base station and a terminal. Moreover, although the above embodiments have been described based on the FDD LTE system, other variants based on the technical idea of the embodiments may also be implemented in other communication systems such as TDD LTE, and 5G, or NR systems.
In the drawings in which methods of the disclosure are described, the order of the description does not always correspond to the order in which steps of each method are performed, and the order relationship between the steps may be changed or the steps may be performed in parallel.
Alternatively, in the drawings in which methods of the disclosure are described, some elements may be omitted and only some elements may be included therein without departing from the essential spirit and scope of the disclosure.
In addition, in methods of the disclosure, some or all of the contents of each embodiment may be implemented in combination without departing from the essential spirit and scope of the disclosure.
Various embodiments of the disclosure have been described above. The above description of the disclosure is for the purpose of illustration, and is not intended to limit embodiments of the disclosure to the embodiments set forth herein. Those skilled in the art will appreciate that other specific modifications and changes may be easily made to the forms of the disclosure without changing the technical idea or essential features of the disclosure. The scope of the disclosure is defined by the appended claims, rather than the above detailed description, and the scope of the disclosure should be construed to include all changes or modifications derived from the meaning and scope of the claims and equivalents thereof.
Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2024-0006281 | Jan 2024 | KR | national |
