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 include: receiving information related to a plurality of candidate physical uplink control channel (PUCCH) resources in a first radio access technology (RAT) via high layer signaling; receiving downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) in the second RAT, the DCI including a bit field indicating a candidate PUCCH resource included in the plurality of candidate PUCCH resources; performing rate matching applied to resource elements (REs) that overlap with the candidate PUCCH resource among the REs included in the PUSCH; and transmitting the PUSCH to which the rate matching is applied.

Description

Technical Field

[0001] This disclosure generally relates to wireless communication systems, and more specifically, to methods for transmitting and receiving signals in a communication system and means for supporting such methods. Background Technology

[0002] Looking back at the successive generations of wireless communication development, the technologies have primarily been developed for human-centric services such as voice, multimedia, and data. With the commercialization of fifth-generation (5G) communication systems, an explosive growth in connected devices is expected. Examples of network-connected objects include vehicles, robots, drones, home appliances, displays, smart sensors installed in various infrastructures, construction machinery, and factory equipment. Furthermore, mobile devices are expected to evolve into diverse forms, including augmented reality glasses, virtual reality headsets, and holographic devices. To connect hundreds of billions of devices and objects and provide diverse services in the 6G era, the industry is continuously striving to develop enhanced 6G communication systems. For this purpose, 6G communication systems are often referred to as "beyond 5G" systems.

[0003] The 6G communication system, expected to be realized around 2030, will have peak data rates of terabit per second (i.e., 1000 gigabit per second) and wireless latency of 100 microseconds (μsec). This means that compared to 5G communication systems, 6G communication systems will have data rates 50 times faster and latency reduced to one-tenth.

[0004] To achieve such high data rates and ultra-low latency, 6G communication systems are being considered in the terahertz (THz) band (e.g., from 95 GHz to 3 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 ensuring signal arrival (i.e., coverage) even more critical. To guarantee this coverage, key technologies must be developed, including advanced radio frequency (RF) components, antennas, new waveforms superior to orthogonal frequency division multiplexing (OFDM) in terms of coverage, beamforming, and multi-antenna transmission technologies such as massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, and massive MIMO. Furthermore, to improve coverage of terahertz band signals, new technologies such as metamaterial-based lenses and antennas, high-dimensional spatial multiplexing using orbital angular momentum (OAM), and reconfigurable smart surfaces (RIS) are being discussed.

[0005] In addition, several technologies are being developed for 6G communication systems to improve spectrum efficiency and enhance system networks: full-duplex technology that allows uplink and downlink to utilize the same frequency resources simultaneously; integrated network technology combining satellites and High Altitude Platform Stations (HAPS); innovative network architecture technologies that support mobile base stations and optimize and automate network operation; dynamic spectrum sharing technology that avoids conflicts based on spectrum usage prediction; AI-based communication technologies that leverage artificial intelligence (AI) from the design stage and internalize end-to-end AI support functions to achieve system optimization; and next-generation distributed computing technologies that utilize ultra-high-performance communication and computing resources (mobile edge computing (MEC), cloud, etc.) to enable services with complexity exceeding the limitations of terminal computing capabilities. Furthermore, efforts continue to be made to design new protocols for use in 6G communication systems, develop mechanisms for achieving hardware-based secure environments and secure data use, develop technologies for maintaining privacy, strengthen connectivity between devices, optimize networks, promote the software-defined networking of network entities, and increase the openness of wireless communication.

[0006] This research and development of 6G communication systems is expected to enable a new level of hyper-connected experiences (next-generation hyper-connected experiences) through the hyper-connectivity of 6G communication systems. This includes 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 twins. Furthermore, services such as remote surgery, industrial automation, and emergency response provided by 6G communication systems with enhanced security and reliability will be applied in various fields such as industry, healthcare, automotive, and home appliances. Summary of the Invention

[0007] [Technical Issues]

[0008] Various embodiments of this disclosure can provide methods for transmitting and receiving signals in a communication system and apparatus for supporting such methods.

[0009] Various embodiments of this disclosure can provide rate matching and / or puncturing methods for different radio access technologies (RATs) and / or between RATs in a communication system, as well as apparatus for supporting such methods.

[0010] The technical problems to be solved by the various embodiments of this disclosure are not limited to the above-described technical problems, and those skilled in the art can consider other unmentioned technical problems from the various embodiments of this disclosure described below.

[0011] [Solution to the problem]

[0012] According to the implementation method, a method executed by a terminal in a wireless communication system can be provided.

[0013] According to an implementation, the method may include receiving information relating to a plurality of candidate Physical Uplink Control Channel (PUCCH) resources in a first Radio Access Technology (RAT) via higher-layer signaling.

[0014] According to an implementation, the method may include receiving downlink control information (DCI) for scheduling the Physical Uplink Shared Channel (PUSCH) in a second RAT.

[0015] According to an implementation, DCI may include a bit field indicating the candidate PUCCH resources included in a plurality of candidate PUCCH resources.

[0016] According to an implementation, the method may include performing rate matching applied to REs that overlap with candidate PUCCH resources among the resource elements (REs) included in the PUSCH.

[0017] According to an implementation, the method may include sending a PUSCH with rate matching applied.

[0018] According to the implementation method, the number of bits in the bit field can be determined to satisfy... The value of L is related to the number of multiple candidate PUCCH resources.

[0019] According to the implementation, the bit field can indicate a value corresponding to the index of the candidate PUCCH resource.

[0020] According to the implementation, one bit in the bit field can indicate a value corresponding to the time domain position of the candidate PUCCH resource, and the remaining bits in the bit field other than the one bit can indicate a value corresponding to the frequency domain position of the PUCCH resource.

[0021] According to the implementation, when a Media Access Control (MAC) control element (CE) is received indicating an active candidate PUCCH resource among a plurality of candidate PUCCH resources, the bit field is a first bit map indicating the candidate PUCCH resources included in the active candidate PUCCH resources, and the size of the first bit map may be equal to the number of active candidate PUCCH resources.

[0022] According to the implementation, in the absence of a MAC CE, the bit field is a second bitmap indicating the candidate PUCCH resources included in a plurality of candidate PUCCH resources, and the size of the second bitmap may be equal to the number of the plurality of candidate PUCCH resources.

[0023] According to the implementation, upon receiving a MAC CE, the activated candidate PUCCH resource can be applied after a slot offset starting from the slot where the MAC CE was received.

[0024] According to the implementation method, the time slot offset can be a predefined value or can be configured via higher layer signaling.

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

[0026] According to the implementation, based on the information related to the starting RB index and the number of multiple candidate PUCCH resources received via higher-layer signaling, the DCI may further include an indicator of whether a bit field is included in the DCI.

[0027] According to the implementation method, rate matching may not be performed when the bit field is set to all "1"s or all "0".

[0028] According to the implementation, when the RE with applied rate matching corresponds to the symbols included in the first half of the PUSCH time slot and a demodulation reference signal (DM-RS) for PUSCH is configured for one of the symbols included in the first half of the PUSCH time slot: the RE corresponding to all symbols of the PUSCH time slot can be rate matched in the RB corresponding to the candidate PUCCH resource, or the DM-RS can be transmitted in one of the symbols included in the second half of the PUSCH time slot.

[0029] According to the implementation, when a DM-RS for PUSCH is configured for a first symbol included in the first half of the PUSCH time slot and a second symbol included in the second half of the PUSCH time slot: when the rate-matched RE corresponds to a symbol included in the first half of the time slot, the DM-RS configured for the first symbol may not be transmitted and the DM-RS configured for the second symbol may be transmitted; and when the rate-matched RE corresponds to a symbol included in the second half of the time slot, the DM-RS configured for the first symbol may be transmitted and the DM-RS configured for the second symbol may not be transmitted.

[0030] According to the implementation method, a terminal in a wireless communication system can be provided.

[0031] According to one implementation, the terminal may include a transceiver and a processor connected to the transceiver.

[0032] According to an implementation, the processor can be configured to receive information relating to multiple candidate Physical Uplink Control Channel (PUCCH) resources in a first Radio Access Technology (RAT) via higher-layer signaling.

[0033] According to an implementation, the processor can be configured to receive downlink control information (DCI) for scheduling the Physical Uplink Shared Channel (PUSCH) in the second RAT.

[0034] According to an implementation, the processor can be configured such that the DCI includes a bit field indicating the candidate PUCCH resources included among a plurality of candidate PUCCH resources.

[0035] According to an implementation, the processor can be configured to perform rate matching applied to REs that overlap with candidate PUCCH resources among the resource elements (REs) included in the PUSCH.

[0036] According to the implementation, the processor can be configured to send a PUSCH with rate matching applied.

[0037] According to an implementation, a method performed by a base station in a wireless communication system can be provided.

[0038] According to an implementation, the method may include transmitting information relating to a plurality of candidate Physical Uplink Control Channel (PUCCH) resources in a first Radio Access Technology (RAT) via higher-layer signaling.

[0039] According to an implementation, the method may include sending downlink control information (DCI) for scheduling the Physical Uplink Shared Channel (PUSCH) in the second RAT.

[0040] According to an implementation, DCI may include a bit field indicating the candidate PUCCH resources included in a plurality of candidate PUCCH resources.

[0041] According to an implementation, the method may include receiving a PUSCH.

[0042] According to the implementation, rate matching can be applied to REs that overlap with candidate PUCCH resources among the resource elements (REs) included in the PUSCH.

[0043] According to the implementation method, a base station in a wireless communication system can be provided.

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

[0045] According to an implementation, the processor can be configured to transmit information relating to multiple candidate Physical Uplink Control Channel (PUCCH) resources in a first Radio Access Technology (RAT) via higher-layer signaling.

[0046] According to the implementation, the processor can be configured to send downlink control information (DCI) for scheduling the Physical Uplink Shared Channel (PUSCH) in the second RAT.

[0047] According to an implementation, DCI may include a bit field indicating the candidate PUCCH resources included in a plurality of candidate PUCCH resources.

[0048] According to the implementation method, the processor can be configured to receive PUSCH.

[0049] According to the implementation, rate matching can be applied to REs that overlap with candidate PUCCH resources among the resource elements (REs) included in the PUSCH.

[0050] The various embodiments described above are merely some preferred embodiments of this disclosure, and based on the detailed description below, several embodiments reflecting the technical features of various embodiments of this disclosure can be derived and understood by those skilled in the art.

[0051] [Beneficial effects of the invention]

[0052] Various embodiments of this disclosure can provide methods for transmitting and receiving signals in a communication system and apparatus for supporting such methods.

[0053] Various embodiments of this disclosure can provide rate matching and / or puncturing methods for different radio access technologies (RATs) and / or between RATs in a communication system, as well as means for supporting such methods.

[0054] Various embodiments of this disclosure may provide a method for indicating a rate matching mode for PUCCH resources with low overhead, and apparatus for supporting the method.

[0055] Various embodiments of this disclosure can minimize the waste of uplink resources.

[0056] In spectrum-sharing scenarios, various implementations of this disclosure can maximize uplink throughput.

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

[0058] The accompanying drawings are provided to aid in understanding the embodiments of this disclosure and its detailed description. The technical features of these embodiments are not limited to the specific drawings, and the features shown in each drawing can be combined with each other to form new embodiments. Reference numerals in each drawing denote structural elements.

[0059] Figure 1 This is a diagram illustrating the basic structure of the time-frequency domain in a wireless communication system according to an embodiment of the present disclosure.

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

[0061] Figure 3 This is a diagram illustrating an example of the configuration of the bandwidth portion (BWP) in a wireless communication system according to an embodiment of the present disclosure.

[0062] Figure 4 This diagram illustrates the wireless protocol structure of the base station and the UE in a wireless communication system according to embodiments of the present disclosure, under single cell, carrier aggregation, and dual connectivity scenarios.

[0063] Figure 5 This is a diagram illustrating a method by which a base station and a UE perform data transmission / reception by taking into account downlink data channels and rate matching resources according to an embodiment of the present disclosure.

[0064] Figure 6 This is a diagram illustrating an example of the configuration of the control resource set of the downlink control channel in a wireless communication system according to an embodiment of the present disclosure.

[0065] Figure 7 This is a diagram illustrating an example of the basic units that constitute the time and frequency resources of a downlink control channel that can be used in 5G.

[0066] Figure 8 This is a diagram illustrating an example of frequency domain resource allocation for a PDSCH or PUSCH in a wireless communication system according to an embodiment of the present disclosure.

[0067] Figure 9 This is a diagram illustrating the VRB-PRB interleaving scheme of PDSCH in an FDRA type-1 resource allocation according to an embodiment of this disclosure.

[0068] Figure 10 This is a diagram illustrating an example of time-domain resource allocation for a PDSCH in a wireless communication system according to an embodiment of the present disclosure.

[0069] Figure 11 This is a diagram illustrating an example of an LTE / NR DSS scenario to which embodiments of this disclosure are applicable.

[0070] Figure 12 This is a diagram illustrating an example of LTE PUCCH allocation applicable to embodiments of this disclosure.

[0071] Figure 13 This is a diagram illustrating an example of an LTE / NR DSS scenario to which embodiments of this disclosure are applicable.

[0072] Figure 14 This is a diagram illustrating an example of an LTE / NR DSS scenario to which embodiments of this disclosure are applicable.

[0073] Figure 15 An example of a rate matching method in a communication system to which embodiments of this disclosure apply is shown.

[0074] Figure 16 This is a diagram illustrating an example of the signaling process between a UE and a base station according to an embodiment of this disclosure.

[0075] Figure 17 This is a diagram illustrating an example of RRC parameters according to an embodiment of this disclosure.

[0076] Figure 18 This is a diagram illustrating an example of a bit field in a DCI according to an embodiment of the present disclosure.

[0077] Figure 19 This is a diagram illustrating an example of the relationship between a bitmap included in a MAC CE and a bitmap included in a DCI according to an embodiment of this disclosure.

[0078] Figure 20 This is a diagram illustrating an example of the relationship between a bitmap included in a MAC CE and a bitmap included in a DCI according to an embodiment of this disclosure.

[0079] Figure 21 This is a diagram illustrating a DM-RS suitable for PUSCH transmission according to an embodiment of the present disclosure.

[0080] Figure 22 This is a diagram illustrating a DM-RS suitable for PUSCH transmission according to an embodiment of the present disclosure.

[0081] Figure 23 This is a diagram illustrating a DM-RS suitable for PUSCH transmission according to an embodiment of the present disclosure.

[0082] Figure 24 This is a diagram illustrating a DM-RS suitable for PUSCH transmission according to an embodiment of the present disclosure.

[0083] Figure 25 This is a diagram illustrating an example of an operation flowchart of a UE according to an embodiment of the present disclosure.

[0084] Figure 26 This is a diagram illustrating an example of an operation flowchart of a base station according to an embodiment of the present disclosure.

[0085] Figure 27 This is a diagram illustrating the structure of a UE in a wireless communication system according to an embodiment of the present disclosure.

[0086] Figure 28 This is a diagram illustrating the structure of a base station in a wireless communication system according to an embodiment of the present disclosure. Detailed Implementation

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

[0088] In describing embodiments of this disclosure, descriptions of technical content known in the art and not directly related to this disclosure will be omitted. This is to more clearly convey the subject matter of this disclosure without obscuring it by omitting unnecessary descriptions.

[0089] For the same reason, some elements are exaggerated, omitted, or shown schematically in the accompanying drawings. Furthermore, the size depicted for each element does not perfectly reflect its actual size. In the drawings, identical or corresponding elements are given the same reference numerals.

[0090] The advantages and features of this disclosure, as well as the ways in which they are implemented, will become apparent from the following detailed description of embodiments and from the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to make this disclosure comprehensive and complete, and to fully convey the scope of this disclosure to those skilled in the art. This disclosure is defined only by the scope of the claims. Throughout this disclosure, the same reference numerals are used to denote the same elements. Furthermore, detailed descriptions will be omitted if it is determined that a particular function or configuration unnecessarily obscures the subject matter of this disclosure. Additionally, the terminology used herein is defined in consideration of the functions described in this disclosure and may vary depending on the intent or habit of the user or operator. Therefore, definitions should be based on the content throughout this disclosure.

[0091] In this disclosure, although the implementation methods are described using terms found in some communication standards (e.g., Long Term Evolution (LTE) and New Radio (NR) as defined by the 3rd Generation Partnership Project (3GPP)), this is merely exemplary for illustrative purposes. The implementation methods of this disclosure can be readily modified and applied to other communication systems. That is, this disclosure is not limited to 5G or LTE communication systems, but can also be applied to 6G and subsequent communication systems.

[0092] In this disclosure, a base station refers to an entity that performs resource allocation for a terminal and can be at least one of a gNode B (gNB), eNode B (eNB), Node B, base station (BS), radio access unit, base station controller, or a node on a network. Furthermore, a terminal can include a user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. In this disclosure, downlink (DL) refers to the radio transmission path of a signal from the base station to the terminal, while uplink (UL) refers to the radio transmission path of a signal from the terminal to the base station. Additionally, in the following description, LTE or LTE-A systems are described as examples, but embodiments of this disclosure can also be applied to other communication systems with similar technical backgrounds or channel types. Examples of such communication systems may include fifth-generation mobile communication technologies (5G, New Radio, NR) developed after LTE-A, and in the following description, 5G covers existing LTE, LTE-A, or other similar services. Furthermore, based on the determination of those skilled in the art, embodiments of this disclosure can also be applied to other communication systems with modifications without significantly departing from the scope of this disclosure.

[0093] It will be understood that each box in the flowchart illustration, and combinations of boxes in the flowchart illustration, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate means for implementing the function specified in the flowchart box. These computer program instructions can also be stored in a computer-usable or computer-readable storage medium that can direct the computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-usable or computer-readable storage medium produce an article of writing including instruction means that implement the function specified in the flowchart box. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus, thereby producing a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the function specified in the flowchart box.

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

[0095] The term "unit" as used in this implementation refers to a software component or hardware component, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC), and a "unit" performs certain tasks. However, a "unit" is not limited to software or hardware. A "unit" may be configured to reside on an addressable memory medium and to execute on one or more processors. Therefore, a "unit" may include, for example, components (such as software components, object-oriented software components, class components, and task components), processes, functions, attributes, flows, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided in components and "units" may be combined into fewer components or "units," or further separated into additional components or "units." Furthermore, components and "units" may be implemented as one or more central processing units (CPUs) in an operating device or secure multimedia card. Additionally, in this implementation, a "unit" may include one or more processors.

