Method and apparatus for controlling measurement and reporting of adjacent channel interference in a wireless communication system

Abstract

A method and apparatus for controlling measurement and reporting of adjacent channel interference in a wireless communication system are disclosed. The method includes the steps of: transmitting a terminal capability report related to measurement and reporting of adjacent channel leakage (ACL) interference of a specific subband to a base station; receiving setting information from the base station, the setting information indicating frequency resources and time resources for measurement and reporting of the subband-specific ACL interference; measuring the subband-specific ACL interference based on the setting information; and reporting the measured subband-specific ACL interference to the base station.

Description

Technical Field

[0001] This disclosure relates to methods and apparatus for measuring and reporting adjacent channel interference in wireless communication systems. Background Technology

[0002] To meet the surging demand for wireless data services since the introduction of 4G communication systems, efforts are underway to develop enhanced 5G communication systems, or pre-5G communication systems. Therefore, 5G communication systems or pre-5G communication systems are referred to as beyond-4G network communication systems or post-LTE systems. For higher data transmission rates, 5G communication systems are considered to be implemented in the ultra-high frequency band (millimeter wave) (e.g., 60 GHz). To mitigate path loss in the ultra-high frequency band and increase the reach of radio waves, the following technologies are considered for 5G communication systems: beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO. Various technologies are also being developed for 5G communication systems to enhance networks, such as evolved or advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, cooperative multipoint (CoMP), and receive interference cancellation. There are also various other schemes being developed for 5G systems, including, for example, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC), which are advanced coding modulation (ACM) schemes, as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA), which are advanced access schemes.

[0003] The internet, a human-centric network of connections where humans generate and consume information, is now evolving into the Internet of Things (IoT), where distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE), combining IoT technology with big data processing, has emerged through connections to cloud servers. As essential technological elements for realizing IoT, such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology, sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) have recently been studied. Such an IoT environment can provide intelligent internet technology services, creating new value for human life by collecting and analyzing data generated between interconnected things. Through the convergence and integration 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 or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] Correspondingly, 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 convergence between 5G and IoT technologies.

[0005] As stated above, as wireless communication systems evolve to provide a variety of services, a method for smoothly delivering such services is needed. Specifically, a technique is needed for efficiently measuring and reporting interference between frequency bands allocated as adjacent in a wireless communication system that flexibly allocates uplink and downlink resources in both the time and frequency domains for additional coverage extension. Summary of the Invention

[0006] Technical issues

[0007] The technical objective of this disclosure is to provide a method and apparatus for measuring and reporting interference when uplink and downlink are operating simultaneously for various services in a wireless communication system.

[0008] Technical solutions

[0009] According to embodiments of this disclosure, a method performed by a user equipment (UE) configured to perform measurement and reporting of adjacent channel interference in a wireless communication system may include: sending a UE capability report to a base station relating to measurement and reporting of subband-specific adjacent channel leakage (ACL) interference; receiving from the base station configuration information indicating frequency and time resources for measurement and reporting of subband-specific ACL interference; measuring the subband-specific ACL interference based on the configuration information; and reporting the measured subband-specific ACL interference to the base station.

[0010] According to embodiments of this disclosure, a method performed by a base station configured to control the measurement and reporting of adjacent channel interference in a wireless communication system may include: receiving from a UE a UE a UE report relating to the measurement and reporting of subband-specific adjacent channel leakage (ACL) interference; sending to the UE configuration information indicating frequency and time resources for measuring and reporting subband-specific ACL interference; and receiving from the UE a measurement report of subband-specific ACL interference based on the configuration information.

[0011] According to embodiments of this disclosure, a device for a UE configured to perform measurement and reporting of adjacent channel interference in a wireless communication system may include a transceiver and a processor. The transceiver is configured to send a UE capability report to a base station relating to the measurement and reporting of subband-specific adjacent channel leakage (ACL) interference, and to receive configuration information from the base station indicating frequency and time resources for measuring and reporting subband-specific ACL interference. The processor is configured to measure the subband-specific ACL interference based on the configuration information and to control the transceiver to report the measured subband-specific ACL interference to the base station.

[0012] According to embodiments of this disclosure, a device for a base station configured to control the measurement and reporting of adjacent channel interference in a wireless communication system may include a transceiver and a processor. The transceiver is configured to receive a UE capability report related to the measurement and reporting of subband-specific adjacent channel leakage (ACL) interference from a UE, send configuration information to the UE indicating frequency and time resources for the measurement and reporting of subband-specific ACL interference, and receive a measurement report of subband-specific ACL interference from the UE based on the configuration information. The processor is configured to send inter-base station shared information generated based on the configuration information and / or the measurement report to another base station.

[0013] Beneficial effects

[0014] The disclosed embodiments may provide a method and apparatus for measuring and reporting interference signals in a wireless communication system for efficient uplink or downlink transmission / reception. Attached Figure Description

[0015] Figure 1 This is a view showing the basic structure of the time-frequency domain, which is the radio resource region of a wireless communication system;

[0016] Figure 2 This is a view showing the time slot structure considered in a wireless communication system;

[0017] Figure 3 This is a view showing an example of the configuration of the bandwidth portion in a wireless communication system;

[0018] Figure 4 This is a view illustrating an example of how bandwidth changes in a wireless communication system;

[0019] Figure 5 This is a view illustrating an example of a control resource set (CORESET) in a wireless communication system in which the downlink control channel is transmitted;

[0020] Figure 6A , Figure 6B and Figure 6CThis is a view illustrating an example of frequency domain resource allocation in a wireless communication system;

[0021] Figure 7 This is a view illustrating an example of time-domain resource allocation in a wireless communication system;

[0022] Figure 8A and 8B This is a view illustrating an example of time-domain resource allocation based on subcarrier spacing in a wireless communication system;

[0023] Figure 9A , 9B 9C and 9C are views illustrating the radio protocol structure of a base station and a UE in a wireless communication system;

[0024] Figure 10 This is a view showing an example of configuring CSI-RS through CSI-RS resource mapping;

[0025] Figure 11A and 11B This is a view illustrating an example of a non-periodic CSI reporting method;

[0026] Figure 12A , 12B 12C and 12C are views illustrating examples of various operating scenarios for the SRS;

[0027] Figure 13 This is a view showing the uplink transmission structure of a wireless communication system;

[0028] Figure 14 This is a view showing the structure in which SRS are assigned in each subband;

[0029] Figure 15 This is a view showing data transmission / reception considering downlink data channel and rate matching resources;

[0030] Figure 16 This is a view illustrating an example of an uplink-downlink configuration considered in a wireless communication system;

[0031] Figure 17 This is a view showing an example of an uplink-downlink configuration in an XDD system;

[0032] Figure 18 This is a view showing an example of the uplink-downlink configuration and bandwidth portion (BWP) configuration of a base station in an XDD system;

[0033] Figure 19 This is a view illustrating an example of a TRS pattern according to an embodiment of the present disclosure;

[0034] Figure 20This is a view illustrating an example of a 1-port CSI-RS configuration according to an embodiment of the present disclosure;

[0035] Figure 21 This is a view illustrating an example of uplink receive frequency response measurement during uplink independent transmission / reception according to an embodiment of the present disclosure;

[0036] Figure 22 This is a view illustrating an example of uplink receive frequency response measurement during simultaneous uplink / downlink transmission / reception according to an embodiment of the present disclosure;

[0037] Figure 23 This is a view illustrating an example of an uplink-downlink interference scenario in an XDD system according to an embodiment of the present disclosure;

[0038] Figure 24A and 24B This is a view illustrating an example of frequency domain resource configuration for adjacent channel leakage interference measurement according to an embodiment of the present disclosure;

[0039] Figure 25 This is a view illustrating an example of uplink frequency hopping considering adjacent channel leakage interference measurement and reporting according to an embodiment of this disclosure;

[0040] Figure 26 This is a view illustrating an example of an interface for sharing adjacent channel leakage interference measurements according to an embodiment of this disclosure;

[0041] Figure 27A This is a flowchart illustrating UE operation according to embodiments of the present disclosure;

[0042] Figure 27B This is a flowchart illustrating base station operation according to embodiments of the present disclosure;

[0043] Figure 28 This is a view illustrating an example of a base station implementation according to an embodiment of the present disclosure;

[0044] Figure 29 This is a view illustrating another example of a base station implementation according to an embodiment of the present disclosure;

[0045] Figure 30 This is a view illustrating another example of a base station implementation according to an embodiment of the present disclosure;

[0046] Figure 31 This is a view illustrating another example of a base station implementation according to an embodiment of the present disclosure;

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

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

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

[0050] In describing the embodiments, descriptions of techniques known in the art and not directly related to this disclosure have been omitted. This is to further clarify the key points of this disclosure without making them unclear.

[0051] For the same reason, some elements may be exaggerated or shown schematically. The size of each element does not necessarily reflect its true size. In all figures, the same reference numerals are used to refer to the same elements.

[0052] The advantages and features of this disclosure, as well as methods for achieving these advantages and features, can be understood from the embodiments described below in conjunction with the accompanying drawings. However, the invention is not limited to the embodiments disclosed herein, and various modifications can be made thereto. The embodiments disclosed herein are provided only to inform those skilled in the art of the scope of this disclosure. The invention is defined only by the appended claims. Throughout the specification, the same reference numerals denote the same elements. Detailed descriptions of known techniques or functions may be omitted when it is determined that the subject matter of the invention is unclear. The terminology used herein is defined in consideration of the functions in this disclosure and may be replaced with other terms depending on the intent or practice of the user or operator. Therefore, these terms should be defined based on the entire disclosure.

[0053] In the following description, a base station (BS) is an entity that performs resource allocation to a UE and can be at least one of a 5G (or NR) gNodeB (gNB), an LTE eNodeB (eNB), a 3GPP Node B (NB), a radio access unit, a base station controller, or a network node. A user equipment (UE) can include a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. In this disclosure, downlink (DL) refers to the radio transmission path of a signal from the base station to the UE, and uplink (UL) refers to the radio transmission path of a signal from the UE to the base station. Although LTE or LTE-A systems are described below as examples, embodiments can be applied to other communication systems with similar technical backgrounds or channel modes. For example, 5G mobile communication technology (or new radio, NR) developed after LTE-A can be included therein, and 5G below can be a concept encompassing legacy LTE, LTE-A, and other similar services. Furthermore, it will be determined by those skilled in the art that embodiments can be modified within the scope of the invention without explicitly departing from it, and such modifications can be applied to other communication systems.

[0054] It should be understood that each block in a flowchart, and combinations thereof, can be executed by computer program instructions. Since computer program instructions can be located in the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, the instructions, executed by the processor of the computer or other programmable data processing apparatus, produce means for performing the functions described in combination with each block(s) in each flowchart. Since computer program instructions can be stored in a computer-usable or computer-readable memory that can be functionally implemented in a particular manner for the computer or other programmable data processing apparatus, the instructions stored in the computer-usable or computer-readable memory can produce a product comprising instruction components for performing the functions described in combination with each block(s) in each flowchart. Because computer program instructions can be located in a computer or other programmable data processing apparatus, when a series of operational steps are performed on the computer or other programmable data processing apparatus, the instructions that generate the process executed by the computer and operate the computer or other programmable data processing apparatus can provide steps for performing the functions described in combination with each block(s) in each flowchart.

[0055] Furthermore, each box can represent a module, code segment, or code section that includes one or more executable instructions for performing a specific logical function. It should also be noted that in some alternative execution examples, the functions mentioned in the boxes may appear in different orders. For example, depending on the corresponding function, two boxes shown consecutively may be executed substantially simultaneously or in reverse order.

[0056] As used herein, the term "cell" means a software element or hardware element, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). A cell plays a specific role. However, the term "cell" is not limited to referring to a software or hardware element. A "cell" may be configured in an addressable storage medium or may be configured to reproduce one or more processors. Thus, by way of example, a "cell" includes elements such as software elements, object-oriented software elements, class elements and task elements, procedures, functions, attributes, processes, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data schemas, tables, arrays, and variables. The functionality provided in an element or "cell" may be combined with additional elements or may be divided into sub-elements or sub-cells. Furthermore, an element or "cell" may be implemented as one or more CPUs in a reproduction device or secure multimedia card. Additionally, in this disclosure, "...cell" may include one or more processors.

[0057] Wireless communication systems have evolved from voice-centric services to broadband wireless communication systems (such as 3GPP High-Speed ​​Packet Access (HSPA), LTE or Evolved Universal Terrestrial Radio Access (E-UTRA), LTE-A Advanced, LTE-pro, 3GPP2 High-Speed ​​Packet Data (HRPD), Ultra Mobile Broadband (UMB), or the IEEE 802.16e communication standard) to provide high data rates and high-quality packet data services.

[0058] As a representative example of such a broadband wireless communication system, the LTE system employs Orthogonal Frequency Division Multiplexing (OFDM) for the downlink and Single-Carrier Frequency Division Multiple Access (SC-FDMA) for the uplink. The uplink refers to the radio link through which the UE transmits data or control signals to the base station (BS), and the downlink refers to the radio link through which the base station transmits data or control signals to the UE. This multiple access scheme allocates and operates time-frequency resources carrying data or control information for each user without overlap, i.e., maintaining orthogonality, thereby distinguishing the data or control information for each user.

[0059] Post-LTE communication systems (e.g., 5G communication systems) need to simultaneously support a variety of requirements to freely reflect the diverse needs of users or service providers. Services considered for 5G communication systems include, for example, enhanced mobile broadband (eMBB), massive machine-type communications (MMTC), or ultra-reliable low-latency communications (URLLC).

[0060] Compared to LTE, LTE-A, or LTE-pro, eMBB aims to provide further enhanced data transmission rates. For example, for a single base station, eMBB for a 5G communication system needs to provide a peak data rate of 20Gbps during download and 10Gbps during uplink. 5G communication systems also need to provide increased user-aware data rates while delivering these peak data rates. To meet these requirements, further enhancements to various transmit (TX) / receive (RX) technologies and multiple-input multiple-output (MIMO) may be necessary. LTE uses up to 20MHz of TX bandwidth in the 2GHz band to transmit signals, while 5G communication systems employ wider frequency bandwidths in the 3GHz to 6GHz or higher bands to meet the data rates required by 5G communication systems.

[0061] Attention is being drawn to Bandwidth Partial (BWP) technology, which divides an entire carrier frequency band into several bands that each UE's base station can support when the base station supports wideband frequencies. In other words, if the base station supports BWP and a particular UE has a small BW capability, the BWP can support a small band for the UE, and the number of bands can be reduced by changing the BWP, thus reducing the UE's energy consumption. There is also the effect of supporting various services for a UE without delay by supporting different frame structures in each of the several BWPs while changing the BWP. BWP technology can be applied to control or data channels that are pre-defined in a one-to-one correspondence between a UE and the base station. Furthermore, even for control and data channels used to transmit common signals (e.g., synchronization signals, physical broadcast channel (PBCH), and system information) sent by the base station to multiple UEs in the system, they can be transmitted only in the configured BWP, thus saving base station energy.

[0062] mMTC is also considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To effectively deliver IoT, mMTC needs to support at least one of the following: support for a large number of UEs in a cell, enhanced UE coverage, enhanced battery life, or UE cost savings. IoT devices connect to various sensors or devices to provide communication capabilities; therefore, it needs to support multiple UEs per cell (e.g., 1,000,000 UEs / km). 2 Because UEs supporting mMTC are likely to be located in shadow areas not covered by the cell, such as underground in buildings, depending on the nature of the service, they require wider coverage compared to other services provided by 5G communication systems. UEs supporting mMTC also need very long battery life, such as 10 to 15 years, due to the need for low cost and the difficulty in frequently replacing batteries.

[0063] URLLC is a cellular-based mission-critical wireless communication service. Examples include services used in at least one of the following: remote control of robots or machines, industrial automation, unmanned aerial vehicles, remote healthcare, or emergency alerts. This requires URLLC to provide very low latency and very high reliability communication. For example, services supporting URLLC need to meet an air interface latency of less than 0.5 milliseconds while having 10... -5 Or even lower packet error rates. Therefore, for services that support URLLC, 5G communication systems are required to provide shorter Transmission Time Intervals (TTIs) than other services, while ensuring reliable communication links by allocating wide resources in the frequency band.

[0064] The three services of a 5G communication system (hereinafter referred to as 5G system), namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted within a single system. In this case, different TX / RX schemes and TX / RX parameters can be used to meet their different requirements.

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

[0066] Figure 1 This is a view showing the basic structure of the time-frequency domain, which is the radio resource area of ​​a 5G system.

[0067] exist Figure 1 In this diagram, the horizontal axis refers to the time domain, and the vertical axis refers to the frequency domain. The basic unit of a resource in both the time and frequency domains is a resource element (RE) 101, which can be defined as an orthogonal frequency division multiplexing (OFDM) symbol (or a discrete Fourier transform extended OFDM (DFT-s-OFDM) symbol) 102 on the time axis, and a subcarrier 103 in the frequency domain. In the frequency domain, One (e.g., 12) consecutive REs can constitute a resource block (RB) 104. In the time domain A series of consecutive OFDM symbols can form a subframe 110.

[0068] Figure 2 This is a view showing the time slot structure considered in a 5G system.

[0069] Figure 2 An example structure including frame 200, subframe 201, and time slot 202 is shown. A frame 200 can be defined as 10 ms. A subframe 201 can be defined as 1 ms; therefore, a frame 200 can consist of a total of 10 subframes 201. Furthermore, a time slot 202 or 203 can be defined as 14 OFDM symbols. In other words, the number of symbols in each time slot ( The value is 14. A subframe 201 may consist of one or more time slots 202 and 203, and the number of time slots 202 and 203 in each subframe 201 may vary depending on μ (204 or 205), where μ is the setting value of the subcarrier spacing.

[0070] exist Figure 2 In the example, the slot structures with μ=0 (204) and μ=1 (205) as the set subcarrier spacing values ​​are shown. When μ = 0 (204), a subframe 201 may include one slot 202, and when μ = 1 (205), a subframe 201 may include two slots (203). In other words, the number of slots per subframe depends on the set subcarrier spacing value μ. The number of time slots per frame can vary. They can be different. In this embodiment, based on each subcarrier spacing μ, and It can be defined in Table 1 below.

[0071] [Table 1]

[0072]

[0073] In 5G wireless communication systems, for initial access, a synchronization signal block (SSB) (or SS block or SS / PBCH block) can be transmitted, and the synchronization signal block can include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). During the initial access phase when a UE first accesses the system, the UE can obtain downlink time-domain and frequency-domain synchronization from the synchronization signals through cell search and execute the cell ID. The synchronization signals can include the PSS and SSS.

[0074] The UE can receive the Transmit Master Information Block (MIB) PBCH from the base station to obtain system information related to transmission and reception (such as system bandwidth or related control information) and basic parameter values. Based on the obtained information, the UE can decode the Physical Downlink Control Channel (PDCCH) and Physical Downlink Shared Channel (PDSCH) to obtain the System Information Block (SIB). Subsequently, the UE exchanges identifiers with the base station through the random access phase and initially accesses the network via registration and authentication steps.

