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

Abstract

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

Description

[0001] This application is a divisional application of patent application No. 202080066917.5 (International Application No. PCT / KR2020 / 010931), filed on March 24, 2022, with an international application date of August 17, 2020, entitled "Method, Apparatus and System for Transmitting and Receiving Physical Uplink Shared Channel (PUSCH) in a Wireless Communication System". Technical Field

[0002] The present invention relates to wireless communication systems, and more particularly, to methods for transmitting and receiving Physical Uplink Shared Channel (PUSCH) in wireless communication systems. Background Technology

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

[0004] The downlink control channel (PDCCH / EPDCCH) mentioned above is used by the base station to send uplink / downlink scheduling allocation control information, uplink transmission power control information, and other control information to one or more user equipments. Since the resources available for a single PDCCH transmission by the base station are limited, different resources cannot be allocated to each user equipment, and control information should be sent to any user equipment through resource sharing. For example, in 3GPP LTE(-A), four resource elements (REs) can be grouped to form a resource element group (REG), generating nine control channel elements (CCEs). User equipments can be notified of the resources available for combining and transmitting one or more CCEs, and multiple user equipments can share and use CCEs. Here, the number of combined CCEs is called the CCE combination level, and the resources allocated to CCEs according to the possible CCE combination levels are called the search space. The search space can 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 (UE) performs decoding for multiple cases of all possible CCE combinations in the search space, and can identify whether the UE belongs to the PDCCH by the UE identifier included in the PDCCH. Therefore, this operation of the UE requires a long time to decode the PDCCH and inevitably leads to a large amount of energy consumption.

[0005] Efforts are underway to develop an improved 5G communication system, or pre-5G communication system, to meet the growing demand for wireless data services following the commercialization of 4G communication systems. For this purpose, 5G communication systems, or pre-5G communication systems, are referred to as super-4G network communication systems or post-LTE systems. The implementation of 5G communication systems in ultra-high frequency (mmWave) bands (e.g., the 60-GHz band) is being considered to achieve high data transmission rates. 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 MIMO technologies have been discussed in the field of 5G communication systems. Furthermore, 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, cooperative communication, multi-point cooperation (CoMP), and interference cancellation have been developed in the field of 5G communication systems. In addition, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding and modulation (ACM) schemes in the 5G system field, as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0006] Simultaneously, within the human-centric network of interconnected networks where humans generate and consume information, the Internet has evolved into the Internet of Things (IoT) network, which exchanges information between distributed components such as objects. The Internet of Everything (IoE) technology, combining IoT with big data processing through connections to cloud servers, is also emerging. Realizing IoT requires technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology. This has led to the recent research into technologies such as sensor networks, machine-to-machine (M2M), and machine-type communication (MTC) to connect objects. In the IoT environment, intelligent Internet of Things (IT) services can be provided, collecting and analyzing data generated from connected objects to create new value in human life. Through the integration and hybridization of existing information technology (IT) with various industries, IoT can be applied to areas such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0007] 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 communication (MTC) utilize 5G communication technologies (i.e., beamforming, MIMO, array antennas, etc.). The application of cloud radio access networks (cloud RAN) as a means of handling the aforementioned big data processing technologies can be seen as an example of the convergence of 5G and IoT technologies.

[0008] Mobile communication systems have typically been developed to provide voice services while protecting user activities. However, the scope of mobile communication systems has expanded beyond voice services to include data services, and high-speed data services are now being developed. However, resource shortages exist in current mobile communication systems used to provide these services, and users require even faster speeds. Therefore, a more advanced wireless communication system is needed.

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

[0010] In Rel-16 Enhanced URLLC (eURLLC), various techniques for providing lower latency and higher reliability are discussed. To provide lower latency, transmission of uplink control channels including two or more HARQ-ACKs in a single timeslot is supported. User equipment is able to send HARQ-ACKs as quickly as possible in response to successful reception of the downlink shared channel, thus ensuring lower latency. Summary of the Invention

[0011] Technical issues

[0012] The purpose of embodiments of the present invention is to provide a method for a user equipment to transmit a Physical Uplink Shared Channel (PUSCH) to a base station in a wireless communication system, and a user equipment thereof.

[0013] Furthermore, another object of the present invention is to provide a method and user equipment thereof for allocating resources for periodically sending PUSCH to a base station based on configuration-based licensing.

[0014] Furthermore, another object of the present invention is to provide a method and user equipment thereof for configuration-based license activation / release of configurations for periodically sending PUSCH to a base station.

[0015] Technical solution

[0016] A method for transmitting a Physical Uplink Shared Channel (PUSCH) from a user equipment to a base station in a wireless communication system includes: receiving from the base station a first Physical Downlink Control Channel (PDCCH) including first Downlink Control Information (DCI), the first DCI including a first specific identifier (ID) for releasing one or more configurations configured for transmission of a PUSCH based on configuration permission, the PUSCH representing a channel periodically transmitted by resources repeatedly configured according to configuration permission, 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.

[0017] Furthermore, in this invention, when multiple configurations are configured for the 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 of the multiple configurations.

[0018] Furthermore, in this invention, the method further includes receiving configuration information for identifying one or more configurations, wherein the configuration information includes a plurality of identifiers corresponding to a specific value of a HARQ process number field, each of the plurality of identifiers individually corresponding to one or more configurations, and the one or more configurations corresponding to the plurality of identifiers are released when the HARQ process number field is indicated by a specific value.

[0019] Furthermore, in this invention, the first DCI is scrambled with 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.

[0020] Furthermore, in this invention, when one configuration is configured for PUSCH transmission, DCI verification 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 PUSCH transmission, DCI verification is determined based on the NDI field, RV field, MCS field, and FDRA field, excluding the HARQ process number field.

[0021] Furthermore, in this invention, DCI indicates whether the release of one or more configurations is identified based on the value of the type of the FDRA field.

[0022] Furthermore, in this invention, when a dynamic switch is set to determine the type of FDRA based on the value of the most significant bit (MSB) of the FDRA field, the value of the FDRA field used to identify whether the DCI indicates the release of one or more configured FDRA fields varies depending on the type of FDRA.

[0023] Furthermore, in this invention, the method further includes receiving configuration information from a base station for the transmission of PUSCH, wherein the configuration information includes the offset, period, and number of HARQ processes for determining the HARQ process number for the transmission of PUSCH.

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

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

[0026] Furthermore, in this invention, the second DCI further includes a start group index of multiple resource groups for the transmission of PUSCH and the length of multiple resource groups.

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

[0028] Beneficial effects

[0029] According to an embodiment of the present invention, the method for repeatedly transmitting PUSCH to a base station by a user equipment can achieve the target performance of providing low-latency, high-reliability service in a 5G wireless communication system by enabling the user equipment to repeatedly transmit PUSCH to the base station as quickly as possible.

[0030] Furthermore, the present invention has the effect of efficiently allocating resource block groups for periodic transfers of PUSCH based on configured permissions via a start group index and its length allocation group.

[0031] Furthermore, the present invention has the effect of effectively activating / releasing multiple configurations for periodic transmission of PUSCH by activating / releasing configuration-based permissions via an identifier.

[0032] The effects that can be obtained from this disclosure are not limited to those described above, and other effects not mentioned will be clearly understood by those skilled in the art from the following description. Attached Figure Description

[0033] Figure 1This diagram illustrates an example of a wireless frame structure used in a wireless communication system.

[0034] Figure 2 This diagram illustrates an example of a downlink (DL) / uplink (UL) timeslot structure in a wireless communication system.

[0035] Figure 3 This is a diagram used to illustrate the physical channels used in 3GPP systems and typical signal transmission methods using those physical channels.

[0036] Figure 4 The diagram illustrates the SS / PBCH block used for initial cell access in a 3GPP NR system.

[0037] Figure 5 The diagram illustrates the process of transmitting control information and control channels in a 3GPP NR system.

[0038] Figure 6 The diagram shows a control resource set (CORESET) in a 3GPP NR system that can transmit the Physical Downlink Control Channel (PUCCH).

[0039] Figure 7 The diagram illustrates a method for configuring the PDCCH search space in a 3GPP NR system.

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

[0041] Figure 9 This diagram is used to illustrate signal carrier communication and multi-carrier communication.

[0042] Figure 10 This is a diagram illustrating an example of the application of cross-carrier scheduling technology.

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

[0044] Figure 12 This is a diagram illustrating an example of uplink licensing that can be applied to embodiments of the present invention.

[0045] Figure 13 This is a diagram illustrating an example of a grant-free initial transfer.

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

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

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

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

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

[0051] Figure 19 This is a flowchart illustrating an example of a method for releasing a configuration configured in a user equipment for transmitting PUSCH by a base station, according to an embodiment of the present invention. Detailed Implementation

[0052] The terminology used in this specification adopts, as far as possible, commonly used terms that are widely used in light of the functions of this invention; however, these terms may be modified according to the intent, practice, and emergence of new technologies of those skilled in the art. Furthermore, in certain cases, there are terms arbitrarily chosen by the applicant, and in such cases, their meaning will be described in the corresponding descriptive section of this invention. Therefore, it is intended to reveal that the terminology used in this specification should not be analyzed solely based on its name, but rather on its substantive meaning within the entire specification.

[0053] Throughout the specification and subsequent claims, when an element is described as being “connected” to another element, that element may be “directly connected” to the other element or “electrically connected” to the other element via a third element. Furthermore, unless explicitly stated otherwise, the word “comprising” will be understood to imply the inclusion of the stated element without implying the exclusion of any other elements. Additionally, in some exemplary embodiments, limitations such as “greater than or equal to” or “less than or equal to” based on a specific threshold may be appropriately replaced with “greater than” or “less than”, respectively.

[0054] The following technologies can be used in various wireless access systems: such as Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier-FDMA (SC-FDMA). CDMA can be implemented using wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using wireless technologies such as Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), and Enhanced Data Rate GSM Evolution (EDGE). OFDMA can be implemented using wireless technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is 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 intended to support Enhanced Mobile Broadband (eMBB), Ultra-Reliable Low Latency Communication (URLLC), and Massive Machine-Type Communication (mMTC) services as required by IMT-2020. For clarity, 3GPP NR is described primarily, but the technical concept of this invention is not limited thereto.

[0055] Unless otherwise specified in this specification, "base station" may refer to the next-generation node B (gNB) as defined in 3GPP NR. Furthermore, unless otherwise specified, "terminal" may refer to "user equipment" (UE).

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

[0057] Figure 1 This diagram illustrates an example of a wireless frame structure used in a wireless communication system. (Reference) Figure 1 The radio frames (or radio frames) used in 3GPP NR systems can have a duration of 10ms (Δf). max N f / 100)*T c The length of the radio frame is Δf. Furthermore, a radio frame consists of 10 equal-sized subframes (SF). Here, Δf... max =480*10 3 Hz, Nf =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 single radio frame. Each subframe is 1ms long and can include one or more time slots depending on the subcarrier spacing. More specifically, in 3GPP NR systems, the usable subcarrier spacing is 15*2. μ The subcarrier spacing can be configured as μ = 0, 1, 2, 3, 4, and the subcarrier frequency can be kHz. That is, 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz can be used for subcarrier spacing. A subframe of 1ms length can include 2... μ There are 2 time slots. In this case, the length of each time slot is 2. -μ ms. This can range from 0 to 2. μ The number -1 is assigned to 2 within a subframe. μ Each time slot. Furthermore, slots from 0 to 10*2 can be allocated. μ The number -1 is assigned to a time slot within a radio frame. Time resources can be distinguished by at least one of the radio frame number (also known as the radio frame index), subframe number (also known as the subframe index), and time slot number (or time slot index).

