KR20200137980A - Method and apparatus for uplink communication in unlicensed band - Google Patents

Abstract

Disclosed are a method for uplink communication in an unlicensed band, and an apparatus thereof. According to the present invention, an operating method of user equipment (UE) comprises the steps of: receiving information on one configured grant (CG) setting for uplink transmission from a base station; obtaining common time domain resource allocation information for combinations of resource blog (RB) sets based on the information on the one CG setting; obtaining frequency domain resource allocation information for each of the combinations of the RB sets based on the information on the one CG setting; and determining the number of physical resource blocks (PRBs) to which an uplink channel is mapped based on the frequency domain resource allocation information corresponding to one of the combinations. Accordingly, the performance of a communication system can be improved.

Description

Method and apparatus for uplink communication in an unlicensed band {METHOD AND APPARATUS FOR UPLINK COMMUNICATION IN UNLICENSED BAND}

The present invention relates to a technology for transmitting and receiving signals in a communication system, and more particularly, to a technology for transmitting and receiving an uplink signal in an unlicensed band.

In order to process rapidly increasing radio data, a frequency band higher than the frequency band of LTE (long term evolution) (or LTE-A) (eg, a frequency band of 6 GHz or less) (eg, a frequency band of 6 GHz or higher) A communication system using (for example, a new radio (NR) communication system) is being considered. The NR communication system can support not only a frequency band of 6 GHz or less but also a frequency band of 6 GHz or more, and can support various communication services and scenarios compared to the LTE communication system. For example, the usage scenario of the NR communication system may include enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communication (URLLC), and Massive Machine Type Communication (mMTC). Communication technologies are needed to meet the requirements of eMBB, URLLC, and mMTC.

On the other hand, in order to process the rapidly increasing wireless data, communication using an unlicensed band may be used. Currently, communication technologies that use unlicensed bands include LTE-U (LTE-Unlicensed), LAA (Licensed-Assisted-Access), and MultiFire (MulteFire). Can support standalone mode to operate. However, in the unlicensed band, the initial access procedure, the signal transmission procedure, the channel access method suitable for the flexible frame structure, and the broadband carrier operation are not clearly defined. Therefore, it is necessary to clearly define the operation of the base station and the terminal for the above-described technical elements.

An object of the present invention for solving the above problems is to provide a method and apparatus for transmitting and receiving an uplink signal in an unlicensed band.

The operating method of the terminal according to the first embodiment of the present invention to achieve the above object, the step of receiving information about one CG configuration for uplink transmission from a base station, based on the information on the one CG configuration Obtaining common time domain resource allocation information for combinations of RB sets, obtaining frequency domain resource allocation information for each of the combinations of RB sets based on the information on the one CG configuration, the Determining the number of PRBs to which an uplink channel is mapped based on the frequency domain resource allocation information corresponding to one of combinations, TBS based on the common time domain resource allocation information and the number of PRBs Determining, and transmitting the TB having the TBS to the base station through the uplink channel according to the common time domain resource allocation information and the frequency domain resource allocation information within the one combination.

Here, the RB sets may be located within the same bandwidth portion.

Here, the frequency domain resource allocation information may include information indicating one or more interlaces applied to each of the combinations.

Here, each of the RB sets may include consecutive RBs in the frequency domain, and when the RB sets include a first RB set and a second RB set, the combinations are "combination consisting of a first RB set. It may be ", "a combination consisting of a second RB set", and "a combination consisting of a first RB set and a second RB set".

Here, a guard band may be located between the RB sets, and the guard band disposed between RB sets constituting the one combination may be used for transmission of the uplink channel.

Here, the one combination may be determined based on a combination of one or more RB sets in which the LBT operation performed in the terminal is successful.

Here, the RB sets may be one or more RB sets among all RB sets constituting the same bandwidth portion, and the information information on the one CG setting is the one or more RB sets or a combination of the one or more RB sets It may further include information indicating to listen.

Here, the information on the one CG setting may further include information indicating a set of RVs, and the TB may be repeatedly transmitted according to the set of RVs.

Here, the operating method of the terminal may further include receiving HARQ-ACK information from the base station, the HARQ-ACK information may be a reception response to the TB transmitted in a time window, and the time The window may be determined by the time point at which the HARQ-ACK information is received.

In order to achieve the above object, a method of operating a base station according to a second embodiment of the present invention includes the steps of generating frequency domain resource allocation information for each of combinations of RB sets, and one including the frequency domain resource allocation information. Transmitting information on CG configuration to a terminal, and receiving a TB from the terminal in an uplink channel according to the frequency domain resource allocation information, wherein the frequency domain resource allocation information is applied to each of the combinations And information indicating one or more interlaces to be formed, and the size of the TB is determined based on the number of PRBs corresponding to the one or more interlaces.

Here, the RB sets may be located within the same bandwidth portion, each of the RB sets may include consecutive RBs in the frequency domain, and the RB sets include a first RB set and a second RB set , The combinations may be "combination composed of a first RB set", "combination composed of a second RB set", and "a combination composed of a first RB set and a second RB set".

Here, the RB sets may be one or more RB sets among all RB sets constituting the same bandwidth portion, and the information on the one CG configuration indicates the one or more RB sets or combinations of the one or more RB sets. It may further include information to do.

Here, the information on the one CG configuration may further include common time domain resource allocation information indicating a set of RVs, and the TB may be repeatedly transmitted from the terminal according to the set of RVs, and the Common time domain resource allocation information may be configured for combinations of the RB sets.

Here, the method of operating the base station may further include transmitting HARQ-ACK information to the terminal, the HARQ-ACK information may be a reception response to the TB received in a time window, and the time The window may be determined by a time point at which the HARQ-ACK information is received.

The terminal according to the third embodiment of the present invention for achieving the above object includes a processor, a memory in electronic communication with the processor, and instructions stored in the memory, and when the instructions are executed by the processor, The commands include: the UE receives information on one CG configuration for uplink transmission from a base station, and provides frequency domain resource allocation information for each of combinations of RB sets based on the information on the one CG configuration. Acquire, determine the number of PRBs to which an uplink channel is mapped based on the frequency domain resource allocation information corresponding to one of the combinations, determine the TBS based on the number of PRBs, and the one It operates to cause transmission of the TB having the TBS to the base station through the uplink channel according to the frequency domain resource allocation information within a combination of.

Here, the frequency domain resource allocation information may include information indicating one or more interlaces applied to each of the combinations.

Here, the RB sets may be located within the same bandwidth portion, each of the RB sets may include consecutive RBs in the frequency domain, and the RB sets include a first RB set and a second RB set , The combinations may be "combination composed of a first RB set", "combination composed of a second RB set", and "a combination composed of a first RB set and a second RB set".

Here, the RB sets may be one or more RB sets among all RB sets constituting the same bandwidth portion, and the information on the one CG configuration indicates the one or more RB sets or combinations of the one or more RB sets. It may further include information to do.

Here, the information on the one CG setting may further include common time domain resource allocation information indicating a set of RVs, and the TB may be repeatedly transmitted according to the set of RVs, and the common time Domain resource allocation information may be set for combinations of the RB sets.

Here, the commands may be operated to cause further reception of HARQ-ACK information from the base station, and the HARQ-ACK information may be a reception response to the TB transmitted in a time window, and the time window is the It may be determined by the time point at which the HARQ-ACK information is received.

According to the present invention, the terminal may receive configuration information of a configured grant (CG) resource from a base station. The configuration information of the CG resource may include frequency domain resource allocation information and time domain resource allocation information. The frequency domain resource allocation information may include information of an interlace applied to each of RB (resource block) combinations configured in the terminal. The UE may check the number of physical resource blocks (PRBs) to which an uplink channel is mapped based on interlace information, and may determine a transport block size (TBS) based on the number of PRBs.

In addition, the time domain resource allocation information may include a redundancy version (RV) pattern. The terminal may repeatedly transmit a transport block (TB) according to the RV pattern. The UE may receive hybrid automatic repeat request (HARQ)-acknowledgement (ACK) for TB from the base station, and may determine that HARQ-ACK is a reception response to TB(s) transmitted in a time window. According to the above-described operations, the unlicensed band communication can be efficiently performed, and the performance of the communication system can be improved.

1 is a conceptual diagram showing a first embodiment of a communication system.
2 is a block diagram showing a first embodiment of a communication node constituting a communication system.
3A is a conceptual diagram showing a first embodiment of a bandwidth portion in a communication system.
3B is a conceptual diagram showing a second embodiment of a bandwidth portion in a communication system.
3C is a conceptual diagram showing a third embodiment of a bandwidth portion in a communication system.
4A is a conceptual diagram showing a first embodiment of a communication method within a COT.
4B is a conceptual diagram showing a second embodiment of a communication method within a COT.
5A is a conceptual diagram illustrating a first embodiment of a PUSCH transmission method according to a combination of RB set(s).
5B is a conceptual diagram illustrating a second embodiment of a PUSCH transmission method according to a combination of RB set(s).
6 is a conceptual diagram illustrating a first embodiment of an interlace-based PUSCH frequency domain resource allocation scheme.
7 is a conceptual diagram illustrating a first embodiment of a method for allocating PUSCH resources according to method 110.
8 is a conceptual diagram illustrating a first embodiment of a PUSCH resource allocation method according to method 120.
9 is a conceptual diagram illustrating a second embodiment of a method for allocating PUSCH resources according to method 120.
10A is a conceptual diagram illustrating a first embodiment of a method of setting a time domain resource of a configuration grant PUSCH.
10B is a conceptual diagram illustrating a second embodiment of a method of setting a time domain resource of a configuration grant PUSCH.
11 is a conceptual diagram illustrating a third embodiment of a method of setting a time domain resource of a configuration grant PUSCH.
12 is a conceptual diagram showing the first embodiment of the DFI transmission timing.
13 is a conceptual diagram showing a first embodiment showing the ambiguity of DFI analysis.
14A is a conceptual diagram showing a first embodiment of a method of setting a DFI window.
14B is a conceptual diagram showing a second embodiment of a method for setting a DFI window.

In the present invention, various modifications may be made and various embodiments may be provided, and specific embodiments will be illustrated in the drawings and described in detail. However, this is not intended to limit the present invention to a specific embodiment, it is to be understood to include all changes, equivalents, or substitutes included in the spirit and scope of the present invention.

Terms such as first and second may be used to describe various components, but the components should not be limited by the terms. These terms are used only for the purpose of distinguishing one component from another component. For example, without departing from the scope of the present invention, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. The term and/or includes a combination of a plurality of related listed items or any of a plurality of related listed items.

When a component is referred to as being "connected" or "connected" to another component, it is understood that it may be directly connected or connected to the other component, but other components may exist in the middle. Should be. On the other hand, when a component is referred to as being "directly connected" or "directly connected" to another component, it should be understood that there is no other component in the middle.

The terms used in the present application are only used to describe specific embodiments, and are not intended to limit the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In the present application, terms such as "comprise" or "have" are intended to designate the presence of features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, but one or more other features. It is to be understood that the presence or addition of elements or numbers, steps, actions, components, parts, or combinations thereof, does not preclude in advance.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which the present invention belongs. Terms as defined in a commonly used dictionary should be interpreted as having a meaning consistent with the meaning in the context of the related technology, and should not be interpreted as an ideal or excessively formal meaning unless explicitly defined in the present application. Does not.

Hereinafter, preferred embodiments of the present invention will be described in more detail with reference to the accompanying drawings. In describing the present invention, in order to facilitate an overall understanding, the same reference numerals are used for the same elements in the drawings, and duplicate descriptions for the same elements are omitted.

A communication system to which embodiments according to the present invention are applied will be described. The communication system may be a 4G communication system (eg, a long-term evolution (LTE) communication system, an LTE-A communication system), a 5G communication system (eg, a new radio (NR) communication system), or the like. A 4G communication system can support communication in a frequency band of 6 GHz or less, and a 5G communication system can support communication in a frequency band of 6 GHz or more as well as a frequency band of 6 GHz or less. The communication system to which the embodiments according to the present invention are applied is not limited to the contents described below, and the embodiments according to the present invention can be applied to various communication systems. Here, the communication system may be used with the same meaning as a communication network, and “LTE” may indicate “4G communication system”, “LTE communication system” or “LTE-A communication system”, and “NR” May designate “5G communication system” or “NR communication system”.

1 is a conceptual diagram showing a first embodiment of a communication system.

Referring to FIG. 1, a communication system 100 includes a plurality of communication nodes 110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6). In addition, the communication system 100 includes a core network (eg, a serving-gateway (S-GW), a packet data network (PDN)-gateway), and a mobility management entity (MME)). It may contain more. When the communication system 100 is a 5G communication system (eg, a new radio (NR) system), the core network is an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), etc. It may include.

The plurality of communication nodes 110 to 130 may support communication protocols (eg, LTE communication protocol, LTE-A communication protocol, NR communication protocol, etc.) specified in the 3rd generation partnership project (3GPP) standard. The plurality of communication nodes 110 to 130 are code division multiple access (CDMA) technology, wideband CDMA (WCDMA) technology, time division multiple access (TDMA) technology, frequency division multiple access (FDMA) technology, orthogonal frequency division (OFDM) technology. multiplexing) technology, Filtered OFDM technology, CP (cyclic prefix)-OFDM technology, DFT-s-OFDM (discrete Fourier transform-spread-OFDM) technology, OFDMA (orthogonal frequency division multiple access) technology, SC (single carrier)-FDMA Technology, NOMA (Non-orthogonal Multiple Access) technology, GFDM (generalized frequency division multiplexing) technology, FBMC (filter bank multi-carrier) technology, UFMC (universal filtered multi-carrier) technology, SDMA (Space Division Multiple Access) technology, etc. Can support. Each of the plurality of communication nodes may have the following structure.

2 is a block diagram showing a first embodiment of a communication node constituting a communication system.

Referring to FIG. 2, the communication node 200 may include at least one processor 210, a memory 220, and a transmission/reception device 230 connected to a network to perform communication. In addition, the communication node 200 may further include an input interface device 240, an output interface device 250, and a storage device 260. Each of the components included in the communication node 200 may be connected by a bus 270 to perform communication with each other.

