Method and apparatus for transmitting control information of network coordinated communication

Abstract

The disclosure relates to a communication technology and system for converging a 5G communication system with a IoT technology to support higher data rates beyond 4G systems. The disclosure can be applied to smart services (e.g., smart home, smart building, smart city, smart car or connected car, health care, digital education, retail business, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology.

Description

Technical Field

[0001] This disclosure relates to a wireless communication system, and more specifically, to a method and apparatus in which a terminal transmits control information to multiple transmission points / panels / beams for the purpose of cooperative communication among multiple transmission points / panels / beams. Background Technology

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

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

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

[0005] The above information is presented as background information only to aid in understanding this disclosure. It is neither determined nor asserted whether any of the above content can be applied as prior art to this disclosure. Summary of the Invention

[0006] Technical issues

[0007] This disclosure provides a method in which a terminal transmits control information to multiple transmission points / panels / beams for the purpose of network coordination in a wireless communication system.

[0008] Solution to the problem

[0009] To address the aforementioned problems, this disclosure provides a method performed by a terminal in a communication system. The method includes: receiving information from a base station regarding a Physical Uplink Control Channel (PUCCH) and information regarding a Physical Downlink Shared Channel (PDSCH); receiving downlink control information (DCI) including resource allocation information from the base station; receiving data from the base station related to resources determined based on the information regarding the PDSCH and the resource allocation information; identifying PUCCH resources for transmitting Hybrid Automatic Repeat Request Acknowledgment (HARQ ACK) information based on the information regarding the PUCCH; and repeatedly transmitting HARQ ACK information to the base station based on offset information included in the information regarding the PUCCH, provided that the symbol length of the PUCCH resource is equal to or less than 2 and repeated transmission is configured for at least one Transmit and Receive Point (TRP) for the PUCCH resource. Furthermore, the terminal method in this disclosure may also include transmitting terminal capability information to the base station, including whether the terminal supports repeated transmission.

[0010] Furthermore, to address the aforementioned problems, this disclosure provides a method performed by a base station in a communication system. The method includes: sending information about a Physical Uplink Control Channel (PUCCH) and information about a Physical Downlink Shared Channel (PDSCH) to a terminal; sending downlink control information (DCI) including resource allocation information to the terminal; sending data to the terminal related to resources determined based on the information about the PDSCH and the resource allocation information; and receiving from the terminal hybrid Automatic Repeat Request Acknowledgment (HARQ ACK) information related to the PUCCH resources determined based on the PUCCH information, wherein, if the symbol length of the PUCCH resource is equal to or less than 2 and retransmission is configured for at least one Transmit and Receive Point (TRP) of the PUCCH resource, the HARQ ACK information is retransmitted based on offset information included in the information about the PUCCH. Additionally, the base station method in this disclosure may further include receiving terminal capability information from the terminal, including whether the terminal supports retransmission.

[0011] Furthermore, to address the aforementioned problems, this disclosure provides a terminal in a communication system, comprising a transceiver and a controller connected to the transceiver and configured to: receive information from a base station regarding the Physical Uplink Control Channel (PUCCH) and information regarding the Physical Downlink Shared Channel (PDSCH); receive downlink control information (DCI) including resource allocation information from the base station; receive data from the base station relating to resources determined based on the information regarding the PDSCH and the resource allocation information; identify PUCCH resources for transmitting Hybrid Automatic Repeat Request Acknowledgment (HARQ ACK) information based on the information regarding the PUCCH; and, when the symbol length of the PUCCH resource is equal to or less than 2 and repeated transmission is configured for at least one Transmit and Receive Point (TRP) of the PUCCH resource, repeatedly transmit HARQ ACK information to the base station based on offset information included in the information regarding the PUCCH. Furthermore, the controller of the terminal in this disclosure can transmit terminal capability information to the base station, including whether the terminal supports repeated transmission.

[0012] Furthermore, to address the aforementioned problems, this disclosure provides a base station in a communication system, comprising a transceiver and a controller connected to the transceiver and configured to: transmit to a terminal information about a Physical Uplink Control Channel (PUCCH) and information about a Physical Downlink Shared Channel (PDSCH); transmit to the terminal downlink control information (DCI) including resource allocation information; transmit to the terminal data related to resources determined based on the information about the PDSCH and the resource allocation information; and receive from the terminal hybrid automatic repeat request acknowledgment (HARQ ACK) information related to PUCCH resources determined based on the information about the PUCCH, wherein, in cases where the symbol length of the PUCCH resource is equal to or less than 2 and repeated transmission is configured for at least one transmit and receive point (TRP) of the PUCCH resource, the HARQ ACK information is repeatedly transmitted based on offset information included in the information about the PUCCH. Furthermore, the controller of the base station in this disclosure can receive from the terminal terminal terminal capability information including whether the terminal supports repeated transmission.

[0013] Advantages of the invention

[0014] The advantage of this disclosure is that, when network coordination is used for a wireless communication system, the terminal sends control information to each transmission point / panel / beam, thereby improving reliability compared to the case where control information is sent to a single transmission point / panel / beam.

[0015] Before proceeding with the following specific description, it may be advantageous to define certain words and phrases used throughout this patent document: the term “comprising” and its derivatives mean including but not limited to; the term “or” is inclusive, meaning and / or; the phrases “associated with” and “associated with” and their derivatives may mean including, contained within, interconnected with, including, included in, connected to or connected to, coupled to or coupled to, capable of communicating with, cooperating with, interleaved, juxtaposed, proximate, bound to or bound to, having, possessing the nature of, etc.; and the term “controller” means any device, system, or part thereof that controls at least one operation, which may be implemented in hardware, firmware, or software, or at least a combination of two thereof. It should be noted that the functionality associated with any particular controller may be centralized or distributed, local or remote.

[0016] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and embodied in a computer-readable medium. The terms "application program" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof that are implemented in suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of media accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transmit transient electrical signals or other transient signals. Non-transitory computer-readable media includes media that can permanently store data, as well as media that can store data and subsequently rewrite it, such as rewritable optical discs or erasable memory devices.

[0017] Throughout this patent document, definitions of certain words and phrases are provided, and those skilled in the art will understand that, in many instances (if not most), such definitions apply to the previous and future use of the words and phrases so defined. Attached Figure Description

[0018] To gain a more complete understanding of this disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which the same reference numerals denote the same parts:

[0019] Figure 1 This is a view of the basic time-frequency domain structure of a mobile communication system according to one embodiment;

[0020] Figure 2 It is a view illustrating the structure of frames, subframes, and time slots of a mobile communication system according to one embodiment;

[0021] Figure 3 This is a view illustrating an example of the configuration of the bandwidth portion (BWP) in a wireless communication system according to one embodiment;

[0022] Figure 4 This is a view illustrating an example of configuring a control area of ​​a downlink control channel in a wireless communication system according to one embodiment;

[0023] Figure 5 This is a view illustrating the structure of a downlink control channel in a wireless communication system according to one embodiment;

[0024] Figure 6This is a view illustrating an example of frequency axis resource allocation in a Physical Downlink Shared Channel (PDSCH) in a wireless communication system according to one embodiment;

[0025] Figure 7 This is a view illustrating an example of time axis resource allocation for a PDSCH in a wireless communication system according to one embodiment;

[0026] Figure 8 This is a view illustrating an example of time axis resource allocation in a wireless communication system according to the subcarrier spacing of the data channel and the control channel, according to one embodiment.

[0027] Figure 9 This is a view illustrating a situation where multiple PUCCH resources used for HARQ-ACK transmission of PDSCH overlap when multi-slot repetition is not configured, according to one embodiment;

[0028] Figure 10 This is a view illustrating the case of PUCCH resource overlap when multiple time slots are configured for repetition, according to one embodiment;

[0029] Figure 11 This is a view showing the switching time required to switch between a transmit OFF state and a transmit ON state during uplink transmission of a terminal according to one embodiment;

[0030] Figure 12 This is a view illustrating the switching time required for a change in transmission power, a change in transmission RB, or frequency hopping in frequency range 1 (FR1) according to one embodiment;

[0031] Figure 13 This is a view illustrating the switching time required for a change in transmission power or transmission RB or frequency hopping in frequency range 2 (FR2) according to one embodiment;

[0032] Figure 14 This is a view illustrating the structure of the base station and terminal radio protocols when performing single-cell, carrier aggregation, and dual connectivity according to one embodiment;

[0033] Figure 15 This is a view illustrating an example of antenna port configuration and resource allocation for cooperative communication in a wireless communication system according to one embodiment;

[0034] Figure 16 This is a view illustrating an exemplary configuration of downlink control information (DCI) for cooperative communication in a wireless communication system according to one embodiment;

[0035] Figure 17aThis is a view illustrating a method for sending HARQ-ACK information when using a single PDCCH for NC-JT transmission in a wireless communication system according to one embodiment;

[0036] Figure 17b This is a view illustrating a method for transmitting joint HARQ-ACK information when using multiple PDCCHs for NC-JT transmission in a wireless communication system according to one embodiment;

[0037] Figure 17c This is a view illustrating a method for transmitting inter-slot time-division multiplexing HARQ-ACK information when using multiple PDCCHs for NC-JT transmission in a wireless communication system according to one embodiment;

[0038] Figure 17d This is a view illustrating a method for transmitting time-division multiplexing HARQ-ACK information within a time slot when using multiple PDCCHs for NC-JT transmission in a wireless communication system according to one embodiment;

[0039] Figure 17e This is a view illustrating an example of a method for a terminal to send HARQ-ACK information for NC-JT transmission to a base station in a wireless communication system according to one embodiment;

[0040] Figure 17f This is a view illustrating an example of a method for a base station to receive HARQ-ACK information for NC-JT transmission from a terminal in a wireless communication system according to one embodiment;

[0041] Figure 18a This is a view illustrating repeated PUCCH transmissions in a sub-slot unit of a wireless communication system according to one embodiment;

[0042] Figure 18b This is a view illustrating repeated PUCCH transmissions in a time slot or sub-time slot in a wireless communication system according to one embodiment;

[0043] Figure 18c This is another view illustrating repeated PUCCH transmissions in a time slot or sub-time slot in a wireless communication system according to one embodiment;

[0044] Figure 19 This is a view illustrating an example of the mapping rules between repeated PUCCH transmissions and transmit and receive points (TRPs) according to some embodiments;

[0045] Figure 20 The structure of a terminal in a wireless communication system according to one embodiment is shown; and

[0046] Figure 21The structure of a base station in a wireless communication system according to one embodiment is shown. Detailed Implementation

[0047] The following discussion Figures 1 to 21 The various embodiments described in this patent document to illustrate the principles of this disclosure are merely illustrative and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or apparatus.

[0048] Embodiments of this disclosure will be described in detail below with reference to the accompanying drawings.

[0049] In describing embodiments of this disclosure, descriptions relating to technical content well-known in the art and not directly related to this disclosure will be omitted. This omission of unnecessary descriptions is to prevent obscuring the main ideas of this disclosure and to more clearly convey them.

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

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

[0052] Here, it should be understood that each box in the flowchart description, and combinations of boxes in the flowchart description, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more flowchart boxes. These computer program instructions can also be stored in a computer-usable or computer-readable storage medium that can direct 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 functions specified in the one or more flowchart boxes. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus, thereby producing a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowchart boxes.

[0053] Furthermore, each box in the flowchart illustration may 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 described in the boxes may occur out of order. For example, depending on the functionality involved, two boxes shown consecutively may actually execute approximately simultaneously, or these boxes may sometimes execute in reverse order.

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

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

[0056] In the following description, for convenience, terms referring to broadcast information, terms referring to control information, terms related to communication coverage, terms referring to state changes (e.g., events), terms referring to network entities, terms referring to messages, terms referring to device elements, etc., are used by way of example. Therefore, this disclosure is not limited to the terms used below, and other terms that refer to the subject matter having equivalent technical meaning may be used.

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

[0058] Wireless communication systems have evolved from initially providing voice-oriented services to providing broadband wireless communication systems that offer high-speed and high-quality packet data services, such as 3GPP's High Speed ​​Packet Access (HSPA), Long Term Evolution (LTE) or Evolved Universal Terrestrial Radio Access (E-UTRA), LTE-Advanced (LTE-A), LTE-pro, 3GPP2's High Rate Packet Data (HRPD), Ultra Mobile Broadband (UMB), and the IEEE 802.16e communication standard.

[0059] In LTE systems, a representative example of broadband wireless communication systems, Orthogonal Frequency Division Multiplexing (OFDM) is used for the downlink (DL) and Single Carrier Frequency Division Multiple Access (SC-FDMA) for the uplink (UL). The uplink refers to the radio link through which a terminal (User Equipment) or mobile station (MS) transmits data or control signals to a base station (eNode B or base station (BS)), and the downlink refers to the radio link through which the base station transmits data or control signals to the terminal. The multiple access methods described above allocate and manipulate time-frequency resources to divide the data or control information for each user, ensuring that the data or control information carried by each user does not overlap, i.e., establishing orthogonality.

[0060] Future communication systems following LTE, namely 5G communication systems, should be able to freely reflect various needs such as those of users and service providers, and thus support services that meet diverse needs. Services considered for 5G communication systems include enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC).

[0061] According to some embodiments, eMBB is designed to provide improved data transmission rates than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, from the perspective of a base station, eMBB should be able to provide a maximum transmission rate of 20 Gbps in the downlink and a maximum transmission rate of 10 Gbps in the uplink. Simultaneously, it should provide increased user-perceived data rates for the terminal. To meet these requirements, improved transmission and reception technologies are needed, including more advanced multiple-input multiple-output (MIMO) transmission technologies. Furthermore, the data transmission rates required by 5G communication systems can be met by using a wider frequency bandwidth than 20 MHz in the 3 GHz to 6 GHz or 6 GHz or higher frequency bands, replacing the 2 GHz band currently used by LTE.

[0062] Meanwhile, in 5G communication systems, mMTC is considered to support application services such as the Internet of Things (IoT). To effectively deliver IoT, mMTC may require support for large-scale terminal access within a cell, improved terminal coverage, improved battery life, and reduced terminal costs. IoT attaches to various sensors and devices to provide communication capabilities, therefore it must be able to support a large number of terminals within a cell (e.g., 1,000,000 terminals / km²). Furthermore, because mMTC-enabled terminals are likely to be located in shadow areas not covered by cell coverage due to the nature of the service, such as building basements, they may require wider coverage compared to other services provided by 5G communication systems. mMTC-enabled terminals should be configured as low-cost devices, and due to the difficulty in frequently replacing their batteries, they may require very long battery life.

[0063] Finally, in the case of URLLC, it identifies a cellular-based wireless communication service for a specific purpose (mission-critical). URLLC must provide communication with ultra-low latency and ultra-reliability for remote control of robots or machinery, industrial automation, and services such as drones, remote healthcare, and emergency alerts. 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 also require design requirements to allocate wider resources in the frequency band. However, the above-mentioned mMTC, URLLC, and eMBB are merely examples of different service types, and the service types to which this disclosure applies are not limited to the examples above.

[0064] The services considered in the aforementioned 5G communication system should be provided by integrating them based on a unified framework. In other words, for effective resource management and control, it is best to integrate each service into a single system for control and transmission, rather than allowing them to operate independently.

[0065] Furthermore, although embodiments of this disclosure are described below as examples of LTE, LTE-A, LTE Pro, or NR systems, embodiments of this disclosure can be applied to other communication systems with similar technical backgrounds or channel types. Additionally, embodiments can be applied to other communication systems with modifications that, as determined by a person skilled in the art, do not significantly depart from the scope of this disclosure.

[0066] This disclosure relates to methods and apparatus for reporting channel state information in a wireless communication system to enhance the power-saving efficiency of a terminal.

[0067] According to this disclosure, when a terminal operates in power-saving mode in a wireless communication system, the power-saving effect can be further improved by correspondingly optimizing the method used to report channel state information.

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

[0069] Figure 1 This is a view illustrating the basic time-frequency domain structure of a mobile communication system according to one embodiment.

[0070] refer to Figure 1 The horizontal axis represents the time domain and the vertical axis represents the frequency domain. The basic unit of a resource in both the time and frequency domains is a resource element (RE) 1-01, which can define one orthogonal frequency division multiplexing (OFDM) symbol 1-02 on the time axis and one subcarrier 1-03 on the frequency axis. In the frequency domain, (For example, 12) consecutive REs can constitute a resource block (RB) 1-04. In one embodiment, multiple OFDM symbols can constitute a subframe 1-10.

[0071] Figure 2 It is a view showing the structure of frames, subframes and time slots of a mobile communication system according to one embodiment.

[0072] refer to Figure 2 A frame 2-00 can consist of one or more subframes 2-01, and a subframe can consist of one or more time slots 2-02. For example, a frame 2-00 can be defined as 10 ms. A subframe 2-01 can be defined as 1 ms, and in this case, a frame 2-00 can consist of a total of 10 subframes 2-01. A time slot 2-02 or 2-03 can be defined as 14 OFDM symbols (i.e., the number of symbols per time slot (...)). =14). A subframe 2-01 may consist of one or more time slots 2-02 or 2-03, and the number of time slots 2-02 or 2-03 in each subframe 2-01 may vary depending on the configuration value μ 2-04 or 2-05 for the subcarrier spacing.

[0073] exist Figure 2 The example demonstrates the cases where μ=0 (2-04) and μ=1 (2-05) are used as subcarrier spacing settings. When μ=0 (2-04), one subframe 2-01 can consist of one time slot 2-02, and when μ=1 (2-05), one subframe 2-01 can consist of two time slots 2-03. That is, the number of time slots per subframe... The number of time slots per frame can vary depending on the subcarrier spacing setting value μ, and therefore... It can be changed. The value μ is set according to the interval between each subcarrier. and It can be defined as shown in [Table 1].