[0058] Figure 2 This diagram illustrates an example of a downlink (DL) / uplink (UL) timeslot structure in a wireless communication system. Specifically, Figure 2 This illustrates the structure of the resource grid in a 3GPP NR system. Each antenna port has one resource grid. (Reference) Figure 2 A time slot comprises 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 simply referred to as a symbol. An RB comprises 12 consecutive subcarriers in the frequency domain. (See 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 The resource grid of OFDM symbols is used for representation. Here, x = DL when the signal is a DL signal, and x = UL when the signal is a UL signal. N size,μ grid,xThis represents the number of resource blocks (RBs) based on the subcarrier spacing component μ (x is either DL or UL), and N slot symb This indicates the number of OFDM symbols in the time slot. N RB sc It is the number of subcarriers that make up an RB and N RB sc =12. OFDM symbols can be referred to as cyclic shift OFDM (CP-OFDM) symbols or discrete Fourier transform extended OFDM (DFT-s-OFDM) symbols according to the multiple access scheme.

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

[0060] An RB can be composed of N in the frequency domain RB sc (For example, 12) consecutive subcarriers are defined. For reference, a resource configured with one OFDM symbol and one subcarrier can be called a resource element (RE) or tone. Therefore, an RB can be configured with N slot symb *N RB sc 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 from 0 to N in the frequency domain. size,μ grid,x *N RB sc -1 is the index assigned, and l can be from 0 to N in the time domain. slot symb -1 The index assigned.

[0061] To enable the UE to receive or transmit signals from the base station, the UE's time / frequency can be synchronized with the base station's time / frequency. This is because when the base station and the UE are synchronized, the UE can determine the necessary time and frequency parameters to demodulate the DL signal and transmit the UL signal at the correct time.

[0062] Each symbol of a radio frame used in Time Division Duplex (TDD) or unpaired spectrum can be configured with at least one of DL symbol, UL symbol, and flexible symbol. Radio frames used as DL carriers in Frequency Division Duplex (FDD) or paired spectrum can be configured with either DL symbol or flexible symbol, while radio frames used as UL carriers can be configured with either UL symbol or flexible symbol. In a DL symbol, DL transmission is possible, but UL transmission is not. In a UL symbol, UL transmission is possible, but DL transmission is not. A flexible symbol can be determined as being used as either DL or UL based on the signal.

[0063] Information regarding the type of each symbol—that is, information indicating any of DL symbols, UL symbols, and flexible symbols—can be configured with cell-specific or public Radio Resource Control (RRC) signals. Furthermore, information regarding the type of each symbol can be additionally configured with UE-specific or dedicated RRC signals. The base station uses cell-specific RRC signals to inform i) the period of the cell-specific time slot configuration, ii) the number of time slots with only DL symbols starting from the beginning of the cell-specific time slot configuration period, iii) the number of DL symbols starting from the first symbol of the time slot immediately following a time slot with only DL symbols, iv) the number of time slots with only UL symbols starting from the end of the cell-specific time slot configuration period, and v) the number of UL symbols starting from the last symbol of the time slot immediately preceding a time slot with only UL symbols. Here, a symbol not configured with either UL or DL ​​symbols is a flexible symbol.

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

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

[0066] 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 the primary synchronization signal (PSS) and the 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 the physical broadcast channel from the base station and obtain the broadcast information in the cell.

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

[0068] 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 of radio resource control (RRC) and is referred to as remaining system information or system information block (SIB)1.

[0069] When a UE initially accesses a base station or lacks radio resources for signal transmission, the UE can perform a random access procedure (operations S103 to S106). First, the UE can send a preamble via the Physical Random Access Channel (PRACH) (S103) and receive a response message for the preamble from the base station via the PDCCH and the corresponding PDSCH (S104). When the UE receives a valid random access response message, the UE sends data, including its identifier, to the base station via the Physical Uplink Shared Channel (PUSCH) indicated by the UL license sent by the base station via the PDCCH (S105). Next, the UE waits for the reception of the PDCCH as an indication from the base station for conflict resolution. If the UE successfully receives the PDCCH via its identifier (S106), the random access procedure is terminated. During the random access procedure, the user equipment can obtain the terminal-specific system information required for proper operation of the user equipment in the physical layer of the RRC layer. When the user equipment obtains the terminal-specific system information from the RRC layer, the user equipment enters RRC connection mode.

[0070] The RRC layer is used to generate or manage messages between user equipment (UE) and the radio access network (RAN). More specifically, base stations and UEs in the RRC layer can perform tasks such as broadcasting cell system information required by all UEs in the cell, managing the transmission of paging messages, mobility management and handover, UE measurement reporting and control, and storage management including UE capability management and device management. Typically, because the updates of signals transmitted in the RRC layer (hereinafter referred to as RRC signals) are longer than the transmission / reception period (i.e., transmission time interval (TTI)) in the physical layer, RRC signals can remain unchanged for a long period.

[0071] Following the above process, the UE receives the PDCCH / PDSCH (S107) and transmits the Physical Uplink Shared Channel (PUSCH) / Physical Uplink Control Channel (PUCCH) (S108) as a general UL / DL signal transmission process. Specifically, the UE can receive downlink control information (DCI) via the PDCCH. The DCI may include control information for the UE, such as resource allocation information. Furthermore, the format of the DCI can vary depending on the intended purpose. The uplink control information (UCI) transmitted by the UE to the base station via the UL includes DL / UL ACK / NACK signals, Channel Quality Indicator (CQI), Precoding Matrix Index (PMI), Rank Indicator (RI), etc. Here, CQI, PMI, and RI can be included in the Channel State Information (CSI). In a 3GPP NR system, the UE can transmit control information such as the aforementioned HARQ-ACK and CSI via the PUSCH and / or PUCCH.

[0072] Figure 4 The diagram illustrates the SS / PBCH block used for initial cell access in a 3GPP NR system. When power is on or when accessing a new cell, the UE can obtain time and frequency synchronization with that cell and perform an initial cell search procedure. The UE can detect the physical cell identifier N of the cell during the cell search procedure. cell ID Therefore, the UE can receive synchronization signals from the base station, such as the primary synchronization signal (PSS) and secondary synchronization signal (SSS), and synchronize with the base station. In this case, the UE can obtain information such as the cell identifier (ID).

[0073] refer to Figure 4 Section (a) will describe the synchronization signal (SS) in more detail. Synchronization signals 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 slot synchronization. SSS can be used to obtain frame synchronization and cell group ID. (See reference...) Figure 4 According to (a) and Table 2, the SS / PBCH block can be configured with 20 consecutive RBs (=240 subcarriers) on the frequency axis and 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 via subcarriers 56 to 182 and the SSS is transmitted in the third OFDM symbol. Here, the lowest subcarrier index of the SS / PBCH block is numbered starting from 0. In the first OFDM symbol for transmitting the PSS, the base station does not transmit signals via the remaining subcarriers, i.e., subcarriers 0 to 55 and subcarriers 183 to 239. Furthermore, in the third OFDM symbol for transmitting the SSS, the base station does not transmit signals via subcarriers 48 to 55 and subcarriers 183 to 191. The base station transmits the Physical Broadcast Channel (PBCH) via the remaining REs in the SS / PBCH block, excluding the signals mentioned above.

[0074] [Table 1]

[0075]

[0076] The SS allows a total of 1008 unique physical layer cell IDs to be divided into 336 physical layer cell identifier groups through a combination of three PSSs and SSSs. Each group includes three unique identifiers, specifically ensuring that each physical layer cell ID is only a part of one physical layer cell identifier group. Therefore, the physical layer cell ID N cell ID =3N (1) ID +N (2) IDAn index N, ranging from 0 to 335, can be used to indicate the physical layer cell identifier group. (1) ID and an index N indicating the range of physical layer identifiers in the physical layer cell identifier group from 0 to 2. (2) ID Uniquely defined. The UE can detect the PSS and identify one of three unique physical layer identifiers. Furthermore, the UE can detect the SSS and identify one of 336 physical layer cell IDs associated with the physical layer identifier. In this case, the sequence d of the PSS... PSS (n) is as follows.

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

[0078]

[0079] 0≤n<127

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

[0081] [x(6) (5) (4) x(3) x(2) x(1) x(0)]=[1 1 1 0 1 1 0]

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

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

[0084]

[0085]

[0086] 0≤n<127

[0087] x0(i+7)=(x0(i+4)+x0(i))mod2

[0088] Here, x1(i+7) = (x1(i+1) + x1(i)) mod 2 and is given as

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

[0090] [x1(6) x1(5) x14) x1(3) x1(2) x1(1) x1(0)]=[0 0 0 0 0 0 1]

[0091] A radio frame with a length of 10ms can be divided into two half-frames with a length of 5ms each. (Reference) Figure 4 Section (b) describes the time slots for transmitting the SS / PBCH block in each half-frame. The time slot for transmitting the SS / PBCH block can be any of cases A, B, C, D, and E. In case A, the subcarrier spacing is 15 kHz and the start time of the SS / PBCH block is the ({2,8}+14*n)th symbol. In this case, at carrier frequencies of 3 GHz or lower, n = 0 or 1. Furthermore, at carrier frequencies above 3 GHz and below 6 GHz, n can be 0, 1, 2, or 3. In case B, the subcarrier spacing is 30 kHz and the start time of the SS / PBCH block is {4,8,16,20}+28*n. In this case, at carrier frequencies of 3 GHz or lower, n = 0. Furthermore, at carrier frequencies above 3 GHz and below 6 GHz, n can be 0 or 1. In case C, the subcarrier spacing is 30 kHz and the start time of the SS / PBCH block is the ({2,8}+14*n)th symbol. In this case, at carrier frequencies of 3 GHz or lower, n = 0 or 1. Furthermore, at carrier frequencies above 3 GHz but below 6 GHz, n can be 0, 1, 2, or 3. In case D, the subcarrier spacing is 120 kHz and the start time of the SS / PBCH block is the ({4,8,16,20}+28*n)th symbol. In this case, at carrier frequencies 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 start time of the SS / PBCH block is the ({8,12,16,20,32,36,40,44}+56*n)th symbol. In this case, at carrier frequencies of 6 GHz or higher, n = 0, 1, 2, 3, 5, 6, 7, 8.

