Method and apparatus for transmitting and receiving signal in communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate than a 4G communication system such as LTE. According to an embodiment, a method performed by a UE in a communication system may be provided. According to an embodiment, the method may comprise the steps of: receiving, through higher layer signaling, information related to candidate physical uplink control channel (PUCCH) resources in a first radio access technology (RAT); receiving downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) in a second RAT, the DCI including a bit field indicating a candidate PUCCH resource included in the candidate PUCCH resources; performing rate-matching applied to a resource element (RE) overlapping the candidate PUCCH resource from among REs included in the PUSCH; and transmitting the PUSCH to which the rate-matching is applied.

Description

Method and device for transmitting and receiving signals in a communication system

[0001] The present disclosure relates generally to a wireless communication system, and more particularly to a method for transmitting and receiving a signal in a communication system and a device supporting the same.

[0002] Looking back at the evolution of wireless communication over successive generations, technologies have primarily been developed for human-facing services such as voice, multimedia, and data. With the commercialization of 5G (5th-generation) communication systems, an explosive increase in connected devices is expected to be connected to communication networks. Examples of networked objects include vehicles, robots, drones, home appliances, displays, smart sensors installed in various infrastructures, construction equipment, and factory equipment. Mobile devices are also expected to evolve into diverse form factors, such as augmented reality glasses, virtual reality headsets, and holographic devices. In the 6th-generation (6G) era, efforts are being made to develop improved 6G communication systems to connect hundreds of billions of devices and objects and provide diverse services. For this reason, 6G communication systems are often referred to as "Beyond 5G" systems.

[0003] The 6G communication system, expected to be realized around 2030, will have a maximum transmission speed of terabytes per second (i.e., 1,000 gigabits per second) and a wireless latency of 100 microseconds (μsec). In other words, compared to 5G, the transmission speed in a 6G communication system will be 50 times faster, while the wireless latency will be reduced to one-tenth.

[0004] To achieve these high data rates and ultra-low latency, 6G communication systems are being considered for implementation in the terahertz band (e.g., from 95 gigahertz (GHz) to 3 terahertz (THz)). Compared to the millimeter wave (mmWave) band introduced in 5G, the terahertz band is expected to experience more severe path loss and atmospheric absorption, making it more crucial to ensure signal reach, or coverage, in this band. Key technologies to ensure coverage include radio frequency (RF) components, antennas, new waveforms that offer better coverage than orthogonal frequency division multiplexing (OFDM), beamforming, and multiple antenna transmission technologies such as massive multiple-input and multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas. In addition, new technologies such as metamaterial-based lenses and antennas, high-dimensional spatial multiplexing using orbital angular momentum (OAM), and reconfigurable intelligent surfaces (RIS) are being discussed to improve the coverage of terahertz band signals.

[0005] In addition, in order to improve frequency efficiency and system network, 6G communication systems are developing full duplex technology that utilizes the same frequency resources at the same time for uplink and downlink; network technology that integrates satellites and high-altitude platform stations (HAPS); network structure innovation technology that supports mobile base stations and enables optimization and automation of network operation; dynamic spectrum sharing technology through collision avoidance based on spectrum usage prediction; AI-based communication technology that utilizes artificial intelligence (AI) from the design stage and internalizes end-to-end AI support functions to realize system optimization; and next-generation distributed computing technology that realizes services with complexity that exceeds the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources (mobile edge computing (MEC), cloud, etc.). In addition, efforts are being made to further strengthen connectivity between devices, further optimize networks, promote softwareization of network entities, and increase the openness of wireless communications through the design of new protocols to be used in 6G communication systems, the implementation of hardware-based security environments, the development of mechanisms for the safe use of data, and the development of technologies for maintaining privacy.

[0006] Research and development of these 6G communication systems are expected to enable a new level of hyper-connected experience (the next hyper-connected experience) through the hyper-connectivity of 6G communication systems, which encompass not only connections between things but also connections between people and things. Specifically, 6G communication systems are expected to enable services such as truly immersive extended reality (XR), high-fidelity mobile holograms, and digital replicas. Furthermore, services such as remote surgery, industrial automation, and emergency response, which are provided through 6G communication systems through enhanced security and reliability, will be applied in diverse fields such as industry, medicine, automobiles, and home appliances.

[0007] Various embodiments of the present disclosure can provide a method for transmitting and receiving a signal in a communication system and a device supporting the same.

[0008] Various embodiments of the present disclosure may provide a rate matching and / or puncturing method for different radio access technologies (RATs) and / or inter-RATs in a communication system and a device supporting the same.

[0009] The technical problems to be achieved in various embodiments of the present disclosure are not limited to those mentioned above, and other technical problems not mentioned can be considered by a person having ordinary skill in the art from various embodiments of the present disclosure described below.

[0010] According to one embodiment, a method performed by a terminal in a communication system may be provided.

[0011] According to one embodiment, the method may include: receiving information related to candidate physical uplink control channel (PUCCH) resources in a first radio access technology (RAT) through upper layer signaling;

[0012] According to one embodiment, the method may include: receiving downlink control information (DCI) scheduling a physical uplink shared channel (PUSCH) in a second RAT.

[0013] According to one embodiment, the DCI may include a bit field indicating a candidate PUCCH resource included in the candidate PUCCH resources.

[0014] According to one embodiment, the method may include: performing rate-matching applied to an RE (resource element) included in the PUSCH that overlaps with the candidate PUCCH resource;

[0015] According to one embodiment, the method may include: transmitting a PUSCH to which the rate-matching is applied.

[0016] According to one embodiment, the number of bits in the bit field is is determined as a value satisfying , and L may be related to the number of candidate PUCCH resources.

[0017] According to one embodiment, the bit field may indicate a value corresponding to an index of the candidate PUCCH resource.

[0018] According to one embodiment, one bit of the bit field may indicate a value corresponding to a time domain location of the candidate PUCCH resource, and the remaining bits of the bit field excluding the one bit may indicate a value corresponding to a frequency domain location of the PUCCH resource.

[0019] According to one embodiment, when a MAC CE (medium access control control element) indicating an activated candidate PUCCH resource among the candidate PUCCH resources is received, the bit field is a first bitmap indicating the candidate PUCCH resource included in the activated candidate PUCCH resource, and the size of the first bitmap may be equal to the number of the activated candidate PUCCH resources.

[0020] According to one embodiment, when the MAC CE is not received, the bit field is a second bitmap indicating the candidate PUCCH resource included in the candidate PUCCH resources, and the size of the second bitmap may be equal to the number of the candidate PUCCH resources.

[0021] According to one embodiment, when the MAC CE is received, the activated candidate PUCCH resource may be applied after a slot offset from the slot in which the MAC CE is received.

[0022] According to one embodiment, the slot offset may be a predefined value or may be set via the upper layer signaling.

[0023] According to one embodiment, the information about the candidate PUCCH resources may include information related to a starting resource block (RB) index in the frequency domain of the candidate PUCCH resources and information related to the number of the candidate PUCCH resources.

[0024] According to one embodiment, based on information related to the start RB index and information related to the number of candidate PUCCH resources being received through the higher layer signaling, the DCI may further include an indicator of whether the bit field is included in the DCI.

[0025] According to one embodiment, if the bit fields are all set to '1' or all set to '0', the rate-matching may not be performed.

[0026] According to one embodiment, when the RE to which the rate-matching is applied corresponds to symbols included in a first half-slot of a slot for the PUSCH, and a DM-RS (demodulation reference signal) for the PUSCH is set to one of the symbols included in the first half-slot of the slot for the PUSCH: within an RB corresponding to the candidate PUCCH resource, REs corresponding to all symbols of the slot for the PUSCH may be rate-matched, or the DM-RS may be transmitted in one of the symbols included in a second half-slot of the slot for the PUSCH.

[0027] According to one embodiment, when a DM-RS for the PUSCH is set to a first symbol of one of the symbols included in a first half-slot of a slot for the PUSCH and a second symbol of one of the symbols included in a second half-slot of a slot for the PUSCH: when the RE to which the rate-matching is applied corresponds to symbols included in the first half-slot, the DM-RS set to the first symbol may not be transmitted and the DM-RS set to the second symbol may be transmitted, and when the RE to which the rate-matching is applied corresponds to symbols included in the second half-slot, the DM-RS set to the first symbol may be transmitted and the DM-RS set to the second symbol may not be transmitted.

[0028] According to one embodiment, a terminal of a communication system may be provided.

[0029] According to one embodiment, the terminal may include a transceiver; and a processor connected to the transceiver.

[0030] According to one embodiment, the processor may be configured to: receive information related to candidate physical uplink control channel (PUCCH) resources in a first radio access technology (RAT) via upper layer signaling;

[0031] According to one embodiment, the processor may be configured to: receive downlink control information (DCI) scheduling a physical uplink shared channel (PUSCH) in a second RAT;

[0032] According to one embodiment, the processor may be configured such that: the DCI includes a bit field indicating a candidate PUCCH resource included in the candidate PUCCH resources;

[0033] According to one embodiment, the processor may be configured to: perform rate-matching applied to an RE (resource element) included in the PUSCH that overlaps with the candidate PUCCH resource.

[0034] According to one embodiment, the processor may be configured to: transmit a PUSCH to which the rate-matching is applied;

[0035] According to one embodiment, a method performed by a base station in a communication system may be provided.

[0036] According to one embodiment, the method may include the step of transmitting information related to candidate physical uplink control channel (PUCCH) resources in a first radio access technology (RAT) via upper layer signaling.

[0037] According to one embodiment, the method may include transmitting downlink control information (DCI) scheduling a physical uplink shared channel (PUSCH) in a second RAT.

[0038] According to one embodiment, the DCI may include a bit field indicating a candidate PUCCH resource included in the candidate PUCCH resources.

[0039] According to one embodiment, the method may include receiving the PUSCH.

[0040] According to one embodiment, rate-matching may be applied to REs (resource elements) included in the PUSCH that overlap with the candidate PUCCH resource.

[0041] According to one embodiment, a base station of a communication system may be provided.

[0042] According to one embodiment, the base station may include a transceiver; and a processor connected to the transceiver.

[0043] According to one embodiment, the processor may be configured to: transmit information related to candidate physical uplink control channel (PUCCH) resources in a first radio access technology (RAT) via upper layer signaling.

[0044] According to one embodiment, the processor may be configured to: transmit downlink control information (DCI) scheduling a physical uplink shared channel (PUSCH) in a second RAT;

[0045] According to one embodiment, the DCI may include a bit field indicating a candidate PUCCH resource included in the candidate PUCCH resources.

[0046] According to one embodiment, the processor may be configured to: receive the PUSCH;

[0047] According to one embodiment, rate-matching may be applied to REs (resource elements) included in the PUSCH that overlap with the candidate PUCCH resource.

[0048] The various embodiments of the present disclosure described above are only some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the various embodiments of the present disclosure can be derived and understood by a person having ordinary skill in the art based on the detailed description to be described below.

[0049] Various embodiments of the present disclosure can provide a method for transmitting and receiving a signal in a communication system and a device supporting the same.

[0050] Various embodiments of the present disclosure may provide a rate matching and / or puncturing method for different radio access technologies (RATs) and / or inter-RATs in a communication system and a device supporting the same.

[0051] Various embodiments of the present disclosure can provide a method for indicating a rate matching pattern for PUCCH resources with low overhead and a device supporting the same.

[0052] Various embodiments of the present disclosure can minimize uplink resource waste.

[0053] Various embodiments of the present disclosure can maximize uplink throughput in spectrum sharing situations.

[0054] The effects that can be obtained from various embodiments of the present disclosure are not limited to the effects mentioned above, and other effects not mentioned can be clearly derived and understood by a person skilled in the art based on the detailed description below.

[0055] The accompanying drawings are intended to aid in understanding various embodiments of the present disclosure, and provide various embodiments of the present disclosure together with detailed descriptions. However, the technical features of the various embodiments of the present disclosure are not limited to specific drawings, and the features disclosed in each drawing may be combined with each other to form new embodiments. Reference numerals in each drawing represent structural elements.

[0056] FIG. 1 is a diagram illustrating a basic structure of a time-frequency domain in a wireless communication system according to one embodiment of the present disclosure.

[0057] FIG. 2 is a diagram illustrating a frame, subframe, and slot structure in a wireless communication system according to one embodiment of the present disclosure.

[0058] FIG. 3 is a diagram illustrating an example of bandwidth portion settings in a wireless communication system according to one embodiment of the present disclosure.

[0059] FIG. 4 is a diagram illustrating a wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, and dual connectivity situation in a wireless communication system according to one embodiment of the present disclosure.

[0060] FIG. 5 is a diagram for explaining a method for a base station and a terminal to transmit and receive data in consideration of a downlink data channel and rate matching resources in a wireless communication system according to one embodiment of the present disclosure.

[0061] FIG. 6 is a diagram illustrating an example of setting a control region of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0062] Figure 7 is a diagram showing an example of a basic unit of time and frequency resources that constitute a downlink control channel that can be used in 5G.

[0063] FIG. 8 is a diagram illustrating an example of frequency axis resource allocation of PDSCH or PUSCH in a wireless communication system according to one embodiment of the present disclosure.

[0064] FIG. 9 is a diagram illustrating a VRB-PRB interleaving method of PDSCH in FDRA type-1 resource allocation according to one embodiment of the present disclosure.

[0065] FIG. 10 is a diagram illustrating an example of time axis resource allocation of PDSCH in a wireless communication system according to one embodiment of the present disclosure.

[0066] FIG. 11 is a diagram illustrating an example of an LTE / NR DSS scenario to which one embodiment of the present disclosure is applicable.

[0067] FIG. 12 is a diagram showing an example of LTE PUCCH allocation to which one embodiment of the present disclosure is applicable.

[0068] FIG. 13 is a diagram illustrating an example of an LTE / NR DSS scenario to which one embodiment of the present disclosure is applicable.

[0069] FIG. 14 is a diagram illustrating an example of an LTE / NR DSS scenario to which one embodiment of the present disclosure is applicable.

[0070] FIG. 15 illustrates an example of a rate matching method in a communication system to which one embodiment of the present disclosure is applicable.

[0071] FIG. 16 is a diagram illustrating an example of a signaling procedure between a terminal and a base station according to one embodiment of the present disclosure.

[0072] FIG. 17 is a diagram illustrating an example of RRC parameters according to one embodiment of the present disclosure.

[0073] FIG. 18 is a diagram illustrating an example of a bit field in DCI according to one embodiment of the present disclosure.

[0074] FIG. 19 is a diagram illustrating an example of a relationship between a bitmap included in a MAC CE and a bitmap included in a DCI according to one embodiment of the present disclosure.

[0075] FIG. 20 is a diagram illustrating an example of a relationship between a bitmap included in a MAC CE and a bitmap included in a DCI according to one embodiment of the present disclosure.

[0076] FIG. 21 is a diagram for explaining a DM-RS applicable to PUSCH transmission according to one embodiment of the present disclosure.

