Method and apparatus for transmitting / receiving data for network cooperative communication

Abstract

The present disclosure relates to a communication technology for converging an IoT technology with a 5G communication system to support a higher data transmission rate beyond a 4G system, and a system therefor. The present disclosure relates to a method and apparatus for performing cooperative communication in a wireless communication system. A method of a terminal of a communication system comprises the steps of: receiving information for a synchronization signal and a physical broadcast channel block (SSB) resource set from a base station, the information comprising an SSB index associated with the SSB resource set; receiving an information SSB associated with the SSB resource set from the base station; identifying a Layer 1 Reference Signal Received Power (L1-RSRP) associated with the SSB; and transmitting, to a base station, channel state information (CSI) related to L1-RSRP, the L1-RSRP being associated with the SSB, where the information includes physical cell identities (PCIs) of the SSBs associated with the SSB resource set, and where each PCI is associated with a corresponding SSB index among the SSB indexes associated with the SSB resource set.

Description

[0001] This application is a divisional application of patent application filed on September 28, 2020, with application number 202080067994.2 and invention title "Method and apparatus for sending / receiving data for network collaborative communication". Technical Field

[0002] This disclosure relates to methods and apparatus for performing communications in a wireless communication system, and more particularly, to methods and apparatus for performing cooperative communications. Background Technology

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

[0004] The Internet, a human-centric network of connections in which humans generate and consume information, is now 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, combining IoT technology and big data processing technology with connections to cloud servers. With technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology becoming necessary for IoT implementation, sensor networks, machine-to-machine (M2M) communication, and machine-type communication have recently been explored. This IoT environment can provide intelligent Internet technology services that create new value for human life by collecting and analyzing data generated from interconnected things. Through the integration and combination of existing information technology (IT) and various industrial applications, IoT can be applied to a wide range of fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

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

[0006] With the development of wireless communication systems as described above, there is a need for data transmission / reception methods for network cooperative communication. Summary of the Invention

[0007] Technical issues

[0008] Based on the above discussion, this disclosure provides a method and apparatus for transmitting and receiving signals between a transmission node and a UE to perform cooperative communication in a wireless communication system.

[0009] Technical solution

[0010] A method for a UE in a communication system according to an embodiment of the present disclosure may include: receiving cell configuration information from a base station associated with a first cell, the cell configuration information including a Transmission Configuration Indicator (TCI) configuration and a Quasi-Co-location (QCL) configuration; identifying a QCL reference antenna port based on the cell configuration information; and receiving a signal from the base station based on a QCL relationship with the identified QCL reference antenna port, wherein the QCL reference antenna port may be identified based on a Synchronization Signal Block (SSB) or Channel State Information Reference Signal (CSI-RS) associated with a second cell.

[0011] According to an embodiment, the first cell and the second cell may correspond to different Physical Cell Identifiers (PCIs).

[0012] According to an embodiment, the TCI configuration or QCL configuration may include information about the Physical Cell Identifier (PCI) corresponding to the second cell, and the QCL reference antenna port may be identified based on the SSB associated with the PCI corresponding to the second cell.

[0013] According to an embodiment, the TCI configuration or QCL configuration may include information about the CSI-RS index associated with the second cell included in the CSI-RS configuration for mobility, and the QCL reference antenna port may be identified based on the CSI-RS corresponding to the CSI-RS index associated with the second cell.

[0014] According to an embodiment, the signal received from the base station may include at least one of a reference signal, data, and a control signal, and the reference signal may include a tracking reference signal (TRS).

[0015] According to an embodiment, the QCL reference antenna port can be identified based on the SSB or CSI-RS associated with the second cell, depending on whether the UE performs inter-cell multi-TRP operations.

[0016] According to the embodiments, whether the UE performs inter-cell multi-TRP operations can be identified based on the UE's capability report or the SSB configuration received from the base station.

[0017] According to an embodiment, the SSB or CSI-RS associated with the second cell can be correlated with a reference signal used for channel state measurement.

[0018] According to an embodiment, the SSB or CSI-RS associated with the second cell may be related to a beam failure detection (BFD) reference signal or a candidate beam detection (CBD) reference signal.

[0019] A method for a base station in a communication system according to an embodiment of the present disclosure may include: sending cell configuration information to a UE, the cell configuration information including a transmission configuration indicator (TCI) configuration and a quasi-co-location (QCL) configuration; and sending a signal to the UE based on a QCL relationship with a QCL reference antenna port identified based on the cell configuration information, wherein the QCL reference antenna port may be identified based on a synchronization signal block (SSB) or channel state information reference signal (CSI-RS) associated with a second cell.

[0020] A UE in a wireless communication system according to an embodiment of the present disclosure may include: a transceiver; and a controller configured to: receive cell configuration information from a base station associated with a first cell, the cell configuration information including a Transmission Configuration Indicator (TCI) configuration and a Quasi-Co-location (QCL) configuration; identify a QCL reference antenna port based on the cell configuration information; and receive signals from the base station based on a QCL relationship with the identified QCL reference antenna port, wherein the QCL reference antenna port may be identified based on a Synchronization Signal Block (SSB) or Channel State Information Reference Signal (CSI-RS) associated with a second cell.

[0021] A base station in a communication system according to an embodiment of the present disclosure may include: a transceiver; and a controller configured to: send cell configuration information to a UE, the cell configuration information including a transmission configuration indicator (TCI) configuration and a quasi-co-location (QCL) configuration, and send signals to the UE based on a QCL relationship with a QCL reference antenna port identified based on the cell configuration information, wherein the QCL reference antenna port may be identified based on a synchronization signal block (SSB) or channel state information reference signal (CSI-RS) associated with a second cell.

[0022] Beneficial effects of the invention

[0023] According to this disclosure, when using network cooperative communication in a wireless communication system, the UE can improve the reliability of transmitted or received data / control signals by repeating transmissions between transmission points, or can increase the transmission capacity of transmitted or received data / control signals by transmitting or receiving them separately (independently) for each transmission point. Attached Figure Description

[0024] Figure 1 The basic time-frequency domain structure of a radio resource area serving as a data or control channel in a 5G system, according to an embodiment of the present disclosure, is shown.

[0025] Figure 2 The structure of frames, subframes, and time slots in a 5G system according to embodiments of the present disclosure is shown;

[0026] Figure 3 The configuration of a BWP in a wireless communication system according to an embodiment of the present disclosure is shown;

[0027] Figure 4 A method for dynamically changing the configuration of a BWP according to embodiments of the present disclosure is shown;

[0028] Figure 5 The control resource set (CORESET) for transmitting downlink control channels in a 5G system according to an embodiment of the present disclosure is shown.

[0029] Figure 6 A PDSCH frequency domain resource allocation method in an NR system according to an embodiment of the present disclosure is illustrated;

[0030] Figure 7 A method for allocating physical downlink shared channel (PDSCH) time-domain resources in a wireless communication system according to an embodiment of the present disclosure is illustrated.

[0031] Figure 8 A time-domain resource allocation method based on the subcarrier spacing of the data channel and the subcarrier spacing of the control channel in a wireless communication system is illustrated according to an embodiment of the present disclosure.

[0032] Figure 9 The radio protocol structure of the base station and the UE is shown according to an embodiment of the present disclosure when performing single-cell, carrier aggregation (CA), dual connectivity (DC);

[0033] Figure 10 A cooperative communication antenna port configuration according to an embodiment of the present disclosure is shown;

[0034] Figure 11 Examples of configuration and indication of TCI status according to embodiments of this disclosure are shown;

[0035] Figure 12 An example of configuring and indicating TCI status according to another embodiment of this disclosure is shown;

[0036] Figure 13 The structure of a MAC CE message for indicating TCI status according to an embodiment of the present disclosure is shown;

[0037] Figure 14 An example of configuring the serving cell and the cell identifier per TRP according to an embodiment of this disclosure is shown;

[0038] Figure 15 Examples of methods for configuring and instructing TCI / QCL for inter-cell multiple TRP operations are shown according to embodiments of the present disclosure;

[0039] Figure 16 Another example of configuring and instructing a method for inter-cell multiple TRP operations is shown according to embodiments of the present disclosure;

[0040] Figure 17 Intra-cell multiple TRP operations and inter-cell multiple TRP operations according to embodiments of the present disclosure are illustrated;

[0041] Figure 18 This is a block diagram illustrating the structure of a UE according to an embodiment of the present disclosure; and

[0042] Figure 19 This is a block diagram illustrating the structure of a base station according to an embodiment of the present disclosure. Detailed Implementation

[0043] In the following, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0044] In describing embodiments of this disclosure, descriptions related to techniques well-known in the art and not directly associated with this disclosure will be omitted. Unnecessary descriptions are omitted to prevent obscuring the main ideas of this disclosure and to more clearly convey them.

[0045] For the same reason, some elements may be exaggerated, omitted, or shown schematically in the accompanying drawings. Furthermore, the size of each element does not perfectly reflect its actual size. In the drawings, identical or corresponding elements have the same reference numerals.

[0046] The advantages and features of this disclosure, as well as the ways in which they are implemented, will become apparent from the embodiments described in detail below with reference to the accompanying drawings. However, this disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are provided only to fully disclose this disclosure and to inform those skilled in the art of its scope, and this disclosure is limited only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals denote the same or similar elements.

[0047] In this document, it will be understood that each box in a flowchart illustration, and combinations of boxes 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 boxes. These computer program instructions can also be stored in a computer-usable or computer-readable storage medium that can direct a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-usable or computer-readable storage medium produce an article of writing including instruction means that implement the functions specified in one or more flowchart boxes. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus, thereby producing a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowchart boxes.

[0048] Furthermore, each box in the flowchart diagram can represent a module, segment, or code section, 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 mentioned in the boxes may not appear in a specific order. For example, depending on the functions involved, two boxes shown consecutively may actually execute substantially simultaneously, or these boxes may sometimes execute in reverse order.

[0049] As used herein, "cell" refers to a software or hardware element that performs a predetermined function, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC). However, "cell" is not always limited to software or hardware. A "cell" can be configured to be stored in addressable memory or to execute one or more processors. Thus, a "cell" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. Elements and functions provided by a "cell" can be combined into a smaller number of elements or "cells," or divided into a larger number of elements or "cells." Furthermore, elements and "cells" may be implemented as replicas of one or more CPUs within a device or secure multimedia card. Additionally, a "cell" in an embodiment may include one or more processors.

[0050] In the following description, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the following description of the present disclosure, descriptions of known functions or configurations incorporated herein will be omitted where it is determined that a detailed description would unnecessarily obscure the subject matter of the disclosure. The terminology described below is defined in consideration of the functions in the present disclosure and may vary depending on the user, the user's intent, or habit. Therefore, the definitions of terms should be based on the entire contents of the specification. In the following description, a base station is an entity that allocates resources to a terminal and may be at least one of a gNode B, eNode B, Node B, base station (BS), radio access unit, base station controller, and a node on a network. A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Of course, examples of base stations and terminals are not limited thereto. The following description of the present disclosure pertains to techniques for receiving broadcast information from a base station by a terminal in a wireless communication system. The present disclosure relates to communication technologies and systems for integrating IoT technologies with 5G (fifth generation) communication systems designed to support higher data transmission rates than 4G (fourth generation) systems. This disclosure can be applied to smart services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail commerce, security and safety-related services, etc.) based on 5G communication technology and IoT-related technologies.

[0051] In the following description, for convenience, terms referring to broadcast information, terms referring to control information, terms relating to communication coverage, terms referring to state changes (e.g., events), terms referring to network entities, terms referring to messages, terms referring to device elements, etc., are used illustratively. Therefore, this disclosure is not limited to the terms used below, and other terms referring to subjects with equivalent technical meanings may be used.

[0052] In the following description, for ease of description, terms and names defined in the 3GPP LTE standard may be used. However, this disclosure is not limited to these terms and names and may be applied in the same manner to systems conforming to other standards.

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

[0054] As a representative example of a broadband wireless communication system, the LTE system employs Orthogonal Frequency Division Multiplexing (OFDM) for the downlink (DL) and Single-Carrier Frequency Division Multiple Access (SC-FDMA) for 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 an eNodeB or Base Station (BS), while the downlink refers to the radio link through which the eNodeB transmits data or control signals to the UE. These multiple access schemes allocate and manage time-frequency resources used to carry data or control information for each user, ensuring they do not overlap, i.e., they are orthogonal to each other, thus dividing the data or control information for each user.

[0055] Post-LTE communication systems, namely 5G communication systems, need to be able to freely reflect various demands from users and service providers, and therefore need to support services that meet these diverse needs. Services considered for 5G communication systems include enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC).