The processor 210 may execute a program command stored in at least one of the memory 220 and the storage device 260. The processor 210 may mean a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which methods according to embodiments of the present invention are performed. Each of the memory 220 and the storage device 260 may be configured with at least one of a volatile storage medium and a nonvolatile storage medium. For example, the memory 220 may be formed of at least one of a read only memory (ROM) and a random access memory (RAM).

Referring back to FIG. 1, the communication system 100 includes a plurality of base stations 110-1, 110-2, 110-3, 120-1, 120-2, and a plurality of terminals 130- 1, 130-2, 130-3, 130-4, 130-5, 130-6). Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 may form a macro cell. Each of the fourth base station 120-1 and the fifth base station 120-2 may form a small cell. The fourth base station 120-1, the third terminal 130-3, and the fourth terminal 130-4 may belong to the cell coverage of the first base station 110-1. The second terminal 130-2, the fourth terminal 130-4, and the fifth terminal 130-5 may belong to the cell coverage of the second base station 110-2. The fifth base station 120-2, the fourth terminal 130-4, the fifth terminal 130-5, and the sixth terminal 130-6 may belong within the cell coverage of the third base station 110-3. have. The first terminal 130-1 may belong to the cell coverage of the fourth base station 120-1. The sixth terminal 130-6 may belong to the cell coverage of the fifth base station 120-2.

Here, each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 is a NodeB (NB), evolved NodeB (eNB), gNB, advanced base station (ABS), and HR. -BS (high reliability-base station), BTS (base transceiver station), radio base station, radio transceiver, access point, access node, radio access station (RAS) ), MMR-BS (mobile multihop relay-base station), RS (relay station), ARS (advanced relay station), HR-RS (high reliability-relay station), HNB (home NodeB), HeNB (home eNodeB), It may be referred to as a road side unit (RSU), a radio remote head (RRH), a transmission point (TP), a transmission and reception point (TRP), and the like.

Each of the plurality of terminals 130-1, 130-2, 130-3, 130-4, 130-5, and 130-6 is a user equipment (UE), terminal equipment (TE), advanced mobile station (AMS), HR-MS (high reliability-mobile station), terminal, access terminal, mobile terminal, station, subscriber station, mobile station, portable It may be referred to as a portable subscriber station, a node, a device, an on board unit (OBU), and the like.

Meanwhile, each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may operate in different frequency bands or may operate in the same frequency band. Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may be connected to each other through an ideal backhaul link or a non-ideal backhaul link, , Information can be exchanged with each other through an ideal backhaul link or a non-ideal backhaul link. Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may be connected to the core network through an ideal backhaul link or a non-ideal backhaul link. Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 transmits a signal received from the core network to the corresponding terminal 130-1, 130-2, 130-3, 130 -4, 130-5, 130-6), and the signal received from the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) Can be transferred to.

In addition, each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 transmits MIMO (e.g., single user (SU)-MIMO, multi-user (MU)- MIMO, massive MIMO, etc.), coordinated multipoint (CoMP) transmission, carrier aggregation (CA) transmission, transmission in an unlicensed band, direct communication between terminals (device to device communication, D2D) (or , ProSe (proximity services)), Internet of Things (IoT) communication, dual connectivity (DC), etc. may be supported. Here, each of the plurality of terminals 130-1, 130-2, 130-3, 130-4, 130-5, and 130-6 is a base station 110-1, 110-2, 110-3, 120-1 , 120-2) and operations supported by the base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may be performed. For example, the second base station 110-2 may transmit a signal to the fourth terminal 130-4 based on the SU-MIMO scheme, and the fourth terminal 130-4 may transmit a signal to the fourth terminal 130-4 by the SU-MIMO scheme. A signal may be received from the second base station 110-2. Alternatively, the second base station 110-2 may transmit a signal to the fourth terminal 130-4 and the fifth terminal 130-5 based on the MU-MIMO method, and the fourth terminal 130-4 And each of the fifth terminal 130-5 may receive a signal from the second base station 110-2 by the MU-MIMO method.

Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 may transmit a signal to the fourth terminal 130-4 based on the CoMP scheme, and The terminal 130-4 may receive signals from the first base station 110-1, the second base station 110-2, and the third base station 110-3 by the CoMP method. Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 has terminals 130-1, 130-2, 130-3, and 130-4 belonging to their cell coverage. , 130-5, 130-6) and the CA method can transmit and receive signals. Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 can control D2D between the fourth terminal 130-4 and the fifth terminal 130-5. And, each of the fourth terminal 130-4 and the fifth terminal 130-5 may perform D2D under the control of the second base station 110-2 and the third base station 110-3, respectively. .

On the other hand, a communication system (e.g., NR communication system) supports one or more services from an enhanced mobile broadband (eMBB) service, an ultra-reliable and low-latency communication (URLLC) service, and a massive machine type communication (mMTC) service. I can. Communication can be performed to satisfy the technical requirements of the services in the communication system. In the URLLC service, a requirement of transmission reliability may be 1-10 ^-5 , and a requirement of uplink and downlink user plane delay time may be 0.5 ms.

In the following embodiments, a channel access method and a signal transmission/reception method in a communication system supporting an unlicensed band will be described. The following embodiments may be applied not only to an NR communication system, but also to other communication systems (eg, LTE communication systems). The unlicensed band may mean a shared band.

The NR communication system may support a system bandwidth (eg, a carrier bandwidth) wider than the system bandwidth provided by the LTE communication system in order to efficiently use a wide frequency band. For example, the maximum system bandwidth supported by the LTE communication system may be 20 MHz. On the other hand, the NR communication system can support a carrier bandwidth of up to 100 MHz in a frequency band of 6 GHz or less, and a carrier bandwidth of 400 MHz in a frequency band of 6 GHz or more.

In a communication system (eg, an NR communication system), the numerology applied to physical signals and channels may vary. Numerology can be varied to meet the various technical requirements of the communication system. In a communication system to which a cyclic prefix (CP) based OFDM waveform technology is applied, a newer roller may include a subcarrier spacing and a CP length (or CP type). Table 1 may be a first embodiment of a neurology configuration for CP-based OFDM. The subcarrier spacings may have a relationship of an exponential multiple of 2 to each other, and the CP length may be scaled at the same ratio as the OFDM symbol length. Some of the neurons in Table 1 may be supported according to the frequency band in which the communication system operates. When the subcarrier spacing is 60 kHz, an extended CP may be additionally supported.

In the following, the frame structure in the communication system will be described. Building blocks in the time domain may be subframes, slots, and/or mini slots. The subframe may be used as a transmission unit, and the length of the subframe may have a fixed value (eg, 1 ms) regardless of the subcarrier interval. When a general CP is used, a slot may include consecutive symbols (eg, 14 OFDM symbols). The length of the slot may be variable different from the length of the subframe, and may be inversely proportional to the subcarrier spacing. The slot may be used as a scheduling unit, and may be used as a setting unit for scheduling and hybrid automatic repeat request (HARQ) timing. Each of the scheduling interval and transmission duration may not coincide with the length of the slot.

The base station can schedule a data channel (e.g., a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), a physical sidelink shared channel (PSSCH)) using some or all of the symbols constituting the slot. . Alternatively, the base station may schedule a data channel using a plurality of slots. The mini slot may be used as a transmission unit, and the length of the mini slot may be set shorter than the length of the slot. For example, a mini slot may be a scheduling or transmission unit having a length shorter than that of the slot. In a communication system, a slot having a length shorter than that of an existing slot may be referred to as a mini slot. The mini-slot-based scheduling operation can be used for partial slot transmission, URLLC data transmission, analog beamforming-based multi-user scheduling, etc. in the "unlicensed band" or "the coexistence band of the NR communication system and the LTE communication system". . In the NR communication system, since the PDCCH (pysical downlink control channel) monitoring period and/or the duration of the data channel is set to be shorter than that of the existing slot, mini-slot-based transmission may be supported.

In the frequency domain of the NR communication system, the building block may be a physical resource block (PRB). One PRB may include consecutive subcarriers (eg, 12 subcarriers) regardless of the newer roller. Therefore, the bandwidth occupied by one PRB may be proportional to the subcarrier spacing of the newer roller. The PRB may have a reduced frequency length. In this case, it may be used as a resource allocation unit for a control channel and/or a data channel in the data channel domain. The minimum unit for resource allocation of the downlink control channel may be a control channel element (CCE). One CCE may include one or more PRBs. Resource allocation of the data channel may be performed in units of PRBs or resource block groups (RBGs). One RBG may include one or more consecutive PRBs.

In addition, in a communication system (eg, an LTE communication system), the PRB may be used as a resource allocation unit including both a frequency domain and a time domain. For example, PRB may refer to a physical resource composed of 12 consecutive subcarriers and 7 consecutive symbols. Alternatively, the PRB may mean a physical resource composed of 12 consecutive subcarriers and 6 consecutive symbols.

In the NR communication system, a slot (eg, a slot format) may be composed of a combination of one or more of a downlink period, a flexible period (or an unknown period), and an uplink period. Each of the downlink period, the flexible period, and the uplink period may be composed of one or more consecutive symbols. The flexible section may be located between a downlink section and an uplink section, between a first downlink section and a second downlink section, between a first uplink section and a second uplink section, and the like. When a flexible section is inserted between the downlink section and the uplink section, the flexible section can be used as a guard section.

One slot may include one or more flexible sections. Alternatively, one slot may not include a flexible section. Until the flexible period is overridden by a downlink period, an uplink period, etc., the terminal operates a predefined operation in the flexible period or a semi-static or periodically set operation from the base station (e.g., PDCCH Monitoring operation, synchronization signal/physical broadcast channel (SS/PBCH) block reception and measurement operation, CSI-RS (channel state information-reference signal) reception and measurement operation, downlink semi-persistent scheduling (SPS) PDSCH reception operation, A sounding reference signal (SRS) transmission operation, a physical random access channel (PRACH) transmission operation, a periodically configured PUCCH transmission operation, a PUSCH transmission operation according to a configured grant, etc.) may be performed. Alternatively, the terminal may not perform any operation in the flexible period until the flexible period is overridden by the downlink period or the uplink period.

The slot format may be semi-fixedly set by higher layer signaling (eg, radio resource control (RRC) signaling). Information indicating the semi-fixed slot format may be included in system information, and the semi-fixed slot format may be set cell-specifically. For example, the cell-specific slot format may be configured through the RRC parameter “TDD-UL-DL-ConfigCommon”. In addition, the slot format may be additionally configured for each terminal through terminal-specific upper layer signaling (eg, RRC signaling). For example, the UE-specific slot format may be configured through the RRC parameter “TDD-UL-DL-ConfigDedicated”. The flexible period of the slot format configured specifically for the cell may be overridden by the downlink period or the uplink period by UE-specific higher layer signaling. In addition, the slot format may be dynamically indicated by a slot format indicator (SFI) included in downlink control information (DCI).

The UE may perform a downlink operation, an uplink operation, and a sidelink operation in a bandwidth part. The bandwidth portion may be defined as a set of consecutive PRBs in the frequency domain having a specific neuron. Only one neuron may be used for transmission of a control channel or a data channel in one bandwidth portion. The terminal performing the initial access procedure may obtain configuration information of an initial bandwidth portion from the base station through system information. A terminal operating in an RRC connected state may obtain configuration information of a bandwidth portion from a base station through terminal-specific upper layer signaling.

The configuration information of the bandwidth portion may include a newer roller applied to the bandwidth portion (eg, subcarrier spacing and CP length). In addition, the setting information of the bandwidth portion may further include information indicating the position of the starting PRB of the bandwidth portion and information indicating the number of PRBs constituting the bandwidth portion. At least one of the bandwidth portion(s) set in the terminal may be activated. For example, each of one uplink bandwidth portion and one downlink bandwidth portion may be activated within one carrier. In a time division duplex (TDD)-based communication system, a pair of an uplink bandwidth portion and a downlink bandwidth portion may be activated. The base station may set a plurality of bandwidth portions in the terminal within one carrier and may switch the active bandwidth portion of the terminal.

In the embodiments, that a certain frequency band (for example, a carrier, a bandwidth part, a resource block (RB) set, a guard band, etc.) is activated means that the base station or the terminal uses the corresponding frequency band. It may mean that the signal can be transmitted and received. Further, that a certain frequency band is activated may mean that a radio frequency (RF) filter (eg, a band pass filter) of a transceiver is operating including the frequency band. In embodiments, the RB set may consist of consecutive RB(s). The RB set may be referred to as a "listen before talk (LBT) subband".

The minimum resource unit constituting the PDCCH may be a resource element group (REG). REG may consist of one PRB (eg, 12 subcarriers) in the frequency domain and one OFDM symbol in the time domain. Therefore, one REG may include 12 RE (resource elements). DM-RS (demodulation reference signal) for decoding of the PDCCH may be mapped to 3 REs among 12 REs constituting the REG, and control information (eg, modulated DCI) is the remaining 9 REs Can be mapped to.

One PDCCH candidate may consist of one CCE or aggregated CCEs. One CCE may be composed of a plurality of REGs. The NR communication system may support CCE aggregation levels 1, 2, 4, 8, 16, and the like, and one CCE may consist of 6 REGs.

The CORESET (control resource set) may be a resource region in which the UE performs blind decoding of the PDCCH. CORESET may be composed of a plurality of REGs. CORESET may be composed of one or more PRBs in the frequency domain and one or more symbols (eg, OFDM symbols) in the time domain. Symbols constituting one CORESET may be continuous in the time domain. PRBs constituting one CORESET may be continuous or discontinuous in the frequency domain. One DCI (eg, one PDCCH) may be transmitted within one CORESET. A plurality of CORESETs may be set from a cell perspective or a terminal perspective, and a plurality of CORESETs may overlap each other in time-frequency resources.

CORESET may be set in the terminal by PBCH (eg, system information transmitted through the PBCH). The ID (identifier) of CORESET set by the PBCH may be 0. That is, the CORESET set by the PBCH may be referred to as CORESET #0. A terminal operating in an RRC idle state may perform a monitoring operation at CORESET #0 in order to receive an initial PDCCH in an initial access procedure. Not only the terminal operating in the RRC idle state, but also the terminal operating in the RRC connected state can perform a monitoring operation in CORESET #0. CORESET may be set in the terminal by system information other than system information transmitted through the PBCH (eg, system information block type 1 (SIB1)). For example, in order to receive a random access response (or Msg2) in a random access procedure, the UE may receive SIB1 including setting information of CORESET. In addition, CORESET may be set in the terminal by terminal-specific higher layer signaling (eg, RRC signaling).