[0077] FIG. 22 is a diagram for explaining a DM-RS applicable to PUSCH transmission according to one embodiment of the present disclosure.

[0078] FIG. 23 is a diagram for explaining a DM-RS applicable to PUSCH transmission according to one embodiment of the present disclosure.

[0079] FIG. 24 is a diagram for explaining a DM-RS applicable to PUSCH transmission according to one embodiment of the present disclosure.

[0080] FIG. 25 is a drawing showing an example of a terminal operation flow chart according to one embodiment of the present disclosure.

[0081] FIG. 26 is a drawing showing an example of an operation flow chart of a base station according to one embodiment of the present disclosure.

[0082] FIG. 27 is a diagram illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0083] FIG. 28 is a diagram illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

[0084] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0085] In describing the embodiments, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to avoid obscuring the gist of the present disclosure by omitting unnecessary explanations and to convey the gist more clearly.

[0086] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0087] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification. In addition, when describing the present disclosure, if a specific description of a related function or configuration is determined to unnecessarily obscure the gist of the present disclosure, the detailed description thereof will be omitted. In addition, the terms described below are terms defined in consideration of the functions of the present disclosure, and these may vary depending on the intention or custom of the user or operator. Therefore, their definitions should be made based on the contents throughout the specification.

[0088] In this disclosure, although the embodiments are described using terms used in certain communication standards (e.g., long term evolution (LTE) and new radio (NR) defined by the 3rd generation partnership project (3GPP)), these are merely examples for illustrative purposes. The embodiments of the present disclosure can be easily modified and applied to other communication systems. That is, the present disclosure is not limited to 5G communication systems or LTE communication systems, and can also be applied to 6G and later communication systems.

[0089] Hereinafter, the base station is an entity that performs resource allocation of the terminal, and may be at least one of a gNode B, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, although the LTE or LTE-A system may be described below as an example, the embodiments of the present disclosure may also be applied to other communication systems having a similar technical background or channel type. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included here, and the 5G below may also be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems through some modifications within a scope that does not significantly deviate from the scope of the present disclosure, as judged by a person having skilled technical knowledge.

[0090] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0091] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0092] Here, the term '~ part' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ parts' may be combined into a smaller number of components and '~ parts' or further separated into additional components and '~ parts'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.

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

[0094] As a representative example of the above broadband wireless communication system, the LTE system adopts the OFDM (Orthogonal Frequency Division Multiplexing) method in the downlink (DL) and the SC-FDMA (Single Carrier Frequency Division Multiple Access) method in the uplink (UL). The uplink refers to a wireless link in which a terminal (User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (eNode B or base station (BS)), and the downlink refers to a wireless link in which a base station transmits data or control signals to a terminal. The above multiple access method can distinguish the data or control information of each user by allocating and operating the time-frequency resources for transmitting data or control information to each user so that they do not overlap, that is, so as to achieve orthogonality.

[0095] As a future communications system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0096] eMBB aims to provide data transmission rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to support a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. Furthermore, 5G communication systems must simultaneously provide the peak data rate and an increased user-perceived data rate for terminals. To meet these requirements, improvements in various transmission and reception technologies, including improved multi-input, multi-output (MIMO) transmission technology, are required. Furthermore, while LTE transmits signals using a maximum transmission bandwidth of 20 MHz in the 2 GHz band, 5G communication systems can meet the data transmission rates required by 5G communication systems by using a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz band.

[0097] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC requires supporting large-scale terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, terminals supporting mMTC are likely to be located in shadow areas, such as basements, beyond cell coverage due to the nature of the service, and thus may require broader coverage compared to other services provided by 5G communication systems. Terminals supporting mMTC must be inexpensive, and since frequent battery replacement is unlikely, they may require extremely long battery lifespans, such as 10 to 15 years.

[0098] Finally, URLLC refers to cellular-based wireless communication services used for specific mission-critical purposes. Examples include remote control of robots or machinery, industrial automation, unmanned aerial vehicles (UAVs), remote health care, and emergency alerts. Therefore, URLLC communications must offer extremely low latency and high reliability. For example, URLLC-enabled services must meet air interface latency requirements of less than 0.5 milliseconds and a packet error rate (PER) of 10-5 or lower. Therefore, for URLLC-enabled services, 5G systems must provide shorter Transmit Time Intervals (TTIs) than other services, while simultaneously allocating extensive resources in the frequency band to ensure communication link reliability.

[0099] The three 5G services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters can be used. Of course, 5G is not limited to the three services described above.

[0100] Hereinafter, a / b can be understood as at least one of a or b.

[0101] [NR time-frequency resources]

[0102] Below, the frame structure of the 5G system is described in more detail with reference to drawings.

[0103] Figure 1 is a diagram illustrating the basic structure of the time-frequency domain, which is a radio resource domain in which data or control channels are transmitted in a 5G system.

[0104] The horizontal axis of Figure 1 represents the time domain, and the vertical axis represents the frequency domain. The basic unit of resources in the time and frequency domains is a resource element (RE, 101), which can be defined as 1 OFDM symbol (102) on the time axis and 1 subcarrier (103) on the frequency axis. In the frequency domain (For example, 12) consecutive REs can constitute one resource block (RB, 104). One subframe (110) on the time axis can include multiple OFDM symbols (102). For example, the length of one subframe can be 1 ms.

[0105] FIG. 2 is a diagram illustrating a frame, subframe, and slot structure in a wireless communication system according to one embodiment of the present disclosure.

[0106] Figure 2 illustrates an example of a structure of a frame (Frame, 200), a subframe (Subframe, 201), and a slot (Slot, 202). One frame (200) can be defined as 10ms. One subframe (201) can be defined as 1ms, and therefore one frame (200) can be composed of a total of 10 subframes (201). One slot (202, 203) can be defined as 14 OFDM symbols (i.e., the number of symbols per slot ( ). 1 subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing. In an example of FIG. 2, the cases where the subcarrier spacing setting value μ = 0 (204) and μ = 1 (205) are illustrated. When μ = 0 (204), 1 subframe (201) may be composed of one slot (202), and when μ = 1 (205), 1 subframe (201) may be composed of two slots (203). That is, the number of slots per subframe ( ) may vary, and accordingly the number of slots per frame ( ) may vary. Depending on the subcarrier spacing setting μ and can be defined as [Table 1] below.

[0107] [Table 1]

[0108]

[0109] [Bandwidth Part (BWP)]

[0110] Next, the bandwidth part (BWP) setting in the 5G communication system will be explained in detail with reference to the drawing.

[0111] FIG. 3 is a diagram illustrating an example of bandwidth portion settings in a wireless communication system according to one embodiment of the present disclosure.

[0112] FIG. 3 shows an example in which the UE bandwidth (300) is set to two bandwidth portions, namely, bandwidth portion #1 (BWP#1) (301) and bandwidth portion #2 (BWP#2) (302). The base station can set one or more bandwidth portions to the UE, and can set the information in [Table 2] below for each bandwidth portion.

[0113] [Table 2]

[0114]

[0115] Of course, the above example is not limited, and in addition to the above configuration information, various parameters related to the bandwidth portion can be configured for the terminal. The above information can be transmitted from the base station to the terminal via upper layer signaling, for example, RRC (Radio Resource Control) signaling. At least one bandwidth portion among the configured one or more bandwidth portions can be activated. Whether or not the configured bandwidth portion is activated can be semi-statically transmitted from the base station to the terminal via RRC signaling or dynamically transmitted via DCI.

[0116] According to some embodiments, a terminal before RRC connection can be configured with an initial bandwidth portion (Initial BWP) for initial access from a base station through a Master Information Block (MIB). More specifically, the terminal can receive configuration information about a control resource set (CORESET) and a search space in which a PDCCH for receiving system information required for initial access (which may correspond to Remaining System Information (RMSI) or System Information Block 1 (SIB1)) and search space can be transmitted through the MIB during the initial access phase. The control space and search space configured by the MIB can each be regarded as identifier (ID) 0. The base station can notify the terminal of configuration information such as frequency allocation information, time allocation information, and numerology for control space #0 through the MIB. Additionally, the base station can notify the terminal of the monitoring cycle and monitoring occasion settings for control area #0, i.e., search space #0, via the MIB. The terminal can consider the frequency range set as control area #0 obtained from the MIB as the initial bandwidth portion for initial access. At this time, the identifier (ID) of the initial bandwidth portion can be considered as 0.

[0117] The settings for the bandwidth supported by the above 5G can be used for various purposes.

[0118] In some embodiments, when the bandwidth supported by a terminal is smaller than the system bandwidth, this can be supported through bandwidth portion configuration. For example, the base station can configure the bandwidth portion frequency location (configuration information 2) for the terminal, thereby allowing the terminal to transmit and receive data at a specific frequency location within the system bandwidth.

[0119] Additionally, in some embodiments, a base station may configure multiple bandwidth segments for a terminal to support different numerologies. For example, to support data transmission and reception using both 15 kHz and 30 kHz subcarrier spacing for a given terminal, two bandwidth segments may be configured with subcarrier spacings of 15 kHz and 30 kHz, respectively. The different bandwidth segments may be frequency-division multiplexed (FDM), and when data is to be transmitted and received using a specific subcarrier spacing, the bandwidth segment configured for that subcarrier spacing may be activated.

[0120] Furthermore, in some embodiments, the base station may configure bandwidth portions with different bandwidth sizes for the terminal for the purpose of reducing power consumption of the terminal. For example, if the terminal supports a very large bandwidth, for example, 100 MHz, and constantly transmits and receives data using that bandwidth, very large power consumption may occur. In particular, monitoring unnecessary downlink control channels using a large bandwidth of 100 MHz in a situation where there is no traffic may be very inefficient in terms of power consumption. To reduce power consumption of the terminal, the base station may configure a bandwidth portion with a relatively small bandwidth, for example, 20 MHz, for the terminal. In a situation where there is no traffic, the terminal can perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, it can transmit and receive data using the 100 MHz bandwidth portion according to the instructions of the base station.

[0121] In the method for setting the bandwidth portion, terminals prior to RRC connection (Connected) can receive configuration information for the initial bandwidth portion (Initial BWP) through the MIB during the initial access phase. More specifically, the terminal can receive a control region (i.e., CORESET) for a downlink control channel on which a DCI scheduling a System Information Block (SIB) can be transmitted from the MIB of the Physical Broadcast Channel (PBCH). The bandwidth of the control region set by the MIB can be regarded as the initial bandwidth portion, and the terminal can receive the Physical Downlink Shared Channel (PDSCH) on which the SIB is transmitted through the set initial bandwidth portion. In addition to receiving the SIB, the initial bandwidth portion can also be utilized for other system information (Other System Information (OSI), paging, and random access).

[0122] [Bandwidth Part (BWP) Change]

[0123] When one or more bandwidth part values ​​are set for a terminal, the base station can instruct the terminal to change (or switch, transition) the bandwidth part value using the bandwidth part indicator field in the DCI. For example, in FIG. 3, when the currently activated bandwidth part of the terminal is bandwidth part #1 (301), the base station can instruct the terminal to bandwidth part #2 (302) using the bandwidth part indicator in the DCI, and the terminal can perform a bandwidth part change to bandwidth part #2 (302) indicated by the bandwidth part indicator in the received DCI.

[0124] As mentioned above, since DCI-based bandwidth part changes can be indicated by DCI scheduling PDSCH or PUSCH, when a UE receives a bandwidth part change request, it must be able to seamlessly receive or transmit the PDSCH or PUSCH scheduled by the corresponding DCI in the changed bandwidth part. To this end, the standard stipulates requirements for the delay time (TBWP) required when changing the bandwidth part, which can be defined, for example, as shown in [Table 3] below.

[0125] [Table 3]

[0126]

[0127] The bandwidth-partial change delay time requirement supports Type 1 or Type 2 depending on the terminal's capability. The terminal can report the supported bandwidth-partial delay time type to the base station.

[0128] According to the requirement on the bandwidth part change delay time described above, when a terminal receives a DCI including a bandwidth part change indicator in slot n, the terminal can complete the change to the new bandwidth part indicated by the bandwidth part change indicator at a time no later than slot n + TBWP, and can perform transmission and reception for the data channel scheduled by the corresponding DCI in the changed new bandwidth part. When the base station wants to schedule a data channel in the new bandwidth part, the base station can determine the time domain resource allocation for the data channel by considering the bandwidth part change delay time (TBWP) of the terminal. That is, when the base station schedules a data channel in the new bandwidth part, the data channel can be scheduled after the bandwidth part change delay time in the method of determining the time domain resource allocation for the data channel. Accordingly, the terminal may not expect the DCI indicating the bandwidth part change to indicate a slot offset (K0 or K2) value smaller than the bandwidth part change delay time (TBWP).

[0129] If the terminal receives DCI (e.g., DCI format 1_1 or 0_1) indicating a bandwidth change, the terminal may not perform any transmission or reception during the time period from the third symbol of the slot in which the PDCCH including the DCI is received to the start point of the slot indicated by the slot offset (K0 or K2) value indicated by the time domain resource allocation indicator field in the DCI. For example, if the terminal receives DCI indicating a bandwidth change in slot n and the slot offset value indicated by the DCI is K, the terminal may not perform any transmission or reception from the third symbol of slot n to the symbol before slot n+K (i.e., the last symbol of slot n+K-1).

[0130] [CA / DC related]

[0131] FIG. 4 is a diagram illustrating a wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, and dual connectivity situation according to one embodiment of the present disclosure.

[0132] Referring to FIG. 4, the wireless protocol of the next-generation mobile communication system is composed of NR SDAP (Service Data Adaptation Protocol S25, S70), NR PDCP (Packet Data Convergence Protocol S30, S65), NR RLC (Radio Link Control S35, S60), and NR MAC (Medium Access Control S40, S55) in the terminal and NR base station, respectively.

[0133] Key features of NR SDAP (S25, S70) may include some of the following:

[0134] - Transfer of user plane data

[0135] - Mapping function between QoS flow and data bearer for both DL and UL

[0136] - Marking function of QoS flow ID for both uplink and downlink (marking QoS flow ID in both DL and UL packets)

[0137] - Ability to map reflective QoS flow to data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0138] For the above SDAP layer device, the terminal can be configured by an RRC message for each PDCP layer device, each bearer, or each logical channel, whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device, and when the SDAP header is configured, the terminal can instruct the NAS QoS reflection configuration 1-bit indicator (NAS reflective QoS) and the AS QoS reflection configuration 1-bit indicator (AS reflective QoS) of the SDAP header to update or reset the mapping information for the QoS flow and data bearer of the uplink and downlink. The SDAP header can include QoS flow ID information indicating QoS. The QoS information can be used as data processing priority, scheduling information, etc. to support a smooth service.

[0139] The main functions of NR PDCP (S30, S65) may include some of the following functions:

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

[0141] - User data transfer function

[0142] - In-sequence delivery of upper layer PDUs