[0092] Figure 5 The diagram illustrates the process of transmitting control information and using the control channel in a 3GPP NR system. (Reference) Figure 5(a) The base station may add a Cyclic Redundancy Check (CRC) masked with a Radio Network Temporary Identifier (RNTI) (e.g., XOR operation) to the 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 / objective of each control information. The common RNTI used by one or more UEs may include at least one of System Information RNTI (SI-RNTI), Paging RNTI (P-RNTI), Random Access RNTI (RA-RNTI), and Transmit Power Control RNTI (TPC-RNTI). In addition, UE-specific RNTIs may include at least one of Cell Temporary RNTI (C-RNTI) and 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 the DCI based on the PDCCH structure based on Control Channel Elements (CCE) (S208). Furthermore, the base station can apply additional processes such as scrambling, modulation (e.g., QPSK), and interleaving to the multiplexed DCI (S210), and then map the DCI to the resources to be transmitted. CCE is the basic resource unit used for PDCCH, and a CCE can include multiple (e.g., six) Resource Element Groups (REGs). A REG can be configured with multiple (e.g., 12) REs. The number of CCEs used for a PDCCH can be defined as the aggregation level. In 3GPPNR systems, aggregation levels of 1, 2, 4, 8, or 16 can be used. Figure 5 b is a diagram relating to CCE aggregation levels and PDCCH multiplexing, illustrating the type of CCE aggregation level used for a PDCCH and the CCEs sent in the control area accordingly.

[0093] Figure 6 The diagram illustrates a control resource set (CORESET) in a 3GPP NR system where the Physical Downlink Control Channel (PUCCH) can be transmitted. A CORESET is a time-frequency resource in which the PDCCH (i.e., the control signal for the UE) is transmitted. Furthermore, a search space, described later, can be mapped to a CORESET. Therefore, the UE can monitor the time-frequency domain designated as a CORESET instead of monitoring all frequency bands used for PDCCH reception and decode the PDCCH mapped to the CORESET. The base station can configure one or more CORESETs for each cell for the UE. A CORESET can be configured with up to three consecutive symbols on the time axis. Additionally, a CORESET can be configured in units of six consecutive PRBs on the frequency axis. Figure 5In this embodiment, CORESET#1 is configured with consecutive PRBs, while CORESET#2 and CORESET#3 are configured with discontinuous PRBs. A CORESET can reside in any symbol within a time slot. For example, in... Figure 5 In one embodiment, CORESET#1 begins at the first symbol of the time slot, CORESET#2 begins at the fifth symbol of the time slot, and CORESET#9 begins at the ninth symbol of the time slot.

[0094] Figure 7 The diagram illustrates a method for setting up a PDCCH search space in a 3GPP NR system. Each core may have at least one search space to transmit a PDCCH to a UE. In embodiments of this disclosure, the search space is the set of all time-frequency resources (hereinafter referred to as PDCCH candidates) capable of transmitting a UE's PDCCH. The search space may include a common search space that requires common searching by UEs in 3GPP NR and a terminal-specific search space or UE-specific search space that requires specific UEs to search. In the common search space, a UE may monitor a PDCCH configured to be commonly searched by all UEs belonging to the same base station cell. Furthermore, a UE-specific search space may be set up for each UE, allowing the UE to monitor the PDCCH allocated to each UE at search space locations that vary depending on the UE. In the case of a UE-specific search space, the search spaces between UEs may partially overlap and be allocated due to the limited control area that can be used to allocate PDCCHs. Monitoring the PDCCH includes blind decoding of PDCCH candidates within the search space. When blind decoding is successful, it can be expressed as (successfully) detecting / receiving the PDCCH, while when blind decoding fails, it can be expressed as not detecting / receiving or not successfully detecting / receiving the PDCCH.

[0095] For ease of explanation, a PDCCH scrambled with a Group Common (GC) RNTI previously known to the UE in order to send DL control information to one or more UEs is called a Group Common (GC) PDCCH or a common PDCCH. Furthermore, a PDCCH scrambled with a RNTI of a specific terminal already known to a specific UE in order to send UL scheduling information or DL ​​scheduling information to that specific UE is called a UE-specific PDCCH. Common PDCCHs can be included in the common search space, and UE-specific PDCCHs can be included in either the common search space or the UE-specific PDCCH.

[0096] The base station can signal to each UE or group of UEs via the PDSCH information regarding resource allocation for the Paging Channel (PCH) and Downlink Shared Channel (DL-SCH) as transport channels (i.e., DL clearance) or resource allocation for the Uplink Shared Channel (UL-SCH) and Hybrid Automatic Repeat Request (HARQ) (i.e., UL clearance). The base station can transmit PCH and DL-SCH transport blocks via the PDSCH. The base station can also transmit data excluding specific control information or specific service data via the PDSCH. Furthermore, the UE can receive data excluding specific control information or specific service data via the PDSCH.

[0097] The base station can include information in the PDCCH about which UE (one or more UEs) the PDSCH data is sent to and how the PDSCH data will be received and decoded by the corresponding UE, and then send the PDCCH. For example, suppose the DCI sent via 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 location) and indicates transmission format information "C" (e.g., block size, modulation scheme, coding information, etc.). The UE uses the RNTI information it possesses to monitor the PDCCH. In this case, if there is a UE performing blind decoding of the PDCCH using RNTI "A", then that UE receives the PDCCH and, based on the information in the received PDCCH, receives the PDSCH indicated by "B" and "C".

[0098] Table 2 shows an example of the Physical Uplink Control Channel (PUCCH) used in a wireless communication system.

[0099] [Table 2]

[0100] PUCCH format Length of OFDM symbol Number of bits 0 1-2 ≤2 1 4-14 ≤2 2 1-2 ＞2 3 4-14 ＞2 4 4-14 ＞2

[0101] PUCCH can be used to send the following UL control information (UCI).

[0102] - Scheduling Request (SR): Information used to request UL UL-SCH resources.

[0103] -HARQ-ACK: A response to the PDCCH (indicating DL SPS release) and / or to a DL transport block (TB) on the PDSCH. HARQ-ACK indicates whether information transmitted on the PDCCH or PDSCH has been received. HARQ-ACK responses include positive ACK (abbreviated as ACK), negative ACK (hereinafter NACK), discontinuous transmission (DTX), or NACK / DTX. Here, the terms HARQ-ACK are used interchangeably with HARQ-ACK / NACK and ACK / NACK. Typically, ACK can be represented by a bit value of 1, while NACK can be represented by a bit value of 0.

[0104] - Channel State Information (CSI): Feedback information about the DL channel. The UE generates it based on the CSI-reference signal (RS) transmitted by the base station. 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.

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

[0106] PUCCH format 0 is a format capable of transmitting 1 or 2 bits of HARQ-ACK information or SR. PUCCH format 0 can be transmitted using one or two OFDM symbols on the time axis and one PRB on the frequency axis. When transmitting PUCCH format 0 using two OFDM symbols, the same sequence on both symbols can be transmitted using different RBs. Here, the sequence can be a cyclically shifted (CS) sequence from the basic sequence used in PUCCH format 0. In this way, the user equipment can obtain frequency diversity gain. More specifically, the user equipment can, according to M... bit Bit UCI (M) bit =1 or 2) to determine the cyclic shift (CS) value m cs Additionally, based on a determined CS value m cs A cyclic shift of a basic sequence of length 12 yields a sequence that can be mapped to an OFDM symbol and 12 REs of an RB for transmission. When the cyclic shift available to the user equipment is 12 and M... bit When M = 1, 1 bit UCI 0 and 1 can be mapped to two cyclic shift sequences with a cyclic shift value difference of 6, respectively. Additionally, when M... bit When =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.

[0107] PUCCH format 1 can deliver 1 or 2 bits of HARQ-ACK information or SR. PUCCH format 1 can be transmitted via consecutive OFDM symbols on the time axis and a 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, it can be used for M... bit BPSK modulation is performed using a UCI of 1. The UE can then use Quadrature Phase Shift Keying (QPSK) to modulate the M... bit Modulation is performed using a UCI of 2. The signal is obtained by multiplying the modulated complex-valued symbol d(0) by a sequence of length 12. In this case, the sequence can be the base sequence used for PUCCH format 0. The UE transmits the obtained signal by extending the even-numbered OFDM symbols assigned to PUCCH format 1 with a time-axis orthogonal cover code (OCC). PUCCH format 1 determines the maximum number of different UEs multiplexed in a RB based on the length of the OCC to be used. The demodulation reference signal (DMRS) can be extended with the OCC and mapped to the odd-numbered OFDM symbols of PUCCH format 1.

[0108] PUCCH format 2 can deliver more than 2 bits of UCI. PUCCH format 2 can be transmitted via one or two OFDM symbols on the time axis and one or more RBs on the frequency axis. When transmitting PUCCH format 2 in two OFDM symbols, the sequences transmitted in different RBs through the two OFDM symbols can be identical. Here, the sequence can be multiple 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 One bit UCI (M bit >2) Perform bit-level scrambling, QPSK modulation, and map it to the RB of one or two OFDM symbols. Here, the number of RBs can be one from 1 to 16.

[0109] 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 using consecutive 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 utilizes e / 2-binary phase shift keying (BPSK) or QPSK to transmit M... bit One bit UCI (M bit >2) Modulate to generate complex numerical symbols d(0) to d(M) symb-1Here, when using π / 2-BPSK, M symb =M bit However, when using QPSK, M symb =M bit / 2. The UE may not apply block unit extension to PUCCH format 3. However, the UE may use a 12-length PreDFT-OCC to apply block unit extension to one RB (i.e., 12 subcarriers), 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.

[0110] In this scenario, the number of Restricted Blocks (RBs) occupied by PUCCH Format 2, PUCCH Format 3, or PUCCH Format 4 can be determined based on the length of the UCI sent by the UE and the maximum coding rate. When the UE uses PUCCH Format 2, it can send HARQ-ACK and CSI information together via PUCCH. When the number of RBs that the UE can send exceeds the maximum number of RBs that can be used with PUCCH Format 2, PUCCH 3, or PUCCH Format 4, the UE can send only the remaining UCI information without sending some UCI information, based on the priority of the UCI information.

[0111] PUCCH format 1, PUCCH format 3, or PUCCH format 4 can be configured using the RRC signal to indicate frequency hopping in the time slot. When frequency hopping is configured, the index of the RB to be hopped can be configured using the RRC signal. When PUCCH format 1, PUCCH format 3, or PUCCH format 4 is transmitted over 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.

[0112] 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 via an RRC signal. The repeatedly transmitted PUCCH must begin at a constant position in the OFDM symbol within each time slot and have a constant length. When one of the OFDM symbols in the time slot where the UE should transmit the PUCCH is indicated as a DL symbol via an RRC signal, the UE can choose not to transmit the PUCCH in the corresponding time slot and delay the transmission of the PUCCH to the next time slot.

[0113] In 3GPP NR systems, user equipment (UEs) can perform transmission / reception using bandwidth less than or equal to the carrier (or cell) bandwidth. For this purpose, UEs can receive a bandwidth portion (BWP) configuration configured with a portion of the carrier bandwidth as a contiguous bandwidth. Under TDD operation or operating in unpaired spectrum, UEs can receive up to four DL / UL BWP pairs in a single carrier (or cell). Furthermore, UEs can activate one DL / UL BWP pair. Under FDD operation or operating in paired spectrum, UEs 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), UEs can activate one DL BWP and one UL BWP. UEs may not receive or transmit in time-frequency resources other than the activated BWPs. The activated BWP can be referred to as the active BWP.

