Method and apparatus for receiving semi-persistent scheduling physical downlink shared channel and transmitting configured grant physical uplink shared channel in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method of a user equipment (UE) in a wireless communication system according to an embodiment of the present disclosure may comprise the steps of: receiving, from a base station, a radio resource control (RRC) message including a scheduling parameter set for a plurality of semi-persistent scheduling (SPS) physical downlink shared channels (PDSCHs); receiving, from the base station, downlink control information (DCI) for activating an SPS configuration including the scheduling parameter set for the plurality of SPS PDSCHs; and receiving, from the base station, an SPS PDSCH in an SPS reception slot by using a first SPS PDSCH scheduling parameter set or a second SPS PDSCH scheduling parameter set determined on the basis of the scheduling parameter set for the plurality of SPS PDSCHs.

Description

Method and device for receiving a semi-fixed scheduling physical downlink common channel and transmitting a set grant physical uplink common channel in a wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method for a terminal to receive a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) and transmit a configured grant (CG) physical uplink shared channel (PUSCH), and a device capable of performing the same.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

[0005] In addition, standardization of radio interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover (CHO) and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] As described above and with the development of mobile communication systems, various services have become available, and methods for effectively providing these services are required.

[0009] The present disclosure seeks to provide a device and method capable of effectively providing a service in a mobile communication system.

[0010] According to one embodiment of the present disclosure, a method of a user equipment (UE) in a wireless communication system may include the steps of: receiving, from a base station, an RRC (radio resource control) message including a scheduling parameter set for a plurality of semi-persistent scheduling (SPS) physical downlink shared channels (PDSCHs); receiving, from the base station, downlink control information (DCI) for activating an SPS configuration including the scheduling parameter set for the plurality of SPS PDSCHs; and receiving, in an SPS reception slot, an SPS PDSCH from the base station using a first SPS PDSCH scheduling parameter set or a second SPS PDSCH scheduling parameter set determined based on the scheduling parameter set for the plurality of SPS PDSCHs.

[0011] According to one embodiment of the present disclosure, a method of a base station in a wireless communication system may include the steps of: transmitting, to a user equipment (UE), an RRC (radio resource control) message including a scheduling parameter set for a plurality of semi-persistent scheduling (SPS) physical downlink shared channels (PDSCHs); transmitting, to the UE, downlink control information (DCI) for activating an SPS configuration including the scheduling parameter set for the plurality of SPS PDSCHs; and transmitting, in an SPS reception slot, an SPS PDSCH to the UE using a first SPS PDSCH scheduling parameter set or a second SPS PDSCH scheduling parameter set determined based on the scheduling parameter set for the plurality of SPS PDSCHs.

[0012] According to one embodiment of the present disclosure, a user equipment (UE) in a wireless communication system may include a transceiver; and a control unit. The control unit may be configured to: receive an RRC (radio resource control) message including a scheduling parameter set for a plurality of SPS (semi-persistent scheduling) physical downlink shared channels (PDSCHs) from a base station, receive DCI (downlink control information) for activating an SPS configuration including the scheduling parameter set for the plurality of SPS PDSCHs from the base station, and receive an SPS PDSCH from the base station in an SPS reception slot using a first SPS PDSCH scheduling parameter set or a second SPS PDSCH scheduling parameter set determined based on the scheduling parameter set for the plurality of SPS PDSCHs.

[0013] According to one embodiment of the present disclosure, a base station in a wireless communication system may include a transceiver; and a control unit. The control unit may transmit an RRC (radio resource control) message including a scheduling parameter set for a plurality of semi-persistent scheduling (SPS) physical downlink shared channels (PDSCHs) to a user equipment (UE), transmit downlink control information (DCI) for activating an SPS configuration including the scheduling parameter set for the plurality of SPS PDSCHs to the UE, and transmit an SPS PDSCH to the UE in an SPS reception slot using a first SPS PDSCH scheduling parameter set or a second SPS PDSCH scheduling parameter set determined based on the scheduling parameter set for the plurality of SPS PDSCHs.

[0014] The disclosed embodiment can provide a device and method capable of effectively providing a service in a mobile communication system.

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

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

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

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

[0019] FIG. 5 is a diagram illustrating the structure of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0020] FIG. 6 is a diagram for explaining a method for a base station and a terminal to transmit and receive data by taking into account downlink data channels and rate matching resources according to one embodiment of the present disclosure.

[0021] FIG. 7 is a diagram illustrating an example of frequency axis resource allocation of a physical downlink shared channel (PDSCH) in a wireless communication system according to one embodiment of the present disclosure.

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

[0023] FIG. 9 is a diagram illustrating an example of time axis resource allocation according to subcarrier spacing of a data channel and a control channel in a wireless communication system according to one embodiment of the present disclosure.

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

[0025] Figure 11 is a drawing illustrating a problem to be addressed in this disclosure.

[0026] FIG. 12 is a diagram for receiving a PDSCH based on a plurality of SPS PDSCH scheduling parameter sets according to one embodiment of the present disclosure.

[0027] FIG. 13 is a drawing illustrating an embodiment of the present disclosure.

[0028] Figure 14 is a flowchart according to one embodiment of the present disclosure.

[0029] FIG. 15 is a diagram illustrating an indicator for a terminal to receive an SPS PDSCH of slot n according to one embodiment of the present disclosure.

[0030] FIG. 16 is a diagram illustrating a process for selecting an SPS PDSCH to be received in one slot according to one embodiment of the present disclosure.

[0031] FIG. 17 is a diagram illustrating an SPS PDSCH that a terminal can receive according to one embodiment of the present disclosure.

[0032] FIG. 18 is a diagram illustrating an example of an operation when a terminal has the ability to receive multiple PDSCHs in one symbol according to one embodiment of the present disclosure.

[0033] FIG. 19 is a diagram illustrating another example of operation when a terminal has the ability to receive multiple PDSCHs in one symbol according to one embodiment of the present disclosure.

[0034] FIG. 20 is a diagram illustrating a process for selecting an SPS PDSCH to be received by a terminal according to one embodiment of the present disclosure.

[0035] FIG. 21 is a diagram illustrating a method for a terminal to cancel reception of an SPS PDSCH in order to receive a DG PDSCH when the terminal has the ability to receive one PDSCH in one symbol according to one embodiment of the present disclosure.

[0036] FIG. 22 is a diagram for a case where a terminal has the ability to receive up to two PDSCHs in one symbol according to one embodiment of the present disclosure.

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

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

[0039] To meet the increasing demand for wireless data traffic since the commercialization of 4G communication systems, efforts are being made to develop improved 5G communication systems, or pre-5G communication systems. For this reason, 5G communication systems, or pre-5G communication systems, are also called beyond 4G networks or post-LTE systems. To achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (e.g., 60 GHz bands). To mitigate radio path loss and increase the transmission range of radio waves in ultra-high frequency bands, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antenna technologies are being discussed in 5G communication systems. In addition, to improve the network of the system, technologies such as evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device communication (D2D), wireless backhaul, moving networks, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation are being developed in 5G communication systems.In addition, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access) are being developed in 5G systems.

[0040] Meanwhile, the Internet is evolving from a human-centric network where humans create and consume information to an Internet of Things (IoT) network where information is exchanged and processed between distributed components, such as objects. The Internet of Everything (IoE) is also emerging, combining IoT technologies with big data processing technologies, such as those connected to cloud servers. To implement the IoT, technological elements such as sensing technology, wireless and wired communication and network infrastructure, service interface technology, and security technology are required. Recently, research is being conducted on technologies such as sensor networks, Machine-to-Machine (M2M), and Machine-Type Communication (MTC) for connecting objects. In the IoT environment, intelligent IT (Internet Technology) services can be provided that collect and analyze data generated from connected objects to create new value for human life. IoT can be applied to areas such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services through the convergence and integration of existing IT (information technology) technologies with various industries.

[0041] Accordingly, various attempts are being made to apply 5G communication systems (also known as New Radio (NR)) to IoT networks. For example, technologies such as sensor networks, machine-to-machine (M2M), and machine-type communication (MTC) are being implemented using 5G communication techniques such as beamforming, MIMO, and array antennas. The application of cloud RAN, a big data processing technology described above, can also be considered an example of the convergence of 3eG and IoT technologies.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0057] [NR time-frequency resources]

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

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

[0060] The horizontal axis of Figure 1 represents the time domain, and the vertical axis represents the frequency domain. The basic unit of resources in the time and frequency domains is a resource element (RE, 101), which can be defined as 1 OFDM (Orthogonal Frequency Division Multiplexing) symbol (102) on the time axis and 1 subcarrier (103) on the frequency axis. In the frequency domain (For example, 12) consecutive REs can form one resource block (RB, 104).

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

[0062] Referring to FIG. 2, an example of a structure of a frame (200), a subframe (201), and a slot (202) is illustrated. One frame (200) can be defined as 10 ms. One subframe (201) can be defined as 1 ms, and therefore one frame (200) can be composed of a total of 10 subframes (201). One slot (202, 203) can be defined as 14 OFDM symbols (i.e., the number of symbols per slot ( ) 1 subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per 1 subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing.

[0063] In Fig. 2, the cases where μ=0(204) and μ=1(205) are illustrated as the subcarrier spacing setting values. When μ=0(204), 1 subframe (201) can be composed of 1 slot (202), and when μ=1(205), 1 subframe (201) can be composed of 2 slots (203). That is, depending on the setting value μ for the subcarrier spacing, the number of slots per subframe ( ) may vary, and accordingly the number of slots per frame ( ) may vary. Depending on the subcarrier spacing setting μ can be defined as [Table 1] below.

[0064] [Table 1]

[0065]

[0066] [Bandwidth Part (BWP)]

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

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

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

[0070] [Table 2]

[0071]

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

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

[0074] The bandwidth settings supported by 5G systems can be used for various purposes.

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

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

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

[0078] In the method of configuring the bandwidth part, terminals before RRC connection (Connected) can receive configuration information for the initial bandwidth part through the MIB (Master Information Block) during the initial access stage. More specifically, the terminal can receive a control region (Control Resource Set, CORESET) for a downlink control channel on which downlink control information (DCI) that schedules a system information block (SIB) can be transmitted from the MIB of the physical broadcast channel (PBCH). The bandwidth of the control region configured by the MIB can be regarded as the initial bandwidth part, and the terminal can receive the physical downlink shared channel (PDSCH) on which the SIB is transmitted through the configured initial bandwidth part. In addition to receiving the SIB, the initial bandwidth part can also be utilized for other system information (Other System Information, OSI), paging, and random access.

[0079] [Bandwidth Part (BWP) Change]

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

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

[0082] [Table 3]

[0083]

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

[0085] According to the requirement for bandwidth part change delay time mentioned above, when the terminal receives DCI including bandwidth part change indicator in slot n, the terminal changes to the new bandwidth part indicated by the bandwidth part change indicator in slot n+T. BWP It can be completed at a later time, and transmission and reception for the data channel scheduled by the DCI can be performed in the new bandwidth portion that has been changed. When the base station wants to schedule a data channel in the new bandwidth portion, the terminal's bandwidth portion change delay time (T BWP ), time domain resource allocation for the data channel can be determined. That is, when the base station schedules a data channel with a new bandwidth portion, the data channel can be scheduled after the bandwidth portion change delay time in the method of determining time domain resource allocation for the data channel. Accordingly, the terminal can determine whether the DCI instructing a bandwidth portion change is after the bandwidth portion change delay time (T BWP) may not be expected to indicate a slot offset (K0 or K2) value smaller than that.

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

[0087] [SS / PBCH block]

[0088] Next, we will explain the SS (Synchronization Signal) / PBCH block in the 5G system.

[0089] An SS / PBCH block may refer to a physical layer channel block consisting of a PSS (Primary SS), SSS (Secondary SS), and PBCH. Specifically, it is as follows.

[0090] - PSS: A signal that serves as a reference for downlink time / frequency synchronization and provides some information about the cell ID.

[0091] - SSS: It serves as a reference for downlink time / frequency synchronization and provides the remaining cell ID information not provided by PSS. Additionally, it can serve as a reference signal for PBCH demodulation.

[0092] - PBCH: Provides essential system information required for the terminal's data channel and control channel transmission and reception. Essential system information may include search space-related control information indicating radio resource mapping information for the control channel, and scheduling control information for a separate data channel that transmits system information.

[0093] - SS / PBCH Block: An SS / PBCH block is composed of a combination of PSS, SSS, and PBCH. One or more SS / PBCH blocks can be transmitted within a 5ms period, and each transmitted SS / PBCH block can be distinguished by an index.

[0094] The terminal can detect PSS and SSS in the initial access stage, and decode PBCH. The terminal can obtain MIB from PBCH, and can set control region (Control Resource Set; CORESET) #0 (which may correspond to a control region with a control region index of 0) therefrom. The terminal can monitor control region #0, assuming that the selected SS / PBCH block and the DMRS (Demodulation Reference Signal) transmitted in control region #0 are QCL (Quasi Co Location). The terminal can receive system information through downlink control information transmitted in control region #0. The terminal can obtain RACH (Random Access Channel) related configuration information required for initial access from the received system information. The terminal can transmit PRACH (Physical RACH) to the base station considering the selected SS / PBCH index, and the base station receiving the PRACH can obtain information on the SS / PBCH block index selected by the terminal. The base station can know that the terminal has selected a block among each SS / PBCH block and monitors the control region #0 associated with it.

[0095] [PDCCH: DCI related]

[0096] Next, we will specifically explain downlink control information (DCI) in the 5G system.

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

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

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

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

[0101] [Table 4]

[0102]

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

[0104] [Table 5]

[0105]

[0106]

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

[0108] [Table 6]

[0109]

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

[0111] [Table 7]

[0112]

[0113]

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

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

[0116] FIG. 4 is a diagram illustrating an example of setting a control region of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure. FIG. 4 illustrates an example of a control region (Control Resource Set, CORESET) in which a downlink control channel is transmitted in a 5G wireless communication system. FIG. 4 illustrates an example in which two control regions (Control Region #1 (401), Control Region #2 (402)) are set within a UE bandwidth part (410) in the frequency axis and one slot (420) in the time axis. The control regions (401, 402) may be set to specific frequency resources (403) within the entire UE bandwidth part (410) in the frequency axis. The control regions (401, 402) may be set to one or more OFDM symbols in the time axis, and this may be defined as a control region length (Control Resource Set Duration, 404). Referring to the illustrated example of FIG. 4, control area #1 (401) is set to a control area length of 2 symbols, and control area #2 (402) is set to a control area length of 1 symbol.

[0117] In the aforementioned 5G system, the control region can be established by the base station to the terminal through higher-layer signaling (e.g., system information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). The base station establishing a control region for the terminal means that the base station provides the terminal with information such as the control region identifier (Identity), the frequency location of the control region, and the symbol length of the control region. For example, this information may include the information in Table 8.

[0118] [Table 8]

[0119]

[0120]

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

[0122] FIG. 5 is a diagram illustrating the structure of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0123] Fig. 5 shows an example of a basic unit of time and frequency resources that constitute a downlink control channel that can be used in a 5G system. According to Fig. 5, the basic unit of time and frequency resources that constitute a control channel can be referred to as a REG (Resource Element Group, 503), and a REG (503) can be defined as 1 OFDM symbol (501) on the time axis and 1 PRB (Physical Resource Block, 502) on the frequency axis, i.e., 12 subcarriers. A base station can concatenate REGs (503) to constitute a downlink control channel allocation unit.

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

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

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

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

[0128] [Table 9]

[0129]

[0130]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0153] The aforementioned specified DCI formats may follow definitions such as the examples in Table 10.