[0074] [Table 1]

[0075]

[0076] In NR systems, a component carrier (CC) or serving cell can consist of up to 250 or more RBs. Therefore, when a terminal, like in LTE, always receives the entire serving cell bandwidth, its power consumption can be very high. To address this, the base station configures one or more bandwidth portions (BWPs) for the terminal. This allows the terminal to change its reception area within the cell. In NR, the base station can set the "initial BWP" for the terminal via the MIB, which is the bandwidth of CORESET #0 (or Common Search Space (CSS)). Below, the base station can set the terminal's initial BWP (first BWP) via RRC signaling and can notify at least one or more BWP configuration information that can be indicated in the future via downlink control information (DCI). Subsequently, the base station can notify the BWP ID via DCI to indicate which frequency band the terminal will use. If the terminal does not receive DCI in the currently allocated BWP for a certain period, the terminal returns to the "default BWP" and attempts to receive DCI.

[0077] Figure 3 This is a view illustrating an example of the configuration of the bandwidth portion (BWP) in a wireless communication system according to one embodiment.

[0078] refer to Figure 3 , Figure 3 An example is shown where terminal bandwidth 3-00 is configured as two bandwidth sections, namely bandwidth section #1 3-05 and bandwidth section #2 3-10. The base station can set one or more bandwidth sections for the terminal, and can set the information shown in Table 2 below for each bandwidth section.

[0079] [Table 2]

[0080]

[0081] Not limited to the examples above, and in addition to the configuration information described above, various parameters related to bandwidth sections can also be configured for the terminal. This information can be delivered to the terminal from the base station via higher-level signaling (e.g., RRC signaling). At least one of the configured bandwidth sections can be activated. Whether a configured bandwidth section is activated can be sent from the base station to the terminal in a semi-static manner via RRC signaling, or dynamically via the MAC control element (CE) or DCI.

[0082] According to one embodiment, a terminal prior to a Radio Resource Control (RRC) connection can receive an Initial Bandwidth Part (BWP) for initial access from a base station via a Master Information Block (MIB). More specifically, in order to receive the system information required for initial access (which may correspond to Remaining System Information (RMSI) or System Information Block 1 (SIB1)) via the MIB during the initial access step, the terminal can receive setting information regarding the control area (Control Resource Set (CORESET)) and search space where PDCCH can be transmitted. The control area and search space set as the MIB can be considered as identifier (ID) 0, respectively.

[0083] The base station can use the MIB to notify the terminal of information such as frequency allocation, time allocation, and parameter set configuration for control area #0. Additionally, the base station can use the MIB to notify the terminal of the monitoring period and timing settings for control area #0, i.e., the settings for search space #0. The terminal can consider the frequency domain of control area #0 configured to be obtained from the MIB as the initial bandwidth portion used for initial access. In this case, the identifier (ID) of the initial bandwidth portion can be considered as 0.

[0084] The bandwidth portion supported by the aforementioned next-generation mobile communication systems (5G or NR systems) can be configured for various purposes.

[0085] For example, when the bandwidth supported by the terminal is less than the system bandwidth, the bandwidth supported by the terminal can be increased by configuring the bandwidth portion. For example, in [Table 2], the frequency position of the bandwidth portion is configured for the terminal (Configuration Information 2), so that the terminal can send or receive data at a specific frequency position in the system bandwidth.

[0086] As another example, to support different parameter sets, a base station can configure multiple bandwidth sections for a terminal. For instance, to support the transmission and reception of data to any terminal using subcarrier spacings of 15 kHz and 30 kHz, the two bandwidth sections can be configured to use subcarrier spacings of 15 kHz and 30 kHz, respectively. The different bandwidth sections can be frequency division multiplexing (FDM), and the bandwidth section configured under the corresponding subcarrier spacing can be activated when data is transmitted / received at a specific subcarrier spacing.

[0087] For example, to reduce terminal power consumption, base stations can allocate bandwidth portions with different sizes for each terminal. For instance, if a terminal supports a very large bandwidth, such as 100 MHz, and always sends and receives data through that bandwidth, it could result in very high power consumption. Specifically, unnecessary downlink control channel monitoring across a large 100 MHz bandwidth when there is no service is highly inefficient in terms of power consumption. Therefore, to reduce terminal power consumption, base stations can allocate relatively small bandwidth portions for the terminal, such as 20 MHz. When there is no service, the terminal can perform monitoring operations within the 20 MHz bandwidth portion, and when data is generated, the terminal can use the 100 MHz bandwidth portion to send and receive data according to the base station's instructions.

[0088] In the above method for configuring the bandwidth portion, the terminal prior to the RRC connection can receive configuration information about the initial bandwidth portion via the Master Information Block (MIB) during the initial access step. More specifically, the terminal can be configured with a Control Resource Set (CORESET) for the downlink control channel, through which the Distributed System Information Block (SIB) DCI can be transmitted from the MIB of the Physical Broadcast Channel (PBCH). The bandwidth of the control area set as the MIB can be regarded as the initial bandwidth portion, and the terminal can receive the PDSCH of the transmitted SIB through it via the configured initial bandwidth portion. In addition to using the receive SIB, the initial bandwidth portion can also be used for other System Information (OSI), paging, and random access.

[0089] The synchronization signal (SS) / PBCH block of next-generation mobile communication systems (5G or NR systems) will be described below.

[0090] An SS / PBCH block can refer to a physical layer channel block consisting of a primary SS (PSS), secondary SS (SSS), and PBCH. More specifically, an SS / PBCH block can be defined as follows.

[0091] -PSS: PSS is a signal used as a downlink time / frequency synchronization reference and can provide some information about the cell ID.

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

[0093] -PBCH: The PBCH can provide the basic system information required for the terminal to transmit and receive data and control channels. Basic system information may include search space-related control information indicating radio resource mapping information for the control channel, scheduling control information for separate data channels used to transmit system information, etc.

[0094] -SS / PBCH Blocks: SS / PBCH blocks can be composed of combinations of PSS, SSS, and PBCH. One or more SS / PBCH blocks can be sent within a 5 ms time interval, and each sent SS / PBCH block can be distinguished by an index.

[0095] The terminal can detect the PSS and SSS during the initial access phase and can decode the PBCH. The terminal can obtain the MIB from the PBCH and receive control area #0 set via the MIB. Assuming the selected SS / PBCH block and the demodulation reference signal (DMRS) transmitted in control area #0 are quasi-co-located (QCL), the terminal can perform monitoring of control area #0. The terminal can receive system information from the downlink control information transmitted in control area #0. The terminal can obtain configuration information related to the random access channel (RACH) required for initial access from the received system information. Considering the selected SS / PBCH index, the terminal can transmit the physical RACH (PRACH) to the base station, and the base station receiving the PRACH can obtain information about the SS / PBCH block index selected by the terminal. The base station monitors control area #0 corresponding to (or associated with) the SS / PBCH block selected by the terminal and the block selected by the terminal from the SS / PBCH block.

[0096] The following text will describe in detail the downlink control information (hereinafter referred to as "DCI") in next-generation mobile communication systems (5G or NR systems).

[0097] In next-generation mobile communication systems (5G or NR systems), scheduling information for uplink data (or Physical Uplink Shared Channel (PUSCH)) or downlink data (or Physical Downlink Data Channel (PDSCH)) can be delivered from the base station to the terminal via DCI. The terminal can monitor the DCI format used for fallback and the non-fallback DCI format used for PUSCH or PDSCH. The fallback DCI format can consist of fixed fields predetermined between the base station and the terminal, while the non-fallback DCI format can include configurable fields.

[0098] DCI messages can be transmitted via the Physical Downlink Control Channel (PDCCH) through channel coding and modulation processes. 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 terminal's identity. Depending on the purpose of the DCI message—e.g., UE-specific data transmission, power control commands, or random access responses—the RNTI can be used to scramble the CRC of the payload appended to the DCI message. That is, the RNTI is not explicitly sent but can be included in and transmitted during the CRC calculation process. When a DCI message is received on the PDCCH, the terminal can use the assigned RNTI to check the CRC. If the CRC check result is correct, the terminal knows that the message has been sent.

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

[0100] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, and in this case, CRC can be scrambled with C-RNTI. In one embodiment, DCI format 0_0 with CRC scrambled with C-RNTI may include information as shown in Table 3.

[0101] [Table 3]

[0102]

[0103] DCI format 1_0 can be used as a non-back-off DCI for scheduling PUSCH, and in this case, CRC can be scrambled with C-RNTI. In one embodiment, DCI format 0_1, where CRC is scrambled with C-RNTI, may include information as shown in Table 4.

[0104] [Table 4]

[0105]

[0106]

[0107] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, and in this case, CRC can be scrambled with C-RNTI. In one embodiment, DCI format 1_0 where CRC is scrambled with C-RNTI may include information as shown in Table 5.

[0108] [Table 5]

[0109]

[0110] Alternatively, DCI format 1_0 can be used as the DCI for scheduling PDSCH for RAR messages, and in this case, CRC can be scrambled with RA-RNTI. The DCI format 1_0 with CRC scrambled with C-RNTI can include information as shown in Table 6.

[0111] [Table 6]

[0112]

[0113] DCI format 1_1 can be used as a non-back-off DCI for scheduling PDSCH, and in this case, CRC can be scrambled with C-RNTI. In one embodiment, DCI format 1_1 where CRC is scrambled with C-RNTI may include information as shown in Table 7.

[0114] [Table 7]

[0115]

[0116] Figure 4 This is a view illustrating the control area of ​​a downlink control channel configured in a wireless communication system according to one embodiment. That is, Figure 4 This is a view illustrating an embodiment of a control resource set (CORESET) for transmitting a downlink control channel in a 5G wireless communication system, according to one embodiment.