[0114] The base station can indicate the active BWP among the BWPs configured for the user equipment (UE) via downlink control information (DCI). The BWP indicated by the DCI is activated, while other configured BWPs are deactivated. In a TDD-operated carrier (or cell), the base station can add a Bandwidth Part Indicator (BPI) indicating the BWP to be activated to the DCI of the scheduling PDSCH or PUSCH to change the UE's DL / UL BWP pair. The UE can receive the DCI of the scheduling PDSCH or PUSCH and can identify the DL / UL BWP pair activated based on the BPI. In the case of an FDD-operated downlink carrier (or cell), the base station can add a BPI indicating the BWP to be activated to the DCI of the scheduling PDSCH to change the base station's DL BWP. In the case of an FDD-operated uplink carrier (or cell), the base station can add a BPI indicating the BWP to be activated to the DCI of the scheduling PUSCH to change the base station's UL BWP.

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

[0116] Carrier aggregation is a method in which a UE uses multiple frequency blocks or (in a logical sense) cells configured with UL resources (or component carriers) and / or DL ​​resources (or component carriers) as a large logical band so that the wireless communication system can use a wider bandwidth. A component carrier can also be referred to by the terms primary cell (PCell), secondary cell (SCell), or primary SCell (PScell). However, for convenience, the term "component carrier" will be used below.

[0117] refer to Figure 8As an example of a 3GPP NR system, the entire system bandwidth can include up to 16 component carriers, and each component carrier can have a bandwidth of up to 400 MHz. Component carriers can include one or more physically contiguous subcarriers. Although in Figure 8 The diagram shows each component carrier with the same bandwidth, but this is merely an example, and each component carrier can have a different bandwidth. Furthermore, although each component carrier is shown as adjacent to each other on the frequency axis, the diagram is shown conceptually, and each component carrier can be physically adjacent to each other or spaced apart.

[0118] Different center frequencies can be used for each component carrier. Alternatively, a common center frequency can be used for physically adjacent component carriers. Assuming in Figure 8 In one embodiment, all component carriers are physically adjacent, so center frequency A can be used in all component carriers. Alternatively, assuming that the component carriers are not physically adjacent to each other, then center frequency A and center frequency B can be used in each component carrier.

[0119] When extending the total system bandwidth through carrier aggregation, the bandwidth used for communication with each UE can be defined on a component carrier basis. UE A can use 100MHz as the total system bandwidth and perform communication using all five component carriers. UEs B1-B5 can perform communication using only 20MHz bandwidth and one component carrier. UEs C1 and C2 can each use 40MHz bandwidth and two component carriers for 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.

[0120] Figure 9 This is a diagram used to illustrate signal carrier communication and multi-carrier communication. Specifically, Figure 9 (a) shows the single-carrier subframe structure and Figure 9 (b) shows the multi-carrier subframe structure.

[0121] refer to Figure 9 (a) In FDD mode, a typical wireless communication system can perform data transmission or reception using a DL band and a corresponding UL band. In another specific embodiment, in TDD mode, the wireless communication system can divide radio frames into UL time units and DL time units in the time domain, and perform data transmission or reception using the UL / DL time units. (See reference...) Figure 9(b) It is possible to aggregate three 20MHz component carriers (CCs) into each of the UL and DL, enabling a bandwidth of 60MHz. Each CC can be adjacent to or not adjacent to each other in the frequency domain. Figure 9 (b) illustrates a case where the bandwidth of the ULCC and DLCC are the same and symmetrical, but the bandwidth of each CC can be determined independently. Furthermore, asymmetric carrier aggregation with different numbers of UL CCs and DL CCs is possible. The DL / UL CCs allocated / configured to a specific UE via RRC can be referred to as the serving DL / UL CCs for that specific UE.

[0122] A base station can communicate with a UE by activating some or all of the UE's serving CCs or by deactivating some CCs. The base station can change the CCs to be activated / deactivated, and can also 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. A CC that is not deactivated by the UE is called the primary CC (PCC) or primary cell (PCell), while CCs that the base station can freely activate / deactivate are called secondary CCs (SCCs) or secondary cells (SCells).

[0123] Meanwhile, 3GPP NR uses the concept of cells to manage radio resources. A cell is defined as a combination of DL resources and UL resources, i.e., a combination of DL CC and UL CC. A cell can be configured with DL resources alone, or it can be configured with a combination of DL resources and UL resources. When carrier aggregation is supported, the link between the carrier frequencies of DL resources (or DL ​​CC) and 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 a PCC is called a PCell, and the cell corresponding to an SCC is called an SCell. The carrier corresponding to a PCell in DL is the DL PCC, and the carrier corresponding to a PCell in UL is the UL PCC. Similarly, the carrier corresponding to an SCell in DL is the DL SCC, and the carrier corresponding to an SCell in UL is the UL SCC. Depending on the UE's 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, only one serving cell is configured with only a PCell.

[0124] As mentioned above, the term "cell" used in carrier aggregation is distinguished from the term "cell" referring to a geographical area that provides communication services through a base station or an antenna array. That is, a component carrier can also be referred to as a scheduled 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 representing a geographical area are referred to as cells.

[0125] Figure 10 This diagram illustrates an example of cross-carrier scheduling technology. When cross-carrier scheduling is set up, the control channel transmitted via the first CC can use the Carrier Indicator Field (CIF) to schedule the data channel transmitted via either the first CC or the second CC. The CIF is included in the DCI. In other words, a scheduling cell is set up, and the DL license / UL license transmitted in the PDCCH area of ​​that 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. A PCell can essentially be a scheduling cell, and a specific SCell can be designated as a scheduling cell by a higher layer.

[0126] exist Figure 10 In the embodiment, it is assumed that three DL CCs are combined. Here, it is assumed that DL component carrier #0 is a DLPCC (or PCell), and DL component carriers #1 and #2 are DL SCCs (or SCells). Furthermore, it is assumed that the DLPCC is set as a PDCCH monitoring CC. When cross-carrier scheduling is not configured via UE-specific (or UE group-specific or cell-specific) higher-layer signaling, CIF is disabled, and each DL CC can transmit only the PDCCH for scheduling its PDSCH according to the NR PDCCH rules without CIF (non-cross-carrier scheduling, self-carrier scheduling). Meanwhile, if cross-carrier scheduling is configured via 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 transmit not only the PDCCH for scheduling DL CC A but also the PDCCH for scheduling another CC (cross-carrier scheduling). On the other hand, no PDCCH is transmitted in another DL CC. Therefore, the UE monitors the PDCCH excluding CIF to receive the PDSCH of self-carrier scheduling depending on whether cross-carrier scheduling is configured for the UE, or monitors the PDCCH including CIF to receive the PDSCH of cross-carrier scheduling.

[0127] on the other hand, Figure 9 and Figure 10 The diagram illustrates the subframe structure of a 3GPP LTE-A system, and the same or similar configuration can be applied to a 3GPP NR system. However, in a 3GPP NR system, Figure 9 and Figure 10 Subframes can be replaced with time slots.

[0128] Figure 11 This is a block diagram illustrating the configuration of a UE and a base station according to embodiments of the present disclosure. In embodiments 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 can be referred to as a User Equipment (UE), a Station (STA), a Mobile Subscriber (MS), etc. Furthermore, in embodiments of the present disclosure, the base station controls and manages cells (e.g., macro cells, femtocells, picocells, etc.) corresponding to the service area, and performs functions such as signal transmission, channel designation, channel monitoring, self-diagnosis, and relaying. The base station can be referred to as a Next Generation Node B (gNB) or an Access Point (AP).

[0129] As shown in the accompanying drawings, 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.

[0130] First, the processor 110 can execute various instructions or procedures and process data within the UE 100. Furthermore, the processor 110 can control the overall operation of each unit including 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 this 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.

[0131] Next, the communication module 120 can be an integrated module that uses a wireless communication network to perform wireless communication and uses a wireless LAN to perform wireless LAN access. For this purpose, the communication module 120 can include multiple network interface cards (NICs), such as cellular communication interface cards 121 and 122 and a license-free band communication interface card 123, either internally or externally. In the accompanying drawings, the communication module 120 is shown as an integrated module, but unlike the drawings, each network interface card can be arranged independently depending on the circuit configuration or usage.

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

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

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

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

[0136] 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. Furthermore, the user interface 140 can use various output means to execute output based on instructions from the processor 110.

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

[0138] Furthermore, the base station 200 according to embodiments of the present disclosure may include a processor 210, a communication module 220, and a memory 230.

[0139] First, the processor 210 can execute various instructions or programs and process the internal data of the base station 200. Furthermore, 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 this disclosure. For example, the processor 210 can notify time slot configurations with signals and perform communication based on the time slot configurations notified by the used signals.

[0140] Next, the communication module 220 can be an integrated module that uses a wireless communication network to perform wireless communication and uses a wireless LAN to perform wireless LAN access. For this purpose, the communication module 120 can include multiple network interface cards, such as cellular communication interface cards 221 and 222 and a license-free band communication interface card 223, either internally or externally. In the accompanying drawings, the communication module 220 is shown as an integral integrated module; however, unlike the drawings, each network interface card can be arranged independently depending on the circuit configuration or usage.

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

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

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

[0144] Figure 11 This 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 individually are logically divided elements of the device. Therefore, the aforementioned elements of the device can be installed in a single chip or multiple chips depending on the device design. Furthermore, a portion of the configuration of the UE 100, such as a user interface 140, a display unit 150, etc., may be selectively provided in the UE 100. Additionally, the user interface 140, display unit 150, etc., may be additionally provided in the base station 200 if necessary.

[0145] In NR wireless communication systems, user equipment (UE) can transmit a codebook including hybrid Automatic Repeat Request (HARQ)-ACK information to signal whether downlink signal or channel reception was successful. The HARQ-ACK codebook includes one or more bits indicating whether downlink signal or channel reception was 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 can 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 can configure one of the two HARQ-ACK codebooks for the UE. The UE can use the HARQ-ACK codebook configured for the UE.

[0146] When using a semi-static HARQ-ACK codebook, the base station can use RRC signals 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 to the user equipment the information required to send the HARQ-ACK codebook every time it needs to be sent.

[0147] When using a dynamic HARQ-ACK codebook, the base station can signal the information needed to generate the HARQ-ACK codebook via the PDCCH (or DCI). Specifically, the base station can signal the information needed to generate the HARQ-ACK codebook via the Downlink Assignment Index (DAI) field of the PDCCH (or DCI). In a particular embodiment, the DAI represents information about the number of bits in the HARQ-ACK codebook and information about which channel or signal each bit in the HARQ-ACK codebook indicates successful or failed reception. The user equipment can receive the DAI field via the PDCCH (or DCI) used to schedule the PDSCH. The value of the DAI field can be divided into counter-DAI and total-DAI. Total-DAI indicates the number of downlink signals or channels that have indicated successful or failed reception via the HARQ-ACK codebook up to the current monitoring time (MO). The counter-DAI indicates the HARQ-ACK codebook bits, which indicate the success or failure of downlink signal or channel reception in the current cell up to the current monitoring time, as indicated by the HARQ-ACK codebook. The PDCCH (or DCI) used for scheduling PDSCH may include the value of the counter-DAI corresponding to the scheduled PDSCH. Furthermore, the PDCCH (or DCI) used for scheduling PDSCH may include the total-DAI value corresponding to the scheduled PDSCH. The user equipment can determine the number of bits in the dynamic HARQ-ACK codebook based on information signaled by the PDCCH (or DCI). Specifically, the user equipment can determine the number of bits in the dynamic HARQ-ACK codebook based on the DAI of the PDCCH (or DCI).

[0148] Configuration license

[0149] Figure 12 This is a diagram illustrating an example of uplink licensing that can be applied to embodiments of the present invention.