[0096] Wireless communication systems have expanded beyond their original role of providing voice-oriented services and have evolved into broadband wireless communication systems that provide high-speed and high-quality packet data services based on communication standards such as 3GPP's High Speed ​​Packet Access (HSPA), Long Term Evolution (LTE or Evolved Universal Terrestrial Radio Access (E-UTRA)) and LTE-Advanced (LTE-A), 3GPP2's High Rate Packet Data (HRPD) and Ultra Mobile Broadband (UMB), and IEEE's 802.16e.

[0097] As a typical example of a broadband wireless communication system, the LTE system employs Orthogonal Frequency Division Multiplexing (OFDM) in the downlink (DL) and Single-Carrier Frequency Division Multiple Access (SC-FDMA) in the uplink (UL). The uplink refers to the radio link through which a User Equipment (UE) or Mobile Station (MS) transmits data or control signals to a Base Station (BS or eNode B), and the downlink refers to the radio link through which the Base Station transmits data or control signals to the UE. These multiple access schemes can distinguish the data or control information of each user by allocating and manipulating time-frequency resources for transmitting data or control information, ensuring that they do not overlap, i.e., establishing orthogonality.

[0098] As the future communication system following LTE, 5G communication systems should be able to freely reflect the various needs of users, service providers, and others, and therefore should support services that simultaneously meet diverse requirements. Services considered for 5G communication systems include enhanced mobile broadband (eMBB) communication, massive machine-type communication (mMTC), and ultra-reliable low-latency communication (URLLC).

[0099] eMBB aims to provide data rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro systems. For example, in a 5G communication system, from the perspective of a single base station, eMBB should be able to provide a peak data rate of 20 Gbps in the downlink and 10 Gbps in the uplink. Furthermore, 5G communication systems should provide increased user-aware data rates for the UE while delivering peak data rates. To meet this requirement, improvements to various transmit and receive technologies are needed, including further enhanced multiple-input multiple-output (MIMO) transmission technology. Additionally, while LTE uses a maximum transmission bandwidth of 20 MHz in the 2 GHz band to transmit signals, 5G communication systems can meet the required data rates by using a wider frequency bandwidth than 20 MHz in the 3 GHz to 6 GHz or 6 GHz or higher frequency bands.

[0100] Furthermore, in 5G communication systems, mMTC is considered to support application services such as the Internet of Things (IoT). To efficiently deliver IoT, mMTC needs to support a large number of UEs within a cell, enhance UE coverage, increase battery life, and reduce UE costs. Since IoT provides communication capabilities by connecting to various sensors and devices, it should be able to support a large number of UEs within a cell (e.g., 1,000,000 UEs / km). 2 Additionally, mMTC-enabled UEs may require wider coverage than other services offered in 5G communication systems because, due to the nature of the service, the UE is likely to be located in shadow areas not covered by the cell, such as the basement of a building. mMTC-enabled UEs should be configured to be inexpensive and may require very long battery life (e.g., 10 to 15 years) because it is difficult to frequently replace the UE's battery.

[0101] Finally, URLLC is a cellular-based wireless communication service for a specific purpose (mission-critical). Examples include services for remote control of robots or machines, industrial automation, unmanned aerial vehicles, remote healthcare, and emergency alerts. Therefore, the communication provided by URLLC should offer ultra-low latency and ultra-high reliability. For example, services supporting URLLC should meet an air interface latency of less than 0.5 milliseconds and simultaneously have 10... -5 Or a lower packet error rate requirement. Therefore, for services supporting URLLC, 5G systems should provide shorter transmission time intervals (TTIs) than other services, and at the same time, may need to allocate wide resources in the frequency band to ensure the design requirements of communication link reliability.

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

[0103] In the following text, “a / b” can be understood as at least one of “a” and “b”.

[0104] [NR Time and Frequency Resources]

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

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

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

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

