Method and apparatus for transmitting / receiving data information in a measurement gap in a wireless communication system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. According to one embodiment of the present invention, a method performed by a terminal in a communication system includes the steps of: receiving a measurement gap (MG) configuration through higher layer signaling; identifying one or more MGs based on the MG configuration; receiving a downlink control information (DCI) format through a physical downlink control channel (PDCCH), the DCI format including a field related to whether to perform MG cancellation; identifying a specific MG among the one or more MGs; and canceling the specific MG if MG cancellation is identified based on the field related to whether to perform MG cancellation.

Description

Technical Field

[0001] This disclosure relates to the operation of terminals and base stations in wireless communication systems. Specifically, this disclosure relates to a method for transmitting / receiving data information in a wireless communication system and an apparatus capable of performing the method. Background Technology

[0002] 5G mobile communication technology defines a wide frequency band, enabling high transmission rates and new services. It can be implemented not only in the "below 6 GHz" band, such as 3.5 GHz, but also in the "above 6 GHz" band, including 28 GHz and 39 GHz, known as mmWave. Furthermore, 6G mobile communication technology (referred to as "super 5G systems") is being considered in terahertz bands (such as the 95 GHz to 3 THz band) to achieve transmission rates fifty times faster than 5G and ultra-low latency one-tenth that of 5G.

[0003] At the outset of 5G mobile communication technology development, standardization was underway regarding beamforming and massive MIMO to support services and meet performance requirements associated with enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC). This standardization aimed to mitigate radio wave path loss in millimeter waves and increase radio wave transmission distance; support parameter sets for dynamic operation (e.g., operating multiple subcarrier spacings) to efficiently utilize millimeter wave resources and time slot formats; initial access technologies to support multi-beam transmission and broadband; the definition and operation of bandwidth portions (BWP); new channel decoding methods (such as low-density parity-check (LDPC) codes for large data transmissions and polar codes for highly reliable transmission of control information); L2 preprocessing; and network slicing for providing dedicated networks for specific services.

[0004] Currently, given the services supported by 5G mobile communication technology, discussions are underway regarding improvements and performance enhancements to the initial 5G mobile communication technology. Physical layer standardization for technologies such as Vehicle-to-Everything (V2X) is also in place, designed to assist autonomous vehicle driving decisions based on information about the vehicle's location and status transmitted by the vehicle, and to enhance user convenience. This includes NR-U (New Radio Unlicensed) and NR UE Energy Saving (NTN), which are UE-satellite direct communication technologies used to provide coverage and positioning in areas where communication with terrestrial networks is unavailable.

[0005] Furthermore, standardization is ongoing for technologies within the air interface architecture / protocol, such as the Industrial Internet of Things (IIoT) for supporting new services through interoperability and convergence with other industries, Integrated Access and Backhaul (IAB) for providing nodes for network service area extension by supporting wireless backhaul and access links in an integrated manner, mobility enhancements including conditional handover and Dual Active Protocol Stack (DAPS) handover, and two-step random access (two-step RACH for NR) for simplifying the random access process. Standardization is also underway for 5G baseline architectures (such as service-based architectures or service-based interfaces) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, as well as system architectures / services for Mobile Edge Computing (MEC) based on UE location reception services.

[0006] With the commercialization of 5G mobile communication systems, the already exponentially growing number of connected devices will be connected to the communication network, thus necessitating enhanced functionality and performance of 5G mobile communication systems as well as integrated operation of connected devices. To this end, new research related to extended reality (XR) has been arranged to effectively support augmented reality (AR), virtual reality (VR), mixed reality (MR), etc., by leveraging artificial intelligence (AI) and machine learning (ML), AI service support, metaspace service support, and drone communication to improve 5G performance and reduce complexity.

[0007] Furthermore, this development of 5G mobile communication systems will not only serve as the foundation for developing new waveforms for providing terahertz band coverage in 6G mobile communication technologies, such as multi-antenna transmission technologies like full-dimensional MIMO (FD-MIMO), array antennas, and massive MIMO; metamaterial-based lenses and antennas for improving terahertz band signal coverage; high-dimensional spatial multiplexing technologies using orbital angular momentum (OAM); and reconfigurable smart surfaces (RIS); it will also serve as the foundation for developing full-duplex technologies to improve the frequency efficiency of 6G mobile communication technologies and enhance system networks; AI-based communication technologies to achieve system optimization by leveraging satellites and AI from the design phase and internalizing end-to-end AI support functions; and next-generation distributed computing technologies to achieve services with complexity levels exceeding the operational capabilities of UEs by utilizing ultra-high-performance communication and computing resources. Summary of the Invention

[0008] Technical issues

[0009] The embodiments described herein are intended to provide an apparatus and method for effectively providing services in a mobile communication system.

[0010] The technical topics explored in the various embodiments of this disclosure are not limited to those described above, and those skilled in the art may consider other technical topics not mentioned herein from the various embodiments of this disclosure described below.

[0011] Technical solution

[0012] According to an embodiment of the present invention, a method performed by a terminal in a communication system includes: receiving a measurement gap (MG) configuration via higher-layer signaling; identifying one or more MGs based on the MG configuration; receiving downlink control information (DCI) format via a physical downlink control channel (PDCCH), the DCI format including fields related to whether to perform MG cancellation; identifying a specific MG from the one or more MGs; and canceling the specific MG if it is identified that the MG is to be canceled based on the fields related to whether to perform MG cancellation.

[0013] According to embodiments of this disclosure, a specific MG is the earliest MG that starts X time intervals after the end time of the PDCCH, and the X time intervals are defined based on the UE capability report of the terminal.

[0014] According to embodiments of this disclosure, when multiple DCI formats associated with a specific MG are received, and each DCI format includes a field related to whether MG cancellation is performed, the DCI format is the last of the multiple DCI formats.

[0015] According to embodiments of this disclosure, the DCI format is either DCI format 0_X or DCI format 1_X, wherein it is identified whether a configuration regarding the inclusion of a field related to whether to perform MG cancellation in DCI format 0_X or DCI format 1_X has been received via higher-layer signaling, wherein if the configuration regarding the inclusion of a field related to whether to perform MG cancellation has been received, the field related to whether to perform MG cancellation is 1 bit, wherein if the configuration regarding the inclusion of a field related to whether to perform MG cancellation has not been received, the field related to whether to perform MG cancellation is 0 bit, and wherein if the configuration regarding the inclusion of a field related to whether to perform MG cancellation has been received, reception of the DCI format containing the field related to whether to perform MG cancellation is performed.

[0016] According to embodiments of this disclosure, a value of 1 in a field related to whether to cancel MG indicates that MG should be canceled, and a value of 0 in a field related to whether to cancel MG indicates that MG should not be canceled.

[0017] According to embodiments of this disclosure, fields that are related to whether MG cancellation is performed and have a value of 0 are ignored.

[0018] According to embodiments of the present disclosure, a terminal in a communication system includes a transceiver and a processor connected to the transceiver, wherein the processor is configured to: receive a measurement gap (MG) configuration via higher-layer signaling; identify one or more MGs based on the MG configuration; receive downlink control information (DCI) format via a physical downlink control channel (PDCCH), the DCI format including fields related to whether to perform MG cancellation; identify a specific MG from the one or more MGs; and cancel a specific MG if it is identified that an MG should be canceled based on the fields related to whether to perform MG cancellation.

[0019] According to embodiments of this disclosure, a specific MG is the earliest MG that starts X time intervals after the end time of the PDCCH, and the X time intervals are defined based on the UE capability report of the terminal.

[0020] According to embodiments of this disclosure, when multiple DCI formats associated with a specific MG are received, and each DCI format includes a field related to whether MG cancellation is performed, the DCI format is the last of the multiple DCI formats.

[0021] According to embodiments of this disclosure, the DCI format is either DCI format 0_X or DCI format 1_X, wherein it is identified whether a configuration regarding the inclusion of a field related to whether to perform MG cancellation in DCI format 0_X or DCI format 1_X has been received via higher-layer signaling, wherein if the configuration regarding the inclusion of a field related to whether to perform MG cancellation has been received, the field related to whether to perform MG cancellation is 1 bit, wherein if the configuration regarding the inclusion of a field related to whether to perform MG cancellation has not been received, the field related to whether to perform MG cancellation is 0 bit, and wherein if the configuration regarding the inclusion of a field related to whether to perform MG cancellation has been received, reception of the DCI format containing the field related to whether to perform MG cancellation is performed.

[0022] According to embodiments of this disclosure, a value of 1 in a field related to whether to cancel MG indicates that MG should be canceled, and a value of 0 in a field related to whether to cancel MG indicates that MG should not be canceled.

[0023] According to embodiments of this disclosure, fields that are related to whether MG cancellation is performed and have a value of 0 are ignored.

[0024] According to embodiments of this disclosure, a method performed by a base station in a communication system includes: transmitting a measurement gap (MG) configuration associated with one or more MGs via higher-layer signaling; identifying a specific MG from the one or more MGs; transmitting downlink control information (DCI) format including fields related to whether MG cancellation is performed via a physical downlink control channel (PDCCH); and performing communication within the specific MG if the MG is cancelled based on fields related to whether MG cancellation is performed.

[0025] According to embodiments of this disclosure, a value of 1 in a field related to whether to cancel MG indicates that MG should be canceled, and a value of 0 in a field related to whether to cancel MG indicates that MG should not be canceled.

[0026] According to an embodiment of this disclosure, a base station in a communication system includes a transceiver and a processor connected to the transceiver, wherein the processor is configured to: transmit measurement gap (MG) configurations associated with one or more MGs via higher-layer signaling; identify a specific MG from one or more MGs; transmit downlink control information (DCI) format including fields related to whether to perform MG cancellation via a physical downlink control channel (PDCCH); and perform communication within a specific MG if the MG is indicated to be cancelled based on the fields related to whether to perform MG cancellation.

[0027] The various embodiments described above are merely some preferred embodiments of this disclosure, and those skilled in the art can derive and understand various embodiments reflecting the technical features of various embodiments of this disclosure from the detailed description below.

[0028] Beneficial effects

[0029] The embodiments described herein provide an apparatus and method for effectively providing services in a mobile communication system.

[0030] The advantageous effects that can be obtained from the various embodiments of this disclosure are not limited to those described above, and other effects not mentioned herein can be clearly derived and understood by those skilled in the art based on the following detailed description. Attached Figure Description

[0031] Figure 1 The basic structure of the time-frequency domain in a wireless communication system according to an embodiment of the present disclosure is shown.

[0032] Figure 2 The structure of frames, subframes, and time slots in a wireless communication system according to an embodiment of the present disclosure is shown.

[0033] Figure 3 An example of bandwidth configuration in a wireless communication system according to an embodiment of this disclosure is shown.

[0034] Figure 4 An example of a control resource set for a downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown.

[0035] Figure 5 The structure of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown.

[0036] Figure 6 The span illustrates a scenario where a UE, according to an embodiment of this disclosure, may have multiple PDCCH monitoring opportunities within a time slot in a wireless communication system.

[0037] Figure 7 An example of base station beam allocation configured according to TCI state in a wireless communication system according to an embodiment of the present disclosure is shown.

[0038] Figure 8 An example of a method for allocating TCI states to a PDCCH in a wireless communication system, according to an embodiment of the present disclosure, is shown.

[0039] Figure 9 The TCI indication MACCE signaling structure for PDCCH DMRS in a wireless communication system according to an embodiment of the present disclosure is shown.

[0040] Figure 10 An example of beam configuration regarding the control resource set and search space in a wireless communication system according to an embodiment of the present disclosure is shown.

[0041] Figure 11 A method for transmitting / receiving data in a wireless communication system according to embodiments of the present disclosure, taking into account downlink data channel and rate matching resources, is illustrated.

[0042] Figure 12 A method according to an embodiment of the present disclosure is illustrated, wherein upon receiving a downlink control channel, the UE selects an acceptable set of control resources by considering priorities in the wireless communication system.

[0043] Figure 13 An example of a non-periodic CSI reporting method according to an embodiment of this disclosure is shown.

[0044] Figure 14 An example of PUSCH repetition type B transmission in a wireless communication system according to an embodiment of the present disclosure is shown.

[0045] Figure 15 The radio protocol structures of the base station and UE in single-cell, carrier aggregation, and dual connectivity scenarios in a wireless communication system according to embodiments of this disclosure are illustrated.

[0046] Figure 16An example of antenna port configuration and resource allocation for cooperative communication in a wireless communication system according to an embodiment of this disclosure is shown.

[0047] Figure 17 An example of the configuration of downlink control information (DCI) for cooperative communication in a wireless communication system according to an embodiment of the present disclosure is shown.

[0048] Figure 18 This illustrates the process by which a base station controls the transmit power of a UE in a cellular system.

[0049] Figure 19 The process of generating a Type 1 (semi-static) HARQ-ACK codebook for a UE according to an embodiment of this disclosure is illustrated.

[0050] Figure 20 The process of generating a Type 2 (dynamic) HARQ-ACK codebook for a UE according to an embodiment of this disclosure is illustrated.

[0051] Figure 21 The transmission and reception measurement gaps and SS / PBCH blocks according to embodiments of this disclosure are illustrated.

[0052] Figure 22 A dynamic skipping process for the measurement gap according to an embodiment of this disclosure is illustrated.

[0053] Figure 23 A determination interval for dynamically skipping measurement gaps according to an embodiment of this disclosure is shown.

[0054] Figure 24 The determination interval is shown according to an embodiment of the present disclosure in a case where the measurement gap can be dynamically partially skipped.

[0055] Figure 25 This is a flowchart illustrating UE operation according to an embodiment of the present disclosure in a case where measurement gaps can be dynamically skipped.

[0056] Figure 26 The structure of a UE in a wireless communication system according to an embodiment of the present disclosure is shown.

[0057] Figure 27 The structure of a base station in a wireless communication system according to an embodiment of the present disclosure is shown. Detailed Implementation

[0058] The embodiments of this disclosure will be described in detail below with reference to the accompanying drawings.

[0059] In describing the embodiments, descriptions relating to technical content known in the relevant art and not directly related to this disclosure will be omitted. This omission of unnecessary descriptions is to prevent confusion with the main ideas of this disclosure and to more clearly convey these main ideas.

[0060] For the same reason, some elements may be exaggerated, omitted, or shown schematically in the accompanying drawings. Furthermore, the dimensions of the corresponding components do not perfectly reflect their actual dimensions. Identical or corresponding components in each drawing are indicated by the same reference numerals.

[0061] The advantages and features of this disclosure, and the ways in which they are implemented, will be apparent from the following detailed description of embodiments in conjunction with the accompanying drawings. However, this disclosure is not limited to the embodiments set forth below, but can be implemented in a variety of different forms. The following embodiments are provided only to fully disclose this disclosure and to inform those skilled in the art of its scope, and this disclosure is limited only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals denote the same or similar elements. Furthermore, in describing this disclosure, detailed descriptions of known functions or configurations contained herein will be omitted where it is determined that such description might unnecessarily obscure the subject matter of the disclosure. Additionally, the terminology described below is defined in consideration of the functions in this disclosure and may vary depending on the user, the user's intentions, or customs. Therefore, its definition should be made based on the entire contents of this specification.

[0062] In the following description, a base station is an entity that allocates resources to a terminal and can be at least one of a gNode B, eNode B, Node B, base station (BS), radio access unit, base station controller, and nodes on a network. A terminal can include a user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. In this disclosure, "downlink (UL)" refers to a radio link through which a base station transmits signals to a terminal, and "uplink (UL)" refers to a radio link through which a terminal transmits signals to a base station. Furthermore, while LTE or LTE-A systems may be described by way of example in the following description, embodiments of this disclosure can also be applied to other communication systems with similar technical backgrounds or channel types. Examples of such communication systems may include 5G (New Radio or NR), a fifth-generation mobile communication technology developed after LTE-A, and in the following description, "5G" can be a concept encompassing existing LTE, LTE-A, and other similar services. Moreover, based on the determination of those skilled in the art, this disclosure can also be applied to other communication systems with modifications without significantly departing from its scope.

[0063] In this document, it should be understood that each block and combination of blocks in a flowchart diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus used to produce a machine, such that the instructions, executable by the processor of the computer or other programmable data processing apparatus, create components for performing the functions specified in one or more flowchart blocks. These computer program instructions can also be stored in a computer-usable or computer-readable storage medium that can instruct the computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-usable or computer-readable storage medium produce an article of manufacture including instruction components that implement the functions specified in one or more flowchart blocks. Computer program instructions that execute on a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus to produce a computer-implemented process can provide steps for implementing the functions specified in the flowchart block(s).

[0064] Furthermore, each block in the flowchart diagram may represent a module, segment, or section of code, which includes one or more executable instructions for implementing a specified logical function(s). It should also be noted that in some alternative implementations, the functions described in a block may not occur in this order. For example, depending on the functions involved, two blocks shown consecutively may actually be executed substantially simultaneously, or sometimes they may be executed in reverse order.

[0065] As used in embodiments of this disclosure, the term "unit" refers to a software element or hardware element, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC), and a "unit" can perform a specific function. However, "unit" does not always have a meaning limited to software or hardware. A "unit" can be configured to be stored in addressable storage media or to execute one or more processors. Thus, a "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. The elements and functions provided by a "unit" can be combined into a smaller number of elements or "units," or divided into a larger number of elements or "units." Furthermore, these elements and "units" can be implemented to reproduce one or more CPUs within a device or secure multimedia card. Additionally, a "unit" in the embodiments may include one or more processors.

[0066] Wireless communication systems are evolving towards broadband wireless communication systems, using communication standards such as 3GPP High-Speed ​​Packet Access (HSPA), LTE (Long Term Evolution or Evolved Universal Terrestrial Radio Access (E-UTRA)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2 High-Speed ​​Packet Data (HRPD), Ultra Mobile Broadband (UMB), IEEE 802.16e, and typical voice-based services to provide high-speed and high-quality packet data services.

[0067] As a typical example of a broadband wireless communication system, the LTE system employs Orthogonal Frequency Division Multiplexing (OFDM) in the downlink (DL) and Single-Carrier Frequency Division Multiple Access (SC-FDMA) in the uplink (UL). The uplink refers to the radio link through which a User Equipment (UE) or Mobile Station (MS) transmits data or control signals to a Base Station (BS) (or eNode B), and the downlink refers to the radio link through which the Base Station transmits data or control signals to the UE. These multiple access schemes can separate the data or control information of each user by allocating and manipulating the time-frequency resources used to transmit each user's data or control information, thereby avoiding overlap and establishing orthogonality.

[0068] As a post-LTE communication system, 5G communication systems must freely reflect the various requirements of users, service providers, and others, and therefore must support services that meet these diverse needs. Services considered in 5G communication systems include enhanced mobile broadband (eMBB) communication, massive machine-type communication (mMTC), and ultra-reliable low-latency communication (URLLC), among others.

[0069] eMBB aims to provide higher data rates than those supported by existing LTE, LTE-A, or LTE-Pro systems. For example, in 5G communication systems, eMBB must provide a peak data rate of 20 Gbps in the downlink and 10 Gbps in the uplink for a single base station. Furthermore, 5G communication systems must provide higher user-aware data rates and maximum data rates to the UE. To meet these requirements, improved transmit / receive technologies, including further enhanced multiple-input multiple-output (MIMO) transmission techniques, are needed. Moreover, the data rates required by 5G communication systems can be achieved using bandwidths exceeding 20 MHz in the 3 to 6 GHz or 6 GHz or higher frequency bands, rather than using up to 20 MHz of transmit bandwidth in the 2 GHz band used in LTE.

[0070] Furthermore, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. mMTC has requirements such as supporting a large number of UEs in a cell, enhancing UE coverage, improving battery life, and reducing UE costs to effectively deliver IoT. Since IoT provides communication capabilities while simultaneously serving various sensors and devices, it must support a large number of UEs in a cell (e.g., 1,000,000 UEs / km²). Additionally, UEs supporting mMTC may require wider coverage than other services offered by 5G communication systems because UEs may be located in shaded areas, such as building basements, where the service is not covered by the cell due to its nature. UEs supporting mMTC must be configured to be inexpensive and may require very long battery lives, such as 10 to 15 years, as frequent battery replacements are difficult.

[0071] Finally, URLLC is a cellular-based mission-critical wireless communication service. For example, URLLC can be used for services such as remote control of robots or machines, industrial automation, drones, remote healthcare, and emergency alerts. Therefore, URLLC must provide communication with ultra-low latency and ultra-high reliability. For instance, services supporting URLLC must meet an air interface latency of less than 0.5 ms and may also require a packet error rate of 10⁻⁵ or lower. Therefore, for services supporting URLLC, 5G systems must provide shorter Transmission Intervals (TTIs) than other services and may also require designs that allocate significant resources in the frequency band to ensure the reliability of the communication link.

[0072] The three services in 5G—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. In this case, different transmit / receive technologies and parameters can be used between services to meet their varying requirements. Of course, 5G is not limited to these three services.

[0073] To meet the increased demand for wireless data services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "beyond 4G networks" or "post-LTE" systems. 5G communication systems are considered to be implemented in ultra-high frequency (mmWave) bands (e.g., the 60GHz band) to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance in the ultra-high frequency band, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are being discussed in 5G communication systems. Furthermore, in 5G communication systems, technologies for improving system networks are being developed based on evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and receiver interference cancellation. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding and modulation (ACM) schemes, as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0074] The internet is a human-centric network of connections where humans generate and consume information. It is now evolving into the Internet of Things (IoT), where distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE) has emerged, combining IoT technology and big data processing technology with connections to cloud servers and other systems. With the increasing demand for technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology in the implementation of IoT, recent research has focused on sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC). Such an IoT environment can provide intelligent internet technology (IT) services, creating new value for human life by collecting and analyzing data generated between interconnected things. IoT can be applied to various fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services, through the integration and combination of existing information technology (IT) with various industrial applications.

[0075] Consistent with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-type communication (MTC), and machine-to-machine (M2M) communication are being implemented using beamforming, MIMO, and array antenna technologies, which are part of 5G communication. Cloud radio access networks (cloud RAN), as an application of the aforementioned big data processing technologies, can also be seen as an example of the integration of 5G and IoT technologies.

[0076] With the advancements in wireless communication systems as described above, a variety of services can be provided, thus necessitating methods for the smooth delivery of these services.

[0077] [NR Time-Frequency Resources]

[0078] The frame structure of a 5G system will be described in more detail below with reference to the accompanying drawings.

[0079] Figure 1 The basic structure of the time-frequency domain in a 5G system is shown. The time-frequency domain is the radio resource domain used for transmitting data or control channels.

[0080] exist Figure 1 In this diagram, the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The basic unit of a resource in the time-frequency domain is a resource element (RE) 101, which can be defined as an orthogonal frequency division multiplexing (OFDM) symbol 102 along the time axis and a subcarrier 103 along the frequency axis. In the frequency domain, One (e.g., 12) consecutive REs can form a resource block (RB) 104.

[0081] Figure 2 This is a diagram illustrating the structure of frames, subframes, and time slots in a wireless communication system according to an embodiment of the present disclosure.

[0082] Figure 2 An example of the structure of frame 200, subframe 201, and time slot 202 is shown. A frame 200 can be defined as 10 ms. A subframe 201 can be defined as 1 ms, so a frame 200 can include a total of ten subframes 201. A time slot 202 or 203 can be defined as 14 OFDM symbols (i.e., the number of symbols per time slot). =14). A subframe 201 may include one or more time slots 202 and 203, and the number of time slots 202 and 203 in each subframe 201 may vary depending on the configuration value μ of the subcarrier spacing 204 or 205. Figure 2The examples illustrate the cases where the subcarrier spacing configuration value is µ=0 (204) and µ=1 (205). In the case of µ=0 (204), a subframe 201 may include one time slot 202, and in the case of µ=1 (205), a subframe 201 may include two time slots 203. That is, the number of time slots in each subframe... The number of time slots per frame can vary depending on the subcarrier spacing configuration value µ. It may also be different accordingly. and The µ configuration can be defined based on the subcarrier spacing in Table 1 below.

[0083] [Table 1]

[0084]

[0085] [Bandwidth Component (BWP)]

[0086] The bandwidth portion (BWP) configuration in a 5G communication system will now be described in detail with reference to the accompanying drawings.

[0087] Figure 3 An example of bandwidth configuration in a wireless communication system according to an embodiment of this disclosure is shown.

[0088] Figure 3 An example is shown where UE bandwidth 300 is configured to include two bandwidth portions, namely bandwidth portion #1 (BWP#1) 301 and bandwidth portion #2 (BWP#2) 302. The base station can configure one or more bandwidth portions for the UE, and the following information about each bandwidth portion can be configured as follows.

[0089] [Table 2]

[0090]

[0091] Obviously, the above examples are not limiting, and various parameters related to bandwidth can be configured for the UE in addition to the configuration information described above. The base station can transmit the above information to the UE via upper-layer signaling (e.g., Radio Resource Control (RRC) signaling). One or more configured bandwidth portions can be activated. Whether a configured bandwidth portion is activated can be transmitted from the base station to the UE semi-statically via RRC signaling or dynamically via downlink control information (DCI).

[0092] According to some embodiments, prior to Radio Resource Control (RRC) connection, the base station can configure an Initial Bandwidth Part (BWP) for initial access for the UE via the Master Information Block (MIB). More specifically, the UE can receive configuration information regarding the Control Resource Set (CORESET) and the search space. This configuration information can be used to send a PDCCH to receive system information (which may correspond to Residual System Information (RMSI) or System Information Block 1 (SIB1)) required for initial access via the MIB during the initial access step. Each of the Control Resource Set and the search space configured via the MIB can be considered as ID 0. The base station can notify the UE of configuration information regarding Control Resource Set #0 via the MIB, such as frequency allocation information, time allocation information, and parameter sets. Furthermore, the base station can notify the UE of configuration information regarding the monitoring period and timing of Control Resource Set #0, i.e., configuration information regarding search space #0, via the MIB. The UE can consider the frequency domain configured by Control Resource Set #0 obtained from the MIB as the Initial Bandwidth Part for initial access. The ID of the Initial Bandwidth Part can be considered as 0.

[0093] The bandwidth-related configurations supported by 5G can be used for various purposes.

[0094] According to some embodiments, if the bandwidth supported by the UE is less than the system bandwidth, the UE can support it through bandwidth configuration. For example, the base station can configure the frequency position of the bandwidth portion for the UE (configuration information 2), thereby enabling the UE to send / receive data at a specific frequency position within the system bandwidth.

[0095] Furthermore, according to some embodiments, the base station can configure multiple bandwidth portions for the UE to support different parameter sets. For example, to support the UE using both 15kHz and 30kHz subcarrier spacings for data transmission / reception, the two bandwidth portions can be configured with 15kHz and 30kHz subcarrier spacings, respectively. Different bandwidth portions can be frequency-division multiplexed (FDM), and if data needs to be transmitted / received at a specific subcarrier spacing, the bandwidth portion configured for that subcarrier spacing can be activated.

