Method, device and system for transmitting and receiving a physical uplink shared channel (PUSCH) in a wireless communication system

Abstract

A method for transmitting a physical uplink shared channel (PUSCH) by a user equipment to a base station in a wireless communication system is disclosed. The user equipment may receive a first physical downlink control channel (PDCCH) including first downlink control information (DCI) from the base station, and release a configuration for activating repeated transmission of the PUSCH based on the received DCI.

Description

Technical Field

[0001] The present invention relates to a wireless communication system, and more particularly, to a method for transmitting and receiving a Physical Uplink Shared Channel (PUSCH) in a wireless communication system. Background Art

[0002] 3GPP LTE(-A) defines uplink / downlink physical channels for transmitting physical layer signals. For example, it defines the Physical Uplink Shared Channel (PUSCH) as a physical channel for transmitting data on the uplink, the Physical Uplink Control Channel (PUCCH) for transmitting control signals, and the Physical Random Access Channel (PRACH). Furthermore, it defines the Physical Downlink Shared Channel (PDSCH) for transmitting data on the downlink, and the Physical Control Format Indicator Channel (PCFICH), Physical Downlink Control Channel (PDCCH), and Physical Hybrid ARQ Indicator Channel (PHICH) for transmitting L1 / L2 control signals.

[0003] The downlink control channel (PDCCH / EPDCCH) among the above channels is a channel used by the base station to send uplink / downlink scheduling allocation control information, uplink transmit power control information and other control information to one or more user equipment. Since the resources available for the PDCCH that can be sent by the base station at one time are limited, different resources cannot be allocated to each user equipment, and control information should be sent to any user equipment through shared resources. For example, in 3GPP LTE(-A), four resource elements (REs) can be grouped to form a resource element group (REG), nine control channel elements (CCEs) can be generated, the user equipment can be notified of the resources that can combine and transmit one or more CCEs, and multiple user equipment can share and use CCEs. Here, the number of combined CCEs is called the CCE combination level, and the resources to which CCEs are allocated according to the possible CCE combination levels are called search spaces. The search space may include a common search space defined for each base station and a terminal-specific or UE-specific search space defined for each user equipment. The user equipment performs decoding for multiple cases of all possible CCE combinations in the search space and can identify whether the user equipment belongs to the PDCCH by the user equipment (UE) identifier included in the PDCCH. Therefore, this operation of the user equipment takes a long time to decode the PDCCH and inevitably leads to a large amount of energy consumption.

[0004] Efforts are underway to develop an improved 5G communication system or pre-5G communication system to meet the growing demand for wireless data services after the commercialization of the 4G communication system. For this reason, the 5G communication system or pre-5G communication system is referred to as a super-4G network communication system or a post-LTE system. Consider implementing a 5G communication system in an ultra-high frequency (mmWave) band (e.g., a 60-GHz band) to achieve high data transmission rates. In order to reduce radio propagation path loss and increase the transmission distance of radio waves in the ultra-high frequency band, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed in the field of 5G communication systems. Furthermore, in order to improve the network of the system, technologies such as advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device communication (D2D), wireless backhaul, mobile networks, collaborative communications, coordinated multi-point (CoMP), interference cancellation, etc. have been developed in the field of 5G communication systems. In addition, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coding modulation (ACM) schemes, as well as filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies have been developed in the field of 5G systems.

[0005] At the same time, the Internet, a human-centric connected network where humans generate and consume information, has evolved into the Internet of Things (IoT) network, which exchanges information between distributed components such as objects. The Internet of Everything (IoE) technology, which combines IoT technology with big data processing technology through connection to cloud servers, is also emerging. Implementing the IoT requires technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology. Consequently, in recent years, technologies such as sensor networks, machine-to-machine (M2M), and machine-type communication (MTC) have been studied to connect objects. Within the IoT environment, intelligent Internet technology (IT) services can be provided that collect and analyze data generated by networked objects to create new value in human life. Through the integration and hybridization of existing information technology (IT) and various industries, the IoT can be applied to areas such as smart homes, smart buildings, smart cities, smart cars or connected vehicles, smart grids, healthcare, smart appliances, and advanced medical services.

[0006] Various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-to-machine (M2M), and machine-type communications (MTC) are being implemented using 5G communication technologies (i.e., beamforming, MIMO, array antennas, etc.). The application of cloud radio access networks (cloud RAN) as a big data processing technology is an example of the convergence of 5G and IoT technologies.

[0007] Mobile communication systems have traditionally been developed to provide voice services while protecting user activity. However, the scope of mobile communication systems has expanded beyond voice services to include data services, and has even been developed to provide high-speed data services. However, current mobile communication systems for providing these services are experiencing resource shortages, and users are demanding higher-speed services. Therefore, a more advanced wireless communication system is needed.

[0008] As mentioned above, with the emergence of new applications such as real-time control and tactile Internet, future 5G technology requires lower data transmission latency, and it is expected that the required latency of 5G data will be reduced to 1ms. The goal of 5G is to provide data latency that is approximately 10 times lower than that of existing technologies. To address this problem, it is expected to propose a 5G communication system that uses micro slots with shorter TTI intervals (e.g., 0.2ms) in addition to existing time slots (or subframes).

[0009] In Rel-16 enhanced URLLC (eURLLC), various technologies for providing lower latency and higher reliability are discussed. To provide even lower latency, support is provided for the transmission of uplink control channels that include two or more HARQ-ACKs in a single time slot. User equipment can send HARQ-ACKs as quickly as possible in response to successful reception of a downlink shared channel, thereby ensuring lower latency. Summary of the Invention

[0010] Technical issues

[0011] An object of the embodiments of the present invention is to provide a method for transmitting a Physical Uplink Shared Channel (PUSCH) by a user equipment to a base station in a wireless communication system and the user equipment thereof.

[0012] Furthermore, another object of the present invention is to provide a method for allocating resources for periodically transmitting a PUSCH to a base station based on a configured grant, and a user equipment thereof.

[0013] In addition, another object of the present invention is to provide a method for activating / releasing a configuration for periodically transmitting a PUSCH to a base station based on a configured grant, and a user equipment thereof.

[0014] Technical Solution

[0015] A method for transmitting a physical uplink shared channel (PUSCH) by a user equipment to a base station in a wireless communication system includes: receiving a first physical downlink control channel (PDCCH) including first downlink control information (DCI) from the base station, the first DCI including a first specific identifier (ID) for releasing one or more configurations, the one or more configurations being configured for transmission of a PUSCH based on a configured grant, the PUSCH representing a channel periodically transmitted through resources repeatedly configured according to the configured grant, the first specific identifier indicating one or more configurations configured for transmission of the PUSCH; and releasing the one or more configurations indicated by the first specific identifier.

[0016] In addition, in the present invention, when multiple configurations are configured for transmission of PUSCH, the first specific identifier is indicated by the hybrid automatic repeat request (HARQ) process number (HARQ process number) field of the first DCI, and the HARQ process number field is used to identify one or more configurations among the multiple configurations.

[0017] In addition, in the present invention, the method further includes receiving configuration information for identifying one or more configurations, wherein the configuration information includes multiple identifiers corresponding to specific values ​​of the HARQ process number field, each of the multiple identifiers individually corresponds to one or more configurations, and when the HARQ process number field is indicated by a specific value, the one or more configurations corresponding to the multiple identifiers are released.

[0018] In addition, in the present invention, the first DCI is scrambled with the CS-RNTI and further includes a new data indicator (NDI) field indicating new data transmission, a redundancy version (RV) field, a modulation and coding scheme (MCS) field, and a frequency domain resource assignment (FDRA) field for resource allocation in the frequency domain.

[0019] In addition, in the present invention, when one configuration is configured for transmission of PUSCH, verification of DCI is determined based on the NDI field, RV field, MCS field, HARQ process number field, and FDRA field, and when multiple configurations are configured for transmission of PUSCH, verification of DCI is determined based on the NDI field, RV field, MCS field, and FDRA field in addition to the HARQ process number field.

[0020] Furthermore, in the present invention, whether the DCI indicates the release of one or more configurations is identified based on a value according to the type of the FDRA field.

[0021] In addition, in the present invention, when dynamic switching of the type of FDRA is determined according to the value of the most significant bit (MSB) of the FDRA field, the value of the FDRA field used to identify whether DCI indicates the release of one or more configurations varies depending on the type of FDRA.

[0022] In addition, in the present invention, the method further includes receiving configuration information for PUSCH transmission from the base station, wherein the configuration information includes an offset, a period, and a number of HARQ processes for determining a HARQ process number for PUSCH transmission.

[0023] Furthermore, in the present invention, the HARQ process number is determined by adding an offset to a value determined based on the slot number in a frame, the number of slots in each frame, the system frame number (SFN), the number of HARQ processes, and a cycle.

[0024] In addition, in the present invention, the method further includes: receiving configuration information for transmission of PUSCH; receiving a second PDCCH including a second DCI for scheduling resources for transmission of PUSCH based on the configuration information, the second DCI including a second specific identifier (ID) for activating a configuration configured for transmission of PUSCH, the second specific identifier (ID) indicating one or more configurations configured for transmission of PUSCH; activating one or more configurations indicated by the second specific identifier; and performing transmission of PUSCH through the allocated resources based on the activated one or more configurations.

[0025] In addition, in the present invention, the second DCI further includes the starting group indexes of the multiple resource groups used for transmission of the PUSCH and the lengths of the multiple resource groups.

[0026] In addition, the present invention provides a user equipment, including a communication module and a processor for controlling the communication module, wherein the processor: receives a first physical downlink control channel (PDCCH) including first downlink control information (DCI) from a base station, the first DCI including a first specific identifier (ID) for releasing one or more configurations, the one or more configurations being configured for transmission of a PUSCH based on a configured grant, the PUSCH representing a channel periodically transmitted through resources repeatedly configured according to the configured grant, the first specific identifier indicating one or more configurations configured for transmission of the PUSCH; and releases the one or more configurations indicated by the first specific identifier.

[0027] Beneficial effects

[0028] According to an embodiment of the present invention, according to a method for a user equipment to repeatedly send PUSCH to a base station, the target performance of a 5G wireless communication system to provide a low-latency, high-reliability service can be achieved by enabling the user equipment to repeatedly send PUSCH to the base station as quickly as possible.

[0029] Furthermore, the present invention has an effect of efficiently allocating resource block groups for periodic transmission of a PUSCH by allocating groups based on a configured grant via a starting group index and its length.

[0030] Furthermore, the present invention has an effect of efficiently activating / releasing a plurality of configurations for periodic transmission of a PUSCH based on a grant of a configuration by activating / releasing the configuration via one identifier.

[0031] Effects obtainable from the present disclosure are not limited to the above-mentioned effects, and other effects not mentioned can be clearly understood by those skilled in the art from the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 An example of a radio frame structure used in a wireless communication system is illustrated.

[0033] Figure 2 An example of a downlink (DL) / uplink (UL) slot structure in a wireless communication system is illustrated.

[0034] Figure 3 This is a diagram for explaining physical channels used in the 3GPP system and a typical signal transmission method using the physical channels.

[0035] Figure 4 Illustration of SS / PBCH blocks used for initial cell access in a 3GPP NR system.

[0036] Figure 5 Illustration of a process for transmitting control information and control channels in a 3GPP NR system.

[0037] Figure 6 Illustration of a control resource set (CORESET) in which a physical downlink control channel (PUCCH) can be transmitted in a 3GPP NR system.

[0038] Figure 7 A method for configuring a PDCCH search space in a 3GPP NR system is illustrated.

[0039] Figure 8 is a conceptual diagram illustrating carrier aggregation.

[0040] Figure 9 It is a diagram for explaining signal carrier communication and multi-carrier communication.

[0041] Figure 10 is a diagram illustrating an example in which a cross-carrier scheduling technology is applied.

[0042] Figure 11 is a block diagram illustrating a configuration of a user equipment and a base station according to an embodiment of the present invention.

[0043] Figure 12 is a diagram illustrating an example of an uplink grant to which an embodiment of the present invention can be applied.

[0044] Figure 13 is a diagram illustrating an example of grant-free initial transmission.

[0045] Figure 14 is a flowchart illustrating an example for transmitting and receiving a Physical Uplink Shared Channel (PUSCH) according to an embodiment of the present invention.

[0046] Figure 15 is a flowchart illustrating an example of a configuration for releasing transmission for a PUSCH according to an embodiment of the present invention.

[0047] Figure 16 is a diagram illustrating an example of a method for grouping resource blocks according to an embodiment of the present invention.

[0048] Figure 17 is a diagram illustrating a configuration example of a bandwidth part (BWP) according to an embodiment of the present invention.

[0049] Figure 18 is a flowchart illustrating an example of a method for releasing a configuration configured for transmission of a PUSCH by a user equipment according to an embodiment of the present invention.

[0050] Figure 19 is a flowchart illustrating an example of a method for releasing a configuration configured in a user equipment for transmission of a PUSCH by a base station according to an embodiment of the present invention. DETAILED DESCRIPTION

[0051] The terms used in this specification are generally used, as much as possible, based on the functions of the present invention. However, these terms may be changed according to the intentions, customs, and new technologies of those skilled in the art. In addition, in certain cases, there are terms arbitrarily selected by the applicant, and in such cases, their meanings will be described in the corresponding description of the present invention. Therefore, it is intended that the terms used in this specification should not be analyzed based solely on the name of the term, but should be analyzed based on the substantive meaning of the term and content throughout the specification.

[0052] Throughout the specification and the claims that follow, when it is described that an element is “connected” to another element, the element may be “directly connected” to the other element or “electrically connected” to the other element through a third element. In addition, unless explicitly described to the contrary, the word “include” will be understood to imply the inclusion of the elements stated and not the exclusion of any other elements. Furthermore, in some exemplary embodiments, limitations such as “greater than or equal to” or “less than or equal to” based on a specific threshold value may be appropriately replaced with “greater than” or “less than”, respectively.

[0053] The following technologies can be used in various wireless access systems: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier-FDMA (SC-FDMA), etc. CDMA can be implemented by wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented by wireless technologies such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented by wireless technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, Evolved UTRA (E-UTRA), etc. UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using Evolved UMTS Terrestrial Radio Access (E-UTRA), and LTE Advanced (A) is an evolved version of 3GPP LTE. 3GPP New Radio (NR) is a system designed separately from LTE / LTE-A, and is a system for supporting enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine type communication (mMTC) services that are requirements of IMT-2020. For clarity of description, 3GPP NR is mainly described, but the technical idea of ​​the present invention is not limited thereto.

[0054] Unless otherwise specified in this specification, a base station may refer to a next generation Node B (gNB) defined in 3GPP NR. In addition, unless otherwise specified, a terminal may refer to a user equipment (UE).

[0055] Although specific implementations are individually categorized into embodiments to aid understanding, these embodiments may be used in combination. In this disclosure, configuration of a user equipment may refer to configuration by a base station. Specifically, a base station may send a signal to a user equipment to set parameter values ​​used in the operation of the user equipment or the wireless communication system.

[0056] Figure 1 An example of a radio frame structure used in a wireless communication system is shown. Figure 1 , the radio frame (or radio frame) used in the 3GPP NR system may have a 10ms (Δf max N f / 100)*T c ) length. In addition, the wireless frame consists of 10 subframes (SFs) of equal size. Here, Δf max =480*10 3 Hz, N f =4096, T c =1 / (Δf ref *N f,ref ), Δf ref =15*10 3 Hz, and N f,ref =2048. Numbers from 0 to 9 can be assigned to 10 subframes within a radio frame. Each subframe is 1ms long and can include one or more time slots according to the subcarrier spacing. More specifically, in the 3GPP NR system, the subcarrier spacing that can be used is 15*2 μ kHz, and μ can have values ​​of μ=0, 1, 2, 3, 4 as subcarrier spacing configurations. That is, 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz can be used for subcarrier spacing. One subframe with a length of 1ms may include 2 μ In this case, the length of each time slot is 2 -μ ms. It can be set from 0 to 2 μ -1 are assigned to the 2 μ In addition, the time slots from 0 to 10*2 μ Numbers of -1 are assigned to time slots within a radio frame, respectively. Time resources may be distinguished by at least one of a radio frame number (also referred to as a radio frame index), a subframe number (also referred to as a subframe index), and a time slot number (or time slot index).