[0056] According to some embodiments, eMBB aims to provide data rates that are further increased than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, for a base station, eMBB needs to be able to provide a peak data rate of 20Gbps in the downlink and a peak data rate of 10Gbps in the uplink. Furthermore, eMBB needs to provide increased user-aware data rates. To meet these requirements, improved transmit and receive technologies are needed, including enhanced multiple-input multiple-output (MIMO) transmission technologies. Additionally, the data rates required by 5G communication systems can be met by using a wider frequency bandwidth than 20MHz in a frequency band ranging from 3GHz to 6GHz, or a frequency band of 6GHz or higher, instead of the 2GHz frequency band currently used for LTE.

[0057] In 5G communication systems, mMTC is considered for supporting application services such as the Internet of Things (IoT). To effectively deliver IoT, mMTC may need to support a large number of UEs within a cell, enhance UE coverage, increase battery life, and reduce UE costs. IoT attaches to various sensors and devices to provide communication capabilities, thus requiring the ability to support a large number of UEs within a cell (e.g., 1,000,000 UEs / km²). Due to the nature of the service, UEs supporting mMTC are likely to be located in shadowed areas not covered by the cell, such as basements of buildings, and therefore may require wider coverage than other services provided by 5G communication systems. UEs supporting mMTC need to be configured as low-cost UEs and may require very long battery life because it is difficult to frequently replace UE batteries.

[0058] Finally, URLLC is a cellular-based mission-critical wireless communication service used for remote control of robots or machines, industrial automation, drones, telemedicine, emergency alerts, etc., and requires ultra-low latency and ultra-reliable communication. For example, services supporting URLLC not only need to meet air interface latency of less than 0.5 milliseconds, but also need to have a packet error rate of 10⁻⁵ or lower. Therefore, for services supporting URLLC, 5G systems need to provide shorter transmission time intervals (TTIs) than other services, and also require designs for allocating wide resources in the frequency band. The aforementioned mMTC, URLLC, and eMBB are merely examples of different service types, and the types of services to which this disclosure applies are not limited to the aforementioned examples.

[0059] The aforementioned services considered in 5G communication systems need to be provided in an integrated manner within a unified framework. That is, for efficient resource management and control, it is preferable to control and deliver services as an integrated system rather than operating them independently.

[0060] In the following description, although embodiments are illustrated by reference to LTE, LTE-A, LTE Pro, or NR systems, these embodiments can also be applied to other communication systems with similar technical backgrounds or channel configurations. Furthermore, with modifications, the embodiments can also be applied to other communication systems without departing from the scope of this disclosure as determined by those skilled in the art.

[0061] This disclosure relates to methods and apparatus for transmitting data and control signals between multiple transmission nodes and a UE performing cooperative communication to improve communication reliability.

[0062] According to this disclosure, when using network cooperative communication in a wireless communication system, the UE can improve the reliability of transmitted or received data / control signals by repeating transmissions between transmission points, or can increase the transmission capacity of transmitted or received data / control signals by transmitting them individually (independently) for each transmission point.

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

[0064] Figure 1 The transmission structure in the time-frequency domain of an LTE system, LTE-A system, NR system, or similar wireless communication system is shown.

[0065] Figure 1 The basic time-frequency domain structure of the radio resource area, which serves as a data or control channel in a 5G system, is shown.

[0066] exist Figure 1 In the diagram, the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The basic unit of resources in the time-frequency domain is the resource element (RE) 1-01, which can be defined by an orthogonal frequency division multiplexing (OFDM) symbol 1-02 on the time axis and a subcarrier 1-03 on the frequency axis. In the frequency domain, One (e.g., 12) consecutive REs can form a resource block (RB) 1-04.

[0067] Figure 2 The structure of frames, subframes, and time slots in a 5G system is shown.

[0068] Figure 2 An example of the structure of frame 2-00, subframe 2-01, and time slot 2-02 is shown. A frame 2-00 can be defined as 10 ms. A subframe 2-01 can be defined as 1 ms. Therefore, a frame 2-00 can include a total of ten subframes 2-01. Time slots 2-02 and 2-03 can be defined as 14 OFDM symbols (i.e., the number of symbols per time slot). A subframe 2-01 may include one or more time slots 2-02 and 2-03, and the number of time slots 2-02 and 2-03 in each subframe 2-01 may vary depending on the set subcarrier spacing values ​​μ2-04 and μ2-05.

[0069] exist Figure 2 In the example, the subcarrier spacing values ​​are set as μ = 0 (2-04) and μ = 1 (2-05). When μ = 0 (2-04), one subframe 2-01 can include one time slot 2-02; when μ = 1 (2-05), one subframe 2-01 can include two time slots 2-03. That is, the number of time slots per subframe... It can vary according to the set subcarrier spacing value μ, and the number of time slots per frame. It can be changed accordingly. μ is set according to each subcarrier interval. and It can be defined as shown in Table 1.

[0070] [Table 1]

[0071]

[0072] In NR, a component carrier (CC) or serving cell can include up to 250 RBs. Therefore, when the UE always receives the entire serving cell bandwidth as in LTE, the UE's power consumption can be extremely high. To address this issue, the base station can configure one or more bandwidth portions (BWPs) for the UE, allowing the UE to change the reception area within the cell.

[0073] In NR, the base station can configure an initial BWP for the UE via the Master Information Block (MIB), which is the bandwidth of CORESET#0 (or Common Search Space: CSS). Subsequently, the base station can configure a first BWP for the UE via RRC signaling and can report at least one BWP configuration message, which can be indicated in the future via Downlink Control Information (DCI). The base station can report the BWPID via DCI, thereby indicating the frequency band available to the UE. If the UE fails to receive DCI in the currently allocated BWP for a specified time or longer, the UE returns to the default BWP and attempts to receive DCI.

[0074] Figure 3 The configuration of a BWP in a wireless communication system according to an embodiment is shown.

[0075] refer to Figure 3The UE bandwidth 3-00 can include two BWPs, namely BWP#1 3-05 and BWP#2 3-10. The base station can configure one or more BWPs for the UE and can configure information about each BWP, as shown in Table 2 below.

[0076] [Table 2]

[0077]

[0078]

[0079] In addition to the configuration information shown in Table 2, various parameters related to the BWP can be configured for the UE. This information can be sent from the base station to the UE via higher-layer signaling (e.g., RRC signaling). One or more configured BWPs can be activated. The activation of a configured BWP can be indicated from the base station to the UE semi-statically via RRC signaling or dynamically via the MAC control unit (CE) or DCI.

[0080] The BWP configuration supported by 5G communication systems can be used for a variety of purposes.

[0081] In one example, when the bandwidth supported by the UE is less than the system bandwidth, the BWP can be configured to support the bandwidth supported by the UE. For example, the frequency position of the BWP in Table 2 (Configuration Information 2) can be set for the UE, enabling the UE to send and receive data at a specific frequency position within the system bandwidth.

[0082] In another example, the base station can configure multiple BWPs for the UE to support different parameter sets. For instance, to support a random UE transmitting and receiving data using both 15kHz and 30kHz subcarrier intervals, two BWPs can be configured to use 15kHz and 30kHz subcarrier intervals respectively. Different BWPs can withstand frequency division multiplexing (FDM). When the UE intends to transmit and receive data with a specific subcarrier interval, the BWP configured with that subcarrier interval can be activated.

[0083] In another example, the base station can configure a BWP with a different bandwidth for the UE to reduce the UE's power consumption. For instance, when the UE supports a very large bandwidth (e.g., 100MHz) and always transmits and receives data within that bandwidth, the UE may consume a lot of power. Specifically, the UE unnecessarily monitors the downlink control channel over a large 100MHz bandwidth even when there is no service, which is very inefficient in terms of power consumption. Therefore, to reduce the UE's power consumption, the base station can configure the UE with a BWP with a relatively small bandwidth, such as a 20MHz BWP. The UE can perform monitoring operations in the 20MHz BWP when there is no service, and when data is generated, the UE can transmit and receive data using the 100MHz bandwidth according to instructions from the base station.

[0084] Figure 4 A method for dynamically changing the configuration of a BWP according to an embodiment of this disclosure is shown.

[0085] refer to Figure 4 As shown in Table 2, the base station can configure one or more BWPs for the UE, and can report information about the bandwidth, frequency location, and parameter set of each BWP to the UE as the configuration for each BWP. Figure 4 As shown, for a UE, which two BWPs are configured as BPW#1 4-05 and BWP#2 4-10 in UE bandwidth 4-00? One or more configured BWPs can be activated, and Figure 4 An example of activating a BWP is shown. In the configured BWP, BWP#1 4-02 is activated in time slot #0 4-25, and the UE can monitor the Physical Downlink Control Channel (PDCCH) in control area 1 4-45 configured in BWP#1 4-05, and can send and receive data 4-55 in BWP#1 4-05. The control area for the UE to receive the PDCCH can vary depending on which BWP is activated in the configured BWP, therefore the bandwidth for the UE to monitor the PDCCH can vary.

[0086] The base station can also send an indicator to the UE for switching the configuration of a BWP. Here, the configuration for switching the BWP can be considered the same as activating a specific BWP (e.g., switching the active BWP from BWP A to BWP B). The base station can send the configuration switching indicator to the UE in a specific time slot. After receiving the configuration switching indicator from the base station, the UE can determine the BWP to activate by applying the changed configuration based on the configuration switching indicator from the specific time slot. Furthermore, the UE can monitor the PDCCH in the control area configured in the activated BWP.

[0087] exist Figure 4In this process, the base station can send a configuration handover indicator 4-15 to the UE in time slot #1 4-30, indicating that the activated BWP is switching from the existing BWP #1 4-05 to BWP #2 4-10. Upon receiving the indicator, the UE can activate BWP #2 6-10 according to its content. Here, a transition time of 4-20 may be required for the BWP handover, and the timing of the handover and application of the activated BWP can be determined accordingly. Figure 4 In the process, after receiving the configuration switching indicator 4-15, a transition time of one time slot 4-20 is required. Data transmission and reception may not be performed during the transition time 4-20 (4-60). Therefore, BWP#2 4-10 can be activated in time slot #2 4-35, and thus control channels and data can be transmitted and received via this BWP.

[0088] The base station can pre-configure one or more BWPs for the UE via higher-layer signaling (e.g., RRC signaling), and can indicate activation by mapping configuration switching indicators 4-15 to one of the base station's pre-configured BWP configurations. For example, a log2N bit indicator can indicate the selection of a BWP from N pre-configured BWPs. Table 3 shows an example of using two-bit indicators to indicate configuration information about a BWP.

[0089] [Table 3]

[0090] Indicator value BWP Configuration 00 Bandwidth configuration A via higher layer signaling 01 Bandwidth configuration B configured via higher-layer signaling 10 Bandwidth configuration C via higher-layer signaling 11 Bandwidth configuration D via higher-layer signaling

[0091] The configuration switching indicators 4-15 for BWP shown in Table 4 can be sent from the base station to the UE via Media Access Control (MAC) Control Element (CE) signaling or L1 signaling (e.g., public DCI, group public DCI, or UE-specific DCI).

[0092] The timing for applying BWP activation according to the configuration handover indicator 4-15 for BWP shown in Table 4 above can depend on the following. The timing for applying the configuration handover can depend on a predefined value (e.g., applying the configuration handover after N (≥1) time slots since receiving the configuration handover indicator), can be set by the base station for the UE via higher-layer signaling (e.g., RRC signaling), or can be sent via the configuration handover indicator 4-15. Furthermore, the timing for applying the configuration handover can be determined by combining the above methods. After receiving the configuration handover indicator 4-15 for BWP, the UE can begin applying the handover configuration from the time obtained through the above methods.

[0093] Figure 5 A control resource set (CORESET) for transmitting downlink control channels in a 5G system according to an embodiment of the present disclosure is shown.

[0094] refer to Figure 5 In this embodiment, UE BWP 5-10 can be configured on the frequency axis, and two control resource sets (control resource set #1 5-01 and control resource set #2 5-02) can be configured in a time slot 5-20 on the time axis. Control resource sets 5-01 and 5-02 can be configured in a specific frequency resource 5-03 within the entire UE BWP 5-10 on the frequency axis. Control resource sets 5-01 and 5-02 can be configured with one or more OFDM symbols on the time axis, which can be defined as a control area set duration 5-04. Figure 5 In the example, control resource set #1 5-01 is configured with a control resource set duration of two symbols, and control resource set #2 5-02 is configured with a control resource set duration of one symbol.

[0095] In the aforementioned 5G system, the control resource set can be configured for the UE by the base station via higher-layer signaling (e.g., system information, Master Information Block (MIB), or Radio Resource Control (RRC) signaling). Configuring the control resource set for the UE means providing the UE with information such as the identifier of the control resource set, the frequency location of the control resource set, and the symbol duration of the control resource set. For example, the information used to configure the control resource set for the UE may include multiple pieces of information as shown in Table 4.

[0096] [Table 4]

[0097]

[0098]

[0099] In Table 4, the tci-StatesPDCCH (TCI state for short) configuration information may include information about the index of one or more Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) blocks (referred to as SSB or SS / PBCH blocks) that have a quasi-co-address (QCL) relationship with the Demodulation Reference Signal (DMRS) transmitted in the Control Resource Set, or the index of the Channel State Information Reference Signal (CSI-RS).