[0117] refer to Figure 4 , Figure 4 An embodiment is shown in which a UE bandwidth portion 4-10 on the frequency axis and two control regions (control region #1 4-01 and control region #2 4-02 within one timeslot 4-20 on the time axis) are configured. Control regions 4-01 and 4-02 can be configured within a specific frequency resource 4-03 within the entire terminal bandwidth portion 4-10 on the frequency axis. Control regions 4-01 and 4-02 can be configured as one or more OFDM symbols on the time axis, which can be defined as a control resource set duration 4-04. Reference Figure 4Control region #1 4-01 can be configured to a control region length of 2 symbols, and control region #2 4-02 can be configured to a control region length of 1 symbol.

[0118] In next-generation mobile communication systems (5G or NR systems), the control region can be configured for the terminal by the base station executing higher-level signaling (e.g., system information, master information block (MIB), radio resource control (RRC) signaling). Setting up a control region for a terminal involves providing information such as the control region identifier, the frequency location of the control region, and the symbol length of the control region. For example, setting up the control region may include information as shown in Table 8.

[0119] [Table 8]

[0120]

[0121] In Table 8, the tci-StatesPDCCH (hereinafter referred to as "TCI state") configuration information may include information about one or more Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block indices or Channel State Information Reference Signal (CSI-RS) indices that have a quasi-co-address (QCL) relationship with the DMRS transmitted in the corresponding control area.

[0122] In a wireless communication system, one or more different antenna ports (which may alternatively be replaced by one or more channels, signals and combinations thereof, but in this disclosure, different antenna ports are collectively referred to as different antenna ports) can be associated with each other through QCL configuration, as shown in Table 9.

[0123] [Table 9]

[0124]

[0125] Specifically, in a QCL configuration, two different antenna ports can be connected as a (QCL) target antenna port and a (QCL) reference antenna port, and the terminal can apply (or assume) all or part of the statistical characteristics of the channel measured at the reference antenna port when receiving at the target antenna port (e.g., large-scale channel parameters such as Doppler shift, Doppler spread, average delay, delay spread, average gain, spatial Rx (or Tx) parameters, or the terminal's receive spatial filtering coefficients or transmit spatial filtering coefficients). In the above context, the target antenna port refers to the antenna port used to transmit a channel or signal configured by a higher-level setting including the QCL setting, or a channel or antenna port used to transmit a signal applying a TCI state indicating the QCL setting. In the above context, the reference antenna port refers to the antenna port used to transmit a channel or signal indicated (specified) by reference signal parameters in the QCL configuration.

[0126] Specifically, the statistical characteristics of a channel defined by the QCL settings (indicated by the QCL-type parameter in the QCL configuration) can be classified according to the QCL type as follows.

[0127] ○ "QCL-Type A": {Doppler frequency shift, Doppler spread, average delay, delay spread}

[0128] ○ "QCL-Type B": {Doppler frequency shift, Doppler spread}

[0129] ○ "QCL-Type C": {Doppler shift, average delay}

[0130] ○ "QCL-Type D": {Space Rx parameter}

[0131] In this context, the QCL type is not limited to the four types mentioned above; however, to avoid confusion, not all possible combinations are listed. In QCL-Type A above, the bandwidth and transmission portion of the target antenna port are sufficient compared to the reference antenna port (i.e., when the number of samples and transmission bandwidth / time at the target antenna port are greater than those at the reference antenna port), and QCL-Type A is the QCL type used when all statistical characteristics measurable on the frequency and time axes can be referenced. QCL-Type B is the QCL type used when the bandwidth of the target antenna port is sufficient to measure statistical characteristics measurable on the frequency axis (i.e., Doppler shift and Doppler spread). QCL-Type C is the QCL type used when the bandwidth and transmission spacing of the target antenna port are insufficient to measure second-order statistics, i.e., Doppler spread and delay spread, so that only first-order statistics, i.e., Doppler shift and average delay, can be referenced. QCL-Type D is the QCL type set when the spatial receiving filter value used when receiving the reference antenna port can be used when receiving the target antenna port.

[0132] Meanwhile, the base station can set or indicate up to two QCL settings for a target antenna port through the following TCI status settings.

[0133]

[0134] Between two QCL settings included in a TCI state setting, the first QCL setting can be configured as one of QCL-Type A, QCL-Type B, and QCL-Type C. The configurable QCL type is specified based on the type of the target antenna port and the reference antenna port, as described in detail below. Furthermore, in a TCI state setting with two QCL settings, the second QCL setting can be configured as QCL-Type D and may be omitted in some cases.

[0135] Tables 9-1 to 9-5 below show the valid TCI status settings based on the target antenna port type.

[0136] Table 9-1 shows the valid TCI state settings when the target antenna port is a CSI-RS (TRS) for tracking. TRS refers to an NZP CSI-RS where no repetition parameter is configured between CSI-RSs and the trs-info is configured as true. Setting 3 in Table 9-1 can be used for aperiodic TRS.

[0137] [Table 9-1] Effective TCI State Settings When the Target Antenna Port is a CSI-RS (TRS) for Tracking

[0138]

[0139] Table 9-2 shows the valid TCI state settings when the target antenna port is a CSI-RS for CSI. A CSI-RS for CSI refers to an NZP CSI-RS in which no duplicate parameters are configured between CSI-RSs and the trs-information is configured as true.

[0140] [Table 9-2] Effective TCI Status Settings When the Target Antenna Port is a CSI-RS for CSI

[0141]

[0142] Table 9-3 shows the valid TCI status configuration when the target antenna port is a CSI-RS for beam management (with the same meaning as BM and CSI-RS for L1 RSRP reporting). A CSI-RS for BM refers to an NZP CSI-RS in which repeated parameters are configured between CSI-RS and have on or off values ​​and the trs-info is not configured as true.

[0143] [Table 9-3] Valid TCI state configuration when the target antenna port is for CSI-RS for BM (for L1 RSRP reporting).

[0144]

[0145] Table 9-4 shows the valid TCI state settings when the target antenna port is PDCCH DMRS.

[0146] [Table 9-4] Effective TCI State Settings When the Target Antenna Port is PDCCH DMRS

[0147]

[0148] Table 9-5 shows the valid TCI status settings when the target antenna port is PDSCH DMRS.

[0149] [Table 9-5] Effective TCI State Settings When the Target Antenna Port is PDSCH DMRS

[0150]

[0151] In the typical QCL setup methods according to Tables 9-1 to 9-5, the target antenna port and reference antenna port for each step are selected from "SSB" → "TRS" → "CSI-RS for CSI, CSI-RS for BM, PDCCH DMRS, or PDSCHDMRS". This allows the terminal's reception operation to be aided by linking statistical characteristics measurable from the SSB and TRS to each antenna port.

[0152] Figure 5 This is a view illustrating the structure of a downlink control channel in a wireless communication system according to one embodiment. That is, Figure 5 This is a view illustrating examples of basic units constituting the time and frequency resources of a downlink control channel that can be used in 5G, according to embodiments of the present disclosure.

[0153] refer to Figure 5 The basic unit constituting the time and frequency resources of the control channel can be defined as a resource element group (REG) 5-03. REG 5-03 can be defined as one OFDM symbol 5-01 on the time axis and one physical resource block (PRB) 5-02 on the frequency axis, i.e., 12 subcarriers. The base station can configure the downlink control channel allocation unit by connecting REG 5-03.

[0154] like Figure 5 As shown, when the basic unit allocated to the downlink control channel in 5G is a control channel element (CCE) 5-04, one CCE 5-04 can be composed of multiple REG 5-03s. For example, Figure 5 A REG 5-03 in a CCE 5-04 can consist of 12 REs, and if one CCE 5-04 consists of 6 REG 5-03s, then one CCE 5-04 can consist of 72 REs. When configuring a downlink control area, the corresponding area can consist of multiple CCE 5-04s, and a specific downlink control channel, as one or more CCE 5-04s, can be mapped and transmitted according to the aggregation level (AL) within the control area. CCE 5-04s in the control area are classified by number, and the numbers of CCE 5-04s can be allocated according to a logical mapping method.

[0155] As Figure 5 The REG (5-03), the basic unit of the downlink control channel, can include the RE to which the DCI is mapped and the region to which the DMRS 5-05, serving as a reference signal for decoding, is mapped. For example... Figure 5 As shown, three DMRS 5-05s can be transmitted within one REG 5-03. Depending on the aggregation level (AL), the number of CCEs required to transmit the PDCCH can be 1, 2, 4, 8, or 16, and different numbers of CCEs can be used to achieve link adaptation for the downlink control channel. For example, when AL=L, one downlink control channel can be transmitted using L CCEs.

[0156] The terminal needs to detect signals without knowing information about the downlink control channels, and for this blind decoding, a search space indicating a set of CCEs can be defined. The search space is a set of downlink control channel candidates, consisting of the CCEs the terminal should attempt to decode at a given aggregation level. Since there are various aggregation levels that constitute a bundle with 1, 2, 4, 8, and 16 CCEs, the terminal may have multiple search spaces. The set of search spaces can be defined as a set of search spaces across all configured aggregation levels.

[0157] The search space can be categorized into a common search space or a UE-specific search space. According to one embodiment, a group of terminals or all terminals can search the common search space of the PDCCH to receive common cell control information, such as dynamic scheduling or paging messages for system information.

[0158] For example, a terminal can receive PDSCH scheduling and allocation information for transmitting SIBs, including cell operator information, by searching the common search space of the PDCCH. In the case of a common search space, since a group of terminals or all terminals must receive the PDCCH, the common search space can be defined as a set of predetermined CCEs. Simultaneously, a terminal can receive scheduling and allocation information for a specific terminal's PDSCH or PUSCH by searching the specific terminal search space of the PDCCH. The specific terminal search space can be defined terminal-specifically based on the terminal's identifier and various system parameters.

[0159] In 5G systems, parameters for the search space used for PDCCH can be configured from the base station to the terminal via higher-level signaling (e.g., SIB, MIB, RRC signaling). For example, the base station can configure the terminal the number of PDCCH candidates under each aggregation level L, the monitoring period of the search space, the monitoring timing in symbol cells within the time slots of the search space, the search space type (public search space or terminal-specific search space), the combination of DCI format and RNTI to be monitored in the search space, and the control area index used for monitoring the search space. These settings can include information as shown in Table 10.

[0160] [Table 10]

[0161]

[0162]

[0163] The base station can set one or more search space sets for the terminal based on configuration information. According to one embodiment, the base station can set search space set 1 and search space set 2 for the terminal, and configure a DCI format A scrambled with X-RNTI in search space set 1 to be monitored in a common search space. Additionally, a DCI format B scrambled with Y-RNTI in search space set 2 can be configured to be monitored in a specific terminal search space.

[0164] Depending on the settings, one or more search space sets can exist in a public search space or a specific terminal 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 a specific terminal search space.

[0165] Public search spaces can be categorized into a specific set of search spaces based on their purpose. For each type of ensemble search space, the RNTIs to be monitored may differ. For example, public search space type, purpose, and RNTIs to be monitored can be categorized as follows.

[0166]

[0167] Additionally, the following combinations of DCI formats and RNTI can be monitored in the public search space. This is not limited to the examples below.

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

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

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

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

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

[0173] Within a specific terminal search space, combinations of the following DCI formats and RNTI can be monitored. This is not limited to the examples below.

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

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

[0176] The specified RNTI can follow the following definitions and uses.

[0177] Cell RNTI (SI-RNTI): Used for PDSCH scheduling of specific terminals.

[0178] Temporary Cell RNTI (TC-RNTI): Used for PDSCH scheduling of specific terminals.

[0179] Configured Scheduling RNTI (CS-RNTI): For PDSCH scheduling of specific terminals in a semi-static configuration.

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

[0181] Paging RNTI (P-RNTI): PDSCH scheduling used for paging transmission

[0182] System Information RNTI (SI-RNTI): Used for PDSCH scheduling in which system information is transmitted.

[0183] Interrupt RNTI (INT-RNTI): Used to notify PDSCH whether pruning is in progress.

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

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

[0186] Transmission Power Control (TPC-SRS-RNTI) of SRS RNTI: Used to indicate power control commands of the SRS.

[0187] In one embodiment, the DCI format described above can be defined as shown in Table 11 below.

[0188] [Table 11]

[0189]

[0190] According to one embodiment, in a 5G system, multiple search space sets can be configured with different parameters (e.g., parameters in [Table 10]). Accordingly, the set of search space sets monitored by the terminal can change at each point in time. For example, if search space set #1 is configured for an X-timeslot period, search space set #2 is configured for a Y-timeslot period, and X and Y are different, then the terminal searches for search space set #1 in a specific timeslot. Both space sets #2 can be monitored, and one of search space set #1 and search space set #2 can be monitored in a specific timeslot.

[0191] When configuring multiple search space sets in a terminal, the following conditions can be considered to determine which search space sets the terminal should monitor.

[0192] [Condition 1: Limit the maximum number of PDCCH candidates]

[0193] The number of PDCCH candidates that can be monitored in each time slot can not exceed Mμ. Mμ can be defined as the maximum number of PDCCH candidate groups in each time slot in a cell with a subcarrier spacing of 15.2 μ kHz, and can be defined as shown in Table 12 below.

[0194] [Table 12]

[0195]

[0196] [Condition 2: Limit the maximum number of CCEs]

[0197] The number of CCEs constituting the entire search space in each time slot (here, the entire search space can refer to the entire set of CCEs corresponding to the joint region of multiple search space sets) can not exceed Cμ. Cμ can be defined as the maximum number of CCEs in each time slot in a cell with a subcarrier spacing of 15.2 μkHz, and can be defined as shown in Table 13 below.

[0198] [Table 13]

[0199]

[0200] For ease of explanation, the situation where both conditions 1 and 2 are satisfied at a specific point in time can be exemplarily defined as "condition A". Therefore, not satisfying condition A may mean that at least one of conditions 1 and 2 above is not satisfied.

[0201] Depending on the base station's search space set settings, there may be instances where condition A is not met at a specific time point. If condition A is not met at a specific time point, the terminal can select and monitor only a portion of the search space set that is set to meet condition A at that specific time point, and the base station can send the PDCCH to the selected search space set.

[0202] According to one embodiment, the following method can be followed as a way to select some search spaces from the entire set of search spaces.

[0203] [Method 1]

[0204] When PDCCH condition A is not met at a specific time point (time slot).

[0205] A terminal (or base station) can preferentially select a search space set whose search space type is configured as a public search space from the search space set that exists at the corresponding time point in the search space set configured as a specific terminal search space set.

[0206] When all search space sets configured as public search spaces are selected (i.e., if condition A is satisfied even after selecting all search spaces configured as public search spaces), the terminal (or base station) can select a search space set configured as a specific terminal search space. In this case, when multiple search space sets are configured as a specific terminal search space, the search space set with a lower search space set index can have a higher priority. Considering the priority, the terminal or base station can select a specific terminal search space set within the range that satisfies condition A.

[0207] The methods for allocating time and frequency resources for data transmission in NR are described below.

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

[0209] Figure 6 This is a view illustrating an example of frequency axis resource allocation for a PDSCH in a wireless communication system according to one embodiment.

[0210] Figure 6It is a view that shows three frequency axis resource allocation methods that can be configured through the upper layer of the NR system: Type 0 6-00, Type 1 6-05, and Dynamic Switching 6-10.

[0211] refer to Figure 6 If the terminal is configured to use resource type 0 only via higher-layer signaling 6-00, some downlink control information (DCI) allocated to the UE via PDSCH has a bitmap consisting of NRBG bits. The conditions for this will be described later. In this case, NRBG refers to the number of resource block groups (RBGs) determined by the BWP size allocated by the BWP indicator and the upper-layer parameter rbg-size, as shown in Table 14 below, and data is sent to the RBG indicated by the bitmap as 1.

[0212]

[0213] If the terminal is configured to use resource type 1 only via higher-layer signaling (6-05), then some DCIs that allocate PDSCH to the corresponding terminal have the following characteristics: Frequency axis resource allocation information consisting of bits. Its conditions will be described later. Thus, the base station can set the starting VRB 6-20 and the length of the frequency axis resources continuously allocated from it 6-25.

[0214] If the terminal is configured to use both resource type 0 and resource type 1 via higher-layer signaling 6-10, then some DCIs allocating PDSCH to the corresponding terminal have frequency axis resource allocation information. This frequency axis resource allocation information consists of bits 6-35, which is the larger of the payload 6-15 used to set resource type 0 and the payload 6-20 and 6-25 used to set resource type 1. The conditions will be described later. In this case, a bit can be added to the first part (MSB) of the frequency axis resource allocation information in the DCI, and if the corresponding bit is 0, it indicates the use of resource type 0, and if the corresponding bit is 1, it indicates the use of resource type 1.

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

[0216] The base station can configure time-domain resource allocation information tables for the Physical Downlink Data Channel (PDSCH) and Physical Uplink Data Channel (PUSCH) for terminals as higher-layer signaling (e.g., RRC signaling). For PDSCH, a table consisting of maxNrofDL-allocation = 16 entries can be configured, and for PUSCH, a table consisting of maxNrofUL-allocation = 16 entries can be configured. In one embodiment, the time-domain resource allocation information may include PDCCH-to-PDSCH time slot timing (corresponding to the time interval in time slots between the time of receiving PDCCH and the time of sending PDSCH scheduled by the received PDCCH, and denoted as K0), PDCCH-to-PUSCH time slot timing (corresponding to the time interval in time slots between the time of receiving PDCCH and the time of sending PUSCH scheduled by the received PDCCH, and denoted as K2), information about the position and length of the start symbol for scheduling PDSCH or PUSCH within a time slot, and the mapping type of PDSCH or PUSCH. For example, information such as [Table 15] or [Table 16] can be notified from the base station to the terminal.

[0217] [Table 15]

[0218]

[0219] [Table 16]

[0220]

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

[0222] Figure 7 This is a view illustrating an example of time axis resource allocation for a PDSCH in a wireless communication system according to one embodiment.

[0223] refer to Figure 7 The base station can use the data channels and control channels set by the upper layer ( , The time axis position of the PDSCH resource is indicated by the subcarrier spacing (SCS), scheduling offset value K0, and the OFDM symbol start position (7-00) and length (7-05) within a time slot dynamically indicated by DCI.

[0224] Figure 8This is a view illustrating an example of time-axis resource allocation based on the subcarrier spacing of the data channel and the control channel in a wireless communication system according to one embodiment.

[0225] refer to Figure 8 It can be seen that when the subcarrier spacing of the data channel and the control channel is the same (8-00), When the number of time slots for data and control is the same, a scheduling offset occurs in the base station and terminal according to the predetermined time slot offset K0. On the other hand, it can be seen that when the subcarrier spacing of the data channel and the control channel is different (8-05, Due to the different number of time slots for data and control, the subcarrier spacing based on PDCCH in the base station and terminal is scheduled to be offset according to the predetermined time slot offset K0.

[0226] In an NR system, the terminal sends uplink control information (UCI) to the base station via PUCCH. The control information may include at least one of the following: a HARQ-ACK indicating the success or failure of demodulation / decoding of a transport block (TB) received by the UE via PDSCH; a scheduling request (SR) requesting resource allocation from the terminal to the PUSCH base station for uplink data transmission; and channel state information (CSI), which is used to report the channel state of the terminal.

[0227] Based on the length of the allocated symbols, PUCCH resources can be broadly categorized into long PUCCHs and short PUCCHs. In NR, a long PUCCH has a length of 4 symbols or longer in a time slot, while a short PUCCH has a length of 2 symbols or shorter in a time slot.

[0228] More specifically, regarding long PUCCH, long PUCCH can be used to improve uplink cell coverage and therefore can be transmitted in a DFT-S-OFDM scheme as a single-carrier transmission rather than OFDM transmission. Long PUCCH supports transmission formats such as PUCCH format 1, PUCCH format 3, and PUCCH format 4, depending on the number of bits of control information supported and whether terminal multiplexing is supported through Pre-DFT OCC support at the IFFT front-end.

[0229] First, PUCCH format 1 is a long PUCCH format based on DFT-S-OFDM, capable of supporting up to 2 bits of control information and using as many frequency resources as 1RB. The control information can consist of a combination of HARQ-ACK and SR, or either individually. In PUCCH format 1, OFDM symbols including the demodulation reference signal (DMRS) as a demodulation reference signal (or reference signal) and OFDM symbols including UCI are repeatedly configured.

[0230] For example, when the number of transmitted symbols in PUCCH format 1 is 8, the first start symbol of the 8 symbols consists of the DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, and UCI symbol, respectively. The DMRS symbol uses orthogonal codes (or orthogonal sequences or extended codes) on the time axis. The sequence is expanded to a length corresponding to 1 RB on the frequency axis within an OFDM symbol and sent after the IFFT.

[0231] The UCI symbol is generated as follows. The terminal generates d(0) by modulating 1-bit control information with BPSK and 2-bit control information with QPSK. The generated d(0) is multiplied by a sequence corresponding to the length of 1 RB on the frequency axis for scrambling. Orthogonal codes (or orthogonal sequences or extended codes, w) on the time axis are used. i (m) is used to expand the scrambled sequence and then sent after performing an IFFT.

[0232] The terminal generates a sequence based on group frequency hopping or sequence frequency hopping configuration and a set ID set to the higher signal from the base station, and generates a sequence corresponding to a length of 1 RB by cyclically shifting the generated sequence, wherein the initial cyclic shift (CS) value is set to the higher signal.

[0233] When the length of the extension code (NSF) is given, Determined as And this is explained in detail in Table 16 below. In the above, i represents the index of the extension code itself, and m represents the index of the element of the extension code. Here, the numbers in [] in Table 16 indicate, for example, if the length of the extension code is 2, and the index of the extension code is set to i=0, the extension code w i (m) becomes , And w i (m) = [1 1].

[0234]

[0235] Next, PUCCH format 3 is a long PUCCH format based on DFT-S-OFDM, which can support more than 2 bits of control information and the number of RBs used can be configured by the upper layer. The control information can be composed of a combination or individually of HARQ-ACK, SR, and CSI. In PUCCH format 3, the position of the DMRS symbol is indicated by whether frequency hopping is performed in the time slot and whether additional DMRS symbols are configured, as shown in Table 17 below.

[0236] [Table 17]

[0237]

[0238] For example, when the number of transmission symbols in PUCCH format 3 is 8, the first start symbol of the 8 symbols begins with 0, and DMRS is transmitted in the first and fifth symbols. The table above also applies to the DMRS symbol positions in PUCCH format 4.

[0239] Next, PUCCH format 4 is a long PUCCH format based on DFT-S-OFDM, capable of supporting more than 2 bits of control information and using the same number of frequency resources as 1 RB. Control information can consist of a combination of HARQ-ACK, SR, and CSI, or each of them individually. The difference between PUCCH format 4 and PUCCH format 3 is that, in the case of PUCCH format 4, multiple terminals' PUCCH format 4 can be multiplexed within one RB. Multiple terminals' PUCCH format 4 can be multiplexed by applying Pre-DFT OCCs to the control information preceding the IFFT. However, the number of control information symbols that a terminal can transmit decreases depending on the number of multiplexed terminals. The number of multiplexed terminals, i.e., the number of different OCCs that can be used, can be 2 or 4, and the number of OCCs and the OCC indexes to be applied can be configured through higher layers.

[0240] Next, the short PUCCH will be described. The short PUCCH can be transmitted in both the downlink center time slot and the uplink center time slot. Typically, the short PUCCH can be transmitted at the last symbol or the last OFDM symbol of a time slot (e.g., the last OFDM symbol, the second OFDM symbol from the end, or the last two OFDM symbols). Of course, the short PUCCH can also be transmitted at any position within a time slot. Furthermore, a short PUCCH can be transmitted using one or two OFDM symbols. The short PUCCH can be used to reduce latency compared to the long PUCCH when uplink cell coverage is good, and it is transmitted in the CP-OFDM scheme.

[0241] Short PUCCH supports transmission formats such as PUCCH Format 0 and PUCCH Format 2, depending on the number of control information bits supported. First, PUCCH Format 0 is a short PUCCH format capable of supporting up to 2 bits of control information and using 1 RB of frequency resources. The control information can consist of a combination of HARQ-ACK and SR, or each of them individually. PUCCH Format 0 does not transmit DMRS, but only transmits a sequence of 12 subcarriers mapped onto a frequency axis within an OFDM symbol. The terminal generates a sequence based on group frequency hopping or sequence frequency hopping configuration and a set ID set to higher signals from the base station. The generated sequence is cyclically shifted to a final cyclic shift (CS) value, obtained by adding another CS value based on whether the initial CS value is ACK or NACK. The terminal then maps the shifted sequence onto the 12 subcarriers and transmits it.

[0242] For example, when HARQ-ACK is 1 bit, as shown in Table 18 below, if it is ACK, 6 is added to the initial CS value to generate the final CS; if it is NACK, 0 is added to the initial CS to generate the final CS. The standard defines the CS value of 0 for NACK and the CS value of 6 for ACK, and the terminal always generates PUCCH format 0 based on this value to send a 1-bit HARQ-ACK.

[0243] [Table 18]

[0244]

[0245] For example, when HARQ-ACK is 2 bits, if it is (NACK, NACK), as shown in Table 19 below, then 0 is added to the initial CS value; if it is (NACK, ACK), then 3 is added to the initial CS value; if it is (ACK, ACK), then 6 is added to the initial CS value; and if it is (ACK, NACK), then 9 is added to the initial CS value. The standard defines CS values ​​of 0 for (NACK, NACK), 3 for (NACK, ACK), 6 for (ACK, ACK), and 9 for (ACK, NACK). The terminal always sends a 2-bit HARQ-ACK by generating PUCCH format 0 based on this value.

[0246] If the final CS value exceeds the CS value of 12 added to the initial CS value based on ACK or NACK, then modulo 12 is applied to the final CS value because the sequence length is 12.

[0247] [Table 19]

[0248]

[0249] Next, PUCCH format 2 is a short PUCCH format that supports more than 2 bits of control information, and the number of RBs used can be configured by the upper layer. Control information can consist of a combination of HARQ-ACK, SR, and CSI, or each of them individually. In PUCCH format 2, as... Figure 4 As shown, when the index of the first subcarrier is #0, the positions of the subcarriers transmitting the DMRS within an OFDM symbol are fixed at indices #1, #4, #7, and #10. Control information is mapped to the remaining subcarriers, excluding the subcarrier containing the DMRS, through a channel-coded modulation process.

[0250] In summary, the values ​​that can be configured for each of the above PUCCH formats and their ranges can be arranged as shown in Table 20 below. If a value does not need to be configured in Table 20, it is represented as NA.

[0251] [Table 20]

[0252]

[0253] Meanwhile, in order to improve uplink coverage, PUCCH formats 1, 3 and 4 can support multi-slot repetition, and PUCCH repetition can be configured for each PUCCH format.

[0254] The terminal repeatedly transmits PUCCHs including UCIs, the same number of times as the number of slots configured via nrof slots (nrofSlot, which is higher-layer signaling). For repeated PUCCH transmissions, the same number of consecutive symbols can be used in each slot, and the corresponding consecutive symbols can be configured via nrof symbols (nrofSymbol, which is higher-layer signaling) in PUCCH-Format 1, PUCCH-Format 3, or PUCCH-Format 4. For repeated PUCCH transmissions, the same number of start symbols can be used in each slot, and the corresponding start symbols can be configured via startingSymbolIndex (startingSymbolIndex, which is higher-layer signaling) in PUCCH-Format 1, PUCCH-Format 3, or PUCCH-Format 4.

[0255] For repeated PUCCH transmissions, if the terminal has been configured to perform frequency hopping in different time slots during PUCCH transmissions, the terminal performs frequency hopping on a time slot basis. Additionally, in even-numbered time slots, if the terminal has been configured to perform frequency hopping in different time slots during PUCCH transmissions, the terminal begins PUCCH transmission from the first PRB index configured via the startingPRB (which is a higher-layer signaling). In odd-numbered time slots, the terminal begins PUCCH transmission from the second PRB index configured via the secondHopPRB (which is a higher-layer signaling).

[0256] Additionally, if the terminal is configured to perform frequency hopping in PUCCH transmissions across different time slots, the index of the time slot instructing the terminal to send the first PUCCH is 0, and the number of repeated PUCCH transmissions is incremented in each time slot, regardless of the PUCCH transmission being performed, during the configured total number of repeated PUCCH transmissions. If the terminal is configured to perform frequency hopping in PUCCH transmissions across different time slots, the terminal does not expect to configure frequency hopping in that time slot when sending a PUCCH. If the terminal is not configured to perform frequency hopping in PUCCH transmissions across different time slots, but is configured to perform frequency hopping within a time slot, the first and second PRB indices are applied equally in that time slot.

[0257] Next, the PUCCH resource configuration for the base station or terminal is described. The base station can configure the PUCCH resources for each BWP for a specific terminal through the upper layer. The configuration can be shown in Table 21.

[0258] [Table 21]

[0259]

[0260] According to the table above, one or more PUCCH resource sets can be configured in the PUCCH resource settings for a specific BWP, and the maximum payload value for UCI transmission can be configured in some PUCCH resource sets. Each PUCCH resource set can belong to one or more PUCCH resources, and each PUCCH resource can belong to one of the PUCCH formats mentioned above.

[0261] For PUCCH resource sets, the maximum payload value of the first PUCCH resource set can be fixed at 2 bits, and therefore the corresponding value does not need to be configured separately by the upper layer. When configuring the remaining PUCCH resource sets, the indices of the corresponding PUCCH resource sets can be configured in ascending order according to the maximum payload value, and the maximum payload value does not need to be configured in the last PUCCH resource set. The upper-layer configuration of the PUCCH resource sets can be shown in Table 22 below.

[0262] [Table 22]

[0263]

[0264] The resourceList parameter of the table can include the IDs of PUCCH resources that belong to the PUCCH resource set.

[0265] During initial access or when no PUCCH resource set is configured, a PUCCH resource set consisting of multiple cell-specific PUCCH resources from the initial BWP, as shown in Table 23, can be used. The PUCCH resources in this PUCCH resource set used for initial access can be indicated by SIB1.

[0266] [Table 23]

[0267]

[0268] The maximum payload of each PUCCH resource in the PUCCH resource set can be 2 bits in PUCCH format 0 or 1, and in the remaining formats, it can be determined by the symbol length, the number of PRBs, and the maximum coding rate. The symbol length and number of PRBs can be configured for each PUCCH resource, and the maximum coding rate can be configured for each PUCCH format.

[0269] Next, the selection of PUCCH resources for UCI transmissions is described. In the case of SR transmissions, the PUCCH resource corresponding to the SR with the scheduling request ID can be configured at a higher layer, as shown in Table 24. The PUCCH resource can be a resource belonging to PUCCH format 0 or PUCCH format 1.

[0270]

[0271] For the configured PUCCH resources, the transmission period and offset are configured using the periodicity and offset parameters in Table 24. When the terminal has uplink data to send at the time corresponding to the configured period and offset, it sends the corresponding PUCCH resource; otherwise, it may not send the corresponding PUCCH resource.

[0272] In the case of CSI transmission, PUCCH resources used for transmitting periodic or semi-persistent CSI reports via PUCCH can be configured as higher signaling in the pucch-CSI-resource list parameter as shown in [Table 25]. This parameter includes a list of PUCCH resources for each BWP of the cell or CC to which the corresponding CSI report will be sent. PUCCH resources can be resources belonging to PUCCH format 2, PUCCH format 3, or PUCCH format 4.

[0273] [Table 25]

[0274]

[0275] For PUCCH resources, the transmission period and offset are configured using the report slot configuration in Table 25.

[0276] In the case of HARQ-ACK transmission, the resource set of PUCCH resources to be transmitted is first selected based on the payload including the corresponding HARQ-ACK's UCI. That is, the PUCCH resource set with the smallest payload not less than the UCI payload is selected. Next, PUCCH resources in the PUCCH resource set can be selected by scheduling the PUCCH resource indicator (PRI) in the DCI corresponding to the corresponding HARQ-ACK's TB, and this PRI can be the PUCCH resource indicator specified in Table 5 or Table 6. The relationship between the PRI configured as higher signaling and the PUCCH resources selected from the PUCCH resource set can be shown in Table 26.

[0277] [Table 26]

[0278]

[0279] If the number of PUCCH resources in the selected PUCCH resource set is greater than 8, then the PUCCH resources can be selected using the following Equation 1.

[0280] [Equation 1]

[0281]

[0282] In equation 1 above, It is an index of the selected PUCCH resources in the PUCCH resource set. This refers to the number of PUCCH resources belonging to the PUCCH resource set. It is the PRI value. It is the total number of CCEs in the CORESET p to which the DCI belongs, and It is the first CCE index to receive DCI.

[0283] The transmission of the corresponding PUCCH resource occurs after the K1 slot transmitted from the TB corresponding to the corresponding HARQ-ACK. Candidate K1 values ​​are configured for the upper layer, and more specifically, for the dl-DataToUL-ACK parameter in the PUCCH configuration specified in [Table 21]. One of these candidates' K1 values ​​can be selected by the PDSCH-to-HARQ feedback timing indicator in the DCI that schedules the TB, and this value can be one specified in Table 5 or Table 6. The unit of the K1 value can be a slot unit or a sub-slot unit. Here, a sub-slot is a unit shorter than a slot, and one or more symbols can constitute a sub-slot.

[0284] Next, the case where two or more PUCCH resources reside in a single time slot is described. A terminal may transmit a UCI using one or two PUCCH resources within a time slot or sub-time slot, and when transmitting a UCI using two PUCCH resources within a time slot / sub-time slot, i) each PUCCH resource does not overlap on a symbol-by-symbol basis, and ii) at least one PUCCH resource can be a short PUCCH. Simultaneously, the terminal may not expect to transmit multiple PUCCH resources within a single time slot for HARQ-ACK transmission.

[0285] Next, the PUCCH transmission process when two or more PUCCH resources overlap is described. When two or more PUCCH resources overlap, one of the overlapping PUCCH resources can be selected, or a new PUCCH resource can be selected, based on the condition that the transmitted PUCCH resources should not overlap on a symbol-by-symbol basis. Furthermore, UCI payloads transmitted via overlapping PUCCH resources can be multiplexed and transmitted, or some can be discarded. First, the cases where multi-slot repetition is not configured in the PUCCH resources (Case 1) and the cases where multi-slot repetition is configured (Case 2) are described.

[0286] When PUCCH resources overlap for Case 1, it is divided into Case 1-1): the case where two or more PUCCH resources used for HARQ-ACK transmission overlap, and Case 1-2): the remaining cases.