[0057] Figure 2 An example of a downlink (DL) / uplink (UL) slot structure in a wireless communication system is shown. In particular, Figure 2 The structure of the resource grid of the 3GPP NR system is shown. There is one resource grid for each antenna port. Figure 2 , a time slot includes multiple orthogonal frequency division multiplexing (OFDM) symbols in the time domain and multiple resource blocks (RBs) in the frequency domain. An OFDM symbol also refers to a symbol interval. Unless otherwise specified, an OFDM symbol may be referred to as a symbol. An RB includes 12 consecutive subcarriers in the frequency domain. Reference Figure 2, the signal transmitted from each time slot can be composed of N size,μ grid,x *N RB sc subcarriers and N slot symb Here, when the signal is a DL signal, x=DL, and when the signal is a UL signal, x=UL. N size,μ grid,x represents the number of resource blocks (RBs) according to the subcarrier spacing component μ (x is DL or UL), and N slot symb Indicates the number of OFDM symbols in a time slot. RB sc is the number of subcarriers constituting one RB and N RB sc = 12. The OFDM symbol may be called a cyclic shift OFDM (CP-OFDM) symbol or a discrete Fourier transform spread OFDM (DFT-s-OFDM) symbol according to a multiple access scheme.

[0058] The number of OFDM symbols included in one slot may vary depending on the length of the cyclic prefix (CP). For example, in the case of a normal CP, one slot includes 14 OFDM symbols, but in the case of an extended CP, one slot may include 12 OFDM symbols. In certain embodiments, the extended CP may be used only at a 60 kHz subcarrier spacing. Figure 2 In the embodiment, for the convenience of description, one time slot is configured with 14 OFDM symbols as an example, but the embodiments of the present disclosure can be applied to time slots with different numbers of OFDM symbols in a similar manner. Figure 2 , each OFDM symbol includes N in the frequency domain size,μ grid,x *N RB sc Subcarriers can be divided into data subcarriers for data transmission, reference signal subcarriers for reference signal transmission, and guard bands. The carrier frequency is also called the center frequency (fc).

[0059] An RB can be composed of N in the frequency domain RB sc For reference, a resource configured with one OFDM symbol and one subcarrier is referred to as a resource element (RE) or tone. Thus, one RB can be configured with N slot symb *N RB scresource elements. Each resource element in the resource grid can be uniquely defined by a pair of indices (k, l) in a time slot. k can be a value from 0 to N in the frequency domain. size,μ grid,x *N RB sc –1 is the assigned index, and l can be from 0 to N in the time domain slot symb –1 The assigned index.

[0060] In order for a UE to receive signals from or transmit signals to a base station, the UE's time / frequency may be synchronized with the base station's time / frequency. This is because when the base station and UE are synchronized, the UE can determine the time and frequency parameters necessary to demodulate the downlink signal and transmit the uplink signal at the correct time.

[0061] Each symbol of a radio frame used in time division duplex (TDD) or unpaired spectrum may be configured with at least one of a DL symbol, a UL symbol, and a flexible symbol. A radio frame used as a DL carrier in frequency division duplex (FDD) or paired spectrum may be configured with a DL symbol or a flexible symbol, while a radio frame used as a UL carrier may be configured with a UL symbol or a flexible symbol. In a DL symbol, DL transmission is possible, but UL transmission is not possible. In a UL symbol, UL transmission is possible, but DL transmission is not possible. A flexible symbol may be determined to be used as DL or UL based on a signal.

[0062] Information about the type of each symbol, that is, information indicating any one of a DL symbol, a UL symbol, and a flexible symbol, may be configured with a cell-specific or common radio resource control (RRC) signal. In addition, information about the type of each symbol may be additionally configured with a UE-specific or dedicated RRC signal. The base station notifies, by using a cell-specific RRC signal, i) the period of the cell-specific time slot configuration, ii) the number of time slots having only DL symbols from the beginning of the period of the cell-specific time slot configuration, iii) the number of DL symbols from the first symbol of the time slot immediately following the time slot having only DL symbols, iv) the number of time slots having only UL symbols from the end of the period of the cell-specific time slot configuration, and v) the number of UL symbols from the last symbol of the time slot immediately preceding the time slot having only UL symbols. Here, a symbol not configured with any one of the UL symbol and the DL symbol is a flexible symbol.

[0063] When information on symbol types is configured with UE-specific RRC signals, the base station can signal whether the flexible symbol is a DL symbol or a UL symbol with cell-specific RRC signals. In this case, the UE-specific RRC signals cannot change the DL symbols or UL symbols configured with cell-specific RRC signals into another symbol type. The UE-specific RRC signals can signal the number of DL symbols among the N symbols of the corresponding time slot for each time slot and the number of UL symbols among the N symbols of the corresponding time slot. In this case, the DL symbols of a time slot can be continuously configured as the first symbol to the i-th symbol of the time slot. In addition, the UL symbols of a time slot can be continuously configured as the j-th symbol to the last symbol of the time slot (where i < j). In a time slot, a symbol not configured with any of the UL symbols and DL symbols is a flexible symbol. slot symb symbols of the corresponding time slot and the number of UL symbols among the N slot symb symbols of the corresponding time slot. In this case, the DL symbols of a time slot can be continuously configured as the first symbol to the i-th symbol of the time slot. In addition, the UL symbols of a time slot can be continuously configured as the j-th symbol to the last symbol of the time slot (where i < j). In a time slot, a symbol not configured with any of the UL symbols and DL symbols is a flexible symbol.

[0064] Figure 3 is a diagram for explaining physical channels used in a 3GPP system (e.g., NR) and a typical signal transmission method using the physical channels.

[0065] If the power of the UE is turned on or the UE camps on a new cell, the UE performs initial cell search (S101). Specifically, the UE can synchronize with the BS during the initial cell search. To this end, the UE can receive a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station to synchronize with the base station and obtain information such as the cell ID. Thereafter, the UE can receive a physical broadcast channel from the base station and obtain broadcast information in the cell.

[0066] When the initial cell search is completed, the UE receives a physical downlink shared channel (PDSCH) according to the physical downlink control channel (PDCCH) and the information in the PDCCH, enabling the UE to obtain more specific system information than the system information obtained through the initial cell search (S102).

[0067] Here, the system information received by the user equipment is cell-common system information for the normal operation of the user equipment in the physical layer in radio resource control (RRC) and is referred to as remaining system information or system information block (SIB)1.

[0068] When the UE initially accesses the base station or does not have radio resources for signal transmission, the UE can perform a random access procedure on the base station (operations S103 to S106). First, the UE is able to send a preamble through a physical random access channel (PRACH) (S103) and receive a response message for the preamble from the base station through a PDCCH and the corresponding PDSCH (S104). When the UE receives a valid random access response message, the UE sends data including the UE's identifier, etc. to the base station through a physical uplink shared channel (PUSCH) indicated by the UL grant sent from the base station through the PDCCH (S105). Next, the UE waits for the reception of the PDCCH as an indication of the base station for conflict resolution. If the UE successfully receives the PDCCH through the UE's identifier (S106), the random access procedure is terminated. The user equipment can obtain the terminal-specific system information required for the user equipment to operate correctly in the physical layer in the RRC layer during the random access procedure. When the user equipment obtains the terminal-specific system information from the RRC layer, the user equipment enters RRC connected mode.

[0069] The RRC layer is used to generate or manage messages between user equipment and the radio access network (RAN). More specifically, the base station and user equipment can perform, in the RRC layer, broadcasting cell system information required by all user equipment in the cell, managing the transmission of paging messages, mobility management, handover, user equipment measurement reporting and its control, and storage management including user equipment capability management and device management. Generally, since the update of the signal transmitted in the RRC layer (hereinafter referred to as the RRC signal) is longer than the transmission / reception period (i.e., transmission time interval (TTI)) in the physical layer, the RRC signal can be maintained and unchanged for a long period.

[0070] After the above process, the UE receives PDCCH / PDSCH (S107) and sends physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) (S108) as a general UL / DL signal transmission process. In particular, the UE can receive downlink control information (DCI) through PDCCH. DCI may include control information such as resource allocation information for the UE. In addition, the format of DCI may vary according to the intended use. The uplink control information (UCI) sent by the UE to the base station through UL includes DL / UL ACK / NACK signals, channel quality indicator (CQI), precoding matrix index (PMI), rank indicator (RI), etc. Here, CQI, PMI and RI may be included in channel state information (CSI). In the 3GPP NR system, the UE can send control information such as the above-mentioned HARQ-ACK and CSI through PUSCH and / or PUCCH.

[0071] Figure 4 The figure shows the SS / PBCH blocks used for initial cell access in a 3GPP NR system. When the power is turned on or when the UE wants to access a new cell, it can obtain time and frequency synchronization with the cell and perform an initial cell search procedure. The UE can detect the physical cell identity N of the cell during the cell search procedure. cell ID To this end, the UE may receive synchronization signals, such as a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), from the base station and synchronize with the base station. In this case, the UE may obtain information such as a cell identity (ID).

[0072] refer to Figure 4 (a) of FIG. 1 , the synchronization signal (SS) will be described in more detail. The synchronization signal can be classified into PSS and SSS. PSS can be used to obtain time domain synchronization and / or frequency domain synchronization, such as OFDM symbol synchronization and time slot synchronization. SSS can be used to obtain frame synchronization and cell group ID. Figure 4 (a) and Table 2, the SS / PBCH block can be configured with 20 consecutive RBs (=240 subcarriers) on the frequency axis and can be configured with 4 consecutive OFDM symbols on the time axis. In this case, in the SS / PBCH block, the PSS is transmitted in the first OFDM symbol and the SSS is transmitted in the third OFDM symbol through the 56th to 182nd subcarriers. Here, the lowest subcarrier index of the SS / PBCH block is numbered from 0. In the first OFDM symbol in which the PSS is transmitted, the base station does not transmit signals through the remaining subcarriers, i.e., the 0th to 55th subcarriers and the 183rd to 239th subcarriers. In addition, in the third OFDM symbol in which the SSS is transmitted, the base station does not transmit signals through the 48th to 55th subcarriers and the 183rd to 191st subcarriers. The base station transmits the physical broadcast channel (PBCH) through the remaining REs in the SS / PBCH block except for the above signals.

[0073] [Table 1]

[0074]

[0075] The SS allows a total of 1008 unique physical layer cell IDs to be grouped into 336 physical layer cell identifier groups, each group including three unique identifiers, through a combination of three PSSs and SSSs, specifically so that each physical layer cell ID will be part of only one physical layer cell identifier group. cell ID =3N (1) ID +N (2) IDThe physical layer cell identifier group can be indicated by an index N ranging from 0 to 335. (1) ID and an index N ranging from 0 to 2 indicating a physical layer identifier in the physical layer cell identifier group (2) ID Uniquely defined. The UE can detect the PSS and identify one of the three unique physical layer identifiers. In addition, the UE can detect the SSS and identify one of the 336 physical layer cell IDs associated with the physical layer identifier. In this case, the sequence d of the PSS PSS (n) are as follows.

[0076] d PSS (n) = 1-2x(m)

[0077]

[0078] 0≤n<127

[0079] Here, x(i+7)=(x(i+4)+x(i)) mod 2 and is given as

[0080] [x(6) x(5) x(4) x(3) x(2) x(1) x(0)]-[1 1 1 0 1 1 0]

[0081] In addition, the sequence d of SSS SSS (n) are as follows.

[0082] d SSS (n)=[1-2x0((n+m0)mod127)][1-2x1((n+m1)mod127)]

[0083]

[0084]

[0085] 0≤n<127

[0086] here, and is given as

[0087] [x0(6) x0(5) x0(4) x0(3) x0(2) x0(1) x0(0)]=[0 0 0 0 0 0 1]

[0088] [x1(6) x1(5) x1(4) x1(3) x1(2) x1(1) x1(0)]=[0 0 0 0 0 0 1]

[0089] A radio frame having a length of 10ms can be divided into two half-frames having a length of 5ms. Figure 4 (b) of the Serial Number Protocol (SN) will describe the time slot in which the SS / PBCH block is transmitted in each half frame. The time slot in which the SS / PBCH block is transmitted may be any of Cases A, B, C, D, and E. In Case A, the subcarrier spacing is 15 kHz and the starting time point of the SS / PBCH block is the ({2,8}+14*n)th symbol. In this case, at a carrier frequency of 3 GHz or lower, n=0 or 1. In addition, at a carrier frequency higher than 3 GHz and lower than 6 GHz, n=0, 1, 2, 3 may be used. In Case B, the subcarrier spacing is 30 kHz and the starting time point of the SS / PBCH block is {4,8,16,20}+28*n. In this case, at a carrier frequency of 3 GHz or lower, n=0. In addition, at a carrier frequency higher than 3 GHz and lower than 6 GHz, n=0, 1 may be used. In Case C, the subcarrier spacing is 30 kHz and the starting time point of the SS / PBCH block is the ({2,8}+14*n)th symbol. In this case, at a carrier frequency of 3 GHz or lower, n = 0 or 1. In addition, at a carrier frequency higher than 3 GHz and lower than 6 GHz, n can be 0, 1, 2, 3. In case D, the subcarrier spacing is 120 kHz and the starting time point of the SS / PBCH block is the ({4, 8, 16, 20} + 28 * n)th symbol. In this case, at a carrier frequency of 6 GHz or higher, n = 0, 1, 2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, 18. In case E, the subcarrier spacing is 240 kHz and the starting time point of the SS / PBCH block is the ({8, 12, 16, 20, 32, 36, 40, 44} + 56 * n)th symbol. In this case, at a carrier frequency of 6 GHz or higher, n = 0, 1, 2, 3, 5, 6, 7, 8.

[0090] Figure 5 This figure illustrates the process of transmitting control information and control channels in the 3GPP NR system. Figure 5(a) The base station may add a cyclic redundancy check (CRC) masked (e.g., XORed) with a radio network temporary identifier (RNTI) to control information (e.g., downlink control information (DCI)) (S202). The base station may scramble the CRC with an RNTI value determined according to the purpose / target of each control information. The common RNTI used by one or more UEs can include at least one of a system information RNTI (SI-RNTI), a paging RNTI (P-RNTI), a random access RNTI (RA-RNTI), and a transmit power control RNTI (TPC-RNTI). In addition, the UE-specific RNTI may include at least one of a cell temporary RNTI (C-RNTI) and a CS-RNTI. Thereafter, the base station may perform rate matching according to the amount of resources used for PDCCH transmission after performing channel coding (e.g., polarity coding) (S204) (S206). Thereafter, the base station may multiplex DCI based on a PDCCH structure based on control channel elements (CCEs) (S208). In addition, the base station may apply additional processes such as scrambling, modulation (e.g., QPSK), interleaving, etc. to the multiplexed DCI (S210), and then map the DCI to the resources to be transmitted. CCE is the basic resource unit for PDCCH, and one CCE may include multiple (e.g., six) resource element groups (REGs). One REG may be configured with multiple (e.g., 12) REs. The number of CCEs used for one PDCCH may be defined as an aggregation level. In a 3GPP NR system, aggregation levels of 1, 2, 4, 8, or 16 may be used. Figure 5 B is a diagram related to CCE aggregation levels and multiplexing of PDCCHs, and illustrates the type of CCE aggregation level for one PDCCH and CCEs transmitted in the control region accordingly.

