Methods and apparatus for transmitting and receiving data information in satellite communication systems

Abstract

This disclosure relates to fifth-generation (5G) or sixth-generation (6G) communication systems for supporting higher data transmission rates. A method performed by a user equipment (UE) in the communication system is provided. The method includes: identifying a Physical Uplink Shared Channel (PUSCH) transmission to be transmitted on a time slot; identifying a plurality of Orthogonal Cover Code (OCC) groups corresponding to the PUSCH transmission; and transmitting the PUSCH transmission on the time slot, the PUSCH transmission having OCCs based on the plurality of OCC groups applied, wherein the same redundant version RV value is applied to one of the plurality of OCC groups.

Description

Technical Field

[0001] This disclosure relates to wireless communication systems. More specifically, this disclosure relates to the operation of user equipment (UE) and base station (BS) in satellite communication systems, and methods for transmitting and receiving data information in satellite communication systems, and apparatus capable of performing such methods. Background Technology

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

[0003] In the early stages of 5G mobile communication technology development, to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC), standardization has been ongoing for the following technologies: beamforming and massive multiple-input multiple-output (MIMO) for reducing radio wave path loss and increasing radio wave transmission distance in millimeter waves; support parameter sets for dynamic operation (e.g., operating multiple subcarrier spacings) for efficient utilization of millimeter wave resources and time slot formats; initial access technologies for supporting multi-beam transmission and broadband; definition and operation of bandwidth portions (BWP); new channel coding methods such as low-density parity-check (LDPC) codes for large-volume data transmission and polar codes for highly reliable transmission of control information; layer 2 (L2) preprocessing; and network slicing for providing dedicated networks for specific services.

[0004] Currently, regarding the services supported by 5G mobile communication technology, the industry is discussing improvements and performance enhancements to the initial 5G mobile communication technology, and physical layer standardization has been completed for technologies such as: Vehicle-to-Everything (V2X) for assisting autonomous vehicle driving decisions and improving user convenience based on information sent by the vehicle about its location and status; Unlicensed New Radio (NR-U) designed to comply with various regulatory requirements in unlicensed frequency bands for system operation; NR-U UE power saving; Non-Terrestrial Networks (NTN) for direct satellite communication between UEs to provide coverage in areas where communication with terrestrial networks is not possible; and positioning.

[0005] Furthermore, standardization of air interface architectures / protocols for technologies such as: 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 (RACH for NR) for simplifying the random access process. Standardization of system architectures / services for technologies such as: 5G baseline architectures (e.g., service-based architectures or service-based interfaces) for combining Virtual Network Functions (NFV) and Software-Defined Networking (SDN) technologies; and Mobile Edge Computing (MEC) for receiving services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, the already exponentially growing number of connected devices will connect to communication networks, thus necessitating enhanced functionality and performance of 5G mobile communication systems, as well as the integrated operation of connected devices. To this end, new research is planned related to the following technologies: Extended Reality (XR) for efficient support of Augmented Reality (AR), Virtual Reality (VR), Mixed Reality (MR), etc.; 5G performance improvements and complexity reductions through the utilization of Artificial Intelligence (AI) and Machine Learning (ML); AI service support; Metaverse service support; and drone communication.

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

[0008] The above information is presented as background information only to aid in understanding this disclosure. No decision has been made, nor any assertion has been asserted, regarding whether any of the above content is applicable as prior art in connection with this disclosure. Summary of the Invention

[0009] [Technical Issues]

[0010] The aspects of this disclosure are intended to at least address the aforementioned problems and / or disadvantages, and to provide at least the advantages described below. Therefore, one aspect of this disclosure will provide an apparatus and method capable of efficiently providing services in a wireless communication system.

[0011] Other aspects will be set forth in part in the description which follows, and will be apparent in part from the description, or may be learned by practice of the embodiments presented.

[0012] [Solution to the problem]

[0013] According to one aspect of this disclosure, a method performed by a user equipment (UE) in a communication system is provided. The method includes: identifying a Physical Uplink Shared Channel (PUSCH) transmission to be transmitted in a time slot; identifying a plurality of Orthogonal Cover Code (OCC) groups corresponding to the PUSCH transmission; and transmitting the PUSCH transmission in the time slot, the PUSCH transmission having OCCs applied based on the plurality of OCC groups, wherein the same Redundancy Version (RV) value is applied to one of the plurality of OCC groups.

[0014] According to an embodiment, the method further includes receiving downlink control information (DCI) including PUSCH scheduling information and an RV field, wherein the PUSCH transmission is identified based on the DCI.

[0015] According to an embodiment, the RV value identified based on the RV field is cyclically applied to multiple OCC groups.

[0016] According to an embodiment, the method further includes receiving a first configuration associated with PUSCH repetition and a second configuration associated with OCC length.

[0017] According to an embodiment, the PUSCH transmission corresponds to PUSCH repetition, and wherein, when the number of repetitions of the PUSCH repetition is greater than the OCC length, the RV value is cyclically applied to multiple OCC groups.

[0018] According to an embodiment, the same RV value is applied to multiple OCC groups.

[0019] According to an embodiment, the PUSCH transmission is sent in a non-terrestrial network (NTN).

[0020] According to another aspect of this disclosure, a user equipment (UE) in a communication system is provided. The UE includes a transceiver; and a processor connected to the transceiver and configured to: identify a Physical Uplink Shared Channel (PUSCH) transmission to be transmitted on a time slot; identify a plurality of Orthogonal Cover Code (OCC) groups corresponding to the PUSCH transmission; and transmit the PUSCH transmission on the time slot, the PUSCH transmission having an OCC applied based on the plurality of OCC groups, wherein the same Redundancy Version (RV) value is applied to one of the plurality of OCC groups.

[0021] According to an embodiment, the processor is further configured to receive downlink control information (DCI) including PUSCH scheduling information and an RV field, wherein the DCI includes an RV field for PUSCH transmission.

[0022] According to an embodiment, the RV value identified based on the RV field is cyclically applied to multiple OCC groups.

[0023] According to an embodiment, the processor is further configured to receive a first configuration associated with PUSCH repetition and a second configuration associated with OCC length.

[0024] According to an embodiment, when the number of repetitions of PUSCH is greater than the OCC length, the RV value is cyclically applied to multiple OCC groups.

[0025] According to an embodiment, the same RV value is applied to multiple OCC groups.

[0026] According to an embodiment, the PUSCH transmission is sent in a non-terrestrial network (NTN).

[0027] According to another aspect of this disclosure, a method performed by a base station in a communication system is provided. The method includes: transmitting downlink control information (DCI) including Physical Uplink Shared Channel (PUSCH) scheduling information; and receiving a PUSCH transmission in a time slot, the PUSCH transmission having an OCC based on multiple orthogonal coverage code (OCC) groups corresponding to the PUSCH transmission, wherein the same redundancy version (RV) value is applied to one of the multiple OCC groups.

[0028] According to an embodiment, the DCI includes the RV field.

[0029] According to an embodiment, the RV value associated with the RV field is applied cyclically to multiple OCC groups.

[0030] According to an embodiment, the method further includes sending a first configuration associated with PUSCH repetition and a second configuration associated with OCC length.

[0031] According to an embodiment, the PUSCH transmission corresponds to PUSCH repetition, and wherein, when the number of repetitions of the PUSCH repetition is greater than the OCC length, the RV value is cyclically applied to multiple OCC groups.

[0032] According to an embodiment, the same RV value is applied to multiple OCC groups.

[0033] According to an embodiment, the PUSCH transmission is received in a non-terrestrial network (NTN).

[0034] According to another aspect of this disclosure, a base station in a communication system is provided. The base station includes a transceiver; and a processor connected to the transceiver and configured to: transmit downlink control information (DCI) including physical uplink shared channel (PUSCH) scheduling information; and receive PUSCH transmissions in time slots, the PUSCH transmissions having an OCC based on multiple orthogonal coverage code (OCC) groups corresponding to the PUSCH transmissions, wherein the same redundancy version (RV) value is applied to one of the multiple OCC groups.

[0035] According to an embodiment, the DCI includes the RV field.

[0036] According to an embodiment, the RV value associated with the RV field is applied cyclically to multiple OCC groups.

[0037] According to an embodiment, the processor is further configured to send a first configuration associated with PUSCH repetition and a second configuration associated with OCC length.

[0038] According to an embodiment, when the number of repetitions of PUSCH is greater than the OCC length, the RV value is cyclically applied to multiple OCC groups.

[0039] According to an embodiment, the same RV value is applied to multiple OCC groups.

[0040] According to an embodiment, the PUSCH transmission is received in a non-terrestrial network (NTN).

[0041] [Beneficial Effects]

[0042] The embodiments described herein provide an apparatus and method for efficiently providing services in a wireless communication system.

[0043] Other aspects, advantages, and distinctive features of this disclosure will become apparent to those skilled in the art from the following detailed description of various embodiments thereof, taken in conjunction with the accompanying drawings. Attached Figure Description

[0044] The above and other aspects, features, and advantages of certain embodiments of this disclosure will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which: 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; Figure 2 The structure of frames, subframes, and time slots in a wireless communication system according to embodiments of the present disclosure is shown; Figure 3 An example of bandwidth configuration in a wireless communication system according to an embodiment of the present disclosure is shown; Figure 4 An example of the control resource set configuration of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown; Figure 5 The structure of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown; Figure 6 This illustrates, from a span perspective, the situation where a UE in a wireless communication system according to an embodiment of the present disclosure may have multiple PDCCH monitoring opportunities within a time slot; Figure 7 An example of base station beam allocation configured according to the Transmission Configuration Indicator (TCI) state in a wireless communication system according to an embodiment of the present disclosure is shown; 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; Figure 9 The TCI indication media access control (MAC) control element (MAC CE) signaling structure for PDCCH DMRS in a wireless communication system according to an embodiment of the present disclosure is shown. 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; 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 channels and rate matching resources, is illustrated. Figure 12 A method is shown in which a UE in a wireless communication system according to an embodiment of the present disclosure selects a set of receivable control resources by considering priority when receiving a downlink control channel; Figure 13 An example of a non-periodic CSI reporting method according to an embodiment of this disclosure is shown; Figure 14An example of PUSCH repetition type B transmission in a wireless communication system according to an embodiment of the present disclosure is shown; 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. Figure 16 An example of antenna port configuration and resource allocation for cooperative communication in a wireless communication system according to an embodiment of the present disclosure is shown; Figure 17 An example of downlink control information (DCI) configuration for cooperative communication in a wireless communication system according to an embodiment of the present disclosure is shown; Figure 18 The process of a base station controlling the transmit power of a UE in a cellular system according to an embodiment of the present disclosure is illustrated; Figure 19 The process of a UE generating a Type 1 (semi-static) Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) codebook according to an embodiment of this disclosure is illustrated. 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; Figure 21 The Earth orbit period of a communication satellite according to an embodiment of this disclosure is shown. Figure 22 This is a block diagram illustrating a method for generating LTE Physical Uplink Control Channel (PUCCH) format 5 according to an embodiment of the present disclosure; Figure 23 This invention illustrates a method by which different UEs perform mapping to virtual frequency subcarriers (tones) by applying different OCC values, according to embodiments of the present disclosure. Figure 24 This is a flowchart illustrating a UE processing procedure for PUSCH transmission according to an embodiment of the present disclosure; Figure 25 This invention illustrates a method for applying an OCC scheme when a UE performs a PUSCH retransmission for each time slot, according to an embodiment of the present disclosure. Figure 26 This invention illustrates a method for applying an OCC scheme when a UE performs a PUSCH retransmission within a time slot, according to an embodiment of the present disclosure. Figure 27 This invention illustrates a method for applying an OCC scheme from a time resource perspective when a UE performs a PUSCH transmission, according to an embodiment of the present disclosure. Figure 28This invention illustrates a method for applying an OCC scheme from a frequency resource perspective when a UE performs a PUSCH transmission, according to an embodiment of the present disclosure. Figure 29 This is a diagram illustrating OCC spread spectrum applied to each PUSCH group according to an embodiment of the present disclosure; Figure 30 This illustrates a situation where a specific PUSCH and PUCCH overlap when the UE performs a PUSCH retransmission according to an embodiment of this disclosure; Figure 31 The resource allocation shown is based on an embodiment of the present disclosure, illustrating the order in which uplink control information (UCI) is multiplexed to the PUSCH; Figure 32 The present disclosure illustrates the scheduling of PUSCH retransmissions by a UE according to an embodiment of the present disclosure, where PUSCH retransmissions overlap with PUCCH retransmissions. Figure 33 The process of performing a PUSCH transfer in conjunction with an OCC scheme according to an embodiment of this disclosure is illustrated; Figure 34 The structure of a UE in a wireless communication system according to an embodiment of the present disclosure is shown; and Figure 35 The structure of a base station in a wireless communication system according to an embodiment of the present disclosure is shown.

[0045] In all the accompanying drawings, the same reference numerals are used to denote the same elements. Detailed Implementation

[0046] The following description, with reference to the accompanying drawings, is provided to aid in a full understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. This description includes various specific details to aid understanding, but these are to be considered exemplary only. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. Furthermore, for clarity and brevity, descriptions of well-known functions and structures may be omitted.

[0047] The terms and words used in the following description and claims are not limited to their dictionary literal meanings, but are used by the inventors only to achieve a clear and consistent understanding of this disclosure. Therefore, those skilled in the art will understand that the following description, which provides various embodiments of this disclosure, is for illustrative purposes only and is not intended to limit the disclosure as defined by the appended claims and their equivalents.

[0048] It should be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context explicitly specifies otherwise. Thus, for example, referring to “the surface of a component” includes referring to one or more such surfaces.

[0049] In the following description, a base station is an entity that allocates resources to a terminal and can be at least one of the following: gNode B, eNode B (eNB), Node B, base station (BS), radio access unit, base station controller, and nodes on a network. A terminal can include user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. In this disclosure, "downlink (DL)" 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, in the following description, Long Term Evolution (LTE) or Enhanced LTE (LTE-A) systems are described by way of example, but embodiments of this disclosure can also be applied to other communication systems with similar technical backgrounds or channel types. Examples of such communication systems can include fifth-generation mobile communication technologies (5G, New Radio, and NR) developed on top of LTE-A, and in the following description, "5G" can be a concept covering 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 the scope of this disclosure.

[0050] In this document, it will be understood that each block of a flowchart illustration, and combinations of blocks in a flowchart illustration, 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 to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more flowchart blocks. These computer program instructions can also be stored in a computer-usable or computer-readable storage medium that can direct 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 writing including instruction means for implementing the functions specified in one or more flowchart blocks. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operations to be performed on the computer or other programmable apparatus, thereby producing a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide operations for implementing the functions specified in one or more flowchart blocks.

[0051] Furthermore, each block in the flowchart diagram can represent a module, segment, or section of code, which includes one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions recorded in a block may occur out of order. For example, two blocks shown consecutively may actually execute substantially simultaneously, or these blocks may sometimes execute in reverse order, depending on the functions involved.

[0052] 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" is not always 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, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. 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, elements and "units" can be implemented as one or more central processing units (CPUs) within a playback device or secure multimedia card. Additionally, in embodiments, a "unit" may include one or more processors.

[0053] Wireless communication systems are evolving into broadband wireless communication systems that use communication standards and typical voice-based services to provide high-speed and high-quality packet data services. These communication standards include High-Speed ​​Packet Access (HSPA) of the 3rd Generation Partnership Project (3GPP), LTE (Long Term Evolution or Evolved Universal Terrestrial Radio Access (E-UTRA)), LTE Enhanced (LTE-A), LTE-Pro, High-Rate Packet Data (HRPD) of 3GPP2, Ultra Mobile Broadband (UMB), IEEE 802.16e, etc.

[0054] 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 eNodeB, 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 separate the data or control information of each user by allocating and manipulating the time and frequency resources used to transmit data or control information for each user, thus avoiding overlap and establishing orthogonality.

[0055] As a communication system following LTE, 5G communication systems must flexibly respond to the diverse needs of users and service providers, and therefore must support services that meet these diverse needs. Services considered in 5G communication systems include enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable low-latency communication (URLLC).

[0056] 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 20Gbps in the downlink and 10Gbps in the uplink for a single base station. Furthermore, 5G communication systems must provide increased 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 a frequency bandwidth greater than 20MHz in the 3GHz to 6GHz band, or 6GHz or higher, instead of using the maximum 20MHz transmission bandwidth in the 2GHz band used in LTE.

[0057] Furthermore, mMTC is considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently deliver IoT, mMTC has requirements such as supporting a large number of UEs in a cell, enhancing UE coverage, improving battery life, and reducing UE costs. Since IoT provides communication capabilities while being supplied to various sensors and devices, it must support a large number of UEs in a cell (e.g., 1,000,000 UEs / km). 2 Furthermore, mMTC-enabled UEs may require wider coverage than other services provided by 5G communication systems because the UE may be located in shaded areas such as the basement of a building, which are not covered by the cell due to the nature of the service. mMTC-enabled UEs must be configured to be inexpensive and may require very long battery life (such as 10 to 15 years) because it is difficult to replace the UE's battery frequently.

[0058] 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, telemedicine, and emergency alerts. Therefore, URLLC must provide communication with ultra-low latency and ultra-high reliability. For example, services supporting URLLC must meet an air interface latency of less than 0.5ms, and may also require 10... -5Or even lower packet error rates. Therefore, for services that support URLLC, 5G systems must provide shorter Transmission Time Intervals (TTIs) than other services, and may also require designs that allocate significant resources in the frequency band to ensure the reliability of communication links.

[0059] These 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 across the services to meet their varying requirements. Of course, 5G is not limited to these three services.

[0060] To meet the increased demand for wireless data traffic since the deployment of 4G communication systems, efforts have been focused on developing improved 5G or near-5G communication systems. Therefore, 5G or near-5G communication systems are also referred to as "super-4G network" communication systems 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 propagation loss and increase transmission distance of radio waves in the mmWave 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, 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, cooperative multipoint (CoMP), and receiver interference cancellation. In 5G systems, hybrid frequency shift keying (FSK) and quadrature amplitude modulation (QAM) (FQAM) as advanced coding and modulation (ACM) schemes, as well as sliding window superposition coding (SWSC), and filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies have also been developed.

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

[0062] Correspondingly, various attempts have been made to apply 5G communication systems (fifth-generation communication systems or New Radio (NR)) to IoT networks. For example, technologies such as sensor networks, machine-type communication (MTC), and machine-to-machine (M2M) communication are implemented using beamforming, MIMO, and array antenna technologies, which are 5G communication technologies. The application of cloud radio access networks (cloud RAN), which are the aforementioned big data processing technologies, can also be seen as an example of the integration of 5G and IoT technologies.

[0063] With the development of wireless communication systems as described above, various services can be provided, thus requiring methods for smoothly delivering these services.

[0064] [NR Time and Frequency Resources]

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

[0066] It should be understood that the boxes in each flowchart and the combination of flowcharts can be executed by one or more computer programs including instructions. The entirety of the one or more computer programs can be stored in a single memory device, or the one or more computer programs can be divided into different parts and stored in different multiple memory devices.

[0067] Any function or operation described herein may be processed by a processor or a combination of processors. The processor or combination of processors is a circuit that performs the processing and includes circuits such as: application processors (APs, e.g., central processing units (CPUs)), communication processors (CPs, e.g., modems), graphics processing units (GPUs), neural processing units (NPUs) (e.g., artificial intelligence (AI) chips), Wi-Fi chips, Bluetooth chips, global positioning system (GPS) chips, near field communication (NFC) chips, connectivity chips, sensor controllers, touch controllers, fingerprint sensor controllers, display driver integrated circuits (ICs), audio CODEC chips, universal serial bus (USB) controllers, camera controllers, image processing ICs, microprocessor units (MPUs), system-on-a-chip (SoCs), integrated circuits (ICs), etc.

[0068] Figure 1 The basic structure of the time-frequency domain in a 5G system according to an embodiment of the present disclosure is shown. The time-frequency domain is a radio resource domain used for transmitting data or control channels.

[0069] refer to Figure 1 In subframe 110, 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 on the time axis and a subcarrier 103 on the frequency axis. In the frequency domain, (For example, 12) consecutive REs can form a resource block (RB) 104.

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

[0071] refer to 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 10 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 μ for 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 per subframe... The number of time slots per frame can vary depending on the subcarrier spacing configuration value μ. They can be different accordingly. and The µ configuration can be defined based on the subcarrier spacing in Table 1 below.

[0072] Table 1

[0073] [Bandwidth Component (BWP)]

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

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

[0076] refer to Figure 3 The following example illustrates this: 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 can configure multiple pieces of information as shown in Table 2 below for each bandwidth portion.

[0077] Table 2

[0078] Of course, the above examples are not limiting, and various parameters related to bandwidth portions can be configured for the UE in addition to the configuration information given above. The base station can transmit configuration information to the UE via higher-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 semi-statically transmitted from the base station to the UE via RRC signaling, or dynamically transmitted from the base station to the UE via downlink control information (DCI).

[0079] According to an embodiment, 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 about the Control Resource Set (CORESET) and Search Space via the MIB during the initial access step. The CORESET and Search Space can be used to transmit a PDCCH, which is used to receive system information necessary for initial access (which may correspond to Residual System Information (RMSI) or System Information Block 1 (SIB1)). Each of the CORESET and Search Space configured via the MIB can be considered as ID 0. The base station can notify the UE of configuration information about the 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 about the monitoring period and monitoring timing of the Control Resource Set #0 via the MIB, i.e., configuration information about the Search Space #0. The UE can consider the frequency domain configured by the 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.

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

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

[0082] 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 subcarrier spacings of 15kHz and 30kHz, respectively. Different bandwidth portions can be frequency-division multiplexed (FDM), and the bandwidth portion configured for the corresponding subcarrier spacing can be activated if data is transmitted / received at a specific subcarrier spacing.

[0083] Furthermore, according to some embodiments, the base station can configure bandwidth portions with different bandwidth sizes for the UE to reduce the power consumed by the UE. For example, if the UE supports a fairly large bandwidth (e.g., 100MHz) and always transmits / receives data using the corresponding bandwidth, a considerable amount of power consumption may occur. In particular, from a power consumption perspective, unnecessarily monitoring the downlink control channel with a large bandwidth of 100MHz in the absence of service may be quite inefficient. To reduce the power consumed by the UE, the base station can configure a relatively small bandwidth portion (e.g., a bandwidth portion of 20MHz) for the UE. In the absence of service, the UE can perform monitoring operations in the 20MHz bandwidth portion, and if data is received, it can transmit / receive data using the 100MHz bandwidth portion as instructed by the base station.

[0084] Regarding the bandwidth configuration method, before RRC connection, the UE can receive configuration information about the initial bandwidth portion via the MIB during the initial access step. More specifically, the UE can have a control resource set (CORESET) configured from the MIB of the Physical Broadcast Channel (PBCH) for the downlink control channel, which can be used to transmit downlink control information (DCI) for scheduling System Information Blocks (SIBs). The bandwidth of the control resource set configured via the MIB can be considered 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 SIB is transmitted. The initial bandwidth portion can be used not only for receiving SIBs but also for other System Information (OSI), paging, random access, etc.