[0143] - Out-of-sequence delivery of upper layer PDUs

[0144] - PDCP PDU reordering for reception

[0145] - Duplicate detection of lower layer SDUs

[0146] - Retransmission function (Retransmission of PDCP SDUs)

[0147] - Encryption and decryption functions (Ciphering and deciphering)

[0148] - Timer-based SDU discard in uplink.

[0149] The reordering function of the NR PDCP device above refers to a function of reordering PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number), and may include a function of transmitting data to an upper layer in the reordered order. Alternatively, the reordering function of the NR PDCP device may include a function of transmitting data directly without considering the order, a function of recording lost PDCP PDUs by reordering the order, a function of reporting a status of lost PDCP PDUs to the transmitting side, and a function of requesting retransmission of lost PDCP PDUs.

[0150] The main functions of NR RLC (S35, S60) may include some of the following functions:

[0151] - Data transfer function (Transfer of upper layer PDUs)

[0152] - In-sequence delivery of upper layer PDUs

[0153] - Out-of-sequence delivery of upper layer PDUs

[0154] - ARQ function (Error Correction through ARQ)

[0155] - Concatenation, segmentation and reassembly of RLC SDUs

[0156] - Re-segmentation of RLC data PDUs

[0157] - Reordering of RLC data PDUs

[0158] - Duplicate detection function

[0159] - Protocol error detection

[0160] - RLC SDU discard function

[0161] - RLC re-establishment function

[0162] In the above, the in-sequence delivery function of the NR RLC device refers to the function of sequentially delivering RLC SDUs received from a lower layer to an upper layer. The in-sequence delivery function of the NR RLC device may include a function of reassembling and delivering a single RLC SDU when it is received divided into multiple RLC SDUs, a function of rearranging received RLC PDUs based on the RLC SN (sequence number) or PDCP SN (sequence number), a function of recording lost RLC PDUs by rearranging the order, a function of reporting the status of lost RLC PDUs to the transmitting side, and a function of requesting retransmission of lost RLC PDUs. The in-sequence delivery function of an NR RLC device may include a function to sequentially deliver to the upper layer only the RLC SDUs up to the lost RLC SDU when there is a lost RLC SDU, or may include a function to sequentially deliver to the upper layer all RLC SDUs received before the timer starts if a predetermined timer has expired even if there is a lost RLC SDU. Alternatively, the in-sequence delivery function of an NR RLC device may include a function to sequentially deliver to the upper layer all RLC SDUs received up to the present if a predetermined timer has expired even if there is a lost RLC SDU.In addition, the RLC PDUs may be processed in the order in which they are received (in the order of arrival, regardless of the order of the sequence number) and delivered to the PDCP device out of order (out-of-sequence delivery). In the case of segments, the segments stored in the buffer or to be received later may be received, reconstructed into a complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include a concatenation function, and the function may be performed in the NR MAC layer or replaced with a multiplexing function of the NR MAC layer.

[0163] The out-of-sequence delivery function of the NR RLC device above refers to the function of directly delivering RLC SDUs received from a lower layer to an upper layer regardless of the order, and may include a function of reassembling and delivering RLC SDUs when one RLC SDU is received divided into multiple RLC SDUs, and may include a function of storing and arranging the RLC SN or PDCP SN of received RLC PDUs to record lost RLC PDUs.

[0164] NR MAC (S40, S55) can be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of NR MAC can include some of the following functions.

[0165] - Mapping function (Mapping between logical channels and transport channels)

[0166] - Multiplexing / demultiplexing of MAC SDUs

[0167] - Scheduling information reporting function

[0168] - HARQ function (Error correction through HARQ)

[0169] - Priority handling between logical channels of one UE

[0170] - Priority handling between UEs by means of dynamic scheduling

[0171] - MBMS service identification function

[0172] - Transport format selection function

[0173] - Padding function

[0174] The NR PHY layer (S45, S50) can perform operations such as channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it over a wireless channel, or demodulating and channel decoding OFDM symbols received over a wireless channel and transmitting them to a higher layer.

[0175] The above wireless protocol structure can have various detailed structures depending on the carrier (or cell) operation method. For example, when a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal use a protocol structure that has a single structure for each layer, such as S00. On the other hand, when a base station transmits data to a terminal based on CA (carrier aggregation) using multiple carriers in a single TRP, the base station and the terminal use a protocol structure that has a single structure up to RLC, but multiplexes the PHY layer through the MAC layer, such as S10. As another example, when a base station transmits data to a terminal based on DC (dual connectivity) using multiple carriers in multiple TRPs, the base station and the terminal use a protocol structure that has a single structure up to RLC, but multiplexes the PHY layer through the MAC layer, such as S20.

[0176] [Rate matching / Puncturing related]

[0177] Below, the rate matching operation and puncturing operation are described in detail.

[0178] When a time and frequency resource A, through which an arbitrary symbol sequence A is to be transmitted, overlaps with an arbitrary time and frequency resource B, a rate matching or puncturing operation may be considered for transmission and reception operations of channel A considering resource C, an area in which resources A and B overlap. The specific operations may follow the contents below.

[0179] Rate Matching Operation