[0096] Furthermore, according to some embodiments, the base station can configure bandwidth portions with different bandwidth sizes for the UE to reduce UE power consumption. For example, if the UE supports a fairly large bandwidth (e.g., 100MHz) and always transmits / receives data at that bandwidth, considerable power consumption may occur. In particular, from a power consumption perspective, unnecessarily monitoring a downlink control channel with a large bandwidth of 100MHz when there is no service can be inefficient. To reduce UE power consumption, the base station can configure the UE with a bandwidth portion with a relatively small bandwidth, such as a 20MHz bandwidth portion. The UE can perform monitoring operations in the 20MHz bandwidth portion when there is no service, and if data has been transmitted, it can transmit / receive data with the 100MHz bandwidth portion as instructed by the base station.

[0097] Using the bandwidth configuration method, the UE can receive configuration information about the initial bandwidth portion via the MIB during the initial access step before RRC connection. More specifically, the UE can have a control resource set (CORESET) configured for the downlink control channel, which can be used to transmit downlink control information (DCI) to schedule system information blocks (SIBs) from the MIB of the physical broadcast channel (PBCH). The bandwidth of the control resource set configured by the MIB can be regarded as the initial bandwidth portion, and the UE can receive the physical downlink shared channel (PDSCH) through the configured initial bandwidth portion, through which the SIBs are transmitted. In addition to receiving SIBs, the initial bandwidth portion can also be used for other system information (OSI), paging, and random access.

[0098] [Bandwidth Component (BWP) Change]

[0099] If the UE has one or more bandwidth portions configured for this purpose, the base station can indicate to the UE to change (or switch or convert) the bandwidth portion by using the bandwidth portion indicator field within the DCI. For example, if the UE's currently active bandwidth portion is... Figure 3 If the bandwidth portion #1 301 is in the DCI, the base station can indicate the bandwidth portion #2 302 in the DCI using the bandwidth portion indicator, and the UE can change the bandwidth portion to the bandwidth portion #2 302 indicated by the bandwidth portion indicator in the received DCI.

[0100] As mentioned above, the DCI used for scheduling PDSCH or PUSCH can indicate a DCI-based bandwidth portion change. Therefore, upon receiving a bandwidth portion change request, the UE needs to be able to receive or transmit PDSCH or PUSCH scheduled by the corresponding DCI in the changed bandwidth portion without any problems. To this end, the standard specifies the required delay time (T) during the bandwidth portion change. BWP Requirements, for example, can be defined as follows.

[0101] [Table 3]

[0102]

[0103] The bandwidth portion of the delay time requirement depends on the UE's capability to support either Type 1 or Type 2. The UE can report the supported bandwidth portion delay time type to the base station.

[0104] If the UE receives a DCI including a bandwidth partial change indicator in time slot n, then according to the above requirements regarding the bandwidth partial change delay time, the UE can proceed no later than time slot n+T. BWP The change to the new bandwidth portion indicated by the bandwidth portion change indicator is completed at the specified time, and data channels scheduled by the corresponding DCI can be transmitted / received in the newly changed bandwidth portion. If the base station wants to schedule data channels using the new bandwidth portion, the base station can consider the UE's bandwidth portion change delay time (T). BWP This is used to determine the temporal resource allocation for the data channel. That is, when scheduling a data channel using a new bandwidth portion, the base station can combine the method used to determine the temporal resource allocation for the data channel to schedule the corresponding data channel after the bandwidth portion change delay time. Therefore, the UE may not expect the DCI indicating the bandwidth portion change to indicate a delay time less than the bandwidth portion change delay time (T). BWP The time slot offset (K0 or K2) value.

[0105] If the UE has already received a DCI indicating a partial change in bandwidth (e.g., DCI format 1_1 or 0_1), the UE may not perform transmission or reception for the time interval from the third symbol of the slot used to receive the PDCCH including the corresponding DCI to the start point of the slot indicated by the slot offset (K0 or K2) value indicated by the time domain resource allocation indicator field in the corresponding DCI. For example, if the UE has already received a DCI indicating a partial change in bandwidth in slot n, and if the slot offset value indicated by the corresponding DCI is K, the UE may not perform transmission or reception from the third symbol of slot n to the symbols before slot n+K (i.e., the last symbol of slot n+K-1).

[0106] [SS / PBCH block]

[0107] Next, the synchronization signal (SS) / PBCH block in 5G will be described.

[0108] The SS / PBCH block can refer to a physical layer channel block that includes the primary synchronization signal (PSS), secondary synchronization signal (SSS), and PBCH. Details are as follows.

[0109] -PSS: PSS is a signal that serves as a reference for downlink time / frequency synchronization and provides information about the cell ID.

[0110] -SSS: The SSS serves as a reference for downlink time / frequency synchronization and provides information about other parts of the cell ID that the PSS does not provide. Additionally, the SSS can be used as a reference signal for PBCH demodulation of the PBCH.

[0111] -PBCH: The PBCH provides the mandatory system information required by the UE to transmit / receive data and control channels. Mandatory system information may include search space-related control information indicating radio resource mapping information for control channels, scheduling control information for separate data channels used to transmit system information, etc.

[0112] -SS / PBCH Blocks: SS / PBCH blocks consist of a combination of PSS, SSS, and PBCH. One or more SS / PBCH blocks can be sent within a 5ms time period, and each sent SS / PBCH block can be distinguished by an index.

[0113] The UE can detect the PSS and SSS during the initial access procedure and can decode the PBCH. The UE can obtain the MIB from the PBCH, thereby receiving the configuration of control resource set (CORESET) #0 (which may correspond to the control resource set index 0). Assuming the demodulation reference signal (DMRS) transmitted in control resource set #0 is quasi-co-located (QCL) with the selected SS / PBCH block, the UE can monitor control resource set #0. The UE can receive system information using downlink control information transmitted in control resource set #0. The UE can obtain the random access channel (RACH) configuration information required for initial access from the received system information. The UE can send a physical RACH (PRACH) to the base station considering the selected SS / PBCH index, and the base station, having received the PRACH, can obtain information about the SS / PBCH block index selected by the UE. The base station can identify which block the UE has selected in each SS / PBCH block and can recognize that the associated control resource set #0 is being monitored.

[0114] [PDCCH: About DCI]

[0115] Next, we will describe downlink control information (DCI) in a 5G system in detail.

[0116] In 5G systems, scheduling information for uplink data (or Physical Uplink Shared Channel (PUSCH)) or downlink data (or Physical Downlink Shared Channel (PDSCH)) is included in the DCI and transmitted from the base station to the UE via the DCI. The UE can monitor the backoff DCI format and the non-backoff DCI format for either the PUSCH or PDSCH. The backoff DCI format may include predefined fixed fields between the base station and the UE, while the non-backoff DCI format may include configurable fields.

[0117] The DCI message undergoes channel coding and modulation before being transmitted via the Physical Downlink Control Channel (PDCCH). Cyclic Redundancy Check (CRC) can be attached to the DCI message payload, and the CRC can be scrambled by a Radio Network Temporary Identifier (RNTI) corresponding to the UE's identifier. Different RNTIs can be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control commands, or random access responses. That is, the RNTI is not explicitly sent but is included in the CRC calculation process. Upon receiving a DCI message transmitted via the PDCCH, the UE can use the assigned RNTI to identify the CRC, and if the CRC identification result is correct, the UE knows that the corresponding message has been sent.

[0118] For example, the DCI used for scheduling PDSCH about System Information (SI) can be scrambled using SI-RNTI. The DCI used for scheduling PDSCH about Random Access Response (RAR) messages can be scrambled using RA-RNTI. The DCI used for scheduling PDSCH about paging messages can be scrambled using P-RNTI. The DCI used for notifying Slot Format Indicator (SFI) can be scrambled using SFI-RNTI. The DCI used for notifying Transmit Power Control (TPC) can be scrambled using TPC-RNTI. The DCI used for scheduling UE-specific PDSCH or PUSCH can be scrambled using Cell RNTI (C-RNTI).

[0119] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, in which case CRC can be scrambled via C-RNTI. The DCI format 0_0 with CRC scrambling via C-RNTI can include, for example, the following information.

[0120] [Table 4]

[0121]

[0122] DCI format 0_1 ​​can be used as a non-back-off DCI for scheduling PUSCH, in which case CRC can be scrambled via C-RNTI. The DCI format 0_1 ​​with CRC scrambling via C-RNTI can include, for example, the following information.

[0123] [Table 5]

[0124]

[0125] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, in which case CRC can be scrambled via C-RNTI. The DCI format 1_0 with CRC scrambling via C-RNTI can include, for example, the following information.

[0126] [Table 6]

[0127]

[0128] DCI format 1_1 can be used as a non-back-off DCI for scheduling PDSCH, in which case CRC can be scrambled via C-RNTI. The DCI format 1_1 with CRC scrambling via C-RNTI may include, for example, the following information.

[0129] [Table 7]

[0130]

[0131] [PDCCH: CORESET, REG, CCE, and Search Space]

[0132] The downlink control channel in a 5G communication system will be described in more detail below with reference to the accompanying drawings.