[0150] Figure 12 (a) An example of dynamic licensing is illustrated. Figure 12 (b) An example of a license configuration shown in the diagram.

[0151] In this invention, for convenience, uplink transmission using dynamic licensing will be referred to as licensed uplink transmission, and uplink transmission using UL-configured licensing without dynamic licensing (license-free) will be referred to as license-free uplink transmission. However, these are exemplary and the invention is not limited thereto.

[0152] Dynamic licensing refers to a method for transmitting / receiving data based on base station scheduling to maximize resource utilization. This means that when a User Equipment (UE) has data to transmit, it can first request uplink resources from the base station and transmit data using only the uplink resources allocated by the base station. To efficiently utilize uplink radio resources, the base station must know what kind of data each UE wants to transmit in the uplink and how much data it wants to transmit. Accordingly, UEs can directly send information about the uplink data to be transmitted to the base station, and the base station can allocate uplink resources to UEs based on this information. In this case, the information about the uplink data sent from the UE to the base station indicates the amount of uplink data buffered in its own buffer, which is called a Buffer Status Report (BSR). A BSR is sent using a MAC control element when resources are allocated to a UE on the PUSCH in the current TTI and a report event is triggered.

[0153] Figure 12 (a) This diagram illustrates the process by which a user equipment (UE) allocates uplink resources for actual data when uplink radio resources for buffer status reporting are not allocated to the UE. In other words, when a UE switches from discontinuous reception (DRX) mode to active mode, because there are no pre-allocated data resources, it must begin requesting resources for uplink data with an SR transmission via PUCCH. In this case, a five-step uplink resource allocation process is used.

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

[0155] Depending on whether PUCCH resources for SR are configured, the user equipment sends SR or initiates a random access procedure via PUCCH. Specifically, upper layers (e.g., the RRC layer) can specifically configure PUCCH resources for the user equipment that enable SR transmission.

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

[0157] When a user equipment receives a UL license from a base station for PUSCH resources used for BSR transmission, the user equipment sends a triggered BSR to the base station using the PUSCH resources allocated by the UL license.

[0158] The base station checks the actual amount of data the user equipment (UE) intends to transmit via the uplink using the BSR (Base Station Response) and sends a UL (Universal License) grant for PUSCH resources used for the actual data transmission to the UE. The UE, having received the UL grant, then transmits the actual uplink data to the base station using the allocated PUSCH resources.

[0159] Reference Figure 12 (b) Describe the method of sending PUSCH using the configured permissions.

[0160] User equipment receives resource configuration from the base station for transmitting UL data without dynamic permission. Resource configuration can be performed solely through RRC signaling (Type 1), or through a combination of Layer 1 (L1) signaling and RRC signaling (Type 2).

[0161] In the case of type 1, RRC can receive and configure the following parameters.

[0162] – Period and offset for SFN=0

[0163] -Power control parameters

[0164] Time / Frequency Resource Allocation

[0165] -DMRS parameters / MCS / TBS

[0166] - Number of repeated transmissions K

[0167] In the case of type 2, RRC can receive and configure the following parameters.

[0168] -cycle

[0169] -Power control parameters

[0170] - Number of repeated transmissions K

[0171] Additionally, in the case of Type 2, the following items can be indicated by L1 signaling.

[0172] – Offset used for initial transmission timing

[0173] Time / Frequency Resource Allocation

[0174] -DMRS parameters / MCS / TBS

[0175] Additionally, without dynamic clearance, the user equipment performs the initial transmission to the base station via L1 signaling based on the resource configuration received via RRC signaling. 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).

[0176] Resources used for initial transfers permitted by the configured permissions may or may not be shared among one or more user devices.

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

[0178] The base station can allocate different DMRS resources and parameters to different user equipments sharing the same resources. Furthermore, when a user equipment performs a retransmission, it is switched to a dynamic licensing basis, receives a dynamic license from the base station, and performs the retransmission based on the dynamic license. That is, the user equipment performs the initial transmission without a dynamic license, but performs retransmissions based on the dynamic license.

[0179] Figure 13 This is a diagram illustrating an example of a license-free initial transfer.

[0180] refer to Figure 13 The configuredGrantConfig of the BWP-UplinkDedicated Information Element (IE) sent via RRC signaling and the PUSCH transport corresponding to the configured grant configure the uplink resources for the PUSCH transport as semi-static, and subsequent parameters can be used to allocate the configured uplink resources according to the transport type.

[0181] When the upper layer does not deliver transport blocks for transmission on resources allocated for uplink transmission without dynamic permission, the user equipment may not perform any transmission on the resources configured by configuredGrantConfig.

[0182] In the case of type 1PUSCH transmission used for configuration licensing

[0183] In the case of type 1PUSCH transmission for configuration purposes, the base station can configure the following information in the user equipment via RRC signals.

[0184] - The upper-level parameter `timeDomainAllocatio` value `m`: indicates the row index `m+1` of the matrix that indicates the assigned table, and the assigned table indicates a combination of start symbol, length, and PUSCH mapping type. Here, table selection follows rules specific to the user device search space.

[0185] - Frequency domain resource allocation is determined by the process indicated by the upper-level parameter frequencyDomainAllocation based on the given resource allocation type indicated by frequencyAllocation.

[0186] -MCS is provided by the upper-level parameter mcsAndTBS.

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

[0188] - When frequency hopping is enabled, the frequency offset between two frequency hops is configured by the upper-level parameter frequencyHoppingOffset.

[0189] In the case of type 2PUSCH transmission used for configuration licenses

[0190] In the case of type 2PUSCH transmission for a configured license, resource allocation is based on the UL license received on the DCI.

[0191] Repeating of transport blocks for configured permitted uplink transmissions

[0192] The upper-layer configuration parameters repK and repK-RV define the pattern of the K repetitions and the redundant version (RV) to be applied to the transmitted block.

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

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

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

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

[0197] In the case of RV sequences, repeated transmissions can be stopped after K repeated transmissions, or they can be stopped at the earliest of the following times: the last transmission time point in the K repeated transmissions during period P and the start point of the repeat that overlaps with the PUSCH of the same HARQ process scheduled in DCI format 0_0 or 0_1.

[0198] User equipment (UE) does not expect the time interval for K repeated transmissions to be greater than the time interval derived from period P. If UE determines that the number of symbols available for PUSCH transmission in a time slot used for transmission timing is less than the number of symbols in the transmission interval, UE will not transmit PUSCH at that transmission timing.

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

[0200] Depending on the conditions of the time slot configuration, permitted Type 1 or Type 2 PUSCH transmissions configured in the time slot may be omitted.

[0201] refer to Figure 14 The user equipment (UE) receives RRC configuration information (S14010) from the base station, which includes information for receiving downlink control information (DCI).

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

[0203] Additionally, as in Figure 12 and Figure 13 As described herein, RRC configuration information may include parameters for configuring each type (Type 1, Type 2) of the configured license.

[0204] Then, the user equipment can receive the DCI by detecting the PDCCH at the monitoring time based on the RRC configuration information (S14020). The user equipment can obtain the DCI by detecting the PDCCH in a specific search space at the monitoring time based on the service type and / or data based on the RRC configuration information.

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

[0206] Table 3 below shows examples of DAI bits according to the DCI format.

[0207] [Table 3]

[0208]

[0209]

[0210] In addition, resources can be allocated to user equipment for receiving PDSCH or transmitting PUSCH via PDCCH (or DCI).

[0211] If resources that are repeatedly configured are used to send different transport blocks (TBs) via PUSCH at regular intervals based on the configuration permission, the information for resource configuration may be included in the DCI depending on the type, and may further include an identifier for activating the configuration associated with the configured resource.

[0212] In other words, an indicator that specifies the configuration to be activated for PUSCH transmission can be included in the DCI and sent to the user equipment.

[0213] The user equipment can then activate at least one configuration for transmitting the PUSCH by using an indicator included in the received DCI, and can transmit the PUSCH to the base station based on the activated configuration using resources allocated in a regular interval (S14030).

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

[0215] In order to transmit PUSCH, symbols allocated from the base station via DCI can be assigned to user equipment based on the position of the starting symbol, the length of the allocated resources, and the number of repetitions.

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

[0217] refer to Figure 15 User equipment can release the configuration activated for PUSCH transmission based on the identifier included in the DCI.

[0218] Specifically, the user equipment may include RRC configuration information, which is used to... Figure 14 The method described herein releases the active configuration from the base station when performing a licensed PUSCH transmission (S15010). The RRC configuration information may include an identifier for each resource to be released, for releasing the active configuration used for PUSCH transmission.

[0219] In such a case, the identifier can be the identifier for each of the released configurations in the license-activated configurations for both types of configurations, or the identifier for each of the released configurations in the semi-persistent scheduling (SPS) activated configurations.

[0220] The user equipment can then receive a PDCCH (S15010) from the base station that includes a DCI indicating the release of an activated configuration. In this case, the DCI may include a specific indicator indicating a set of configurations to be released. For example, when a 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 configurations or configuration groups 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.

[0221] If no RRC configuration information for releasing the configured settings is received, the user equipment can identify specific indicators in the DCI that indicate the release of the configured settings. Figure 14 The configuration in the RRC configuration information described in [the document]. That is, if no RRC configuration information for release is received, the user equipment can identify a resource corresponding to a specific indicator whose value is the same as the value of the indicator described below, which indicates that [the resource is being released]. Figure 14 The configuration of the PUSCH transmission configuration in step S14010 includes the configuration in the RRC configuration information.

[0222] In other words, if no RRC configuration information for release is provided, the user equipment can identify the specific indicator used for release configuration that indicates the configuration for transmitting PUSCH.

[0223] A specific indicator can be used to release multiple configurations activated for PUSCH transmission, and a user equipment can release multiple configurations indicated by a specific indicator.

[0224] In this scenario, a specific indicator can be sent via 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 through fields other than the HARQ process number field.

[0225] User equipment can identify the configuration to be released by specific indicators included in the received DCI, and can release one or more identified configurations.

[0226] As described in the previously configured license, the user equipment can be configured to receive PDSCH configured by RRC signals (or configured by RRC signals and activated by L1 signals). This can be referred to as semi-persistent scheduling (SPS) or configuration scheduling (CS). On the other hand, when receiving / transmitting PDSCH / PUSCH based on SPS / CS, the corresponding DCI for PDSCH / PUSCH does not exist.

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

[0228] That is, even though a PDSCH / PUSCH is configured with an RRC signal (or configured with an RRC signal and activated by an L1 signal), the user equipment can switch to the default DL BWP.

[0229] <Proposal 1: Group RBs and indicate the resources allocated to user equipment via RIVs that indicate the starting RBG index and length>

[0230] Method 1: Use the common RB index to group RBs, and the set of grouped RBGs can be indicated to the user equipment by the starting index and length of the RBG.

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

[0232] refer to Figure 16 Multiple RBs can be grouped to form RB groups (RBGs) to indicate frequency domain resource assignments with a small number of bits to user equipment using URLLC. RBGs can be indicated using the RIV scheme.

[0233] The user equipment can be configured with a specific value (e.g., a P value) related to the number of packets (RBs) from the base station. The user equipment can use the P value to obtain N. RBG There are RBGs. When grouping RBGs, RBs can always be grouped by P from the PRB (lowest PRB) with the lowest index value of the active BWP. However, this method may not be aligned with RBGs of user equipment with different BWPs.