[0180] - The base station can map and transmit channel A only for the remaining resource areas excluding resource C corresponding to the overlapping area with resource B among the entire resources A that want to transmit symbol sequence A to the terminal. For example, if symbol sequence A is composed 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 and transmit symbol sequence A to {resource #1, resource #2, resource #4}, which are the remaining resources among resource A excluding {resource #3} corresponding to resource C. As a result, the base station can map and transmit symbol sequences {symbol #1, symbol #2, symbol #3} to {resource #1, resource #2, resource #4}, respectively.

[0181] The terminal can determine resources A and B from scheduling information for symbol sequence A from the base station, and can thereby determine resource C, which is an area where resources A and B overlap. The terminal can receive symbol sequence A, assuming that symbol sequence A was mapped and transmitted in the remaining area of ​​the entire resource A except for resource C. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, and resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the terminal can receive symbol sequence A, assuming that it was sequentially mapped to {resource #1, resource #2, resource #4}, which are the remaining resources among resource A except for {resource #3}, which corresponds to resource C. As a result, the terminal can perform a series of subsequent reception operations, assuming that symbol sequences {symbol #1, symbol #2, symbol #3} were mapped and transmitted to {resource #1, resource #2, resource #4}, respectively.

[0182] Puncture action

[0183] If a base station wants to transmit symbol sequence A to a terminal, and there is a resource C corresponding to an area overlapping with resource B among all resources A, the base station maps symbol sequence A to the entire resource A, but does not perform transmission in the resource area corresponding to resource C, and can perform transmission only for the remaining resource areas of resource A excluding resource C. For example, if symbol sequence A is composed 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 symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} to resource A {resource #1, resource #2, resource #3, resource #4}, and transmit only the symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to the remaining resources {resource #1, resource #2, resource #4} excluding {resource #3} corresponding to resource C among resources A, and may not transmit {symbol #3} mapped to {resource #3} corresponding to resource C. As a result, the base station can transmit symbol sequences {symbol #1, symbol #2, symbol #4} by mapping them to {resource #1, resource #2, resource #4}, respectively.

[0184] The terminal can determine resources A and B from scheduling information for symbol sequence A from the base station, and can thereby determine resource C, which is an area where resources A and B overlap. The terminal can receive symbol sequence A assuming that symbol sequence A is mapped to the entire resource A, but is transmitted only in the remaining area of ​​resource area A excluding resource C. For example, if symbol sequence A is composed 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 terminal can assume that symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} is mapped to resource A {resource #1, resource #2, resource #3, resource #4} respectively, but {symbol #3} mapped to {resource #3} corresponding to resource C is not transmitted, and can receive it assuming that symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to {resource #1, resource #2, resource #4}, which are the remaining resources among resource A except {resource #3} corresponding to resource C, are mapped and transmitted. As a result, the terminal can assume that the symbol sequence {symbol #1, symbol #2, symbol #4} is transmitted by being mapped to {resource #1, resource #2, resource #4}, respectively, and perform a series of subsequent receiving operations.

[0185] Below, we describe a method for configuring rate-matching resources for the purpose of rate-matching in 5G communication systems. Rate-matching refers to adjusting the size of a signal based on the amount of resources available for transmission. For example, rate-matching a data channel may mean adjusting the size of data accordingly, without mapping the data channel to a specific time and frequency resource region.

[0186] Figure 5 is a diagram for explaining a method in which a base station and a terminal transmit and receive data by considering downlink data channels and rate matching resources.

[0187] FIG. 5 illustrates a downlink data channel (PDSCH) 501 and a rate matching resource (502). A base station can configure one or more rate matching resources (502) to a terminal through upper layer signaling (e.g., RRC signaling). Rate matching resource (502) configuration information may include time-domain resource allocation information (503), frequency-domain resource allocation information (504), and period information (505). In the following, the bitmap corresponding to the frequency-domain resource allocation information (504) is named “first bitmap,” the bitmap corresponding to the time-domain resource allocation information (503) is named “second bitmap,” and the bitmap corresponding to the period information (505) is named “third bitmap.” When all or part of the time and frequency resources of a scheduled data channel (501) overlap with the set rate matching resources (502), the base station can rate-match and transmit the data channel (5601) in the rate matching resource (502) portion, and the terminal can perform reception and decoding after assuming that the data channel (501) is rate-matched in the rate matching resource (502) portion.

[0188] The base station can dynamically notify the terminal via DCI whether to rate-match the data channel in the set rate-matching resource portion through additional configuration (corresponding to the “rate-matching indicator” in the aforementioned DCI format). Specifically, the base station can select some of the set rate-matching resources and group them into rate-matching resource groups, and can use a bitmap to indicate to the terminal via DCI whether the data channel for each rate-matching resource group is rate-matched. For example, if four rate-matching resources, RMR#1, RMR#2, RMR#3, and RMR#4, are set, the base station can set RMG#1={RMR#1, RMR#2}, RMG#2={RMR#3, RMR#4} as the rate-matching groups, and can use two bits in the DCI field to indicate to the terminal whether to rate-match in RMG#1 and RMG#2, respectively, using a bitmap. For example, if rate matching is required, it can be indicated as “1”, and if rate matching is not required, it can be indicated as “0”.

[0189] 5G supports granularity at the "RB symbol level" and "RE level" by setting the aforementioned rate matching resources on the terminal. More specifically, the following configuration method can be followed.

[0190] RB symbol level

[0191] A terminal can receive up to four RateMatchPatterns for each bandwidth section through upper layer signaling, and one RateMatchPattern can include the following contents.

[0192] - As a reserved resource within the bandwidth section, a resource in which the time and frequency resource domains of the reserved resource are set by combining a bitmap at the RB level and a bitmap at the symbol level along the frequency axis may be included. The reserved resource may span one or two slots. A time domain pattern (periodicityAndPattern) in which the time and frequency domains composed of each RB level and symbol level bitmap pair are repeated may additionally be set.

[0193] - It may include a time and frequency domain resource area set as a control resource set within the bandwidth section and a resource area corresponding to a time domain pattern set as a search space setting in which the resource area is repeated.

[0194] RE level

[0195] The terminal can be configured with the following contents through upper layer signaling.

[0196] - The configuration information (lte-CRS-ToMatchAround) for RE corresponding to the LTE CRS (Cell-specific Reference Signal or Common Reference Signal) pattern may include the number of LTE CRS ports (nrofCRS-Ports) and the LTE-CRS-vshift(s) value (v-shift), the location information (carrierFreqDL) of the center subcarrier of the LTE carrier from the reference frequency point (e.g., reference point A), the bandwidth size (carrierBandwidthDL) information of the LTE carrier, and the subframe configuration information (mbsfn-SubframConfigList) corresponding to the MBSFN (Multicast-broadcast single-frequency network). Based on the above-described information, the terminal can determine the location of the CRS within the NR slot corresponding to the LTE subframe.

[0197] - It may include configuration information for a set of resources corresponding to one or more ZP (Zero Power) CSI-RSs within the bandwidth section.

[0198] [Regarding LTE CRS rate match]

[0199] Next, the rate match process for the LTE CRS described above will be described in detail. In order to coexist between LTE (Long Term Evolution) and NR (New RAT) (LTE-NR Coexistence), NR provides a function to set a pattern of LTE's CRS (Cell Specific Reference Signal) to NR terminals. More specifically, the CRS pattern can be provided by RRC signaling including at least one parameter in the ServingCellConfig IE (Information Element) or ServingCellConfigCommon IE. Examples of the parameters can include lte-CRS-ToMatchAround, lte-CRS-PatternList1-r16, lte-CRS-PatternList2-r16, crs-RateMatch-PerCORESETPoolIndex-r16, etc.

[0200] In Rel-15 NR, the lte-CRS-ToMatchAround parameter provides a function that allows one CRS pattern to be set per serving cell. In Rel-16 NR, the function has been extended to allow multiple CRS patterns to be set per serving cell. More specifically, a single-TRP (transmission and reception point) configured terminal can have one CRS pattern set per LTE carrier, and a multi-TRP configured terminal can have two CRS patterns set per LTE carrier. For example, a single-TRP configured terminal can have up to three CRS patterns set per serving cell through the lte-CRS-PatternList1-r16 parameter. As another example, a multi-TRP configured terminal can have CRS set per TRP. That is, the CRS pattern for TRP1 can be set via the lte-CRS-PatternList1-r16 parameter, and the CRS pattern for TRP2 can be set via the lte-CRS-PatternList2-r16 parameter. Meanwhile, when two TRPs are set as above, whether both the CRS patterns of TRP1 and TRP2 or only the CRS pattern for one TRP is applied to a specific PDSCH (Physical Downlink Shared Channel) is determined via the crs-RateMatch-PerCORESETPoolIndex-r16 parameter. If the crs-RateMatch-PerCORESETPoolIndex-r16 parameter is set to enabled, only the CRS pattern of one TRP is applied, and in other cases, the CRS patterns of both TRPs are applied.

[0201] [Table 4] shows a ServingCellConfig IE including the above CRS pattern, and [Table 5] shows a RateMatchPatternLTE-CRS IE including at least one parameter for the CRS pattern.

[0202] [Table 4]

[0203]

[0204]

[0205]

[0206] [Table 5]

[0207]

[0208] [PDCCH: DCI related]

[0209] Next, we will specifically explain downlink control information (DCI) in 5G systems.

[0210] In a 5G system, scheduling information for uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) is transmitted from a base station to a terminal via DCI. The terminal can monitor a DCI format for fallback and a DCI format for non-fallback for the PUSCH or PDSCH. The fallback DCI format can be composed of fixed fields defined between the base station and the terminal, and the non-fallback DCI format can include configurable fields.

[0211] DCI can be transmitted through the Physical Downlink Control Channel (PDCCH) after going through the channel coding and modulation process. A Cyclic Redundancy Check (CRC) is attached to the DCI message payload, and the CRC can be scrambled with a Radio Network Temporary Identifier (RNTI) corresponding to the identity of the UE. Different RNTIs can be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control command, or random access response. That is, the RNTI is not transmitted explicitly, but is included in the CRC calculation process. When the UE receives a DCI message transmitted on the PDCCH, it verifies the CRC using the assigned RNTI. If the CRC verification result is correct, the UE can determine that the message was transmitted to the UE.

[0212] For example, a DCI scheduling a PDSCH for System Information (SI) may be scrambled with SI-RNTI. A DCI scheduling a PDSCH for a Random Access Response (RAR) message may be scrambled with RA-RNTI. A DCI scheduling a PDSCH for a Paging message may be scrambled with P-RNTI. A DCI notifying a Slot Format Indicator (SFI) may be scrambled with SFI-RNTI. A DCI notifying a Transmit Power Control (TPC) may be scrambled with TPC-RNTI. A DCI scheduling a UE-specific PDSCH or PUSCH may be scrambled with C-RNTI (Cell RNTI).

[0213] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI can include, for example, the information in [Table 6] below.

[0214] [Table 6]

[0215]

[0216] DCI format 0_1 ​​can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_1 ​​with the CRC scrambled with C-RNTI can include, for example, the information in [Table 7] below.

[0217] [Table 7]

[0218]

[0219]

[0220] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI can include, for example, the information in [Table 8] below.

[0221] [Table 8]

[0222]

[0223] DCI format 1_1 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI can include, for example, the information in [Table 9] below.

[0224] [Table 9]

[0225]

[0226] [PDCCH: CORESET, REG, CCE, Search Space]

[0227] Below, the downlink control channel in a 5G communication system will be described in more detail with reference to drawings.

[0228] FIG. 6 is a diagram illustrating an example of a control region (Control Resource Set, CORESET) in which a downlink control channel is transmitted in a 5G wireless communication system.

[0229] FIG. 6 illustrates an example in which two control regions (Control Region #1 (601), Control Region #2 (602)) are set within a UE bandwidth part (610) in the frequency axis and within one slot (620) in the time axis. The control regions (601, 602) can be set to specific frequency resources (603) within the entire UE bandwidth part (610) in the frequency axis. The time axis can be set to one or more OFDM symbols, which can be defined as the control region length (Control Resource Set Duration, 604). Referring to the example illustrated in FIG. 8, Control Region #1 (601) is set to a control region length of two symbols, and Control Region #2 (602) is set to a control region length of one symbol.

[0230] The control region in the aforementioned 5G can be established by the base station to the terminal via higher-layer signaling (e.g., system information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). Establishing a control region for the terminal means providing information such as the control region identifier, the frequency location of the control region, and the symbol length of the control region. For example, this information may include the information in [Table 10] below.

[0231] [Table 10]

[0232]

[0233]

[0234] In [Table 10], the tci-StatesPDCCH (simply named TCI (Transmission Configuration Indication) state) configuration information may include information on one or more SS (Synchronization Signal) / PBCH (Physical Broadcast Channel) block indices or CSI-RS (Channel State Information Reference Signal) indices that are in a QCL (Quasi Co Located) relationship with the DMRS transmitted in the corresponding control region.

[0235] FIG. 7 is a diagram showing an example of a basic unit of time and frequency resources that constitute a downlink control channel that can be used in 5G. According to FIG. 7, the basic unit of time and frequency resources that constitute a control channel can be referred to as a REG (Resource Element Group, 703), and a REG (703) can be defined as 1 OFDM symbol (701) on the time axis and 1 PRB (Physical Resource Block, 702) on the frequency axis, i.e., 12 subcarriers. A base station can concatenate REGs (703) to constitute a downlink control channel allocation unit.

[0236] As illustrated in FIG. 7, if the basic unit to which a downlink control channel is allocated in 5G is called a CCE (Control Channel Element, 704), 1 CCE (704) can be composed of multiple REGs (703). Taking the REG (703) illustrated in FIG. 7 as an example, the REG (703) can be composed of 12 REs, and if 1 CCE (704) is composed of 6 REGs (703), 1 CCE (704) can be composed of 72 REs. When a downlink control region is established, the region can be composed of multiple CCEs (704), and a specific downlink control channel can be mapped to one or multiple CCEs (704) and transmitted according to the aggregation level (AL) within the control region. CCEs (704) within the control area are distinguished by numbers, and the numbers of the CCEs (704) can be assigned according to a logical mapping method.

[0237] The basic unit of the downlink control channel illustrated in FIG. 7, that is, the REG (703), may include both the REs to which the DCI is mapped and the areas to which the DMRS (705), which is a reference signal for decoding the REs, is mapped. As shown in FIG. 7, three DMRSs (705) may be transmitted within one REG (703). The number of CCEs required to transmit the PDCCH may be 1, 2, 4, 8, or 16 depending on the aggregation level (AL), and different numbers of CCEs may be used to implement link adaptation of the downlink control channel. For example, when AL = L, one downlink control channel may be transmitted through L CCEs. The terminal must detect a signal without knowing information about the downlink control channel, and a search space representing a set of CCEs is defined for blind decoding. A search space is a set of downlink control channel candidates (CCEs) that a terminal must attempt to decode at a given aggregation level. Since there are multiple aggregation levels, each of which can be a set of 1, 2, 4, 8, or 16 CCEs, a terminal can have multiple search spaces. A search space set can be defined as the set of search spaces at all configured aggregation levels.

[0238] Search spaces can be categorized into common search spaces and UE-specific search spaces. A certain group of UEs, or all UEs, can search the common search space of the PDCCH to receive cell-common control information, such as dynamic scheduling of system information or paging messages. For example, PDSCH scheduling allocation information for transmitting SIBs, including cell operator information, can be received by searching the common search space of the PDCCH. In the case of the common search space, since a certain group of UEs, or all UEs, must receive the PDCCH, it can be defined as a set of pre-arranged CCEs. Scheduling allocation information for UE-specific PDSCH or PUSCH can be received by searching the UE-specific search space of the PDCCH. The UE-specific search space can be defined UE-specifically as a function of the UE's identity and various system parameters.

[0239] In 5G, parameters for the search space for PDCCH can be configured from the base station to the terminal through higher layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station can configure the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the monitoring occasion for each symbol within the slot for the search space, the search space type (common search space or terminal-specific search space), the combination of DCI format and RNTI to be monitored in the corresponding search space, the control region index to be monitored for the search space, etc. to the terminal. For example, the information in [Table 11] below can be included.

[0240] [Table 11]

[0241]

[0242]

[0243] Depending on the configuration information, the base station may configure one or more search space sets for the terminal. In some embodiments, the base station may configure search space set 1 and search space set 2 for the terminal, and may configure the terminal to monitor DCI format A scrambled with X-RNTI in search space set 1 in a common search space, and may configure the terminal to monitor DCI format B scrambled with Y-RNTI in search space set 2 in a terminal-specific search space.

[0244] According to the configuration information, one or more search space sets may exist in a common search space or a terminal-specific search space. For example, search space set #1 and search space set #2 may be configured as a common search space, and search space set #3 and search space set #4 may be configured as terminal-specific search spaces.

[0245] In the common search space, the following combinations of DCI formats and RNTIs can be monitored. Of course, the examples below are not limited to these.

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

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

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

[0249] - DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, TPC-PUCCH-RNTI

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

[0251] In a terminal-specific search space, the following combinations of DCI formats and RNTIs can be monitored. Of course, the examples below are not limited to these examples.

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

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

[0254] The RNTIs specified may follow the definitions and uses below.

[0255] C-RNTI (Cell RNTI): For terminal-specific PDSCH scheduling purposes

[0256] TC-RNTI (Temporary Cell RNTI): For terminal-specific PDSCH scheduling purposes

[0257] CS-RNTI (Configured Scheduling RNTI): Used for terminal-specific PDSCH scheduling that is set semi-statically.

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

[0259] P-RNTI (Paging RNTI): Used for scheduling PDSCH where paging is transmitted.

[0260] SI-RNTI (System Information RNTI): Used for scheduling PDSCH where system information is transmitted.

[0261] INT-RNTI (Interruption RNTI): Used to indicate whether pucturing is in progress for PDSCH.

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

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

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

[0265] The aforementioned specified DCI formats may follow the definitions in [Table 12] below.

[0266] [Table 12]

[0267]

[0268] In 5G, the search space of aggregation level L in the control region p and search space set s can be expressed as in [Mathematical Formula 1] below.

[0269] [Mathematical Formula 1]

[0270]

[0271] - :Integration level

[0272] - : Carrier Index

[0273] - : Total number of CCEs existing within the control region p

[0274] - : slot index

[0275] - : Number of PDCCH candidates for aggregation level L

[0276] - : PDCCH candidate index of aggregation level L

[0277] -

[0278] -

[0279] - : Terminal identifier

[0280] - The value can be 0 for a common search space.

[0281] In the case of a terminal-specific search space, the value may correspond to a value that changes depending on the terminal's identity (C-RNTI or ID set to the terminal by the base station) and the time index.

[0282] In 5G, since multiple search space sets can be configured with different parameters (e.g., parameters in [Table 11]), the set of search space sets monitored by a terminal at each point in time can be different. For example, if search space set #1 is configured with an X-slot period and search space set #2 is configured with a Y-slot period and X and Y are different, the terminal can monitor both search space set #1 and search space set #2 in a specific slot, or can monitor either search space set #1 or search space set #2 in a specific slot.

[0283] [PDSCH / PUSCH: Frequency Resource Allocation Related]

[0284] Next, we describe the frequency domain resource assignment (FDRA) for the Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) in NR.

[0285] FIG. 8 is a diagram illustrating an example of frequency axis resource allocation of PDSCH or PUSCH in a wireless communication system according to one embodiment of the present disclosure.

[0286] FIG. 8 is a diagram illustrating three frequency axis resource allocation methods, FDRA type 0 (800), FDRA type 1 (805), and dynamic switch (810), which can be set through an upper layer in an NR wireless communication system.

[0287] Referring to FIG. 8, if the terminal is configured to use only FDRA type 0 through upper layer signaling (800), some downlink control information (DCI) for scheduling PDSCH or PUSCH to the terminal is N RBG It contains a bitmap consisting of N bits. The conditions for this will be explained later. At this time, N RBG refers to the number of RBGs (resource block groups) determined according to the size of the bandwidth portion allocated by the bandwidth portion indicator and the upper layer parameter rbg-Size as shown in [Table 13] below, and data is transmitted to the RBG indicated as 1 by the bitmap.

[0288] [Table 13]

[0289]

[0290] The size of the frequency resource in the bandwidth part can be defined as the number of RBs included in the bandwidth part. More specifically, if the terminal is instructed to allocate FDRA type-0 resources, the length of the FDRA field of the DCI received by the terminal is equal to the number of RBGs (NRBGs) in the bandwidth part. Here, the first RBG within the bandwidth section is It contains RBs of the dog, and the last RBG within the bandwidth part is On the other hand, Contains the RBs of the dog, otherwise, It contains P RBs. The remaining RBGs within the bandwidth portion contain P RBs, where P is the number of nominal RBGs determined according to [Table 13] above.

[0291] If the terminal is configured to use only FDRA type 1 through upper layer signaling (805), the DCI that allocates PDSCH or PUSCH to the terminal is It contains frequency domain resource allocation information (FDRA) consisting of bits. Here, is the number of RBs included in the bandwidth portion. Through this, the base station can set the starting VRB (820) and the length of frequency axis resources (825) allocated continuously therefrom.

[0292] If a terminal is configured to use both FDRA type-0 resource allocation and FDRA type-1 resource allocation through upper layer signaling (810), some DCIs that allocate PDSCH / PUSCH to the terminal include frequency-axis resource allocation information composed of bits of the larger value (1835) among the payload (815) for configuring FDRA type-0 resource allocation and the payload (820, 1025) for configuring FDRA type-1 resource allocation. The conditions for this will be explained later. At this time, one bit may be added to the first part (MSB) of the frequency-axis resource allocation information in the DCI, and if the bit has a value of '0', it may indicate that FDRA type-0 resource allocation is used, and if the bit has a value of '1', it may indicate that FDRA type-1 resource allocation is used.

[0293] If the terminal has been set to the FDRA type-2 resource allocation method through upper layer signaling, the terminal can be instructed by the base station about the FDRA type-2 resource allocation method according to the following method.

[0294] If the terminal does not receive the upper layer signaling vrb-ToPRB-Interleaver, the terminal can connect the resources allocated to the VRB to the PRB without interleaving. If the terminal receives the upper layer signaling vrb-ToPRB-Interleaver, the upper layer signaling has a value of 2 or 4, and this value can be the unit of multiple RBs that perform interleaving. In other words, RB bundles of 2 or 4 units can be used for interleaving.

[0295] If the terminal Starting from the position and length The i-th BWP consisting of RBs is set, and the vrb-ToPRB-Interleaver is If set to , the terminal will set the i-th BWP It can be divided into RB bundles, and each RB bundle is It can be made up of RBs.

[0296] - In the i-th BWP, the first RB bundle is It can be made up of RBs.

[0297] - In the i-th BWP, the last RB bundle is if If the value is greater than 0 It can be made up of RBs of dogs, and if not It can be made up of RBs.

[0298] - In the i-th BWP, the remaining RB bundles are It can be made up of RBs.

[0299] At this time, VRB can be connected to PRB according to the following method.

[0300] - The last VRB bundle can be connected to the last PRB bundle.

[0301] - jth VRB bundle is can be connected to the th PRB bundle, can be expressed as in [Mathematical Formula 2] below.

[0302] [Equation 2]

[0303]

[0304] FIG. 9 is a diagram illustrating a VRB-PRB interleaving method of PDSCH in FDRA type-1 resource allocation according to an embodiment of the present disclosure. In FIG. 9, the first and last VRB bundles (900) in a BWP consisting of 10 RBs are represented as (910) consisting of 1 VRB. Therefore, the number of VRB bundles can be 6, and by the above [Mathematical Formula 2] can be calculated as follows. Therefore, since the jth VRB bundle can be connected to the f(j)th PRB bundle by the above [Mathematical Formula 2], the connection from the VRB bundle to the PRB bundle can be performed as in (920) through the result (930) calculated by the above [Mathematical Formula 2]. For example, VRB bundle 1 (940) can be connected to PRB bundle 3 (950).

[0305] The terminal can receive RB allocation information from the base station, which is a set of M interlace indices.

[0306] Interlace Index Silver common RB It can be composed of fields, and M can be defined as in [Table 14].

[0307] [Table 14]

[0308]

[0309] RB in interlace m and bandwidth part i and common RB The relationship with can be defined as follows:

[0310]

[0311] When the subcarrier spacing is 15 kHz (u=0), RB allocation information for an interlace set with m0 + l indices can be notified from the base station to the terminal. In addition, the resource allocation field can be configured with a Resource Indication Value (RIV). The Resource Indication Value When the starting interlace m0 and the number of consecutive interlaces It can be composed of , and its values ​​are as follows:

[0312]

[0313] The resource indicator value is When this happens, the resource indicator value is composed of the start interlace index m0 and l values ​​and can be configured as in [Table 15].

[0314] [Table 15]

[0315]

[0316] When the subcarrier spacing is 30 kHz (u=1), RB allocation information can be notified from the base station to the terminal in the form of a bitmap indicating the interlaces allocated to the terminal. The size of the bitmap is M, and each bit in the bitmap corresponds to an interlace. The order of the interlace bitmap can be mapped from the MSB to the LSB, from interlace index 0 to M-1.

[0317] Also, the least significant bit (LSB) of the FDRA field for 15 kHz and 30 kHz may mean a set of consecutive RBs of PUSCH scheduled with DCI format 0_1. The Y bit may be configured as a resource indication value (RIVRBset). In RIVRBset the value is the starting RB set ( ) and the number of consecutive RB sets ( ) can be determined. The RIVRBset value can be defined as follows.

[0318]

[0319] It refers to the number of RB sets included in the bandwidth portion, and can be determined by the number of guard gaps (or bands) within the carrier set by upper signaling (or preset).

[0320] [PDSCH / PUSCH: Time Resource Allocation Related]

[0321] Below, a time domain resource allocation method for data channels in next-generation mobile communication systems (5G or NR systems) is described.

[0322] A base station can set up a table for time domain resource allocation information for a downlink data channel (PDSCH) and an uplink data channel (PUSCH) to a terminal via higher layer signaling (e.g., RRC signaling). A table with up to maxNrofDL-Allocations=16 entries can be set up for the PDSCH, and a table with up to maxNrofUL-Allocations=16 entries can be set up for the PUSCH. In one embodiment, the time domain resource allocation information may include PDCCH-to-PDSCH slot timing (corresponding to the time interval in slot units between the time point at which a PDCCH is received and the time point at which a PDSCH scheduled by the received PDCCH is transmitted, denoted as K0), PDCCH-to-PUSCH slot timing (corresponding to the time interval in slot units between the time point at which a PDCCH is received and the time point at which a PUSCH scheduled by the received PDCCH is transmitted, denoted as K2), information on the position and length of the start symbol for which a PDSCH or PUSCH is scheduled within a slot, a mapping type of the PDSCH or PUSCH, etc. For example, information such as [Table 16] or [Table 17] below may be transmitted from the base station to the terminal.

[0323] [Table 16]

[0324]

[0325] [Table 17]

[0326]

[0327] The base station may notify the terminal of one of the entries in the table for the time domain resource allocation information described above via L1 signaling (e.g., DCI) (e.g., indicated by the 'Time Domain Resource Allocation' field in the DCI). The terminal may obtain the time domain resource allocation information for the PDSCH or PUSCH based on the DCI received from the base station.

[0328] FIG. 10 is a diagram illustrating an example of time axis resource allocation of PDSCH in a wireless communication system according to an embodiment of the present disclosure.

[0329] Referring to FIG. 10, the base station can indicate the time axis position of the PDSCH resource according to the subcarrier spacing (SCS) (μPDSCH, μPDCCH) of the data channel and control channel set using the upper layer, the scheduling offset (K0) value, and the start position (1000) and length (1005) of an OFDM symbol within a slot dynamically indicated through DCI.

[0330] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. The contents of the present disclosure can be applied to FDD, TDD and / or XDD (and / or SBFD, full duplex) systems. In the present disclosure below, upper signaling (or upper layer signaling) refers to a signal transmission method in which a base station transmits a signal to a terminal using a downlink data channel of a physical layer, or a terminal transmits a signal to a base station using an uplink data channel of a physical layer, and may also be referred to as RRC signaling, PDCP signaling, or MAC (medium access control) control element (MAC control element; MAC CE).

[0331] Hereinafter, the base station is an entity that performs resource allocation of the terminal, and may be at least one of a gNode B, a gNB, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. Hereinafter, the embodiments of the present disclosure will be described using a 5G system as an example, but the embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel type. For example, LTE or LTE-A mobile communication and mobile communication technologies developed after 5G may be included here. Therefore, the embodiments of the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure as determined by a person skilled in the art. The contents of the present disclosure can be applied to FDD, TDD, XDD (or SBFD, full duplex) systems.

[0332] Additionally, when describing the present disclosure, detailed descriptions of related functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the contents of this specification.

[0333] In the following description of the present disclosure, upper layer signaling may be signaling corresponding to at least one or a combination of one or more of the following signaling.

[0334] - MIB (Master Information Block)

[0335] - SIB (System Information Block) or SIB

[0336] - RRC (Radio Resource Control)

[0337] - MAC (Medium Access Control) CE (Control Element)

[0338] In addition, L1 signaling may be signaling corresponding to at least one or a combination of one or more signaling methods using the following physical layer channels or signaling.

[0339] - PDCCH (Physical Downlink Control Channel)

[0340] - DCI (Downlink Control Information)

[0341] - UE-specific DCI

[0342] - Group common DCI

[0343] - Common DCI

[0344] - Scheduling DCI (e.g. DCI used for scheduling downlink or uplink data)

[0345] - Non-scheduled DCI (e.g. DCI not intended for scheduling downlink or uplink data)

[0346] - PUCCH (Physical Uplink Control Channel)

[0347] - UCI (Uplink Control Information)

[0348] The term "slot" used in the present disclosure below is a general term that can refer to a specific time unit corresponding to a Transmit Time Interval (TTI). Specifically, it can refer to a slot used in a 5G NR system, a slot or subframe used in a 4G LTE system, or a time resource unit used in a 6G system.

[0349] In the following description of the present disclosure, rate matching is used as an example. However, this is only an example of freeing up certain resources to prevent overlapping resources when a specific RAT uses the same frequency band as another RAT, and is not limited to rate matching. For example, puncturing may be used.

[0350] Unless otherwise specifically stated herein, in the description of the present disclosure, it may be understood that instructing rate matching, instructing a rate matching pattern, setting rate matching, etc. are the same.

[0351] In the following description of the present disclosure, for the sake of convenience, the case where the first RAT (radio access technology) and the second RAT collide / overlap is taken as an example, and the case where 5G and LTE collide / overlap are explained, but the present disclosure is not limited thereto. For example, the present disclosure may also be applied to the case where 6G and 5G collide / overlap, the case where 6G and LTE collide / overlap, the case where a RAT after 6G collides / overlaps with a RAT before 6G, etc., but is not limited thereto. In the following description of the present disclosure, candidate LTE PUCCH resources may be replaced with candidate PUCCH resources.

[0352] In the present disclosure below, the above examples are described through a number of embodiments, but they are not independent and one or more embodiments may be applied simultaneously or in combination.

[0353] Spectrum sharing technologies may be crucial in 6G systems. These technologies may include, but are not limited to, technologies that allow multi-RAT coexistence in the same frequency band, such as dynamic spectrum sharing (DSS) or multi-radio access technology (RAT) spectrum sharing (MRSS). Spectrum sharing technologies are important in 6G systems for the following reasons.

[0354] 1) Scarcity of spectrum for 6G