[0109] exist Figure 2 The diagram illustrates an example of the structure of frame 200, subframe 201, and time slot 202. A frame 200 can be defined as 10 ms. A subframe 201 can be defined as 1 ms, and therefore a frame 200 can consist of a total of 10 subframes 201. A time slot 202 or 203 can be defined as 14 OFDM symbols (i.e., the number of symbols per time slot). =14). A subframe 201 may consist of one or more time slots 202 and 203, and the number of time slots 202 and 203 in each subframe 201 may vary depending on the configuration value µ 204 or 205 for the subcarrier spacing. Figure 2In the examples, cases 204 (μ=0) and 205 (μ=1) are shown as subcarrier spacing configuration values. In case 204 (μ=0), a subframe 201 can consist of one time slot 202, and in case 205 (μ=1), a subframe 201 can consist of two time slots 203. That is, the number of time slots in each subframe ( The number of time slots per frame can vary depending on the subcarrier spacing configuration value μ, and therefore, the number of time slots per frame ( They can be different. The μ value is configured according to each subcarrier spacing. and It can be defined as shown in Table 1 below.

[0110] [Table 1]

[0111] [Bandwidth Component (BWP)]

[0112] The BWP configuration in the 5G communication system will now be described in detail with reference to the accompanying drawings.

[0113] Figure 3 This is a diagram illustrating an example of a BWP configuration in a wireless communication system according to an embodiment of the present disclosure.

[0114] exist Figure 3 The diagram illustrates an example where UE bandwidth 300 is configured with two BWPs (i.e., BWP#1 301 and BWP#2 302). A base station can configure one or more BWPs for a UE, and the information in Table 2 below can be configured for each BWP.

[0115] [Table 2]

[0116] The above examples are not limiting, and various parameters related to the BWP can be configured for the UE in addition to the configuration information described above. This information can be sent from the base station to the UE via higher-layer signaling (e.g., Radio Resource Control (RRC) signaling). At least one of the configured BWPs can be activated. Whether a configured BWP is activated can be semi-statically sent from the base station to the UE via RRC signaling, or dynamically sent via downlink control information (DCI).

[0117] According to some implementations, prior to RRC connection, the UE can configure an initial BWP for initial access from the base station via the Master Information Block (MIB). More specifically, during the initial access phase, the UE can receive configuration information about the Control Resource Set (CORESET) and search space via the MIB. Through this CORESET and search space, the UE can send a PDCCH for receiving system information required for initial access (which may correspond to the Residual System Information (RMSI) or System Information Block 1 (SIB1)). The CORESET and search space configured via the MIB can be considered as ID 0. The base station can notify the UE of the configuration information for CORESET#0 via the MIB, such as frequency allocation information, time allocation information, and parameter set. Additionally, the base station can notify the UE of the configuration information regarding the monitoring period and timing of CORESET#0 via the MIB, i.e., the configuration information regarding search space #0. The UE can consider the frequency domain obtained from the MIB and configured as CORESET#0 as the initial BWP for initial access. In this case, the ID of the initial BWP can be considered as 0.

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

[0119] According to some implementation methods, when the bandwidth supported by the UE is less than the system bandwidth, this situation can be supported through BWP configuration. For example, the base station can configure the frequency position of the BWP to the UE (configuration information 2), so that the UE can send or receive data at a specific frequency position within the system bandwidth.

[0120] Furthermore, according to some implementation methods, a base station can configure multiple BWPs for a UE to support different parameter sets. For example, for a given UE, to support data transmission / reception using subcarrier spacings of 15 kHz and 30 kHz, two BWPs can be configured with subcarrier spacings of 15 kHz and 30 kHz, respectively. Different BWPs can be used for frequency division multiplexing (FDM), and the BWP configured with the corresponding subcarrier spacing can be activated when data needs to be transmitted or received with a specific subcarrier spacing.

[0121] Additionally, according to some implementations, the base station can configure a BWP with different bandwidth sizes for the UE to reduce UE power consumption. For example, considerable power consumption may occur when the UE supports a fairly large bandwidth (e.g., 100 MHz) and always transmits or receives data through that bandwidth. In particular, monitoring an unnecessary downlink control channel with a large bandwidth of 100 MHz can be very inefficient in terms of power consumption when there is no service. To reduce UE power consumption, the base station can configure a BWP with a relatively small bandwidth (e.g., a 20 MHz BWP). When there is no service, the UE can perform monitoring operations in a 20 MHz BWP, and when data is generated, the UE can transmit or receive data in a 100 MHz BWP according to instructions from the base station.

[0122] In the method of configuring the BWP, the UE can receive configuration information about the initial BWP via the MIB during the initial access phase before RRC connection. More specifically, the UE can be configured with a CORESET for the downlink control channel based on the MIB of the Physical Broadcast Channel (PBCH), through which DCI for scheduling System Information Blocks (SIBs) can be transmitted. The bandwidth of the CORESET configured via the MIB can be regarded as the initial BWP, and the UE can receive the Physical Downlink Shared Channel (PDSCH) through the configured initial BWP, through which SIBs are transmitted. The initial BWP can be used for other System Information (OSI), paging, and random access, and for receiving SIBs.

[0123] [Bandwidth Partial (BWP) Switching]

[0124] If one or more BWPs have already been configured for the UE, the base station can indicate to the UE to switch (or change or transform) the BWP by using the BWP indicator field in the DCI. As an example, in Figure 3 If the UE's currently active BWP is BWP#1 301, the base station can indicate BWP#2 302 to the UE via the BWP indicator in the DCI, and the UE can perform a BWP handover to BWP#2 302 indicated by the BWP indicator in the received DCI.

[0125] As mentioned above, since DCI-based BWP handover can be indicated by the DCI scheduling PDSCH or PUSCH, the UE receiving the BWP handover request needs to smoothly receive or transmit the DCI-scheduled PDSCH or PUSCH in the BWP being handed over without any difficulty. For this purpose, the standard specifies the delay time (T) required during BWP handover. BWPThe requirements for (e.g., can be defined as shown in Table 3 below).

[0126] [Table 3]

[0127] The BWP handover latency requirement supports either Type 1 or Type 2, depending on the UE's capabilities. The UE can report the supported BWP handover latency types to the base station.

[0128] According to the BWP handover delay time requirements, when the UE is in the time slot n When the UE receives the DCI including the BWP handover indicator, it can do so no later than the time slot. n+T BWP The handover to the new BWP indicated by the BWP handover indicator is completed at the specified time, and data channel transmission or reception scheduled by the corresponding DCI can be performed in the new BWP. When the base station intends to schedule data channels in the new BWP, the base station can consider the UE's BWP handover delay time. T BWP This method determines the time-domain resource allocation for the data channel. In other words, when scheduling a data channel in a new BWP, the base station can schedule the corresponding data channel after the BWP handover delay time in the method for determining the time-domain resource allocation for the data channel. Therefore, the UE may not expect the DCI indication instructing the BWP handover to be less than the BWP handover delay time. T BWP The time slot offset (K0 or K2) value.

[0129] If the UE receives a DCI indicating a BWP handover (e.g., DCI format 1_1 or 0_1), the UE may refrain from any transmission or reception during the time interval from the third symbol of the time slot used to receive the PDCCH including that DCI to the start time of the time slot indicated by the time slot offset (K0 or K2) value indicated by the time domain resource allocation indicator field in that DCI. For example, if the UE is in time slot n The DCI indicating BWP switching is received, and if the time slot offset indicated by the DCI is... K Then the UE can travel from the third symbol of time slot n to time slot n. n + K Previous symbols (e.g., time slots) n + K The last symbol of -1 does not perform any sending or receiving.

[0130] [CA / DC related]

[0131] Figure 4This is a diagram illustrating the radio protocol structure of the base station and UE in the cases of single cell, carrier aggregation, and dual connectivity according to embodiments of the present disclosure.

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

[0133] The main functions of NR SDAP S25 or S70 may include some of the following: - Functionality for transmitting user data (transmission of user plane data); - Functionality for mapping between QoS streams and data bearers for both uplink and downlink (mapping between QoS streams and DRBs for both DL and UL). - The ability to tag QoS flow IDs in both uplink and downlink (tag QoS flow IDs in both DL and UL packets); and - For uplink SDAP PDUs, the function of mapping reflective QoS flows to data bearers (for UL SDAPPDUs, the mapping of reflective QoS flows to DRBs).

[0134] For SDAP layer devices, RRC messages can be used to configure the UE regarding whether to use the header of an SDAP layer entity, or whether to use the functionality of an SDAP layer entity for each PDCP layer entity, each bearer, or each logical channel. If the SDAP header is configured, the 1-bit NAS-reflective QoS indicator and the 1-bit AS-reflective QoS indicator in the SDAP header can indicate to the UE that it can update or reconfigure the mapping information between uplink and downlink QoS flows and data bearers. The SDAP header can include QoS flow ID information indicating QoS. QoS information can be used as data processing priority information, scheduling information, etc., to support seamless service.

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

[0136] - Header compression and decompression functions (header compression and decompression: ROHC only); - User data transmission function (transmission of user data); - Order delivery function (order delivery of upper-layer PDUs); - Out-of-order delivery function (out-of-order delivery of upper-layer PDUs); - Reordering function (for reordering received PDCP PDUs). - Duplicate detection function (duplicate detection of lower-level SDU); - Retransmission function (retransmission of PDCP SDU); - Encryption and decryption functions (encryption and decryption); and - Timer-based SDU dropping function (timer-based SDU dropping in the uplink).

[0137] In the above description, the reordering function of the NR PDCP entity refers to the function of reordering PDCP PDUs received from the lower layer based on the PDCP sequence number (SN), and may include the function of delivering data to the upper layer in the reordered order. Alternatively, the reordering function of the NR PDCP entity may include the following functions: delivering data immediately regardless of order, recording lost PDCP PDUs by reordering them, performing a status report for lost PDCP PDUs to the sending side, or requesting retransmission of lost PDCP PDUs.

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

[0139] - Data transmission function (transmission of upper-layer PDUs); - Order delivery function (order delivery of upper-layer PDUs); - Out-of-order delivery function (out-of-order delivery of upper-layer PDUs); - ARQ functionality (error correction via ARQ); - Cascading, segmentation, and reassembly functionality (cascading, segmentation, and reassembly of RLC SDUs); - Re-segmentation function (re-segmentation of RLC data PDUs); - Reordering function (reordering of RLC data PDUs); - Duplicate detection function (duplicate detection); - Error detection function (protocol error detection); - RLC SDU discard function (RLC SDU discard); and - RLC Reconstruction Function (RLC Reconstruction).

[0140] In the above description, the in-order delivery function of the NR RLC entity refers to the function of delivering RLC PDUs received from the lower layer to the upper layer in sequence. The in-order delivery function of the NR RLC entity may include the following functions: when receiving an original RLC SDU by segmenting it into multiple RLC SDUs, reassembling and delivering these multiple RLC SDUs. The in-order delivery function may include the following functions: reordering received RLC PDUs based on the RLC sequence number (SN) or PDCP SN; recording lost RLC PDUs through reordering; performing a status report for lost RLC PDUs to the transmitting side; and requesting retransmission of lost RLC PDUs. In the case of lost RLC SDUs, the in-order delivery function of the NR RLC entity may include the following function: delivering only RLC SDUs preceding the lost RLC SDU in sequence to the upper layer. Alternatively, even in the event of lost RLC SDUs, the in-order delivery function can include the following: delivering all RLC SDUs received before the timer starts to the upper layer in order, or delivering all RLC SDUs received up to the current timer to the upper layer in order. Additionally, RLC PDUs can be processed in the order they were received (regardless of sequence number order) and delivered to the PDCP entity out of order. In the case of segmentation, segments stored in a buffer or to be received later can be reassembled into a complete RLC PDU, which is then processed and delivered to the PDCP entity. The NR RLC layer may not include cascading functionality, and this functionality can be implemented in the NR MAC layer or replaced by multiplexing functionality of the NRMAC layer.

[0141] In the above description, the out-of-order delivery function of an NR RLC device refers to the function of directly delivering RLC SDUs received from a lower layer to an upper layer regardless of their order. When receiving an original RLC SDU by segmenting it into multiple RLC SDUs, the out-of-order delivery function can include the following functions: reassembling and delivering multiple RLC SDUs; storing the RLC SN or PDCP SN of the received RLC PDUs; reordering the sequence; and recording any lost RLC PDUs.

[0142] NR MAC S40 or S55 can connect to multiple NR RLC layer entities configured in a UE, and the main functions of NR MAC can include some of the following functions.

[0143] - Mapping function (mapping between logical channels and transport channels); - Multiplexing / demultiplexing function (MAC SDU multiplexing / demultiplexing); - Scheduling information reporting function (Scheduling information report); - HARQ functionality (error correction via HARQ); - Logical channel priority adjustment function (priority processing between logical channels of a UE). - UE priority adjustment function (performs priority processing among UEs through dynamic scheduling). - MBMS service identification function (MBMS service identification); - Transmission format selection function (transmission format selection); and - Fill function (fill).

[0144] The NR PHY layer S45 or S50 can perform the following operations: channel coding and modulation on upper-layer data to obtain OFDM symbols and transmit them through a wireless channel; or demodulate and channel decode OFDM symbols received through a wireless channel and transmit them to the upper layer.

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

[0146] [Rate matching / punch-related]

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

[0148] Used to send specific symbol sequences A Time and frequency resources A With specific time and frequency resources B In cases of overlap, considering the resource A and resources B Resources in overlapping areas C It can be considered for use in channels. A The rate matching or punching operation for sending and receiving. Specific operations can be followed in the details below.

[0149] Rate matching operation

[0150] -Base stations can use channels A Mapped to the entire resource only A The exclusion of resources B Resources corresponding to overlapping areas C Use the remaining resource area to send the channel A To send symbol sequences to the UE A For example, if the symbol sequence A Composed of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A It consists of {resource #1, resource #2, resource #3, resource #4}, and resources B Composed of {resource #3, resource #5}, the base station can sequentially transmit the symbol sequence. A Mapped to {resource #1, resource #2, resource #4}, they are resources A Excluded from resources C The corresponding remaining resources of {resource #3}. As a result, the base station can transmit the symbol sequence by mapping the symbol sequence {symbol #1, symbol #2, symbol #3} to {resource #1, resource #2, resource #4} respectively.

[0151] The UE can base its data on the symbol sequence received from the base station. A The scheduling information is used to determine the resources A and resources B Therefore, it can be determined as a resource A and resources B Resources in overlapping areas C The UE can receive symbol sequences based on the following assumptions. A Symbolic sequence A Mapped to the entire resource A Resources were excluded C The remaining area is then sent within it. For example, if the symbol sequence... A Composed of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A It consists of {resource #1, resource #2, resource #3, resource #4}, and resources B Composed of {Resource #3, Resource #5}, the UE can receive the symbol sequence based on the following assumptions. A Symbolic sequence A They are sequentially mapped to {resource #1, resource #2, resource #4}, which are resources. A Excluded from resources CThe remaining resources corresponding to {resource #3}. As a result, the UE can perform subsequent receive operations assuming that the symbol sequence {symbol #1, symbol #2, symbol #3} is mapped to {resource #1, resource #2, resource #4} and transmitted therein.

[0152] Drilling operation

[0153] Used to send symbol sequences to the UE A The entire resource A Existence and Resources B Resources corresponding to overlapping areas C In this case, the base station can transmit symbol sequences A Mapped to the entire resource A However, it is possible to use only the entire resource A Resources were excluded C Sending is performed in the remaining resource area, not in the resource area. C Sending is performed in the corresponding resource area. For example, if the symbol sequence... A Composed of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A It consists of {resource #1, resource #2, resource #3, resource #4}, and resources B Composed of {resource #3, resource #5}, the base station can transmit the symbol sequence. A {symbol #1, symbol #2, symbol #3, symbol #4} are mapped to resources respectively. A {Resource #1, Resource #2, Resource #3, Resource #4}, and can only send the symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to {Resource #1, Resource #2, Resource #4}, where {Resource #1, Resource #2, Resource #4} is a resource. A Excluded from resources C The remaining resources corresponding to {resource #3}, without sending the mapping to the corresponding resource. C {Resource #3} is {symbol #3}. As a result, the base station can transmit the symbol sequence by mapping the symbol sequence {symbol #1, symbol #2, symbol #4} to {resource #1, resource #2, resource #4} respectively.

[0154] The UE can base its data on the symbol sequence received from the base station. A The scheduling information is used to determine the resources A and resources B Therefore, it can be determined as a resource A and resources B Resources in overlapping areas C The UE can receive symbol sequences based on the following assumptions. A Symbol sequence A is mapped to the entire resource. AHowever, only in resources A Resources were excluded C Send it in the remaining region. For example, if the symbol sequence A Composed of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A It consists of {resource #1, resource #2, resource #3, resource #4}, and resources B If the symbol sequence consists of {resource #3, resource #5}, then the UE can assume a symbol sequence. A {Symbol #1, Symbol #2, Symbol #3, Symbol #4} are mapped to {Resource #1, Resource #2, Resource #3, Resource #4} respectively, but are mapped to the resources corresponding to... C {Resource #3} {Symbol #3} is not sent. Furthermore, by assuming the sequence is mapped and sent, the UE can receive information related to the resource. A The middle excludes resources C The remaining resources {resource #1, resource #2, resource #4} of {resource #3} correspond to the symbol sequence {symbol #1, symbol #2, symbol #4}. The UE can perform subsequent reception operations assuming that the symbol sequence {symbol #1, symbol #2, symbol #4} is mapped to {resource #1, resource #2, resource #4} and transmitted therein.

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

[0156] Figure 5 This diagram illustrates how a base station and a UE perform data transmission and reception by taking into account downlink data channel and rate matching resources.

[0157] Figure 5A downlink data channel (PDSCH) 501 and rate matching resource 502 are illustrated. The base station can configure one or more rate matching resources 502 for the UE via higher-layer signaling (e.g., RRC signaling). The configuration information for the rate matching resource 502 may include time-domain resource allocation information 503, frequency-domain resource allocation information 504, and periodic information 505. In the following text, the bitmap corresponding to the frequency-domain resource allocation information 504 is referred to as the "first bitmap," the bitmap corresponding to the time-domain resource allocation information 503 is referred to as the "second bitmap," and the bitmap corresponding to the periodic information 505 is referred to as the "third bitmap." If all or part of the time and frequency resources of the scheduled data channel 501 overlap with the configured rate matching resource 502, the base station can rate match the data channel 501 on a portion of the rate matching resource 502 for transmission, and the UE can perform reception and decoding by assuming that the data channel 501 is rate-matched in a portion of the rate matching resource 502.

[0158] The base station can dynamically notify the UE via DCI using additional configuration (corresponding to the "rate matching indicator" in the DCI format described above) whether to perform rate matching for the data channel in the configured rate matching resource portion. Specifically, the base station can select some of the configured rate matching resources and group them into rate matching resource groups, and can indicate to the UE whether to perform rate matching for the data channel for each rate matching resource group using a bitmap scheme in the DCI. For example, if four rate matching resources RMR#1, RMR#2, RMR#3, and RMR#4 are configured, the base station can configure RMG#1={RMR#1, RMR#2} and RMG#2={RMR#3, RMR#4} as rate matching groups, and can use 2 bits in the bitmap form of the DCI field to indicate to the UE whether to perform rate matching in RMG#1 and RMG#2 respectively. For example, if rate matching is to be performed, the base station can indicate "1", and if rate matching is not to be performed, the base station can indicate "0".

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

[0160] RB symbol level

[0161] Through higher-layer signaling, a UE can be configured with up to four RateMatchPatterns per BWP, and a RateMatchPattern can include the following information.

[0162] - Reserved resources within a BWP can include resources where time and frequency resource regions are configured using a combination of RB-level and symbol-level bitmaps. Reserved resources can span one or two time slots. Additionally, a time-domain pattern (periodicityAndPattern) can be configured, where time and frequency regions defined by a pair of RB-level and symbol-level bitmaps are repeated.

[0163] - This may include a time-frequency domain resource region in the BWP that is configured as a control resource set (CORESET), and a resource region corresponding to a time-domain mode configured by the search space configuration, in which the resource region is repeated.

[0164] RE Level

[0165] The UE can be configured with the following information through higher-level signaling.

[0166] - Configuration information for the RE corresponding to the LTE cell-specific reference signal or common reference signal (CRS) mode (lte-CRS-ToMatchAround) may include the number of LTE CRS ports (nrofCRS-Ports), the LTE-CRS-vshift value (v-shift), the center subcarrier position information of the LTE carrier relative to the reference frequency point (e.g., reference point A) (carrierFreqDL), the bandwidth information of the LTE carrier (carrierBandwidthDL), and the subframe configuration information corresponding to the Multicast Broadcast Single Frequency Network (MBSFN) (mbsfn-SubframeConfigList), etc. Based on this information, the UE can determine the position of the CRS in the NR slot corresponding to the LTE subframe.

[0167] - This can include configuration information for resource sets in the BWP that correspond to one or more Zero Power (ZP) CSI-RS.

[0168] [LTE CRS rate matching related]

[0169] The rate matching process for the aforementioned LTE CRS will be described in detail below. For the coexistence of Long Term Evolution (LTE) and New RAT (NR) (LTE-NR coexistence), NR provides the functionality to configure LTE Cell-Specific Reference Signal (CRS) modes for NR UEs. Specifically, the CRS mode can be provided via RRC signaling, which includes at least one parameter within the ServingCellConfig Information Element (IE) or the ServingCellConfigCommon IE. Examples of these parameters include lte-CRS-ToMatchAround, lte-CRS-PatternList1-r16, lte-CRS-PatternList2-r16, and crs-RateMatch-PerCORESETPoolIndex-r16.

[0170] In Rel-15NR, a feature was provided where one CRS pattern could be configured for each serving cell via the lte-CRS-ToMatchAround parameter. In Rel-16NR, this feature was extended to allow multiple CRS patterns to be configured for each serving cell. Specifically, one CRS pattern per LTE carrier can be configured for a UE configured with a single transmit and receive point (single TRP), and two CRS patterns per LTE carrier can be configured for a UE configured with multiple TRPs. For example, for a UE configured with a single TRP, up to three CRS patterns per serving cell can be configured via the lte-CRS-PatternList1-r16 parameter. As another example, for a UE configured with multiple TRPs, a CRS pattern can be configured for each TRP. That is, a CRS pattern for TRP1 can be configured via the lte-CRS-PatternList1-r16 parameter, and a CRS pattern for TRP2 can be configured via the lte-CRS-PatternList2-r16 parameter. Meanwhile, when two TRPs are configured as described above, whether the CRS modes of both TRP1 and TRP2 are applied to a specific Physical Downlink Shared Channel (PDSCH) or only the CRS mode of one TRP is applied is determined by the crs-RateMatch-PerCORESETPoolIndex-r16 parameter. If the crs-RateMatch-PerCORESETPoolIndex-r16 parameter is set to "Enabled", then only the CRS mode of one TRP is applied; otherwise, the CRS mode of both TRPs is applied.

[0171] Table 4 shows the ServingCellConfig IE including CRS mode, and Table 5 shows the RateMatchPatternLTE-CRS IE including at least one parameter for CRS mode.

[0172] [Table 4]

[0173] [Table 5]

[0174] [PDCCH: About DCI]

[0175] Next, we will describe downlink control information (DCI) in 5G systems in detail.

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

[0177] DCI messages can be transmitted via the Physical Downlink Control Channel (PDCCH) after channel coding and modulation. Cyclic Redundancy Check (CRC) can be appended to the DCI message payload, and the CRC can be scrambled using a Radio Network Temporary Identifier (RNTI) corresponding to the UE's identifier. Different RNTIs can be used depending on the purpose of the DCI message (e.g., UE-specific data transmission, power control command, or random access response). That is, the RNTI is not explicitly transmitted but is included in the CRC calculation process. After receiving a DCI message transmitted via the PDCCH, the UE can check the CRC using the assigned RNTI, and if the CRC check is successful, the UE can identify that the corresponding message was sent to the UE.

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

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

[0180] [Table 6]

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

[0182] [Table 7]

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

[0184] [Table 8]

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

[0186] [Table 9]

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

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

[0189] Figure 6 This is a diagram illustrating an example of a control resource set (CORESET) for transmitting downlink control channels in a 5G wireless communication system.

[0190] Figure 6 An example is shown where two CORESETs (CORESET#1 601 and CORESET#2 602) are configured within the UE BWP 610 in the frequency domain and within a time slot 620 in the time domain. CORESETs 601 and 602 can be configured for a specific frequency resource 603 within the entire UE BWP 610 in the frequency domain. One or more OFDM symbols can be configured in the time domain and defined as the CORESET duration 604. Figure 6 In the example shown, CORESET#1 601 is configured with a CORESET duration of two symbols, and CORESET#2 602 is configured with a CORESET duration of one symbol.

[0191] The base station can configure the CORESET in 5G for the UE via higher-layer signaling (e.g., System Information (SI), Master Information Block (MIB), Radio Resource Control (RRC) signaling). Configuring the CORESET for the UE means providing information such as the CORESET identifier, the frequency location of the CORESET, and the symbol length of the CORESET. For example, it may include the information in Table 10 below.

[0192] [Table 10]

[0193] In Table 10, the tci-StatesPDCCH (Transmission Configuration Indicator (TCI) status) configuration information may include information on one or more Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block indices or Channel State Information Reference Signal (CSI-RS) indices that have a QCL relationship with the DMRS transmitted in the corresponding CORESET.

[0194] Figure 7 This is a diagram illustrating an example of the basic units that constitute the time and frequency resources of a downlink control channel that can be used in 5G. According to... Figure 7The basic unit constituting the time and frequency resources of the control channel can be called a resource element group (REG) 703, and REG 703 can be defined as an OFDM symbol 701 in the time domain and a physical resource block (PRB) 702 (i.e., 12 subcarriers) in the frequency domain. The base station can construct the downlink control channel allocation unit by cascading REG 703.

[0195] like Figure 7 As shown, in 5G, where the basic unit for allocating downlink control channels is called a control channel element 704, one CCE 704 can be composed of multiple REG 703s. Figure 7 In the example shown, REG 703 can include 12 REs, and if a CCE 704 consists of six REG 703s, then a CCE 704 can include 72 REs. When a downlink CORESET is configured, it can consist of multiple CCE 704s, and a specific downlink control channel can be transmitted while mapping a specific downlink control channel to one or more CCE 704s according to the aggregation level (AL) in the CORESET. CCE 704s in a CORESET are distinguished by numbering, and the numbering of CCE 704s can be assigned according to a logical mapping scheme.

[0196] Figure 7 The basic unit of the downlink control channel shown (i.e., REG 703) can include both the RE mapped to by the DCI and the region mapped to by DMRS 705 (which is the reference signal used to decode the DCI). Figure 7 As shown, three DMRS 705s can be transmitted within a single REG 703. Depending on the aggregation level (AL), the number of CCEs required to transmit the PDCCH can be 1, 2, 4, 8, or 16, and different numbers of CCEs can be used to implement link adaptation for the downlink control channel. For example, if AL=L, a downlink control channel can be transmitted using L CCEs. The UE needs to detect signals when it lacks information about the downlink control channel, and a search space representing the set of CCEs is defined for blind decoding. The search space is the set of downlink control channel candidates, consisting of the CCEs the UE will attempt to decode under a given AL. Since there are various ALs where 1, 2, 4, 8, or 16 CCEs form a bundle, the UE can have multiple search spaces. The search space set can be defined as the set of search spaces under all configured aggregation levels.

[0197] The search space can be categorized into a common search space and a UE-specific search space. A group of UEs or all UEs can monitor the common search space of the PDCCH to receive cell common control information, such as system information or dynamic scheduling of paging messages. For example, monitoring the common search space of the PDCCH can be used to receive PDSCH scheduling allocation information for transmitting SIBs (including cell operator information, etc.). In the case of the common search space, since a group of UEs or all UEs need to receive the PDCCH, the common search space can be defined as a predefined set of CCEs. Monitoring the UE-specific search space of the PDCCH can be used to receive scheduling allocation information for UE-specific PDSCH or PUSCH. The UE-specific search space can be defined in a UE-specific manner as a function of the UE identifier and various system parameters.

[0198] In 5G, the base station can configure parameters for the search space used for PDCCH for the UE via higher-layer signaling (e.g., SIB, MIB, RRC signaling, etc.). For example, the base station can configure the number of PDCCH candidates under each aggregation level L, the monitoring period of the search space, the monitoring timing in symbols within the time slot of the search space, the search space type (public search space or UE-specific search space), the combination of DCI format and RNTI to be monitored in the search space, and the CORESET index of the search space. For example, the parameters may include the information in Table 11 below.

[0199] [Table 11]

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

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

[0202] In the public search space, the following combinations of DCI format and RNTI can be monitored. However, this disclosure is not limited to the following examples.

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

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

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

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

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

[0208] Within the UE-specific search space, the following combinations of DCI format and RNTI can be monitored. However, this disclosure is not limited to the following examples.

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

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

[0211] The specified RNTI can follow the definitions and uses described below.

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

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

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

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

[0216] Paging RNTI (P-RNTI): Used to schedule PDSCHs carrying paging messages.

[0217] System Information RNTI (SI-RNTI): Used to schedule PDSCHs carrying system information.

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

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

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

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

[0222] The DCI format specified above can follow the definitions shown in Table 12 below.

[0223] [Table 12]

[0224] In 5G, in CORESET p and search space set s In, aggregation level L The search space can be represented by the following formula 1.

[0225] [Formula 1]

[0226] - L Aggregation Level

[0227] - n CI Carrier index

[0228] - N CCE,p CORESET p The total number of CCEs existing in

[0229] - n μ s,f Time slot index

[0230] - M （L） s,max The number of PDCCH candidates at aggregation level L; - m s,nCI =0, ……, M （L） s,max -1: PDCCH candidate group index at aggregation level L - i=0, ……, L-1 - , , , , ,

[0231] - n RNTI UE identifier

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

[0233] In the case of a specific search space for the UE It can correspond to a value that varies based on the UE identifier (C-RNTI or ID configured for the UE by the base station) and time index.

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

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

[0236] Next, we will describe the frequency domain resource allocation (FDRA) of the Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) in NR.

[0237] Figure 8 This is a diagram illustrating an example of frequency domain resource allocation for a PDSCH or PUSCH in a wireless communication system according to an embodiment of the present disclosure.

[0238] Figure 8 Three frequency domain resource allocation methods that can be configured at higher levels in an NR wireless communication system are shown: FDRA type 0 800, FDRA type 1 805, and dynamic switching 810.

[0239] refer to Figure 8 In the case where the UE is configured to use only FDRA type 0 via higher-layer signaling, the specific DCI for scheduling PDSCH or PUSCH for the UE includes N RBG A bitmap composed of bits. The conditions for this case will be described later. In this case, N RBGThis indicates the number of Resource Block Groups (RBGs) determined by the size of the BWP allocated by the BWP indicator and the higher-level parameter rbg-Size (as shown in Table 13 below), and data is sent in the RBG indicated by "1" in the bitmap.

[0240] [Table 13]

[0241] The size of the frequency resources in the BWP can be defined as the number of RBs included in the BWP. More specifically, if the UE is instructed to allocate FDRA type 0 resources, the length of the FDRA field of the DCI received by the UE is equal to the number of RBGs (N) in the BWP. RBG ), which is Here, the first RBG in BWP includes RB, and if Then the last RBG in BWP includes One RB, otherwise, including The remaining RGB in the BWP consists of P RBs, where P is the nominal number of RBGs determined according to Table 13 above.

[0242] In case 805, where the UE is configured to use only FDRA type 1 via higher-layer signaling, the DCI for allocating PDSCH or PUSCH to the UE includes... Frequency Domain Resource Allocation (FDRA) information composed of bits. Here, This refers to the number of RBs included in the BWP. In this way, the base station can configure the starting VRB 820 and the length 825 of the frequency domain resources continuously allocated from it.

[0243] In case 810, where the UE is configured to use FDRA type 0 resource allocation and FDRA type 1 resource allocation via higher-layer signaling, a certain DCI that allocates PDSCH / PUSCH to the UE includes FDRA information. This FDRA information consists of bits representing the larger of the payload 815 used to configure FDRA type 0 resource allocation and the payloads 820 and 825 used to configure FDRA type 1 resource allocation, which are the largest values ​​between them. The conditions for this case will be described later. In this case, a bit can be added to the most significant bit (MSB) of the FDRA information in the DCI. If the bit has a value of "0", it can indicate the use of FDRA type 0 resource allocation, and if the bit has a value of "1", it can indicate the use of FDRA type 1 resource allocation.

[0244] If the FDRA type 2 resource allocation method is configured for the UE via higher-layer signaling, the FDRA type 2 resource allocation method can be indicated from the base station to the UE according to the following method.

[0245] If the UE is not configured with the higher-layer signaling vrb-ToPRB-Interleaver, the UE can connect the resources allocated to the VRB to the PRB without interleaving. If the UE is configured with the higher-layer signaling vrb-ToPRB-Interleaver, the higher-layer signaling has a value of 2 or 4, and this value can be a unit for multiple RBs used to perform interleaving. That is, RB bundles (each RB bundle consists of 2 or 4 RBs) can be used for interleaving.

[0246] If the UE is configured to... Starting from the position and in length by The i-th BWP consists of RBs, and vrb-ToPRB-Interleaver is configured as follows: Then the UE can divide the i-th BWP into Each RB bundle can be composed of RB bundles. It consists of RBs.

[0247] - In the i-th BWP, the first RB bundle can be... It consists of RBs.

[0248] - In the i-th BWP, if If the value is greater than 0, then the last RB bundle can be... It consists of RBs; otherwise, it can be composed of... L i It consists of RBs.

[0249] - In the i-th BWP, the remaining RB bundles can be... L i It consists of RBs.

[0250] In this case, the VRB can be connected to the PRB using the following method.

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

[0252] -The jth VRB bundling can be connected to the first A PRB bundle, and It can be expressed as Formula 2 below.

[0253] [Formula 2]

[0254] Figure 9 This is a diagram illustrating the VRB-PRB interleaving scheme of PDSCH in FDRA type 1 resource allocation according to an embodiment of this disclosure. Figure 9Case 910 is shown, where each of the first and last VRB bundles consists of one VRB within BWP 900 (composed of 10 RBs). Therefore, the number of VRB bundles... It can be 6, and it can be calculated using formula 2 above. Since the j-th VRB bundle can be connected to the f(j)-th PRB bundle via Equation 2, the connection from VRB bundle to PRB bundle can be performed using the result 930 calculated by Equation 2 (as shown in 920). For example, VRB bundle 1 940 can be connected to PRB bundle 3 950.

[0255] The base station can indicate RB allocation information to the UE, which includes a set of M interleaving indices.

[0256] Intertwined Index Can be made by public RB The composition, and M can be defined as shown in Table 20.

[0257] [Table 20]

[0258] Intertwined m and the RB in the bandwidth part i and public RB The relationship can be defined as follows.

[0259]

[0260] in It is the bandwidth portion of the common resource block relative to common resource block 0. μ is the subcarrier spacing index.

[0261] When the subcarrier spacing is 15kHz (μ=0), the base station can notify the UE of the RB allocation information for the interleaving set with (m0+l) indices. Furthermore, the resource allocation field can consist of a resource indicator value (RIV). When the resource indicator value is... , At that time, it can be determined by the initial interlacing m0 and the number of consecutive interlacings. It consists of, and its value is as follows.

[0262] if ,but

[0263] otherwise,

[0264] When the resource indicator value is At that time, the resource indicator value is determined by the starting interleaving index m0 andl The values ​​are composed of, and can be composed as shown in Table 15.

[0265] [Table 15]

[0266] When the subcarrier spacing is 30kHz (u=1), the base station can notify the UE of the RB allocation information in the form of a bitmap, which indicates the interleaving allocated to the UE. The bitmap is M in size, and 1 bit in the bitmap corresponds to one interleaving. For interleaving indices 0 to M-1, the interleaving bitmap can be mapped in order from MSB to LSB.

[0267] Additionally, for 15kHz and 30kHz, the least significant bit (LSB) of the FDRA field. It can indicate a contiguous set of RBs for PUSCHs scheduled in DCI format 0_1. The Y bit can consist of resource indication values ​​(RIVRBset). , In this case, the RIVRBset value can be determined by the initial RB set ( ) and the number of consecutive RB sets ( (Identify.) The RIVRBset value can be defined as follows.

[0268] if ,but

[0269] otherwise, 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 configured (or pre-configured) via higher-layer signaling.

[0270] [PDSCH / PUSCH: Related to time-domain resource allocation]

[0271] The following section describes a method for allocating time-domain resources for data channels in next-generation mobile communication systems (5G or NR systems).

[0272] The base station can configure tables for the UE via higher-layer signaling (e.g., RRC signaling) to provide time-domain resource allocation information for the downlink data channel (PDSCH: Physical Downlink Shared Channel) and the uplink data channel (PUSCH: Physical Uplink Shared Channel). For the PDSCH, a table consisting of up to maxNrofDL-Allocations=16 entries can be configured, and for the PUSCH, a table consisting of up to maxNrofUL-Allocations=16 entries can be configured. In the implementation, the time-domain resource allocation information may include the time slot timing from PDCCH to PDSCH (corresponding to the time interval in units of time slots between the time of receiving PDCCH and the time of sending PDSCH scheduled by PDCCH, denoted by K0), the time slot timing from PDCCH to PUSCH (corresponding to the time interval in units of time slots between the time of receiving PDCCH and the time of sending PUSCH scheduled by PDCCH, denoted by K2), information regarding the start symbol position and length of the PDSCH or PUSCH scheduled within the time slot, the mapping type of PDSCH or PUSCH, etc. For example, information such as Table 16 or Table 17 below can be sent from the base station to the UE.

[0273] [Table 16]

[0274] [Table 17]

[0275] The base station can notify the UE of one of the entries in the table for time-domain resource allocation information mentioned above via L1 signaling (e.g., DCI) (e.g., it can be indicated by the "Time-domain Resource Allocation" field in the DCI). Based on the DCI received from the base station, the UE can obtain time-domain resource allocation information for PDSCH or PUSCH.

[0276] Figure 10 This is a diagram illustrating an example of time-domain resource allocation for a PDSCH in a wireless communication system according to an embodiment of the present disclosure.

[0277] refer to Figure 10 Based on the subcarrier spacing (SCS) (μPDSCH, μPDCCH) and scheduling offset (K0) values ​​of the data and control channels configured via higher-layer signaling, and the start position 1000 and length 1005 of the OFDM symbol within a time slot dynamically indicated by DCI, the base station can indicate the temporal location of the PDSCH resource.

[0278] In the following, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. This disclosure applies to FDD, TDD, and / or XDD (and / or SBFD or full-duplex) systems. In this disclosure, higher-layer signaling (or upper-layer signaling) refers to a signal transmission method that uses downlink data channels of the physical layer to transmit signals from a base station to a UE or uses uplink data channels of the physical layer to transmit signals from a UE to a base station, and may be referred to as RRC signaling, PDCP signaling, or Media Access Control (MAC) control element (MAC CE).

[0279] In the following text, a base station refers to an entity that performs resource allocation for a terminal and can be at least one of a gNode B (gNB), eNode B (eNB), Node B, base station (BS), radio access unit, base station controller, or node on a network. A terminal may include a user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. The embodiments of this disclosure will be described below using a 5G system as an example, but these embodiments can also be applied to other communication systems with similar technical backgrounds or channel types, such as LTE or LTE-A mobile communications and technologies developed after 5G. Therefore, embodiments of this disclosure can also be applied to other communication systems with modifications without significantly departing from the scope of this disclosure, as will be apparent to those skilled in the art. The content of this disclosure is applicable to FDD, TDD, and XDD (or SBFD or full-duplex) systems.

[0280] In the description of this disclosure, descriptions of known functions or components will be omitted where such detailed descriptions might unnecessarily obscure the subject matter of this disclosure. The terminology described below is defined with reference to the functions in this disclosure and may vary depending on the intent or practice of the user or operator. Therefore, the definitions of terms should be based on the entire contents of this specification.

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

[0282] -MIB (Master Information Block)

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

[0284] -RRC (Radio Resource Control)

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

[0286] In addition, L1 signaling can refer to signaling that corresponds to at least one, or a combination of two or more, of the following physical layer channels or signaling methods.

[0287] -PDCCH (Physical Downlink Control Channel)

[0288] -DCI (Downlink Control Information)

[0289] -UE-specific DCI

[0290] -Group Public DCI

[0291] -Public DCI

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

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

[0294] -PUCCH (Physical Uplink Control Channel)

[0295] -UCI (Uplink Control Information)

[0296] The term “time slot” as used in this disclosure is a general term that can refer to a specific time unit corresponding to a transmission time interval (TTI), and specifically, can refer to a time slot used in a 5G NR system, or a time slot or subframe used in a 4G LTE system, or a time resource unit used in a 6G system.

[0297] In the following description of this disclosure, rate matching is described as an example; however, this is merely an example of reserving specific resources to prevent resource overlap when different RATs use the same frequency band, and this disclosure is not limited to rate matching. For example, punching can be used.

[0298] Unless otherwise specifically stated, in the description of this disclosure, indication rate matching, indication rate matching mode and configuration rate matching can be interpreted as having the same meaning.

[0299] For convenience, in the following description of this disclosure, the case of 5G and LTE overlapping / conflicting with each other is described as an example of the case of the first radio access technology (RAT) and the second RAT overlapping / conflicting. However, this disclosure is not limited thereto. For example, this disclosure can also be applied to cases of 6G and 5G overlapping / conflicting, 6G and LTE overlapping / conflicting, 6G post-RAT and 6G pre-RAT overlapping / conflicting, etc., and is not limited thereto. In the following description of this disclosure, the term "candidate LTE PUCCH resource" may be replaced by "candidate PUCCH resource".

[0300] Although the above examples have been described in this disclosure through various embodiments, these embodiments are not mutually exclusive, and one or more embodiments may be applied simultaneously or in combination.

[0301] In 6G systems, spectrum sharing technologies may be important. For example, technologies such as Dynamic Spectrum Sharing (DSS) or Multiple Radio Access Technologies (RAT) Spectrum Sharing (MRSS) can be used to allow multiple RATs to coexist in the same frequency band, but this disclosure is not limited thereto. The reasons why spectrum sharing technologies are important in 6G systems are as follows.

[0302] 1) 6G spectrum is scarce

[0303] New frequency bands can be operated for 6G systems. Furthermore, 6G systems can also utilize existing frequency bands. For example, 6G systems can provide wide-area coverage by efficiently utilizing existing spectrum, such as low-frequency bands. Since existing frequency bands are already used by existing users (e.g., LTE / 5G communication systems), 6G systems may require spectrum sharing technologies such as DSS and MRSS to efficiently utilize existing frequency bands.

[0304] 2) Implement Standalone (SA) architecture

[0305] In the early stages of 5G, the Radio Access Network (RAN) operated in a Non-Standalone (NSA) architecture, leading to issues such as limited use of 5G capabilities, complex development, and increased operational overhead. Therefore, it is expected that 6G systems will operate in an SA architecture from the outset, and SA architecture may require spectrum sharing technologies such as DSS and MRSS. For example, spectrum sharing technology can be a key technology for supporting smooth network migration and multiple RAT connections.

[0306] To implement spectrum sharing technologies such as DSS and MRSS, resource conflicts and / or spectrum conflicts arising from resource usage should not occur between RATs (hereinafter referred to as inter-RAT conflicts). Rate matching or puncturing functions can be supported to prevent such resource conflicts and / or spectrum conflicts.

[0307] Figure 11 This is a diagram illustrating an example of an LTE / NR DSS scenario to which embodiments of this disclosure are applicable. Figure 11 An example of DSS applied between LTE and NR is shown, but this disclosure is not limited thereto.

[0308] Figure 12 This is a diagram illustrating an example of LTE PUCCH allocation applicable to embodiments of this disclosure.

[0309] refer to Figure 11LTE / NR PUCCHs can be located at both ends of the bandwidth, and their positions can be interchanged. In the portion of the bandwidth excluding the mapped / allocated portions of LTE and NR PUCCHs, LTE PUSCH (LTE PUSCH only), NR PUSCH (NR PUSCH only), and / or LTE PUSCH and NRPUSCH (LTE / NR PUSCH FDM) can be mapped / allocated. In other words, spectrum sharing can be applied between LTE and NR in flexible modes. Such modes can be LTE only, NR only, or LTE / NR FDM, and can have RB-level granularity.

[0310] In the case of LTE PUCCH, it can be mapped / assigned to the control area within a subframe. RB pairs within a subframe can be assigned to the LTE PUCCH of a single UE. RBs included in an RB pair can occupy different subcarriers in each of the two time slots within the subframe. That is, RB pairs assigned to LTE PUCCH can hop frequencies at time slot boundaries.

[0311] In the case of NR PUCCH, it can be mapped / assigned to the control area within the time slot. For example, in the case of long PUCCH, since the control channel with long transmission intervals is used for the purpose of increasing cell coverage, it can be transmitted using a Discrete Fourier Transform-Extended OFDM (DFT-S-OFDM) scheme (which is a single-carrier transmission) instead of an OFDM scheme. Therefore, PUCCH should only be transmitted using consecutive subcarriers, and frequency hopping can be configured to achieve frequency diversity. That is, when frequency hopping is applied (e.g., when frequency hopping is enabled by higher-layer signaling), the UE can configure uplink control channels with long transmission intervals based on resources at mutually separate frequency locations. When frequency hopping is not applied (e.g., when frequency hopping is disabled by higher-layer signaling), long PUCCH can be transmitted using long PUCCH transmission symbols at frequency locations determined by transmission start PRB information and PRB quantity information (configured via higher-layer signaling).

[0312] For example, in the case of a short PUCCH, the short PUCCH can be transmitted in both downlink-centric and uplink-centric time slots, and is typically transmitted in the last symbol of the time slot or in the OFDM symbols following it (e.g., the last OFDM symbol, the penultimate OFDM symbol, or the last two OFDM symbols). The short PUCCH can also be transmitted at any location within the time slot. One or two OFDM symbols can be used to transmit the short PUCCH. Radio resources for the short PUCCH are allocated in the frequency domain in units of PRBs, where the allocated PRBs can include a single PRB, multiple consecutive PRBs, or multiple non-consecutive PRBs spaced apart from each other in the frequency band. Furthermore, the allocated PRBs should be included in a frequency band equal to or smaller than the frequency band supported by the UE.

[0313] refer to Figure 11 and Figure 12 In the case of LTE PUCCH resources, PUCCH resources (0, 1, 2, 3, 4, 5...) can be mapped / allocated within a subframe comprising 14 OFDM symbols, where RB pairs corresponding to PUCCH resources with the same index can hop at slot boundaries. For example, PUCCH resource 0 can be assigned to UE A, and PUCCH resource 5 can be assigned to UE B. The index of the PRB forming the PUCCH (e.g., physical resource block number) can be represented as... ,and It can represent the uplink bandwidth configuration or the number of UL RBs included in the uplink bandwidth.

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

[0315] The characteristics of LTE PUCCH can be summarized as follows. When frequency hopping is applied to NR PUCCH (e.g., when IntraSlotFrequencyHopping is enabled), NR PUCCH can also have characteristics corresponding to the following. That is, it can have modes corresponding to the following LTE PUCCH modes.

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

[0317] 2) The location of the PUCCH changes at the time slot boundary depending on the time slot number.

[0318] When IntraSlotFrequencyHopping is enabled, since the NR PUCCH has features corresponding to those of the LTE PUCCH, the LTE PUCCH can be replaced by an NR PUCCH with IntraSlotFrequencyHopping enabled, unless otherwise stated in the description of the embodiments of this disclosure. For the NR PUCCH, compared to the LTE PUCCH, subframes can be replaced by time slots, and time slots can be replaced by half-time slots. Unless otherwise stated in the description of the embodiments of this disclosure, PUCCH resources can be interpreted as, but are not limited to, LTE PUCCH resources or NR PUCCH resources with IntraSlotFrequencyHopping enabled.

[0319] PUCCH resources can be categorized into periodic transmissions and on-demand transmissions. For example, periodic PUCCH resources can be used for scheduling requests (SRs) or CSI reports. On-demand PUCCH resources can be used to send uplink control information (UCI) for Hybrid Automatic Repeat Request (HARQ) feedback. For example, each PUCCH resource can be reserved for a specific UE via RRC (re)configuration.

[0320] According to embodiments of this disclosure, a method for indicating a rate matching mode can be provided. For example, the signaling method for rate matching can vary depending on the LTE PUCCH format. Table 18 summarizes the signaling methods for rate matching applicable to each PUCCH format. However, this disclosure is not limited thereto, and signaling methods for other rate matching methods can be applied to each PUCCH format.

[0321] [Table 18]

[0322] Figure 13 This is a diagram illustrating an example of an LTE / NR DSS scenario to which embodiments of this disclosure are applicable.

[0323] Figure 14 This is a diagram illustrating an example of an LTE / NR DSS scenario to which embodiments of this disclosure are applicable.

[0324] refer to Figure 13This illustrates the NR PUSCH area that can be allocated from the perspective of a single UE. When both LTE PUCCH and NR PUCCH are allocated within the bandwidth, the NR PUSCH can be allocated to an area other than the areas allocated to LTE PUCCH and NR PUCCH. If no LTE PUCCH is allocated within the bandwidth, but an NR PUCCH is allocated, the area corresponding to the LTE PUCCH can also be used for NR PUSCH. If neither LTE PUCCH nor NR PUCCH is allocated within the bandwidth, all resources within the bandwidth can be used for NR PUSCH. Figure 13 In this case, resources not used for NR PUSCH are used for PUCCHs of another RAT or NR PUCCHs, and if a PUCCH is not allocated, the area corresponding to that unallocated PUCCH can be used for NR PUSCHs, thus preventing resource waste. However, in Figure 14 In the example, a problem of resource waste occurred.

[0325] As mentioned above, frequency resource allocation methods for NR PUSCH can be classified into bitmap-based (Resource Allocation Type (RAT) 0) methods and RIV-based (RAT 1) methods. Due to the limitations of these NR PUSCH frequency resource allocation methods, Figure 13 In the examples, there may be wasted resources that cannot be used for NR PUSCH or for other purposes.

[0326] Specifically, in the case of RAT 0, a single bit in the bitmap can represent a consecutive RB. That is, RAT 0 can indicate frequency resource allocation in units of RBGs. Therefore, if the LTE PUCCH and NR PUSCH overlap within an RBG, the remaining non-overlapping resources (remaining RBs) within the RBG cannot be indicated by RAT 0. Consequently, resources cannot be allocated in units of RBGs, which are the resource allocation granularity of RAT 0, leading to resource waste.

[0327] In the case of RAT 1, frequency resource allocation can be indicated using the starting RB and the number of consecutive RBs starting from the starting RB. That is, RAT 1 does not support non-consecutive RB allocation. Therefore, if the LTE PUCCH and NR PUSCH overlap within the bandwidth, all RBs after the overlapping RBs in the frequency domain cannot be indicated by RAT 1.

[0328] Specifically, in Figure 14In this example, assuming a bandwidth of 20MHz, the number of RBs in the NR bandwidth is 106. When using configuration 1 in RAT0, the RBG size is 8. Although 2 RBs are allocated for the LTE PUCCH purpose, it is unlikely that 16 RBs corresponding to 2 RBGs will be allocated for the NRPUSCH purpose. Since RAT 1 only allows consecutive RB allocations, even a greater amount of resources may be wasted and not allocated to the NR PUSCH compared to RAT 0.

[0329] Traditional 5G systems support rate matching to avoid transmissions in resource locations overlapping with other RATs and to perform transmissions only in the remaining resource locations. However, traditional 5G systems only support a limited number of modes and types. Specifically, traditional 5G systems do not support rate matching for single or multiple non-contiguous LTE PUCCH resources. Furthermore, traditional 5G systems do not support PUCCH resource-level rate matching for each slot variation. This makes it difficult to indicate rate matching for dynamically used LTE PUCCH resources via DCI (e.g., UL-licensed DCI). Moreover, if rate matching is performed based on methods supported by traditional 5G systems, the number of states required for various LTE PUCCH resource configurations increases exponentially, potentially leading to excessive signaling overhead for indicating rate matching.

[0330] Figure 15 An example of a rate matching method in a communication system to which embodiments of this disclosure apply is shown. Regarding... Figure 15 For more specific details on the rate matching method, refer to the description of rate matching above.

[0331] refer to Figure 15 (a) Rate matching can be performed at the symbol / RB level. For example, if rate matching is performed on symbols #5, #8, #9, and #11, it means that all RBs within each of these symbols are rate matched. Therefore, Figure 15 Method (a) results in wasted RBs and may not be suitable for PUCCH-level rate matching. For example, it may not be suitable for rate matching of PUCCHs with in-slot frequency hopping (in-slot frequency hopping mode rate matching). Furthermore, Figure 15 Method (a) only supports a maximum of four rate matching modes, making it insufficient for rate matching on dynamically indicated PUCCH resources.

[0332] refer to Figure 15 (b) allows rate matching to be performed on the RE mapped to by the LTE CRS. In other words, since rate matching is performed based on the CRS mode, therefore... Figure 15 Method (b) cannot be applied to PUCCH-level rate matching.

[0333] According to embodiments of this disclosure, a PUCCH resource-level rate matching method between RATs can be supported. According to embodiments of this disclosure, a method is proposed for dynamically indicating the rate matching mode of PUCCH resources used by another RAT in a UL spectrum sharing scenario.

[0334] According to embodiments of this disclosure, a rate matching mode indication can be included in the DCI used for UL licensing. According to embodiments of this disclosure, resource efficiency can be maximized in UL spectrum sharing scenarios by minimizing the amount of unused resources caused by constraints of resource allocation schemes (e.g., RGB-based allocation in RAT 0 or contiguous RB-only allocation in RAT 1).

[0335] The rate matching method according to the embodiments of this disclosure can be summarized as shown in Table 19.

[0336] [Table 19]

[0337] Figure 16 This is a diagram illustrating an example of the signaling process between a UE and a base station according to an embodiment of this disclosure. Figure 16 The flowchart illustrates exemplary methods that can be implemented according to the principles of this disclosure, and various modifications can be made to the methods depicted in the flowchart. For example, although shown as a series of steps, the individual steps in the flowchart may overlap, occur in parallel, occur in different orders, or occur multiple times. In other examples, certain steps may be omitted or replaced with other steps.

[0338] refer to Figure 16 In operation 1601 according to an embodiment, the base station (gNB) may send an RRC reconfiguration message, and the UE may receive the message. The RRC reconfiguration message is an example and may be replaced by RRC signaling, RRC messages, or higher-layer signaling. This also applies to the description of this disclosure unless specifically stated otherwise. In operation 1603 according to an embodiment, the UE may send an RRC reconfiguration complete message, and the base station may receive the message. In operation 1605 according to an embodiment, the base station may send a MAC CE, and the UE may receive the MAC CE. In operation 1607 according to an embodiment, the base station may send a UL-granted DCI (e.g., format 0_0 or 0_1), and the UE may receive the UL-granted DCI. In operation 1609 according to an embodiment, the UE may send a PUSCH based on the UL-granted DCI, and the base station may receive the PUSCH.

[0339] More specific details regarding the above-described operation of the UE and base station according to embodiments of this disclosure can be found in the detailed description provided below.

[0340] To support operation according to embodiments of this disclosure, the UE and / or base station may support one or more of the following capabilities. For example, signaling for each capability may be supported. Specifically, the UE may send UE capability information indicating that the UE supports one or more of the following capabilities. When the base station determines, based on the UE capability information, that the UE supports one or more of the following capabilities, the base station may perform PUCCH resource-level rate matching operation according to embodiments of this disclosure.

[0341] -UE perspective

[0342] -PHY layer: Capable of receiving / decoding Information Elements (IEs) related to the Rate Matching Mode Indication in the DCI and of transmitting / encoding rate-matched PUSCH.

[0343] - MAC layer: Capabilities of receiving / decoding the IE associated with the rate match mode indication in the MAC CE.

[0344] -RRC layer: Capabilities for receiving / decoding IEs related to rate matching mode indication in RRC signaling.

[0345] -Base station perspective

[0346] -PHY layer: Capable of transmitting / encoding IEs associated with rate-matched mode indication in DCI, and capable of receiving / decoding rate-matched PUSCHs.

[0347] - MAC layer: Capable of sending / encoding IEs associated with rate matching mode indication in MAC CE.

[0348] -RRC layer: Capable of sending / encoding IEs related to rate matching mode indication in RRC signaling.

[0349] According to embodiments of this disclosure, the individual IEs transmitted and received via RRC signaling, MAC CE, and DCI can be different, as will be described below.

[0350] According to embodiments of this disclosure, the RRC reconfiguration message may include information about candidate LTE PUCCH resources. For example, the RRC reconfiguration message may include location information for the candidate LTE PUCCH resources. These candidate LTE PUCCH resources can be configured via the RRC reconfiguration message. The candidate LTE PUCCH resources can be used for rate matching. That is, the candidate LTE PUCCH resources can be candidates for which rate matching has been applied.

[0351] According to embodiments of this disclosure, an LTE base station (e.g., an eNB) can send 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 corresponding candidate LTE PUCCH resources, generate / acquire candidate LTE PUCCH resource information, and send this information to the UE via an RRC reconfiguration message. For example, the multiple PUCCH resources identified based on the PUCCH resource configuration information can be candidate LTE PUCCH resources that match application rates.

[0352] According to the embodiments of this disclosure, when the base station identifies candidate LTE PUCCH resources, it can be assumed that there is a UE for each PUCCH resource. .here, This refers to the number of cyclic shifts (CS) used for PUCCH format 1 / 1a / 1b in a mixed resource block having formats 1 / 1a / 1b and 2 / 2a / 2b. Furthermore, in this disclosure, it can be assumed that code domain multiplexing (CDM) (or code domain sharing) is not applied to PUCCH resources. Specifically, when the base station identifies candidate LTE PUCCH resources, it can be assumed that CDM is not used. That is, in the description of this disclosure, it can be assumed that PUCCH resources are dedicated to a single UE and no CDM is configured.

[0353] However, this assumption is made for the purpose of identifying candidate LTE PUCCH resources, and this disclosure is not limited to the PUCCH resources of a single UE without CDM. This disclosure can also be applied to the PUCCH resources of multiple UEs with CDM configured. That is, regardless of the actual PUCCH resource configuration, this disclosure assumes that the PUCCH resources are used for a single UE without CDM when identifying candidate LTE PUCCH resources. However, the PUCCH resources actually transmitted and received can be used for a single UE without CDM or for multiple UEs with CDM configured.

[0354] Figure 17 This is a diagram illustrating an example of RRC parameters according to an embodiment of this disclosure.

[0355] refer to Figure 17 According to embodiments of this disclosure, the RRC reconfiguration message may include one or more of the following RRC parameters: 1) The lowest RB index (hereinafter referred to as α) of the PUCCH of other RATs (i.e., the target RAT for spectrum sharing, such as LTE). It can be understood as the starting RB offset of the PUCCH of other RATs. The starting RB offset can be an offset relative to PRB0 in the RBs included in the bandwidth.

[0356] 2) The total number of rate matching modes (hereinafter referred to as L) or the total number of PUCCH RBs used in other RATs. For example, if the other RAT is LTE and assuming no CDM is configured, this could be the total number of PUCCH resources available in LTE. That is, it can be understood as the total number of PUCCH resources used in other RATs. The specific definition of L may vary depending on the implementation described below and will be provided in the description of each implementation.

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

[0358] According to embodiments of this disclosure, the RRC reconfiguration complete message can be a message sent to the base station when the UE can support the candidate rate matching mode. The UE's support for the candidate rate matching mode means that the UE supports the rate matching related operations according to embodiments of this disclosure. If the UE does not support the candidate rate matching mode, it can instead send an RRC reconfiguration failure message to the base station. Upon receiving the RRC reconfiguration complete message, the base station can determine / identify that the UE supports the candidate rate matching mode and continue to perform the rate matching related operations according to embodiments of this disclosure. Upon receiving the RRC reconfiguration failure message, the base station can determine / identify that the UE does not support the candidate rate matching mode and avoid performing the rate matching related operations according to embodiments of this disclosure.

[0359] According to embodiments of this disclosure, instead of relying on RRC reconfiguration complete / failure messages, the UE can send information about its ability to support candidate rate matching modes before receiving the RRC reconfiguration message. In this case, the base station can identify / determine whether the UE supports candidate rate matching modes based on the capability information received from the UE.

[0360] According to embodiments of this disclosure, the MCE CE can be used to update a bitmap included in the DCI for dynamic rate matching modes. Alternatively, the MAC CE can be used to configure periodic rate matching modes.

[0361] According to embodiments of this disclosure, the DCI can be a UL-licensed DCI for scheduling PUSCHs. The DCI can indicate the rate matching mode for the scheduled PUSCHs.

[0362] According to embodiments of this disclosure, methods for indicating rate matching modes can be categorized into methods capable of indicating rate matching for a single PUCCH resource and methods capable of indicating rate matching for multiple PUCCH resources. According to the method for indicating rate matching for multiple PUCCH resources, rate matching can be indicated for one or more PUCCH resources. That is, this method does not necessarily mean that multiple PUCCH resources must always be indicated.

[0363] Each method is described below. In the description of each method, parameter B may be the number of bits required to represent the entire rate matching pattern (or the total number of rate matching patterns). According to embodiments of this disclosure, one or more of the following embodiments and / or a combination of at least some of the following embodiments may be used.

[0364] Implementation 1 - A method for indicating rate matching for a single PUCCH resource

[0365] According to embodiments of this disclosure, within the DCI or MAC CE The bit can be used to indicate a single PUCCH resource. Here, L can be the total number of PUCCH resources.

[0366] Method 1-1) According to an embodiment of this disclosure, each PUCCH resource can be indicated by a single parameter based on B bits. Each bit included in the B bits can indicate a PUCCH resource index.

[0367] Methods 1-2) According to embodiments of this disclosure, each PUCCH resource can be indicated by two parameters based on the B bits. In the B bits, the B-1 bit can indicate the frequency domain location of the PUCCH resource. That is, the B-1 bit in the B bits can indicate the RB index of the PUCCH resource. The remaining 1 bit besides the B-1 bit can indicate the time domain location (and / or symbol domain location and / or symbol index) of the PUCCH resource. See again Figure 17 Bit B-1 can indicate For example, if bit B-1 indicates α and the remaining bit is 0, it can be interpreted as indicating PUCCH resource #0. Conversely, if bit B-1 indicates α and the remaining bit is 1, it can be interpreted as indicating PUCCH resource #1. In other words, based on the slot boundaries within a subframe, the remaining bit in bit B, excluding bit B-1, can indicate whether it refers to the RB of the first slot or the RB of the second slot. The remaining bit can be, but is not limited to, the most significant bit (MSB) or the least significant bit (LSB) of the bit B.