[0154] [Table 10]

[0155]

[0156] In a 5G system, the search space of aggregation level L in a control region p and a search space set s can be expressed as in the following mathematical expression 1.

[0157] [Mathematical Formula 1]

[0158]

[0159]

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

[0161] [PDCCH: BD / CCE limit]

[0162] When multiple search space sets are set for a terminal, the following conditions may be considered in determining the search space set that the terminal should monitor.

[0163] If the value of monitoringCapabilityConfig-r16, which is an upper layer signaling, is set to r15monitoringcapability, the terminal defines the maximum values ​​for the number of PDCCH candidates that can be monitored and the number of CCEs that constitute the entire search space (wherein the entire search space means the entire set of CCEs corresponding to the union area of ​​multiple search space sets) per slot, and if the value of monitoringCapabilityConfig-r16 is set to r16monitoringcapability, the terminal defines the maximum values ​​for the number of PDCCH candidates that can be monitored and the number of CCEs that constitute the entire search space (wherein the entire search space means the entire set of CCEs corresponding to the union area of ​​multiple search space sets) per Span.

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

[0165] As described above, depending on the setting value of the upper layer signaling, the maximum number of PDCCH candidates that the terminal can monitor is M. μ is a subcarrier spacing of 15·2 μ When defined by slot in a cell set to kHz, Table 11 below can be followed, and when defined by span, Table 12 below can be followed.

[0166] [Table 11]

[0167]

[0168] [Table 12]

[0169]

[0170] [Condition 2: Maximum CCE limit]

[0171] As above, according to the setting value of the upper layer signaling, the maximum number of CCEs that constitute the entire search space (here, the entire search space means the entire set of CCEs corresponding to the union area of ​​multiple search space sets) is C μ is a subcarrier spacing of 15·2 μ When defined by slot in a cell set to kHz, Table 13 below may be followed, and when defined by span, Table 14 below may be followed.

[0172] [Table 13]

[0173]

[0174] [Table 14]

[0175]

[0176] For convenience of explanation, let us define a situation where both conditions 1 and 2 are satisfied at a certain point in time as “condition A.” Therefore, not satisfying condition A may mean not satisfying at least one of conditions 1 and 2.

[0177] [PDCCH: Overbooking]

[0178] Depending on the configuration of the search space sets of the base station, there may be cases where condition A is not satisfied at a certain point in time. If condition A is not satisfied at a certain point in time, the terminal can select and monitor only some of the search space sets configured to satisfy condition A at that point in time, and the base station can transmit a PDCCH to the selected search space set.

[0179] The following method can be followed to select a partial search space from the entire set of search spaces.

[0180] If condition A for PDCCH is not satisfied at a specific point in time (slot), the terminal (or base station) may preferentially select a search space set whose search space type is set to a common search space from among the search space sets existing at that point in time over a search space set whose search space type is set to a terminal-specific search space.

[0181] If all search space sets set as common search spaces are selected (i.e., if condition A is satisfied even after selecting all search spaces set as common search spaces), the terminal (or base station) can select search space sets set as terminal-specific search spaces. At this time, if there are multiple search space sets set as terminal-specific search spaces, a search space set with a lower search space set index may have a higher priority. The terminal (or base station) can select terminal-specific search space sets within the range where condition A is satisfied, taking the priority into consideration.

[0182] [Rate matching / Puncturing related]

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

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

[0185] Rate Matching Operation

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

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

[0188] Puncture action

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

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

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

[0192] FIG. 6 is a diagram for explaining a method for a base station and a terminal to transmit and receive data by taking into account downlink data channels and rate matching resources according to one embodiment of the present disclosure.

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

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

[0195] 5G systems support "symbol level" and "level" granularity by setting the aforementioned rate matching resources on terminals. More specifically, the following configuration methods can be followed.

[0196] RB symbol level

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

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

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

[0200] RE level

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

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

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

[0204] [Regarding LTE CRS rate match]

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

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

[0207] Table 15 shows a ServingCellConfig IE that includes the above CRS pattern, and Table 16 shows a RateMatchPatternLTE-CRS IE that includes at least one parameter for the CRS pattern.

[0208] [Table 15]

[0209]

[0210]

[0211]

[0212] [Table 16]

[0213]

[0214] [PDSCH: Frequency Resource Allocation Related]

[0215] FIG. 7 is a diagram illustrating an example of frequency-axis resource allocation of PDSCH in a wireless communication system according to an embodiment of the present disclosure.

[0216] FIG. 7 is a diagram illustrating three frequency axis resource allocation methods, type 0 (700), type 1 (705), and dynamic switch (710), which can be set through an upper layer in an NR wireless communication system.

[0217] Referring to Fig. 7, if a terminal is set to use only resource type 0 through upper layer signaling (700), some downlink control information (DCI) that allocates PDSCH to the terminal includes a bitmap composed of NRBG bits. The conditions for this will be explained later. At this time, NRBG means the number of RBGs (resource block groups) determined according to the BWP size allocated by the BWP indicator and the upper layer parameter rbg-Size as shown in [Table 17] below, and data is transmitted to the RBG indicated as 1 by the bitmap.

[0218] [Table 17]

[0219]

[0220] If the terminal is configured to use only resource type 1 through upper layer signaling (705), some DCIs that allocate PDSCH to the terminal It includes frequency axis resource allocation information consisting of bits. The conditions for this will be explained later. Through this, the base station can set the starting VRB (720) and the length (725) of frequency axis resources allocated continuously therefrom.

[0221] If a terminal is configured to use both resource type 0 and resource type 1 through upper layer signaling (710), some DCIs that allocate PDSCH to the terminal include frequency-axis resource allocation information composed of bits of a larger value (735) among the payload (715) for configuring resource type 0 and the payload (720, 725) for configuring resource type 1. Conditions for this will be explained later. At this time, one bit may be added to the first part (MSB) of the frequency-axis resource allocation information in the DCI, and if the bit has a value of '0', it may indicate that resource type 0 is used, and if the bit has a value of '1', it may indicate that resource type 1 is used.

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

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

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

[0225] [Table 18]

[0226]

[0227] [Table 19]

[0228]

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

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

[0231] Referring to FIG. 8, the base station uses the upper layer to set the subcarrier spacing (SCS) (μ) of the data channel and the control channel. PDSCH , μ PDCCH ), scheduling offset (K0) value, and the time axis position of the PDSCH resource can be indicated according to the OFDM symbol start position (800) and length (805) within a slot dynamically indicated through DCI.

[0232] FIG. 9 is a diagram illustrating an example of time-domain resource allocation according to subcarrier spacing of a data channel and a control channel in a wireless communication system according to one embodiment of the present disclosure.

[0233] Referring to Fig. 9, when the subcarrier spacing of the data channel and the control channel is the same (900, μ PDSCH = μ PDCCH), since the slot numbers for data and control are the same, the base station and the terminal can generate a scheduling offset according to the predetermined slot offset K0. On the other hand, if the subcarrier spacing of the data channel and the control channel are different (905, μ PDSCH ≠ μ PDCCH ), since the slot numbers for data and control are different, the base station and the terminal can generate a scheduling offset according to a predetermined slot offset K0 based on the subcarrier interval of the PDCCH.

[0234] [PUSCH: Transmission Method Related]

[0235] Next, we describe the scheduling method for PUSCH transmission. PUSCH transmission can be dynamically scheduled by the UL grant within the DCI or can operate by configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transmission are possible in DCI format 0_0 or 0_1.

[0236] Configured grant Type 1 PUSCH transmission can be semi-statically configured by receiving configuredGrantConfig including rrc-ConfiguredUplinkGrant of [Table 20] through higher-order signaling, without receiving UL grant in DCI. Configured grant Type 2 PUSCH transmission can be semi-persistently scheduled by UL grant in DCI after receiving configuredGrantConfig not including rrc-ConfiguredUplinkGrant of [Table 20] through higher-order signaling. When PUSCH transmission operates by configured grant, parameters applied to PUSCH transmission are applied through configuredGrantConfig of higher-order signaling of [Table 20], except for dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH provided by pusch-Config of [Table 21]. If the terminal has been provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of [Table 20], the terminal applies tp-pi2BPSK in pusch-Config of [Table 21] to PUSCH transmission operated by the configured grant.

[0237] [Table 20]

[0238]

[0239]

[0240] Next, the PUSCH transmission method is described. The DMRS antenna port for PUSCH transmission is the same as the antenna port for SRS transmission. PUSCH transmission can follow a codebook-based or non-codebook-based transmission method, respectively, depending on whether the value of txConfig in the upper signaling, pusch-Config in [Table 21], is 'codebook' or 'nonCodebook'.

[0241] As described above, PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can be semi-statically configured by configured grant. If the UE is instructed to schedule PUSCH transmission via DCI format 0_0, the UE performs beam configuration for PUSCH transmission using pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource corresponding to the minimum ID within the activated uplink BWP within the serving cell, and the PUSCH transmission is based on a single antenna port. The UE does not expect scheduling for PUSCH transmission via DCI format 0_0 within a BWP where a PUCCH resource including pucch-spatialRelationInfo is not configured. If the UE does not configure txConfig in pusch-Config of [Table 21], the UE does not expect to be scheduled with DCI format 0_1.

[0242] [Table 21]

[0243]

[0244] Next, we describe codebook-based PUSCH transmission. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, or can operate semi-statically based on a configured grant. When codebook-based PUSCH is dynamically scheduled via DCI format 0_1 ​​or semi-statically configured via a configured grant, the UE determines a precoder for PUSCH transmission based on the SRS Resource Indicator (SRI), Transmission Precoding Matrix Indicator (TPMI), and transmission rank (the number of PUSCH transmission layers).