[0355] New frequency bands may be introduced for 6G systems. Furthermore, 6G systems can utilize existing frequency bands. For example, 6G systems can efficiently utilize existing low-band spectrum to provide wide-area coverage. Since existing frequency bands are already in use by existing users, such as LTE / 5G communication systems, spectrum sharing technologies such as DSS and MRSS may be required for 6G systems to effectively utilize these bands.

[0356] 2) SA (Enabling Standard Alone) architecture

[0357] In the early stages of 5G, the RAN (radio access network) was operated in a Non-Standard Alone (NSA) configuration, resulting in limited 5G functionality, complex development, and increased operational burden. Accordingly, 6G systems are expected to initially operate with an SA architecture, which may require spectrum sharing technologies such as DSS and MRSS. For example, spectrum sharing technologies could be key to supporting smooth network migration and multi-RAT connectivity.

[0358] To apply spectrum sharing technologies such as DSS and MRSS, resource conflicts and / or spectrum collisions due to resource use must not occur between RATs (hereinafter, “Inter-RAT”). Rate-matching or puncturing functions may be supported to prevent resource conflicts and / or spectrum collisions.

[0359] FIG. 11 is a diagram illustrating an example of an LTE / NR DSS scenario to which an embodiment of the present disclosure is applicable. FIG. 11 illustrates an example of a case where DSS is applied between LTE and NR, but the present disclosure is not limited thereto.

[0360] FIG. 12 is a diagram showing an example of LTE PUCCH allocation to which one embodiment of the present disclosure is applicable.

[0361] Referring to Fig. 11, the PUCCH of LTE / NR can be located at both ends of the bandwidth, and the positions of the LTE PUCCH and NR PUCCH can be interchanged. Outside the portion of the bandwidth where the LTE PUCCH and NR PUCCH are mapped / allocated, the LTE PUSCH (LTE PUSCH only), NR PUSCH (NR PUSCH only), and / or the LTE PUSCH and NR PUSCH (LTE / NR PUSCH FDM) can be mapped / allocated. That is, spectrum sharing can be applied between LTE and NR with a flexible pattern. The pattern can be LTE only, NR only, LTE / NR FDM, and can have a granularity at the RB level.

[0362] In the case of LTE PUCCH, it can be mapped / allocated to the control region within a subframe. An RB pair within a subframe can be allocated to the LTE PUCCH for one terminal. The RBs included in the RB pair can occupy different subcarriers in each of the two slots within the subframe. That is, the RB pair allocated to the LTE PUCCH can frequency hop at the slot boundary.

[0363] In the case of NR PUCCH, it can be mapped / allocated to the control area within the slot. For example, in the case of long PUCCH, the control channel of the long transmission period can be transmitted in the DFT-S-OFDM (Discrete Fourier Transform-spread-OFDM) method, which is a single-carrier transmission method rather than OFDM transmission, because it is used for the purpose of increasing cell coverage. Therefore, at this time, PUCCH must be transmitted using only consecutive subcarriers, and frequency hopping can be configured to obtain the frequency diversity effect. That is, when frequency hopping is applied (when frequency hopping is enabled by a higher signal), the terminal can configure the uplink control channel of the long transmission period based on the resources of a distant location. When frequency hopping is not applied (when frequency hopping is disabled by a higher signal), the long PUCCH can be transmitted during the transmission symbol period of the long PUCCH at the frequency position according to the transmission start PRB information and PRB number information set by the higher signal.

[0364] For example, in the case of a short PUCCH, it can be transmitted in both a downlink-centered slot and an uplink-centered slot, and is generally transmitted in the last symbol of the slot, or the OFDM symbol at the back (e.g., the last OFDM symbol, the penultimate OFDM symbol, or the last two OFDM symbols). Of course, it is also possible for a short PUCCH to be transmitted at any position within the slot. And a short PUCCH can be transmitted using one OFDM symbol or two OFDM symbols. Radio resources for a short PUCCH are allocated in PRB units on the frequency side, and the allocated PRBs can be one PRB, multiple consecutive PRBs, or multiple PRBs spaced apart in the frequency band. And the allocated PRBs must be included in a band equal to or smaller than the frequency band supported by the terminal.

[0365] Referring to FIG. 11 and FIG. 12, in the case of LTE PUCCH resources, PUCCH resources (0, 1, 2, 3, 4, 5, ...) can be mapped / allocated within a subframe including 14 OFDM symbols, where RB pairs corresponding to PUCCH resources with the same index can be frequency hopped at slot boundaries. For example, PUCCH resource 0 can be allocated to UE A, and PUCCH resource 5 can be allocated to UE B. The index (Physical resource block number) of the PRB constituting the PUCCH is This can be, It can be an uplink bandwidth configuration or the number of UL RBs included in the uplink bandwidth.

[0366] In case of NR PUCCH resources, PUCCH resources (0, 1, 2, 3, 4, 5, ...) can be mapped / allocated within a slot containing 14 OFDM symbols, and frequency hopping can be applied at the slot boundary for RBs corresponding to PUCCH resources with the same index. For example, PUCCH resource 0 can be allocated to UE A, and PUCCH resource 5 can be allocated to UE B. In case of NR PUCCH, it can be a long PUCCH, but is not limited thereto.

[0367] The characteristics of LTE PUCCH can be summarized as follows. When frequency hopping is applied to NR PUCCH (e.g., when IntraSlotFequencyHopping is enabled), NR PUCCH can also have the corresponding characteristics below. That is, it can have a pattern corresponding to the pattern of LTE PUCCH below.

[0368] 1) PUCCH uses one RB in each of the two slots within a subframe.

[0369] 2) The location of PUCCH changes at the slot boundary depending on the change in slot number.

[0370] When IntraSlotFequencyHopping is enabled, since NR PUCCH has characteristics corresponding to LTE PUCCH, LTE PUCCH can be replaced with NR PUCCH with IntraSlotFequencyHopping enabled unless otherwise specifically mentioned in the description of an embodiment of the present disclosure. In the case of NR PUCCH, compared to LTE PUCCH, subframes can be changed to slots, and slots can be changed to half slots. Unless otherwise specifically mentioned in the description of an embodiment of the present disclosure, PUCCH resources can be understood as LTE PUCCH or NR PUCCH with IntraSlotFequencyHopping enabled, but are not limited thereto.

[0371] PUCCH resources can be divided into those transmitted periodically and those transmitted on-demand. For example, periodic PUCCH resources can be used for scheduling requests (SRs) or CSI reporting. On-demand PUCCH resources can be used to transmit uplink control information (UCI) for hybrid automatic repeat request (HARQ) feedback. For example, each PUCCH resource can be reserved for a specific UE through RRC (re)configuration.

[0372] According to one embodiment of the present disclosure, a method for indicating a rate matching pattern may be provided. For example, the signaling method for rate matching may vary depending on the format of the LTE PUCCH. Table 18 summarizes signaling methods for appropriate rate matching according to the PUCCH format. However, the present disclosure is not limited thereto, and signaling methods for other rate matching may be applied to each PUCCH format.

[0373] [Table 18]

[0374]

[0375] FIG. 13 is a diagram illustrating an example of an LTE / NR DSS scenario to which one embodiment of the present disclosure is applicable.

[0376] FIG. 14 is a diagram illustrating an example of an LTE / NR DSS scenario to which one embodiment of the present disclosure is applicable.

[0377] Referring to FIG. 13, the area of ​​NR PUSCH that can be allocated from the standpoint of a single UE is illustrated. If both LTE PUCCH and NR PUCCH are allocated within a bandwidth, NR PUSCH can be allocated to an area other than the area to which LTE PUCCH and NR PUCCH are allocated. If LTE PUCCH is not allocated within a bandwidth and NR PUCCH is allocated, the area corresponding to LTE PUCCH can also be used as NR PUSCH. If neither LTE PUCCH nor NR PUCCH is allocated within a bandwidth, all resources within the bandwidth can be used as NR PUSCH. In the case of FIG. 13, resources that are not used as NR PUSCH are used as PUCCHs of other RATs or NR PUCCHs, and if each PUCCH is not allocated, the area corresponding to the unallocated PUCCH can be used as NR PUSCH, so the problem of resource waste does not occur. However, the example in Fig. 14 causes a problem of resource waste.