[0287] The case corresponding to case 1-1 is Figure 9 As shown in the image.

[0288] Figure 9 This is a view illustrating a scenario where multiple PUCCH resources used for HARQ-ACK transmission of PDSCH overlap when multi-slot repetition is not configured, according to one embodiment. Reference Figure 9For two or more different PDCCHs 9-10 and 9-11 that schedule PDSCHs, the corresponding PUCCH resources can be considered to overlap when the transmission time slots corresponding to the PUCCH resources for each PDCCH are the same. In other words, when the uplink time slots corresponding to the K1 values ​​9-50 and 9-51 indicated by multiple PDCCHs are the same, the PUCCH resources for the corresponding PDCCHs can be considered to overlap.

[0289] In this scenario, among the PUCCH resources indicated by PRI 9-40 and 9-41 in the PDCCH, only PUCCH resource 9-31, selected based on PRI 9-41 corresponding to PDCCH 9-11 sent at the last point, is chosen, and HARQ-ACK information is sent on this PUCCH resource. Therefore, the HARQ-ACK information of PDSCH 9-21, and the HARQ-ACK information of other PUCCH 9-30s overlapping with PUCCH resource 9-31, are all sent after being encoded using the HARQ-ACK codebook defined by the selected PUCCH resource 9-31.

[0290] Next, for cases 1-2, we describe the situation where PUCCH resources used for HARQ-ACK transmission overlap with PUCCH resources used for SR and / or CSI transmission, or where multiple PUCCH resources used for SR and / or CSI transmission overlap. In the above cases, when multiple PUCCH resources transmitted in the same time slot overlap on the time axis by more than one symbol, it is defined as corresponding PUCCH resource overlap, and whether UCI is reused within these resources can be summarized as shown in Table 27 below.

[0291] [Table 27]

[0292]

[0293] According to the table above, these UCIs are always reused when the PUCCH resources to which HARQ-ACK is transmitted overlap, or when the PUCCHs through which SR and CSI are transmitted overlap.

[0294] Meanwhile, when each PUCCH resource for sending SR and HARQ-ACK overlaps, i.e. in case 1-2-1, whether to perform UCI multiplexing according to the format of the PUCCH resource is determined as follows.

[0295] -SR on PUCCH format 0 + HARQ-ACK on PUCCH format 1: SR is discarded, and only HARQ-ACK is sent.

[0296] - Other cases: SR and HARQ-ACK are reused.

[0297] Furthermore, the remaining cases correspond to Case 1-2-2, where HARQ-ACK and CSI overlap between transmitted PUCCH resources, or between multiple PUCCH resources in which CSI is transmitted. In these cases, the multiplexing of these UCIs can follow a higher-level configuration. Additionally, whether HARQ-ACK and CSI are multiplexed, and whether multiple CSIs are multiplexed, can be performed independently. For example, for each PUCCH format 2, 3, or 4, the multiplexing of HARQ-ACK and CSI can be configured via the simultaneous HARQ-ACK-CSI parameter, and for each PUCCH format, the corresponding parameter can be configured to the same value. If multiplexing is not configured via the above parameters, only HARQ-ACK is transmitted, and overlapping CSIs may be discarded. Alternatively, the multiplexing of multiple CSIs can be configured via the multi-CSI-PUCCH-resource list parameter in the PUCCH configuration. That is, when the multi-CSI-PUCCH-resource list parameter is configured, multiplexing between CSIs is possible. Otherwise, only the PUCCH corresponding to the CSI with the higher priority can be sent based on the CSI priority.

[0298] When UCI multiplexing is performed as described above, the selection method and multiplexing method of the PUCCH resource used to send the corresponding UCI resource may be different depending on the information of the overlapping UCI and the format of the PUCCH resource. This can be summarized in Table 28 below.

[0299] [Table 28]

[0300]

[0301] Each option in the table above is as follows.

[0302] Option 1: The terminal selects different PUCCH resources based on the SR values ​​of the HARQ-ACK PUCCH resource and the overlapping SR PUCCH resource. That is, if the SR value is positive, the PUCCH resource for SR is selected, and if the SR value is negative, the PUCCH resource for HARQ-ACK is selected. HARQ-ACK information is sent to the selected PUCCH resource.

[0303] - Option 2: The terminal performs HARQ-ACK transmission by multiplexing HARQ-ACK information and SR information into PUCCH resources.

[0304] - Option 3: The terminal transmits the information by multiplexing the SR information and CSI into the PUCCH resource used for CSI transmission.

[0305] Option 4: PUCCH resource transfer is used for overlap between HARQ-ACKs. Detailed operation has been described in case (1-1).

[0306] - Option 5: If the PUCCH resource for HARQ-ACK corresponding to the PDSCH scheduled as PDCCH overlaps with the PUCCH resource for CSI transmission, and when multiplexing between HARQ-ACK and CSI is configured as the upper layer, the terminal multiplexes and sends HARQ-ACK information and CSI information to the PUCCH resource for HARQ-ACK.

[0307] - Option 6: When the PUCCH resource for HARQ-ACK corresponding to the semi-persistent scheduling (SPS) PDSCH overlaps with the PUCCH resource for CSI transmission and the multiplexing between HARQ-ACK and CSI is configured as the upper layer, the terminal multiplexes and sends HARQ-ACK information and CSI information to the PUCCH resource for CSI transmission.

[0308] If a PUCCH resource list for upper-layer multiplexing is configured, i.e., a multi-CSI-PUCCH resource list, the terminal selects one of the resources in the list with the lowest index that can send all multiplexed UCI payloads, and then transmits the payload via UCI. If there is no resource in the list that can send all multiplexed UCI payloads, the terminal selects the resource with the highest index and then sends the same number of HARQ-ACK and CSI reports to that resource as can be sent.

[0309] Option 7: When multiple CSI transmission PUCCH resources overlap and multiplexing between multiple CSIs is configured for higher layers, the terminal selects the resource with the lowest index from the list of PUCCH resources configured for higher-layer CSI multiplexing (i.e., the multi-CSI-PUCCH-resource list) that has the capability to send all multiplexed UCI payloads, and then sends that UCI payload. If there is no resource in the list that can send all multiplexed UCI payloads, the terminal selects the resource with the highest index and then sends as many CSI reports as possible to the corresponding resource.

[0310] For ease of description, the above section focused on the case of overlapping two PUCCH resources. However, this method can be applied similarly even when three or more PUCCH resources overlap. For example, if the PUCCH resources multiplexed by SR+HARQ-ACK overlap with the CSI PUCCH resources, the multiplexing method between HARQ-ACK and CSI can be followed.

[0311] If configured not to multiplex between specific UCIs, higher-priority UCIs are sent in the order HARQ-ACK > SR > CSI, and lower-priority UCIs can be discarded. When multiple CSI PUCCH resources are configured not to multiplex when overlapping, the PUCCH corresponding to the higher-priority CSI is sent, and PUCCHs corresponding to other CSIs can be discarded.

[0312] Next, Case 2, which involves multiple time slot repetition in the configuration, is divided into two cases: one where two or more PUCCH resources for HARQ-ACK transmission are located in the same starting time slot (Case 2-1), and another case (Case 2-2). Each case is further divided into... Figure 10 As shown in the image.

[0313] Figure 10 This is a view illustrating the case of PUCCH resource overlap when configuring multi-slot repetition according to one embodiment.

[0314] Referring to Case 2-1), when multiple time slots are configured for HARQ-ACK reuse in the PUCCH resource (i.e., when PUCCH #1 is repeatedly transmitted on multiple time slots 10-30 and 10-40, and PUCCH #2 is also repeatedly transmitted on multiple time slots 10-31 and 10-41), if the starting time slots of the two PUCCHs represented by K1 are the same, then a single PUCCH resource (the latest PUCCH transmitted in a time slot), i.e., PUCCH #2, can be selected in the same way as in Case 1-1). Therefore, the HARQ-ACK information corresponding to PDSCH #1 and PDSCH #2 is multiplexed and sent to the PUCCH via the HARQ-ACK codebook.

[0315] For ease of description, an example is given of the case where multiple PUCCHs undergoing multi-slot repetition overlap, but the same method can be applied when multi-slot repetition PUCCHs overlap with PUCCHs transmitted in a single slot.

[0316] Case 2-2) corresponds to the situation where symbol cell overlap occurs between a PUCCH used for HARQ-ACK transmission and a PUCCH used for SR or CSI transmission, or between PUCCHs used for multiple SR or CSI transmissions. That is, when PUCCH #1 is repeatedly transmitted on multiple time slots 10-50 and 10-51 and PUCCH #2 is also repeatedly transmitted on multiple time slots 10-60 and 10-61, PUCCH #1 and PUCCH #2 correspond to the situation where more than one symbol overlap occurs in one time slot 10-70.