[0091] Figure 6 The figure shows a control resource set (CORESET) in which the physical downlink control channel (PUCCH) can be transmitted in a 3GPP NR system. A CORESET is a time-frequency resource in which a PDCCH (i.e., a control signal for a UE) is transmitted. In addition, a search space to be described later can be mapped to one CORESET. Therefore, the UE can monitor the time-frequency domain designated as the CORESET instead of monitoring all frequency bands for PDCCH reception, and decode the PDCCH mapped to the CORESET. The base station can configure one or more CORESETs for each cell to the UE. The CORESET can be configured with a maximum of three consecutive symbols on the time axis. In addition, the CORESET can be configured in units of six consecutive PRBs on the frequency axis. Figure 5In the embodiment of FIG, CORESET#1 is configured with continuous PRBs, while CORESET#2 and CORESET#3 are configured with discontinuous PRBs. A CORESET can be located in any symbol in a time slot. For example, in Figure 5 In the embodiment of FIG. 5 , CORESET#1 starts at the first symbol of the time slot, CORESET#2 starts at the fifth symbol of the time slot, and CORESET#9 starts at the ninth symbol of the time slot.

[0092] Figure 7 The figure illustrates a method for setting a PDCCH search space in a 3GPP NR system. In order to send a PDCCH to a UE, each CORESET may have at least one search space. In an embodiment of the present disclosure, a search space is a set of all time-frequency resources (hereinafter referred to as PDCCH candidates) that can be used to send a PDCCH of a UE. The search space may include a common search space that UEs of 3GPP NR are required to search together and a terminal-specific search space or a UE-specific search space that a specific UE is required to search. In the common search space, the UE may monitor a PDCCH that is set so that all UEs in a cell belonging to the same base station search together. In addition, a UE-specific search space may be set for each UE so that the UE monitors the PDCCH allocated to each UE at a search space position that is different according to the UE. In the case of a UE-specific search space, since a limited control region to which a PDCCH can be allocated, the search spaces between UEs may partially overlap and be allocated. Monitoring the PDCCH includes blind decoding the PDCCH candidates in the search space. When blind decoding is successful, it can be expressed as PDCCH is (successfully) detected / received, and when blind decoding fails, it can be expressed as PDCCH is not detected / received or is not successfully detected / received.

[0093] For ease of explanation, a PDCCH that is scrambled with a group common (GC) RNTI previously known to a UE in order to transmit DL control information to one or more UEs is referred to as a group common (GC) PDCCH or a common PDCCH. Furthermore, a PDCCH that is scrambled with the RNTI of a specific terminal already known to a specific UE in order to transmit UL scheduling information or DL ​​scheduling information to a specific UE is referred to as a UE-specific PDCCH. A common PDCCH may be included in a common search space, and a UE-specific PDCCH may be included in a common search space or a UE-specific PDCCH.

[0094] The base station can signal each UE or UE group with information related to resource allocation of the paging channel (PCH) and downlink shared channel (DL-SCH) as transport channels (i.e., DL grant) or information related to resource allocation of the uplink shared channel (UL-SCH) and hybrid automatic repeat request (HARQ) (i.e., UL grant) through the PDCCH. The base station can transmit PCH transport blocks and DL-SCH transport blocks through the PDSCH. The base station can transmit data excluding specific control information or specific service data through the PDSCH. In addition, the UE can receive data excluding specific control information or specific service data through the PDSCH.

[0095] The base station can include information in the PDCCH about which UE (one or more UEs) the PDSCH data is to be sent and how the PDSCH data will be received and decoded by the corresponding UE, and send the PDCCH. For example, assume that the DCI sent through a specific PDCCH is CRC-masked with RNTI "A", and the DCI indicates that the PDSCH is allocated to radio resource "B" (e.g., frequency position) and indicates transmission format information "C" (e.g., transport block size, modulation scheme, coding information, etc.). The UE monitors the PDCCH using the RNTI information that the UE has. In this case, if there is a UE that performs blind decoding on the PDCCH using the "A" RNTI, the UE receives the PDCCH and receives the PDSCH indicated by "B" and "C" through the information of the received PDCCH.

[0096] Table 2 shows an embodiment of a physical uplink control channel (PUCCH) used in a wireless communication system.

[0097] [Table 2]

[0098] PUCCH format OFDM symbol length Number of bits 0 1-2 ≤2 1 4-14 ≤2 2 1-2 >2 3 4-14 >2 4 4-14 >2

[0099] The PUCCH may be used to transmit the following UL control information (UCI).

[0100] - Scheduling Request (SR): information for requesting UL UL-SCH resources.

[0101] -HARQ-ACK: A response to the PDCCH (indicating a DL SPS release) and / or a response to a DL transport block (TB) on the PDSCH. HARQ-ACK indicates whether the information sent on the PDCCH or PDSCH is received. The HARQ-ACK response includes a positive ACK (abbreviated as ACK), a negative ACK (hereinafter referred to as NACK), a discontinuous transmission (DTX), or NACK / DTX. Here, the term HARQ-ACK is used in combination with HARQ-ACK / NACK and ACK / NACK. Generally, ACK can be represented by a bit value of 1, while NACK can be represented by a bit value of 0.

[0102] Channel State Information (CSI): Feedback information about the DL channel. The UE generates this information based on the CSI-Reference Signal (RS) transmitted by the base station. Multiple-Input Multiple-Output (MIMO)-related feedback information includes the Rank Indicator (RI) and the Precoding Matrix Indicator (PMI). The CSI can be divided into CSI Part 1 and CSI Part 2 based on the information indicated by the CSI.

[0103] In the 3GPP NR system, five PUCCH formats can be used to support various service scenarios, various channel environments and frame structures.

[0104] PUCCH format 0 is a format capable of transmitting 1-bit or 2-bit HARQ-ACK information or SR. PUCCH format 0 can be transmitted through one or two OFDM symbols on the time axis and one PRB on the frequency axis. When PUCCH format 0 is transmitted through two OFDM symbols, the same sequence on the two symbols can be transmitted through different RBs. Here, the sequence can be a sequence that is cyclically shifted (CS) from the basic sequence used in PUCCH format 0. In this way, the user equipment can obtain frequency diversity gain. In more detail, the user equipment can obtain frequency diversity gain according to M bit Bit UCI(M bit =1 or 2) to determine the cyclic shift (CS) value m cs In addition, by determining the CS value m cs A sequence obtained by cyclically shifting a base sequence having a length of 12 can be mapped to 12 REs of one OFDM symbol and one RB for transmission. bit =1, the 1-bit UCI 0 and 1 can be mapped to two cyclic shift sequences with a cyclic shift value difference of 6. In addition, when M bit =2, the 2-bit UCI 00, 01, 11 and 10 can be mapped to four cyclic shift sequences with cyclic shift values ​​differing by 3 respectively.

[0105] PUCCH format 1 can deliver 1-bit or 2-bit HARQ-ACK information or SR. PUCCH format 1 can be transmitted through continuous OFDM symbols on the time axis and one PRB on the frequency axis. Here, the number of OFDM symbols occupied by PUCCH format 1 can be one of 4 to 14. More specifically, M bit =1 UCI is BPSK modulated. The UE can use quadrature phase shift keying (QPSK) to modulate M bit =2 for modulation. The signal is obtained by multiplying the modulated complex-valued symbol d(0) by a sequence of length 12. In this case, the sequence may be a base sequence for PUCCH format 0. The UE extends the even-numbered OFDM symbols to which PUCCH format 1 is allocated by a time axis orthogonal cover code (OCC) to transmit the obtained signal. PUCCH format 1 determines the maximum number of different UEs multiplexed in one RB according to the length of the OCC to be used. The demodulation reference signal (DMRS) may be extended with the OCC and mapped to the odd-numbered OFDM symbols of PUCCH format 1.

[0106] PUCCH format 2 can deliver more than 2 bits of UCI. PUCCH format 2 can be sent through one or two OFDM symbols on the time axis and one or more RBs on the frequency axis. When PUCCH format 2 is sent in two OFDM symbols, the sequences sent in different RBs of the two OFDM symbols can be the same as each other. Here, the sequence can be a plurality of modulated complex-valued symbols d(0), ..., d(M symbol-1 ). Here, M symbol It can be M bit / 2. Through this, the UE can obtain frequency diversity gain. More specifically, for M bit bits UCI (M bit >2) Bit-level scrambling, QPSK modulation, and mapping to RBs of one or two OFDM symbols. Here, the number of RBs can be one from 1 to 16.

[0107] PUCCH format 3 or PUCCH format 4 can deliver more than 2 bits of UCI. PUCCH format 3 or PUCCH format 4 can be transmitted through continuous OFDM symbols on the time axis and one PRB on the frequency axis. The number of OFDM symbols occupied by PUCCH format 3 or PUCCH format 4 can be one of 4 to 14. Specifically, the UE uses e / 2-binary phase shift keying (BPSK) or QPSK for M bit bits UCI (M bit >2) is modulated to generate complex-valued symbols d(0) to d(M symb-1). Here, when π / 2-BPSK is used, M symb =M bit , and when using QPSK, M symb =M bit / 2. The UE may not apply block-based extension to PUCCH format 3. However, the UE may apply block-based extension to one RB (i.e., 12 subcarriers) using a PreDFT-OCC length of 12, allowing PUCCH format 4 to have two or four multiplexing capabilities. The UE performs transmit precoding (or DFT precoding) on ​​the extended signal and maps it to each RE to transmit the extended signal.

[0108] In this case, the number of RBs occupied by PUCCH format 2, PUCCH format 3, or PUCCH format 4 can be determined based on the length of the UCI transmitted by the UE and the maximum coding rate. When the UE uses PUCCH format 2, the UE can transmit HARQ-ACK information and CSI information together through the PUCCH. When the number of RBs that the UE can transmit is greater than the maximum number of RBs that can be used by PUCCH format 2, PUCCH format 3, or PUCCH format 4, the UE can transmit only the remaining UCI information without transmitting some UCI information based on the priority of the UCI information.

[0109] PUCCH format 1, PUCCH format 3, or PUCCH format 4 can be configured via RRC signaling to indicate frequency hopping within a time slot. When frequency hopping is configured, the index of the RB to be frequency hopped can be configured via RRC signaling. When PUCCH format 1, PUCCH format 3, or PUCCH format 4 is transmitted via N OFDM symbols on the time axis, the first hop can have floor (N / 2) OFDM symbols and the second hop can have ceiling (N / 2) OFDM symbols.

[0110] PUCCH format 1, PUCCH format 3, or PUCCH format 4 can be configured to be repeatedly transmitted in multiple time slots. In this case, the number K of time slots in which the PUCCH is repeatedly transmitted can be configured through RRC signaling. The repeatedly transmitted PUCCH must start at an OFDM symbol at a constant position in each time slot and have a constant length. When one of the OFDM symbols of the time slot in which the UE should transmit the PUCCH is indicated as a DL symbol through RRC signaling, the UE may not transmit the PUCCH in the corresponding time slot and delay the transmission of the PUCCH to the next time slot to transmit the PUCCH.

[0111] Meanwhile, in 3GPP NR systems, user equipment can perform transmission / reception using a bandwidth that is less than or equal to the bandwidth of a carrier (or cell). To this end, the user can receive a configuration of a bandwidth part (BWP) configured with a portion of contiguous bandwidth within the carrier bandwidth. User equipment operating in TDD or unpaired spectrum can receive configurations of up to four DL / UL BWP pairs in one carrier (or cell). Furthermore, the user equipment can activate one DL / UL BWP pair. User equipment operating in FDD or paired spectrum can receive up to four DL BWPs in a downlink carrier (or cell) and up to four UL BWPs in an uplink carrier (or cell). For each carrier (or cell), the user equipment can activate one DL BWP and one UL BWP. The user equipment may not receive or transmit in time-frequency resources other than the activated BWP. The activated BWP may be referred to as an active BWP.

[0112] The base station can indicate the activated BWP among the BWPs configured for the user equipment through downlink control information (DCI). The BWP indicated by the DCI is activated, while the other configured BWPs are deactivated. In a carrier (or cell) operating in accordance with TDD, the base station can add a bandwidth part indicator (BPI) indicating the BWP to be activated to the DCI scheduling the PDSCH or PUSCH to change the DL / UL BWP pair of the user equipment. The user equipment can receive the DCI scheduling the PDSCH or PUSCH and identify the DL / UL BWP pair activated based on the BPI. In the case of a downlink carrier (or cell) operating in accordance with FDD, the base station can add the BPI indicating the BWP to be activated to the DCI scheduling the PDSCH to change the base station's DL BWP. In the case of an uplink carrier (or cell) operating in accordance with FDD, the base station can add the BPI indicating the BWP to be activated to the DCI scheduling the PUSCH to change the base station's UL BWP.

[0113] Figure 8 is a conceptual diagram illustrating carrier aggregation.

[0114] Carrier aggregation is a method in which a UE uses multiple frequency blocks or (logically) cells configured with UL resources (or component carriers) and / or DL ​​resources (or component carriers) as a large logical frequency band, allowing the wireless communication system to use a wider frequency band. A component carrier may also be referred to as a primary cell (PCell), a secondary cell (SCell), or a primary SCell (PScell). However, hereinafter, for convenience of description, the term "component carrier" is used.

[0115] refer to Figure 8As an example of a 3GPP NR system, the entire system band may include up to 16 component carriers, and each component carrier may have a bandwidth of up to 400 MHz. A component carrier may include one or more physically contiguous subcarriers. Figure 8 , each component carrier is shown to have the same bandwidth, but this is merely an example, and each component carrier may have a different bandwidth. In addition, although each component carrier is shown as being adjacent to each other on the frequency axis, the drawings are shown in a logical concept, and each component carrier may be physically adjacent to each other, or may be spaced apart.

[0116] A different center frequency can be used for each component carrier. Alternatively, a common center frequency can be used in physically adjacent component carriers. Figure 8 In the embodiment of FIG5 , all component carriers are physically adjacent, then center frequency A can be used in all component carriers. Alternatively, assuming that the respective component carriers are not physically adjacent to each other, center frequency A and center frequency B can be used in each component carrier.

[0117] When the total system frequency band is extended by carrier aggregation, the frequency band used to communicate with each UE can be defined in units of component carriers. UE A can use 100 MHz as the total system frequency band and use all five component carriers to perform communication. UEs B1 to B5 can use only 20 MHz bandwidth and use one component carrier to perform communication. UEs C1 and C2 can each use 40 MHz bandwidth and use two component carriers to perform communication. These two component carriers can be logically / physically adjacent or non-adjacent. UE C1 represents the case of using two non-adjacent component carriers, while UE C2 represents the case of using two adjacent component carriers.

[0118] Figure 9 It is a diagram for explaining signal carrier communication and multi-carrier communication. In particular, Figure 9 (a) shows a single carrier subframe structure and Figure 9 (b) shows the multi-carrier subframe structure.

[0119] refer to Figure 9 (a), in FDD mode, a general wireless communication system can perform data transmission or reception through one DL frequency band and one UL frequency band corresponding thereto. In another specific embodiment, in TDD mode, a wireless communication system can divide a radio frame into UL time units and DL time units in the time domain, and perform data transmission or reception through the UL / DL time units. Figure 9(b) Three 20 MHz component carriers (CCs) can be aggregated into each of the UL and DL, enabling support of a 60 MHz bandwidth. Each CC may be adjacent or non-adjacent to each other in the frequency domain. Figure 9 (b) shows the case where the bandwidth of the UL CC and the bandwidth of the DL CC are the same and symmetrical, but the bandwidth of each CC can be determined independently. In addition, asymmetric carrier aggregation with different numbers of UL CCs and DL CCs is possible. The DL / UL CC assigned / configured to a specific UE through RRC can be called the serving DL / UL CC for the specific UE.