[0133] Figure 4 An example of a control resource set (CORESET) for transmitting downlink control channels in a 5G wireless communication system is shown. Figure 4 An example is shown in which the UE bandwidth portion 410 is configured along the frequency domain and two control resource sets (control resource set #1 401 and control resource set #2 402) are configured along the time domain within a timeslot 420. Control resource sets 401 and 402 can be configured along the frequency domain in specific frequency resources 403 within the entire UE bandwidth portion 410. The control resource sets can be configured along one or more OFDM symbols in the time domain, and this can be defined as the control resource set duration 404. Reference Figure 4 In the example shown, control resource set #1 401 is configured to have a control resource set duration of 2 symbols, and control resource set #2 402 is configured to have a control resource set duration of 1 symbol.

[0134] The control resource set in 5G described above can be configured by the base station for the UE via upper-layer signaling (e.g., system information, master information block (MIB), or radio resource control (RRC) signaling). Configuring the control resource set for the UE means providing information including the control resource set identifier, control resource set frequency location, and control resource set symbol duration. For example, this may include the following information.

[0135] [Table 8]

[0136]

[0137]

[0138] In Table 9, the tci-StatesPDCCH (Transmit Configuration Indicator (TCI) status) configuration information may include information on one or more SS / PBCH block indices or Channel State Information Reference Signal (CSI-RS) indices that are quasi-co-located (QCLed) with the DMRS transmitted in the corresponding control resource set.

[0139] Figure 5 An example of the basic units constituting the time and frequency resources available in the downlink control channel in 5G is shown. Figure 5 The basic unit constituting the time and frequency resources of the control channel can be called a resource element group (REG) 503, and REG 503 can be defined by an OFDM symbol 501 along the time domain and a physical resource block (PRB) 502 (which has 12 subcarriers) along the frequency domain. The base station can configure the downlink control channel allocation unit by cascading REG 503.

[0140] Assuming the basic unit of downlink control channel allocation in 5G is as follows: Figure 5 The control channel element 504 shown can be a single CCE 504 that may include multiple REG 503s. (For description...) Figure 5 The REG 503 shown, for example, may include 12 REs, and if a CCE 504 includes 6 REs 503, then a CCE 504 may include 72 REs. Once configured, a downlink control resource set may include multiple CCE 504s, and a specific downlink control channel may be mapped to one or more CCE 504s and then transmitted according to the aggregation level (AL) in the control resource set. CCE 504s in the control resource set are distinguished by numbers, and the number of CCE 504s can be allocated according to a logical mapping scheme.

[0141] Figure 5The basic unit of the downlink control channel shown, REG 503, can include both a RE mapping the DCI and a region mapping the reference signal (DMRS) 505 used for decoding the DCI. Figure 5 As shown, three DMRS 505s can be transmitted within a single REG 503. Depending on the aggregation level (AL), the number of CCEs required to transmit the PDCCH can be 1, 2, 4, 8, or 16, and different numbers of CCEs can be used to achieve link adaptation of the downlink control channel. For example, in the case of AL=L, a downlink control channel can be transmitted with L CCEs. The UE needs to detect signals without information about the downlink control channel; therefore, a search space indicating a set of CCEs has been defined for blind decoding. The search space is a set of downlink control channel candidates, including the CCEs that the UE needs to attempt to decode for a given AL, and since 1, 2, 4, 8, or 16 CCEs can form a bundle across various ALs, the UE can have multiple search spaces. The search space set can be defined as a set of search spaces across all configured aggregation levels.

[0142] The search space can be categorized into a common search space and a UE-specific search space. A group of UEs or all UEs can search the common search space of the PDCCH to receive cell common control information, such as dynamic scheduling of system information or paging messages. For example, searching the common search space of the PDCCH can be used to receive PDSCH scheduling allocation information for transmitting SIBs, including cell operator information. In the case of a common search space, a group of UEs or all UEs need to receive the PDCCH; therefore, the common search space can be defined as a set of predetermined CCEs. Searching the UE-specific search space of the PDCCH can be used to receive scheduling allocation information for UE-specific PDSCHs or PUSCHs. The UE-specific search space can be defined specifically for the UE based on functions of various system parameters and the UE's identifier.

[0143] In 5G, base stations can configure parameters for the UE regarding the PDCCH search space via upper-layer signaling (such as SIB, MIB, or RRC signaling). For example, the base station can provide the UE with configurations such as the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the monitoring timing for each symbol in the search space time slots, the search space type (common search space or UE-specific search space), the combination of RNTI and DCI formats to be monitored in the corresponding search space, and the control resource set index used for monitoring the search space. For example, the following information may be included.

[0144] [Table 9]

[0145]

[0146]

[0147] Based on the configuration information, the base station can configure one or more search space sets for the UE. According to some embodiments, the base station can configure search space set 1 and search space set 2 for the UE, and can configure DCI format A scrambled by X-RNTI to be monitored in the common search space of search space set 1, and can configure DCI format B scrambled by Y-RNTI to be monitored in the UE-specific search space of search space set 2.

[0148] Depending on the configuration information, one or more search space sets can exist in a public search space or a UE-specific search space. For example, search space set #1 and search space set #2 can be configured as a public search space, and search space set #3 and search space set #4 can be configured as UE-specific search spaces.

[0149] The combinations of DCI format and RNTI given below can be monitored in the public search space. Obviously, the examples below are not restrictive.

[0150] -DCI format 0_0 / 1_0, where CRC is scrambled using C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, and SI-RNTI.

[0151] -DCI format 2_0, where CRC is scrambled via SFI-RNTI.

[0152] -DCI format 2_1, where CRC is scrambled via INT-RNTI

[0153] -DCI format 2_2, where CRC is scrambled using TPC-PUSCH-RNTI and TPC-PUCCH-RNTI.

[0154] -DCI format 2_3, where CRC is scrambled via TPC-SRS-RNTI.

[0155] The combinations of DCI formats and RNTI given below can be monitored within the UE-specific search space. Obviously, the examples below are not limiting.

[0156] -DCI format 0_0 / 1_0, where CRC is scrambled using C-RNTI, CS-RNTI, and TC-RNTI.

[0157] -DCI format 1_0 / 1_1, where CRC is scrambled using C-RNTI, CS-RNTI, and TC-RNTI.

[0158] The listed RNTIs can be defined and used as follows:

[0159] Cell RNTI (C-RNTI): Used for scheduling UE-specific PDSCH

[0160] Temporary Cell RNTI (TC-RNTI): Used for scheduling UE-specific PDSCH

[0161] Configuration-based scheduling RNTI (CS-RNTI): Used to schedule UE-specific PDSCHs with semi-static configurations.

[0162] Random Access RNTI (RA-RNTI): Used to schedule PDSCH during the random access step.

[0163] Paging RNTI (P-RNTI): Used to schedule the PDSCH for sending paging requests.

[0164] System Information RNTI (SI-RNTI): Used to schedule the transmission of system information via PDSCH.

[0165] Interrupt RNTI (INT-RNTI): Used to indicate whether the PDSCH has been punched.

[0166] Transmit power control of PUSCH RNTI (TPC-PUSCH-RNTI): Used to indicate power control commands regarding the PUSCH.

[0167] Transmit power control of PUCCH RNTI (TPC-PUCCH-RNTI): Used to indicate power control commands regarding the PUCCH.

[0168] Transmit power control of SRS RNTI (TPC-SRS-RNTI): Used to indicate power control commands regarding the SRS.

[0169] The DCI formats listed above can follow the definitions given below.

[0170] [Table 10]

[0171]

[0172] In 5G, the search space at the aggregation level L, which combines the control resource set p and the search space set s, can be represented by the following Equation 1.

[0173] [Equation 1]

[0174]

[0175] – L Aggregation level

[0176] - Carrier index

[0177] – Control resource set p The total number of CCEs in the country

[0178] – Time slot index

[0179] – Number of PDCCH candidates at aggregation level L

[0180] – = 0, …, -1: PDCCH candidate index at aggregation level L

[0181] – = 0, …, -1

[0182] – , , , , ,

[0183] – UE identifier

[0184] In the context of public search spaces, The value can correspond to 0.

[0185] In the case of a specific search space for the UE The value can correspond to a value that is changed by the UE's identifier (C-RNTI or ID configured by the base station for the UE) and time index.

[0186] In 5G, multiple search space sets can be configured with different parameters (e.g., the parameters in Table 10), and the group of search space sets monitored by the UE at each time point can be different accordingly. For example, if search space set #1 is configured with a time slot period of X, and search space set #2 is configured with a time slot period of Y, and if X and Y are different, then the UE can monitor search space set #1 and search space set #2 in a specific time slot, and can monitor one of search space set #1 and search space set #2 in another specific time slot.

[0187] [PDCCH: Span]

[0188] For scenarios with multiple PDCCH monitoring opportunities within a time slot, the UE can perform a UE capability report in each subcarrier interval. In this regard, the concept of a "span" can be used. A span refers to the consecutive symbols configured to allow the UE to monitor the PDCCH within a time slot, with each PDCCH monitoring opportunity falling within a span. A span can be represented as (X, Y), where X is the minimum number of symbols that must separate the first symbols of two consecutive spans, and Y is the number of consecutive symbols within a span that can be monitored. Here, the UE can monitor the PDCCH within a span, starting from the first symbol of the span and covering a range of Y symbols.

[0189] Figure 6 The span indicates the possible scenarios where the UE may have multiple PDCCH monitoring opportunities within a time slot in the wireless communication system. Possible spans are (X,Y) = (7,3), (4,3), and (2,2). These three cases... Figure 6 The symbols are denoted as "6-00", "6-05", and "6-10" respectively. For example, "6-00" can describe a case where there are two spans described by (7,3) within a time slot. The interval between the first symbols of the two spans is described as X=7, the PDCCH monitoring opportunity can exist within a total of Y=3 symbols from the first symbol of each span, and search spaces 1 and 2 can each exist within Y=3 symbols. As another example, "6-05" can describe a case where there are a total of three spans described by (4,3) within a time slot, and the second and third spans are separated by X'=5 symbols, which is greater than X=4.

[0190] [PDCCH: UE Capability Report]

[0191] The slot locations of the aforementioned public search space and UE-specific search space are indicated by the parameter "monitoringSymbolsWithinSlot" in Table 9, and the symbol positions within the slots are indicated as a bitmap by the parameter "monitoringSymbolsWithinSlot" in Table 9. Simultaneously, the UE can report the symbol positions within the slots of the search space it monitors to the base station through the following UE capabilities.

[0192] -UE Capability 1 (hereinafter referred to as FG 3-1). This UE capability can have the following meaning: If a monitoring opportunity (MO) exists within a time slot regarding the common search space of Type 1 and Type 3 or the UE-specific search space, as shown in Table 11 below, then the UE can monitor the corresponding MO when it is located within the first three symbols of that time slot. This UE capability is a mandatory capability that all UEs supporting NR must support, and the UE does not explicitly report to the base station whether it supports this UE capability.

[0193] [Table 11]

[0194]

[0195] -UE Capability 2 (hereinafter referred to as FG 3-2). This UE capability means that if there is a monitoring opportunity (MO) regarding a common search space or a UE-specific search space within a time slot, as shown in Table 12 below, the UE can monitor the corresponding MO regardless of the start symbol position of the corresponding MO. This UE capability is optionally supported by the UE, and whether or not the UE capability is supported is explicitly reported to the base station.

[0196] [Table 12]

[0197]

[0198] - UE Capability 3 (hereinafter referred to as FG 3-5, 3-5a, or 3-5b). This UE capability has the following meaning: if multiple monitoring opportunities (MOs) exist within a time slot regarding a common search space or a UE-specific search space, as shown in Table 13 below, then it indicates the pattern of MOs that the UE can monitor. The above pattern includes the interval X between the start symbols of different MOs and the maximum symbol length Y of a MO. The combination of (X,Y) supported by the UE can be one or more of {(2,2), (4,3), (7,3)}. This UE capability is optionally supported by the UE, and whether the UE capability is supported and the above combination of (X,Y) is explicitly reported to the base station.

[0199] [Table 13]

[0200]

[0201]

[0202]

[0203] The UE can report to the base station whether it supports capability 2 and / or capability 3 mentioned above, along with related parameters. The base station can allocate time-domain resources to the public search space and the UE-specific search space based on the UE's capability report. During resource allocation, the base station can ensure that the MO is not located in a position that the UE cannot monitor.

[0204] [QCL, TCI Status]

[0205] In wireless communication systems, one or more different antenna ports (which may be replaced by one or more channels, signals, and combinations thereof, but for convenience, will be collectively referred to as different antenna ports in the following description of this disclosure) can be associated with each other through a quasi-co-location (QCL) configuration as shown in Table 14 below. The TCI state is used to announce the QCL relationship between the PDCCH (or PDCCH DMRS) and another RS ​​or channel, and the description of the QCL between a reference antenna port A (reference RS#A) and another target antenna port B (target RS#B) means that the UE is allowed to apply some or all of the large-scale channel parameters estimated in antenna port A to channel measurements from antenna port B. Depending on the situation, the QCL may need to be associated with different parameters, such as 1) time tracking affected by average delay and delay spread, 2) frequency tracking affected by Doppler shift and Doppler spread, 3) radio resource management (RRM) affected by average gain, or 4) beam management (BM) affected by spatial parameters. Therefore, four types of QCL relationships are supported in NR, as shown in Table 14 below.

[0206] [Table 14]

[0207]

[0208] Spatial RX parameters can refer to some or all of various parameters as a whole, such as angle of arrival (AoA), power angular spectrum (PAS) of AoA, angle of departure (AoD), PAS of AoD, transmit / receive channel correlation, transmit / receive beamforming, and spatial channel correlation.

[0209] QCL relationships can be configured for a UE using the RRC parameters TCI-state and QCL-info, as shown in Table 15 below. Referring to Table 15, the base station can configure one or more TCI states for the UE, thereby informing about up to two QCL relationships (qcl-Type1, qcl-Type2) for the RS (i.e., the target RS) with the reference TCI state ID. Each QCL information (QCL-Info) included in each TCI state includes the serving cell index and BWP index of the reference RS indicated by the corresponding QCL information, the type and ID of the reference RS, and the QCL type, as shown in Table 14 above.

[0210] [Table 15]

[0211]

[0212] Figure 7 An example of base station beam allocation configured according to TCI status is shown. (Reference) Figure 7 The base station can transmit information about N different beams to the UE through N different TCI states. For example, in... Figure 7 As shown in the case of N=3, the base station can configure the qcl-Type2 parameters included in the three TCI states 700, 705 and 710 in qcl type D, and associate them with the CSI-RS or SSB corresponding to different beams, thereby notifying the antenna ports of different TCI states 700, 705 and 710 that they are associated with different spatial Rx parameters, i.e. different beams.

[0213] Tables 16 to 20 below list the valid TCI state configurations based on the target antenna port type.

[0214] Table 16 lists the valid TCI state configurations when the target antenna port is a CSI-RS (TRS) for tracking. TRS refers to an NZP CSI-RS configured with no repeating parameters and its trs-Info configured as "true" in the CSI RS. In Table 16, configuration 3 can be used for aperiodic TRS.

[0215] [Table 16] Valid TCI state configuration when the target antenna port is a CSI-RS (TRS) for tracking.

[0216]

[0217] Table 17 lists the valid TCI state configurations when the target antenna port is a CSI-RS for CSI. A CSI-RS for CSI refers to an NZP CSI-RS configured without any parameters indicating repetition (e.g., repetitive parameters) and whose trs-Info is not configured as "true" in the CSI-RS.

[0218] [Table 17] Effective TCI State Configuration when the target antenna port is a CSI-RS for CSI

[0219]

[0220] Table 18 lists the valid TCI status configurations when the target antenna port is a CSI-RS for beam management (BM) (which has the same meaning as a CSI-RS for L1 RSRP reporting). A CSI-RS for BM refers to an NZP CSI-RS configured with repeating parameters having an "on" or "off" value, and whose trs-Info is not configured as "true" in the CSI-RS.

[0221] [Table 18] Valid TCI state configuration when the target antenna port is for BM's CSI-RS (for L1 RSRP reporting)

[0222]

[0223] Table 19 lists the valid TCI state configurations when the target antenna port is PDCCH DMRS.

[0224] [Table 19] Effective TCI State Configuration when the target antenna port is PDCCH DMRS

[0225]

[0226] Table 20 lists the valid TCI state configurations when the target antenna port is PDSCH DMRS.

[0227] [Table 20] Effective TCI State Configuration when the target antenna port is PDSCH DMRS

[0228]

[0229] Based on the representative QCL configuration methods in Tables 16 to 20 above, the target antenna port and reference antenna port are configured and operated at each step, for example, “SSB” -> “TRS” -> “CSI-RS for CSI, or CSI-RS for BM, or PDCCH DMRS, or PDSCH DMRS”. Therefore, by associating the statistical characteristics that can be measured from SSB and TRS with the corresponding antenna ports, the UE's reception operation can be aided.

[0230] [PDCCH: Regarding TCI Status]

[0231] The specific TCI state combinations applicable to the PDCCH DMRS antenna port are given in Table 21 below. The fourth row in Table 21 corresponds to the combination assumed by the UE before RRC configuration, and cannot be configured after RRC.

[0232] [Table 21]

[0233]

[0234] In NR, such as Figure 8 The layered signaling method shown is supported for dynamic allocation of PDCCH beams. (Reference) Figure 8 The base station can configure N TCI states 805, 810, ..., 820 for the UE via RRC signaling 800, and can configure some states as the CORESET TCI state (825). Then, the base station can indicate one of the CORESET TCI states 830, 835, and 840 (845) to the UE via MAC CE signaling. The UE can then receive the PDCCH based on the beam information included in the TCI state indicated by the MAC CE signaling.

[0235] Figure 9 The TCI indication MAC CE signaling structure for PDCCH DMRS is shown. (Reference) Figure 9 The TCI indication MAC CE signaling used for PDCCH DMRS can be configured by 2 bytes (16 bits) and includes a 5-bit serving cell ID 915, a 4-bit CORESETID 920 and a 7-bit TCI status ID 925.

[0236] Figure 10 An example of beam configuration regarding the control resource set (CORESET) and search space as described above is shown. (Reference) Figure 10 The base station can indicate one of the TCI state lists (1005) included in the CORESET 1000 configuration via MAC CE signaling. Until different TCI states are indicated for the corresponding CORESET via different MAC CE signaling, the UE can consider that the same QCL information (beam #1) 1005 is applied to one or more search spaces 1010, 1015, and 1020 connected to the CORESET. The above PDCCH beam allocation method may have a problem: it is difficult to indicate beam changes that are delayed faster than MAC CE signaling, and the same beam is unilaterally applied to each CORESET regardless of search space characteristics, thus hindering flexible PDCCH beam operation. The following embodiments of this disclosure provide a more flexible PDCCH beam configuration and operation method. Although several different examples will be provided for ease of description of embodiments of this disclosure, they are not mutually exclusive and can be appropriately combined and applied for each situation.

[0237] The base station can configure one or more TCI states for a UE for a specific control resource set, and can activate one of the configured TCI states via a MAC CE activation command. For example, if {TCI state #0, TCI state #1, TCI state #2} are configured as TCI states for control resource set #1, the base station can send an activation command to the UE via MAC CE, causing TCI state #0 to be assumed to be a TCI state for control resource set #1. Based on the activation command for the TCI state received via MAC CE, the UE can correctly receive the DMRS for the corresponding control resource set based on the QCL information in the activated TCI state.

[0238] For a CORESET with configuration index 0 (CORESET#0), if the UE fails to receive a MAC CE activation command regarding the TCI state of CORESET #0, the UE may assume that the DMRS sent in CORESET #0 has been QCLed with the SS / PBCH block identified during the initial access procedure, or was not triggered by a PDCCH command during a contention-based random access procedure.

[0239] For a CORESET (CORESET #X) with a configuration index value other than 0, if the UE has not configured a TCI state for CORESET #X, or if the UE has configured one or more TCI states but has not received a MAC CE activation command to activate one of them, the UE may assume that the DMRS sent in CORESET #X has been QCLed with the SS / PBCH block identified during the initial access procedure.

[0240] [PDCCH: Regarding QCL Priority Rules]

[0241] The following sections will describe in detail the operations used to determine the QCL priority for the PDCCH.

[0242] If, during a specific PDCCH monitoring period, multiple control resource sets exist within the active bandwidth portion of one or more cells and overlap temporally, exhibiting the same or different QCL-Type D (Type D) characteristics, based on carrier aggregation operation within a single cell or frequency band, the UE can select a specific control resource set based on QCL priority and monitor control resource sets with the same QCL-Type D characteristics as the corresponding control resource set. That is, if multiple control resource sets overlap temporally, only one QCL-Type D characteristic can be received. QCL priority can be determined according to the following criteria.

[0243] Standard 1. The control resource set connected to the public search space has the lowest index in the cell corresponding to the lowest index among the cells including the public search space.

[0244] Standard 2. The control resource set connected to the UE-specific search space has the lowest index in the cell corresponding to the lowest index among the cells that include the UE-specific search space.

[0245] As stated above, if one criterion is not met, the next criterion can be applied. For example, if the control resource sets overlap in time during a specific PDCCH monitoring period, and if none of the control resource sets are connected to the common search space, but are connected to the UE-specific search space (e.g., if criterion 1 is not met), then the UE can omit the application of criterion 1 and apply criterion 2 instead.

[0246] If a control resource set is selected according to the above criteria, the UE can further consider two aspects regarding the QCL information configured for the control resource set. First, if control resource set 1 has CSI-RS 1 as a reference signal with a QCL-TypeD relationship, and if CSI-RS 1 has a QCL-TypeD relationship with reference signal SSB 1, and if another control resource set 2 has a QCL-TypeD relationship with reference signal SSB 1, then the UE can consider that control resource sets 1 and 2 have different QCL-TypeD characteristics. Second, if control resource set 1 has CSI-RS 1 configured for cell 1 as a reference signal with a QCL-TypeD relationship, and if CSI-RS 1 has a QCL-TypeD relationship with reference signal SSB 1, and if control resource set 2 has a QCL-TypeD relationship with reference signal CSI-RS 2 configured for cell 2, and if CSI-RS 2 has a QCL-TypeD relationship with the same reference signal SSB 1, then the UE can consider that these two control resource sets have the same QCL-TypeD characteristics.

[0247] Figure 12A method according to an embodiment of this disclosure is illustrated, wherein upon receiving a downlink control channel, a UE selects an acceptable set of control resources in a wireless communication system based on priority considerations; for example, the UE may be configured to receive multiple control resource sets that overlap in time during a specific PDCCH monitoring time 1210, and these multiple control resource sets may be connected to a common search space or a UE-specific search space for multiple cells. In the corresponding PDCCH monitoring time, control resource set 1 1215 connected to common search space 1 may exist in bandwidth portion 1 1200 of cell 1, and control resource set 1 1220 connected to common search space 1 and control resource set 21225 connected to UE-specific search space 2 may exist in bandwidth portion 1 1205 of cell 2. Control resource sets 1215 and 1220 may have a QCL-TypeD relationship with CSI-RS resource 1 configured in bandwidth portion 1 of cell 1, and control resource set 1225 may have a QCL-TypeD relationship with CSI-RS resource 1 configured in bandwidth portion 1 of cell 2. If Standard 1 is applied to the corresponding PDCCH monitoring time 1210, all other control resource sets having the same QCL-TypeD reference signal as control resource set 1 1215 can be received. Therefore, the UE can receive control resource sets 1215 and 1220 in the corresponding PDCCH monitoring time 1210. As another example, the UE can be configured to receive multiple control resource sets that overlap in time in a specific PDCCH monitoring time 1240, and these multiple control resource sets can be connected to a common search space or a UE-specific search space for multiple cells. In the corresponding PDCCH monitoring time, control resource set 1 1245 connected to UE-specific search space 1 and control resource set 2 1250 connected to UE-specific search space 2 can exist in the bandwidth portion 1 1235 of cell 1, and control resource set 1 1255 connected to UE-specific search space 1 and control resource set 2 1260 connected to UE-specific search space 3 can exist in the bandwidth portion 1 1230 of cell 2. Control resource sets 1245 and 1250 can have a QCL-TypeD relationship with CSI-RS resource 1 configured in bandwidth portion 1 of cell 1, control resource set 1255 can have a QCL-TypeD relationship with CSI-RS resource 1 configured in bandwidth portion 1 of cell 2, and control resource set 1260 can have a QCL-TypeD relationship with CSI-RS resource 2 configured in bandwidth portion 1 of cell 2. If standard 1 is applied to the corresponding PDCCH monitoring timing 1240, there is no common search space, therefore the next standard, standard 2, can be applied.If Standard 2 is applied to the corresponding PDCCH monitoring time 1240, all other control resource sets that have the same QCL-TypeD reference signal as control resource set 1 1245 can be received. Therefore, the UE can receive control resource sets 1245 and 1250 in the corresponding PDCCH monitoring time 1240.

[0248] [Regarding rate matching / punching]

[0249] The rate matching operation and the punching operation will be described in detail below.

[0250] When time and frequency resources A used to transmit arbitrary symbol sequences A overlap with arbitrary time and frequency sources B, considering resources C in the overlapping region of resources A and B, rate matching or puncturing operations can be considered for the transmission and reception operations of channel A. Specific operations may follow the description below.

[0251] Rate matching operation

[0252] - The base station can transmit channel A by mapping only the remaining resource areas of resource A, excluding the area of ​​resource C that overlaps with resource B, within the entire resource A to which the base station intends to transmit symbol sequence A to the UE. For example, when symbol sequence A is configured as {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the base station can sequentially map symbol sequence A to {resource #1, resource #2, resource #4}, which are the remaining resources in resource A excluding {resource #3} corresponding to resource C, and can transmit the same resources. Therefore, the base station can transmit symbol sequence {symbol #1, symbol #2, symbol #3} by mapping it to {resource #1, resource #2, resource #4} respectively.

[0253] The UE can determine resource A and resource B based on the scheduling information of symbol sequence A from the base station, and thus determine resource C, which is the overlapping area of ​​resource A and resource B. The UE can receive symbol sequence A under the assumption that symbol sequence A has been mapped and transmitted in the remaining area of ​​resource A except for resource C. For example, if symbol sequence A is configured as {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, then the UE can receive symbol sequence A, assuming that symbol sequence A is sequentially mapped to the remaining resources {resource #1, resource #2, resource #4}, which are the remaining resources in resource A except for {resource #3} corresponding to resource C. Therefore, the UE can assume that symbol sequence {symbol #1, symbol #2, symbol #3} has been mapped to {resource #1, resource #2, resource #4} and transmitted through it, and then perform a series of reception operations.

[0254] Drilling operation

[0255] If a base station intends to send symbol sequence A to a UE, and there exists a resource C in the entire resource A that overlaps with resource B, the base station can map symbol sequence A to the entire resource A. However, it can choose not to send the signal in the resource area corresponding to resource C, and can only send the remaining resource areas in resource A excluding resource C. For example, if symbol sequence A is configured as {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, then the base station can map symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} to resource A {resource #1, resource #2, resource #3, resource #4} respectively, and only send the remaining resources {resource #1, resource #2, resource #4} in resource A excluding {resource #3} corresponding to resource C. It can also omit sending {symbol #3} mapped to {resource #3} corresponding to resource C. Therefore, the base station can transmit the symbol sequence {symbol #1, symbol #2, symbol #4} by mapping them to {resource #1, resource #2, resource #4} respectively.

[0256] The UE can determine resource A and resource B based on the scheduling information of symbol sequence A from the base station, and thus determine resource C, which is the overlapping area of ​​resource A and resource B. The UE can receive symbol sequence A assuming that symbol sequence A has been mapped to the entire resource A, but will only transmit it in the remaining area of ​​resource A excluding resource C. For example, when symbol sequence A is configured as {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the UE can assume that symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} is mapped to resource A {resource #1, resource #2, resource #3, resource #4} respectively. However, {symbol #3} mapped to {resource #3} corresponding to resource C is not transmitted. The UE can receive the symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to the remaining resources {resource #1, resource #2, resource #4} in resource A, excluding {resource #3} corresponding to resource C. Therefore, the UE can assume that symbol sequence {symbol #1, symbol #2, symbol #4} has been mapped to {resource #1, resource #2, resource #4} and transmitted through these resources, and then perform a series of receive operations.

[0257] The following describes a method for configuring rate matching resources in a 5G communication system for rate matching purposes. Rate matching means adjusting the signal size by taking into account the amount of resources available for signal transmission. For example, rate matching of a data channel might mean that the data size is adjusted accordingly without mapping the data channel to a specific time and frequency resource region for transmission.

[0258] Figure 11 This illustrates a method by which the base station and UE consider downlink data channel and rate matching resources to transmit / receive data.

[0259] Figure 11The diagram illustrates a downlink data channel (PDSCH) 1101 and rate matching resources 1102. The base station can configure one or more rate matching resources 1102 for the UE via higher-layer signaling (e.g., RRC signaling). The rate matching resource 1102 configuration information may include time-domain resource allocation information 1103, frequency-domain resource allocation information 1104, and periodicity information 1105. The bitmap corresponding to the frequency-domain resource allocation information 1104 will be referred to hereinafter as the "first bitmap," the bitmap corresponding to the time-domain resource allocation information 1103 will be referred to as the "second bitmap," and the bitmap corresponding to the periodicity information 1105 will be referred to as the "third bitmap." If all or some of the time and frequency resources of the scheduled PDSCH 1101 overlap with the configured rate matching resources 1102, the base station can rate match and transmit the data channel 1101 in the rate matching resource portion 1102, and the UE can perform reception and decoding after assuming that the data channel 1101 has already been rate matched in the rate matching resource portion 1102.

[0260] The base station can dynamically notify the UE via DCI whether the PDSCH will perform rate matching in the configured rate matching resource section through additional configuration (e.g., corresponding to the "rate matching indicator" in the DCI format described above). Specifically, the base station can select some configured rate matching resources and group them into rate matching resource groups, and can indicate to the UE via DCI whether the data channels of each rate matching resource group are rate matched using a bitmap scheme. For example, when four rate matching resources RMR#1, RMR#2, RMR#3, and RMR#4 are configured, the base station can use two bits in the DCI field to indicate to the UE via a bitmap whether rate matching is performed in RMR#1 and RMR#2. For example, the base station can indicate this by using "1" when rate matching is to be performed, and by using "0" when rate matching is not to be performed.

[0261] 5G supports both "RB symbol level" and "RE level" granularity as a method for configuring the aforementioned rate matching resources for the UE. More specifically, this method can follow the configuration steps below.

[0262] RB symbol level

[0263] The UE can configure up to four RateMatchPatterns for each bandwidth segment via higher-layer signaling, and a RateMatchPattern can include the following.

[0264] -RateMatchPattern can include resources that are reserved resources within a bandwidth portion, having time and frequency resource domains for the corresponding reserved resources configured as a combination of RB-level bitmaps and symbol-level bitmaps in the frequency domain. Reserved resources can span one or two time slots. A time-domain pattern (periodicityAndPattern) can be additionally configured, in which time and frequency regions consisting of RB-level and symbol-level bitmap pairs are repeated.

[0265] -RateMatchPattern can include resource regions corresponding to time-domain patterns configured by CORESET within the bandwidth portion of the time-domain and frequency-domain resource regions, as well as search space configurations that repeat the corresponding resource regions.

[0266] RE Level

[0267] The UE can configure the following via upper-layer signaling.

[0268] The content may include configuration information for the RE corresponding to the LTE CRS (Cell-Specific Reference Signal or Common Reference Signal) mode (lte-CRS-ToMatchAround), the LTE CRS port number (nrofCRS-Ports) and (multiple) LTE-CRS-vshift values ​​(v-shift), the location information of the center subcarrier of the LTE carrier relative to the reference frequency point (e.g., reference point A) (carrierFreqDL), the bandwidth of the LTE carrier (carrierBandwidthDL), and the subframe configuration information corresponding to the Multicast-Broadcast Single Frequency Network (MBSFN) (mbsfn-SubframConfigList), etc. The UE can determine the location of the CRS within the NR slot corresponding to the LTE subframe based on the above information.

[0269] - The content may include configuration information about resource sets corresponding to one or more Zero Power (ZP) CSI-RS within the bandwidth portion.

[0270] [Regarding LTE CRS rate matching]

[0271] Next, the rate matching process for the aforementioned LTE CRS will be described in detail. In NR, for coexistence between Long Term Evolution (LTE) and New RAT (NR) (LTE-NR coexistence), the LTE Cell-Specific Reference Signal (CRS) mode can be configured for the NR UE. More specifically, the CRS mode can be provided by RRC signaling, which includes at least one parameter within the ServingCellConfigIE (information element) or ServingCellConfigCommonIE. Examples of parameters may include lte-CRS-ToMatchAround, lte-CRS-PatternList1-r16, lte-CRS-PatternList2-r16, crs-RateMatch-PerCORESETPoolIndex-r16, etc.

[0272] Rel-15 NR provided a feature that allowed configuring one CRS pattern for each serving cell via the parameter lte-CRS-ToMatchAround. Rel-16 NR expanded this feature to allow multiple CRS patterns to be configured for each serving cell. More specifically, UEs with a single TRP (Transmit and Receive Point) configuration can now configure one CRS pattern for each LTE carrier, while UEs with multiple TRP configurations can configure two CRS patterns for each LTE carrier. For example, a UE with a single TRP configuration can configure up to three CRS patterns for each serving cell via the parameter lte-CRS-PatternList1-r16. As another example, a UE with multiple TRP configurations can configure CRS for each TRP. That is, the CRS pattern for TRP1 can be configured via the parameter lte-CRS-PatternList1-r16, and the CRS pattern for TRP2 can be configured via the parameter lte-CRS-PatternList2-r16. If two TRPs are configured as described above, the parameter crs-RateMatch-PerCORESETPoolIndex-r16 determines whether the CRS modes of both TRP1 and TRP2 are applied to a specific Physical Downlink Shared Channel (PDSCH) or only the CRS mode for one TRP is applied. If the parameter crs-RateMatch-PerCORESETPoolIndex-r16 is configured to "Enable", only the CRS mode of one TRP is applied; otherwise, both CRS modes of both TRPs are applied.

[0273] Table 22 shows the ServingCellConfig IE including CRS mode, and Table 23 shows the RateMatchPatternLTE-CRS IE including at least one parameter regarding CRS mode.

[0274] [Table 22]

[0275]

[0276]

[0277]

[0278]

[0279] [Table 23]

[0280]

[0281] [PDSCH: Processing Time]

[0282] Next, the PDSCH processing time (PDSCH process time) will be described. If the base station schedules PDSCH transmission to the UE using DCI format 1_0, 1_1, or 1_2, the UE may require PDSCH processing time to receive the PDSCH by applying the transmission method indicated by the DCI (Modulation / Demodulation and Coding Indicator Index (MCS), demodulation reference signal related information, time and frequency resource allocation information, etc.). With this in mind, the PDSCH preparation process time is defined in the NR. The UE's PDSCH processing time can be followed by Equation 2 given below.

[0283] [Equation 2]

[0284]

[0285] The T described in Equation 2 above proc,1 Each parameter in the formula can have the following meanings.

[0286] -N1: The number of symbols determined based on the UE's capabilities and parameter set μ, according to either UE processing capability 1 or 2. If UE processing capability 1 is reported based on the UE's capability report, N1 can have the value in Table 24; if UE processing capability 2 is reported, and if the availability of UE processing capability 2 is configured via higher-layer signaling, it can have the value in Table 25. The parameter set μ can correspond to μ... PDCCH μ PDSCH μ UL The minimum value in order to maximize T proc,1 , and μ PDCCH μPDSCH μ UL It can refer to the parameter set of the PDCCH that schedules the PDSCH, the parameter set of the scheduled PDSCH, and the parameter set of the uplink channel to which HARQ-ACK is to be sent.

[0287] [Table 24]

[0288] PDSCH processing time under PDSCH processing capacity 1

[0289]

[0290] [Table 25]

[0291] PDSCH processing time under PDSCH processing capacity 2

[0292]

[0293] - κ:64

[0294] -T ext If the UE uses a shared spectrum channel access scheme, then the UE can calculate T. ext And apply it to the PDSCH processing time. Otherwise, assume T ext It is 0.

[0295] - If l1, representing the PDSCH DMRS position value, is 12, then N in Table 24 above 1,0 Its value is 14, otherwise its value is 13.

[0296] - Regarding PDSCH mapping type A, if the last symbol of the PDSCH is the i-th symbol in the time slot where the PDSCH was sent, and if i < 7, then d 1,1 It is 7-i, otherwise d 1,1 It is 0.

[0297] -d2: If a PUCCH with a high priority index overlaps in time with another PUCCH or a PUSCH with a low priority index, then d2 for the PUCCH with the high priority index can be configured to the value reported from the UE. Otherwise, d2 is 0.

[0298] -If PDSCH mapping type B is used for UE processing capability 1, then d 1,1 The value can be determined by the number of symbols (L) of the scheduled PDSCH and the number of overlapping symbols between the PDCCH that scheduled the PDSCH and the scheduled PDSCH, as shown below.

[0299] -If L≥7, then d 1,1 = 0.

[0300] -If L≥4 and L≤6, then d 1,1 = 7 – L.

[0301] -If L=3, then d 1,1 = min (d, 1).

[0302] -If L=2, then d 1,1 = 3 + d.

[0303] -If PDSCH mapping type B is used for UE processing capability 2, then d 1,1 The value can be determined by the number of symbols (L) of the scheduled PDSCH and the number of overlapping symbols between the PDCCH that scheduled the PDSCH and the scheduled PDSCH, as shown below.

[0304] -If L≥7, then d 1,1 = 0.

[0305] -If L≥4 and L≤6, then d 1,1 = 7 – L.

[0306] -If L=2,

[0307] - If the scheduling PDCCH exists within a CORESET containing three symbols, and if the CORESET and the scheduling PDSCH have the same starting symbol, then d 1,1 = 3.

[0308] -Otherwise, d 1,1 = d.

[0309] - If the UE supports capability 2 within a given serving cell, and if processingType2Enabled (upper-layer signaling) is configured to be "enabled" for the corresponding cell, the UE can apply PDSCH processing time based on UE processing capability 2.

[0310] If the position of the first uplink transmission symbol of the PUCCH that includes HARQ-ACK information (corresponding to the position defined as the HARQ-ACK transmission time point) K 1. The PUCCH resources used for sending HARQ-ACK and the timing advance effect that can be considered) are not earlier than T. proc,1 The UE needs to send a valid HARQ-ACK message starting from the first uplink transmission symbol after the last symbol of the PDSCH within the specified time. That is, the UE only needs to send a PUCCH including HARQ-ACK if the PDSCH processing time is sufficient. Otherwise, the UE cannot provide the base station with valid HARQ-ACK information corresponding to the scheduled PDSCH. The above T... proc,1This can be used for both normal CP and extended CP scenarios. When the PDSCH has two PDSCH transmission positions configured within a time slot, d is calculated by referring to the first PDSCH transmission position within the corresponding time slot. 1,1 .

[0311] [PDSCH: Receive preparation time during cross-carrier scheduling]

[0312] Next, in sending the parameter set (μ) of the scheduling PDCCH PDCCH ) and the parameter set (μ) sent by the corresponding PDSCH scheduled by the PDCCH. PDSCH In the case of different cross-carrier scheduling, the UE's PDSCH reception preparation time (N) will be described as the time interval between the PDCCH and PDSCH. pdsch ).

[0313] If μ PDCCH <μ PDSCH Then, N after the last symbol of the PDCCH that schedules the corresponding PDSCH. pdsch Scheduled PDSCHs cannot be sent before the first symbol of a time slot following a symbol. The corresponding PDSCH transmission symbols may include DM-RS.

[0314] If μ PDCCH >μ PDSCH Then, the last symbol of the PDCCH that schedules the corresponding PDSCH can be used in N. pdsch The scheduled PDSCH is sent after each symbol. The corresponding PDSCH transmission symbol may include DM-RS.

[0315] [Table 25] Based on the N of the scheduled PDCCH subcarrier spacing pdsch

[0316]

[0317] [About SRS]

[0318] Next, an uplink channel estimation method using the UE's Sounding Reference Signal (SRS) will be described. The base station can configure at least one SRS configuration for each uplink base station (BWP) to transmit configuration information for SRS transmission to the UE, and can also configure at least one SRS resource set for each SRS configuration. For example, the base station and the UE can exchange higher-layer signaling information as follows to transmit information about the SRS resource set.

[0319] - srs-ResourceSetId: SRS resource set index

[0320] - srs-ResourceIdList: A set of SRS resource indexes referenced by the SRS resource set.

[0321] - resourceType: The time-domain transmission configuration of the SRS resources referenced by the SRS resource set, and can be configured as "Periodic," "Semi-Persistent," or "Aperiodic." If configured as "Periodic" or "Semi-Persistent," associated CSI-RS information can be provided based on the location where the SRS resource set is used. If configured as "Aperiodic," aperiodic SRS resource trigger list / slot offset information can be provided, and associated CSI-RS information can be provided based on the location where the SRS resource set is used.

[0322] - usage: Configuration of the usage location of SRS resources referenced by the SRS resource set, and can be configured as one of "beamManagement", "codebook", "nonCodebook" and "antennaSwitching".

[0323] -α, p0, pathlossReferenceRS, srs-PowerControlAdjustmentStates: Provides parameter configuration for adjusting the transmit power of the SRS resources referenced by the SRS resource set.

[0324] The UE can understand that the SRS resources included in a set of SRS resource indexes referenced by the SRS resource set follow the information configured for the SRS resource set.

[0325] In addition, the base station and UE can send / receive higher-layer signaling information to transmit individual configuration information about SRS resources. For example, individual configuration information about SRS resources may include time-frequency domain mapping information within the time slots of the SRS resources, which may include information about frequency hopping within or between time slots of the SRS resources. Individual configuration information about SRS resources may include the time-domain transmission configuration of the SRS resources and may be configured as "periodic," "semi-persistent," and "aperiodic." The time-domain transmission configuration of the SRS resources may be restricted to having the same time-domain transmission configuration as the set of SRS resources that includes the SRS resources. If the time-domain transmission configuration of the SRS resources is configured as "periodic" or "semi-persistent," the time-domain transmission configuration may also include the SRS resource transmission period and time slot offset (such as periodicityAndOffset).

[0326] The base station can activate or deactivate the UE's SRS transmission via higher-layer signaling, including RRC signaling, MAC CE signaling, or L1 signaling (e.g., DCI). For example, the base station can activate or deactivate the UE's periodic SRS transmission via higher-layer signaling. The base station can indicate the activation of an SRS resource set with a resourceType configured as "periodic" via higher-layer signaling, and the UE can transmit SRS resources referenced in the activated SRS resource set. The intra-slot time-frequency domain resource mapping of the transmitted SRS resources follows the resource mapping information configured for the SRS resources, and the slot mapping, including the transmission period and slot offset, follows the periodicityAndOffset configured for the SRS resources. Furthermore, the spatial domain transmission filter applied to the transmitted SRS resources can refer to the spatial relationship information configured for the SRS resources, or it can refer to the relevant CSI-RS information configured for the SRS resource set including the SRS resources. The UE can transmit SRS resources within the uplink BWP activated for periodic SRS resources activated via higher-layer signaling.

[0327] For example, a base station can activate or deactivate a UE's semi-persistent SRS transmission via higher-layer signaling. The base station can indicate the activation of an SRS resource set via MAC CE signaling, and the UE can transmit the SRS resources referenced by the activated SRS resource set. The SRS resource set activated via MAC CE signaling can be restricted to an SRS resource set with a resourceType configured as "semi-persistent". The intra-slot time-frequency domain resource mapping of the transmitted SRS resources follows the resource mapping information configured for the SRS resources, and the slot mapping, including the transmission period and slot offset, follows the periodicityAndOffset configured for the SRS resources. Furthermore, the spatial domain transmission filter applied to the transmitted SRS resources can refer to the spatial relation information configured for the SRS resources, or it can refer to the relevant CSI-RS information configured for the SRS resource set including the SRS resources. If the SRS resources have spatial relation information configured for this purpose, the spatial domain transmission filter can be determined by referring to the configuration information about the spatial relation information transmitted via MAC CE signaling activating semi-persistent SRS transmission, without having to follow the same configuration information. The UE can transmit SRS resources within the uplink BWP activated for semi-persistent SRS resources activated via higher-layer signaling.

[0328] For example, a base station can trigger an aperiodic SRS transmission by the UE via a DCI. The base station can indicate one of the aperiodic SRS triggers (aperiodic SRS-ResourceTrigger) via the SRS request field of the DCI. The UE understands that the SRS resource set, which includes the aperiodic SRS resource trigger indicated by the DCI in the aperiodic SRS resource trigger list in the SRS resource set configuration information, has been triggered. The UE can transmit the SRS resource referenced by the triggered SRS resource set. The time-frequency domain resource mapping within the time slot of the transmitted SRS resource follows the resource mapping information configured for the SRS resource. Furthermore, the time slot mapping of the transmitted SRS resource can be determined by the time slot offset between the SRS resource and the PDCCH including the DCI, which can refer to the values ​​included in the time slot offset set configured for the SRS resource set. Specifically, as the time slot offset between the SRS resource and the PDCCH including the DCI, the value indicated in the time domain resource allocation field of the DCI can be applied from the offset values ​​included in the time slot offset set configured for the SRS resource set. Furthermore, the spatial domain transmission filter applied to the transmitted SRS resources can refer to the spatial relationship information configured for the SRS resources, or it can refer to the relevant CSI-RS information configured for the SRS resource set including the SRS resources. The UE can transmit SRS resources within the uplink BWP activated for aperiodic SRS resources triggered by DCI.

[0329] If the base station triggers aperiodic SRS transmission by the UE via DCI, a minimum time interval may be required between the transmitted SRS and the PDCCH containing the DCI that triggered the aperiodic SRS transmission, allowing the UE to transmit the SRS by applying configuration information about the SRS resources. The time interval for the UE to transmit SRS can be defined as the number of symbols between the last symbol of the PDCCH containing the DCI that triggered the aperiodic SRS transmission and the first symbol of the first SRS source mapped to the first transmitted SRS source(s) among the transmitted SRS(s) resources(s). The minimum time interval can be determined with reference to the PUSCH preparation time required for the UE to prepare for PUSCH transmission. Furthermore, the minimum time interval can have different values ​​depending on the usage location of the SRS resource set including the transmitted SRS resources. For example, the minimum time interval can be determined as N² symbols, defined taking into account the UE's processing capacity, which follows the UE's capabilities, with reference to the UE's PUSCH preparation time. Furthermore, if the usage location of the SRS resource set, including the transmitted SRS resources, is configured as "codebook" or "antennaSwitching," the minimum time interval can be determined to be N² symbols. If the usage location is configured as "nonCodebook" or "beamManagement," the minimum time interval can be determined to be N²+14 symbols. If the time interval used for aperiodic SRS transmission is greater than or equal to the minimum time interval, the UE can transmit aperiodic SRS. If the time interval used for aperiodic SRS transmission is less than the minimum time interval, the UE can ignore the DCI that triggers aperiodic SRS.

[0330] [Table 26]

[0331]

[0332] Referring to a reference signal, the configuration information spatialRelationInfo in Table 26 above can be applied to the beam used for SRS transmission corresponding to the beam information of the corresponding reference signal. For example, the configuration of spatialRelationInfo may include the information given in Table 27 below.

[0333] [Table 27]

[0334]

[0335] Referring to the `spatialRelationInfo` configuration, the SS / PBCH block index, CSI-RS index, or SRS index can be configured as the index of a reference signal to be referenced, so as to use the beam information of a specific reference signal. The higher-layer signaling `referenceSignal` corresponds to the configuration information indicating which reference signal's beam information to reference in the corresponding SRS transmission. `ssb-Index` refers to the SS / PBCH block index, `csi-RS-Index` refers to the CSI-RS index, and `srs` refers to the SRS index. If the higher-layer signaling `referenceSignal` has the configuration value "ssb-Index", the UE can apply the receive beam used to receive the SS / PBCH block corresponding to `ssb-Index` as the transmit beam for the corresponding SRS transmission. If the higher-layer signaling `referenceSignal` has the configuration value "csi-RS-Index", the UE can apply the receive beam used to receive the CSI-RS corresponding to `csi-RS-Index` as the transmit beam for the corresponding SRS transmission. If the higher-layer signaling referenceSignal has the configuration value "srs", the UE can use the receive beam used to transmit the SRS corresponding to srs as the transmit beam for the corresponding SRS.

[0336] [PUSCH: Regarding the transmission scheme]

[0337] Next, the PUSCH transmission scheduling scheme will be described. PUSCH transmissions can be dynamically scheduled by UL authorization within the DCI, or operated through configured authorization type 1 or type 2. Dynamic scheduling instructions for PUSCH transmissions can be given via DCI format 0_0 or 0_1.

[0338] Configured authorization type 1 PUSCH transmissions can be semi-statically configured via upper-layer signaling receiving of the `configuredGrantConfig` in Table 28, which includes `rrc-ConfiguredUplinkGrant`, without needing to receive UL authorizations within the DCI. After receiving a `configuredGrantConfig` in Table 28, which does not include `rrc-ConfiguredUplinkGrant`, via upper-layer signaling, UL authorizations within the DCI can be semi-persistently scheduled for configured authorization type 2 PUSCH transmissions. If the PUSCH transmission is operated by a configured authorization, the parameters applied to the PUSCH transmission are applied via `configuredGrantConfig` (upper-layer signaling) in Table 28, except for the scaling of `dataScramblingIdentityPUSCH`, `txConfig`, `codebookSubset`, `maxRank`, and `UCI-OnPUSCH` provided by `pusch-Config` (upper-layer signaling) in Table 29. If transformPrecoder is provided in configuredGrantConfig (higher-layer signaling) in Table 28, the UE will apply tp-pi2BPSK in pusch-Config in Table 29 to PUSCH transmissions by the configured grant operation.

[0339] [Table 28]

[0340]

[0341]

[0342] Next, the PUSCH transmission method will be described. The DMRS antenna port used for PUSCH transmission is the same as the antenna port used for SRS transmission. PUSCH transmission can follow either a codebook-based or non-codebook-based transmission method depending on whether the txConfig value in the pusch-Config, which serves as upper-layer signaling, is "codebook" or "nonCodebook".

[0343] As described above, PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can be semi-statically configured via configured authorization. Upon receiving a scheduling instruction for PUSCH transmission via DCI format 0_0, the UE performs beam configuration for PUSCH transmission using the pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource with the smallest ID within the active uplink BWP in the serving cell, and PUSCH transmission is based on a single antenna port. The UE does not expect PUSCH transmission to be scheduled via DCI format 0_0 within a BWP that does not have a PUCCH resource configured with pucch-spatialRelationInfo. If the UE has not configured txConfig in pusch-Config in Table 29, the UE does not expect scheduling via DCI format 0_1.

[0344] [Table 29]

[0345]

[0346] Next, codebook-based PUSCH transmission will be described. Codebook-based PUSCH transmission can be dynamically scheduled using DCI format 0_0 or 0_1, and can be semi-statically configured with configured grants. If codebook-based PUSCH is dynamically scheduled using DCI format 0_1, or semi-statically configured with configured grants, the UE determines the precoder used for PUSCH transmission based on the SRS Resource Indicator (SRI), the Transmit Precoding Matrix Indicator (TPMI), and the transmission rank (the number of PUSCH transmission layers).

[0347] In this scenario, the SRI can be provided via the SRS resource indicator in the DCI or configured via the srs-ResourceIndicator as upper-layer signaling. When transmitting codebook-based PUSCH, the UE can configure at least one SRS resource and up to two. When providing an SRI to the UE via the DCI, the SRS resource indicated by the corresponding SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH including the SRI. Furthermore, the TPMI and transmission rank can be provided via "Precoding Information and Layer Number" (a field within the DCI) or configured via precodingAndNumberOfLayers (upper-layer signaling). The TPMI is used to indicate the precoder applied to PUSCH transmission. If the UE has configured one SRS resource, the TPMI indicates the precoder to be applied to that configured SRS resource. If the UE has configured multiple SRS resources, the TPMI indicates the precoder to be applied to the SRS resources indicated by the SRI.

[0348] The precoder used for PUSCH transmission is selected from an uplink codebook with the same number of antenna ports as the nrofSRS-Ports value in the SRS-Config (which is upper-layer signaling). In codebook-based PUSCH transmission, the UE determines the codebook subset based on the TPMI and codebookSubset within the pusch-Config, which serves as upper-layer signaling. The codebookSubset within the pusch-Config, which serves as upper-layer signaling, can be configured as one of "fullyAndPartialAndNonCoherent", "partialAndNonCoherent", or "nonCoherent" based on the UE capabilities reported by the UE to the base station. If the UE has reported "partialAndNonCoherent" as a UE capability, the UE does not expect the value of the codebookSubset, which serves as upper-layer signaling, to be configured as "fullyAndPartialAndNonCoherent". Furthermore, if the UE has reported "nonCoherent" as a UE capability, the UE does not expect the value of codebookSubset, as upper-layer signaling, to be configured as "fullyAndPartialAndNonCoherent" or "partialAndNonCoherent". If nrofSRS-Ports in the SRS-ResourceSet (which is upper-layer signaling) indicates two SRS antenna ports, the UE does not expect the value of codebookSubset, as upper-layer signaling, to be configured as "partialAndNonCoherent".

[0349] A UE can configure an SRS resource set, where the purpose value in the SRS-ResourceSet used for upper-layer signaling is configured as "codebook", and an SRS resource can be indicated by the SRI in the corresponding SRS resource set. If multiple SRS resources are configured in the SRS resource set, and the purpose value in the SRS-ResourceSet used for upper-layer signaling is configured as "codebook", the UE expects the value of nrofSRS-Ports in the SRS-Resource used for upper-layer signaling to be the same for all SRS resources.

[0350] The UE transmits one or more SRS resources included in the SRS resource set to the base station according to upper-layer signaling, where the usage value is configured as "codebook". The base station instructs the UE to perform PUSCH transmission by using the transmission beam information of a selected SRS resource from the SRS resources transmitted by the UE. In this case, in codebook-based PUSCH transmission, the SRI is used as information for selecting an SRS resource and is included in the DCI. Furthermore, the base station may include information in the DCI indicating the TPMI and the rank used by the UE for PUSCH transmission. Using the SRS resource indicated by the SRI, the UE can apply a precoder indicated by the rank and a TPMI based on the transmission beam indication of the corresponding SRS resource when performing PUSCH transmission.

[0351] Next, we will describe non-codebook-based PUSCH transmission. Non-codebook-based PUSCH transmission can be dynamically scheduled using DCI format 0_0 or 0_1, and can be semi-statically operated using configured authorization. If at least one SRS resource is configured in the SRS resource set, and the usage value in the SRS-ResourceSet (higher-layer signaling) is "nonCodebook", then non-codebook-based PUSCH transmission can be scheduled for the UE using DCI format 0_1.

[0352] For an SRS resource set with a usage value of "nonCodebook" within the SRS-ResourceSet (higher-layer signaling), a connected NZP CSI-RS resource (non-zero power CSI-RS) can be configured for the UE. The UE can calculate the precoder for SRS transmission by measuring the NZP CSI-RS resource connected to the SRS resource set. If the difference between the last received symbol of the non-periodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of the non-periodic SRS transmission in the UE is less than 42 symbols, the UE does not expect the information about the precoder for SRS transmission to be updated.

[0353] If the resourceType configuration value in the SRS-ResourceSet (higher-layer signaling) is "aperiodic", then the connected NZP CSI-RS is indicated by an SRS request, which is a field within DCI format 0_1 ​​or 1_1. If the connected NZP CSI-RS resource is an aperiodic NZP CSI-RS resource, then the presence of a connected NZP CSI-RS is indicated by a value for the SRS request (a field within DCI format 0_1 ​​or 1_1) that is not "00". The corresponding DCI should not indicate cross-carrier or cross-BWP scheduling. Furthermore, if the SRS request value indicates the presence of an NZP CSI-RS, then the NZP CSI-RS is located in the time slot used to transmit the PDCCH including the SRS request field. In this case, the TCI state configured for the scheduled subcarrier is not configured as QCL-TypeD.

[0354] If a periodic or semi-persistent SRS resource set is configured, the associated CSI-RS within the SRS-ResourceSet (higher-layer signaling) can indicate the connected NZP CSI-RS. Regarding non-codebook-based transmission, the UE does not expect the higher-layer signaling spatialRelationInfo for SRS resources and the associated CSI-RS within the SRS-ResourceSet (higher-layer signaling) to be configured together.

[0355] If the UE is configured with multiple SRS resources, it can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. In this case, the SRI can be indicated by the SRS Resource Indicator field in the DCI, or configured by the srs-ResourceIndicator as upper-layer signaling. Similar to the codebook-based PUSCH transmission described above, if the SRI is provided to the UE via the DCI, the SRS resource indicated by the corresponding SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH including the SRI. The UE can use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be transmitted simultaneously in the same symbol within an SRS resource set and the maximum number of SRS resources are determined by the UE capabilities reported by the UE to the base station. In this case, the SRS resources transmitted simultaneously by the UE occupy the same RB. The UE configures one SRS port for each SRS resource. Only one SRS resource set in the SRS-ResourceSet used for upper-layer signaling can be configured with the usage value set to "nonCodebook", and a maximum of four SRS resources can be configured for PUSCH transmission based on non-codebook.

[0356] The base station sends an NZP-CSI-RS connected to the SRS resource set to the UE, and the UE calculates a precoder for transmitting one or more SRS resources in the corresponding SRS resource set based on the measurement results received upon receiving the corresponding NZP-CSI-RS. The UE applies the calculated precoder when transmitting one or more SRS resources from the SRS resource set to the base station, where the configured purpose is "nonCodebook," and the base station selects one or more SRS resources from the received one or more SRS resources. Combined with nonCodebook-based PUSCH transmission, the SRI indication can represent an index of one or more SRS resources or a combination of SRS resources, and the SRI is included in the DCI. In this case, the number of SRS resources indicated by the SRI transmitted by the base station can be the same as the number of transmission layers of the PUSCH, and the UE transmits the PUSCH by applying the precoder used for SRS resource transmission to each layer.

[0357] [PUSCH: Preparation procedure time]

[0358] Next, the PUSCH preparation process time will be described. If the base station schedules the UE to transmit PUSCH using DCI format 0_0, 0_1, or 0_2, the UE may require a PUSCH preparation process time to transmit the PUSCH by applying the transmission method indicated by the DCI (SRS resource transmission precoding method, number of transmission layers, spatial transmission filter). With this in mind, the PUSCH preparation process time is defined in the NR. The UE's PUSCH preparation process time can be followed by Equation 3 given below.

[0359] [Equation 3]

[0360] T proc,2 = max(( N2+ d 2,1 + d2)( 2048 + 144 ) κ2 -μ T c + T ext + T switch , d 2,2 )

[0361] The T described in Equation 3 above proc,2 Each parameter in the formula can have the following meanings.

[0362] -N2: The number of symbols determined based on the UE's capabilities and parameter set μ, according to either the UE's processing capability 1 or 2. If the UE's processing capability 1 is reported based on the UE's capability report, then N2 can have the value in Table 30; if the UE's processing capability 2 is reported, and if the availability of the UE's processing capability 2 is configured via higher-layer signaling, then N2 can have the value in Table 31.

[0363] [Table 30]

[0364]

[0365] [Table 31]

[0366]

[0367] (11 for frequency range 1)

[0368] -d 2,1 If all resource elements of the first OFDM symbol sent by PUSCH include DM-RS, then the symbol count is determined to be 0; otherwise, it is 1.

[0369] - κ:64

[0370] -μ: Follows the... and Between T proc,2 Larger values. This refers to the set of parameters used to send the downlink PDCCH, which includes the DCI scheduling PUSCH, and... This refers to the set of parameters used for sending PUSCH in the uplink.

[0371] -Tc: has .

[0372] -d 2,2 If the DCI of the PUSCH scheduling indicates a BWP handover, then the BWP handover time is followed; otherwise, it is 0.

[0373] -d2: If OFDM symbols overlap in time between a PUSCH with a high-priority index and a PUCCH with a low-priority index, then the d2 value of the PUSCH with the high-priority index is used. Otherwise, d2 is 0.

[0374] -T ext If the UE uses a shared spectrum channel access scheme, then the UE can calculate T. ext And apply it to the PUSCH preparation process time. Otherwise, assume T ext It is 0.

[0375] -T switch If the uplink handover interval is triggered, then assume T switch This is the switching interval. Otherwise, assume T... switch It is 0.

[0376] Considering the timing advance between the uplink and downlink, and the impact of the time-domain resource mapping information of the PUSCH scheduled by the DCI, if the first symbol of the PUSCH is earlier than the last symbol of the PDCCH from the DCI that schedules the PUSCH, then... proc,2 If the first uplink symbol that follows starts earlier, the base station and UE can determine that the PUSCH preparation time is insufficient. Otherwise, the base station and UE determine that the PUSCH preparation time is sufficient. The UE can send the PUSCH only if the PUSCH preparation time is sufficient, and can ignore the DCI that schedules the PUSCH if the PUSCH preparation time is insufficient.

[0377] [PUSCH: Regarding duplicate transmissions]

[0378] The following section describes in detail the retransmission of uplink data channels in 5G systems. 5G systems support two types of uplink data channel retransmission methods: PUSCH retransmission type A and PUSCH retransmission type B. One of PUSCH retransmission type A or PUSCH retransmission can be configured for the UE via upper-layer signaling.

[0379] PUSCH repeat type A send

[0380] As mentioned above, the symbol length and the position of the starting symbol of the uplink data channel can be determined by the time-domain resource allocation method in a time slot, and the base station can notify the UE of the number of repeated transmissions through upper-layer signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI).

[0381] Based on the number of retransmissions received from the base station, the UE can retransmit an uplink data channel with the same length and start symbol as the configured uplink data channel in consecutive time slots. If the base station configures the time slot as the UE's downlink, or if at least one symbol of the uplink data channel configured for the UE is configured as downlink, the UE omits uplink data channel transmission, but the number of retransmissions of the uplink data channel is still counted.

[0382] PUSCH repeat type B send

[0383] As mentioned above, the symbol length and the position of the starting symbol of the uplink data channel can be determined by the time-domain resource allocation method in a time slot, and the base station can notify the UE of the number of repetitions through upper-layer signaling (such as RRC signaling) or L1 signaling (such as DCI).

[0384] - The nominal repetition of the uplink data channel is determined based on the previously configured start symbol and uplink data channel length as follows. The time slot in which the nth nominal repetition begins is determined by... The symbols given, and those starting from this time slot, are... The time slot at the end of the nth nominal repetition is given. The symbol given, and which ends in that time slot, is... Given: n = 0, ..., numberofrepetitions-1, S refers to the start symbol of the configured uplink data channel, and L refers to the symbol length of the configured uplink data channel. The time slot at which PUSCH transmission begins and This refers to the number of symbols in each time slot.

[0385] - The UE determines invalid symbols transmitted by PUSCH repetition type B. Symbols configured for downlink by tdd-UL-DL-ConfigurationCommon or dd-UL-DL-ConfigurationDedicated are determined to be invalid symbols transmitted by PUSCH repetition type B. Furthermore, invalid symbols can be configured in higher-layer parameters (e.g., InvalidSymbolPattern). Higher-layer parameters (e.g., InvalidSymbolPattern) can provide a symbol-level bitmap on one or two time slots to configure invalid symbols. In the bitmap, 1 represents an invalid symbol. Furthermore, the periodicity and pattern of the bitmap can be configured through higher-layer parameters (e.g., InvalidSymbolPattern). If a higher-layer parameter (e.g., InvalidSymbolPattern) is configured, and if the parameter InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 indicates 1, the UE applies the invalid symbol pattern; if the aforementioned parameter indicates 0, the UE does not apply the invalid symbol pattern. If a higher-level parameter (e.g., InvalidSymbolPattern) is configured, and if the parameter InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 is not configured, the UE applies the invalid symbol mode.

[0386] After identifying invalid symbols, the UE can consider valid symbols for each nominal repeat, excluding invalid symbols. If each nominal repeat includes one or more valid symbols, then the nominal repeat may include one or more actual repeats. Each actual repeat consists of a set of consecutive valid symbols that can be used for PUSCH repeat type B transmission in a time slot.

[0387] Figure 14An example of PUSCH repetition type B transmission in a wireless communication system according to an embodiment of this disclosure is shown. The UE may receive the following configuration: the start symbol S of the uplink data channel is 0, the uplink data channel length L is 14, and the number of repetitions is 16. In this case, nominal repetitions may appear in 16 consecutive time slots (1401). Thereafter, the UE may determine that the symbols configured as downlink symbols in each nominal repetition 1401 are invalid symbols. The UE determines that the symbols configured as 1 in invalid symbol mode 1402 are invalid symbols. If valid symbols other than invalid symbols constitute one or more consecutive symbols in a time slot in each nominal repetition, they are configured and transmitted as actual repetitions (1403).

[0388] Regarding repeated PUSCH transmissions, NR version 16 allows defining additional methods for UL-authorized PUSCH transmissions across time slot boundaries and configured authorization-based PUSCH transmissions, as follows:

[0389] - Method 1 (Micro-slot-level repetition): Two or more PUSCH retransmissions are scheduled within a slot or at the boundary of consecutive slots using a single UL grant. In conjunction with Method 1, the time-domain resource allocation information within the DCI indicates the resources allocated to the first retransmission. Furthermore, the frequency-domain resource information for the remaining retransmissions can be determined based on the time-domain resource information of the first retransmission and the uplink or downlink direction determined for each symbol in each slot. Each retransmission occupies consecutive symbols.

[0390] - Method 2 (Multi-segment Transmission): Two or more PUSCH retransmissions are scheduled in consecutive time slots using a single UL grant. Transmission 1 is assigned to each time slot, and the start point or repetition length of each transmission can be different. In Method 2, the time-domain resource allocation information within the DCI indicates the start point and repetition length of all retransmissions. When performing retransmissions within a single time slot using Method 2, if there are multiple consecutive uplink symbol bundles in the corresponding time slot, corresponding retransmissions can be performed for each uplink symbol bundle. If there is only a single consecutive uplink symbol bundle in the corresponding time slot, a single PUSCH retransmission is performed according to the method of NR version 15.

[0391] Method 3: Schedule two or more PUSCH retransmissions in consecutive time slots using two or more UL grants. A transmission 1 can be specified for each time slot, and the nth UL grant can be received before the PUSCH transmission scheduled by the (n-1)th UL grant has finished.

[0392] Method 4: One or more PUSCH retransmissions within a single time slot, or two or more PUSCH retransmissions spanning consecutive time slot boundaries, can be supported through a UL authorization or a configured authorization. The number of retransmissions indicated by the base station to the UE is only a nominal value, and the UE may actually perform more PUSCH retransmissions than the nominal number. The time-domain resource allocation information or configured authorization within the DCI refers to the resources indicated by the base station for the first retransmission. The time-domain resource information for the remaining retransmissions can be determined by referring to the resource information of the first retransmission and the uplink or downlink direction of the symbol. If the time-domain resource information for the retransmissions indicated by the base station spans time slot boundaries or includes uplink / downlink switching points, the corresponding retransmission can be divided into multiple retransmissions. One retransmission can be included in a time slot for each uplink period.

[0393] The aforementioned repeated transmission can be applied to Dynamic Grant (DG) PUSCH and Configuration Grant (CG) PUSCH. DG PUSCH refers to a scheme where all scheduling information is provided by the DCI, while CG PUSCH refers to a scheme where PUSCH scheduling information is provided only through upper-layer signals or partially through the DCI. Furthermore, DG PUSCH corresponds to a scheme where the UE transmits PUSCH only within the scheduling area provided by the DCI, while CG PUSCH corresponds to a scheme where the UE periodically transmits PUSCH according to the period configured by the upper-layer signals without receiving DCI signals independently.

[0394] [PUSCH: Frequency Hopping Process]

[0395] The frequency hopping of the Physical Uplink Shared Channel (PUSCH) in 5G systems will be described in detail below.

[0396] 5G supports two PUSCH frequency hopping methods for each PUSCH repetition transmission type. First, in PUSCH repetition type A transmission, intra-slot frequency hopping and inter-slot frequency hopping are supported, and in PUSCH repetition type B transmission, inter-repetition frequency hopping and inter-slot frequency hopping are supported.

[0397] The intra-slot frequency hopping method supported in PUSCH repetition type A transmission may include a method in which the UE, after changing the allocated resources in the frequency domain by a configured frequency offset for two hops within a time slot, transmits the allocated resources in the frequency domain. The starting RB of each hop associated with intra-slot frequency hopping can be represented by Equation 4 below.

[0398] [Equation 4]

[0399]

[0400] In Equation 4, i=0 and i=1 can represent the first jump and the second jump, respectively, and RBstart It can represent the starting RB in the UL BWP and can be calculated according to the frequency resource allocation method. RB offset This represents the frequency offset between two hops through higher-level parameters. The number of symbols in the first hop can be determined by... This indicates that the number of symbols in the second hop can be determined by... express. It is the length of PUSCH transmission in a time slot, represented by the number of OFDM symbols.

[0401] Next, the inter-slot frequency hopping method supported in PUSCH repetition type A and type B transmissions is a method in which the UE transmits the allocated resources in the frequency domain after changing the allocated resources in the frequency domain with a configured frequency offset in each time slot. This applies to time slots related to inter-slot frequency hopping. The initial RB during the period can be represented by the following equation 5.

[0402] [Equation 5]

[0403]

[0404] In equation 5, This indicates the current slot number during a multi-slot PUSCH transmission, and RB start This represents the starting RB within the UL BWP, calculated according to the frequency resource allocation method. RB offset This represents the frequency offset between two hops through higher-level parameters.

[0405] Next, the inter-repetition frequency hopping method supported in PUSCH repetition type B transmission is a method in which resources allocated in the frequency domain for one or more actual repetitions in each nominal repetition are moved by a configured frequency offset and then transmitted. The index RB in the frequency domain for the starting RB in the nth nominal repetition or one or more actual repetitions. start(n) Equation 6 can be followed.

[0406] [Equation 6]

[0407]

[0408] In Equation 6, n represents the nominal repeating index, RB offset This represents the RB offset between two hops using higher-level parameters.

[0409] [PUSCH: Reuse Rules During AP / SP CSI Reporting]

[0410] The following section describes in detail a method for measuring and reporting channel states in a 5G communication system. Channel state information (CSI) may include channel quality indicators (CQI), precoding matrix indexes (PMI), CSI-RS resource indicators (CRI), SS / PBCH block resource indicators (SSBRI), layer indicators (LI), rank indicators (RI), reference signal received power (L1-RSRP), etc. The base station can control the time and frequency resources used for the aforementioned CSI measurements and reporting of the UE.

[0411] For the aforementioned CSI measurements and reports, the UE can configure the settings information for N (N≥1) CSI reports (CSI-ReportConfig), the settings information for M (M≥1) RS transmission resources (CSI-ResourceConfig), and the list information for one or two trigger states (CSI-AperiodicTriggerStateList, CSI-SemiPersistentOnPUSCH-TriggerStateList) via higher-layer signaling. More specifically, the configuration information for the aforementioned CSI measurements and reports can be described in Tables 32 to 38 below.

[0412] [Table 32] CSI-ReportConfig

[0413] IE CSI-ReportConfig is used to configure periodic or semi-persistent reports to be transmitted on the PUCCH on a cell that includes CSI-ReportConfig, or to configure semi-persistent or non-periodic reports to be transmitted on the PUSCH triggered by a DCI received on a cell that includes CSI-ReportConfig (in which case the cell on which the report is transmitted is determined by the received DCI). See section 5.2.1 of TS 38.214

[19] .

[0414] CSI-ReportConfig Information elements

[0415]

[0416]

[0417]

[0418]

[0419]

[0420]

[0421]

[0422]

[0423] [Table 33] CSI-ResourceConfig

[0424] IE CSI-ResourceConfig defines a set of one or more NZP-CSI-RS-ResourceSet, CSI-IM-ResourceSet, and / or CSI-SSB-ResourceSet.

[0425] CSI-ResourceConfig Information elements

[0426]

[0427]

[0428] [Table 34] NZP-CSI-RS-ResourceSet

[0429] The IE NZP-CSI-RS-ResourceSet is a set of non-zero power (NZP) CSI-RS resources (with their IDs) and sets specific parameters.

[0430] NZP-CSI-RS-ResourceSet Information elements

[0431]

[0432]

[0433] [Table 35] CSI-SSB-ResourceSet

[0434] The IE CSI-SSB-ResourceSet is used to configure an SS / PBCH block resource set, which refers to the SS / PBCH indicated in ServingCellConfigCommon.

[0435] CSI-SSB-ResourceSet Information elements

[0436]

[0437] [Table 36] CSI-IM-ResourceSet

[0438] The IE CSI-IM-ResourceSet is used to configure a group of one or more CSI interference management (IM) resources (with their IDs) and set specific parameters.

[0439] CSI-IM-ResourceSet Information elements

[0440]

[0441]

[0442] [Table 37] CSI-AperiodicTriggerStateList

[0443] The CSI-AperiodicTriggerStateList IE is used to configure the UE with a list of aperiodic trigger states. Each code point in the DCI field "CSI request" is associated with a trigger state. Upon receiving a value associated with a trigger state, the UE will perform CSI-RS (Reference Signal) measurements and aperiodic reporting on L1 based on all entries in the associatedReportConfigInfoList for that trigger state.

[0444] CSI-AperiodicTriggerStateList Information elements

[0445]

[0446]

[0447]

[0448] [Table 38] CSI-SemiPersistentOnPUSCH-TriggerStateList

[0449] The CSI-SemiPersistentOnPUSCH-TriggerStateList IE is used to configure the UE to have a list of trigger states for semi-persistent reporting of channel state information on L1. See also Section 5.2 of TS 38.214

[19] .

[0450] CSI-SemiPersistentOnPUSCH-TriggerStateList Information elements

[0451]

[0452] Regarding the aforementioned CSI report settings (CSI-ReportConfig), each CSI-ReportConfig can be associated with a downlink (DL) bandwidth portion, which is identified by the higher-layer parameter bandwidth portion identifier (bwp-id) given by the CSI resource setting (CSI-ResourceConfig) associated with the corresponding report setting. As the time-domain report for each CSI-ReportConfig, "aperiodic," "semi-persistent," and "periodic" schemes can be supported. The base station can configure these schemes for the UE through the reportConfigType parameter configured from higher layers. The semi-persistent CSI reporting method supports both "PUCCH-based semi-persistent (semi-PersistentOnPUCCH)" and "PUSCH-based semi-persistent (semi-PersistentOnPUSCH)" methods. In the case of periodic or semi-persistent CSI reporting methods, the base station can configure the PUCCH or PUSCH resources for the UE to transmit CSI via higher-layer signaling. The periodicity and slot offset of the PUCCH or PUSCH resources for transmitting CSI can be given by a set of parameters configuring the uplink (UL) bandwidth portion used for CSI reporting. In the case of non-periodic CSI reporting methods, the base station can schedule the PUSCH resources for the UE to transmit CSI via L1 signaling (DCI format 0_1 ​​above).

[0453] Regarding the aforementioned CSI resource configurations (CSI-ResourceConfig), each CSI resource configuration (CSI-ReportConfig) may include S (≥1) CSI resource sets (e.g., given by higher-layer parameters of csi-RS-ResourceSetList). The list of CSI resource sets may include non-zero power (NZP) CSI-RS resource sets and SS / PBCH block sets, or may include CSI interference measurement (CSI-IM) resource sets. Each CSI resource setting may reside in a downlink (DL) bandwidth portion identified by the higher-layer parameter bwp-id and may be connected to CSI reporting settings within the same downlink bandwidth portion. The time-domain operation of CSI-RS resources within a CSI resource setting can be configured as one of "aperiodic," "periodic," or "semi-persistent" from the higher-layer parameter resourceType. For periodic or semi-persistent CSI resource settings, the number of CSI-RS resource sets may be limited to S (S=1), and the configured periodicity and slot offset may be given based on the parameter set of the downlink bandwidth portion identified by bwp-id. The base station can configure one or more CSI resource configurations for the UE for channel or interference measurement via higher-layer signaling, and may include, for example, the following CSI resources.

[0454] - CSI-IM resources for interference measurement

[0455] - NZP CSI-RS resources for interference measurement

[0456] - NZP CSI-RS resources for channel measurements

[0457] For a CSI-RS resource set associated with resource settings where the higher-layer parameter of resourceType is configured as “aperiodic,” “periodic,” or “semi-persistent,” the triggering state of a CSI reporting setting with reportType configured as “aperiodic” can be configured via the higher-layer parameter of CSI-AperiodicTriggerStateList, as well as resource settings for performing channel or interference measurements on one or more component cells (CCs).

[0458] UE aperiodic CSI reporting can be performed using PUSCH, periodic CSI reporting can be performed using PUCCH, and semi-persistent CSI reporting can be performed using PUSCH when triggered or activated via DCI, and can be performed using PUCCH after activation via MAC control element (MAC CE). As mentioned above, CSI resource configuration can also be configured to be aperiodic, periodic, or semi-persistent. Based on Table 39 below, combinations of CSI reporting settings and CSI resource settings are supported.

[0459] [Table 39]

[0460] Table 5.2.1.4-1: CSI Reports for Triggering / Activating Possible CSI-RS Configurations.

[0461]

[0462] Aperiodic CSI reports can be triggered by the "CSI Request" field in DCI format 0_1, which corresponds to the PUSCH scheduling DCI. The UE can monitor the PDCCH, acquire DCI format 0_1, and obtain the PUSCH scheduling information and CSI request indicator. The CSI request indicator can be configured to have NTS (=0, 1, 2, 3, 4, 5, or 6) bits and can be determined via higher-layer signaling (reportTriggerSize). One of one or more aperiodic CSI report trigger states, which can be configured via higher-layer signaling (CSI-AperiodicTriggerStateList), can be triggered by the CSI request indicator.

[0463] - If all bits in the CSI request field are 0, this may indicate that no CSI report has been requested.

[0464] - If the number M of CSI trigger states configured in CSI-AperiodicTriggerStateLite is greater than 2NTs-1, then the M CSI trigger states can be mapped to 2NTs-1 trigger states according to the predefined mapping relationship, and one of the 2NTs-1 trigger states can be indicated through the CSI request field.

[0465] - If the number M of CSI trigger states configured in CSI-AperiodicTriggerStateLite is less than or equal to 2NTs-1, the CSI Request field can indicate one of the M CSI trigger states.

[0466] Table 40 below shows an example of the relationship between CSI request indicators and the CSI triggering states that can be indicated by the corresponding indicators.

[0467] [Table 40]

[0468]

[0469] The UE can measure the CSI resource in the CSI trigger state triggered via the CSI request field, and then generate a CSI (including at least one of, for example, CQI, PMI, CRI, SSBRI, LI, RI, or L1-RSRP) based on the measurement. The UE can transmit the acquired CSI using a PUSCH scheduled via the corresponding DCI format 0_1. If a bit corresponding to the uplink data indicator (UL-SCH indicator) in DCI format 0_1 ​​indicates "1", the UE can multiplex the uplink data (UL-SCH) and the acquired CSI on the PUSCH resource scheduled by DCI format 0_1 ​​to transmit them. If a bit corresponding to the uplink data indicator (UL-SCH indicator) in DCI format 0_1 ​​indicates "0", the UE can map the CSI to the PUSCH resource scheduled by DCI format 0_1 ​​only, without mapping the uplink data (UL-SCH), to transmit the CSI.

[0470] Figure 13 An example of a non-periodic CSI reporting method is shown.

[0471] exist Figure 13In Example 1300, the UE can acquire DCI format 0_1 ​​by monitoring PDCCH 1301, and can obtain scheduling information and CSI request information from PUSCH 1305. The UE can obtain resource information for the CSI-RS 1302 to be measured from the received CSI request indicator. The UE can determine the time point at which the UE needs to measure the CSI-RS 1302 resource based on the time point of receiving DCI format 0_1 ​​and the offset parameter (e.g., aperiodicTriggeringOffset mentioned above) in the CSI resource set configuration (e.g., NZP CSI-RS resource set configuration (NZP-CSI-RS-ResourceSet)). More specifically, the UE can configure the offset value X of the aperiodicTriggeringOffset parameter from the base station via higher-layer signaling in the NZP-CSI-RS resource set configuration, and the configured offset value X can refer to the offset between the time slot for receiving DCI triggering aperiodic CSI reports and the time slot for sending CSI-RS resources. For example, the aperiodicTriggeringOffset parameter value and the offset value X may have the mapping relationship shown in Table 41 below.

[0472] [Table 41]

[0473]

[0474] Figure 13 Example 1300 illustrates an example where the aforementioned offset value X is configured to be 0 (X=0). In this case, the UE can receive the DCI format 0_1 ​​slot (corresponding to) that triggers an aperiodic CSI report. Figure 13 The UE receives CSI-RS 1302 in time slot 0 (1306) and can report CSI information based on the received CSI-RS measurements to the base station via PUSCH 1305. The UE can obtain the scheduling information for CSI reporting on PUSCH 1305 (information corresponding to each field of DCI format 0_1) from DCI format 0_1. For example, in DCI format 0_1, the UE can obtain information about the time slot in which PUSCH 1305 will be transmitted from the time-domain resource allocation information of PUSCH 1305. Figure 13 In Example 1300, the UE obtains 3 as the K2 value corresponding to the slot offset value from PDCCH to PUSCH. Therefore, PUSCH 1305 can be transmitted in slot 3 1309, which is 3 slots away from slot 0 1306 (i.e., the time when PDCCH 1301 has been received).

[0475] exist Figure 13In Example 1310, the UE can obtain DCI format 0_1 ​​by monitoring PDCCH 1311, and can obtain scheduling information and CSI request information of PUSCH 1315 from it. The UE can obtain resource information of CSI-RS 1312 to be measured from the received CSI request indicator. Figure 13 Example 1310 illustrates an example where the offset value X of the aforementioned CSI-RS is configured to be 1 (X=1). In this case, the UE can receive the DCI format 0_1 ​​slot (corresponding to) that triggers the aperiodic CSI report. Figure 13 The CSI-RS 1312 is received in time slot 0 (1316) and can report CSI information based on the received CSI-RS measurement to the base station via PUSCH 1315.

[0476] Aperiodic CSI reports may include at least one or both of CSI Part 1 and CSI Part 2, and aperiodic CSI reports may be multiplexed on a transport block when transmitted via PUSCH. After inserting CRC into the input bits of the aperiodic CSI for multiplexing, encoding and rate matching can be performed, and transmission can then be performed by mapping to resource elements within the PUSCH in a specific pattern. Depending on the encoding method or the length of the input bits, CRC insertion may be omitted. The number of modulation symbols calculated for rate matching during the multiplexing of CSI Part 1 or CSI Part 2 included in the aperiodic CSI report can be calculated as shown in Table 42 below.

[0477] [Table 42]

[0478]

[0479]

[0480] Specifically, for PUSCH repetition types A and B, the UE can reuse the aperiodic CSI report only on the first repetition of the repetitive PUSCH transmission before transmission. This is because the aperiodic CSI report information to be reused is encoded in a polar coordinate code scheme. In this case, each PUSCH repetition needs to have the same frequency and time resource allocation so that the aperiodic CSI report information can be reused across multiple PUSCH repetitions. Particularly in the case of PUSCH repetition type B transmission, since each actual repetition may have a different OFDM symbol duration, the aperiodic CSI report can be reused only on the first repetition before transmission.

[0481] Furthermore, for PUSCH repetition type B transmission, when the UE receives a DCI for activating a semi-persistent CSI report or scheduling an aperiodic CSI report without scheduling a transport block, the UE can assume the nominal repetition value is 1 even if the number of PUSCH repetitions configured via higher-layer signaling is greater than 1. Additionally, if aperiodic or semi-persistent CSI reports are scheduled or activated without scheduling a transport block based on PUSCH repetition type B transmission, the UE can expect the first nominal repetition to be the same as the first actual repetition. Regarding PUSCH transmissions including semi-persistent CSI, in PUSCH transmission scheme B based on repetition, after activating a semi-persistent CSI report via DCI, no DCI scheduling is performed, and if the first nominal repetition is different from the first actual repetition, the transmission of the first nominal repetition can be ignored.

[0482] [Regarding UE Capability Report]

[0483] In LTE and NR, a UE can perform a procedure in which, when the UE connects to a serving base station, the UE can report the capabilities it supports to the corresponding base station. In the following description, the above procedure will be referred to as UE capability reporting.

[0484] A base station can send a UE capability query message to a UE in a connected state to request capability reports. This message can include UE capability requests for each Radio Access Technology (RAT) type of the base station. RAT type-specific requests can include information such as supported frequency band combinations. Furthermore, in the case of a UE capability query message, a request for UE capabilities for multiple RAT types can be made through a single RRC message container sent by the base station, or the base station can transmit a UE capability query message including multiple UE capability requests for various RAT types. That is, capability queries can be repeated multiple times in a single message, and the UE can configure corresponding UE capability information messages and report them multiple times. In next-generation mobile communication systems, UE capability requests for multi-RAT dual connectivity (MR-DC), such as NR, LTE, and E-UTRA-NR dual connectivity (EN-DC), can be made. UE capability query messages are typically sent initially after the UE connects to the base station, but can be requested under any conditions if the base station requires it.

[0485] In the above steps, after receiving the UE capability report request from the base station, the UE configures its capabilities based on the frequency band information and RAT type requested by the base station. The method for configuring UE capabilities in the NR system is summarized below.

[0486] 1. If the UE receives a list of LTE and / or NR frequency bands from the base station upon a UE capability request, the UE constructs a band combination (BC) for EN-DC and NR Independent (SA). That is, the UE configures a BC candidate list for EN-DC and NR SA based on the frequency bands received from the base station upon request via FreqBandList. Furthermore, the frequency bands are prioritized according to the order described in the FreqBandList.

[0487] 2. If the base station sets the “eutra-nr-only” flag or the “eutra” flag and requests a UE capability report, the UE will remove all content related to NR SA BC from the configured BC candidate list. This operation only occurs when the LTE base station (eNB) requests “eutra” capability.

[0488] 3. Then, the UE removes the fallback BC from the BC candidate list configured in the above steps. As used herein, a fallback BC refers to a BC that can be obtained by removing the frequency band corresponding to at least one SCell from a specific BC, and since the BC prior to removing the frequency band corresponding to at least one SCell has already covered the fallback BC, this BC can be omitted. This step also applies to MR-DC, i.e., LTE frequency bands also apply. The BCs remaining after the above steps constitute the final "candidate BC list".

[0489] 4. The UE can select a BC suitable for the requested RAT type from the final "Candidate BC List" and choose the BC to report. In this step, the UE configures the supportedBandCombinationList in a predetermined order. That is, the UE configures the BC and the UE capabilities to be reported according to the pre-configured rat-Type order (NR -> EUTRA-NR -> EUTRA). Furthermore, the UE configures featureSetCombination for the configured supportedBandCombinationList and configures a "Candidate Feature Set Combination" list from the candidate BC list, removing entries related to fallback BCs (including capabilities of the same or lower level). The "Candidate Feature Set Combination" can include all feature set combinations related to NR and EUTRA-NR BCs and can be obtained from the feature set combinations of the containers of UE-NR-Capabilities and UE-MRDC-Capabilities.

[0490] 5. If the requested RAT type is eutra-nr and has effects, featureSetCombinations are included on both the UE-MRDC-Capabilities and UE-NR-Capabilities containers. However, the NR feature set is only included in UE-NR-Capabilities.

[0491] After configuring UE capabilities, the UE transmits a UE capability information message, including the UE capabilities, to the base station. The base station then performs appropriate scheduling and transmit / receive management based on the UE capabilities received from the UE.

[0492] [About CA / DC]

[0493] Figure 15 The radio protocol structures of the base station and UE in single-cell, carrier aggregation, and dual connectivity scenarios according to embodiments of this disclosure are shown.

[0494] refer to Figure 15 The radio protocols of the next-generation mobile communication system include NR Service Data Adaptation Protocol (SDAP) S25 or S70 on each side of the UE and NR base station, NR Packet Data Convergence Protocol (PDCP) S30 or S65, NR Radio Link Control (RLC) S35 or S60, and NR Media Access Control (MAC) S40 or S55.

[0495] The main functions of NR SDAP S25 or S70 may include some of the following functions.

[0496] -Transmission of user plane data

[0497] - Mapping between QoS flows and DRB for both UL and DL

[0498] - Mark QoS flow IDs in both DL and UL packets.

[0499] - Reflection QoS flow to DRB mapping for UL SDAP PDU

[0500] Regarding SDAP layer devices, the UE can configure via RRC messages whether to use the SDAP layer device header, or whether to use the SDAP layer device functionality for each PDCP layer device, each bearer, or each logical channel. If the SDAP header is configured, it can indicate the Non-Access Stratum (NAS) QoS reflection configuration 1-bit indicator (NAS reflected QoS) and the AS QoS reflection configuration 1-bit indicator (AS reflected QoS) in the SDAP header, allowing the UE to update or reconfigure the mapping information for uplink and downlink QoS flows and data bearers. The SDAP header can include QoS flow ID information indicating QoS. QoS information can be used for data processing priority, scheduling information, etc., to support the required services.

[0501] The main functions of NR PDCP S30 or S65 may include some of the following functions.

[0502] -Header compression and decompression: ROHC only

[0503] -Transmission of user data

[0504] - Sequential transmission of upper-layer PDUs

[0505] -Disordered transmission of upper-layer PDUs

[0506] -PDCP PDU reordering for reception

[0507] -Duplicate detection of lower-level SDUs

[0508] -PDCP SDU retransmission

[0509] - Encryption and decryption

[0510] - Timer-based SDU dropping in the uplink

[0511] In the aforementioned functions, the reordering of the NR PDCP device refers to the function of reordering PDCP PDUs received from the lower layer in sequence based on the PDCP sequence number (SN), and may include the function of transmitting data in the reordered sequence to the upper layer. Alternatively, the reordering of the NR PDCP device may include the function of direct transmission without considering the sequence, the function of reordering the sequence and recording lost PDCP PDUs, the function of reporting the status of lost PDCP PDUs to the transmitting side, and the function of requesting retransmission of lost PDCP PDUs.

[0512] The main functions of NR RLC S35 or S60 may include some of the following functions.

[0513] -Transmission of upper-layer PDUs

[0514] - Sequential transmission of upper-layer PDUs

[0515] -Disordered transmission of upper-layer PDUs

[0516] - Error correction via ARQ

[0517] Cascading, splitting, and reassembling of RLC SDUs

[0518] -Re-segmentation of RLC data PDUs

[0519] - Reordering of RLC data PDUs

[0520] -Duplicate detection

[0521] -Protocol error detection

[0522] -RLC SDU discard

[0523] -RLC Reconstruction

[0524] In the aforementioned functions, the sequential transmission of an NR RLC device refers to the function of transmitting RLC SDUs received from a lower layer to an upper layer in sequence. The sequential transmission of an NR RLC device may include the function of reassembling and transmitting multiple RLC SDUs that have been fragmented and received from a single RLC SDU; the function of reordering received RLCPDUs based on the RLC sequence number (SN) or PDCP sequence number (SN); the function of recording lost RLC PDUs by reordering the sequence; the function of reporting the status of lost RLC PDUs to the transmitting side; and the function of requesting retransmission of lost RLC PDUs. The sequential transmission of an NR RLC device may include the following functions: if a lost RLC SDU exists, transmitting RLC SDUs sequentially to the upper layer only before the lost RLC SDU; or it may include the function of transmitting all RLC SDUs received before the timer started sequentially to the upper layer if a predetermined timer has expired, despite the existence of lost RLCPDUs. Alternatively, the sequential transmission of an NR RLC device may include the function of sequentially transmitting all RLC SDUs received to date to the upper layer in the event of a predetermined timer expiration, despite the existence of lost RLC SDUs. Furthermore, RLC PDUs can be processed in the order they are received (according to arrival order, regardless of sequence number order) and then transmitted out of order (out-of-order delivery) to the PDCP device. In the case of fragmentation, fragments stored in a buffer or fragments to be received later can be received, reconstructed into a complete RLC PDU, processed, and transmitted to the PDCP device. The NR RLC layer may not include concatenation functionality; concatenation functionality can be implemented in the NR MAC layer or replaced by multiplexing functionality in the NR MAC layer.

[0525] In the above functions, the out-of-order transmission of NR RLC devices refers to the function of directly transmitting RLC SDUs received from the lower layer to the upper layer regardless of the order. It may also include the function of reassembling and transmitting RLC SDUs that have been divided into multiple RLC SDUs from one RLC SDU, and may include the function of storing the RLC SN or PDCP SN of the received RLC PDUs, sorting the sequence, and recording lost RLC PDUs.

[0526] The NR MAC S40 or S55 can connect to multiple NR RLC layer devices configured in a single UE, and the main functions of the NR MAC can include the following.

[0527] Mapping between logical channels and transport channels

[0528] - MAC SDU multiplexing / demultiplexing

[0529] - Scheduling Information Report

[0530] - Error correction via HARQ

[0531] Priority processing between logical channels of a UE

[0532] - Prioritization among UEs is performed through dynamic scheduling.

[0533] -MBMS service identifier

[0534] -Transmission format selection

[0535] -filling

[0536] The NR PHY layer S45 or S50 can perform channel coding and modulation of upper-layer data to obtain OFDM symbols and transmit them via radio channels, or demodulate OFDM symbols received via radio channels, channel code them, and transmit them to higher layers.

[0537] The detailed structure of a radio protocol can vary depending on the carrier (or cell) operation scheme. For example, when a base station transmits data to a UE based on a single carrier (or cell), the base station and UE can use a protocol structure with a single structure for each layer, such as S00. On the other hand, when a base station transmits data to a UE based on carrier aggregation (CA) using multiple carriers in a single TRP, the base station and UE can use a protocol structure with a single structure up to RLC, but multiplexing the PHY layer through the MAC layer, such as S10. As another example, when a base station transmits data to a UE based on dual connectivity (DC) using multiple carriers in multiple TRPs, the base station and UE can use a protocol structure with a single structure up to RLC, but multiplexing the PHY layer through the MAC layer, such as S20.

[0538] Referring to the above description related to PDCCH and beam configuration, since the current Rel-15 and Rel-16 NR do not support PDCCH retransmission, it is difficult to achieve the required reliability in scenarios requiring high reliability (such as URLLC). This disclosure can improve the PDCCH reception reliability of the UE by providing a method of PDCCH retransmission through multiple transmission points (TRPs). Specific methods will be described in detail in the following embodiments.

[0539] In the following, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The details of the present disclosure apply to FDD and TDD systems. As used below, higher-layer signaling (or higher-layer signaling) is a method of transmitting signals from a base station to a UE using a downlink data channel of the physical layer, or from a UE to a base station using an uplink data channel of the physical layer, and may also be referred to as “RRC signaling,” “PDCP signaling,” or “Media Access Control (MAC) control element (MACCE).”

[0540] As described below, the UE can use various methods to determine whether to apply cooperative communication. These methods include assigning a PDSCH(s) to which cooperative communication is applied, having a specific format, including specific indicators indicating whether cooperative communication is applied, scrambling the PDSCH(s) to which cooperative communication is applied with a specific RNTI, or assuming that cooperative communication is applied to a specific part of a higher-layer indication. For ease of description, the reception of a PDSCH to which cooperative communication is applied will be referred to as the NC-JT case, based on conditions similar to those described above.

[0541] As used below, determining the priority between A and B can refer to various operations, such as selecting the one with higher priority according to a predetermined priority rule and executing the operation corresponding to the selected operation, omitting or deleting the operation corresponding to the operation with lower priority, etc.

[0542] The above examples can be described below through several embodiments, but they are not independent of each other and one or more embodiments can be applied simultaneously or in combination.

[0543] [About NC-JT]

[0544] According to embodiments of this disclosure, noncoherent joint transmission (NC-JT) can be used by the UE to receive PDSCH from multiple TRPs.

[0545] Unlike conventional systems, 5G wireless communication systems can support all services with very short transmission latency, services requiring high connection density, and services requiring high transmission rates. In wireless communication networks comprising multiple cells, transmit and receive points (TRPs) or beams, cooperative communication (coordinated transmission) between cells, TRPs, and / or beams can meet various service requirements by enhancing the strength of the signal received by the UE or effectively performing interference control between cells, TRPs, and / or beams.

[0546] Joint Transmission (JT) is a representative transmission scheme for the aforementioned cooperative communication, and it is a scheme to increase the strength or throughput of the signal received by the UE by transmitting signals to a UE via multiple different cells, TRPs, and / or beams. In this case, the channels between the UE and each cell, TRP, and / or beam may have significantly different characteristics. In particular, Non-coherent Joint Transmission (NC-JT) supporting non-interference coding between cells, TRPs, and / or beams may require separate precoding, MCS, resource allocation, TCI indication, etc., according to the channel characteristics of each link between the UE and each cell, TRP, and / or beam.

[0547] The aforementioned NC-JT transmission can be applied to at least one of the following channels: downlink data channel (Physical Downlink Shared Channel (PDSCH)), downlink control channel (Physical Downlink Control Channel (PDCCH)), uplink data channel (Physical Uplink Shared Channel (PUSCH)), and uplink control channel (Physical Uplink Control Channel (PUCCH)). During PDSCH transmission, transmission information such as precoding, MCS, resource allocation, and TCI is indicated via DL DCI, and for NC-JT transmission, the transmission information should be indicated independently for each cell, TRP, and / or beam. This becomes a major factor increasing the payload required for DL ​​DCI transmission, which may adversely affect the reception performance of the PDCCH transmitting DCI. Therefore, to support JT with PDSCH, it is necessary to carefully design the trade-off between DCI information volume and control information reception performance.

[0548] Figure 16 An example of antenna port configuration and resource allocation for transmitting PDSCH using cooperative communication in a wireless communication system, according to an embodiment of this disclosure, is shown.

[0549] refer to Figure 16 An example of PDSCH transmission is described for each Joint Transmission (JT) scheme, and an example of radio resource allocation for each TRP is shown.

[0550] refer to Figure 16 Example N000 shows coherent joint transmission (C-JT) that supports phase interference coding between individual cells, TRPs, and / or beams.

[0551] In the C-JT scenario, TRP A N005 and TRP B N010 send a single data transmission (PDSCH) to UE N015, and multiple TRPs can perform joint precoding. This may mean that TRP A N005 and TRP B N010 transmit DMRS through the same DMRS port to send the same PDSCH. For example, TRP A N005 and TRP B N010 could transmit DMRS to the UE through DMRS port A and DMRS port B, respectively. In this case, the UE can receive a DCI for receiving a PDSCH based on the DMRS demodulated via DMRS port A and DMRS port B.

[0552] Figure 16 Example N020 is shown, which supports non-coherent joint transmission (NC-JT) with non-interference coding between individual cells, TRPs, and / or beams for PDSCH transmission.

[0553] In the NC-JT case, PDSCH is transmitted to UE N035 on a per-cell, per-TRP, and / or per-beam basis, and individual precoding can be applied to each PDSCH. Individual cells, TRPs, and / or beams can transmit different PDSCHs or different PDSCH layers to the UE, thereby improving throughput compared to single-cell, TRP, and / or beam transmission. Furthermore, individual cells, TRPs, and / or beams can repeatedly transmit the same PDSCH to the UE, thereby improving reliability compared to single-cell, TRP, and / or beam transmission. For ease of description, cells, TRPs, and / or beams are often referred to as TRPs.

[0554] In this case, various radio resource allocations can be considered, such as case N040 in which the frequency and time resources used in multiple TRPs for PDSCH transmission are the same, case N045 in which the time and frequency resources used in multiple TRPs do not overlap at all, and case N050 in which some time and frequency resources used in multiple TRPs overlap.

[0555] To support NC-JT, various types, structures, and relationships of DCIs can be considered to simultaneously assign multiple PDSCHs to a single UE.

[0556] Figure 17 An example of downlink control information (DCI) configuration for NC-JT according to an embodiment of the present disclosure is shown, wherein in a wireless communication system, each TRP sends different PDSCH or different PDSCH layers to the UE.

[0557] refer to Figure 17 Case #1 N100 is an example where, in addition to the serving TRP (TRP #0) used during a single PDSCH transmission, N-1 different PDSCHs are transmitted from N-1 additional TRPs (from TRP #1 to TRP #N-1). The control information for the PDSCHs transmitted in the additional N-1 TRPs is transmitted independently of the control information for the PDSCHs transmitted in the serving TRP. That is, the UE can obtain the control information for PDSCHs transmitted from different TRPs (TRP #0 to TRP #N-1) via each independent DCI (DCI #0 to DCI #(N-1)). The formats of the independent DCIs can be the same or different from each other, and the payloads of the DCIs can also be the same or different. In Case #1 above, the freedom of control or allocation for each PDSCH can be fully guaranteed. However, if the DCIs are transmitted from different TRPs, coverage differences may occur for each DCI, potentially degrading reception performance.

[0558] Case #2 N105 is an example in which (N-1) different PDSCHs are sent from (N-1) additional TRPs (from TRP #1 to TRP #(N-1)) other than the serving TRP (TRP #0) used for sending a single PDSCH, and multiple control messages (DCIs) of the PDSCHs of the (N-1) additional TRPs are sent, and each DCI depends on the control message of the PDSCH sent from the serving TRP.

[0559] For example, DCI#0, which is the control information for PDSCH sent from the serving TRP (TRP#0), includes all the information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2. However, the shortened DCI (hereinafter referred to as sDCI) (sDCI#0 to sDCI#N-2), which is the control message for PDSCH sent from the cooperating TRPs (TRP#1 to TRP#(N-1)), may only include some of the information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2. Therefore, when the sDCI used to send control information for PDSCH is sent from the cooperating TRP, the payload is smaller than that of the normal DCI (nDCI) used to send control information related to PDSCH sent from the serving TRP. Therefore, compared with nDCI, reserved bits may be included.

[0560] In scenario #2 above, the control or allocation degrees of freedom for each PDSCH can be restricted based on the content of the information elements included in the sDCI. However, since the reception performance of the sDCI is better than that of the nDCI, the probability of coverage differences occurring in each DCI can be reduced.

[0561] Case #3 N110 is an example in which (N-1) different PDSCHs are sent from (N-1) additional TRPs (from TRP #1 to TRP #(N-1)) other than the serving TRP (TRP #0) used for sending a single PDSCH, and the DCI depends on the control information of the PDSCH sent from the serving TRP.

[0562] For example, DCI#0, which is the control information for PDSCH transmitted from the serving TRP (TRP#0), includes all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2. However, for the control information for PDSCH transmitted from the cooperating TRPs (TRP#1 to TRP#N-1), only some information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2 may be collected in a single "auxiliary" DCI (sDCI) for transmission. For example, the sDCI may include at least one HARQ-related piece of information, such as the frequency domain resource allocation, time domain resource allocation, and MCS of the cooperating TRP. Furthermore, information not included in the sDCI, such as the bandwidth portion (BWP) indicator or carrier indicator, may follow the serving TRP's DCI (DCI#0, normal DCI, or nDCI).

[0563] In Case #3 N110, the degree of freedom for PDSCH control or allocation can be limited based on the content of the information elements included in the sDCI, but the reception performance of the sDCI can be controlled, and Case #3 N110 can have a smaller UE DCI blind decoding complexity compared to Case #1 N100 or Case #2 N105.

[0564] Case #4 N115 illustrates an example where, in addition to the serving TRP (TRP #0) used during a single PDSCH transmission, N-1 different PDSCHs are transmitted from N-1 additional TRPs (TRP #1 to TRP #(N-1)). The control information for the PDSCHs transmitted from the N-1 additional TRPs is transmitted in the same DCI (long DCI) as the control information for the PDSCHs transmitted from the serving TRP. That is, the UE can obtain the control information for PDSCHs transmitted from different TRPs (TRP #0 to TRP #(N-1)) via a single DCI. In Case #4 N115, the complexity of blind DCI decoding for the UE may not increase, but the freedom of PDSCH control or allocation may be lower, thus limiting the number of cooperating TRPs based on the long DCI payload constraints.

[0565] In the following description and embodiments, sDCI may refer to various multiple supplementary DCIs, such as shortened DCIs, auxiliary DCIs, or normal DCIs that include PDSCH control information sent in the cooperative TRP (DCI formats 1_0 and 1_1 above), and unless specific constraints are mentioned, the corresponding descriptions may be similarly applied to various multiple supplementary DCIs.

[0566] In the following description and embodiments, cases #1 N100, #2 N105, and #3 N110, where one or more DCIs are used for NC-JT support, can be classified as multi-PDCCH-based NC-JT, while case #4 N115, where a single DCI (PDCCH) is used for NC-JT support, can be classified as single-PDCCH-based NC-JT. In multi-PDCCH-based PDSCH transmission, a CORESET can be distinguished between a DCI that schedules a serving TRP (TRP #0) and a CORESET that schedules a cooperating TRP (TRP #1 to TRP #(N-1)). One method for distinguishing CORESETs may include a method of distinguishing by the higher-layer indicator of each CORESET and a method of distinguishing by the beam configuration of each CORESET. Furthermore, in single-PDCCH-based NC-JT, a single DCI is used to schedule a single PDSCH with multiple layers, instead of scheduling multiple PDSCHs, and the multiple layers can be transmitted from multiple TRPs. In this case, the connection relationship between the layer and the TRP used to send the layer can be indicated by the Transmission Configuration Indicator (TCI) of that layer.

[0567] In embodiments of this disclosure, when applied in practice, “Cooperative TRP” can be replaced by various terms, such as “cooperative panel” or “cooperative beam”.

[0568] In the embodiments of this disclosure, depending on the circumstances, "the case of applying NC-JT" can be interpreted differently as "the case where the UE simultaneously receives one or more PDSCHs in a BWP", "the case where the UE simultaneously receives PDSCHs based on two or more Transmission Configuration Indicators (TCIs) in a BWP", and "the case where the PDSCHs received by the UE are associated with one or more DMRS port groups", but for ease of description, it is represented by one expression.

[0569] As used in this article, the NC-JT radio protocol architecture can be used in various ways depending on the TRP deployment scenario. For example, if there is little or no backhaul latency between cooperating TRPs, it can be used in conjunction with... Figure 15 The “S10” approach uses a MAC layer multiplexing-based architecture (CA-like method). Conversely, if the backhaul latency between cooperative TRPs is too large to be ignored (e.g., when exchanging CSI, scheduling, and HARQ-ACK information between cooperative TRPs takes 2ms or more), a similar approach can be adopted. Figure 15 Similar to the “S20” approach, this method (a DC-like approach) ensures latency robustness by using independent structures for each TRP, starting from the RLC layer.

[0570] UEs supporting C-JT / NC-JT can receive C-JT / NC-JT related parameters and settings from higher-level configurations and set their RRC parameters accordingly. For higher-level configurations, the UE can use UE capability parameters (e.g., tci-StatePDSCH). UE capability parameters (e.g., tci-StatePDSCH) can define the TCI states used for PDSCH transmission. The number of TCI states can be configured as 4, 8, 16, 32, 64, and 128 in FR1, and as 64 and 128 in FR2. Within the configured number, up to eight states can be indicated by configuring three bits of the TCI field in the DCI via the MAC CE message. The maximum value of 128 can refer to the value indicated by maxNumberConfiguredTCIstatesPerCC in the tci-StatePDSCH parameters included in the UE's capability signaling. In this way, a series of configuration procedures from higher-level configuration to MAC CE configuration can be applied to beamforming change commands or beamforming indications for at least one PDSCH in a TRP.

[0571] [Multi-DCI-based Multi-TRP]

[0572] According to embodiments of the present invention, downlink control channels for NC-JT transmission can be configured based on multiple PDCCHs.

[0573] In a multi-PDCCH-based NC-JT, when sending the DCI for PDSCH scheduling for each TRP, a CORESET or search space distinct for each TRP can be provided. The CORESET or search space for each TRP can be configured according to at least one of the following configuration options.

[0574] High-level index configuration for each CORESET: The CORESET configuration information configured through high-level settings can include index values, and the TRPs used for PDCCH transmission within a corresponding CORESET can be distinguished by the configured index value of each CORESET. That is, in a group of CORESETs with the same high-level index value, it can be assumed that the same TRP is sending PDCCH, or sending PDCCH for scheduling the same TRP. The aforementioned index for each CORESET can be named CORESETPoolIndex, and for CORESETs configured with the same CORESETPoolIndex value, it can be assumed or determined that the PDCCH is sent from the same TRP. In the case of CORESETs, for CORESETs that have not yet configured a CORESETPoolIndex value, it can be assumed that a default value has been configured for CORESETPoolIndex, and the default value can be 0.

[0575] Multiple-PDCCH-Config configuration: Multiple values ​​for a PDCCH-Config can be configured in a single BWP, and each PDCCH-Config can include the PDCCH configuration for each TRP. That is, a list of CORESETs and / or a list of search spaces for each TRP can be configured in a single PDCCH-Config, and one or more CORESETs and one or more search spaces included in a single PDCCH-Config can be considered to correspond to a specific TRP.

[0576] CORESET beam / beam group configuration: The TRP corresponding to a given CORESET can be distinguished by the beam or beam group configured for each CORESET. For example, if the same TCI state is configured for multiple CORESETs, it can be assumed that these CORESETs are transmitted through the same TRP, or that the PDCCH used to schedule the PDSCH of the same TRP is transmitted in the corresponding CORESET.

[0577] Search Space Beam / Beamgroup Configuration: Beams or beamgroups can be configured for each search space, and the TRP for each search space can be distinguished based on the configured beams or beamgroups. For example, if the same beam / beamgroup or TCI state is configured in multiple search spaces, it can be assumed that the same TRP sends PDCCH in the corresponding search space, or sends PDCCH for scheduling the same TRP in the corresponding search space.

[0578] As described above, by separating the CORESET or search space of each TRP, PDSCH and HARQ-ACK can be partitioned for each TRP, and an independent HARQ-ACK codebook can be generated for each TRP accordingly, using independent PUCCH resources.

[0579] For each cell or each BWP, the configuration can be independent. For example, while two different CORESETPoolIndex values ​​can be configured for a PCell, a specific CORESETPoolIndex value cannot be configured for a particular SCell. In this case, NC-JT can be configured in the PCell, but it might not be configured in the SCell where no CORESETPoolIndex value is configured.

[0580] [Multi-TRP based on a single DCI]

[0581] According to another embodiment of this disclosure, the downlink beam for NC-JT transmission can be configured based on a single PDCCH.

[0582] In a single PDCCH-based NC-JT, a single DCI can be used to schedule PDSCH transmissions from multiple TRPs. In this case, the number of TCI states can be used as a method to indicate the number of TRPs transmitting the corresponding PDSCH. That is, if the number of TCI states indicated in the DCI used to schedule the PDSCH is two, single PDCCH-based NC-JT transmission can be considered, and if the number of TCI states is one, single TRP transmission can be considered. The TCI states indicated in the DCI can correspond to one or two TCI states activated by the MAC-CE. If the TCI states in the DCI correspond to two TCI states activated by the MAC-CE, then the TCI code point indicated by the DCI is associated with the TCI states activated by the MAC-CE, and this can correspond to the case where the number of TCI states activated by the MAC-CE corresponding to the TCI code point is two.

[0583] For each cell or each BWP, the configuration can be independent. For example, in a PCell, the maximum number of active TCI states corresponding to a TCI code point is 2, but in a specific SCell, the maximum number of active TCI states corresponding to a TCI code point can be 1. In this case, it can be assumed that NC-JT is configured in the PCell, but not in the SCell.

[0584] [PHR]

[0585] Figure 18 This illustrates the process by which a base station controls the transmit power of a UE in a cellular system. Figure 18 In operations 18-10, the UE within the base station's coverage area can perform downlink synchronization with the base station and obtain system information. According to some embodiments, downlink synchronization can be performed using synchronization signals from the primary synchronization signal / secondary synchronization signal (PSS / SSS) received from the base station. The UE that has already performed downlink synchronization can receive the main information block (MIB) and system information block (SIB) from the base station and obtain system information. In operations 18-15, via a random access procedure, the UE can perform uplink synchronization with the base station and establish a radio resource control (RRC) connection. During the random access procedure, the UE can send a random access preamble and message 3 (msg3) to the base station via the uplink. In this case, uplink transmit power control can be performed when sending the random access preamble and message 3. Specifically, the UE can receive parameters for uplink transmit power control from the base station via the acquired system information (e.g., SIB), or it can perform uplink transmit power control using predetermined parameters. In another embodiment of this disclosure, the UE can measure the reference signal received power (RSRP) from the path fading estimation signal transmitted by the base station, and can estimate the downlink path fading value as given in Equation 7. Furthermore, based on the estimated path fading value, the UE can configure the uplink transmit power value for transmitting the random access preamble and message 3.

[0586] [Equation 7]

[0587] Downlink path attenuation = Base station signal transmit power - UE-measured RSRP

[0588] In Equation 7, the transmit power of the base station signal refers to the transmit power of the downlink path fading estimation signal transmitted by the base station. The downlink path fading estimation signal transmitted by the base station can be a cell-specific reference signal (CRS) or a synchronization signal block (SSB). If the path fading estimation signal is a cell-specific reference signal (CRS), the transmit power of the base station signal can indicate the transmit power of the CRS and can be sent to the UE via the referenceSignalPower parameter in the system information. If the path fading estimation signal is a synchronization signal block (SSB), the transmit power of the base station signal can indicate the transmit power of the secondary synchronization signal (SSS) and demodulation reference signal (DMRS) transmitted via the PBCH and can be sent to the UE via the ss-PBCH-BlockPower parameter in the system information. In Operations 18-20, the UE can receive RRC parameters for uplink transmit power control from the base station via UE-specific RRC or common RRC. In this case, the received transmit power control parameters may differ from each other depending on the uplink channel type and signal type. That is, the transmit power control parameters applied to the Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), and Sounding Reference Signal (SRS) can be different from each other. Furthermore, as mentioned above, the transmit power control parameters received by the UE from the base station via the SIB before the RRC connection is established, or the transmit power management parameters used as predetermined values ​​by the UE before the RRC connection is established, can be included in the RRC parameters transmitted from the base station after the RRC connection is established. The UE can use the RRC parameter values ​​received from the base station after the RRC connection is established to control the uplink transmit power. In operations 18-25, the UE can receive a path fading estimation signal from the base station. More specifically, after the UE's RRC connection is established, the base station can configure the Channel State Information Reference Signal (CSI-RS) as the UE's path fading estimation signal. In this case, the base station can send information about the transmit power of the CSI-RS to the UE via the powerControlOffsetSS parameter of the UE-specific RRC information. Here, powerControlOffsetSS can indicate the transmit power difference (offset) between the SSB and the CSI-RS. In operations 18-30, the UE can estimate the downlink path attenuation value and configure the uplink transmit power value. More specifically, the UE can measure the downlink RSRP using CSI-RS and estimate the downlink path attenuation value via Equation 7 using information received from the base station regarding the transmit power of CSI-RS. Furthermore, based on the estimated downlink path attenuation value, the UE can configure the uplink transmit power values ​​for PUCCH, PUSCH, and SRS transmission. In operations 18-35, the UE can perform a Power Headroom Report (PHR) to the base station.Power headroom indicates the difference between a UE's current transmit power and its maximum output power. In operations 18-40, the base station can optimize system operation based on the reported power headroom. For example, if a particular UE reports a positive power headroom value to the base station, the base station can allocate more resource blocks (RBs) to the UE, thereby improving system gains. In operations 18-45, the UE can receive a transmit power control command (TPC) from the base station. For example, if a particular UE reports a negative power headroom value to the base station, the base station can allocate fewer resources to the UE or reduce the UE's transmit power via the TPC. This can increase system throughput or reduce unnecessary power consumption by the UE. In operations 18-50, the UE can update its transmit power based on the TPC command. In this case, the TPC command can be sent to the UE via a UE-specific DCI or a group common DCI. Therefore, the base station can dynamically control the UE's transmit power via the TPC command. In operations 18-55, the UE can perform uplink transmission based on the updated transmit power.

[0589] [PUSCH Power Control]

[0590] The PUSCH transmit power can be determined using Equation 8 below.

[0591] [Equation 8]

[0592]

[0593] In equation 8, This indicates that at the PUSCH transmission time i, the carrier f for the serving cell c is the maximum transmission power configured for the UE. This represents the reference transmit power configuration value for the active uplink bandwidth portion (BWP) b of the carrier f of the serving cell c, and has different values ​​depending on the various transmit types j. The PUSCH can be sent according to the case of message 3 for random access, or the case of PUSCH being a configured authorized PUSCH, or the PUSCH having various values ​​according to the schedule. This indicates the magnitude of the frequency allocated to PUSCH. This represents the compensation ratio for the path loss of the UL BWP b of the carrier f of serving cell c, and can be configured by the higher-layer signal and can have different values ​​depending on j. The downlink path loss estimate of the UL BWP b of carrier f of serving cell c is represented by a value measured using a reference signal in the activated downlink bandwidth portion. The reference signal can be an SS / PBCH block or CSI-RS. The downlink path loss can be calculated as described above in Equation 7. In another embodiment of this disclosure, This represents the downlink path attenuation value and corresponds to the path attenuation calculated by the UE, as shown in Equation 7. Based on the higher-layer signal configuration, the UE calculates the path attenuation based on reference signal resources associated with the SS / PBCH block or CSI-RS. As reference signal resources, one set of multiple sets of reference signal resources can be selected based on higher-layer signals or L1 signals, and the UE calculates the path loss based on these reference signal resources. It is a value determined by the modulation and coding scheme (MCS) value of the PUSCH at the PUSCH transmission time i of the UL BWP b of the carrier f of the serving cell c. This indicates the adaptive value for power control, and the power value can be dynamically controlled via the TPC command.

[0594] TPC commands are categorized into cumulative mode and absolute mode, one of which is determined by higher-level signals. Cumulative mode accumulates the currently determined power control adaptive value to the value indicated by the TPC command, and the power control adaptive value can be increased or decreased according to the TPC command, with the following relationship: . This is the value indicated by the TPC command. Absolute mode has a value determined by the TPC command, independent of the currently determined power control adaptive value, and has the following relationship: Table 43 below shows the values ​​that the TPC command can indicate.

[0595] [Table 43] TPC Commands

[0596]

[0597] [PUCCH Power Control]

[0598] Equation 9 below is used to determine the PUCCH transmit power.

[0599] [Equation 9]

[0600]

[0601] In equation 9, This indicates the reference transmit power configuration value, and can be adjusted according to various transmit types. The value can have different values ​​and can be changed by higher-layer signals such as RRC or MAC CE. If the value is changed by MAC CE and a HARQ-ACK for a received MAC CE PDSCH is sent in time slot k, the UE determines the value from time slot k + k. offset Start applying this value. k offset The subcarrier intervals can have different values, for example, they can be 3ms. This indicates the size of the frequency resource domain to which the PUCCH is allocated. This represents the path attenuation estimate of the UE, and as described above in Equation 7, it is calculated by the UE based on specific reference signals in various CSI-RS or SS / PBCH according to the higher-layer signal configuration and type. The same Applicable to repeated PUCCH transmissions. Same. Suitable for repeated PUCCH transmission.

[0602] [HARQ-ACK: About Type 1 (Semi-static) Codebooks]

[0603] When the number of HARQ-ACK PUCCHs that a UE can send in a time slot is limited to one, upon receiving a semi-static HARQ-ACK codebook with higher-layer configuration, the UE reports HARQ-ACK information for PDSCH reception or SPS PDSCH release within the HARQ-ACK codebook in the time slot indicated by the value of the PDSCH-HARQ feedback timing indicator in DCI format 1_0 or DCI format 1_1. The UE reports the HARQ-ACK information bit values ​​within the HARQ-ACK codebook via NACK in time slots not indicated by the PDSCH-HARQ feedback timing indicator field in DCI format 1_0 or DCI format 1_1. If the UE reports only HARQ-ACK information about a PDSCH reception or an SPS PDSCH release during the MAC timing for candidate PDSCH reception, and if the report is scheduled by DCI format 1_0 including information indicating 1 in the counter DAI field of the Pcell, then the UE determines a HARQ-ACK codebook for the corresponding SPS PDSCH transmission or the corresponding PDSCH reception.

[0604] In other cases, the HARQ-ACK codebook determination method follows the procedure below.

[0605] If the PDSCH reception candidate time set in serving cell c is MA,c, then MA,c can be obtained through the following steps [pseudocode 1].

[0606] [Beginning of Pseudocode 1]

[0607] Step 1: Initialize j to 0, and initialize MA,c to an empty set. Initialize the HARQ-ACK transmission timing index k to 0.

[0608] Step 2: Configure R as a set of rows in the table, including information about the time slot to which the PDSCH is mapped, information about the start symbol, and information about the number or length of the symbols. If each value of R indicates a PDSCH available for mapping as a UL symbol based on the DL and UL configurations of the upper layer, then delete the corresponding row from R.

[0609] - Step 3-1: If the UE is able to receive a PDSCH for unicast in a time slot and R is not an empty set, then add a PDSCH to set MA,c.

[0610] -Step 3-2: If the UE is able to receive two or more PDSCHs for unicast in one time slot, count the number of PDSCHs that can be allocated in different symbols according to the calculated R, and add the same number of PDSCHs as the counted number to MA,c.

[0611] Step 4: Increment k by 1, and then start from step 2 again.

[0612] [End of Pseudocode 1]

[0613] by Figure 19 As an example, pseudocode 1 is described, considering all slot candidates that can indicate the availability of HARQ-ACK timing for PDSCH in slot #k 1908, so that HARQ-ACK PUCCH transmission can be performed in slot #k 1908. Figure 19 In this context, assuming that HARQ-ACK transmission is possible in time slot #k 1908 via a combination of PDSCH-to-HARQ-ACK timings, only PDSCHs scheduled in time slots #n 1902, #n+1 1904, and #n+2 1906 are possible under this timing. Furthermore, for each of time slots 1902, 1904, and 1906, the maximum number of PDSCHs that can be scheduled in each time slot is determined by considering the temporal resource configuration information of the PDSCHs available for scheduling in each time slot and information indicating whether the symbols in the time slot are downlinks or uplinks. For example, if two PDSCHs in time slot 1902, three PDSCHs in time slot 1904, and two PDSCHs in time slot 1906 are available for maximum scheduling, then the maximum number of PDSCHs included in the HARQ-ACK codebook transmitted in time slot 1908 is seven. This is called the cardinality of the HARQ-ACK codebook.

[0614] Step 3-2 within a specific time slot will be described using Table 44 below (Default PDSCH Time Domain Resource Allocation A for Normal CP).

[0615] [Table 44]

[0616]

[0617] Table 44 is the time resource allocation table, according to which the UE operates by default before receiving time resource allocation via a separate RRC signal. For reference, the PDSCH time resource allocation value is determined not only by the RRC-indicated row index value but also by the dmrs-TypeA-Position, which is the UE's common RRC signal. In Table 44, for ease of description, the end column and sequence column are values ​​added separately and may not actually exist. The end column indicates the end symbol of the scheduled PDSCH, and the sequence column indicates the code position value within a specific codebook in the semi-static HARQ-ACK codebook. The corresponding table is applied to the time domain resource allocation of DCI format 1_0 in the common search space of the PDSCH.

[0618] To determine the HARQ-ACK codebook, the UE calculates the maximum number of non-overlapping PDSCHs within a specific time slot. To do this, the UE performs the following operations.

[0619] Step 1: Locate the PDSCH allocation value that ends first within the time slot in all rows of the PDSCH time resource allocation table. In Table 44, it can be seen that row index 14 ends first. This row index is indicated as "1" in the sequence column. In addition, other row indices that overlap with row index 14 in at least one symbol are indicated as "1x" in the sequence column.

[0620] Step 2: Then, among the remaining row indices not indicated in the sequence column, find the PDSCH allocation value that ends first within the time slot. In Table 44, the row with row index 7 and dmrs-TypeA-Position value 3 corresponds to this. Other row indices that overlap with the corresponding row index in at least one symbol are indicated as "2x" in the sequence column.

[0621] Step 3: Repeat Step 2, incrementing and indicating the sequence value. For example, in the row indices not indicated in the sequence column of Table 44, find the PDSCH assignment value that ends first. In Table 44, the row with row index 6 and dmrs-TypeA-Position value 3 corresponds to this. Furthermore, other row indices that overlap with the corresponding row index in at least one symbol are indicated as "3x" in the sequence column.

[0622] Step 4: The process terminates when all row indices indicate an order value. The size of the order corresponds to the maximum number of PDSCHs that can be scheduled without time overlap within the corresponding time slot. Non-overlapping scheduling means scheduling different PDSCHs in a TDM manner.

[0623] In the "Sequence" column of Table 44, the maximum value of "Sequence" indicates the size of the HARQ-ACK codebook for the corresponding time slot, and the sequence value indicates the HARQ-ACK codebook point where the HARQ-ACK feedback bit of the corresponding scheduled PDSCH is located. For example, row index 16 of Table 44 indicates that the HARQ-ACK feedback bit corresponding to the PDSCH is located at the second code position in a semi-static HARQ-ACK codebook of size 3. If the set of timings for receiving candidate PDSCHs in serving cell c is MA,c, the UE sending the HARQ-ACK feedback can obtain MA,c through the steps of [Pseudocode 1] or [Pseudocode 2]. MA,c can be used to determine the number of HARQ-ACK bits to be sent by the UE. Specifically, the HARQ-ACK codebook can be configured using the cardinality of the set MA,c.

[0624] As another example, considerations for determining a semi-static HARQ-ACK codebook (or a type 1 HARQ-ACK codebook) may include the following.

[0625] a) Regarding a set of time slot timing values ​​associated with the activity UL BWP

[0626] a) If the UE is configured to monitor the PDCCH of DCI format 1_0 on serving cell c, but not configured to monitor the PDCCH of DCI format 1_1, then the timing values ​​of the slots in DCI format 1_0 {1,2,3,4,5,6,7,8} are provided.

[0627] b) If the UE is configured to monitor the PDCCH of serving cell c in DCI format 1_1, then it is provided by dl-DataToUL-ACK in DCI format 1_1.

[0628] b) A set of row indexes R for a table provided by the first set of row indexes of the table provided by PDSCH-TimeDomainResourceAllocationList in PDSCH-ConfigCommon or the default PDSCH time domain resource allocation A [6, TS38.214], or by the union of the first set of row indexes and the second set of row indexes. If provided by PDSCH-TimeDomainResourceAllocationList in PDSCH-Config, it is associated with the active DL BWP and the corresponding time slot offset set is defined. The start and length indicators SLIV and the PDSCH mapping type received by PDSCH, as described in [6, TS38.214].

[0629] c) Regarding downlink SCS configuration Uplink SCS configuration The ratio between Subcarrier Spacing in the BWP downlink and BWP uplink respectively provides support for active DL BWP and active UL BWP.

[0630] d) If provided, then TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated as described in Sub-clause 11.1.

[0631] Another example of pseudocode used for HARQ-ACK codebook determination can be as follows.

[0632] [Beginning of Pseudocode 2]

[0633] For this set of time slot timing values The UE determines a set of candidate PDSCH reception or SPS PDSCH release based on the following pseudocode. Timing. The position of the HARQ-ACK information corresponding to the SPS PDSCH release in the Type-1 HARQ-ACK codebook is the same as the position of the corresponding SPS PDSCH reception.

[0634] set up - Timing index of candidate PDSCH reception or SPS PDSCH release

[0635] set up

[0636] set up

[0637] Will Set as a set cardinality

[0638] set up k =0-Service Cell set Medium time slot timing value The index is sorted in descending order by time slot timing value.

[0639] While

[0640] If

[0641] set up - Index of DL time slots within UL time slots

[0642] when

[0643] Set R as a row set

[0644] Will Set as the base of R

[0645] Set r = 0 - the row index in set R.

[0646] If (if) time slot The time slot changes simultaneously with or after the active DL BWP on serving cell c or the active UL BWP on PCell, and the time slot... Before the time slot for an active DLBWP change on service cell c or an active UL BWP change on PCell.

[0647] continue;

[0648] otherwise

[0649] when

[0650] If (if) UE is provided TDD-UL-DL-ConfigurationCommon or TDD-UL-DL- ConfigDedicated And for time slots Time slot For each time slot, at least one symbol of the PDSCH time resource derived from line r is configured as UL, where It is a set The timing value of the k-th time slot in the data.

[0651] ;

[0652] End conditional statement (end if)

[0653] r = r + 1;

[0654] End the while loop (end while)

[0655] If the UE does not indicate the ability to receive more than one unicast PDSCH per time slot and ,

[0656] ;

[0657] j = j + 1;

[0658] The UE does not expect to receive SPS PDSCH release and unicast PDSCH in the same time slot;

[0659] otherwise

[0660] Will Set as the base of R

[0661] Set m to all rows of R containing SLIV Determined minimum last OFDM symbol index

[0662] when

[0663] Set r=0

[0664] when

[0665] If (if) for the starting OFDM symbol index S of line r

[0666] ; - Index of the timing of candidate PDSCH reception or SPS PDSCH release associated with line r

[0667] R = R / r;

[0668] ;

[0669] end if

[0670] r = r + 1;

[0671] end while

[0672]

[0673] j = j + 1;

[0674] Set m to the smallest last OFDM symbol index among all rows of R;

[0675] end while

[0676] end if

[0677] end if

[0678] ;

[0679] end while

[0680] end if

[0681] ;

[0682] end while

[0683] [End of Pseudocode 2]

[0684] In pseudocode 2, the location of the HARQ-ACK information in the HARQ-ACK codebook that includes the DCI indicating the release of the DL SPS is determined based on the location of the received DL SPS PDSCH. For example, if the starting symbol for transmitting the DL SPS PDSCH is the fourth OFDM symbol based on the time slot and has a length of 5 symbols, the HARQ-ACK information including the release of the DL SPS indicating the release of the corresponding SPS can be determined by assuming that the PDSCH has been mapped. The PDSCH starts from the fourth OFDM symbol in the time slot, where the DL SPS release has been transmitted, and has a length of 5 symbols. This HARQ-ACK information can be determined by the PDSCH-to-HARQ-ACK timing indicator and the PUSCH resource indicator included in the control information indicating the release of the DL SPS. As another example, if the starting symbol used to send the DL SPS PDSCH is the fourth OFDM symbol based on the time slot and has a length of 5 symbols, then the HARQ-ACK information including the DL SPS release indicating the release of the corresponding SPS can be determined by assuming that the PDSCH has been mapped. The PDSCH starts from the fourth OFDM symbol in the time slot indicated by the DCI's Time Domain Resource Allocation (TDRA), which is the DL SPS release, and has a length of 5 symbols. This HARQ-ACK information can be determined by the PDSCH-to-HARQ-ACK timing indicator and the PUSCH resource indicator included in the control information indicating the DL SPS release.

[0685] [HARQ-ACK: About Type 2 (Dynamic) Codebook]

[0686] The UE transmits HARQ-ACK information on one of the PUCCHs in time slot n, which is used for PDSCH reception or SPS PDSCH release, based on the PDSCH to HARQ feedback timing value and K0 (which is the transmission time slot position information of the PDSCH scheduled by DCI format 1_0 or 1_1) transmitted in the PUCCH of time slot n. Specifically, for the above HARQ-ACK information transmission, the UE determines the HARQ-ACK codebook of the PUCCH to be transmitted in the time slot determined by the PDSCH to HARQ feedback timing and K0, based on the DAI included in the DCI indicating the release of PDSCH or SPS PDSCH.

[0687] DAI includes counter DAI and total DAI. Counter DAI is information indicating the position in the HARQ-ACK codebook corresponding to the HARQ-ACK information associated with a PDSCH scheduled in DCI format 1_0 or DCI format 1_1. Specifically, the value of counter DAI in DCI format 1_0 or 1_1 represents the cumulative number of PDSCH receptions or SPS PDSCH releases scheduled by DCI format 1_0 or 1_1 in a particular cell c. The cumulative value is configured based on the serving cell and the timing of PDCCH monitoring for the presence of the scheduled DCI.

[0688] Total DAI is a value indicating the size of the HARQ-ACK codebook. Specifically, the total DAI value represents the total number of PDSCHs or SPS PDSCHs released before (and including) the time point when the DCI is scheduled. Furthermore, total DAI is a parameter used in carrier aggregation (CA) scenarios, where the HARQ-ACK information in serving cell c includes the HARQ-ACK information of PDSCHs scheduled in other cells, including serving cell c. In other words, there is no total DAI parameter in a system operating as a single cell.

[0689] Example of DAI operation: Figure 20 As shown. Figure 20 The diagram illustrates the changes in the values ​​of the counter DAI (C-DAI) and total DAI (T-DAI) indicated by the DCI retrieved at each PDCCH monitoring opportunity for each carrier when the UE transmits a HARQ-ACK codebook based on DAI selection on PUCCH 2020 in the nth time slot of carrier 0 2002, with two carriers configured. First, the DCI found at m=0 2006 indicates that both C-DAI and T-DAI are 1 (indicated by "2012"). The DCI found at m=12008 indicates that both C-DAI and T-DAI are 2 (indicated by "2014"). The DCI found at m=2 2010 in carrier 0 (c=0, 2002) indicates that the C-DAI value is 3 (indicated by "2016"). In the DCI retrieved on carrier 1 (c=1) 2004 at m=2 2010, C-DAI can indicate a value of 4 in 2018. If carriers 0 and 1 are scheduled during the same monitoring period, both T-DAIs are indicated by 4.

[0690] exist Figure 19 and Figure 20In this method, the determination of the HARQ-ACK codebook is performed under the condition that only one PUCCH carrying HARQ-ACK information is transmitted in a time slot. This is called Mode 1. As an example of a method for determining a PUCCH transmission resource within a time slot, when PDSCHs scheduled by different DCIs are multiplexed with a HARQ-ACK codebook and transmitted in the same time slot, the PUCCH resource selected for HARQ-ACK transmission is determined to be the PUCCH resource indicated by the PUCCH resource field indicated in the DCI, and the PDSCH was most recently scheduled by the DCI. That is, PUCCH resources indicated by the PUCCH resource field indicated in the DCI scheduled before the DCI are ignored.

[0691] The following description defines a method and apparatus for determining the HARQ-ACK codebook in a time slot where two or more PUCCHs, including HARQ-ACK information, can be transmitted. This is referred to as Mode 2. A UE can operate only in Mode 1 (transmitting only one HARQ-ACK PUCCH in a time slot) or only in Mode 2 (transmitting one or more HARQ-ACK PUCCHs in a time slot). Alternatively, a UE supporting both Mode 1 and Mode 2 can be configured to operate only in one mode by the base station via higher-layer signaling, or Mode 1 and Mode 2 can be implicitly determined by DCI format, RNTI, DCI-specific field values, scrambling, etc. For example, a PDSCH scheduled by DCI format A and its associated HARQ-ACK information is based on Mode 1, while a PDSCH scheduled by DCI format B and its associated HARQ-ACK information is based on Mode 2. Whether the aforementioned HARQ-ACK codebook is semi-static or dynamic is determined by the RRC signal.

[0692] [Measuring gap]

[0693] The measurement gap (MG) will be described below. Before handover, the UE typically measures the cell power (signal quality) of the target cell and reports the measured cell power to the base station. The base station can then determine whether to handover the UE to the target cell based on the reported measurement results. Measuring the signal quality of the target cell at a different frequency than the current cell (inter-frequency measurement) from the UE's perspective can be more complex than measuring the signal quality of the target cell at the same frequency as the serving cell (inter-frequency measurement). This is because it may require implementing two RF transceivers to measure different frequencies, and this dual-transceiver solution presents several practical problems. First, implementing additional transceivers incurs extra cost. Second, frequency interference can occur when the frequencies of the serving cell and the target cell are close to each other. To address these issues, a measurement gap is introduced, whereby the UE does not transmit or receive signals during the corresponding interval. Therefore, since there is no signal transmission or reception during the measurement gap, the UE can handover to the target cell and perform signal quality measurements before returning to the serving cell. For this purpose, the base station can pre-configure higher-layer signaling associated with the measurement gap for the UE, thereby enabling the UE to measure the signal quality of the target cell within the corresponding gap interval.

[0694] When a UE needs to measure gaps to identify and measure intra-frequency cells and / or inter-frequency cells and / or inter-RAT E-UTRAN cells, and the UE does not support independent measurement gap modes for different frequency ranges, the network should provide a single measurement gap mode for each UE to monitor all frequency layers simultaneously, in order to meet the requirements of the following clauses.

[0695] When a UE requires measurement gaps to identify and measure intra-frequency cells and / or inter-frequency cells and / or inter-RAT E-UTRAN cells, and the UE supports independent measurement gap modes for different frequency ranges, the network should provide a measurement gap mode for each FR for independent and simultaneous monitoring of all frequency layers in each frequency range, or provide a single measurement gap mode for each UE for simultaneous monitoring of all frequency layers in all frequency ranges, in order to comply with the requirements of the following terms.

[0696] When a UE configures Reference Signal Time Difference (RSTD), Positioning Reference Signal (PRS)-Reference Signal Received Power (RSRP), and UE Rx-Tx Time Difference Measurement via the LTE Positioning Protocol (LPP), the network should provide the following.

[0697] - Individual measurement gap mode for each UE, used to simultaneously monitor all positioning frequency layers and intra-frequency, inter-frequency, and / or RAT inter-frequency layers across all frequency ranges; or

[0698] - For measurement gap modes other than #24 and #25, when the UE supports independent measurement gap modes for different frequency ranges for PRS measurements, the measurement gap mode of each FR is used to simultaneously monitor all positioning frequency layers in the corresponding frequency range as well as intra-frequency and inter-frequency cell and / or RAT inter-frequency layers.

[0699] During the measurement interval of each UE, the UE:

[0700] -According to TS 38.321, apart from receiving (multiple) RRM measurements and signals used for random access procedures, it is not necessary to perform reception / transmission from / to the corresponding E-UTRAN PCell, (multiple) E-UTRAN SCell and NR serving cell, nor is it necessary to transmit to them;

[0701] -According to TS 38.321, apart from (multiple) RRM measurements, (multiple) PRS measurements and signal reception for random access procedures, it is not necessary to perform reception / transmission to or from the corresponding NR serving cell of the SA (single carrier or CA configuration), nor is it necessary to transmit to it;

[0702] -According to TS 38.321, apart from receiving (multiple) RRM measurements, (multiple) PRS measurements, and signals used for random access procedures, it is not necessary to perform NR-E-UTRA dual-connectivity reception / transmission from / to the corresponding PCell, (multiple) SCell, and E-UTRAN serving cell, nor is it necessary to transmit to them; and

[0703] According to TS 38.321, apart from receiving (multiple) RRM measurements, (multiple) PRS measurements, and signals used for random access procedures, it is not necessary to perform reception / transmission to or from the corresponding NR serving cell to / from the NR-DC.

[0704] During the measurement interval of each FR, UE:

[0705] -According to TS 38.321, apart from receiving (multiple) RRM measurements and signals used for random access procedures, it is not necessary to perform reception / transmission from / to the corresponding E-UTRAN PCell, (multiple) E-UTRAN SCell and NR serving cell, nor is it necessary to transmit to them;

[0706] -According to TS 38.321, apart from receiving (multiple) RRM measurements, (multiple) PRS measurements and signals used for random access procedures, it is not necessary to perform reception / transmission from / to the corresponding NR serving cell, nor is it necessary to transmit to it;

[0707] -According to TS 38.321, apart from receiving (multiple) RRM measurements, (multiple) PRS measurements, and signals used for random access procedures, it is not necessary to perform NR-E-UTRA dual-connectivity reception / transmission from / to the corresponding PCell, (multiple) SCell, and E-UTRAN serving cell, nor is it necessary to transmit to them; and

[0708] -According to TS 38.321, apart from receiving (multiple) RRM measurements, (multiple) PRS measurements, and signals used for random access procedures, it is not necessary to perform reception / transmission from / to the corresponding NR serving cell, nor is it necessary to transmit to it.

[0709] The UE should support the measurement gap pattern listed in Table 45 based on the applicability specified in Table 46. The UE determines the measurement gap timing based on the gap offset configuration and measurement gap timing advance configuration provided by the higher-layer signaling specified in TS 38.331 and TS 36.331.

[0710] [Table 45]

[0711]

[0712] Gap pattern Configurations: Gap pattern configuration

[0713] Gap mode ID, measurement gap length (MGL, ms), measurement gap repetition period (MGRP, ms)

[0714] [Table 46]

[0715] Applicability of gap mode configuration supported by E-UTRA-NR dual-connectivity UE or NR-E-UTRA dual-connectivity UE

[0716]

[0717] Figure 21 The transmission and reception measurement gaps and SS / PBCH blocks according to embodiments of this disclosure are illustrated. Figure 21 In the figure, reference numeral 2100 illustrates the measurement gap configuration resource 2104 of the UE when the measurement gap repetition period, measurement gap length, and measurement offset are configured to 40ms, 6ms, and 0 respectively via higher-layer signaling, as shown in Table 45. Figure 21 In the figure, reference numeral 2102 illustrates a configuration where the SS / PBCH block is configured to have a repetition period of 20 ms and the SS / PBCH block 2106 is transmitted during a 5 ms interval. Figure 21In the accompanying drawings, reference numerals 2100 and 2102 correspond to the same frame, and for ease of description, the cases of periodically configuring measurement gaps and periodically transmitting and receiving SS / PBCH blocks are shown, respectively. The UE can measure received signal quality by performing channel estimation using SS / PBCH blocks in the intra-frequency or inter-frequency domain during the measurement gap. Typically, the base station can configure the length of the measurement gap interval to be longer than the length of the SS / PBCH block interval. This is because when measuring frequency bands of different frequency bands or different RATs, the UE may require additional time for RF retuning. Typically, the measurement gap can include all or part of the SS / PBCH block transmission resources. For example... Figure 21 As shown, the transmit and receive periods of the SS / PBCH block and the measurement gap period can be the same, or the measurement gap period can be longer than the transmit and receive periods of the SS / PBCH block. Figure 21 In this context, SFN is an abbreviation for System Frame Number, which consists of 10 subframes.

[0718] In the following, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. As used herein, a base station is an entity that allocates resources to a terminal and may be at least one of a gNode B, gNB, eNode B, Node B, base station (BS), radio access unit, base station controller, or node on a network. A terminal may include a user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. In the following description of embodiments of the present disclosure, a 5G system will be described by way of example, but embodiments of the present disclosure can also be applied to other communication systems with similar technical backgrounds or channel types. For example, such communication systems may include mobile communication technologies such as LTE or LTE-A, as well as mobile communication technologies developed after 5G. Therefore, based on the determination of those skilled in the art, embodiments of the present disclosure can also be applied to other communication systems with some modifications without departing from the scope of the present disclosure. The content of this disclosure can be applied to FDD, TDD, and XDD (and / or SBFD, full-duplex) systems.

[0719] Furthermore, in describing this disclosure, detailed descriptions of known functions or configurations included herein will be omitted where it is determined that such description might unnecessarily obscure the subject matter of the disclosure. Additionally, the terminology described below is defined with reference to the functions in this disclosure and may vary depending on the intent or custom of the user or operator. Therefore, its definition should be based on the entirety of this specification.

[0720] In the following description of this disclosure, upper-layer signaling (or upper-level signaling) may refer to signaling corresponding to at least one of the following signaling, or a combination of one or more thereof.

[0721] -Master Message Block (MIB)

[0722] -System Information Block (SIB) or SIB X (X=1, 2, ...)

[0723] - Radio Resource Control (RRC)

[0724] -Media Access Control (MAC) Controller Element (CE)

[0725] In addition, L1 signaling can refer to signaling corresponding to at least one of the following signaling methods that use physical layer channels or signaling, or a combination of one or more of them.

[0726] -Physical Downlink Control Channel (PDCCH)

[0727] Downlink Control Information (DCI)

[0728] -UE-specific DCI

[0729] -Public DCI Group

[0730] -Public DCI

[0731] - Scheduling DCI (e.g., DCI used to schedule downlink or uplink data)

[0732] - Non-scheduled DCI (e.g., DCI not used for scheduling downlink or uplink data)

[0733] -Physical Uplink Control Channel (PUCCH)

[0734] -Uplink Control Information (UCI)

[0735] As used in this article, the term “skip” can be replaced by other terms with similar meanings. For example, “skip” can be replaced by terms such as “cancel,” “omit,” and “pause.”

[0736] As used herein, the term “slot” can generally refer to a specific unit of time corresponding to a transmission time interval (TTI), specifically a slot used in a 5G NR system, or a slot or subframe in a 4G LTE system.

[0737] As described below, the above examples can be described through multiple embodiments, but the above examples are not independent of each other, and one or more embodiments can be applied simultaneously or in combination.

[0738] The scheduling constraints caused by measurement gaps will be described below. (See reference...) Figure 21During the measurement gap interval, the UE may refrain from transmitting and receiving on either the uplink or downlink channel according to the following procedure. The operation of the UE's serving cell within the corresponding frequency range of the measurement gap configured via higher-layer signaling related to the measurement gap during the active measurement gap can be referenced in Table 47.

[0739] [Table 47]

[0740]

[0741] As described in Table 47 above, the UE does not perform general data transmission and reception during the measurement gaps configured by the base station. Therefore, in the case of latency-sensitive services (such as XR services), additional latency may occur due to the inability to transmit and receive data within the corresponding intervals, thus potentially preventing the fulfillment of XR service requirements. For example, when an XR service occurs at the start of a measurement gap, the UE may be unable to transmit or receive data during the measurement gap interval but may transmit or receive data immediately after the measurement gap ends. Therefore, in this case, a latency of at least the measurement gap interval may occur. Furthermore, the more frequently the measurement gap is configured with repetitive intervals, the higher the frequency of the above situation. Therefore, a more adaptive method for configuring measurement gap intervals may be needed to process services such as XR services more quickly. A combination of one or more embodiments in the following examples may be used.

[0742] [Example 1]

[0743] In the following description, Example 1 describes a method in which a base station instructs a UE not to dynamically perform measurements during a Measurement Gauge (MG) interval and is able to send and receive data or control information. For ease of description, in the following embodiments, UE skipping an MG interval means that the UE does not perform measurements during the corresponding MG interval and is able to send and receive data or control information. Base station instructing UE to skip an MG interval means that the base station instructs the UE not to perform measurements during the corresponding MG interval and is able to send and receive data or control information. For ease of description, in the following embodiments, UE not skipping an MG interval means that the UE performs measurements during the corresponding MG interval and follows the operations described in Table 47. Base station not instructing UE to skip an MG interval and / or base station instructing UE not to skip an MG interval means that the base station instructs the UE to perform measurements during the corresponding MG interval.

[0744] For example, a base station can notify the UE whether it wants to skip the MG interval immediately following (or after) the corresponding DCI format by using a 1-bit DCI field in the DCI format (e.g., an MG skip indicator). A method for configuring the bits of an indicator that indicates whether to perform an MG skip will be described in detail below.

[0745] For example, when the 1-bit MG skip indicator in the corresponding DCI format indicates 0 (or 1), this can mean that the UE does not skip the MG interval immediately following the corresponding DCI format. Conversely, when the 1-bit MG skip indicator in the corresponding DCI format indicates 1 (or 0), this can mean that the UE skips the MG interval immediately following the corresponding DCI format. The DCI format can be a DCI format used for scheduling PDSCH, a DCI format used for scheduling PUSCH, or a DCI format provided to the UE together when there is no separate data scheduling information.

[0746] Although the MG skip indicator is described as a single bit in the example above, multiple bits can be configured. That is, the MG skip indicator can consist of one or more bits. Furthermore, the MG skip indicator can be configured using bit information from another DCI field in the DCI format. For example, one of the five MCS bits can be used for the MG skip indicator. Alternatively, one or more most significant bits (MSBs) or one or more least significant bits (LSBs) from another DCI field can be used.

[0747] Figure 22 A dynamic skipping process for the measurement gap according to an embodiment of this disclosure is illustrated. Figure 22 In the figures, reference numerals 2200, 2202, 2204, 2206, and 2208 denote the DCI format transmitted and received on the PDCCH, and reference numerals 2210 and 2212 denote the first MG interval and the second MG interval, respectively. Reference numerals 2220 and 2222 indicate reference time points used to determine whether to skip the corresponding MG interval. The DCI format transmitted and received on the PDCCH can be transmitted and received in one or more of 2200, 2202, 2204, 2206, and 2208. In the following text, reference will be made to... Figure 22 Describe a method for indicating whether to skip each MG interval using skip information in DCI format. A combination of one or more of the following methods may be used.

[0748] Method 1-1: Method 1-1 is a method of indicating whether the immediately following MG interval has been skipped by using a 1-bit MG skip indicator. As described above, when at least one of MG intervals 2210 and 2212 indicates an MG skip indicator with a value of 1 (or 0), the UE can determine that the first MG interval has been skipped. Alternatively, when both MG intervals 2210 and 2212 indicate MG skip indicators with a value of 0 (or 1), the UE can determine that the first MG interval has not been skipped. Furthermore, DCI formats received after reference time point 2220 may not indicate whether the first MG interval has been skipped. For example, DCI formats 2200 and 2202 are signals indicating whether the first MG interval 2210 has been skipped, but signals received after reference time point 2220 may not indicate whether the first MG interval has been skipped. The DCI format may be a DCI format for scheduling PDSCH, a DCI format for scheduling PUSCH, or a DCI format in the absence of data scheduling. Similarly, DCI formats 2204, 2206, and 2208 are signals indicating whether the second MG interval 2212 is skipped, and signals received after reference time point 2222 may not indicate whether the second MG interval is skipped. Reference time point 2220 can be defined as the time point relative to the first start symbol of the first MG interval existing before the X value. Here, the value of X can correspond to T in [Equation 2]. proc,1 T in [Equation 3] proc,2 min(T) proc,1 , T proc,2 ), max(T) proc,1 , T proc,2 The value of X is defined by the UE capability report, or a combination thereof (or a value obtained by dividing any of the above values ​​by a natural number). For example, when the MG skip indicator is only included in the DCI format used for scheduling PDSCH, the value of X can be determined as T in Equation 2]. proc,1 When the MG skip indicator is only included in the DCI format used for scheduling PUSCH, the value of X can be determined as T in [Equation 2]. proc,2 And when the MG skip indicator is included in each of the DCI formats for scheduling PUSCH and PDSCH, the value of X can be determined as max(T). proc,1 , T proc,2Alternatively, the value of X may correspond to a value after a predetermined time from the time the UE sends a PUCCH or PUSCH in response to the reception of the DCI format. Alternatively, the value of X may be determined by the UE capability, and the final value of X may be configured by the base station through higher-layer signaling considering the UE capability. Furthermore, the value of X may have different values ​​depending on the purpose or intended use of the MG interval. For example, the value of X applied to intra-cell measurements and the value of X applied to inter-cell measurements may be different. Alternatively, the value of X applied to FR1 measurements and the value of X applied to FR2 measurements may be different. Additionally, the UE determines whether to skip the earliest MG existing after the X time starting from the last symbol or time of receiving the DCI format including the MG skip indicator information.