[0378] Frequency resource allocation methods for NR PUSCH can be divided into bitmap-based (RAT (resource allocation type) 0) and RIV-based (RAT 1) methods as described above. Due to the limitations of these NR PUSCH frequency resource allocation methods, in the example of FIG. 13, resources that cannot be used for NR PUSCH or for other purposes, i.e., wasted resources, may occur.

[0379] Specifically, for RAT 0, one bit in the bitmap can represent consecutive RBs. That is, RAT 0 can indicate frequency resource allocation in units of RBGs. Therefore, when LTE PUCCH and NR PUSCH overlap in an RBG, the remaining resources (remaining RBs) that do not overlap in the RBG cannot be indicated by RAT 0. Therefore, resources cannot be allocated in units of RBGs, which are resource allocation units of RAT 0, and thus resource waste may occur.

[0380] For RAT 1, frequency resource allocation can be indicated by the start RB and the number of consecutive RBs from the start RB. That is, RAT 1 does not support non-contiguous RB allocation. Therefore, when LTE PUCCH and NR PUSCH overlap within the bandwidth, all RBs after the overlapping RB in the frequency domain cannot be indicated by RAT 1.

[0381] Specifically, in Fig. 14, assuming a bandwidth of 20 MHz, the number of RBs in the bandwidth is 106 for NR. When configuration 1 is used in RAT 0, the RBG size is 8, and a total of 2 RBs are allocated for LTE PUCCH purposes, but 16 RBs corresponding to 2 RBGs may not be allocated for NR PUSCH purposes. Since RAT 1 can only allocate consecutive RBs, a larger amount of resources may not be allocated to NR PUSCH and may be wasted compared to the case of RAT 0.

[0382] Existing 5G systems support rate matching, which allows transmission to occur only in resource locations that conflict with other RATs and only in the remaining resource locations. However, only limited patterns and types are supported in existing 5G systems. Existing 5G systems do not support rate matching for single or multiple non-contiguous LTE PUCCH resources. Furthermore, existing 5G systems do not support rate matching at different PUCCH resource levels for each slot. This makes it difficult to indicate rate matching for dynamically used LTE PUCCH resources in DCI (e.g., UL grant DCI). Furthermore, if the rate matching method supported in existing 5G systems is based on this, the number of expressions for expressing LTE PUCCH resources increases exponentially, which can significantly increase the overhead for indicating rate matching.

[0383] FIG. 15 illustrates an example of a rate matching method in a communication system to which one embodiment of the present disclosure is applicable. For more specific details of the rate matching method of FIG. 15, refer to the description of rate matching described above.

[0384] Referring to Fig. 15(a), rate matching can be performed at the symbol / RB level. For example, rate matching can be performed for symbols #5, #8, #9, and #11, which means that all RBs in each symbol #5, #8, #9, and #11 are rate-matched. Therefore, the method of Fig. 15(a) may result in wasted RBs, and thus may not be suitable for PUCCH level rate matching. For example, it may not be suitable for intra slot hopping pattern rate matching for PUCCH. In addition, the method of Fig. 15(a) supports only up to four rate matching patterns, and thus may not be suitable for rate matching for dynamically indicated PUCCH resources.

[0385] Referring to Fig. 15(b), rate matching can be performed for REs to which LTE CRSs are mapped. That is, since rate matching is performed by the CRS pattern, the method of Fig. 15(b) cannot be applied to PUCCH level rate matching.

[0386] According to one embodiment of the present disclosure, an inter-RAT PUCCH resource level rate matching method may be supported. According to one embodiment of the present disclosure, a method for dynamically indicating a rate matching pattern for PUCCH resources used by another RAT in a UL spectrum sharing situation may be proposed.

[0387] According to one embodiment of the present disclosure, a rate matching pattern indication may be included in a DCI for a UL grant. According to one embodiment of the present disclosure, resource efficiency can be maximized by minimizing the amount of resources that cannot be used due to constraints of a resource allocation scheme in a UL spectrum sharing situation (e.g., allocation of RBG units in RAT 0 or allocation of only contiguous RBs in RAT 1).

[0388] A rate matching method according to one embodiment of the present disclosure can be summarized as shown in Table 19.

[0389] [Table 19]

[0390]

[0391] FIG. 16 is a diagram illustrating an example of a signaling procedure between a terminal and a base station according to one embodiment of the present disclosure. The flowchart of FIG. 16 illustrates an exemplary method that can be implemented according to the principles of the present disclosure, and various modifications may be made to the method illustrated in the flowchart. For example, although illustrated as a series of steps, the various steps in each drawing may overlap, occur in parallel, occur in different orders, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0392] Referring to FIG. 16, in operation 1601 according to an embodiment, the base station may transmit an RRC reconfiguration message, and the terminal may receive the same. The RRC reconfiguration message is an example and may be replaced with RRC signaling, an RRC message, or higher layer signaling. This applies equally to the description of the present disclosure unless specifically stated otherwise. In operation 1603 according to an embodiment, the terminal may transmit an RRC reconfiguration complete message, and the base station may receive the same. In operation 1605 according to an embodiment, the base station may transmit a MAC CE, and the terminal may receive the same. In operation 1607 according to an embodiment, the base station may transmit a UL grant DCI (e.g., format 0_0 or 0_1), and the terminal may receive the same. In operation 1609 according to an embodiment, the terminal may transmit a PUSCH based on the UL grant DCI, and the base station may receive the same.

[0393] For more specific details of terminal operation and base station operation according to one embodiment of the present disclosure described above, reference may be made to the description of the present disclosure described below.

[0394] To support operations according to one embodiment of the present disclosure, a terminal and / or a base station may support one or more of the following capabilities. For example, signaling for each capability may be supported. For example, a terminal may transmit terminal capability information indicating that it supports one or more of the following capabilities, and if the base station identifies that the terminal supports one or more of the following capabilities through the terminal capability information, it may perform a PUCCH resource level rate matching operation according to one embodiment of the present disclosure.

[0395] - Terminal perspective

[0396] - - PHY layer: Capability to receive / decode IE (information element) related to rate matching pattern indication in DCI, ability to transmit / encode rate-matched PUSCH

[0397] - MAC layer: Ability to receive / decode IE related to rate matching pattern indication within MAC CE

[0398] - RRC layer: Ability to receive / decode IEs related to rate matching pattern indication in RRC signaling

[0399] - Base station perspective

[0400] - - PHY layer: Transmit / encode capability for rate-matching pattern indication related IE in DCI, rate-matched PUSCH reception / decoding capability

[0401] - MAC layer: Transmit / encode capability for IE related to rate matching pattern indication within MAC CE

[0402] - RRC layer: Transmission / encoding capability for rate matching pattern indication related IE in RRC signaling

[0403] According to one embodiment of the present disclosure, each IE transmitted and received in RRC signaling / MAC CE / DCI may be different, as will be described later.

[0404] According to one embodiment of the present disclosure, the RRC reconfiguration message may include candidate LTE PUCCH resource information. For example, the RRC reconfiguration message may include location information for the candidate LTE PUCCH resource. The candidate LTE PUCCH resource may be configured via the RRC reconfiguration message. The candidate LTE PUCCH resource may be for rate matching. That is, the candidate LTE PUCCH resource may be a candidate for which rate matching is applied.

[0405] According to one embodiment of the present disclosure, an LTE base station (e.g., an eNB) can transmit PUCCH resource configuration information to an NR base station (e.g., a gNB). Based on the PUCCH resource configuration information, the NR base station can identify a corresponding candidate LTE PUCCH resource, generate / obtain candidate LTE PUCCH resource information, and transmit the same to a terminal via an RRC reconfiguration message. For example, a plurality of PUCCH resources identified based on the PUCCH resource configuration information can be candidate LTE PUCCH resources to which rate matching will be applied.

[0406] According to one embodiment of the present disclosure, when a base station identifies a candidate LTE PUCCH resource, one terminal per PUCCH resource It can be assumed that Lim. is the number of cyclic shifts (CS) used for PUCCH formats 1 / 1a / 1b in a resource block with a mix of formats 1 / 1a / 1b and 2 / 2a / 2b, and in the present disclosure, it can be assumed that no CDM (code domain multiplex or code domain sharing) is applied to PUCCH resources. It can be assumed that no CDM is used when the base station identifies candidate LTE PUCCH resources. That is, in the description of the present disclosure, it can be assumed that a PUCCH resource is for one terminal and no CDM is set.

[0407] However, this is an assumption in identifying candidate LTE PUCCH resources, and the present disclosure is not limited to PUCCH resources for a single terminal without CDM configured. The present disclosure may also be applied to PUCCH resources for multiple terminals with CDM configured. That is, regardless of the configuration of the PUCCH resources, the present disclosure assumes that the PUCCH resource is for a single terminal without CDM configured in identifying candidate LTE PUCCH resources, and the PUCCH resources actually transmitted and received may be for a single terminal without CDM configured, or may be for multiple terminals with CDM configured.

[0408] FIG. 17 is a diagram illustrating an example of RRC parameters according to one embodiment of the present disclosure.

[0409] Referring to FIG. 17, according to one embodiment of the present disclosure, the RRC reset message may include one or more of the following RRC parameters.

[0410] 1) The lowest RB index (hereinafter, α) of the PUCCH of another RAT (the RAT that is the target of spectrum sharing, e.g., LTE). This can be understood as the start RB offset of the PUCCH of the other RAT. The start RB offset can be an offset relative to PRB0 among the RBs included in the bandwidth.

[0411] 2) The total number of rate matching patterns (hereinafter, L) or the total number of PUCCH RBs used in other RATs. For example, if the other RAT is LTE, assuming that CDM is not configured, this may be the total number of PUCCH resources available in LTE. In other words, it may also be understood as the total number of PUCCH resources used in other RATs. The specific definition of L may vary depending on the embodiments described below, and this will be described later in the description of each embodiment.

[0412] Referring to Figure 17, starting from the starting RB with index α, PUCCH resources can be set up in consecutive RBs up to RB α. That is, the index α is the index of the RB where the PUCCH starts. Since intra-slot hopping is applied to LTE PUCCH, the frequency region corresponding to L / 2 can include half of the RB pairs that constitute PUCCH resources.

[0413] According to one embodiment of the present disclosure, an RRC reconfiguration complete message may be a message transmitted to a base station when a terminal can support a candidate rate matching pattern. The fact that the terminal can support the candidate rate matching pattern may mean that the terminal supports a rate matching-related operation according to one embodiment of the present disclosure. If the terminal does not support the candidate rate matching pattern, the terminal may transmit an RRC reconfiguration failure message to the base station. When the base station receives the RRC reconfiguration complete message, the base station may determine / identify that the terminal can support the candidate rate matching pattern and perform a rate matching-related operation according to one embodiment of the present disclosure. When the base station receives the RRC reconfiguration failure message, the base station may determine / identify that the terminal does not support the candidate rate matching pattern and may not perform a rate matching-related operation according to one embodiment of the present disclosure.

[0414] According to one embodiment of the present disclosure, rather than determining / identifying that a terminal can support a candidate rate matching pattern based on an RRC reconfiguration complete / failure message, the base station may transmit capability information related to whether the terminal supports the candidate rate matching pattern before the terminal receives the RRC reconfiguration message, and the base station may identify / judge whether the terminal supports the candidate rate matching pattern based on the capability information received from the terminal.

[0415] According to one embodiment of the present disclosure, the MCE CE may be used to update a bitmap included in the DCI in a dynamic rate matching pattern. Alternatively, the MAC CE may be used to set a periodic rate matching pattern.

[0416] According to one embodiment of the present disclosure, the DCI may be a UL grant DCI for scheduling a PUSCH. The DCI may indicate a rate matching pattern for the scheduled PUSCH.

[0417] According to one embodiment of the present disclosure, a method for indicating a rate matching pattern can be divided into a method capable of indicating rate matching for a single PUCCH resource and a method capable of indicating rate matching for multiple PUCCH resources. According to the method capable of indicating rate matching for multiple PUCCH resources in the present disclosure, rate matching for one or multiple PUCCH resources can be indicated. In other words, this does not necessarily mean that multiple PUCCH resources are indicated by the method.

[0418] Below, each method is described. In the description of each method, parameter B may be the number of bits required to express the entire rate matching pattern (or the total number of rate matching patterns). According to one embodiment of the present disclosure, a method in which one or more of the following embodiments and / or at least some of the following embodiments are combined may be used.

[0419] Example 1 - A method capable of indicating rate matching for a single PUCCH resource

[0420] According to one embodiment of the present disclosure, to indicate one PUCCH resource, Bits can be used. L can be the total number of PUCCH resources.

[0421] Method 1-1) According to one embodiment of the present disclosure, each PUCCH resource may be indicated by one parameter based on B bits. Each bit included in the B bits may indicate a PUCCH resource index.

[0422] Method 1-2) According to one embodiment of the present disclosure, each PUCCH resource can be indicated by two parameters based on B bits. The B-1 bit included in the B bit can indicate the frequency domain location of the PUCCH resource. That is, the B-1 bit included in the B bit can indicate the RB index of the PUCCH resource. The remaining one bit except the B-1 bit included in the B bit can indicate the time domain location (and / or symbol domain location and / or symbol index) of the PUCCH resource. Referring again to FIG. 17, the B-1 bit can be indicated. For example, if the B-1 bit indicates α and the remaining 1 bit is 0, it can be understood that PUCCH resource #0 is indicated. For example, if the B-1 bit indicates α and the remaining 1 bit is 1, it can be understood that PUCCH resource #1 is indicated. That is, the remaining 1 bit excluding the B-1 bit included in the B bit can indicate whether the RB for the first slot or the RB for the second slot is indicated based on the slot boundary within the subframe. The remaining 1 bit excluding the B-1 bit included in the B bit can be, but is not limited to, the MSB (most significant bit) or the LSB (least significant bit) among the B bits.

[0423] According to one embodiment of the present disclosure, to indicate one single PUCCH RB, Bits can be used. L can be the total number of PUCCH RBs. Alternatively, it can be half of the total number of PUCCH resources.

[0424] Method 1-3) According to one embodiment of the present disclosure, each PUCCH RB can be indicated based on B bits. The B bits can indicate the frequency domain location of the PUCCH resource. That is, the B bits can indicate the RB index of the PUCCH resource. In the case of LTE PUCCH (or when intra-slot frequency hopping is enabled), each index can indicate two RBs. Otherwise, each index can indicate one RB.