[0120] The base station can perform communication with the UE by activating some or all of the UE's serving CCs or deactivating some CCs. The base station can change the CCs to be activated / deactivated and change the number of CCs to be activated / deactivated. If the base station allocates CCs available to the UE as cell-specific or UE-specific, at least one of the allocated CCs will not be deactivated unless the CC allocation for the UE is completely reconfigured or the UE is handed over. One CC that is not deactivated by the UE is called a primary CC (PCC) or primary cell (PCell), while a CC that the base station can freely activate / deactivate is called a secondary CC (SCC) or secondary cell (SCell).

[0121] At the same time, 3GPP NR uses the concept of cells to manage radio resources. A cell is defined as a combination of DL resources and UL resources, that is, a combination of DL CCs and UL CCs. A cell can be configured with DL resources alone or a combination of DL resources and UL resources. When carrier aggregation is supported, the link between the carrier frequency of the DL resources (or DL ​​CC) and the carrier frequency of the UL resources (or UL CC) can be indicated by system information. The carrier frequency refers to the center frequency of each cell or CC. The cell corresponding to the PCC is called the PCell, while the cell corresponding to the SCC is called the SCell. The carrier corresponding to the PCell in the DL is the DL PCC, while the carrier corresponding to the PCell in the UL is the UL PCC. Similarly, the carrier corresponding to the SCell in the DL is the DL SCC, while the carrier corresponding to the SCell in the UL is the UL SCC. Depending on the UE capabilities, a serving cell can be configured with one PCell and zero or more SCells. In the case of a UE in the RRC_CONNECTED state but not configured for carrier aggregation or not supporting carrier aggregation, there is only one serving cell configured with only the PCell.

[0122] As described above, the term "cell" used in carrier aggregation is distinguished from the term "cell" which refers to a geographical area where communication services are provided by a base station or an antenna group. That is, a component carrier may also be referred to as a scheduling cell, a scheduled cell, a primary cell (PCell), a secondary cell (SCell), or a primary SCell (PScell). However, to distinguish between cells representing a geographical area and cells in carrier aggregation, in this disclosure, cells in carrier aggregation are referred to as CCs, and cells in a geographical area are referred to as cells.

[0123] Figure 10 is a diagram showing an example in which cross-carrier scheduling technology is applied. When cross-carrier scheduling is set, the control channel sent through the first CC can use the carrier indicator field (CIF) to schedule the data channel sent through the first CC or the second CC. The CIF is included in the DCI. In other words, a scheduling cell is set, and the DL grant / UL grant sent in the PDCCH area of ​​the scheduling cell schedules the PDSCH / PUSCH of the scheduled cell. That is, there is a search area for multiple component carriers in the PDCCH area of ​​the scheduling cell. The PCell can basically be a scheduling cell, and a specific SCell can be designated as a scheduling cell by an upper layer.

[0124] exist Figure 10 In the embodiment of the present invention, it is assumed that three DL CCs are merged. Here, it is assumed that DL component carrier #0 is DL PCC (or PCell), and DL component carrier #1 and DL component carrier #2 are DL SCC (or SCell). In addition, it is assumed that DL PCC is set as a PDCCH monitoring CC. When cross-carrier scheduling is not configured through UE-specific (or UE group-specific or cell-specific) higher layer signaling, CIF is disabled, and each DL CC is able to send only the PDCCH for scheduling its PDSCH without CIF according to the NR PDCCH rule (non-cross-carrier scheduling, self-carrier scheduling). At the same time, if cross-carrier scheduling is configured through UE-specific (or UE group-specific or cell-specific) higher layer signaling, CIF is enabled, and a specific CC (e.g., DL PCC) can use CIF to send not only the PDCCH for scheduling the PDSCH of DL CC A but also the PDCCH for scheduling the PDSCH of another CC (cross-carrier scheduling). On the other hand, PDCCH is not sent in another DL CC. Therefore, the UE monitors the PDCCH not including the CIF to receive the self-carrier scheduled PDSCH, or monitors the PDCCH including the CIF to receive the cross-carrier scheduled PDSCH according to whether cross-carrier scheduling is configured for the UE.

[0125] on the other hand, Figure 9 and Figure 10 The subframe structure of the 3GPP LTE-A system is shown in the figure, and the same or similar configuration can be applied to the 3GPP NR system. However, in the 3GPP NR system, Figure 9 and Figure 10 The subframes can be replaced by time slots.

[0126] Figure 11 is a block diagram showing the configuration of a UE and a base station according to an embodiment of the present disclosure. In an embodiment of the present disclosure, the UE can be implemented using various types of wireless communication devices or computing devices that are guaranteed to be portable and mobile. The UE may be referred to as a user equipment (UE), a station (STA), a mobile subscriber (MS), etc. In addition, in an embodiment of the present disclosure, the base station controls and manages a cell (e.g., a macro cell, a femto cell, a pico cell, etc.) corresponding to a service area, and performs functions such as signal transmission, channel designation, channel monitoring, self-diagnosis, and relaying. The base station may be referred to as a next-generation node B (gNB) or an access point (AP).

[0127] As shown in the drawing, the UE 100 according to an embodiment of the present disclosure may include a processor 110 , a communication module 120 , a memory 130 , a user interface 140 , and a display unit 150 .

[0128] First, the processor 110 can execute various instructions or processes within the UE 100 and process data. In addition, the processor 110 can control the overall operation of each unit comprising the UE 100 and can control the transmission / reception of data between the units. Here, the processor 110 can be configured to perform operations according to the embodiments described in the present disclosure. For example, the processor 110 can receive time slot configuration information, determine a time slot configuration based on the time slot configuration information, and perform communication according to the determined time slot configuration.

[0129] Next, the communication module 120 may be an integrated module that performs wireless communication using a wireless communication network and performs wireless LAN access using a wireless LAN. To this end, the communication module 120 may include a plurality of network interface cards (NICs) such as cellular communication interface cards 121 and 122 and an unlicensed band communication interface card 123 in an internal or external form. In the drawings, the communication module 120 is shown as an integrally integrated module, but unlike the drawings, each network interface card can be independently arranged according to circuit configuration or usage.

[0130] The cellular communication interface card 121 can transmit or receive radio signals with at least one of the base station 200, an external device, and a server using a mobile communication network and provide cellular communication services in a first frequency band based on instructions from the processor 110. According to an embodiment, the cellular communication interface card 121 may include at least one NIC module that uses a frequency band less than 6 GHz. The at least one NIC module of the cellular communication interface card 121 can independently perform cellular communication with at least one of the base station 200, an external device, and a server in a frequency band less than 6 GHz supported by the corresponding NIC module in accordance with a cellular communication standard or protocol.

[0131] The cellular communication interface card 122 can transmit or receive radio signals with at least one of the base station 200, an external device, and a server using a mobile communication network and provide cellular communication services in the second frequency band based on instructions from the processor 110. According to an embodiment, the cellular communication interface card 122 may include at least one NIC module that uses a frequency band greater than 6 GHz. The at least one NIC module of the cellular communication interface card 122 can independently perform cellular communication with at least one of the base station 200, an external device, and a server in a frequency band greater than 6 GHz supported by the corresponding NIC module in accordance with a cellular communication standard or protocol.

[0132] The unlicensed band communication interface card 123 transmits or receives radio signals with at least one of the base station 200, an external device, and a server using the third frequency band as the unlicensed frequency band, and provides unlicensed band communication services based on instructions from the processor 110. The unlicensed band communication interface card 123 may include at least one NIC module that uses the unlicensed frequency band. For example, the unlicensed frequency band may be a 2.4 GHz or 5 GHz frequency band. The at least one NIC module of the unlicensed band communication interface card 123 may independently or dependently perform wireless communication with at least one of the base station 200, an external device, and a server according to the unlicensed frequency band communication standard or protocol of the frequency band supported by the corresponding NIC module.

[0133] The memory 130 stores a control program and various data therefor used in the UE 100. Such a control program may include a prescribed program required to perform wireless communication with at least one of the base station 200, an external device, and a server.

[0134] Next, the user interface 140 includes various input / output means provided in the UE 100. In other words, the user interface 140 can use various input means to receive user input, and the processor 110 can control the UE 100 based on the received user input. In addition, the user interface 140 can use various output means to perform output based on instructions from the processor 110.

[0135] Next, the display unit 150 outputs various images on the display screen. The display unit 150 may output various display objects such as content or a user interface executed by the processor 110 based on a control instruction from the processor 110.

[0136] In addition, the base station 200 according to an embodiment of the present disclosure may include a processor 210 , a communication module 220 , and a memory 230 .

[0137] First, the processor 210 can execute various instructions or programs and process internal data of the base station 200. In addition, the processor 210 can control the overall operation of each unit in the base station 200 and control the transmission and reception of data between the units. Here, the processor 210 can be configured to perform operations according to the embodiments described in the present disclosure. For example, the processor 210 can signal a time slot configuration and perform communication according to the signaled time slot configuration.

[0138] Next, the communication module 220 may be an integrated module that performs wireless communication using a wireless communication network and performs wireless LAN access using a wireless LAN. To this end, the communication module 220 may include multiple network interface cards, such as cellular communication interface cards 221 and 222 and an unlicensed band communication interface card 223, in an internal or external form. In the drawings, the communication module 220 is shown as an integrally integrated module, but unlike the drawings, each network interface card can be independently arranged according to circuit configuration or usage.

[0139] The cellular communication interface card 221 can transmit or receive radio signals with at least one of the base station 200, an external device, and a server using a mobile communication network and provide cellular communication services in a first frequency band based on instructions from the processor 210. According to an embodiment, the cellular communication interface card 221 may include at least one NIC module that uses a frequency band less than 6 GHz. The at least one NIC module of the cellular communication interface card 221 can independently perform cellular communication with at least one of the base station 200, an external device, and a server in a frequency band less than 6 GHz supported by the corresponding NIC module in accordance with a cellular communication standard or protocol.

[0140] The cellular communication interface card 222 can transmit or receive radio signals with at least one of the base station 200, an external device, and a server using a mobile communication network and provide cellular communication services in the second frequency band based on instructions from the processor 210. According to an embodiment, the cellular communication interface card 222 may include at least one NIC module that uses a frequency band of 6 GHz or higher. The at least one NIC module of the cellular communication interface card 222 can independently perform cellular communication with at least one of the base station 200, an external device, and a server in accordance with a cellular communication standard or protocol in the frequency band of 6 GHz or higher supported by the corresponding NIC module.

[0141] Unlicensed band communication interface card 223 transmits or receives radio signals with at least one of base station 200, external devices, and servers using the third frequency band, which is an unlicensed frequency band, and provides unlicensed band communication services based on instructions from processor 210. Unlicensed band communication interface card 223 may include at least one NIC module that utilizes the unlicensed frequency band. For example, the unlicensed frequency band may be a 2.4 GHz or 5 GHz frequency band. The at least one NIC module of unlicensed band communication interface card 223 may independently or dependently perform wireless communication with at least one of base station 200, external devices, and servers in accordance with the unlicensed frequency band communication standard or protocol supported by the corresponding NIC module.

[0142] Figure 11 1 is a block diagram illustrating a UE 100 and a base station 200 according to an embodiment of the present disclosure, and the blocks shown separately are logically divided elements of the device. Therefore, the aforementioned elements of the device can be installed in a single chip or multiple chips according to the design of the device. In addition, part of the configuration of the UE 100, such as the user interface 140 and the display unit 150, can be selectively provided in the UE 100. In addition, the user interface 140 and the display unit 150 can be additionally provided in the base station 200 as necessary.

[0143] In the NR wireless communication system, the user equipment may send a codebook including hybrid automatic repeat request (HARQ)-ACK information to signal whether the reception of the downlink signal or channel is successful. The HARQ-ACK codebook includes one or more bits indicating whether the reception of the downlink signal or channel is successful. Here, the downlink channel may include at least one of a physical downlink shared channel (PDSCH), a semi-persistent scheduling (SPS) PDSCH, and a PDCCH for releasing the SPS PDSCH. The HARQ-ACK codebook may be divided into a semi-static HARQ-ACK codebook (or a first type codebook) and a dynamic HARQ-ACK codebook (or a second type codebook). The base station may set one of the two HARQ-ACK codebooks for the user equipment. The user equipment may use the HARQ-ACK codebook set for the user equipment.

[0144] When using a semi-static HARQ-ACK codebook, the base station can use RRC signaling to configure the number of bits in the HARQ-ACK codebook and the information used by each bit of the HARQ-ACK codebook to determine which downlink signal or channel was successfully received. Therefore, the base station does not need to signal the user equipment with the information required to send the HARQ-ACK codebook every time the HARQ-ACK codebook needs to be sent.

[0145] When a dynamic HARQ-ACK codebook is used, the base station may signal the information required to generate the HARQ-ACK codebook through the PDCCH (or DCI). In detail, the base station may signal the information required to generate the HARQ-ACK codebook through the downlink assignment index (DAI) field of the PDCCH (or DCI). In a specific embodiment, the DAI represents information about the number of bits of the HARQ-ACK codebook and information about which channel or signal each bit of the HARQ-ACK codebook indicates reception success or failure. The user equipment may receive the DAI field through the PDCCH (or DCI) for scheduling the PDSCH. The value of the DAI field may be divided into a counter-DAI and a total-DAI. The total-DAI indicates the number of downlink signals or channels for which the reception success or failure is indicated by the HARQ-ACK codebook until the current monitoring opportunity (MO). The counter-DAI indicates a HARQ-ACK codebook bit, which indicates the success or failure of reception of a downlink signal or channel among the downlink signals or channels of the current cell up to the current monitoring opportunity, which are indicated by the HARQ-ACK codebook. The PDCCH (or DCI) for scheduling the PDSCH may include the value of the counter-DAI corresponding to the scheduled PDSCH. Moreover, the PDCCH (or DCI) for scheduling the PDSCH may include the value of the total-DAI corresponding to the scheduled PDSCH. The user equipment may determine the number of bits of the dynamic HARQ-ACK codebook based on the information signaled by the PDCCH (or DCI). In detail, the user equipment may determine the number of bits of the dynamic HARQ-ACK codebook based on the DAI of the PDCCH (or DCI).

[0146] Configured License

[0147] Figure 12 is a diagram illustrating an example of an uplink grant to which an embodiment of the present invention can be applied.

[0148] Figure 12 (a) illustrates an example of dynamic licensing, Figure 12 (b) illustrates an example of configured permissions.

[0149] Hereinafter, in the present invention, for convenience, uplink transmission using a dynamic grant is referred to as grant-based uplink transmission, and uplink transmission using a grant configured in the UL without a dynamic grant (grant-free) is referred to as grant-free uplink transmission. However, these are exemplary and the present invention is not limited thereto.

[0150] Dynamic grant refers to a method for sending / receiving data based on the scheduling of the base station in order to maximize resource utilization. This means that when a user equipment has data to send, the user equipment can first request the base station to allocate uplink resources, and only use the uplink resources allocated from the base station to send data. In order to effectively use the uplink radio resources, the base station has to know what kind of data each user equipment wants to send in the uplink and how much data to send. Accordingly, the user equipment can directly send information about the uplink data to be sent to the base station, and the base station can allocate uplink resources to the user equipment based on this information. In this case, the information about the uplink data sent from the user equipment to the base station indicates the amount of uplink data buffered in its own buffer area, which is called a buffer status report (BSR). The BSR is sent using a MAC control element when resources are allocated to the user equipment on the PUSCH in the current TTI and a reporting event is triggered.

[0151] Figure 12 (a) illustrates the process by which a user equipment allocates uplink resources for actual data when uplink radio resources for buffer status reporting are not allocated to the user equipment. Specifically, when the user equipment switches from discontinuous reception (DRX) mode to active mode, since there are no pre-allocated data resources, it is necessary to request resources for uplink data starting with SR transmission via the PUCCH. In this case, a five-step uplink resource allocation process is used.