[0100] In a wireless communication system, one or more different antenna ports (which may be replaced by one or more channels, signals and combinations thereof, but for convenience, the term "different antenna ports" will be used throughout the following description of this disclosure) can be associated with each other through the following QCL configuration.

[0101]

[0102] Specifically, the QCL configuration can associate two different antenna ports through a relationship between a (QCL) target antenna port and a (QCL) reference antenna port. When receiving the target antenna port, the UE can apply all or some of the statistical characteristics of the channel measured at the reference antenna port (e.g., large-scale parameters of the channel or the UE's receive or transmit spatial filter coefficients, such as Doppler shift, Doppler spread, average delay, delay spread, average gain, and spatial Rx (or Tx) parameters). Here, the target antenna port refers to the antenna port that transmits a channel or signal configured by a higher-layer configuration including the QCL configuration, or the antenna port that transmits a channel or signal with a TCI state indicating the QCL configuration applied. The reference antenna port refers to the antenna port that transmits a channel or signal indicated (specified) by the referenceSignal parameter in the QCL configuration.

[0103] Specifically, the statistical characteristics of a channel defined by the QCL configuration (indicated by the qcl-Type parameter in the QCL configuration) can be classified according to the following QCL types.

[0104] o 'QCL-TypeA': {Doppler frequency shift, Doppler spread, average delay, delay spread}

[0105] o 'QCL-TypeB': {Doppler frequency shift, Doppler spread}

[0106] o 'QCL-TypeC': {Doppler shift, average delay}

[0107] o 'QCL-TypeD': {space Rx parameter}

[0108] QCL types are not limited to the four types mentioned above, but to avoid confusion, not all possible combinations are listed. QCL-Type A is the QCL type used when the bandwidth and transmission time of the target antenna port are sufficient compared to the reference antenna port, and all measurable statistical characteristics on the frequency and time axes are available for reference (i.e., when the sample count and transmission bandwidth / time of the target antenna port are greater than those of the reference antenna port on both the frequency and time axes). QCL-Type B is the QCL type used when the bandwidth of the target antenna port is sufficient to measure the measurable statistical characteristics on the frequency axis (i.e., Doppler shift and Doppler spread). QCL-Type C is the QCL type used when the bandwidth and transmission time of the target antenna port are insufficient to measure second-order statistics (i.e., Doppler spread and delay spread), and therefore only first-order statistics (i.e., Doppler offset and average delay) are available for reference. QCL-Type D is the QCL type configured such that the spatial Rx filter value used when receiving the reference antenna port can be used when receiving the target antenna port.

[0109] The base station can be configured to use the following TCI states to indicate a single target antenna port configuration or to indicate up to two QCL configurations.

[0110]

[0111] In a TCI state configuration, the first QCL configuration can be configured as one of QCL-TypeA, QCL-TypeB, and QCL-TypeC. The configurable QCL type is specified based on the types of the target antenna port and the reference antenna port, which will be described in detail below. The second QCL configuration in a TCI state configuration can be configured as QCL-TypeD, and in some cases, it can be omitted.

[0112] Tables 4-1 to 4-5 show the valid TCI state configurations based on the target antenna port type.

[0113] Table 4-1 shows the valid TCI state configurations when the target antenna port is a CSI-RS (or Tracking Reference Signal: TRS) used for tracking. TRS refers to a CSI-RS without configured repeat parameters and where trs-Info is configured as a true NZP CSI-RS. In Table 4-1, configuration 3 can be used for aperiodic TRS.

[0114] Effective TCI State Configuration when the target antenna port is a CSI-RS (TRS) for tracking

[0115]

[0116] Table 4-2 shows the valid TCI state configuration when the target antenna port is a CSI-RS for CSI. A CSI-RS for CSI refers to an NZP CSI-RS in which no duplicate parameters are configured and trs-Info is not configured as true.

[0117] Effective TCI State Configuration when the target antenna port is a CSI-RS (TRS) for tracking

[0118]

[0119] Table 4-3 shows the valid TCI status configuration when the target antenna port is a CSI-RS for beam management (BM, equivalent to a CSI-RS for L1 RSRP reporting). A CSI-RS for BM refers to an NZP CSI-RS where the repeat parameter in the CSI-RS is configured to on or off and trs-Info is not configured to true.

[0120] Effective TCI State Configuration when the target antenna port is a CSI-RS for BM (for L1 RSRP reporting).

[0121]

[0122] Table 4-4 shows the valid TCI state configurations when the target antenna port is a PDCCH DMRS. Valid TCI State Configurations when the Target Antenna Port is a PDCCH DMRS

[0123]

[0124] Table 4-5 shows the valid TCI state configurations when the target antenna port is a PDSCH DMRS. Valid TCI State Configurations when the Target Antenna Port is a PDSCH DMRS

[0125]

[0126] According to the representative QCL configuration methods in Tables 4-1 to 4-5, the target antenna port and reference antenna port are configured as "SSB" → "TRS" → "CSI-RS for CSI, CSI-RS for BM, PDCCH DMRS, or PDSCHDMRS" at each stage, and then operated accordingly. Therefore, statistical characteristics measurable from SSB and TRS can be linked to each antenna port, thereby aiding in the terminal's reception operation.

[0127] The following section describes a method for allocating time and frequency resources for data transmission in an NR system.

[0128] In addition to the frequency domain resource candidate allocation indicated by BWP, the NR system can also provide the following specific frequency domain resource allocations (FD-RA).

[0129] Figure 6 A PDSCH frequency domain resource allocation method in an NR system according to an embodiment of the present disclosure is illustrated.

[0130] refer to Figure 6 In NR systems, frequency domain resource allocation methods can include Type 06-00, Type 16-05, and dynamic switching 6-10, which can be configured by higher layers.

[0131] When the UE is configured via higher-layer signaling to use only resource type 0 (6-00), some downlink control information (DCI) used to allocate PDSCH to the UE has a bitmap with NRBG bits, the conditions of which will be described later. Here, NRBG represents the number of resource block groups (RBGs) determined by the BWP size allocated by the BWP indicator and the higher-layer parameter rbg-Size, as well as the RBG phase indicated by 1 in the bitmap, as determined in Table 5, and data is transmitted on the RBG indicated by 1 according to the bitmap.

[0132] [Table 5]

[0133] Bandwidth portion size Configuration 1 Configuration 2 1-36 2 4 37-72 4 8 73-144 8 16 145-275 16 16

[0134] When the UE is configured via higher-layer signaling to use only resource type 16-05, some DCIs used to allocate PDSCH to the UE have The frequency domain resource allocation information for the bits will be described later. This information allows the base station to configure the starting VRB 6-20 and the length of the frequency domain resources continuously allocated from it, which is 6-25.

[0135] When a UE is configured via higher-layer signaling to use both resource type 0 and resource type 1 (6-10), some DCIs used to allocate PDSCH to the UE contain frequency domain resource allocation information, specifically bits 6-15 for configuring payload 0 and bits 6-20 and 6-25 for configuring payload 1, with the larger value being 6-35. The conditions for this will be described later. Here, a bit can be added to the most significant bit (MSB) of the frequency domain resource allocation information in the DCI, where a bit equal to 0 indicates the use of resource type 0, and a bit equal to 1 indicates the use of resource type 1.

[0136] Figure 7A method for allocating physical downlink shared channel (PDSCH) time-domain resources in a wireless communication system according to an embodiment of the present disclosure is illustrated.

[0137] refer to Figure 7 The base station can determine the subcarrier spacing (μ) of the data channel and control channel by using higher-layer configuration. PDSCH ,μ PDCCH The time-domain location of the PDSCH resource is indicated by the start position 7-00 and length 7-05 of the OFDM symbol in the time slot indicated by the scheduling offset (K0) value and the DCI dynamic indication.

[0138] Figure 8 A time-domain resource allocation method based on the subcarrier spacing of a data channel and the subcarrier spacing of a control channel in a wireless communication system is illustrated according to an embodiment of the present disclosure.

[0139] Reference Figure 8 When the data channel and control channel have the same subcarrier spacing (8-00, μ) PDSCH =μ PDCCH When the data time slot number and the control time slot number are the same, the base station and the UE recognize that the scheduling offset occurs according to the predetermined time slot offset K0.

[0140] When the subcarrier spacing of the data channel and the subcarrier spacing of the control channel are different (8-05, μ) PDSCH ≠μP DCCH) Since the data time slot number and the control time slot number are different, the base station and the UE identify the scheduling offset based on the subcarrier interval of the PDCCH, which occurs according to the predetermined time slot offset K0.

[0141] In NR systems, various types of DCI formats, as shown in Table 6, are provided for efficient control channel reception by the UE, depending on the purpose.

[0142] [Table 6]

[0143]

[0144] For example, a base station can use DCI format 0_0 or DCI format 0_1 ​​to schedule PDSCH for a cell.

[0145] When transmitted together with a CRC scrambled with a Cell Radio Network Temporary Identifier (C-RNTI), a configured Scheduled RNTI (CS-RNTI), or a new RNTI, DCI format 0_1 ​​includes at least the following information.

[0146] -DCI format identifier (1 bit): DCI format indicator, always set to 1.