[0368] According to embodiments of this disclosure, within the DCI or MAC CE The bit can be used to indicate a single PUCCH RB. Here, L can be the total number of PUCCH RBs. Alternatively, it can be half the total number of PUCCH resources.

[0369] Methods 1-3) According to embodiments of this disclosure, each PUCCH RB can be indicated based on the B bit. The B bit can indicate the frequency domain location of the PUCCH resource. That is, the B bit 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.

[0370] Refer again Figure 17 The B position can indicate For example, if bit B indicates α, it can be understood as indicating two RBs: the RB corresponding to PUCCH resource #0 in the first time slot and the RB corresponding to PUCCH resource #0 in the second time slot. That is, the index indicated by bit B can be understood as indicating the index of two RBs in the first time slot corresponding to that index and in the second time slot, such as (maximum number of RBs - RB of the indicated index). For example, if rate matching is indicated to be applied to RB α, the UE can apply rate matching to PUCCH resource #0 and PUCCH resource #1. That is, based on the time slot boundaries, PUCCH resource #0 and PUCCH resource #1 in the first time slot, and PUCCH resource #0 and PUCCH resource #1 in the second time slot, can be rate matched. In cases other than LTE PUCCH, or when intra-slot frequency hopping is not applied, the index indicated by bit B can be understood as indicating a single RB corresponding to that index. For example, methods 1-3 can be used, but are not limited to, when complexity reduction / simplification is required or when the PUCCH DMRS resource configuration has one symbol.

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