[0152] like Figure 12 As shown in (a), when a user equipment is not allocated PUSCH resources for transmitting a BSR, the user equipment first sends a scheduling request (SR) to the base station to receive a PUSCH resource allocation. When the user equipment is not scheduled for radio resources on the PUSCH in the current TTI, the scheduling request is used to request the base station to allocate PUSCH resources for uplink transmission by the user equipment, even though a reporting event has occurred. That is, when a regular buffer status report (regular BSR) is triggered but the user equipment does not have uplink radio resources to send the BSR to the base station, the user equipment sends an SR on the PUCCH.

[0153] Depending on whether PUCCH resources for SR are configured, the user equipment sends SR via PUCCH or initiates a random access procedure. Specifically, the upper layer (eg, RRC layer) can configure PUCCH resources in which SR can be sent specifically for the user equipment.

[0154] The SR configuration includes the SR transmission period (SR periodicity) and SR subframe offset information.

[0155] When the user equipment receives a UL grant of PUSCH resources for BSR transmission from the base station, the user equipment transmits a triggered BSR to the base station through the PUSCH resources allocated by the UL grant.

[0156] The base station checks the actual amount of data that the user equipment wants to send through the uplink through the BSR, and sends a UL grant of PUSCH resources for actual data transmission to the user equipment. The user equipment that has received the UL grant for actual data transmission sends the actual uplink data to the base station through the allocated PUSCH resources.

[0157] Will refer to Figure 12 (b) describes a method for transmitting PUSCH using the configured grant.

[0158] The user equipment receives resource configuration for transmitting UL data from the base station without dynamic grant. Resource configuration can be performed only through RRC signaling (Type 1), or can be performed through Layer 1 (L1) signaling and RRC signaling (Type 2).

[0159] In case of Type 1, RRC may receive and configure the following parameters.

[0160] – Period and offset for SFN=0

[0161] -Power control parameters

[0162] -Time / frequency resource allocation

[0163] -DMRS parameters / MCS / TBS

[0164] - Number of repeated transmissions K

[0165] In case of Type 2, RRC may receive and configure the following parameters.

[0166] -cycle

[0167] -Power control parameters

[0168] - Number of repeated transmissions K

[0169] In addition, in case of Type 2, the following items may be indicated by L1 signaling.

[0170] – Offset used for initial transmission timing

[0171] -Time / frequency resource allocation

[0172] -DMRS parameters / MCS / TBS

[0173] In addition, the user equipment performs initial transmission to the base station through L1 signaling based on the resource configuration received through RRC signaling without dynamic grant. In this case, the initial transmission can be repeated, and the initial transmission for the same transport block can be repeated K times (K≥1).

[0174] Resources used for initial transmissions made by the configured grant may or may not be shared among one or more user equipments.

[0175] When an initial transmission fails with a configured grant, the base station can send a dynamic grant to the user equipment for retransmission of the TB associated with the initial transmission. In this case, even if a collision occurs, the base station needs to identify the user equipment. The base station can identify the user equipment performing UL transmission without an uplink dynamic grant based on time / frequency resources and reference signal (RS) parameters.

[0176] The base station can allocate different DMRS resources and parameters to different user equipment sharing the same resources. Furthermore, when a user equipment performs a retransmission, it switches to a dynamic grant basis, receives a dynamic grant from the base station, and performs a retransmission based on the dynamic grant. In other words, the user equipment performs an initial transmission without a dynamic grant but performs a retransmission based on the dynamic grant.

[0177] Figure 13 is a diagram illustrating an example of permission-free initial transmission.

[0178] refer to Figure 13 , the configuredGrantConfig of the BWP-UplinkDedicated information element (IE) sent through RRC signaling and the PUSCH transmission corresponding to the configured grant configures the configured granted uplink resources for PUSCH transmission as semi-static, and subsequent parameters can be used to allocate the configured granted uplink resources depending on the transmission type.

[0179] When upper layers do not deliver a transport block for transmission on the resources allocated for uplink transmission without a dynamic grant, the user equipment may not perform any transmission on the resources configured by configuredGrantConfig.

[0180] In case of type 1 PUSCH transmission for configured grants

[0181] In case of type 1 PUSCH transmission for configured grant, the base station may configure the following information in the user equipment through RRC signaling.

[0182] - Upper layer parameter timeDomainAllocatio value m: indicates the row index m+1 of the matrix indicating the allocated table, and the allocated table indicates the combination of starting symbol, length and PUSCH mapping type. Here, the table selection follows the rules of the user equipment specific search space.

[0183] - Frequency domain resource allocation is determined by the upper layer parameter frequencyDomainAllocation according to the procedure for a given resource allocation type indicated by reusrceAllocation.

[0184] -MCS is provided by the upper layer parameter mcsAndTBS.

[0185] -The number of DMRS groups, DMRS ports, SRS resource indicators, and DMRS sequence initialization are determined by the DCI format used to schedule PUSCH, and the antenna port value, the bit value for DMRS sequence initialization, the precoding information and the number of layers, and the SRS resource indicator are provided separately by antennaPort, dmrs-SeqInitialization, precodingAndNumberOfLayers, and srs-ResourceIndicator, respectively.

[0186] - When frequency hopping is enabled, the frequency offset between two hop frequencies is configured by the upper layer parameter frequencyHoppingOffset.

[0187] In case of type 2 PUSCH transmission for configured grants

[0188] In case of Type 2 PUSCH transmission for configured grant, resource allocation is based on the UL grant received on the DCI.

[0189] Repetition of transport blocks for uplink transmission of configured grants

[0190] The upper layer configuration parameters repK and repK-RV define the K repetitions to be applied to the transmitted transport block and the pattern of redundancy versions (RVs) to be applied to the K repetitions.

[0191] If the parameter repK-RV is not provided in configuredGrantConfig, the RV for uplink transmission of the configured grant is set to 0. If the parameter repK-RV is provided in configuredGrantConfig, the RV sequence can be configured based on repK-RV. The RV of the nth (n=1, 2, ..., K)th transmission opportunity among K repetitions is the (mod(n-1, 4)+1)th value in the configured RV sequence. When configured to repeat K times in the configured grant, the initial transmission of the transport block can begin at the next time point.

[0192] - If the configured RV sequence is {0, 2, 3, 1}, the first transmission time point among the K repetitions.

[0193] - If the configured RV sequence is {0, 3, 0, 3}, then any time point associated with RV=0 during the K repeated transmissions.

[0194] - If the configured RV sequence is {0,0,0,0}, any time point of K repeated transmissions, where K is "8", excluding the last transmission time point.

[0195] In the case of the RV sequence, the repeated transmission can be stopped after K repeated transmissions, or it can be stopped at the earliest time point among the last transmission time point among the K repetitions during period P and the start point of the repetition overlapping with the PUSCH of the same HARQ process scheduled with DCI format 0_0 or 0_1.

[0196] The user equipment does not desire to set the time interval of the K repetition transmissions to be greater than the time interval derived from the period P. If the user equipment determines that the number of symbols available for PUSCH transmission in the time slot used for the transmission opportunity is less than the number of symbols in the transmission interval, the user equipment does not transmit the PUSCH at the transmission opportunity.

[0197] For type 1 and type 2 PUSCH transmissions for configured grants, when the value of repK is set to greater than 1, the user equipment has to repeatedly transmit the TB over consecutive slots according to the repK value by applying the same symbol in each slot.

[0198] Depending on the conditions of the timeslot configuration, Type 1 or Type 2 PUSCH transmission of the grant configured in the timeslot may be omitted.

[0199] refer to Figure 14 , a user equipment (UE) receives RRC configuration information including information for receiving downlink control information (DCI) from a base station (S14010).

[0200] For example, the RRC configuration information may include information related to a control resource set (CORESET) and a search space for a user equipment to detect a PDCCH including downlink control information. In this case, the information related to the control resource set may include at least one of an identifier (ID) of a control resource set in which the user equipment can detect a PDCCH including DCI, control channel element (CCE) configuration information, a length (duration) of the control resource set, or frequency resource information. In this case, the information related to the search space may include at least one of an identifier (ID) of a search space in which the user equipment can detect a PDCCH including DCI, a format of DCI that can be detected in each search space, a detection duration, or resource information.

[0201] In addition, as in Figure 12 and Figure 13 As described in , the RRC configuration information may include parameters for configuration according to each type (type 1, type 2) of the configured grant.

[0202] Then, the user equipment may receive DCI by detecting PDCCH at a monitoring opportunity based on the RRC configuration information (S14020). The user equipment may acquire DCI by detecting PDCCH in a specific search space at a monitoring opportunity according to a service type and / or data based on the RRC configuration information.

[0203] In this case, the DAI included in the DCI may be configured with different bits depending on the DCI format. For example, in DCI format 1_0, the DAI may be configured with 2 bits, and in DCI format 1_1, the DAI may be configured with 1 bit in the case of a semi-static HARQ-ACK codebook, and may be configured with 2 bits in the case of a dynamic HARQ-ACK codebook.

[0204] Table 3 below shows an example of DAI bits according to the DCI format.

[0205] [Table 3]

[0206]

[0207] In addition, resources may be allocated to the user equipment for receiving the PDSCH or transmitting the PUSCH through the PDCCH (or DCI).

[0208] If different transport blocks (TBs) are transmitted at regular intervals through the PUSCH using repeatedly configured resources based on the configured grant, information for resource configuration may be included in the DCI depending on the type and may further include an identifier for activating configuration related to the configured resources.

[0209] That is, an indicator indicating a configuration to be activated for transmission of a PUSCH may be included in the DCI and transmitted to the user equipment.

[0210] Then, the user equipment may activate at least one configuration for transmitting the PUSCH by using an indicator included in the received DCI, and may transmit the PUSCH to the base station through resources allocated at regular intervals based on the activated configuration (S14030).

[0211] Alternatively, when the user equipment receives the PDSCH from the base station, the user equipment may generate a HARQ-ACK codebook indicating ACK / NACK for the received PDSCH based on the DAI value included in the PDCCH (or DCI) that schedules the PDSCH, and may include the generated HARQ-ACK codebook in the uplink control information (UCI) and transmit it to the base station. In this case, the PUSCH may be repeatedly transmitted between time slots using resources allocated via the DCI.

[0212] In order to transmit the PUSCH, symbols allocated from the base station through DCI may be allocated to the user equipment by the position of the starting symbol, the length of the allocated resources, and the number of repetitions.

[0213] Figure 15 is a flowchart illustrating an example of a configuration for releasing PUSCH transmission according to an embodiment of the present invention.

[0214] refer to Figure 15 , the user equipment may release the configuration activated for transmission of the PUSCH based on the identifier included in the DCI.

[0215] Specifically, the user equipment may include RRC configuration information, which is used to Figure 14 The method described in the foregoing releases the activated configuration from the base station when performing the configured grant-based PUSCH transmission (S15010). The RRC configuration information may include an identifier for identifying each resource to be released, for releasing the activated configuration for PUSCH transmission.

[0216] In this case, the identifier may be an identifier for each of released configurations among configurations activated for both types of configurations, or an identifier for each of released configurations among configurations activated for semi-persistent scheduling (SPS).

[0217] The user equipment may then receive a PDCCH from the base station including a DCI for indicating the release of the activated configuration (S15010). In this case, the DCI may include a specific indicator indicating a set of configurations to be released. For example, when one configuration is activated, the DCI may not include a specific indicator, and when multiple configurations are activated, the DCI may include a specific indicator indicating the configuration or configuration group to be released. In this case, when the specific indicator indicates a configuration group, the configuration group may include the configurations to be released, which are included in the RRC configuration information.

[0218] If the RRC configuration information for releasing the configured configuration is not received, the user equipment may recognize that the specific indicator of the DCI indicates that the DCI is included in the Figure 14 That is, if the RRC configuration information for release is not received, the user equipment may recognize that the specific indicator indicates a resource corresponding to the same value as the value of the following indicator, which indicates that the resource is configured in the RRC configuration information for release. Figure 14 The configuration of the PUSCH transmission in step S14010 is included in the RRC configuration information.

[0219] In other words, if RRC configuration information for release is not provided, the user equipment may recognize that the specific indicator for release configuration indicates the configuration for transmitting the PUSCH.

[0220] The specific indicator may be used to release multiple configurations activated for PUSCH transmission, and the user equipment may release multiple configurations indicated by one specific indicator.

[0221] In this case, a specific indicator can be sent through the HARQ process number field. The user equipment can obtain the specific indicator from the HARQ process number field. When the HARQ process number field is used for resource release, the validity of the DCI can be determined by fields other than the HARQ process number field.

[0222] The user equipment may identify the configuration to be released through a specific indicator included in the received DCI, and may release one or more identified configurations.

[0223] As described in the previously configured grant, the user equipment may be configured to receive a PDSCH configured by an RRC signal (or configured by an RRC signal and activated using an L1 signal). This may be referred to as semi-persistent scheduling (SPS) or configured scheduling (CS). On the other hand, when receiving / transmitting a PDSCH / PUSCH based on SPS / CS, the DCI corresponding to the PDSCH / PUSCH does not exist.

[0224] Therefore, when SPS / CS is configured, even if the user equipment receives / transmits PDSCH / PUSCH, it will not receive the corresponding DCI. Therefore, even if PDSCH / PUCH is received / transmitted, a timer configured for the user equipment may be increased, and when the timer reaches a predetermined value, the default DL BWP may be switched.

[0225] That is, although there is a PDSCH / PUSCH configured with an RRC signal (or configured with an RRC signal and activated using an L1 signal), the user equipment can switch to the default DL BWP.

[0226] <Proposal 1: Group RBs and indicate the resources allocated to the user equipment through RIV indicating the starting RBG index and length>

[0227] Method 1: RBs are grouped using a common RB index, and the set of grouped RBGs may be indicated to the user equipment through the start index and length of the RBG.

[0228] Figure 16 is a diagram illustrating an example of a method for grouping resource blocks according to an embodiment of the present invention.

[0229] refer to Figure 16 In the embodiment of the present invention, multiple RBs may be grouped to form an RB group (RBG) so as to indicate frequency domain resource assignment with a small number of bits to a user equipment using URLLC. The grouped RBG may be indicated by the RIV scheme.

[0230] The user equipment may be configured with a specific value (eg, P value) related to the number of grouped RBs from the base station. The user equipment may use the P value to obtain N RBG RBGs. When grouping RBGs, RBs may always be grouped by P from the PRB with the lowest index value of the active BWP (lowest PRB). However, this approach may not align the RBGs of user equipment with different BWPs.

[0231] Therefore, to solve this situation, a common PRB index can be used to bundle RBGs, such as Figure 16 Here, the common PRB index is the index assigned from the PRB when the base station sets the PRB corresponding to PRB index 0. Therefore, the user equipments of the cell use the same PRB index.

[0232] Specifically, one RBG may be composed of RBs with common PRB indices {P*n, P*n+1, .., P*n+P-1}, where n is a non-negative integer.

[0233] In this case, RBs included in the RBG have to be included in the active BWP.

[0234] The user equipment may acquire S, which is the index of the start RBG of the grouped RBGs, and L, which is the number of RBGs, by using the RIV value. Specifically, the RIV may be obtained by the following Equation 1.

[0235] [Equation 1]

[0236] If (L-1)≤floor(N RBG / 2), then RIV=N RBG *(L-1)+S, and

[0237] If (L-1)>floor(N RBG / 2), then RIV=N RBG *(N RBG -L+1)+(N RBG -1-S), where S+L≤N RBG .

[0238] In another embodiment of the present invention, the user equipment may be configured with a P value as a unit for the length of the bundled RBG and a Q value as a unit for the starting RBG from the base station. That is, the user equipment may be configured with a P value indicating the number of RBs grouped into an RBG and a Q value indicating the starting RB of the RBs grouped into the RBG from the base station. Here, the P value and the Q value may be the same or different.