[0425] Referring back to Figure 17, the B bit is can be indicated. For example, if the B bit indicates α, it can be understood that two RBs are indicated, such as an RB corresponding to PUCCH resource #0 in the first slot and an RB corresponding to PUCCH resource #0 in the second slot. That is, the index indicated by the B bit can be understood as an index that indicates the RB corresponding to the index in the first slot and two RBs, such as (maximum number of RBs - RB of the indicated index), in the second slot. For example, if it is indicated that rate-matching will be applied to RB α, the terminal can apply rate-matching to PUCCH resource #0 and PUCCH resource #1. That is, based on the slot boundary, PUCCH resource #0 and PUCCH resource #1 in the first slot, and PUCCH resource #0 and PUCCH resource #1 in the second slot can be rate-matched. In cases other than LTE PUCCH or when intra-slot frequency hopping is not applied, the index indicated by the B bit can be understood as indicating one RB corresponding to the index. For example, methods 1-3 can be used in cases where complexity mitigation / simplification is required or when PUCCH DMRS resources are set to 1 symbol, but are not limited thereto.

[0426] Methods 1-1 to 1-3 can be summarized as in Table 20.

[0427] [Table 20]

[0428]

[0429] In Table 20, the number of bits included in the B bit applied in Method 1-3 may be 1 less than the number of bits included in the B bit applied in Methods 1-1 and 1-2. For example, if there are 10 PUCCH resources (#0,...,#9), the B bit applied in Methods 1-1 and 1-2 may be determined as 10 bits, and the B bit applied in Method 1-3 may be determined as 9 bits.

[0430] Example 2 - A method capable of indicating rate matching for multiple PUCCH resources

[0431] Method 2-1) According to one embodiment of the present disclosure, the B=L bit in the DCI or MAC CE may be used to indicate one or more or multiple PUCCH resources.

[0432] According to one embodiment of the present disclosure, a PUCCH resource index may be indicated. L may be the total number of PUCCH resources. The lth bit among the B=L bits may be mapped to the lth PUCCH resource among the L PUCCH resources. For example, when the value of the lth bit is '1' (or '0'), rate matching may be performed on the lth PUCCH resource. Conversely, when the value of the lth bit is '0' (or '1'), rate matching may not be performed on the lth PUCCH resource. That is, the B=L bit may indicate whether or not rate matching is performed on each PUCCH resource using a bitmap.

[0433] Method 2-2) According to one embodiment of the present disclosure, the B=L bit in the DCI or MAC CE may be used to indicate one or more or multiple PUCCH RBs.

[0434] According to one embodiment of the present disclosure, a PUCCH RB index may be indicated. L may be the total number of PUCCH RBs. Alternatively, it may be half of the total number of PUCCH resources. The lth bit among B=L bits may be mapped to the lth PUCCH RB among L PUCCH RBs. For example, when the value of the lth bit is '1' (or '0'), rate matching may be performed on the lth PUCCH RB. Conversely, when the value of the lth bit is '0' (or '1'), rate matching may not be performed on the lth PUCCH RB. That is, the B=L bit may indicate, as a bitmap, whether rate matching is performed on each PUCCH RB.

[0435] For LTE PUCCH (or when intra-slot frequency hopping is enabled), the lth bit of the B=L bits (or each bit included in the B=L bits) can indicate two RBs. For example, the first bit can indicate RB α and RB Whether to apply rate matching to PUCCH resource #0 and PUCCH resource #1 can be indicated. If rate matching is indicated to be applied by the first bit, the terminal can apply rate matching to PUCCH resource #0 and PUCCH resource #1. That is, based on the slot boundary, PUCCH resource #0 and PUCCH resource #1 can be rate-matched in the first slot, and PUCCH resource #0 and PUCCH resource #1 can be rate-matched in the second slot. Otherwise (if it is not LTE PUCCH and / or intra-slot frequency hopping is disabled), the lth bit among the B=L bits can indicate one RB.

[0436] FIG. 18 is a diagram illustrating an example of a bit field in DCI according to one embodiment of the present disclosure.

[0437] Referring to FIG. 18, the DCI field may include 1 octet, i.e., 8 bits. This may mean that L=8. For example, if the DCI field is '00011001', rate matching may be performed for PUCCH resource IDs 0, 3, and 4. That is, after rate matching is performed at RE positions corresponding to PUCCH resource IDs 0, 3, and 4, a PUSCH with rate matching applied may be transmitted. As another example, if the DCI field is '00000001', rate matching may be performed for PUCCH resource ID 7. That is, after rate matching is performed at RE positions corresponding to PUCCH resource ID 7, a PUSCH with rate matching applied may be transmitted.

[0438] Example 3 - A method capable of indicating rate matching for multiple PUCCH resources

[0439] According to one embodiment of the present disclosure, B in DCI is provided to indicate one or more or more PUCCH resources (or RBs). <L 비트가 사용될 수 있다.

[0440] According to one embodiment of the present disclosure, among candidate PUCCH resources (or RBs) set by RRC signaling, a candidate PUCCH resource (or RB) may be indicated by MAC CE, and among the candidate PUCCH resources (or RBs) indicated by MAC CE, a candidate PUCCH resource (or RB) may be indicated by DCI.

[0441] Method 3-1) According to one embodiment of the present disclosure, a PUCCH resource index may be indicated. L may be the total number of PUCCH resources.

[0442] According to one embodiment of the present disclosure, a bitmap indicating a set of expected total PUCCH resources among all PUCCH resources may be indicated by a MAC CE. The l-th bit of the bitmap may be mapped to the l-th PUCCH resource among L PUCCH resources. For example, when the value of the l-th bit is '1' (or '0'), it may indicate that the l-th PUCCH resource is selected as an activated rate matching pattern. Conversely, when the value of the l-th bit is '0' (or '1'), it may indicate that the l-th PUCCH resource is not selected as an activated rate matching pattern. The maximum number M of activated rate matching patterns that may be indicated by a MAC CE is It could be.

[0443] According to one embodiment of the present disclosure, a bit field indicated in DCI may indicate an activated rate matching pattern indicated by MAC CE as a bitmap. For example, the b-th bit of the bitmap indicated in DCI may be mapped to the activated rate matching pattern, i.e., the b-th PUCCH resource among the PUCCH resources indicated by MAC CE. For example, when the value of the b-th bit is '1' (or '0'), rate matching may be performed on the b-th PUCCH resource. Conversely, when the value of the b-th bit is '0' (or '1'), rate matching may not be performed on the b-th PUCCH resource.

[0444] Method 3-2) According to one embodiment of the present disclosure, a PUCCH RB index may be indicated. L may be the total number of PUCCH RBs. Alternatively, it may be half of the total number of PUCCH resources.

[0445] According to one embodiment of the present disclosure, a bitmap indicating a set of expected total PUCCH RBs among all PUCCH RBs may be indicated by a MAC CE. The l-th bit of the bitmap may be mapped to the l-th PUCCH RB among L PUCCH RBs. For example, when the value of the l-th bit is '1' (or '0'), it may indicate that the l-th PUCCH RB is selected as an activated rate matching pattern. Conversely, when the value of the l-th bit is '0' (or '1'), it may indicate that the l-th PUCCH RB is not selected as an activated rate matching pattern. The maximum number M of activated rate matching patterns that may be indicated by a MAC CE is It could be.

[0446] For LTE PUCCH (or when intra-slot frequency hopping is enabled), the lth bit of the bitmap of the MAC CE (or each bit included in the bitmap of the MAC CE) can indicate two RBs. For example, the RB indicated by the lth bit of the bitmap of the MAC CE can be the RB corresponding to the index l and the RB corresponding to the index (maximum index of RB - (α + RB of the indicated index)). For example, the first bit can indicate RB α and RB can correspond to . Otherwise (if it is not LTE PUCCH and / or intra-slot frequency hopping is disabled), the lth bit among B=L bits can indicate 1 RB.

[0447] According to one embodiment of the present disclosure, a bit field indicated in DCI may indicate an activated rate matching pattern indicated by MAC CE as a bitmap. For example, the b-th bit of the bitmap indicated in DCI may be mapped to the activated rate matching pattern, i.e., the b-th PUCCH RB among the PUCCH RBs indicated by MAC CE. For example, when the value of the b-th bit is '1' (or '0'), rate matching may be performed on the b-th PUCCH RB. Conversely, when the value of the b-th bit is '0' (or '1'), rate matching may not be performed on the b-th PUCCH RB.

[0448] FIG. 19 is a diagram illustrating an example of a relationship between a bitmap included in a MAC CE and a bitmap included in a DCI according to one embodiment of the present disclosure.

[0449] Referring to FIG. 19, the bitmap included in the MAC CE can indicate M activated PUCCH resources among L PUCCH resources set by RRC. The bitmap included in the DCI can indicate PUCCH resources to which rate matching will be applied among M activated PUCCH resources by the MAC CE. Accordingly, the bitmap included in the DCI can include M bits.

[0450] For example, the M PUCCH resources activated by the MAC CE can be applied after a certain time from the time of reception of the MAC CE (or the PDSCH including the MAC CE). For example, if the MAC CE (or the PDSCH including the MAC CE) is received in slot #n, the M PUCCH resources activated by the MAC CE can be applied after slot #n+k, where k can be an integer greater than or equal to 0. k can be predefined and / or set by higher layer signaling.

[0451] FIG. 20 is a diagram illustrating an example of a relationship between a bitmap included in a MAC CE and a bitmap included in a DCI according to one embodiment of the present disclosure. FIG. 20 is an example when L=16 and B=4.

[0452] Referring to FIG. 20, 16 bits included in the MAC CE can indicate the activated PUCCH resource index among 16 PUCCH resources set by RRC as a bitmap. For example, if the 1st, 4th, 7th, and 14th bits among the 16 bits included in the MAC CE are indicated as 1 and the remaining bits are indicated as 0, the 1st, 4th, 7th, and 14th PUCCH resources among the 16 PUCCH resources may be activated. The bitmap included in the DCI can indicate whether rate matching is performed for the activated 1st, 4th, 7th, and 14th PUCCH resources.

[0453] According to one embodiment of the present disclosure, whether a rate matching pattern indication related IE is included in DCI can be identified / determined as follows.

[0454] - If the RRC reset message does not contain information about candidate PUCC resources (e.g., information about α and / or L), the DCI may not include the rate matching pattern indication related IE.

[0455] - If the RRC reset message contains information about candidate PUCC resources (e.g., information about α and / or L),

[0456] - - DCI always includes an IE related to rate matching pattern indication, or

[0457] - - The DCI includes a 1-bit flag indicating whether the rate matching pattern indication related IE is included, and if the 1-bit flag is '1' (or '0'), the DCI includes the rate matching pattern indication related IE, and if the 1-bit flag is '0' (or '1'), the DCI does not include the rate matching pattern indication related IE, and / or

[0458] - - If all bits included in the rate matching pattern indication IE included in DCI are set to '0's or '1's, it can be indicated that rate matching is not performed.

[0459] FIG. 21 is a diagram for explaining a DM-RS applicable to PUSCH transmission according to one embodiment of the present disclosure.

[0460] FIG. 22 is a diagram for explaining a DM-RS applicable to PUSCH transmission according to one embodiment of the present disclosure.

[0461] Referring to FIG. 21, when an additional DM-RS (demodulation reference signal) is not configured (e.g., dmrs-AdditionalPosition = 0), a DM-RS for PUSCH can be mapped to one symbol within one slot (e.g., a DM-RS symbol of symbol #2). The DM-RS mapped to one symbol can be composed of CDM group 0 and CDM group 1.

[0462] For example, if LTE PUCCH corresponds to symbol #7 to symbol #13 (right side, case 2), rate matching is applied to symbol #7 to symbol #13, and PUSCH and DM-RS for PUSCH can be transmitted in symbol #0 to symbol #6.

[0463] On the other hand, in the case where LTE PUCCH corresponds to symbol #0 to symbol #6 (left side, case 1), rate matching is applied to symbol #0 to symbol #6, and PUSCH must be transmitted in symbol #7 to symbol #13. However, since DM-RS for PUSCH is not set in symbol #7 to symbol #13, DM-RS for PUSCH cannot be transmitted, which may cause a problem in which channel estimation is impossible at the receiver.

[0464] According to one embodiment of the present disclosure, for a PRB (index n) corresponding to case 1, one or more of the following methods may be applied.

[0465] 1) According to one embodiment of the present disclosure, rate matching may be performed for all symbols (e.g., symbols #0 to #13) included in PRB n. Referring to alt.1 of FIG. 22, REs included in PRB n may be rate matched and not used for PUSCH transmission.

[0466] 2) According to one embodiment of the present disclosure, rate matching can be performed for all symbols included in PRB n (e.g., symbols #0 to #13). Referring to alt.2 of FIG. 22, in PRB n, the DM-RS symbol can be changed to any one of symbols #7 to #13 (e.g., symbol #11). In this case, in PRB n, the PUSCH and the DM-RS for the PUSCH can be transmitted in symbols #7 to #13.

[0467] FIG. 23 is a diagram for explaining a DM-RS applicable to PUSCH transmission according to one embodiment of the present disclosure.

[0468] FIG. 24 is a diagram for explaining a DM-RS applicable to PUSCH transmission according to one embodiment of the present disclosure.

[0469] Referring to FIGS. 23 and 24, when an additional demodulation reference signal (DM-RS) is configured (e.g., dmrs-AdditionalPosition > 0), a DM-RS for PUSCH can be mapped to two symbols within one slot (e.g., DM-RS symbols of symbol #2 and symbol #11). The DM-RS mapped to one symbol can be composed of CDM group 0 and CDM group 1.

[0470] For example, if LTE PUCCH corresponds to symbols #0 to #6 (left side, case 1), rate matching is applied to symbols #0 to #6, and PUSCH and DM-RS for PUSCH (symbol #11) can be transmitted in symbols #7 to #13. In this case, DM-RS for PUSCH may not be transmitted in symbol #2. The base station can perform channel estimation from DM-RS for PUSCH in symbol #11.

[0471] For example, if LTE PUCCH corresponds to symbols #7 to #13 (right side, case 2), rate matching is applied to symbols #7 to #13, and PUSCH and DM-RS for PUSCH (symbol #2) can be transmitted in symbols #0 to #6. In this case, DM-RS for PUSCH may not be transmitted in symbol #11. The base station can perform channel estimation from DM-RS for PUSCH in symbol #2.

[0472] FIG. 25 is a flowchart illustrating an example of a terminal operation according to one embodiment of the present disclosure. Various modifications may be made to the method illustrated in the flowchart of FIG. 25. For example, although illustrated as a series of steps, the various steps in each drawing may overlap, occur in parallel, occur in different orders, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0473] Referring to FIG. 25, in operation 2510 according to one embodiment, a terminal may receive information related to candidate PUCCH (physical uplink control channel) resources in a first radio access technology (RAT) through upper layer signaling (e.g., an RRC message).

[0474] In operation 2520 according to one embodiment, the terminal may receive information related to activated candidate PUCCH resources among candidate PUCCH resources through a medium access control element (MAC CE). Operation 2520 according to one embodiment may be omitted.

[0475] In operation 2530 according to an embodiment, the terminal may receive downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) (or uplink channel). The DCI may include a bit field indicating a candidate PUCCH resource included in candidate PUCCH resources. For example, if a MAC CE is received in operation 2520 according to an embodiment, the bit field may indicate a candidate PUCCH resource among the activated candidate PUCCH resources. For example, if a MAC CE is not received in operation 2520 according to an embodiment, the bit field may indicate a candidate PUCCH resource among the candidate PUCCH resources conveyed in upper layer signaling.