[0749] Method 1-2: Method 1-2 is a method that uses a 2-bit MG skip indicator to indicate whether to skip each of the two immediately following MG intervals. For example, when the 2-bit MG skip indicator is configured in DCI format 2200 or 2202, the MSB can be used to indicate whether to skip the first MG interval 2210, and the LSB can be used to indicate whether to skip the second MG interval 2212. Similarly, when the 2-bit MG skip indicator is configured in DCI formats 2204, 2206, or 2208, the MSB can be used to indicate whether to skip the second MG interval 2212, and the LSB can be used to indicate whether to skip another MG interval configured immediately after the second MG interval. Therefore, for skipping information of the second MG interval, in DCI formats transmitted and received before reference time point 2220, skipping the second MG interval is indicated by the LSB, while in DCI formats transmitted and received after reference time point 2220, skipping the second MG interval is indicated by the MSB. Furthermore, the configuration related to X can be similar to Method 1-1. In addition, the UE refers to the last symbol or time of the DCI format received, which includes MG skip indicator information, to determine whether to skip each of the earliest MG interval and the second MG interval that exists after time X.

[0750] Method 1-3: Method 1-3 is a method that uses an n-bit (n>2) MG skip indicator to indicate whether to skip each of the immediately following n MG intervals. Method 1-3 is similar to Methods 1-1 and 1-2. The k-th bit of the n-bit (n>2) MG skip indicator can be used to indicate whether to skip the k-th MG interval in chronological order among the n MG intervals. Furthermore, the configuration associated with X can be similar to Method 1-1. Additionally, the UE refers to the last symbol or time of the DCI format received, which includes the MG skip indicator information, to determine whether to skip each of the first n MGs existing after time X.