[0317] In the case of PUCCHs with more than one symbol overlap in time slots 10-70, the priority of UCIs in the PUCCH is compared, and the UCI with the higher priority is sent, while the other UCIs are dropped in the corresponding time slot. In this case, the priority of UCIs follows the highest order: HARQ-ACK > SR > CSI.

[0318] Furthermore, when multiple CSI PUCCH resources overlap, a PUCCH corresponding to a higher-priority CSI can be transmitted, and a PUCCH corresponding to another CSI can be discarded in the corresponding time slot. PUCCH transmission or discarding based on the aforementioned priorities is only performed in the time slot where each symbol overlap occurs, and not in other time slots. That is, a PUCCH configured for multi-slot repetition can be discarded in the time slot where symbol cell overlap occurs, but can be transmitted in the remaining time slots as configured.

[0319] In the above case, for ease of description, an example is given of the case where multiple PUCCHs undergoing multi-slot repetition overlap. However, the same method can also be applied when there is overlap between multi-slot repetition PUCCHs and PUCCHs transmitted in a single slot.

[0320] Furthermore, the overlap between PUCCH and PUSCH transmissions is described. If the terminal is in... If a PUCCH is sent in the first time slot of a repeated transmission, then a PUSCH is sent in the second time slot. When a PUCCH transmission overlaps with a PUSCH transmission in one or more time slots, and when a UCI is multiplexed into a PUSCH in an overlapping time slot, the terminal sends a PUCCH but does not send a PUSCH in the time slot where the PUCCH and PUSCH overlap.

[0321] In single-slot transmissions and multi-slot repetitions of PUCCH, the aforementioned slots used for low-latency services such as URLLC can be replaced and used as microslots. A microslot is shorter than a single slot on the timeline, and a microslot may consist of fewer than 14 symbols. For example, two or seven symbols can constitute a microslot. When configuring microslots through upper layers, units such as the HARQ-ACK feedback timing K1 value and the number of repetitions can be replaced with the microslot units in the existing slots. Microslot configuration can be applied to all PUCCH transmissions or can be limited to PUCCH transmissions for specific services. For example, slot unit transmissions can be applied to PUCCHs for eMBB services, while microslot unit transmissions can be applied to PUCCHs for URLLC services.

[0322] Next, the beam configuration to be applied to PUCCH transmissions is described. If the terminal does not have a specific terminal configuration for PUCCH resource configuration (dedicated PUCCH resource configuration), the PUCCH resource set is provided via the upper-layer signaling pucch-ResourceCommon. In this case, the beam configuration for PUCCH transmissions follows the beam configuration used in PUSCH transmissions scheduled via Random Access Response (RAR) UL authorization. If the terminal has a specific terminal configuration for PUCCH resource configuration (dedicated PUCCH resource configuration), the beam configuration for PUCCH transmissions is provided via the pucch-spatial-related-association-ID (pucch-spatialRelationInfoId), which is the higher-level signaling shown in Table 29. If the terminal has already been configured with a pucch-spatial-related-association-ID, the beam configuration for the terminal's PUCCH transmissions is provided via a single pucch-spatial-related-association-ID. If the terminal is configured with multiple pucch-spatial-related-association-IDs (pucch-spatialRelationInfoIDs), the terminal is instructed to activate one of the multiple pucch-spatial-related-association-IDs via the MAC control element (CE). The terminal can receive up to eight pucch-space-related information IDs via higher-level signaling, and can receive an indication that only one of the pucch-space-related information IDs is active.

[0323] When a terminal is instructed to activate any pucch-space-related information ID via MAC CE, the terminal applies the pucch-space-related information ID activation from a timeslot via MAC CE. This timeslot begins when the HARQ-ACK transmission for the PDSCH used to send the MAC CE includes activation information for the pucch-space-related information ID. This is the first time it has appeared since a time slot. In the above text, It is a parameter set applied to PUCCH transmission, and This represents the number of time slots in each subframe within a given parameter set. The upper-level composition used for pucch-spatial related information can be shown in Table 29 below. Pucch-spatial related information is interchangeable with PUCCH beam information.

[0324]

[0325] According to Table 29, a reference signal configuration may exist in a specific pucch-spatial-related information (pucch-spatialRelationInfo) configuration, and the reference signal is an SSB-index indicating a specific SS / PBCH, a CSI-RS-index indicating a specific CSI-RS, or an SRS indicating a specific SRS. If the reference signal is configured as an SSB-index, the terminal is configured to use the beam when receiving an SS / PBCH corresponding to the SSB-index in the SS / PBCH in the same serving cell as the beam used for PUCCH transmission. Alternatively, if a serving cell Id is provided, the beam used when receiving an SS / PBCH corresponding to the SSB-index in the SS / PBCH in the cell indicated by the serving cell Id can be configured as the beam used for pucch transmission. If the reference signal is configured as a CSI-RS-index, the beam used by the terminal when receiving a CSI-RS corresponding to the CSI-RS-index in the same serving cell as the beam used for PUCCH transmission, or if a serving cell ID is provided, the beam used when receiving a CSI-RS corresponding to the CSI-RS-index in the CSI-RS of the cell indicated by the serving cell ID can be configured as the beam for PUCCH transmission. If the reference signal is configured as an SRS, the transmission beam used by the terminal when transmitting an SRS corresponding to a resource index provided as a higher signaling resource in the same serving cell and / or in an active uplink BWP is configured as the beam for PUCCH transmission, or if a serving cell ID and / or uplink BWP are provided, the transmission beam used when transmitting an SRS corresponding to a resource index provided as a higher signaling resource in the cell indicated by the serving cell ID and / or uplink BWP can be configured as the beam for PUCCH transmission.

[0326] A pucch-path loss reference RS-Id configuration may exist in a specific pucch-space-related information configuration. The pucch-path loss reference RSs in Table 30 can be mapped to the pucch-path loss reference RS-Ids in [Table 29], and up to four path loss reference RSs can be configured through the upper-layer signaling pucch-power control in Table 30. If the pucch-path loss reference RS is connected to the SS / PBCH via the reference signal in Table 30, the ssb-index is configured, and if it is connected to the CSI-RS, the csi-RS-index is configured.

[0327] [Table 30]

[0328]

[0329] During uplink transmission at the terminal, a transition time may be required to meet the transmit power requirements of the transmit-on state when switching from the transmit-off state to the transmit-on state. Similarly, a transition time may be required to meet the transmit power requirements of the transmit-off state when switching from the transmit-on state to the transmit-off state. Alternatively, switching time may also be required even if a change in transmit power, transmit RB change, or transition occurs during the transmit-on state.

[0330] Figure 11 This demonstrates the switching time required to switch between the send-off and send-on states.

[0331] refer to Figure 11 The switching time (11-05, 11-10) can be defined for frequency range 1 (FR1) and frequency range 2 (FR2) respectively.

[0332] Figure 12 This demonstrates the switching time required for changes in transmission power, transmission RB, or transitions in frequency range 1 (FR1) when transmission is enabled.

[0333] refer to Figure 12 When the transmission channel changes, the switching time can be defined as 12-05 and 12-10 when changes in transmission power, transmission RB, or transitions are involved. The switching time between the SRS channel and other channels can be defined differently depending on whether SRS detection is performed through the same antenna port as another channel (12-05) or through a different antenna port (12-10).

[0334] Meanwhile, when changes in transmission power or transmission RBs or transitions are involved, different switching times (12-15, 12-20, 12-25) can be defined based on the length of the transmission channel before and after the change / transition.

[0335] In cases of changes in transmission power, transmission RB, or transitions between long and short sub-slot transmissions, a transition time can be defined within the long sub-slot (12-15). When changes in transmission power, transmission RB, or transitions between short sub-slot transmissions are involved, a transition time can be defined between short sub-slots (12-20, 12-25). When the parameter set in FR1 is less than 60 kHz, no blank symbols are required between short sub-slots (12-20), while when the parameter set in FR1 is 60 kHz, blank symbols are required between short sub-slots (12-25).

[0336] A long sub-slot can indicate a PUSCH transmission with more than 2 symbols or a long PUCCH transmission, and a short sub-slot can indicate a PUSCH transmission with 2 or fewer symbols or a short PUCCH transmission.

[0337] Figure 13 This demonstrates the switching time required for changes in transmission power, transmission RB, or transitions in frequency range 2 (FR2) when transmission is enabled.

[0338] refer to Figure 13 When the transmission channel changes, the switching time when the transmission power changes, the transmission RB changes, or the switching occurs can be defined as (13-05).

[0339] Meanwhile, when changes in transmission power or transmission RBs or transitions are involved, different switching times (13-10, 13-15, 13-20) can be defined based on the length of the transmission channel before and after the change / transition.

[0340] When changes in transmission power or transmission RB are involved, or when switching between long sub-slot transmission and short sub-slot transmission are involved, the switching time can be defined within the long sub-slot (13-10).

[0341] When changes in transmission power, transmission RB, or transitions between short sub-slots are involved, the transition time between short sub-slots (13-15, 13-20) can be defined. When the parameter set in FR2 is less than 120 kHz, it is not necessary to configure the blank symbol (13-15) between short sub-slots, while when the parameter set in FR2 is 120 kHz, it is necessary to configure the blank symbol (13-20) between short sub-slots.

[0342] A long sub-slot can indicate a PUSCH transmission with more than 2 symbols or a long PUCCH transmission, and a short sub-slot can indicate a PUSCH transmission with 2 or fewer symbols or a short PUCCH transmission.

[0343] In LTE and NR systems, when a terminal connects to a serving base station, it can perform a process of reporting its supported capabilities to the corresponding base station. In the following description, this may be referred to as a terminal capability (report). The base station may deliver a terminal capability query message requesting a capability report to a terminal in a connected state. In this message, the base station may include a request for terminal capabilities for each RAT type. The request for each RAT type may include the requested frequency band information.

[0344] Furthermore, terminal capability query messages can request multiple RAT types from a single RRC message container, or can include multiple terminal capability query messages to the terminal for each RAT type. That is, terminal capability queries are repeated multiple times, and the terminal can configure the corresponding terminal capability information messages and report them multiple times. In next-generation mobile communication systems, terminal capability queries can be performed for MR-DC, including NR, LTE, and EN-DC. For reference, terminal capability query messages are generally sent after the terminal connects, but can also be requested under any circumstances when a base station is needed.

[0345] In the above steps, the terminal that receives the terminal capability report request from the base station can configure its capabilities based on the RAT type and frequency band information requested from the base station. In an NR system, the method for configuring terminal capabilities may include at least one of the following methods.

[0346] 1. If the terminal receives a list of LTE and / or NR frequency bands upon receiving a terminal capability request from the base station, the terminal can configure a frequency band combination (BC) for EN-DC and NR SA independently. That is, the BC candidate list for EN-DC and NR SA can be configured as a frequency band list (FreqBandList) based on the frequency bands requested by the base station. Furthermore, the frequency bands can have priorities in the order described in the frequency band list.

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

[0348] 3. Next, the terminal can remove the fallback BC from the candidate list of BCs configured in the above steps. Here, the fallback BC corresponds to removing the frequency band corresponding to at least one SCell from the superset BC, and can be omitted because the superset BC may already cover the fallback BC. This step also applies to MR-DC, i.e., it can also be applied to LTE frequency bands. The remaining BCs after this stage constitute the final "candidate BC list".

[0349] 4. The terminal selects the BC to report by choosing a BC suitable for the requested RAT type from the final "Candidate BC List". In this step, the terminal can configure the supported band combination list in a defined order. That is, the terminal configures the BCs and UE capabilities to be reported according to the preset rat-type order (nr->eutra-nr->eutra). Additionally, the feature set combination of the configured supported band combination list can be configured, and a list of "candidate feature set combinations" can be configured from the candidate BC list, removing the list of BCs used for fallback (including capabilities of the same or lower level). The "candidate feature set combinations" include two feature set combinations for NR and EUTRA-NR BCs, and can be obtained from the feature set combinations of UE-NR-capability and UE-MRDC-capability containers.

[0350] 5. Furthermore, if the requested RAT type is EUTRA-NR and has an impact, the feature set combination can be included in both the UE-MRDC-capability and UE-NR-capability containers. However, the NR feature set may only be included in the UE-NR-capability.

[0351] After configuring terminal capabilities, the terminal sends a terminal capability information message, including the terminal capabilities, to the base station. The base station then performs appropriate scheduling and transmission / reception management for the corresponding terminal based on the terminal capabilities received from the terminal.

[0352] Figure 14 This is a view illustrating the structure of the base station and terminal radio protocols when performing single-cell, carrier aggregation, and dual connectivity according to one embodiment.

[0353] refer to Figure 14 The radio protocols for next-generation mobile communication systems include NR Service Data Adaptation Protocol (NRSDAP) 1425 and 1470, NR Packet Data Convergence Protocol (NR PDCP) 1430 and 1465, NR Radio Link Control (NRRLC) 1435 and 1460, and NR Media Access Control (NR MAC) 1440 and 1455 located at the terminal and NR base station.

[0354] The main functions of NR SDAP 1425 and 1470 may include some of the following functions.

[0355] -Transmission of user plane data

[0356] - Mapping function for QoS flows and data bearers in uplink and downlink

[0357] - QoS flow ID marked in both DL and UL packets

[0358] -Mapping of reflective QoS flow from UL SDAP PDU to DRB

[0359] For SDAP layer devices, terminals can configure via RRC messages whether to use the SDAP layer device header or whether to use the SDAP layer device's functions for each PDCP layer device, each bearer, or each logical channel. When the SDAP header is configured, the NAS QoS reflection configuration 1-bit indicator (NAS reflective QoS) and AS QoS reflection configuration 1-bit indicator (AS reflective QoS) in the SDAP header can indicate the mapping information of QoS flows and data bearers used for uplink and downlink. 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 smooth service.

[0360] The main functions of NR PDCP 1430 and 1465 may include some of the following functions.

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

[0362] -Transmission of user data

[0363] - Sequential delivery of upper-layer PDUs

[0364] -Disordered delivery of upper-layer PDUs

[0365] - Reordering function (PDCP PDU reordering for reception)

[0366] -Duplicate detection of lower-level SDUs

[0367] -PDCP SDU retransmission

[0368] - Encryption and decryption functions (passwords and decryption)

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

[0370] In the above text, the reordering function of the NR PDCP device can refer to the function of reordering PDCP PDUs received from the lower layer based on the PDCP sequence number (SN). It can include the function of delivering data to the upper layer in the reordered order, the function of delivering data directly without considering the order, the function of reordering to record lost PDCP PDUs, the function of reporting the status of lost PDCP PDUs to the transmitting side, and the function of requesting the retransmission of lost PDCP PDUs.

[0371] The main functions of NR RLC 1435 and 1460 may include some of the following functions.

[0372] - Data transmission function (transmission of upper-layer PDUs)

[0373] - Sequential delivery of upper-layer PDUs

[0374] -Disordered delivery of upper-layer PDUs

[0375] -ARQ function (error correction via ARQ)

[0376] Cascading, segmentation, and reassembly of RLC SDUs

[0377] - Resegmentation of RLC data PDUs

[0378] - Reordering of RLC data PDUs

[0379] -Duplicate detection

[0380] -Protocol error detection

[0381] -RLC SDU discard function (RLC SDU discard)

[0382] -RLC Reconstruction

[0383] In the above text, the sequential delivery function of the NR RLC device refers to the function of delivering RLC SDUs received from the lower layer to the upper layer in sequence. This may include the function of reassembling and transmitting an RLC SDU when it is initially divided into several RLC SDUs and received; the function of rearranging received RLC PDUs based on the RLC sequence number (SN) or PDCP sequence number (SN); the function of recording lost RLC PDUs by rearranging their order; the function of reporting the status of lost RLC PDUs to the transmitting side; the function of requesting the retransmission of lost RLC PDUs; the function of transmitting RLC SDUs to the upper layer in sequence only before the lost RLC SDU when a lost RLC SDU exists; the function of delivering all RLC SDUs received before the start of the timer in sequence to the upper layer even if a lost RLC SDU exists, if a predetermined timer expires; or the function of delivering all RLC SDUs received to date in sequence to the upper layer even if a lost RLC SDU exists, if a predetermined timer expires. Furthermore, as described above, RLC PDUs can be processed in the order of reception (regardless of sequence number or serial number, according to arrival order), and regardless of the order in which they are delivered to the PDCP device (out-of-order delivery). In the case of fragmentation, segments stored in the buffer or received later can be received, reconstructed into a complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include concatenation functionality, and this functionality can be performed by the NR MAC layer or replaced by the multiplexing functionality of the NR MAC layer.

[0384] In the above text, the out-of-order delivery function of NR RLC devices refers to the function of delivering RLC SDUs received from the lower layer directly to the upper layer regardless of the order. It may include the function of reassembling and sending the original RLC SDUs that have been divided into multiple RLC SDUs, or it may include the function of storing the RL CSN or PDCP SN of the received RLC PDUs, sorting and recording the lost RLC PDUs.