One or more CORESETs may be set for the UE for each downlink bandwidth part. Here, that the CORESET is set in the bandwidth part may mean "the CORESET is logically combined with the bandwidth part, and the terminal monitors the corresponding CORESET in the bandwidth part". The initial downlink active bandwidth part may include CORESET #0, and may be mutually combined with CORESET #0. CORESET #0 having a QCL (quasi co-location) relationship with an SS/PBCH block in a primary cell (PCell), a secondary cell (SCell), and a primary secondary cell (PSCell) Can be set for the terminal. CORESET #0 in the secondary cell may not be set for the terminal.

The search space may be a set of candidate resource regions in which the PDCCH can be transmitted. The UE may perform blind decoding on each of the PDCCH candidates within a predefined search space. The UE may determine whether the PDCCH has been transmitted to itself by performing a cyclic redundancy check (CRC) on the blind decoding result. When it is determined that the PDCCH is a PDCCH for the UE, the UE may receive the PDCCH.

The PDCCH candidate may be composed of CCE(s) selected by a hash function predefined within a CORESET or a search space occasion. The search space may be defined/set for each CCE aggregation level. In this case, the sum of the search spaces for all CCE aggregation levels may be referred to as a search space set. In embodiments, "search space" may mean "search space set", and "search space set" may mean "search space".

The set of search spaces may be logically associated with one CORESET. One CORESET can be logically combined with one or more sets of search spaces. A common search space set set through the PBCH may be used to monitor DCI scheduling a PDSCH for transmitting SIB1. The ID of the common search space set configured through the PBCH may be set to 0. That is, the common search space set configured through the PBCH may be defined as a type 0 PDCCH common search space set or search space set #0. Search space set #0 can be logically combined with CORESET #0.

The search space set may be divided into a common search space set and a UE-specific search space set according to a purpose or related operation. The common DCI may be transmitted in the common search space set, and the terminal-specific DCI may be transmitted in the terminal-specific search space set. In consideration of scheduling degrees of freedom and/or fallback transmission, a UE-specific DCI may be transmitted even in a common search space set. For example, the common DCI may include resource allocation information of PDSCH for transmission of system information, paging, power control command, slot format indicator (SFI), preemption indicator, and the like. The terminal-specific DCI may include PDSCH resource allocation information, PUSCH resource allocation information, and the like. A plurality of DCI formats may be defined according to the DCI payload, size, and type of radio network temporary identifier (RNTI).

In the following embodiments, the common search space may be referred to as a CSS (common search space), and the common search space set may be referred to as a CSS set. In addition, in the following embodiments, the UE-specific search space may be referred to as a UE-specific search space (USS), and the UE-specific search space set may be referred to as a USS set.

In the following embodiments, the signaling is PHY (physical) signaling (eg, DCI), MAC (medium access control) signaling (eg, MAC CE (control element)), and RRC signaling (eg, MIB ( master information block), system information block (SIB), cell-specific RRC signaling, terminal-specific RRC signaling, etc.). In addition, signaling (or setting) may mean both signaling (or setting) by an explicit method and signaling (or setting) by an implicit method. In the following embodiments, “signal” may be used as a meaning including “physical layer signal” and “physical layer channel”. For example, the downlink signal is a downlink physical layer signal (e.g., DM-RS, CSI-RS, PT (phase tracking)-RS, SS/PBCH block, etc.) and a downlink physical layer channel (e.g. , PDCCH, PDSCH, etc.). The uplink signal may include an uplink physical layer signal (eg, DM-RS, SRS, PT-RS, etc.) and an uplink physical layer channel (eg, PUCCH, PUSCH, PRACH, etc.).

Embodiments of the present invention can be applied to various communication scenarios using an unlicensed band. For example, with the help of the primary cell of the licensed band, the cell of the unlicensed band may be set as a secondary cell, and the carrier of the secondary cell may be aggregated with other carriers. Alternatively, a cell in an unlicensed band (eg, a secondary cell) and a cell in a licensed band (eg, a primary cell) may support a dual connectivity operation. Therefore, the transmission capacity can be increased. Alternatively, the cells of the unlicensed band may independently perform the function of the primary cell. Alternatively, the downlink carrier of the licensed band may be combined with the uplink carrier of the unlicensed band, and the combined carriers may perform one cell function. Conversely, the uplink carrier of the licensed band can be combined with the downlink carrier of the unlicensed band, and the combined carriers can perform one cell function. In addition, embodiments of the present invention can be applied not only to a communication system supporting an unlicensed band, but also to other communication systems (eg, a communication system supporting a licensed band).

In communication in an unlicensed band, a contention-based channel access method may be used to satisfy spectrum regulation conditions and coexist with an existing communication node (eg, a Wi-Fi terminal). For example, a communication node attempting to access a channel of an unlicensed band may check the channel occupancy status by performing a clear channel assessment (CCA) operation. The transmitting node (e.g., a communication node performing a transmitting operation) is based on a predefined (or preset) CCA threshold, whether the channel is in a busy state or an idle state. You can check whether it is. When the channel is in an idle state, the transmitting node may transmit a signal and/or a channel in the corresponding channel. The above-described operation may be referred to as a “listen before talk (LBT) operation”.

LBT operations can be classified into four categories depending on whether the LBT operation is performed or not and an application method. The first category (eg, LBT category 1) may be a method in which the transmitting node does not perform an LBT operation. That is, when the first category is used, the transmitting node may transmit a signal and/or a channel without performing a channel sensing operation (eg, a CCA operation). The second category (eg, LBT category 2) may be a method in which a transmitting node performs an LBT operation without random back-off. The second category may be referred to as “one-shot LBT operation”. In the third category (eg, LBT category 3), the transmitting node performs an LBT operation based on a random backoff value (eg, a random backoff counter) according to a fixed contention window (CW). It can be a way to do it. The fourth category (eg, LBT category 4) may be a method in which a transmitting node performs an LBT operation based on a random backoff value according to a contention window of a variable size.

The LBT operation may be performed in a specific frequency bundle unit. The frequency bundle may be referred to as “LBT subband”, “subband”, or “resource block (RB) set”. In the following embodiments, the RB set may mean an LBT subband or subband. Here, the LBT operation may include the aforementioned CCA operation. Alternatively, the LBT operation may include "CCA operation + signal and/or channel transmission operation according to CCA operation". The bandwidth of the RB set may differ depending on the frequency band or spectrum regulation by region, communication system, operator, manufacturer, etc. For example, in a band in which a Wi-Fi terminal and a 3GPP terminal coexist (eg, a 5 GHz band), the bandwidth of the RB set may be 20 MHz (or about 20 MHz). The communication node may perform a channel sensing operation and/or a signal transmission operation according to the channel sensing operation in units of 20 MHz (or units of about 20 MHz).

In a communication system (eg, an NR communication system or an LTE communication system), the RB set may be a set of consecutive RBs corresponding to about 20 MHz. In this case, the bandwidth of the set of consecutive RBs may not exceed 20 MHz. In the following embodiments, "the RB set is referred to as X _L MHz" may mean "the bandwidth of the RB set is X _L MHz or about X _L MHz". Unless otherwise stated, X _L can be assumed to be generally 20. In the following embodiments, RB may mean a PRB constituting a bandwidth portion depending on the case. Alternatively, RB may mean CRB (common RB) or VRB (virtual RB). In particular, when RB is used in the sense of an RB constituting a carrier, the RB may refer to a CRB constituting a carrier. In the NR communication system, the CRB may mean an RB on a common RB grid set in the terminal based on point A.

Point A may mean the frequency position of subcarrier #0 in CRB #0. Point A may be signaled from the base station to the terminal. For example, information indicating point A may be included in system information block 1 (SIB1) or remaining minimum system information (RMSI), and SIB1 or RMSI indicating point A may be transmitted. Alternatively, information indicating point A may be transmitted through UE-specific RRC signaling. The frequency range of the carrier or bandwidth portion may be set in the terminal based on point A.

Considering the above-described operation LBT, carriers and / or bandwidth of the bandwidth is set to the terminal portion may be set to a value approximate to a multiple or a multiple of the X _L X _L. For example, the carrier and/or bandwidth portion may be set to X MHz. Alternatively, the carrier and/or bandwidth portion may be configured as a set of consecutive RBs having a bandwidth approximating X MHz. Here, X may be 20, 40, 60, 80, or the like.

In the NR communication system, the carrier and/or bandwidth portion may be defined as a set of CRB(s) in the CRB grid, and the CRB(s) may correspond to the PRB(s). The bandwidth portion may be set to belong to one carrier. Alternatively, the bandwidth portion may be set to include a frequency domain of a plurality of carriers. When the bandwidth portion includes a frequency domain of a plurality of carriers, one bandwidth portion may be logically combined with the plurality of carriers.

3A is a conceptual diagram showing a first embodiment of a bandwidth portion in a communication system, FIG. 3B is a conceptual diagram showing a second embodiment of a bandwidth portion in a communication system, and FIG. 3C is a third embodiment of a bandwidth portion in a communication system. It is a conceptual diagram showing an example.

3A to 3C, one bandwidth portion may include a plurality of RB sets (eg, a plurality of LBT subbands). A plurality of carriers may be aggregated for the terminal, and each of the aggregated carriers (or a bandwidth portion corresponding to the aggregated carriers) may be composed of one or more RB sets. For example, one bandwidth portion may include 4 RB sets, and each RB set may have a bandwidth of 20 MHz. That is, it may be X _L =20. A transmitting node (eg, a base station or a terminal) may perform a CCA operation in units of an RB set before transmitting a signal and/or a channel. Depending on the result of the CCA operation, the channel(s) corresponding to some or all of the bandwidth portion may be occupied by the transmitting node, and the occupied channel(s) may be used for signal and/or channel transmission.

In the embodiment shown in Fig. 3A, the LBT operation performed at the transmitting node may succeed in all RB sets of the bandwidth portion. In this case, the transmitting node may transmit a signal and/or a channel using the entire band of the bandwidth portion. In the embodiment shown in FIG. 3B, the LBT operation performed at the transmitting node may succeed in RB sets #1, #3, and #4 belonging to the bandwidth portion. In this case, the transmitting node may transmit signals and/or channels using RB sets #1, #3, and #4.

In the embodiment shown in FIG. 3C, the LBT operation performed at the transmitting node may succeed in RB sets #1, #2, and #3 belonging to the bandwidth portion. In this case, the transmitting node may transmit signals and/or channels using RB sets #1, #2, and #3. In the embodiments, "the LBT operation is successful" means that the state of the channel is determined to be idle by an LBT operation (eg, a CCA operation) performed by a communication node (eg, a transmitting node). Can mean On the other hand, "LBT operation failed" means "the state of the channel is determined to be occupied by the LBT operation (eg, CCA operation) performed by the communication node (eg, the transmitting node)." can do.

Meanwhile, a guard band may be inserted between the RB sets included in the carrier and/or the bandwidth portion. The transmitting node may transmit a signal in the frequency domain excluding the guard band in the occupied RB set. Therefore, a normal channel sensing operation in an unoccupied RB set can be guaranteed. For example, in the embodiment shown in FIG. 3B, in order to ensure a normal channel sensing operation in RB set #2, guard bands may be inserted into RB sets #1 and #3, and the transmitting node is RB set # Signals and/or channels may not be transmitted in the guard bands 1 and #3. Therefore, interference to RB set #2 by communication using RB set #1 and/or #3 can be minimized. In the embodiment shown in FIG. 3C, in order to ensure a normal channel sensing operation in RB set #4, the guard band may be inserted into RB set #3, and the transmitting node signals in the corresponding guard band in RB set #3. And/or the channel may not be transmitted. Therefore, interference to RB set #4 by communication using RB set #3 can be minimized. The above-described guard band may be referred to as an in-carrier guard band in order to distinguish it from a guard band disposed outside a carrier bandwidth.

Configuration information of the RB set belonging to the carrier and bandwidth portion may be predefined for each "channel" to which the carrier and bandwidth portion are allocated. Also, configuration information of a guard band belonging to a carrier and a bandwidth portion may be predefined for each "channel" to which a carrier and a bandwidth portion are allocated. The configuration information of the RB set and the configuration information of the guard band include information indicating the number of RB sets constituting the carrier and/or bandwidth portion, information related to RB(s) constituting each RB set, and the carrier and/or bandwidth portion. It may include information indicating the number of guard bands constituting A, information related to a set of RB(s) constituting each guard band, and the like. For example, when the subcarrier interval is 30 kHz, the bandwidth of one RB set having a bandwidth of 20 MHz may be defined to correspond to 51 consecutive RBs. When the subcarrier spacing is 15 kHz, the bandwidth of one RB set having a bandwidth of 20 MHz may be defined to correspond to 106 consecutive RBs. The configuration information of the RB set and/or the configuration information of the guard band may be shared in advance between the base station and the terminal.

Alternatively, the base station may signal part or all of the configuration information of the RB set for the bandwidth part to the terminal. The frequency position of each RB set (eg, the starting PRB index of the RB set) may be predefined for each channel. Alternatively, the base station may signal information indicating the frequency position of each RB set to the terminal. For another example, the number of RB sets constituting the bandwidth portion, information on the RB(s) constituting each RB set, and/or information on the set of RB(s) constituting each guard band are provided by the base station. It can be signaled to the terminal. In a specific case, information on RB(s) constituting each RB set and information on a set of RB(s) constituting each guard band may have a mutually substitute relationship. In this case, one of information from "information on the RB(s) constituting each RB set" and "information on the set of RB(s) constituting each guard band" may be signaled from the base station to the terminal.