[0372] [Table 20]

[0373] In Table 20, the number of bits included in the B bits applied in methods 1-3 can be one less than the number of bits included in the B bits applied in methods 1-1 and 1-2. For example, if there are 10 PUCCH resources (#0, ..., #9), the B bits in methods 1-1 and 1-2 can be determined to be 10 bits, while the B bits in method 1-3 can be determined to be 9 bits.

[0374] Implementation Method 2 - A method for rate matching of multiple PUCCH resources

[0375] Method 2-1) According to an embodiment of this disclosure, the B=L bit in the DCI or MAC CE can be used to indicate one or more PUCCH resources.

[0376] According to embodiments of this disclosure, a PUCCH resource index can be indicated. L can be the total number of PUCCH resources. B = the first bit in L. l The bit can be mapped to the first of L PUCCH resources. l The PUCCH resource. For example, if the first... l If the value of the bit is "1" (or "0"), then it can be in the second position. l Execution rate matching occurs on the PUCCH resource. Conversely, if the first PUCCH resource... l If the value of the bit is "0" (or "1"), then it can be excluded from the first position. l Rate matching is performed on each PUCCH resource. In other words, the B = L bits can be used as a bitmap to indicate whether rate matching is performed on each PUCCH resource.

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

[0378] According to embodiments of this disclosure, a PUCCH RB index can be indicated. L can be the total number of PUCCH RBs. Alternatively, it can be half the total number of PUCCH resources. B = the 1st bit in L. l The bit can be mapped to the Lth PUCCH RB. l The first PUCCH RB. For example, if the first PUCCH RB... l If the value of the bit is "1" (or "0"), then it can be in the second position. l Rate matching is performed on the PUCCH RB. Conversely, if the first... l If the value of the bit is "0" (or "1"), then it can be excluded from the first position. l Rate matching is performed on each PUCCH RB. That is, B = L bits can be used as a bitmap to indicate whether rate matching is performed on each PUCCH RB.