[0751] Method 1-4: Method 1-4 is a method for implicitly indicating whether an MG interval should be skipped without using a separate MG skip indicator bit. Specifically, when the PDSCH or PUSCH resources provided via DCI overlap with at least one MG interval in terms of time resources, the UE can determine that the corresponding MG interval has been skipped. Such operation can be performed by pre-configuration via higher-layer signaling. When there is no separate higher-layer signaling, if the PDSCH or PUSCH resources provided via DCI overlap with at least one MG interval in terms of time resources, the UE can treat it as an error condition and not skip the corresponding MG interval.

[0752] - Method 1-5: In methods 1-1 to 1-3, when the DCI format providing PDSCH or the DCI format providing PUSCH includes an MG skip indicator, the CRC of the corresponding DCI format is scrambled with CS-RNTI, and the DCI format is used to activate SPS PDSCH or CG PUSCH. If all bits of the MG skip indicator are 1 (or at least one bit is 1), the UE may consider skipping the periodically configured MG interval after the X value starting from the receipt of the corresponding DCI format. Furthermore, when the MG skip indicator is included in the DCI format providing PDSCH or the DCI format providing PUSCH, and the corresponding DCI format is scheduled with CS-RNTI and is used to activate SPS PDSCH or CG PUSCH, if all bits of the MG skip indicator are 0 (or at least one bit is 0), the UE may consider not skipping the periodically configured MG interval after the X value starting from the receipt of the corresponding DCI format.