[0239] The user equipment can create RBGs by grouping RBs using P and Q values. First, Q may always be limited to one of the divisors of P, and P may have one of the values ​​corresponding to powers of 2, such as 2, 4, 8, and 16. For example, if the value of P is 4, the value of Q may be set to one of 1, 2, or 4. In this case, assuming that K (K is a natural number) is P / Q, the user equipment can create K RBG sets by bundling RBGs using the following common PRB index.

[0240] - First RBG set: one RBG consists of RBs with common PRB index {P*n, P*n+1, .., P*n+P-1}

[0241] - Second RBG set: one RBG consists of RBs with common PRB index {P*n+Q, P*n+Q+1, .., P*n+Q+P-1}

[0242] - Third RBG set: one RBG consists of RBs with common PRB index {P*n+2*Q, P*n+2*Q+1, .., P*n+2*Q+P-1}

[0243] - ...kth RBG set: an RBG consists of RBs with common PRB index {P*n+(k-1)*Q, P*n+(k-1)*Q+1, .., P*n+(k-1)*Q+P-1}

[0244] - ...Kth RBG set: an RBG consists of RBs with common PRB index {P*n+(K-1)*Q, P*n+(K-1)*Q+1, .., P*n+(K-1)*Q+P-1}

[0245] As another method, RBGs may be grouped using a UE-specific PRB index to generate K RBG sets as follows.

[0246] - First RBG set: One RBG consists of RBs with UE-specific PRB indices {P*n, P*n+1, .., P*n+P-1}

[0247] - Second RBG set: One RBG consists of RBs with UE-specific PRB indices {P*n+Q, P*n+Q+1, .., P*n+Q+P-1}

[0248] - Third RBG set: one RBG consists of RBs with UE-specific PRB indices {P*n+2*Q, P*n+2*Q+1, .., P*n+2*Q+P-1}

[0249] - ...kth RBG set: one RBG consists of RBs with UE-specific PRB indices {P*n+(k-1)*Q, P*n+(k-1)*Q+1, .., P*n+(k-1)*Q+P-1}

[0250] ...Kth RBG set: One RBG consists of RBs with UE-specific PRB indices {P*n+(K-1)*Q, P*n+(K-1)*Q+1, ..., P*n+(K-1)*Q+P-1}. For reference, among {P*n+(K-1)*Q, P*n+(K-1)*Q+1, ..., P*n+(K-1)*Q+P-1}, only RBs included in the active BWP can be composed of RBGs. An RBG set consists of P RBs, and the indices of the first RBs of two RBG sets differ by a multiple of the Q value. An RBG can consist only of RBs included in the active BWP. That is, if some grouped RBs are not included in the active BWP, the RBG can be grouped using the remaining RBs excluding the excluded RBs.

[0251] The RBGs in the grouped RBGs allocated to the user equipment may be indicated to the user equipment through resource allocation information in the frequency domain of the user equipment through the following two steps.

[0252] 1) First, information indicating the set allocated to the user equipment may be included in the DCI. For example, the DCI may use X=ceil(log2(K)) bits to indicate the RBG set to be used by the user equipment among the K RBG sets. For example, Figure 16 As shown in , when K is 2, X may be 1 bit. In this case, if the value of X is "0", the first RBG set may be indicated to the user equipment, and if it is "1", the second RBG set may be indicated to the user equipment.

[0253] 2) The user equipment can obtain the index value S of the starting RBG of the RBG allocated to the user equipment and the length L of the RBG from the RBG set by using the RIV value. That is, the user equipment can obtain S indicating the index of the RBG from which the allocated RBG starts by using the RIV value included in the DCI and L indicating the number (or length) of the allocated RBGs.

[0254] In this case, the RIV value can be determined by the following equation 2. Here, N RBG,x is the number of RBGs included in the RBG set indicated in the first step.

[0255] [Equation 2]

[0256] If (L-1)≤floor(N RBG,x / 2), then RIV=N RBG,x *(L-1)+S, and

[0257] If (L-1)>floor(N RBG,x / 2), then RIV=N RBG,x *(N RBG,x -L+1)+(N RBG,x -1-S),

[0258] Where S+L<=N RBG,x .

[0259] As another method, the RIV value can be determined by the following equation 3. In this case, N RBG,max It means the maximum value among the number of RBGs included in all RBG sets.

[0260] [Equation 3]

[0261] If (L-1)≤floor(N RBG,max / 2), then RIV=N RBG,max *(L-1)+S, and

[0262] If (L-1)>floor(N RBG,max / 2), then RIV=N RBG,max *(N RBG,max -L+1)+(N RBG,max -1-S),

[0263] Where S+L<=N RBG,x .

[0264] The number of RBGs included in different RBG sets may be the same or different.

[0265] The user equipment has to determine the bit size of the frequency domain resource assignment (FDRA) field indicating the RIV value. For example, because the length (bit size) of the FDRA field may consist of the RB including the most RBGs, the user equipment has to know the bit size of the FDRA field. For example, the bit size of the FDRA field may be ceil(log2(N RBG,max *(N RBG,max

[0266] +1) / 2)), and N RBG,max It means the maximum value among the number of RBGs included in all RBG sets.

[0267] In other words, when a grant scheduled by a specific type of DCI (e.g., DCI format 1_2) is received, the RIV indicating the resources allocated on the frequency domain included in the DCI may include a start index and a length.

[0268] The start index refers to the index of a start RBG of RBGs allocated to the user equipment, and the length may refer to the number of consecutively allocated RBGs.

[0269] Figure 17 is a diagram illustrating an example of a configuration of a bandwidth part (BWP) according to an embodiment of the present invention.

[0270] Method 2: RIV may be used based on an offset to indicate the RBG allocated to the user equipment.

[0271] Specifically, variables and parameters can be defined as follows.

[0272] P: length granularity.

[0273] Q: Starting granularity.

[0274] K: P / Q.

[0275] RB_start: The index of the RB where the allocated resources start in the frequency domain.

[0276] L_RB: the number of RBs to which resources are allocated.

[0277] RB_end: The index of the RB where the allocated resources end.

[0278] P is a multiple of Q, and RB_end may be a value obtained by subtracting 1 from the sum of RB_Start and L_RB (RB_end=RB_Start+L_RB).

[0279] First, the user equipment may receive an offset value of a starting RB having X=ceil(log2(K)) bits. That is, the user equipment may receive an offset value of a starting RB from which allocated resources start through an X-bit DCI.

[0280] The X bits may be obtained through the most significant bit (MSB) of the FDRA field of the DCI, or may be obtained through the MSB of the RIV of the FDRA field of the DCI. Alternatively, the X bits may be bit values ​​included in a separate field in the DCI.

[0281] The user equipment may acquire S and L by using the RIV value included in the DCI. In this case, the RIV value may be defined by Equation 4 below.

[0282] [Equation 4]

[0283] If (L-1)≤floor(N / 2), then RIV=N*(L-1)+S, and

[0284] If (L-1)>floor(N / 2), then RIV=N*(N-L+1)+(N-1-S),

[0285] Where S+L<=N.

[0286] In Equation 4, N represents the quotient of the value obtained by dividing N_BWP, the number of PRBs included in the active BWP, by P. That is, N can be expressed as floor(N_BWP / P). This means that the active BWP can contain a maximum of N RBs having a length of P. S is one of 0, 1, ..., N-1, and L is one of 1, 2, ..., N.

[0287] The user equipment may calculate RB_Start and L_RB by using the offset, S, and L through the following Equation 5.

[0288] [Equation 5]

[0289] RB_start = S*P + offset

[0290] L_RB=L*P

[0291] For example, when N_BWP is 15, P is 4, and Q is 1, 0 or 2 may be indicated as a 1-bit offset through DCI. In this case, the value of N may be 3, and possible combinations of RIV values ​​are shown in Table 4 below.

[0292] [Table 4]

[0293]

[0294]

[0295] In this method, even if the active BWP consists of 15 RBs, the last RB (the RB with an index of 14) cannot be used for scheduling, and thus resource waste may occur in the frequency domain.

[0296] Therefore, to resolve this situation, you can use the following method.

[0297] First, the user equipment may receive an offset value of the starting RB having X = ceil (log2 (K)) bits. One of 0, Q, 2*Q, ..., (K-1)*Q values ​​may be indicated as the offset value. The X bit may be obtained by the MSB of the FDRA field of the DCI or the MSB of the RIV of the FDRA field of the DCI. Alternatively, the X bit may be indicated by a separate field included in the DCI.

[0298] The user equipment may acquire S and L by using the RIV value included in the DCI. In this case, the RIV value may be defined in the same manner as in the above-mentioned Equation 4.

[0299] Here, N can be expressed as N=ceil(N_BWP / P). This means that an active BWP can include up to N RBs of length P and can also include RBs smaller than P. S is one of 0, 1, ..., N-1, and L is one of 1, 2, ..., N.

[0300] The user equipment may calculate RB_Start and L_RB by using the offset, S, and L through the following Equation 6.

[0301] [Equation 6]

[0302] RB_start = S*P + offset

[0303] L_RB=L*P(if S*P+offset+L*P <N_BWP)

[0304] L_RB=N_BWP-RB_start(if S*P+offset+L*P <N_BWP)

[0305] For example, when N_BWP is 15, P is 4, and Q is 2, 0 or 2 can be indicated as a 1-bit offset through DCI. In this case, the value of N can be 4, and possible combinations of RIV values ​​are shown in Table 5 below.

[0306] [Table 5]

[0307] Offset S L RB_start L_RB RB_end 0 0 1 0 4 3 0 0 2 0 8 7 0 0 3 0 12 11 0 0 4 0 15 14 0 1 1 4 4 7 0 1 2 4 8 11 0 1 3 4 10 14 0 2 1 8 4 11 0 2 2 8 7 14 0 3 1 12 3 14 2 0 1 2 4 5 2 0 2 2 8 9 2 0 3 2 12 13 2 0 4 2 13 14 2 1 1 6 4 9 2 1 2 6 8 13 2 1 3 6 9 14 2 2 1 10 4 13 2 2 2 10 5 14 2 3 1 14 1 14

[0308] In this case, the effect of scheduling all RBs in the frequency band can be achieved.

[0309] In another embodiment of the present invention, the L_RB may be determined to match the PRB grid. The PRB grid is completed by bundling several consecutive PRBs according to the common PRB index described above.

[0310] When the PRB grid groups A RBs, the common PRB index of the lowest PRB of the active BWP may be referred to as BWP_low, and the common PRB index of the highest PRB of the active BWP may be referred to as BWP_high.

[0311] First, when BWP_high is an integer multiple of A, the RBs bundled by A in order starting from the lowest PRB in the active BWP can coincide with the PRB grid if BWP_low is an integer multiple of A. However, if BWP_low is not an integer multiple of A, the RBs are bundled by A in order starting from the lowest PRB in the active BWP, and L_RB does not coincide with the PRB grid.

[0312] Therefore, if (BWP_low mod A) RBs are bundled apart from the lowest PRB and then RBs are bundled starting from the next one by A, they may overlap with the PRB grid.

[0313] When BWP_high is not an integer multiple of A, the A PRBs may not remain at the end of the last active BWP, and in this case, the remaining PRBs may be grouped.

[0314] Specifically, a total of M RBs of the active BWP may be grouped based on the PRB grid. Here, M=ceil((N_BWP+(BWP_low mod A)) / A).

[0315] In the first grouping, A-(BWP_low mod A) RBs may be grouped, and in the last grouping, if (BWP_low+N_BWP) mod A>0, (BWP_low+N_BWP) mod A RBs may be grouped, otherwise A RBs may be grouped.

[0316] The method for allocating frequency domain resources according to the PRB grid is as follows.

[0317] First, the user equipment may receive an offset value of the starting RB through X=ceil(log2(K)) bits of the DCI. The offset value may be one of 0, Q, 2*Q, ..., (K-1)*Q.

[0318] The X bits may be acquired through the MSB of the FDRA field of the DCI or the MSB of the RIV of the FDRA field of the DCI. Alternatively, the X bits may be indicated by a separate field included in the DCI.

[0319] The user equipment may obtain S and L by using the RIV value included in the DCI. In this case, the RIV value may be obtained by the following Equation 7.

[0320] [Equation 7]

[0321] RIV=N*(L-1)+S(if (L-1)≤floor(N / 2)),

[0322] RIV=N*(N-L+1)+(N-1-S)(if (L-1)>floor(N / 2)),

[0323] S+L<=N

[0324] When BWP_low+offset is a multiple of P and BWP_low+N_BWP+offset is a multiple of P, N=N_BWP / P.

[0325] However, if BWP_low+offset is a multiple of P, but BWP_low+N_BWP+

[0326] Offset is not a multiple of P, then N=floor(N_BWP / P)+1. Alternatively, if BWP_low+offset is not a multiple of P and BWP_low+N_BWP+offset is not a multiple of P, then N=floor(N_BWP / P)+2.

[0327] Based on the PRB grid, the active BWP can contain at most floor(N_BWP / P) RBs of length P, and in addition, the set of PBs with length less than P will be occupied by the BWP.

[0328] S is one of 0, 1, ..., N-1, and L is one of 1, 2, ..., N.

[0329] The user equipment may calculate RB_Start and L_RB by using the offset, S, and L through the following Equation 8.

[0330] [Equation 8]

[0331] If S = 0, R_start = offset,

[0332] If S > 0, R_start = S*P + offset – (BWP_low mod P),

[0333] L_RB = L*(P - 1) + (P - (BWP_low mod P)) (if R_start + L*P < N_BWP and S = 0)),

[0334] L_RB = L*P (if S > 1),

[0335] L_RB = N_BWP - RB_start (if R_start + L*P ≥ N_BWP)

[0336] As [[ID=at]] Figure 17 shown, the virtual BWP can consist of N*P RBs.

[0337] The virtual BWP can be aligned with the PRB grid and includes the RBs {-delta + 1,…0,…,N*P + delta}. In this case, delta = BWP_low mod P.

[0338] Here, the lowest RB with a negative index and the RBs with indices greater than N*P are actually included in the active BWP. The RB indices of the virtual BWP are denoted by 0’, 1’,..., (N*P - 1)’. RB_start_temp is the index of the starting RB among the RB indices of the virtual BWP. This can be obtained by RB_start_temp = (S*P + offset)’ and L_RB_temp = L*P. If the RBs among the virtual RBs that are not included in the actual RBs (i.e., the lowest RB with a negative index and the RBs with indices equal to or greater than N*P) are excluded, then the resource allocation in the actual active BWP can be obtained.

[0339] For example, when N_BWP is 15, P is 4, Q is 2, and the lowest PRB index BWP_low of the active BWP is 2, the offset can be indicated by 0 or 2 using 1-bit offset in the DCI. N can be obtained according to the offset.

[0340] In this case, the possible combinations of the RIV values are as shown in Table 6 below.

[0341] [Table 6]

[0342]

[0343]

[0344] As described above, the base station can group RBs in RBG units and allocate resources to the user equipment, and can send DCI to the user equipment, which includes the index and length information of the starting RBG of the allocated resources. In this case, the base station can additionally include offset information about the starting RBG in the DCI and send the DCI.

[0345] The user equipment may perform repeated transmission of the PUSCH by identifying allocated resources based on the DCI for resource allocation received from the base station.

[0346] Specifically, as described in Method 1 and / or Method 2, the user equipment can identify the resources used for PUSCH repetition transmission based on the index and length information of the starting RBG of the allocated resources included in the DCI transmitted from the base station. In this case, when the offset information is further included in the DCI, the allocated resources can be identified by additionally using the offset information.

[0347] The user equipment may then repeatedly transmit the PUSCH to the base station by using the identified resources.

[0348] <Proposal 2: Freeing allocated resources for repeated PUSCH transmissions by using one DCI>

[0349] In another embodiment of the present invention, the base station may release the resources allocated and activated for repeated transmission of the PUSCH through DCI. In this case, the base station may release multiple resources activated through one DCI at a time.