[0379] In the case of LTE PUCCH (or when in-slot frequency hopping is enabled), the first bit in B = L is... l A bit (or each bit included in B = L bits) can indicate two RBs. For example, the first bit can indicate whether rate matching should be applied to RB α and RB β. If the first bit indicates that rate matching should be applied, the UE can apply rate matching to both PUCCH resource #0 and PUCCH resource #1. That is, based on the slot boundaries, 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 (in cases other than LTE PUCCH and / or when intra-slot frequency hopping is disabled), the first bit of B = L... l A single bit can indicate a single RB.

[0380] Figure 18 This is a diagram illustrating an example of a bit field in a DCI according to an embodiment of the present disclosure.

[0381] refer to Figure 18 The DCI field can include an octet, i.e., 8 bits, which can mean L = 8. For example, if the DCI field is "00011001", rate matching can be performed for PUCCH resource IDs 0, 3, and 4. That is, after performing rate matching at the RE positions corresponding to PUCCH resource IDs 0, 3, and 4, a rate-matched PUSCH can be sent. As another example, if the DCI field is "00000001", rate matching can be performed for PUCCH resource ID 7. That is, after performing rate matching at the RE position corresponding to PUCCH resource ID 7, a rate-matched PUSCH can be sent.

[0382] Implementation Method 3 - A method for indicating rate matching for multiple PUCCH resources