[0385] NR MAC 1440 and 1455 can be connected to several NR RLC layer devices configured in a single terminal, and the main functions of NR MAC can include some of the following functions.

[0386] - Mapping between logical channels and transmission channels

[0387] - Multiplexing and demultiplexing functions (MAC SDU multiplexing / demultiplexing)

[0388] - Scheduling information reporting function

[0389] - HARQ function (error correction via HARQ)

[0390] Priority processing between logical channels of a UE

[0391] - Prioritization among UEs is achieved through dynamic scheduling.

[0392] -MBMS service identifier

[0393] -Transmission format selection

[0394] - Fill function

[0395] The NR PHY layers 1445 and 1450 can perform channel coding and modulation of upper-layer data, convert it into OFDM symbols, and send them to the radio channel, or they can demodulate OFDM symbols received through the radio channel, perform channel decoding, and send them to the upper layer.

[0396] The detailed structure of a radio protocol architecture can vary depending on the carrier (or cell) operation method. For example, when a base station transmits data to a terminal based on a single carrier (or cell), the base station and terminal use a protocol architecture with a single structure at each layer, such as 1400. On the other hand, when a base station uses multiple carriers in a single TRP to transmit data to a terminal based on CA (carrier aggregation), the base station and terminal have a single structure up to RLC, such as 1410, but use a protocol architecture to multiplex the PHY layer through the MAC layer. Similarly, when a base station uses multiple carriers in multiple TRPs to transmit data to a terminal based on DC (dual connectivity), the base station and terminal have a single structure up to RLC, such as 1420, but use a protocol architecture to multiplex the PHY layer through the MAC layer.

[0397] Referring to the above descriptions related to PUCCH, in Rel-15 NR, PUCCH transmission focuses on transmission to a single cell and / or a single transmission point and / or a single panel and / or a single beam and / or a single transmission direction. In the following description, for ease of description, indicators such as cell, transmission point, panel, beam, and / or transmission direction, which can be distinguished by higher-layer / L1 parameters such as TCI status or spatial relationship information, or indicators such as cell ID, TRP ID, and panel ID, are uniformly described as Transmitter Receiver Points (TRPs). Therefore, in practical applications, TRP can be appropriately replaced by one of the aforementioned terms.

[0398] In NR Releases 15 and 16, since there is only one PUCCH resource used for PUCCH transmission, and only one PUCCH-space-related information can be activated for one PUCCH resource, the terminal can maintain the indicated transmission beam when transmitting PUCCH. When PUCCH is repeatedly transmitted over several time slots or several micro-time slots, the transmission beam according to an indicated PUCCH-space-related information needs to be maintained throughout the repeated transmission.

[0399] Additionally, when PUCCH transmission for multiple TRPs is supported, PUCCH can be repeatedly sent for each TRP. In this case, the terminal must support the configuration for PUCCH transmission to multiple TRPs.

[0400] For example, multiple beam directions can be indicated for transmission to multiple TRPs for a single PUCCH, or each of multiple PUCCHs including the same UCI can be sent to different TRPs, requiring the indication of different beam directions for these PUCCHs. In this disclosure, considering the above, by providing various methods for configuring PUCCH resources, the transmission delay time of uplink control information is minimized and high reliability is achieved. Detailed PUCCH resource setting methods will be described in detail in the following embodiments.

[0401] The appendix will be referenced below. Figure 1 The embodiments of this disclosure will be described in detail below. Furthermore, in describing this disclosure, detailed descriptions of relevant functions or configurations will be omitted where it is determined that such descriptions might unnecessarily obscure the subject matter of this disclosure. Additionally, the terminology described later is defined in consideration of the functions in this disclosure and may vary depending on the intent or customization of the user or operator. Therefore, definitions should be based on the entire contents of this specification.

[0402] In the following text, the base station is the entity that performs resource allocation for the terminal and can be at least one of gNode B, gNB, eNodeB, Node B, base station (BS), radio access unit, base station controller, or a node on the network. The terminal may include user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. Furthermore, NR or LTE / LTE-A systems will be used as examples to describe embodiments of this disclosure; however, embodiments of this disclosure can be applied to other communication systems with similar technical backgrounds or channel types. Moreover, embodiments of this disclosure can be applied to other communication systems with modifications that do not significantly depart from the scope of this disclosure, as determined by a person skilled in the art.

[0403] The contents of this disclosure apply to FDD and TDD systems.

[0404] In the following text, higher signaling (or higher-layer signaling) is a signal transmission method that uses the downlink data channel of the physical layer to send signals from the base station to the terminal or uses the uplink data channel of the physical layer to send signals from the terminal to the base station, RRC signaling, and may be referred to as PDCP signaling or Media Access Control Element (MAC CE).

[0405] In the following, in this disclosure, when determining whether to apply cooperative communication, the PDCCH used to allocate the PDSCH with cooperative communication applied has a specific format, or the PDCCH used to allocate the PDSCH with cooperative communication applied is applied to a specific indicator including notification of cooperative communication, or the PDCCH used to allocate the PDSCH with cooperative communication applied is scrambled with a specific RNTI, or it is assumed that cooperative communication is applied in a specific part indicated by a higher layer, etc. The terminal can use them. For ease of explanation, the case in which the terminal receives the PDSCH with cooperative communication applied based on the same conditions as described above is referred to as the NC-JT case.

[0406] In the following text, determining the priority between A and B refers to selecting the one with higher priority and executing the corresponding operation, or the operation with lower priority, according to predetermined priority rules. This can be mentioned in various ways, such as omitting or abandoning the process.

[0407] Although the above examples have been described with reference to multiple embodiments, these embodiments are not independent and one or more embodiments may be applied simultaneously or in combination.

[0408] <Example 1: DCI Reception of NC-JT>

[0409] Unlike conventional systems, 5G wireless communication systems can support services requiring high transmission rates, as well as services with extremely low transmission latency and high connection density. In wireless communication networks comprising multiple cells, TRPs, or beams, coordinated transmission between each cell, TRP, and / or beam is one of the key technologies that enables various service requirements to be met by increasing the strength of the signal received by the terminal or by effectively controlling interference between cells, TRPs, and / or beams.

[0410] Joint transmission (JT) is a representative transmission technology for cooperative communication, which supports a terminal through different cells, TRPs, and / or beams to increase the signal strength received by the terminal. However, since the channel characteristics between each cell, TRP, and / or beam and the terminal can vary significantly, different precoding, MCS, resource allocation, etc., need to be applied to the link between each cell, TRP, and / or beam and the terminal. Specifically, in the case of noncoherent joint transmission (NC-JT) supporting non-interference coding between each cell, it is important to configure separate downlink (DL) transmission information for each cell, TRP, and / or beam.

[0411] Meanwhile, configuring separate DL transmission information for each cell, TRP, or / or beam is a major factor increasing the payload required for DL ​​DCI transmission, which can adversely affect DCI reception performance. Therefore, it is necessary to carefully design the trade-off between DCI information volume and PDCCH reception performance for JT support.

[0412] Figure 15 This is a view illustrating an example of antenna port configuration and resource allocation for cooperative communication in a wireless communication system according to one embodiment.

[0413] refer to Figure 15 This demonstrates an example of radio resource allocation for each TRP based on the Joint Transmission (JT) scheme and scenario.

[0414] exist Figure 15 In the example, 1500 is a coherent joint transmission (C-JT) that supports phase interference coding between each cell, TRP, and / or beam.

[0415] In C-JT, TRP A 1505 and TRP B 1510 can send a single data transmission (PDSCH) to terminal 1515, and multiple TRPs can perform joint precoding. This means using the same DMRS ports (e.g., DMRS ports A and B in two TRPs) to perform the same PDSCH transmission in TRP A 1505 and TRP B 1510. In this case, the terminal can receive a DCI message for receiving a PDSCH based on DMRS demodulation transmitted through DMRS ports A and B.

[0416] exist Figure 15In the example 1520, noncoherent joint transmission (NC-JT) with non-interference coding is supported between each cell, TRP, and / or beam. In the case of NC-JT, PDSCHs are sent to terminal 1535 for each cell, TRP, and / or beam, and individual precoding can be applied to each PDSCH. Compared to single-cell, TRP, and / or beam transmission, different PDSCHs can be sent for each cell, TRP, and / or beam to improve throughput, or the same PDSCH can be repeatedly sent for each cell, TRP, and / or beam, thereby improving reliability compared to single-cell, TRP, and / or beam transmission.

[0417] Various radio resource allocations can be considered when the frequency and time resources used for PDSCH transmission by multiple TRPs are the same (1540), when the frequency and time resources used by multiple TRPs do not overlap at all (1545), and when some frequency and time resources used by multiple TRPs overlap (1550).

[0418] In each of the above scenarios, when multiple TRPs repeatedly transmit the same PDSCH to improve reliability, if the receiving terminal is unaware of whether the corresponding PDSCH has been repeatedly transmitted, the corresponding terminal cannot physically combine the corresponding PDSCH, and thus the improvement in reliability may be limited. Therefore, this disclosure provides a retransmission instruction and configuration method for improving the reliability of NC-JT transmission.

[0419] To assign multiple PDSCHs to a single terminal simultaneously to support NC-JT, various types, structures, and relationships of DCIs can be considered.

[0420] Figure 16 This is a view illustrating an exemplary configuration of downlink control information (DCI) for cooperative communication in a wireless communication system according to embodiments of the present disclosure.

[0421] refer to Figure 16 This demonstrates various examples of DCI used for NC-JT support.

[0422] refer to Figure 16Case #1 (1600) is an example in which (N-1) different PDSCHs are sent in (N-1) additional TRPs (TRP#1 to TRP#(N-1)) besides the serving TRP (TRP#0) used for a single PDSCH transmission, and the control information of the PDSCHs sent in the (N-1) additional TRPs is sent in the same form (same DCI format) as the control information of the PDSCHs sent in the serving TRP. That is, the terminal can obtain control information about the PDSCHs sent in different TRPs (TRP#0 to TRP#(N-1)) through DCIs (DCI#0 to DCI#(N-1)) with the same DCI format and the same payload. Meanwhile, in this embodiment and the embodiments described later, the control information sent in the serving TRP can be classified as the first DCI, and the DCI sent in another TRP (cooperative TRP) can be called the second DCI.

[0423] In scenario #1 above, the degree of freedom in controlling (allocating) each PDSCH can be fully guaranteed. However, when each DCI is sent in different TRPs, the coverage of each DCI may differ, and the reception performance may degrade.

[0424] Case #2 (1605) is an example in which the control information of the PDSCH sent in the (N-1) additional TRPs (TRP #1 to TRP #(N-1)) other than the serving TRP (TRP #0) for a single PDSCH transmission is sent in a different form (different DCI format or different DCI payload) than the control information of the PDSCH sent in the serving TRP.

[0425] For example, in the case of DCI#0, which is the control information of PDSCH sent from the service TRP (TRP#0), all information elements of DCI format 1_0 to DCI format 1_1 are included. However, in the case of DCI#0 (hereinafter referred to as sDCI) (sDCI#0 to sDCI#(N-2)), which is the control information of PDSCH sent in the cooperative TRP (TRP#1 to TRP#(N-1)), only some information elements of DCI format 1_0 to DCI format 1_1 are included.

[0426] Therefore, in the case of sDCI which includes control information about the PDSCH sent in the cooperative TRP, the payload may be smaller than that of normal DCI (nDCI) which includes control information related to the PDSCH sent in the service TRP, or may include as many reserved bits as nDCI.

[0427] In scenario #2 above, the degrees of freedom for control (allocation) of each PDSCH can be limited based on the content of the information elements included in the sDCI, or the probability of coverage differences between each DCI can be reduced because the receiving performance of the sDCI is better than that of the nDCI.

[0428] Case #3 (1610) is an example in which the control information of the PDSCH sent in the (N-1) additional TRPs (TRP #1 to TRP #(N-1)) other than the serving TRP (TRP #0) used when sending a single PDSCH is sent, and the control information of the PDSCH sent in the (N-1) additional TRPs is sent in a different form (different DCI format or different DCI payload) than the control information of the PDSCH sent from the serving TRP.

[0429] For example, in the case of DCI#0, which is the control information of PDSCH sent in the service TRP (TRP#0), all information elements of DCI format 1_0 to DCI format 1_1 are included, while in the case of control information of PDSCH sent in the cooperative TRP (TRP#1 to TRP#(N-1)), only some information elements of DCI format 1_0 to DCI format 1_1 may be included in an "auxiliary" DCI (sDCI).