[0350] That is, resources allocated for UL grant-free transmission or transmission using a configured grant may be released through one DCI.

[0351] Typically, uplink transmission is based on grants (GBs), where the user equipment is configured to transmit on corresponding resources based on the scheduling information of a grant received via DCI on the PDCCH transmitted from the base station. In GB transmission, the base station configures a UL grant for uplink transmission as DCI and sends the UL grant to the user equipment via a downlink control channel. This grant is a dynamic grant.

[0352] The user equipment can send a TB mapped to the HARQ process ID according to the HARQ process ID of the UL grant to the base station through the time-frequency resources indicated by the UL grant. The user equipment can manage HARQ retransmissions based on the UL grant with the same HARQ process ID. For example, the user equipment can check whether the previous TB has been successfully sent to the base station by comparing the new data indicator (NDI) with the NDI of the previously received UL grant, and the NDI indicates whether new data is indicated by the UL grant from the base station. That is, when the NDI of the received UL grant is a toggled value of the previously received NDI, the user equipment can determine that the previously sent TB has been successfully sent. However, if the NDI of the received UL grant is the same as the value of the previously received NDI, it is determined that the TB has not been sent normally and the transmission has failed, and a retransmission process for the corresponding TB can be performed.

[0353] In uplink free-grant (GF) transmission, when the user equipment has data to send to the base station, the user equipment does not receive a grant for uplink transmission from the base station, and the base station and the user equipment can be pre-configured through RRC configuration information according to corresponding configuration information, or the user equipment can send data to the base station through predefined time-frequency resources.

[0354] In this case, the time-frequency resources may be configured differently depending on the user equipment. The demodulation reference signal (DM-RS) used by the user equipment when transmitting the GF may be configured differently depending on the user equipment. Accordingly, when performing uplink GF transmission, the user equipment may transmit the DM-RS and data configured for the user equipment to the base station by using the time-frequency resources configured for the user equipment.

[0355] To increase the reliability of uplink GF transmission, the base station can be configured to repeatedly transmit uplink data to the user equipment. For example, if the base station is configured to repeatedly transmit data to the user equipment K times, the user equipment can repeatedly transmit the data to the base station K times. In this case, the user equipment can repeat the data K times, or can end the repeated transmission when receiving a response (ACK) to the uplink GF transmission from the base station.

[0356] When receiving an uplink GF transmission, the base station can identify which user equipment has performed uplink transmission on the GF resource through the time-frequency resources and the DMRS, but may not be able to receive data.

[0357] In this case, the user equipment may send a grant for retransmitting uplink data to the user equipment. If the user equipment receives the grant for uplink data retransmission, the user equipment may stop GF transmission of the TB and may perform GB retransmission.

[0358] In Release 16 NR, a BWP for a cell can include grants for up to 12 UL configurations. In this case, using a configuration that releases a grant for each UL configuration per DCI may have the limitation of increased DCI overhead.

[0359] To address this limitation, one DCI may be used to release the configuration of grants for two or more UL configurations.

[0360] Method 1: The IDs of the configured grants released through DCI may be indicated by grouping the IDs of the configured grants.

[0361] In an embodiment of the present invention, when a base station configures a UL-configured grant for uplink transmission for a user equipment, one group ID may indicate multiple UL-configured grants by grouping the individual UL-configured grants.

[0362] Specifically, when configuring a UL configured grant for a user equipment, the base station may configure it so that the ID indicates the IDs of two or more UL configured grants with a specific value (for example, 12, 13, 14, 15, or if X configured grants are configured, then X, X+1, ..., X+15). For example, the ID may be configured to be 12 so that the IDs of the UL configured grant include 0, 1, 2, and 3. That is, a specific value may be configured so that the ID indicates that the configured grant has already been configured, rather than a new UL configured grant.

[0363] When the user equipment receives a DCI for releasing a UL configured grant, the user equipment can use four bits of the DCI to receive the ID of the UL configured grant. If the indicated ID is a specific value, multiple UL configured grants indicated by the specific value can be released at once.

[0364] That is, if the user equipment has multiple configurations through grants for multiple configurations of repeated PUSCH transmission from the base station, it is possible to release the multiple configurations through the DCI sent from the base station. In this case, the DCI may include a specific indicator indicating the grants (or resources) of the multiple configurations. The specific indicator (or ID field) may indicate the ID of the grant (or resource) of one or more configurations configured for repeated transmission of the PUSCH.

[0365] At this time, the ID of each configured grant to be released can be provided to the user equipment through RRC configuration, and if there is no RRC configuration, the user equipment can determine that the specific indicator of DCI corresponds to the ID of the configured grant activated for repeated transmission of PUSCH.

[0366] The above method may be used to activate one or more configured grants (or resources) for repeated transmissions of PUSCH.

[0367] That is, the user equipment may receive a DCI for activating a UL configured grant and may use four bits of the DCI to receive the IDs of one or more configured grants to be activated. The user equipment may perform repeated transmission of the PUSCH by activating one or more configured grants corresponding to the IDs received through the DCI.

[0368] In this case, a field consisting of 4 bits is required in order to indicate the ID of each of the multiple configured grants released through one DCI. Therefore, the following field can be used to indicate the release of the multiple configured grants.

[0369] - HARQ process number field: The HARQ process number field is always 4 bits and is included in DCI formats 0_0 and 0_1.

[0370] - Four bits in the FDRA, TDRA, RV and / or MCS fields: Specifically, the first 1 bit of each field can be bundled and reused as 4 bits.

[0371] -DCI format 0_0: The frequency hopping flag (1 bit), NDI (1 bit), and TPC command for scheduled PUSCH (2 bits) can be bundled and reused to indicate the permission of the configuration being released. Alternatively, if the frequency hopping flag consists of 1 bit in DCI format 0_1, the frequency hopping flag (1 bit), NDI (1 bit), and TPC command for scheduled PUSCH (2 bits) can be bundled and reused to indicate the permission of the configuration to be released in the same manner as DCI format 0_0. If the frequency hopping flag consists of 0 bits in DCI format 0_1, 1 bit can be used additionally in another field. For example, 1 bit can be used additionally in the downlink assignment indicator (DAI) field. In this case, the DAI field is 1 bit or 2 bits.

[0372] For example, when the user equipment is configured with one or more UL configured grants (e.g., UL grant type 2 PUSCH) from the base station via DCI, the value of the HARQ process number field in the DCI format may indicate activation of the UL configured grant (or resource) corresponding to the same value as the value provided by the RRC configuration information.

[0373] That is, each configuration value of each configured grant provided through higher layer signaling corresponds to a 4-bit HARQ process number field included in the DCI, and the user equipment can activate one or more configured grants corresponding to the HARQ process number field.

[0374] In this case, the validation of the DCI may be determined using fields other than the HARQ process number field.The user equipment may perform repeated transmission of the PUSCH using the activated resources.

[0375] When the user equipment is configured with one or more configured grants from the base station, the following method may be used to release the one or more configured grants.

[0376] If the user equipment is provided with a configuration (or list) of one or more configured grants to be released via higher layer signaling (e.g., RRC configuration information), the value of the HARQ process number field in the DCI format may indicate an item for scheduling the configuration of releasing one or more UL configured grants. That is, the user equipment may release the configuration of one or more configured grants corresponding to the value of the HARQ process number field included in one DCI. In this case, the configuration of one or more configured grants to be released may be sent to the user equipment via higher layer signaling.

[0377] If the user equipment is not provided with a configuration (or list) of one or more configured grants released through higher layer signaling (e.g., RRC configuration information), the value of the HARQ process number field in the DCI format may indicate the release of a UL-configured grant having the same value as the index value of the configuration for one or more UL-configured grants. That is, the user equipment may release the configuration of one or more configured grants corresponding to the value of the HARQ process number field included in one DCI. In this case, the configuration of the one or more configured grants may be a configuration sent to the user equipment through higher layer signaling to activate the configured grants.

[0378] In this way, the base station can indicate activation / release permission for repeated transmission of the PUSCH to the user equipment through one DCI, and the user equipment can activate / release permission for multiple UL configurations through the received DCI.

[0379] Method 2: The field used to determine verification of DCI to activate / release a configured grant (eg, a type 2 configured grant) or SPS PDSCH may vary depending on the number of configured type 2 configured grants or PDSCHs.

[0380] Specifically, a bit field for determining verification of DCI for activating / releasing a grant configured in type 2 or SPS PDSCH, which is type 2 of two types (type 1, type 2) of configured grants, may vary according to different situations.

[0381] The base station may transmit DCI for activating / releasing a grant or SPS PDSCH configured in type 2 to the user equipment. In this case, the DCI may be scrambled with the CS-RNTI and the value of the NDI field may be set to 0 and transmitted.

[0382] In this case, the value of the field for determining whether activation / deactivation of configuration of repeated transmission of DCI for PUSCH is valid is shown in Table 7 and Table 8 below.

[0383] Table 7 shows an example of field values ​​for determining verification of DCI for activating / releasing a single SPS configuration or a single configured grant when a single SPS configuration or a single configured grant is configured for downlink transmission.

[0384] [Table 7]

[0385]

[0386] Table 8 shows an example of field values ​​for determining verification of DCI for activating / releasing multiple SPS configurations or multiple configured grants when multiple SPS configurations or multiple configured grants are configured for downlink transmission.

[0387] [Table 8]

[0388]

[0389]

[0390] Referring to Table 7 and Table 8, the HARQ process number field may or may not be used for authentication determination depending on whether the SPS configuration or the configuration of the configured permissions is single or multiple.

[0391] For example, when one or more (multiple) configured grants are configured as described in Method 1 of Proposal 2, the HARQ process number field can be used to activate / release the configured multiple configured grants. In this case, since the HARQ process number field is already used to activate / release the multiple configured grants, the HARQ process number field is not used to determine whether the DCI is valid.

[0392] However, if a configured grant is configured, since the HARQ process number field may not be used to activate / release the configured grant, in this case, the HARQ process number field may be used to determine whether the DCI is valid.

[0393] In Tables 7 and 8, the DCI verification check according to the value of the FDRA field may vary depending on the type of FDRA. For example, FDRA type 0 refers to a type used to generate a group (RBG) by bundling RBs, and indicates whether each of the generated RBGs is allocated with a bitmap. In this case, it may mean that if all values ​​of the FDRA field are set to 0, all grouped RBGs are not allocated. Therefore, in general, in FDRA type 0, since the method of allocating RBGs by setting all bits of the FDRA field to 0 may not be used, the user equipment can recognize that the DCI received when all bits of the FDRA field are set to 0 is DCI for release.

[0394] In addition, FDRA type 1 may indicate RIV, which is a value obtained by jointly encoding the start and end of the RB through DCI. Generally speaking, a valid RIV value may be set in advance, and the method of setting all bits of the FDRA field to 1 may not be used.

[0395] Therefore, when the FDRA type is set to FDRA type 1, when all bit values ​​of the FDRA field of the received DCI are 1, the user equipment may determine that the received DCI is DCI for release.

[0396] In addition, when dynamic switching between FDRA types is set, the user equipment can identify the FDRA type based on the MSB value of the FDRA field. For example, if the MSB of the FDRA field is 0, the FDRA type can be determined as FDRA type 0, and if the MSB is 1, the FDRA type can be determined as FDRA type 1.

[0397] When dynamic switching is applied to determine the FDRA type as described above, it is difficult to use the configuration of the FDRA field described in Tables 7 and 8. In this case, the method described below may be used to determine whether the DCI is valid.

[0398] In the first embodiment, if dynamic switching between FDRA types is set, the user equipment can determine that the received DCI is a release DCI when all bit values ​​of the FDRA field are 0 or 1. That is, if dynamic switching is set, if all bit values ​​of the FDRA field are set to be equal to a specific value (0 or 1), the user equipment can determine that the received DCI is a release DCI.

[0399] In the second embodiment, if dynamic switching between FDRA types is set, the user equipment can determine the value of the subsequent bits based on the MSB value of the FDRA field. For example, if the MSB of the FDRA field is 0, the FDRA type can be determined to be FDRA type 0. In this case, as described in Tables 7 and 8, if all bits except the MSB are set to 0, the user equipment can determine that the received DCI is DCI for release.

[0400] For example, if the MSB of the FDRA field is 1, the FDRA type may be determined to be FDRA type 1. In this case, as described in Tables 7 and 8, if all bits except the MSB are set to 1, the user equipment may determine that the received DCI is DCI for release.

[0401] In a third embodiment, when only FDRA type 0 is configured in the user equipment, if all bit values ​​of the FDRA field are 0, the user equipment can determine that the received DCI is DCI for release, and in other cases (for example, the FDRA type is not configured, or FDRA type 1 is set or dynamic switching is set, etc.), if all bit values ​​of the FDRA field are set to 1, the user equipment can determine that the received DCI is DCI for release.

[0402] Table 9 and Table 10 below show examples of field values ​​for determining verification of DCI when dynamic switching according to the first to third embodiments is set.

[0403] Table 9 shows an example of a field value for determining verification of DCI for activating / releasing a single SPS configuration or a single configured grant when a single SPS configuration or a single configured grant is configured for downlink transmission.

[0404] [Table 9]

[0405]

[0406] Table 10 shows an example of a field value for determining verification of DCI for activating / releasing multiple SPS configurations or multiple configured grants when multiple SPS configurations or multiple configured grants are configured for downlink transmission.

[0407] [Table 10]

[0408]

[0409] Similarly, when the type of FDRA is not configured in the DCI format, if all bits of the FDRA field are set to '1', the user equipment may determine that the received DCI is DCI for release.

[0410] The user equipment may be configured with multiple SPS PDSCH configurations from the base station to support different service types. In this case, the user equipment may receive the DCI for SPS activation to activate one of the multiple SPS PDSCH configurations. In this case, the DCI for activating the SPS configuration may be scrambled with the CS-RNTI.

[0411] If the user equipment receives a DCI for activating an SPS configuration, the user equipment may determine the SPS PDSCH configuration to be activated among multiple SPS PDSCH configurations using a specific field of the received DCI. That is, when the user equipment is configured with an SPS PDSCH configuration from a base station, an ID corresponding to each configuration may also be configured, and among the configured IDs, an ID corresponding to the SPS PDSCH configuration to be activated may be received through the DCI.

[0412] In addition, the user equipment may receive DCI for releasing one of the multiple PDSCH configurations or the multiple SPS PDSCH configurations from the base station, and may scramble the DCI using the CS-RNTI.

[0413] If the user equipment receives a DCI for release, the user terminal can use the specific indicator or specific field of the received DCI to determine the SPS PDSCH configuration to be released. That is, if the user equipment receives a DCI for releasing the SPS configuration, the user equipment can use the specific field of the received DCI to determine the SPS PDSCH configuration to be released among multiple SPS PDSCH configurations. That is, when the user equipment is configured with an SPS PDSCH configuration from a base station, an ID corresponding to each configuration can also be configured, and among the configured IDs, an ID corresponding to the SPS PDSCH configuration to be activated can be received through DCI.

[0414] In order to release multiple SPS PDSCH configurations, the user equipment can be configured with a group of multiple IDs bundled from the base station, and because the group ID is included in the DCI for release, the user equipment can be instructed to release the SPS PDSCH configuration corresponding to the group ID.

[0415] Hereinafter, when multiple SPS PDSCH configurations are configured for a user equipment, a method for sending HARQ-ACK for multiple SPS PDSCHs will be described.

[0416] To release multiple SPS PDSCH configurations, the DCI may require up to 4 bits, and the user equipment may use a maximum of 4 bits of DCI for release to indicate a set of configurations to be released.

[0417] For example, a field for indicating the ID of a group can be obtained as follows.

[0418] First, the user equipment may use the HARQ process ID field to indicate the release of the SPS PDSCH configuration via DCI. That is, the HARQ process ID field of the SPS release DCI may indicate the group ID to be released.