[0383] According to embodiments of this disclosure, the B < L bit in the DCI can be used to indicate one or more PUCCH resources (or RBs).

[0384] According to embodiments of this disclosure, a subset of candidate PUCCH resources (or RBs) configured via RRC signaling can be indicated by MAC CE, and candidate PUCCH resources (or RBs) in the subset indicated by MAC CE can be indicated by DCI.

[0385] Method 3-1) According to an embodiment of this disclosure, a PUCCH resource index can be indicated. L can be the total number of PUCCH resources.

[0386] According to embodiments of this disclosure, the MAC CE can indicate a bitmap representing a set of desired total PUCCH resources from all available PUCCH resources. The bitmap's... l The bit can be mapped to the first of L PUCCH resources. l The PUCCH resource. For example, if the first...l If the value of the bit is "1" (or "0"), it can indicate the selection of the digit. l The first PUCCH resource is used as the active rate matching mode. Conversely, if the first... l If the value of the bit is "0" (or "1"), it can indicate that the digit is not selected. l One PUCCH resource is used as the active rate matching mode. The maximum number M of active rate matching modes that can be indicated by MAC CE can be 2. B .

[0387] According to embodiments of this disclosure, bit fields within the DCI can indicate the active rate matching mode (previously indicated by the MAC CE) in the form of a bitmap. For example, the b-th bit of the bitmap in the DCI can be mapped to the b-th PUCCH resource in the active rate matching mode (i.e., the PUCCH resource indicated by the MAC CE). For example, if the value of the b-th bit is "1" (or "0"), rate matching can be performed on the b-th PUCCH resource. Conversely, if the value of the b-th bit is "0" (or "1"), rate matching can not be performed on the b-th PUCCH resource.

[0388] Method 3-2) According to an embodiment of this disclosure, a PUCCH RB index can be indicated. L can be the total number of PUCCH RBs. Alternatively, it can be half the total number of PUCCH resources.

[0389] According to embodiments of this disclosure, the MAC CE can indicate a bitmap representing a set of desired total PUCCH RBs from all available PUCCH RBs. The bitmap's... l The bit can be mapped to the Lth PUCCH RB. l The first PUCCH RB. For example, if the first PUCCH RB... l If the value of the bit is "1" (or "0"), it can indicate the selection of the digit. l The first PUCCH RB is used as the active rate-matching mode. Conversely, if the first PUCCH RB is used as the active rate-matching mode. l If the value of the bit is "0" (or "1"), it can indicate that the digit is not selected. l 1 PUCCH RB is used as the active rate matching mode. The maximum number M of active rate matching modes that can be indicated by MAC CE can be 2. B .

[0390] In the case of LTE PUCCH (or when in-slot frequency hopping is enabled), the bitmap in the MAC CE is... l A bit (or each bit included in the MAC CE bitmap) can indicate two RBs. For example, the bit in the MAC CE bitmap... l The RB indicated by the bit can be related to the index.l The corresponding RB and the RB corresponding to the index (the largest index of RB - (α + the RB of the indicated index)). For example, the first digit can correspond to RB α and RB. Otherwise (in cases other than LTE PUCCH and / or when in-slot frequency hopping is disabled), the first bit in B = L... l A single bit can indicate a single RB.

[0391] According to embodiments of this disclosure, bit fields within the DCI can indicate the active rate matching mode (previously indicated by the MAC CE) in the form of a bitmap. For example, the b-th bit of the bitmap in the DCI can be mapped to the b-th PUCCH RB in the active rate matching mode (i.e., the PUCCH RB indicated by the MAC CE). For example, if the value of the b-th bit is "1" (or "0"), rate matching can be performed on the b-th PUCCH RB. Conversely, if the value of the b-th bit is "0" (or "1"), rate matching can be omitted from the b-th PUCCH RB.

[0392] Figure 19 This is a diagram illustrating an example of the relationship between a bitmap included in a MAC CE and a bitmap included in a DCI according to an embodiment of this disclosure.

[0393] refer to Figure 19 The bitmap included in the MAC CE can indicate M active PUCCH resources out of L PUCCH resources configured via RRC. The bitmap included in the DCI can indicate the specific PUCCH resource to be rate-matched among the M PUCCH resources activated by the MAC CE. Therefore, the bitmap included in the DCI can include M bits.

[0394] For example, M PUCCH resources activated by a MAC CE can be applied sometime after the reception of the MAC CE (or the PDSCH carrying the MAC CE). For instance, if the MAC CE (or the PDSCH carrying the MAC CE) is received in time slot #n, the M PUCCH resources activated by the MAC CE can be applied starting from time slot #n+k, where k is an integer greater than or equal to 0. The value of k can be predefined and / or configured by higher-layer signaling.

[0395] Figure 20 This is a diagram illustrating an example of the relationship between a bitmap included in a MAC CE and a bitmap included in a DCI according to an embodiment of this disclosure. Figure 20 An example where L = 16 and B = 4 is shown.

[0396] Reference Figure 20The 16-bit bitmap included in the MAC CE can indicate the index of the active PUCCH resource among the 16 PUCCH resources configured via RRC. For example, if bits 1, 4, 7, and 14 of the 16 bits in the MAC CE are set to 1 and the remaining bits are set to 0, then PUCCH resources 1, 4, 7, and 14 out of the 16 PUCCH resources can be activated. The bitmap included in the DCI can indicate whether rate matching should be performed on the active PUCCH resources 1, 4, 7, and 14.

[0397] According to embodiments of this disclosure, whether the DCI includes an IE associated with a rate matching mode indication can be identified or determined as follows.

[0398] - If the RRC reconfiguration message does not contain information about the candidate PUCC resources (e.g., information about α and / or L), then the DCI may not include the IE associated with the rate matching mode indication.

[0399] - If the RRC reconfiguration message contains information about the candidate PUCC resources (e.g., information about α and / or L), - - DCI always includes an IE associated with the rate matching mode indication, or -- The DCI includes a 1-bit flag indicating the presence of an IE associated with the rate match mode indication. If the 1-bit flag is "1" (or "0"), the DCI includes the IE associated with the rate match mode indication. If the 1-bit flag is "0" (or "1"), the DCI does not include the IE associated with the rate match mode indication, and / or If all bits in the IE associated with the rate matching mode indication in the DCI are set to "0" or "1", it can indicate that rate matching is not performed.

[0400] Figure 21 This is a diagram illustrating a DM-RS suitable for PUSCH transmission according to an embodiment of the present disclosure.

[0401] Figure 22 This is a diagram illustrating a DM-RS suitable for PUSCH transmission according to an embodiment of the present disclosure.