[0147] -Frequency domain resource allocation (NRBG Bit or (Bit): Indicates frequency domain resource allocation. When DCI format 1_0 is monitored in the UE-specific search space, It is the size of the active DL BWP; otherwise, This is the initial DL BWP size. N RBG This refers to the number of resource block groups. The detailed method was explained in the aforementioned section on frequency domain resource allocation.

[0148] - Time-domain resource allocation (0 to 4 bits): Indicates the allocation of time-domain resources according to the above description.

[0149] -VRB to PRB mapping (1 bit): 0 indicates a non-interleaved VRP to PRB mapping, and 1 indicates an interleaved VRP to PRB mapping.

[0150] - Modulation and coding scheme (5 bits): Indicates the modulation order and coding rate used for PDSCH transmission.

[0151] - New Data Indicator (1 bit): Indicates whether the PDSCH corresponds to the initial transmission or a retransmission based on the toggling indication.

[0152] - Redundant version (2 bits): Indicates the redundant version used for PDSCH transmission.

[0153] -HARQ process number (4 bits): Indicates the HARQ process number used for PDSCH transmission.

[0154] - Downlink Dispatch Index (DAI) (2 bits): DAI indicator.

[0155] - TPC command (2 bits) for scheduling PUCCH: PUCCH power control indicator.

[0156] -PUCCH Resource Indicator (3 bits): The PUCCH resource indicator indicates one of eight resources configured via a higher layer.

[0157] -PDSCH-to-HARQ_feedback timing indicator (3 bits): HARQ feedback timing indicator, indicating one of eight feedback timing offsets configured by a higher layer.

[0158] When transmitted together with a CRC scrambled with a Cell Radio Network Temporary Identifier (C-RNTI), a configured Scheduled RNTI (CS-RNTI), or a new RNTI, DCI Format 1_1 includes at least the following information.

[0159] -DCI format identifier (1 bit): DCI format indicator, always set to 1.

[0160] - Carrier indicator (0 or 3 bits): Indicates the CC (or cell) transmitting the PDSCH assigned by the DCI.

[0161] - Bandwidth Part Indicator (0, 1, or 2 bits): Indicates the BWP for sending the PDSCH allocated by the DCI.

[0162] - Frequency domain resource allocation (the payload is determined based on the aforementioned frequency domain resource allocation): indicates the frequency domain resource allocation. This refers to the size of the active DL BWP. The detailed method was explained in the aforementioned frequency domain resource allocation section.

[0163] - Time-domain resource allocation (0 to 4 bits): Indicates the allocation of time-domain resources according to the above description.

[0164] -VRB to PRB mapping (0 or 1 bit): 0 indicates a non-interleaved VRP to PRB mapping, and 1 indicates an interleaved VRP to PRB mapping. This information is 0 bits when the frequency domain resource allocation is set to resource type 0.

[0165] -PRB Bundle Size Indicator (0 or 1 bit): This information is 0 bits when the higher-level parameter prb-BundlingType is not set or is set to "static"; this information is 1 bit when the higher-level parameter prb-BundlingType is set to "dynamic".

[0166] - Rate Matching Indicator (0, 1, or 2 bits): Indicates the rate matching mode.

[0167] -ZP CSI-RS trigger (0, 1, or 2 bits): Indicator that triggers a non-periodic ZP CSI-RS.

[0168] For transport block 1:

[0169] - Modulation and coding scheme (5 bits): Indicates the modulation order and coding rate used for PDSCH transmission.

[0170] - New Data Indicator (1 bit): Indicates whether the PDSCH corresponds to the initial transmission or a retransmission based on the toggling indication.

[0171] - Redundant version (2 bits): Indicates the redundant version used for PDSCH transmission.

[0172] -For transport block 2:

[0173] - Modulation and coding scheme (5 bits): Indicates the modulation order and coding rate used for PDSCH transmission.

[0174] - New Data Indicator (1 bit): Indicates whether the PDSCH corresponds to the initial transmission or a retransmission based on the toggling indication.

[0175] - Redundant version (2 bits): Indicates the redundant version used for PDSCH transmission.

[0176] -HARQ process number (4 bits): Indicates the HARQ process number used for PDSCH transmission.

[0177] - Downlink dispatch index (0, 2, or 4 bits): DAI indicator.

[0178] - TPC command (2 bits) for scheduling PUCCH: PUCCH power control indicator.

[0179] -PUCCH Resource Indicator (3 bits): The PUCCH resource indicator indicates one of eight resources configured via a higher layer.

[0180] -PDSCH-to-HARQ_feedback timing indicator (3 bits): HARQ feedback timing indicator, indicating one of eight feedback timing offsets configured by a higher layer.

[0181] - Antenna port (4, 5, or 6 bits): Indicates the DMRS port and the CDM group without data.

[0182] -Transmission Configuration Indicator (0 or 3 bits): TCI indicator.

[0183] -SRS Request (2 or 3 bits): SRS transmission request indicator.

[0184] -CBG transmission information (0, 2, 4, 6, or 8 bits): An indicator that indicates whether a code block group in the allocated PDSCH has been transmitted. 0 indicates that the CBG has not been transmitted, and 1 indicates that the CBG has been transmitted.

[0185] -CBG flushing information (0 or 1 bit): An indicator of whether a previous CBG was contaminated. 0 indicates that the CBG may have been contaminated, and 1 indicates that the CBG can be reassembled during retransmission reception.

[0186] -DMRS sequence initialization (0 or 1 bit): DMRS scrambling ID selection indicator.

[0187] The UE can receive up to 4 DCIs of different sizes per time slot in the cell. The UE can receive up to 3 DCIs of different sizes scrambled with C-RNTI per time slot in the cell.

[0188] Antenna port indication can be indicated using Tables 7 to 10.

[0189] [Table 7] Antenna Ports (1000+DMRS Ports), dmrs-Type = 1, maxLength = 1

[0190]

[0191] [Table 8] Antenna Ports (1000+DMRS Ports), dmrs-Type = 1, maxLength = 2

[0192]

[0193] [Table 9] Antenna ports (1000+DMRS ports), dmrs-Type = 2, maxLength = 1

[0194]

[0195] [Table 10] Antenna ports (1000+DMRS ports), dmrs-Type = 2, maxLength = 2

[0196]

[0197] The DMRS ports used are indicated using Table 7 when dmrs-type is 1 and maxLength is 1; Table 8 when dmrs-type is 1 and maxLength is 2; Table 9 when dmrs-type is 2 and maxLength is 1; and Table 10 when dmrs-type is 2 and maxLength is 2. In the tables, the numbers 1, 2, and 3 for DMRS CDM groups without data refer to CDMR groups {0}, {0, 1}, and {0, 1, 2}, respectively. DMRS ports are arranged sequentially according to the index of the port used. Antenna ports are indicated by DMRS port + 1000. As shown in Tables 11 and 12, the DMRS CDM groups are associated with the methods used to generate the DMRS sequence and antenna ports. Table 11 shows the parameters when using dmrs-type = 1, and Table 12 shows the parameters when using dmrs-type = 2.

[0198] [Table 11] Parameters for PDSCH DM-RS dmrs-type=1

[0199]

[0200] [Table 12] Parameters for PDSCH DM-RS dmrs-type=2

[0201]

[0202] The DMRS sequence based on the parameters can be determined by Equation 1.

[0203]

[0204] When only one codeword is enabled in Tables 7 and 8, rows 2, 9, 10, 11, and 30 can be used for single-user MIMO only. That is, the UE cannot assume that different UEs are co-scheduled and cannot perform multi-user MIMO receive operations such as multi-user interference cancellation, zeroing, or whitening operations.

[0205] When only one codeword is enabled in Tables 9 and 10, rows 2, 10, and 23 can be used only for single-user MIMO. That is, the UE may not perform multi-user MIMO receive operations, such as multi-user interference cancellation, zeroing, or whitening, and does not assume that different UEs are co-scheduled.

[0206] Figure 9 The radio protocol structure of the base station and the UE is illustrated according to an embodiment of the present disclosure when performing single-cell, carrier aggregation (CA), dual connectivity (DC).

[0207] refer to Figure 9 The radio protocols of the NR system may include NR Service Data Adaptation Protocol (SDAP) 9-25 and 9-70, NR Packet Data Convergence Protocol (PDCP) 9-30 and 9-65, NR Radio Link Control (RLC) 9-35 and 9-60, and NR Media Access Control (MAC) 9-40 and 9-55, which are located at the UE and NR base station, respectively.

[0208] The main functions of NR SDAP 9-25 and 9-70 may include at least some of the following functions.

[0209] -Transmission of user plane data

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

[0211] - Mark QoS flow IDs in both DL and UL groups

[0212] - UL SDAP PDU reflection QoS flow to DRB mapping

[0213] Regarding SDAP layer devices, the UE can receive configuration via RRC messages regarding whether to use the SDAP layer device header or its functionality for each PDCP layer device, each bearer, or each logical channel. When the SDAP header is configured, the base station can use a one-bit NAS QoS reflection indicator (NAS reflected QoS) and a one-bit AS QoS reflection indicator (AS reflected QoS) in the SDAP header to indicate that the UE can update or reconfigure the uplink and downlink QoS flows and data bearer mapping information. The SDAP header may include QoS flow ID information indicating QoS. QoS information can be used for data processing priority, scheduling information, etc., to support the desired service.

[0214] The main functions of NR PDCP 9-30 and 9-65 may include at least some of the following functions.

[0215] - Header compression and decompression (ROHC only)

[0216] -Transmission of user data

[0217] -Sequential transmission of high-level PDUs

[0218] -Disordered transmission of high-level PDUs

[0219] - Reordering received PDCP PDUs

[0220] -Repetition detection of low-level SDUs

[0221] -PDCP SDU retransmission

[0222] - Encryption and decryption

[0223] - Timer-based SDUs are dropped in the uplink.

[0224] Among the aforementioned functions, the reordering function of the NR PDCP device refers to the function of rearranging the PDCP PDUs received in the lower layers according to their PDCP sequence numbers (SNs). The reordering function may include the function of sending data to the higher layers in the rearranged order, or the function of sending data immediately regardless of the order. Additionally, the reordering function may include the function of recording lost PDCP PDUs via reordering, the function of reporting the status of lost PDCP PDUs to the transmitter, and the function of requesting retransmission of lost PDCP PDUs.

[0225] The main functions of NR RLC 9-35 and 9-60 may include at least some of the following functions.

[0226] -Transmission of high-level PDUs

[0227] -Sequential transmission of high-level PDUs

[0228] -Disordered transmission of high-level PDUs

[0229] - Error correction via ARQ

[0230] - Assembly, segmentation and reassembly of RLC SDUs

[0231] - Resegmentation of RLC data PDUs

[0232] - Reordering of RLC data PDUs

[0233] -Duplicate detection

[0234] -Protocol error detection

[0235] -RLC SDU discard

[0236] -RLC Reconstruction

[0237] In the aforementioned functions, the sequential delivery function of the NR RLC device refers to the function of sequentially delivering RLC SDUs received from lower layers to higher layers. The sequential delivery function may include the ability to reassemble and deliver multiple RLC SDUs when an original RLC SDU is divided into multiple RLC SDUs to be received. Furthermore, the sequential delivery function may include the ability to rearrange received RLC PDUs based on the RLC SN or PDCP SN, and may include the ability to record lost RLCPDUs via reordering. Additionally, the sequential delivery function may include the ability to report the status of lost RLC PDUs to the transmitter, the ability to request retransmission of lost RLC PDUs, and, if lost RLC SDUs exist, the ability to sequentially deliver only the RLC SDUs preceding the lost RLC SDU to the higher layer. Furthermore, the sequential delivery function may include the ability to sequentially deliver all RLC SDUs received before the timer started to the higher layer when a timer expires, even if lost RLC SDUs exist, or the ability to sequentially deliver all currently received RLC SDUs to the higher layer when a timer expires, even if lost RLC SDUs exist. Furthermore, based on the in-order delivery function, NR RLC devices can process RLC PDUs in the order they are received (arrival order, regardless of SN order) and can deliver RLC PDUs to PDCP devices in an out-of-order manner. When segments are received, the in-order delivery function enables NR RLC devices to receive segments stored in a buffer or to be received later, reconstruct segments into a complete RLC PDU, and deliver the RLC PDU to the PDCP device. The NR RLC layer may not include splicing functionality, and splicing functionality can be performed in the NR MAC layer or replaced by multiplexing functions of the NR MAC layer.

[0238] The out-of-order delivery function of an NR RLC device refers to the function of directly delivering RLC SDUs received from lower layers to higher layers without regard to order. It may also include the function of reassembling and delivering multiple RLC SDUs when an original RLC SDU is divided into multiple RLC SDUs to be received. Furthermore, the out-of-order delivery function may include the function of recording lost RLC PDUs by storing and reordering the RLC SN or PDCP SN of the received RLC PDUs.

[0239] NR MAC 9-40 and 9-55 can connect to multiple NR RLC layer devices configured in one device, and the main functions of NRMAC can include at least some of the following functions.

[0240] Mapping between logical channels and transport channels

[0241] - MAC SDU multiplexing / demultiplexing

[0242] - Scheduling Information Report

[0243] - Error correction via HARQ

[0244] Priority processing between logical channels of a UE

[0245] - Priority handling among dynamically scheduled UEs

[0246] -MBMS service identifier

[0247] -Transmission format selection

[0248] -filling

[0249] NR PHY layers 9-45 and 9-50 can perform channel coding and modulation of higher-layer data, convert the data into OFDM symbols for transmission via a radio channel, or demodulate OFDM symbols received via a radio channel and perform channel decoding of OFDM symbols to pass the OFDM symbols to higher layers.

[0250] The details of the wireless protocol architecture can vary depending on the carrier (or cell) operation method. For example, when a base station transmits data to a UE based on a single carrier (or cell), the base station and UE use a protocol architecture with a single structure for each layer, as shown in 9-00. When a base station transmits data to a UE based on carrier aggregation (CA) using multiple carriers on a single TRP, the base station and UE use a protocol architecture where the RLC has a single structure, but the PHY layer is multiplexed through the MAC layer, as shown in 9-10. In another example, when a base station transmits data to a UE based on dual connectivity (DC) using multiple carriers on multiple TRPs, the base station and UE use a protocol architecture where the RLC has a single structure, but the PHY layer is multiplexed through the MAC layer, as shown in 9-20.

[0251] In LTE and NR, a UE has a process for reporting its supported capabilities to the serving base station while connected to it. In the following description, this process is referred to as UE capability reporting. The base station may send a UE capability query message to a connected UE to request a capability report. The base station may include a UE capability request for each RAT type in this message. The request for each RAT type may include the requested frequency band information.

[0252] Furthermore, a UE capability query message can request multiple RAT types within a single RRC message container. According to another example, a UE capability query message including requests for each RAT type can be sent to the UE multiple times. That is, the UE capability query is repeated multiple times, and the UE can respond to the query by configuring a UE capability information message and can report the message multiple times. In NR systems, requests are made for UE capabilities for MR-DC, including NR, LTE, and EN-DC. Typically, the UE capability query message is initially sent after the UE establishes a connection, but the base station can request capability reports from the UE under any circumstances when needed.

[0253] When a UE receives a UE capability report request from a base station, the UE can configure its capabilities based on the RAT type and frequency band information requested from the base station. The method for configuring UE capabilities in an NR system will be described below.

[0254] 1. When a list of LTE and / or NR frequency bands is provided to the UE via a UE capability request from the base station, the UE can configure a frequency band combination (BC) for EN-DC and NR Independent (SA). That is, the UE can configure a candidate list of BCs for EN-DC and NR SA based on the frequency bands requested from the base station via FreqBandList. The frequency bands can have priorities in the order described in the FreqBandList.

[0255] 2. When a base station requests a UE capability report by setting the “eutra-nr-only” or “eutra” flag, the UE can completely remove the NR SA BC from the configured BC candidate list. This operation can only occur when the LTE base station (eNB) requests “eutra” capability.

[0256] 3. The UE removes the fallback BC from the BC candidate list configured in the above operation. The fallback BC corresponds to the superset BC that has been removed from it, which corresponds to the band of at least one SCell, and can be omitted because the superset BC may already cover the fallback BC. This operation also applies to MR-DC, i.e., LTE bands. The BCs remaining after this operation are the final "candidate BC list".

[0257] 4. The UE can select the BC to report from the final "Candidate BC List" by choosing the BC corresponding to the requested RAT type. In this operation, the UE configures the supportedBandCombinationList in a predetermined order. That is, the UE can configure the BC to report and UE capabilities according to the preset rat-Type order (nr->eutra-nr->eutra). In addition, the UE configures featureSetCombination for the configured supportedBandCombinationList and configures a list of "Candidate Feature Set Combinations" based on the candidate BC list after removing fallback BCs (including capabilities of the same or lower level). The "Candidate Feature Set Combinations" include feature set combinations for both NR and EUTRA-NR BCs and can be obtained from the feature set combinations in the UE-NR-Capabilities and UE-MRDC-Capabilities containers.

[0258] 5. When the requested rat type is eutra-nr and has an impact, featureSetCombinations are included in both the UE-MRDC-Capabilities and UE-NR-Capabilities containers. However, NR feature sets are only included in UE-NR-Capabilities.

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

[0260] Figure 10 A cooperative communication antenna port configuration according to an embodiment is shown.

[0261] Figure 10 An example of radio resource allocation per transmit-receive point (TRP) based on Joint Transmission (JT) technology and circumstances is shown. Figure 10 In Figure 10-00, coherent joint transmission (C-JT) supporting phase interference coding between individual cells, TRPs, and / or beams is illustrated. In C-JT, TRP A 10-05 and TRP B 10-10 transmit the same data (PDSCH), and multiple TRPs can perform joint precoding. This may mean that TRP A 10-05 and TRP B 10-10 transmit the same DMRS ports for receiving the same PDSCH (e.g., both TRPs transmit DMRS ports A and B). In this case, UE 10-15 can receive a DCI for receiving a PDSCH demodulated by DMRS ports A and B.

[0262] exist Figure 10 Table 10-20 illustrates noncoherent joint transmission (NC-JT) supporting non-interference coding between individual cells, TRPs, and / or beams. In NC-JT, each cell, TRP, and / or beam transmits a different PDSCH, thus allowing for the application of individual precoding to each data (or PDSCH). This could mean that TRP A 10-25 and TRP B 10-30 transmit different DMRS ports for receiving different PDSCHs (e.g., TRP A transmits DMRS port A, and TRP B transmits DMRS port B). In this case, the UE receives two types of DCIs for receiving PDSCH A demodulated by DMRS port A and PDSCH B demodulated by DMRS port B.

[0263] To support NC-JT where two or more transmission points simultaneously provide data to a single UE, it is necessary to allocate PDSCHs transmitted from two (or more) different transmission points via a single PDCCH, or to allocate PDSCHs transmitted from two or more different transmission points via multiple PDCCHs. The UE can obtain the quasi-co-location (QCL) relationship between reference signals or channels based on L1 / L2 / L3 signaling, and can efficiently estimate the large-scale parameters of the reference signals or channels through the QCL relationship. When the transmission points of a reference signal or channel are different, large-scale parameters are difficult to share. Therefore, when performing cooperative transmission, the base station needs to simultaneously notify the UE of multiple quasi-co-location information about two or more transmission points through two or more TCI states.

[0264] When noncoherent cooperative transmission is supported via multiple PDCCHs (i.e., when two or more PDCCHs simultaneously assign two or more PDSCHs to the same serving cell and the same BWP), two or more TCI states can be assigned to the corresponding PDSCH or DMRS ports via the respective PDCCHs. However, when noncoherent cooperative transmission is supported via a single PDCCH (i.e., when one PDCCH simultaneously assigns two or more PDSCHs to the same serving cell and the same BWP), two or more TCI states can be assigned to the corresponding PDSCH or DMRS ports via a single PDCCH.

[0265] Suppose that the DMRS ports allocated to a UE at a specific time are divided into DMRS port group A, transmitted from transmission point A, and DMRS port group B, transmitted from transmission point B. Two or more TCI states are associated with the corresponding DMRS port groups, and the channel can be estimated based on different QCL assumptions for the corresponding groups. Different DMRS ports can undergo code division multiplexing (CDM), frequency division multiplexing (FDM), or time domain multiplexing (TDM) to increase the accuracy of channel measurements and reduce transmission load. Here, when DMRS ports undergoing CDM are collectively referred to as CDM groups, it can be important to ensure that DMRS ports in the same CDM group do not have different TCI states because code-based multiplexing operates appropriately when DMRS ports in a CDM group have similar channel characteristics (i.e., ports are easily distinguishable by orthogonal coverage codes (OCC) when they have similar channel characteristics).

[0266] In the following text, for ease of description, Tables X to Y are referred to as “First Antenna Port Indication (or Conventional Antenna Port Indication)”, and any table in which some or all of the code points in Tables X to Y are modified is referred to as “Second Antenna Port Indication (New Antenna Port Indication)”. Furthermore, DMRS port and CDM group assignments are referred to as DMRS assignments.

[0267] The UE can determine the number of antenna ports used for PDSCH transmission using a table indicating DMRS ports. In DCI format 1_1, the Rel-15-based antenna port indication method is based on an index of 4 to 6 bits in length indicated by the antenna port field in the DCI. The UE can identify information about the number and index of DMRS ports used for PDSCH, the number of preamble symbols, and the number of CDM groups based on the indicator (index) sent by the base station. Furthermore, the UE can determine dynamic changes in beamforming direction based on information in the Transmission Configuration Indication (TCI) field in DCI 1_1. When tci-PresentDCI is configured as "enabled" in the higher layers, the UE can identify the three-bit TCI field to determine the TCI status for DL ​​BWP or scheduled component carrier activation and the beam direction associated with DL-RS. When tci-PresentDCI is disabled, the UE can assume that the beam direction is not changing during beamforming.

[0268] In various embodiments of this disclosure, scenarios are considered where PDSCHs transmitted from two (or more) different transmission points are allocated via multiple PDCCHs or a single PDCCH. A Rel-15 UE can receive single-layer or multi-layer PDSCH streams conforming to QCL based on TCI information and antenna port information in a single PDCCH. However, a Rel-16 UE can receive C-JT / NC-JT formatted data transmitted from multiple TRPs or multiple base stations. To support C-JT / NC-JT, a Rel-16 UE requires basic higher-layer configuration. Specifically, the UE can receive parameters or settings related to C-JT / NC-JT via higher layers and can perform configuration to support C-JT / NC-JT based on the received parameters or settings.

[0269] The UE can support C-JT / NC-JT format data transmitted from multiple TRPs or multiple base stations. UEs supporting C-JT / NC-JT can receive C-JT / NC-JT-related parameters or settings in higher-layer configurations and can set the UE's RRC parameters based on these parameters or settings. For higher-layer configurations, the UE can utilize the UE capability parameter tci-StatePDSCH. The UE capability parameter tci-StatePDSCH defines the TCI states used for PDSCH transmission, and the number of TCI states can be configured as 4, 8, 16, 32, 64, and 128 in FR1, and as 64 and 128 in FR2. Up to eight states can be configured, indicated by three bits of the TCI field in the DCI via the MAC CE message. The maximum value of 128 refers to the value indicated by maxNumberConfiguredTCIstatesPerCC in the tci-StatePDSCH parameter included in the UE's capability signaling. This series of configuration processes, 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.

[0270] According to embodiments of this disclosure, a base station can instruct a UE to activate / deactivate a specific TCI state via at least one MAC CE signaling. Specifically, as in DCI format 1_1, when a PDSCH is assigned to a specific UE, the base station enables the UE to dynamically support QCL change commands that include (receive) beamforming direction indication or beamforming direction information using the TCI field.

[0271] QCL change command refers to the operation applied when a UE that recognizes the TCI status field information in DCI format 1_1 receives PDSCH in the downlink after a certain time (e.g., from the time of receiving DCI, after a specified threshold (such as timeDurationForQCL) indicated by the UE capability report or signaling), and the direction refers to the corresponding beamforming configuration direction related to the DL RS of the base station / TRP that conforms to QCL.

[0272] The Rel-16 MAC CE can be configured as a partial extension of the Rel-15 MAC CE message. This embodiment may propose including all TCI states activated by the Rel-15 MAC CE within the TCI states activated by the Rel-16 MAC CE.

[0273] In one example, such as Figure 11 As shown, the base station can determine a total of M TCI states 11-00 of the Rel-15 RRC configuration, such as TCI#0, TCI#1, TCI#2, ..., TCI#M-1, and can select TCI#0', TCI#1', TCI#2', ..., TCI#K-1 as a subset 11-20 of the TCI states selected by the Rel-15 MAC CE. However, base stations and UEs supporting Rel-16 can configure TCI states for Rel-16 RRC configuration separately, or can use the TCI states configured in Rel-15 RRC configuration as is. Here, the TCI states for Rel-16 RRC configuration can include some or all of the TCI states configured in Rel-15 RRC configuration. When M=128, the number of TCI states in Rel-16 can be equal to or greater than 128. When a base station or UE scales the number of TCI states supported by Rel-15 proportionally to the number of base stations / TRPs operating according to C-JT / NC-JT in Rel-16, up to 256 TCI states can be configured if two TRPs operate. Here, in the TCI states configured for Rel-16 RRC, the Rel-16 MAC CE can include some or all of the TCI states supported by the Rel-15 MAC CE. Specifically, when the Rel-16 MAC CE includes all TCI states supported by the Rel-15 MAC CE, and the number of TCI states scales proportionally to the number of base stations / TRPs operating according to C-JT / NC-JT in Rel-16, up to 2K TCI states can be configured if two TRPs operate.

[0274] Table 13 shows the details of the tci-StatePDSCH parameters described in the above embodiments. Specifically, the FR2 forced value of the parameter maxNumberConfiguredTCIstatesPerCC can be modified from 64 to 128 or 256, or can be individually added to 64, 128 or 256 for C-JT / NC-JT.

[0275] [Table 13]

[0276]

[0277] In another example, a base station or UE supporting Rel-15 and Rel-16 can configure a maximum value for each of Rel-15 and Rel-16 to configure the TCI state via MAC CE, and the number of TCI states can be configured to be less than or equal to the configured maximum value. Various embodiments can be proposed below as methods for configuring the number of TCI states to be less than or equal to the maximum value.

[0278] The number of TCI states activated by Rel-15 and Rel-16 MAC CE messages can be configured based on UE capability values ​​reported by the UE. According to another example, the number of TCI states activated by Rel-15 and Rel-16 MAC CE messages can be determined as a value preset by the base station. According to yet another example, the number of TCI states activated by Rel-15 and Rel-16 MAC CE messages can be determined as a value pre-agreed upon between the base station and the UE.

[0279] For example, such as Figure 11 As shown, the base station and UE can determine a total of M TCI states 11-00 configured in the Rel-15 RRC, such as TCI#0, TCI#1, TCI#2, ..., TCI#M-1, and can select a subset 11-20 of the TCI states selected by the Rel-15 MAC CE from them, thereby arranging TCI#0', TCI#1', TCI#2', ..., TCI#K-1. When TCI#0 is selected from the M TCI states, TCI#0 can be arranged in TCI#0'. Here, for example, the maximum value K for Rel-15 supported base stations and UEs can be configured or determined to be 8, and the maximum value K for Rel-16 supported base stations and UEs can also be configured to be 8. When the maximum value is configured to 8, the base station can instruct the UE to select a beam for the PDSCH in a CORESET through a DCI-based beam selection operation. The beam selection can be determined by identifying the TCI field information 11-40 in the DCI in up to eight lines. Figure 11The TCI field #I indicated in the DCI can be selected as a value from 0 to 7. For example, when the TCI field of the DCI is indicated as 000, it can be determined that TCI#0' (TCI#I = TCI#0') is indicated among TCI#0', TCI#1', TCI#2', TCI#3', TCI#4', TCI#5', TCI#6', and TCI#7'. Although this embodiment shows that each maximum value is configured as 8 (K = 8), the maximum value can be configured to a value less than 8. Although this embodiment shows that the maximum value K for MAC CE for Rel-15 and the maximum value K for MAC CE for Rel-16 are the same, the maximum value can be configured to different values.

[0280] In another example, when the number of TCI states scales proportionally to the number of base stations / TRPs operating in C-JT / NC-JT mode, if two TRPs are operating, the maximum value of K for both the Rel-16-supporting base station and the UE can be configured to 16. When the maximum value is configured to 16, the base station can instruct the UE to select one or two or more beams for the PDSCH in a CORESET via DCI-based beam selection operation. When K is 16, #I, selected and indicated by the base station, can be selected as a value from 0 to 15. Although this embodiment shows the maximum value configured to 16 (K = 16), the maximum value can be configured to a value less than 16.

[0281] In yet another example, it can be determined that the base station or UE uses only Rel-16 MAC CE signaling. That is, Rel-15 MAC CE and Rel-16 MAC CE can use a single Rel-16 MAC CE for C-JT / NC-JT merging.

[0282] For example, when a UE is scheduled by a DCI based on Rel-15, if a TCI code point in the DCI is associated with two or more TCI states, the UE may consider only the first TCI state among the multiple TCI states. When a Rel-15 UE and a Rel-16 UE receive signaling via a merged or compatible format MAC CE, the Rel-15 UE can operate similarly to receiving a Rel-15 MAC CE as defined in the current standard and obtaining the desired information. However, a Rel-16 UE can determine at least one TCI state to be selected from multiple TCI states selected from the DCI based on the base station's transmission determination. The base station's transmission determination method can be determined by the UE based on at least one of the following: information about the number of antenna ports in the DCI, DMRS port information indicated in the DMRS table, and TCI index information.

[0283] For example, such as Figure 12As shown, the base station can determine a total of M TCI states 12-00 of the Rel-15 RRC configuration, such as TCI#0, TCI#1, TCI#2, ..., TCI#M-1, where a set of TCI states for C-JT / NC-JT or at least one set of TCI states can be configured by MAC CE (12-20). The MAC CE set can be configured to include one TCI state information and at least two TCI state information for C-JT / NC-JT. For example, in this configuration, sets including more TCI states can be subsequently placed according to the listing order in which a set including one TCI state is placed first and a set including two TCI states is placed later. In another example, the TCI states can be arranged in a list order based on the TCI states with smaller TCI state indices, such as TCI#0, (TCI#1, TCI#32), TCI#2, (TCI#3, TCI#34), ..., (TCI#10, TCI#31). Upon receiving the MAC CE, based on the DCI-based beamforming information in the DCI, the UE can be instructed with either (12-40) TCI#I or (TCI#I, TCI#J). In this embodiment, when TCI#I is indicated, the UE can determine that a beamforming direction has been selected. Specifically, when TCI#0 is indicated, the UE can perform beamforming in the direction of the beam mapped to TCI#0. Furthermore, in this embodiment, when (TCI#I, TCI#J) is indicated, the Rel-15 UE can determine that TCI#I is selected as the first index among the two beamforming directions. Specifically, when (TCI#1, TCI#32) is indicated, the UE can perform beamforming in the direction mapped to the beam of TCI#1 in the first TRP. Furthermore, in this embodiment, when (TCI#I, TCI#J) is indicated, the Rel-16 UE can determine that two beamforming directions have been selected. Specifically, when (TCI#1, TCI#32) is indicated, the UE can perform beamforming in the direction mapped to the beam of TCI#1 in the first TRP, and can perform beamforming in the direction mapped to the beam of TCI#32 in the second TRP.

[0284] In other words, when the UE is a Rel-15 UE, the UE can interpret only TCI#I, which is the first TCI state information, from the information obtained from the MAC CE, and can determine a single transmission performed by a TRP. However, when the UE is a Rel-16 UE, the UE can interpret at least some or all of the MAC CE information obtained through indexing. When two TRPs are configured for C-JT / NC-JT for the UE, the UE can interpret all TCI state information as (TCI#I, TCI#J) and can determine the selection of two beams. In this embodiment, when three TRPs are configured for C-JT / NC-JT for the UE, TCI states such as (TCI#I, TCI#J, TCI#L) can be additionally included in the MAC CE.

[0285] When a UE is scheduled by DCI based on Rel-15, if a TCI code point in the DCI is associated with two or more TCI states, the UE may consider only the smallest TCI state ID among the multiple TCI states.

[0286] For example, such as Figure 12 As shown, the base station can determine a total of M TCI states 12-00 of the Rel-15 RRC configuration, such as TCI#0, TCI#1, TCI#2, ..., TCI#M-1, where a set of TCI states for C-JT / NC-JT or at least one set of TCI states can be configured by MAC CE (12-20). The MAC CE set can be configured to include one TCI state information and at least two TCI state information for C-JT / NC-JT. For example, in this configuration, sets including more TCI states can be subsequently placed according to the listing order in which a set including one TCI state is placed first and a set including two TCI states is placed later. In another example, in the aforementioned configuration, based on the minimum value in the TCI state index, the TCI states can be arranged such that TCI states with smaller TCI state indices are placed first, such as TCI#0, (TCI#32, TCI#1), TCI#2, (TCI#34, TCI#3), ..., (TCI#10, TCI#31). Upon receiving the MAC CE, based on the DCI-based beam selection information in the DCI, one of (12-40) TCI#I or (TCI#I, TCI#J) can be indicated to the UE.

[0287] In this embodiment, when TCI#I is indicated, the UE can determine to select a beamforming direction. Specifically, when TCI#0 is indicated, the UE can perform beamforming in the direction of the beam mapped to TCI#0. In addition, in this embodiment, when (TCI#I, TCI#J) is indicated, the Rel-15 UE can consider the smallest TCI state ID to determine to select TCI#I (I < J) among the two beamforming directions. Specifically, when (TCI#32, TCI#1) is indicated, the UE can perform beamforming in the direction of the beam mapped to TCI#1 in the first TRP. In addition, in this embodiment, when (TCI#I, TCI#J) is indicated, the Rel-16 UE can determine to select two beamforming directions. Specifically, when (TCI#32, TCI#1) is indicated, the UE can perform beamforming in the direction of the beam mapped to TCI#1 in the first TRP, and can perform beamforming in the direction of the beam mapped to TCI#32 in the second TRP. In this embodiment, when three TRPs are configured for the UE for C-JT / NC-JT, TCI states such as (TCI#I, TCI#J, TCI#L) can be additionally included in the MAC CE.

[0288] Figure 13 Fig. shows the structure of the MAC CE message for indicating the TCI state. Figure 13 Fig. shows when in Figure 11 the base station selects K TCI states 11-20 from M TCI states 11-00, the structure of the MAC CE message sent to the UE to indicate the K TCI states. The MAC CE message can basically include information about the serving cell ID (e.g., 5 bits) and the BWP ID (e.g., 2 bits) configured for communication between the base station and the UE. In addition, the MAC CE message requires M bits to respectively use one-bit indication to indicate whether the M TCI states are activated. As Figure 13As shown, M bits can be aligned using resources in octet format. Indices T0, T1, ..., T(N-2)x8-7 represent TCI states, and M is configured to be equal to or greater than T(N-2)x8 and less than or equal to T(N-2)x8-7 to indicate a total of M bits. For example, to indicate the active TCI state out of 128 TCI states, the MAC CE message requires a total of 17 octets (N=17) of resources, including the configured serving cell ID and BWPID (Oct 1). Here, when eight TCI states from T0 to T7 are active, the resource positions from T0 to T7 in the MAC CE message are indicated by '1', while the remaining T8 to T127 are indicated by '0'. When the UE receiving the MAC CE successfully decodes it, the resource positions indicated by the '1' used to indicate the active TCI state are mapped to determine the direction of the active beamforming.

[0289] Figure 14 Various examples of multiple TRP operations according to embodiments are shown.

[0290] Figure 14 Case #4 14-30 illustrates an example of configuring the serving cell and physical cell identifier (PCI) according to conventional CA operations. This serves as a guideline for indicating differences between multiple TRP operation methods. Referring to Case #4, in a typical CA scenario where each cell occupies different frequency resources, the base station can configure different serving cells (ServCellConfigCommon) for each cell (i.e., the frequencyband value FrequencyInfoDL indicated by DownlinkConfigCommon is different in each serving cell configuration). Therefore, different indices (ServCellIndex) can be configured for each cell, and different PCI values ​​can be mapped. Here, the parameters in ServCellConfigCommon are shown in the table below.

[0291]

[0292] Figure 14Case #1 14-00 illustrates intra-cell multi-TRP operation where one or more TRPs operate within a single serving cell configuration. Referring to Case #1, because the base station configures channels and signals transmitted from different TRPs to be included in a single serving cell configuration, multiple TRPs operate based on a single ServCellIndex (ServCellIndex #1), and since there is only one ServCellIndex, only one PCI is used. In this case, when multiple SSBs are transmitted from TRP 1 and TRP 2, the SSBs have the same PCI value, and there are no issues in mapping the ServCellIndex value indicated by the cell parameters in the QCL-Info to the PCI and specifying the SSB transmitted from TRP 1 or TRP 2 as the reference antenna port.

[0293] Figure 14 Case #3 14-20 illustrates inter-cell multi-TRP operation where one or more TRPs have different PCIs. In Case #3, the base station configures the channels and signals transmitted from different TRPs to be included in different serving cell configurations (i.e., the respective TRPs have independent serving cell configurations, and the frequency bands at least partially overlap are indicated by the frequencyInfoDL value indicated by DownlinkConfigCommon in the serving cell configuration), and since multiple TRPs operate based on multiple ServCellIndexes (ServCellIndex#1 and ServCellIndex#2) included in the serving cell configurations, a separate PCI can be used for each TRP (i.e., one PCI can be allocated per ServCellIndex). When multiple SSBs are transmitted from TRP 1 and TRP 2, the SSBs can have different PCI values ​​(PCI#1 or PCI#2). In case #3, there is no problem in mapping the PCI value suitable for each TRP by appropriately selecting the ServCellIndex values ​​(ServCellIndex#1 and ServCellIndex#2) indicated by the cell parameters included in the QCL-Info in different serving cell configurations, and in specifying the SSB transmitted from TRP 1 or TRP 2 as the reference antenna port. However, since this configuration uses a single serving cell configuration that can be used for the UE's CA, the freedom of CA configuration may be limited or the signaling load may increase for multiple TRPs.

[0294] Figure 14Case #2 14-10 illustrates another example of inter-cell multi-TRP operation where one or more TRPs have different PCIs. Referring to Case #2, the base station can configure channels and signals transmitted from different TRPs to be included in a single serving cell configuration (considering the signaling load of the application according to Case #3). In this case, the UE operates based on the ServCellIndex (ServCellIndex#1) included in a single serving cell configuration, and therefore may not recognize the PCI (PCI#2) assigned to the second TRP. When multiple SSBs are transmitted from TRP 1 and TRP 2, the SSBs can have different PCI values ​​(PCI#1 or PCI#2), and in Case #2, the PCI value (PCI#2) of the second TRP may not be mapped by the ServCellIndex value indicated by the cell parameters included in a single serving cell configuration. Therefore, in inter-cell multiple TRP operations according to case #2 14-10, it is only possible to designate the SSB sent from TRP 1 as the reference antenna port, and it is not possible to designate the SSB sent from TRP 2 as the reference antenna port.

[0295] The following embodiments of this disclosure provide a method for instructing / configuring a QCL reference antenna port to support case #2 14-10, namely, inter-cell multiple TRP operation (inter-cell multiple TRP with non-CA framework) using a single serving cell configuration within a frequency resource.

[0296] Base stations may explicitly or implicitly indicate to the UE the application of non-CA framework inter-cell multi-TRP through various methods.

[0297] For example, a base station can notify the UE to apply inter-cell multi-TRP with a non-CA framework by using higher-layer signaling, such as by configuring parameters to divide a CORESET configured in a serving cell or BWP into two or more groups (CORESET groups) (higher-layer parameters per CORESET), by configuring parameters to divide a PUCCH resource configured in a serving cell or BWP into two or more groups (PUCCH groups) (higher-layer parameters per PUCCH), or by defining and configuring independent higher-layer parameters.

[0298] In another example, when a serving cell is configured to perform multiple TRP operations (i.e., when it is configured to receive one or more PDSCHs at a time in a BWP within a serving cell), the UE can understand that inter-cell multiple TRP with a non-CA framework is applied if the serving cell’s frequency resources (i.e., the frequency resources indicated by the frequency band value FrequencyInfoDL indicated by the DownlinkConfigCommon configured by the corresponding serving cell) do not overlap with any frequency configurations configured by other serving cells.

[0299] Although omitted to avoid obscuring the key points described in the following embodiments, it should be noted that if the UE recognizes that the base station is performing inter-cell multi-TRP operations with a non-CA framework using the above examples or one of their applications, then one of the methods in the following embodiments can be applied.

[0300] [First Example: Method for Adding PCI Values ​​to TCI or QCL Configuration]

[0301] The first embodiment provides a method to configure the SSB based on the additional PCI as the QCL reference antenna port by adding parameters for associating additional PCI values ​​other than the first PCI value mapped to the existing ServCellIndex to the TCI configuration or QCL configuration included in a serving cell configuration.

[0302] Figure 15 An example of a method for configuring the QCL target antenna port and reference antenna port according to an embodiment is shown.

[0303] refer to Figure 15 According to Table 4-1, when the QCL target antenna port is TRS15-00, the configurable QCL reference antenna port can be SSB 15-05 or CSI-RS15-10 for BM. In an inter-cell multi-TRP environment with a non-CA framework, it can be assumed that SSB 15-05 or CSI-RS 15-10 for BM is configured in the same serving cell configuration as TRS, and PCI#1 is assigned to the corresponding serving cell. Here, as mentioned above, SSB 15-20 and 15-30, which have different PCIs (PCI#2 and PCI#3), cannot be configured as QCL reference antenna ports via traditional signaling.

[0304] According to one method used to address the aforementioned problem, as shown below, a parameter (physCellId) referring to a PCI other than the PCI#1 assigned to the serving cell may be added to the QCL configuration included in a serving cell configuration used in an inter-cell multi-TRP environment with a non-CA framework. For example, to configure SSB 15-20 associated with PCI#2 as a QCL reference antenna port, the value of physCellId added to the following QCL configuration can be set to PCI#2.

[0305]

[0306] According to another approach to address the aforementioned problem, as shown below, a parameter (physCellId) used to refer to a PCI other than the PCI#1 assigned to the serving cell might be added to the TCI configuration included in a serving cell configuration used in an inter-cell multi-TRP environment with a non-CA framework. For example, to configure SSB 15-20 associated with PCI#2 as a QCL reference antenna port, the value of physCellId added to the following TCI configuration could be set to PCI#2.

[0307]

[0308]

[0309] Similarly, in order to map different PCI values ​​to the first QCL configuration (qcl-Type1) and the second QCL configuration (qcl-Type2) in the TCI configuration, two PCIs (physcellid 1 and physCellId2) may be added to the TCI configuration as follows.

[0310]

[0311] When assigning additional PCI values ​​to the QCL or TCI configuration, specific constraints may be considered based on the UE's mobility configuration (or handover configuration) values.

[0312] For example, according to the table below, the base station can configure a list of PCI values ​​associated with the SSB to be measured by the UE through SSB-MTC and SSB-MTC2 configurations.

[0313]

[0314]

[0315] exist Figure 15In the example, when PCI#2 is included in the pci-list of SSB-MTC2, but PCI#3 is not, the UE is forced to measure SSB 15-20 associated with PCI#2, but not SSB 15-30 associated with PCI#3. Therefore, the UE can apply the configuration of the QCL reference antenna port to SSB 15-20 associated with PCI#2, but does not expect the configuration of the QCL reference antenna port to be used for SSB 15-30 associated with PCI#3. Here, "the UE does not expect the configuration of the QCL reference antenna port" can be applied differently in practice, such as "ignoring configuration details when performing configuration," "allowing random processing because no UE operation is defined for this configuration," or "ensuring the base station does not perform this configuration."

[0316] As another example of a specific constraint, a base station may consider a black cell list or a white cell list in its MeasObject configuration. According to the table below, a base station can configure a series of PCI value lists through the MeasObject configuration, which are associated with the blacklist (blackCellsToAddModList) and whitelist (whiteCellsToAddModList) of PCI values ​​considered by the UE when measuring SSB.

[0317]

[0318]

[0319]

[0320] exist Figure 15In the example, when PCI#2 is included in the whiteCellsToAddModList of MeasObjectNR (or not included in the blackCellsToAddModList), but PCI#3 is not included in the whiteCellsToAddModList of MeasObjectNR (or included in the blackCellsToAddModList), the UE is forced to measure SSB 15-20 associated with PCI#2, but not forced to measure SSB 15-30 associated with PCI#3. Therefore, the UE can apply the configuration of the QCL reference antenna port to SSB 15-20 associated with PCI#2, but does not expect the configuration of the QCL reference antenna port for SSB 15-30 associated with PCI#3. Here, "the UE does not expect the configuration of the QCL reference antenna port" can be applied differently in practice, such as "ignoring configuration details when performing configuration," "allowing random processing because no UE operation is defined for this configuration," or "ensuring the base station does not perform this configuration."

[0321] [Second Embodiment: Method for Adding CSI-RS for Mobility to the QCL Reference Antenna Port]

[0322] The second embodiment provides a method to reference the PCI values ​​of neighboring cells by adding an antenna port (or channel / signal) configured with an independent PCI value regardless of the PCI value mapped to the ServCellIndex of a serving cell as a new QCL reference antenna port.

[0323] Figure 16 An example of a method for configuring the QCL target antenna port and reference antenna port according to an embodiment is shown.

[0324] refer to Figure 16 According to Table 4-1, when the QCL target antenna port is TRS16-00, the configurable QCL reference antenna port can be SSB 16-05 or CSI-RS16-10 for BM. In an inter-cell multi-TRP environment with a non-CA framework, it can be assumed that SSB 16-05 or CSI-RS 16-10 for BM is configured in the same serving cell configuration as TRS, and PCI#1 is assigned to the corresponding serving cell. Here, as mentioned above, SSB 15-20 with different PCIs (PCI#2 or PCI#3) cannot be configured as a QCL reference antenna port via conventional signaling.

[0325] One approach to address the aforementioned problem, as shown below, is to reference a PCI other than the PCI#1 assigned to the serving cell by adding a CSI-RS for mobility to an antenna port that can be selected via referenceSignal in the QCL configuration.

[0326]

[0327] In the table above, CSI-RS-Index is a parameter used to refer to the index of the following CSI-RS-Resource-Mobility configurations included in the serving cell configuration used in an inter-cell multi-TRP environment with a non-CA framework.

[0328]

[0329]

[0330] In this embodiment, some constraints can be considered when adding the CSI-RS16-15 for mobility as a new QCL reference antenna port.

[0331] For example, when the CSI-RS16-15 for mobility is applied as a new QCL reference antenna port, given the accuracy of the QCL application, it can be guaranteed that the density of the CSI-RS for mobility will always be configured to a high value (i.e., density = d3 is always configured in the CSI-RS-CellMobility configuration).

[0332] In another example, when CSI-RS16-15 for mobility is applied as a new QCL reference antenna port, the association ensures that only the UE's receive beam information is specified by restricting the QCL configuration type to QCL-type D. In this case, QCL-type A through QCL-type C can be referenced in the UE's current serving cell.

[0333] In yet another example, when the CSI-RS16-15 for mobility is applied as a new QCL reference antenna port, it may be guaranteed that the SSB 16-20 associated with CSI-RS-Resource-Mobility (i.e., the SSB indicated by the associated SSB in CSI-RS-Resource-Mobility) will be used as the QCL reference antenna port, instead of directly using the CSI-RS16-15 for mobility. Here, by configuring isQuasiColocated in the associated SSB, it can be guaranteed that this example will only be applied if the CSI-RS for mobility and the associated SSB mutually conform to the QCL.

[0334] [Third Embodiment: Method for satisfying the condition of using a TRS that is not configured as a QCL reference antenna port]

[0335] The third embodiment relates to a method for performing appropriate operations based on scenarios where the PCI value of the adjacent TRP does not need to be referenced, i.e., scenarios where additional QCL reference antenna ports other than the QCL reference antenna port based on the serving cell are configured as needed, and scenarios where additional QCL reference antenna ports do not need to be configured.

[0336] Figure 17 The intra-cell multiple TRP operation and inter-cell multiple TRP operation according to the embodiments are illustrated.

[0337] refer to Figure 17 The UE can perform a UE capability report regarding multiple TRP operations (17-00). This report can report both intra-cell and inter-cell multiple TRP operations (i.e., report whether both are possible or impossible), or it can report the possibility of each operation separately. Subsequently, the base station can configure multiple TRP operations for UEs capable of performing them (17-05). The UE can determine the feasibility of inter-cell multiple TRP operations based on pre-agreed rules, i.e., whether TRS reception is possible without configuring the QCL reference antenna port (17-10). For example, in the pre-agreed rules, when the deriveSSB-IndexFromCell parameter is configured as true, the base station specifies the alignment subframe number (SFN) and frame boundary for each cell. When inter-cell multiple TRP operations are not possible, the UE can receive the QCL reference antenna port configured based on the serving cell PCI to perform intra-cell multiple TRP operations (17-15). When inter-cell multi-TRP operations are possible, the UE can perform intra-cell multi-TRP operations without configuring the QCL reference antenna port (17-20).

[0338] In the above embodiments, it is assumed that TRS15-00 and 16-00 are target antenna ports, but this disclosure is not limited thereto, and methods similar to those described above can be applied to other types of target antenna ports.

[0339] [Fourth Embodiment: Method for Adding PCI Values ​​to SSB-Based Channel State Measurement Configuration]

[0340] This embodiment provides a method for using RS (e.g., SSB or CSI-RS for mobility) transmitted in a cell or TRP where the UE is not attached to / camped in a non-CA framework inter-cell multi-TRP scenario as a reference signal for channel state measurement.

[0341] First, a method for configuring a reference signal for L1-RSRP or L1-SINR measurement is provided. The configuration of the standard reference signal for L1-RSRP or L1-SINR measurement is indicated to the UE from the base station via a CSI-ResourceConfig IE or similar signaling structure, as shown in the table below. The type of reference signal that can be configured for L1-RSRP or L1-SINR measurement can be SSB, CSI-RS, or CSI-IM.

[0342]

[0343] When configuring an SSB in the CSI-ResourceConfig IE of a table, you can indicate a list of SSB sets used for measuring L1-RSRP or L1-SINR in the csi-SSB-ResourceSetList element. Each SSB set in the csi-SSB-ResourceSetList element can include the SSB set ID (csi-SSB-ResourceSetId) and a list of SSB indices belonging to that SSB set (csi-SSB-ResourceList), as shown in the table below.

[0344]

[0345] SSB indices belonging to a regular SSB set are limited to the PCell to which the UE is attached or camped, or the SCell configured for the UE. According to embodiments of this disclosure, in order to use an SSB that is a PCell to which the UE is not attached or camped, or a cell that is a PCI not configured as an SCell, or a TRP used for L1-RSRP or L1-SINR measurements, the base station can indicate not only the SSB index to the UE, but also the PCI corresponding to the SSB index. When indicating a PCI, a separate PCI can be indicated for each SSB index in the SSB set, one PCI can be indicated for each SSB set, or one PCI can be indicated for each CSI-ResourceConFigure. For example, when indicating one PCI for each SSB set, the parameter (physCellId) indicating the PCI can be added to the SSB set configuration (csi-SSB-ResourceList) as follows.

[0346]

[0347] Next, a method for configuring a reference signal for beam failure recovery is provided. After periodically measuring the reference signal corresponding to a specific link, when the UE determines that the reception quality (e.g., RSRP) of the reference signal is poor, the UE can declare a beam failure in the link and can perform a beam recovery procedure. The beam recovery procedure can begin by the UE sending beam failure declaration information to the base station. The beam failure declaration information may include information about the link that needs to be recovered and information about the beam used to recover the link. The information about the link that needs to be recovered may include an index of the serving cell of the link and / or information about the reference signal periodically measured in the serving cell. The "periodically measured reference signal" may be referred to as a beam failure detection (BFD) reference signal. The information about the beam used to recover the link may include an index of a new reference signal with good reception quality selected by the UE. The "new reference signal with good reception quality" may be referred to as a candidate beam detection (CBD) reference signal.

[0348] In conventional beam recovery procedures, SSBs and CSI-RS can be used as BFD RSs and CBD RSs, and conventionally available SSBs are limited to those belonging to the PCell to which the UE is attached or camped, or the SCell configured for the UE. Therefore, according to embodiments of this disclosure, in order to use an SSB that is a cell or TRP of a PCell to which the UE is not attached or camped, or a PCI not configured as an SCell, the PCI to which the SSB belongs can also be indicated when the SSB is indicated as a BFD RS and / or CBD RS. For example, when an SSB is used as a BFD RS and / or CBD RS for a beam recovery procedure for a PCell, the parameter indicating the PCI (physCellId) can be indicated together with the SSB index, as shown in the table below.

[0349]

[0350] The default values ​​of the PCI parameters configured in the foregoing embodiments can be configured. For example, when physCellId is not indicated, the default value of physCellId can be the PCI of the PCell to which the UE is attached or resides or the configured SCell.

[0351] Next, in the foregoing embodiments, it can be determined whether PCI parameters can be configured in the SSB based on the UE capability report, which can be similar to... Figure 17As described in [the document], the UE capability report regarding multi-TRP operations can report both intra-cell multi-TRP operations and inter-cell multi-TRP operations together (i.e., report whether both operations are possible or impossible), or it can report whether both operations are possible separately. Subsequently, the base station can configure multi-TRP operations for UEs capable of performing them. The configuration of multi-TRP operations refers to the configuration of the SSB used to measure inter-cell multi-TRP for L1-RSRP / L1-SINR measurements or BFD / CBD procedures. When configuring this operation, pre-agreed constraints can be configured separately. For example, a pre-agreed constraint could be a condition where the deriveSSB-IndexFromCell parameter is configured to be true, thus the base station aligns the subframe number (SFN) and frame boundary for each cell. When inter-cell multi-TRP operations are impossible, the base station can be configured not to perform multi-TRP operations; that is, when using SSBs for L1-RSRP / L1-SINR measurements or BFD / CBD procedures, only the SSB of the serving cell is used. Based on the aforementioned configuration, the UE can perform multiple TRP operations between cells or perform only single-cell operations.

[0352] According to embodiments of the present disclosure described above, in a wireless communication system, a base station can send at least one MAC control element (MAC CE) and downlink control information (DCI) to allocate multiple physical downlink shared channels (PDSCH) to multiple UEs in order to support joint transmission (JT).

[0353] A method for a UE to perform communication in a wireless communication system according to embodiments of the present disclosure may include: sending capability information about the UE to a base station, the capability information including information about whether cooperative communication is supported; when the UE supports cooperative communication, obtaining information from the base station via Radio Resource Control (RRC) about whether cooperative communication is activated; identifying the format of a MAC control element (CE) received from the base station based on whether cooperative communication is activated by the base station; determining the Transmission Configuration Indicator (TCI) state of each Transmitter Receiver Point (TRP) based on the identified MAC CE format; and receiving a PDSCH sent from one or more TRPs by referring to the determined TCI state.

[0354] A method for a UE to perform communication in a wireless communication system according to embodiments of the present disclosure may include: sending capability information about the UE to a base station, the capability information including information about whether cooperative communication is supported; when the UE supports cooperative communication, obtaining information from the base station via Radio Resource Control (RRC) about whether cooperative communication is activated; detecting downlink control information (DCI) sent from the base station based on whether cooperative communication is activated by the base station; and receiving the PDSCH allocated by each DCI by referring to the Transmission Configuration Indication (TCI) state indicated by each DCI when two or more of the detected DCIs perform PDSCH allocation for a specific time / frequency resource.

[0355] In a method for a UE to perform communication in a wireless communication system according to an embodiment of the present disclosure, the operation of determining the TCI state may include: when cooperative communication is activated, the base station identifies information about one or more TCI states activated according to one or more MAC CEs.

[0356] In a method for a UE to perform communication in a wireless communication system according to an embodiment of the present disclosure, the operation of determining the TCI state may include: when cooperative communication is activated, the base station identifies information about one or more TCI states indicated by one or more DCIs.

[0357] In a method for a UE to perform communication in a wireless communication system according to an embodiment of the present disclosure, the operation of determining the TCI state may include the following operation: when cooperative communication is activated, the base station references a first physical cell identifier (PCI) for a quasi-co-location (QCL) information and a second PCI for another QCL information when referencing QCL information based on one or more TCI states indicated from one or more DCIs.

[0358] The method for a UE to perform communication in a wireless communication system according to embodiments of this disclosure may further include: updating the beam direction of the PDCCH or PDSCH based on the active TCI state pairs of each TRP included in the MAC CE.

[0359] The method for a UE to perform communication in a wireless communication system according to embodiments of the present disclosure may further include: receiving downlink control information (DCI); and determining a DMRS port for cooperative communication from a preset field in the received DCI when it is determined that the base station has activated cooperative communication.

[0360] The method for a UE to perform communication in a wireless communication system according to embodiments of the present disclosure may further include: when it is determined that a base station is activating cooperative communication, an operation of identifying a field including information about a DMRS port for cooperative communication from a preset field in a DCI received from the base station; and an operation of determining the DMRS port for cooperative communication based on the value included in the identified field.

[0361] A method for a base station to perform communication in a wireless communication system according to an embodiment may include: receiving capability information about a UE, the capability information including information about whether cooperative communication is supported; when the UE supports cooperative communication, sending information to the UE via RRC about whether cooperative communication is activated; and sending a MAC control element (CE) including information about the Transmission Configuration Indication (TCI) status of a plurality of Transmit Receive Points (TRPs).

[0362] Figure 18 This is a block diagram illustrating the structure of a UE according to some embodiments.

[0363] refer to Figure 18 The UE may include a UE receiver 18-00, a UE transmitter 18-10, and a UE processor 18-05. The UE receiver 18-00 and the UE transmitter 18-10 may be collectively referred to as a transceiver. The UE receiver 18-00, UE transmitter 18-10, and UE processor 18-05 of the UE can operate according to the aforementioned communication method of the UE. However, the components of the UE are not limited to the foregoing examples. For example, the UE may include more components (e.g., memory) or fewer components than those described above. Furthermore, the UE receiver 18-00, UE transmitter 18-10, and UE processor 18-05 may be configured as a single chip.

[0364] UE receiver 18-00 and UE transmitter 18-10 (or transceiver) can transmit signals to and receive signals from the base station. Here, signals may include control information and data. For this purpose, the transceiver may include an RF transmitter for up-converting and amplifying the transmitted signal, and an RF receiver for performing low-noise amplification and down-converting the received signal. However, this is merely one embodiment of the transceiver, and the components of the transceiver are not limited to RF transmitters and RF receivers.

[0365] In addition, the transceiver can receive signals via a radio channel to output signals to the UE processor 18-05, and can also transmit signals output from the UE processor 18-05 via a radio channel.

[0366] The memory (not shown) can store programs and data required for UE operation. Additionally, the memory can store control information or data included in signals received by the UE. The memory can be configured as a storage medium, such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

[0367] The UE processor 18-05 can control a series of processes, enabling the UE to operate according to the foregoing embodiments of this disclosure. The UE processor 18-05 can be configured as a controller or one or more processors.

[0368] Figure 19 This is a block diagram illustrating the structure of a base station according to some embodiments.

[0369] refer to Figure 19 The base station may include a base station receiver 19-00, a base station transmitter 19-10, and a base station processor 19-05. The base station receiver 19-00 and the base station transmitter 19-10 may be collectively referred to as a transceiver. The base station receiver 19-00, base station transmitter 19-10, and base station processor 19-05 of the base station can operate according to the aforementioned communication method of the base station. However, the components of the base station are not limited to the foregoing examples. For example, the base station may include more components (e.g., memory) or fewer components than those described above. Furthermore, the base station receiver 19-00, base station transmitter 19-10, and base station processor 19-05 may be configured as a single chip.

[0370] The base station receiver 19-00 and the base station transmitter 19-10 (or transceiver) can transmit signals to and receive signals from the UE. Here, the signals may include control information and data. For this purpose, the transceiver may include an RF transmitter for up-converting and amplifying the transmitted signal, and an RF receiver for performing low-noise amplification and down-converting the received signal. However, this is merely one embodiment of the transceiver, and the components of the transceiver are not limited to RF transmitters and RF receivers.

[0371] In addition, the transceiver can receive signals via a radio channel to output signals to the base station processor 19-05, and can also transmit signals output from the base station processor 19-05 via a radio channel.

[0372] The memory (not shown) can store programs and data required for base station operation. Additionally, the memory can store control information or data included in signals acquired by the base station. The memory can be configured as a storage medium, such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

[0373] The base station processor 19-05 can control a series of processes, enabling the base station to operate according to the foregoing embodiments. The base station processor 19-05 can be configured as a controller or one or more processors.

[0374] The embodiments of this disclosure described and illustrated in the specification and drawings are merely specific examples presented to readily explain the technical content of this disclosure and aid in understanding it, and are not intended to limit the scope of this disclosure. That is, it will be apparent to those skilled in the art that other variations based on the technical ideas of the embodiments can be implemented. Furthermore, the various embodiments described above can be combined as needed. For example, embodiments 1 to 4 of this disclosure can be combined in whole or in part to operate a base station and a terminal.

Claims

1. A method executed by a user equipment (UE) in a communication system, the method comprising: Information for synchronization signals and physical broadcast channel block (SSB) resource sets is received from the base station, wherein the information includes an SSB index associated with the SSB resource set; Receive SSBs associated with the SSB resource set from the base station; Identify the Layer 1 Reference Signal Received Power (L1-RSRP) associated with the SSB; and The base station sends Channel State Information (CSI) associated with the L1-RSRP, which is linked to the SSB. The information includes the Physical Cell Identifier (PCI) of the SSB associated with the SSB resource set, and Each PCI is associated with a corresponding SSB index within the SSB index associated with the SSB resource set.

2. The method according to claim 1, wherein, The PCI of an SSB associated with an SSB resource set includes at least one PCI that is different from the PCI of the serving cell.

3. The method according to claim 1, further comprising: Information for the Transmission Configuration Indicator (TCI) status is received from the base station, and the information for the TCI status is associated with a PCI that is different from the PCI of the serving cell.

4. The method according to claim 3, wherein, The information used for TCI status indicates that the SSB associated with a PCI different from the PCI of the serving cell is used as a QCL reference signal.

5. A method performed by a base station in a communication system, the method comprising: Send information for synchronization signals and physical broadcast channel block (SSB) resource sets to the user equipment (UE), wherein the information includes an SSB index associated with the SSB resource set; Send the SSB associated with the SSB resource set to the UE; and The UE receives Channel State Information (CSI) associated with the Layer 1 Reference Signal Received Power (L1-RSRP), which is related to the SSB. The information includes the Physical Cell Identifier (PCI) of the SSB associated with the SSB resource set, and Each PCI is associated with a corresponding SSB index within the SSB index associated with the SSB resource set.

6. The method according to claim 5, wherein, The PCI of an SSB associated with an SSB resource set includes at least one PCI that is different from the PCI of the serving cell.

7. The method according to claim 5, further comprising: Information for the Transmission Configuration Indicator (TCI) status is sent to the UE, and the information for the TCI status is associated with a PCI that is different from the PCI of the serving cell.

8. The method according to claim 7, wherein, The information used for TCI status indicates that the SSB associated with a PCI different from the PCI of the serving cell is used as a QCL reference signal.

9. A user equipment (UE) in a communication system, the UE comprising: transceiver; and The controller is configured as follows: Information for synchronization signals and physical broadcast channel block (SSB) resource sets is received from the base station, wherein the information includes an SSB index associated with the SSB resource set; Receive SSBs associated with the SSB resource set from the base station; Identify the Layer 1 Reference Signal Received Power (L1-RSRP) associated with the SSB; and The base station sends Channel State Information (CSI) associated with the L1-RSRP, which is linked to the SSB. The information includes the Physical Cell Identifier (PCI) of the SSB associated with the SSB resource set, and Each PCI is associated with a corresponding SSB index within the SSB index associated with the SSB resource set.

10. The UE according to claim 9, wherein, The PCI of an SSB associated with an SSB resource set includes at least one PCI that is different from the PCI of the serving cell.

11. The UE according to claim 9, wherein, The controller is further configured to receive information from the base station for transmitting configuration indicator (TCI) status, the information for the TCI status being associated with a PCI that is different from the PCI of the serving cell.

12. The UE according to claim 11, wherein, The information used for TCI status indicates that the SSB associated with a PCI different from the PCI of the serving cell is used as a QCL reference signal.

13. A base station in a communication system, the base station comprising: transceiver; and The controller is configured as follows: Send information for synchronization signals and physical broadcast channel block (SSB) resource sets to the user equipment (UE), wherein the information includes an SSB index associated with the SSB resource set; Send the SSB associated with the SSB resource set to the UE; and The UE receives Channel State Information (CSI) associated with the Layer 1 Reference Signal Received Power (L1-RSRP), which is related to the SSB. The information includes the Physical Cell Identifier (PCI) of the SSB associated with the SSB resource set, and Each PCI is associated with a corresponding SSB index within the SSB index associated with the SSB resource set.

14. The base station according to claim 13, wherein, The PCI of an SSB associated with an SSB resource set includes at least one PCI that is different from the PCI of the serving cell.

15. The base station according to claim 13, wherein, The controller is further configured to send information to the UE for the Transmission Configuration Indicator (TCI) state, the TCI state information being associated with a PCI different from the PCI of the serving cell, and The information used for TCI status indicates that the SSB associated with a PCI different from the PCI of the serving cell is used as a QCL reference signal.

Images