[0234] Therefore, to address this situation, a public PRB index can be used to bundle RBG, such as... Figure 16 As shown in the diagram. 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, it is the same PRB index used by the user equipment in this cell.

[0235] Specifically, an RBG can consist of RBs with a common PRB index {P*n, P*n+1, ..., P*n+P-1}. Here, n is a non-negative integer.

[0236] In this case, the RB included in the RBG must be included in the active BWP.

[0237] User equipment can obtain the index S of the starting RBG as a group and the number L of RBGs by using the RIV value. Specifically, the RIV can be obtained by the following Equation 1.

[0238] [Equation 1]

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

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

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

[0242] User equipment can create an RBG by grouping RBs using P and Q values. First, Q is likely always restricted to one of the divisors of P, and P can 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 can be set to one of 1, 2, or 4. In this case, when assuming K (K is a natural number) is...

[0243] During P / Q, the user equipment can create K instances of RBG by using the following common PRB index to bundle RBG.

[0244] RBG set.

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

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

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

[0248] -...The k-th RBG set: An RBG consists of RBs with a common PRB index of (P*n+(k-1)*Q, P*n+(k-1)*Q+1, ..., P*n+(k-1)*Q+P-1}.

[0249] -...The Kth RBG set: An RBG consists of RBs with a common PRB index of (P*n+(K-1)*Q, P*n+(K-1)*Q+1, ..., P*n+(K-1)*Q+P-1}.

[0250] As an alternative approach, RBGs can be grouped using a UE-specific PRB index to generate a set of K RBGs.

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

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

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

[0254] -...The k-th RBG set: An 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}.

[0255] - ...The Kth RBG set: An 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, only RBs included in the active BWP within {P*n+(K-1)*Q, P*n+(K-1)*Q+1,...,P*n+(K-1)*Q+P-1} can be composed of RBGs. An RBG set consists of P RBs, and the indices of the first RBs in two RBG sets differ by a multiple of the value Q. An RBG can consist only of RBs included in the active BWP. That is, if some packets' RBs are not included in the active BWP, the RBG can utilize the remaining RB packets other than the excluded RBs.

[0256] The RBG in the RBG assigned to the user equipment can be indicated to the user equipment through the resource allocation information in the frequency domain of the user equipment in the following two steps.

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

[0258] 2) The user equipment can obtain the index value S of the starting RBG and the length L of the RBG assigned to the user equipment from the RBG set by using the RIV value. That is, the user equipment can obtain the index S of the RBG that indicates the number (or length) of the assigned RBG by using the RIV value included in the DCI and L that indicates the number (or length) of the assigned RBG.

[0259] In this case, the RIV value can be determined using Equation 2 below. Here, N RBG,x It is the number of RBGs included in the RBG set indicated in the first step.

[0260] [Equation 2]

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

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

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

[0264] As another method, the RIV value can be determined using Equation 3 below. In this case, N RBG,max This refers to the maximum number of RBGs included in the entire RBG set.

[0265] [Equation 3]

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

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

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

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

[0270] User equipment (UE) must determine the bit size of the Frequency Domain Resource Assignment (FDRA) field that indicates the RIV value. For example, because the length (bit size) of the FDRA field may consist of RBs including at most RBGs, the UE must know the bit size of the FDRA field. For instance, the bit size of the FDRA field could be ceil(log2(N) RBG,max *(N RBG,max +1) / 2)), and N RBG,max This refers to the maximum number of RBGs included in all RBG sets.

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

[0272] The starting index refers to the index of the starting RBG assigned to the user device, and the length can refer to the number of consecutively assigned RBGs.

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

[0274] Method 2: RIV can be used based on offset to indicate the RBG assigned to the user equipment.

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

[0276] P: Length granularity.

[0277] Q: Starting granularity.

[0278] K: P / Q.

[0279] RB_start: The index of the RB that starts the allocated resources in the frequency domain.

[0280] L_RB: The number of RBs allocated to the resource.

[0281] RB_end: The index of the RB at which the allocated resource ends.

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

[0283] First, the user equipment can receive the offset value of the starting RB with X = ceil(log2(K)) bits. That is, the user equipment can receive the offset value of the starting RB from which the allocated resource begins through X bits of DCI.

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

[0285] User equipment can obtain S and L by using the RIV value included in the DCI. In this case, the RIV value can be defined by Equation 4 below.

[0286] [Equation 4]

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

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

[0289] Where S + L <= N.

[0290] In Equation 4, N represents the quotient obtained by dividing the number of PRBs N_BWP 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 at most N RBs of length P. S is one of 0, 1, ..., N-1, and L is one of 1, 2, ..., N.

[0291] User equipment can calculate RB_Start and L_RB using offset, S, and L via Equation 5 below.

[0292] [Equation 5]

[0293] RB_start = S * P + offset

[0294] L_RB=L*P

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

[0296] [Table 4]

[0297] 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 1 1 4 4 7 0 1 2 4 8 11 0 2 1 8 4 11 2 0 1 2 4 5 2 0 2 2 8 9 2 0 3 2 12 13 2 1 1 6 4 9 2 1 2 6 8 13 2 2 1 10 4 13

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

[0299] Therefore, the following method can be used to resolve this situation.

[0300] First, the user equipment can receive an offset value of the starting RB having X = ceil(log2(K)) bits. One of the values ​​0, Q, 2*Q, ..., (K-1)*Q can be indicated as the offset value. The X bits can be obtained via 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 can be indicated via a separate field included in the DCI.

[0301] User equipment can obtain S and L by using the RIV value included in the DCI. In this case, the RIV value can be defined in the same way as in Equation 4 above.

[0302] Here, N can be expressed as N = ceil(N_BWP / P). This means that the active BWP can include at most 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.

[0303] User equipment can calculate RB_Start and L_RB using offset, S, and L via Equation 6 below.

[0304] [Equation 6]

[0305] RB_start = S * P + offset

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

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

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

[0309] [Table 5]

[0310]

[0311]

[0312] In this case, it is possible to schedule all RBs in the frequency band.

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

[0314] When the PRB grid groups A RBs, the common PRB index of the lowest PRB of the active BWP can be called BWP_low, and the common PRB index of the highest PRB of the active BWP can be called BWP_high.

[0315] First, when BWP_high is an integer multiple of A, if BWP_low is also an integer multiple of A, then the RBs bound by A in order starting from the lowest PRB in the active BWPs can coincide with the PRB grid. However, if BWP_low is not an integer multiple of A, then the RBs bound by A in order of the lowest PRB in the active BWPs will not coincide with the PRB grid.

[0316] Therefore, if (BWP_low mod A) RBs are separated from the lowest PRB and then the RBs are bound by A starting from the next one, they may coincide with the PRB grid.

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

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

[0319] In the first group, A - (BWP_low mod A) RBs can be grouped, and in the last group, if (BWP_low + N_BWP) mod A > 0, then (BWP_low + N_BWP) mod A RBs can be grouped; otherwise, A RBs can be grouped.

[0320] The method for allocating frequency domain resources based on the PRB grid is as follows.

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

[0322] X bits can be obtained via the MSB of the FDRA field in the DCI or the MSB of the RIV field in the FDRA field of the DCI. Alternatively, X bits can be indicated via a separate field included in the DCI.

[0323] User equipment can obtain S and L by using the RIV value included in the DCI. In this case, the RIV value can be obtained through Equation 7 below.

[0324] [Equation 7]

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

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

[0327] S+L<=N

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

[0329] However, if BWP_low+ offset is a multiple of P, but BWP_low+N_BWP+ 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.

[0330] Based on the PRB grid, an active BWP can contain at most floor (N_BWP / P) RBs of length P. Additionally, the set of PBs of length less than P will be determined by the BWP.

[0331] Composed of the lowest PRB and the highest PRB. S is one of 0, 1, ..., N - 1, and L is one of 1, 2, ..., N.

[0332] The user equipment can calculate

[0333] RB_Start and L_RB by using the offset, S, and L through Equation 8 below.

[0334] [Equation 8]

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

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

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

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

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

[0340] As Figure 17 shown, the virtual BWP can be composed of N * P RBs.

[0341] The virtual BWP can be aligned with the PRB grid and includes the RBs that are {-delta + 1, …

[0342] 0, …, N * P + delta}. In this case, delta = BWP_low mod P.

[0343] Here, the lowest RB with a negative index and the RB with an index greater than N * P are actually included in the active BWP. The RB indices of the virtual BWP are represented by 0’, 1’, ..., (N * P - 1)’.

[0344] RB_start_temp is the index of the starting RB among the RB indices of the virtual BWP.

[0345] This can be obtained by RB_start_temp = (S * P + offset)’ and L_RB_temp = L * P. If the RBs that are not included in the actual RBs among the virtual RBs are excluded (i.e., the lowest RB with a negative index and the RB with an index equal to or greater than N * P are excluded), then the resource allocation in the actual active BWP can be obtained.

[0346] For example, when N_BWP is 15, P is 4, Q is 2, and the minimum active BWP is...

[0347] When the PRB index BWP_low is 2, the offset can be indicated by 0 or 2 using a 1-bit offset in the DCI. N can be obtained from the offset.

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

[0349] [Table 6]

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

[0351] As described above, the base station can group RBs into units of RBGs and allocate resources to user equipment, and can send a 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.

[0352] User equipment can perform repeated transmission of PUSCH by identifying the allocated resources based on the DCI for resource allocation received from the base station.

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

[0354] Then, the user equipment can repeatedly send the PUSCH to the base station using the identified resources.

[0355] <Proposal 2: Free up the resources allocated for repeated transmissions of PUSCH by using a single DCI>

[0356] In another embodiment of the invention, the base station can release resources allocated and activated for repeated transmission of PUSCH via DCI. In this case, the base station can release multiple resources activated by one DCI at a time.

[0357] That is, resources allocated for UL-unlicensed transmissions or transmissions using configured licenses can be released through a DCI.

[0358] Typically, uplink transmission is license-based (GB) transmission, where the user equipment (UE) is configured to perform transmissions on appropriate resources based on scheduling information of the license received via the DCI from the PDCCH sent from the base station. In GB transmission, the base station configures the UL license for uplink transmission as the DCI and sends the UL license to the UE via the downlink control channel. This license is dynamic.

[0359] User Equipment (UE) can send Data Transfers (TBs) mapped to HARQ process IDs according to the UL license's time-frequency resources to the base station. UE can manage HARQ retransmissions based on UL licenses with the same HARQ process ID. For example, UE can check whether a previous TB was successfully sent to the base station by comparing the New Data Indicator (NDI) with the NDI of a previously received UL license; the NDI indicates whether new data was indicated by the UL license from the base station. That is, when the received UL license NDI is a toggled value of the previously received NDI, UE can determine that the previously sent TB was successfully transmitted. However, if the received UL license NDI is the same as the previously received NDI, it is determined that the TB was not transmitted correctly and the transmission failed, and a retransmission procedure for the corresponding TB can be executed.

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

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

[0362] To increase the reliability of uplink GF transmission, the base station can be configured to repeatedly send uplink data to the user equipment. For example, if the base station is configured to repeatedly send data to the user equipment K times, the user equipment can repeatedly send data to the base station K times. In this case, the user equipment can either repeatedly send data K times or terminate the repeated transmission upon receiving an ACK response for uplink GF transmission from the base station.

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