In the communication of the unlicensed band, the transmitting node can occupy a channel for a certain time when the LBT operation is successful. In this case, the channel occupancy time or the channel occupancy period may be referred to as “channel occupancy time (COT)”. "The sending node succeeds in the LBT operation" may mean "the sending node has secured the COT". The transmitting node may transmit a signal and/or a channel using some or all of the COT that it initiated. In addition, the COT initiated by the transmitting node may be shared with a receiving node (eg, a communication node performing a receiving operation). In the COT shared between the transmitting node and the receiving node, the receiving node can perform not only the receiving operation but also the transmitting operation. Therefore, the transmitting node can perform not only the transmission operation but also the reception operation within the shared COT. In embodiments, a transmitting node may mean a node that has initiated or initiated a COT (eg, an initiating node), and a receiving node is a signal from a corresponding COT without starting or initiating a COT. It may mean a node that transmits/receives.

The terminal may transmit a data channel in a carrier or a guard band within a bandwidth portion. Alternatively, the terminal may not be able to transmit the data channel in the guard band within the carrier or bandwidth portion. The terminal may determine whether to transmit the data channel in the guard band within the carrier or bandwidth portion according to the COT or the time interval within the transmission burst interval. The guard band (eg, guard RB(s)) may be regarded as a reserved resource. The protection RB(s) may be set as a reserved resource, and the terminal may transmit and receive a data channel (eg, PUSCH, PDSCH, PSSCH) by performing a rate matching operation on the reserved resource. The terminal may map the data channel to a resource region excluding the reserved resource, and may transmit the mapped data channel. The above-described operation of the terminal may be performed when some or all of the reserved resources are included in the resource region of the data channel.

4A is a conceptual diagram showing a first embodiment of a communication method within a COT.

Referring to FIG. 4A, a base station (eg, gNB) may acquire a COT by performing a CCA operation. The base station may transmit a downlink transmission burst at the beginning of the COT. The downlink transmission burst may mean a set or transmission of consecutive downlink signals and/or channels in the time domain. The uplink transmission burst may mean a set or transmission of consecutive uplink signals and/or channels in the time domain. When signals and/or channels constituting a downlink and uplink transmission burst are continuous in the time domain, it may mean that a gap between transmissions of signals and/or channels is less than or equal to a reference value. For example, the reference value may be 0. For another example, the reference value may be a value greater than 0 (eg, 16 μs). The COT initiated by the base station may be shared with the terminal. The terminal may transmit an uplink transmission burst within the shared COT.

In this case, the terminal may perform an LBT operation for transmission of an uplink transmission burst. For example, the UE may perform a CCA operation after transmission of the downlink transmission burst is finished. When it is determined that the channel state is idle as a result of the CCA operation, the terminal may transmit an uplink transmission burst. Alternatively, the terminal may transmit an uplink transmission burst without performing a CCA operation. For example, "when the time interval (eg, T1) between the downlink transmission burst and the uplink transmission burst is less than or equal to a preset value (eg, 16 µs)" or "the base station LBT operation according to LBT category 1 When the terminal is instructed to perform ", the terminal can transmit an uplink transmission burst without performing a CCA operation. T1 may be a time interval between the end point of the downlink transmission burst and the start point of the uplink transmission burst.

4B is a conceptual diagram showing a second embodiment of a communication method within a COT.

Referring to FIG. 4B, the UE may acquire a COT by performing a CCA operation. The UE may transmit an uplink transmission burst at the beginning of the COT. The COT initiated by the terminal may be shared with the base station. The base station may transmit a downlink transmission burst within the shared COT. In this case, the base station may perform an LBT operation for transmission of a downlink transmission burst. For example, the base station may perform a CCA operation after transmission of an uplink transmission burst is finished. When it is determined that the channel state is the idle state as a result of the CCA operation, the base station may transmit a downlink transmission burst. Alternatively, the base station may transmit a downlink transmission burst without performing a CCA operation. For example, if the time interval (eg, T2) between the uplink transmission burst and the downlink transmission burst is less than a preset value (eg, 16 μs), the base station performs a downlink transmission burst without performing a CCA operation. Can send. T2 may be a time interval between the end point of the uplink transmission burst and the start point of the downlink transmission burst.

The maximum occupancy time (or maximum transmission time of a signal) of a channel according to the CCA operation may be defined as a maximum COT (MCOT). In embodiments, the maximum occupancy time of the channel according to the CCA operation performed by the base station may be referred to as "downlink MCOT", and the maximum occupancy time of the channel according to the CCA operation performed by the terminal is "uplink MCOT. May be referred to as ". Accordingly, the COT initiated by the base station cannot exceed the downlink MCOT, and the COT initiated by the terminal cannot exceed the uplink MCOT. The downlink MCOT may be predefined in the technical standard according to frequency regulation, channel access priority class, and the like. The uplink MCOT may be predefined in the technical standard according to frequency regulation and channel access priority class. Alternatively, the base station may inform the UE of the uplink MCOT.

Meanwhile, uplink unicast data (eg, uplink shared channel (UL-SCH)) may be transmitted through an uplink data channel (hereinafter, referred to as “PUSCH”). The PUSCH may be scheduled by a dynamic grant or a configured grant. The scheme in which the PUSCH is scheduled by the dynamic grant may be a scheme of dynamically indicating the scheduling information of the PUSCH to the terminal through physical layer signaling (eg, DCI). DCI may be transmitted to the terminal through a downlink control channel (eg, PDCCH). The scheme in which the PUSCH is scheduled by the configuration grant is a semi-fixed configuration, a semi-permanent configuration, and/or a UE through higher layer signaling (e.g., RRC signaling) and/or physical layer signaling (e.g., DCI) scheduling information of the PUSCH. Alternatively, it may be a method of dynamically resetting.

The scheduling information of the PUSCH may include resource allocation information. The UE may receive, from the base station, a resource region in which a PUSCH (hereinafter, referred to as “setting grant PUSCH”) according to the setting grant can be transmitted. The resource region in which the configuration grant PUSCH can be transmitted may be referred to as a "configuration grant resource". When uplink traffic occurs, the UE may transmit a PUSCH in the configuration grant resource without receiving a separate scheduling request (SR) and a dynamic grant according to the scheduling request. In the NR communication system, the configuration grant resource configuration method can be classified into two types. In the type 1 configuration method of the configuration grant resource, both configuration of PUSCH scheduling information and activation of a resource (eg, configuration grant resource) may be performed by an RRC signaling procedure. In the type 2 configuration method of the configuration grant resource, the configuration of some scheduling information of the PUSCH may be performed by an RRC signaling procedure, and the configuration of the remaining scheduling information of the PUSCH and the activation of a resource (for example, a configuration grant resource) are physical. It may be performed by a layer signaling procedure (eg, DCI).

In the unlicensed band, the terminal can initiate or initiate the COT by transmitting the configuration grant PUSCH. In the embodiment shown in FIG. 4B, the uplink transmission burst may be initiated by the configuration grant PUSCH. That is, the start of the uplink transmission burst (e.g., symbols from the first symbol to the Xth symbol, slots from the first slot to the Yth slot, etc.) will be occupied by at least one configuration grant PUSCH. I can. In this case, the terminal may perform a random backoff-based LBT operation (eg, an LBT operation according to a third category or an LBT operation according to a fourth category) for channel access. PUSCH may be transmitted in the configuration grant resource.

The UE can transmit the PUSCH automatically using the configuration grant resource without receiving the dynamic grant from the base station. Therefore, the transmission delay according to the setting grant can be reduced compared to the transmission delay according to the dynamic grant. In addition, when the configuration grant is used, the probability of transmission failure of the PUSCH due to the failure of the LBT operation may be lower than the probability of transmission failure of the PUSCH due to the failure of the LBT operation when the dynamic grant is used. In the following embodiments, methods of setting a configuration grant resource in a communication system supporting an unlicensed band will be described.

[How to set up frequency domain resources]

Each of the one or more bandwidth portions may be composed of one or more RB sets. In the activated uplink bandwidth part or the activated downlink bandwidth part, the LBT operation may be performed for each RB set, and the combination of various RB sets according to the result of the LBT operation is a communication node (e.g., a terminal or Can be occupied by a base station). The UL transmission burst or DL transmission burst may be transmitted through a combination of various RB sets.

FIG. 5A is a conceptual diagram showing a first embodiment of a PUSCH transmission method according to a combination of RB set(s), and FIG. 5B is a conceptual diagram showing a second embodiment of a PUSCH transmission method according to a combination of RB set(s) to be.

5A and 5B, one uplink bandwidth portion may include three RB sets. The terminal may perform an LBT operation in each of the RB sets, and may occupy one of eight combinations of the RB sets according to the result of the LBT operation.

In the embodiment shown in FIG. 5A, the UE may transmit one PUSCH using all RB set(s) for which the LBT operation is successful. For example, when the LBT operation is successful in the first RB set and the second RB set (for example, a6), the UE transmits one PUSCH in a preset time interval through the first RB set and the second RB set. Can be transmitted. That is, one PUSCH may be mapped to the first RB set and the second RB set. One PUSCH may include one TB (transport block). Alternatively, when the number of PUSCH transport layers is greater than or equal to the reference value, one PUSCH may include a plurality of TBs. In this case, the frequency domain resource region of the PUSCH may be different for each combination of RB set(s).

In the transmission procedure of the configuration grant PUSCH, the base station may independently configure configuration grant resources for each of the combinations of RB set(s) corresponding to a1 to a7 of FIG. 5A to the terminal. The terminal may receive configuration information of 7 configuration grant resources from the base station. The frequency domain resource region of each of the configuration grant resources may respectively correspond to seven combinations of RB set(s). The PUSCH may be mapped to some or all of the PRB(s) constituting each RB set. In addition, guard bands may be inserted between RB sets constituting the bandwidth portion.

In the embodiment shown in FIG. 5B, the UE may transmit one PUSCH in each of the RB sets in which the LBT operation is successful. For example, when the LBT operation is successful in the first RB set and the second RB set (for example, b6), the UE provides one PUSCH through each of the first RB set and the second RB set in a preset time interval. Can be transmitted. That is, two PUSCHs may be transmitted. One PUSCH may include one TB. Alternatively, one PUSCH may include a plurality of TBs according to the number of PUSCH transport layers. In this case, the frequency domain resource region of the PUSCH may be allocated for each RB set. In the transmission procedure of the configuration grant PUSCH, the base station may independently configure the configuration grant resource for each of the RB sets to the terminal. That is, the terminal may receive configuration information of three configuration grant resources from the base station. The frequency domain resource region of each of the configuration grant resources may respectively correspond to three RB sets.

According to the above-described method, the terminal may have to receive configuration information of a plurality of configuration grant resources from the base station due to the uncertainty of the LBT operation. When a plurality of configuration grant resources are set according to a plurality of combinations of RB set(s), other configuration information other than frequency domain resource allocation information (e.g., time domain resource allocation information, DM-RS configuration information, antenna Port information, modulation and coding scheme (MCS) information, power control information, frequency hopping information, etc.) may be identically set for a plurality of configuration grant resources.

Even in this case, if a plurality of configuration grant resources are independently configured in the terminal, the same configuration information may be redundantly configured, and unnecessary signaling overhead may increase. In addition, in the embodiment shown in FIG. 5A, as the number of RB sets increases, the number of configuration grant resources to be set in the terminal may rapidly increase. In embodiments, “setting grant resource setting” may mean “an operation of setting setting grant resource”. In addition, "configuration grant resource configuration" may mean "configuration grant resource configuration information" or "a signaling unit of configuration grant resource configuration". The base station may set one or more configuration grant resource configurations to the terminal. That is, the terminal may receive one or more configuration grant resource configurations from the base station.

To overcome the problem of the above-described method, one configuration grant resource configuration may include allocation information of frequency domain resources for a plurality of combinations of RB set(s). This method is called "Method 100". "The operation of setting the setting grant resource" may include all operations according to the type 1 setting method and/or the type 2 setting method of the setting grant resource. For example, "an operation of setting the configuration grant resource" may include an activation operation of the configuration grant resource, a re-initialization operation of the configuration grant resource, and the like.

Frequency domain resource allocation information for each of the combinations of the RB set(s) may be individually set in the terminal. For example, frequency domain resource allocation information for each of the combinations of RB set(s) may be transmitted to the terminal through individual RRC parameters. This method is called "Method 110". Alternatively, one frequency domain resource allocation information (eg, one RRC parameter) may be set in the terminal. Based on one frequency domain resource allocation information (eg, frequency domain resource allocation information included in one configuration grant resource configuration), the UE Frequency domain resource allocation information for each of combinations of one or more RB sets) among the sets may be obtained. This operation is called "Method 120". In embodiments to which the method 120 is applied, information other than one frequency domain resource allocation information (eg, time domain resource allocation information) may be commonly configured for a plurality of terminals. In this case, the UE may obtain common time domain resource allocation information for combinations of RB set(s) (eg, one or more RB sets of all RB sets constituting the same bandwidth portion). One frequency domain resource allocation information and common time domain resource allocation information may be included in one configuration grant resource configuration.

Allocation schemes of frequency domain resources of an uplink channel (eg, PUSCH or PUCCH) in the unlicensed band will be described. In order to satisfy the requirements of the occupied channel bandwidth (OCB) in the unlicensed band, an interlace-based uplink channel (eg, PUSCH or PUCCH) resource allocation scheme in the frequency domain may be used. .

6 is a conceptual diagram illustrating a first embodiment of an interlace-based PUSCH frequency domain resource allocation scheme.

Referring to FIG. 6, the bandwidth portion may be set to 52 consecutive PRBs corresponding to CRB #12 to CRB #63. One interlace may be composed of PRBs corresponding to CRBs having the same interval. When a specific subcarrier spacing (eg, 15 kHz) is used, one interlace may be composed of PRBs corresponding to every tenth CRB. In this case, the interval M between CRBs may be 10. When M is 10, 10 different interlaces may be defined. Interlace #0 may be composed of PRBs corresponding to CRB #0, #10, #20, #30, and the like (ie, PRB #8, #18, #28, #38, and #48). Interlace #2 may be composed of PRBs corresponding to CRB #2, #12, #22, #32, etc. (ie, PRB #0, #10, #20, #30, #40, and #50). The position of each interlace may be determined based on point A. In addition, the number of PRBs constituting some interlaces may be one more than the number of PRBs constituting other interlaces according to the size of a bandwidth portion or an RB set. Alternatively, the number of PRBs constituting some interlaces may be one less than the number of PRBs constituting other interlaces according to the size of a bandwidth portion or an RB set.