[0753] - Method 1-6: The UE can apply methods 1-1 to 1-3 only when the CRC of the DCI format is scrambled with C-RNTI. In other words, the UE can apply methods 1-1 to 1-3 except when the CRC of the corresponding DCI format is scrambled with CS-RNTI and the DCI format is used to activate SPS PDSCH or CG PUSCH. If the CRC of the corresponding DCI format is scrambled with CS-RNTI and an MG skip indicator exists in the DCI format used to activate SPS PDSCH or CG PUSCH, the corresponding field can always be fixed at 0 (or 1).

[0754] In the description of the above method, the MG interval has been mainly described as a reference. Figure 22 The diagram shows a continuous MG interval, but multiple discontinuous MG intervals can refer to a single MG interval. For example, Figure 22The first MG interval 2210 and the second MG interval 2212 can refer to a single MG interval. This can be determined by higher-layer signaling or L1 signaling. In methods 1-1 to 1-3, the provision of an MG skip indicator has been described, and this can be performed by the base station pre-configuring an MG skip indicator field consisting of n bits from DCI format 0_x or DCI format 1_x via higher-layer signaling. When there is no separate higher-layer signaling, the MG skip indicator field is configured with 0 bits. Furthermore, this can only be applied when the UE reports a UE capability indicating that the UE supports this operation before the base station provides higher-layer signaling to the UE.