[0476] In operation 2530 according to one embodiment, the terminal may transmit an uplink channel based on DCI. Rate-matching may be applied to REs (resource elements) included in the uplink channel that overlap with candidate PUCCH resources indicated by the DCI.

[0477] For specific details of terminal operation according to one embodiment of the present disclosure described above, reference may be made to the description of one embodiment of the present disclosure described above.

[0478] FIG. 26 is a flowchart illustrating an example of an operation flow of a base station according to one embodiment of the present disclosure. Various modifications may be made to the method illustrated in the flowchart of FIG. 26. For example, although illustrated as a series of steps, the various steps in each drawing may overlap, occur in parallel, occur in different orders, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0479] Referring to FIG. 26, in operation 2610 according to one embodiment, a base station may transmit information related to candidate physical uplink control channel (PUCCH) resources in a first radio access technology (RAT) via upper layer signaling (e.g., an RRC message).

[0480] In operation 2620 according to one embodiment, the base station may transmit information related to activated candidate PUCCH resources among candidate PUCCH resources through a medium access control element (MAC CE). Operation 2620 according to one embodiment may be omitted.

[0481] In operation 2630 according to an embodiment, the base station may transmit downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) (or uplink channel). The DCI may include a bit field indicating a candidate PUCCH resource included in candidate PUCCH resources. For example, if a MAC CE is transmitted in operation 2620 according to an embodiment, the bit field may indicate a candidate PUCCH resource among the activated candidate PUCCH resources. For example, if a MAC CE is not transmitted in operation 2620 according to an embodiment, the bit field may indicate a candidate PUCCH resource among the candidate PUCCH resources conveyed in higher layer signaling.

[0482] In operation 2630 according to one embodiment, a base station may receive an uplink channel. Rate-matching may be applied to an RE (resource element) included in the uplink channel that overlaps with a candidate PUCCH resource indicated by DCI.

[0483] For specific details of the base station operation according to one embodiment of the present disclosure described above, reference may be made to the description of one embodiment of the present disclosure described above.

[0484] FIG. 27 is a diagram illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0485] Referring to FIG. 27, the terminal may include a transceiver, which refers to a terminal receiving unit (2700) and a terminal transmitting unit (2710), a memory (not shown), and a terminal processing unit (2705, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver units (2700, 2710), the memory, and the terminal processing unit (2705) of the terminal may operate. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. In addition, the transceiver unit, the memory, and the processor may be implemented in the form of a single chip.

[0486] A transceiver unit can transmit and receive signals to and from a base station. The signals may include control information and data. To this end, the transceiver unit may include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is merely one embodiment of the transceiver unit, and the components of the transceiver unit are not limited to the RF transmitter and RF receiver.

[0487] Additionally, the transceiver can receive a signal through a wireless channel and output it to the processor, and transmit a signal output from the processor through the wireless channel.

[0488] Memory can store programs and data necessary for the terminal's operation. Furthermore, memory can store control information or data included in signals transmitted and received by the terminal. Memory can be comprised of a storage medium, such as ROM, RAM, a hard disk, CD-ROM, or DVD, or a combination of such storage media. Furthermore, there can be multiple memories.

[0489] Additionally, the processor can control a series of processes to enable the terminal to operate according to the aforementioned embodiments. For example, the processor can receive DCI consisting of two layers and control components of the terminal to simultaneously receive multiple PDSCHs. There may be multiple processors, and the processors can perform component control operations of the terminal by executing programs stored in memory.

[0490] FIG. 28 is a diagram illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

[0491] Referring to FIG. 28, the base station may include a transceiver, which refers to a base station receiver (2800) and a base station transmitter (2810), a memory (not shown), and a base station processor (2805, or a base station control unit or processor). Depending on the communication method of the base station described above, the transceiver (2800, 2810), the memory, and the base station processor (2805) of the base station may operate. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. In addition, the transceiver, the memory, and the processor may be implemented in the form of a single chip.

[0492] The transceiver can transmit and receive signals with the terminal. Here, the signals may include control information and data. To this end, the transceiver may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is only one embodiment of the transceiver, and the components of the transceiver are not limited to the RF transmitter and RF receiver.

[0493] Additionally, the transceiver can receive a signal through a wireless channel and output it to the processor, and transmit the signal output from the processor through the wireless channel.

[0494] The memory can store programs and data necessary for the operation of the base station. Furthermore, the memory can store control information or data included in signals transmitted and received by the base station. The memory can be comprised of a storage medium, such as ROM, RAM, a hard disk, CD-ROM, or DVD, or a combination of such storage media. Furthermore, there can be multiple memories.

[0495] The processor can control a series of processes to enable the base station to operate according to the aforementioned embodiments of the present disclosure. For example, the processor can configure two layers of DCIs containing allocation information for multiple PDSCHs and control each component of the base station to transmit them. There may be multiple processors, and the processors can perform component control operations of the base station by executing programs stored in memory.

[0496] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0497] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.

[0498] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0499] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure.

[0500] In the specific embodiments of the present disclosure described above, components included in one embodiment are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0501] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples to easily explain the technical contents of the present disclosure and to help the understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the above-mentioned embodiments can be combined and operated with each other as needed. For example, parts of one embodiment of the present disclosure and parts of another embodiment can be combined with each other to operate a base station and a terminal. For example, parts of the first embodiment and the second embodiment of the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above-mentioned embodiments have been presented based on an FDD LTE system, other modifications based on the technical idea of ​​the above-mentioned embodiments can be implemented with other systems such as a TDD LTE system, 5G, or NR system.

[0502] Meanwhile, the order of description in the drawings explaining the method of the present disclosure does not necessarily correspond to the order of execution, and the order of precedence may be changed or executed in parallel.

[0503] Alternatively, the drawings illustrating the method of the present disclosure may omit some components and include only some components without detracting from the essence of the present disclosure.

[0504] In addition, the method of the present disclosure may be implemented by combining some or all of the contents included in each embodiment within a scope that does not harm the essence of the present disclosure.

[0505] Various embodiments of the present disclosure have been described above. The foregoing description of the present disclosure is for illustrative purposes only, and the embodiments of the present disclosure are not limited to the disclosed embodiments. Those skilled in the art will appreciate that the present disclosure can be readily modified into other specific forms without altering the technical spirit or essential characteristics of the present disclosure. The scope of the present disclosure is indicated by the claims described below rather than the detailed description above, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included within the scope of the present disclosure.

Claims

1. In a method performed by a terminal in a communication system, A step of receiving information related to candidate PUCCH (physical uplink control channel) resources in a first RAT (radio access technology) through upper layer signaling; A step of receiving downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) in a second RAT, the DCI including a bit field indicating a candidate PUCCH resource included in the candidate PUCCH resources; A step of performing rate-matching applied to an RE (resource element) included in the PUSCH that overlaps with the candidate PUCCH resource; and A method comprising the step of transmitting a PUSCH to which the above rate-matching is applied.

2. In paragraph 1, The number of bits in the above bit field is is determined as a value satisfying , and L is related to the number of candidate PUCCH resources, The above bit field indicates a value corresponding to the index of the candidate PUCCH resource, or A method wherein one bit of the bit field indicates a value corresponding to a time domain location of the candidate PUCCH resource, and the remaining bits of the bit field except for the one bit indicate a value corresponding to a frequency domain location of the PUCCH resource.

3. In paragraph 1, If a MAC CE (medium access control control element) indicating an activated candidate PUCCH resource among the above candidate PUCCH resources is received, the bit field is a first bitmap indicating the candidate PUCCH resource included in the activated candidate PUCCH resource, and the size of the first bitmap is equal to the number of the activated candidate PUCCH resources, If the MAC CE is not received, the bit field is a second bitmap indicating the candidate PUCCH resource included in the candidate PUCCH resources, and the size of the second bitmap is equal to the number of the candidate PUCCH resources, When the above MAC CE is received, the activated candidate PUCCH resource is applied after the slot offset from the slot in which the MAC CE is received. A method wherein the above slot offset is a predefined value or set via the upper layer signaling.

4. In paragraph 1, Information about the above candidate PUCCH resources includes information related to a starting RB (resource block) index in the frequency domain of the above candidate PUCCH resources and information related to the number of the above candidate PUCCH resources. Based on the information related to the above start RB index and the information related to the number of the candidate PUCCH resources being received through the upper layer signaling, the DCI further includes an indicator of whether the bit field is included in the DCI, A method in which rate-matching is not performed when all of the above bit fields are set to '1' or all are set to '0'.

5. In paragraph 1, If the RE to which the rate-matching is applied corresponds to symbols included in the first half-slot of the slot for the PUSCH, and a DM-RS (demodulation reference signal) for the PUSCH is set to one of the symbols included in the first half-slot of the slot for the PUSCH: In the RB corresponding to the above candidate PUCCH resource, the RE corresponding to all symbols of the slot for the PUSCH is rate-matched, or A method wherein the DM-RS is transmitted in one of the symbols included in a second half-slot of a slot for the PUSCH.

6. In paragraph 1, When a DM-RS for the PUSCH is set to a first symbol of one of the symbols included in a first half-slot of the slot for the PUSCH and a second symbol of one of the symbols included in a second half-slot of the slot for the PUSCH: If the RE to which the above rate-matching is applied corresponds to symbols included in the first half-slot, the DM-RS set to the first symbol is not transmitted and the DM-RS set to the second symbol is transmitted. A method in which, if the RE to which the rate-matching is applied corresponds to symbols included in the second half-slot, the DM-RS set to the first symbol is transmitted and the DM-RS set to the second symbol is not transmitted.

7. At the terminal of the communication system, Transmitter and receiver; and A processor coupled to the transceiver, the processor comprising: Receiving information related to candidate PUCCH (physical uplink control channel) resources in the first RAT (radio access technology) through upper layer signaling; Receive DCI (downlink control information) for scheduling PUSCH (physical uplink shared channel) in the second RAT; The above DCI includes a bit field indicating a candidate PUCCH resource included in the candidate PUCCH resources; Performing rate-matching applied to REs (resource elements) included in the PUSCH that overlap with the candidate PUCCH resource; and A terminal configured to transmit a PUSCH to which the above rate-matching is applied.

8. In paragraph 7, The number of bits in the above bit field is is determined as a value satisfying , and L is related to the number of candidate PUCCH resources, The above bit field indicates a value corresponding to the index of the candidate PUCCH resource, or A terminal, wherein one bit of the bit field indicates a value corresponding to the time domain location of the candidate PUCCH resource, and the remaining bits of the bit field except for the one bit indicate a value corresponding to the frequency domain location of the PUCCH resource.

9. In paragraph 7, If a MAC CE (medium access control control element) indicating an activated candidate PUCCH resource among the above candidate PUCCH resources is received, the bit field is a first bitmap indicating the candidate PUCCH resource included in the activated candidate PUCCH resource, and the size of the first bitmap is equal to the number of the activated candidate PUCCH resources, If the MAC CE is not received, the bit field is a second bitmap indicating the candidate PUCCH resource included in the candidate PUCCH resources, and the size of the second bitmap is equal to the number of the candidate PUCCH resources, When the above MAC CE is received, the activated candidate PUCCH resource is applied after the slot offset from the slot in which the MAC CE is received. The above slot offset is a predefined value or is set via the upper layer signaling.

10. In paragraph 7, Information about the above candidate PUCCH resources includes information related to a starting RB (resource block) index in the frequency domain of the above candidate PUCCH resources and information related to the number of the above candidate PUCCH resources. Based on the information related to the above start RB index and the information related to the number of the candidate PUCCH resources being received through the upper layer signaling, the DCI further includes an indicator of whether the bit field is included in the DCI, A terminal in which rate-matching is not performed when all of the above bit fields are set to '1' or all are set to '0'.

11. In paragraph 7, If the RE to which the rate-matching is applied corresponds to symbols included in the first half-slot of the slot for the PUSCH, and a DM-RS (demodulation reference signal) for the PUSCH is set to one of the symbols included in the first half-slot of the slot for the PUSCH: In the RB corresponding to the above candidate PUCCH resource, the RE corresponding to all symbols of the slot for the PUSCH is rate-matched, or The terminal wherein the DM-RS is transmitted in one of the symbols included in the second half-slot of the slot for the PUSCH.

12. In paragraph 7, When a DM-RS for the PUSCH is set to a first symbol of one of the symbols included in a first half-slot of the slot for the PUSCH and a second symbol of one of the symbols included in a second half-slot of the slot for the PUSCH: If the RE to which the above rate-matching is applied corresponds to symbols included in the first half-slot, the DM-RS set to the first symbol is not transmitted and the DM-RS set to the second symbol is transmitted. A terminal in which, if the RE to which the rate-matching is applied corresponds to symbols included in the second half-slot, the DM-RS set to the first symbol is transmitted and the DM-RS set to the second symbol is not transmitted.

13. In a method performed by a base station in a communication system, A step of transmitting information related to candidate PUCCH (physical uplink control channel) resources in a first RAT (radio access technology) through upper layer signaling; A step of transmitting DCI (downlink control information) for scheduling a PUSCH (physical uplink shared channel) in a second RAT, the DCI including a bit field indicating a candidate PUCCH resource included in the candidate PUCCH resources; and Comprising a step of receiving the above PUSCH, A method in which rate-matching is applied to REs (resource elements) included in the above PUSCH that overlap with the candidate PUCCH resource.

14. In paragraph 13, When a MAC CE (medium access control control element) indicating an activated candidate PUCCH resource among the above candidate PUCCH resources is transmitted, the bit field is a first bitmap indicating the candidate PUCCH resource included in the activated candidate PUCCH resource, and the size of the first bitmap is equal to the number of the activated candidate PUCCH resources, A method wherein, if the MAC CE is not transmitted, the bit field is a second bitmap indicating the candidate PUCCH resource included in the candidate PUCCH resources, and the size of the second bitmap is equal to the number of the candidate PUCCH resources.

15. In the base station of the communication system, Transmitter and receiver; and A processor coupled to the transceiver, the processor comprising: Transmitting information related to candidate PUCCH (physical uplink control channel) resources in the first RAT (radio access technology) through upper layer signaling; Transmitting DCI (downlink control information) that schedules PUSCH (physical uplink shared channel) in the second RAT; The above DCI includes a bit field indicating a candidate PUCCH resource included in the candidate PUCCH resources; and is set to receive the above PUSCH; A base station in which rate-matching is applied to REs (resource elements) included in the above PUSCH that overlap with the candidate PUCCH resources.

Images