The uplink channel (eg, PUSCH or PUCCH) may be allocated to one or more RB sets within one bandwidth portion. When the PUSCH is allocated to a plurality of RB sets, one interlace may be composed of PRBs of a plurality of RB sets, and PRBs corresponding to one interlace may correspond to CRBs having the same interval. The base station may set or indicate to the terminal one or more interlaces (eg, an interlace number, an interlace index) as frequency domain resource allocation information of the PUSCH. In addition, the base station may set or indicate to the terminal an RB set(s) to which the interlace(s) are mapped together with the interlace(s) (eg, the number of the RB set, the index of the RB set). The configuration information of the configuration grant resource may include frequency domain resource allocation information, and the frequency domain resource allocation information may include interlace information. Information of the RB set mapped to the interlace indicated by the frequency domain resource allocation information may be included in the corresponding frequency domain resource allocation information or the configuration information of the configuration grant resource.

In the embodiment shown in FIG. 6, the base station may set or instruct the terminal to interlace #0 or interlace #2. In this case, the UE may transmit the PUSCH in 5 PRBs corresponding to interlace #0. Alternatively, the UE may transmit a PUSCH in 6 PRBs corresponding to interlace #2. Alternatively, the base station may set or instruct the terminal to interlace #0 and #2. In this case, the UE may transmit PUSCH in 11 PRBs corresponding to interlace #0 and #2. In the embodiment shown in FIG. 6, the bandwidth portion may be composed of one RB set, and in this case, information on the RB set(s) may not be transmitted from the base station to the terminal.

FIG. 7 is a conceptual diagram illustrating a first embodiment of a PUSCH resource allocation method according to method 110, and FIG. 8 is a conceptual diagram illustrating a first embodiment of a PUSCH resource allocation method according to method 120.

7 and 8, a bandwidth portion consisting of two RB sets may be configured in a terminal. The bandwidth portion may be composed of 102 consecutive PRBs, and each RB set may be composed of 51 consecutive PRBs. The bandwidth portion may be an uplink bandwidth portion, and may be activated in the terminal in various ways. Depending on the result of performing the LBT operation, the UE may set the first RB set (hereinafter, referred to as “first RB combination”), the second RB set (hereinafter referred to as “the second RB combination”), or the first RB set and the second It may occupy a set of RBs (hereinafter referred to as "third RB combination"). The first RB combination may be an RB combination composed of a first RB set, the second RB combination may be an RB combination composed of a second RB set, and the third RB combination may be a first RB set and a second RB set. It may be a configured RB combination. The UE may transmit the PUSCH using the first RB combination, the second RB combination, or the third RB combination. The PUSCH may be a configuration grant PUSCH. In embodiments, the combination of RB set(s) may be referred to as “RB combination”.

In the embodiment shown in FIG. 7, for transmission of the PUSCH according to the RB combination, the terminal may receive configuration information of the configuration grant resource from the base station by method 110. For example, the base station may set any one configuration grant resource to the terminal. The configuration grant resource configuration may include allocation information of frequency domain resources for one or more RB combinations from among the first RB combination, the second RB combination, and the third RB combination.

In the embodiment shown in FIG. 7, for transmission of the configuration grant PUSCH in the first RB combination and the second RB combination, the terminal transmits the configuration information (eg, allocation information) of each of the interlaces #2 and #0 from the base station. Can receive. The configuration information for each of the interlaces #2 and #0 may be included in the configuration information (eg, frequency domain resource allocation information) of the configuration grant resource. Interlace #2 may be set for a first RB combination, and interlace #0 may be set for a second RB combination. The frequency domain resource allocation information may be used for transmission of the configuration grant PUSCH in the third RB combination.

For example, when one PUSCH is to be transmitted in the first RB set and the second RB set (for example, when the LBT operation is successful in the first RB set and the second RB set), the UE sets the PUSCH to the first It may map to interlace #2 of the RB set and interlace #0 of the second RB set. That is, the PUSCH may be mapped to 10 PRBs. Alternatively, the UE may receive interlace configuration information (allocation information) for transmission of the configuration grant PUSCH in the third RB combination from the base station. The interlace for the third RB combination may be set or indicated independently from the interlace for the other RB combination (eg, the first RB combination and the second RB combination). Information on the RB combination corresponding to the setting information of each interlace may be included in the setting grant resource setting.

In the embodiment illustrated in FIG. 8, the terminal may receive configuration information of the configuration grant resource according to method 120 from the base station. For example, the base station may set any one configuration grant resource to the terminal. The configuration grant resource configuration may include allocation information of a single frequency domain resource (or allocation information of a joint frequency domain resource).

The terminal may obtain allocation information of a single frequency domain resource from the base station, and each RB combination (e.g., one or more RBs from among all RB sets constituting one bandwidth part) based on the allocation information of a single frequency domain resource. Each combination of sets) can find out PRB allocation information for transmission of the configuration grant PUSCH. Also, the configuration grant resource configuration may include common time domain resource allocation information. The common time domain resource allocation information may be set for combinations of RB sets (eg, one or more RB sets among all RB sets constituting one bandwidth portion). The terminal may obtain not only single frequency domain resource allocation information but also common time domain resource allocation information from the configuration grant resource configuration.

In the embodiment shown in FIG. 8, the UE may receive configuration information of interlace #0 (eg, information indicating interlace #0) from the base station as allocation information of a single frequency domain resource for PUSCH. When it is desired to transmit the configuration grant PUSCH in the first RB set (e.g., when the LBT operation is successful in the first RB set), the UE transmits the PUSCH to interlace #0 (for example, PRB #0) in the first RB set. , #10, #20, #30, #40, and #50). When it is desired to transmit the configuration grant PUSCH in the second RB set (e.g., when the LBT operation is successful in the second RB set), the UE transmits the PUSCH to the interlace #0 (for example, PRB #60) in the second RB set. , #70, #80, #90, and #100).

When it is desired to transmit the configuration grant PUSCH in the third RB combination (e.g., when the LBT operation is successful in the first RB set and the second RB set), the UE sends the PUSCH to the interlace #0 in the third RB combination (e.g. For example, PRBs #0, #10, #20, #30, #40, #50, #60, #70, #80, #90, and #100) may be mapped. That is, the PUSCH may be mapped to 11 PRBs. In embodiments, interlace #0 may be configured based on PRB #0. However, the above-described configuration method is only one embodiment. Interlace #0 may be configured based on a different PRB (eg, one PRB from PRB #1 to PRB #9) according to the distance between PRB #0 and point A.

9 is a conceptual diagram illustrating a second embodiment of a method for allocating PUSCH resources according to method 120.

Referring to FIG. 9, a bandwidth portion composed of two RB sets may be configured in a terminal. The bandwidth portion may be composed of 102 consecutive PRBs, and each RB set may be composed of 49 consecutive PRBs. In addition, a guard band may be inserted between RB sets. The guard band may consist of 4 consecutive PRBs. The bandwidth portion may be an uplink bandwidth portion, and may be activated in the terminal in various ways. In the same or similar manner as in the above-described embodiments, the terminal is the first RB set (hereinafter, referred to as “first RB combination”) and the second RB set (hereinafter, “second RB combination”) according to the result of performing the LBT operation. "), or the first RB set and the second RB set (hereinafter referred to as "third RB combination") may be occupied. The UE may transmit the PUSCH using the first RB combination, the second RB combination, or the third RB combination. The PUSCH may be a configuration grant PUSCH.

In the embodiment shown in FIG. 9, according to method 120, the terminal indicates configuration information of interlaces #2 and #3 (e.g., interlaces #2 and #3 as allocation information of a single frequency domain resource for PUSCH). Information) can be received from the base station. When it is desired to transmit the configuration grant PUSCH in the first RB combination (e.g., when the LBT operation is successful in the first RB combination), the terminal uses the PUSCH as interlaces #2 and #3 in the first RB combination (e.g., RB #2, #3, #12, #13, #22, #23, #32, #33, #42, and #43) can be mapped. When it is desired to transmit the configuration grant PUSCH in the second RB combination (for example, when the LBT operation is successful in the second RB combination), the terminal uses the PUSCH as interlaces #2 and #3 in the second RB combination (e.g., RB #53, #62, #63, #72, #73, #82, #83, #92, and #93). In addition, if the configuration grant PUSCH is to be transmitted in the third RB combination (for example, when the LBT operation is successful in the third RB combination), the terminal uses the PUSCH as interlace #2 in the first RB set and the second RB set. And #3 (for example, RB #2, #3, #12, #13, #22, #23, #32, #33, #42, #43, #53, #62, #63, #72 , #73, #82, #83, #92, and #93). That is, the PUSCH may be mapped to 19 PRBs.

The embodiment shown in FIG. 9 may be an embodiment in which PUSCH is not transmitted in the guard band. Alternatively, in the case of transmitting the PUSCH in the third RB combination, the UE may map the PUSCH to the frequency domain including the guard band. In this case, the UE may transmit the PUSCH by additionally using PRB #52 belonging to both the guard band and interlace #2. For example, the terminal may activate the guard band from a predefined point in time (or a preset point in time) within the COT or transmission burst, and the guard band activated for transmission of an uplink signal (eg, PUSCH) You can use

In the embodiments shown in FIGS. 7 to 9, the base station allocates a configuration grant PUSCH resource for all possible RB combinations (eg, a first RB combination, a second RB combination, and a third RB combination) to the terminal. It can be a case. However, in general, the base station may allocate configuration grant resources to only some of the possible RB combinations. Method 120 may also be performed based on the above-described constraint condition. In method 120, when it is desired to allocate configuration grant resources to only some RB combinations, the base station sets information on the RB set(s) or RB combination(s) in which the configuration grant resources are set together with the interlace configuration information in the terminal Or you can direct. Interlace configuration information and information on the RB set(s) or RB combination(s) in which the configuration grant resource is configured may be included in the configuration information of the configuration grant resource. In this case, method 120 may be applied to RB set(s) or RB combination(s) set or indicated by the base station. For example, the UE may obtain frequency domain resource allocation information of the PUSCH for each of the combination(s) of the RB set(s) configured with the RB set(s) to which the configuration grant resource is allocated. These operations can also be applied to embodiments to be described later.

Meanwhile, some of the parameters configuring the configuration grant resource configuration may be set in the terminal, and a method shared by a plurality of configuration grant resource configurations may be used. This method may be "Method 200". For example, other information (eg, (common) time domain resource allocation information, etc.) other than frequency domain resource allocation information for a plurality of configuration grant resource configurations may be set to the same value. Method 200 may be used to reduce signaling overhead of configuration grant resource configuration. As an embodiment for the method 200, one or more configuration grant resource configurations may be regarded as one group or one set, and configuration grant resource configuration may be performed in groups. In this case, the parameter(s) shared by the setting grant resource setting(s) constituting the same group may be defined for the corresponding group and may be transmitted only once without duplication. The parameter(s) shared by the setting grant resource setting(s) constituting the same group may be set on a group basis. On the other hand, parameter(s) that are not shared by the setting grant resource setting(s) constituting a group (for example, frequency domain resource allocation information) may be defined for each setting grant resource setting, and may be independently transmitted. .

In another embodiment, the first configuration grant resource configuration may include information or an index for referring to the second configuration grant resource configuration. For example, the second configuration grant resource configuration may be configured in the terminal and may include all configuration parameters. In this case, the first configuration grant resource configuration may be configured in the terminal. The first configuration grant resource configuration may include some configuration parameters (eg, frequency domain resource allocation information). The remaining setting parameters for setting the first setting grant resource (eg, remaining setting parameters excluding frequency domain resource allocation information) may refer to setting the second setting grant resource.

Alternatively, the first configuration grant resource configuration may include an index of the second configuration grant resource configuration. In this case, the remaining configuration parameters for configuring the first configuration grant resource may refer to the second configuration grant resource configuration indicated by the index included in the corresponding first configuration grant resource configuration. Setting parameters that are not included in the first setting grant resource setting (eg, remaining setting parameters) may be considered to have the same values as the referenced setting parameters of the second setting grant resource setting. For example, the first configuration grant resource configuration may include frequency domain resource allocation information and an index of the second configuration grant resource configuration.

The type 1 configuration method of the configuration grant resource may be applied to the above-described embodiments. On the other hand, in the type 2 configuration method of the configuration grant resource, the resource and scheduling information of the configuration grant PUSCH may be activated or initialized by DCI. In this case, one or more configuration grant resource settings constituting the above-described group may be activated or initialized by one DCI. That is, a joint activation method or an initialization method by a single DCI may be used. A single DCI may include shared configuration parameter(s) only once, and configuration parameter(s) that are not shared may be included for each configuration grant resource configuration.

[How to determine TBS]

를 계산할 수 있다.The transport block size (TBS) for the data channel (eg, PUSCH, PDSCH) may be determined as a function of the total number of REs allocated to the data channel or an approximate value of the number of REs (hereinafter referred to as “N _RE ”). . This operation can be applied to an NR communication system. For example, the terminal is based on Equation 1 below

Can be calculated.

는 RB당 부반송파들의 개수일 수 있고,

는 슬롯 내에서 PUSCH에 할당된 심볼들의 개수일 수 있고,

는 데이터가 없는 DM-RS CDM(code division multiplexing) 그룹의 오버헤드를 포함한 PRB당 DM-RS들을 위한 RE 개수일 수 있고,

는 기지국으로부터 설정되는 오버헤드 값일 수 있다. 단말은 수학식 1에 의해 계산된

를 기초로 N_RE를 유도할 수 있다. 예를 들어, 단말은 아래 수학식 2에 기초하여 N_RE를 계산할 수 있다.

May be the number of subcarriers per RB,

May be the number of symbols allocated to the PUSCH in the slot,

May be the number of REs for DM-RSs per PRB including the overhead of a DM-RS code division multiplexing (CDM) group without data,

May be an overhead value set by the base station. The terminal is calculated by Equation 1

N _RE can be derived based on. For example, the terminal may calculate N _RE based on Equation 2 below.

n _PRB may be the number of PRBs allocated to the UE for PUSCH. As a next step, the UE may derive N _info, which is an intermediate value of information bits, based on the N _RE calculated by Equation 2. For example, the terminal may calculate N _info based on Equation 3 below.