[0245] At this time, the SRI can be given through the SRS resource indicator field in the DCI or configured through the srs-ResourceIndicator higher-level signaling. The UE is configured with at least one SRS resource when transmitting a codebook-based PUSCH, and can be configured with up to two. When the UE receives an SRI through the DCI, the SRS resource indicated by the SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH containing the SRI. In addition, the TPMI and transmission rank can be given through the precoding information and number of layers fields in the DCI or configured through the precodingAndNumberOfLayers higher-level signaling. The TPMI is used to indicate the precoder applied to the PUSCH transmission. If the UE is configured with one SRS resource, the TPMI is used to indicate the precoder to be applied to the configured one SRS resource. When a terminal is configured with multiple SRS resources, TPMI is used to indicate the precoder to be applied in the SRS resource indicated through SRI.

[0246] The precoder to be used for PUSCH transmission is selected from an uplink codebook having the same number of antenna ports as the nrofSRS-Ports value in the upper layer signaling, SRS-Config. In codebook-based PUSCH transmission, the UE determines the codebook subset based on the TPMI and codebookSubset in the upper layer signaling, pusch-Config. The codebookSubset in the upper layer signaling, pusch-Config, can be set to one of 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', or 'nonCoherent' based on the UE capability reported by the UE to the base station. If the UE reported 'partialAndNonCoherent' as the UE capability, the UE does not expect the value of codebookSubset in the upper layer signaling to be set to 'fullyAndPartialAndNonCoherent'. Additionally, if the UE reports 'nonCoherent' as the UE capability, the UE does not expect the value of the upper signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent'. If nrofSRS-Ports in the upper signaling SRS-ResourceSet points to two SRS antenna ports, the UE does not expect the value of the upper signaling codebookSubset to be set to 'partialAndNonCoherent'.

[0247] The terminal can be configured with one SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'codebook', and one SRS resource in the SRS resource set can be indicated via SRI. If multiple SRS resources are configured in the SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'codebook', the terminal expects that the value of nrofSRS-Ports in the upper signaling SRS-Resource is set to the same value for all SRS resources.

[0248] The terminal transmits to the base station one or more SRS resources included in the SRS resource set in which the usage value is set to 'codebook' according to upper signaling, and the base station selects one of the SRS resources transmitted by the terminal and instructs the terminal to perform PUSCH transmission using transmission beam information of the corresponding SRS resource. At this time, in codebook-based PUSCH transmission, the SRI is used as information for selecting an index of one SRS resource and is included in the DCI. Additionally, the base station includes in the DCI information indicating the TPMI and rank to be used by the terminal for PUSCH transmission. The terminal performs PUSCH transmission by applying the indicated rank and the precoder indicated by the TPMI based on the transmission beam of the corresponding SRS resource using the SRS resource indicated by the SRI.

[0249] Next, we describe non-codebook-based PUSCH transmission. Non-codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can operate semi-statically based on a configured grant. If at least one SRS resource is configured within an SRS resource set in which the usage value in the upper signaling, SRS-ResourceSet, is set to 'nonCodebook', the UE can be scheduled for non-codebook-based PUSCH transmission via DCI format 0_1.

[0250] For an SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'nonCodebook', the UE can be configured with one connected NZP CSI-RS resource (non-zero power CSI-RS). The UE can perform calculations for a precoder for SRS transmission by measuring the NZP CSI-RS resource connected to the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of the aperiodic SRS transmission at the UE is less than 42 symbols, the UE does not expect information about the precoder for SRS transmission to be updated.

[0251] If the value of resourceType in the upper signaling SRS-ResourceSet is set to 'aperiodic', the connected NZP CSI-RS is indicated by the SRS request field in DCI format 0_1 ​​or 1_1. At this time, if the connected NZP CSI-RS resource is an aperiodic NZP CSI-RS resource, the presence of the connected NZP CSI-RS is indicated when the value of the SRS request field in DCI format 0_1 ​​or 1_1 is not '00'. At this time, the DCI must not indicate cross-carrier or cross BWP scheduling. In addition, if the value of the SRS request indicates the presence of an NZP CSI-RS, the NZP CSI-RS is located in the slot in which the PDCCH including the SRS request field is transmitted. At this time, the TCI states set for the scheduled subcarriers are not set to QCL-TypeD.

[0252] If a periodic or semi-persistent SRS resource set is configured, the associated NZP CSI-RS can be indicated through the associatedCSI-RS in the upper-level signaling SRS-ResourceSet. For non-codebook-based transmission, the UE does not expect the upper-level signaling spatialRelationInfo for the SRS resource and the associatedCSI-RS in the upper-level signaling SRS-ResourceSet to be configured together.

[0253] When multiple SRS resources are configured, the UE can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. At this time, the SRI can be indicated through the SRS resource indicator field in the DCI or can be set through the srs-ResourceIndicator, which is a higher-level signaling. Similar to the codebook-based PUSCH transmission described above, when the UE receives an SRI through the DCI, the SRS resource indicated by the SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH containing the SRI. The UE can use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be simultaneously transmitted in the same symbol within one SRS resource set and the maximum number of SRS resources are determined by the UE capability reported by the UE to the base station. At this time, the SRS resources that the UE simultaneously transmits occupy the same RB. The UE configures one SRS port for each SRS resource. Only one SRS resource set with the usage value set to 'nonCodebook' in the upper signaling SRS-ResourceSet can be set, and up to four SRS resources for non-codebook based PUSCH transmission can be set.

[0254] The base station transmits one NZP-CSI-RS associated with an SRS resource set to the terminal, and the terminal calculates a precoder to be used when transmitting one or more SRS resources within the SRS resource set based on the result measured upon reception of the NZP-CSI-RS. When the terminal transmits one or more SRS resources within the SRS resource set with usage set to 'nonCodebook' to the base station, the terminal applies the calculated precoder, and the base station selects one or more SRS resources from the received one or more SRS resources. At this time, in non-codebook based PUSCH transmission, the SRI represents an index that can express a combination of one or more SRS resources, and the SRI is included in the DCI. At this time, the number of SRS resources indicated by the SRI transmitted by the base station can be the number of transmission layers of the PUSCH, and the terminal transmits the PUSCH by applying the precoder applied to SRS resource transmission to each layer.

[0255] [PUSCH: Preparation time]

[0256] Next, the PUSCH preparation procedure time is described. When the base station schedules a UE to transmit a PUSCH using DCI format 0_0, 0_1, or 0_2, the UE may require a PUSCH preparation procedure time to transmit the PUSCH by applying the transmission method indicated through the DCI (transmission precoding method of SRS resources, number of transmission layers, spatial domain transmission filter). NR takes this into account and defines the PUSCH preparation procedure time. The PUSCH preparation procedure time of the UE can follow the following [Mathematical Formula 2].

[0257] [Equation 2]

[0258]

[0259] T as described in mathematical formula 2 proc,2 In , each variable can have the following meanings:

[0260] - N2: The number of symbols determined by the UE processing capability (UE processing capability) 1 or 2 and the numerology μ according to the UE capability. If UE processing capability 1 is reported according to the UE capability report, it has the value of [Table 22]. If UE processing capability 2 is reported and the availability of UE processing capability 2 is set through upper layer signaling, it can have the value of [Table 23].

[0261] [Table 22]

[0262]

[0263] [Table 23]

[0264]

[0265] - d 2,1: The number of symbols set to 0 if all resource elements of the first OFDM symbol of PUSCH transmission are configured to consist of only DM-RS, and 1 otherwise.

[0266] - κ: 64

[0267] - μ: μ DL or μ UL Medium, T proc,2 This follows the larger value μ DL refers to the numerology of the downlink in which the PDCCH containing the DCI scheduling the PUSCH is transmitted, and μ UL It refers to the numerology of the uplink in which PUSCH is transmitted.

[0268] - T c : 1 / (Δ max *N f ), Δ max = 480*10 3 Hz, N f =has 4096.

[0269] - d 2,2 : If the DCI scheduling the PUSCH indicates BWP switching, it follows the BWP switching time, otherwise it has 0.

[0270] - d2: When the OFDM symbols of a PUCCH with a high priority index and a PUCCH with a low priority index overlap in time, the d2 value of the PUSCH with the high priority index is used. Otherwise, d2 is 0.

[0271] - T ext : If the terminal uses a shared spectrum channel access method, the terminal is T ext can be calculated and applied to the PUSCH preparation process time. Otherwise, T ext is assumed to be 0.

[0272] - T switch : T when the uplink switching interval is triggeredswitch is assumed to be the switching interval time. Otherwise, it is assumed to be 0.

[0273] When the base station and the terminal consider the time domain resource mapping information of the PUSCH scheduled through DCI and the influence of the timing advance between uplink and downlink, the base station and the terminal determine T from the last symbol of the PDCCH including the DCI that scheduled the PUSCH. proc,2 If the first symbol of the PUSCH begins before the first uplink symbol of the CP, the PUSCH preparation time is determined to be insufficient. Otherwise, the base station and the UE determine that the PUSCH preparation time is sufficient. The UE transmits the PUSCH only when the PUSCH preparation time is sufficient, and may ignore the DCI scheduling the PUSCH if the PUSCH preparation time is insufficient.

[0274] [CA / DC related]

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

[0276] Referring to FIG. 10, the wireless protocol of the next-generation mobile communication system is composed of NR SDAP (Service Data Adaptation Protocol 1025, 1070), NR PDCP (Packet Data Convergence Protocol 1030, 1065), NR RLC (Radio Link Control 1035, 1060), and NR MAC (Medium Access Control 1040, 1055) in the terminal and NR base station, respectively.

[0277] The main functions of NR SDAP (1025, 1070) may include some of the following functions:

[0278] - Transfer of user plane data

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

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

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

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

[0283] The main functions of NR PDCP (1030, 1065) may include some of the following functions:

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

[0285] - User data transfer function

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

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

[0288] - PDCP PDU reordering for reception

[0289] - Duplicate detection of lower layer SDUs

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

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

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

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

[0294] The main functions of NR RLC (1035, 1060) may include some of the following functions:

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

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

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

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

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

[0300] - Re-segmentation of RLC data PDUs

[0301] - Reordering of RLC data PDUs

[0302] - Duplicate detection function

[0303] - Protocol error detection

[0304] - RLC SDU discard function

[0305] - RLC re-establishment function

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

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

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

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

[0310] - Multiplexing / demultiplexing of MAC SDUs

[0311] - Scheduling information reporting function

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

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

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

[0315] - MBMS service identification function

[0316] - Transport format selection function

[0317] - Padding function

[0318] The NR PHY layer (1045, 1050) can perform operations of channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it through a wireless channel, or demodulating and channel decoding OFDM symbols received through a wireless channel and transmitting them to a higher layer.

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

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

[0321] In the present disclosure, determining the priority between A and B may be referred to in various ways, such as selecting a higher priority according to a predetermined priority rule and performing an action corresponding to it, or omitting or dropping an action for a lower priority.

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

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

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

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

[0326] - MIB (Master Information Block)

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

[0328] - RRC (Radio Resource Control)

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

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

[0331] - PDCCH (Physical Downlink Control Channel)

[0332] - DCI (Downlink Control Information)

[0333] - UE-specific DCI

[0334] - Group common DCI

[0335] - Common DCI

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

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

[0338] - PUCCH (Physical Uplink Control Channel)

[0339] - UCI (Uplink Control Information)

[0340] In the present disclosure, determining the priority between A and B may be referred to in various ways, such as selecting a higher priority according to a predetermined priority rule and performing an action corresponding to it, or omitting or dropping an action for a lower priority.

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

[0342] The service covered by this disclosure may be an XR (eXtended Reality) service. The size of an XR service packet may vary depending on the time point. For example, an XR packet at one time point may contain voice-related information. An XR packet at another time point may contain video-related information. The video information may be larger in size than the voice information.

[0343] The timing of XR service packets' transmission to the physical layer may be aperiodic. For example, XR service packets may be generated at a specific interval in a higher layer and transmitted to the physical layer. Delays may occur at the physical layer due to signal processing. Therefore, the timing of actual transmission to the physical layer may be aperiodic. This aperiodicity may be referred to as jitter.

[0344] Figure 11 is a drawing illustrating a problem to be addressed in this disclosure.