[0364] In this scenario, the user equipment can send a permission to retransmit uplink data. If the user equipment receives the permission to retransmit uplink data, it can stop the GF transmission of TB and perform GB retransmission.

[0365] In version 16NR, a single BWP for a cell can include licenses for up to 12 UL configurations. In this case, the configuration that releases the license for each UL configuration using each DCI may have limitations due to increased DCI overhead.

[0366] To overcome this limitation, a single DCI can be used to release the licensed configurations of two or more UL configurations.

[0367] Method 1: The license ID of the configuration released via DCI can be indicated by grouping the license IDs of the configuration.

[0368] In an embodiment of the present invention, when a base station configures a license for a user equipment UL configuration for uplink transmission, a group ID can indicate licenses for multiple UL configurations by grouping the licenses for individual UL configurations.

[0369] Specifically, when configuring UL configuration licenses for user equipment, the base station can configure the ID to indicate the IDs of two or more UL configuration licenses with a specific value (e.g., 12, 13, 14, 15, or X, X+1, ..., X+15 if X configuration licenses are configured). For example, the ID can be configured to be 12, such that the IDs of the UL configuration licenses include 0, 1, 2, and 3. That is, a specific value can be configured such that the ID indicates that a configured license has already been configured, rather than a new UL configuration license.

[0370] When a user equipment receives a DCI (Distributed Control Information) for releasing licenses for UL configurations, the user equipment can use four bits of the DCI to receive the license ID for the UL configuration. If the indicated ID is a specific value, licenses for multiple UL configurations indicated by that specific value can be released at once.

[0371] In other words, if a user equipment has multiple configurations with permission for multiple configurations used for repeated transmissions of PUSCH from a base station, these multiple configurations can be released via a DCI sent from the base station. In this case, the DCI may include a specific indicator indicating the permission (or resource) for the multiple configurations. The specific indicator (or ID field) may indicate the ID of the permission (or resource) for one or more configurations configured for repeated transmissions of PUSCH.

[0372] At this point, the ID of the license to be released for each configuration can be provided to the user equipment via RRC configuration, and if no RRC configuration exists, the user equipment can determine that the specific indicator of the DCI corresponds to the ID of the license of the configuration activated for repeated transmission of PUSCH.

[0373] The above method can be used to activate licenses (or resources) for one or more configurations used for repeated transmissions of PUSCH.

[0374] In other words, the user equipment can receive a DCI (Distributed Control Information Center) for activating a UL (Ultimate Utility) configuration, and can use four bits of the DCI to receive the ID of the license for one or more configurations to be activated. The user equipment can perform repeated transmissions of PUSCH by activating the license for one or more configurations corresponding to the ID received via the DCI.

[0375] In this scenario, a 4-bit field is needed to indicate the ID of each of the licenses for multiple configurations released via a single DCI. Therefore, the following field can be used to indicate the release of licenses for multiple configurations.

[0376] - HARQ process ID field: The HARQ process ID field is always 4 bits and is included in DCI format 0_0 and 0_1.

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

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

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

[0380] That is, each configuration value of the license for each configuration provided by higher-level signaling corresponds to a 4-bit HARQ process number field included in the DCI, and the user equipment can activate the license for one or more configurations corresponding to the HARQ process number field.

[0381] In this scenario, fields other than the HARQ process number field can be used to determine DCI authentication. User equipment can then use the activated resources to perform repeated PUSCH transfers.

[0382] When a user equipment is configured with one or more licenses from a base station, the following methods can be used to release the licenses for one or more configurations.

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

[0384] - If the user equipment is not provided with a configuration (or list) (e.g., RRC configuration information) that grants permission to one or more configurations via higher-level signaling, the value of the HARQ process number field in the DCI format can indicate a UL configuration that grants permission to one or more UL configurations with the same index value as the configuration that grants permission to one or more UL configurations. That is, the user equipment can grant a configuration that grants permission to one or more configurations corresponding to the value of the HARQ process number field included in a DCI. In this case, the configuration that grants permission to one or more configurations can be a configuration that grants permission to the user equipment via higher-level signaling to activate the configuration.

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

[0386] Method 2: The field used to determine the verification of DCI to activate / release the license of the configuration (e.g., the license of type 2 configuration) or SPS PDSCH can vary depending on the number of licenses or PDSCHs in the type 2 configuration.

[0387] Specifically, the bit field used to determine the verification of the DCI for activating / releasing a type 2 configuration license or SPS PDSCH is type 2 of the two types of configured licenses (type 1, type 2), which can vary depending on the circumstances.

[0388] The base station can send a license or DCI for activating / releasing type 2 configuration or SPS PDSCH to the user equipment. In this case, the DCI can be scrambled with CS-RNTI, and the NDI field value can be set to 0 and sent.

[0389] In this case, the values ​​of the fields used to determine whether the activation / deactivation of the DCI configuration for repeated transmission of PUSCH is effective are shown in Tables 7 and 8 below.

[0390] Table 7 shows examples of field values ​​used to determine the verification of the DCI for activating / releasing a single SPS configuration or a single configuration license when a single SPS configuration or a single configuration license is configured for downlink transmission.

[0391] [Table 7]

[0392]

[0393]

[0394] Table 8 shows examples of field values ​​used to determine the verification of DCI for activating / releasing multiple SPS configurations or multiple configuration licenses when multiple SPS configurations or multiple configuration licenses are configured for downlink transmission.

[0395] [Table 8]

[0396]

[0397] Referring to Tables 7 and 8, depending on whether the SPS configuration or the configuration of the permission is single or multiple, the HARQ process number field may or may not be used for verification determination.

[0398] For example, when one or more configurations are licensed as described in Method 1 of Proposal 2, the HARQ process ID field can be used to activate / deactivate the licenses for multiple configurations. In this case, since the HARQ process ID field has already been used to activate / deactivate the licenses for multiple configurations, it is not used to determine whether the DCI is valid.

[0399] However, if a configured license is set up, the HARQ process ID field may not be used to activate / deactivate the configured license. In this case, the HARQ process ID field can be used to determine whether DCI is valid.

[0400] In Tables 7 and 8, the verification of DCI based on the value of the FDRA field can vary depending on the type of FDRA. For example, FDRA type 0 indicates the type used to generate groups (RBGs) by bundling RBs and indicates whether each of the generated RBGs is assigned a bitmap. In this case, it might mean that if all values ​​of the FDRA field are set to 0, no RBGs will be assigned to any of the groups. Therefore, generally, in FDRA type 0, because the method of assigning RBGs by setting all bits of the FDRA field to 0 is unlikely to be used, the user equipment can recognize that the DCI received when all bits of the FDRA field are set to 0 is a DCI for release.

[0401] Additionally, FDRA type 1 can indicate the RIV, which is a value obtained by jointly encoding the start and end of the RB using DCI. Generally, a valid RIV value can be preset, and it is not necessary to use the method of setting all bits of the FDRA field to 1.

[0402] Therefore, when the FDRA type is set to FDRA type 1, the user equipment can determine that the received DCI is a DCI for release when all bits of the FDRA field of the received DCI are 1.

[0403] Additionally, when setting dynamic switching between FDRA types, 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.

[0404] When using dynamic switching to determine the FDRA type as described above, it is difficult to configure the FDRA fields as described in Tables 7 and 8. In this case, the method described below can be used to determine whether DCI is valid.

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

[0406] In the second embodiment, if dynamic switching is set between FDRA types, the user equipment can determine the value of 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 a DCI for release.

[0407] For example, if the MSB of the FDRA field is 1, then the FDRA type can 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 can determine that the received DCI is a DCI for release.

[0408] In the third embodiment, when only FDRA type 0 is configured in the user equipment, if all bits of the FDRA field are 0, the user equipment can determine that the received DCI is a DCI for release. In other cases (e.g., FDRA type is not configured, or FDRA type 1 is set or dynamic switching is performed), if all bits of the FDRA field are set to 1, the user equipment can determine that the received DCI is a DCI for release.

[0409] Tables 9 and 10 below show examples of field values ​​used to determine the verification of DCI when setting dynamic switching according to the first to third embodiments.

[0410] Table 9 shows examples of field values ​​used to determine the verification of the DCI for activating / releasing a single SPS configuration or a single configuration license when a single SPS configuration or a single configuration license is configured for downlink transmission.

[0411] [Table 9]

[0412]

[0413]

[0414] Table 10 shows examples of field values ​​used to determine the verification of DCI for activating / releasing multiple SPS configurations or multiple configuration licenses when multiple SPS configurations or multiple configuration licenses are configured for downlink transmission.

[0415] [Table 10]

[0416]

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

[0418] User equipment (UE) can be configured with multiple SPS PDSCH configurations from the base station to support different service types. In this case, UE can receive the DCI used for SPS activation to activate one of the multiple SPS PDSCH configurations. In this scenario, the DCI used to activate the SPS configuration can be scrambled using CS-RNTI.

[0419] If a user equipment receives a DCI for activating an SPS configuration, the user equipment can use specific fields of the received DCI to determine the SPS PDSCH configuration to be activated among multiple SPS PDSCH configurations. That is, when the user equipment is configured with an SPS PDSCH configuration from the base station, it can also configure an ID corresponding to each configuration, and the ID corresponding to the SPS PDSCH configuration to be activated can be received through the DCI from the configured ID.

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

[0421] If a user equipment (UE) receives a DCI for release, the UE can use the specific indicator or field of the received DCI to determine the SPS PDSCH configuration to be released. In other words, if a UE receives a DCI for releasing an SPS configuration, the UE can use the specific fields of the received DCI to determine which SPS PDSCH configuration among multiple SPS PDSCH configurations is to be released. Specifically, when a UE has configured SPS PDSCH configurations from the base station, it can also configure an ID corresponding to each configuration, and within the configured IDs, the ID corresponding to the SPS PDSCH configuration to be activated can be received via the DCI.

[0422] To release multiple SPS PDSCH configurations, a user equipment can be configured with a group of multiple IDs bound from the base station, and because the group ID is included in the DCI used for release, the user equipment can be instructed to release the SPSPDSCH configuration corresponding to the group ID.

[0423] In the following text, when configuring multiple SPS PDSCH configurations for a user equipment, the method for sending multiple SPSPDSCH HARQ-ACKs will be described.

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

[0425] For example, the field used to indicate the group's ID can be obtained as follows.

[0426] First, the user equipment can use the HARQ process ID field to indicate the release of the SPS PDSCH configuration via DCI. In other words, the HARQ process ID field of the SPS release DCI can indicate the group ID to be released.

[0427] In this case, the size of the HARQ process ID field can be smaller than the size of the group ID. That is, the HARQ process ID field can be omitted to indicate all group IDs.

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

[0429] [Equation 9]