R may be a target code rate, Q _m may be a modulation level, and v may be the number of transport layers. R, Q _m , and v may be dynamically scheduled to the terminal through DCI. Alternatively, R, Q _m , and v may be semi-permanently scheduled through RRC signaling to the terminal. As a next step, when N _info calculated by Equation 3 is less than or equal to the reference value, the UE can convert N _info into a quantized value according to a predefined equation, and the quantized value and the most You can select a TBS with a close value.

는 각 PUSCH 인스턴스에 할당되는 총 RE의 개수 또는 RE 개수의 근사값일 수 있다.On the other hand, when N _info calculated by Equation 3 exceeds the reference value, the terminal may directly derive the TBS from N _info based on the predefined equation. The above-described procedure can be applied when I _MCS is allocated to an entry having both R and Q _m (eg, 0≦I _MCS ≦27 or 0≦I _MCS ≦28). When the I _MCS is allocated to an entry other than the above-described entry, the UE may assume that the current TBS is the same TB size in the previous transmission procedure. When repeated PUSCH transmission is performed,

May be the total number of REs allocated to each PUSCH instance or an approximation of the number of REs.

In the following embodiments, a method of determining a TBS associated with a method of allocating a frequency domain resource of a configuration grant PUSCH will be described. According to method 100, one configuration grant resource configuration may include frequency domain resource allocation information for RB combinations (eg, combinations of RB set(s)). In this case, the TBS for PUSCH transmission in each of the RB combinations may be determined by frequency domain resource allocation for each of the RB combinations. For example, the terminal may derive or determine a TBS for each RB combination based on one configuration grant resource configuration. Specifically, the procedure of determining the TBS for each of the RB combinations may include considering the number of PRBs allocated for the PUSCH of the RB combinations as n _PRBs in method 100. Other steps for determining TBS for each RB combination may follow the above-described method.

Method 110 and method 120 may be methods in which the configuration and signaling of frequency domain resource allocation information of method 100 are embodied. Therefore, the method of determining TBS can also be applied to Method 110 and Method 120.

Referring back to the embodiment shown in FIG. 7 (for example, an embodiment to which method 110 is applied), the configuration grant PUSCH in the first RB combination is mapped to five PRBs constituting interlace #2, so that the terminal and The base station may regard the number of PUSCH PRBs as 5 (ie, n _PRB = 5), and may determine the TBS for the first RB combination based on the number of PUSCH PRBs. Here, the PUSCH PRB may be a PRB to which PUSCH is transmitted or mapped. In the second RB combination, since the configuration grant PUSCH is mapped to five PRBs constituting interlace #0, the UE and the base station may consider the number of PUSCH PRBs to be 5 (i.e., n _PRB = 5), and the PUSCH PRB TBS for the second RB combination may be determined based on the number. Since the configuration grant PUSCH in the third RB combination is mapped to 10 PRBs constituting interlace #2 of the first RB set and interlace #0 of the second RB set, the UE and the base station set the number of PUSCH PRBs to 10 (i.e. n _PRB = 10), and the TBS for the third RB combination may be determined based on the number of PUSCH PRBs.

Referring back to the embodiment shown in FIG. 8 (for example, an embodiment to which method 120 is applied), the configuration grant PUSCH in the first RB combination is mapped to six PRBs constituting interlace #0, so that the terminal and The base station may regard the number of PUSCH PRBs as 6 (ie, n _PRB = 6), and may determine the TBS for the first RB combination based on the number of PUSCH PRBs. In the second RB combination, since the configuration grant PUSCH is mapped to five PRBs constituting interlace #0, the UE and the base station may consider the number of PUSCH PRBs to be 5 (i.e., n _PRB = 5), and the PUSCH PRB TBS for the second RB combination may be determined based on the number. Since the configuration grant PUSCH in the third RB combination is mapped to 11 PRBs constituting the interlace #0 of the first RB set and the second RB set, the UE and the base station set the number of PUSCH PRBs to 11 (i.e., n _PRB = 11 ), and TBS for the third RB combination may be determined based on the number of PUSCH PRBs.

Referring again to the embodiment shown in FIG. 9 (for example, an embodiment to which method 120 is applied), the configuration grant PUSCH in the first RB combination is mapped to 10 PRBs constituting interlaces #2 and #3. , The UE and the base station may consider the number of PUSCH PRBs to be 10 (ie, n _PRB = 10), and may determine the TBS for the first RB combination based on the number of PUSCH PRBs. Since the configuration grant PUSCH in the second RB combination is mapped to 9 PRBs constituting interlace #2 and #3, the terminal and the base station may consider the number of PUSCH PRBs to 9 (i.e., n _PRB = 9), TBS for the second RB combination may be determined based on the number of PUSCH PRBs. Since the configuration grant PUSCH in the third RB combination is mapped to 19 PRBs constituting the interlaces #2 and #3 of the first RB set and the second RB set, the UE and the base station set the number of PUSCH PRBs to 19 (i.e., n _PRB = 19), and the TBS for the third RB combination may be determined based on the number of PUSCH PRBs.

According to the above-described methods, the number of different TBSs may occur as many as the maximum number of RB combinations. For example, when the bandwidth portion is composed of 4 RB sets, up to 15 different TBSs may be derived for each RB combination according to the above-described methods. Meanwhile, an upper layer of the terminal (eg, an entity performing an upper layer function) may generate a plurality of TBs having different sizes for the same HARQ process in consideration of a plurality of TBSs, and A plurality of TBs having a size may be delivered to a physical layer (eg, an entity performing a physical layer function) of the terminal. The physical layer of the terminal may select one TB from among a plurality of TBs having different sizes for the same HARQ process, and may transmit the selected TB through the PUSCH.

The TB selection criterion may be a combination of RB sets that succeed in the LBT operation. The physical layer of the terminal may inform the upper layer of the terminal of the TB selection result. Alternatively, the upper layer of the terminal may generate only one TB for one HARQ process, and may transmit one TB to the physical layer of the terminal. When a plurality of TBSs are derived for PUSCH transmission as in the above-described embodiment, one TB may have one size among a plurality of TBSs. In consideration of such a terminal operation, as the number of TBSs configured for transmission of the configuration grant PUSCH increases, the complexity of the MAC layer protocol of the terminal may increase.

As a method for limiting the number of TBSs, a plurality of RB combinations may be grouped, and a common TBS may be applied to RB combinations belonging to the same group. As an embodiment of the grouping method, RB combination(s) including the same number of RB sets may belong to the same group. In addition, the common TBS may be determined based on the PUSCH resource allocation of one RB combination (hereinafter referred to as "representative RB combination") among RB combination(s) belonging to the group. Alternatively, the common TBS may be determined based on PUSCH resource allocation of at least one RB combination (s) (eg, all RB combination (s)) among RB combination (s) belonging to the group.

Referring again to the embodiment shown in FIG. 8 (eg, an embodiment to which the method 120 is applied), the first RB combination and the second RB combination may belong to one group. In this case, a common TBS may be applied to the first RB combination and the second RB combination, and the common TBS may be determined based on allocation of one PUSCH resource from among the first RB combination and the second RB combination. For example, the first RB combination may be a representative RB combination for the group, and the common TBS for the first RB combination and the second RB combination may be determined by considering that n _PRB =6. According to this method, the number of TBSs that the terminal can assume for setting the corresponding configuration grant resource may be reduced by one. Although the above-described operations have been described as being applied when the bandwidth part is composed of two RB sets, the number of bandwidth parts to which the above-described operations are applied and the number of RB sets may not be limited. As the number of RB sets used for transmission of the configuration grant PUSCH increases, the effect of reducing the number of TBSs according to the above-described method may be greater.

The representative RB combination for the group of RB combination(s) may be signaled from the base station to the terminal. Alternatively, a representative RB combination for a group of RB combination(s) may be determined by a predefined rule. For example, the representative RB combination may be determined in consideration of the index or number of RB(s) constituting the RB combination(s). For another example, the representative RB combination may be determined by considering the TBS for the RB combination(s). For example, an RB combination having the smallest TBS or the largest TBS in a group may be considered a representative RB combination, and the smallest TBS or the largest TBS may be considered a common TBS.

As another method of setting the TBS, the base station may explicitly signal the TBS to the terminal. For example, TBS may be included in MCS (modulation and coding scheme) information, and MCS information including TBS may be transmitted. Alternatively, the TBS may be defined as a separate parameter, and a separate parameter may be transmitted. When methods 100 to 120 are used, the TBS may be set for each RB combination within one configuration grant resource configuration. Alternatively, as a method for solving the above-described problem, a common TBS for a plurality of RB combinations included in one configuration grant resource configuration may be explicitly signaled. For example, TBS may be set in a group unit of RB combination(s). Alternatively, the TBS may be set in units of setting grant resources.

On the other hand, when a plurality of configuration grant resource configurations are configured in the terminal, the TBS for each configuration grant resource configuration may be basically independently defined. Even in this case, if a plurality of configuration grant resource configurations are configured, there is a problem in that the UE considers a plurality of TBSs for uplink transmission. As a method for solving this problem, a method in which a plurality of configuration grant resource configurations share the same TBS may be used. For example, the base station may set the same TBS for the first configuration grant resource configuration and the second configuration grant resource configuration in the terminal. That is, the terminal may receive information indicating the same TBS for setting the first configuration grant resource and setting the second configuration grant resource from the base station.

According to the above-described embodiment, one or more configuration grant resource configurations may be regarded as one group or one set, and configuration grant resource configuration may be performed in groups. In this case, the setting grant resource setting(s) constituting the same group may have the same TBS. As a method for realizing this, similar to the above-described method, the common TBS may be determined based on the PUSCH resource allocation of one configuration grant resource configuration (hereinafter referred to as "representative configuration grant resource configuration") in the group. The representative configuration grant resource configuration may be determined by the terminal in a method similar to the determination method of the representative RB combination. Alternatively, a method of explicitly setting the TBS to the terminal may be used. In this case, the TBS may be defined for the configuration grant resource configuration group, and may be transmitted only once without duplication. For example, the TBS may be defined in units of a configuration grant resource configuration group. That is, method 200 can be used. When MCS information including TBS is transmitted, the MCS may be set to the same value in the configuration grant resource configuration group.

According to another embodiment described above, the first configuration grant resource configuration may include information or an index for referring to the second configuration grant resource configuration. In this case, the TBS of the first configuration grant resource configuration may be regarded as the same as the TBS of the second configuration grant resource configuration. In this case, the second setting grant resource setting may be regarded as the representative setting grant resource setting.

[How to select RB combination]

The terminal through the RB combination (e.g., the RB combination consisting of the largest number of RB set (s)) having the widest frequency range among the RB combination (s) consisting of the RB set (s) for which the LBT operation is successful. PUSCH can be transmitted. In this case, the terminal may transmit one PUSCH in the RB combination as in the embodiment shown in FIG. 5A. Alternatively, the UE may transmit one PUSCH in each RB set constituting the RB combination as in the embodiment shown in FIG. 5B. That is, when the RB combination is composed of a plurality of RB sets, the UE may transmit a plurality of PUSCHs through different RB sets at the same time.

The terminal may arbitrarily select one of the two methods described above, and may transmit a PUSCH based on the selected method. According to this method, the base station cannot know how many PUSCHs the terminal has transmitted. Therefore, the base station may have to perform a blind detection operation on the PUSCH. To prevent the base station from performing a blind detection operation for PUSCH, a COT (eg, a COT initiated by a terminal) or a transmission burst (eg, an uplink transmission burst) is divided into one or more time intervals. In each of the time periods, one of the two methods described above may be applied. For example, the start area of the COT or the transmission burst may be defined as a first period, and the remaining area of the COT or transmission burst (eg, an area other than the first period) may be defined as the second period. For example, the first interval may include symbols from a first symbol to an X-th symbol (ie, X symbols) of a COT or a transmission burst. Alternatively, the first period may include slots (eg, Y slots) from the first slot to the Y-th slot of the COT or transmission burst. Y slots may include partial slots according to the success point of the LBT operation. The base station may inform the terminal of information indicating the boundary between the first interval and the second interval through a signaling procedure.

The transmission method applied in each time interval may be predefined in the technical standard. For example, the transmission method according to the embodiment shown in FIG. 5B (for example, a method in which PUSCH is transmitted in each RB set) may be applied in the first section, and the embodiment shown in FIG. 5A in the second section The transmission method according to (for example, a method in which one PUSCH is transmitted in all RB sets in which the LBT operation is successful) may be applied. In this case, the base station can start the PUSCH detection operation in each RB set within the first interval, and the RB combination in which the PUSCH is transmitted through the detected PUSCH and/or other signals (for example, the LBT operation performed by the terminal is successful. RB combination) can be confirmed. Through this, the base station may perform a detection operation for one PUSCH in the RB combination in the second period. That is, the base station may receive the setting grant PUSCH without blind detection operation for a plurality of RB combinations in each section. Alternatively, the transmission method applied in each time interval may be signaled from the base station to the terminal.

The above-described methods can be applied to both a type 1 configuration method and a type 2 configuration method of the configuration grant resource. In the case of the type 2 configuration method of the configuration grant resource, the above-described methods can be applied for transmission of the remaining PUSCHs except for the PUSCH scheduled by the dynamic grant.

On the other hand, in the type 2 configuration method of the configuration grant resource, the base station schedules the PUSCH to the terminal through a dynamic grant (eg, DCI including uplink scheduling information) to activate the configuration grant resource, change the configuration, or Initialization operation can be performed. The PUSCH may be scheduled through DCI having CRC scrambled by CS (configured scheduling)-RNTI. In this case, when the frequency domain resource and TBS for a plurality of RB combinations are determined by the dynamic grant, the RB combination for transmitting the PUSCH may need to be determined. Even in this case, the UE is the RB combination having the widest frequency range among the RB combination(s) composed of the RB set(s) in which the LBT operation is successful (e.g., the RB composed of the largest number of RB set(s). Combination) can be transmitted through the PUSCH.