[0345] Referring to Fig. 11, packets (e.g., packets of an XR service) can be generated in a higher layer at a specific period (16.67 ms). In the physical layer, the actual transmission time may vary due to jitter. To this end, the terminal may be configured with an SPS PDSCH or a CG PUSCH from the base station. Here, the SPS PDSCH may be a PDSCH that is periodically received, and the CG PUSCH may be a PUSCH that is periodically transmitted. The base station may transmit a packet to the terminal using the SPS PDSCH, taking into account the packet arrival time and jitter. Alternatively, the terminal may transmit a packet to the base station using the CG PUSCH, taking into account the packet arrival time and jitter.

[0346] Referring to FIG. 11, an SPS PDSCH configured for a terminal may have a set period. The terminal may receive an SPS PDSCH in a slot corresponding to the period. In the following description, a slot for receiving an SPS PDSCH according to the SPS PDSCH period may be referred to as an SPS reception slot. For example, referring to FIG. 11, when the period of an SPS PDSCH is P (slot unit), the SPS reception slots may be slot n, slot n+P, slot n+2*P,… (generally, slot n+M*P, where M is a non-negative integer). Here, slot n may be the first SPS reception slot. Slot n may be a slot indicated in an SPS activation DCI.

[0347] Referring to FIG. 11, an SPS PDSCH reception opportunity (SPS occasion) may be set within an SPS reception slot, in which reception of an SPS PDSCH is attempted. An SPS occasion may include time-frequency resources and a reception method determined according to a set of SPS PDSCH scheduling parameters included in the SPS configuration. For example, in FIG. 11, the SPS reception slots may be slot n, slot n+P, and slot n+2*P. The terminal may determine an SPS occasion (1101) in slot n, an SPS occasion (1111) in slot n+P, and an SPS occasion (1121) in slot n+2*P according to the set of SPS PDSCH scheduling parameters.

[0348] For reference, in FIG. 11, the terminal is configured with one SPS PDSCH reception opportunity (SPS occasion) in the SPS reception slot. This is an example. For example, the terminal may be configured with multiple SPS reception opportunities (SPS occasions) in a time unit (e.g., slot) corresponding to a cycle. When multiple SPS reception opportunities (SPS occasions) are configured, each SPS occasion may be located in a different symbol. For example, SPS occasion 0 may be received in the first symbol set, and SPS occasion 1 may be received in the second symbol set. Here, the first symbol set and the second symbol set may not overlap with each other on the time axis.

[0349] SPS occasions corresponding to one SPS configuration may assume the same Modulation and Coding Scheme (MCS), the same Frequency Domain Resource Assignment (FDRA), and the same Time Domain Resource Assignment (TDRA). More specifically, the SPS configuration may include a period for receiving an SPS PDSCH, one MCS, one FDRA, or one TDRA. The UE may determine an SPS occasion in an SPS reception slot corresponding to the period, and may receive an SPS PDSCH in the SPS occasion. Here, the reception of the SPS PDSCH received in each SPS occasion may be determined according to the one MCS, one FDRA, and one TDRA. In the present disclosure, the MCS, the FDRA, and the TDRA may be referred to as a set of SPS PDSCH scheduling parameters. This is an embodiment of the present disclosure, and the SPS PDSCH scheduling parameter set may include reception beam related information (Transmission configuration indication), Quasi-co-located (QCL) information, MIMO related information (Antenna port information, DMRS information), etc.

[0350] Referring to FIG. 11, the SPS PDSCH set in the terminal can be assigned a unique HARQ process number (HPN). More specifically, the HARQ process number can be determined using mathematical expression 3.

[0351] [Equation 3]

[0352] HARQ Process ID = [floor (CURRENT_slot × 10 / (numberOfSlotsPerFrame × periodicity))] modulo nrofHARQ-Processes + harq-ProcID-Offset

[0353] Here, CURRENT_slot = [(SFN × numberOfSlotsPerFrame) + slot number in the frame], where numberOfSlotsPerFrame is the number of slots in the frame. If harq-ProcID-Offset is not set, harq-ProcID-Offset=0 can be assumed.

[0354] For convenience, the following description in this disclosure is based on the SPS PDSCH. However, the embodiments of the present disclosure can be equally applied to the CG PUSCH. When applying the embodiments of the present disclosure to the CG PUSCH, the SPS PDSCH scheduling parameter set can be replaced with the CG PUSCH scheduling parameter set, and the CG PUSCH scheduling parameter set can include the MCS, FDRA, or TDRA of the CG PUSCH. In addition, the CG PUSCH scheduling parameter set can include transmission beam-related information (Transmission configuration indication), Quasi-co-located (QCL) information, or MIMO-related information (Antenna port information, DMRS information).

[0355] Referring to FIG. 11, a first packet (1100) may be received at an SPS occasion (1101) corresponding to slot n, a second packet (1110) may be received at an SPS occasion (1111), and a third packet (1120) may be received at an SPS occasion (1121). The first packet (1100), the second packet (1110), and the third packet (1120) to be transmitted by the base station may have different lengths. For example, the length of the third packet (1120) may be relatively longer compared to the lengths of the first packet (1100) and the second packet (1110). Accordingly, the first packet (1100) to the second packet (1110) may be transmitted in the SPS occasion (1101) of slot n to the SPS occasion (1111) of slot n+P, but the third packet (1120) may not be transmitted in the SPS occasion (1120) of slot n+2*P.

[0356] The problem addressed in the present disclosure is a method for transmitting an SPS PDSCH when the size of a specific packet (e.g., the third packet (1120)) is relatively larger than that of other packets. According to the prior art, multiple SPS PDSCHs within a period may always have the same MCS, the same FDRA, and the same TDRA. Therefore, multiple SPS PDSCHs may always have the same TB (transport block) length. Here, the TB length may be determined based on the MCS, the number of RBs allocated to the FDRA, and the number of OFDM symbols allocated to the TDRA. The TB length may increase in proportion to the spectral efficiency corresponding to the MCS, the number of RBs, or the number of OFDM symbols.

[0357] To transmit larger packets, the terminal must use an MCS corresponding to higher spectral efficiency, use an FDRA containing a larger number of RBs to secure more resources, or use a TDRA containing a larger number of OFDM symbols.

[0358] [Example 1: SPS PDSCH reception using multiple SPS PDSCH scheduling parameters]

[0359] FIG. 12 is a diagram for receiving a PDSCH based on a plurality of SPS PDSCH scheduling parameter sets according to one embodiment of the present disclosure.

[0360] According to one embodiment of the present disclosure, a terminal may receive an SPS configuration from a base station. The SPS configuration may include a plurality of SPS PDSCH scheduling parameter sets. Here, the SPS PDSCH scheduling parameter sets may include at least one of MCS, FDRA, and TDRA. For example, a first SPS PDSCH scheduling parameter set may include {a first MCS value, a first FDRA value, a first TDRA value}, and a second SPS PDSCH scheduling parameter set may include {a second MCS value, a second FDRA value, a second TDRA value}.

[0361] Here, the first MCS value and the second MCS value may be different. Alternatively, the first FDRA value and the second FDRA value may be different. Alternatively, the first TDRA value and the second TDRA value may be different.

[0362] Here, the first FDRA value and the second FDRA value may be related to each other. For example, RBs scheduled with the first FDRA value may be included in RBs scheduled with the second FDRA value. That is, the number of RBs corresponding to the second FDRA value may be greater than the number of RBs corresponding to the first FDRA value.

[0363] Here, the first TDRA value and the second TDRA value may be associated with each other. For example, OFDM symbols scheduled with the first TDRA value may be included in OFDM symbols scheduled with the second TDRA value. That is, the number of OFDM symbols corresponding to the second TDRA value may be greater than the number of OFDM symbols corresponding to the first TDRA value.

[0364] Referring to Fig. 12, the terminal can set the period of the slot in which the SPS PDSCH should be received through the SPS setting. For example, when the period is P (period in slot units), the slot for receiving the SPS PDSCH can be slot n+M*P. Here, M can be 0, 1, 2,…. Here, n can be the slot in which the first SPS PDSCH is scheduled. The terminal can receive the SPS PDSCH based on a plurality of SPS PDSCH scheduling parameter sets within the slot.

[0365] A method for receiving an SPS PDSCH based on multiple sets of SPS PDSCH scheduling parameters is as follows.

[0366] When the SPS configuration received by the terminal includes a plurality of SPS PDSCH scheduling parameter sets, the terminal can determine an SPS reception opportunity based on the parameter sets of the plurality of SPS PDSCH schedules. For example, when the SPS configuration received by the terminal includes a first SPS PDSCH scheduling parameter set and a second SPS PDSCH scheduling parameter set, the terminal can determine a first SPS reception opportunity (SPS occasion 0, 1201, 1211, 1221) corresponding to the first SPS PDSCH scheduling parameter set and a second SPS reception opportunity (SPS occasion 1, 1202, 1212, 1222) corresponding to the second SPS PDSCH scheduling parameter set. The terminal can receive the SPS PDSCH through the first SPS reception opportunity to the second SPS reception opportunity. Here, receiving an SPS PDSCH based on the i-th SPS PDSCH scheduling parameter set can be referred to as receiving a PDSCH at the i-th SPS occasion.

[0367] For example, a terminal may receive an SPS PDSCH based on a first SPS PDSCH scheduling parameter set. The first SPS PDSCH scheduling parameter set may include a first MCS value, a first FDRA value, and a first TDRA value. The MCS value of the SPS PDSCH received by the terminal may be determined to be the first MCS value, and RBs and OFDM symbols occupied by the SPS PDSCH may be determined from the first FDRA value and the first TDRA value, respectively. In addition, the length of a TB transmitted by the SPS PDSCH may be a value determined based on the first MCS value, the first FDRA value, and the first TDRA value. The terminal may attempt to receive the SPS PDSCH based on the determined value. The terminal may confirm whether reception of the SPS PDSCH is successful through a CRC attached to the TB. If the CRC is verified correctly, the terminal can determine that it has successfully received the SPS PDSCH corresponding to the first SPS PDSCH scheduling parameter set.

[0368] For example, the terminal can receive the SPS PDSCH based on a second SPS PDSCH scheduling parameter set. The second SPS PDSCH scheduling parameter set can include a second MCS value, a second FDRA value, and a second TDRA value. The MCS value of the SPS PDSCH received by the terminal is determined to be the second MCS value, and the RBs and OFDM symbols occupied by the SPS PDSCH can be determined from the second FDRA value and the second TDRA value, respectively. In addition, the length of the TB transmitted by the SPS PDSCH can be a value determined based on the second MCS value, the second FDRA value, and the second TDRA value. The terminal can attempt to receive the SPS PDSCH based on the determined value. The terminal can confirm whether the reception of the SPS PDSCH is successful through a CRC attached to the TB. If the CRC is verified correctly, the terminal can determine that it has successfully received the SPS PDSCH corresponding to the second SPS PDSCH scheduling parameter set.

[0369] When a terminal receives an SPS PDSCH based on multiple SPS PDSCH scheduling parameter sets in one slot, the terminal can expect to correctly receive only an SPS PDSCH corresponding to one SPS PDSCH scheduling parameter set. That is, if the terminal successfully receives an SPS PDSCH based on a first SPS PDSCH scheduling parameter set, the terminal can expect not to successfully receive an SPS PDSCH based on a second SPS PDSCH scheduling parameter set. If the terminal successfully receives an SPS PDSCH based on the first SPS PDSCH scheduling parameter set and simultaneously successfully receives a second SPS PDSCH based on the second SPS PDSCH scheduling parameter set, the terminal can determine this as an error case. That is, the terminal can determine that it did not correctly receive an SPS PDSCH for the SPS PDSCH opportunity. That is, NACK can be generated with HARQ-ACK information corresponding to the above SPS PDSCH opportunity.

[0370] In one embodiment of the present disclosure, a terminal may determine a single HARQ process number for multiple SPS opportunities in a single slot. In other words, the same HPN may be determined for SPS opportunities corresponding to multiple SPS PDSCH scheduling parameter sets in a single slot. For example, in FIG. 12 , the same HPN may be determined for SPS occasion 0 (1201) and SPS occasion 1 (1202) corresponding to slot n. In FIG. 12 , HPN0 may be determined for SPS occasion 0 (1201) and SPS occasion 1 (1202) corresponding to slot n. The terminal may correctly receive an SPS PDSCH through one of the two SPS occasions 0 and 1 (through one SPS PDSCH scheduling parameter set), and the HARQ-ACK of the SPS PDSCH may correspond to HPN0.

[0371] FIG. 13 is a drawing illustrating an embodiment of the present disclosure.