[0075] Synchronization signals are used as reference signals for cell search and can be transmitted using subcarrier spacing appropriate to the channel environment (e.g., including phase noise) for each frequency band to which they are applied. A 5G base station can transmit multiple synchronization signal blocks depending on the number of analog beams to be operated. PSS and SSS can be mapped to 12 RBs and transmitted, and PBCH can be mapped to 24 RBs and transmitted.

[0076] The following describes in detail the configuration of the bandwidth component (BWP) in a 5G communication system with reference to the accompanying drawings.

[0077] Figure 3 This is a view showing an example of the configuration of the bandwidth portion in a wireless communication system.

[0078] Figure 3 The diagram illustrates an example where the UE bandwidth 300 is divided into two bandwidth portions, for example, bandwidth portion #1 (BWP #1) 301 and bandwidth portion #2 (BWP #2) 302. The base station can configure one or more bandwidth portions in the UE, and can configure the information shown in Table 2 below for each bandwidth portion.

[0079] [Table 2]

[0080]

[0081] Here, bwp-Id represents the bandwidth portion identifier, locationAndBandwidth indicates the location of the bandwidth portion, subcarrierSpacing indicates the subcarrier spacing, and cyclicPrefix indicates the length of the cyclic prefix (CP).

[0082] The bandwidth configuration is not limited to this; various other BWP-related parameters besides the configuration information described above can be configured in the UE. The base station can transmit configuration information to the UE via higher-layer signaling (e.g., Radio Resource Control (RRC) signaling). At least one of the configured bandwidth portions can be activated. Whether a configured bandwidth portion is activated can be transmitted from the base station to the UE semi-statically via RRC signaling or dynamically via downlink control information (DCI).

[0083] Prior to Radio Resource Control (RRC) connection, the UE can be configured by the base station via the Master Information Block (MIB) with an Initial Bandwidth Part (BWP) for initial access. Specifically, the UE can receive configuration information regarding the search space and control resource set (CORESET), where CORESET represents a control area. Within this control area, the PDCCH for receiving system information required for initial access (e.g., residual system information, RMSI, or SIB1) can be transmitted via the MIB during the initial access phase. The CORESET and search space configured by the MIB can each be considered to have an identifier (ID) of 0.

[0084] The base station can provide configuration information to the UE via the MIB, which includes frequency allocation information, time allocation information, or at least one parameter set for control area #0. Furthermore, the base station can provide the UE with configuration information regarding the timing and monitoring period of control area #0, i.e., configuration information about search space #0, via the MIB. The UE can consider the frequency range obtained from the MIB and set to control area #0 as the initial BWP for initial access. In this case, the identifier (ID) of the initial BWP can be considered as 0.

[0085] The bandwidth configurations supported in the aforementioned 5G can be used for various purposes.

[0086] In this embodiment, the configuration of the bandwidth portion can support UEs with a smaller supported bandwidth than the system bandwidth. For example, the base station can configure information in the UE indicating the frequency location of the bandwidth portion (e.g., configuration information 2), allowing the UE to send / receive data at a specific frequency location within the system bandwidth.

[0087] In this embodiment, to support different parameter sets, the base station can configure the UE to have multiple bandwidth portions. For example, to support data transmission / reception using both 15kHz and 30kHz subcarrier intervals for some UEs, the base station can configure the UE to have two bandwidths, such as 15kHz and 30kHz subcarrier intervals. Different bandwidth portions can be frequency-division multiplexed, and the bandwidth portion configured for the corresponding subcarrier interval can be activated when data is transmitted / received at a specific subcarrier interval.

[0088] According to an embodiment, to reduce the power consumption of the UE, the base station can configure the UE to have bandwidth portions with different bandwidth sizes. For example, significant power consumption may occur when the UE supports bandwidths exceeding a very large bandwidth (e.g., 100 MHz) and uses that bandwidth to send / receive data. In particular, using a large bandwidth of 100 MHz to monitor unnecessary downlink control channels in the absence of service is very inefficient in terms of power consumption. To reduce the power consumption of the UE, the base station can configure a relatively small bandwidth portion for the UE, such as a 20 MHz bandwidth portion. In the absence of service, the UE can perform monitoring in the 20 MHz bandwidth, and if data is available, the UE can send / receive data in the 100 MHz bandwidth according to instructions from the base station.

[0089] In this embodiment, during the bandwidth configuration phase, the UE prior to RRC connection can receive initial bandwidth configuration information via the MIB during the initial access phase. Specifically, the UE can obtain the configuration of the control area (e.g., CORESET) of the downlink control channel on the Physical Broadcast Channel (PBCH) from the MIB, where the DCI used for scheduling SIBs can be transmitted. The bandwidth configured by the MIB can be considered as the initial BWP, and the UE can receive the Physical Downlink Shared Channel (PDSCH) for transmitting SIBs via the initial BWP. The initial BWP can be used for other System Information (OSI), paging and random access, and receiving SIBs.

[0090] In an embodiment, if the UE is configured with one or more BWPs, the base station can use a BWP indicator in the DCI to indicate a change in the BWP to the UE. As an example, when the UE's currently active bandwidth portion is... Figure 3 When the bandwidth portion #1 301 is specified in the DCI, the base station can use the bandwidth portion indicator in the DCI to indicate the bandwidth portion #2 302 to the UE, and the UE can change the bandwidth portion to the bandwidth portion #2 302 indicated by the bandwidth portion indicator in the DCI.

[0091] As described above, since DCI-based bandwidth portion changes can be indicated by the DCI scheduling PDSCH or Physical Uplink Shared Channel (PUSCH), if the UE receives a bandwidth portion change request (e.g., a bandwidth portion indicator), the UE should be able to successfully receive or transmit the DCI-scheduled PDSCH or PUSCH within the changed bandwidth portion. To this end, the standard specifies the required conversion time T when changing the bandwidth portion. BWP The requirements can be defined as shown in Table 3 below.

[0092] [Table 3]

[0093]

[0094] Depending on the UE's capabilities, the latency requirement for bandwidth portion changes can support either Type 1 or Type 2. The UE can report the supported bandwidth portion latency time type to the base station.

[0095] Figure 4 This is a view illustrating an example of a method for changing a portion of the bandwidth in a wireless communication system.

[0096] refer to Figure 4 Within the UE bandwidth 400, either bandwidth portion #1 405 or bandwidth portion #2 410 can be configured for the UE. Bandwidth portion #1 405 can occupy a portion of the UE bandwidth 400, and bandwidth portion #2 410 can occupy the entire UE bandwidth 400. In time slot n-1 (e.g., time slot #0 425), the UE can perform communication within the configured bandwidth portion #1 405.

[0097] The UE can receive the DCI, including the bandwidth portion change indicator 415, in time slot n (e.g., time slot #1 430). Depending on the requirement for the bandwidth portion (BWP) transition time 420, the UE can receive the DCI no later than time slot n+T. BWP The time 435 completes the change to the new bandwidth section (e.g., bandwidth section #2 410) indicated by the bandwidth section change indicator 415, and transmit / receive is performed on the data channel scheduled by DCI in bandwidth section #2 410.

[0098] When scheduling data channels in bandwidth section #2 410, the base station can consider the UE's bandwidth section switching time (T). BWPThe time-domain resource allocation of the data channel is determined at time 420. In other words, when scheduling the data channel in bandwidth portion #2 410, the base station can schedule the data channel in time slots after the bandwidth portion transition time 420 (e.g., time slots #2 and #3 435 and 440) during the determination of the time-domain resource allocation of the data channel. Therefore, the UE may not expect the DCI indication indicating the bandwidth portion change to be less than the bandwidth portion transition time (T). BWP )420 time slot offset (K0 or K2).

[0099] In an embodiment, if the UE has already received a DCI indicating a partial change in bandwidth (e.g., DCI format 1_1 or 0_1), the UE may refrain from transmitting or receiving for a period from the third symbol of the time slot in which the PDCCH including the DCI has been received to the time slot start point indicated by the time slot offset (K0 or K2) value indicated by the time domain resource allocation indicator field in the DCI. For example, if the UE receives a DCI indicating a partial change in bandwidth in time slot n, and the time slot offset value indicated by the DCI is K, the UE may refrain from transmitting or receiving from the third symbol of time slot n to the symbol preceding the previous symbol of time slot n+K (i.e., the last symbol of time slot n+K-1).

[0100] Next, we describe the methods in 5G for configuring transmit / receive related parameters for each bandwidth segment.

[0101] The UE can be configured with one or more bandwidth portions by the base station, and can be further configured with transmission / reception parameters for each configured bandwidth portion (including, for example, configuration information related to data channels and / or control channels). For example, when the UE is in Figure 3 When bandwidth section #1 301 and bandwidth section #2 302 are configured, the UE can be configured with a transmit / receive parameter set #1 for bandwidth section #1 301 and a transmit / receive parameter set #2 for bandwidth section #2 302. When bandwidth section #1 301 is active, the UE can perform transmit / receive with the base station based on transmit / receive parameter set #1, and when bandwidth section #2 302 is active, the UE can perform transmit / receive with the base station based on transmit / receive parameter set #2.

[0102] More specifically, the base station can configure the following parameters for the UE.

[0103] In this embodiment, the information in Table 4 below can be configured for the uplink bandwidth portion.

[0104] [Table 4]

[0105]

[0106] Here, bwp-Id is the bandwidth identifier, bwp-Common is cell-specific or common configuration information, bwp-Dedicated is UE-specific configuration information, genericParameters are general parameters, rach-ConfigCommon is common configuration information related to random access, pusch-ConfigCommon is common configuration information related to PUSCH, pucch-ConfigCommon is common configuration information related to PUSCH, pucch-Config is UE-specific configuration information related to PUSCH, pucch-Config is UE-specific configuration information related to PUSCH, configuredGrantConfig is configuration information related to configured grants, srs-Config is configuration information related to sounding reference signals (SRS), and beamFailureRecoveryConfig is configuration information related to beam failure recovery.

[0107] According to Table 4 above, the UE can be configured by the base station with cell-specific (or common or cell-common) transmission-related parameters (e.g., parameters related to at least one of the Random Access Channel (RACH), Physical Uplink Control Channel (PUCCH), or Physical Uplink Shared Channel for Uplink Data) (corresponding to BWP-UplinkCommon). Furthermore, the UE can be configured by the base station with UE-specific (or dedicated) transmission-related parameters (e.g., parameters related to at least one of PUCCH, PUSCH, Unlicensed Uplink Transmission (e.g., a configured licensed PUSCH), or Sounding Reference Signal (SRS)) (corresponding to BWP-UplinkDedicated).

[0108] In this embodiment, the information in Table 5 below can be configured for the downlink bandwidth portion.

[0109] [Table 5]

[0110]

[0111] According to Table 5 above, the UE can be configured by the base station with cell-specific (or common or cell-common) reception-related parameters (e.g., parameters related to PDCCH and / or PDSCH) (corresponding to BWP-DownlinkCommon). Furthermore, the UE can be configured by the base station with UE-specific (or dedicated) reception-related parameters (e.g., parameters related to at least one of PDCCH, PDSCH, unlicensed downlink data transmission (e.g., semi-persistently scheduled PDSCH), or radio link surveillance (RLM) (corresponding to BWP-UplinkDedicated).

[0112] Figure 5 This is a view illustrating an example of a CORESET in a wireless communication system in which the downlink control channel is transmitted.

[0113] refer to Figure 5 The UE bandwidth portion 510 is configured in the frequency domain, and two control resource sets, namely control resource set #1 501 and control resource set #2 502, are configured in a time slot 520 in the time domain. Control resource sets 501 and 502 can be configured as specific frequency resources 503 within the UE bandwidth portion 510 in the frequency domain. Furthermore, each control resource set 501 and 502 can be configured with one or more OFDM symbols in the time domain, and the number of OFDM symbols can be defined as the control resource set length (CORESET duration) 504. In the example shown, control resource set #1 501 can be configured for a control resource set length of two symbols, and control resource set #2 502 can be configured for a control resource set length of one symbol.

[0114] Each of the aforementioned control resource sets (e.g., control resource set 501 or 502) can be configured by the base station to the UE via higher-level signaling (e.g., system information, MIB, or RRC signaling). Configuring the UE with a control resource set may mean providing at least one of the following: control resource set identifier, frequency location of the control resource set, or symbol length of the control resource set.

[0115] In an embodiment, higher-level signaling information elements provided to configure the control resource set may include information as shown in Table 6.

[0116] [Table 6]

[0117]

[0118] In 5G, a set of control resources of number N can be represented in the frequency domain by N... RB CORESET It consists of RBs, and is composed of N in the time axis. symb CORESET A Control Channel Element (CCE) consists of ∈{1, 2, 3} symbols. A CCE can be composed of six Resource Groups (REGs). During one OFDM symbol, a REG can be defined as one Resource Block (RB). Within a control resource set, REGs can be indexed in time-priority order, starting with REG index 0 from the first OFDM symbol (lowest RB) of the control resource set.

[0119] In 5G, both interleaving and non-interleaving schemes can be supported as PDCCH transmission schemes. The base station can configure the UE to perform interleaved or non-interleaved transmission for each control resource set via higher-layer signaling. Interleaving can be performed within each REG bundle unit. A REG bundle can be defined as a set of one or more REGs. The UE can determine the CCE-to-REG mapping scheme for the corresponding control resource set based on whether interleaved or non-interleaved transmission is configured by the base station, for example, as shown in Table 7 below.

[0120] [Table 7]

[0121]

[0122] The basic unit of the download control channel (i.e., REG) can contain the RE to which the DCI is mapped and the region to which the reference signal DMRS used to decode the RE is mapped. A REG can include three DMRS REs. Depending on the aggregation level (AL), the number of CCEs required to transmit the PDCCH can be, for example, 1, 2, 4, 8, or 16, and link adaptation of the downlink control channel can be achieved using different numbers of CCEs. For example, if AL = 1, a downlink control channel can be transmitted via L CCEs. The UE needs to detect the signal but is unaware of the downlink control channel information, and for blind decoding, a search space is defined indicating the set of CCEs. The search space is the set of candidate control channels consisting of CCEs that the UE needs to attempt to decode at a given aggregation level, and since several aggregation levels with bundles of 1, 2, 4, 8, or 16 CCEs can be configured, the UE has multiple search spaces. The search space set can be defined as the set of search spaces across all configured aggregation levels.

[0123] <Search Space>

[0124] The search space can be a common search space or a UE-specific search space. UEs in a group, or all UEs, can check the common search space of the PDCCH to receive cell common control information (e.g., dynamic scheduling or paging messages for system information). For example, PDSCH scheduling allocation information regarding transmissions including the SIB of the cell service provider can be received by checking the common search space of the PDCCH. The common search space includes the PDCCHs received by a group of UEs or all UEs, and can therefore be defined as a pre-agreed set of CCEs. UE-specific PDSCH or PUSCH scheduling allocation information can be received by checking the UE-specific search space of the PDCCH. The UE-specific search space can be UE-specifically defined using various system parameters and UE identifiers.

[0125] In 5G, the parameters for the search space used for PDCCH can be configured by the base station in the UE via higher-level signaling (e.g., SIB, MIB, or RRC signaling). For example, the base station can configure the UE with at least one of the following: the number of PDCCH candidates at aggregation level L, the monitoring period of the search space, the monitoring timing of symbol cells in the time slots of the search space, the search space type (public search space or UE-specific search space), the combination of RNTI and DCI formats to be monitored in the search space, and the control resource set index to be monitored in the search space. For example, the parameters for the search space used for PDCCH may include the following information.

[0126] [Table 8]

[0127]

[0128] Based on the configuration information, the base station can configure one or more search space sets for the UE. As an example, the base station can configure search space set 1 and search space set 2 for the UE. Search space set 1 can be configured to allow the UE to monitor DCI format A scrambled with X-RNTI in a common search space, and search space set 2 can be configured to allow the UE to monitor DCI format B scrambled with Y-RNTI in a UE-specific search space.

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

[0130] According to an embodiment, combinations of DCI formats and RNTI can be monitored in a public search space. Of course, this is not limited to the examples described below.

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

[0132] DCI format 2_0, CRC scrambled by SFI-RNTI

[0133] DCI format 2_1, CRC scrambling is done by INT-RNTI.

[0134] DCI format 2_2, CRC is scrambled by TPC-PUSCH-RNTI and TPC-PUCCH-RNTI.

[0135] DCI format 2_3, CRC scrambling is done by TPC-SRS-RNTI.

[0136] According to an embodiment, within a UE-specific search space, combinations of the following DCI formats and RNTI can be monitored. Of course, this is not limited to the examples described below.

[0137] DCI format 0_0 / 1_0, CRC scrambling is done by C-RNTI, CS-RNTI, and TC-RNTI.

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

[0139] In this embodiment, RNTI can be defined and used as follows.

[0140] Cell RNTI (C-RNTI): Used to schedule UE-specific PDSCH

[0141] Temporary Cell RNTI (TC-RNTI): Used to schedule UE-specific PDSCH

[0142] Configured Scheduling RNTI (CS-RNTI): Used to schedule UE-specific PDSCHs with semi-static configuration.

[0143] Random Access RNTI (RA-RNTI): Used for scheduling PDSCH during the random access phase.

[0144] Paging RNTI (P-RNTI): Used to schedule the PDSCH sent for paging.

[0145] System Information RNTI (SI-RNTI): Used to schedule the PDSCH in which system information is sent.

[0146] Interrupted RNTI (INT-RNTI): Used to indicate whether a puncture (PDSCH) has occurred.

[0147] Transmit power control of PUSCH RNTI (TPC-PUSCH-RNTI): Used to indicate power control commands for PUSCH.

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

[0149] SRS RNTI Transmit Power Control (TPC-SRS-RNTI): Used to indicate the power control command of the SRS.

[0150] In this embodiment, the DCI format may follow the definitions in Table 9 below.

[0151] [Table 9]

[0152]

[0153] In an embodiment, in 5G, the control resource set p and the search space with aggregation level L in the search space set s can be represented by the following Equation 1.

[0154] [Equation 1]

[0155]

[0156] L: Aggregation Level

[0157] n CI Carrier index

[0158] N CCE,p The number of control channel elements (CCEs) present in the control resource set p.

[0159] n μ s,f Time slot index

[0160] M （L） p,s,max Number of PDCCH candidates at aggregation level L

[0161] m snCI = 0, …, M （L） p,s,max -1: PDCCH candidate index at aggregation level L

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

[0163] Y p,-1 = n RNTI ≠ 0, A0=39827, A1=39829, A2=39839, D=65537

[0164] -n RNTI UE identifier

[0165] In the context of a public search space, Y_(p,n) μ s,f () can be 0.

[0166] Given a UE-specific search space, Y_(p,n) μ s,f It can have values ​​that change based on the UE’s identifier (C-RNTI or ID configured by the base station in the UE) and time index.

[0167] <TCI Status>

[0168] The following describes in detail a method for configuring TCI states, which is a means of indicating or exchanging quasi-co-address (QCL) information between a UE and a base station in a 5G wireless communication system.

[0169] The base station can inform the UE of the QCL relationship between two different RSs or channels by configuring and indicating the TCI status between them through appropriate signaling. When different RSs or channels are quasi-co-located, this may mean that when estimating the channel via a reference antenna port A (hereinafter referred to as reference RS #A) and an RS antenna port B (target RS #B) with a QCL relationship, the UE is allowed to apply all or some of the large-scale channel parameters estimated from antenna port A to the channel measurement from antenna port B.

[0170] QCL can associate different parameters based on at least one of the following contexts: 1) time tracking affected by average delay and delay spread, 2) frequency tracking affected by Doppler shift and Doppler spread, 3) radio resource management (RRM) affected by average gain, or 4) beam management (BM) affected by spatial parameters. Therefore, NR can support four types of QCL relationships, as shown in Table 10 below.