[0085] [Bandwidth Component (BWP) Change]

[0086] 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. As an 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 use the bandwidth portion indicator in the DCI to indicate the bandwidth portion #2 302, and the UE can change the bandwidth portion to the bandwidth portion #2 302 indicated by the bandwidth portion indicator in the received DCI.

[0087] As described above, bandwidth portion changes based on DCI can be indicated by the DCI used to schedule PDSCH or PUSCH, and 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 without problems within the changed bandwidth portion. For this purpose, the required delay time (T) during the bandwidth portion change...BWP The requirements are specified in the standard and can be defined, for example, as shown in Table 3 below.

[0088] Table 3

[0089] Depending on the UE's capabilities, the requirement for bandwidth portion change delay time supports either Type 1 or Type 2. The UE can report the supported bandwidth portion change delay time type to the base station.

[0090] If the UE has already received the DCI including the 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 point, and data channels scheduled by the corresponding DCI can be transmitted / received in the newly changed bandwidth portion. According to an embodiment, if the base station wants to schedule data channels using the new bandwidth portion, the base station can change the delay time (T) based on the UE's bandwidth portion. BWP This is used to determine the time-domain resource allocation for the data channel. In other words, when scheduling a data channel using a new bandwidth portion, the base station can schedule the corresponding data channel after the bandwidth portion change delay time, in conjunction with the method used to determine the time-domain resource allocation for the data channel. 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.

[0091] 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 during 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 preceding slot n+K (e.g., the last symbol of slot n+K-1).

[0092] [SS / PBCH block]

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

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

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

[0096] -SSS: Serves as a reference for downlink time / frequency synchronization and provides residual cell ID information not provided by PSS. Additionally, SSS can be used as a reference signal for PBCH demodulation.

[0097] -PBCH: Provides mandatory system information necessary for 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.

[0098] -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 5 ms time period, and each sent SS / PBCH block can be distinguished by an index.

[0099] The UE can detect the PSS and SSS and decode the PBCH during the initial access phase. The UE can obtain the MIB from the PBCH, and this can be used to configure the control resource set (CORESET) #0 (which may correspond to a control resource set with a control resource set index of 0). The UE can monitor the control resource set #0 by assuming that the demodulation reference signal (DMRS) transmitted in the selected SS / PBCH block and control resource set #0 is quasi-co-located (QCLed). The UE can use the downlink control information transmitted in control resource set #0 to receive system information. The UE can obtain configuration information related to the random access channel (RACH) required for initial access from the received system information. The UE can consider the selected SS / PBCH index when transmitting the physical RACH (PRACH) to the base station, and the base station can obtain information about the SS / PBCH block index selected by the UE upon receiving the PRACH. The base station can know which block the UE has selected from each SS / PBCH block and can know that the associated control resource set #0 is being monitored.

[0100] [PDCCH: About DCI]

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

[0102] 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. For either PUSCH or PDSCH, the UE can monitor both the fallback DCI format and the non-fallback DCI format. The fallback DCI format may include predefined fixed fields between the base station and the UE, while the non-fallback DCI format may include configurable fields.

[0103] The DCI message can undergo channel coding and modulation, and then be transmitted via the Physical Downlink Control Channel (PDCCH) after the channel coding and modulation process. Cyclic Redundancy Check (CRC) can be appended to the payload of the DCI message, 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 (e.g., UE-specific data transmission, power control command, or random access response). That is, the RNTI may not be explicitly sent, but can be sent during the CRC calculation process. Upon receiving a DCI message transmitted via the PDCCH, the UE can identify the CRC using the assigned RNTI, and if the CRC identification result is correct, the UE knows that the corresponding message has been sent.

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

[0105] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, and in this case, CRC can be scrambled by C-RNTI. For example, DCI format 0_0 where CRC is scrambled by C-RNTI can include the following information.

[0106] Table 4

[0107] DCI format 0_1 ​​can be used as a non-back-off DCI for scheduling PUSCH, and in this case, CRC can be scrambled by C-RNTI. For example, DCI format 0_1 ​​where CRC is scrambled by C-RNTI can include the following information.

[0108] Table 5

[0109] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, and in this case, CRC can be scrambled by C-RNTI. For example, DCI format 1_0 where CRC is scrambled by C-RNTI can include the following information.

[0110] Table 6

[0111] DCI format 1_1 can be used as a non-back-off DCI for scheduling PDSCH, and in this case, CRC can be scrambled by C-RNTI. For example, DCI format 1_1 where CRC is scrambled by C-RNTI can include the following information.

[0112] Table 7

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

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

[0115] Figure 4 An example of a control resource set (CORESET) for transmitting a downlink control channel in a 5G wireless communication system according to an embodiment of the present disclosure is shown.