[0372] Referring to FIG. 13, the lengths of the first packet (1300) and the second packet (1310) transmitted by the base station to the terminal may be short, and the length of the third packet (1320) may be long. The base station may transmit the first packet (1300) to the terminal as SPS occasion 0 (1301) determined by the first SPS PDSCH scheduling parameter set. The base station may transmit the second packet (1310) to the terminal as SPS occasion 0 (1311) determined by the first SPS PDSCH scheduling parameter set. The base station may transmit the third packet (1320) to the terminal as SPS occasion 1 (1322) determined by the second SPS PDSCH scheduling parameter set.

[0373] The terminal may attempt to receive the SPS PDSCH in slot n, slot n+P, and slot n+2*P. In each slot, the terminal may attempt to receive the SPS PDSCH in SPS occasion 0 determined by the first SPS PDSCH scheduling parameter set, and may attempt to receive the SPS PDSCH in SPS occasion 1 determined by the second SPS PDSCH scheduling parameter set. The terminal may succeed in receiving the SPS PDSCH in either SPS occasion 0 or SPS occasion 1. For example, the terminal may correctly receive the SPS PDSCH in SPS occasion 0 (1301) in slot n, SPS occasion 0 (1311) in slot n+P, and SPS occasion 1 (1322) in slot n+2*P. The HARQ-ACK of SPS occasion 0 (1301) correctly received by the terminal in slot n can correspond to HPN0, the HARQ-ACK of SPS occasion 0 (1311) correctly received in slot n+P can correspond to HPN1, and the HARQ-ACK of SPS occasion 1 (1322) correctly received in slot n+2*P can correspond to HPN2.

[0374] Figure 14 is a flowchart according to one embodiment of the present disclosure.

[0375] Step 1 (1400): The terminal may receive an SPS PDSCH configuration from the base station. The SPS PDSCH configuration may include a period (P, in slot units) for determining an SPS reception slot and a plurality of SPS PDSCH scheduling parameter sets for determining SPS occasions within the SPS reception slot. Here, the SPS PDSCH scheduling parameter set may include at least one of MCS, FDRA, and TDRA.

[0376] Step 2 (1410): The terminal may receive a DCI activating an SPS configuration including multiple sets of SPS PDSCH scheduling parameters. The terminal may be instructed on the first SPS reception slot from the DCI. If the first SPS reception slot is slot n, the terminal may determine slot n + M * P as the SPS reception slot, where M may be a non-negative integer.

[0377] Step 3 (1420): The terminal can receive an SPS PDSCH based on multiple sets of SPS PDSCH scheduling parameters in an SPS reception slot. For example, if two sets of SPS PDSCH scheduling parameters are configured in Step 1 (1400), the terminal can attempt to receive an SPS PDSCH using the first set of SPS PDSCH scheduling parameters, and the terminal can attempt to receive an SPS PDSCH using the second set of SPS PDSCH scheduling parameters.

[0378] Step 4 (1430): The terminal attempts to receive the SPS PDSCH with the first SPS PDSCH scheduling parameter set, and if correctly received (if the CRC of the SPS PDSCH is correctly confirmed), the terminal can generate an ACK with HARQ-ACK information for the SPS PDSCH. The terminal attempts to receive the SPS PDSCH with the second SPS PDSCH scheduling parameter set, and if correctly received (if the CRC of the SPS PDSCH is correctly confirmed), the terminal can generate an ACK with HARQ-ACK information for the SPS PDSCH. However, the terminal can generate a NACK in the following cases.

[0379] If the terminal correctly receives the SPS PDSCH with the first SPS PDSCH scheduling parameter set and correctly receives the SPS PDSCH with the second SPS PDSCH scheduling parameter set, the terminal generates a NACK.

[0380] If the terminal fails to correctly receive the SPS PDSCH with the first SPS PDSCH scheduling parameter set and fails to correctly receive the SPS PDSCH with the second SPS PDSCH scheduling parameter set, the terminal generates a NACK.

[0381] In step 4 (1430), the terminal can generate 1-bit HARQ-ACK information for the SPS PDSCH. That is, even if multiple SPS PDSCH scheduling parameter sets are set, only 1-bit HARQ-ACK information can be generated.

[0382] Step 5 (1440): The terminal can transmit the generated 1-bit HARQ-ACK information to the base station. At this time, the 1-bit HARQ-ACK information can be transmitted while being included in a Type-1 HARQ-ACK codebook or a Type-2 HARQ-ACK codebook.

[0383] According to the present disclosure, a terminal can receive an SPS PDSCH based on a plurality of SPS PDSCH scheduling parameter sets, and can generate 1 bit as HARQ-ACK information of the SPS PDSCH. When the terminal is configured to transmit HARQ-ACK information using a Type-1 HARQ-ACK codebook, the terminal can determine the position of the HARQ-ACK bit of a 1-bit SPS PDSCH within the Type-1 HARQ-ACK codebook based on a plurality of SPS PDSCH scheduling parameter sets.

[0384] In one embodiment, the terminal may determine the position of the HARQ-ACK bit of a 1-bit SPS PDSCH within a Type-1 HARQ-ACK codebook based on one SPS PDSCH scheduling parameter set among a plurality of SPS PDSCH scheduling parameter sets. More specifically, the terminal may determine one SPS PDSCH scheduling parameter set among the plurality of SPS PDSCH scheduling parameter sets by one of the following methods.

[0385] - In the first method, each SPS PDSCH scheduling parameter set can be assigned a unique index. The position of the HARQ-ACK bit of a 1-bit SPS PDSCH within the Type-1 HARQ-ACK codebook can be determined based on the SPS PDSCH scheduling parameter set with the lowest index among the unique indices.

[0386] - In a second method, a single SPS PDSCH scheduling parameter set can be determined based on a TDRA value included in a plurality of SPS PDSCH scheduling parameter sets. For example, the position of the HARQ-ACK bit of a 1-bit SPS PDSCH within a Type-1 HARQ-ACK codebook can be determined based on a TDRA value corresponding to a symbol starting earliest among symbols corresponding to the TDRA values. Alternatively, the position of the HARQ-ACK bit of a 1-bit SPS PDSCH within a Type-1 HARQ-ACK codebook can be determined based on a TDRA value including a largest number of symbols among symbols corresponding to the TDRA values. Alternatively, the position of the HARQ-ACK bit of a 1-bit SPS PDSCH within a Type-1 HARQ-ACK codebook can be determined based on a TDRA value including a symbol ending latest among symbols corresponding to the TDRA values.

[0387] - In a third method, a single SPS PDSCH scheduling parameter set can be determined based on FDRA values ​​included in multiple SPS PDSCH scheduling parameter sets. For example, the position of the HARQ-ACK bit of a 1-bit SPS PDSCH within a Type-1 HARQ-ACK codebook can be determined based on the FDRA value corresponding to the PRB starting earliest among the PRBs corresponding to the FDRA values. Alternatively, the position of the HARQ-ACK bit of a 1-bit SPS PDSCH within a Type-1 HARQ-ACK codebook can be determined based on the FDRA value including the largest number of symbols among the PRBs corresponding to the FDRA values. Alternatively, the position of the HARQ-ACK bit of a 1-bit SPS PDSCH within a Type-1 HARQ-ACK codebook can be determined based on the FDRA value including the PRB ending latest among the symbols corresponding to the FDRA values.

[0388] - In a fourth method, a single SPS PDSCH scheduling parameter set can be determined based on an MCS value included in a plurality of SPS PDSCH scheduling parameter sets. For example, the position of the HARQ-ACK bit of a 1-bit SPS PDSCH within a Type-1 HARQ-ACK codebook can be determined based on an SPS PDSCH scheduling parameter set corresponding to a lowest MCS value among the MCS values. Alternatively, the position of the HARQ-ACK bit of a 1-bit SPS PDSCH within a Type-1 HARQ-ACK codebook can be determined based on an SPS PDSCH scheduling parameter set corresponding to a highest MCS value among the MCS values.

[0389] In one embodiment of the present disclosure, a terminal may receive a single SPS PDSCH through multiple SPS reception opportunities. For example, multiple SPS reception opportunities (SPS occasions) may be configured for a time unit (e.g., a slot) corresponding to a period. When multiple SPS reception opportunities (SPS occasions) are configured, each SPS occasion may be located in a different symbol. For example, SPS occasion 0 may be received in a first symbol set, and SPS occasion 1 may be received in a second symbol set. Here, the first symbol set and the second symbol set may not overlap with each other on the time axis. The terminal can receive an SPS PDSCH based on a first SPS PDSCH scheduling parameter set in each SPS occasion (each of the first symbol set and each of the second symbol sets), and the terminal can receive an SPS PDSCH based on a second SPS PDSCH scheduling parameter set in two SPS occasions (each of the first symbol set and each of the second symbol sets). That is, the terminal can receive from the base station first SPS PDSCH scheduling parameter set information for receiving one SPS PDSCH in each SPS occasion and second SPS PDSCH scheduling parameter set information for receiving one SPS PDSCH in multiple SPS occasions.

[0390] Here, multiple SPS occasions receiving one SPS PDSCH may satisfy at least one or a combination of the following conditions.

[0391] - One condition is that multiple SPS occasions are included in one slot. That is, if a first symbol set corresponding to a first SPS occasion and a second symbol set corresponding to a second SPS occasion are included in the same slot, the terminal can receive one SPS PDSCH in the two SPS occasions.

[0392] - This is when multiple SPS occasions are consecutive on the time axis under one condition. That is, if the first symbol set corresponding to the first SPS occasion and the second symbol set corresponding to the second SPS occasion are consecutive on the time axis, the terminal can receive one SPS PDSCH in the two SPS occasions.

[0393] - A case where multiple SPS occasions are within a certain time window on the time axis under one condition. That is, when a first symbol set corresponding to a first SPS occasion and a second symbol set corresponding to a second SPS occasion are within a certain time window on the time axis (i.e., when the interval between the two symbol sets is less than or equal to a certain number of symbols, or when the interval between the start symbol and the last symbol of the symbol set resulting from the combination of the two symbol sets is less than or equal to a certain number of symbols), the terminal can receive one SPS PDSCH in the two SPS occasions.

[0394] In the above-described embodiment, multiple SPS occasions may contain the same number of symbols.

[0395] In the above-described embodiment, multiple SPS occasions may include different numbers of PRBs.

[0396] In the above-described embodiment, when receiving one SPS PDSCH in multiple SPS occasions, the length of the TB (transport block) included in the SPS PDSCH (TB size, TBS) can be determined based on the number of REs included in the multiple SPS occasions.

[0397] In the above-described embodiment, receiving one SPS PDSCH in multiple SPS occasions may mean that a CRC (cyclic redundancy code) is attached to one TB, and a signal modulated according to an MCS value after being channel-coded is received in multiple SPS occasions.

[0398] [Example 2: Method for indicating a set of SPS PDSCH scheduling parameters to be received]

[0399] According to the present disclosure, when a terminal is configured with multiple SPS PDSCH scheduling parameter sets, the terminal can receive an SPS PDSCH based on the multiple SPS PDSCH scheduling parameter sets. In this case, the terminal must attempt to decode the SPS PDSCH a number of times corresponding to the number of SPS PDSCH scheduling parameter sets. Therefore, high complexity and energy consumption of the terminal may occur.

[0400] A method to address this may be disclosed.

[0401] In a first method, a terminal may be configured with a set of SPS PDSCH scheduling parameters corresponding to an HPN (HARQ process number). For example, a first HPN set (e.g., 0, 2) may correspond to a first SPS PDSCH scheduling parameter set, and a second HPN set (e.g., 2, 3) may correspond to a second SPS PDSCH scheduling parameter set. The above configurations may be included in the SPS configuration.

[0402] A terminal can determine a slot in which to receive an SPS PDSCH. The terminal can obtain an HPN corresponding to the slot. This can be obtained using mathematical expression 3. If the HPN corresponding to the slot is included in the first set (e.g., the HPN corresponding to the slot is 0), the SPS PDSCH can be received based on the first SPS PDSCH scheduling parameter set. In this case, the second SPS PDSCH scheduling parameter set can be ignored. If the HPN corresponding to the slot is included in the second set (e.g., the HPN corresponding to the slot is 1), the SPS PDSCH can be received based on the second SPS PDSCH scheduling parameter set. In this case, the first SPS PDSCH scheduling parameter set can be ignored.