In this case, the base station may inform the UE of a method used for transmission of the PUSCH among the method according to the embodiment shown in FIG. 5A and the method according to the embodiment shown in FIG. 5B through a signaling procedure. For example, information indicating a method used for transmission of a PUSCH may be included in a dynamic grant (eg, DCI). That is, DCI including information indicating a method used for transmission of PUSCH may be transmitted to the terminal. As a generalized method for this operation, the base station may inform the terminal of the maximum number of transmittable PUSCHs and information on the RB set(s) to which each PUSCH is mapped. The terminal may transmit one or more PUSCHs in the RB set(s) in which the LBT operation is successful based on information received from the base station.

On the other hand, considering the HARQ retransmission procedure of PUSCH, a method in which information on the number of PUSCHs transmitted in the frequency domain and RB combination(s) through which each PUSCH is transmitted at a specific time point is dynamically determined by the terminal may be helpful. In this case, the UE can actively participate in the scheduling of the PUSCH. Accordingly, the UE may arbitrarily select one RB combination from among the RB combination(s) composed of the RB set(s) in which the LBT operation is successful, and transmit a PUSCH from the selected RB combination. This operation may be performed based on a type 1 setting method or a type 2 setting method of the configuration grant resource. The selection operation of the RB combination may be performed in the physical layer of the terminal. In this case, the upper layer of the terminal may generate a plurality of TBs for the same HARQ process, and may transfer the plurality of TBs to the physical layer of the terminal. Here, the sizes of the plurality of TBs may be different.

Alternatively, the RB combination selection operation may be performed in an upper layer (eg, MAC layer) of the terminal. In this case, the physical layer of the terminal may transmit information on the RB set (eg, the RB set occupied by the terminal) on which the LBT operation is successful to the upper layer of the terminal. The upper layer of the terminal may select an RB combination to transmit the PUSCH based on the result of the LBT operation, and may transmit information on the selected RB combination to the physical layer of the terminal. The physical layer of the terminal may transmit the PUSCH in the selected RB combination according to the instruction of the upper layer of the terminal.

[How to set up time domain resources]

In unlicensed band communication, the terminal may have to continuously transmit a plurality of TBs (eg, a plurality of uplink TBs). A plurality of TBs may be transmitted through a plurality of PUSCHs. In the COT occupied by the terminal, a plurality of TBs may be transmitted through a plurality of configuration grant PUSCHs. In order to support this operation, the UE must be able to transmit a plurality of PUSCHs (eg, a plurality of configuration grant PUSCHs) corresponding to a plurality of TBs within one period of the configuration grant resource. A plurality of TBs may be transmitted through different PUSCHs, and may correspond to different HARQ processes. In the following embodiments, a method of setting a time domain resource for a configuration grant PUSCH to support continuous transmission of an uplink TB will be described. The time domain resource allocation information may be included in the configuration information of the configuration grant resource.

The configuration grant resource may appear periodically and repeatedly. A period of the configuration grant resource may be set in the terminal, and one or more configuration grant resources may be allocated within one period of the configuration grant resource. Information indicating the period of the setting grant resource may be included in the setting information of the setting grant resource. The configuration grant resource may mean a candidate resource through which a PUSCH may be transmitted, and one PUSCH may be transmitted in each configuration grant resource. Each configuration grant resource may be disposed in one slot, and may be composed of consecutive symbol(s). In the following embodiments, the number of configuration grant resources allocated within one period may be expressed as "N". That is, N may mean the maximum number of PUSCHs that can be transmitted within one period. N can be a natural number.

In addition, M configuration grant resource(s) may be allocated within one period of the configuration grant resource. The M set grant resource(s) may be set continuously in the time domain. M can be a natural number. M consecutive configuration grant resource(s) may be referred to as a "configuration grant resource group". K configuration grant resource groups may be allocated within one period. K can be a natural number. In this case, the number of consecutive set grant resource(s) constituting the k-th set grant resource group (k=1, 2, ...K) may be expressed as _Mk . A plurality of configuration grant resource groups may not overlap each other. In this case, the sum of M ₁ to M _K may be equal to N.

When K is 1 (eg, when the number of configuration grant resource groups is 1), "M ₁ =M=N" may be defined. The above-described parameters (eg, N, M, M _k ) may be set in the terminal. The above-described parameters may be included in the setting information of the setting grant resource (eg, allocation information of the time domain resource). In addition, a time offset indicating the location of the configuration grant resource(s) or the configuration grant resource group(s) within one period may be set in the terminal. The time offset may be a slot unit offset or a symbol unit offset. The reference time point of the time offset may be a start time point of a period of the set grant resource or an absolute specific time point (eg, a start time point of a specific radio frame). Also, one or more time offsets may be set. For example, the time offset may be set for each configuration grant resource group.

FIG. 10A is a conceptual diagram illustrating a first embodiment of a method of setting a time domain resource of a setting grant PUSCH, and FIG. 10B is a conceptual diagram showing a second embodiment of a method of setting a time domain resource of a setting grant PUSCH.

10A and 10B, resources of eight consecutive configuration grant PUSCHs may be allocated to a terminal. Here, M or M _k may be 8. The resources of the configuration grant PUSCHs may be configured in the terminal in the form of a configuration grant resource group. The configuration grant PUSCH may be allocated within one period of the configuration grant resource. The location of the configuration grant PUSCH within one period of the configuration grant resource may be indicated by a time offset set in the terminal.

In this case, the RV of each configuration grant resource may be predefined. Alternatively, the RV of each configuration grant resource may be preset in the terminal. The UE may transmit the PUSCH using the RV corresponding to each configuration grant resource. A set of RV(s) (eg, RV pattern) may be set in the terminal. The RV pattern may be included in the setting information (eg, time domain resource allocation information) of the setting grant resource. The first RV constituting the RV pattern may be 0. In the embodiment shown in FIG. 10A, the RV pattern may be set to 0 or 2. The RV pattern may be repeatedly applied to the configuration grant resource(s). For example, in eight configuration grant resources, RVs may be 0, 2, 0, 2, 0, 2, 0, 2. The UE may start PUSCH transmission in a configuration grant resource having an RV set to 0 (ie, RV = 0).

In addition, the terminal may (repeated) transmit the PUSCH for the same TB within the configuration grant resource(s) corresponding to the length of the RV pattern. In the embodiment shown in FIG. 10A, the first TB may be transmitted in the first and second configuration grant resources, the second TB may be transmitted in the third and fourth configuration grant resources, and the third TB May be transmitted in the fifth and sixth configuration grant resources, and the fourth TB may be transmitted in the seventh and eighth configuration grant resources. The terminal can start PUSCH transmission for a certain TB in a configuration grant resource (eg, a third configuration grant resource) having an RV set to 0 (i.e., RV = 0), corresponding to the remaining RVs of the RV pattern. PUSCH for the same TB may be repeatedly transmitted in the configuration grant resource(s) (eg, the fourth configuration grant resource). The above-described embodiment may be effective in "when the LBT operation performed in the terminal succeeds within the third configuration grant resource" or "when the LBT operation performed in the terminal succeeds before the third configuration grant resource". Thereafter, for example, if the LBT operation is successful in the fifth configuration grant resource or the sixth configuration grant resource, the terminal PUSCH for TB in the fifth configuration grant resource having an RV set to 0 (ie, RV=0) Transmission can be started, and PUSCH for the same TB can be repeatedly transmitted in the sixth configuration grant resource after the fifth configuration grant resource.

In the embodiment shown in FIG. 10B, the RV pattern may be set to 0, 2, 3, or 1. The RV pattern may be repeatedly applied to the configuration grant resource(s). For example, in 8 configuration grant resources, RVs may be 0, 2, 3, 1, 0, 2, 3, 1. According to the above-described methods, the terminal may transmit the first TB in the first to fourth configuration grant resources and the second TB in the fifth to eighth configuration grant resources. The UE can start PUSCH transmission for a certain TB in a configuration grant resource (eg, a first configuration grant resource) having an RV set to 0 (i.e., RV = 0), and to the remaining RV(s) of the RV pattern The PUSCH for the same TB may be repeatedly transmitted in the corresponding configuration grant resource(s) (eg, second to fourth configuration grant resources). The above-described embodiment may be effective when "the LBT operation performed in the terminal succeeds within the first configuration grant resource" or "when the LBT operation performed in the terminal succeeds before the first configuration grant resource". According to the above-described method, the UE can start uplink burst transmission only in the first and fifth configuration grant resources among eight configuration grant resources.

According to the above-described embodiments, the UE may regard the length of the RV pattern as the maximum number of repetitive PUSCH transmissions for the same TB (or, a repetition factor, a slot aggregation factor). In this case, the repetition coefficient for setting the corresponding configuration grant resource may not be separately set in the terminal. Even when the number of the set grant resource(s) (eg, M _k , M, or N) is not divided by the length of the RV pattern, the RV pattern may be repeatedly applied repeatedly until the last set grant resource. In addition, the number of TBs that can be transmitted within one period of the configuration grant resource or in one configuration grant resource group may be determined by the length of the RV pattern.

11 is a conceptual diagram illustrating a third embodiment of a method of setting a time domain resource of a configuration grant PUSCH.

Referring to FIG. 11, resources of eight consecutive configuration grant PUSCHs may be allocated to a terminal. Here, M or M _k may be 8. In this case, the base station may set the RV for each configuration grant resource to the terminal. That is, the terminal may receive information indicating eight RVs for the first to eighth configuration grant resources from the base station. Here, the eight RVs may be 0, 2, 3, 1, 0, 0, 2, 0. The UE may start PUSCH transmission for a certain TB in a configuration grant resource (eg, a sixth configuration grant resource) having an RV set to 0 (ie, RV=0). In this case, the terminal is the configuration grant resource (s) (e.g., the seventh configuration grant resource) until the next configuration grant resource (e.g., the eighth configuration grant resource) having an RV set to 0 (i.e., RV = 0) Resources) may repeatedly transmit PUSCH for the same TB. The above-described embodiment may be effective when "the LBT operation performed at the terminal succeeds in the sixth setting grant resource" or "when the LBT operation performed at the terminal succeeds before the sixth setting grant resource". The terminal may transmit the first TB in the first to fourth configuration grant resources, the second TB in the fifth configuration grant resource, and the third TB in the sixth and seventh configuration grant resources. In addition, the fourth TB may be transmitted in the eighth configuration grant resource.

In the above-described embodiments, the RV may be set in a unit of setting grant resource setting. For example, when one configuration grant resource configuration includes a plurality of configuration grant resource groups, common RV information (eg, RV pattern, RV(s)) may be applied to a plurality of configuration grant resource groups. have. Alternatively, the RV information may be set for each configuration grant resource group. When multi-layer transmission is used, each of the first TB to the fourth TB may include a plurality of TBs. In addition, not only the above-described configuration grant resources, but also other configuration grant resource(s) (for example, different configuration grant resource groups) may be configured together, and configuration grant resources configured together have the same period and the same configuration grant resource configuration. You can follow.

Meanwhile, in order to effectively perform continuous uplink transmission in unlicensed band communication, it may be allowed that the UE retransmits the PUSCH in the configuration grant resource. In this case, within one period of the configuration grant resource, only one consecutive PUSCH transmission(s) for the same TB may be allowed. That is, the terminal may transmit the configuration grant PUSCH(s) for a certain TB in one or more consecutive configuration grant resource(s) within a certain period, and the terminal may not retransmit the PUSCH for the same TB within the same period. have. For example, the retransmission PUSCH for the same TB may be transmitted in the next period within the same or different uplink COT. Alternatively, within one period of the configuration grant resource, the UE may transmit consecutive PUSCH(s) for the same TB several times. Separately, the UE may transmit different TBs having the same HARQ process within one period of the configuration grant resource.

In the above-described embodiments, each configuration grant resource may be disposed in one slot. In this case, the duration of each configuration grant resource may occupy all of one slot. That is, the duration of each configuration grant resource may include all symbols (eg, 14 symbols) in one slot. Alternatively, the duration of each configuration grant resource may include some symbol(s) (eg, one or more symbols) in one slot. In this case, the number of symbols included in the configuration grant resource may be limited to a factor(s) of the number of symbols per slot. According to the above limitation, configuration grant resources may be aligned on a slot boundary, and may be continuously arranged in the time domain. This feature can be important in unlicensed band communications. Alternatively, the duration of each configuration grant resource may include a plurality of slots. The base station may set the duration of the configuration grant resource to the terminal. Information indicating the duration of the configuration grant resource may be included in the configuration information of the configuration grant resource. The duration of the configuration grant resource may be set in a configuration grant resource configuration unit or a configuration grant resource group unit. When the duration of the configuration grant resource is set in units of the configuration grant resource group, different durations may be applied in a plurality of configuration grant resource groups.

Meanwhile, in the unlicensed band communication, uplink control information (UCI) may be piggybacked on the set grant PUSCH. That is, the UE may map the UCI to a partial region of the configuration grant resource and may transmit the PUSCH and UCI together. Alternatively, the terminal may map the UCI to the entire configuration grant resource and may transmit the UCI. UCI may be information necessary for transmission of the configuration grant PUSCH. For example, UCI is a HARQ process ID (identifier), MCS, RV, NDI (new data indicator), UE-ID (eg, CS-RNTI, C (cell)-RNTI, MCS (modulation coding scheme)- C-RNTI, etc.), a channel access priority class (CAPC) of UL-SCH, and the like. The UCI piggybacked to the setting grant PUSCH may be referred to as “setting grant UCI” or “CG-UCI”. CG-UCI can be distinguished from conventional UCI including HARQ-ACK (acknowledgement), SR, and/or CSI. The transmission/reception operation of the CG-UCI may include an encoding operation and a decoding operation. For the transmission/reception operation of CG-UCI, a polar code, a Reed-Muller code, a low density parity check (LDPC) code, a turbo code, and the like may be applied. CRC may be applied to improve the decoding performance of CG-UCI. The CG-UCI may be included in all configuration grant PUSCHs, and configuration grant PUSCH including CG-UCI may be transmitted.

Each configuration grant PUSCH may be transmitted together with a HARQ process ID, RV, and NDI corresponding to the configuration grant PUSCH. Accordingly, the UE can arbitrarily determine the transmission location and the number of repetitions of the TB without dependence on the above-described RV pattern or the configuration grant resource group for repetitive transmission, and can transmit the TB based on the determined results. This operation may provide flexibility in terms of transmission of the terminal, but decoding performance of the PUSCH may deteriorate in terms of reception of the base station. For example, when the base station cannot receive some CG-UCI, the decoding performance of the PUSCH may be degraded. As a compromise point of the above-described trade-off, when the terminal arbitrarily determines the transmission location and/or the number of repetitions of the TB, a plurality of configuration grant PUSCHs for the same TB within one period of the configuration grant resource are It can be limited to being physically mapped to consecutive slots.