[0116] refer to Figure 4 The following example is shown: where the UE bandwidth portion 410 is configured along the frequency axis, and two CORESETs (CORESET #1 401 and CORESET #2 402) are configured within a time slot 420 along the time axis. Control resource sets 401 and 402 can be configured within a specific frequency resource 410 within the entire UE bandwidth portion 403 along the frequency axis. Control resource sets 401 and 402 can each be configured as one or more OFDM symbols along the time domain, and the number of OFDM symbols can be defined as the control resource set duration 404. Reference Figure 4In the example shown, control resource set #1 401 is configured to have a control resource set duration corresponding to two symbols, and control resource set #2 402 is configured to have a control resource set duration corresponding to one symbol.

[0117] The base station can configure the control resource set in 5G as described above for the UE via higher-layer signaling (e.g., system information, master information block (MIB), radio resource control (RRC) signaling). Configuring the control resource set for the UE means providing information such as the control resource set identifier, the frequency location of the control resource set, and the symbol duration of the control resource set. For example, the control resource set may include several pieces of information, as given in Table 8 below.

[0118] Table 8

[0119] In Table 9, the tci-StatesPDCCH (Transmission Configuration Indication (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.

[0120] Figure 5 The structure of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown. Figure 5 An example of the basic unit constituting the time and frequency resources of the downlink control channel available in a 5G system is shown.

[0121] refer to 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 axis and a physical resource block (PRB) 502 (i.e., 12 subcarriers) along the frequency axis. The base station can configure the downlink control channel allocation unit by cascading REG 503.

[0122] Assuming the basic unit of downlink control channel allocation in 5G is as follows: Figure 5 The Control Channel Unit (CCE) 504 shown herein may include multiple REG 503s. For the purpose of description Figure 5The 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 particular downlink control channel may be mapped to one or more CCE 504s according to the aggregation level (AL) in the control resource set and then transmitted. CCE 504s in the control resource set are distinguished by numbering, and the numbers of CCE 504s may be assigned according to a logical mapping scheme.

[0123] Figure 5 The basic unit of the downlink control channel shown, REG 503, can include the RE to which the DCI is mapped, and the region to which the reference signal (DMRS 505) used for decoding the DCI is mapped. Figure 5 As shown, three DRMS ​​503s can be transmitted within one REG 505. 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, one downlink control channel can be transmitted with L CCEs. The UE needs to detect the signal without information about the downlink control channel, and 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 under a given AL, and since 1, 2, 4, 8, or 16 CCEs can form a bundle under different ALs, the UE can have multiple search spaces. The search space set can be defined as the set of search spaces under all configured aggregation levels.

[0124] 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 or paging messages regarding system information. 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 or similar information). In the case of a common search space, a group of UEs or all UEs need to receive the PDCCH, and the common search space can therefore be defined as a predetermined set of CCEs. Searching the UE-specific search space of the PDCCH can be used to receive scheduling allocation information regarding UE-specific PDSCHs or PUSCHs. The UE-specific search space can be defined in a UE-specific manner as a function of various system parameters and the UE's identifier.

[0125] In 5G, parameters regarding the PDCCH search space can be configured by the base station for the UE via higher-layer signaling (e.g., 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's time slots, the search space type (public 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, this may include several pieces of information.

[0126] Table 9

[0127] Based on the configuration information, the base station can configure one or more search space sets for the UE. According to an embodiment, 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 in search space set 1, and can configure DCI format B scrambled by Y-RNTI to be monitored in the UE-specific search space in search space set 2.

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

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

[0130] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, and SI-RNTI.

[0131] - DCI format 2_0 with CRC scrambled by SFI-RNTI

[0132] - DCI format 2_1 with CRC scrambled by INT-RNTI

[0133] - DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI and TPC-PUCCH-RNTI

[0134] - DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI

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

[0136] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, and TC-RNTI.

[0137] - DCI format 1_0 / 1_1 with CRC scrambled by C-RNTI, CS-RNTI, and TC-RNTI.

[0138] The listed RNTIs can follow the definitions and usages given below.

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

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

[0141] Configurable Scheduled RNTI (CS-RNTI): Used to schedule UE-specific PDSCHs with semi-static configuration.

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

[0143] Paging RNTI (P-RNTI): Used to schedule the PDSCH that sends paging requests.

[0144] System Information RNTI (SI-RNTI): Used to schedule the PDSCH that sends system information.

[0145] Interrupted RNTI (INT-RNTI): Used to indicate whether the PDSCH has been punctured.

[0146] Transmit Power Control RNTI for PUSCH (TPC-PUSCH-RNTI): Used to indicate power control commands regarding the PUSCH.

[0147] Transmit Power Control RNTI for PUCCH (TPC-PUCCH-RNTI): Used to indicate power control commands for PUCCH.

[0148] Transmit Power Control RNTI for SRS (TPC-SRS-RNTI): Used to indicate power control commands regarding the SRS.

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

[0150] Table 10

[0151] In 5G, the search space at the aggregation level L, which is related to CORESET p and the search space set s, can be represented by the following formula 1.

[0152] Formula 1

[0153] -L: Aggregation Level

[0154] - Carrier index

[0155] - : The total number of CCEs existing in the control resource set p

[0156] - Time slot index

[0157] - Number of PDCCH candidates at aggregation level L

[0158] - Candidate indexes of PDCCH under aggregation level L

[0159] -i = 0, …, L -1

[0160] -

[0161] - UE identifier

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

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

[0164] In 5G, multiple search space sets can be configured using different parameters (e.g., those in Table 9), 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 in time slot X, and search space set #2 is configured in time slot Y, and if X and Y are different, the UE can monitor search space set #1 and search space set #2 in a specific time slot, and can monitor only one of search space set #1 and search space set #2 in another specific time slot.

[0165] [PDCCH: Span]

[0166] For situations where a UE has multiple PDCCH monitoring opportunities within a time slot, the UE can perform a UE capability report in each subcarrier interval, and the concept of a "span" can be used in this regard. A span refers to the consecutive symbols configured to enable the UE to monitor the PDCCH within a time slot, with each PDCCH monitoring opportunity occurring 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 for the PDCCH. The UE can monitor the PDCCH within a span, starting from the first symbol of the span and extending for Y symbols.

[0167] Figure 6 This illustrates, from a span perspective, a scenario in a wireless communication system according to an embodiment of the present disclosure where a UE may have multiple PDCCH monitoring opportunities within a time slot.

[0168] refer to Figure 6 The span can be (X, Y) = (7,3), (4,3), or (2,2), and these three cases can be indicated by "6-00", "6-05", and "6-10" respectively. As an example, "6-00" can describe the following case: within a time slot, there are two spans described by (7,4). The interval between the first symbols of the two spans is described as X = 7, the PDCCH monitoring timing can exist within a total of Y = 3 symbols starting 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 the following case: within a time slot, there are a total of three spans described by (4,3), and the second and third spans are separated by X' = 5 symbols, which is greater than X = 4.

[0169] [PDCCH: UE Capability Report]

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

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

[0172] Table 11

[0173] -UE Capability 2 (hereinafter referred to as FG 3-2). This UE capability has the following meaning: If a monitoring opportunity (MO) exists within a time slot regarding a common search space or a UE-specific search space, as shown in Table 12 below, the UE can monitor the corresponding MO, regardless of the starting symbol position of the corresponding MO. This UE capability is optional to be supported by the UE, and whether or not the UE capability is supported is explicitly reported to the base station.

[0174] Table 12

[0175] -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 patterns of MOs that the UE can monitor. The aforementioned patterns include the interval X between the start symbols of different MOs, and the maximum symbol length Y of a MO. The UE-supported combination of (X, Y) 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 aforementioned combinations of (X, Y), are explicitly reported to the base station.

[0176] Table 13

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

[0178] [QCL, TCI Status]

[0179] In wireless communication systems, one or more different antenna ports (which can be replaced by one or more channels, signals, and combinations thereof, but for convenience, they are generally 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 declare the QCL relationship between the PDCCH (or PDCCH DRMS) and another RS ​​or channel, and the description of reference antenna port A (reference RS#A) and another target antenna port B (target RS#B) being quasi-co-located (QCLed) 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. QCL needs to be associated with different parameters based on conditions 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, as shown in Table 14 below, four types of QCL relationships are supported in NR.

[0180] Table 14

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

[0182] QCL relationships can be configured for a UE using RRC parameters TCI state (TCI-state) and QCL information (QCL-info), as shown in Table 15 below. Referring to Table 15, a base station can configure one or more TCI states for a UE to notify up to two types of QCL relationships (qc1-Type1, qc1-Type2) related to the RS (i.e., the target RS) with the ID of the reference TCI state. Each QCL information (QCL-Info) for each TCI state may include 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.

[0183] Table 15

[0184] Figure 7An 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. Figure 7 An example of base station beam allocation configured according to TCI status is shown.

[0185] refer to 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 In the case of N=3 shown, the base station can configure qcl-Type2 parameters included in the three TCI states 700, 705 and 710 in QCL type D, and these parameters are simultaneously associated with CSI-RS or SSB corresponding to different beams, thereby notifying the antenna ports involved in different TCI states 700, 705 and 710 that they are associated with different spatial Rx parameters (i.e. different beams).

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

[0187] Table 16 lists the valid TCI state configurations when the target antenna port is a CSI-RS (TRS) for tracking. A TRS is a non-zero power CSI-RS (NZP CSI-RS) in the CSI-RS that does not have the repetition parameters configured for it and whose trs-Info is configured as "true". In Table 16, configuration 3 can be used for aperiodic TRS.

[0188] Table 16 Effective TCI State Configuration When the Target Antenna Port is a CSI-RS (TRS) for Tracking

[0189] 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 that does not have a parameter (e.g., a repeat parameter) configured for it in the CRI-RS and whose trs-Info is configured as "true".

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

[0191] 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 in the CRI RS that has repeating parameters configured to have a "on" or "off" value and whose trs-Info is not configured to "true".

[0192] Table 18 Effective TCI State Configuration When the Target Antenna Port is a CSI-RS for BM (for L1 RSRP Reporting)

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

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

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

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

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

[0198] [PDCCH: Regarding TCI Status]

[0199] 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 combinations assumed by the UE before RRC configuration and which cannot be configured after RRC.

[0200] Table 21

[0201] Figure 8An 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.

[0202] refer to Figure 8 In NR, dynamic allocation of PDCCH beams is supported, such as... Figure 8 The layered signaling method is shown. (See 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 of these states as TCI states for CORESET (825). Then, the base station can indicate to the UE via MAC CE signaling (845) that one of the TCI states 830, 835, and 840 is for CORESET. The UE can then receive the PDCCH based on the beam information included in the TCI states indicated by the MAC CE signaling.

[0203] 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. Figure 9 The TCI indicator MAC CE signaling structure for PDCCH DMRS is shown.

[0204] refer to 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 CORESET ID 920, and a 7-bit TCI status ID 925.

[0205] 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. Figure 10 An example of beam configuration regarding the control resource set (CORESET) and search space as described above is shown.

[0206] refer to Figure 10The base station can indicate one of the TCI status lists included in the CORESET 1000 configuration via MAC CE signaling (1005). Before indicating different TCI states for the corresponding CORESET via different MAC CE signaling, the UE can assume that the same QCL information (beam #1) 1005 is applied to all of the search spaces 1010, 1015, and 1020 connected to the CORESET. The above-described PDCCH beam allocation method may have the problem that it is difficult to indicate beam changes faster than the MAC CE signaling delay, and that the same beam is unilaterally applied to each CORESET regardless of search space characteristics, making flexible PDCCH beam operation difficult. The following embodiments of this disclosure provide a more flexible PDCCH beam configuration and operation method. Although several different examples will be provided for the convenience of describing embodiments of this disclosure, they are not mutually exclusive and can be appropriately combined and applied for each situation.

[0207] 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} is configured as the TCI state 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 the 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 of the corresponding CORESET based on the QCL information in the activated TCI state.

[0208] For a CORESET with configuration index 0 (CORESET #0), if the UE does not receive a MAC CE activation command regarding the TCI state of CORESET #0, the UE may assume that the DMRS transmitted in CORESET #0 is quasi-co-located (QCL-ed) with the SS / PBCH block identified during the initial access procedure or during a contention-free random access procedure not triggered by a PDCCH command.

[0209] For a CORESET (CORESET #X) with a configuration index value other than 0, if the UE does not have a TCI state configured for CORESET #X, or if the UE has one or more TCI states configured for CORESET #X but has not received a MAC CE activation command to activate one or more TCI states, the UE may assume that the DMRS sent in CORESET #X is quasi-co-located (QCL-ed) with the SS / PBCH block identified during the initial access procedure.

[0210] [PDCCH: Regarding QCL Priority Rules]

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

[0212] If, during a specific PDCCH monitoring period, multiple control resource sets operating under carrier aggregation within a single cell or frequency band and existing within the active bandwidth portion of one or more cells overlap temporally, and these control resource sets have the same or different QCL-TypeD characteristics, the UE can select a specific control resource set based on the QCL priority determination operation and can monitor control resource sets with the same QCL-TypeD characteristics as the corresponding control resource set. In other words, if multiple control resource sets overlap temporally, only one QCL-TypeD characteristic can be received. QCL priority can be determined by the following criteria.

[0213] -Standard 1. A control resource set connected to a public search space, wherein the control resource set has a lowest index in the cell corresponding to the lowest index within the cell that includes the public search space.

[0214] -Standard 2. A control resource set connected to a UE-specific search space, the control resource set having a lowest index in the cell corresponding to the lowest index within the cell that includes the UE-specific search space.

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

[0216] If the 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.

[0217] Figure 12 A method is shown in which a UE in a wireless communication system according to an embodiment of the present disclosure selects a set of receivable control resources by considering priorities after receiving a downlink control channel.

[0218] refer to Figure 12 The UE can be configured to receive multiple control resource sets that overlap in time during a specific PDCCH monitoring period 1210, and these multiple control resource sets can be connected to a common search space or a UE-specific search space for multiple cells. During the corresponding PDCCH monitoring period, control resource set 1 1200 connected to common search space 1 can exist in bandwidth portion 1 1215 of cell 1, and control resource set 1 1205 connected to common search space 1 and control resource set 2 1220 connected to UE-specific search space 2 can exist in bandwidth portion 1 1225 of cell 2. Control resource sets 1215 and 1220 can have a QCL-TypeD relationship with CSI-RS resource 1 configured in bandwidth portion 1 of cell 1, and control resource set 1225 can 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 that have the same QCL-TypeD reference signal as control resource set 1 1215 can be received. Therefore, the UE can receive control resource sets 1220 and 1215 in the corresponding PDCCH monitoring time 1210.

[0219] As another example, the UE can be configured to receive multiple control resource sets that overlap in time during 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 1230 connected to UE-specific search space 1 and control resource set 2 1245 connected to UE-specific search space 2 can exist in the bandwidth portion 1 1230 of cell 1, and control resource set 1 1235 connected to UE-specific search space 1 and control resource set 2 1255 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 time 1240, but there is no common search space, then the next standard, standard 2, can be applied. If standard 2 is applied to the corresponding PDCCH monitoring time 1240, then all other control resource sets with the same QCL-TypeD reference signal as control resource set 1 1245 can be received. Therefore, the UE can receive control resource sets 1250 and 1245 in the corresponding PDCCH monitoring time 1240.

[0220] [Regarding rate matching / punching]

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

[0222] If the time and frequency resources A used to transmit symbol sequence A overlap with time and frequency resources B, rate matching or puncturing operations can be considered as operations for transmit / receive channel A that take into account resource C (the area where resources A and B overlap). Specific operations can be described below.

[0223] Rate matching operation

[0224] - The base station can transmit channel A after mapping it only to the remaining resource area of ​​the entire resource A (which will be used to transmit symbol sequence A to the UE), excluding resource C (the area overlapping with resource B). For example, if symbol sequence A is configured as {symbol #1, symbol #2, symbol #3, symbol #4}, if resource A is {resource #1, resource #2, resource #3, resource #4}, and if resource B is {resource #3, resource #5}, then the UE can receive symbol sequence A based on the assumption that symbol sequence A has been successively mapped to the remaining resources {resource #1, resource #2, resource #4} in resource A, excluding {resource #3} (corresponding to resource C). Therefore, the base station can transmit symbol sequence {symbol #1, symbol #2, symbol #3} after mapping symbol sequence {symbol #1, symbol #2, symbol #3} to {resource #1, resource #2, resource #4} respectively.

[0225] The UE can evaluate resources A and B, and thus evaluate resource C (the overlapping area of ​​resources A and B), based on scheduling information about symbol sequence A from the base station. The UE can receive symbol sequence A based on the assumption that it has already been mapped and transmitted in the remaining area of ​​resource A, excluding resource C. For example, if symbol sequence A is configured as {symbol #1, symbol #2, symbol #3, symbol #4}, if resource A is {resource #1, resource #2, resource #3, resource #4}, and if resource B is {resource #3, resource #5}, then the UE can receive symbol sequence A based on the assumption that it has been continuously mapped to the remaining resources {resource #1, resource #2, resource #4} in resource A, excluding {resource #3} (corresponding to resource C). Therefore, the UE can perform a series of subsequent reception operations based on the assumption that symbol sequence {symbol #1, symbol #2, symbol #4} is transmitted after being mapped to {resource #1, resource #2, resource #4}, respectively.

[0226] Drilling operation

[0227] If there is a resource C (an area overlapping with resource B) in the entire resource A used to transmit symbol sequence A to the UE, the base station can map symbol sequence A to the entire resource A, but can not perform transmission in the resource area corresponding to resource C, and can only perform transmission for the remaining resource area in resource A other than resource C. For example, if symbol sequence A is configured as {symbol #1, symbol #2, symbol #3, symbol #4}, if resource A is {resource #1, resource #2, resource #3, resource #4}, and if resource B is {resource #3, resource #5}, then 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, but {symbol #3} mapped to {resource #3} (corresponding to resource C) is not sent, and based on the assumption that the symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to the remaining resources {resource #1, resource #2, resource #4} in resource A other than {resource #3} (corresponding to resource C) has been mapped and sent, the UE can receive the symbol sequence. Therefore, the base station can send the symbol sequence {symbol #1, symbol #2, symbol #4} after mapping the symbol sequence {symbol #1, symbol #2, symbol #4} to {resource #1, resource #2, resource #4} respectively.

[0228] The UE can evaluate resources A and B based on scheduling information about symbol sequence A from the base station, and thus evaluate resource C (the area where resources A and B overlap). The UE can receive symbol sequence A based on the assumption that symbol sequence A has been mapped to the entire resource A, but is only transmitted in the remaining area of ​​resource A excluding resource C. For example, if symbol sequence A is configured as {symbol #1, symbol #2, symbol #3, symbol #4}, if resource A is {resource #1, resource #2, resource #3, resource #4}, and if resource B is {resource #3, resource #5}, then 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, but {symbol #3} mapped to {resource #3} (corresponding to resource C) is not sent, and based on the assumption that the symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to the remaining resources {resource #1, resource #2, resource #4} in resource A other than {resource #3} (corresponding to resource C) has been mapped and sent, the UE can receive the symbol sequence. Therefore, the UE can perform a series of subsequent reception operations based on the following assumption: the symbol sequence {symbol #1, symbol #2, symbol #4} is sent after being mapped to {resource #1, resource #2, resource #4} respectively.

[0229] The following describes a method for configuring rate matching resources in a 5G communication system to perform rate matching. Rate matching refers to adjusting the signal size by taking into account the amount of resources available for signal transmission. For example, data channel rate matching may mean that for a specific time and frequency resource domain, the data channel is not mapped and transmitted, and the data size is adjusted accordingly.

[0230] Figure 11 A method is shown for a base station and a UE in a wireless communication system according to embodiments of the present disclosure to transmit / receive data, taking into account downlink data channels and rate matching resources.

[0231] refer to Figure 11 The 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 periodic information 1105. In the following text, the bitmap corresponding to the frequency-domain resource allocation information 1104 is referred to as the "first bitmap," the bitmap corresponding to the time-domain resource allocation information 1103 is referred to as the "second bitmap," and the bitmap corresponding to the periodic information 1105 is referred to as the "third bitmap." If all or part 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 the PDSCH 1101 on a portion of the rate matching resources 1102 and transmit the PDSCH 1101, and the UE can perform reception and decoding after assuming that the PDSCH 1101 has already been rate matched in a portion of the rate matching resources 1102.

[0232] The base station can dynamically notify the UE via DCI whether to perform rate matching on the PDSCH in the configured rate matching resource portion through additional configuration (e.g., corresponding to the "rate matching indicator" in the DCI format described above). Specifically, the base station can select some rate matching resources from the configured rate matching resources and group them into rate matching resource groups. It can also indicate to the UE via DCI using a bitmap type whether to perform rate matching on the PDSCH for each rate matching resource group. For example, if four rate matching resources RMR#1, RMR#2, RMR#3, and RMR#4 are configured, the base station can configure rate matching groups RMG#1={RMR#1, RMR#2} and RMG#2={RMR#3, RMR#4}. It can also indicate to the UE via a bitmap using two bits in the DCI field whether rate matching occurs in RMG#1 and RMG#2 respectively. For example, the base station can use "1" to indicate that rate matching is to be performed, and "0" to indicate that rate matching is not to be performed.

[0233] 5G supports "RB symbol level" and "RE level" granularity as methods for configuring the aforementioned rate matching resources for the UE. Specifically, the following configuration methods can be followed.

[0234] RB symbol level

[0235] Through higher-layer signaling, a UE can have up to four RateMatchPatterns configured for each bandwidth segment, and a RateMatchPattern can include the following information.

[0236] - Regarding reserved resources within the bandwidth portion, this may include resources with corresponding time and frequency resource domains, configured in the frequency domain as a combination of RB-level and symbol-level bitmaps. These reserved resources may span one or two time slots. An additional time-domain pattern (periodicityAndPattern) can be configured, which includes the repetition of the time-frequency domain for the corresponding RB-level and symbol-level bitmap pairs.

[0237] - This may include a resource region corresponding to the time domain mode, which is configured by the CORESET within the bandwidth portion and the time and frequency domain resource regions configured by the corresponding resource regions being repeatedly searched in the search space.

[0238] RE Level

[0239] The UE can have the following features configured via higher-layer signaling.

[0240] - Configuration information for the RE corresponding to the LTE CRS (Cell-Specific Reference Signal or Common Reference Signal) mode (lte-CRS-ToMatchAround) may include the number of LTE CRS ports (nrofCRS-Ports), the LTE-CRS-vshift value (v-shift), the center subcarrier position information 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. Based on the above information, the UE can determine the location of the CRS within the NR slot corresponding to the LTE subframe.

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

[0242] [Regarding LTE CRS rate matching]

[0243] 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 ServingCellConfig IE (information element) or ServingCellConfigCommon IE. Examples of these parameters include lte-CRS-ToMatchAround, lte-CRS-PatternList1-r16, lte-CRS-PatternList2-r16, crs-RateMatch-PerCORESETPoolIndex-r16, etc.

[0244] Rel-15 NR provided a feature where a CRS pattern could be configured for each serving cell via the parameter lte-CRS-ToMatchAround. In Rel-16 NR, this feature was extended to allow multiple CRS patterns to be configured for each serving cell. More specifically, a UE with a single TRP (Transmit and Receive Point) configuration can now have one CRS pattern configured for one LTE carrier, and a UE with a multi-TRP configuration can now have two CRS patterns configured for one LTE carrier. For example, a UE with a single TRP configuration can have up to three CRS patterns configured for each serving cell via the parameter lte-CRS-PatternList1-r16. As another example, a UE with a multi-TRP configuration can have a CRS configured 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", the CRS mode for only one TRP is applied; otherwise, the CRS modes for both TRPs are applied.

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

[0246] Table 22

[0247] Table 23

[0248] [PDSCH: Processing Time]

[0249] Next, the PDSCH processing time (PDSCH processing procedure time) will be described. If the base station schedules the UE to send PDSCH 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 PUSCH preparation procedure time is defined in NR. The UE's PUSCH processing time can follow Equation 2 given below.

[0250] Formula 2

[0251] The T described in Formula 3 above proc，1 Each parameter in the formula can have the following meanings.

[0252] -N1: The number of symbols determined based on UE processing capability 1 or 2 (based on UE capability) and parameter set μ. If UE processing capability 1 is reported based on the UE capability report, then N1 can have the values ​​in Table 24-1; if UE processing capability 2 is reported, and the availability of UE processing capability 2 is configured via higher-layer signaling, then N1 can have the values ​​in Table 24-2. 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 that will send HARQ-ACK.

[0253] Table 24-1 PDSCH processing time under PDSCH processing capacity 1

[0254] Table 24-2 PDSCH processing time with PDSCH processing capacity 2

[0255] -κ:64

[0256] -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, T ext It is assumed to be 0.

[0257] - If l1, representing the PDSCH DMRS position value, is 12, then N in Table 22 above 1，0 It has a value of 14, otherwise it has a value of 13.

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

[0259] -d2: If a PUCCH with a high-priority index overlaps in time with another PUCCH or 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.

[0260] -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 schedules the PDSCH and the scheduled PDSCH, as described below.

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

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

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

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

[0265] -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 schedules the PDSCH and the scheduled PDSCH, as described below.

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

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

[0268] -If L = 2, - If the scheduled PDCCH exists within a CORESET containing three symbols, and if the CORESET and the scheduled PDSCH have the same starting symbol, then d 1，1 = 3.

[0269] -Otherwise, d 1，1 = d.

[0270] - When a UE with capability 2 is in a given serving cell, if processingType2Enabled (higher-layer signaling) is configured to "enable" for the corresponding cell, the UE can apply PDSCH processing time based on UE processing capability 2.

[0271] If the position of the first uplink transmission symbol of the PUCCH containing HARQ-ACK information (regarding the corresponding position, one can consider: K1 being defined as the HARQ-ACK transmission time point, the PUCCH resources used to send the HARQ-ACK, and the impact of timing advance) is not earlier than the last symbol of the PDSCH after T proc，1 The UE needs to send a valid HARQ-ACK message at the start of the first uplink transmission symbol after the scheduled time. In other words, the UE only needs to send a PUCCH including HARQ-ACK if there is sufficient time for PDSCH processing. Otherwise, the UE cannot provide the base station with valid HARQ-ACK information corresponding to the scheduled PDSCH. proc，1 This can be used under normal or extended CP conditions. 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 .

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

[0273] Next, in the case of cross-carrier scheduling (where the parameter set (μPDCCH) for transmitting the scheduled PDCCH is different from the parameter set (μPDSCH) for transmitting the PDSCH scheduled by the corresponding PDCCH), the UE's PDSCH reception preparation time (N) defined for the time interval between the PDCCH and PDSCH will be described. pdsch ).

[0274] If μPDCCH < μPDSCH, then the scheduled PDSCH cannot be transmitted before the first symbol of the time slot arriving after Npdsch symbols following the last symbol of the PDCCH that scheduled the corresponding PDSCH. The transmission symbols of the corresponding PDSCH may include DM-RS.

[0275] If μPDCCH > μPDSCH, then the scheduled PDSCH can be transmitted Npdsch symbols after the last symbol of the PDCCH that scheduled the corresponding PDSCH. The transmission symbols of the corresponding PDSCH may include DM-RS.

[0276] Table 25 Npdsch based on the scheduled PDCCH subcarrier spacing

[0277] [About SRS]

[0278] Next, a method for uplink channel estimation using the UE's Sounding Reference Signal (SRS) transmission 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. As an example, the base station and the UE can exchange the following higher-layer signaling information to transmit information about the SRS resource set.

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

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

[0281] -resourceType: The time-domain transport 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 use case of the SRS resource set. 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 use case of the SRS resource set.

[0282] -usage: Configuration related to the use case of the SRS resources referenced by the SRS resource set, and can be configured as one of "beam management", "codebook", "noncodebook" and "antenna switching".

[0283] -alpha, p0, pathlossReferenceRS, srs-PowerControlAdjustmentStates provide parameter configurations for adjusting the transmission power of SRS resources referenced by the SRS resource set.

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

[0285] In addition, the base station and UE can send / receive higher-layer signaling information to transmit various configuration information regarding SRS resources. As an example, the various configuration information regarding SRS resources may include time-frequency domain mapping information within the time slots of the SRS resource, and may include information regarding intra- or inter-time slot frequency hopping of the SRS resource. The various configuration information regarding SRS resources may include the time-domain transmission configuration of the SRS resource, and may be configured as "periodic," "semi-persistent," and "aperiodic." The time-domain transmission configuration of the SRS resource may be restricted to having the same time-domain transmission configuration as the set of SRS resources that includes the SRS resource. If the time-domain transmission configuration of the SRS resource is configured as "periodic" or "semi-persistent," the time-domain transmission configuration may also include the SRS resource transmission period and time slot offset (e.g., periodicityAndOffset).

[0286] The base station can activate or deactivate the UE's SRS transmission via higher-layer signaling or L1 signaling (e.g., DCI), including RRC signaling or MAC CE signaling. 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 the SRS resources referenced by 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 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 associated 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.

[0287] 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 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 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 associated CSI-RS information configured for the SRS resource set including the SRS resources. If the SRS resources have spatial relation information configured for them, the spatial transmission filter can be determined by referring to configuration information related to the spatial relation information transmitted via MAC CE signaling to activate the semi-persistent SRS transmission, without adhering to that spatial relation information. The UE can transmit SRS resources within the uplink BWP activated for semi-persistent SRS resources activated via higher-layer signaling.

[0288] For example, a base station can trigger aperiodic SRS transmissions by a UE via a DCI. The base station can indicate one of the aperiodic SRS triggers (aperiodicSRS-ResourceTrigger) through the SRS request field of the DCI. The UE understands that the SRS resource set, including the aperiodic SRS resource trigger list indicated by the DCI, has been triggered in the SRS resource set configuration information. The UE can then transmit the SRS resources 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, and this time slot offset can refer to a value included in the time slot offset set configured for the SRS resource set. Specifically, the time slot offset between the SRS resource and the PDCCH including the DCI can be the value indicated in the time domain resource allocation field of the DCI from the offset values ​​included in the time slot offset set configured for the SRS resource set. Furthermore, the spatial 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 associated 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.

[0289] If the base station triggers aperiodic SRS transmissions by the UE via DCI, a minimum time interval may be required between the transmitted SRS and the PDCCH containing the DCI that triggers the aperiodic SRS transmission, allowing the UE to transmit SRS by applying configuration information about the SRS resources. The time interval for the UE to perform SRS transmissions can be defined as the number of symbols between the last symbol of the PDCCH containing the DCI that triggers the aperiodic SRS transmission and the first symbol of the first transmitted SRS resource mapped to the first transmitted SRS resource. The minimum time interval can be determined with reference to the PUSCH preparation time required for the UE to prepare for PUSCH transmission. The minimum time interval can have different values ​​depending on the use case of the SRS resource set including the transmitted SRS resources. For example, the minimum time interval can be determined as N² symbols, taking into account the UE's processing capacity, which follows the UE's PUSCH preparation time. Furthermore, considering the use case of the SRS resource set including the transmitted SRS resources, if the use case of the SRS resource set is configured as "codebook" or "antennaSwitching", the minimum time interval can be determined to be N² symbols. If the use case of the SRS resource set 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.

[0290] Table 26

[0291] The configuration information spatialRelationInfo in Table 26 above can refer to a reference signal applied to the beam used for SRS transmission corresponding to the beam information of the corresponding reference signal. For example, the configuration of spatialRelationInfo can include the information in Table 27 below.

[0292] Table 27

[0293] Referring to the spatialRelationInfo configuration above, the SS / PBCH block index, CSI-RS-INDEX, or SRS index can be configured as the index of a reference signal to be referenced, using the beam information of a specific reference signal. The higher-layer signaling referenceSignal corresponds to configuration information indicating which reference signal's beam information will be referenced for 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 "ssb-Index", the UE can use the receive beam used to receive the SS / PBCH block corresponding to ssb-Index as the transmit beam used for the corresponding SRS transmission.

[0294] [PUSCH: Regarding the transmission scheme]

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

[0296] Configuration grant type 1 PUSCH transmissions can be semi-statically configured via receiving a configuredGrantConfig including rrc-ConfiguredUplinkGrant from Table 28 through higher-layer signaling, without receiving UL grants within the DCI. Configuration grant type 2 PUSCH transmissions can be semi-persistently scheduled via UL grants within the DCI after receiving a configuredGrantConfig excluding rrc-ConfiguredUplinkGrant from Table 28 through higher-layer signaling. If the PUSCH transmission operates with configuration grants, the parameters applied to the PUSCH transmission are applied via configuredGrantConfig (higher-layer signaling) from Table 28, except for dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and UCI-OnPUSCH scaling (these parameters are provided by pusch-Config in Table 29). If transformPrecoder is provided within configuredGrantConfig (higher-layer signaling) from Table 28, the UE applies tp-pi2BPSK from pusch-Config in Table 29 to PUSCH transmissions operating with configuration grants.

[0297] Table 28

[0298] 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. Depending on whether the value of txConfig in pusch-Config (which is higher-layer signaling) in Table 29 is "codebook" or "non-codebook", PUSCH transmission can follow either a codebook-based transmission method or a non-codebook-based transmission method.

[0299] As described above, PUSCH transmissions can be dynamically scheduled via DCI format 0_0 or 0_1, and can be semi-statically configured via configuration 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 in the active uplink BWP within the UE serving cell, and PUSCH transmission is based on a single antenna port. The UE does not expect PUSCH transmission scheduling via DCI format 0_0 in a BWP that does not have a configured PUCCH resource including pucch-spatialRelationInfo. If the UE does not have a configured txConfig in the pusch-Config in Table 29, the UE does not expect scheduling via DCI format 0_1.

[0300] Table 29

[0301] The codebook-based PUSCH transport will be described below. Codebook-based PUSCH transport can be dynamically scheduled using DCI format 0_0 or 0_1, and can be operated semi-statically using configuration grants. If codebook-based PUSCH is dynamically scheduled using DCI format 0_1 ​​or semi-statically configured using configuration grants, the UE determines the precoder used for PUSCH transport based on the SRS Resource Indicator (SRI), the Transport Precoding Matrix Indicator (TPMI), and the transport rank (the number of PUSCH transport layers).

[0302] The SRI can be given via the SRS Resource Indicator (a field within the DCI) or configured via the srs-ResourceIndicator (higher-layer signaling). During codebook-based PUSCH transmission, the UE has at least one SRS resource configured for PUSCH transmission and can have up to two SRS resources configured for PUSCH transmission. 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 corresponding SRI. Furthermore, the TPMI and transport rank can be given via the Precoding Information and Number of Layers (a field within the DCI) or configured via precodingAndNumberOfLayers (higher-layer signaling). The TPMI is used to indicate the precoder to be applied to the PUSCH transmission. If one SRS resource is configured for the UE, the TPMI can be used to indicate the precoder to be applied to the configured SRS resource. If multiple SRS resources are configured for the UE, the TPMI is used to indicate the precoder to be applied to the SRS resource indicated by the SRI.

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

[0304] A UE can have an SRS resource set configured for it, where the usage value in the SRS-ResourceSet (higher-layer signaling) is a "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 (where the usage value in the SRS-ResourceSet (higher-layer signaling) is a "codebook"), the UE expects the value of nrofSRS-Ports in the SRS-Resource (higher-layer signaling) to be the same for all SRS resources.

[0305] The UE sends one or more SRS resources from an SRS resource set (where the usage value is configured as a "codebook" according to higher-layer signaling) to the base station. The base station selects one SRS resource from those sent by the UE and instructs the UE to use the transmit beam information of the corresponding SRS resource to transmit PUSCH. Regarding codebook-based PUSCH transmission, the SRI is used as an index for selecting an SRS resource and is included in the DCI. Additionally, the base station adds rank sum TPMI information to the DCI, indicating the rank sum to be used by the UE for PUSCH transmission. Using the SRS resource indicated by the SRI, the UE applies a precoder indicated by the rank sum TPMI (which is based on the transmit beam of the corresponding SRS resource) when performing PUSCH transmission, thereby performing the PUSCH transmission.

[0306] Next, non-codebook-based PUSCH transmissions will be described. Non-codebook-based PUSCH transmissions can be dynamically scheduled using DCI format 0_0 or 0_1, and can be operated semi-statically through configuration authorization. If at least one SRS resource is configured within the SRS resource set (where the value of the purpose within the SRS-ResourceSet (higher-layer signaling) is "codebook"), non-codebook-based PUSCH transmissions can be scheduled for the UE using DCI format 0_1.

[0307] For SRS resource sets whose purpose value within the SRS-ResourceSet (higher-layer signaling) is "non-codebook," 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 information related to the precoder for SRS transmission to be updated.

[0308] If the configuration value of resourceType in the SRS-ResourceSet (higher-layer signaling) is "aperiodic," 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, the presence of a connected NZP CSI-RS is indicated for the SRS request (a field within DCI format 0_1 ​​or 1_1) value not being "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, 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.

[0309] If a configured periodic or semi-persistent SRS resource set exists, the associated CSI-RS within the SRS-ResourceSet (higher-layer signaling) can indicate the connected NZP CSI-RS. For non-codebook-based transmissions, the UE does not expect spatialRelationInfo (which is higher-layer signaling about SRS resources) to be configured together with the associated CSI-RS within the SRS-ResourceSet (higher-layer signaling).

[0310] If multiple SRS resources are configured for the UE, the UE can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. The SRI can be indicated by an SRS resource indicator (a field within the DCI) or configured via the srs-ResourceIndicator (higher-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 those transmitted before the PDCCH including the corresponding 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 to the base station by the UE. SRS resources transmitted simultaneously by the UE occupy the same RB. The UE configures one SRS port for each SRS resource. There can be only one configured SRS resource set in which the value of the purpose within the SRS-ResourceSet (higher-layer signaling) is "non-codebook", and up to four SRS resources can be configured for non-codebook-based PUSCH transports.

[0311] The base station sends an NZP-CSI-RS connected to the SRS resource set to the UE. Based on measurements received upon receiving the corresponding NZP-CSI-RS, the UE calculates the precoder to be used when transmitting one or more SRS resources within the corresponding SRS resource set. The UE applies the calculated precoder when transmitting one or more SRS resources within the SRS resource set (where the configured purpose is "non-codebook") to the base station, and the base station selects one or more SRS resources from the received one or more SRS resources. Regarding non-codebook-based PUSCH transmission, the SRI indicator can represent an index of one SRS resource or a combination of multiple SRS resources, and the SRI is included in the DCI. The number of SRS resources indicated by the SRI transmitted by the base station can be the number of transport layers of the PUSCH, and the UE transmits the PUSCH by applying the precoder used for SRS resource transmission to each layer.

[0312] [PUSCH: Preparation time]

[0313] Next, the PDSCH processing time (PDSCH process time) will be described. If the base station schedules the UE to send PUSCH using DCI format 0_0, 0_1, or 0_2, the UE may require a PUSCH preparation process time to send the PUSCH by applying the transmission method indicated by the DCI (SRS resource transmission precoding method, number of transport 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 follow the formula given below (Formula 3).

[0314]

[0315] …Formula 3

[0316] The T described above in Formula 3 proc,2 Each parameter in the expression can have the following meaning.

[0317] -N2: 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 according to the UE's capability report, then N2 can have the value in Table 40, and if UE processing capability 2 is reported, and if the availability of UE processing capability 2 is configured via higher-layer signaling, then N2 can have the value in Table 41.

[0318] Table 30

[0319] Table 31

[0320] -d 2,1 The number of symbols is determined to be 0 if all resource elements of the first OFDM symbol transmitted by PUSCH include DM-RS; otherwise, it is determined to be 1.

[0321] -κ: 64.

[0322] -μ: Follow μ DL and μ UL In the middle, T proc,2 A larger value. μ DL This refers to the set of parameters used to send the downlink PDCCH, which includes the DCI scheduling PUSCH, and μ UL This refers to the set of parameters used for sending PUSCH in the uplink.

[0323] -T c :have

[0324] -d 2,2 If the DCI of the scheduling PUSCH indicates a BWP handover, then d 2,2 Follow the BWP switchover time, otherwise d 2,2 It is 0.

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

[0326] -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, T ext It is assumed to be 0.

[0327] -T switch If the uplink handover interval has been triggered, then T switch It is assumed to be the switching interval time. Otherwise, T switch It is assumed to be 0.

[0328] - Considering the impact of timing advance between the uplink and downlink, and the time-domain resource mapping information of the PUSCH scheduled by the DCI, if the first symbol of the PUSCH is earlier than the first uplink symbol (in the first uplink symbol, the CP passes through T from the last symbol of the PDCCH of the DCI that schedules the PUSCH), proc,2If the PUSCH preparation process begins earlier (after the initial PUSCH preparation), the base station and UE 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 scheduling the PUSCH if the PUSCH preparation time is insufficient.

[0329] [PUSCH: Regarding duplicate transfers]

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

[0331] PUSCH repeat type A transmission

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

[0333] Based on the number of repeated transmissions received from the base station, the UE may repeatedly transmit 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 of the symbols of the uplink data channel configured for the UE is configured as downlink, the UE omits uplink data channel transmission, but counts the number of repeated transmissions of the uplink data channel.

[0334] PUSCH repeat type B transmission

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

[0336] Based on the previously configured start symbol and the length of the uplink data channel, the nominal repetition of the uplink data channel is determined as follows. The time slot at which the nth nominal repetition begins is determined by... The symbol given, and the one that begins in that time slot, is... 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 is the start symbol of the configured uplink data channel, and L is the symbol length of the configured uplink data channel. This refers to the time slot at which the PUSCH transmission begins, and This refers to the number of symbols in each time slot.

[0337] The UE determines invalid symbols for PUSCH repetition type B transmission. Symbols configured for downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated can be determined as invalid symbols for PUSCH repetition type B transmission. Alternatively, invalid symbols can be configured in higher-layer parameters (e.g., InvalidSymbolPattern). This higher-layer parameter (e.g., InvalidSymbolPattern) can provide a symbol-level bitmap across one or two time slots to configure invalid symbols. In the bitmap, 1 represents an invalid symbol. Furthermore, the period and mode of the bitmap can be configured via 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 mode; if the aforementioned parameter indicates 0, the UE does not apply the invalid symbol mode. 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.

[0338] After identifying invalid symbols, for each nominal repeat, the UE can treat all symbols except the invalid ones as valid 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 includes a set of consecutive valid symbols in a time slot that can be used for PUSCH repeat transmission type B.

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

[0340] refer to Figure 14 The UE can receive the following configuration: the start symbol S of the uplink data channel is 0, the length L of the uplink data channel is 14, and the number of repetitions is 16. In this case, nominal repetitions may occur in 16 consecutive time slots (1403). The UE can then 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 as actual repetitions (1403) and transmitted as actual repetitions (1403).

[0341] In addition, regarding PUSCH repetition, additional methods related to UL-licensed PUSCH transmissions and configuration-licensed PUSCH transmissions can be defined across time slot boundaries in NR Release 16, as follows: Method 1 (Mini-slot Level Repetition): Two or more PUSCH repetitions are scheduled within a single slot or across consecutive slot boundaries using a single UL grant. For Method 1, the time-domain resource allocation information within the DCI indicates the resources for the first repetition. Furthermore, the time-domain resource information for the remaining repetitions can be determined based on the time-domain resource information of the first repetition and the uplink or downlink direction determined for each symbol in each slot. Each repetition occupies consecutive symbols.

[0342] Method 2 (Multi-segment Transmission): Two or more PUSCH repeat transmissions are scheduled in consecutive time slots using a single UL grant. Each time slot is assigned a transmission numbered 1, and the start points or repeat lengths of the transmissions differ. In Method 2, the time-domain resource allocation information within the DCI indicates the start point and repeat length of all repeat transmissions. When performing repeat transmissions within a single time slot using Method 2, if multiple consecutive uplink symbol bundles exist in the corresponding time slot, the corresponding repeat transmission can be performed for the respective uplink symbol bundle. If a single consecutive uplink symbol bundle exists in the corresponding time slot, a single PUSCH repeat transmission is performed according to the method of NR version 15.

[0343] Method 3: Schedule two or more PUSCH repeat transmissions in consecutive time slots via two or more UL grants. Assign a transmission numbered 1 for each time slot, and the nth UL grant can be received before the PUSCH transmission scheduled via the (n-1)th UL grant is completed.

[0344] Method 4: One or more PUSCH repetitions within a single time slot can be supported via a UL grant or a configuration grant, or two or more PUSCH repetitions spanning consecutive time slot boundaries. The number of repetitions indicated to the UE by the base station is merely a nominal value, and the UE can actually perform more PUSCH repetitions than the nominal number. The time-domain resource allocation information within the DCI or configuration grant refers to the resources for the first repetition indicated by the base station. The time-domain resource information for the remaining repetitions can be determined by referring to the resource information of the first repetition and the uplink or downlink direction of the symbol. If the time-domain resource information for the repetition indicated by the base station spans time slot boundaries or includes uplink / downlink switching points, the corresponding repetition can be divided into multiple repetitions. For each uplink cycle, one repetition can be included in one time slot.

[0345] The aforementioned repeated transmissions 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 higher-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 higher-layer signals without receiving DCI signals independently.

[0346] [PUSCH: Frequency Hopping Process]

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

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

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

[0350]

[0351] ...Formula 4

[0352] In Formula 4, i = 0 and i = 1 can represent the first jump and the second jump respectively, and RB start It can represent the starting RB in ULBWP 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 expressed as... And the number of symbols in the second jump can be expressed as . It is the length of the PUSCH transmission in a time slot and is represented by the number of OFDM symbols.

[0353] 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 resources allocated in the frequency domain in each time slot after changing the resources allocated in the frequency domain by the configured frequency offset. The starting RB during the time slot period related to inter-slot frequency hopping can be represented by Equation 5 below.

[0354]

[0355] ...Formula 5

[0356] In Formula 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, and the RB is calculated according to the frequency resource allocation method. start RB offset This represents the frequency offset between two hops through higher-level parameters.

[0357] Next, the inter-repetition frequency hopping method supported in PUSCH repetition type B transmission is such that the resources allocated in the frequency domain associated with one or more actual repetitions in each nominal repetition are moved by a configured frequency offset and then transmitted. The index RB of the starting RB associated with one or more actual repetitions in the nth nominal repetition in the frequency domain is... start (n) can follow the formula 6 given below:

[0358] ...Formula 6

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

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

[0361] The methods for channel state measurement and reporting in 5G communication systems will be described in detail below. Channel state information (CSI) may include channel quality information (CQI), precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), SS / PBCH block resource indicator (SSBRI), layer indicator (L1), rank indicator (RI), and / or L1 reference signal received power (L1-RSRP). The base station can control the time and frequency resources used for the above-mentioned UE CSI measurement and reporting.

[0362] For the aforementioned CSI measurements and reporting, higher-layer signaling can be used to configure the UE with settings for N (≥1) CSI reports (CSIReportConfig), settings for M (>1) RS transmission resources (CSI-ResourceConfig), and one or two trigger states (CSI-AperiodicTriggerStateList and CSI-SemiPersistentOnPUSCH-TriggerStateList). The configuration information for the aforementioned CSI measurements and reporting can be described in more detail in Tables 32 to 38.

[0363] Table 32: CSI-ReportConfig

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

[19] , Section 5.2.1.

[0365] Table 32: CSI-ReportConfig Information Elements

[0366] Table 33: CSI-ResourceConfig

[0367] The IE CSI-ResourceConfig defines one or more groups of NZP-CSI-RS-ResourceSet, CSI-IM-ResourceSet, and / or CSI-SSB-ResourceSet.

[0368] Table 33: CSI-ResourceConfig Information Elements

[0369] Table 34: NZP-CSI-RS-ResourceSet

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

[0371] Table 34: Information Elements of NZP-CSI-RS-ResourceSet

[0372] Table 35: CSI-SSB-ResourceSet

[0373] The IE CSI-SSB-ResourceSet is used to configure an SS / PBCH block resource set that references the SS / PBCH indicated in ServingCellConfigCommon.

[0374] Table 35: CSI-SSB-ResourceSet Information Elements

[0375] Table 36: CSI-IM-ResourceSet

[0376] The IE CSI-IM-ResourceSet is used to configure one or more CSI Interference Management (IM) resources (their IDs) and a set of set-specific parameters.

[0377] Table 36: CSI-IM-ResourceSet Information Elements

[0378] Table 37: CSI-AperiodicTriggerStateList

[0379] The CSI-AperiodicTriggerStateList IE is a list used to configure aperiodic trigger states for the UE. Each code point in the DCI field "CSI Request" is associated with a trigger state. Upon receiving the 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.

[0380] Table 37: CSI-AperiodicTriggerStateList Information Elements

[0381] Table 38: CSI-SemiPersistentOnPUSCH-TriggerStateList

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

[19] , Section 5.2.

[0383] Table 38: CSI-SemiPersistentOnPUSCH-TriggerStateList Information Elements

[0384] For the aforementioned CSI report settings (CSI-ReportConfig), each CSI-ReportConfig can be associated with a CSI resource setting (which is associated with the corresponding report configuration) and with a downlink (DL) bandwidth portion identified by the bandwidth portion identifier (bwp-id) given as a higher-layer parameter in the CSI-ResourceConfig. As the time-domain reporting operation for each CSI-ReportConfig, "aperiodic," "semi-persistent," and "periodic" methods are supported, and they can be configured from the base station to the UE via the reportConfigType parameter configured from the higher layers. The semi-persistent CSI reporting method supports "semi-persistent on PUCCH" and "semi-persistent on PUSCH." In the case of periodic or semi-persistent CSI reporting methods, the UE can configure PUCCH or PUSCH resources for transmitting CSI from the base station via higher-layer signaling. The period and slot offset of the PUCCH or PUSCH resources used for transmitting CSI can be given based on a set of parameters of the uplink (UL) bandwidth portion configured to transmit CSI reports. In the case of a non-periodic CSI reporting method, the PUSCH resources used for transmitting CSI can be scheduled for the UE from the base station via L1 signaling (DCI format 0_1 ​​above).

[0385] For the CSI resource settings (CSI-ResourceConfig) described above, each CSI resource setting (CSI-ReportConfig) can include S (≥1) CSI resource sets (given as the higher-layer parameter csi-RS-ResourceSetList). The list of CSI resource sets can be configured by non-zero power (NZP) CSI-RS resource sets and SS / PBCH block sets, or by CSI interference measurement (CSI-IM) resource sets. Each CSI resource setting can reside in a downlink (DL) bandwidth portion identified by the higher-layer parameter bwp-id, and CSI resource settings can be connected to CSI reporting settings in the same downlink bandwidth portion. The temporal behavior of the CSI-RS resources in a CSI resource setting can be configured as "aperiodic," "periodic," or "semi-persistent" according to the higher-layer parameter resourceType. For periodic or semi-persistent CSI resource settings, the number of CSI-RS resource sets can be limited to S = 1, and the configured period and slot offset can be given in the parameter set of the DLBWP identified by bwp-id. One or more CSI resource settings for channel measurement or interference measurement can be configured for the UE via higher-layer signaling from the base station, and may include the following CSI resources.

[0386] - CSI-IM resources for interference measurement

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

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

[0389] The CSI-RS resource set (where the higher-layer parameter resourceType is associated with a resource setting configured as “aperiodic”, “periodic”, or “semi-persistent”), the trigger state for CSI report settings (where reportType is configured as “aperiodic”), and the resource settings for channel or interference measurements for one or more CCs can be configured as the higher-layer parameter CSI-AperiodicTriggerStateList.

[0390] 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 by DCI, and can be performed using PUCCH after activation by MAC control element (MAC CE). As mentioned above, CSI resource settings can also be configured to be aperiodic, periodic, or semi-persistent. Combinations between CSI reporting settings and CSI resource settings can be supported based on Table 39 below.

[0391] Table 39

[0392] Table 5.2.1.4-1: Triggering / activation of CSI reports for possible CSI-RS configurations.

[0393]

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

[0395] - If all bits in the CSI request field are 0, it means that no CSI report is requested.

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

[0397] - If the number M of CSI trigger states in the configured CSI-AperiodicTriggerStateLite is equal to or less than 2NTs-1, then one of the M CSI trigger states can be indicated as a CSI request field.

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

[0399] Table 40

[0400] For a CSI resource in a CSI trigger state triggered as a CSI request field, the UE can perform a measurement and generate a CSI (including at least one of CQI, PMI, CRI, SSBRI, LI, RI, or L1-RSRP as described above). The UE can transmit the acquired CSI using a PUSCH scheduled by 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 to the PUSCH resource scheduled by DCI format 0_1 ​​and transmit it. 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 only to the PUSCH resource scheduled by DCI format 0_1 ​​without mapping the uplink data (UL-SCH) and transmit the CSI.

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

[0402] refer to Figure 13 The UE can obtain DCI format 0_1 ​​by monitoring PDCCH 1301 and can obtain scheduling information and CSI request information from PUSCH 1305 based on the measurement. The UE can obtain resource information related to the CSI-RS 1302 to be measured from the received CSI request indicator. The UE can determine at which point to perform the measurement of the resources of the transmitted CSI-RS 1302 based on the time point of receiving DCI format 0_1 ​​and the offset parameter (aperiodicTriggeringOffset) in the CSI resource set configuration (e.g., the NZP CSI-RS resource set configuration (NZP-CSI-RS-ResourceSet)). More specifically, the offset value X of the parameter aperiodicTriggeringOffset in the NZP-CSI-RS resource set configuration can be configured for the UE by the base station via higher-layer signaling, and the configured offset value X can represent the offset between the time slot for receiving the DCI used to trigger the aperiodic CSI report and the time slot used to transmit the CSI-RS resources. For example, the aperiodicTriggeringOffset parameter value and the offset value X can have the mapping relationship described in Table 41 below.

[0403] Table 41

[0404] exist Figure 13 In Example 1300, offset value 1303 is configured as X = 0. In this case, the UE can receive the DCI format 0_1 ​​that triggers the aperiodic CSI report in the time slot (corresponding to...). Figure 13 The UE receives CSI-RS 1302 in time slot 0 (1306) and can report CSI information to the base station via PUSCH 1305. CSI information is measured using the received CSI-RS. The UE can obtain scheduling information (multiple pieces of information corresponding to fields in DCI format 0_1) about PUSCH 1305 used for CSI reporting from DCI format 0_1. For example, the UE can obtain information about the time slot for transmitting PUSCH 1305 from the time-domain resource allocation information in DCI format 0_1 ​​about PUSCH 1305. Figure 13 In Example 1300, the UE can obtain the value 3 as the K2 value 1304 corresponding to the slot offset value from PDCCH to PUSCH, and therefore, PUSCH 1305 can be transmitted in slot 3 1309, which is 3 slots away from slot 0 1306 where PDCCH 1301 is received ( Figure 13 (Time slots 0-1306, 1307, and 2-1308).

[0405] exist Figure 13 In Example 1310, the UE can obtain DCI format 0_1 ​​by monitoring PDCCH 1311, and can obtain scheduling information and CSI information about PUSCH 1315 from DCI format 0_1. The UE can obtain resource information about the CSI-RS 1312 to be measured from the received CSI request indicator. Figure 13 In Example 1310, the aforementioned offset value 1313 of the CSI-RS is configured as X = 1. In this case, the UE can receive the DCI format 0_1 ​​in the time slot that triggers the aperiodic CSI report ( Figure 13 The CSI-RS 1312 is received in time slot 0 (1316), and the CSI information measured using the received CSI-RS can be reported to the base station via PUSCH 1315. Figure 13 In Example 1310, the UE can obtain the value 3 as the K2 value 1314 corresponding to the slot offset value from PDCCH to PUSCH, and therefore, PUSCH 1315 can be transmitted in slot 3 1319, which is 3 slots away from slot 0 1316 where PDCCH 1311 is received ( Figure 13(Time slots 0-1316, 1317, and 2-1318).

[0406] Aperiodic CSI reports may include at least one of CSI Part 1 or CSI Part 2, or both CSI Part 1 and CSI Part 2, and when an aperiodic CSI report is to be transmitted via PUSCH, the aperiodic CSI report and transport block can be multiplexed. For multiplexing, a CRC can be inserted into the input bits of the aperiodic CSI, which can then be encoded and rate matched, and thereafter the input bits can be mapped to resource elements in the PUSCH according to a specific pattern and transmitted. Depending on the encoding method or the length of the input bits, the CRC insertion may be omitted. The number of modulation symbols to be calculated for rate matching in the multiplexing of CSI Part 1 or CSI Part 2 included in the aperiodic CSI report can be calculated as shown in Table 42.

[0407] Table 42

[0408] Specifically, in PUSCH repetition types A and B, the UE can multiplex and transmit aperiodic CSI reports only in the first repetition of the PUSCH repetition. The aperiodic CSI report information to be multiplexed is encoded using a polar coding scheme. Here, in order to multiplex aperiodic CSI report information for multiple PUSCH repetitions, each PUSCH repetition must have the same frequency and time resource allocation. Specifically, in the case of PUSCH repetition type B, each actual repetition can have a different OFDM symbol length, and therefore, the aperiodic CSI report can be multiplexed and transmitted only in the first PUSCH repetition.

[0409] Furthermore, for PUSCH repetition type B, when the UE receives DCI to schedule aperiodic CSI reports or activates semi-persistent CSI reports without scheduling transport blocks, the UE can assume the nominal repetition value to be 1 even if the number of PUSCH repetitions configured by higher-layer signaling is greater than 1. Additionally, when scheduling or activating aperiodic or semi-persistent CSI reports based on PUSCH repetition type B without scheduling transport blocks, the UE can expect the first nominal repetition to be the same as the first actual repetition. For PUSCHs sent based on PUSCH repetition type B that contain semi-persistent CSI reports and are not scheduled by DCI after a semi-persistent CSI report is activated by DCI, if the first nominal repetition is different from the first actual repetition, the transmission of the first nominal repetition can be ignored.

[0410] [Regarding UE Capability Report]

[0411] In LTE and NR, a UE can perform a process whereby, when a UE connects to a serving base station, the UE can report the capabilities it supports to the corresponding base station. In the following description, this process will be referred to as UE capability reporting.

[0412] 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 send 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 those UE capability information messages multiple times. In next-generation mobile communication systems, UE capability requests for multi-RAT dual connectivity (MR-DC) (such as NR, LTE, E-UTRA-NR dual connectivity (EN-DC)) can be made. Typically, a UE capability query message can initially be sent after the UE connects to the base station, but it can be requested under any conditions if the base station requires it.

[0413] After receiving a UE capability report request from the base station during the above operations, the UE can configure its capabilities based on the frequency band information and RAT type requested by the base station. The following outlines the method for configuring UE capabilities in an NR system.

[0414] 1. If the UE receives a list of LTE and / or NR frequency bands from the base station upon requesting UE capabilities, the UE constructs a frequency band combination (BC) for EN-DC and NR standalone (SA). In other words, the UE configures a candidate list of BCs for EN-DC and NR SA based on the frequency bands received from the base station upon request via FreqBandList. The frequency bands have priorities in the order described in FreqBandList.

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

[0416] 3. Then, the UE removes the fallback BC from the BC candidate list configured in the above operation. As used herein, a fallback BC is a BC that can be obtained by removing the band corresponding to at least one SCell from a particular BC, and since the fallback BC may have been covered by the BC before the removal of the band corresponding to at least one SCell, it can be omitted. This operation also applies to MR-DC, that is, LTE bands are also used. The remaining BCs after the above operation constitute the final "candidate BC list".

[0417] 4. The UE selects a BC suitable for the requested RAT type from the final "Candidate BC List" and configures the BC for reporting. In this operation, the UE configures the supportedBandCombinationList in a predetermined order. That is, the UE configures the BC and UE capabilities for reporting according to the pre-configured RAT type order ((nr->eutra-nr->eutra) → (nr->eutra-nr->eutra)). Furthermore, the UE configures the featureSetCombination for the configured supportedBandCombinationList and configures a list of "Candidate Feature Set Combinations" from the candidate BC list that has removed fallback BCs (including capabilities with the same or lower operation). The "Candidate Feature Set Combinations" can include all feature set combinations for NR and EUTRA-NR BCs and can be obtained from the feature set combinations of the UE-NR capability and UE-MRDC capability containers.

[0418] 5. If the requested RAT type is eutra-nr and has an impact, featureSetCombinations are included on both the UE-MRDC capability and the UE-NR capability. However, the NR feature set is only included in the UE-NR capability.

[0419] 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 scheduling and transmit / receive management appropriate to the UE based on the UE capabilities received from the UE.

[0420] [About CA / DC]

[0421] Figure 15 This is a diagram illustrating the radio protocol structure of a base station and a UE in single-cell (S00), carrier aggregation (S10), and dual connectivity (S20) scenarios according to embodiments of the present disclosure.

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

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

[0424] - Transmission of user plane data

[0425] - Mapping between Quality of Service (QoS) streams and Data Radio Bearers (DRBs) for both DL and UL

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

[0427] - Mapping of reflective QoS streams to DRB for UL SDAP Packet Data Units (PDUs)

[0428] For SDAP layer devices, RRC messages can be used to configure whether the UE uses 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, a 1-bit Non-Access Stratum (NAS) QoS reflection configuration indicator (NAS reflective QoS) and an 1-bit AS QoS reflection configuration indicator (AS reflective QoS) can be specified 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 as data processing priority information, scheduling information, etc., to smoothly support services.

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

[0430] - Header compression and decompression: Robust header compression only (ROHC)

[0431] - Transmission of user data

[0432] - Ordered delivery of upper-layer PDUs

[0433] - Unordered delivery of upper-layer PDUs

[0434] - Reordering of received PDCP PDUs

[0435] - Duplicate detection of lower-level service data units (SDUs)

[0436] - PDCP SDU retransmission

[0437] - Encryption and decryption

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

[0439] The reordering of the aforementioned NR PDCP device refers to the function of reordering PDCP PDUs received from the lower layer in order based on the PDCP sequence number (SN), and may include the function of transmitting data to the upper layer in the reordered sequence. Alternatively, the reordering of the NR PDCP device may include the following functions: transmitting data immediately regardless of order, recording PDCP PDUs lost as a result of reordering, reporting the status of lost PDCP PDUs to the transmitting side, and requesting retransmission of lost PDCP PDUs.

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

[0441] - Transmission of upper-layer PDUs

[0442] - Ordered delivery of upper-layer PDUs

[0443] - Unordered delivery of upper-layer PDUs

[0444] Error correction via Automatic Repeat Request (ARQ)

[0445] - Cascading, segmentation, and reassembly of RLC SDUs

[0446] - Resegmentation of RLC data PDUs

[0447] - Reordering of RLC data PDUs

[0448] - Duplicate Detection

[0449] - Protocol error detection

[0450] - RLC SDU discard

[0451] - RLC Reconstruction

[0452] The sequential delivery of the aforementioned NR RLC device refers to the function of delivering RLC SDUs received from the lower layer to the upper layer in sequence. The sequential delivery of the NR RLC device may include the following functions: reassembling and delivering multiple received RLC SDUs segmented from a single original RLC SDU; reordering received RLC SDUs with reference to the RLC sequence number (SN) or PDCP sequence number (SN); recording RLC PDUs lost as a result of reordering; reporting the status of lost RLC PDUs to the transmitter; and requesting retransmission of lost RLC PDUs. The sequential delivery function of the NR RLC device may include the following functions: if there are lost RLC SDUs, only RLC SDUs preceding the lost RLC SDU will be delivered to the upper layer sequentially; and even if there are lost RLC SDUs, if a predetermined timer expires, all RLC SDUs received before the timer starts will be delivered to the upper layer sequentially. Alternatively, in-order delivery by the NR RLC device may include the following functionality: despite the presence of lost RLC SDUs, if a predetermined timer has expired, all currently received RLC SDUs are delivered sequentially to the upper layer. Additionally, in-order delivery by the NR RLC device may include the following functionality: processing RLC PDUs in the order of reception (regardless of sequence number order, in the order of arrival) and delivering them to the PDCP device, regardless of the order (out-of-order delivery); and in the case of segmentation, receiving segments stored in a buffer or to be received later, reconfiguring them into a complete RLCPDU, processing them, and delivering them to the PDCP device. The NR RLC layer may not include cascading functionality, which may be performed in the NR MAC layer or replaced by multiplexing functionality of the NR MAC layer.

[0453] The out-of-order delivery of NR RLC devices refers to the function of delivering RLC SDUs received from lower layers to upper layers in real time, regardless of the order. This can include the following functions: if a raw RLC SDU is received as a segment of multiple received RLC SDUs, then reassemble and deliver them; and store the RLC SN or PDCP SN of the received RLC PDUs and record any RLC PDUs lost as a result of reordering.

[0454] The NR MAC S40 or S55 can be connected to multiple NR RLC layer devices configured in a UE, and the main functions of the NR MAC may include some of the following functions.

[0455] - Mapping between logical channels and transport channels

[0456] - MAC SDU multiplexing / demultiplexing

[0457] - Scheduling Information Report

[0458] - Error correction via Hybrid Automatic Repeat Request (HARQ)

[0459] Priority handling between logical channels of a UE

[0460] - Prioritize UEs through dynamic scheduling

[0461] - Multimedia Broadcast Multicast Service (MBMS) Service Identification

[0462] - Transmission format selection

[0463] - Fill

[0464] According to embodiments of this disclosure, physical layer 2-20 or 2-25 may perform the following operations: channel coding and modulation of upper-layer data to obtain OFDM symbols and deliver them via a wireless channel; or demodulate OFDM symbols received via a wireless channel, channel decode them, and deliver them to the upper layer.

[0465] The detailed structure of a wireless 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 400. 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 410. 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.

[0466] Referring to the above description related to PDCCH and beam configuration, PDCCH retransmission is not supported in current Rel-15 and Rel-16 NR, and therefore, it may be 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 PDCCH retransmission via multiple Transport Points (TRPs). Specific methods will be described below through the following embodiments.

[0467] The operating principles of this disclosure will be described in detail below with reference to the accompanying drawings. The contents of this disclosure can be applied to Frequency Division Duplex (FDD), Time Division Duplex (TDD), and / or Cross-Duplex (XDD) (and / or Subband Non-overlapping Full-Duplex (SBFD)) systems. As used herein, upper-layer signaling (or higher-layer signaling) is a method for transmitting signals from a base station to a UE using downlink data channels of the physical layer or from a UE to a base station using uplink data channels of the physical layer, and may also be referred to as “RRC signaling,” “PDCP signaling,” or “Media Access Control (MAC) control element (MAC CE).”

[0468] In the following, within this disclosure, the UE may use various methods to determine whether cooperative communication is applied. For example, the PDCCH to which cooperative communication is applied has a specific format, or the PDCCH to which cooperative communication is applied includes a specific indicator indicating whether cooperative communication is applied, or the PDCCH to which cooperative communication is applied is scrambled by a specific RNTI, or cooperative communication is assumed to be applied within a specific range indicated by the upper layer. In the following, for ease of description, it will be assumed that the NC-JT case refers to the case where the UE receives a PDSCH to which cooperative communication is applied based on conditions similar to those described above.

[0469] In the following text, determining the priority between A and B can be described differently, for example, by selecting the entity with higher priority and performing the corresponding operation according to a predetermined priority rule, or by omitting or discarding operations concerning the entity with lower priority.

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

[0471] [About NC-JT]

[0472] According to embodiments of this disclosure, the UE may use noncoherent joint transport (NC-JT) to receive PDSCH from multiple TRPs.

[0473] Unlike traditional systems, 5G wireless communication systems support not only services requiring high transmission rates, but also services with very short transmission latency and services requiring high connection density. 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 increasing the strength of the signal received by the UE or effectively controlling interference between cells, TRPs, and / or beams.

[0474] Joint transmission (JT) is a representative transmission technology for cooperative communication, which can increase the strength of the signal received by the UE, the processing rate, or the throughput by transmitting signals to a UE via different cells, TRPs, and / or beams. The channels between each cell, TRP, and / or beam and the UE can have significantly different characteristics, and in particular, noncoherent joint transmission (NC-JT) that supports non-interference coding between individual cells, TRPs, and / or beams may require separate precoding, MCS, resource allocation, and TCI indication based on the channel characteristics of each link between each cell, TRP, and / or beam and the UE.

[0475] The aforementioned NC-JT can be applied to at least one of the Physical Downlink Data Channel (PDSCH), Physical Downlink Control Channel (PDCCH), Physical Uplink Data Channel (PUSCH), and Physical Uplink Control Channel (PUCCH). In PDSCH transmission, transmission information such as precoding, MCS, resource allocation, and TCI can be indicated via DL DCI and should be indicated independently for each cell, TRP, and / or beam of the NC-JT. This is a major factor increasing the payload required for DL ​​DCI transmission, which can adversely affect the reception performance of the PDCCH used to transmit DCI. Therefore, to support JT for PDSCH, a careful design is needed to balance the DCI information volume with the reception performance of the control information.

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

[0477] refer to Figure 16 Examples of PDSCH transmissions are described for each scheme of Joint Transmission (JT), and examples of allocating radio resources for each TRP are also described.

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

[0479] 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 can 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 can send DMRS to the UE through DMRS port A and DMRS port B, respectively. In this case, the UE can receive a DCI message for receiving a PDSCH based on the DMRS demodulated through DMRS port A and DMRS port B.

[0480] Figure 16 Example N020 shows noncoherent joint transmission (NC-JT) that supports non-interference coding between individual cells, TRPs, and / or beams for PDSCH transmission.

[0481] In the NC-JT scenario, for each cell, each TRP, and / or each beam, the PDSCH can be sent to the UE N035, and independent precoding can be applied to each PDSCH. Individual cells, TRPs (N025 or N030), and / or beams can send 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 send 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 typically referred to as TRPs.

[0482] At this point, various radio resource allocations can be considered, such as: case N040, in which multiple TRPs use the exact same frequency and time resources for PDSCH transmission; case N045, in which multiple TRPs use completely non-overlapping frequency and time resources; and case N050, in which some of the frequency and time resources used by multiple TRPs overlap with each other.

[0483] To support NC-JT, various forms, structures, and relationships of DCI can be considered to simultaneously allocate multiple PDSCHs to a UE.

[0484] 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. Figure 17An example of downlink control information (DCI) configuration for NC-JT in a wireless communication system according to an embodiment of the present disclosure is shown, in which each TRP sends different PDSCH or different PDSCH layers to the UE.

[0485] refer to Figure 17 Case #1 N100 is an example where (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) besides the serving TRP (TRP#0) used for a single PDSCH transmission. The control information for the PDSCHs transmitted from the (N-1) additional TRPs is transmitted independently of the control information for the PDSCHs transmitted by the serving TRP. That is, the UE can obtain the control information for the PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through independent DCIs (DC1#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, the freedom of PDSCH control or allocation is fully guaranteed; however, when each DCI is transmitted by different TRPs, differences in DCI coverage may occur, and reception performance may degrade.

[0486] Case #2 N105 is an example where (N-1) different PDSCHs are sent from (N-1) additional TRPs (TRP#1 to TRP#(N1)) other than the serving TRP (TRP#0) for a single PDSCH transmission, and control information for the PDSCHs of the (N-1) additional TRPs is sent, and each DCI depends on the control information for the PDSCHs sent from the serving TRP.

[0487] For example, DCI#0, which serves as control information for PDSCH sent from a serving TRP (TRP#0), may include all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2. However, shortened DCIs (hereinafter referred to as sDCIs) (sDCI#0 to sDCI#(N-2)) used for control information for PDSCH sent from cooperative TRPs (TRP#1 to TRP#(N-1)) may include only some of the information elements from DCI format 1_0, DCI format 1_1, and DCI format 1_2. Therefore, sDCIs used for sending control information for PDSCH sent from cooperative TRPs have a smaller payload than regular DCIs (nDCIs) used for sending control information related to PDSCH sent from a serving TRP, and thus may include reserved bits compared to nDCIs.

[0488] In scenario #2 above, the degree of freedom for controlling or allocating each PDSCH may be limited by the content of the information elements included in the sDCl, but the reception capability of sDCI is superior to that of nDCI, and therefore the probability of differences in DCI coverage may become lower.

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

[0490] For example, when DCI#0 is control information for PDSCH transmitted from the serving TRP (TRP#0), it can include all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2. However, when it is control information for PDSCH transmitted from the cooperating TRPs (TRP#1 to TRP#(N-1)), only some of the information elements from DCI format 1_0, DCI format 1_1, and DCI format 1_2 can be aggregated into a single “supplementary” DCI (sDCI) and transmitted. For example, the sDCI can include at least one HARQ-related piece of information, such as the frequency domain resource allocation and time domain resource allocation of the cooperating TRP, and the MCS. Furthermore, information not included in the sDCI, such as the BWP indicator and carrier indicator, can follow the serving TRP's DCI (DCI#0, normal DCI, or nDCI).

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

[0492] Case #4 N115 is an example where (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) besides the serving TRP (TRP#0) used for a single PDSCH transmission. The control information for the PDSCHs transmitted from the (N-1) additional TRPs is transmitted in a long DCI, which is the same as the DCI used for the control information of the PDSCHs transmitted from the serving TRP. That is, the UE can obtain the control information for the PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through a single DCI. In Case #4 1715, the complexity of the UE's blind DCI decoding may not increase, but the freedom of PDSCH control or allocation may be lower because the number of cooperating TRPs is limited by the long DCI payload constraint.

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

[0494] In the following description and embodiments, cases #1 N100, #2 N105, and #3 N110 (where one or more DCIs (or PDCCHs) are used to support NC-JT) can be classified as NC-JT based on multiple PDCCHs, while case #4 N115 (where a single DCI (or PDCCH) is used to support NC-JT) can be classified as NC-JT based on a single PDCCH. In PDSCH transmission based on multiple PDCCHs, the CORESET of the DCI used to schedule the serving TRP (TRP#0) is separate from the CORESET of the DCI used to schedule the cooperating TRPs (TRP#1 to TRP#(N-1)). The method of distinguishing CORESETs may include a method of distinguishing by a higher-layer indicator for each CORESET and a method of distinguishing by a beam configuration for each CORESET. Furthermore, in NC-JT based on a single PDCCH, a single DCI schedules a single PDSCH with multiple layers, rather than scheduling multiple PDSCHs, and multiple layers can be sent from multiple TRPs. At this point, the correlation between the layer and the TRP that sends the corresponding layer can be indicated by the Transport Configuration Indicator (TCI) for the layer.

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

[0496] In embodiments of this disclosure, depending on the circumstances, "the case in which NC-JT is applied" can be interpreted differently as: "the case in which the UE simultaneously receives one or more PDSCHs in a BWP", "the case in which the UE simultaneously receives PDSCHs in a BWP based on two or more Transport Configuration Indicators (TCIs)", and "the case in which the PDSCHs received by the UE are associated with one or more DMRS port groups", but for ease of interpretation, one expression is used.

[0497] In this disclosure, the wireless protocol architecture for NC-JT can be used differently depending on the TRP development scenario. For example, when there is no backhaul delay or a small backhaul delay exists between cooperative TRPs, it can be similar to... Figure 15 The attached diagram, reference numeral S10, uses a MAC layer multiplexing-based structure (similar to the CA approach). On the other hand, when the backhaul delay between cooperative TRPs is too large to be ignored (e.g., when 2ms or more is needed to exchange information such as CSI, scheduling, and HARQ-ACK between cooperative TRPs), a similar approach can be used. Figure 15 As shown in the attached figure S20, a method that ensures robustness to delay is used by employing an independent structure starting from the RLC layer for each TRP (similar to the DC method).

[0498] UEs supporting C-JT / NC-JT can receive C-JT / NC-JT related parameters or settings from higher-level configurations and set the UE's RRC parameters based on these parameters or settings. For higher-level configurations, the UE can use UE capability parameters, such as tci-StatePDSCH. UE capability parameters (e.g., tciStatePDSCH) can define TCI states for PDSCH transmission. In FR1, the number of TCI states can be configured to 4, 8, 16, 32, 64, and 128, and in FR2, the number of TCI states can be configured to 64 and 128. Up to 8 states can be configured via MAC CE messages (these states can be indicated by 3 bits of the TCI field in the DCI). The maximum value of 128 refers to the value indicated by maxNumberConfiguredTCIstatesPerCC within the parameter tci-StatePDSCH (which is included in the UE's capability signaling). As described above, a series of configuration procedures from high-level configuration to MAC CE configuration can be applied to beamforming indications or beamforming change commands for at least one PDSCH in a TRP.

[0499] [Multi-DCI-based Multi-TRP]

[0500] According to embodiments of this disclosure, downlink control channels for NC-JT transmission can be configured based on multiple PDCCHs.

[0501] In an NC-JT based on multiple PDCCHs, when sending a DCI for scheduling a PDSCH for each TRP, a separate CORESET or search space may exist for each TRP. The CORESET or search space for each TRP can be configured according to at least one of the following configuration options.

[0502] Configuration of the higher-level index for each CORESET: The CORESET configuration information configured by the higher-level layer can include index values, and the TRP used to send PDCCHs in the corresponding CORESET can be distinguished by the index value configured for each CORESET. That is, in a set of CORESETs with the same higher-level index value, it can be assumed that the same TRP sends PDCCHs, or that PDCCHs used to schedule PDSCHs for the same TRP are sent. The index for each CORESET can be called the CORESETPoolIndex, and it can be assumed that in CORESETs with the same CORESETPoolIndex value, PDCCHs are sent from the same TRP. In CORESETs without the same CORESETPoolIndex value, it can be assumed that the default value of the CORESETPoolIndex is configured, and the default value can be 0.

[0503] Configuration of multiple PDCCH-Configs: Multiple PDCCH-Configs are configured in a BWP, and each PDCCH-Config can include PDCCH configurations for each TRP. That is, a list of CORESETs and / or a list of search spaces for each TRP can be included in a PDCCH-Config, and one or more CORESETs and one or more search spaces included in a PDCCH-Config can be considered to correspond to a specific TRP.

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

[0505] Search space beam / beam group configuration: Each search space is configured with a beam or beam group, and the TRP for each search space can be distinguished by it. For example, when the same beam / beam group 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 that the PDCCH used to schedule the PDSCH of the same TRP is sent in the corresponding search space.

[0506] As described above, by separating the CORESET or search space for each TRP, it is possible to partition the PDSCH and HARQ-ACK information for each TRP, and thus generate an independent HARQ-ACK codebook for each TRP and use an independent PUCCH resource.

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

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

[0509] According to embodiments of this disclosure, downlink beams for NC-JT transmission can be configured based on a single PDCCH.

[0510] In a single PDCCH-based NC-JT, PDSCHs transmitted by multiple TRPs can be scheduled by a single DCI. In this case, the number of TRPs transmitting the corresponding PDSCH can be used as a method to indicate the number of TCI states. That is, when the number of TCI states indicated by the DCI used to schedule the PDSCH is 2, a single PDCCH-based NC-JT can be considered, and when the number of TCI states is 1, a single TRP transmission can be considered. The TCI states indicated by the DCI can correspond to one or two TCI states activated by the MAC CE. When the TCI states of the DCI correspond to two TCI states activated by the MAC CE, the TCI code point indicated by the DCI is associated with the TCI state activated by the MAC CE, and here, the number of TCI states activated by the MAC CE corresponding to the TCI code point can be 2.

[0511] The above configuration can be independent for each cell or for each BWP. For example, a PCell can have at most two active TCI states corresponding to a TCI code point, while a specific SCell can have at most one active TCI state corresponding to a TCI code point. In this case, it can be considered that NC-JT is configured for the PCell, but not for the aforementioned SCell.

[0512] [PHR]

[0513] Figure 18 The process of a base station controlling the transmit power of a UE in a wireless communication system according to an embodiment of the present disclosure is illustrated.

[0514] Reference Figure 18 In operations 18-10, UEs within the base station's coverage area can perform downlink synchronization with the base station and acquire system information. According to some embodiments, downlink synchronization can be performed using a primary synchronization signal / secondary synchronization signal (PSS / PSS) received from the base station. UEs that have performed downlink synchronization can receive the main information block (MIB) and system information block (SIB) and acquire system information. In operations 18-15, UEs can perform uplink synchronization with the base station through a random access procedure and configure 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. During the transmission of the random access preamble and message 3, the uplink transmit power can be controlled. Specifically, the UE can receive parameters for controlling the uplink transmit power from the base station using the acquired system information (e.g., SIB), or it can control the uplink transmit power using specified parameters. In another embodiment of this disclosure, the UE can measure the reference signal received power (RSRP) based on the path attenuation estimation signal transmitted by the base station, and estimate the downlink path attenuation value, as shown in Formula 7. Furthermore, the UE can configure the uplink transmit power value for transmitting the random access preamble and message 3 based on the estimated path attenuation value.

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

[0516] Formula 7

[0517] In Formula 7, the transmit power of the base station signal can refer 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). When the path fading estimation signal is a cell-specific reference signal (CRS), the transmit power of the base station signal can refer to the transmit power of the CRS, and can be sent to the UE through the system information parameter referenceSignalPower. When the path fading estimation signal is a synchronization signal block (SSB), the transmit power of the base station signal can refer to the transmit power of the demodulation reference signal (DMRS) transmitted through the secondary synchronization signal (SSS) and PBCH, and can be sent to the UE through the system information parameter ss-PBCH-BlockPower.

[0518] In operations 18-20, the UE can receive RRC parameters for controlling uplink transmit power from the base station via UE-specific RRC or common RRC. The received transmit power control parameters can vary depending on the type of uplink channel and signal transmitted via the uplink. In other words, the transmit power control parameters applied to the uplink control channel (Physical Uplink Control Channel (PUCCH)), the uplink data channel (Physical Uplink Shared Channel (PUSCH)), and the sounding reference signal (SRS) can be different from each other. Furthermore, as mentioned above, transmit power control parameters received by the UE from the base station via SIB before RRC connection configuration, or transmit power control parameters used as pre-specified values ​​by the UE before RRC connection configuration, can be included in the RRC parameters transmitted from the base station after RRC connection configuration. The UE can use the RRC parameter values ​​received from the base station after RRC connection configuration to control the uplink transmit power.

[0519] In operations 18-25, the UE can receive a path fading estimation signal from the base station. More specifically, the base station can configure the Channel State Information Reference Signal (CSI-RS) as the UE's path fading estimation signal after the UE's RRC connection configuration. In this case, the base station can send information related to the transmit power of the CSI-RS to the UE via the powerControlOffsetSS parameter of the UE-specific RRC information. Here, powerControlOffsetSS can refer to the transmit power offset between the SSB and the CSI-RS.

[0520] 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 using Equation 7 by using information related to the transmit power of CSI-RS received from the base station. Furthermore, the UE can configure the uplink transmit power values ​​for transmitting PUCCH, PUSCH, and SRS based on the estimated path attenuation value.

[0521] In Operations 18-35, the UE can transmit a Power Headroom Report (PHR) to the base station. The power headroom can be the difference between the UE's current transmit power and the UE's maximum output power.

[0522] In operations 18-40, the base station can optimize system operation based on the reported power margin. For example, when a particular UE reports a positive power margin value to the base station, the base station can allocate more resource blocks (RBs) to the corresponding UE to increase system throughput (yield).

[0523] In operations 18-45, the UE can receive transmit power control (TCP) commands from the base station. For example, when a specific UE reports a negative power margin value to the base station, the base station can allocate a smaller amount of resources to the corresponding UE or reduce the transmit power of the corresponding UE through transmit power control commands (TPC). This can increase system throughput or reduce unnecessary power consumption by the UE.

[0524] In Operations 18-50, the UE can update its transmit power based on a TPC command. The TPC command can be sent to the UE via a UE-specific DCI or a group command DCI. Therefore, the base station can dynamically control the UE's transmit power using TPC commands. In Operations 18-55, the UE can perform uplink transmissions based on the updated transmit power.

[0525] [PUSCH Power Control]

[0526] The PUSCH transmit power can be determined using the following formula 8.

[0527]

[0528] ...Formula 8

[0529] In Formula 8, This represents the maximum transmit power configured in the UE for carrier f of serving cell c at PUSCH transmission time point i. This represents the reference configuration transmit power configuration value for the active uplink bandwidth portion (BWP) b based on the carrier f of the serving cell c, and has different values ​​depending on the various transmission types j. These values ​​may vary depending on whether the PUSCH transmission is a message 3 PUSCH for random access, a configured licensed PUSCH, or a scheduled PUSCH. This indicates the magnitude of the frequency assigned to PUSCH. This represents the compensation rate value of the path loss of the UL BWP b of the carrier f used for serving cell c, and can be configured by higher-layer signals, and can have different values ​​depending on j. This represents the downlink path loss estimate of the UL BWP b of carrier f in serving cell c, and can be a value measured using a reference signal in the activated downlink BWP. The reference signal can be an SS / PBCH block or CSI-RS. The downlink path loss can be calculated as shown 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. The UE calculates the path attenuation based on reference signal resources associated with the SS / PBCH block or CSI-RS, depending on whether higher-layer signals are configured. For reference signal resources, one of the multiple reference signal resource sets is selected by either higher-layer signals or L1 signals, and the UE calculates the path attenuation based on these reference signal resources. This represents the value determined by the modulation and coding scheme (MCS) value of the PUSCH at time point i of the PUSCH transmission of the UL BWP b of carrier f in serving cell c. This indicates the power control adaptation value, and the power value can be dynamically controlled via the TPC command.

[0530] TPC commands are divided into accumulation mode and absolute mode, with one of the two modes determined by higher-layer signals. In accumulation mode, the currently determined power control adaptation value is accumulated based on the value indicated by the TPC command, and can be increased or decreased according to the TPC command, establishing a relational relationship. . This is the value indicated by the TPC command. In absolute mode, this value is determined by the TPC command, regardless of the currently determined power control adaptation value, and a relational expression is established. Table 43 below shows the values ​​that can be indicated by the TPC command.

[0531] Table 43 TPC Commands

[0532] [PUCCH Power Control]

[0533] Formula 9 is the formula for determining the PUCCH transmit power:

[0534] ...Formula 9

[0535] In Formula 9, This represents the reference configuration transmit power value, and can be configured according to various transmission types q. u These values ​​can be different and can be changed by higher-layer signals such as RRC or MAC CE. When this value is changed by MAC CE and the time slot used to send HARQ-ACK is k relative to the PDSCH that has already received MAC CE, the UE determines the time slot (k+k) from which the UE will receive the HARQ-ACK. offset Start applying the corresponding value. K offset The subcarrier spacing can have different values, and for example, 3ms. This indicates the size of the frequency resource area allocated to PUCCH. This represents the path fading estimate of the UE, calculated by the UE based on a specific reference signal in each CSI-RS or SS / PBCH, depending on whether higher-layer signals are configured and, depending on the type of higher-layer signals, as shown in Equation 7. The same q d It is applied to repeated PUCCH transmissions. The same q u It is used for repeated PUCCH transmissions.

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

[0537] When the number of HARQ-ACK PUCCHs that a UE can send in a single time slot is limited to one, when the UE receives a semi-static HARQ-ACK codebook with a high configuration, the UE receives the PDSCH in the HARQ-ACK codebook in the time slot indicated by the value of the PDSCH-to-HARQ feedback timing indicator in DCI format 1_0 or DCI format 1_1, or reports HARQ-ACK information for SPS PDSCH release in that time slot. In the HARQ-ACK codebook in a time slot not indicated by the PDSCH-to-HARQ feedback timing indicator field in DCI format 1_0 or DCI format 1_1, the UE reports the HARQ-ACK information bit value as NACK. If the UE only reports HARQ-ACK information for a PDSCH release or a PDSCH reception in one of the MA,C cases for candidate PDSCH reception, and the report is scheduled by DCI format 1_0 in the Pcell (which includes information indicating that the counter DCI field is 1), the UE determines a HARQ-ACK codebook for the SPS PDSCH release or the PDSCH reception.

[0538] In addition to the above situations, the HARQ-ACK codebook determination method is adopted according to the following method.

[0539] When the set of PDSCH reception candidate opportunities in serving cell c is MA,c, MA,c can be obtained through the following [pseudocode 1] stage.

[0540] [Starting with pseudocode 1]

[0541] Phase 1: Initialize j to 0, and initialize MA,c to an empty set. Initialize k, which serves as the timing index for HARQ-ACK transmission, to 0.

[0542] Phase 2: Configure R as a set of rows in a table that includes information about the time slot to which the PDSCH is mapped, the start symbol information, and the number or length of symbols. When a PDSCH available mapping symbol indicated by the value R is configured as a UL symbol according to the DL and UL configurations configured through higher-level configurations, the corresponding row is removed from R.

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

[0544] Phase 3-2: When the UE is able to receive two or more unicast PDSCHs in one time slot, the number of PDSCHs that can be allocated in different symbols is counted according to the calculated R, and the counted number of PDSCHs is added to MA,c.

[0545] Phase 4: Increase k by 1 and start over from Phase 2.

[0546] [End of Pseudocode 1]

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

[0548] In pseudocode 1, such as Figure 19 As shown, in order to send a HARQ-ACK PUCCH in time slot #k 1908, all such time slot candidates are considered: where it is possible to indicate the HARQ-ACK timing from the PDSCH in time slot #k 1908. (Reference) Figure 19Assuming that HARQ-ACK transmission is possible in time slot #k 1908 via a combination of PDSCH-to-HARQ-ACK timings, and that this PDSCH-to-HARQ-ACK timing is possible only when PDSCHs scheduled in time slots #n 1902, #(n+1) 1904, and #(n+2) 1906 are involved, the maximum number of PDSCHs that can be scheduled for each time slot is derived by considering the time-domain resource configuration information of the PDSCHs that can be scheduled in each of time slots 1902, 1904, and 1906, as well as information indicating whether the symbols in the time slots correspond to uplink or downlink. For example, when a maximum of two PDSCHs can be scheduled in time slot 1902, a maximum of three PDSCHs can be scheduled in time slot 1904, and a maximum of two PDSCHs can be scheduled in time slot 1906, the maximum number of PDSCHs included in the HARQ-ACK codebook transmitted in time slot 1908 is 7. This is known as the radix of the HARQ-ACK codebook.

[0549] In a specific time slot, phase 3-2 will be described by the following table 44 (default PDSCH time domain resource allocation A for regular CP).

[0550] Table 44

[0551] Table 44 is the time resource allocation table for the UE operating in its default mode before allocating time resources to the UE via a separate RRC signal. For reference, in addition to the index value of the row indicated separately by the RRC, the PDSCH time resource allocation value is also determined by dmrs-TypeA-Position, which is the UE's common RRC signal. In Table 44, for ease of interpretation, end and sequence columns are added separately, and these columns may not actually exist. The end column indicates the end symbol of the scheduled PDSCH, and the sequence column indicates the position value of the code in a specific codebook within the semi-static HARQ-ACK codebook. Table 44 is applied to the time resource allocation, which applies to DCI format 1_0 of the common search area of ​​the PDCCH.

[0552] The UE performs the following stages to calculate the maximum number of non-overlapping PDSCHs in a specific time slot, thereby determining the HARQ-ACK codebook.

[0553] Phase 1: Search all rows in the PDSCH time resource allocation table for the PDSCH allocation value indicating the first PDSCH to end in the time slot. In Table 44, note that row index 14 ends first. Row index 14 is represented by 1 in the sequence column. Other row indices that overlap with row index 14 by at least one symbol are represented by 1× in the sequence column.

[0554] Phase 2: Search the remaining row indices not represented in the sequence column for the PDSCH allocation value that indicates the first PDSCH to end. In Table 44, the PDSCH allocation value corresponds to the row indicated by row index 7 and the dmrs-TypeA-Position value (which is 3). Additionally, other row indices that overlap with their corresponding row indices by at least one symbol are represented by 2× in the sequence column.

[0555] Phase 3: Repeat Phase 2, adding and displaying sequence values. For example, in Table 44, find the PDSCH assignment value indicating the first PDSCH to end in the index of rows not represented in the sequence column. In Table 44, the PDSCH assignment value corresponds to the row indicated by row index 6 and the dmrs-TypeA-Position value (which is 3). Furthermore, other row indices that overlap with their corresponding row indices by at least one symbol are represented by 3× in the sequence column.

[0556] Phase 4: The process ends when the order has been represented for all row indices. Furthermore, the size of the corresponding order corresponds to the maximum number of PDSCHs that can be scheduled in the corresponding time slot without time overlap. Scheduling without time overlap means that different PDSCHs are scheduled by TDM.

[0557] In the sequence columns of Table 44, the maximum sequence value signifies the HARQ-ACK codebook size for the corresponding time slot, and the sequence value signifies the HARQ-ACK codebook point where the HARQ-ACK feedback bit for the corresponding scheduled PDSCH is located. For example, row index 16 in Table 44 means that the HARQ-ACK feedback bit is located in the second code position in a semi-static HARQ-ACK codebook with a size of 3. If the set of opportunities for candidate PDSCH reception in serving cell c is M... A,c Then the UE that sends HARQ-ACK feedback can obtain M through stage [pseudocode 1] or [pseudocode 2]. A,c M A,c This can be used to determine the number of HARQ-ACK bits that the UE needs to send. Specifically, this can be achieved by using M... A,c The cardinality of the set is used to configure the HARQ-ACK codebook.

[0558] As another example, the factors to consider in determining a semi-static HARQ-ACK codebook (or a type 1 HARQ-ACK codebook) can be described below.

[0559]

[0560] As another example, the pseudocode used to determine the HARQ-ACK codebook can be as follows.

[0561]

[0562] In pseudocode 2, the position of the HARQ-ACK codebook containing HARQ-ACK information for indicating the release of the DL SPS is based on the position where the DL SPS PDSCH is received. For example, if the starting symbol of the DL SPS PDSCH transmission is the fourth OFDM symbol based on the time slot and has a length of 5 symbols, the HARQ-ACK information for the DL SPS release indicating the release of the corresponding SPS is determined under the following assumptions: a PDSCH starting from the fourth OFDM symbol of the time slot where the DL SPS release is transmitted and having a length of 5 symbols is mapped, and the corresponding HARQ-ACK information is determined by the PDSCH-to-HARQ-ACK timing indicator and PUSCH resource indicator included in the control information indicating the DL SPS release. As another example, in the case where the starting symbol of the DL SPS PDSCH is transmitted is the fourth OFDM symbol based on the time slot and has a length of 5 symbols, the HARQ-ACK information of the DL SPS release, including the indication of the release of the corresponding SPS, is determined under the following assumptions: a PDSCH with a length of 5 symbols, starting from the fourth OFDM symbol of the time slot indicated by the time domain resource allocation (TDRA) of the DCI released by the DL SPS, is mapped, and the corresponding HARQ-ACK information is determined by the PDSCH-to-HARQ-ACK timing indicator and PUSCH resource indicator included in the control information indicating the release of the DL SPS.

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

[0564] The UE transmits HARQ-ACK information in a PUCCH within the corresponding time slot n, based on the PDSCH-HARQ feedback timing value of the PUCCH transmission used for PDSCH reception or SPS PDSCH release, and K0, which serves as the time slot position information for the PDSCH transmission scheduled by DCI format 1_0 or 1_1. Specifically, for the aforementioned HARQ-ACK information transmission, the UE determines the HARQ-ACK codebook for the PUCCH transmitted in the time slot determined by the PDSCH-HARQ feedback timing and K0, based on the DAI included in the DCI indicating PDSCH or SPS PDSCH release.

[0565] The DAI is configured by the counter DAI and the total DAI. The counter DAI is information indicating the location of HARQ-ACK information in the HARQ-ACK codebook, corresponding to PDSCHs scheduled by DCI format 1_0 or DCI format 1_1. Specifically, the counter DAI value in DCI format 1_0 or 1_1 indicates the accumulated value of PDSCH reception or SPSPDSCH release scheduled by DCI format 1_0 or 1_1 in a specific cell c. The above accumulated value is configured based on the presence of PDCCH monitoring opportunities and the serving cell with scheduled DCI.

[0566] Total DAI is a value indicating the size of the HARQ-ACK codebook. Specifically, the total DAI value means the total number of PDSCHs or SPS PDSCHs released at or before the time the DCI was scheduled. Total DAI is a parameter used in cases where, in carrier aggregation (CA) scenarios, the HARQ-ACK information in serving cell c also includes HARQ-ACK information for PDSCHs scheduled in another cell, including serving cell c. In other words, there is no total DAI parameter in a system operated by a single cell.

[0567] 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. Examples of operations related to DAI are provided in... Figure 20 As shown in the image.

[0568] refer to Figure 20When two carriers are configured for the UE, when the UE transmits a HARQ-ACK codebook based on DAI selection via PUCCH 2020 in the nth time slot of carrier 0 2002, the values ​​of the counter DAI (C-DAI) and total DAI (T-DAI) indicated by the DCI detected in each PDCCH monitoring opportunity configured for each carrier are changed. First, in the DCI detected in opportunity 2006 indicated by m = 0, C-DAI and T-DAI each indicate a value of 1 (indicated by reference numeral 2012). In the DCI detected in opportunity 2008 indicated by m = 1, C-DAI and T-DAI each indicate a value of 2 (indicated by reference numeral 2014). In the DCI detected in opportunity 2010 indicated by m = 2 (c = 0, 2002) in carrier 0, C-DAI indicates a value of 3 (indicated by reference numeral 2016). In the DCI detected at timing 2010 indicated by m = 2 (c = 1, 2004) in carrier 1, the C-DAI indicates value 4 (indicated by reference numeral 2018). If carriers 0 and 1 are scheduled at the same monitoring timing, all T-DAIs are indicated by value 4.

[0569] refer to Figure 19 and Figure 20 The determination of the HARQ-ACK codebook occurs when only one PUCCH containing HARQ-ACK information is transmitted in a time slot. This operation is referred to as Mode 1. As an example of a method for determining a PUCCH transmission resource in a time slot, when PDSCHs scheduled in different DCIs are multiplexed on a single HARQ-ACK codebook in the same time slot, and the codebook is transmitted, the PUCCH resource selected for HARQ-ACK transmission is determined to be the PUCCH resource indicated by the PUCCH resource field in the DCI that last scheduled the PDSCH. That is, PUCCH resources indicated by the PUCCH resource field in DCIs scheduled before this DCI are ignored.

[0570] In the following description, the HARQ-ACK codebook determination method and apparatus are defined in the following case: where two or more PUCCHs containing HARQ-ACK information can be transmitted in one time slot. This operation is referred to as Mode 2. The UE can operate only in Mode 1 (transmitting only one HARQ-ACK PUCCH in one time slot) or only in Mode 2 (transmitting one or more HARQ-ACK PUCCHs in one time slot). Alternatively, if the UE supports both Mode 1 and Mode 2 simultaneously, the base station can configure the UE to operate in only one mode via higher-layer signaling, or implicitly configure Mode 1 and Mode 2 via DCI format, RNTI, DCI-specific field values, and scrambling. For example, a PDSCH scheduled by DCI format A and multiple HARQ-ACK messages associated with that PDSCH are based on Mode 1, and a PDSCH scheduled by DCI format B and multiple HARQ-ACK messages associated with that PDSCH are based on Mode 2. Whether the above HARQ-ACK codebook is semi-static or dynamic is determined by the RRC signal.

[0571] Explanation of satellite communication architecture

[0572] The characteristics of satellite communication are described below. Satellites used for communication can be classified according to their orbits into Low Earth Orbit (LEO), Medium Earth Orbit (MEO), and Geostationary Orbit (GEO). Generally, GEO refers to satellites at an altitude of approximately 36,000 km, MEO refers to satellites at an altitude of 5,000 km to 15,000 km, and LEO can refer to satellites at an altitude of 500 km to 1,000 km. Of course, communication satellites are not limited to the examples above. According to embodiments of this disclosure, the Earth's orbital period varies depending on each altitude. In the case of GEO, the Earth's orbital period is approximately 24 hours, in the case of MEO, the Earth's orbital period is approximately 6 hours, and in the case of LEO, the Earth's orbital period is approximately 90 to 120 minutes. Low Earth Orbit (up to 2,000 km) satellites may have advantages over geostationary orbit (36,000 km) satellites in terms of propagation delay (which can be understood as the time it takes for a signal sent from a transmitter to reach a receiver) and losses due to their relatively low altitude.

[0573] Figure 21 The Earth orbit period of a communication satellite according to an embodiment of this disclosure is shown.

[0574] refer to Figure 21Assuming the UE communicates with a satellite at an altitude of 1200 km, the distance between the UE and the satellite varies depending on the elevation angle between them. For example, when the elevation angle is 90 degrees, the distance is 1200 km, while when it is 10 degrees, the distance is approximately 3135 km. Therefore, in satellite communication, even if the UE is stationary, the distance between the satellite and the UE can vary due to satellites that periodically orbit (such as low-Earth orbit satellites). Furthermore, since the distance between the UE and the satellite in satellite communication is much greater than the distance between the UE and the base station in a terrestrial network, it is necessary to transmit control and data information in the form of data transmission with low bit rates or repetitive transmissions.

[0575] [OCC-based PUCCH transmission]

[0576] The following describes the PUCCH transmission method using Orthogonal Covering Code (OCC) for UEs. LTE PUCCH Format 5 is primarily used to transmit positive acknowledgment / negative acknowledgment (ACK / NACK) feedback for downlink data transmission by using one of the signals transmitted in the PUCCH (PUCCH is the uplink control channel). In PUCCH Format 5, Frequency Division Multiple Access (FDMA) and Time Division Multiple Access (TDMA) methods are combined to classify signals transmitted from different UEs (i.e., OFDMA method), and cyclic shifting techniques are used for signal transmission. To achieve these functions, LTE PUCCH Format 5 applies orthogonal OCC technology. OCC is used to classify signals transmitted from different UEs, and each UE selects an OCC sequence based on a predefined OCC index and transmits ACK / NACK bits covered by the corresponding sequence. Therefore, PUCCH Format 5 using OCC achieves efficient control channel transmission in a multiple access environment, thereby improving the overall performance of the LTE system.

[0577] Figure 22 This is a block diagram illustrating a method for generating LTE PUCCH format 5 according to an embodiment of the present disclosure.

[0578] refer to Figure 22The UE generates HARQ ACK / NACK bits and then performs channel coding and scrambling to generate coded bits. Furthermore, the UE divides the 72 modulated symbols into 12 OFDM symbols through Quadrature Phase Shift Keying (QPSK) modulation and demultiplexing. Then, OCC spreading maps the six modulated symbols allocated to each symbol to 12 frequency subcarriers (tones). An extension scheme can be implemented, allowing QPSK modulated symbols to be mapped to a larger number of virtual frequency subcarriers. Therefore, mutual interference between signals from multiple users can be prevented.

[0579] In other existing LTE PUCCH formats, 12 QPSK modulation symbols can be mapped to a single resource block (RB) SC-FDMA symbol. However, in LTE PUCCH 5, only 6 QPSK modulation symbols are mapped to a single RB and SC-FDMA symbol, such as... Figure 22 As shown. Furthermore, the Code Division Multiplexing (CDM) index used in the spread spectrum scheme is a value assigned to each user and can have a value of 0 or 1. This value determines how each user's signal is spread. For example, a user with a CDM index of 0 maps their own signal twice to 12 virtual frequency subcarriers, while a user with a CDM index of 1 maps their own signal twice, but half of each is multiplied by -1 and mapped to 12 virtual frequency tones. This allows each user's signal to be spread over a wider bandwidth and avoids interference between users in a multi-user environment. An explanation of how interference can be avoided despite using the same time and frequency resources will refer to... Figure 23 Further explanation.

[0580] Figure 23 This invention illustrates a method by which different UEs perform mapping to virtual frequency subcarriers (tones) by applying different OCC values ​​according to embodiments of the present disclosure.

[0581] refer to Figure 23The first UE repeatedly maps the information (A1, A2, A3, A4, A5, and A6) to 1RB. The second UE repeatedly maps the information (B1, B2, B3, B4, B5, and B6) to 1RB, where half of the information is multiplied by 1 and mapped, and the other half is multiplied by -1 and mapped. Subsequently, the first and second UEs transmit the information by performing Discrete Fourier Transform (DFT) and Inverse Fast Fourier Transform (IFFT) on the information. After receiving the information, the base station performs a despreading process and can decode each of A1 and B1, for example, based on the values ​​of "(A1+B1)" and "(A1-B1)" respectively. As described above, the base station can decode the remaining multiple pieces of information, namely, the information of the first UE (A2, A3, A4, A5, and A6) and the information of the second UE (B2, B3, B4, B5, and B6). Although Figure 22 and Figure 23 The OCC spread spectrum scheme is illustrated using the frequency axis as an example, but a time-axis OCC spread spectrum scheme can also be applied. Furthermore, although references have been made... Figure 22 and Figure 23 A method is described for applying OCC sequences (1,1) and (1,-1) to two different UEs with an OCC length of 2. However, sequences with an OCC length greater than 2 can be considered, where two or more different UEs can use the same time and frequency resources to send PUCCH.

[0582] [OCC-based PUSCH transmission]

[0583] The following section describes the PUSCH transmission method using the OCC scheme.

[0584] Figure 24 This is a flowchart illustrating a UE processing procedure for PUSCH transmission according to an embodiment of the present disclosure.

[0585] refer to Figure 24 When there is data to be sent by the UE to the base station, the processing for PUSCH transmission can be performed through the following series of procedures. The following procedures are illustrative only, and some of them may be omitted or their order may be changed to allow the UE to apply them.

[0586] Data block CRC appending (transmission block CRC appending): Error check codes appended to the data.

[0587] LDPC base map selection: Select an appropriate LDPC base map for channel coding.

[0588] Code block segmentation and CRC appending: The data is segmented into smaller blocks, and a CRC is appended to each block.

[0589] Channel coding: Encoding blocks to prevent transmission errors.

[0590] Rate matching: Encoded data is mapped to match available transmission resources.

[0591] Code block concatenation: Encoded blocks are concatenated together.

[0592] Data and control reuse: When control resources overlap with data resources, the corresponding control information and data information are reused.

[0593] Scrambling: Scrambling data to prevent predictable patterns that may degrade signal quality.

[0594] Modulation: Scrambled data is modulated by a carrier wave.

[0595] Layer mapping: Mapping data at the transport layer.

[0596] OCC Spread Spectrum: OCC is applied to data mapped to layers. Applicable... Figure 23 Or other methods.

[0597] Transform precoding: Reconstructing a time-domain signal from a frequency-domain signal using the Discrete Fourier Transform (DFT). This operation is particularly useful in single-transmission-layer scenarios and is used to improve signal orthogonality and reduce interference.

[0598] Precoding: This is a spatial processing operation that optimizes performance by adjusting the transformed signal before transmission. This operation involves applying a matrix to the signal, which can improve its directivity and receiver reception, taking into account different antenna configurations and channel conditions.

[0599] Mapping to Virtual Resource Block (VRB): Data is mapped to virtual resource blocks in the frequency domain.

[0600] Mapping from RB to Physical Resource Block (PRB): Then the virtual resource block is mapped to the physical resource block used for the actual transport.

[0601] In the above process, the OCC spread spectrum scheme can be applied in different ways.

[0602] For example, when the UE repeatedly transmits PUSCH for each time slot, an OCC sequence can be applied for each time slot.

[0603] Figure 25 A method for applying an OCC scheme when a UE performs a PUSCH retransmission for each time slot, according to an embodiment of this disclosure, is illustrated.

[0604] With an OCC length of 2, two different UEs repeatedly transmit PUSCH using the same time and frequency resources. The first UE transmits PUSCH A, and the second UE transmits PUSCH B. The first UE generates the same data a1 (indicated by reference numeral 2500) and repeatedly transmits the data in time slot n and time slot (n+1) (indicated by reference numeral 2502). The second UE maps data b1 in time slot n and maps -b1 (indicated by reference numeral 2501), obtained by multiplying data b1 by -1, in time slot (n+1). Furthermore, the second UE transmits data b1 to PUSCH B in time slot n and data -b1 to PUSCH B in time slot (n+1).

[0605] refer to Figure 25 PUSCH A and PUSCH B transmitted in time slot n and time slot (n+1) are shown to be transmitted by the first UE and the second UE through the same time and frequency resources, but there may be only some overlap in time and frequency resources and other different time and frequency resources are used.

[0606] In addition, Figure 25 In the accompanying drawings, reference numerals 2500 and 2501 illustrate a conceptual diagram used to explain that the data is not generated in time slots n and (n+1), but is transmitted by the first UE and the second UE via PUSCH. In practice, the data can be generated before time slot n, where the PUSCH is first transmitted.

[0607] exist Figure 25 In this context, since the base station receives information (a1+b1) via PUSCH A and PUSCH B (which are transmitted by the first UE and the second UE in time slot n), and receives information (a1-b1) via PUSCH A and PUSCH B (which are transmitted by the first UE and the second UE in time slot (n+1)), the base station can receive each of the data a1 and b1 by applying an OCC despreading scheme to the received information (a1+b1) and (a1-b1). Here, a1 and b1 refer to a set of symbols in which a series of data is channel-coded and modulated. Alternatively, a1 and b1 can be a set of data prior to the DFT.

[0608] For application Figure 25In the OCC scheme shown, the base station can provide the UE in advance with an indication of the value of the OCC sequence to be applied to each time slot during PUSCH retransmission via higher-layer signals or Layer 1 (L1) signals. For example, in the case of a second UE, when the DCI field, referred to as the OCC index, is present in the L1 signal and the corresponding value indicates the bit value corresponding to the OCC sequence (1, -1), the second UE can apply "1" in time slot n and "-1" in time slot (n+1). Specifically, when the DCI field, referred to as the OCC index, is present as a single bit, if a bit has a value of 0, the OCC sequence can be indicated as (1, 1), and if a bit has a value of 1, the OCC sequence can be indicated as (1, -1) or (-1, 1). The OCC sequence type and DCI field size can be determined through higher-layer signal configuration. The length of the OCC sequence can be a value greater than the length 2 described in the example above.

[0609] In addition, Figure 25 In this context, the first UE is described as applying the OCC sequence (1,1), but without considering this, the first UE can perform conventional PUSCH retransmissions without applying the OCC sequence. Therefore, in Figure 25 In this configuration, the first UE may or may not transmit UE capabilities that enable the application of the OCC spreading method. On the other hand, the second UE may apply the OCC spreading method only if it transmits UE capabilities that enable the application of the OCC spreading method.

[0610] although Figure 25 The illustration shows the scenario where the first UE and the second UE apply two repeated transmissions, but the number of time slots for repeated transmissions can be four, eight, or more. In this case, assuming that the OCC sequence (1, -1) applied by the second UE is repeated four times, b1 can be applied to time slot n, -b1 to time slot (n+1), b1 to time slot (n+2), and -b1 to time slot (n+3), or b1 can be applied to time slot n, b1 to time slot (n+1), -b1 to time slot (n+2), and -b1 to time slot (n+3). Alternatively, the OCC sequence of 1 (or -1) can always be applied to even-numbered time slots, while the OCC sequence of -1 (or 1) can always be applied to odd-numbered time slots. Alternatively, the OCC sequence can be applied using modulo operations. Since the OCC sequence (1, -1) has a length of 2, the OCC sequence value applied to PUSCH in the nth time slot can be 1 (or -1) if mod(n / 2) has a value of 1, and the OCC sequence value applied to PUSCH in the nth time slot can be -1 (or 1) if mod(n / 2) has a value of 0.

[0611] Furthermore, despite Figure 25The illustration shows that the first UE and the second UE start with the same number of repeated transmissions from the same time slot, but this can be applied to situations where repeated transmissions start from different time slots and / or perform different numbers of repeated transmissions.

[0612] In another example, when performing PUSCH retransmission within a time slot, the UE can apply an OCC sequence for each PUSCH retransmission unit.

[0613] Figure 26 A method for applying an OCC scheme when a UE performs a PUSCH retransmission within a time slot, according to an embodiment of this disclosure, is illustrated.

[0614] according to Figure 26 The method of the illustrated embodiment is substantially similar to Figure 25 The operation is as follows: With an OCC length of 2, two different UEs repeatedly transmit PUSCH using the same time and frequency resources. The first UE transmits PUSCH A, and the second UE transmits PUSCH B. The first UE generates the same data a1 (indicated by reference numeral 2600) and performs repeated transmission in a time slot N (indicated by reference numeral 2602). The second UE maps data b1 to the first PUSCH B in time slot N and maps -b1 (obtained by multiplying data b1 by -1) to the second PUSCH B in time slot N. Furthermore, the second UE transmits data b1 to the first PUSCH B in time slot N and data -b1 to the second PUSCH B in time slot N.

[0615] refer to Figure 26 PUSCH A and PUSCH B transmitted in time slot n are shown to be transmitted by the first UE and the second UE using the same time and frequency resources, but there may be only some overlap in time and frequency resources, and other different time and frequency resources may be used. Furthermore, in Figure 26 In the accompanying diagram, reference numerals 2600 and 2601 are conceptual diagrams used to illustrate that data is not generated in time slot n, but is transmitted by the first UE and the second UE via PUSCH. In practice, the data can be generated before time slot n, where the PUSCH is first transmitted. Figure 26In this context, since the base station receives information (a1+b1) via first PUSCH A and PUSCH B (which are transmitted by each of the first UE and the second UE in time slot n), and receives information (a1-b1) via second PUSCH A and PUSCH B (which are transmitted by each of the first UE and the second UE in time slot n), the base station can receive each of data a1 and b1 by applying an OCC despreading scheme to the received information (a1+b1) and (a1-b1). Here, a1 and b1 refer to a set of symbols in which one set of data is channel-coded and modulated. Alternatively, a1 and b1 can be a set of data prior to the DFT.

[0616] In order to apply, such as Figure 26 In the OCC scheme shown, the base station can pre-indicate the value of the OCC sequence to be applied to each time slot during PUSCH retransmissions via higher-layer signals or L1 signals. For example, in the case of a second UE, when the DCI field, referred to as the OCC index, exists in the L1 signal and the corresponding value indicates the bit value corresponding to the OCC sequence (1, -1), the second UE can apply "1" in the first PUSCH and "-1" in the second PUSCH. Specifically, the DCI field, referred to as the OCC index, exists as a single bit; if a bit has a value of 0, the OCC sequence can be indicated as (1, 1), and if a bit has a value of 1, the OCC sequence can be indicated as (1, -1) or (-1, 1). The OCC sequence type and DCI field size can be determined through higher-layer signal configuration. The length of the OCC sequence can be a value greater than the length 2 described in the example above.

[0617] In addition, Figure 26 In this context, the first UE is described as applying the OCC sequence (1,1), but without considering this, the first UE can perform conventional PUSCH retransmissions without applying the OCC sequence. Therefore, in Figure 26 In this configuration, the first UE may or may not transmit UE capabilities that enable the application of the OCC spreading method. On the other hand, the second UE may apply the OCC spreading method only if it transmits UE capabilities that enable the application of the OCC spreading method.

[0618] although Figure 26This addresses the case where the first UE and the second UE apply two repeated transmissions, but the number of PUSCHs that are repeatedly transmitted can also be four, eight, or more. Furthermore, PUSCHs can be repeatedly transmitted across multiple time slots, rather than just within a single time slot. In this case, assuming the OCC sequence (1, -1) applied by the second UE is repeatedly transmitted four times, b1 can be applied to the first PUSCH, -b1 to the second PUSCH, b1 to the third PUSCH, and -b1 to the fourth PUSCH; or b1 can be applied to the first PUSCH, b1 to the second PUSCH, -b1 to the third PUSCH, and -b1 to the fourth PUSCH. Alternatively, an OCC sequence of 1 (or -1) can always be applied to even-numbered PUSCH transmissions, while an OCC sequence of -1 (or 1) can always be applied to odd-numbered PUSCH transmissions. Alternatively, the OCC sequence can be applied using modulo operations. Since the OCC sequence (1, -1) has a length of 2, the OCC sequence value applied to the nth PUSCH can be 1 (or -1) if mod(n / 2) has a value of 1, and the OCC sequence value applied to the nth PUSCH can be -1 (or 1) if mod(n / 2) has a value of 0.

[0619] Furthermore, despite Figure 26 The illustration shows that the first UE and the second UE start with the same number of repeated transmissions from the same time slot, but this can be applied to situations where repeated transmissions start from different time slots and / or perform different numbers of repeated transmissions.

[0620] In another example, an OCC sequence can be applied between multiple messages belonging to different time resources within a single PUSCH.

[0621] Figure 27 This invention illustrates a method for applying an OCC scheme from a time resource perspective when a UE performs a PUSCH transmission, according to an embodiment of the present disclosure.

[0622] refer to Figure 27 When applying a 2-length OCC scheme from a time resource perspective, when calculating the Transport Block Size (TBS), both the first and second UEs can determine the actual TBS value by dividing the size of the PUSCH resources allocated to the respective UE by 2. Alternatively, the TBS calculation can consider the actual size of the PUSCH transport resource region separately. The size of the PUSCH transport resource region is determined by the frequency resource size (number of RBs) and the time resource size (number of symbols). Subsequently, the UE... Figure 24 The process described herein performs data transmission preparation. Furthermore, in OCC spread spectrum operations, such as... Figure 27As shown, the first UE arranges two identical data points a1 in time resource order, and for each of these two data points (indicated by reference numeral 2700), the OCC sequence (1, 1) is applied to the first a1 and the second a1. Furthermore, the first UE transmits them in the PUSCH A resource area allocated by the base station (indicated by reference numeral 2702). The second UE also arranges two identical data points b1 in time resource order, and for each of these two data points (indicated by reference numeral 2701), the OCC sequence (1, -1) is applied to the first b1 and the second b1. Furthermore, the second UE transmits them in the PUSCH B resource area allocated by the base station (indicated by reference numeral 2702).

[0623] although Figure 27 The diagram illustrates dividing the data applied by OCC into two equal parts based on time resources. However, data can be divided and applied to three, four, or more equal parts. When the same data is mapped to four equal parts, the first UE can generate data (a1, a1, a1, a1), and the second UE can generate data (b1, -b1, b1, -b1) or (b1, b1, -b1, -b1). Furthermore, although in Figure 23 The OCC spread spectrum and despreading schemes have already been described from a frequency axis perspective, but they can also be applied from a time axis perspective, and they can be compared with reference... Figure 23 The descriptions are the same or somewhat similar.

[0624] refer to Figure 27 PUSCH A and PUSCH B transmitted in time slot n are shown to be transmitted by the first UE and the second UE using the same time and frequency resources, but there may be only some overlap in time and frequency resources, and other different time and frequency resources may be used.

[0625] In addition, Figure 27 In the accompanying diagram, reference numerals 2700 and 2701 are conceptual diagrams used to illustrate that the data is not generated in time slot n, but is transmitted by the first UE and the second UE via PUSCH. In reality, the data can be generated before time slot n, where PUSCH is first transmitted.

[0626] exist Figure 27In this context, since the base station receives the information (a1+b1) via PUSCH A and PUSCH B (which are transmitted by the first UE and the second UE in time slot n), the base station can receive each of the data a1 and b1 by applying an OCC despreading scheme to the received (a1+b1) and (a1-b1) information. Here, a1 and b1 refer to a set of symbols in which a series of data is channel-coded and modulated. Alternatively, a1 and b1 can be a set of data prior to the DFT.

[0627] In order to apply, such as Figure 27 In the OCC scheme shown, the base station can pre-indicate to the UE, via higher-layer signals or L1 signals, the value of the OCC sequence to be applied to each time slot during PUSCH retransmission. For example, in the case of a second UE, when the DCI field, referred to as the OCC index, exists in the L1 signal and the corresponding value indicates the bit value corresponding to the OCC sequence (1, -1), the second UE can apply the value "1" to the first part of the PUSCH and the value "-1" to the second part of the PUSCH. Specifically, the DCI field, referred to as the OCC index, exists as a single bit, and if a bit has a value of 0, the OCC sequence can be indicated as (1, 1), and if a bit has a value of 1, the OCC sequence can be indicated as (1, -1) or (-1, 1). The OCC sequence type and DCI field size can be determined through higher-layer signal configuration. The length of the OCC sequence can use a value greater than the length 2 described in the example above.

[0628] exist Figure 27 In this context, the first UE may or may not transmit UE capabilities that can apply the OCC spread spectrum method.

[0629] Despite Figure 27 The example described is of sending a single PUSCH, but it is not limited to this, and it is also possible for a PUSCH to be transmitted repeatedly on multiple time slots.

[0630] Furthermore, despite Figure 27 The illustration shows that the first UE and the second UE start PUSCH transmission from the same time slot, but this can be applied to situations where PUSCH transmission starts from different time slots and / or performs different numbers of repeated transmissions.

[0631] In another example, an OCC sequence can be applied between multiple messages belonging to different time resources within a single PUSCH.

[0632] Figure 28 This invention illustrates a method for applying an OCC scheme from a frequency resource perspective when a UE performs a PUSCH transmission, according to an embodiment of the present disclosure.

[0633] refer to Figure 28 When the first UE and the second UE apply an OCC scheme of length 2 from a frequency resource perspective, when calculating the TBS, the UE can determine the actual TBS value by dividing the size of the PUSCH resources allocated to the respective UE by 2. Alternatively, the TBS calculation can consider the actual size of the PUSCH transmission resource area separately. The size of the PUSCH transmission resource area is determined by the frequency resource size (number of RBs) and the time resource size (number of symbols). Subsequently, the UE... Figure 24 The process described herein performs data transmission preparation. Furthermore, in OCC spread spectrum operations, such as... Figure 28 As shown, the first UE arranges two identical data points a1 in frequency resource order, and for each of these two data points (indicated by reference numeral 2800), the OCC sequence (1, 1) is applied to the first a1 and the second a1. Furthermore, the first UE transmits them in the PUSCH A resource area allocated by the base station (indicated by reference numeral 2802). The second UE also arranges two identical data points b1 in time resource order, and for each of these two data points (indicated by reference numeral 2801), the OCC sequence (1, -1) is applied to the first b1 and the second b1. Furthermore, the second UE transmits them in the PUSCH B resource area allocated by the base station (indicated by reference numeral 2802).

[0634] although Figure 28 The diagram illustrates dividing the data applied by OCC into two equal parts according to frequency resources. However, the data can be divided and applied to three, four, or more equal parts. In the case where the same data is mapped to four equal parts, the first UE can generate data (a1, a1, a1, a1), and the second UE can generate data (b1, -b1, b1, -b1) or (b1, b1, -b1, -b1). Furthermore, the OCC spreading and despreading scheme can be compared with a reference... Figure 23 The descriptions are the same or somewhat similar. See again. Figure 28 PUSCH A and PUSCH B transmitted in time slot n are shown to be transmitted by the first UE and the second UE using the same time and frequency resources, but there may be only some overlap in time and frequency resources, and other different time and frequency resources may be used.

[0635] In addition, Figure 28 In the accompanying diagram, reference numerals 2800 and 2801 are conceptual diagrams used to illustrate that the data is not generated in time slot n, but is transmitted by the first UE and the second UE via PUSCH. In reality, the data can be generated before time slot n, where PUSCH is first transmitted.

[0636] exist Figure 28In this context, since the base station receives information (a1+b1) and (a1-b1) via PUSCH A and PUSCH B (which are transmitted by the first UE and the second UE in time slot n), the base station can receive each of data a1 and b1 by applying an OCC despreading scheme to the received information (a1+b1) and (a1-b1). Here, a1 and b1 refer to a set of symbols in which a series of data is channel-coded and modulated. Alternatively, a1 and b1 can be a set of data prior to the DFT.

[0637] In order to apply, such as Figure 28 In the OCC scheme shown, the base station can pre-indicate to the UE, via higher-layer signals or L1 signals, the value of the OCC sequence to be applied to each time slot during PUSCH retransmission. For example, in the case of a second UE, when the DCI field, referred to as the OCC index, exists in the L1 signal and the corresponding value indicates the bit value corresponding to the OCC sequence (1, -1), the second UE can apply the value "1" to the first part of the PUSCH and the value "-1" to the second part of the PUSCH. Specifically, the DCI field, referred to as the OCC index, exists as a single bit, and if a bit has a value of 0, the OCC sequence can be indicated as (1, 1), and if a bit has a value of 1, the OCC sequence can be indicated as (1, -1) or (-1, 1). The OCC sequence type and DCI field size can be determined through higher-layer signal configuration. The length of the OCC sequence can use a value greater than the length 2 described in the example above.

[0638] exist Figure 28 In this context, the first UE and the second UE may or may not transmit UE capabilities that can apply the OCC spread spectrum method.

[0639] Despite Figure 28 The example described is of sending a single PUSCH, but it is not limited to this, and it is also possible for a PUSCH to be transmitted repeatedly on multiple time slots.

[0640] Furthermore, despite Figure 28 The illustration shows that the first UE and the second UE start PUSCH transmission from the same time slot, but it can be applied to situations where PUSCH transmission starts from different time slots and / or performs different numbers of repeated transmissions.

[0641] In the following description, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the description below, a base station is an entity that allocates resources to terminals and can be at least one of the following: gNode B, eNode B, Node B, base station (BS), radio access unit, base station controller, and nodes on a network. Terminals may include 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 as an example, but embodiments of the present disclosure can also be applied to other communication systems with similar technical backgrounds or channel types. Examples of such communication systems may include LTE or LTE-A mobile communication systems and mobile communication technologies developed after 5G. Therefore, based on the determination of those skilled in the art, the present disclosure can be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure. The content of the present disclosure is applicable to FDD, TDD, and / or XDD (and / or SBFD) systems.

[0642] Furthermore, in describing this disclosure, a detailed description of a known function or configuration incorporated herein will be omitted where it is determined that such a description would unnecessarily obscure the subject matter of this disclosure. The terminology described below is for the functional definitions considered in this disclosure and may vary depending on the user, the user's intent, or custom. Therefore, the definition of terminology should be based on the entire contents of this specification.

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

[0644] -Master Message Block (MIB)

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

[0646] - Radio Resource Control (RRC)

[0647] -Media Access Control (MAC) Control Element (CE)

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

[0649] -Physical Downlink Control Channel (PDCCH)

[0650] Downlink Control Information (DCI)

[0651] -UE-specific DCI

[0652] -Group Public DCI

[0653] -Public DCI

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

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

[0656] -Physical Uplink Control Channel (PUCCH)

[0657] -Uplink Control Information (UCI)

[0658] In the following text, determining the priority between A and B can be described in various ways, such as selecting the entity with higher priority according to a predetermined priority rule and performing the corresponding operation, or omitting or discarding operations concerning the entity with lower priority. As used herein, the term "discard" can be replaced by other terms with similar meanings. For example, "discard" can be replaced by the terms "cancel," "omit," "pause," etc.

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

[0660] In the following description, the above examples may be described by means of several embodiments, but they are not independent of each other, and one or more embodiments may be applied simultaneously or in combination.

[0661] The following describes the application of OCC-based PUSCH transmission in satellite communications. The methods described below can also be applied to terrestrial networks. Satellite communications generally consist of three components: the UE, the ground station (base station), and the satellite. The link between the UE and the satellite is called the serving link, and the link between the ground station and the satellite is called the feeder link. In the serving link, the downlink typically refers to the satellite-UE link (the link from the satellite to the UE), and the uplink refers to the UE-satellite link (the link from the UE to the satellite).

[0662] Similar to terrestrial networks, the uplink coverage of satellites may be insufficient because the transmit power of a UE may be much lower than that of the satellite. To address this, UEs typically perform repetitive uplink data transmissions. If all UEs within satellite coverage area perform repetitive transmissions of the same data via the uplink, the available frequency and time resources of the satellite network may be insufficient. To solve this problem, in addition to frequency and time resources, code resources are needed to support a larger number of UEs. Therefore, the aforementioned OCC scheme can be considered for transmitting uplink data.

[0663] [First Embodiment]

[0664] When a UE receives a schedule for repeated PUSCH transmissions via higher-layer signals or L1 signals, it can apply the same or different Redundancy Version (RV) values ​​for each PUSCH transmission interval unit used for repeated transmissions or for each time slot transmitting a PUSCH. The reason for applying RVs is typically to increase the reliability of data transmission. Specifically, the receiving node can improve reliability by detecting and correcting errors in the data transmitted by the sending node.

[0665] In the case of Configuration Grant (CG) PUSCHs, which are typically configured only by higher-layer signals or activated by both higher-layer signals and L1 signals, the RV value can be configured to at least one of {0, 2, 3, 1}, {0, 3, 0, 3}, and {0, 0, 0, 0} for each PUSCH that is repeatedly transmitted within a CG PUSCH cycle. For example, if four CG PUSCHs are repeatedly transmitted within a CG PUSCH cycle and the RV value is configured to have the value {0, 2, 3, 1}, the UE applies RV=0 to the first CG PUSCH, RV=2 to the second CG PUSCH, RV=3 to the third CG PUSCH, and RV=1 to the fourth CG PUSCH. In the case of Dynamic Grant (DG) PUSCHs, which are scheduled by L1 signals (e.g., DCI), the RV value can be applied to each repeatedly transmitted PUSCH as shown in Table 45.

[0666] Table 45 Redundant Versions for PUSCH Transfer

[0667] When OCC is applied under conditions where different RV values ​​are applied to the retransmitted PUSCH (as described above), the base station may be unable to perform reception. For example, refer to... Figure 25When the base station provides each of the first and second UEs with a DCI for scheduling PUSCH repetition transmissions in two time slots, and the RV value of the DCI is indicated as 0, the first UE transmits a1 with RV = 0 in time slot n and a1' with RV = 1 in time slot (n+1). The second UE transmits data b1 with rv = 0 in time slot n and data -b1' with rv = 1 in time slot (n+1). Therefore, since the base station receives information (a1+b1) in time slot n and information (a1'-b1') in time slot (n+1), it is difficult to decode a1 and b1 by using these two received signals through the OCC despreading process. Therefore, for PUSCH repetition transmissions with OCC spread spectrum, it may be necessary to have the same data with at least the same RV value, and at least one or a combination of the following methods can be considered.

[0668] Method 1-1: When the UE receives a DCI indicating the OCC spreading method and a PUSCH retransmission, the UE applies the same RV applied to the first PUSCH to the retransmitted PUSCH. This method ignores the RV modification rules described in Table 45, and when the UE receives a DCI specifying the OCC spreading method, the same RV value applied to the first PUSCH is used for all subsequent retransmitted PUSCHs. When the UE receives a DCI not indicating the OCC spreading method, the UE can apply Table 45 to the retransmitted PUSCHs. In other words, depending on the OCC spreading method, the UE can apply RV values ​​to the PUSCH transmission resource intervals scheduled for retransmission in different ways.

[0669] Method 1-2: The same RV application method can be applied to each group that has applied OCC.

[0670] Figure 29 An OCC spread spectrum applied to each PUSCH group according to an embodiment of this disclosure is shown. Figure 29 The following scenario is illustrated: the first and second PUSCHs are configured to the same OCC group, the third and fourth PUSCHs are configured to the same OCC group, and the fifth and sixth PUSCHs are configured to the same OCC group. An OCC group is a group applied by the base station to perform OCC despreading. Figure 25 The two PUSCHs sent by each UE shown can be grouped into an OCC group. Figure 29 This is shown from the perspective of the first UE, and the second UE can receive scheduling of PUSCH transmission resources with the same time and frequency resources as the first UE, or can receive scheduling of PUSCH transmission resources with at least different time or frequency resources. Figure 29In the scenario shown, since the RV value only needs to be the same within at least one OCC group, the UE is required to receive information from the base station via a separate higher-layer signal or L1 signal regarding the number of PUSCH repetitions within the OCC group. When the UE receives the DCI indicating the OCC spreading method and determines that the number of PUSCH repetitions within the OCC group is N, the UE can apply the RV values ​​shown in Table 46. For example, if the base station indicates a value of rv = 0 using the DCI, the UE can determine a value of rv = 0 for the first and second PUSCHs, a value of rv = 2 for the third and fourth PUSCHs, and a value of rv = 3 for the fifth and sixth PUSCHs, according to Table 46.

[0671] Table 46 Redundant Versions for PUSCH Transfer

[0672] N: The number of time slots applied to the same OCC group

[0673] The above method may be applicable only when the OCC spread spectrum scheme is applied on the time axis, or only when different OCC sequence values ​​are applied to each repetitive PUSCH transmission. Furthermore, the above method may be applicable only to PUSCH repetitions scheduled from DCIs that include CRCs scrambled by C-RNTI.

[0674] [Second Embodiment]

[0675] The following describes a situation where some PUSCHs overlap with PUCCHs during repeated transmissions of PUSCHs using OCC spread spectrum.

[0676] Figure 30 This illustration shows a situation where a specific PUSCH and PUCCH overlap when the UE performs repeated PUSCH transmissions according to an embodiment of this disclosure. Figure 30 Examples of situations in which embodiments of this disclosure apply are shown.

[0677] refer to Figure 30 The first UE repeatedly transmits PUSCH A, and the second UE repeatedly transmits PUSCH B. The repeatedly transmitted PUSCHs can be located in the same time slot or different time slots. If the first UE's PUSCH A overlaps with the second repeatedly transmitted PUSCH A, the UE can multiplex the Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) or Channel State Information (CSI) contained in PUSCH A into PUSCH A.

[0678] Figure 31Resource allocation is shown according to an embodiment of this disclosure, illustrating the multiplexing order when uplink control information (UCI) is multiplexed to the PUSCH.

[0679] refer to Figure 31 The UE performs rate matching by mapping HARQ-ACK information immediately after the DMRS symbol and mapping CSI Part 1 and CSI Part 2 from the first symbol scheduled by PUSCH.

[0680] In this case, each UE application such as Figure 25 The base station cannot receive correctly when using the OCC spreading method shown and when the receiving node of the base station applies OCC despreading. This is because, Figure 30 In the scenario shown, the base station receives information (a1 + b1) via a first PUSCH A sent by the first UE and a first PUSCH B sent by the second UE, but receives information (c1 - b1) via a second PUSCH A sent by the first UE and a second PUSCH B sent by the second UE. In other words, because the first UE performs UCI mapping in a manner different from the existing PUSCH resource allocation method used in the absence of existing UCI, the base station finds it difficult to decode using the information (a1 + b1) and (c1 - b1) when performing OCC despreading.

[0681] Therefore, at least one or a combination of the following methods can be considered to solve these problems. This disclosure is applicable to overlaps occurring within a single cell, and also to environments with multiple cells. In the case of multiple cells, this disclosure is only applicable to the situation where PUSCH A is selected to perform UCI multiplexing for PUCCH A.

[0682] Method 2-1: If the UE has already received a DCI indicating OCC spread spectrum and PUSCH retransmission, and at least one of the retransmitted PUSCHs overlaps with a PUCCH, the UE does not transmit the PUCCH and discards the UCI contained in the PUCCH. This method can also be applied to PUSCH retransmissions where the PUSCH is configured via higher-layer signals, without needing to receive a separate DCI. This method can be applied only to PUCCHs scheduled via L1 signals, only to PUCCHs configured via higher-layer signals, or both.

[0683] Method 2-2: If the UE has already received a DCI indicating OCC spread spectrum and PUSCH retransmission, and at least one of the retransmitted PUSCH overlaps with a PUCCH, the UE performs PUCCH transmission instead of transmitting the overlapping PUSCH. This method can also be applied to PUSCH retransmission where the PUSCH is configured via higher-layer signals and does not require separate DCI reception. This method can be applied only to PUCCHs scheduled via L1 signals, only to PUCCHs configured via higher-layer signals, or both.

[0684] Methods 2-3: If the UE has received a DCI indicating the OCC spreading method and PUSCH retransmission, and at least one of the retransmitted PUSCHs overlaps with a PUCCH, the UE can multiplex the UCI of the overlapping PUCCH to that overlapping PUSCH, and also multiplex the UCI of the overlapping PUCCH to other non-overlapping PUSCHs with the same data (TB). Alternatively, if the UE has received a DCI indicating the OCC spreading method and PUSCH retransmission, and at least one of the retransmitted PUSCHs overlaps with a PUCCH, the UE can multiplex the UCI of the overlapping PUCCH to that overlapping PUSCH, and also multiplex the UCI of the overlapping PUCCH to other PUSCHs belonging to the same OCC group as the corresponding PUSCH and not overlapping with the PUCCH. (Reference) Figure 30 As an example, when a first UE transmits PUSCH A and PUCCH A, and a second PUSCH A overlaps with PUCCH A, the first UE can multiplex the UCI of PUCCH A on both the first and second PUSCH A. In this case, when calculating the minimum time required to multiplex the UCI of PUCCH A, the time (time interval) between the last symbol of the last symbol of the PDCCH or PDSCH associated with PUCCH A and the last symbol of the PDCCH providing PUSCH A, and the starting symbol of the first PUSCH A, should be greater than the minimum time required for the UE to multiplex the UCI. Therefore, when multiplexing the UCI of PUCCH A to PUSCH A, the first UE can determine whether to multiplex the UCI only to the overlapping PUSCH A based on whether the OCC spreading method provided via DCI is applied (e.g., Figure 30 The second PUSCH A) or also reused to non-overlapping PUSCH A (e.g., Figure 30The first PUSCH A). Therefore, the processing time for the UE to prepare for UCI multiplexing and PUSCH can be determined by considering the following times: the earliest time (X1) of the PUSCH to which the UCI will be multiplexed and the PUCCH containing the UCI, and the latest time (X2) of the PDSCH and PDCCH associated with the corresponding PUSCH and PUCCH. The UE can only map the UCI and send it to the PUSCH to which the UCI is to be multiplexed if the time difference between the earliest time (X1) and the latest time (X2) is greater than the UE's minimum processing time requirement.

[0685] Methods 2-4: When the UE has received a DCI indicating OCC spreading and PUSCH retransmission, if at least one of the retransmitted PUSCHs overlaps with a PUCCH, the UE can transmit both PUSCH and PUCCH simultaneously without multiplexing the UCI of the PUCCH to the PUSCH. Conversely, if the UE has not received an OCC spreading instruction but has received a DCI indicating PUSCH retransmission, if at least one of the retransmitted PUSCHs overlaps with a PUCCH, the UE can multiplex the UCI of the PUCCH to the overlapping PUSCH. Alternatively, and solely, when the OCC spreading method is configured via higher-layer signals and can be dynamically indicated by L1 signals, the UE can always transmit both PUCCH and PUSCH simultaneously, regardless of whether OCC spreading is applied.

[0686] Method 2-5: If the UE has received a DCI indicating OCC spreading and PUSCH retransmission, and at least one of the retransmitted PUSCHs overlaps with a PUCCH, the UE multiplexes the UCI of the PUCCH to the overlapping PUSCH. The UE then allocates the UCI information to the PUSCH by puncturing the data of the PUSCH to which the UCI is multiplexed. In this puncturing method, the UE first allocates the PUSCH data to the PUSCH resource, regardless of whether the UCI is mapped, and then changes the PUSCH data to UCI data for the resource to which the UCI is mapped. Therefore, the base station can demodulate / decode at least some code blocks or transport blocks by performing OCC despreading on multiple data points for which the UCI is not mapped. On the other hand, if OCC spread spectrum is not indicated and the UE receives a DCI indicating repeated PUSCH transmission, and at least one of the repeatedly transmitted PUSCHs overlaps with a PUCCH, the UE multiplexes the UCI of the PUCCH to the overlapping PUSCH, and the UE allocates the UCI information to the PUSCH by rate matching the data of the PUSCH to which the UCI is multiplexed. The rate matching method means that the UE first allocates the UCI mapping to the PUSCH resources, and then sequentially allocates the PUSCH data to areas where no UCI mapping has been allocated.

[0687] Method 2-6: If the UE has already received a DCI indicating OCC spread spectrum and PUSCH retransmission, the UE can schedule itself such that at least one of the retransmitted PUSCHs does not overlap with the PUCCH. (Reference) Figure 30 As an example, when the base station applies the OCC scheme to schedule repeated PUSCH transmissions to the UE (e.g.) Figure 30 As shown), the base station avoids scheduling PUCCHs that overlap with the corresponding PUSCH resources. This occurs when events such as... Figure 30 In the case shown, the UE may treat the situation as an error and may apply at least one of methods 2-1 to 2-5.

[0688] [Third Embodiment]

[0689] The following describes the case where PUCCH and PUSCH repetitive transmissions overlap when the OCC scheme is applied.

[0690] Figure 32 The present invention illustrates the scheduling of PUSCH retransmissions for a UE according to an embodiment of the present disclosure, where the PUSCH retransmissions overlap with the PUCCH retransmissions. Figure 32 Examples of situations in which embodiments of this disclosure apply are shown.

[0691] refer to Figure 32If the first UE repeatedly transmits PUSCH A and the second UE repeatedly transmits PUSCH B, and the resources of the repeatedly transmitted second, third, or fourth PUSCH A overlap with those of the repeatedly transmitted PUCCH A, then the UE will not perform the transmission of the repeatedly transmitted second, third, or fourth PUSCH A. If the PUSCH A repeatedly transmitted by the first UE overlaps with the PUCCH A repeatedly transmitted by the first UE, then the repeated transmission of PUSCH A will not be performed on the overlapping resources.

[0692] Assuming Figure 25 The scheme described is applied to each OCC group. The base station will receive (a1+b1) and -b1 in the first OCC group, b1 and -b1 in the second OCC group, and (a1+b1) and (a1-b1) in the third OCC group. In other words, the second, third, and fourth PUSCH A, which overlap with PUCCH A, are not transmitted, and therefore the a1 signal is not acquired in the corresponding resource areas. Therefore, when the scheme is applied... Figure 25 In the above scheme, the base station will receive (a1+b1) and -b1 in the first OCC group, b1 and -b1 in the second OCC group, and (a1+b1) and (a1-b1) in the third OCC group.

[0693] In the following cases: depending on the implementation of the base station receiver, the PUSCH applied to the OCC sequence during the OCC despreading process is fixed, regardless of whether the corresponding PUSCH is discarded (i.e., the OCC despreading process is performed regardless of whether the PUSCH is discarded). For example, assuming that (a1+b1) and (a1-b1) received in the third OCC group are the first and second received signals, respectively, the base station can fix / define the following process: during the OCC despreading process, execute "((first received signal) + (second received signal)) / 2" or "(first received signal) + (second received signal)" to obtain the a1 signal, and execute "((first received signal) - (second received signal)) / 2" or "(first received signal) - (second received signal)" to obtain the b1 signal. In this case, the base station may not be able to correctly detect the second received signal for (a1+b1) and -b1 received in the first OCC group. Therefore, the UE can apply at least one or a combination of the following methods. The following methods can only be applied to Figure 32 The PUSCH in the context is either a DG PUSCH, or only applies to the case where the PUSCH is a CG PUSCH, or both.

[0694] Method 3-1: When the first UE receives and references... Figure 32The scheduling information shown is the same as or similar to the scheduling information (used for repeated transmission of PUSCH (and / or PUCCH)). Figure 32 In cases where the same / similar scheduling information is repeatedly transmitted as illustrated above, the UE may not transmit PUSCH A belonging to the first OCC group. In other words, if at least one PUSCH within an OCC group is transmitted due to the aforementioned... Figure 32 If a PUSCH is not transmitted for the same reason as illustrated in the example (or for other reasons), the UE may not perform the remaining PUSCH transmission. Other such reasons may include the inability to transmit a PUSCH due to overlap with downlink resources or due to transmit power prioritization.

[0695] Method 3-2: When the first UE receives a signal from... Figure 32 The same or similar scheduling information (for repeated transmission of PUSCH (and / or PUCCH)) Figure 32 In cases where the same / similar scheduling information is repeatedly transmitted as illustrated in the examples, the UE does not perform the transmission of the first PUCCH A. That is, the UE can perform repeated transmissions of the second and third PUCCH A, but not the transmission of the first PUCCH A.

[0696] [Fourth Implementation Plan]

[0697] In the following text, a method is applied in which the UE determines the transmission power of the PUSCH when the UE transmits a PUSCH using the OCC scheme.

[0698] Basically, the UE operates as described in Formula 8 regarding the transmit power of the PUSCH. Furthermore, the transmit power between PUSCHs that are repeatedly transmitting the same data can be the same or different. An example of different transmit powers between PUSCHs could correspond to the case where the UE receives a group common TPC from the base station in the middle of a PUSCH retransmission. In other cases (when the transmit power between PUSCHs is the same), the UE can apply the same transmit power applied to the first PUSCH transmission in the retransmitted PUSCHs to the remaining retransmitted PUSCHs.

[0699] If the UE applies OCC to retransmitted PUSCHs, and the transmit power difference between retransmitted PUSCHs is caused by a group common TPC, the base station receiving node cannot correctly perform OCC despreading.

[0700] Therefore, to address this issue, the UE can determine the transmit power determination unit not through the PUSCH transmission interval unit, but through the OCC group unit when OCC is applied. When referencing... Figure 29As an example, if the UE routinely determines the transmit power value to be changed from the fourth PUSCH via the group common TPC, the above method means that the UE maintains the same transmit power as the third PUSCH until the fourth PUSCH, and applies the changed transmit power starting from the fifth PUSCH.

[0701] [Fifth Embodiment]

[0702] The following describes a method for aligning DMRS symbols from the base station's perspective when the UE sends a PUSCH using the OCC scheme.

[0703] During PUSCH transmission, there are two types of DMRS, depending on the symbol in which the DMRS is located. The first type is DMRS type A, where the DMRS is located in the third or fourth symbol of the time slot, regardless of the start position and length of the PUSCH transmission. The second type is DMRS type B, where the DMRS is always located in the first symbol to which the PUSCH resource is allocated.

[0704] When a base station receives PUSCHs from two different UEs that have applied OCC and overlap in time and frequency resources, the DMRS symbols should at least not overlap with data transmitted by the other UEs. This may require aligning the resource areas where the DMRS resides between UEs. Therefore, when the OCC scheme is applied to PUSCH retransmissions, the UE can always be provided with a DMRS type A configuration to avoid the complexity of aligning DMRS resource areas considering base station scheduling.

[0705] Figure 33 The procedure for performing a PUSCH transfer using an OCC scheme according to an embodiment of this disclosure is illustrated. It is possible to... Figure 33 The methods shown in the flowchart can be modified in various ways. For example, although shown as a series of operations, the various operations in each diagram can overlap, occur in parallel, occur in different orders, or occur multiple times. In other examples, individual operations can be omitted or replaced with other operations.

[0706] refer to Figure 33 In operation 3301, the UE sends a UE capability indicating whether an OCC sequence can be applied in the PUSCH transmission to the base station. The base station receives the UE capability indicating whether an OCC sequence can be applied in the PUSCH transmission from the UE.

[0707] In operation 3303, the base station provides the UE with OCC-related higher-layer signaling information. The base station can provide the UE with OCC-related signal configuration information via higher-layer signals. For example, this could be, but is not limited to, a UE reporting a UE capability indicating that the UE can apply OCC sequences during PUSCH transmission. The UE can receive OCC-related signal configuration information from the base station via higher-layer signals.

[0708] In Operation 3305, the base station can indicate to the UE whether to apply OCC via higher-layer signals and / or L1 signals during PUSCH scheduling. The base station can indicate whether to apply OCC via higher-layer signals and / or L1 signals. The UE can receive the indication regarding the application of OCC from the base station via higher-layer signals and / or L1 signals.

[0709] In operation 3307, the UE can perform PUSCH transmission by applying an OCC scheme determined / indicated by higher-layer signals and / or L1 signals. The UE can apply the OCC scheme, or a combination thereof, of the methods described in the first to fifth embodiments above to perform PUSCH transmission.

[0710] In Operation 3309, the base station performs demodulation / decoding of data for each UE by applying an OCC despreading scheme to the received signals received from multiple UEs.

[0711] In the description of the embodiments of the present disclosure above, reference may be made to the specific details of the operation of the UE and the base station according to the embodiments of the present disclosure above.

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

[0713] refer to Figure 34 The UE may include a transceiver (which collectively refers to UE receiver 3400 and UE transmitter 3410), a memory (not shown), and a UE processor 3405 (or UE controller or processor). The UE transceivers 3400 and 3410, the memory, and the UE processor 3405 can operate according to the communication method described above for the UE. The components of the UE are not limited to the examples described above. For example, the UE may include more or fewer components than those described above. Furthermore, the transceiver, memory, and processor may be implemented as a single chip.

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

[0715] In addition, the transceiver can receive signals, output signals to the processor, and transmit signals output from the processor via the wireless channel.

[0716] The memory can store programs and data required for the operation of the UE. 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 a combination of storage media. Furthermore, the memory can include multiple memories.

[0717] Furthermore, the processor can control a series of processes that enable the UE to operate according to the above embodiments. 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 processor can perform operations controlling the UE's components by executing programs stored in memory.

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

[0719] refer to Figure 35 A base station may include transceivers (which collectively refer to base station receiver 3500 and base station transmitter 3510), a memory (not shown), and a base station processor 3505 (or base station controller or processor). The base station transceivers 3500 and 3510, the memory, and the base station processor 3505 can operate according to the communication method of the base station described above. However, the components of a base station are not limited to the examples described above. For example, a 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.

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

[0721] In addition, the transceiver can receive signals, output signals to the processor, and transmit signals output from the processor via the wireless channel.

[0722] The memory can store programs and data required for the operation of the base station. 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 disk, CD-ROM, and DVD) or a combination of storage media. Furthermore, the memory can include multiple memories.

[0723] 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 components of the base station to configure DCIs in two layers, including allocation information regarding multiple PDSCHs, and transmit the configured DCIs. The processor may include multiple processors, and the processor can perform operations controlling the components of the base station by executing programs stored in memory.

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

[0725] When the method is 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 that cause the electronic device to perform the method as defined by the appended claims and / or as disclosed herein, according to various embodiments of this disclosure.

[0726] 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 optical disc (DVD) or other types of optical storage devices, or magnetic tape cassettes. Alternatively, any combination of some or all of them can form the memory in which the programs are stored. Furthermore, an electronic device may include multiple such memories.

[0727] Furthermore, the program can be stored on an attachable storage device that can be accessed by 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 storage devices can access the electronic device via an external port. Additionally, a separate storage device on a communication network can access portable electronic devices.

[0728] In the detailed embodiments described above, 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 is suitably chosen for the presented situation, and this disclosure is not limited to elements represented in a singular or plural form. Thus, an element represented in a plural form may also include a single element, or an element represented in a singular form may include multiple elements.

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

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

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

[0732] Furthermore, in the methods of this disclosure, some or all of the contents of each embodiment may be combined and implemented without departing from the essential spirit and scope of this disclosure.

[0733] Although this disclosure has been shown and described with reference to various embodiments thereof, those skilled in the art will understand that various changes in form and detail may be made therein without departing from the spirit and scope of this disclosure as defined by the appended claims and their equivalents.

Claims

1. A method performed by a user equipment (UE) in a communication system, the method comprising: Identify the Physical Uplink Shared Channel (PUSCH) transmissions to be sent in the time slot; Identify multiple orthogonal overlay code (OCC) groups corresponding to the PUSCH transmission; as well as The PUSCH transmission is sent in the time slot, the PUSCH transmission having an OCC based on the multiple OCC groups applied. The same redundant version RV value is applied to one of the multiple OCC groups.

2. The method according to claim 1, further comprising: Receive downlink control information (DCI) including PUSCH scheduling information and the RV field. The PUSCH transmission is identified based on the DCI, and The RV value identified based on the RV field is cyclically applied to the multiple OCC groups.

3. The method according to claim 2, further comprising: Receive the first configuration associated with PUSCH repetition and the second configuration associated with OCC length. Wherein, the PUSCH transmission corresponds to the PUSCH repetition, and Where the number of repetitions of the PUSCH is greater than the OCC length, the RV value is applied cyclically to the plurality of OCC groups.

4. The method according to claim 1, wherein, The same RV value is applied to the multiple OCC groups.

5. The method according to claim 1, wherein, The PUSCH transmission is sent in the non-terrestrial network NTN.

6. A user equipment (UE) in a communication system, the UE comprising: transceiver; as well as The processor, connected to the transceiver, is configured to: Identify the Physical Uplink Shared Channel (PUSCH) transmissions to be sent in the time slot; Identify multiple orthogonal overlay code (OCC) groups corresponding to the PUSCH transmission; as well as The PUSCH transmission is sent in the time slot, the PUSCH transmission having an OCC based on the multiple OCC groups applied. The same redundant version RV value is applied to one of the multiple OCC groups.

7. The UE according to claim 6, in, The processor is also configured to receive downlink control information (DCI) including PUSCH scheduling information and an RV field. The PUSCH transmission is identified based on the DCI, and The RV value identified based on the RV field is cyclically applied to the multiple OCC groups.

8. The UE according to claim 7, in, The processor is also configured to receive a first configuration associated with PUSCH repetition and a second configuration associated with OCC length. Wherein, the PUSCH transmission corresponds to the PUSCH repetition, and Where the number of repetitions of the PUSCH is greater than the OCC length, the RV value is applied cyclically to the plurality of OCC groups.

9. The UE according to claim 6, wherein, The same RV value is applied to the multiple OCC groups.

10. The UE according to claim 6, wherein, The PUSCH transmission is sent in the non-terrestrial network NTN.

11. A method performed by a base station in a communication system, the method comprising: Send downlink control information (DCI) that includes physical uplink shared channel (PUSCH) scheduling information; as well as A PUSCH transmission is received in a time slot, the PUSCH transmission having an OCC based on multiple orthogonal coverage code OCC groups corresponding to the PUSCH transmission. The same redundant version RV value is applied to one of the multiple OCC groups.

12. The method according to claim 11, in, The DCI includes the RV field, and The RV value associated with the RV field is applied cyclically to the plurality of OCC groups.

13. The method of claim 12, further comprising: Send the first configuration associated with PUSCH repetition and the second configuration associated with OCC length. Wherein, the PUSCH transmission corresponds to the PUSCH repetition, and Where the number of repetitions of the PUSCH is greater than the OCC length, the RV value is applied cyclically to the plurality of OCC groups.

14. The method according to claim 11, wherein, The same RV value is applied to the multiple OCC groups.

15. A base station in a communication system, the base station comprising: transceiver; as well as The processor, connected to the transceiver, is configured to: Send downlink control information (DCI) that includes physical uplink shared channel (PUSCH) scheduling information; as well as A PUSCH transmission is received in a time slot, the PUSCH transmission having an OCC based on multiple orthogonal coverage code OCC groups corresponding to the PUSCH transmission. The same redundant version RV value is applied to one of the multiple OCC groups.

Images