[0403] In a second method, the terminal may configure a set of SPS PDSCH scheduling parameters corresponding to the order of the SPS PDSCH. More specifically, the terminal may determine the order of the SPS PDSCH. For example, when the SPS PDSCH is activated in slot n, the terminal may determine the order of the SPS PDSCH of slot n as 0, the order of the SPS PDSCH of slot n+P as 1, and the order of the SPS PDSCH of slot n+2*P as 2. That is, if the index of the slot in which the SPS PDSCH is received is X, the order may be determined as (Xn) / P. The terminal may configure a set of SPS PDSCH scheduling parameters corresponding to the order. For example, the first orders may correspond to the first SPS PDSCH scheduling parameter set, and the second orders may correspond to the second SPS PDSCH scheduling parameter set. The above configuration may be included in the SPS configuration. Here, the first orders may be even orders and the second orders may be odd orders.

[0404] In a third method, the terminal may be instructed with a set of SPS PDSCH scheduling parameters for each SPS reception slot. Referring to FIG. 15, the terminal may receive an indicator for reception of an SPS PDSCH of slot n. The SPS PDSCH may be transmitted at SPS occasion 0 (1501) corresponding to the first SPS PDSCH scheduling parameter set of slot n. Therefore, the indicator for reception of the SPS PDSCH of slot n may include a value corresponding to SPS occasion 0 (1501). The terminal may receive an indicator for reception of an SPS PDSCH of slot n+P. The SPS PDSCH may be transmitted at SPS occasion 0 (1511) corresponding to the first SPS PDSCH scheduling parameter set of slot n+P. Therefore, the indicator for reception of the SPS PDSCH of slot n+P may include a value corresponding to SPS occasion 0 (1511). The terminal may receive an indicator for reception of the SPS PDSCH of slot n+2*P. The SPS PDSCH may be transmitted in SPS occasion 1 (1522) corresponding to the second SPS PDSCH scheduling parameter set of slot n+2*P. Accordingly, the indicator for reception of the SPS PDSCH of slot n+2*P may include a value corresponding to SPS occasion 1 (1522).

[0405] The above instruction can be received by the terminal in at least one of the following ways.

[0406] The terminal may receive downlink control information (DCI) including the above indicator. The DCI may include at least one of the following information.

[0407] - {Information about the SPS reception slot, information about the set of SPS PDSCH scheduling parameters to be used in the slot}

[0408] If the slot in which the DCI is received and the SPS receiving slot are always the same, the information about the SPS receiving slot may be omitted. Alternatively, if the slot in which the DCI is received and the SPS receiving slot always have a constant relationship, the information about the SPS receiving slot may be omitted. Here, the constant relationship may be when the slot in which the DCI is received is the first slot and the SPS receiving slot is the second slot, and the difference between the index of the first slot and the index of the second slot is constant. In this case, the DCI may include the following information.

[0409] - {Information about the set of SPS PDSCH scheduling parameters to be used in the SPS reception slot}

[0410] The slot in which the DCI is received may be the same time as or earlier than the SPS reception slot. That is, the terminal may receive the DCI in the first slot and obtain information about the set of SPS PDSCH scheduling parameters to be used in the SPS reception slots in the first slot or later slots in time.

[0411] A terminal can obtain information about a plurality of SPS reception slots and information about a set of SPS PDSCH scheduling parameters to be used in the plurality of slots from the DCI. For example, the terminal can obtain information about a first SPS reception slot and information about a second SPS reception slot from the DCI, and information about a set of SPS PDSCH scheduling parameters to be used in the first SPS reception slot and information about a set of SPS PDSCH scheduling parameters to be used in the second SPS reception slot. When the terminal receives an SPS PDSCH in the first slot, the terminal can receive the SPS PDSCH based on the indicated set of SPS PDSCH scheduling parameters. When the terminal receives an SPS PDSCH in the second slot, the terminal can receive the SPS PDSCH based on the indicated set of SPS PDSCH scheduling parameters. In this case, the DCI may include the following information.

[0412] - {Information about the first SPS reception slot, information about the set of SPS PDSCH scheduling parameters to be used in the first SPS reception slot, information about the second SPS reception slot, information about the set of SPS PDSCH scheduling parameters to be used in the second SPS reception slot}

[0413] The second SPS reception slot may be an SPS reception slot of the cycle immediately following the first SPS reception slot. And, the third SPS reception slot may be an SPS reception slot of the second cycle following the first SPS reception slot. The n-th SPS reception slot may be an SPS reception slot of the (n-1)-th cycle following the first SPS reception slot. For example, if the first SPS reception slot is slot X, the second SPS reception slot may be slot X+P, and the third SPS reception slot may be slot X+2*P. In this case, the DCI may include information about the first SPS reception slot, but may not include information about the second SPS reception slot or information about the third SPS reception slot. That is, the DCI may include the following information.

[0414] - {Information about the first SPS reception slot, information about the set of SPS PDSCH scheduling parameters to be used in the first SPS reception slot, information about the set of SPS PDSCH scheduling parameters to be used in the second SPS reception slot}

[0415] If the slot in which the DCI is received and the first SPS reception slot are always the same, information about the first SPS reception slot may be omitted. Alternatively, if the slot in which the DCI is received and the first SPS reception slot always have a constant relationship, information about the first SPS reception slot may be omitted. In this case, the DCI may include the following information.

[0416] - {Information about the set of SPS PDSCH scheduling parameters to be used in the first SPS reception slot, information about the set of SPS PDSCH scheduling parameters to be used in the second SPS reception slot}

[0417] Here, the first SPS reception slot may be a slot in which DCI is received, and the second SPS reception slot may be a slot in the cycle immediately following the first SPS reception slot.

[0418] At the time when the base station transmits the DCI, the base station may not be able to determine the set of SPS PDSCH scheduling parameters to be used in a specific SPS reception slot. Therefore, the base station may not be able to instruct the terminal which set of SPS PDSCH scheduling parameters to be used. To instruct this, one of the pieces of information about the set of SPS PDSCH scheduling parameters to be used in the SPS reception slot may not be able to instruct the set of SPS PDSCH scheduling parameters to be used in the SPS reception slot. More specifically, the terminal may be configured with a first set of SPS PDSCH scheduling parameters and a second set of SPS PDSCH scheduling parameters. The terminal may be instructed with a first value as the information about the set of SPS PDSCH scheduling parameters to be used in the SPS reception slot. The first value may correspond to the first set of SPS PDSCH scheduling parameters. Therefore, the terminal may attempt to receive the SPS PDSCH based on the first set of SPS PDSCH scheduling parameters in the SPS reception slot. The terminal may be instructed with a second value as information about a set of SPS PDSCH scheduling parameters to be used in the SPS reception slot. The second value may correspond to the second set of SPS PDSCH scheduling parameters. Accordingly, the terminal may attempt to receive an SPS PDSCH based on the second set of SPS PDSCH scheduling parameters in the SPS reception slot. The terminal may be instructed with a third value as information about a set of SPS PDSCH scheduling parameters to be used in the SPS reception slot. When the third value is instructed, the terminal may not be able to determine information about a set of SPS PDSCH scheduling parameters to be used in the SPS reception slot. That is, when the terminal receives an SPS PDSCH in the SPS reception slot, the terminal may receive it based on the first set of SPS PDSCH scheduling parameters and based on the second set of SPS PDSCH scheduling parameters.

[0419] The terminal can receive the DCI via the PDCCH. The PDCCH can include a DCI format that schedules the PDSCH. That is, some fields of the DCI format that schedules the PDSCH can be the DCI. The terminal can receive the DCI via the PDCCH. The PDCCH can include a DCI format that does not schedule the PDSCH. That is, some fields of the DCI format that does not schedule the PDSCH can be the DCI.

[0420] The terminal can receive the DCI via the SPS PDSCH. That is, some REs of the SPS PDSCH can be used for receiving the DCI. The terminal can receive information about some REs in the SPS PDSCH from the base station. At least, the terminal can receive information about the number of REs in the SPS PDSCH from the base station. In addition, the terminal can determine REs corresponding to the number among the REs in the SPS PDSCH and map the DCI to the REs.

[0421] When a terminal is configured with multiple SPS PDSCH scheduling parameter sets, an SPS occasion can be determined based on each configuration. For example, SPS occasion 0 may be included in SPS occasion 1. That is, the REs included in SPS occasion 0 may be included in SPS occasion 1. In this case, the terminal may receive DCI from some of the REs included in the smallest SPS occasion, for example, SPS occasion 0.

[0422] [Example 3: SPS PDSCH Retransmission Method]

[0423] A terminal can schedule retransmission of an SPS PDSCH in a DCI format. The CRC of the DCI format may be scrambled with CS-RNTI, and the NDI (new data indicator) field may be set to 1. In addition, the terminal can be instructed on the HPN to be retransmitted from the HPN field of the DCI format. The terminal can decode the PDSCH by HARQ combining the SPS PDSCH reception result value corresponding to the HPN (the Log-likelihood ratio value stored in the soft buffer) and the retransmitted PDSCH. Here, the HARQ combining may include incremental redundancy (IR) combining.

[0424] According to the above-described embodiment, a terminal may correspond to multiple SPS PDSCH scheduling parameter sets to a single HPN. The SPS PDSCH scheduling parameter sets may include different parameters (MCS, FDRA, TDRA). Therefore, even if the HPN field of the DCI format indicates a single HPN value, the terminal cannot determine which scheduling parameter sets a previously received SPS PDSCH was transmitted with. Accordingly, the terminal cannot receive a previously received SPS PDSCH and a retransmitted PDSCH by HARQ combining.

[0425] According to the present disclosure, a terminal can receive from a base station information regarding which scheduling parameter set a previously received SPS PDSCH was transmitted. More specifically, a DCI format for retransmitting an SPS PDSCH can include information regarding which scheduling parameter set the retransmitted SPS PDSCH was transmitted with. For example, when the terminal receives a first SPS PDSCH scheduling parameter set and a second SPS PDSCH scheduling parameter set from the base station, a DCI format for retransmitting an SPS PDSCH can include a 1-bit indicator. If the 1-bit indicator is a first value (e.g., '0'), this indicates that the retransmitted SPS PDSCH was previously transmitted with the first SPS PDSCH scheduling parameter set, and if the 1-bit indicator is a second value (e.g., '1'), this indicates that the retransmitted SPS PDSCH was previously transmitted with the second SPS PDSCH scheduling parameter set. The terminal can perform HARQ combining according to the above indicator. That is, if the 1-bit indicator is a first value (e.g., '0'), the terminal can decode the PDSCH by HARQ combining the result value (LLR value) received with the first SPS PDSCH scheduling parameter set and the retransmitted PDSCH. If the 1-bit indicator is a second value (e.g., '1'), the terminal can decode the PDSCH by HARQ combining the result value (LLR value) received with the second SPS PDSCH scheduling parameter set and the retransmitted PDSCH.

[0426] <Example 4: Method for selecting SPS PDSCH to receive>

[0427] In the above-described embodiment, a terminal can receive multiple SPS PDSCH scheduling parameters within a single SPS configuration. Accordingly, the terminal can receive an SPS PDSCH through multiple SPS occasions within an SPS reception slot. In another method of the present disclosure, the terminal can receive multiple SPS configurations from a base station. Each SPS configuration can include one SPS PDSCH scheduling parameter configuration. SPS PDSCHs determined by the multiple SPS configurations can overlap. When such an overlapping situation occurs, a method is disclosed for determining which SPS PDSCH the terminal selects and receives.

[0428] When a terminal has the ability to receive only one PDSCH in one symbol, the method by which the terminal selects the SPS PDSCH to receive in one slot is shown in [Table 24].

[0429] For reference, since a terminal can receive only one PDSCH in one symbol, if multiple SPS PDSCHs overlap in one symbol, the terminal can select and receive the SPS PDSCH with the lowest index among the multiple SPS PDSCHs.

[0430] [Table 24]

[0431]

[0432] FIG. 16 is a diagram illustrating a process of selecting an SPS PDSCH to be received in one slot according to Table 24.