[0419] In this case, the size of the HARQ process number field may be smaller than the size of the group ID. That is, the HARQ process number field may not be used to indicate all group IDs.

[0420] In this case, the length of the HARQ process number field may be calculated according to Equation 9 below.

[0421] [Equation 9]

[0422] Length of the HARQ process ID field = ceil(log2(max{# of HARQ processes, # of PDSCH group IDs used for SPS}))

[0423] In Equation 9, # of HARQ process numbers is the number of HARQ processes configured for the user equipment, and # of SPS PDSCH group IDs is the number of SPS PDSCH group IDs configured for the user equipment.

[0424] As another method, when the length of the HARQ process number field is less than ceil(log2(# of group IDs)), bits corresponding to the difference between ceil(log2(# of group IDs)) and the length of the HARQ process number can be obtained in another field of the DCI.

[0425] For example, bits of the FDRA field, bits of the TDRA field, bits of the MCS field, or bits of the RV field may be used.

[0426] The SPS PDSCH is a periodic transmission performed in the downlink. Similarly, there is repeated transmission of the configured grant (CG) PUSCH, which is the periodic transmission in the uplink described above.

[0427] In order to release multiple configured grant (CG) PUSCHs, up to 4 bits of one DCI field may be used as described in Method 1. That is, up to 4 bits of the DCI may be used to indicate the ID of the group to be released.

[0428] In this case, up to 4 bits may be used in the same field as the 4 bits used in the method described in Method 1, or used to release the above-mentioned SPS PDSCH. For example, the HARQ process number field of the DCI may be used to indicate the configured grant PUSCH to be released.

[0429] In this case, the length of the HARQ process number field may be calculated by Equation 10 below.

[0430] [Equation 10]

[0431] HARQ process number field length = ceil(log2(max{# of HARQ processes, # of group IDs used for CG PUSCH}))

[0432] In Equation 10, the # of HARQ process numbers is the number of HARQ processes configured for the user equipment, and the # of group IDs for CGPDSCH is the number of group IDs for CG PUSCH configured for the user equipment. In addition, in order to perform joint release of CG and joint release of SPS using the HARQ process number field, the length of the HARQ process number field can be obtained by the following Equation 11.

[0433] [Equation 11]

[0434] The length of the HARQ process number field = ceil(log2(max{# of HARQ processes, # of group IDs used for CG PUSCH, # of group IDs used for SPS PDSCH})).

[0435] That is, the length of the HARQ process number field may be determined based on a maximum value among the number of HARQ processes, the group ID of the CG PUSCH, and the group ID of the SPS PDSCH.

[0436] In addition, the HARQ process number of the SPS PDSCH can be determined by Equation 12 as follows.

[0437] [Equation 12]

[0438] HARQ process number = [floor(CURRENT_slot×10 / (numberOfSlotsPerFrame×periodicity))] modulo nrofHARQ-Processes

[0439] In Equation 12, CURRENT_slot can be obtained by the following Equation 13.

[0440] [Equation 13]

[0441] CURRENT_slot = [(SFN × numberOfSlotsPerFrame) + number of slots in a frame]

[0442] Each parameter in Equations 12 and 13 is as follows.

[0443] numberOfSlotsPerFrame: The number of slots in each frame

[0444] Periodicity: The period of SPS PDSCH

[0445] nrofHARQ-Processes: The number of HARQ processes of the user equipment

[0446] Number of time slots in a frame: Number of time slots in a frame

[0447] SFN (System Frame Number): System Frame Number

[0448] The periodicity and nrofHARQ-Process can be set from the upper layer, and the numberOfSlotsPerFrame can be determined according to the subcarrier spacing. For example, if the subcarrier spacing is 15kHz, it can be 10, if it is 30kHz, it can be 20, if it is 60kHz, it can be 40, and if it is 120kHz, it can be 80. SFN stands for System Frame Number. The HARQ process number described above is applicable to one SPS PDSCH configuration, but not to multiple SPS PDSCH configurations.

[0449] That is, the values ​​that the HARQ process number can have are limited to 0, 1, ..., nrofHARQ-Process-1, and different SPS PDSCHs are likely to have the same HARQ process number. Therefore, when configuring the SPS PDSCH configuration, an additional HARQ-Process offset value can be set.

[0450] In this case, the HARQ process number may be obtained by additionally using an offset value as shown in Equation 14 below.

[0451] [Equation 14]

[0452] HARQ process number = [[floor(CURRENT_slot×10 / (numberOfSlotsPerFrame×periodicity))] modulo nrofHARQ-Processes] + offset

[0453] By setting the offset value, the HARQ process number can have values ​​such as offset, offset+1, ..., offset+nrofHARQ-Process-1. That is, by using the offset value configured for each SPS PDSCH, the HARQ process number of the SPS PDSCH can be made different from other numbers.

[0454] In the present invention, a method for determining the HARQ process number of the SPS PDSCH using a set offset value has been described; however, this method is not limited to the SPS PDSCH. Even in the method for determining the HARQ process number of the PUSCH in a configured grant-based PUSCH transmission, the HARQ process number can use the set offset value. That is, in grant-based PUSCH transmission, the HARQ process number of the PUSCH can be obtained by adding the offset to a value determined based on the number of slots (numberOfSlotsPerFrame), the system frame number (SFN), the number of HARQ processes (nrofHARQ-Processes), and the period (periodicity).

[0455] Figure 18 is a flowchart illustrating an example of a method for releasing a configuration configured for transmission of a PUSCH by a user equipment according to an embodiment of the present invention.

[0456] refer to Figure 18 , when multiple configurations (eg, configured grants) for PUSCH transmission are activated for a user equipment, the user equipment may release the multiple configurations (or configured grants) based on the DCI sent from the base station.

[0457] Specifically, the user equipment may perform PUSCH transmission through one or more activated configurations. In this case, PUSCH transmission may be periodically transmitted through multiple resources repeatedly configured based on the configured grant, and PUSCH may be transmitted by including different transport blocks in each resource.

[0458] Then, the user equipment may receive a first physical downlink control channel (PDCCH) including first downlink control information (DCI) from the base station ( S18010 ).

[0459] In this case, the DCI may be included in the above Figures 12 to 17 and the fields and parameters described in Proposal 1 and Proposal 2.

[0460] For example, the DCI may include at least one of an NDI field, a HARQ process number field, an RV field, and an FDRA field for determining whether the DCI is valid. In this case, the HARQ process number field may not be used to determine the verification of the DCI based on whether one configuration or multiple configurations are activated to repeatedly transmit the PUSCH.

[0461] In addition, when multiple configurations are activated for repeated transmission of the PUSCH, a first DCI for transmission of the PUSCH may be configured based on the configured grant to include a first specific identifier (ID) for releasing one or more configurations. In this case, the first specific identifier may indicate the one or more configurations configured for transmission of the PUSCH.

[0462] In this case, the PUSCH refers to a channel periodically transmitted through resources repeatedly configured according to a configured grant.

[0463] If multiple configurations are activated for repeated transmission of PUSCH, the first specific identifier can be indicated by a hybrid automatic repeat request (HARQ) process number (HARQ process number) field of the first DCI, and the HARQ process number field can be used to identify one or more configurations among the multiple configurations.

[0464] Therefore, the user equipment can release multiple configurations at once using one DCI based on a specific identifier indicated by the HARQ process number field.

[0465] The user equipment may then release one or more configurations indicated by the first specific identifier of the received DCI ( S18020 ), and may stop periodic transmission of the PUSCH based on the configured grant.

[0466] This method can be equally applied even when multiple SPS PDSCH configurations are configured. In this case, the DCI can be scrambled with the CS-RNTI as the first DCI.

[0467] Even when multiple configured grants or SPS PDSCH configurations are configured and activated using this method, multiple activated configurations can be released through one DCI.

[0468] Figure 19 is a flowchart illustrating an example of a method for releasing a configuration configured in a user equipment for transmission of a PUSCH by a base station according to an embodiment of the present invention.

[0469] refer to Figure 19 When multiple configurations (eg, configured grants) for PUSCH transmission are activated for a user equipment, the base station may indicate the release of the multiple configurations (or configured grants) to the user equipment through one DCI.

[0470] Specifically, the base station may allow the user equipment to be configured with one or more activated configurations for PUSCH transmission. In this case, PUSCH transmission may be periodically transmitted through multiple resources repeatedly configured based on the configured grant, and PUSCH may be transmitted by including different transport blocks in each resource.

[0471] Then, the base station may send configuration information for repeated transmission of the PUSCH to the user equipment (S19010). In this case, the configuration information may include multiple identifiers corresponding to specific values ​​of the HARQ process number field, and each of the multiple identifiers may individually correspond to one or more configurations for configured grant-based PUSCH transmission.

[0472] When the HARQ process number field is indicated by a specific value, one or more configurations corresponding to a plurality of identifiers may be released.

[0473] Then, the base station may transmit a first physical downlink control channel (PDCCH) including first downlink control information (DCI) to the user equipment (S19020).

[0474] In this case, the DCI may be included in the above Figures 12 to 17 As well as the fields and parameters described in Proposal 1 and Proposal 2.

[0475] For example, the DCI may include at least one of an NDI field, a HARQ process number field, an RV field, and an FDRA field for determining whether the DCI is valid. In this case, the HARQ process number field may not be used to determine the verification of the DCI based on whether one configuration or multiple configurations are activated to repeatedly transmit the PUSCH.

[0476] In addition, when multiple configurations are activated for repeated transmission of the PUSCH, the first DCI may be configured for transmission of the PUSCH based on the configured grant to include a first specific identifier (ID) for releasing one or more configurations. In this case, the first specific identifier may indicate the one or more configurations configured for transmission of the PUSCH.

[0477] In this case, the PUSCH refers to a channel periodically transmitted through resources repeatedly configured according to a configured grant.

[0478] If multiple configurations are activated for repeated transmission of PUSCH, the first specific identifier can be indicated by a hybrid automatic repeat request (HARQ) process number (HARQ process number) field of the first DCI, and the HARQ process number field can be used to identify one or more configurations among the multiple configurations.

[0479] Therefore, the base station can instruct to release multiple configurations for the user equipment by using a specific identifier indicated by the HARQ process number field included in one DCI.

[0480] Through this method, even when a plurality of configurations are activated instead of one configuration to repeatedly transmit a PUSCH, release of the plurality of activated configurations can be indicated at once through a specific field of DCI indicating the plurality of activated configurations.

[0481] The above description of the present invention is illustrative only, and it is readily understood that those skilled in the art can readily make modifications without departing from the technical concept of the present invention or changing the basic features. Therefore, the above embodiments should be considered illustrative and should not be construed as limiting. For example, each component described as a single type may be distributed, and similarly, components described as distributed may be implemented in a combined form.

[0482] The scope of the present invention is indicated by the appended claims rather than the detailed description, and it should be interpreted that all changes or modifications derived from the meaning and scope of the claims and their equivalents are included in the scope of the present invention.

Claims

1. A method performed by a user equipment in a wireless communication system, the method comprising: Receive a physical downlink control channel (PDCCH) in a downlink control information (DCI) format from a base station, The DCI format includes a frequency domain resource allocation (FDRA) field, a modulation and coding scheme (MCS) field, and a redundancy version (RV) field. When multiple semi-persistently scheduled physical downlink shared channel SPS PDSCH configurations are provided, determining the validity of the DCI format based on the value of the FDRA field according to the FDRA type to release part or all of the multiple SPS PDSCH configurations; and When the plurality of SPS PDSCH configurations are provided and the DCI format is valid to release some or all of the plurality of SPS PDSCH configurations, some or all of the plurality of SPS PDSCH configurations are released based on the DCI format.

2. The method according to claim 1, in, When the FDRA type is a bitmap-based resource allocation type, the DCI format is valid to release part or all of the multiple SPS PDSCH configurations depending on whether all bits of the FDRA field are set to '0'.

3. The method according to claim 2, in, When the FDRA type is a bitmap-based resource allocation type, the resource allocation scheme for the user equipment is a scheme indicating whether to allocate resource block groups (RBGs) using a bitmap.

4. The method according to claim 1, in, When the FDRA type is a resource indication value, RIV-based resource allocation type, the DCI format is valid to release some or all of the multiple SPS PDSCH configurations depending on whether all bits of the FDRA field are set to '1'.

5. The method according to claim 4, in, The resource allocation scheme for the user equipment is a scheme indicating a start point and a length of an allocated resource block (RB) set when the FDRA type is the RIV-based resource allocation type.

6. The method according to claim 1, in, The validity of the DCI format is determined by further considering the MCS field and the RV field to release part or all of the multiple SPS PDSCH configurations.

7. The method according to claim 1, in, When dynamic switching is configured, the validity of the DCI format to release part or all of the multiple SPS PDSCH configurations is determined by whether all bits of the FDRA field are set to '0', wherein the FDRA type is determined according to the value of the most significant bit MSB of the FDRA field.

8. The method according to claim 1, in, The DCI format further includes a hybrid automatic repeat request HARQ process number field, wherein, when a single SPS PDSCH configuration is provided, the HARQ process number field is considered to determine whether the DCI format is valid to release the single SPS PDSCH configuration, and Wherein, when the multiple SPS PDSCH configurations are provided, the HARQ process number field is not considered to determine whether the DCI format is valid to release some or all of the multiple SPS PDSCH configurations.

9. A user equipment configured to operate in a wireless communication system, the user equipment comprising: Communication module; and a processor, the processor controlling the communication module, wherein the processor is configured to: Receive a physical downlink control channel (PDCCH) in a downlink control information (DCI) format from a base station, The DCI format includes a frequency domain resource allocation (FDRA) field, a modulation and coding scheme (MCS) field, and a redundancy version (RV) field. When multiple semi-persistently scheduled physical downlink shared channel SPS PDSCH configurations are provided, determining the validity of the DCI format based on the value of the FDRA field according to the FDRA type to release part or all of the multiple SPS PDSCH configurations; and When the plurality of SPS PDSCH configurations are provided and the DCI format is valid to release some or all of the plurality of SPS PDSCH configurations, some or all of the plurality of SPS PDSCH configurations are released based on the DCI format.

10. The user equipment according to claim 9, in, When the FDRA type is a bitmap-based resource allocation type, the DCI format is effective to release part or all of the multiple SPS PDSCH configurations depending on whether all bits of the FDRA field are set to "0".

11. The user equipment according to claim 10, in, When the FDRA type is a bitmap-based resource allocation type, the resource allocation scheme for the user equipment is a scheme indicating whether to allocate resource block groups (RBGs) using a bitmap.

12. The user equipment according to claim 9, in, When the FDRA type is a resource indication value, RIV-based resource allocation type, the DCI format is valid to release some or all of the multiple SPS PDSCH configurations depending on whether all bits of the FDRA field are set to '1'.

13. The user equipment according to claim 12, in, The resource allocation scheme for the user equipment is a scheme indicating a start point and a length of an allocated resource block (RB) set when the FDRA type is the RIV-based resource allocation type.

14. The user equipment according to claim 9, in, The validity of the DCI format is determined by further considering the MCS field and the RV field to release part or all of the multiple SPS PDSCH configurations.

15. The user equipment according to claim 9, in, When dynamic switching is configured, the validity of the DCI format to release some or all of the multiple SPS PDSCH configurations is determined by whether all bits of the FDRA field are set to '0', wherein the FDRA type is determined according to the value of the most significant bit MSB of the FDRA field.

16. The user equipment according to claim 9, in, The DCI format further includes a hybrid automatic repeat request HARQ process number field, wherein, when a single SPS PDSCH configuration is provided, the HARQ process number field is considered to determine whether the DCI format is valid to release the single SPS PDSCH configuration, and Wherein, when the multiple SPS PDSCH configurations are provided, the HARQ process number field is not considered to determine whether the DCI format is valid to release some or all of the multiple SPS PDSCH configurations.

Images