[0755] [Example 2]

[0756] In the following, Embodiment 2 describes a method for determining the interval for receiving information indicating whether an MG skip is to be performed. Although Embodiment 1 described above as valid for an MG skip indicator in DCI format sent up to a certain point in time, Embodiment 2 will be described by considering whether an MG skip indicator in DCI format to be sent from a certain point in time is invalid.

[0757] Figure 23 A determined interval for dynamically skipping measurement gaps according to an embodiment of this disclosure is shown. Figure 23 In the figures, reference numerals 2300 and 2302 denote the DCI format transmitted and received on the PDCCH, and reference numerals 2310 and 2312 denote the first MG interval and the second MG interval, respectively. Reference numerals 2320 and 2322 indicate reference time points used to determine whether to skip the corresponding MG interval. The DCI format transmitted and received on the PDCCH can be transmitted and received using one or more of reference numerals 2300 and 2302.

[0758] For example, when a 1-bit MG skip indicator is configured, the interval in which the DCI format that can send and receive information about whether to skip the second MG interval 2312 can be determined as follows: Figure 23 [2320, 2322]. Here, reference time points 2320 and 2322 represent reference times X times earlier than the starting point of the starting symbol of the first MG interval and the second MG interval, respectively. The definition of X is the same as that described in Example 1.