[0171] [Table 10]

[0172]

[0173] Here, the spatial RX parameters may include at least one of the following: angle of arrival (AoA), power angle spectrum (PAS) of AoA, angle of departure (AoD), PAS of AoD, transmit / receive channel correlation, transmit / receive beamforming, or spatial channel correlation.

[0174] As shown in Table 11 below, QCL relationships can be configured for the UE using the RRC parameters TCI-State and QCL-Info. Referring to Table 11, the base station can configure the UE with one or more TCI states, indicating up to two QCL relationships (qcl-Type1 and qcl-Type2) for the RS (i.e., the target RS) with the ID of the reference TCI state. In an embodiment, the QCL-Info included in each TCI state may include the serving cell index and BWP index of the reference RS indicated by the QCL-Info, the type and ID of the reference RS, and the QCL type, as shown in Table 10 above.

[0175] [Table 11]

[0176]

[0177] Here, tci-StateId represents the TCI state ID, qcl-Type1 includes the QCL information of the first reference RS (i.e., the target RS) referencing the TCI state ID, and qcl-Type2 may include the QCL information of the second reference RS (i.e., the target RS) referencing the TCI state ID. For each QCL information, ServCellIndex may represent the serving cell index of the reference RS indicated by the QCL information, bwp-Id may represent the BWP index of the reference RS indicated by the QCL information, and ssb may represent the Channel State Information Reference Signal (CSI-RS) ID or SSB ID indicated by the QCL information.

[0178] <Time and Frequency Domain Resource Allocation>

[0179] The following describes how to allocate time and frequency resources for data transmission in NR.

[0180] In NR, in addition to the frequency domain resource candidate allocation indicated by BWP, the following detailed frequency domain resource allocation (FD-RA) methods are also available.

[0181] Figure 6A , Figure 6B and Figure 6C This is a view illustrating an example of frequency domain resource allocation in a wireless communication system. It shows three types of frequency domain resource allocation: RA type 0 600 and RA type 1 605, which can be configured via higher-level signaling, and RA types 0 & 1 610, used for dynamic switching.

[0182] refer to Figure 6A When the UE is configured to use only RA type 0 600 via higher-layer signaling, some downlink control information (DCI) used to allocate PDSCH to the UE may include information from N. RBG A bitmap 615 consisting of N bits. The conditions for configuring the bitmap are described again below. In the embodiment, N RBG The number of Resource Block Groups (RBGs) determined by the BWP size allocated according to the BWP indicator and the higher-level parameter rbg-Size is shown in Table 12 below, and data can be transmitted in RBGs represented as 1 in the bitmap.

[0183] [Table 12]

[0184]

[0185] refer to Figure 6B When the UE is configured to use only RA type 1 605 via higher-layer signaling, at least one DCI used to allocate PDSCH to the UE can have a DCI consisting of... Frequency domain resource allocation information consisting of bits. The conditions for configuring frequency domain resource allocation information are described again below. In an embodiment, the base station can use the frequency domain resource allocation information to set the length 625 of the frequency domain resources continuously allocated from the starting VRB 620.

[0186] refer to Figure 6C When the UE is configured to use RA type 0 & 1 610 via higher-layer signaling, the DCI used to allocate PDSCH to the UE may have frequency domain resource allocation information 635. This frequency domain resource allocation information 635 has the larger bit size of the information 620 and 625 used for configuring RA type 1 and the bit map 615 used for configuring RA type 0. The conditions for configuring the frequency domain resource allocation information are described again below. In this case, one bit can be added as the most significant bit (MSB) of the frequency domain resource allocation information in the DCI, and an MSB of 0 indicates the use of RA type 0, while an MSB of 1 indicates the use of RA type 1.

[0187] Figure 7 This is a view illustrating an example of time-domain resource allocation in a wireless communication system.

[0188] refer to Figure 7 The base station can use higher-layer signaling to indicate the μ of the subcarrier spacing for the data channel and the control channel, respectively. PDSCH and μ PDCCH And K0, indicating the scheduling offset. In addition, the base station can use DCI to indicate the time-domain resources of PDSCH resources as a dynamic indication of the OFDM symbol start position 700 and length 705 in a time slot.

[0189] Figure 8A and 8B This is a view illustrating an example of time-domain resource allocation based on subcarrier spacing in a wireless communication system.

[0190] refer to Figure 8A When the subcarrier spacing of the data channel and the control channel is the same (800) (μ) PDSCH =μ PDCCH When the number of time slots in the data channel is the same as the number of time slots in the control channel, the base station and the UE can know that the scheduling offset occurs according to the predetermined time slot offset K0.

[0191] refer to Figure 8B When the subcarrier spacing of the data channel and the control channel is different from each other (8-05) (μ) PDSCH ≠μ PDCCH The number of time slots in the data channel is different from the number of time slots in the control channel, so the base station and UE can know that the scheduling offset occurs according to the predetermined time slot offset K0 relative to the subcarrier interval of the PDCCH.

[0192] Although the offset interpretation method for the case where the subcarrier spacing between the data channel and the control channel is the same or different has been described above, this disclosure is not limited thereto, but can also be similarly applied to the case where the subcarrier spacing between different channels or reference signals is the same or different (e.g., when the subcarrier spacing between the CSI-RS and the control channel is different, or when the subcarrier spacing between the SRS and the control channel is different).

[0193] Depending on the purpose of the UE effectively receiving the control channel, NR can provide various types of DCI formats, as shown in Table 13 below.

[0194] [Table 13]

[0195]

[0196] For example, a base station can use DCI format 0_0 or DCI format 0_1 ​​to allocate (e.g., schedule) a PDSCH to a cell.

[0197] In an embodiment, when transmitted together with a CRC scrambled with a Cell Radio Network Temporary Identifier (C-RNTI) or a configured Scheduled RNTI (CS-RNTI) or a new RNTI, DCI format 0_1 ​​may include at least one of the following information.

[0198] DCI format identifier (1 bit): DCI format indicator. This can always be set to 1.