[0402] refer to Figure 21 When no additional demodulation reference signal (DM-RS) is configured (e.g., dmrs-AdditionalPosition = 0), the DM-RS used for PUSCH can be mapped to a single symbol within the time slot (e.g., the DM-RS symbol for symbol #2). The DM-RS mapped to a symbol can consist of CDM group 0 and CDM group 1.

[0403] For example, if the LTE PUCCH corresponds to symbols #7 to #13 (right side, case 2), then rate matching is applied to symbols #7 to #13, and the PUSCH together with its DM-RS can be transmitted in symbols #0 to #6.

[0404] On the other hand, if the LTE PUCCH corresponds to symbols #0 through #6 (left side, case 1), rate matching is applied to symbols #0 through #6. In this case, although the PUSCH should be transmitted in symbols #7 through #13, the DM-RS for the PUSCH cannot be transmitted because no DM-RS is configured in symbols #7 through #13. Therefore, this may lead to a problem where channel estimation cannot be performed at the receiver.

[0405] According to embodiments of this disclosure, one or more of the following methods can be applied to the PRB (index n) corresponding to case 1.

[0406] According to embodiments of this disclosure, rate matching can be performed on all symbols within PRB n (e.g., symbols #0 to #13). See also Figure 22 In Alt.1, the REs included in PRB n are rate-matched and therefore not used for PUSCH transmission.

[0407] According to embodiments of this disclosure, rate matching can be performed on all symbols within PRB n (e.g., symbols #0 to #13). See also Figure 22 In Alt.2, the DM-RS symbol can be shifted to any one of symbols #7 to #13 in PRB n (e.g., symbol #11). In this case, the PUSCH and its corresponding DM-RS can be transmitted within symbols #7 to #13 in PRB n.

[0408] Figure 23 This is a diagram illustrating a DM-RS suitable for PUSCH transmission according to an embodiment of the present disclosure.

[0409] Figure 24 This is a diagram illustrating a DM-RS suitable for PUSCH transmission according to an embodiment of the present disclosure.

[0410] refer to Figure 23 and 24 When an Additional Demodulation Reference Signal (DM-RS) is configured (e.g., dmrs-AdditionalPosition > 0), the DM-RS used for PUSCH can be mapped to two symbols within a time slot (e.g., DM-RS symbols for symbol #2 and symbol #11). The DM-RS mapped to a symbol can consist of CDM group 0 and CDM group 1.

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

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

[0413] Figure 25 This is a diagram illustrating an example of an operation flowchart of a UE according to an embodiment of this disclosure. It is possible to... Figure 25 The methods depicted in the flowchart can be modified in various ways. For example, although shown as a series of steps, the steps in the flowchart can overlap, occur in parallel, occur in different orders, or occur multiple times. In other examples, some steps can be omitted or replaced with other steps.

[0414] refer to Figure 25 In operation 2510 according to the embodiment, the UE can receive information related to candidate physical uplink control channel (PUCCH) resources in the first radio access technology (RAT) via higher-layer signaling (e.g., RRC message).

[0415] In operation 2520 according to the embodiment, the UE can receive information related to the active candidate PUCCH resource among the candidate PUCCH resources via the Media Access Control Element (MAC CE). Operation 2520 according to the embodiment can be omitted.

[0416] In operation 2530 according to the embodiment, the UE may receive downlink control information (DCI) scheduling the Physical Uplink Shared Channel (PUSCH) (or uplink channel). The DCI may include bit fields indicating candidate PUCCH resources included in the candidate PUCCH resources. For example, if a MAC CE is received in operation 2520 according to the embodiment, the bit fields may indicate candidate PUCCH resources among the active candidate PUCCH resources. For example, if no MAC CE is received in operation 2520 according to the embodiment, the bit fields may indicate candidate PUCCH resources among the candidate PUCCH resources transmitted via higher-layer signaling.

[0417] In operation 2540 according to the implementation, the UE can transmit the uplink channel based on the DCI. Rate matching can be applied to REs in the resource elements (REs) included in the uplink channel that overlap with the candidate PUCCH resource indicated by the DCI.

[0418] For more specific details regarding the UE operation described above according to embodiments of this disclosure, refer to the above description of embodiments of this disclosure.

[0419] Figure 26 This is an example diagram illustrating an operation flowchart of a base station according to an embodiment of the present disclosure. It is possible to... Figure 26 The methods depicted in the flowchart can be modified in various ways. For example, although shown as a series of steps, the steps in the flowchart can overlap, occur in parallel, occur in different orders, or occur multiple times. In other examples, some steps can be omitted or replaced with other steps.

[0420] refer to Figure 26 In operation 2610 according to the embodiment, the base station may transmit information related to candidate physical uplink control channel (PUCCH) resources in the first radio access technology (RAT) via higher-layer signaling (e.g., RRC messages).

[0421] In operation 2620 according to the embodiment, the base station may transmit information related to the active candidate PUCCH resource in the candidate PUCCH resources via the Media Access Control Element (MAC CE). Operation 2620 according to the embodiment may be omitted.

[0422] In operation 2630 according to an embodiment, the base station may transmit downlink control information (DCI) for scheduling the Physical Uplink Shared Channel (PUSCH) (or uplink channel). The DCI may include bit fields indicating candidate PUCCH resources included in the candidate PUCCH resources. For example, if a MACCE is transmitted in operation 2620 according to an embodiment, the bit fields may indicate candidate PUCCH resources among the active candidate PUCCH resources. For example, if a MAC CE is not transmitted in operation 2620 according to an embodiment, the bit fields may indicate candidate PUCCH resources among the candidate PUCCH resources transmitted via higher-layer signaling.

[0423] In operation 2640 according to the embodiment, the base station can receive an uplink channel. Rate matching can be applied to REs that overlap with candidate PUCCH resources indicated by the DCI among the resource elements (REs) included in the uplink channel.

[0424] For more specific details regarding the above-described base station operation according to embodiments of this disclosure, refer to the above description of embodiments of this disclosure.

[0425] Figure 27 This is a diagram illustrating the structure of a UE in a wireless communication system according to an embodiment of the present disclosure.

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

[0427] A transceiver can send signals to / receive signals from a base station. These signals may include control information and data. Therefore, a transceiver may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for low-noise amplification and down-converting the frequency of the received signal. However, this is only one possible implementation of a transceiver, and the components of the transceiver are not limited to RF transmitters and RF receivers.

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

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

[0430] Furthermore, the processor can control a series of processes, enabling the UE to operate according to the above-described implementation. For example, the processor can control the UE's components to receive a two-layer DCI and simultaneously receive multiple PDSCHs. Multiple processors can exist, and each processor can execute programs stored in memory to control the UE's components.

[0431] Figure 28 This is a diagram illustrating the structure of a base station in a wireless communication system according to an embodiment of the present disclosure.

[0432] refer to Figure 28 The base station may include transceivers (referring to base station receiver 2800 and base station transmitter 2810), a memory (not shown), and a base station processor 2805 (or base station controller or processor). The base station transceivers 2800 and 2810, the memory, and the base station processor 2805 can operate according to the communication method described above for the base station. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than those described above. Furthermore, the transceiver, memory, and processor may be implemented as a single chip.

[0433] A transceiver can send signals to / receive signals from a UE. These signals may include control information and data. Therefore, a transceiver may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for low-noise amplification and down-converting the frequency of the received signal. However, this is only one possible implementation of a transceiver, and the components of the transceiver are not limited to RF transmitters and RF receivers.

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

[0435] The memory can store the programs and data required for the operation of the base station. Additionally, the memory can store control information or data included in signals transmitted or received by the base station. The memory can include storage media (such as ROM, RAM, hard disk, CD-ROM, and DVD) or a combination of storage media. Furthermore, multiple memories can exist.

[0436] The processor can control a series of processes that enable the base station to operate according to the above-described embodiments. For example, the processor can control the components of the base station to form a two-layer DCI including allocation information for multiple PDSCHs, and transmit the DCI. Multiple processors may exist, and each processor can execute operations controlling the components of the base station by executing programs stored in memory.

[0437] The methods described in this document or the claims can be implemented in hardware, software, or a combination of hardware and software.

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

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

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

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

[0442] The embodiments described herein are merely specific implementations presented to facilitate the explanation of the technical content of this disclosure and to aid in understanding it, and are not intended to limit the scope of this disclosure. That is, it will be apparent to those skilled in the art that other variations based on the technical concepts of this disclosure can be implemented. Furthermore, the corresponding embodiments described above can be combined if desired. For example, embodiments of this disclosure can be partially combined with another embodiment to operate a base station and a UE. As an example, embodiments 1 and 2 of this disclosure can be partially combined to operate a base station and a UE. Moreover, although the above embodiments are described using an FDD LTE system, other variations based on the technical concepts of the embodiments can be implemented in other systems such as TDD LTE and 5G or NR systems.

[0443] Furthermore, in the accompanying drawings describing the methods of this disclosure, the order of description does not necessarily correspond to the order of execution, and the priority order may be changed or the steps may be executed in parallel.

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

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

[0446] Various embodiments of this disclosure have been described. The above description is for illustrative purposes only and is not intended to limit the embodiments of this disclosure to those set forth herein. Those skilled in the art will understand that other specific modifications and alterations can be readily made to this disclosure without changing its technical concept or essential characteristics. The scope of this disclosure should not be determined by the foregoing description but rather by the appended claims, and all variations or modifications derived from the meaning and scope of the claims and their equivalents should be interpreted as falling within the scope of this disclosure.

Claims

1. A method performed by a terminal in a communication system, the method comprising: Information related to multiple candidate Physical Uplink Control Channel (PUCCH) resources in the first Radio Access Technology (RAT) is received via higher-layer signaling. Receive downlink control information (DCI) for scheduling the Physical Uplink Shared Channel (PUSCH) in the second RAT, wherein the DCI includes a bit field indicating the candidate PUCCH resources included in the plurality of candidate PUCCH resources; Perform rate matching applied to REs in the resource elements REs included in the PUSCH that overlap with the candidate PUCCH resource; and The PUSCH with the rate matching applied was sent.

2. The method according to claim 1, wherein, The number of bits in the bit field is determined to satisfy... The value of , where L is related to the number of the plurality of candidate PUCCH resources, and Wherein, the bit field indicates a value corresponding to the index of the candidate PUCCH resource, or In this context, one bit in the bit field indicates a value corresponding to the time-domain position of the candidate PUCCH resource, and the remaining bits in the bit field, excluding the one bit, indicate values ​​corresponding to the frequency-domain position of the PUCCH resource.

3. The method according to claim 1, wherein, When a Media Access Control (MAC) control element (CE) is received indicating an active candidate PUCCH resource among the plurality of candidate PUCCH resources, the bit field is a first bit map indicating the candidate PUCCH resource included in the active candidate PUCCH resource, and the size of the first bit map is equal to the number of active candidate PUCCH resources. In the absence of a MAC CE, the bit field is a second bitmap indicating the candidate PUCCH resources included in the plurality of candidate PUCCH resources, and the size of the second bitmap is equal to the number of the plurality of candidate PUCCH resources. Specifically, upon receiving the MAC CE, the activated candidate PUCCH resource is applied after a slot offset starting from the slot where the MAC CE was received, and The time slot offset is a predefined value or configured via higher-layer signaling.

4. The method according to claim 1, wherein, The information related to the multiple candidate PUCCH resources includes information related to the starting resource block (RB) index of the multiple candidate PUCCH resources in the frequency domain and information related to the number of the multiple candidate PUCCH resources. The information related to the starting RB index and the number of the plurality of candidate PUCCH resources are received via higher-layer signaling. The DCI further includes an indicator of whether the bit field is included in the DCI. Specifically, rate matching is not performed when the bit field is set to all "1"s or all "0"s.

5. The method according to claim 1, wherein, In the case where the RE with applied rate matching is configured with a demodulation reference signal DM-RS for the PUSCH, the symbols included in the first half of the time slot corresponding to the PUSCH and one of the symbols included in the first half of the time slot for the PUSCH are configured: The REs corresponding to all symbols of the PUSCH time slot are rate-matched in the RBs corresponding to the candidate PUCCH resources, or The DM-RS is transmitted in one of the symbols included in the second half of the time slot of the PUSCH.

6. The method according to claim 1, wherein, In the case where the first symbol included in the first half of the time slot for the PUSCH and the second symbol included in the second half of the time slot for the PUSCH are configured with DM-RS for the PUSCH: When the RE with applied rate matching corresponds to a symbol included in the first half of the time slot, the DM-RS configured for the first symbol is not transmitted, and the DM-RS configured for the second symbol is transmitted. When the RE with the applied rate matching corresponds to a symbol included in the second half of the time slot, the DM-RS configured for the first symbol is transmitted and the DM-RS configured for the second symbol is not transmitted.

7. A terminal in a communication system, the terminal comprising: transceiver; as well as A processor, connected to the transceiver, is configured to: Information related to multiple candidate Physical Uplink Control Channel (PUCCH) resources in the first Radio Access Technology (RAT) is received via higher-layer signaling. Receive downlink control information (DCI) for scheduling the Physical Uplink Shared Channel (PUSCH) in the second RAT, wherein the DCI includes a bit field indicating the candidate PUCCH resources included in the plurality of candidate PUCCH resources; Perform rate matching applied to REs in the resource elements REs included in the PUSCH that overlap with the candidate PUCCH resource; and The PUSCH with the rate matching applied was sent.

8. The terminal according to claim 7, wherein, The number of bits in the bit field is determined to satisfy... The value of , where L is related to the number of the plurality of candidate PUCCH resources, and Wherein, the bit field indicates a value corresponding to the index of the candidate PUCCH resource, or In this context, one bit in the bit field indicates a value corresponding to the time-domain position of the candidate PUCCH resource, and the remaining bits in the bit field, excluding the one bit, indicate values ​​corresponding to the frequency-domain position of the PUCCH resource.

9. The terminal according to claim 7, wherein, When a Media Access Control (MAC) control element (CE) is received indicating an active candidate PUCCH resource among the plurality of candidate PUCCH resources, the bit field is a first bit map indicating the candidate PUCCH resource included in the active candidate PUCCH resource, and the size of the first bit map is equal to the number of active candidate PUCCH resources. In the absence of a MAC CE, the bit field is a second bitmap indicating the candidate PUCCH resources included in the plurality of candidate PUCCH resources, and the size of the second bitmap is equal to the number of the plurality of candidate PUCCH resources. Specifically, upon receiving the MAC CE, the activated candidate PUCCH resource is applied after a slot offset starting from the slot where the MAC CE was received, and The time slot offset is a predefined value or configured via higher-layer signaling.

10. The terminal according to claim 7, wherein, The information related to the multiple candidate PUCCH resources includes information related to the starting resource block (RB) index of the multiple candidate PUCCH resources in the frequency domain and information related to the number of the multiple candidate PUCCH resources. The information related to the starting RB index and the number of the plurality of candidate PUCCH resources are received via higher-layer signaling. The DCI further includes an indicator of whether the bit field is included in the DCI. Specifically, rate matching is not performed when the bit field is set to all "1"s or all "0"s.

11. The terminal according to claim 7, wherein, In the case where the RE with applied rate matching is configured with a demodulation reference signal DM-RS for the PUSCH, the symbols included in the first half of the time slot corresponding to the PUSCH and one of the symbols included in the first half of the time slot for the PUSCH are configured: The REs corresponding to all symbols of the PUSCH time slot are rate-matched in the RBs corresponding to the candidate PUCCH resources, or The DM-RS is transmitted in one of the symbols included in the second half of the time slot of the PUSCH.

12. The terminal according to claim 7, wherein, In the case where the first symbol included in the first half of the time slot for the PUSCH and the second symbol included in the second half of the time slot for the PUSCH are configured with DM-RS for the PUSCH: When the RE with applied rate matching corresponds to a symbol included in the first half of the time slot, the DM-RS configured for the first symbol is not transmitted, and the DM-RS configured for the second symbol is transmitted. When the RE with the applied rate matching corresponds to a symbol included in the second half of the time slot, the DM-RS configured for the first symbol is transmitted and the DM-RS configured for the second symbol is not transmitted.

13. A method performed by a base station in a communication system, the method comprising: Information related to multiple candidate Physical Uplink Control Channel (PUCCH) resources in the first Radio Access Technology (RAT) is transmitted via higher-layer signaling. Sending downlink control information (DCI) for scheduling the Physical Uplink Shared Channel (PUSCH) in the second RAT, wherein the DCI includes a bit field indicating the candidate PUCCH resources included in the plurality of candidate PUCCH resources; and Receive the PUSCH, Rate matching is applied to REs in the resource elements REs included in the PUSCH that overlap with the candidate PUCCH resource.

14. The method according to claim 13, wherein, In the case of transmitting a Media Access Control (MAC) control element (CE) indicating the active candidate PUCCH resource among the plurality of candidate PUCCH resources, the bit field is a first bit map indicating the candidate PUCCH resource included in the active candidate PUCCH resource, the size of the first bit map being equal to the number of active candidate PUCCH resources, and Wherein, in the absence of sending the MAC CE, the bit field is a second bitmap indicating the candidate PUCCH resources included in the plurality of candidate PUCCH resources, the size of the second bitmap being equal to the number of the plurality of candidate PUCCH resources.

15. A base station in a communication system, the base station comprising: transceiver; as well as A processor, connected to the transceiver, is configured to: Information related to multiple candidate Physical Uplink Control Channel (PUCCH) resources in the first Radio Access Technology (RAT) is transmitted via higher-layer signaling. Sending downlink control information (DCI) for scheduling the Physical Uplink Shared Channel (PUSCH) in the second RAT, wherein the DCI includes a bit field indicating the candidate PUCCH resources included in the plurality of candidate PUCCH resources; and Receive the PUSCH, Rate matching is applied to REs in the resource elements REs included in the PUSCH that overlap with the candidate PUCCH resource.

Images