[0759] As another example, when a 1-bit MG skip indicator is configured, the interval in which the DCI format that can be sent and received, providing information about whether to skip the second MG interval 2312, can be determined as follows: Figure 23[The last time point of the first MG interval 2310, reference time point 2322]. As another example, when a 1-bit MG skip indicator is configured, the interval in which the DCI format information on whether the second MG interval 2312 has been skipped can be determined as [the last time point of the first MG interval 2310, reference time point 2322]. Figure 23 [The starting time point of the first MG interval 2310, reference time point 2322].

[0760] Furthermore, when the first time point corresponding to the first MG interval 2310 is referred to as reference time point 2320, the second time point corresponding to the second MG interval 2312 is referred to as reference time point 2322, and the time point corresponding to the nth MG interval is referred to as the nth time point, the intervals that can be sent and received in DCI format providing 1-bit information about whether to skip the nth MG interval can be between the (n-1)th time point and the nth time point. The intervals that can be sent and received in DCI format providing 2-bit information about whether to skip the nth MG interval can be between the (n-2)th time point and the nth time point. The intervals that can be sent and received in DCI format providing 3-bit information about whether to skip the nth MG interval can be between the (n-3)th time point and the nth time point. The intervals that can be sent and received in DCI format providing k-bit information about whether to skip the nth MG interval can be between the (nk)th time point and the nth time point.

[0761] Alternatively, when the first time point corresponding to the first MG interval 2310 is reference time point 2320, the second time point corresponding to the second MG interval 2312 is reference time point 2322, and the time point corresponding to the nth MG interval is referred to as the nth time point, the interval in DCI format that can be sent and received, providing 1 bit information about whether the nth MG interval is skipped, can be between the last time point of the (n-1)th MG interval and the nth time point. The interval in DCI format that can be sent and received, providing 2 bits information about whether the nth MG interval is skipped, can be between the last time point of the (n-2)th MG interval and the nth time point. The interval in DCI format that can be sent and received, providing 3 bits information about whether the nth MG interval is skipped, can be between the last time point of the (n-3)th MG interval and the nth time point. The interval in DCI format that can be sent and received, providing k bits information about whether the nth MG interval is skipped, can be between the last time point of the (nk)th MG interval and the nth time point.

[0762] Alternatively, when the first time point corresponding to the first MG interval 2310 is reference time point 2320, the second time point corresponding to the second MG interval 2312 is reference time point 2322, and the time point corresponding to the nth MG interval is referred to as the nth time point, intervals in DCI format that can be sent and received, providing 1-bit information about whether to skip the nth MG interval, can be between the start time point of the (n-1)th MG interval and the nth time point. Intervals in DCI format that can be sent and received, providing 2-bit information about whether to skip the nth MG interval, can be between the start time point of the (n-2)th MG interval and the nth time point. Intervals in DCI format that can be sent and received, providing 3-bit information about whether to skip the nth MG interval, can be between the start time point of the (n-3)th MG interval and the nth time point. Intervals in DCI format that can be sent and received, providing k-bit information about whether to skip the nth MG interval, can be between the start time point of the (nk)th MG interval and the nth time point.

[0763] Alternatively, the UE may receive DCI format 2300 or 2302 including MG skip indicator information, and the MG interval for which the MG skip indicator is applied may be the first n MG intervals existing after X, respectively, of the time resource of the reference DCI format 2300 or 2302. Here, n may have the same value as the size of the MG skip indicator field. The value of X is the same as that described in Embodiment 1, and may be provided with different values ​​depending on the UE capability and the type of DCI format, wherein the MG skip information is configured for the DCI format via higher-layer signaling (e.g., whether the DCI format is a DCI format for scheduling PDSCH or a DCI format for scheduling PUSCH).

[0764] [Example 3]

[0765] In the following, Example 3 describes a method for configuring multiple bits, each indicating whether to skip a portion of the MG interval, and a method for configuring a deadline.

[0766] Figure 24 This illustrates a determined interval according to an embodiment of the present disclosure, where measurement gaps can be dynamically partially skipped. Figure 24In the diagram, reference numerals 2400 and 2402 denote the DCI format transmitted and received on the PDCCH, and reference numerals 2410 and 2412 denote the first and second partial MG intervals, respectively. Reference numerals 2420 and 2422 indicate reference time points used to determine whether to skip the corresponding partial MG interval. The partial MG interval is used to indicate whether to skip each partial MG interval by dividing an interval configured as a continuous MG into n equal parts. The DCI format transmitted and received on the PDCCH can be transmitted and received using one or more of 2400 and 2402.

[0767] Despite Figure 24The first and second MG intervals are shown to have the same time length, but they can have different lengths. This can be configured via higher-layer signaling. Furthermore, while an MG interval is shown as being divided into two MG intervals, it can be divided into three or more MG intervals. For example, when a UE receives a DCI format including a 2-bit MG skip indicator, the corresponding bits can indicate whether to skip the first and second MG intervals, respectively. For example, when receiving "10", the UE can skip the first MG interval and may not skip the second MG interval. Since the corresponding MG intervals have different start times, the intervals during which the corresponding information is valid can be applied differently. For example, the UE can determine that the information used to determine whether to skip the first MG interval is valid only for DCI formats received before or at reference time 2420. The UE can determine that the information used to determine whether to skip the second MG interval is valid only for DCI formats received before or at reference time 2422. For example, when the MG skip indicator "11" is received in DCI format 2400, it can be determined that the first part MG interval and the second part MG interval have been skipped. On the other hand, if the MG skip indicator "00" has already been received in DCI format 2400, and the MG skip indicator "11" is received in DCI format 2402, the UE can determine that only the second part MG interval has been skipped. Furthermore, the UE can determine that the skipping is applied to another first part MG interval configured after the second part MG interval 2412. That is, the deadline for applying each piece of information can be configured differently depending on the position of the bits in the DCI field. Alternatively, regardless of the above, the deadline can be determined based on the DCI format. For example, the last time point in the DCI format that can send and receive indications of whether each of the first part MG interval and the second part MG interval has been skipped can be determined as reference time point 2420. That is, the MG skip indicator in the DCI format transmitted and received after reference time point 2420 can be determined to be applied to other MG intervals configured after the first part MG interval 2410 and the second part MG interval 2412.

[0768] [Example 4]

[0769] In the following, Example 4 describes the UE determination operation in the case of scheduling multiple DCI formats that indicate whether to skip a specific MG interval. Figure 22As an example, a total of three DCI formats 2204, 2206, and 2208 are transmitted and received to indicate whether the second MG interval 2212 is skipped. When the MG skip indicator consists of 1 bit and the MG skip indicator in DCI format 2204 indicates 1 (or 0), the UE can determine that the second MG interval 2212 has been skipped. However, if the MG skip indicator in DCI format 2206 or DCI format 2208 transmitted and received after DCI format 2204 indicates 0, the UE needs to determine whether the second MG interval 2212 is still skipped based on the MG skip indicator information in DCI format 2204, or whether the second MG interval 2212 is not skipped based on the most recently received MG skip indicator information in DCI format 2206 or DCI format 2208. Therefore, the UE can apply at least one of the following methods.

[0770] Method 4-1: When the MG skip indicator information in DCI format 2204 is indicated as 1 (or 0), the MG skip indicator in DCI format 2206 or DCI format 2208 must be indicated as 1 (or 0). That is, if the MG skip indicator in a previous DCI format indicates a skip, then the MG skip indicator in DCI format sent and received thereafter and before reference time point 2222 should indicate a skip value. On the other hand, when the MG skip indicator information in DCI format 2204 is indicated as 0 (or 1), the MG skip indicator in DCI format 2206 can be indicated as 1 (or 0). That is, if the MG skip indicator in a previous DCI format indicates no skip, then the MG skip indicator in DCI format sent and received thereafter and before reference time point 2222 can indicate a skip. In summary, once the base station reports to the UE that a skip is to be performed, the same information related to the skip should be provided to the UE until the deadline for determining whether to skip the corresponding MG interval. Otherwise, the UE may consider this an error. Figure 22 For example, the MG skip indicators in DCI formats 2204, 2206, and 2208 are interrelated.

[0771] Method 4-2: The MG skip indicators in DCI formats 2204, 2206, and 2208 can be independent of each other. For example, regardless of whether the MG skip indicator information in DCI format 2204 indicates 0 or 1, the MG skip indicator information in subsequent DCI formats 2206 or 2208 can also indicate 0 or 1. In this case, the UE ultimately determines whether to skip the second MG interval 2212 based on the MG skip indicator information in DCI format 2208 most recently received before reference time point 2222. Therefore, when the MG skip indicator in DCI format 2208 is 1, the UE can determine that the second MG interval 2212 has been skipped, and when the MG skip indicator in DCI format 2208 is 0, the UE can determine that the second MG interval 2212 has not been skipped.

[0772] [Example 5]

[0773] In the following section, Example 5 describes a UE capability report related to MG skipping. MG skipping can help reduce data latency and improve data transmission rates by allowing the UE to skip measurements and perform data scheduling within the corresponding interval, but it may increase the probability of handover failure due to missed measurement timing. Therefore, the UE can report to the base station in advance how many measurement gaps are required at least during a predetermined interval. For example, the length (Y2) of the measurement gap required during a specific interval (Y1) can be reported as a UE capability. Thus, when determining whether to skip an MG interval, the base station can determine whether to perform the skip by referring to the corresponding UE capability information received from the UE.

[0774] [Example 6]

[0775] In the following, in Embodiment 6, as described in Embodiment 1, an MG skip indicator field may be included in the DCI format, and the UE may determine whether to skip a specific MG interval in response to receiving the corresponding DCI format. When the UE does not receive a DCI format including the MG skip indicator field after receiving higher-layer signaling related to the MG skip indicator from the base station, the UE may determine that the corresponding MG interval has been skipped. As another example, when the UE does not receive a DCI format including the MG skip indicator field after receiving higher-layer signaling related to the MG skip indicator from the base station, the UE may determine that the corresponding MG interval has not been skipped. As yet another example, when the UE does not receive higher-layer signaling related to the MG skip indicator from the base station, the UE may determine that the corresponding MG interval has not been skipped.

[0776] Figure 25 This is a flowchart illustrating UE operation according to an embodiment of the present disclosure, where measurement gaps can be dynamically skipped. It is possible to... Figure 25The method shown in the flowchart can be modified in various ways. For example, although shown as a series of operations, the various operations in the various figures can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, an operation can be omitted or replaced by another operation.

[0777] refer to Figure 25 In Operation 2501, after initial access, the UE reports its MG-related UE capabilities to the base station. The UE can report its MG-related UE capabilities to the base station, and the base station can receive its MG-related UE capabilities.

[0778] In Operation 2503, the UE receives information about the MG period, offset, length, etc. (measurement gap configuration) from the base station via higher-layer signaling. The base station can send the measurement gap configuration to the UE, and the UE can receive the measurement gap configuration. This may occur before the UE capability report, as per the reference. Figure 25 The order of description is different.

[0779] In Operation 2505, the UE performs measurements at periodically configured MG intervals.

[0780] In operation 2507, when an emergency service occurs, the base station can provide the UE with an indication (adaptive measurement gap indication) regarding whether to skip the MG interval by applying at least one embodiment of the above embodiments. According to at least one embodiment of the above embodiments of this disclosure, the base station can provide the UE with an adaptive measurement gap indication, and the UE can receive / recognize the adaptive measurement gap indication.

[0781] Subsequently, in operation 2509, when the base station indicates to skip subsequent MG intervals, the UE does not perform measurements, but instead performs transmission and reception of control and data information provided by L1 signals (or higher-layer signaling) within the corresponding interval. Alternatively, when the base station does not indicate to skip subsequent MG intervals, the UE performs measurements and performs the operations described in Table 47.

[0782] For details regarding UE operation and base station operation according to the embodiments of the present disclosure described above, please refer to the description of the embodiments of the present disclosure described above.

[0783] Figure 26 The structure of a UE in a wireless communication system according to an embodiment of the present disclosure is shown.

[0784] refer to Figure 26The UE may include a transceiver, a memory (not shown), and a UE processor 2605 (or a UE controller or processor), wherein the transceiver generally refers to the UE receiver 2600 and the UE transmitter 2610. The UE transceivers 2600 and 2610, the memory, and the UE processor 2605 can operate according to the communication method described above for the UE. However, the components of the UE are not limited to the examples described above. For example, the UE may also include more or fewer components than those described above. Furthermore, the transceiver, memory, and processor may be implemented as a single chip.

[0785] A transceiver can transmit / receive signals with a base station. These signals can include control information and data. For this purpose, a transceiver can include an RF transmitter configured to perform amplification and frequency up-conversion of the transmitted signal, an RF receiver configured to perform low-noise amplification and frequency down-conversion of the received signal, and so on. However, this is merely one embodiment of a transceiver, and the components of the transceiver are not limited to RF transmitters and RF receivers.

[0786] In addition, the transceiver can receive signals via a radio channel, output them to the processor, and transmit signals output from the processor via a radio channel.

[0787] The memory can store programs and data required for UE operation. Additionally, the memory can store control information or data included in signals transmitted / received by the UE. The memory can include storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or combinations of storage media. Furthermore, the memory can include multiple memories.

[0788] The processor can control a series of processes that enable the UE to operate according to the embodiments described above. For example, the processor can control the UE's components to receive DCIs configured in two layers to receive multiple PDSCHs simultaneously. The processor may include multiple processors, and the processors can perform control operations on the UE's components by executing programs stored in memory.

[0789] Figure 27 The structure of a base station in a wireless communication system according to an embodiment of the present disclosure is shown.

[0790] refer to Figure 27The base station may include a transceiver, a memory (not shown), and a base station processor 2705 (or a base station controller or processor), wherein the transceiver generally refers to the base station receiver 2700 and the base station transmitter 2710. The base station transceivers 2700 and 2710, the memory, and the base station processor 2705 can operate according to the communication method described above for the base station. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than those described above. Furthermore, the transceiver, memory, and processor may be implemented as a single chip.

[0791] A transceiver can transmit / receive signals with a UE. These signals can include control information and data. For this purpose, a transceiver can include an RF transmitter configured to perform amplification and frequency up-conversion of the transmitted signal, an RF receiver configured to perform low-noise amplification and frequency down-conversion of the received signal, and so on. However, this is merely one embodiment of a transceiver, and the components of the transceiver are not limited to RF transmitters and RF receivers.

[0792] In addition, the transceiver can receive signals via a radio channel, output them to the processor, and transmit signals output from the processor via a radio channel.

[0793] The memory can store programs and data required for base station operation. Additionally, the memory can store control information or data included in signals transmitted / received by the base station. The memory can include storage media such as ROM, RAM, hard disks, CD-ROMs, and DVDs, or combinations of storage media. Furthermore, the memory can include multiple memories.

[0794] The processor can control a series of processes that enable the base station to operate according to the embodiments of the present disclosure described above. For example, the processor can control each component of the base station to configure a two-layer DCI including allocation information for multiple PDSCHs and to transmit these DCIs. The processor may include multiple processors, and the processors can perform control operations on the components of the base station by executing programs stored in memory.

[0795] The methods disclosed in the claims or the methods described in the embodiments of this disclosure may be implemented by hardware, software, or a combination of hardware and software.

[0796] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors within an electronic device. At least one program includes instructions to cause the electronic device to perform a method according to the appended claims and / or various embodiments of the present disclosure disclosed herein.

[0797] These programs (software modules or software) can be stored in non-volatile memory, including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), disk storage devices, optical disc-ROM (CD-ROM), digital versatile disc (DVD) or other types of optical storage devices, or magnetic tape. Alternatively, the programs can be stored in memory configured as some or all of these. Furthermore, multiple such memories may be included.

[0798] Furthermore, the program can be stored in an attachable storage device that can access the electronic device via a communication network such as the Internet, intranet, local area network (LAN), wide area network (WLAN), and storage area network (SAN), or a combination thereof. Such a storage device can access the electronic device via an external port. Additionally, a separate storage device on the communication network can access the device executing embodiments of this disclosure.

[0799] In the detailed embodiments described above, the elements included in this disclosure are represented in a singular or plural form according to the presented embodiments. However, for ease of description, the singular or plural form may be appropriately chosen depending on the presented situation, and this disclosure is not limited to elements represented in a singular or plural form. Therefore, an element represented in a plural form may also include a single element, or an element represented in a singular form may also include multiple elements.

[0800] The embodiments of this disclosure described and illustrated in the specification and drawings are merely specific examples presented to facilitate the explanation of the technical content of this disclosure and to aid in understanding it, and are not intended to limit the scope of this disclosure. That is, it will be apparent to those skilled in the art that other variations based on the technical ideas of this disclosure can be implemented. Furthermore, the various embodiments described above can be combined as needed. For example, a portion of one embodiment of this disclosure can be combined with a portion of another embodiment to operate a base station and a terminal. For example, a portion of a first embodiment of this disclosure can be combined with a portion of a second embodiment to operate a base station and a terminal. Moreover, although the above embodiments are described based on an FDD LTE system, other variations based on the technical ideas of the embodiments can also be implemented in other communication systems such as TDD LTE, 5G, or NR systems.

[0801] In the accompanying drawings describing the methods of this disclosure, the order of description does not always correspond to the order of execution steps, and the order relationship between steps can be changed, or steps can be executed in parallel.

[0802] Alternatively, in the accompanying drawings describing the methods of this disclosure, some elements may be omitted and only some elements may be included without departing from the basic spirit and scope of this disclosure.

[0803] Furthermore, in the methods of this disclosure, some or all of the contents of each embodiment may be combined to implement them without departing from the basic spirit and scope of this disclosure.

[0804] Various embodiments of this disclosure have been described above. The foregoing description is for illustrative purposes only and is not intended to limit the embodiments of this disclosure to those described herein. Those skilled in the art will understand that other specific modifications and changes can be readily made to the form of this disclosure without altering its technical concept or essential characteristics. The scope of this disclosure is defined by the appended claims rather than the detailed description above, and the scope of this disclosure should be interpreted to include all variations or modifications derived from the meaning and scope of the claims and their equivalents.

Claims

1. A method performed by a terminal in a communication system, the method comprising: MG configuration is received via high-level signaling; Identify one or more MGs based on the MG configuration; The downlink control information (DCI) format is received via the physical downlink control channel (PDCCH), and the DCI format includes fields related to whether MG cancellation is performed. Identify a specific MG from the one or more MGs; as well as The specific MG is cancelled if the MG is identified as needing to be cancelled based on the fields related to whether MG cancellation is performed.

2. The method of claim 1, wherein the specific MG is the earliest MG starting X time intervals after the end time of the PDCCH, and The X time intervals are defined based on the UE capability report of the terminal.

3. The method of claim 1, wherein, in the case of receiving a plurality of DCI formats associated with the particular MG and each DCI format including the field associated with whether MG cancellation is performed, the DCI format is the last of the plurality of DCI formats.

4. The method according to claim 1, wherein the DCI format is DCI format 0_X or DCI format 1_X. This includes identifying whether configuration regarding the inclusion of the field related to whether to perform MG cancellation has been received via the higher-layer signaling. Where the configuration regarding the field related to whether to perform MG cancellation has been received, the field related to whether to perform MG cancellation is 1 bit. Where no configuration is received regarding the field containing the information related to whether to perform MG cancellation, the field related to whether to perform MG cancellation is 0 bits. Wherein, if the configuration containing the fields related to whether to perform MG cancellation has been received, the receiving of the DCI format containing the fields related to whether to perform MG cancellation is performed.

5. The method of claim 1, wherein a value of 1 in the field associated with whether to cancel the MG indicates that the MG should be canceled, and A value of 0 in the field related to whether to cancel MG indicates that the MG is not canceled.

6. The method of claim 5, wherein the field having a value of 0 that is related to whether MG cancellation is performed is ignored.

7. A terminal in a communication system, the terminal comprising: transceiver; and A processor connected to the transceiver. The processor is configured as follows: MG configuration is received via high-level signaling; Identify one or more MGs based on the MG configuration; The downlink control information (DCI) format is received via the physical downlink control channel (PDCCH), and the DCI format includes fields related to whether MG cancellation is performed. Identify a specific MG from the one or more MGs; as well as The specific MG is cancelled if the MG is identified as needing to be cancelled based on the fields related to whether MG cancellation is performed.

8. The terminal according to claim 7, wherein the specific MG is the earliest MG starting X time intervals after the end time of the PDCCH, and The X time intervals are defined based on the UE capability report of the terminal.

9. The terminal of claim 7, wherein, when receiving a plurality of DCI formats associated with the particular MG and each DCI format including the field associated with whether MG cancellation is performed, the DCI format is the last of the plurality of DCI formats.

10. The terminal according to claim 7, wherein the DCI format is DCI format 0_X or DCI format 1_X. This includes identifying whether configuration regarding the inclusion of the field related to whether to perform MG cancellation has been received via the higher-layer signaling. Where the configuration regarding the field related to whether to perform MG cancellation has been received, the field related to whether to perform MG cancellation is 1 bit. Where no configuration is received regarding the field containing the information related to whether to perform MG cancellation, the field related to whether to perform MG cancellation is 0 bits. Wherein, if the configuration containing the fields related to whether to perform MG cancellation has been received, the receiving of the DCI format containing the fields related to whether to perform MG cancellation is performed.

11. The terminal of claim 7, wherein a value of 1 in the field related to whether to perform MG cancellation indicates that the MG is to be cancelled, and A value of 0 for the field related to whether to cancel MG indicates that the MG is not canceled.

12. The terminal of claim 11, wherein the field having a value of 0 that is related to whether MG cancellation is performed is ignored.

13. A method performed by a base station in a communication system, the method comprising: The measurement gap MG configuration is transmitted via higher-layer signaling, and the MG configuration is associated with one or more MGs; Identify a specific MG from the one or more MGs; Downlink control information in DCI format, including fields related to whether MG cancellation is performed, is transmitted via the Physical Downlink Control Channel (PDCCH). as well as Communication is performed within the specific MG if the MG is cancelled based on the field indicating whether or not MG cancellation is performed.

14. The method of claim 13, wherein a value of 1 in the field associated with whether to perform MG cancellation indicates that the MG is to be cancelled, and A value of 0 in the field related to whether to cancel MG indicates that the MG is not canceled.

15. A base station in a communication system, the base station comprising: transceiver; and A processor connected to the transceiver. The processor is configured as follows: The measurement gap MG configuration is transmitted via higher-layer signaling, and the MG configuration is associated with one or more MGs; Identify a specific MG from the one or more MGs; Downlink control information in DCI format, including fields related to whether MG cancellation is performed, is transmitted via the Physical Downlink Control Channel (PDCCH). as well as Communication is performed within the specific MG if the MG is cancelled based on the field indicating whether or not MG cancellation is performed.

Images