The base station may feed back HARQ-ACK information (eg, ACK or NACK (negative ACK)) for the PUSCH to the terminal. The NACK may be transmitted in an implicit manner by the base station transmitting an uplink grant for retransmission scheduling of the PUSCH to the terminal. Alternatively, HARQ-ACK information may be explicitly transmitted to the terminal. Explicit HARQ-ACK information corresponding to the PUSCH may be referred to as "downlink feedback information (DFI)." Here, the PUSCH may include a configuration grant PUSCH and a dynamic grant PUSCH.

The DFI may include HARQ-ACK information corresponding to all HARQ processes defined or configured in the terminal. DFI can be expressed as a bitmap. When the number of HARQ processes is N, the length of the bitmap representing DFI may be N or a multiple of N. Here, N may be a natural number. For example, when the maximum number of TBs that can be included in the PUSCH is M, the length of the bitmap may be M×N. Here, M may be a natural number. For another example, when the maximum number of code block groups (CBGs) that can be included in the PUSCH is L, the length of the bitmap may be N×M×L or N×M×L or less. Here, L may be a natural number. That is, the UE may obtain HARQ-ACK information corresponding to TB and/or CBG of all HARQ processes by receiving one DFI regardless of the presence or absence of PUSCH transmission for each HARQ process. DFI may be transmitted through PDCCH. The PDCCH including the DFI may be transmitted through a USS set or a CSS set. When the PDCCH including the DFI is transmitted through the CSS set, the corresponding PDCCH may be a group common PDCCH. That is, the CRC of the PDCCH can be scrambled by the group common RNTI, and the PDCCH can be received by the terminal group. The transmission timing of DFI can be defined as follows.

12 is a conceptual diagram showing the first embodiment of the DFI transmission timing.

Referring to FIG. 12, the DFI may be transmitted from the end point of the PUSCH (eg, the end point of the last symbol or the last symbol) to the point after the minimum duration (T). The minimum duration (T) may mean the minimum distance between the PUSCH resource and the DFI resource. The minimum duration T may be defined in a slot unit (eg, one or more slots) or a symbol unit (eg, one or more symbols). The base station may inform the terminal of the minimum duration (T) through a signaling procedure. For example, in the type 1 configuration method of the configuration grant resource, information indicating the minimum duration (T) may be signaled through an RRC message. In the type 2 configuration method of the configuration grant resource, information indicating the minimum duration (T) may be signaled through an RRC message or DCI (eg, DCI for activation or reconfiguration of a configuration grant resource).

On the other hand, it may be difficult for the UE to know which time interval the HARQ-ACK information included in the DFI corresponds to the PUSCH. This problem will be explained below.

13 is a conceptual diagram showing a first embodiment showing the ambiguity of DFI analysis.

Referring to FIG. 13, the UE may transmit a PUSCH (eg, a configuration grant PUSCH) in a time interval from slot n to slot (n+4). In addition, the terminal may receive DFI in slot (n+7). The above-described slots may belong to the COT initiated by the terminal. Alternatively, the slots described above may belong to the COT initiated by the base station. In case #1, the base station can start the encoding operation of the DFI in slot (n+3). In this case, the base station may reflect HARQ-ACK information (eg, ACK or NACK) for the PUSCH received in the time interval from slot n to slot (n+2) to DFI. HARQ-ACK information for the PUSCH received in the time interval of slot (n+3) and slot (n+4) may not be reflected in the corresponding DFI.

In case #2, the base station can start the encoding operation of the DFI in slot (n+4). In this case, the base station may reflect HARQ-ACK information for the PUSCH received in the time interval from slot n to slot (n+3) to DFI. HARQ-ACK information for the PUSCH in slot (n+4) may not be reflected in the corresponding DFI. In case #3, the base station can start the encoding operation of the DFI in slot (n+5). In this case, the base station may reflect HARQ-ACK information for all PUSCHs received in the time interval from slot n to slot (n+4) to DFI. The terminal may be difficult to know when the encoding operation of the DFI is performed in the base station, and it may be difficult to interpret specific HARQ-ACK information included in the DFI. For example, it may be difficult for the UE to know whether the HARQ-ACK information for HARQ process #1 reflects the reception result of the PUSCH in slot (n+3), and the HARQ-ACK information for HARQ process #2 is slot (n It may be difficult to know whether the PUSCH reception result is reflected in +4).

To solve this problem, a time window for DFI (hereinafter, referred to as “DFI window”) may be defined. The DFI window may mean a time interval in which PUSCH(s) related to HARQ-ACK(s) reflected in DFI are located. The DFI window may have a relative position from the time of transmission of the DFI. For example, the end time point of the DFI window may be a time point before a preset time interval from the start time point of the DFI. In addition, the start time of the DFI window may be a time before the preset time interval from the start time of the DFI or the end of the DFI window. The above-described viewpoints (eg, start time, end time) may be defined in units of slots. For example, the end time point of the DFI window may be a time point before V slots from the start time point of the slot in which the DFI is transmitted. Here, V may be a natural number.

Alternatively, the above-described viewpoints (eg, start time, end time) may be defined in units of symbols. For example, the end time point of the DFI window may be a time point before W symbols from the first symbol in which DFI is transmitted. Here, W may be a natural number. The DFI window may be predefined in the technical standard. Alternatively, the base station may set the DFI window to the terminal. For example, in the type 1 configuration method of the configuration grant resource, the DFI window may be indicated to the terminal by the RRC signaling procedure. In the type 2 configuration scheme of the configuration grant resource, the DFI window may be indicated to the terminal by an RRC signaling procedure or a dynamic signaling procedure. In the dynamic signaling procedure, DCI including information indicating the DFI window (eg, DCI for activation or reconfiguration of a configuration grant resource) may be transmitted. The information indicating the DFI window is from the start time of the DFI window, the offset between the start time of the DFI window and the start time of DFI, the end time of the DFI window, the offset between the end time of the DFI window and the start time of DFI, and the length of the DFI window. It may contain more than one.

The time distance (eg, V slots, W symbols) between the DFI window and the transmission time point of the DFI may be determined by the minimum duration (T). Alternatively, the minimum duration (T) may be determined by a time distance between the DFI window and the transmission time point of the DFI. For example, the time distance between the DFI window and the transmission time point of the DFI may coincide with the minimum duration (T). For another example, the time distance between the DFI window and the transmission time point of the DFI may be greater than or equal to the minimum duration (T).

14A is a conceptual diagram showing a first embodiment of a method for setting a DFI window, and FIG. 14B is a conceptual diagram showing a second embodiment of a method for setting a DFI window.

Referring to FIG. 14A, the UE may transmit a PUSCH (eg, a configuration grant PUSCH) in a time interval from slot n to slot (n+4), and may receive a DFI in slot (n+7). . The end time point of the DFI window may be defined or set as a time point before T _w (eg, two slots or 28 symbols) from the start time point of DFI transmission. The DFI window may be a time interval from slot m to slot (n+4). Slot m may be a slot located before slot n. In this case, the UE may assume that the DFI includes HARQ-ACK information for PUSCH transmission in a time interval from slot m to slot (n+4).

Referring to FIG. 14B, the UE may transmit a PUSCH (eg, a configuration grant PUSCH) in a time interval from slot n to slot (n+4), and may receive a DFI in slot (n+5). . The end time point of the DFI window may be defined or set as a time point before T _w (eg, two slots or 28 symbols) from the start time point of DFI transmission. The DFI window may be a time interval from slot m to slot (n+2). Slot m may be a slot located before slot n. In this case, the UE may assume that the DFI includes HARQ-ACK information for PUSCH transmission in a time interval from slot m to slot (n+2).

The methods according to the present invention may be implemented in the form of program instructions that can be executed through various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like alone or in combination. The program instructions recorded on the computer-readable medium may be specially designed and configured for the present invention, or may be known and usable to those skilled in computer software.

Examples of computer-readable media include hardware devices specially configured to store and execute program instructions, such as rom, ram, flash memory, and the like. Examples of program instructions include not only machine language codes such as those produced by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like. The above-described hardware device may be configured to operate as at least one software module to perform the operation of the present invention, and vice versa.

Although described with reference to the above embodiments, those skilled in the art will understand that various modifications and changes can be made to the present invention without departing from the spirit and scope of the present invention described in the following claims. I will be able to.

Claims (20)

As a method of operating a terminal in a communication system,
Receiving information on one CG (configured grant) configuration for uplink transmission from a base station;
Obtaining common time domain resource allocation information for combinations of resource block (RB) sets based on the information on the one CG configuration;
Acquiring frequency domain resource allocation information for each of the combinations of the RB sets based on the information on the one CG configuration;
Determining the number of physical resource blocks (PRBs) to which an uplink channel is mapped based on the frequency domain resource allocation information corresponding to one of the combinations;
Determining a transport block size (TBS) based on the common time domain resource allocation information and the number of the PRBs; And
And transmitting the TB having the TBS to the base station through the uplink channel according to the common time domain resource allocation information and the frequency domain resource allocation information within the one combination. The method according to claim 1,
The RB sets are located within the same bandwidth part. The method according to claim 1,
The frequency domain resource allocation information includes information indicating one or more interlaces applied to each of the combinations. The method according to claim 1,
Each of the RB sets includes consecutive RBs in the frequency domain, and when the RB sets include a first RB set and a second RB set, the combinations are "combination consisting of the first RB set", "the first 2, a combination consisting of RB sets", and "a combination consisting of a first RB set and a second RB set", the operating method of the terminal. The method according to claim 1,
A guard band is located between the RB sets, and the guard band disposed between the RB sets constituting the one combination is used for transmission of the uplink channel. The method according to claim 1,
The one combination is determined based on a combination of one or more RB sets in which a listen before talk (LBT) operation performed in the terminal is successful. The method according to claim 2,
The RB sets are one or more RB sets among all RB sets constituting the same bandwidth portion, and the information information on the one CG configuration is information indicating the one or more RB sets or combinations of the one or more RB sets. Further comprising, the operating method of the terminal. The method according to claim 1,
The information on the one CG configuration further includes information indicating a set of redundancy version (RV), and the TB is repeatedly transmitted according to the set of RVs. The method according to claim 1,
The operating method of the terminal,
Receiving HARQ (hybrid automatic repeat request)-ACK (acknowledgement) information from the base station, wherein the HARQ-ACK information is a reception response to the TB transmitted in a time window, the time window is the HARQ -Determined by the time point at which the ACK information is received, the operating method of the terminal. As a method of operating a base station in a communication system,
Generating frequency domain resource allocation information for each of combinations of resource block (RB) sets;
Transmitting information on one CG (configured grant) configuration including the frequency domain resource allocation information to the terminal; And
Receiving a TB (transport block) from the terminal in an uplink channel according to the frequency domain resource allocation information,
The frequency domain resource allocation information includes information indicating one or more interlaces applied to each of the combinations, and the size of the TB is the number of physical resource blocks (PRBs) corresponding to the one or more interlaces Determined based on the method of operation of the base station. The method of claim 10,
When the RB sets are located within the same bandwidth part, each of the RB sets includes consecutive RBs in the frequency domain, and the RB sets include a first RB set and a second RB set, the combination Are "combination composed of a first RB set", "combination composed of a second RB set", and "a combination composed of a first RB set and a second RB set". The method of claim 10,
The RB sets are one or more RB sets among all RB sets constituting the same bandwidth portion, and the information on the one CG configuration further includes information indicating the one or more RB sets or combinations of the one or more RB sets. Including, a method of operation of the base station. The method of claim 10,
The information on the one CG configuration further includes common time domain resource allocation information indicating a set of redundancy version (RV), and the TB is repeatedly transmitted from the terminal according to the set of RVs, and the common The time domain resource allocation information is set for combinations of the RB sets. The method of claim 10,
The method of operating the base station,
Further comprising the step of transmitting hybrid automatic repeat request (HARQ)-ACK (acknowledgement) information to the terminal, wherein the HARQ-ACK information is a reception response to the TB received in a time window, the time window is the HARQ -Determined by the time of reception of ACK information, the operation method of the base station. As a terminal in a communication system,
Processor;
A memory in electronic communication with the processor; And
Contains instructions stored in the memory,
When the instructions are executed by the processor, the instructions are the terminal,
Receiving information on one CG (configured grant) configuration for uplink transmission from the base station;
Acquiring frequency domain resource allocation information for each of combinations of resource block (RB) sets based on the information on the one CG configuration;
Determining the number of physical resource blocks (PRBs) to which an uplink channel is mapped based on the frequency domain resource allocation information corresponding to one of the combinations;
Determining a transport block size (TBS) based on the number of PRBs; And
The terminal operating to cause the transmission of the TB having the TBS to the base station through the uplink channel according to the frequency domain resource allocation information within the one combination. The method of claim 15,
The frequency domain resource allocation information includes information indicating one or more interlaces applied to each of the combinations. The method of claim 15,
When the RB sets are located within the same bandwidth part, each of the RB sets includes consecutive RBs in the frequency domain, and the RB sets include a first RB set and a second RB set, the combination Are "a combination composed of a first RB set", "a combination composed of a second RB set", and "a combination composed of a first RB set and a second RB set". The method of claim 15,
The RB sets are one or more RB sets among all RB sets constituting the same bandwidth portion, and the information on the one CG configuration further includes information indicating the one or more RB sets or combinations of the one or more RB sets. Including, terminal. The method of claim 15,
The information on the one CG configuration further includes common time domain resource allocation information indicating a set of redundancy version (RV), and the TB is repeatedly transmitted according to the set of RVs, and the common time domain resource The allocation information is set for combinations of the RB sets. The method of claim 15,
The above commands are:
It operates to further cause the reception of hybrid automatic repeat request (HARQ)-ACK (acknowledgement) information from the base station, and the HARQ-ACK information is a reception response to the TB transmitted in a time window, and the time window is the Terminal determined by the time point at which the HARQ-ACK information is received.

Images