[0430] The length of the HARQ process number field = ceil(log2(max{# of the HARQ process, # of the group ID used for the PDSCH of SPS}))

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

[0432] As an alternative approach, when the length of the HARQ process number field is less than ceil(log2(group ID #)), the bit corresponding to the difference between ceil(log2(group ID #)) and the length of the HARQ process number can be obtained in another field of the DCI.

[0433] For example, bits from the FDRA field, bits from the TDRA field, bits from the MCS field, or bits from the RV field can be used.

[0434] SPS PDSCH is a periodic transmission performed in the downlink. Similarly, there are repeated transmissions of configured licensed (CG)PUSCH, which are periodic transmissions performed in the uplink as described above.

[0435] To release multiple configured permission (CG)PUSCHs, up to 4 bits of a DCI field can be used as described in Method 1. That is, up to 4 bits of the DCI can be used to indicate the ID of the group to be released.

[0436] In this case, up to four bits can be used in the same field as the four bits used in the method described in Method 1, or used to release the aforementioned SPS PDSCH. For example, the DCI's HARQ process number field can be used to indicate the configuration's licensed PUSCH to be released.

[0437] In this case, the length of the HARQ process number field can be calculated using the following equation 10.

[0438] [Equation 10]

[0439] HARQ process ID field length = ceil(log2(max{HARQ process ID #, group ID used for CG PUSCH #}))

[0440] In Equation 10, the # in HARQ process number represents the number of HARQ processes configured for the user equipment, and the # in group ID used for CGPDSCH represents the number of group IDs configured for CG PUSCH for the user equipment. Furthermore, 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 through Equation 11 below.

[0441] [Equation 11]

[0442] The length of the HARQ process ID field = ceil(log2(max{HARQ process ID #, group ID # for CG PUSCH, group ID # for SPS PDSCH})).

[0443] In other words, the length of the HARQ process ID field can be determined based on the maximum value among the number of HARQ processes, the group ID of CG PUSCH, and the group ID of SPS PDSCH.

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

[0445] [Equation 12]

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

[0447] In Equation 12, CURRENT_slot can be obtained through Equation 13 below.

[0448] [Equation 13]

[0449] CURRENT_slot = [(SFN × numberOfSlotsPerFrame) + number of time slots in the frame]

[0450] Each parameter in equations 12 and 13 is as follows.

[0451] numberOfSlotsPerFrame: Number of slots per frame

[0452] Periodicity: The period of SPS PDSCH

[0453] nrofHARQ-Processes: The number of HARQ processes on the user device

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

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

[0456] The periodicity and `nrofHARQ-Process` can be set from the upper layer, and `numberOfSlotsPerFrame` can be determined based on the subcarrier spacing. For example, if the subcarrier spacing is 15kHz, it can be 10; if it's 30kHz, it can be 20; if it's 60kHz, it can be 40; and if it's 120kHz, it can be 80. `SFN` represents the system frame number. The HARQ process number described above applies to one SPS PDSCH configuration but not to multiple SPS PDSCH configurations.

[0457] In other words, the possible values ​​for the HARQ process ID are limited to 0, 1, ..., nrofHARQ-Process-1, and different SPS PDSCHs may have the same HARQ process ID. Therefore, when configuring the SPS PDSCH, the offset value of the HARQ-Process can be set additionally.

[0458] In this case, the HARQ process number can be obtained by additionally using the offset value shown in Equation 14 below.

[0459] [Equation 14]

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

[0461] The HARQ process number can have values ​​such as offset, offset + 1, ..., offset + nrofHARQ-Process-1, depending on the offset value set. 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.

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

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

[0464] refer to Figure 18 When multiple configurations (e.g., configuration licenses) for PUSCH transmission are activated for a user equipment, the user equipment can release multiple configurations (or configuration licenses) based on the DCI sent from the base station.

[0465] Specifically, a user equipment can perform PUSCH transmissions through one or more active configurations. In this case, PUSCH transmissions can be periodically sent through multiple resources that are repeatedly configured based on the configuration permissions, and PUSCH can be sent by including different transport blocks in each resource.

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

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

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

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

[0470] In this context, PUSCH represents a channel that is periodically transmitted using resources that are repeatedly configured according to the configured permissions.

[0471] If multiple configurations are activated for repeated transmission of PUSCH, the first specific identifier may be indicated by the Hybrid Automatic Repeat Request (HARQ) process number (HARQ process number) field of the first DCI, and the HARQ process number field may be used to identify one or more of the multiple configurations.

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

[0473] Then, the user equipment can release one or more configurations indicated by the first specific identifier of the received DCI (S18020), and can stop the periodic transmission of PUSCH based on the permission of the configuration.

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

[0475] Even when using this method to configure and activate multiple configuration licenses or SPS PDSCH configurations, multiple active configurations can be released through a single DCI.

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

[0477] refer to Figure 19 When a user equipment activates multiple configurations (e.g., configuration licenses) for PUSCH transmission, the base station can indicate the release of multiple configurations (or configuration licenses) to the user equipment via a DCI.

[0478] Specifically, the base station can allow user equipment to be configured with one or more active configurations for PUSCH transmission. In this case, PUSCH transmission can be periodically sent through multiple resources that are repeatedly configured based on the configuration permissions, and PUSCH can be sent by including different transport blocks in each resource.

[0479] Then, the base station can send configuration information for repeated PUSCH transmission 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 permission-based PUSCH transmissions.

[0480] When the HARQ process ID field is indicated by a specific value, one or more configurations corresponding to multiple identifiers can be released.

[0481] Then, the base station can send a first physical downlink control channel (PDCCH) (S19020) to the user equipment, which includes first downlink control information (DCI).

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

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

[0484] Additionally, when multiple configurations are activated for repeated PUSCH transmissions, the first DCI can be configured for configuration-based permitted PUSCH transmissions to include a first specific identifier (ID) for releasing one or more configurations. In this case, the first specific identifier can indicate one or more configurations configured for PUSCH transmission.

[0485] In this context, PUSCH represents a channel that is periodically transmitted using resources that are repeatedly configured according to the configured permissions.

[0486] If multiple configurations are activated for repeated transmission of PUSCH, the first specific identifier may be indicated by the Hybrid Automatic Repeat Request (HARQ) process number (HARQ process number) field of the first DCI, and the HARQ process number field may be used to identify one or more of the multiple configurations.

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

[0488] This method allows for the release of multiple active configurations at once, even when multiple configurations are activated instead of a single configuration for repeated PUSCH transmission, by using a specific field of the DCI indicating multiple active configurations.

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

[0490] The scope of this invention is indicated by the appended claims rather than the detailed description, and it should be understood that all variations or modifications derived from the meaning and scope of the claims and their equivalents are included within the scope of this invention.

Claims

1. A user equipment (UE) configured to operate in a wireless communication system, the user equipment comprising: Communication module; as well as A processor that controls the communication module, wherein the processor is configured to: The DCI format received from the base station is one of the multiple downlink control information (DCI) formats. Perform a verification process for the release of the DCI format used to schedule at least one semi-persistent scheduling physical downlink shared channel (SPS PDSCH) configuration. Specifically, when the at least one SPS PDSCH configuration is configured, the verification of whether the DCI format is used to schedule the release of the at least one SPS PDSCH is based on i) the value of the bits constituting the Frequency Domain Resource Assignment (FDRA) field included in the DCI format, and ii) the resource allocation type. Specifically, the verification of the DCI format is achieved when i) the resource allocation type is dynamic switching and ii) all bits of the FDRA field are set to "0".

2. The user equipment according to claim 1, wherein, The processor is further configured to: The system receives configuration information from the base station, including resource allocation information related to the resource allocation type.

3. The user equipment according to claim 1, in, When the resource allocation type is configured for dynamic switching, the resource allocation type is either FDRA type 0 or FDRA type 1, depending on the value of the most significant bit (MSB) of the FDRA field.

4. The user equipment according to claim 1, in, The verification of the DCI format is achieved when i) the resource allocation type is FDRA type 0 and ii) all bits of the FDRA field are set to "0".

5. The user equipment according to claim 4, in, The FDRA type 0 indicates whether a bitmap allocation resource block group (RBG) is used.

6. The user equipment according to claim 1, in, The verification of the DCI format is achieved when i) the resource allocation type is FDRA type 1 and ii) all bits of the FDRA field are set to "1".

7. The user equipment according to claim 6, in, The FDRA type 1 indicates the resource indicator value RIV scheme, which indicates the start and length of the allocated resource block RB set.

8. The user equipment according to claim 1, wherein, The processor is further configured to: When the verification of the DCI format is achieved, part or all of the at least one SPS PDSCH configuration is released based on the DCI format.

9. The user equipment according to claim 1, in, The DCI format further includes a modulation and coding scheme (MCS) field and a redundancy version (RV) field, and The verification of the DCI format used to release the at least one SPSPDSCH configuration is further identified by considering the MCS field and the RV field.

10. The user equipment according to claim 1, in, The DCI format further includes a Hybrid Automatic Repeat Request (HARQ) process number field. Specifically, when a single SPS PDSCH configuration is configured, the HARQ process number field is used to identify the verification of the DCI format used to release the single SPS PDSCH configuration, and When multiple SPS PDSCH configurations are configured, the HARQ process number field is not used to identify the verification of some or all of the DCI format for releasing the multiple SPS PDSCH configurations.

11. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: The DCI format received from the base station is one of the multiple downlink control information (DCI) formats. Perform a verification process for the release of the DCI format used to schedule at least one semi-persistent scheduling physical downlink shared channel (SPS PDSCH) configuration. Specifically, when the at least one SPS PDSCH configuration is configured, the verification of whether the DCI format is used to schedule the release of the at least one SPS PDSCH is based on i) the value of the bits constituting the Frequency Domain Resource Assignment (FDRA) field included in the DCI format, and ii) the resource allocation type. Specifically, the verification of the DCI format is achieved when i) the resource allocation type is dynamic switching and ii) all bits of the FDRA field are set to "0".

12. The method according to claim 11, wherein, The method further includes: The system receives configuration information from the base station, including resource allocation information related to the resource allocation type.

13. The method according to claim 11, in, When the resource allocation type is configured for dynamic switching, the resource allocation type is either FDRA type 0 or FDRA type 1, depending on the value of the most significant bit (MSB) of the FDRA field.

14. The method according to claim 11, in, The verification of the DCI format is achieved when i) the resource allocation type is FDRA type 0 and ii) all bits of the FDRA field are set to "0".

15. The method according to claim 14, in, The FDRA type 0 indicates whether a bitmap allocation resource block group (RBG) is used.

16. The method according to claim 11, in, The verification of the DCI format is achieved when i) the resource allocation type is FDRA type 1 and ii) all bits of the FDRA field are set to "1".

17. The method according to claim 16, in, The FDRA type 1 indicates the resource indicator value RIV scheme, which indicates the start and length of the allocated resource block RB set.

18. The method according to claim 11, wherein the method further comprises: When the verification of the DCI format is achieved, part or all of the at least one SPS PDSCH configuration is released based on the DCI format.

19. The method according to claim 11, in, The DCI format further includes a modulation and coding scheme (MCS) field and a redundancy version (RV) field, and The verification of the DCI format used to release the at least one SPSPDSCH configuration is further identified by considering the MCS field and the RV field.

20. The method according to claim 11, in, The DCI format further includes a Hybrid Automatic Repeat Request (HARQ) process number field. Specifically, when a single SPS PDSCH configuration is configured, the HARQ process number field is used to identify the verification of the DCI format used to release the single SPS PDSCH configuration, and When multiple SPS PDSCH configurations are configured, the HARQ process number field is not used to identify the verification of some or all of the DCI format for releasing the multiple SPS PDSCH configurations.

Images