[0433] Referring to FIG. 16, a terminal may be configured to receive four SPS PDSCHs (SPS#0, SPS#1, SPS#2, SPS#3) in one slot. The terminal may have the ability to receive up to two PDSCHs in one slot.

[0434] The process in Table 24 is as follows.

[0435] Step 0: j=0 and Q={0,1,2,3} (see 1 in Fig. 16)

[0436] Step 1: The SPS PDSCH with the lowest index among the Q set, Q={0,1,2,3}, can be selected and received. That is, SPS#0 can be selected and received. j=1 can be designated. The SPS#0 can be designated as a survivor. (See 1 in Fig. 16)

[0437] Step 2: SPS#1, which is an SPS PDSCH that overlaps with SPS#0 designated as a survivor, can be excluded from the Q set. That is, the Q set can be {2,3}.

[0438] Step 3: Since the terminal has the ability to receive two PDSCHs in one slot, j=1, and the Q set Q={2,3} is not empty, the terminal can repeat steps 1 and 2.

[0439] Step 1: The SPS PDSCH with the lowest index among the Q set, Q={2,3}, can be selected and received. That is, SPS#2 can be selected and received. j=2 can be specified. The SPS#2 can be designated as a survivor. (See 2 in Fig. 16)

[0440] Step 2: SPS#3, which is an SPS PDSCH that overlaps with SPS#2 designated as a survivor, can be excluded from the Q set. In other words, the Q set is (It may be an empty set).

[0441] Step 3: Since the terminal has the ability to receive two PDSCHs in one slot and j=2 or the Q set is empty, the terminal can terminate the above pseudocode.

[0442] Through the above process, the terminal can receive two SPS PDSCHs (SPS#0, SPS#2) out of four SPS PDSCHs (SPS#0, SPS#1, SPS#2, SPS#3) in a slot.

[0443] For reference, according to Step 1 of the pseudocode in Table 24, the terminal can prioritize an SPS with a lower index over an SPS with a higher index.

[0444] Figure 17 is a diagram showing an SPS PDSCH that a terminal can receive.

[0445] Referring to FIG. 17, the terminal is configured to receive four PDSCHs (SPS#0, SPS#1, SPS#2, SPS#3) in one slot, and the terminal may have the ability to receive up to two PDSCHs in one slot.

[0446] If the terminal can receive only one PDSCH in a symbol, the terminal can receive SPS#0 and SPS#2 according to the pseudocodes in Table 24 above. However, if the terminal has the ability to receive two PDSCHs in a symbol, it may be desirable for the terminal to receive SPS#0 and SPS#1. This is because SPS#1 has a lower index (higher priority) than SPS#2.

[0447] The present disclosure relates to a method for selecting an SPS PDSCH to be received by a terminal when the terminal has the capability to receive multiple PDSCHs in one symbol.

[0448] Table 25 and FIG. 18 are pseudocodes for selecting an SPS PDSCH to be received by a terminal when the terminal has the ability to receive multiple PDSCHs in a single symbol, according to the present disclosure. Steps 1800, 1810, 1820, and 1830 of FIG. 18 correspond to Steps 0, 1, 2, and 3 of Table 25, respectively.

[0449] [Table 25]

[0450]

[0451] Referring to Table 25, in Step 2, the UE can determine the number of overlapping survivor PDSCHs for each symbol of the survivor PDSCH designated in Step 1. Here, the survivor PDSCHs may be all survivor PDSCHs designated in Step 1 so far. If the number of overlapping survivor PDSCHs in a certain symbol is equal to the number of PDSCHs that the UE can receive in a certain symbol, the UE can determine other PDSCHs (PDSCHs other than survivor PDSCHs) overlapping with the symbol. In addition, the UE can exclude other PDSCHs overlapping with the symbol from the Q set.

[0452] As an example of the present disclosure, Table 26 and FIG. 19 are pseudocodes for selecting an SPS PDSCH to be received by a terminal when the terminal has the ability to receive multiple PDSCHs in one symbol. Steps 1900, 1910, 1920, and 1930 of FIG. 19 respectively correspond to Steps 0, 1, 2, and 3 of Table 26.

[0453] [Table 26]

[0454]

[0455] Referring to Table 26, the UE can determine the number of survivor PDSCHs overlapping with the PDSCH with the lowest index in the Q set in Step 1. If the number of overlapping survivor PDSCHs is less than the number of PDSCHs that the UE can receive in one symbol, the UE can designate the PDSCH with the lowest index in the Q set as a survivor. j can be set to j+1. In Step 2, the UE can exclude the PDSCH designated as the survivor PDSCH in Step 1 from the Q set. The UE can continue to repeat Steps 1 and 2 until the Q set is empty or j is equal to the number of PDSCHs that the UE can receive in the slot.

[0456] FIG. 20 is a diagram illustrating a process for selecting an SPS PDSCH to be received by a terminal, with reference to Table 26.

[0457] In Fig. 20, the terminal can receive two PDSCHs in one slot and has the ability to simultaneously receive four PDSCHs in one symbol. The terminal can be configured to receive eight SPS PDSCHs (SPS#0, SPS#1, SPS#2, SPS#3, SPS#4, SPS#5, SPS#6, SPS#7) in one slot.

[0458] The process in Table 26 is as follows.

[0459] Step 0: j=0, and Q={0,1,2,3,4,5,6,7}. (See 1 in Fig. 20)

[0460] Step 1: The number of survivor PDSCHs overlapping with SPS#0, which is the SPS PDSCH with the lowest index among the Q set, Q={0,1,2,3,4,5,6,7}, can be determined. Since the number of survivor PDSCHs overlapping with SPS#0 (here, there are no survivor PDSCHs overlapping with SPS#0) is 0, which is less than the number of PDSCHs that the UE can receive in one symbol, the UE can designate SPS#0 as the survivor PDSCH. In addition, j=1. (See 1 in FIG. 20)

[0461] Step 2: The terminal can exclude SPS#0, which is the SPS PDSCH with the lowest index among the Q set, Q={0,1,2,3,4,5,6,7}, from the Q set. That is, the Q set can be {1,2,3,4,5,6,7}.

[0462] Step 3: Since the terminal has the ability to receive 4 PDSCHs in one slot, j=1, and the Q set Q={1,2,3,4,5,6,7} is not an empty set, the terminal can repeat steps 1 and 2.

[0463] Step 1: The number of survivor PDSCHs overlapping with SPS#1, which is the SPS PDSCH with the lowest index among the Q set, Q={1,2,3,4,5,6,7}, can be determined. Since the number of survivor PDSCHs overlapping with SPS#1 (SPS#0) is 1, which is smaller than the number of PDSCHs that the UE can receive in one symbol, the UE can designate SPS#1 as the survivor PDSCH. In addition, j=2. (See 2 in FIG. 20)

[0464] Step 2: The terminal can exclude SPS#1, which is the SPS PDSCH with the lowest index among the Q set, Q={1,2,3,4,5,6,7}, from the Q set. That is, the Q set can be {2,3,4,5,6,7}.

[0465] Step 3: Since the terminal has the ability to receive 4 PDSCHs in one slot, j=2, and the Q set Q={2,3,4,5,6,7} is not an empty set, the terminal can repeat steps 1 and 2.

[0466] Step 1: The number of survivor PDSCHs overlapping with SPS#2, which is the SPS PDSCH with the lowest index among the Q set, Q={2,3,4,5,6,7}, can be determined. Since the number of survivor PDSCHs overlapping with SPS#1 (SPS#1) is 1, which is smaller than the number of PDSCHs that the UE can receive in one symbol, the UE can designate SPS#2 as the survivor PDSCH. In addition, j can be 3. (See 3 in FIG. 20)

[0467] Step 2: The terminal can exclude SPS#2, which is the SPS PDSCH with the lowest index among the Q set, Q={2,3,4,5,6,7}, from the Q set. That is, the Q set can be {3,4,5,6,7}.

[0468] Step 3: Since the terminal has the ability to receive 4 PDSCHs in one slot, j=3, and the Q set Q={3,4,5,6,7} is not an empty set, the terminal can repeat steps 1 and 2.

[0469] Step 1: The number of survivor PDSCHs overlapping with SPS#3, the SPS PDSCH with the lowest index among the Q set, Q={3,4,5,6,7}, can be determined. The number of survivor PDSCHs overlapping with SPS#3 (SPS#0, SPS#1) is 2, which is the same as the number of PDSCHs that the UE can receive in one symbol, and therefore the UE may not perform any additional actions. (See 4 in FIG. 20)

[0470] Step 2: The terminal can exclude SPS#3, which is the SPS PDSCH with the lowest index among the Q set, Q={3,4,5,6,7}, from the Q set. That is, the Q set can be {4,5,6,7}.

[0471] Step 3: Since the terminal has the ability to receive 4 PDSCHs in one slot, j=3, and the Q set Q={4,5,6,7} is not empty, the terminal can repeat steps 1 and 2.

[0472] Step 1: The number of survivor PDSCHs overlapping with SPS#4, the SPS PDSCH with the lowest index among the Q set, Q={4,5,6,7}, can be determined. Since the number of survivor PDSCHs overlapping with SPS#4 (SPS#2) is 2, which is smaller than the number of PDSCHs that the UE can receive in one symbol, the UE can designate SPS#4 as the survivor PDSCH. In addition, j=4. (See 5 in FIG. 20)

[0473] Step 2: The terminal can exclude SPS#4, which is the SPS PDSCH with the lowest index among the Q set, Q={4,5,6,7}, from the Q set. That is, the Q set can be {5,6,7}.

[0474] Step 3: Since the terminal has the ability to receive 4 PDSCHs in one slot and j=4 (even if the Q set Q={5,6,7} is not empty), the terminal can terminate the above pseudocode.

[0475] Through the above process, the terminal can receive four SPS PDSCHs (SPS#0, SPS#1, SPS#2, SPS#4) out of eight SPS PDSCHs (SPS#0, SPS#1, SPS#2, SPS#3, SPS#4, SPS#5, SPS#6, SPS#7) in a slot.

[0476] <Example 4: SPS PDSCH Cancellation>

[0477] In one embodiment of the present disclosure, a method is provided for a terminal to cancel reception of an SPS PDSCH in order to receive a DG PDSCH when the terminal has the ability to receive multiple PDSCHs in one symbol.

[0478] [Figure 21] is a diagram illustrating a method for a terminal to cancel reception of an SPS PDSCH in order to receive a DG PDSCH when the terminal has the ability to receive one PDSCH in one symbol.

[0479] Referring to FIG. 21, a terminal can determine an SPS PDSCH to be received in a slot through a higher layer signal. Unless otherwise instructed, the terminal can receive the SPS PDSCH in the slot.

[0480] Referring to FIG. 21, a terminal may receive a PDCCH scheduling a DG PDSCH that overlaps with an SPS PDSCH. Depending on the conditions, the terminal may receive the DG PDSCH and cancel reception of the SPS PDSCH. Depending on the conditions, the terminal may determine that the PDCCH includes incorrect downlink control information. The terminal may ignore the DG PDSCH scheduled by the PDCCH that includes incorrect downlink control information, and the terminal may receive the SPS PDSCH.

[0481] Here, the conditions may be as follows. If the reception of the PDCCH is completed N symbols before the start symbol of the SPS PDSCH, the terminal may receive the DG PDSCH scheduled by the PDCCH and cancel the reception of the SPS PDSCH. If the reception of the PDCCH is completed between N symbols from the start symbol of the SPS PDSCH, it may be determined that the PDCCH includes incorrect downlink control information. Here, the value of N may be 14. Here, the value of N may be And, is the subcarrier spacing setting value, The subcarrier spacing can be 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, 480 kHz, or 960 kHz.

[0482] In the above example, the situation where the SPS PDSCH and the DG PDSCH overlap can be when at least one symbol of the SPS PDSCH and at least one symbol of the DG PDSCH are the same symbol. That is, it can be applied when there is overlap in the time domain. In other words, the above example is about the ability of the terminal to receive only one PDSCH in a symbol. Therefore, the terminal cannot receive the DG PDSCH and the SPS PDSCH in the same symbol.

[0483] In the above example, the SPS PDSCH and DG PDSCH overlap when the slot in which the SPS PDSCH is scheduled and the slot in which the DG PDSCH is scheduled are the same. In other words, this can be applied when there is overlap at the slot level. In other words, the above example is about the ability of the terminal to receive only one PDSCH in a slot. Therefore, the terminal cannot receive the DG PDSCH and the SPS PDSCH in the same slot.

[0484] Hereinafter, in the present disclosure, a terminal may have the ability to receive multiple PDSCHs in one symbol or may have the ability to receive multiple PDSCHs in one slot.

[0485] In one embodiment of the present disclosure, when a terminal can receive one PDSCH in one symbol and has the ability to receive Y PDSCHs in one slot, the terminal can determine a PDSCH to receive by at least one of the following methods.

[0486] First, the terminal can determine Y SPS PDSCHs to be received in the slot. The method for determining Y SPS PDSCHs to be received in the slot can follow the pseudo code described above (Table 24). The SPS PDSCHs can be assigned a unique index. This may be an index included in the SPS configuration to which the SPS PDSCH belongs. If multiple SPS PDSCHs have the same index, the terminal can assign the indexes of the multiple SPS PDSCHs based on the scheduling information of the SPS PDSCHs (index of the starting symbol, index of the starting PRB, HARQ process number, etc.).

[0487] The terminal may receive a PDCCH scheduling a DG PDSCH in the slot. The terminal may receive the DG PDSCH according to conditions. The terminal may determine that the PDCCH scheduling the DG PDSCH contains incorrect downlink information according to conditions.

[0488] When the terminal receives the DG PDSCH according to a condition, the terminal may cancel reception of at least one SPS PDSCH. In one embodiment, the SPS PDSCH that the terminal cancels without receiving may be the SPS PDSCH with the highest index. In one embodiment, the SPS PDSCH that the terminal cancels without receiving may be all SPS PDSCHs within a slot. In one embodiment, the SPS PDSCHs in the embodiment may be SPS PDSCHs that start N symbols after the PDCCH that schedules the DG PDSCH.

[0489] The conditions may be as follows. If there is at least one SPS PDSCH starting N symbols after the PDCCH scheduling the DG PDSCH. If there is at least one SPS PDSCH starting N symbols after the PDCCH scheduling the DG PDSCH, the UE can receive the DG PDSCH. In addition, reception of at least one of the SPS PDSCHs starting N symbols after the PDCCH scheduling the DG PDSCH can be canceled. Here, the reception of which SPS PDSCH is to be canceled can follow the example described above. If there is no SPS PDSCH starting N symbols after the PDCCH scheduling the DG PDSCH, it can be determined that the PDCCH scheduling the DG PDSCH includes incorrect downlink information.

[0490] In one embodiment of the present disclosure, when a terminal is capable of receiving X PDSCHs in one symbol and has the ability to receive Y PDSCHs in one slot, the terminal can determine which PDSCH to receive by at least one of the following methods.

[0491] First, the terminal can determine Y SPS PDSCHs to be received in a slot. The SPS PDSCHs can overlap up to X SPS PDSCHs in one symbol. Depending on the above conditions, the SPS PDSCH method can follow the above-described similar code (Tables 25 to 26). The SPS PDSCHs can be assigned a unique index. This may be an index included in the SPS configuration to which the SPS PDSCH belongs. If multiple SPS PDSCHs have the same index, the terminal can assign indexes to the multiple SPS PDSCHs based on scheduling information of the SPS PDSCHs (index of a starting symbol, index of a starting PRB, HARQ process number, etc.).

[0492] The terminal may receive a PDCCH scheduling a DG PDSCH in the slot. The terminal may receive the DG PDSCH according to conditions. The terminal may determine that the PDCCH scheduling the DG PDSCH contains incorrect downlink information according to conditions.

[0493] When the terminal receives the DG PDSCH according to a condition, the terminal may cancel reception of at least one SPS PDSCH. In one embodiment, the SPS PDSCH that the terminal does not receive and cancels may be the SPS PDSCH with the highest index. In one embodiment, the SPS PDSCH that the terminal does not receive and cancels may be all SPS PDSCHs within a slot. In one embodiment, the SPS PDSCH that the terminal does not receive and cancel in the embodiment may be SPS PDSCHs that overlap with the DG PDSCH in the time domain. In one embodiment, the SPS PDSCHs in the embodiment may be SPS PDSCHs that start N symbols after the PDCCH that schedules the DG PDSCH.

[0494] The conditions may be as follows. If there is at least one SPS PDSCH starting N symbols after the PDCCH scheduling the DG PDSCH. If there is at least one SPS PDSCH starting N symbols after the PDCCH scheduling the DG PDSCH, the UE can receive the DG PDSCH. In addition, reception of at least one of the SPS PDSCHs starting N symbols after the PDCCH scheduling the DG PDSCH can be canceled. Here, the reception of which SPS PDSCH is to be canceled can follow the example described above. If there is no SPS PDSCH starting N symbols after the PDCCH scheduling the DG PDSCH, it can be determined that the PDCCH scheduling the DG PDSCH includes incorrect downlink information.

[0495] Figure 22 is a diagram for a case where a terminal has the ability to receive up to two PDSCHs in one symbol.

[0496] Referring to Figure 22, two SPS PDSCHs may overlap in at least one symbol. The UE may receive a PDCCH scheduling a DG PDSCH. Here, the DG PDSCH may overlap with the two SPS PDSCHs in at least one symbol. Therefore, three PDSCHs may overlap in one symbol. This may exceed the UE's capabilities. Therefore, the UE may not be able to receive one DG PDSCH and two SPS PDSCHs.

[0497] Referring to (a) of FIG. 22, N or more symbols may be included between the PDCCH and SPS PDSCHs received by the terminal. In this case, the terminal may perform at least one of the following operations.

[0498] - The terminal can cancel reception of all SPS PDSCHs that overlap with the DG PDSCH and can only receive the DG PDSCH.

[0499] - The terminal can cancel reception of the SPS PDSCH with the highest index among the SPS PDSCHs that overlap with the DG PDSCH. In addition, the terminal can receive the DG PDSCH and the SPS PDSCH with a lower index.

[0500] Referring to (b) of FIG. 22, some of the PDCCHs and SPS PDSCHs received by the terminal may include more than N symbols, while others may include fewer than N symbols. In this case, the terminal may perform at least one of the following actions.

[0501] - The terminal may determine that the PDCCH contains incorrect downlink control information. Therefore, the reception of the DG PDSCH indicated by the PDCCH may be ignored.

[0502] - The terminal can cancel reception of SPS PDSCHs that satisfy the N symbol condition among SPS PDSCHs that overlap with the DG PDSCH. In addition, the terminal can receive SPS PDSCHs that do not satisfy the DG PDSCH and N symbol conditions.

[0503] - The terminal can cancel reception of the SPS PDSCH with the highest index among the SPS PDSCHs that satisfy the N symbol condition among the SPS PDSCHs that overlap with the DG PDSCH. In addition, the terminal can receive the DG PDSCH and the SPS PDSCHs that have not been canceled.

[0504] According to one embodiment of the present disclosure, a terminal cannot receive multiple PDSCHs on the same time-frequency resource. Therefore, the terminal can receive only one PDSCH among multiple PDSCHs on the same time-frequency resource, and can cancel reception of the remaining PDSCHs.

[0505] Figure 22 (c) is a diagram illustrating a situation in which a DG PDSCH and at least one SPS PDSCH overlap in time-frequency resources.

[0506] Referring to (c) of FIG. 22, the terminal may receive the DG PDSCH and cancel reception of the SPS PDSCH that overlaps with the DG PDSCH in time-frequency resources. More specifically, the terminal's operation may be as follows.

[0507] First, the terminal can determine which SPS PDSCH to receive in a slot. The SPS PDSCHs can be assigned a unique index.

[0508] A terminal can schedule a DG PDSCH using a PDCCH. Here, the DG PDSCH can overlap with at least one SPS PDSCH in the time-frequency domain. If reception of the PDCCH is terminated N symbols prior to the earliest symbol among the SPS PDSCHs overlapping with the DG PDSCH, the terminal can receive the DG PDSCH and cancel reception of the SPS PDSCHs. If reception of the PDCCH is not terminated N symbols prior to the earliest symbol among the SPS PDSCHs overlapping with the DG PDSCH, the terminal can determine that the PDCCH includes incorrect downlink control information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0528] Alternatively, the drawings illustrating the method of the present invention may omit some components and include only some components within a scope that does not harm the essence of the present invention.

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

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

Claims

1. In a method of UE (user equipment) in a wireless communication system, A step of receiving an RRC (radio resource control) message including a scheduling parameter set for multiple SPS (semi-persistent scheduling) PDSCH (physical downlink shared channel) from a base station; A step of receiving DCI (downlink control information) from the base station that activates an SPS setting including the set of scheduling parameters for the plurality of SPS PDSCHs; and A method characterized by comprising the step of receiving an SPS PDSCH from the base station using a first SPS PDSCH scheduling parameter set or a second SPS PDSCH scheduling parameter set determined based on the scheduling parameter set for the plurality of SPS PDSCHs in an SPS reception slot.

2. In paragraph 1, A step of generating HARQ-ACK (hybrid automatic repeat request acknowledgment) information for the SPS PDSCH received using the first SPS PDSCH scheduling parameter set or the second SPS PDSCH scheduling parameter set; and A method characterized by further comprising a step of transmitting the HARQ-ACK information to the device.

3. In the first paragraph, a plurality of SPS reception opportunities (SPS occasions) are set in the SPS reception slot, Each of the above multiple SPS reception opportunities is located at at least one different symbol, or Each of the above multiple SPS reception opportunities includes at least one different physical resource block (PRB), or A method characterized in that each of the plurality of SPS reception opportunities is associated with a different MCS (modulation and coding scheme) value.

4. A method according to claim 3, characterized in that the scheduling parameter set for the plurality of SPS PDSCHs is for determining the plurality of SPS reception opportunities within the SPS reception slot.

5. A method according to claim 1, characterized in that the scheduling parameter set for the plurality of SPS PDSCHs includes at least one of a modulation and coding scheme (MCS), a frequency domain resource allocation (FDRA), or a time domain resource allocation (TDRA).

6. A method according to claim 1, characterized in that the RRC message further includes information regarding a period for determining the SPS reception slot.

7. In a method of a base station in a wireless communication system, A step of transmitting an RRC (radio resource control) message including a scheduling parameter set for multiple SPS (semi-persistent scheduling) PDSCH (physical downlink shared channel) to a UE (user equipment); A step of transmitting, to the UE, downlink control information (DCI) that activates an SPS configuration including the set of scheduling parameters for the plurality of SPS PDSCHs; and A method characterized by comprising a step of transmitting an SPS PDSCH to the UE using a first SPS PDSCH scheduling parameter set or a second SPS PDSCH scheduling parameter set determined based on the scheduling parameter sets for the plurality of SPS PDSCHs in an SPS reception slot.

8. In paragraph 7, A method characterized in that it further comprises a step of receiving HARQ-ACK (hybrid automatic repeat request acknowledgment) information for the SPS PDSCH received by the UE from the UE using the first SPS PDSCH scheduling parameter set or the second SPS PDSCH scheduling parameter set.

9. In the 7th paragraph, a plurality of SPS reception opportunities (SPS occasions) are set in the SPS reception slot, Each of the above multiple SPS reception opportunities is located at at least one different symbol, or Each of the above multiple SPS reception opportunities includes at least one different physical resource block (PRB), or A method characterized in that each of the plurality of SPS reception opportunities is associated with a different MCS (modulation and coding scheme) value.

10. A method according to claim 9, characterized in that the scheduling parameter set for the plurality of SPS PDSCHs is for determining the plurality of SPS reception opportunities within the SPS reception slot.

11. A method according to claim 7, characterized in that the scheduling parameter set for the plurality of SPS PDSCHs includes at least one of a modulation and coding scheme (MCS), a frequency domain resource allocation (FDRA), or a time domain resource allocation (TDRA).

12. A method according to claim 7, characterized in that the RRC message further includes information regarding a period for determining the SPS reception slot.

13. In a wireless communication system, in UE (user equipment), Transmitter and receiver; and A control unit comprising: Receive an RRC (radio resource control) message including a scheduling parameter set for multiple SPS (semi-persistent scheduling) PDSCH (physical downlink shared channel) from a base station, Receiving DCI (downlink control information) from the base station that activates an SPS configuration including the set of scheduling parameters for the plurality of SPS PDSCHs, A UE characterized in that, in an SPS reception slot, an SPS PDSCH is received from the base station using a first SPS PDSCH scheduling parameter set or a second SPS PDSCH scheduling parameter set determined based on the scheduling parameter set for the plurality of SPS PDSCHs.

14. In the 13th paragraph, a plurality of SPS reception opportunities (SPS occasions) are set in the SPS reception slot, Each of the above multiple SPS reception opportunities is located at at least one different symbol, or Each of the above multiple SPS reception opportunities includes at least one different physical resource block (PRB), or A UE characterized in that each of the plurality of SPS reception opportunities is associated with a different MCS (modulation and coding scheme) value.

15. In a base station in a wireless communication system, Transmitter and receiver; and A control unit comprising: Transmitting an RRC (radio resource control) message containing a scheduling parameter set for multiple SPS (semi-persistent scheduling) PDSCH (physical downlink shared channel) to a UE (user equipment), Transmitting to the UE downlink control information (DCI) that activates an SPS configuration including the scheduling parameter set for the plurality of SPS PDSCHs, A base station characterized in that, in an SPS reception slot, an SPS PDSCH is transmitted to the UE using a first SPS PDSCH scheduling parameter set or a second SPS PDSCH scheduling parameter set determined based on the scheduling parameter set for the plurality of SPS PDSCHs.

Images