[0199] Frequency domain resource allocation (N) RBG bits or (1 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. For detailed methods, please refer to the above explanation of frequency domain resource allocation.

[0200] Time-domain resource allocation (0-4 bits): can indicate the time-domain resource allocation as described above.

[0201] VRB to PRB mapping (1 bit): 0 indicates uninterleaved, 1 indicates interleaved VRP to PRB mapping.

[0202] Modulation and coding scheme (5 bits): can indicate the modulation order and code rate used for PDSCH transmission.

[0203] The New Data Indicator (1 bit) field can indicate whether the PDSCH is an initial transmission or a retransmission, depending on whether it has been switched.

[0204] Redundant version (2 bits): can indicate the redundant version used for PDSCH transmission.

[0205] HARQ process number (4 bits): This indicates the HARQ process number used for PDSCH transmission.

[0206] Downlink Allocation Index (2 bits): DAI Indicator

[0207] TPC command (2 bits) for PUCCH scheduling: PUCCH power control indicator

[0208] PUCCH resource indicator (3 bits): can be a PUCCH resource indicator and indicates one of eight resources configured by higher-level signaling.

[0209] PDSCH-TO-HARQ_feedback timing indicator (3 bits): can indicate one of eight feedback timing offsets configured by higher-level signaling.

[0210] In an embodiment, when transmitted together with a CRC scrambled by a Cell Radio Network Temporary Identifier (C-RNTI) or a configured Scheduled RNTI (CS-RNTI) or a new RNTI, DCI format 1_1 may include at least one of the following information.

[0211] DCI format identifier (1 bit): DCI format indicator. This can always be set to 1.

[0212] Carrier indicator (0 or 3 bits): can indicate the CC (or cell) in which the PDSCH allocated by the corresponding DCI is transmitted.

[0213] Bandwidth Part Indicator (0, 1, or 2 bits): This indicates the BWP transmitted by the PDSCH allocated by the corresponding DCI.

[0214] Frequency domain resource allocation (including payloads determined based on frequency domain resource allocation): indicates frequency domain resource allocation. This refers to the size of the active DL BWP. For detailed instructions, please refer to the above section on frequency domain resource allocation.

[0215] Time-domain resource allocation (0-4 bits): can indicate the time axis resource allocation as described above.

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

[0217] PRB Bundle Size Indicator (0 or 1 bit): This is 0 bits when the higher-level parameter prb-BundlingType is not set or is set to "Static", and 1 bit when set to "Dynamic".

[0218] Rate matching indicator (0, 1, or 2 bits): can indicate the rate matching pattern.

[0219] ZP CSI-RS trigger (0, 1, or 2 bits): This can trigger an indicator for a non-periodic ZP CSI-RS.

[0220] For transport block 1:

[0221] Modulation and coding scheme (5 bits): can indicate the modulation order and code rate used for PDSCH transmission.

[0222] The New Data Indicator (1 bit) field can indicate whether the PDSCH is an initial transmission or a retransmission, depending on whether it has been switched.

[0223] Redundant version (2 bits): can indicate the redundant version used for PDSCH transmission.

[0224] For transport block 2:

[0225] Modulation and coding scheme (5 bits): can indicate the modulation order and code rate used for PDSCH transmission.

[0226] The New Data Indicator (1 bit) field can indicate whether the PDSCH is an initial transmission or a retransmission, depending on whether it has been switched.

[0227] Redundant version (2 bits): can indicate the redundant version used for PDSCH transmission.

[0228] HARQ process number (4 bits): This indicates the HARQ process number used for PDSCH transmission.

[0229] Downlink Allocation Index (0, 2, or 4 bits): DAI Indicator

[0230] TPC command (2 bits) for PUCCH scheduling: PUCCH power control indicator

[0231] PUCCH resource indicator (3 bits): can be a PUCCH resource indicator and indicates one of eight resources configured by higher-level signaling.

[0232] PDSCH-TO-HARQ_feedback timing indicator (3 bits): can indicate one of eight feedback timing offsets configured by higher-level signaling.

[0233] Antenna port (4, 5, or 6 bits): May indicate a DMRS port and CDM group with no data.

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

[0235] SRS Request (2 or 3 bits): SRS Transmission Request Indicator

[0236] CBG transmission information (0, 2, 4, 6, or 8 bits): An indicator that indicates whether each code block group (CBG) is transmitted in the allocated PDSCH. 0 can mean that no CBG is transmitted, and 1 can mean that a CBG is transmitted.

[0237] CBG Clearance Information (0 or 1 bit): An indicator that the previous CBG has been contaminated - 0 can indicate that it may have been contaminated, and 1 can indicate that it can be used when receiving retransmissions (combinable).

[0238] DMRS sequence initialization (0 or 1 bit): This can be an indicator used to select the DMRS scrambling ID.

[0239] The number of different-sized DCIs that a UE can receive in each time slot of a cell is up to 4. The number of different-sized DCIs scrambled with C-RNTI that a UE can receive in each time slot of a cell is up to 3.

[0240] In an embodiment, the antenna port indication can be indicated by at least one of the tables 14 to 17 below.

[0241] [Table 14]

[0242]

[0243] [Table 15]

[0244]

[0245] [Table 16]

[0246]

[0247] [Table 17]

[0248]

[0249]

[0250] When dmrs-type is 1 and maxLength is 1, use Table 14; when dmrs-type is 1 and maxLength is 2, use Table 15. When dmrs-type is 2 and maxLength is 1, use Table 16; when drms-type is 2 and maxLength is 2, use Table 17 to indicate the DMRS port used.

[0251] The numbers 1, 2, and 3, representing the number of (multiple) DMRS CDM groups without data, can represent CDMR groups {0}, {0, 1}, and {0, 1, 2}, respectively. The (multiple) DMRS ports are the index sequence of the ports to be used. An antenna port can be represented as DMRS port + 1000. As shown in Tables 18 and 19, the CDM groups of the DMRS are associated with the method for generating the DMRS sequence and the antenna ports. Table 18 shows the parameters when using dmrs-type=1, and Table 19 shows the parameters when using dmrs-type=2.

[0252] [Table 18]

[0253]

[0254] [Table 19]

[0255]

[0256] The sequence of DMRS for each parameter can be determined by Equation 2 below.

[0257] [Equation 2]

[0258]

[0259] Figure 9A , 9B Figures 9 and 9C are views illustrating the radio protocol architecture of the base station and UE when single cell, carrier aggregation (CA), and dual connectivity (DC) are performed separately in a wireless communication system.

[0260] refer to Figure 9A The radio protocol stack of a wireless communication system can consist of NR Service Data Adaptation Protocol (NR SDAP) 925 or 970, NR Packet Data Convergence Protocol (NR PDCP) 930 or 965, NR Radio Link Control (NR RLC) 935 or 960, and NR Media Access Control (NR MAC) 940 or 955 in each of the UE and the base station.

[0261] NR SDAP layers 925 and 970 may include at least some of the following functions.

[0262] Transmission of user plane data

[0263] Mapping between QoS streams and data radio bearers (DRBs) for both DL and UL

[0264] Mark QoS flow IDs in both DL and UL groups.

[0265] UL SDAP PDU's reflected QoS flow to DRB mapping.

[0266] For the SDAP layer, RRC messages can be used to configure whether the UE uses the SDAP layer header or whether the SDAP layer functionality is used for each PDCP layer, each bearer, or each logical channel. When the SDAP header is configured, a one-bit NAS-reflected QoS indicator and a one-bit AS-reflected QoS indicator in the SDAP header can instruct the UE to update or reset the uplink and downlink data bearer and QoS flow mapping information. The SDAP header may include a QoS flow ID indicating QoS. The QoS information identified by the QoS flow ID can be used to determine scheduling information and / or data processing priorities for smooth support services.

[0267] NR PDCP layers 930 and 965 may include at least some of the following functions.

[0268] Header compression and decompression: ROHC only

[0269] Transmission of user data

[0270] Sequential delivery of upper-layer PDUs

[0271] Unordered delivery of upper-layer PDUs

[0272] PDCP PDU reordering for received

[0273] Duplicate detection of lower layer SDU

[0274] PDCP SDU retransmission

[0275] Encryption and decryption

[0276] Uplink timer-based SDU dropping

[0277] NR PDCP reordering refers to reordering the PDCP PDUs received from the lower layer based on the PDCP sequence number (SN), and may include transmitting data to the higher layer immediately in the reordered order or without regard to the order, recording PDCP PDUs lost due to reordering, reporting the status of lost PDCP PDUs to the sender, and requesting retransmission of lost PDCP PDUs.

[0278] NR RLC layers 935 and 960 may include at least some of the following functions.

[0279] upper-layer PDU transmission

[0280] Sequential delivery of upper-layer PDUs

[0281] Unordered delivery of upper-layer PDUs

[0282] Error correction via ARQ

[0283] splicing, segmentation and reassembly of RLC SDU

[0284] RLC data PDU resegmentation

[0285] RLC data PDU reordering

[0286] Duplicate detection

[0287] Protocol error detection

[0288] RLC SDU discard

[0289] RLC Reconstruction

[0290] Sequential delivery in NR RLC layers 935 and 960 refers to the sequential delivery of RLC SDUs received from lower layers to higher layers. If an original RLC SDU is fragmented into several RLC SDUs, and these RLC SDUs are then received, sequential delivery may include reassembling and transmitting them, reordering received RLC PDUs based on their RLC sequence number (SN) or PDCP sequence number (SN), recording RLC PDUs lost due to reordering, reporting the status of lost RLC PDUs to the sender, and requesting retransmission of lost RLC PDUs. If lost RLC SDUs exist, sequential delivery may include delivering only RLC SDUs preceding the lost RLC SDU to higher layers sequentially. Even with missing RLC SDUs, if a predetermined timer has expired, sequential delivery may include delivering all RLC SDUs received before the timer started sequentially to higher layers. Alternatively, even with missing RLC SDUs, if a predetermined timer has expired, sequential delivery may include delivering all RLC SDUs received to date sequentially to higher layers.

[0291] NR RLC layers 935 and 960 can process RLC PDUs in the order they are received (according to the order of arrival, regardless of SN order) and deliver them to the PDCP device out of order. If a received RLC PDU is fragmented, it is stored in a buffer or combined with later received fragments to reconstruct a single complete RLC PDU, which is then transmitted 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 functionality in the NR MAC layer.

[0292] The out-of-order delivery of NR RLC layers 935 and 960 refers to the function of immediately delivering RLC SDUs received from lower layers without regard to order, and includes the function of reassembling and delivering them when the initial single RLC SDU is divided into several RLC SDUs that are subsequently received, and may include the function of storing the RLC SN or PDCP SN of the received RLC PDUs and reordering them, as well as the function of recording lost RLC PDUs.

[0293] NR MAC layers 940 and 955 can connect to several NR RLC layer modules configured in a UE and can include at least some of the following functions.

[0294] Mapping between logical channels and transport channels

[0295] MAC SDU multiplexing / demultiplexing

[0296] Dispatch Information Report

[0297] HARQ error correction

[0298] Priority processing between logical channels of a UE

[0299] Priority processing among UEs through dynamic scheduling

[0300] MBMS Service Identifier

[0301] Transmission format selection

[0302] filling

[0303] The NR PHY layers 945 and 950 can encode and modulate higher-layer data channels into OFDM symbols, transmit OFDM symbols over a wireless channel, or demodulate OFDM symbols received over a wireless channel, decode their channels, and transmit them to higher layers.

[0304] The detailed structure of a radio protocol can vary depending on the carrier (or cell) operation scheme. As an example, when a base station transmits data to a UE based on a single carrier (or cell), the base station and UE can use a protocol structure with a single structure for each layer, similar to... Figure 9A The single-cell protocol structure 900.

[0305] refer to Figure 9B When a base station transmits data to a UE based on carrier aggregation (CA) using multiple carriers at a single transmit and receive point (TRP), the CA protocol structure 910 of the base station and the UE can have a single structure at a higher layer before RLC and multiple PHY layers can be multiplexed through the MAC layer.

[0306] refer to Figure 9C When a base station transmits data to a UE based on dual connectivity (DC) using multiple carriers in multiple TRPs, the DC protocol structure 920 of the base station and the UE can have a single structure in a higher layer before PDCP and can include multiple RLC / MAC / PHY layers.

[0307] In LTE and NR, when connected to a serving base station, the UE has a process of reporting its supported capabilities to the base station. Hereinafter, this report may be referred to as a UE capability report. The base station may transmit a UE capability query message to the UE in a connected state to request a capability report. The UE capability query message may include UE capability requests for each Radio Access Technology (RAT) type. Requests for each RAT type may include the requested frequency band information. Furthermore, the UE capability query message may include an RRC message container requesting multiple RAT types. Alternatively, multiple UE capability query messages may be transmitted to the UE including requests for each RAT type. In other words, multiple UE capability queries can be sent, and the UE can configure multiple UE capability information messages corresponding to the UE capability queries and report them to the base station. In next-generation mobile communication systems, UE capability reports for NR, LTE, EN-DC (LTE-NR DC), or MR-DC (Multi-RAT DC) can be requested. Although UE capability query messages are typically sent at the start of a UE connection, the base station may send UE capability query messages as needed, even after the UE has established a connection.

[0308] When a UE receives a request for a UE capability report 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 following describes a method for configuring UE capabilities in an NR system.

[0309] 1. When a UE is provided with a list of LTE and / or NR bands at the request of a base station regarding its capabilities, the UE can configure band combinations (BCs) for EN-DC and NR Independent (SA). In other words, the UE can construct a candidate list of BCs for EN-DC and NR SA based on the bands requested by the base station through the FreqBandlist. Band priorities can be arranged in the order listed in the FreqBandlist.

[0310] 2. When a base station sends a UE capability report request including the “eutra-nr-only” or “eutra” flags, the UE can completely remove the frequency band associated with the BC of the NR SA from the configured BC candidate list. In an embodiment, this operation can be performed when an eNB acting as an LTE base station requests “eutra” capability.

[0311] 3. The UE can remove the fallback BC from the BC candidate list configured in step 2. Here, removing the fallback BC means removing the frequency band corresponding to at least one SCell from a superset BC, and since the superset BC may already cover the fallback BC, the fallback BC can be omitted. Step 3 can also be applied to MR-DC, that is, LTE frequency bands can also be applied. Third step. After this, the remaining BCs can be the final "candidate BC list".

[0312] 4. The UE can select BCs matching the requested RAT type from the final "Candidate BC List" to choose the BCs to report. The UE can configure the supportedBandCombinationList including the selected BCs in a predetermined order. In other words, the UE can configure the UE capabilities and BCs to report according to a preset order of RAT types (e.g., NR -> EUTRA-NR -> EUTRA). Furthermore, the UE can configure featureSetCombinations for the configured supportedBandCombinationList and configure a "Candidate Feature Set Combination" list in which fallback BCs (including capabilities with the same or lower steps) have been removed. The "Candidate Feature Set Combination" can include the entire feature set combination for NR and EUTRA-NRBCs and can be obtained from the feature set combination of the UE-MRDC-Capabilities container and the UE-NR-Capabilities.

[0313] 5. If the requested rat type is eutra-nr and has an impact, the feature set combination can be fully included in both the UE-MRDC-Capabilities and UE-NR-Capabilities containers. However, the NR feature set can be included only in UE-NR-Capabilities.

[0314] After UE capabilities are configured, the UE can transmit UE capability information messages, including the UE capabilities, to the base station. The base station can then perform appropriate scheduling and transmit / receive management of the UE based on the UE capabilities received from the UE.

[0315] In NR, the Channel State Information Reference Signal (CSI-RS) is used as a reference signal for the UE's channel state reporting, and in embodiments, each CSI-RS resource configuration configured by a higher layer may include at least one of the following detailed configuration information. However, it is not limited to the examples below.

[0316] NZP-CSI-RS-Resource ConfigID: The ID for NZP (non-zero power) CSI-RS resource configuration.

[0317] NrofPorts: The number of CSI-RS ports included in the CSI-RS resource.

[0318] CSI-RS-timeConfig: Transmission period and time slot offset of CSI-RS resources

[0319] CSI-RS-ResourceMapping: OFDM symbol locations in time slots and subcarrier locations in PRBs for CSI-RS resources.

[0320] CSI-RS-Density: Frequency density of CSI-RS.

[0321] CDMType: CDM length and CDM RE pattern in CSI-RS.

[0322] CSI-RS-FreqBand: CSI-RS transmission bandwidth and starting position

[0323] Pc: The ratio between PDSCH EPRE (energy per RE) and NZP CSI-RS EPRE.

[0324] Pc-SS: The ratio between SS / PBCH block EPRE and NZP CSI-RS EPRE

[0325] CSI-RS-ResourceRep: This indicates the relationship between NZP CSI-RS resources belonging to a resource set. If CSI-RS-ResourceRep is 'ON', the UE knows that the same spatial transmission filter is applied to NZP CSI-RS resources belonging to this resource set (i.e., the UE can assume that the base station has used the same transmission beam in the NZP CSI-RS resources), and that each NZP CSI-RS resource has the same number and period of CSI-RS ports. If CSI-RS-ResourceRep is 'OFF', the UE may not assume that the same spatial transmission filter is applied to NZP CSI-RS resources belonging to this resource set (i.e., the UE may not assume that the base station has used the same transmission beam in the NZP CSI-RS resources), and may not know that each NZP CSI-RS resource has the same number and period of CSI-RS ports.

[0326] In an NR communication system, one of {1, 2, 4, 8, 12, 16, 24, 32} can be set as the number of CSI-RS ports in a CSI-RS resource, and different degrees of configuration freedom can be supported based on the number of CSI-RS ports set in the CSI-RS resource.

[0327] In the embodiments, Table 20 shows the CSI-RS density, CDM length and type, and frequency and time domain start positions of the CSI-RS component RE patterns. The number of frequency domain REs k' and the number of time domain REs l' can be configured according to the number of NR CSI-RS ports X.

[0328] The CSI-RS component RE pattern is the basic unit constituting a CSI-RS resource and can consist of a total of YZ REs, including Y = 1 + max (k') adjacent REs on the frequency axis and Z = 1 + max (l') adjacent REs on the time axis. In NR, different degrees of freedom in frequency axis configuration can be supported depending on the number of CSI-RS ports set in the CSI-RS resource.

[0329] In the case of a single port, CSI-RS can be configured to have no subcarrier limitation in the PRB, and the UE can pass through a 12-bit bitmap ( Figure 10The UE receives the CSI-RS RE location specification using a bitmap (1000 in the context of the frequency domain). With {2, 4, 8, 12, 16, 24, or 32} ports and Y = 2, the CSI-RS can be configured for every two subcarriers in the PRB, and the UE can receive the CSI-RS RE location specification via a 6-bit bitmap. With four ports and Y = 4, the CSI-RS can be configured for every four subcarriers in the PRB, and the UE can receive the CSI-RS RE location specification via a 3-bit bitmap. Similarly, in the time domain, the UE can receive the CSI-RS RE location specification via a total of 14 bits of bitmap. In this case, the length of the bitmap can vary like the frequency domain location specification, depending on the Z value indicating the CSI-RS location within the time slot in Table 20, but a similar principle applies, so a detailed description is omitted.

[0330] [Table 20]

[0331]

[0332] Figure 10 This is a view that shows an example of configuring CSI-RS through CSI-RS resource mapping.

[0333] refer to Figure 10 This illustrates an example of CSI-RS RE configuration via CSI-RS-ResourceMapping configured by a higher layer. When X=2 ports are configured, the base station can specify the RE location via frequency indication 1005, and if the base station specifies the subcarrier location via a value of 2 for frequency indication 1005 and the OFDM symbol location via a value of 9 for frequency indication 1015, then the UE can know that the CSI-RS is transmitted at RE location 1025 in PRB 1020.

[0334] Channel State Measurement and Reporting

[0335] The following describes in detail the methods for measuring and reporting channel status in 5G communication systems.

[0336] Channel state information (CSI) may include at least one of channel quality information (CQI), precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), SS / PBCH block resource indicator (SSBRI), layer indicator (LI), rank indicator (RI), and / or L1-reference signal received power (RSRP). The base station may control the time and frequency resources used for CSI measurement and reporting for the UE.

[0337] For CSI measurement and reporting, the UE can receive configuration information for at least one of the following via higher-layer signaling: configuration information for N (≥1) CSI reports (CSI-ReportConfig), configuration information for M (≥1) RS transmission resources (CSI-ResourceConfig), or list information for one or more trigger states (CSI-AperiodicTriggerStateList, CSI-SemiPersistentOnPUSCH-TriggerStateList).

[0338] In this embodiment, the configuration information for CSI measurement and reporting may be as shown in Tables 21 to 27.

[0339] [Table 21]

[0340] CSI-ReportConfig

[0341] The IE CSI-ReportConfig is used to configure periodic or semi-permanent reports transmitted on the PUCCH from cells in which the CSI-ReportConfig is included, or to configure semi-permanent or non-periodic reports transmitted on the PUSCH triggered by a DCI received on a cell in which the CSI-ReportConfig is included (in which case the cell on which the report is transmitted is determined by the received DCI). See TS 38.214

[19] , Clause 5.2.1.

[0342] CSI-ReportConfig Information Elements

[0343]

[0344]

[0345]

[0346]

[0347]

[0348]

[0349]

[0350]

[0351]

[0352]

[0353]

[0354]

[0355] [Table 22]

[0356] CSI-ResourceConfig

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

[0358] CSI-ResourceConfig Information Element

[0359]

[0360]

[0361] [Table 23]

[0362] NZP-CSI-RS-ResourceSet

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

[0364] NZP-CSI-RS-ResourceSet Information Element

[0365]

[0366]

[0367] [Table 24]

[0368] CSI-SSB-ResourceSet

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

[0370] CSI-SSB-ResourceSet Information Element

[0371]

[0372] [Table 25]

[0373] CSI-IM-ResourceSet

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

[0375] CSI-IM-ResourceSet Information Element

[0376]

[0377]

[0378] [Table 26]

[0379] CSI-AperiodicTriggerStateList

[0380] The CSI-AperiodicTriggerStateList IE is used to configure the UE with a list of aperiodic trigger states. Each code point in the DCI field “CSI Request” is associated with a trigger state (see TS 38.321 [3], Clause 6.1.3.13). Once the value associated with the trigger state is received, the UE will perform measurements of CSI-RS, CSI-IM and / or SSB (reference signal) and aperiodic reporting on L1 of all entries in the associatedReportConfigInfoList according to the trigger state.

[0381] CSI - AperiodicTriggerStateList Information Element

[0382]

[0383]

[0384]

[0385]

[0386] [Table 27]

[0387] CSI-SemiPersistentOnPusch-TriggerStateList

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

[19] , Clause 5.2.

[0389] CSI-SemiPersistentOnPusch-TriggerStateList Information Element

[0390]

[0391] For the aforementioned CSI report configurations (CSI-ReportConfig), each CSI-ReportConfig can be associated with a CSI resource configuration and a downlink (DL) bandwidth portion identified by a higher-layer parameter bandwidth portion identifier (bwp-id) given as CSI-ResourceConFIG. As a time-domain report for each CSI-ReportConfig, 'aperiodic', 'semi-persistent', and 'periodic' schemes can be supported, and configured from the base station to the UE via the reportConfigType parameter configured from a higher layer. The semi-persistent CSI reporting method can support 'semi-persistent onpunch based PUCCH' and 'semi-persistent onPUSCH based PUSCH'. In the case of periodic or semi-persistent CSI reporting methods, the UE can receive the configuration of the PUCCH or PUSCH resources for transmitting CSI from the base station via higher-layer signaling. The period and slot offset of the PUCCH or PUSCH resources used to transmit CSI can be given as a set of parameters for the uplink (UL) bandwidth portion configured to transmit CSI reports. In the case of a non-periodic CSI reporting method, the UE can receive the scheduling of PUSCH resources for transmitting CSI from the base station via L1 signaling (DCI format 0_1 ​​above).

[0392] For the CSI resource configurations (CSI-ResourceConfig) described above, each CSI resource configuration (CSI-ReportConfig) may include S (≥1) CSI resource sets (given as the higher-layer parameter csi-RS-ResourceSetlist). The list of CSI resource sets may consist of non-zero power (NZP) CSI-RS resource sets and SS / PBCH block sets, or CSI interference measurement (CSI-IM) resource sets. Each CSI resource configuration may reside in a downlink (DL) bandwidth portion identified by the higher-layer parameter bwp-id. CSI resource configurations may be connected to CSI reporting configurations within the same downlink bandwidth portion. The time-domain operation of the CSI-RS resources in a CSI resource configuration may be set to one of 'aperiodic', 'periodic', or 'semi-persistent' based on the higher-layer parameter resource type. For periodic or semi-persistent CSI resource configurations, the number of CSI-RS resource sets may be limited to S=1. The configured period and slot offset may be given as a parameter set for the downlink bandwidth portion identified by bwp-id. The UE can receive configurations for one or more CSI resources used for channel or interference measurements from the base station via higher-layer signaling. For example, the following CSI resources may be included.

[0393] CSI-IM Resources for Interference Measurement

[0394] NZP CSI-RS resources for interference measurement

[0395] NZP CSI-RS resources for channel measurement

[0396] For a CSI-RS resource set associated with a resource where the higher-level parameter resourceType is specified as 'aperiodic', 'periodic', or 'semi-persistent', the resource configuration for channel or interference measurements of one or more component cells (CCs) and the triggering state for CSI reporting configurations where reportType is set to 'aperiodic' can be configured by the higher-level parameter CSI-AperiodicTriggerStateList.

[0397] UE non-periodic CSI reporting can use PUSCH, and periodic CSI reporting can use PUCCH. Semi-persistent CSI reporting can be performed using PUSCH when triggered or activated by DCI, or using PUCCH after activation by MAC control element (CE). As described above, CSI resource configuration can also be configured non-periodicly, periodically, or semi-persistently. In embodiments, combinations of CSI reporting configuration and CSI resource configuration can be supported based on Table 28 below.

[0398] [Table 28]

[0399] Table 5.2.1.4-1: CSI Reporting Triggering / Activation in Possible CSI-RS Configurations

[0400]

[0401] Non-periodic CSI reports can be triggered using the aforementioned DCI format 0_1 ​​"CSI Request" corresponding to the PUSCH scheduling DCI. The UE can monitor the PDCCH, obtain DCI format 0_1, and acquire the PUSCH scheduling information and CSI request indicator. The CSI request indicator can be used with N... TS It can be set using 0, 1, 2, 3, 4, 5, or 6 bits and is determined by higher-level signaling (reportTriggerSize). One of the trigger states in one or more aperiodic CSI report trigger states (CSI-AperiodicTriggerStateList) that can be configured by higher-level signaling can be triggered by a CSI request indicator.

[0402] When all bits in the CSI request field are 0, it can mean that no CSI report has been requested.

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

[0404] If the number M of CSI trigger states in the configured CSI-AperiodicTriggerStateList is equal to or less than 2 NTs- 1. Then one of the M CSI trigger states can be indicated by the CSI request field.

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

[0406] [Table 29]

[0407]

[0408] For CSI resources in a CSI-triggered state triggered by the CSI request field, the UE can perform measurements and generate CSIs (including at least one or more of the aforementioned CQI, PMI, CRI, SSBRI, LI, RI, or L1-RSRP). The UE can transmit the acquired CSIs via a PUSCH scheduled by the corresponding DCI format 0_1. When a bit corresponding to the uplink data indicator (UL-SCH indicator) in DCI format 0_1 ​​indicates "1", the uplink data (UL-SCH) and the acquired CSIs can be multiplexed onto the PUSCH resources scheduled by DCI format 0_1 ​​and transmitted. When a bit corresponding to the uplink data indicator (UL-SCH indicator) in DCI format 0_1 ​​indicates "0", only CSIs are present, without uplink data (UL-SCH), which can be mapped to the PUSCH resources scheduled by DCI format 0_1 ​​and transmitted.

[0409] Figure 11A and 11B This is a view illustrating an example of a non-periodic CSI reporting method.

[0410] refer to Figure 11A The UE can obtain DCI format 0_1 ​​by monitoring PDCCH 1101 and acquiring scheduling information and CSI request information for PUSCH 1105. The UE can obtain resource information for the CSI-RS 1102 to be measured from the received CSI request indicator. The UE can determine when to perform the measurement on the CSI-RS 1102 transmitted based on the reception time of DCI format 0_1 ​​and the offset parameter (aperiodicTriggringOffset mentioned above) in the CSI resource set configuration (e.g., NZP CSI-RS resource set configuration (NZP-CSI-RS-ResourceSet)). Specifically, the UE can receive the configuration of the offset value X of the parameter aperiodicTriggeringOffset in the NZP-CSI-RS resource set configuration from the base station via higher-layer signaling. The configured offset value X can represent the offset between the time slot in which the DCI used to trigger aperiodic CSI reporting is received and the time slot in which the CSI-RS resources are transmitted. For example, the non-trigger offset parameter value and the offset value X can have the mapping relationship shown in Table 30 below.

[0411] [Table 30]

[0412]

[0413] The example shown illustrates an example of the aforementioned offset value X=0. In this case, the UE can receive CSI-RS 1102 in the time slot where DCI format 0_1, used to trigger aperiodic CSI reporting, is received (corresponding to time slot 0 in Figure 6), and report the CSI generated using the measurement results of the received CSI-RS to the base station via PUSCH 1105.

[0414] The UE can obtain the scheduling information for PUSCH 1105 used for CSI reporting from DCI format 0_1 ​​(corresponding to the information of each field in DCI format 0_1 ​​above). As an example, the UE can obtain information about the time slot for transmitting PUSCH 1105 from the time domain resource allocation information of PUSCH 1105 above. In the example of Figure 6, the UE obtains 3 as the K2 value corresponding to the time slot offset from PDCCH to PUSCH, so that PUSCH 1105 can be transmitted in time slot 3 1109, which is three time slots away from time slot 0 1106, which is the reception time of PDCCH 1101.

[0415] refer to Figure 11B The UE can obtain DCI format 0_1 ​​by monitoring PDCCH 1111, obtaining scheduling information and CSI request information from PUSCH 1115. The UE can obtain resource information for the CSI-RS 1112 to be measured from the received CSI request indicator. The example shown illustrates an example of the aforementioned offset value X=1 for CSI-RS. In this case, the UE can receive CSI-RS 1112 in the time slot where DCI format 0_1 ​​used to trigger aperiodic CSI reporting is received (corresponding to time slot 0 1116 in Figure 11), and report the CSI generated from the measurement results of the received CSI-RS to the base station via PUSCH 1115.

[0416] Figure 12A , 12B Views 1 and 12C are examples illustrating various operating scenarios of the SRS. (Reference) Figure 7 For example, the NR system can consider at least three SRS operation scenarios as follows.

[0417] refer to Figure 12ABase station 1205 can configure a beam in one direction for UE 1200. Configuring a beam / precoding in one direction can include avoiding beam / precoding or applying a wide beam (cell coverage or sector coverage). If the SRS is periodic or semi-persistent, UE 1200 can transmit SRS based on the transmission period and offset; or if the SRS is aperiodic, it can transmit SRS based on the base station's SRS request (at a predetermined time after the SRS request). In this case, no additional information regarding beam / precoding is required for the SRS.

[0418] refer to Figure 12B Base station 1215 or 1220 can configure beams in one or more directions for UE 1210, and UE 1210 can transmit multiple SRSs beamformed in one or more directions. For example, as Figure 7 In the example shown, SRS resource (or port) #0 can be configured to beamform base station 1215, and SRS resource (or port) #1 can be configured to beamform base station 1220. In this case, unlike method 1) above, base stations 1215 and 1220 need to provide SRS beamforming / precoding information and an SRS request.

[0419] refer to Figure 12C The base station 1230 can configure beams in one or more directions for the UE 1225, and the UE 1225 can transmit multiple SRSs beamformed in one or more directions. For example, as Figure 7 In the example shown, the base station can configure the UE to apply different beams / precoding to SRS resources (or ports) #0, #1, and #2 respectively to transmit SRS. Therefore, stable communication can be achieved through beam / precoding diversity even when the UE has high mobility. For example, UE 1225 can provide channel state information to the base station via SRS #2 at time A and to base station 1230 via SRS #0 at time A+alpha. In this case, unlike method 1) above, base station 1230 needs to provide UE 1225 with SRS beam / precoding information and an SRS request.

[0420] Although based on SRS transmission, the foregoing description can also be applied to PRACH, PUSCH, or PUCCH or other UL channel / RS transmissions, and detailed descriptions of all scenarios have been omitted to avoid unnecessarily obscuring the key points of this disclosure.

[0421] Figure 13 This is a view showing the uplink transmission structure of a 5G or NR system.

[0422] refer to Figure 13 The basic transmission unit of a 5G or NR system is time slot 1300. Assuming a typical cyclic prefix (CP) length, each time slot can consist of 14 symbols 1305, and one symbol can correspond to one UL waveform (CP-OFDM or DFT-S-OFDM) symbol. A resource block (RB) 1310 is a resource allocation unit corresponding to one time slot in the time domain and can consist of 12 subcarriers in the frequency domain.

[0423] The uplink structure can be mainly divided into a data region and a control region. Unlike LTE systems, in 5G or NR systems, the control region can be configured and transmitted at any location on the uplink. Here, the data region may include a series of communication resources, including data (e.g., voice and / or packets), sent to each UE, and may correspond to the remaining resources in a subframe other than the control region. The control region may include a series of communication resources for at least one of downlink channel quality reports, downlink signal reception ACK / NACK, or uplink scheduling requests from each UE.

[0424] The UE can transmit its data and control information simultaneously in the data and control areas. The UE can periodically transmit SRS symbols (the last six symbols, 1315) within a time slot, and can transmit in the frequency domain via a pre-configured SRS transmission band in the ULBWP. However, this is merely an example; the number of symbols capable of transmitting SRS can be extended to other time ranges or transmitted via frequency bands. When transmitting in the frequency domain, the RBs capable of transmitting SRS can be transmitted in multiples of four RBs, up to a maximum of 272 RBs.

[0425] Furthermore, in 5G or NR systems, the number N of SRS symbols can be set to 1, 2, or 4, and transmissions can be performed in consecutive symbols. Additionally, 5G or NR systems allow repeated transmission of SRS symbols. Specifically, the repetition factor of an SRS symbol is r ∈ {1,2,4}, and can be set to r≤N. For example, when an SRS antenna is mapped to one symbol and transmitted, the transmission can repeat up to four symbols. In contrast, four different antenna ports can transmit in four different symbols. In this case, repeated transmission of SRS symbols is not allowed because each antenna port is mapped to one symbol.

[0426] In the case of LTE / NR, SRS can be configured based on the following higher-level signaling information (or a subset thereof).

[0427] BandwidthConfig: Configures SRS bandwidth information. The exact value for each code point can vary based on the uplink system BW value.

[0428] SubframeConfig (or Configindex): This allows you to configure the SRS transmission period and transmission offset. The exact value for each code point can vary depending on whether Frequency Division Duplex (FDD) or Time Division Duplex (TDD) is being used.

[0429] ackNackSRS-SimultaneousTransmission: Indicates whether ACK / NACK-SRS are sent simultaneously.

[0430] MaxUpPts: Indicates whether the frequency position of SRS transmission is initialized in UpPTS.

[0431] Frequency hopping: This is a two-bit information indicating whether SRS frequency hopping is performed, as well as the location and method of frequency hopping.

[0432] Frequency domain location: Indicates the frequency domain location of SRS transmission.

[0433] Duration: Indicates whether a periodic SRS is sent.

[0434] Transmission comb: Represents the comb offset value during SRS transmission.

[0435] Cyclic shift: Indicates the cyclic shift value during SRS transmission.

[0436] Antenna Ports: Indicates the number of SRS antenna ports used for SRS transmission. LTE can support 1, 2, or 4 ports.

[0437] LTE / LTE-A systems can support periodic and aperiodic SRS transmissions based on the configuration information described above. NR systems can use additional information beyond the above configuration, such as SRS resource activation / deactivation signaling, and can support periodic, semi-persistent, and aperiodic SRS transmissions. Depending on the type of SRS transmission—for example, whether it is periodic, semi-persistent, or aperiodic—some configuration information may be omitted.

[0438] SRS can be configured with constant amplitude zero autocorrelation (CAZAC) sequences. The CAZAC sequences constituting the SRS transmitted from several UEs have different cyclic shift values. Furthermore, a CAZAC sequence generated by cyclic shifting a CAZAC sequence has the following characteristic: it has zero correlation with sequences having different cyclic shift values ​​from themselves. Based on this characteristic, SRSs simultaneously allocated in the same frequency region can be divided according to the cyclic shift values ​​of the CAZAC sequences set by the base station for each SRS.

[0439] The SRS of several UEs can be divided based on frequency location and cyclic shift value. Frequency location can be divided into SRS subband unit allocation or comb. 5G or NR systems may support comb 2 and comb 4. In the case of comb 2, an SRS can be allocated only to the even or odd number of subcarriers in the SRS subband. In this case, each of the even-numbered subcarriers and the odd-numbered subcarriers can form a comb.

[0440] SRS subbands can be allocated to each UE based on a tree structure. The UE can perform frequency hopping on the SRS allocated to each subband during each SRS transmission time. Therefore, all transmit antennas of the UE can transmit SRS across the entire uplink data transmission bandwidth.

[0441] Figure 14 This is a view showing the structure in which SRS are assigned to each subband.

[0442] Figure 14 An example is shown in which SRS is assigned to UEs 1, 2 and 3 1400, 1401 and 1402 through a tree structure configured by the base station when a data transmission band corresponding to 40RB exists in the frequency domain.

[0443] exist Figure 14 In this model, when the level index of the tree structure is b, the highest level of the tree structure (b=0) can consist of one SRS subband with a bandwidth of 40 RB. At the second level (b=1), two SRS subbands with a bandwidth of 20 RB can be generated from the SRS subband at level b=0. Therefore, two SRS subbands can exist throughout the entire data transmission band of the second level (b=1). At the third level (b=2), five 4 RB SRS subbands can be generated from a 20 RB SRS subband immediately preceding (b=1), resulting in a total of 10 4 RB SRS subbands within a single level.

[0444] Depending on the base station configuration, this tree structure can have various levels, SRS subband sizes, and the number of SRS subbands at each level. Here, the number of SRS subbands at level b generated from a higher-level SRS subband is Nb, and the indices of these Nb SRS subbands can be defined as nb = {0, ..., Nb-1}. Since the subbands at each level vary in this way, therefore... Figure 14 As shown, the UE can be assigned to each subband of each level.

[0445] For example, UE 1 1400 can be assigned to the first SRS subband (n1=0) of two SRS subbands with 20 RB bandwidth at the b=1 level, and UE 2 1401 and UE 3 1402 can be assigned to the first SRS subband (n2=0) and the third SRS subband (n2=2) under the second 20 RB SRS subband, respectively. Through these processes, the UE can transmit SRS simultaneously through multiple component carriers (CCs) and simultaneously transmit SRS in multiple SRS subbands within a single CC.

[0446] Specifically, for the above SRS subband configuration, NR can support the SRS bandwidth configuration shown in Table 31 below.

[0447] [Table 31]

[0448]

[0449]

[0450] NR can support SRS frequency hopping based on the values ​​in Table 31. Detailed procedures are described in Table 32 below.

[0451] [Table 32]

[0452]

[0453]

[0454]

[0455] As mentioned above, 5G or NR UEs can support SU-MIMO (single-user) technology and can have up to four transmit antennas. Furthermore, SRS can be transmitted simultaneously in multiple CCs or multiple SRS subbands within a CC. Unlike LTE systems, 5G or NR systems can support various parameter sets, configure various SRS transmission symbols, and allow repeated SRS transmissions.

[0456] 5G or NR systems can support various parameter sets and multiple SRS transmission OFDM symbols, as well as repetition factors in SRS transmissions. Therefore, considering this, it is necessary to count SRS transmissions. SRS transmission counting can be used in various ways. For example, SRS transmission counting can be used to support antenna switching based on SRS transmissions. Specifically, SRS transmission counting can be used to determine the SRS transmission time, antenna, and frequency band for transmitting SRS.

[0457] <Rate Matching and Perforation>

[0458] The matching and piercing will be described in detail below.

[0459] When the time-frequency resource A for transmitting symbol sequence A overlaps with the time-frequency resource B, considering the resource C in the overlapping region of resource A and resource B, rate matching or puncturing can be regarded as the transmission / reception of channel A.

[0460] The base station can map channel A to only the remaining resource area of ​​the entire resource A, excluding resource C which corresponds to the area overlapping with resource B, to send the symbol sequence A to the UE and transmit it. For example, when the symbol sequence A consists of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the base station can sequentially map the symbol sequence A to {resource #1, resource #2, resource #4}, which are the remaining resources of resource A excluding {resource #3} corresponding to resource C, and transmit it. As a result, the base station can map the symbol sequence {symbol #1, symbol #2, symbol #3} to {resource #1, resource #2, resource #4} respectively and transmit it.

[0461] The UE can determine resources A and B based on the scheduling information of symbol sequence A from the base station, thereby determining resource C, which is the overlapping area between resources A and B. The UE can receive symbol sequence A, assuming that it has already been mapped and transmitted in the remaining area of ​​resource A except for resource C. For example, when symbol sequence A consists of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the UE can assume that symbol sequence A has been sequentially mapped to {resource #1, resource #2, resource #4} (which is the remaining resource from resource A except for {resource #3} corresponding to resource C) and receive it. As a result, the UE can assume that symbol sequence {symbol #1, symbol #2, symbol #3} is mapped to {resource #1, resource #2, resource #4} and perform subsequent reception operations.

[0462] <Perforation>

[0463] When a symbol sequence A is sent to the UE from a resource C corresponding to the region of overlapping resource B in the entire resource A, the base station maps the symbol sequence A to the entire resource A, but does not perform transmission in the resource region corresponding to resource C. Instead, it can only perform transmission in the remaining resource regions of resource A excluding resource C. For example, when the symbol sequence A consists of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the base station can map the symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} to resource A {resource #1, resource #2, resource #3, resource #4} respectively, and can only perform transmission in the symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to the remaining resources in resource A excluding {resource #3} corresponding to resource C, but can omit the {symbol #3} mapped to {resource #3} corresponding to resource C. As a result, the base station can map the symbol sequence {symbol #1, symbol #2, symbol #4} to {resource #1, resource #2, resource #4} respectively, and send it.

[0464] The UE can determine resources A and B based on the scheduling information of symbol sequence A from the base station, and thus determine resource C, which is the overlapping area between resources A and resources B. Assuming that symbol sequence A has been mapped to the entire resource A, but transmission is only performed in the remaining area of ​​resource A excluding resource C, the UE can receive symbol sequence A. For example, when symbol sequence A consists of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, assuming that symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} is mapped to resource A {resource #1, resource #2, resource #3, resource #4} respectively, but {symbol #3} mapped to {resource #3} corresponding to resource C is not transmitted, and the symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to the remaining resources of resource A (excluding {resource #3} corresponding to resource C) is mapped, the UE can receive them. As a result, the UE can assume that symbol sequence {symbol #1, symbol #2, symbol #4} is mapped to {resource #1, resource #2, resource #4} and perform subsequent reception operations.

[0465] <Rate Matching Resources>

[0466] Figure 15This is a view showing the data transmission / reception of the base station and UE considering downlink data channel and rate matching resources.

[0467] refer to Figure 15 The diagram illustrates a downlink data channel (e.g., PDSCH) 1501 and rate matching resources 1502. The base station can send configuration information 1502, configuring one or more rate matching resources, to the UE via higher-layer signaling (e.g., RRC signaling). The configuration information associated with rate matching resources 1502 may include time-axis resource allocation information 1503, frequency-axis resource allocation information 1504, and periodic information 1505. In the following description, the bitmap corresponding to the frequency-axis resource allocation information 1504 is referred to as the "first bitmap," the bitmap corresponding to the time-axis resource allocation information 1503 is referred to as the "second bitmap," and the bitmap corresponding to the periodic information 1505 is referred to as the "third bitmap." In time slot 1, when all or part of the time and frequency resources of the scheduled data channel 1501 overlap with the configured rate matching resource 1502, the base station can rate match the data channel 1501 in the part overlapping with the rate matching resource 1502 and transmit it, and the UE can assume that the data channel 1501 has been rate matched in the rate matching resource 1502 and then perform reception and decoding.

[0468] The base station can dynamically notify the UE via DCI (which corresponds to the "rate matching indicator" in the DCI format described above) whether rate matching is performed on the data channel 1501 in the portion overlapping with the configured rate matching resources 1502. In an embodiment, the base station can select some configured rate matching resources 1502, group them into rate matching resource groups, and use a bitmap scheme to notify the UE via DCI whether the data channel 1501 is rate matched for each rate matching resource group. For example, when four rate matching resources, RMR#1, RMR#2, RMR#3, and RMR#4, are configured, the base station can configure rate matching groups RMG#1={RMR#1, RMR#2} and RMG#2={RMR#3, RMR#4}, and can notify the UE whether rate matching has been performed in RMG#1 and RMG#2 in two bits of the DCI field. For example, for rate matching groups that perform rate matching, the corresponding bit in the bitmap can be indicated as "1", while for rate matching groups that should not perform rate matching, the corresponding bit in the bitmap can be indicated as "0".

[0469] 5G can support both "RB symbol level" and "RE level" granularity as a method for configuring the aforementioned rate matching resources to the UE. In an embodiment, the following configuration method can be followed.

[0470] <RB symbol level>

[0471] The UE can receive configurations for up to four rate matching patterns for each bandwidth portion via higher-level signaling (e.g., 'RateMatchPattern'), and a rate matching pattern can include the following.

[0472] Reserved resources within the bandwidth portion may include resources configured with corresponding time and frequency resource regions, as a combination of symbol-level and RB-level bitmaps on the frequency axis. Reserved resources may span one or two time slots. Additional signaling information (e.g., 'periodicityAndPattern') may be configured to indicate a time-domain pattern that repeats the time and frequency regions configured in each RB-level and symbol-level bitmap pair.

[0473] It may include time and frequency domain resource regions configured as control resource sets in the bandwidth portion, as well as resource regions corresponding to time domain patterns configured as search space configurations, in which the corresponding resource regions are repeated.

[0474] <RE Level>

[0475] The UE can receive the following configuration via higher-layer signaling.

[0476] The configuration information of the RE corresponding to the pattern of the LTE CRS (e.g., 'lte-CRS-ToMatchAround') may include at least one of the following: nrofCRS-Ports indicating the number of LTE CRS ports and LTE-CRS-vshift indicating the v-shift value; carrierFreqDL indicating the location of the center subcarrier of the LTE carrier at the reference frequency point (e.g., reference point A); carrierBandwidthDL indicating the bandwidth size of the LTE carrier; or mbsfn-SubframConfigList indicating the subframe configuration corresponding to the Multicast Broadcast Single Frequency Network (MBSFN). The UE can determine the location of the CRS in the NR slot corresponding to the LTE subframe based on the above information.

[0477] Configuration information about the resource set corresponding to one or more Zero Power (ZP) CSI-RS in the bandwidth section can be included in higher-layer signaling.

[0478] Figure 16 This is a view that shows an example of an uplink-downlink configuration in a wireless communication system.

[0479] refer to Figure 16Time slot 1601 can include 14 symbols 1602. The uplink-downlink configuration of the symbols / time slots can be configured in the following three steps. A

[0480] First, the uplink-downlink configuration 1610 of symbols / slots can be semi-statically indicated by symbol elements through cell-specific uplink-downlink configuration information via system information. Specifically, the cell-specific uplink-downlink configuration information may include uplink-downlink pattern information and reference subcarrier spacing information. The uplink-downlink pattern information may include at least one of the following: pattern period 1601 (meaning the period for applying a DL-UL pattern), the number of consecutive full DL slots at the beginning of each DL-UL pattern 1611, the number of consecutive DL symbols at the beginning of a slot after the last full DL slot 1612, the number of consecutive full UL slots at the end of each DL-UL pattern 1613, or the number of consecutive UL symbols at the end of a slot before the first full UL slot 1614. In this case, slots and symbols not indicated by uplink or downlink can be determined as flexible slots / symbols.

[0481] Second, the UE-specific uplink-downlink configuration 1620 for flexible time slots or time slots 1621 and 1622, including flexible symbols, can be semi-statically indicated by UE-specific configuration information via dedicated higher-layer signaling. Each time slot / symbol can be configured as uplink or downlink by a number of consecutive downlink symbols 1623 or 1625 starting from the start symbol of time slot 1621 or 1622 and a number of consecutive uplink symbols 1624 or 1626 ending from the time slot, or the entire time slot can be configured as downlink or uplink.

[0482] Finally, for symbols not indicated as downlink or uplink through system information and UE-specific configuration information, the uplink-downlink configuration 1630 for each UE group can be dynamically configured as downlink or uplink by a slot format indicator (SFI) 1631 or 1632 included in the downlink control channel. The slot format indicator 1631 or 1632 can indicate an index selected from a pre-configuration table showing the uplink-downlink configuration of 14 symbols in a slot. For example, this table can be as shown in Table 33 below.

[0483] [Table 33]

[0484]

[0485] Compared to LTE communication services, additional coverage extension technologies have been used in 5G wireless communication services. However, the actual coverage of 5G wireless communication services can utilize TDD technology, which is typically used for services that give more weight to downlink traffic. Furthermore, as the center frequency increases to extend the frequency band, the coverage area of ​​the base station and the UE decreases. Therefore, coverage enhancement is a key requirement for 5G wireless communication services. Specifically, generally, the UE transmit power is lower than the base station transmit power, and in the time domain, the downlink occupies a larger proportion than the uplink to support services that give greater weight to downlink traffic. Therefore, uplink channel coverage enhancement is a core requirement for 5G wireless communication services.

[0486] Uplink channel coverage for both the base station and the UE can be physically enhanced by increasing uplink channel time resources, lowering the center frequency, or increasing the UE's transmit power. However, due to the limitations of frequency bands predetermined by each network operator, increasing time resources and changing frequencies may be limited. Increasing the UE's transmit power may also be limited because the maximum transmit power is fixed by standard to reduce interference.

[0487] To enhance the coverage of base stations and UEs, uplink and downlink resources can be allocated in the time domain according to the ratio of uplink and downlink services, as in TDD systems, or in the frequency domain, as in FDD systems. Systems that can flexibly allocate uplink and downlink resources in the time and / or frequency domains can be referred to as XDD systems, flexible TDD systems, hybrid TDD systems, TDD-FDD systems, hybrid TDD-FDD systems, sub-band full-duplex systems, or dynamic TDD systems, and for ease of description, they are referred to as XDD systems in this disclosure. In XDD, 'X' may mean time and / or frequency.

[0488] The uplink-downlink configuration of the XDD system can be configured, allowing each symbol or time slot to be flexibly allocated to the uplink or downlink based on the service ratio of the uplink and downlink across the entire frequency band. In the frequency domain, guard bands can be allocated between downlink and uplink resources. These guard bands can be allocated to reduce interference to signal reception or uplink channels caused by out-of-band transmissions when the base station transmits downlink channels or signals within downlink resources.

[0489] By configuring the base station, UEs with more downlink traffic than uplink traffic can be allocated more downlink resources. For example, the downlink to uplink resource ratio in the time domain could be 4:1. Similarly, UEs operating at the cell edge and therefore with insufficient uplink coverage can be given slightly more downlink resources than uplink resources. For instance, the downlink to uplink resource ratio in the time domain could be 1:4. This allows for the allocation of more downlink resources in the time domain to UEs operating relatively at the cell center with more downlink traffic, improving downlink transmission efficiency, while allowing for the allocation of more uplink resources to UEs operating relatively at the cell edge with insufficient uplink coverage.

[0490] Figure 17 This is a view showing an example of an uplink-downlink configuration in an XDD system.

[0491] refer to Figure 17 From the base station's perspective, for cell-specific uplink-downlink configuration 1715, most of the time resources can be set to flexible (F) for flexible resource operation.

[0492] For UEs that do not support full-duplex transmission / reception of uplink and downlink simultaneously in the same time-frequency resources, the base station can configure downlink and uplink resources separately for specific times (e.g., a timeslot). As an example, in the illustrated example, UEs 1 and 2 (1710 & 1705) can be allocated either downlink or uplink resources in each time range. In the second to fourth time ranges, the downlink resources for UE 1710 (receiving downlink) and the uplink resources for UE 1705 (transmitting uplink) should be separated from each other. This is because downlink transmission 1701 and uplink transmission 1702 occur simultaneously within the same time range, as seen from a network perspective in uplink-downlink configuration 1700.

[0493] The separation of downlink and uplink resources can be achieved through one of two methods. The first method involves configuring the BWP (Browser Window) information for UE 1 (1710) and UE 2 (1705) so that the DL (Downlink) BWP of UE 1 (1710) and the UL (Upper) BWP of UE 2 (1705) do not overlap. This offers the advantage of minimizing the impact on the implementation of the UE and the base station, but it may lose flexibility and take a long time because changing the frequency resource ratio between downlink and uplink within a given timeframe requires BWP handover. For ease of description, the first method is referred to below as the BWP-based XDD operation method. The second method involves allocating the scheduled PDSCH of UE 1 (1710) and the scheduled PUSCH of UE 2 (1705) so that they do not overlap in the frequency domain. This method is based on base station scheduling and therefore offers very high flexibility and allows for very rapid changes in the downlink-uplink frequency resource ratio. However, since the DL BWP of UE 1 (1710) may overlap wholly or partially with the UL BWP of UE 2 (1705), various problems described below may arise. For ease of description, the second method will be referred to below as the scheduling-based XDD operation method.

[0494] Figure 18 This is a view illustrating an example of uplink-downlink configuration and bandwidth portion (BWP) configuration for a base station in an XDD system. The base station may appropriately use any of the downlink and uplink frequency resource allocation methods described above for XDD.

[0495] refer to Figure 18 From the base station's perspective, an uplink-downlink configuration such as in 1820 can be used. The base station can allocate a 4:1 downlink-uplink resource ratio to UEs 1825 and 1830, which have more downlink traffic than uplink traffic, in the time domain. In this case, if the base station applies the aforementioned BWP-based XDD operation method to UE 1830, the scheduled DL resources (e.g., PDSCH) 1800 and scheduled UL resources (e.g., PUSCH) 1805 for UE 1830 may not be allocated to areas 1815 other than the active DL BWP and UL BWP, thus potentially partially limiting the uplink / downlink throughput of UE 1830.

[0496] In this embodiment, when the base station applies the above-described scheduling-based XDD operation method to UE 1825, it can have greater scheduling flexibility compared to BWP-based XDD operation. As an example, the base station can allocate the scheduled PDSCH for UE 1825 in a first time range (e.g., multiple symbols, time slots, or subframes) to a wider frequency band than in other time ranges. Similarly, when uplink transmissions for other UEs (e.g., UEs 1835 and 1840) are required in the second to fourth time ranges, the base station may not allocate PDSCH for UE 1825 in the second to fourth time ranges.

[0497] The base station can allocate a 1:4 downlink-to-uplink resource ratio to UEs 1835 and 1840, where UEs 1835 and 1840 have more uplink traffic than downlink traffic, or where uplink coverage is critical to them. In this case, if the base station applies the BWP-based XDD operation method to UE 1840, the scheduled PDSCH 1800 and scheduled PUSCH 1805 for UE 1840 may not be allocated to areas 1815 other than the active DL BWP and UL BWP, thus potentially partially limiting the uplink / downlink throughput of UE 1840.

[0498] In this embodiment, when the base station applies a scheduling-based XDD operation method to UE 1835, it can have greater scheduling flexibility compared to BWP-based XDD operation. As an example, the base station can allocate the scheduled PUSCH for UE 1835 in the fifth time range (e.g., multiple symbols, slots, or subframes) to a wider frequency band than in other time ranges. Similarly, when downlink reception for other UEs (e.g., UE 1830) is required in the second to fourth time ranges, the base station may not allocate a PUSCH for UE 1835 in the second to fourth time ranges.

[0499] There may be a resource 1810, which is included in the active DL BWP or UL BWP of each UE, but without downlink resources (e.g., PDSCH) or uplink resources (e.g., PUSCH) allocated to it, and ambiguity may arise in the operation of the base station and the UE in resource 1810. As an example, the tracking reference signal (TRS) uses 52RB and the minimum of the BWP bandwidth in which the TRS is transmitted as the transmission bandwidth, such that a UE 1825 operating in an active DLBWP that includes uplink resources of other UEs may incorrectly determine to transmit the TRS in resource area 1810 in which no downlink resources (e.g., PDSCH) are allocated for XDD operation. As another example, a UE operating in an active UL BWP that includes downlink resources of other UEs may incorrectly determine to transmit periodic or semi-persistent uplink channels or signals, such as PUCCH or SRS, in resource area 1810 in which no downlink resources are allocated for XDD operation or no uplink resources are available.

[0500] TRS is a reference signal configured for fine time / frequency tracking of a base station and may be referred to as CSI-RS for tracking, but for convenience of description, it is referred to as TRS in this disclosure. TRS can be transmitted in one (X=1) or two (X=2) consecutive time slots according to a pattern of a specific period such as 10ms or 20ms, and consecutive TRS are referred to as TRS bursts.

[0501] Figure 19 This is a view illustrating an example of a TRS pattern according to an embodiment of the present disclosure. It should be noted that the positions of the OFDM symbols shown are examples of TRS configurations, and the actual transmission locations may vary depending on the base station configuration.

[0502] Figure 19The diagram illustrates a possible TRS pattern within a time slot. The TRS shown has a frequency RE density of 3 RE / RB / port, and each RE in the TRS can be repeated once every four subcarriers. In other words, a one-port TRS can be transmitted in a RE with one of the values ​​0, 1, 2, and 3 as indicated in the TRSOFDM symbol RE. In an embodiment, the TRS can be transmitted in one of three OFDM symbol pairs {5th, 9th}, {6th, 10th}, and {7th, 11th} in a frequency band of 6 GHz or lower, referred to as Frequency Range 1 (FR1), and in one of ten OFDM symbol pairs {1st, 5th}, {2nd, 6th}, {3rd, 7th}, {4th, 8th}, {5th, 9th}, {6th, 10th}, {7th, 11th}, {8th, 12th}, {9th, 13th}, and {10th, 14th} in a frequency band of 6 GHz or higher, referred to as Frequency Range 2 (FR2).

[0503] Figure 20 An example of a 1-port CSI-RS configuration according to an embodiment of the present disclosure is shown.

[0504] Figure 20 The cover is shown Figure 19 Example of a 1-port CSI-RS configuration for a TRS pattern. A base station can configure a resource set using resource configuration information, and configure up to four CSI-RS resources in each resource set. In this case, the frequency density of the CSI-RS can be set to 3 RE / RB / port. If X=1 TRS bursts are used, the base station can configure CSI-RS resources #0 and #1. If X=2 TRS bursts are used, the base station can configure all of CSI-RS resources #0, #1, #2, and #3. When X=1 or X=2 TRS bursts are used, for CSI-RS resources configured in one resource set, the UE can assume the same antenna ports with the same port index and perform continuous time / frequency tracking based on this.

[0505] When CSI-RS resources are configured as TRS, the base station may not configure the corresponding reporting settings (i.e., no reporting settings referencing CSI-RS resources) or may set the reporting setting value to 'none' and send it to the UE. Depending on the base station's configuration, the UE may use the CSI-RS resources for time / frequency tracking purposes, or may ensure that no CSI reports are created.

[0506] exist Figure 20 In this context, the subcarrier positions and OFDM symbol positions of the 1-port CSI-RS resource can depend on... Figure 19 The position of the TRS subcarrier changes.

[0507] TRS can be transmitted periodically, semi-persistently, or aperiodically. Periodic TRS (P-TRS) can be transmitted periodically according to the period and slot offset configured by the RRC until the RRC is reconfigured. Semi-persistent TRS (SP-TRS) can be activated or deactivated by the MAC CE or DCI, and when activated, it is transmitted according to the period and slot offset configured by the RRC. Aperiodic TRS (A-TRS) can be transmitted by triggers in the DCI or MAC CE without a period or slot offset.

[0508] In embodiments, the timing of A-TRS triggering and / or A-TRS transmission can follow pre-agreed values ​​(e.g., the same time slot as the A-TRS trigger) or offsets configured by higher layers. Since the REs on the time axis are insufficient when measuring only with aperiodic TRS, it may be difficult to measure the statistical characteristics of the channel; therefore, aperiodic TRS can be connected (associated) with periodic TRS or semi-persistent TRS. The connection between A-TRS and SP-TRS or P-TRS can be supported by various methods such as quasi-co-location (QCL). For example, the base station can configure at least one SP-TRS or P-TRS as the QCL reference RS for the A-TRS to allow the UE to extract channel statistics (QCLtyep A) based on the TRS, including at least one of delay spread, average delay, Doppler spread, or Doppler shift, or to allow the UE to extract spatial parameters associated with at least one of the TX or RX beams (QCL type D).

[0509] In this embodiment, bandwidth can be allocated to the TRS using freqBand, which is a higher-level parameter. For example, when the bandwidth of the BWP in which the TRS is transmitted is less than 52 RB, the bandwidth of the TRS can be the same as the bandwidth of the BWP, and when the bandwidth of the BWP in which the TRS is transmitted is equal to or greater than 52 RB, the bandwidth of the TRS can be set to 52 RB.

[0510] Power amplifiers (PAs) and low-noise amplifiers (LNAs) used in base stations and UEs of wireless communication systems can have predetermined levels of nonlinearity. The baseband equivalent value x of the nonlinear PA output signal... nPA (n) can be expressed as the following equation.

[0511] [Equation 3]

[0512]

[0513] Here, x(n) is the baseband transmitted signal, p is the maximum nonlinear order, and f p,n It is the impulse response of a PA of length N-1, and It's a convolution operation. If the coupling response between the transmitter and receiver (i.e., the coupling response from PA to LNA) is h... n Then the downlink leakage signal x Lkg (n) can be expressed as the following equation.

[0514] [Equation 4]

[0515]

[0516] Here, h p,n It is the effective coupling response coefficient of order p.

[0517] In XDD, when uplink and downlink frequency bands are arranged close together—for example, when the guard band between simultaneously transmitted / received uplink and downlink is not wide enough, or when the distance on the frequency axis between simultaneously allocated uplink and downlink resources is short—the base station can receive downlink leakage signals x while receiving uplink frequency band signals. Lkg (n) and the expected uplink signal x UL (n). In this case, the received uplink signal y(n) can be expressed as the following equation.

[0518] [Equation 5]

[0519]

[0520] Here, z(n) represents the noise signal.

[0521] The above context and corresponding equations can be readily transformed and applied to situations where the UE receives uplink leakage signals simultaneously with downlink band reception. To avoid obscuring the subject matter of this disclosure, a detailed description of the impact of uplink leakage signals on downlink reception will be omitted.

[0522] In this disclosure, for ease of description, uplink leakage signals received together with the desired downlink signal, or downlink leakage signals received together with the desired uplink signal, are collectively referred to as adjacent channel leakage (ACL) interference.

[0523] ACL can be used interchangeably with other terms that indicate uplink signal measurement and reporting by the UE, such as Cross-Link Interference (CLI).

[0524] Figure 21 and 22 An example of the impact of adjacent channel leakage during XDD operation is shown.

[0525] Figure 21This is a view illustrating an example of uplink receive frequency response measurement during uplink independent transmission / reception according to an embodiment of the present disclosure.

[0526] refer to Figure 21 Since there is no interference from adjacent channel leakage when only the uplink is transmitted (i.e., when operating as TDD), the power spectral density (PSD) 2105 measured in the band of interest can have a relatively flat trend.

[0527] Figure 22 This is a view illustrating an example of uplink receive frequency response measurement when uplink / downlink is simultaneously transmitting / receiving, according to an embodiment of this disclosure.

[0528] refer to Figure 22 When uplink and downlink are transmitted / received simultaneously (i.e., when operating as XDD), adjacent channel leakage interference occurs, exhibiting the following trend: [The text abruptly shifts to a different topic] ...in the vicinity of interference ( Figure 22 The frequency band of interest (in the downlink signal) Figure 22 The PSD 2210 measured in the uplink signal (in the signal) has a relatively large value, and is far from interference ( Figure 22 The frequency band of interest (in the downlink signal) Figure 22 The PSD 2205 measured in the uplink signal (in the signal) has a relatively small value. Due to the influence of adjacent channel leakage, even when there is no adjacent channel leakage, the error vector magnitude (EVM) value can increase significantly. Figure 22 The EVM is -16dB, and a large amount of noise is generated in the constellation of the uplink received signal.

[0529] This disclosure provides embodiments for measuring and reporting or sharing adjacent channel leakage interference to enhance the performance of XDD systems, such as maximizing receive performance and minimizing guard bands.

[0530] The main points of this disclosure are described below with reference to specific embodiments.

[0531] The following describes transmission / reception methods and apparatus for base stations and UEs considering XDD systems. However, the points of this disclosure are not limited to XDD systems, but can be similarly applied to channel and signal transmission / reception methods and apparatus for duplex methods (e.g., full-duplex or dynamic TDD) that can be provided in 5G systems for similar purposes.

[0532] <First Embodiment>

[0533] Methods for measuring adjacent channel leakage interference considering XDD operation and for reporting information on measurement interference between base stations, between UEs, and between UEs and base stations are described.

[0534] Figure 23 This is a view illustrating an example of an uplink-downlink interference scenario in an XDD system according to an embodiment of the present disclosure.

[0535] refer to Figure 23 In scenario #1, base station 2305 can consider adjacent channel leakage from downlink signals ② and ③ transmitted simultaneously with the desired uplink signal ④ in order to receive the desired uplink signal ④ transmitted from UE 2320. When measuring adjacent channel leakage, base station 2305 can apply different methods based on at least one of the characteristics of the interfering downlink signals ② and ③, backhaul delay, or network context.

[0536] In this embodiment, base station 2305 may not allocate uplink signals or channels to the time-frequency resources used for measuring downlink adjacent channel leakage, or configure uplink rate matching resources. When downlink adjacent channel leakage includes downlink self-interference ② transmitted from the transmit antenna of base station 2305, since base station 2305 knows the transmission information of self-interference ②, base station 2305 can appropriately determine uplink allocation and uplink rate matching resource configuration for UE 2320 based on the transmission information of self-interference ②.

[0537] In an embodiment, when downlink adjacent channel leakage includes interference ③ from downlink signals transmitted from the transmit antenna of another base station 2315, base station 2305 may not be aware of all or part of the downlink signal transmission information. In this case, to accurately measure downlink adjacent channel leakage, it may be necessary to share information related to the allocation (scheduling) or configuration of downlink signals transmitted from base station 2315 between base stations. Here, depending on the network context, the term "between base stations" may refer to at least one of "between gNBs," "between transmit and receive points (TRPs)," "between distributed units (DUs)," "between controllers or central units (CUs)," "between radio units (RUs)," or "between public land mobile networks (PLMNs) or operators." To share information between base stations, an interface may be defined for transmitting adjacent channel leakage measurements, and related details can be found in the third embodiment below.

[0538] refer to Figure 23In scenario #2, UE 2310 can consider adjacent channel leakage from another UE 2320, which is transmitted simultaneously with the desired downlink signals ① and ⑥, in order to receive the desired downlink signals ① and / or ⑥ transmitted from base stations 2305 and 2315. When configuring UE 2310 to measure adjacent channel leakage, due to the difference in the relative positions between UE 2310 and 2320, base station 2305 can apply different methods based on various conditions, including the characteristics that interfere with the uplink signal ⑤.

[0539] In this embodiment, when the distance between UE 2310, which receives downlink signals, and UE 2320, which transmits uplink signals, is short, base station 2305 can estimate that the downlink reception performance of UE 2310 is likely to deteriorate due to adjacent channel leakage. Base station 2305 can configure the time / frequency resources for measuring uplink adjacent channel leakage via higher-layer signaling, or indicate it to UE 2310 via L1 signaling, to anticipate the degree of deterioration in downlink reception performance. UE 2310 can measure uplink adjacent channel leakage interference in the configured resources and report the measurement value to base station 2305, or share the measurement value with another UE (e.g., UE 2320).

[0540] Here, the distance between UEs can represent geographical distance, or it can represent information obtained through channel estimation using uplink reference signals (such as SRS) or downlink reference signals (such as CSI-RS) (e.g., including at least one of angle information, codebook index, or precoding matrix or channel correlation).

[0541] In an embodiment, adjacent channel leakage interference can be measured and reported based on uplink signals / channels (e.g., SRS) or downlink signals / channels (e.g., CSI-RS).

[0542] <Measuring Adjacent Channel Leakage Interference Based on Uplink Signal / Channel>

[0543] Neighbor channel leakage interference based on uplink signals / channels can be measured based on uplink signal or channel time / frequency resource information (e.g., RE mapping pattern), which includes at least one of SRS resources, UL rate matching resources, UL OFDM symbol positions, UL timeslot positions, UL PRB / subband positions, or UL BWPs. As an example, neighbor channel leakage interference measurement can be performed by combining... Figure 23 The scenario described is executed by UE 2310.

[0544] In an embodiment, the base station can configure at least one SRS resource for the UE, and can measure the SRS-RSRP according to Table 34 below and report it to the base station, or configure or instruct it to be shared among UEs. Similarly, the base station can configure the UE to measure the Cross-Link Interference Received Signal Strength Indicator (CLI-RSSI) in a specific OFDM symbol according to the definitions in Table 35, and report the measurement results to the base station or share them with other UEs. In an embodiment, the base station can send SRS configuration information or CLI configuration information to the UE, including parameters and resources that can be used to measure SRS or CLI. The UE can measure the SRS-RSRP or CLI-RSSI from the received uplink signal based on the configuration information. In an embodiment, the base station can send SRS reporting configuration information or CLI reporting configuration information to the UE, including resources and parameters that can be used to report SRS or CLI. The UE can report the SRS-RSRP or CLI-RSSI based on the reporting configuration information.

[0545] In this embodiment, to allow sharing of at least one of SRS-RSRP and CLI-RSSI among UEs, reporting values ​​such as SRS-RSRP-UE or CLI-RSSI-UE can be defined and configured in the UE. In this embodiment, the base station can indicate via separate higher-layer parameters whether the SRS-RSRP or CLI-RSSI report configured in the UE is for UE-base station reporting or a report shared among UEs. The UE can provide reporting values ​​to other UEs according to the base station's configuration.

[0546] Tables 34 and 35 below show the SRS-RSRP or CLI-RSSI defined as the average of all frequency resources in a given time resource. In an embodiment, subband reporting can be introduced to appropriately report the imbalance of each frequency resource in adjacent channel leakage interference. In other words, the base station can send configuration information to the UE instructing the reporting of SRS-RSRP or CLI-RSSI for at least one subband. In this case, the resource element used to measure and report subband adjacent channel leakage interference can consist of one or more frequency resources. In an embodiment, one or more frequency resources may include consecutive subcarriers (or REs) following a number or setting value defined in the standard, or may include one or more PRBs or Resource Block Groups (RBGs). In an embodiment, one or more frequency resources can be defined using the setting value of csi-ReportingBand and its definition shown in Table 21.

[0547] In embodiments, considering the tendency of adjacent channel leakage interference to gradually decrease or increase along the frequency domain, the subband used for adjacent channel leakage interference measurement can be configured to include frequency resources located at two opposite ends of the configured measurement frequency band, or to include at least some specific frequency resources that equally divide the configured measurement frequency band. As an example, an adjacent channel leakage interference report can include two values, where the first value can represent the amount of interference at the lowest (highest) index on the frequency axis (e.g., one of the lowest (highest) subcarrier / PRB / subband indices), and the second value can represent the amount of interference at the highest (lowest) index on the frequency axis (e.g., one of the highest (lowest) subcarrier / PRB / subband indices). When an adjacent channel leakage interference report includes N values, each value can be expanded in a similar manner to that described above.

[0548] In order to measure adjacent channel leakage interference according to one of the above examples, when a report for at least one of SRS-RSRP or CLI-RSSI is configured in the UE and frequency resources (e.g., at least one subband) for the report are configured, the UE can calculate the “linear average of power contribution (in [W])” for each subband in Tables 34 and 35.

[0549] [Table 34]

[0550] SRS Reference Signal Received Power (SRS-RSRP)

[0551]

[0552] [Table 35]

[0553] CLI Received Signal Strength Indicator (CLI-RSSI)

[0554]

[0555] <Measuring Adjacent Channel Leakage Interference Based on Downlink Signal / Channel>

[0556] Neighbor channel leakage interference based on downlink signals / channels can be measured based on downlink signal or channel time / frequency resource information (e.g., RE mapping pattern) including at least one of CSI-RS resources, DL rate matching resources, DL OFDM symbol positions, DL PRB / subband positions, or DL ​​BWP.

[0557] In an embodiment, the base station can configure at least one CSI-RS resource for the UE, and can measure one or more of CSI-RSRP, CSI-RSRQ, or CSI-SINR according to Tables 36 to 38 below, and report it to the base station, or configure or indicate it for sharing among the UEs. In an embodiment, the base station can configure the UE to measure RSSI in a specific OFDM symbol according to the definitions in Table 39, report it to the base station, or share it among the UEs. Specifically, the base station can send configuration information to the UE, which includes resources and parameters that can be used to measure CSI-RSRP, CSI-RSRQ, CSI-SINR, or RSSI. The UE can measure CSI-RSRP, CSI-RSRQ, CSI-SINR, or RSSI from received downlink signals based on the configuration information. Furthermore, the base station can send reporting configuration information to the UE, which includes resources and parameters that can be used to report CSI-RSRP, CSI-RSRQ, CSI-SINR, or RSSI. The UE can report CSI-RSRP, CSI-RSRQ, CSI-SINR, or RSSI based on the reporting configuration information.

[0558] In an embodiment, a base station can measure CSI-RSRP, CSI-RSRQ, CSI-SINR, or RSSI from downlink signals received from neighboring base stations based on the time and frequency resources of adjacent channel leakage interference in each subband, and share them among base stations.

[0559] As an example, to allow UEs to share at least one of CSI-RSRP, CSI-RSRQ, CSI-SINR, and RSSI, report values ​​such as CSI-RSRP-UE, CSI-RSRQ-UE, CSI-SINR-UE, and RSSI-UE can be defined and configured in the UE. In this example, the base station can indicate, through separate higher-layer parameters, whether a CSI-RSRP, CSI-RSRQ, CSI-SINR, or RSSI report configured in the UE is a report used for UE-base station reporting or UE-UE reporting. The UE can generate CSI-RSRP-UE, CSI-RSRQ-UE, CSI-SINR-UE, or RSSI-UE according to its configuration and send it to another UE.

[0560] Tables 36 to 39 show the CSI-RSRP, CSI-RSRQ, CSI-SINR, or RSSI defined as the average of all frequency resources in a given time resource. However, subband reporting can be introduced to appropriately report the imbalance of each frequency resource in adjacent channel leakage interference. The base station can send configuration information to the UE instructing the reporting of CSI-RSRP, CSI-RSRQ, CSI-SINR, or RSSI for at least one subband. In this case, the resource element used to measure and report subband adjacent channel leakage interference can consist of one or more frequency resources. In embodiments, one or more frequency resources may include consecutive subcarriers (or REs) following a number or setting value defined in the standard, or may include one or more PRBs or RBGs. In embodiments, one or more frequency resources can be defined using the setting values ​​of csi-ReportingBand and their meanings shown in Table 21.

[0561] In embodiments, considering the tendency of adjacent channel leakage interference to gradually decrease or increase along the frequency domain, the subband used for adjacent channel leakage interference measurement can be configured to include frequency resources located at two opposite ends of the configured measurement frequency band, or to include at least some specific frequency resources that equally divide the configured measurement frequency band. As an example, an adjacent channel leakage interference report can include two values, where the first value can represent the amount of interference at the lowest (highest) index on the frequency axis (e.g., one of the lowest (highest) subcarrier / PRB / subband indices), and the second value can represent the amount of interference at the highest (lowest) index on the frequency axis (e.g., one of the highest (lowest) subcarrier / PRB / subband indices). When an adjacent channel leakage interference report includes N values, each value can be expanded in a similar manner to that described above.

[0562] In order to measure adjacent channel leakage interference according to one of the above embodiments, when a report for at least one of CSI-RSRP, CSI-RSRQ, CSI-SINR and RSSI is configured in the UE, and frequency resources (e.g., at least one sub-band) for the report are configured, the UE can calculate the “linear average of power contribution (in [W])” in Tables 36 and 39 for each sub-band.

[0563] [Table 36]

[0564] CSI Reference Signal Received Power (CSI-RSRP)

[0565]

[0566] [Table 37]

[0567] CSI Reference Signal Received Quality (CSI-RSRQ)

[0568]

[0569] [Table 38]

[0570] CSI signal-to-noise ratio (CSI-SINR)

[0571]

[0572] [Table 39]

[0573] Received Signal Strength Indicator (RSSI)

[0574]

[0575] Although the subband measurement of adjacent channel leakage interference has been described above in the SRS RE pattern, in the CSI-RS RE pattern, or at the OFDM symbol level, the embodiments of this disclosure are not limited and similar operations can be performed relative to various time / frequency resource regions including at least one of the PDSCH rate matching pattern, PUSCH rate matching pattern, or reference signal RE pattern.

[0576] Figure 24A and 24B This is a view illustrating an example of frequency domain resource configuration for adjacent channel leakage interference measurement according to an embodiment of the present disclosure. Here, for ease of description, simplified... Figure 22 The PSD. The desired channels 2415, 2425, or 2430 shown can correspond to... Figure 22 The uplink resources in the context shown, and the interference channels 2420 or 2435 shown, can correspond to... Figure 22 Downlink resources in the context shown. This depends on the XDD operating environment, for example, in... Figure 23 In scenario #2, the meanings of the desired channel and the interference channel can be appropriately changed, but their detailed descriptions are omitted to avoid obscuring the key points.

[0577] As shown in the figure, the trend of adjacent channel leakage interference can be changed according to the resource allocation options of the desired channel and the interfering channel, thereby enabling sub-band adjacent channel leakage interference measurement to be performed using one of the following three options.

[0578] refer to Figure 24AOption 1 2400 describes a frequency resource configuration for subband interference measurement, wherein, for XDD operation, an interfering channel 2420 operating in a downlink resource and a desired channel 2415 operating in an uplink resource are configured to be adjacent to each other in the frequency domain. Within the desired channel's frequency band, the closer to the interfering channel 2420, the greater the adjacent channel leakage interference. Therefore, the base station can configure a frequency resource including all or part of the desired channel 2415's frequency band for subband interference measurement to measure and report adjacent channel leakage interference.

[0579] refer to Figure 24B Option 2 2405 describes a frequency resource configuration for subband interference measurement, where, for XDD operation, an interfering channel 2425 in one uplink resource is configured to be adjacent in the frequency domain to desired channels 2425 and 2430 in two downlink resources. This configuration can be considered as minimizing the impact of adjacent channel leakage of the interfering channel 2435 on another operator in an adjacent frequency band. In this case, within the frequency bands of desired channels 2425 and 2430, the closer to the interfering channel 2435, the greater the adjacent channel leakage interference. Therefore, different trends in adjacent channel leakage appear in the two downlink resources 2425 and 2430. Given this, a frequency resource encompassing all frequency bands of the two desired channels 2425 and 2430 can be configured for subband interference measurement, and in some of its frequency bands, it is possible to measure and report adjacent channel leakage interference.

[0580] refer to Figure 24B Option 3 2410 describes a frequency resource configuration for subband interference measurement, where, for XDD operation, an interfering channel 2425 in one uplink resource is configured to be adjacent in the frequency domain between desired channels 2425 and 2430 in two downlink resources. This configuration can be considered as minimizing the impact of adjacent channel leakage of the interfering channel 2435 on another operator in an adjacent frequency band. In this case, within the frequency bands of desired channels 2425 and 2430, the closer to the interfering channel 2435, the greater the adjacent channel leakage interference. Therefore, different trends in adjacent channel leakage appear in the two downlink resources 2425 and 2430. Given this, two separate frequency resources corresponding to the two desired channels 2425 and 2430 can be configured to measure adjacent channel leakage interference.

[0581] <Second Embodiment>

[0582] UL frequency hopping can be provided, taking into account leakage interference from adjacent subband channels. The UL frequency hopping described below can be applied to uplink channels / signals such as PUSCH, PUCCH, or SRS.

[0583] Figure 25This is a view illustrating an example of uplink frequency hopping considering adjacent channel leakage interference measurement and reporting according to an embodiment of this disclosure.

[0584] refer to Figure 25 The base station can be configured with one or more subbands #1 to #N 2510 and 2515 within the UL BWP 2500, which can be used to measure adjacent channel leakage interference 2500. In this case, a subband 2520 may exist in the UL BWP 2500 in addition to the subbands 2510 and 2515 configured for adjacent channel leakage interference measurement.

[0585] In this embodiment, the base station can configure frequency hopping for SRS, PUCCH, or PUSCH to increase uplink coverage. In this case, the UE can transmit SRS, PUCCH, or PUSCH in frequency bands 2530, 2535, 2540, or 2545 determined according to a previously agreed (or configured) frequency hopping mode. By measuring and reporting the first subband 2510, the base station and the UE can know that there is a relatively small adjacent channel leakage interference in frequency band 2530 of the first frequency hopping mode, and by measuring and reporting the nth subband 2515, they can know that there is a relatively large adjacent channel leakage interference in frequency band 2545 of the nth frequency hopping mode. Therefore, uplink reception in the Nth subband 2515 may be less efficient than uplink reception in the first subband 2510.

[0586] To reduce the differences in uplink receive performance for each frequency hopping mode due to varying adjacent channel leakage interference values ​​in each subband, the base station can configure the transmit power of the uplink signal or channel to be increased proportionally to the measured or reported adjacent channel leakage interference value. In an embodiment, the base station can send configuration information to the UE instructing the transmission of uplink channels / signals for measuring adjacent channel leakage interference according to frequency hopping mode #1 and frequency hopping mode #N. The configuration information sent by the base station or separate higher-layer signaling can instruct the UE to use a relatively lower transmit power in subband #1 2510, which overlaps with frequency band 2530 of frequency hopping mode #1, and a relatively higher transmit power in subband #N 2515, which overlaps with frequency band 2545 of frequency hopping mode #N.

[0587] Since the frequency bands of some frequency hopping modes in the UL BWP 2500 (e.g., frequency hopping modes 2535 and 2540) do not overlap with subbands 2510 and 2515 used for measuring and reporting adjacent channel leakage interference, the base station and UE can interpolate the transmit power values ​​of frequency bands 2530 and 2545 applied to frequency hopping modes #1 and #N to obtain interpolated transmit power values, and apply the interpolated transmit power values ​​to frequency bands 2535 and 2540 of the frequency hopping modes. In another embodiment, the base station and UE can interpolate the transmit power values ​​that have been corrected to take into account adjacent channel leakage interference measured in subbands 2510 and 2515 to obtain interpolated transmit power values, and apply the interpolated transmit power values ​​to frequency bands 2535 and 2540 of the frequency hopping modes.

[0588] <Third Embodiment>

[0589] An interface is described for sharing measurement-related information about subband adjacent channel leakage interference among network components.

[0590] Figure 26 This is a view illustrating an interface for sharing adjacent channel leakage interference measurements according to an embodiment of the present disclosure.

[0591] refer to Figure 26 The 5G network may include a 5G core network 2600 and one or more gNB control units (CUs) 2605 connected thereto, gNB distributed units (DUs) 2620 and 2625 connected to one or more CUs, and radio units (or remote units) (RUs) connected to the DUs respectively. The interfaces between components are defined as seamlessly connecting network components. As an example, one gNB CU 2605 and another gNB CU 2630 can exchange the information shown in Table 40 below via interference referred to as Xn 2650. In an embodiment, when gNB CU 2630 is connected to eNB CU 2635, for backward compatibility, the information shown in Table 40 can be exchanged via the X2 interface 2655 defined in LTE.

[0592] [Table 40]

[0593]

[0594] The configuration information for adjacent channel leakage interference measurement mentioned above may include information related to interference between base stations, such as... Figure 23 As shown in ③, and needs to be shared between base stations CU or DU. For this purpose, the X2 interface 2655 or Xn interface 2650 may also carry configuration information corresponding to at least one of the measurements and reports of adjacent channel leakage interference.

[0595] In one embodiment, the gNB CU 2630 can send configuration information regarding the measurement and / or reporting of adjacent channel leakage interference related to inter-base station interference to the gNB CU 2605 via the Xn interface 2650. The configuration information can be used to measure adjacent channel leakage interference in the gNB CU 2605 or to create configuration information for the UE. In another embodiment, the gNB CU 2630 can send configuration information regarding the measurement and / or reporting of adjacent channel leakage interference related to inter-base station interference to the eNB CU 2635 via the Xn interface 2655. The configuration information can be used to measure adjacent channel leakage interference in the eNB CU 2635 or to create configuration information for the UE.

[0596] In this context, Xm interfaces 2660 and 2665 (meaning interfaces used to carry MAC information or interfaces between different DUs) can also be used to carry configuration information related to the measurement and reporting of adjacent channel leakage interference. In an embodiment, a gNB DU (e.g., gNB DU 2625) can send configuration information regarding the measurement and / or reporting of adjacent channel leakage interference related to inter-base station interference to another gNB DU or eNB DU (e.g., eNB DU 2640) via Xm interfaces 2660 and 2665. The configuration information can be used to measure adjacent channel leakage interference in a gNB CU or eNB DU, or to create configuration information for a UE.

[0597] <Fourth Embodiment>

[0598] A method is provided to apply measurement offset by taking into account asynchronous networks when measuring and reporting leakage interference in adjacent channels.

[0599] In this embodiment, information regarding adjacent channel leakage interference measurements may include information about inter-base station interference, such as... Figure 23 As shown in ③, in asynchronous networks, the transmission or reception timing between two different base stations may not be perfectly matched at the sample, symbol, or time slot levels. When the degree of mismatch at the sample, symbol, or time slot levels is not shared between base stations, or when the UE is unaware of the degree of mismatch, the timing of adjacent channel leakage interference measurements may be inaccurate. When base stations treat adjacent channel leakage interference as part of the overall interference when calculating the signal-to-interference-plus-noise ratio (SINR), the ambiguity in the timing of adjacent channel leakage interference measurements may impair the accuracy of the calculation.

[0600] To address this issue, a base station can provide a measurement offset of higher-layer signaling to another base station or UE, indicating the degree of timing mismatch between base stations at the sample level, symbol level, or time slot level. In this case, the measurement offset of the mismatch degree can include at least one of sample-level offset, symbol-level offset, and time slot-level offset, or can be defined as a value indicating the degree of timing mismatch at the sample level, symbol level, or time slot level.

[0601] In one embodiment, the base station may include a measurement offset indicating the timing difference between base stations in MeasGapConfig and send it to the UE. MeasGapConfig is a higher-layer signaling that indicates configuration information regarding the measurement gap. As an example, MeasGapConfig may include refFR2ServCellAsyncXDD, which is a parameter indicating the timing difference between base stations. This parameter may include at least one of sample-level offset, symbol-level offset, and slot-level offset, or may be defined as a value indicating the degree of timing mismatch at the sample-level, symbol-level, or slot-level.

[0602] As another embodiment, the MeasGapConfig sent by the base station can be configured as shown in Table 41. Here, the parameter refFR2ServCellAsyncCA in MeasGapConfig, which indicates the reference cell for Rel-16 asynchronous CA, can include a value indicating the difference between the transmission timing and reception timing between two different base stations at the sample level, symbol level, or slot level.

[0603] In Table 41, the `refFR2ServCellAsyncCA` field exists only when the AsyncCA condition is met. Since adjacent channel leakage interference caused by XDD operation needs to be measured regardless of the AsyncCA condition, the condition for the existence of the `refFR2ServCellAsyncCA` field can be extended to include cases where the base station is configured to perform XDD operation. In this case, the base station configuring XDD operation means that the base station setting UL rate matching can include at least one of the following: when the base station is configured to perform UL rate matching, when the base station is configured to perform XDD BWP, when the base station is configured to perform adjacent channel leakage interference measurement and reporting, or when the base station is configured to perform subband interference measurement and reporting.

[0604] [Table 41]

[0605] MeasGapConfig

[0606] IE MeasGapConfig specifies the measurement gap configuration and controls the setting / releasing of the measurement gap.

[0607] MeasGapConfig information element

[0608]

[0609]

[0610]

[0611]

[0612] The following describes UE operation and base station implementation considering XDD operation.

[0613] Figure 27A This is a flowchart illustrating UE operation according to an embodiment of the present disclosure.

[0614] refer to Figure 27A In step 2700, the UE may send a UE capability report to the base station for measuring and reporting subband adjacent channel leakage interference according to at least one or a combination of the methods described in the above embodiments. The UE capability report may include information indicating whether the measurement and reporting of subband adjacent channel leakage interference is possible, and information indicating the types of methods that the UE can support for measuring and reporting subband adjacent channel leakage interference. The base station may refer to the UE capability report to create configuration information for the UE, including relevant information such as frequency resources and time resources, for the measurement and reporting of subband adjacent channel leakage interference.

[0615] In step 2705, the UE may receive configuration information from the base station via higher-layer signaling and / or L1 signaling. As an example, the configuration information may include information indicating the execution of adjacent channel leakage (ACL) interference measurement and reporting, time resource information indicating the time range to be used for ACL interference measurement, frequency resource information indicating at least one subband to be used for ACL interference measurement, or measurement offset indicating the degree of timing mismatch between base stations at the sample level, symbol level, or time slot level.

[0616] In step 2710, the UE can measure subband adjacent channel leakage interference according to the configuration information and report the measured subband adjacent channel leakage interference.

[0617] Figure 27B This is a flowchart illustrating the operation of a base station according to an embodiment of the present disclosure.

[0618] refer to Figure 27BIn step 2720, the base station can receive from the UE a UE capability report for measuring and reporting subband adjacent channel leakage interference according to at least one or a combination of the above embodiments. The UE capability report may include information indicating whether the measurement and reporting of subband adjacent channel leakage interference is possible, and information indicating the types of methods for measuring and reporting subband adjacent channel leakage interference that the UE can support.

[0619] In step 2725, the base station can refer to the UE capability report to create configuration information for the UE, including information related to frequency and time resources for measuring and reporting subband adjacent channel leakage interference, and send the configuration information for measuring and reporting subband adjacent channel leakage interference to the UE via higher-layer signaling and / or L1 signaling.

[0620] In step 2730, the base station may receive a subband adjacent channel leakage interference measurement report sent from the UE based on configuration information. In step 2735, the base station may send, for example, inter-base station information created based on the interference measurement report and / or configuration information as information related to the subband adjacent channel leakage interference measurement and reporting to another base station, or receive subband adjacent channel leakage interference configuration information and / or information related to the interference measurement report from another base station. Here, step 2735 is shown after step 2730, but the order is not limited to this.

[0621] Next, the hardware architecture used for XDD operations and the XDD bandwidth configuration using this hardware architecture are described.

[0622] Figure 28 This is a view illustrating an example of a base station implementation according to an embodiment of the present disclosure.

[0623] refer to Figure 28 The transmit (TX) baseband processor 2800 can output a digital signal generated through digital processing including modulation, and the digital-to-analog converter (DAC) 2805 can convert the digital signal into an analog signal. The analog signal can be amplified to a preset transmit power level by a power amplifier (PA) 2810, and the amplified signal can be transmitted to a bandpass (BP) filter 2820 via a distributor 2815, which can be configured as a duplexer, circulator, or switch. The signal filtered by the BP filter 2820 to minimize leakage to adjacent channels can be radiated through the transmit / receive antenna 2825.

[0624] When passing through the BP filter 2820, the analog received signal received by the transmit / receive antenna 2825 can be filtered to retain only the signal within the frequency band of interest. The output signal of the BP filter 2820 can be transmitted to the low-noise amplifier (LNA) 2830 via the distributor 2815. The LNA 2830 can amplify the transmitted signal to an appropriate level as the input to the analog-to-digital converter (ADC) 2835, and the ADC 2835 can convert the amplified signal into a digital signal and transmit it to the receiver (RX) baseband processor 2840. The RX baseband processor 2840 can perform digital processing, including demodulation, on the transmitted digital signal.

[0625] Figure 28 The base station implementation shown uses a BP filter 2820, and therefore can operate normally when the uplink and downlink transmission bands are equal or similar to each other.

[0626] Figure 29 This is a view illustrating another example of a base station implementation according to an embodiment of the present disclosure. In the illustrated embodiment, separate transmitting and receiving antennas may be introduced, and two different BP filters may be used for each antenna.

[0627] refer to Figure 29 The transmitting baseband processor 2900 can output a digital signal generated through digital processing including modulation, and the digital-to-analog converter (DAC) 2905 can convert the digital signal into an analog signal. This analog signal can be amplified to a preset transmit power level by a power amplifier (PA) 29-10, and the amplified signal can be transmitted to a transmit BP filter 2915. The signal, filtered by the BP filter 2915 configured with downlink bandwidth to minimize adjacent channel leakage, can be radiated through the transmit antenna 2920.

[0628] When the signal passes through the receiving BP filter 2930, the analog received signal received through the receiving antenna 2925 can be filtered to retain only the signal within the uplink band of interest. The output signal of the BP filter 2930 can be transmitted to the receiving LNA 2940 via the distributor 2935. The received signal, appropriately amplified by the LNA 2940, can be converted into a digital signal by the ADC 2945 and transmitted to the RX baseband processor 2950. The RX baseband processor 2950 can perform digital processing, including demodulation, on the received digital signal.

[0629] When measuring self-interference from the base station transmitter, the base station can control the distributor 2935 (or coupler) to transmit the signal from the transmit BP filter 2915 to the transmit antenna 2920 to the LNA 2940. The distributor 2935 can be configured as a duplexer, circulator, or switch. The self-interference signal, appropriately amplified by the LNA 2940, can be converted into a digital signal by the ADC 2945 and transmitted to the RX baseband processor 2950, ​​where adjacent channel leakage interference can be measured at the digital level.

[0630] Figure 29 The base station implementation uses two different BP filters, 2915 and 2930, so it can achieve excellent adjacent channel leakage suppression performance even when the uplink and downlink transmission frequency bands are different or the transmission bandwidths are significantly different.

[0631] During XDD operation, the uplink frequency band in different time slots can exhibit significant differences, such as... Figure 18 The example shown illustrates this. This means that efficient XDD operation may require one or more receive (or transmit) BP filters.

[0632] When the channel bandwidth of a TDD or XDD base station is B and the XDD UL transmission bandwidth is B_XDD, in addition to a BP filter configured with channel bandwidth B, the base station may include a BP filter that can be implemented in hardware or software, and the passband bandwidth B_F of the BP filter can be configured to satisfy the following equation.

[0633] XDD <= B_F << B

[0634] Here, a continuous frequency band with bandwidth B_F can exist within the channel bandwidth B, and the position of the frequency band B_F can be configured to remain unchanged within the frequency bandwidth B or to be changed semi-statically.

[0635] The frequency bandwidth of B_XDD can be composed of consecutive (multiple) PRBs within the bandwidth B_F, and the location can be dynamically or semi-statically configured to the UE by the base station's scheduling information or system information or its corresponding information.

[0636] Figure 30 This is a view illustrating another example of a base station implementation according to an embodiment of the present disclosure. In the illustrated implementation, a first receive BP filter 3030, which can be configured with a channel bandwidth B of the base station, and a second receive BP filter 3040, which can be configured with a passband bandwidth B_F including a transmission bandwidth B_XDD UL.

[0637] refer to Figure 30The transmitting baseband processor 3000 can transmit the digital signal generated by digital processing, including modulation, to the digital-to-analog converter (DAC) 3005. The DAC 3005 can convert the digital signal into an analog signal. The power amplifier (PA) 3010 can amplify the analog signal to a preset transmit power level and can transmit the amplified signal to the transmit BP filter 3015. The BP filter 3115, configured with downlink frequency bands, filters the signal to minimize adjacent channel leakage, which can be radiated through the transmit antenna 3020.

[0638] When the signal passes through the first receiving BP filter 3030, the analog received signal received through the receiving antenna 3025 can be filtered to retain only the signal within the uplink frequency band of interest. The output signal of the BP filter 3030 can be transmitted to the receiving LNA 3045 via the distributor 3035. The received signal, appropriately amplified by the LNA 3045, can be converted into a digital signal by the ADC 3050 and transmitted to the RX baseband processor 3055. The RX baseband processor 3055 performs digital processing, including demodulation, on the received digital signal.

[0639] When an uplink bandwidth change occurs due to XDD operation, the base station can control the distributor 3035 (which can be configured as a switch or coupler) to input the signal output from the first receive BF filter 3030 to a second receive BP filter 3040 configured with XDD UL or TDD DL bands. The output signal of the second receive BP filter 3040 can be transmitted to the LNA 3045. The interference signal, appropriately amplified by the LNA 3045, can be converted into a digital signal by the ADC 3050 and transmitted to the RX baseband processor 3055, where adjacent channel leakage interference can be measured at the digital level.

[0640] Figure 29 and 30 The BP filter shown can be replaced by a spatial filter for beamforming. When the frequency band supported by the XDD base station is very high (such as millimeter wave), the base station can be configured in essentially the same way using an XDD antenna module instead of a BP filter.

[0641] Figure 31 This is a view illustrating another example of a base station implementation according to an embodiment of the present disclosure. In the illustrated implementation, instead of including a BF filter, the transmit / receive antenna 3120 and the receive antenna 315 can be implemented as an antenna module with spatial filtering capabilities via beamforming.

[0642] refer to Figure 31The transmitting baseband processor 3100 can transmit the digital signal generated by digital processing including modulation to the DAC 3005, which can convert the digital signal into an analog signal. The PA 3110 can amplify the analog signal to a preset transmit power level, and the transmit / receive antenna 3120 can radiate the amplified signal through the distributor 3115.

[0643] In TDD UL operation, the analog received signal received via transmit / receive antenna 3120 can be transmitted to LNA 3135 via splitter 3115. The received signal, appropriately amplified by LNA 3135, can be converted into a digital signal via ADC 3140 and transmitted to RX baseband processor 3145. RX baseband processor 3145 performs digital processing on the received digital signal, such as demodulation.

[0644] The first antenna module 3120 can be used for DL / UL supporting TDD, and the second antenna module 3125 can be used only for XDD UL, in which case the first antenna module 3120 can be used for XDD DL. The first antenna module 3120 can be configured to have a pass bandwidth of channel bandwidth B, and the second antenna module 3125 can be configured to have a pass bandwidth of B_F (<= B).

[0645] The above embodiments and methods are not mutually exclusive and can be combined depending on the context. For example, when applying frequency hopping according to the second embodiment, one of the sub-band adjacent channel leakage interference measurement methods of the first embodiment can be used. Not all possible combinations are listed to avoid obscuring the essence of the embodiments.

[0646] Figure 32 This is a block diagram illustrating a UE according to an embodiment of the present disclosure.

[0647] refer to Figure 32 The UE may include a UE receiver 3200, a UE transmitter 3210, and a UE processor 3205. The transmitter 3210, receiver 3200, and processor 3205 may operate according to at least one or a combination of the above embodiments. The configuration of the UE is not limited to the examples shown, and the UE may add more components than described above or omit some components. Furthermore, in certain cases, the transmitter 3210, receiver 3200, and processor 3205 may be implemented as a single chip.

[0648] According to an embodiment, transmitter 3210 and receiver 3200 can be configured as transceivers. Transceivers 3200 and 3210 can transmit signals to and receive signals from a base station. These signals may include control information and data. For this purpose, transceivers 3200 and 3210 may include an RF transmitter for up-converting and amplifying the transmitted signals, and an RF receiver for low-noise amplification of the received signals and down-converting the received signals. Furthermore, transceivers 3200 and 3210 can receive signals via a radio channel, output signals to processor 3205, and transmit signals output from processor 3205 via a radio channel.

[0649] According to at least one of the above embodiments of this disclosure, the processor 3205 can control a series of operations of the UE. For example, according to at least one or a combination of embodiments of this disclosure, the processor 3205 can perform at least one of uplink channel / signal transmission, downlink channel / signal reception, and measurement and reporting of adjacent channel leakage interference. Furthermore, it may include a memory capable of storing control information or data, such as uplink-downlink configuration information and guard band configuration information included in signals obtained from the UE. The memory may have areas for storing data required for control by the processor 3205 and data generated during control by the controller 3205.

[0650] Figure 33 This is a block diagram illustrating a base station according to an embodiment of the present disclosure.

[0651] refer to Figure 33 The base station may include a base station transmitter 3310, a base station receiver 3300, and a base station processor 3305. The transmitter 3310, receiver 3300, and processor 3305 of the base station may operate according to at least one or a combination of the above embodiments. The configuration of the base station is not limited to the examples shown, and the base station may add more components than described above or omit some components. Furthermore, in certain cases, the transmitter 3310, receiver 3300, and processor 3305 may be implemented as a single chip.

[0652] According to an embodiment, transmitter 3310 and receiver 3300 can be configured as transceivers. Transceivers 3300 and 3310 can transmit signals to and receive signals from the UE. These signals may include control information and data. For this purpose, transceivers 3300 and 3310 may include an RF transmitter for up-converting and amplifying the transmitted signals, and an RF receiver for low-noise amplification of the received signals and down-converting the received signals. Furthermore, transceivers 3300 and 3310 can receive signals via a radio channel, output signals to processor 3305, and transmit signals output from processor 3305 via a radio channel. As an example, transceivers 3300 and 3310 may have the above-described... Figures 28 to 31 One of the realizations.

[0653] According to at least one of the above embodiments of this disclosure, processor 3305 can control a series of operations of the base station. For example, according to at least one or a combination of embodiments of this disclosure, processor 3305 can perform at least one of receiving uplink channels / signals, transmitting downlink channels / signals, and measuring and reporting adjacent channel leakage interference.

[0654] In addition, it may include a memory capable of storing control information or data, such as uplink-downlink configuration information and guard band configuration information determined by the base station, or control information or data received from the UE. The memory may have areas for storing data required for control by the processor 3305 and data generated during control by the controller 3305.

[0655] The embodiments provided herein are merely illustrative of this disclosure and should not be construed as limiting the invention. In other words, it will be apparent to those skilled in the art that various modifications can be made without departing from the scope of this disclosure. Furthermore, these embodiments can be implemented in combination.

Claims

1. A method performed by a user equipment (UE) configured to perform measurement and reporting of adjacent channel interference in a wireless communication system, the method comprising: Send UE capability reports to the base station related to the measurement and reporting of subband-specific adjacent channel leakage ACL interference; Receive configuration information of frequency and time resources from the base station indicating the measurement and reporting of subband-specific ACL interference; Based on the configuration information, measure specific ACL interference in the sub-band; as well as Report the measured subband-specific ACL interference to the base station.

2. The method according to claim 1, wherein the configuration information includes: The measurement configuration information indicates the time and frequency resources for measuring uplink ACL interference. as well as The report configuration information instructs the reporting of measurements of uplink ACL interference on at least one subband, and The measurement configuration information includes time and frequency resource information, which includes at least one of the following: sounding reference signal (SRS) resource, uplink rate matching resource, uplink orthogonal frequency division multiplexing (OFDM) symbol location, uplink time slot location, uplink physical resource block (PRB) or subband location, or uplink bandwidth portion (BWP).

3. The method according to claim 1, wherein the configuration information includes: The measurement configuration information indicates the time and frequency resources for measuring downlink ACL interference. as well as Report configuration information, which instructs the reporting of measurements of downlink ACL interference on at least one subband, and The measurement configuration information includes time and frequency resource information, which includes at least one of the following: Channel State Information (CSI) Reference Signal (RS) resource, Downlink Rate Matching Resource, Downlink Orthogonal Frequency Division Multiplexing (OFDM) symbol location, Downlink Physical Resource Block (PRB) or Subband location, or Downlink Bandwidth Portion (BWP).

4. The method according to claim 2 or 3, wherein the measurement configuration information includes information on frequency resources located at two opposite ends of the measurement frequency band of the UE.

5. The method according to claim 1, wherein the configuration information includes: The first transmit power information indicates that the UE uses a first transmit power on a first subband configured for ACL interference measurement and a second transmit power on a second subband configured for ACL interference measurement; as well as The second transmit power information indicates that the transmit power value obtained by interpolating the first transmit power and the second transmit power will be applied to subbands other than the first and second subbands of the measurement frequency band configured for the UE.

6. The method of claim 1, wherein the measured subband-specific ACL interference comprises at least one of the following: Detection Reference Signal (SRS) - Reference Signal Received Power (RSRP); Cross-link interference received signal strength indicator CLI-RSSI; Channel State Information RSRP (CSI-RSRP) CSI Reference Signal Received Quality (CSI-RSRQ); CSI signal-to-noise ratio (CSI-SINR); or Received Signal Strength Indicator (RSSI) 7. The method of claim 1, wherein the configuration information includes at least one of information indicating the measurement and reporting of adjacent channel leakage ACL interference and a measurement offset indicating the degree of timing mismatch between base stations at the sample level, symbol level, or time slot level.

8. A method performed by a base station configured to control the measurement and reporting of adjacent channel interference in a wireless communication system, the method comprising: Receive UE capability reports related to measurements and reports of subband-specific adjacent channel leakage ACL interference from the UE; Send configuration information of frequency and time resources to the UE, indicating the measurement and reporting of subband-specific ACL interference; as well as Based on the configuration information, a measurement report of subband-specific ACL interference is received from the UE.

9. The method according to claim 8, wherein the configuration information includes: The measurement configuration information indicates the time and frequency resources for measuring uplink ACL interference. as well as The report configuration information instructs the reporting of measurements of uplink ACL interference on at least one subband, and The measurement configuration information includes time and frequency resource information, which includes at least one of the following: sounding reference signal (SRS) resource, uplink rate matching resource, uplink orthogonal frequency division multiplexing (OFDM) symbol location, uplink time slot location, uplink physical resource block (PRB) or subband location, or uplink bandwidth portion (BWP).

10. The method according to claim 8, wherein the configuration information includes: The measurement configuration information indicates the time and frequency resources for measuring downlink ACL interference. as well as The report configuration information instructs the reporting of measurements of downlink ACL interference on at least one subband, and The measurement configuration information includes time and frequency resource information, which includes at least one of the following: Channel State Information (CSI) Reference Signal (RS) resource, Downlink Rate Matching Resource, Downlink Orthogonal Frequency Division Multiplexing (OFDM) symbol location, Downlink Physical Resource Block (PRB) or Subband location, or Downlink Bandwidth Portion (BWP).

11. The method according to claim 9 or 10, wherein the measurement configuration information includes information on frequency resources located at two opposite ends of the measurement frequency band of the UE.

12. An apparatus for a UE configured to perform measurement and reporting of adjacent channel interference in a wireless communication system, comprising: The transceiver is configured to send a UE capability report to the base station related to the measurement and reporting of subband-specific adjacent channel leakage ACL interference, and to receive configuration information from the base station indicating frequency and time resources for the measurement and reporting of subband-specific ACL interference. as well as The processor is configured to measure subband-specific ACL interference based on the configuration information and control the transceiver to report the measured subband-specific ACL interference to the base station.

13. An apparatus for a base station configured to control the measurement and reporting of adjacent channel interference in a wireless communication system, comprising: The transceiver is configured to receive UE capability reports related to the measurement and reporting of subband-specific adjacent channel leakage ACL interference from the UE, send configuration information to the UE indicating frequency and time resources for the measurement and reporting of subband-specific ACL interference, and receive measurement reports of subband-specific ACL interference from the UE based on the configuration information. as well as The processor is configured to send inter-base station shared information generated based on the configuration information and / or the measurement report to another base station.

Images