[0430] For example, sDCI may include at least one of HARQ-related information, such as frequency domain resource allocation, time domain resource allocation, and MCS of the cooperative TRP. In addition, in the case of information not included in sDCI (such as bandwidth portion (BWP) indicator or carrier indicator), the DCI (DCI#0, normal DCI, nDCI) of the serving TRP may be followed.

[0431] In scenario #3, the degrees of freedom used to control (allocate) each PDSCH can be limited based on the content of the information elements included in the sDCI. However, the reception performance of the sDCI can be adjusted, and the complexity of blind decoding of the DCI at the terminal can be reduced compared to scenario #1 or scenario #2.

[0432] Case #4 (1615) is an example where control information for PDSCHs transmitted in (N-1) additional TRPs is sent via a long DCI (LDCI), such as control information for PDSCHs transmitted in a serving TRP. This involves sending different (N-1) PDSCHs in (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used for a single PDSCH transmission. That is, the terminal can obtain control information about the PDSCHs transmitted in different TRPs (TRP#0 to TRP#(N-1)) via a single DCI.

[0433] In scenario #4, the complexity of blind decoding of the terminal's DCI may not increase, but the degree of freedom in PDSCH control (allocation) may be lower, such as the limited number of cooperative TRPs due to the long DCI payload limitation.

[0434] In the following description and embodiments, sDCI may be referred to as various auxiliary DCIs, such as shortened DCIs, auxiliary DCIs, or normal DCIs that include PDSCH control information transmitted in a cooperative TRP (DCI formats 1_0 to 1_1 above). Unless otherwise specified, the description applies equally to various auxiliary DCIs. Furthermore, DCIs may be classified using terms such as first DCI and second DCI based on the form or characteristics of the DCI or the TRP used to transmit the DCI. For example, a DCI transmitted via a serving TRP may be referred to as a first DCI, and a DCI transmitted via a cooperative TRP may be referred to as a second DCI.

[0435] In the following description and embodiments, cases #1, #2 and #3 in which one or more DCIs (PDCCHs) are used for NC-JT support can be classified as multiple PDCCH-based NC-JTs, and case #4 in which a single DCI (PDCCH) is used for NC-JT support can be classified as a single PDCCH-based NC-JT.

[0436] In the embodiments, in practical applications, "cooperative TRP" can be replaced by various terms, such as "cooperative panel" or "cooperative beam".

[0437] In the embodiments, "when NC-JT is applied" can be interpreted in different ways depending on the situation, such as "when the terminal receives one or more PDSCHs simultaneously in a BWP", "when the terminal receives PDSCHs simultaneously in a BWP based on two or more Transport Configuration Indicators (TCIs)", "when the PDSCHs received by the terminal are associated with one or more DMRS port groups", etc., but it is used as an expression for the sake of convenience.

[0438] In this disclosure, the radio protocol architecture of NC-JT can be used in various ways depending on the TRP deployment scenario. For example, when there is no backhaul delay or very little backhaul delay between cooperating TRPs, a similar approach can be used. Figure 14 The 1410 (CA-type method) is based on a MAC layer multiplexing structure. On the other hand, when the backhaul latency between cooperative TRPs becomes too large to be ignored (e.g., when information exchange such as CSI, scheduling, HARQ-ACK between cooperative TRPs takes 2 ms or more), similar to... Figure 14 The 1420 can ensure robust latency characteristics by using an independent structure (DC class approach) for each TRP from the RLC layer.

[0439] <Example 1-1: Method for setting up a downlink control channel for NC-JT transmission based on multi-PDCCH>

[0440] In NC-JT based on multiple PDCCHs, when DCI is sent according to the PDSCH schedule for each TRP, it can be sent through the CORESET or search space classified for each TRP. The CORESET or search space for each TRP can be configured as at least one of the following.

[0441] ● Upper-level index configuration for each CORESET: CORESET settings for higher levels can include index values, and the TRP sending PDCCH from the corresponding CORESET can be identified as the index value configured for each CORESET. That is, in a set of CORESETs with the same upper-level index value, it is possible to determine or consider PDCCHs that send PDCCHs with the same TRP or PDSCHs that are scheduled to send PDCCHs with the same TRP.

[0442] Each of the aforementioned CORESETs can be named CORESETPoolIndex, and for CORESETs configured with the same CORESETPoolIndex value, it can be determined or assumed that the PDCCH is sent from the same TRP. For CORESETs without a configured CORESETPoolIndex value, it can be determined or assumed that a default value for CORESETPoolIndex is configured, and the default value can be 0.

[0443] ● Multiple PDCCH-Config Configurations: A single BWP can be configured with multiple PDCCH-Configs, and each PDCCH-Config can include the PDCCH configuration for each TRP. That is, a PDCCH-Config can configure the CORESET list and / or the search space list for each TRP, and it can be determined that one or more CORESETs and one or more search spaces included in a PDCCH-Config correspond to a specific TRP.

[0444] ●CORESET Beam / Beam Group Configuration: The TRP corresponding to the corresponding CORESET can be classified by the beam or beam group set for each CORESET. For example, when multiple CORESETs are configured with the same TCI state, it can be assumed that the corresponding CORESETs are transmitted through the same TRP, or it can be determined or assumed that the PDCCH of the PDSCH scheduled for the same TRP is transmitted in the corresponding CORESET.

[0445] ● Search Space Beam / Beam Group Configuration: Beams or beam groups can be configured for each search space, and TRPs in each search space can be classified through this configuration. For example, when the same beam / beam group or TCI state is configured in multiple search spaces, it can be determined or assumed that the same TRP is sending PDCCHs, or that PDCCHs of the same TRP's PDSCHs are scheduled to be sent in the search space.

[0446] As mentioned above, by dividing the CORESET or search space for each TRP, the PDSCH and HARQ-ACK information of each TRP can be classified, and through this, an independent HARQ-ACK codebook can be generated for each TRP and an independent PUCCH resource can be used.

[0447] <Example 2: HARQ-ACK Information Delivery Method for NC-JT Transmission>

[0448] The following embodiments provide a detailed method for sending HARQ-ACK information for NC-JT transmission.

[0449] Figure 17a , Figure 17b , Figure 17c and Figure 17d It is a view showing how to send HARQ-ACK information based on various DCI and PUCCH configurations used for NC-JT transmission.

[0450] first, Figure 17a(Option #1: HARQ-ACK for Single PDCCH NC-JT) 17-00 illustrates an example in which HARQ-ACK information for one or more PDSCH 17-05s scheduled by TRP is sent via a PUCCH resource 17-10 in the case of a single PDCCH-based NC-JT. The PUCCH resource can be indicated by the PRI and K1 values ​​in the DCI above.

[0451] Figure 17b (Option #2) to Figure 17d (Options #4) 17-20, 17-40, and 17-60 illustrate the case of NC-JT based on multiple PDCCHs. In this case, each option can be categorized based on the number of PUCCH resources used to send HARQ-ACK information corresponding to the PDSCH for each TRP and the position of the PUCCH resources on the timeline.

[0452] Figure 17b (Option #2: Combined HARQ-ACK) 17-20 shows an example where a terminal sends HARQ-ACK messages corresponding to PDSCH 17-25 and 17-26 for each TRP via a single PUCCH resource. In this case, all HARQ-ACK messages for each TRP can be generated based on a single HARQ-ACK codebook, or the HARQ-ACK messages for each TRP can be generated based on separate HARQ-ACK codebooks. In this case, the HARQ-ACK messages for each TRP are concatenated and can be sent in a single PUCCH resource.

[0453] When using a separate HARQ-ACK codebook for each TRP, as defined in Example 1-1, a TRP can be classified into at least one of the following: a set of CORESETs with the same upper-level index, a set of CORESETs belonging to the same TCI state or beam or beam group, and a set of search spaces belonging to the same TCI state or beam or beam group.

[0454] Figure 17c (Option #3: Time Division Multiplexing (TDMed) Separation of HARQ-ACK) 17-40 shows an example in which the terminal sends HARQ-ACK information corresponding to each TRP's PDSCH 17-45, 17-46 through PUCCH resources 17-50, 17-51 of different time slots 17-52, 17-53.

[0455] The time slots for the PUCCH resources used in each TRP can be determined by the K1 value mentioned above. If the K1 values ​​indicated by multiple PDCCHs point to the same time slot, it is assumed that all corresponding PDCCHs are transmitted in the same TRP, and all corresponding HARQ-ACK messages can be sent. In this case, HARQ-ACK messages connected to a single PUCCH resource located in the same time slot can be sent to the TRP.

[0456] Figure 17d (Option #4: TDMed Separate HARQ-ACK within a Time Slot) 17-60 shows an example of sending HARQ-ACK messages corresponding to each TRP's PDSCH 17-65 and 17-66 through different PUCH resources 17-70 and 17-71 in different symbols within the same time slot 17-75.

[0457] The time slot of the PUCCH resource for each TRP can be determined by the K1 value mentioned above, and if the same time slot is indicated by the K1 value indicated by multiple PDCCHs, the terminal can perform PUCCH resource selection and transmission symbol determination by at least one of the following methods.

[0458] ● TRP PUCCH resource group configuration

[0459] A PUCCH resource group for HARQ-ACK transmission can be configured for each TRP. When the TRPs in each CORESET and / or search space are classified as shown in Example 1-1, PUCCH resources for HARQ-ACK transmission for each TRP can be selected within the corresponding TRP's PUCCH resource group. TDM can be expected between PUCCH resources selected from different PUCCH resource groups; that is, the selected PUCCH resources can be expected to not overlap on a symbol basis (within the same time slot). The terminal can generate a separate HARQ-ACK codebook for each TRP and then transmit it within the PUCCH resources selected for each TRP.

[0460] ●Different PRI instructions for each TRP

[0461] As in Example 1-1, when classifying the CORESET and / or TRP for each search space, the PUCCH resource for each TRP can be selected based on the PRI. That is, the PUCCH resource selection process in Rel-15 above can be performed independently for each TRP. In this case, the PRI used to determine the PUCCH resource for each TRP can be different. For example, the terminal may not expect the PRI used to determine the PUCCH resource for each TRP to be indicated by the same value. For example, the PDCCH of TRP 1 may include PRI=n, and the PDCCH of TRP 2 may include PRIs set to PRI=m respectively.

[0462] Furthermore, TDM can be expected between the PUCCH resources indicated by the PRI of each TRP. That is, it can be expected that the selected PUCCH resources will not overlap on a symbol basis (within the same time slot). As mentioned above, a separate HARQ-ACK codebook for each TRP can be generated in the PUCCH resources selected for each TRP and then transmitted.

[0463] ● Define K1 value in units of sub-time slots

[0464] The PUCCH resource selection process described in Rel-15 above is followed, but the K1 value can be defined on a sub-slot basis. For example, a terminal can generate a HARQ-ACK codebook for a PDSCH / PDCCH indicating that HARQ-ACK should be reported in the same sub-slot, and then transmit it via the PUCCH resource indicated by the PRI. The process of generating the HARQ-ACK codebook and selecting the PUCCH resource may be independent of whether CORESET and / or TRP are classified for each search space.

[0465] When a terminal supports NC-JT reception, one of the options can be configured by the upper layer or implicitly selected depending on the situation. For example, for a terminal that supports NC-JT based on multiple PDCCHs, one of option 2 (joint HARQ-ACK) and option 3 or 4 (individual HARQ-ACK) can be selected by the upper layer. As another example, depending on whether NC-JT based on a single PDCCH or multiple PDCCHs is supported / configured, option 1 for the former and option 2, 3, or 4 for the latter can be selected.

[0466] As another example, in NC-JT based on multiple PDCCHs, the option to be used can be determined based on the selection of PUCCH resources. When PUCCH resources in the same time slot correspond to different TRPs, if the corresponding PUCCH resources are different and do not overlap on a symbol-by-symbol basis, HARQ-ACK can be sent according to option 4. If the corresponding PUCCH resources overlap on a symbol-by-symbol basis or have the same allocated symbols, HARQ-ACK can be sent according to option 2. When selecting PUCCH resources in different time slots within different TRPs, HARQ-ACK can be sent according to option 3.

[0467] The configuration of options can depend on the terminal's capabilities. For example, the base station can receive the terminal's capabilities according to the process described above and configure the options accordingly. For instance, option 4 is configured only for terminals that support in-slot TDMed split HARQ-ACK capabilities, and terminals that do not have the corresponding capabilities may not expect to be configured according to option 4.

[0468] Figure 17e This is a view illustrating an example of how a terminal sends HARQ-ACK information to a base station for NC-JT transmission.

[0469] refer to Figure 17e (Although not shown) The terminal can send the capabilities of the described options to the base station, and the base station can explicitly configure which option to apply to the terminal based on the capability information sent by the terminal, or can implicitly apply a specific option.

[0470] The terminal can receive PUCCH configuration information from the base station via higher-level signaling, step 1480. The PUCCH configuration information may include at least one of Tables 21, 22, 29, and 30, and may include at least one of the following: information for setting PUCCH groups, information for configuring the relationship between PRI and PUCCH resources as shown in Table 26, or information for setting candidate K1 values ​​as shown in Table 21.

[0471] Subsequently, the terminal can receive from the base station on the PDCCH a DCI for scheduling downlink data (which can be mixed with PDCCH reception) (step 1481) and a HARQ-ACK sent according to the above method based on the applied options. The terminal can also check at least one of the HARQ-ACK payload to be sent according to the above method, the PDSCH-to-HARQ feedback timing indicator included in the DCI, or the PRI for sending HARQ-ACK based on the applied options to determine the PUCCH resource for sending HARQ-ACK (step 1482).

[0472] After this, the terminal can send HARQ-ACK information in the determined PUCCH resource (step 1483).

[0473] Not all steps of the above method need to be performed, and specific steps can be omitted or their order can be changed.

[0474] Figure 17f This is a view illustrating an example of how a base station receives HARQ-ACK information from a terminal for NC-JT transmission.

[0475] refer to Figure 17f (Although not shown) The base station can receive terminal capabilities of the described options sent by the terminal, and can explicitly configure which option to apply to the terminal or implicitly apply a specific option based on the capability information sent by the terminal.

[0476] The base station can send PUCCH configuration information to the terminal via higher-layer signaling (step 1485). The PUCCH configuration information may include at least one of Tables 21, 22, 29, and 30, and may include at least one of the following: information for setting PUCCH groups, information for setting the relationship between PRI and PUCCH resources in Table 26, or information for setting candidate K1 values ​​in Table 21.

[0477] Subsequently, the base station sends a DCI for scheduling downlink data to the terminal on the PDCCH (this can be mixed with PDCCH transmission) (step 1486), and the terminal checks at least one of the HARQ-ACK payload to be sent according to the above method, the PDSCH-to-HARQ feedback timing indicator included in the DCI, or the PRI for sending HARQ-ACK based on the applied options, to determine the PUCCH resource to send HARQ-ACK.

[0478] Subsequently, the terminal sends HARQ-ACK information from the determined PUCCH resource, and the base station can receive HARQ-ACK information from the PUCCH resource determined in the same way (step 1487).

[0479] Not all steps of the above method need to be performed, and specific steps can be omitted or their order can be changed.

[0480] <Example 3: Resource Configuration for PUCCH Transmission to Multiple TRPs>

[0481] For PUCCH transmissions to multiple TRPs, PUCCH resources can be configured using at least one of the following methods. Furthermore, the transmission of PUCCH resources can refer to the transmission of PUCCH itself or the transmission of UCI via PUCCH.

[0482] 1) Repeated PUCCH transmission via a single PUCCH resource: PUCCH is repeatedly transmitted via a single PUCCH resource according to a predetermined repeated transmission unit, and the PUCCH transmission beam and / or transmission power can be changed for each repeated transmission or in some repeated transmissions among all repeated transmissions.

[0483] 2) PUCCH transmission via multiple PUCCH resources: Multiple different PUCCHs containing the same control information are transmitted through different TRPs, and the multiple PUCCHs can be non-overlapping. Furthermore, different transmission beams and / or transmission powers can be applied to multiple PUCCHs.

[0484] Detailed embodiments of each of the above resource allocation methods are described below.

[0485] <Example 3-1: Resource configuration for repeatedly sending PUCCH to multiple TRPs on a single PUCCH resource>

[0486] When repeatedly sending PUCCH to multiple TRPs on a single PUCCH resource, the following differences may exist compared to repeatedly sending PUCCH to a single TRP on a single PUCCH resource.

[0487] ●Is repeated transmission of short PUCCH required?

[0488] When PUCCHs are repeatedly transmitted on a single PUCCH resource using a single TRP, only long PUCCHs are used, and repeated transmission of short PUCCHs is not supported. This is because repeated transmission is for enhanced coverage, while short PUCCHs are not designed for enhanced coverage.

[0489] On the other hand, one objective of performing repeated PUCCH transmissions to multiple TRPs can be overcome by blocking, and using short PUCCHs can overcome blocking with less latency compared to using long PUCCHs. Therefore, short PUCCHs can be used for repeated PUCCH transmissions to multiple TRPs.

[0490] ●Does the scheduling need to reflect the transient time between repeated transmissions?

[0491] When performing repeated short PUCCH transmissions across multiple TRPs, beam and transmission power variations may occur between transmissions. Changing the transmission power of a short PUCCH may require a guard time or offset between transmissions to accommodate the aforementioned transients. Therefore, when performing repeated short PUCCH transmissions across multiple TRPs, repeating transmissions that reflect the offset are necessary.

[0492] First, short PUCCH retransmissions can be performed on a sub-slot basis. Figure 18a It is a view showing repeated short PUCCH transmissions in units of sub-slots.

[0493] The length of a sub-slot can be equal to or longer than the length of a repeatedly transmitted short PUCCH, and the length of a sub-slot can vary over time.

[0494] Figure 18a An example (18-05) shows all sub-slots having the same length as 2. The offset between short PUCCHs can be configured through the base station's PUCCH resource scheduling, such as configuring the start symbol position in the sub-slots of the short PUCCH and the length of the short PUCCH. However, if the length of the sub-slot is the same as the length of the short PUCCH and the offset cannot be configured due to PUCCH resource scheduling, it may be necessary to configure a method for offsetting repeated short PUCCH transmissions. The offset can be configured on a sub-slot basis or on a symbol basis.

[0495] Figure 18a An example (18-10) shows an offset configured as 1 symbol. The offset can be configured between repeated transmissions of each short PUCCH. Alternatively, when no transmit power change occurs during repeated transmissions of a short PUCCH, no offset is needed, and therefore the offset can be configured only between repeated transmissions where a transmit power change occurs.

[0496] The phrase “between repeated transmissions that have changed transmission power” can be replaced by expressions such as “between repeated transmissions that have changed beam” and “between repeated transmissions with different spatial relationship information”.

[0497] Although the above description has been described to facilitate the transmission of repeated short PUCCHs, the above description can be similarly applied to long PUCCHs.

[0498] Meanwhile, considering the possibility of repeatedly transmitting PUCCH by alternating the use of multiple PUCCH resources, PUCCH retransmission may not occur for each adjacent sub-slot, but may be repeated for each sub-slot within a predetermined period. Figure 18a An example of configuring the above repetitive transmission period as two sub-slots is shown. The preset offset can be reflected in the repetitive transmission period (18-15).

[0499] Next, the repeated transmission of short PUCCHs can be performed in a time slot or sub-time slot. Figure 18b It is a view showing the short PUCCH transmissions that repeat in a time slot or sub-time slot.

[0500] The aforementioned short PUCCH retransmissions can be performed within a single time slot or sub-time slot (18-20), or across multiple time slots or sub-time slots (18-30). If retransmissions are performed within a single time slot or sub-time slot (18-20), the offset between retransmissions can be configured (18-25). The offset can be configured in units of symbols. The offset can be configured between retransmissions of each short PUCCH. Alternatively, when no transmit power change occurs during the retransmission of a short PUCCH, no offset is required, and therefore the offset can be configured only between retransmissions where a transmit power change occurs.

[0501] The phrase “between repeated transmissions that have changed transmission power” can be replaced by expressions such as “between repeated transmissions that have changed beam” and “between repeated transmissions with different spatial relationship information”.

[0502] Alternatively, the configuration and / or the presence or absence of an offset can be varied depending on the length of the repeatedly transmitted PUCCH. For example, an offset can be configured or applied only when retransmitting short PUCCHs, and not applied when retransmitting long PUCCHs. This may be because the required guard time between transmissions where a power change occurs varies depending on the length of the transmitted PUCCH.

[0503] If repetitive transmissions are performed across multiple time slots or sub-time slots (18-30), the offset between repetitive transmissions can be configured (18-35). The offset can only be applied between repetitive transmissions within a single time slot or sub-time slot. In this case, the offset between repetitive transmissions across different time slots or sub-time slots can be given by configuring the start symbol of the short PUCCH (18-40). That is, the start symbol configuration of the short PUCCH can be applied to the repetitive transmission of the first short PUCCH in each time slot or sub-time slot.

[0504] Alternatively, an offset can be applied between repeated transmissions across different time slots or sub-time slots. In this case, the start symbol configured for the short PUCCH can be applied only to the first short PUCCH transmission in all short PUCCH repeated transmissions. The aforementioned offset can be configured between repeated transmissions of each short PUCCH. Alternatively, when no transmit power change occurs during the repeated transmission of a short PUCCH, no offset is needed, and therefore the offset can be configured only between repeated transmissions where a transmit power change occurs.

[0505] The phrase "between repeated transmissions where transmission power changes" can be replaced by expressions such as "between repeated transmissions where beam changes occur" and "between repeated transmissions with different spatial relationship information." Alternatively, whether to configure and / or apply an offset can vary depending on the length of the repeatedly transmitted PUCCH. For example, an offset can be configured or applied only when repeatedly transmitting short PUCCHs, and not applied when repeatedly transmitting long PUCCHs. This might be because the need for a guard time between transmissions where transmission power changes varies depends on the length of the transmitted PUCCHs.

[0506] Although the above description has been described to facilitate the transmission of repeated short PUCCHs, the above description can be similarly applied to long PUCCHs.

[0507] Figure 18c This is another view showing repeated PUCCH transmissions in a time slot or sub-time slot according to one embodiment.

[0508] refer to Figure 18c When repeating PUCCH transmissions within a time slot or sub-time slot, some of the PUCCHs in all repeating transmissions may cross the boundaries of the time slot or sub-time slot (18-50). As a way to handle this situation, at least one of the following methods may be included.

[0509] Method 1. The terminal can discard symbols that cross the timeslot or sub-slot boundaries in the retransmission PUCCH. In this case, the configured number of retransmissions is the same as the actual number of retransmissions.

[0510] Method 2. The terminal may treat symbols on the boundaries of time slots or sub-time slots in a recurring transmission as new recurring transmissions. In this case, the actual number of recurring transmissions may be greater than the configured number of recurring transmissions.

[0511] Method 3. The terminal can discard duplicate transmissions at the timeslot or sub-timeslot boundaries in the duplicate transmission PUCCH. In this case, the actual number of duplicate transmissions may be less than the configured number of duplicate transmissions.

[0512] Method 4. The terminal can shift repeated transmissions, i.e., repeated transmissions on the boundary of a time slot or sub-time slot, to the next time slot or sub-time slot. The position of the symbol used to send PUCCH by shift can be the first symbol of the next time slot or sub-time slot, or it can be the position set as the start symbol of PUCCH.

[0513] Method 5. The base station can schedule to avoid duplicate PUCCH transmissions, i.e., duplicate transmissions at the boundaries of time slots or sub-time slots. Scheduling is performed within duplicate PUCCH transmissions. In this case, the terminal may not expect duplicate transmissions across time slot or sub-time slot boundaries. The above method can be applied similarly even when one or more DL symbols exist in a time slot or sub-time slot and the duplicate PUCCH transmissions overlap with the DL symbols.

[0514] In these methods, according to methods 1 and 2, the lengths of the repeatedly transmitted PUCCHs can be different. In this case, soft combining between PUCCHs with different lengths can be avoided. Therefore, it may be necessary to change at least one of the following constraints or PUCCH encodings.

[0515] - Constraints: The lengths of repeated PUCCH transmissions for the same target TRP should be the same, while the lengths of repeated PUCCH transmissions for different target TRPs can be different. This is because, in the case of repeated transmissions for different target TRPs, soft combining of PUCCHs received from different TRPs can be difficult due to backhaul capacity limitations between TRPs. Therefore, soft combining between different TRPs is not required. On the other hand, while soft combining is possible in the case of repeated transmissions for the same target TRP, unnecessarily degrading performance may occur if it is not supported.

[0516] PUCCH Encoding Changes: When encoding a PUCCH based on the length of the UCI, if the UCI length is 11 bits or less, Reed-Muller coding can be used; if the UCI length exceeds it, polar coding can be used. In the case of polar coding, if E is the total number of transmittable bits based on the amount of resources allocated to the PUCCH, a different encoding method can be applied to each retransmitted PUCCH based on E. Therefore, in the case of polar coding, it is assumed that the E value is the same for all retransmitted PUCCHs, then encoding is performed, and then adaptive transmission is performed based on the actual amount of resources for each retransmitted PUCCH. For example, if the actual amount of resources for a retransmitted PUCCH is less than the E value, a portion of the code encoded based on the E value can be discarded (pruning). Alternatively, if the actual amount of resources for a retransmitted PUCCH is greater than the value E, a portion of the encoded code can be repeated based on the actual amount of resources. As a criterion for determining the aforementioned E value, at least one of the following can be included.

[0517] ■Reference 1: PUCCH corresponds to a specific order in repeated PUCCH transmissions. For example, the first PUCCH.

[0518] ■Reference 2: PUCCH with the largest resource quantity in repeated transmission PUCCH.

[0519] ■Reference 3: PUCCH with the minimum resource usage in repeated transmission PUCCH.

[0520] ■Reference 4: Average amount of each resource quantity by repeatedly transmitting PUCCH.

[0521] ■Reference 5: PUCCH sent to a specific TRP in the recurring PUCCH. For example, the PUCCH corresponding to the first beam.

[0522] For repeated PUCCH transmissions, the number of TRPs can be less than the number of repeated transmissions. In this case, a mapping rule for each repeated transmission needs to be sent for each TRP. As an example, the transmission mode for each TRP can be configured periodically.

[0523] Figure 19 This is a view illustrating an example of the mapping rules between repeated PUCCH transmissions and transmit and receive points (TRPs) according to embodiments of this disclosure.

[0524] refer to Figure 19 , Figure 19 This illustrates the transmission pattern for each TRP when the total number of repeating transmissions is N and the number of receiving TRPs is K. Each TRP is assigned to L consecutive repeating transmissions in a cyclic manner. The value of L can be configured as 1, 2, ... , One of them (19-10, 19-20). When the L value is small, the TRP switching is more frequent. The advantage is that the probability of early termination increases, but the disadvantage is that more TRP switching overhead is required. As another example, the transmission mode for each TRP used for all repeated transmissions can be indicated. For example, when two receiving TRPs are designated for 4 repeated transmissions and they are named TRP#1 and TRP#2, the repeated transmission mode can be indicated as {TRP#1, TRP#1, TRP#1, TRP#2}.

[0525] <Example 3-2: Resource configuration for PUCCH transmission to multiple TRPs on multiple PUCCH resources>

[0526] By including the same UCI on multiple PUCCH resources, the UCI can be sent to a different TRP on each of the multiple PUCCH resources. In this case, different beams can be configured for each of the multiple PUCCH resources, and when repetitive transmission is configured for a PUCCH resource, the entire repetitive transmission can be sent to the same TRP. The terminal should determine whether a particular UCI is sent on multiple PUCCH resources or on a single PUCCH resource, as in the prior art, and for this purpose, at least one of the following methods can be used.

[0527] - Explicit PUCCH Set Configuration: PUCCH resources used to transmit the same UCI can be grouped into a PUCCH set. PUCCH sets can be explicitly configured, and each PUCCH set can have a different ID. The base station can indicate to the terminal that the UCI is transmitted on multiple PUCCH resources by indicating the PUCCH set ID used for UCI transmission or multiple PUCCH resource IDs belonging to the PUCCH set. Alternatively, by indicating a PUCCH resource ID to the terminal, the UCI can be indicated to be transmitted on a single PUCCH resource. Alternatively, PUCCH sets are also defined in PUCCH resource indicators such as PRI, and the use of multiple PUCCH resources can be determined based on the PRI value. For example, a specific PRI value can indicate a PUCCH set, while another PRI value can be configured to indicate a single PUCCH resource.

[0528] - Implicit PUCCH Set Configuration: When configuring a PUCCH resource group for each TRP, PUCCH resources are selected according to specific rules for each group, and the PUCCH resources selected for all groups can be determined as a PUCCH set. As an example of a rule, PUCCH resources with the same PUCCH resource ID within a group can be configured as a PUCCH set. In this case, the terminal can determine whether to use multiple PUCCH resources based on whether one or more PUCCH resources corresponding to the PUCCH resource ID exist.

[0529] Constraints on the PUCCH set can be configured. For example, if duplicate transmission of PUCCH resources in the PUCCH set is not set, all PUCCH resources in the set can be sent in the same time slot or sub-time slot. In this case, overlap between PUCCH resources in the set on the time axis may not be allowed. As another example, the maximum number of PUCCH resources in the set can be limited to a maximum value. For example, the maximum number of PUCCH resources could be 2.

[0530] <Example 4: Terminal capability for transmission to multiple TRPs>

[0531] Each option associated with PUCCH transmissions to the aforementioned TRPs may require independent terminal capabilities. For example, some terminals may not support repeated short PUCCH transmissions. Accordingly, the terminal reports to the base station whether it supports repeated short PUCCH transmissions via a capability report, and the base station can configure repeated short PUCCH transmissions only for terminals that support them after receiving the terminal capability report.

[0532] Furthermore, even if a terminal supports repeated short PUCCH transmissions, the minimum offset between repetitions that each terminal can support may differ. Therefore, a terminal can report the minimum offset between repetitions that it can support during repeated short PUCCH transmissions to the base station via capability reports, in symbols, time slots, sub-time slots, or absolute time units.

[0533] After reporting the terminal's capabilities, the base station can schedule PUCCHs by referring to the terminal's minimum supported offset. The minimum offset can be reported not only regarding the offset between short PUCCH repetitions, but also regarding the offset between short PUCCH-long PUCCH repetitions and the offset between long PUCCH-long PUCCH repetitions.

[0534] Meanwhile, the minimum offset may not be an offset applied to all repeated PUCCH transmissions. For reasons such as ensuring the aforementioned transition time, the minimum offset may be a value applied only between repeated PUCCH transmissions that accompany beam / transmission power changes. For ease of description, the above description is only for repeated transmissions of the same PUCCH in Embodiment 3-1, but similarly applicable to the transmission of multiple PUCCH resources in Embodiment 3-2.

[0535] Furthermore, the maximum number of PUCCHs that each terminal can repeatedly transmit in a time slot or sub-time slot can also be different. Accordingly, the terminal can report the maximum number of PUCCHs repeatedly transmitted to the base station through a capability report. Simultaneously, the length of the sub-time slots supported by the terminal can also vary from terminal to terminal, and the length of the repeatedly transmitted sub-time slots can be reported to the base station through a capability report. Furthermore, combinations of the above capabilities can be reported to the base station. For example, the maximum number of PUCCHs repeatedly transmitted in a time slot for each length of the sub-time slot can be reported to the base station through a capability report. For ease of description, the above description only pertains to the repeated transmission of the same PUCCH in Embodiment 3-1, but similarly, it can be applied to the transmission of multiple PUCCH resources in Embodiment 3-2.

[0536] Figure 20 This is a view showing the structure of a terminal in a wireless communication system according to one embodiment.

[0537] refer to Figure 20 The terminal may include a transceiver 20-00, a memory 20-05, and a processor 20-10. The transceiver 20-00 and processor 20-10 of the terminal can operate according to the communication method of the base station described above. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than those described above. Furthermore, the transceiver 20-00, memory 20-05, and processor 20-10 may be implemented as a single chip.

[0538] Transceiver 20-00 can transmit and receive signals with a base station. These signals may include control information and data. For this purpose, transceiver 20-00 may include an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts its frequency. However, this is only one embodiment of transceiver 20-00, and the components of transceiver 20-00 are not limited to RF transmitters and RF receivers.

[0539] In addition, transceiver 20-00 can receive signals via a wireless channel, output signals to processor 20-10, and transmit signals output from processor 20-10 via a wireless channel.

[0540] The memory 20-05 can store programs and data necessary for the operation of the terminal. Furthermore, the memory 20-05 can store control information or data included in signals sent or received by the terminal. The memory 20-05 can consist of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. Moreover, multiple memories 20-05 can exist.

[0541] Furthermore, processor 20-10 can control a series of processes, enabling the terminal to operate according to the above embodiments. For example, processor 20-10 can control the terminal's components to receive a DCI consisting of two layers and simultaneously receive multiple PDSCHs. Multiple processors 20-10 may exist, and processor 20-10 can execute terminal component control operations by executing programs stored in memory 20-05.

[0542] Figure 21 This is a view showing the structure of a base station in a wireless communication system according to one embodiment.

[0543] refer to Figure 21 The base station may include a transceiver 21-00, a memory 21-05, and a processor 21-10. The transceiver 21-00 and processor 21-10 of the base station can operate according to the communication method of the base station described above. 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 21-00, memory 21-05, and processor 21-10 may be implemented as a single chip.

[0544] Transceiver 21-00 can send signals to or receive signals from a terminal. Here, signals may include control information and data. For this purpose, transceiver 21-00 may include an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts its frequency. However, this is only one embodiment of transceiver 21-00, and the components of transceiver 21-00 are not limited to RF transmitters and RF receivers.

[0545] In addition, transceiver 21-00 can receive signals via a wireless channel, output signals to processor 21-10, and transmit signals output from processor 21-10 via a wireless channel.

[0546] The memory 21-05 can store programs and data required for the operation of the base station. Furthermore, the memory 21-05 can store control information or data included in signals transmitted and received by the base station. The memory 21-05 can be formed from storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. Moreover, multiple memories 21-05 can exist.

[0547] Processor 21-10 can control a series of processes that enable the base station to operate according to the above embodiments. For example, processor 21-10 can control each component of the base station to configure and transmit two-layer DCI, including allocation information for multiple PDSCHs. Multiple processors 21-10 may exist, and processor 21-10 can perform component control operations of the base station by executing programs stored in memory 21-05.

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

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

[0550] 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), magnetic disk storage devices, compressed optical disc-ROM (CD-ROM), digital versatile optical disc (DVD) or other types of optical storage devices, or magnetic tape cassettes. Alternatively, any combination of some or all of these can form the memory storing the program. Furthermore, an electronic device may include multiple such memories.

[0551] Additionally, 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. Furthermore, a separate storage device on a communication network can access the portable electronic device.

[0552] In the detailed embodiments described above, elements included in this disclosure are expressed 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 expressed in a singular or plural form. Thus, an element expressed in a plural form may also include a single element, or an element expressed in a singular form may include multiple elements.

[0553] The embodiments of this disclosure described and illustrated in the specification and drawings are presented to facilitate 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, other modifications and variations can be made to the technical concept of this disclosure, which will be apparent to those skilled in the art. Furthermore, the corresponding embodiments described above can be combined if necessary. For example, embodiments of this disclosure can be partially combined to operate a base station and a terminal. For example, the methods proposed in this disclosure can be partially combined to operate a base station and a terminal. Moreover, although the above embodiments have been described using an FDD LTE system, other variations based on the technical aspects of the embodiments can be implemented in other systems such as TDD LTE, 5G, and NR systems.

[0554] In the accompanying drawings describing the methods of this disclosure, the order of description does not always correspond to the order in which the steps of each method are performed, and the order of the steps may be changed or the steps may be performed in parallel.

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

[0556] While this disclosure has been described with reference to various embodiments, various changes and modifications may be made to those skilled in the art. This disclosure is intended to include such changes and modifications that fall within the scope of the appended claims.

Claims

1. A method performed by a terminal in a communication system, the method comprising: The Physical Uplink Control Channel (PUCCH) configuration and the Physical Downlink Shared Channel (PDSCH) configuration are received from the base station. The PUCCH configuration includes information about the number of time slots and information about the length of sub-time slots. Receive downlink control information (DCI) including resource allocation information from the base station; Data is received from the base station based on the PDSCH configuration and the resource allocation information; as well as Based on the PUCCH configuration, repeating PUCCH transmissions for the data is performed on N time slots, where N indicates the number of time slots. The repetition of the PUCCH transmission is performed alternately between multiple sending and receiving points (TRPs) based on each L repetition of the PUCCH transmission.

2. The method as described in claim 1, wherein, The value of L is 1 or 2, and the PUCCH includes HARQ ACK information.

3. The method as described in claim 1, wherein, The length of the sub-slot is either 2 symbols or 7 symbols.

4. The method of claim 1, wherein, The PUCCH configuration further includes information about the number of symbols and an index of the starting symbol.

5. A method performed by a base station in a communication system, the method comprising: Send the Physical Uplink Control Channel (PUCCH) configuration and the Physical Downlink Shared Channel (PDSCH) configuration to the terminal. The PUCCH configuration includes information about the number of time slots and information about the length of sub-time slots. Send downlink control information (DCI) including resource allocation information to the terminal; Data is sent to the terminal based on the PDSCH configuration and the resource allocation information; and Based on the PUCCH configuration, the terminal receives repeated PUCCH transmissions for the data on N time slots, where N indicates the number of time slots. The repetition of the PUCCH transmission is performed alternately between multiple sending and receiving points (TRPs) based on each L repetition of the PUCCH transmission.

6. The method of claim 5, wherein, The value of L is 1 or 2, and the PUCCH includes HARQ ACK information.

7. The method of claim 5, wherein, The length of the sub-slot is either 2 symbols or 7 symbols.

8. The method of claim 5, wherein, The PUCCH configuration further includes information about the number of symbols and an index of the starting symbol.

9. A terminal in a communication system, the terminal comprising: transceiver; as well as A controller, connected to the transceiver and configured to: The Physical Uplink Control Channel (PUCCH) configuration and the Physical Downlink Shared Channel (PDSCH) configuration are received from the base station. The PUCCH configuration includes information about the number of time slots and information about the length of sub-time slots. Receive downlink control information (DCI) including resource allocation information from the base station; Data is received from the base station based on the PDSCH configuration and the resource allocation information; as well as Based on the PUCCH configuration, repeating PUCCH transmissions for the data is performed on N time slots, where N indicates the number of time slots. The repetition of the PUCCH transmission is performed alternately between multiple sending and receiving points (TRPs) based on each L repetition of the PUCCH transmission.

10. The terminal as claimed in claim 9, wherein, The value of L is 1 or 2, and the PUCCH includes HARQ ACK information.

11. The terminal as claimed in claim 9, wherein, The length of the sub-slot is either 2 symbols or 7 symbols.

12. The terminal as described in claim 9, wherein, The PUCCH configuration further includes information about the number of symbols and the index of the starting symbol.

13. A base station in a communication system, the base station comprising: transceiver; as well as A controller, connected to the transceiver and configured to: Send the Physical Uplink Control Channel (PUCCH) configuration and the Physical Downlink Shared Channel (PDSCH) configuration to the terminal. The PUCCH configuration includes information about the number of time slots and information about the length of sub-time slots. Send downlink control information (DCI) including resource allocation information to the terminal; Data is sent to the terminal based on the PDSCH configuration and the resource allocation information; and Based on the PUCCH configuration, the terminal receives repeated PUCCH transmissions for the data on N time slots, where N indicates the number of time slots. The repetition of the PUCCH transmission is performed alternately between multiple sending and receiving points (TRPs) based on each L repetition of the PUCCH transmission.

14. The base station as described in claim 13, wherein, The value of L is 1 or 2, and the PUCCH includes a hybrid automatic repeat request acknowledgment.

15. The base station as described in claim 13, wherein, The length of the sub-slot is one of 2 symbols or 7 symbols, and the PUCCH configuration further includes information about the number of symbols and an index of the starting symbol.

Images